VCS code duplication and subordinate
marco at ondina.co
Mon Mar 11 15:03:35 UTC 2013
This might be a good time to mention there's a VCS Charm Helper:
use can be seen in the WordPress charm:
it doesn't handle things like maintenance, branches, authentication, it's
does alleviate the need of having a subordinate charm.
On Mon, Mar 11, 2013 at 10:24 AM, Mark Ramm <
mark.ramm-christensen at canonical.com> wrote:
> On 03/10/2013 02:06 PM, Patrick Hetu wrote:
>> In the process of building the Django charm, I realized that a lot of
>> charms are
>> repeating the parts that handle VCS. Like:
>> There is also a blueprint here:
>> So, I was thinking that we could create one subordinate charm per VCS to:
>> 1) Reduce the installation time
>> 2) Ease the maintenance
>> 3) Include more advance stuff like branches, authentification, etc
>> What do you think?
>> It's also possible to add this to a standard library of charm tools,
> rather than do it in a subordinate.
> What advantages do you see in doing it as a subordinate? Language
> independence is one, I'm sure there are others that I'm not seeing. But I
> also think it makes the relationship between charms and subordinates
> significantly more complicated, since install of one service could actually
> *require* a subordiate, and we don't yet have any way of managing
> requirements, and I personally would like to avoid needing to do
> charm-dependency graph resolution if at all possible.
> --Mark Ramm
> Juju mailing list
> Juju at lists.ubuntu.com
> Modify settings or unsubscribe at: https://lists.ubuntu.com/**
> mailman/listinfo/juju <https://lists.ubuntu.com/mailman/listinfo/juju>
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Juju