One of the major features using a distro over upstream gives is integration.
rhel6 behaves differently then ubuntu 13.10. Sometimes it takes a while to fix 
upstream for a given distro, and even then it may not even be accepted because 
"the distro's too old, go away". Packages allow a distro to make sure all the 
pieces can work together properly. And quickly patch things when needed. Its 
kind of a fork but not quite the same thing. The distro integrates not just 
OpenStack, but all its dependencies and their dependencies all the way up. For 
example there can be subtle issues if neutron, open vswitch and the kernel are 
out of sync. It is the integration that folks like about distro's. "I can trust 
that since it came from X, all the pieces should work together, or I know who 
to call".

The only way I can think of to get the same stability out of just source is for 
Triple-O to provide a whole source distro and test it, itself. More work then 
it probably wants to do. Or pick just one distro and support source only on 
that. Though if you pick the wrong distro, then you get into trust issues and 
religious wars. :/

Kevin

________________________________________
From: Clint Byrum [[email protected]]
Sent: Tuesday, January 07, 2014 3:04 PM
To: openstack-dev
Subject: Re: [openstack-dev] [TripleO] Installing from packages in      
tripleo-image-elements

Excerpts from Chris Jones's message of 2014-01-07 14:43:31 -0800:
> Hi
>
> > On 7 Jan 2014, at 22:18, Clint Byrum <[email protected]> wrote:
> > Packages do the opposite,
> > and encourage entropy by promising to try and update software
>
> Building with packages doesn't require updating running systems with packages 
> and more than building with git requires updating running systems with git 
> pull.
> One can simply build (and test!) a new image with updated packages and 
> rebuild/takeover nodes.
>

Indeed, however one can _more_ simply build an image without package
tooling...  and they will be more similar across multiple platforms.

My question still stands, what are the real advantages? So far the only
one that matters to me is "makes it easier for people to think about
using it."

_______________________________________________
OpenStack-dev mailing list
[email protected]
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

_______________________________________________
OpenStack-dev mailing list
[email protected]
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Reply via email to