Re: [Openstack] GitHub migration timeline?
https://github.com/openstack/keystone is now the main repo for Keystone (rackspace/keystone is now a fork). All changes should go through the new workflow documented here: http://wiki.openstack.org/GerritWorkflow Thanks to the OpenStack CI team for their support. On 7/18/11 4:20 PM, "Monty Taylor" wrote: >On 07/18/2011 02:59 PM, Andy Smith wrote: >> Jay and Monty, could you give the list an update on the status and >> timeline of the GitHub migration? > >Things are going quite swimingly. Proof of concept went well and we've >been working on starting to roll some things out. > >We've moved the CI repos (github.com/openstack/openstack-ci and >github.com/openstack/openstack-ci-puppet) to be managed via >Jenkins/Gerrit (so that we're eating our own dogfood) as we're currently >working with the Keystone team to move their stuff in (since they're >already on github, and since they are not already using tooling, they're >an easier subset of the migration) We're going to let those bake for a >few days so that we can make sure there aren't major trainwrecks either >in the system itself or in the documentation before starting to move the >larger projects. > >Next we'll move a project that is currently on launchpad using tarmac - >I'm voting for either Glance or Burrow. Specifically the need here is >sorting out tarballs/packaging on a lower-traffic project. > >Once THAT is done, we should be in good enough shape to move the larger >projects like Nova. > >> The last informal estimate I had heard was that July 15th was the >> planned date. What are the current issues? > >That's not too far off, actually. We sent out the intro instructions to >the keystone team on the 15th - so you can consider things in motion. > >We've got blueprints up on our current items in work at: > >https://blueprints.launchpad.net/openstack-ci > >The blueprint's in question here are: > >https://blueprints.launchpad.net/openstack-ci/+spec/ci-git-support > >and > >https://blueprints.launchpad.net/openstack-ci/+spec/ci-git-transition > >There are several things we will continue to hack on in terms of >enhancements, but there is no need for those to block the continued >rollout of things. On the other hand, we know of a couple that will >involve small workflow changes, and we're trying to get _those_ done >before we migrate everybody. > >I'd say the largest issue I want to see done before we get to Nova is >listening for +2 events in the event stream from Jenkins. (which should >not be hard to do) I'd love to get a few things sorted around auth/users >and groups - but I'm gonna guess that we won't see that before the final >transition. > >SO - all of that to say - things have begun migrating, and it will be a >little while longer before we get to nova. > >___ >Mailing list: https://launchpad.net/~openstack >Post to : openstack@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. ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] OpenStack Common
Here's the start of a skeleton project: https://github.com/openstack/openstack-skeleton Fork away. We can use the pull requests for discussion about what's best practice, what isn't, etc... -jay On Tue, Jul 26, 2011 at 8:26 AM, Thierry Carrez wrote: > Brian Lamar wrote: >> I love the idea of having an openstack-common project. However, the prospect >> of creating such a project is daunting and quite difficult. >> [...] > > Thanks for bringing up the subject ! I think there are two types of > benefits from this: > > The first is, like you said, to lower the barrier of entry for new > projects. Having a set of proven ways of doing logging, configuration > etc. would definitely help in spawning a new project "the OpenStack way". > > The second is to better establish "OpenStack" as an integrated product > made of cooperating components. If people that want to deploy multiple > OpenStack components end up having to learn 4 different config file > formats and teach their tools to recognize 3 different log formats, it > appears like the whole "OpenStack" thing is non-professional. > > Choosing the "best practice" way among the different projects > implementations and making it the "common" way would allow to quickly > reap the first type of benefits. The cost of separating it is not so large. > > Then we can encourage existing projects using different implementations > to migrate to the "common" way, in order to reap the second type as > well. There would certainly be delays and exceptions to the common rule, > since this part would probably be a bit more painful: the cost of > replacing a current (working) system is a lot larger. > > Cheers, > > -- > Thierry Carrez (ttx) > Release Manager, OpenStack > > ___ > Mailing list: https://launchpad.net/~openstack > Post to : openstack@lists.launchpad.net > Unsubscribe : https://launchpad.net/~openstack > More help : https://help.launchpad.net/ListHelp > ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
[Openstack] Reminder: OpenStack team meeting - 21:00 UTC
Hello everyone, Our weekly team meeting will take place at 21:00 UTC this Tuesday in #openstack-meeting on IRC. PTLs, if you can't make it, please name a substitute on [2]. This is the last meeting before we release Swift 1.4.2 and Glance/Nova diablo-3 milestones, so we'll discuss targeted issues that we need to solve before the release Thursday. Check out how that time translates for *your* timezone: [1] http://www.timeanddate.com/worldclock/fixedtime.html?iso=20110719T26 See the meeting agenda, edit the wiki to add new topics for discussion: [2] http://wiki.openstack.org/Meetings/TeamMeeting Cheers, -- Thierry Carrez (ttx) Release Manager, OpenStack ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] OpenStack Common
Brian Lamar wrote: > I love the idea of having an openstack-common project. However, the prospect > of creating such a project is daunting and quite difficult. > [...] Thanks for bringing up the subject ! I think there are two types of benefits from this: The first is, like you said, to lower the barrier of entry for new projects. Having a set of proven ways of doing logging, configuration etc. would definitely help in spawning a new project "the OpenStack way". The second is to better establish "OpenStack" as an integrated product made of cooperating components. If people that want to deploy multiple OpenStack components end up having to learn 4 different config file formats and teach their tools to recognize 3 different log formats, it appears like the whole "OpenStack" thing is non-professional. Choosing the "best practice" way among the different projects implementations and making it the "common" way would allow to quickly reap the first type of benefits. The cost of separating it is not so large. Then we can encourage existing projects using different implementations to migrate to the "common" way, in order to reap the second type as well. There would certainly be delays and exceptions to the common rule, since this part would probably be a bit more painful: the cost of replacing a current (working) system is a lot larger. Cheers, -- Thierry Carrez (ttx) Release Manager, OpenStack ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
[Openstack] diablo-3 / 1.4.2 milestone proposed candidates
Hi everyone, The milestone-proposed branches were updated to include Nova diablo-3, Glance diablo-3 and Swift 1.4.2 development. Now we need to test those to ensure no critical regression found its way in despite our stellar continuous integration efforts :) You can test the candidates on Ubuntu by enabling: ppa:nova-core/milestone-proposed ppa:glance-core/milestone-proposed (soon) ppa:swift-core/milestone-proposed Alternatively, you can directly check out the branches at: lp:~hudson-openstack/nova/milestone-proposed lp:~hudson-openstack/glance/milestone-proposed lp:~hudson-openstack/swift/milestone-proposed Let us know of any issue. The ones we try to fix before milestone release will be listed at the milestone pages: https://launchpad.net/nova/+milestone/diablo-3 https://launchpad.net/glance/+milestone/diablo-3 https://launchpad.net/swift/+milestone/1.4.2 Note that we already have bugfixes under way for identified issues in Glance and Nova. The plan is to release Thursday morning, US time. Cheers, -- Thierry Carrez (ttx) Release Manager, OpenStack ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
