[openstack-dev] [horizon] packaging problem production build question

Matthew Farina matt at mattfarina.com
Thu Jan 8 22:46:41 UTC 2015

Thanks for humoring me as I ask these questions. I'm just trying to connect
the dots.

How would system packages work in practice? For example, when it comes to
ubuntu lucid (10.04 LTS) there is no system package meeting the jQuery
requirement and for precise (12.04 LTS) you need precise-backports. This is
for the most popular JavaScript library. There is only an angular package
for trusty (14.04 LTS) and the version is older than the horizon minimum.

private-bower would be a nice way to have a private registry. But, bower
packages aren't packages in the same sense as system or pypi packages. If I
understand it correctly, when bower downloads something it doesn't get it
from the registry (bower.io or private-bower). Instead it goes to the
source (e.g., Github) to download the code. private-bower isn't a package
mirror but instead a private registry (of location). How could
private-bower be used to negate network effects if you still need to go out
to the Internet to get the packages?

On Thu, Jan 8, 2015 at 5:11 PM, David Lyle <dklyle0 at gmail.com> wrote:

> Bower is not for use in production environments. There will continue to be
> two environment setup procedures, as there are today. For production,
> deploy Horizon and its dependencies via system packages. For development
> and testing leverage bower to pull the javascript resources, much as pip is
> used today and continue to use pip for python dependencies.
> For those running CI environments, remote access will likely be required
> for bower to work. Although, it seems something like private-bower [1]
> could be utilized to leverage a local mirror where access or network
> performance are issues.
> David
> [1] https://www.npmjs.com/package/private-bower
> On Thu, Jan 8, 2015 at 2:28 PM, Matthew Farina <matt at mattfarina.com>
> wrote:
>> I've been going over the packaging problem in an effort to see how we can
>> move to something better. Given the current proposal around bower I'm still
>> left with a production deployment question.
>> For a build environment sitting in isolation, unable to download from the
>> Internet including Github, how would they be able to get all the bower
>> controlled packages to create a system horizon package (e.g., rpm or deb)?
>> These build environments currently use mirrors and controlled packages.
>> For example, someone might have a pypi mirror with copies of the xstatic
>> packages. This is tightly controlled. If bower is managing packages where,
>> in theory, would it get them from for an environment like this?
>> I may have missed something. If this has already been answered please
>> excuse me and point me in the right direction.
>> Thanks,
>> Matt
>> _______________________________________________
>> OpenStack-dev mailing list
>> OpenStack-dev at lists.openstack.org
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20150108/31f9598b/attachment.html>

More information about the OpenStack-dev mailing list