[Openstack-devel] nova_2013.1-1_amd64.changes REJECTED
Hernando Rivero, Juan Gregorio (HPCS)
ghe.rivero at hp.com
Mon Apr 15 11:59:53 UTC 2013
having a lot of tiny packages for OpenStack is a must do. This
facilities all the scalability issues needed in complex deplouments, soI
have to agree with Thomas and the Debian OpenStack Team.
On 04/15/2013 10:29 AM, Ola Lundqvist wrote:
> I agree with Medhi and Thomas about this. I do not want to
> repeat the reasons as Thomas have already expressed them clearly. :-)
> Separate packages have clearly advantages in this case.
> // Ola
> On Sat, Apr 13, 2013 at 11:54:19AM +0200, Mehdi Abaakouk wrote:
>>> On 04/11/2013 06:04 AM, Joerg Jaspert wrote:
>>> Adding lots of tiny packages where the metadata has
>>> more size than the actual use data of the package is bad enough that it
>>> warrants a reject. Independent of our knowledge of the package -
>>> thats why you can just explain stuff if its really needed.
>> I use this packaging for many different kind of architecture.
>> I also think having the current binary packages for Nova is needed.
>> I don't want to deal with enabled/disabled rc scripts or
>> complicated /etc/default/nova to set which part of nova I want to run on
>> a cluster node. Installing one package to enable one service match the
>> distributed architecture nature of Openstack and made the Openstack
>> installation easier.
>> Mehdi Abaakouk
>> mail: sileht at sileht.net
>> irc: sileht
>> Openstack-devel mailing list
>> Openstack-devel at lists.alioth.debian.org
More information about the Openstack-devel