[Openstack-devel] Rest of the uploads for completing OpenStack Havana upload: current status

[Thomas Goirand]

Hi there,

(copying the FTP masters so they know why there's a sudden burst of
python packages upload from me)

Just, FYI, here's the list of my planned upload, so that I complete the
list of dependencies for OpenStack 2013.2, code name Havana:

- python-misaka
- python-pycadf
- python-pyghmi
- python-dogpile.cache
- python-pystache
- python-mox3
- python-jsonpath-rw

I've been working on these for a few days already. All of them are ready
on my laptop, and build correctly in my Jenkins in a clean (cowbuilder)
chroot. So I will proceed with the upload very soon. As much as I know,
this covers all the global-requirement.txt of Havana.

(ftp masters: you don't need to read past this)

This isn't much, and considering the current fast work of the FTP
masters, this should be smooth and wont wait for months. Let's hope this
can happen in time before the November summit.

Once this will be done, I will have the following new OpenStack core
packages:

- python-troveclient
- trove
- neutron

The rest of will be updates to the already existing packages which are
needing some updates:
- python-keyring
- python-jsonschema
- python-django-openstack-auth
- python-eventlet
- python-hacking
- python-fixtures
- python-hp3parclient
- python-swiftclient
- python-ceilometerclient
- python-subunit
- python-jsonpatch

Plus of course the usual core OpenStack packages:

- ceilometer
- cinder
- glance
- heat
- horizon
- keystone
- neutron
- nova
- swift

plus the corresponding python-*client packages. Neutron is of course
new, and will go through the new queue even though that's a rename from
Quantum. Note that I have already killed all the plugin packages (in
order to reduce the number of binary packages), and replaced that by a
more convenient thing: the core_plugin= directive in neutron.conf is
used in the init scripts to decide which .ini file to load, and this
directive is configured via debconf. This means that there's no need
anymore to manually apt-get install a given plugin, but just configure
the core_plugin directive, either via debconf, or editing the config
file. IMO this is much better, even though this doesn't support custom
plugins (by that, I mean not-currently-packaged pluggins), though if you
do create your own plugin, you probably can also edit the init scripts
to load your custom config file at run time.

My current plan is to upload Havana beta 3 into Experimental, and upload
it to Sid only once the 2013.2 is released as new stable.

Cheers,

Thomas Goirand (zigo)