Open Stack

I've heard this a couple times recently and it's a fine idea. That being said I'm not aware of anyone currently working on this. This would be a great thing to add for Essex and a great topic in general for the upcoming Design Summit in October.

Is this something you want to work on? Either way it would be a good idea to add a blueprint w/ wiki page describing what you'd like to get out of the documentation. Then we can discuss and prioritize for the next release.

-----Original Message-----
From: "Joshua Harlow" <harlowja at yahoo-inc.com>
Sent: Wednesday, August 31, 2011 7:09pm
To: "Vishvananda Ishaya" <vishvananda at gmail.com>, "openstack" <openstack at lists.launchpad.net>
Subject: Re: [Openstack] Diablo RBP

_______________________________________________
Mailing list: https://launchpad.net/~openstack
Post to     : openstack at lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp
This email may include confidential information. If you received it in error, please delete it.
Is there any plan to document the internal-rpc format that will be used (with kombu, carrot...)

It would seem very important to have that and I haven't seen any documentation for it (maybe per release?)

On 8/31/11 11:17 AM, "Vishvananda Ishaya" <vishvananda at gmail.com> wrote:

Hey Everyone,

We managed to get a lot of features in for Diablo-4, and a few have gone in afterwards.  There are still a few that I would like to see land:

https://code.launchpad.net/~cbehrens/nova/rpc-kombu/+merge/73096
(fixes a number of bugs with rpc, leaves the carrot code in place so we can revert to carrot as default if issues arise)

https://code.launchpad.net/~cloudbuilders/nova/os-keypair-integration/+merge/72140
https://code.launchpad.net/~cloudbuilders/nova/os-user_id-description/+merge/72233
(These are extensions that aren't touching much and are key for feature parity in dashboard)

https://code.launchpad.net/~danwent/nova/qmanager-new/+merge/72526
(This is the quantum manager and allows integration with quantum.  It leaves the old managers in place so shouldn't break any existing functionality)

There are also lots of bugfix and cleanup proposals that need to be reviewed and merged as well.

Aside from the above branches, we should have no other feature branches go in. So it is time to focus on testing and filing and fixing bugs. I'm Triaging and targeting bugs to the rbp.  You can find the list here:

https://launchpad.net/nova/+milestone/diablo-rbp
(More will be added as we find them)

There are two critical ones so far:

https://bugs.launchpad.net/nova/+bug/833552
(Rackspace-ozone is tackling this one)

https://bugs.launchpad.net/nova/+bug/834189
(I'm sending out an email discussing this one)

There are a number of bugs that haven't been triaged or targeted yet.  Here is a mostly complete list:

https://bugs.launchpad.net/nova/+bugs?field.searchtext=&orderby=-importance&search=Search&field.status%3Alist=NEW&field.status%3Alist=CONFIRMED&field.status%3Alist=TRIAGED&assignee_option=any&field.assignee=&field.bug_reporter=&field.bug_supervisor=&field.bug_commenter=&field.subscriber=&field.tag=&field.tags_combinator=ANY&field.has_cve.used=&field.omit_dupes.used=&field.omit_dupes=on&field.affects_me.used=&field.has_patch.used=&field.has_branches.used=&field.has_branches=on&field.has_no_branches.used=&field.has_no_branches=on&field.has_blueprints.used=&field.has_blueprints=on&field.has_no_blueprints.used=&field.has_no_blueprints=on <https://bugs.launchpad.net/nova/+bugs?field.searchtext=&orderby=-importance&search=Search&field.status:list=NEW&field.status:list=CONFIRMED&field.status:list=TRIAGED&assignee_option=any&field.assignee=&field.bug_reporter=&field.bug_supervisor=&field.bug_commenter=&field.subscriber=&field.tag=&field.tags_combinator=ANY&field.has_cve.used=&field.omit_dupes.used=&field.omit_dupes=on&field.affects_me.used=&field.has_patch.used=&field.has_branches.used=&field.has_branches=on&field.has_no_branches.used=&field.has_no_branches=on&field.has_blueprints.used=&field.has_blueprints=on&field.has_no_blueprints.used=&field.has_no_blueprints=on>

Please feel free to assign yourself to a bug and get cracking on it.  We don't have a lot of time left, so lets stabilize the best we can.

Vish