Hue Charm

[Cory Johns]

My natural reaction is to say that it would be better to keep the build and
charm logic  separated and just resources (in juju 2.0) to provide those
built artifacts to the charm.  However, with layers, it does seem like we
have a fairly clean way to separate the maintenance burden, so maybe the
benefits of being able to do builds on the fly outweighs the additional
complexity.

Of course, trying to do automatic, JIT builds still runs the risk of it
failing and needing manual intervention, but that's not much different than
the situation where we don't have a pre-built combination for your
deployment.

On Thu, Feb 4, 2016 at 8:33 AM, Merlijn Sebrechts <
merlijn.sebrechts at gmail.com> wrote:

> This build layer is a great idea! If I understand this correctly this
> layer would not be included in the gobblin charm?
>
> I was thinking of doing something similar for my Charms. I'd include a
> pre-build tarball in the charm that is build for a specific combination of
> hadoop+spark+scala versions. When it connects to spark, it checks if it
> includes a tarball for that version combination. If not, it builds it from
> source specifying the correct versions. This way, the Charm could support
> multiple versions.. While still having a fast deploy for the default
> version. What do you think?
>
>
> Op donderdag 4 februari 2016 heeft Cory Johns <cory.johns at canonical.com>
> het volgende geschreven:
> > We have a charm for building Gobblin (
> https://github.com/juju-solutions/layer-gobblin-binary-builder). We are
> planning to expand to contain the build logic for any big data artifact
> that we don't get directly from upstream (or possibly even those, in case a
> custom build is desired).
> > This allows our builds to be repeatable (and auditable), and makes it
> easy to build for different architectures just using Juju.
> > I have created an issue for adding the Hue build process to that charm:
> https://github.com/juju-solutions/layer-gobblin-binary-builder/issues/2
> > On Thu, Feb 4, 2016 at 1:20 PM, Andrew Mcleod <
> andrew.mcleod at canonical.com> wrote:
> >>
> >> Thanks Cory, I was planning on using the info from the relation but
> this is far from a complete charm.
> >> Merlijn, I built the tarball from the source on gethue.com:
> >>
> https://dl.dropboxusercontent.com/u/730827/hue/releases/3.9.0/hue-3.9.0.tgz
> >>
> >>
> >>
> >> On Thu, Feb 4, 2016 at 11:15 AM, Merlijn Sebrechts <
> merlijn.sebrechts at gmail.com> wrote:
> >>>
> >>> Thanks! I see you use a pre build tarball. Did you build this yourself
> or is this something distributed by the hue folks? I'll look further into
> this and create a pull request next week.
> >>>
> >>> Op woensdag 3 februari 2016 heeft Andrew McLeod <
> andrew.mcleod at canonical.com> het volgende geschreven:
> >>> > Hi Merlijn,
> >>> >
> >>> > The url is https://github.com/andrewdmcleod/layer-apache-hue -
> however I'll have to check that I've pushed up my recent changes tomorrow.
> Readme etc hasn't been completed as you will see.
> >>> >
> >>> >
> >>> >
> >>> > Andrew M.
> >>> >
> >>> >
> >>> >> On 3 Feb 2016, at 18:17, Merlijn Sebrechts <
> merlijn.sebrechts at gmail.com> wrote:
> >>> >>
> >>> >> Hi folks
> >>> >>
> >>> >>
> >>> >> Could you provide me with a link to the WIP hue Charm? I'd like to
> look at it to see whether we could merge it with my WIP Hue and Livy
> Charm...
> >>> >>
> >>> >>
> >>> >>
> >>> >> Kind regards
> >>> >> Merlijn
> >>> >> --
> >>> >> Bigdata mailing list
> >>> >> Bigdata at lists.ubuntu.com
> >>> >> Modify settings or unsubscribe at:
> https://lists.ubuntu.com/mailman/listinfo/bigdata
> >>> >
> >>
> >> --
> >> Bigdata mailing list
> >> Bigdata at lists.ubuntu.com
> >> Modify settings or unsubscribe at:
> https://lists.ubuntu.com/mailman/listinfo/bigdata
> >>
> >
> >
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/bigdata/attachments/20160212/cb6ecb14/attachment.html>