Re: [openstack-dev] [Ironic] Nominating Lucas Gomes to ironic core
+1. Great work Lucas! On 25/10/13 09:16, Yuriy Zveryanskyy wrote: +1 for Lucas. On 10/25/2013 03:18 AM, Devananda van der Veen wrote: Hi all, I'd like to nominate Lucas Gomes for ironic-core. He's been consistently doing reviews for several months and has led a lot of the effort on the API and client libraries. Thanks for the great work! -Deva http://russellbryant.net/openstack-stats/ironic-reviewers-90.txt ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [TRIPLEO] tripleo-core update october
On 07/10/13 20:03, Robert Collins wrote: Hi, like most OpenStack projects we need to keep the core team up to date: folk who are not regularly reviewing will lose context over time, and new folk who have been reviewing regularly should be trusted with -core responsibilities. Please see Russell's excellent stats: http://russellbryant.net/openstack-stats/tripleo-reviewers-30.txt http://russellbryant.net/openstack-stats/tripleo-reviewers-90.txt For joining and retaining core I look at the 90 day statistics; folk who are particularly low in the 30 day stats get a heads up: it's not a purely mechanical process :). As we've just merged review teams with Tuskar devs, we need to allow some time for everyone to get up to speed; so for folk who are core as a result of the merge will be retained as core, but November I expect the stats will have normalised somewhat and that special handling won't be needed. IMO these are the reviewers doing enough over 90 days to meet the requirements for core: | lifeless **| 3498 140 2 19957.6% |2 ( 1.0%) | | clint-fewbar ** | 3292 54 1 27283.0% |7 ( 2.6%) | | cmsj ** | 2481 25 1 22189.5% | 13 ( 5.9%) | |derekh ** | 880 28 23 3768.2% |6 ( 10.0%) | Who are already core, so thats easy. If you are core, and not on that list, that may be because you're coming from tuskar, which doesn't have 90 days of history, or you need to get stuck into some more reviews :). Now, 30 day history - this is the heads up for folk: | clint-fewbar ** | 1792 27 0 15083.8% |6 ( 4.0%) | | cmsj ** | 1791 15 0 16391.1% | 11 ( 6.7%) | | lifeless **| 1293 39 2 8567.4% |2 ( 2.3%) | |derekh ** | 410 11 0 3073.2% |0 ( 0.0%) | | slagle | 370 11 26 070.3% |3 ( 11.5%) | |ghe.rivero| 280 4 24 085.7% |2 ( 8.3%) | I'm using the fairly simple metric of 'average at least one review a day' as a proxy for 'sees enough of the code and enough discussion of the code to be an effective reviewer'. James and Ghe, good stuff - you're well on your way to core. If you're not in that list, please treat this as a heads-up that you need to do more reviews to keep on top of what's going on, whether so you become core, or you keep it. In next month's update I'll review whether to remove some folk that aren't keeping on top of things, as it won't be a surprise :). Cheers, Rob Whilst I can see that deciding on who is Core is a difficult task, I do feel that creating a competitive environment based on no. reviews will be detrimental to the project. I do feel this is going to result in quantity over quality. Personally, I'd like to see every commit properly reviewed and tested before getting a vote and I don't think these stats are promoting that. Regards Martyn ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] Announcing Tuskar project and PTL nominations
Hi Sylvain, We are currently working on design docs. We'll be adding some architecture diagrams and description to our documentation soon. To answer your question re: provisioning and images. In our currently implementation (which is very early days), we took images that were built from by Triple O, namely the overcloud non-compute and compute images and we use these directly. in the demo environment you seen in the video, we used Triple O CI to set up the machine, register the relevant overcloud images with glance and so on. In Tuskar, we lifted from TripleO a copy of the triple-o overcloud heat template and made some modifications. We split out the non-compute and compute sections, this allows us to add multiple entries of each of the non-compute and compute sections (based on what is registered in Tuskar) we then add a section to enforce deployment of the particular images onto particular bare metal machines. (This allows us to match hardware to OpenStack services). We do this by using the force_hosts capability in the nova bare metal driver: https://blueprints.launchpad.net/nova/+spec/baremetal-force-node. We also add some extra commands to the Heat template to registers flavors and associates the flavors, host aggregates and baremetal nodes in the overcloud nova control instance. This allows us to tell the nova scheduler to match any instance requests with flavors that were registered with a resource class in Tuskar with particular hardware that has also been added to that resource class. As Tomas mentioned, our initial release is really just a Proof of Concept. We'll be working to add more complex features and probably rework much of our short cuts. Our aim though is to contribute as much as possible (or as much that makes sense) of Tuskar upstream into TripleO or any other component that we utilize and extend and have Tuskar really concentrate on how to utilize existing components to manage and deploy an OpenStack at large scale. Regards Martyn On 21/08/13 16:15, Sylvain Bauza wrote: Hi Tomas, Are there any design docs which could explain how you provision the baremetal hosts ? As far as I can see, it seeems you're relying on TripleO heat templates, right ? Are you then using disk-image-builder ? Thanks, -Sylvain PS : I just looked at the Youtube demo https://www.youtube.com/watch?v=VEY035-Lyzo Le 21/08/2013 14:32, Tomas Sedovic a écrit : Hi everyone, We would like to announce Tuskar, an OpenStack management service. Our goal is to provide an API and UI to install and manage OpenStack at larger scale: where you deal with racks, different hardware classes for different purposes (storage, memory vs. cpu-intensive compute), the burn-in process, monitoring the HW utilisation, etc. Some of this will overlap with TripleO, Ceilometer and possibly other projects. In that case, we will work with the projects to figure out the best place to fix rather than duplicating effort and playing in our own sandbox. Current status: There's a saying that if you're not embarrassed by your first release, you've shipped too late. I'm happy to say, we are quite embarrassed :-) We've got a prototype that allows us to define different hardware classes and provision the racks with the appropriate images, then add new racks and have them provisioned. We've got a Horizon dashboard plugin that shows the general direction we want to follow and we're looking into integrating Ceilometer metrics and alarms. However, we're still tossing around different ideas and things are very likely to change. Our repositories are on Stackforge: https://github.com/stackforge/tuskar https://github.com/stackforge/python-tuskarclient https://github.com/stackforge/tuskar-ui And we're using Launchpad to manage our bugs and blueprints: https://launchpad.net/tuskar https://launchpad.net/tuskar-ui If you want to talk to us, pop in the #tuskar IRC channel on Freenode or send an email to openstack-...@lists.launchpad.net with [Tuskar] in the subject. PTL: Talking to OpenStack developers, we were advised to elect the PTL early. Since we're nearing the end of the Havana cycle, we'll elect the PTL for a slightly longer term -- the rest of Havana and throughout Icehouse. The next election will coincide with those of the official OpenStack projects. If you are a Tuskar developer and want to nominate yourself, please send an email to openstack-...@lists.launchpad.net with subject Tuskar PTL candidacy. The self-nomination period will end on Monday, 26th August 2013, 23:59 UTC. -- Tomas Sedovic ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] Program description for Oslo
On 09/07/13 11:11, Mark McLoughlin wrote: Hey The mission statement is what we've been using for a while. The official title is new. Official Title: OpenStack Common Libraries PTL: Mark McLoughlin mar...@redhat.com Mission Statement: To produce a set of python libraries containing infrastructure code shared by OpenStack projects. The APIs provided by these libraries should be high quality, stable, consistent and generally applicable. I did consider explicitly mentioning technical debt with something like: Mission Statement: To tackle copy-and-paste technical debt in OpenStack by producing a set of python libraries containing infrastructure code shared by OpenStack projects. The APIs provided by these libraries should be high quality, stable, consistent and generally applicable. But for wholly new code, that sounds like you need to introduce copy-and-paste technical debt before it can be considered in scope for Oslo :) Cheers, Mark. Is it worth adding some emphasis on documentation in there somewhere? Specifically documentation for using the libraries and frameworks offered by Oslo in OpenStack. Maybe: Mission Statement: To produce a set of python libraries containing infrastructure code shared by OpenStack projects. The APIs provided by these libraries should be high quality, stable, consistent, well documented and generally applicable. Cheers Martyn ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
