Open Stack

Radomir, thanks for adding some clarity. I do have follow-on questions.

In your example the packages are managed by xstatic. The proposal for
horizon, as I understand it, is to move away from xstatic packages and
instead use bower for development and system packages (for example, debian,
rpm, and other packages) for production. Right now, we (the horizon
community) is maintaining some of the xstatic packages. For many of these
xstatic packages there is no corollary in a system package. Who will create
and maintain the system packages for the JavaScript libraries?

You noted that "we get maintenance and updates for free." Since the system
packages don't exist now and we don't know who will create or maintain them
I'm not sure how to reconcile this.

What am I missing?


On Wed, Jan 21, 2015 at 3:04 AM, Radomir Dopieralski <openstack at sheep.art.pl
> wrote:

> On 20/01/15 20:58, Matthew Farina wrote:
> > Radomir, maybe you can help me better understand where this would go. I
> > have a few questions.
> >
> > First, can you point me to a time when horizon used system packages
> > successfully for JavaScript libraries? When I looked through the Debian
> > and Ubuntu packages I couldn't find the libraries horizon is using. I'm
> > curious to see this in action.
>
> Any distribution (perhaps except Ubuntu, which is a little funny in that
> regard) that has packaged the latest release of OpenStack, has those
> libraries.
> For instance, see
>
> http://pkgs.fedoraproject.org/cgit/python-django-horizon.git/tree/python-django-horizon.spec#n129
>
>
> > Front-end systems almost never use system packagers like this. Can you
> > point me to applications like horizon that use system packages this way?
> > If Horizon is going to go it virtually alone in this space, what will
> > that mean for our level of work and ability to have updates?
>
> Certainly. The XStatic system itself is lifted from MoinMoin wiki, for
> example -- it was created to solve exactly this problem there, and is
> used by a couple of other projects too.
>
> As for our work and updates, using system-wide packages is an excellent
> solution in this regard, as we get maintenance and updates for free. For
> instance, if there is a security issue in one of the JavaScript
> libraries, we don't need to patch Horizon -- the patch that is prepared
> for that specific library and applied system-wide is sufficient.
> --
> Radomir Dopieralski
>
>
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> 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/20150121/5c1ca313/attachment.html>