11.10 beta2 due Thursday (9/22), status for upload to Ubuntu

[Kapil Thangavelu]

Excerpts from Clint Byrum's message of Tue Sep 20 17:25:38 -0700 2011:
> I'm beginning to prepare the final Freeze Exception request for
> Ensemble/Juju in Ubuntu 11.10. So far the only major feature that I see
> that has hit trunk since r336 is actually the rename to juju.


First off, thanks for shepherding juju (formerly ensemble) through the FFE 
process.

> 
> The openstack fixes are just that, fixes, so they don't even require
> feature freeze exceptions.
> 
> Local dev seems to have started to enter the trunk and looks to be
> largely in review at this point. The refactors readying the trunk for
> that can be seen as a feature, so it needs mentioning even if it doesn't
> get completely done.

The review queue currently stands at about 17 branches. There are several 
critical items in the list for the release, the orchestra work and 
ensemble-origin branch are required for the release imo.

There's about 10 branches in the queue relating to local-dev alone, getting 
reviews on them on all of them and incorporating feedback by the end of the 
22nd, is going to be a challenge and require some heroics, but feasible in 
an ideal world. Still challenging, but more realistic is the end of the week 
(9/23). All of the other review queue branches (minus the repository work) are 
standalone.

I think everyone on the juju teams needs to set aside at least half their day 
tomorrow so we can collectively work through the review queue.

> 
> All of the things depending on golang are in an entirely different branch,
> so I'm not sure what is ready or is not, or even how to incorporate
> that into the package. Will the juju repository work be available as a
> package at all?

I don't see the repository getting in as a package by the end of the 
week for oneiric, but gustavo can speak with more knowledge about that. The 
repository work would be a separate package. We can incorporate it into the 
ppa, and push it to universe for oneiric+1. There hasn't been any work on the 
client side integration of the repository so its pretty standalone atm afaics.

> 
> Anyway, I'd like to have a couple of days to test with the version
> we'd like to see in Ubuntu 11.10, including a few days where there's
> no changes landing in trunk so we can fix them and ship whats there. I
> was hoping that the features would all be landed by 9/22 so I can file
> the freeze exception and upload juju to the archive by 9/27. This would
> give us 2 days to find any critical bugs before final freeze, which is
> mostly symbolic for us, but also represents the time where really all
> eyes should be focused on testing the release and especially on bug
> triage to sniff out any last minute show stoppers.
> 

The testing freeze, with all hands on deck for testing and bugfixing sounds 
great. While juju has a great testing story, there's one known criticial issue 
in the pkg dependency tree for oneiric. Juju's functional testing story will be 
much better for the oneiric+1 cycle.

Neither the openstack nor orchestra work have available testing environments for 
the juju devs atm, we're relying on other server team members for feedback. 
The openstack deployment internal to canonical is running an older version with 
known bugs that crash nova. AdamG was able to confirm that it works with the 
latest openstack. I'm a bit unclear as to the server team testing story for 
orchestra + ensemble. My understanding is that there is a sprint next week 
(in earnest startng tuesday) that will exercise this use case, and there's a
possibility that will need additional bug fixes/compatibility work and 
corresponding bug-fix package upload.

Also regarding the openstack+juju out of the box story for oneiric, there's 
several bugs in openstack that have been recently fixed which are critical to have 
packaged in the oneiric openstack packages for juju integration.

 Bug #838419: nova-compute crashes when applying a security group rule
 Bug #845155: instance launched without key has incorrect metadata

Both have fixes committed against the next release. Chuck mentioned that new 
openstack packages were being uploaded today (9/20), afaik with those bug 
fixes.

> So, with that said, what I need is a "go now" signal from juju devs,
> so I don't upload too early, missing some nearly done feature, and so I
> don't wait too long, missing an opportunity for more testing. What would
> be even better is just to plan on a time and if that time is missed,
> so be it, that feature is missed.

Ideally we could freeze on friday, with upload wednesday, if we're 
willing to drop local dev, then thursday freeze with tuesday upload should be 
fine, else we'd could try dropping a day of feature freeze/testing/bugfix mode.

> 
> Thanks everybody!
> -C
> 
> p.s. It would be most excellent to sync up the upload to Ubuntu with the
> upload to macports, so that we can make sure the versions are the same.
> 

The macports integration was against ensemble from two months ago and is not 
incorporated into their main archives. https://trac.macports.org/ticket/30237
If its important to us, we should probably just do a binary installer (dmg/image 
style) ala plone (python cms) and offer it as a download.
https://svn.plone.org/svn/plone/Installers/macosx/trunk/

cheers,

Kapil