Hi Billy On Thu, 30 Jun 2016 at 17:24 Billy Olsen <billy.ol...@gmail.com> wrote:
> I suspect that the reactive charming model wouldn't have this issue > due to the ability to essentially statically link the libraries via > wheels/pip packages. If that's the case, it's likely possible to > follow along the same lines as the base-layer charm and bootstrap the > environment using pip/wheel libraries included at build time. As I see > it, this would require: > > * Updates to the process/tooling for pushing to the charm store > * Update the install/upgrade-charm hook to bootstrap the environment > with the requirements files > * If using virtualenv (not a requirement in my mind), then each of the > hooks needs to be bootstrapped to ensure that they are running within > the virtualenv. > I was thinking of something along those lines as well. I'll spike on something this week to figure out exactly how this might work. > To make life easier in development mode, the charms can downla > build step before deployment, though certainly for the published > versions the statically linked libraries should be included (which, > from my understanding, I believe the licensing allows and why the > reactive charming/layered model wouldn't have this issue). > That sounds like a neat idea (although building out a layered charm is pretty easy as well).
__________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
