[openstack-dev] [ironic] PTL nomination
Hi friends, I'd like to be the ironic PTL for another cycle, if you'll have me. Newton, in my opinion, has been Ironic's best cycle yet. We got a ton of work done, and made good progress on the work we didn't finish. Some of the highlights from this cycle include: * Upgrade testing. We've struggled to make progress until this cycle, when we really went all-out on getting it done. We also have multinode CI working and awaiting reviews, which is a great thing to have anyway, and also a huge first step to testing rolling upgrades. * Multitenant networking. This has been our biggest feature request for years, and we've been hacking on it since Liberty. We finally got it done (though of course, there's more to add on top) in both Ironic and Nova this cycle. * Speaking of Nova, we've made huge progress there. We now support multiple nova-compute services running the Ironic driver. We have a nova-compatible console done in Ironic, with patches ready for Nova to land at the beginning of Ocata. We've laid the groundwork on both sides to make scheduling better, and remove the (host, node) tuple that we plagued Nova with for years. And I believe we've made large strides in how we interact with the Nova team; things seem much more friendlier, and people are willing to help each other out more on both sides. * Fine-grained keystone policy. This is a huge step in helping operators improve the security of their deployments. * Our server and client both properly support Keystone v3 now. * We now have third-party CI for iLO, iRMC, Cisco UCS/CIMC, OneView, PowerKVM, and DRAC. We're on a path to removing drivers without CI. For context, a year ago we had no third-party CI. :) * ironic-python-agent is now the only supported deploy ramdisk, and the APIs it uses have been promoted to first class APIs. * Ironic now emits software metrics and has a framework for emitting notifications for use by Searchlight and other systems. * Existing systems may now be 'adopted' by ironic to help folks migrate their existing environments to be managed by ironic. There's many more things we've done in the 3 releases we shipped this cycle, but this is a PTL nomination, not Newton release notes, so I'll stop there. Going forward into Ocata, there's a few major things I'd like to focus on: * Rolling upgrades. Most of the base IaaS has this or will have it soon. We're on a good path to getting it done, and I think it's super important for deployers. * Continue progress on the networking work. We need to finish portgroups and get a plan (and hopefully some code) together for vlan-aware baremetal instances. This will allow an arbitrary number of Neutron networks to be connected over an arbitrary number of physical NICs, which is incredibly useful to users. * Driver composition. This will get rid of our ever-increasing driver matrix and help users make more sense of all the driver options. It also helps clean up lots of internal code, so it's important to everyone. * Boot from volume. This didn't make as much progress as I liked in Newton, so we should keep working on it and try to at least get all the plumbing landed, if not the first implementation. Lots of folks are asking for this, and it's the best path we have to something that looks like 'nova migrate'. * Above all else, I plan to make it a priority to mentor a few folks that could be the next PTL. I didn't do a good job of this in Newton (though I think some people could do the job now). I think it's important to rotate the leadership, so I hope that the project is in a position where I can step down after Ocata, and write more code in Pike. Whether I'm elected PTL or not, I plan to be working upstream on ironic full-time during Ocata, and look forward to another successful cycle. :) // jim (official nomination at https://review.openstack.org/370709) __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Ironic] PTL nomination
no doubt, +1 On Tue, Sep 24, 2013 at 7:04 PM, Devananda van der Veen devananda@gmail.com wrote: Hi! I would like to nominate myself for the OpenStack Bare Metal Provisioning (Ironic) PTL position. I have been working with OpenStack for over 18 months, and was a scalability and performance consultant at Percona for four years prior. Since '99, I have worked as a developer, team lead, database admin, and linux systems architect for a variety of companies. I am the current PTL of the Bare Metal Provisioning (Ironic) program, which began incubation during Havana. In collaboration with many fine folks from HP, NTT Docomo, USC/ISI, and VirtualTech, I worked extensively on the Nova Baremetal driver during the Grizzly cycle. I also helped start the TripleO program, which relies heavily on the baremetal driver to achieve its goals. During the Folsom cycle, I led the effort to improve Nova's DB API layer and added devstack support for the OpenVZ driver. Through that work, I became a member of nova-core for a time, though my attention has shifted away from Nova more recently. Once I had seen nova-baremetal and TripleO running in our test environment and began to assess our longer-term goals (eg, HA, scalability, integration with other OpenStack services), I felt very strongly that bare metal provisioning was a separate problem domain from Nova and would be best served with a distinct API service and a different HA framework than what is provided by Nova. I circulated this idea during the last summit, and then proposed it to the TC shortly thereafter. During this development cycle, I feel that Ironic has made significant progress. Starting from the initial git bisect to retain the history of the baremetal driver, I added an initial service and RPC framework, implemented some architectural pieces, and left a lot of #TODO's. Today, with commits from 10 companies during Havana (*) and integration already underway with devstack, tempest, and diskimage-builder, I believe we will have a functional release within the Icehouse time frame. I feel that a large part of my role as PTL has been - and continues to be - to gather ideas from a wide array of individuals and companies interested in bare metal provisioning, then translate those ideas into a direction for the program that fits within the OpenStack ecosystem. Additionally, I am often guiding compromise between the long-term goals, such as firmware management, and the short-term needs of getting the project to a fully-functional state. To that end, here is a brief summary of my goals for the project in the Icehouse cycle. * API service and client library (likely finished before the summit) * Nova driver (blocked, depends on ironic client library) * Finish RPC bindings for power and deploy management * Finish merging bm-deploy-helper with Ironic's PXE driver * PXE boot integration with Neutron * Integrate with TripleO / TOCI for automated testing * Migration script for existing deployments to move off the nova-baremetal driver * Fault tolerance of the ironic-conductor nodes * Translation support * Docs, docs, docs! Beyond this, there are many long-term goals which I would very much like to facilitate, such as: * hardware discovery * better integration with SDN capable hardware * pre-provisioning tools, eg. management of bios, firmware, and raid config, hardware burn-in, etc. * post-provisioning tools, eg. secure-erase * boot from network volume * secure boot (protect deployment against MITM attacks) * validation of signed firmware (protect tenant against prior tenant) Overall, I feel honored to be working with so many talented individuals across the OpenStack community, and know that there is much more to learn as a developer, and as a program lead. (*) http://www.stackalytics.com/?release=havanametric=commitsproject_type=Allmodule=ironic http://russellbryant.net/openstack-stats/ironic-reviewers-30.txt http://russellbryant.net/openstack-stats/ironic-reviewers-180.txt -- Devananda ___ 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] [Ironic] PTL nomination
+1 Devananda is a great PLT. It is his vision that has and is driving Ironic's rapid development. Chris Krelle On Tue, Sep 24, 2013 at 11:04 AM, Devananda van der Veen devananda@gmail.com wrote: Hi! I would like to nominate myself for the OpenStack Bare Metal Provisioning (Ironic) PTL position. I have been working with OpenStack for over 18 months, and was a scalability and performance consultant at Percona for four years prior. Since '99, I have worked as a developer, team lead, database admin, and linux systems architect for a variety of companies. I am the current PTL of the Bare Metal Provisioning (Ironic) program, which began incubation during Havana. In collaboration with many fine folks from HP, NTT Docomo, USC/ISI, and VirtualTech, I worked extensively on the Nova Baremetal driver during the Grizzly cycle. I also helped start the TripleO program, which relies heavily on the baremetal driver to achieve its goals. During the Folsom cycle, I led the effort to improve Nova's DB API layer and added devstack support for the OpenVZ driver. Through that work, I became a member of nova-core for a time, though my attention has shifted away from Nova more recently. Once I had seen nova-baremetal and TripleO running in our test environment and began to assess our longer-term goals (eg, HA, scalability, integration with other OpenStack services), I felt very strongly that bare metal provisioning was a separate problem domain from Nova and would be best served with a distinct API service and a different HA framework than what is provided by Nova. I circulated this idea during the last summit, and then proposed it to the TC shortly thereafter. During this development cycle, I feel that Ironic has made significant progress. Starting from the initial git bisect to retain the history of the baremetal driver, I added an initial service and RPC framework, implemented some architectural pieces, and left a lot of #TODO's. Today, with commits from 10 companies during Havana (*) and integration already underway with devstack, tempest, and diskimage-builder, I believe we will have a functional release within the Icehouse time frame. I feel that a large part of my role as PTL has been - and continues to be - to gather ideas from a wide array of individuals and companies interested in bare metal provisioning, then translate those ideas into a direction for the program that fits within the OpenStack ecosystem. Additionally, I am often guiding compromise between the long-term goals, such as firmware management, and the short-term needs of getting the project to a fully-functional state. To that end, here is a brief summary of my goals for the project in the Icehouse cycle. * API service and client library (likely finished before the summit) * Nova driver (blocked, depends on ironic client library) * Finish RPC bindings for power and deploy management * Finish merging bm-deploy-helper with Ironic's PXE driver * PXE boot integration with Neutron * Integrate with TripleO / TOCI for automated testing * Migration script for existing deployments to move off the nova-baremetal driver * Fault tolerance of the ironic-conductor nodes * Translation support * Docs, docs, docs! Beyond this, there are many long-term goals which I would very much like to facilitate, such as: * hardware discovery * better integration with SDN capable hardware * pre-provisioning tools, eg. management of bios, firmware, and raid config, hardware burn-in, etc. * post-provisioning tools, eg. secure-erase * boot from network volume * secure boot (protect deployment against MITM attacks) * validation of signed firmware (protect tenant against prior tenant) Overall, I feel honored to be working with so many talented individuals across the OpenStack community, and know that there is much more to learn as a developer, and as a program lead. (*) http://www.stackalytics.com/?release=havanametric=commitsproject_type=Allmodule=ironic http://russellbryant.net/openstack-stats/ironic-reviewers-30.txt http://russellbryant.net/openstack-stats/ironic-reviewers-180.txt -- Devananda ___ 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] [Ironic] PTL nomination
+1 Devananda On Wed, Sep 25, 2013 at 10:44 PM, Chris K nobody...@gmail.com wrote: +1 Devananda is a great PLT. It is his vision that has and is driving Ironic's rapid development. Chris Krelle On Tue, Sep 24, 2013 at 11:04 AM, Devananda van der Veen devananda@gmail.com wrote: Hi! I would like to nominate myself for the OpenStack Bare Metal Provisioning (Ironic) PTL position. I have been working with OpenStack for over 18 months, and was a scalability and performance consultant at Percona for four years prior. Since '99, I have worked as a developer, team lead, database admin, and linux systems architect for a variety of companies. I am the current PTL of the Bare Metal Provisioning (Ironic) program, which began incubation during Havana. In collaboration with many fine folks from HP, NTT Docomo, USC/ISI, and VirtualTech, I worked extensively on the Nova Baremetal driver during the Grizzly cycle. I also helped start the TripleO program, which relies heavily on the baremetal driver to achieve its goals. During the Folsom cycle, I led the effort to improve Nova's DB API layer and added devstack support for the OpenVZ driver. Through that work, I became a member of nova-core for a time, though my attention has shifted away from Nova more recently. Once I had seen nova-baremetal and TripleO running in our test environment and began to assess our longer-term goals (eg, HA, scalability, integration with other OpenStack services), I felt very strongly that bare metal provisioning was a separate problem domain from Nova and would be best served with a distinct API service and a different HA framework than what is provided by Nova. I circulated this idea during the last summit, and then proposed it to the TC shortly thereafter. During this development cycle, I feel that Ironic has made significant progress. Starting from the initial git bisect to retain the history of the baremetal driver, I added an initial service and RPC framework, implemented some architectural pieces, and left a lot of #TODO's. Today, with commits from 10 companies during Havana (*) and integration already underway with devstack, tempest, and diskimage-builder, I believe we will have a functional release within the Icehouse time frame. I feel that a large part of my role as PTL has been - and continues to be - to gather ideas from a wide array of individuals and companies interested in bare metal provisioning, then translate those ideas into a direction for the program that fits within the OpenStack ecosystem. Additionally, I am often guiding compromise between the long-term goals, such as firmware management, and the short-term needs of getting the project to a fully-functional state. To that end, here is a brief summary of my goals for the project in the Icehouse cycle. * API service and client library (likely finished before the summit) * Nova driver (blocked, depends on ironic client library) * Finish RPC bindings for power and deploy management * Finish merging bm-deploy-helper with Ironic's PXE driver * PXE boot integration with Neutron * Integrate with TripleO / TOCI for automated testing * Migration script for existing deployments to move off the nova-baremetal driver * Fault tolerance of the ironic-conductor nodes * Translation support * Docs, docs, docs! Beyond this, there are many long-term goals which I would very much like to facilitate, such as: * hardware discovery * better integration with SDN capable hardware * pre-provisioning tools, eg. management of bios, firmware, and raid config, hardware burn-in, etc. * post-provisioning tools, eg. secure-erase * boot from network volume * secure boot (protect deployment against MITM attacks) * validation of signed firmware (protect tenant against prior tenant) Overall, I feel honored to be working with so many talented individuals across the OpenStack community, and know that there is much more to learn as a developer, and as a program lead. (*) http://www.stackalytics.com/?release=havanametric=commitsproject_type=Allmodule=ironic http://russellbryant.net/openstack-stats/ironic-reviewers-30.txt http://russellbryant.net/openstack-stats/ironic-reviewers-180.txt -- Devananda ___ 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 -- Wentian Jiang UnitedStack Inc. ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Ironic] PTL nomination
+1! Best Regards, - Sun Jing(孙靖, sjing) Wentian Jiang went...@unitedstack.com 2013/09/25 23:02 Please respond to OpenStack Development Mailing List openstack-dev@lists.openstack.org To OpenStack Development Mailing List openstack-dev@lists.openstack.org, cc Subject Re: [openstack-dev] [Ironic] PTL nomination +1 Devananda On Wed, Sep 25, 2013 at 10:44 PM, Chris K nobody...@gmail.com wrote: +1 Devananda is a great PLT. It is his vision that has and is driving Ironic's rapid development. Chris Krelle On Tue, Sep 24, 2013 at 11:04 AM, Devananda van der Veen devananda@gmail.com wrote: Hi! I would like to nominate myself for the OpenStack Bare Metal Provisioning (Ironic) PTL position. I have been working with OpenStack for over 18 months, and was a scalability and performance consultant at Percona for four years prior. Since '99, I have worked as a developer, team lead, database admin, and linux systems architect for a variety of companies. I am the current PTL of the Bare Metal Provisioning (Ironic) program, which began incubation during Havana. In collaboration with many fine folks from HP, NTT Docomo, USC/ISI, and VirtualTech, I worked extensively on the Nova Baremetal driver during the Grizzly cycle. I also helped start the TripleO program, which relies heavily on the baremetal driver to achieve its goals. During the Folsom cycle, I led the effort to improve Nova's DB API layer and added devstack support for the OpenVZ driver. Through that work, I became a member of nova-core for a time, though my attention has shifted away from Nova more recently. Once I had seen nova-baremetal and TripleO running in our test environment and began to assess our longer-term goals (eg, HA, scalability, integration with other OpenStack services), I felt very strongly that bare metal provisioning was a separate problem domain from Nova and would be best served with a distinct API service and a different HA framework than what is provided by Nova. I circulated this idea during the last summit, and then proposed it to the TC shortly thereafter. During this development cycle, I feel that Ironic has made significant progress. Starting from the initial git bisect to retain the history of the baremetal driver, I added an initial service and RPC framework, implemented some architectural pieces, and left a lot of #TODO's. Today, with commits from 10 companies during Havana (*) and integration already underway with devstack, tempest, and diskimage-builder, I believe we will have a functional release within the Icehouse time frame. I feel that a large part of my role as PTL has been - and continues to be - to gather ideas from a wide array of individuals and companies interested in bare metal provisioning, then translate those ideas into a direction for the program that fits within the OpenStack ecosystem. Additionally, I am often guiding compromise between the long-term goals, such as firmware management, and the short-term needs of getting the project to a fully-functional state. To that end, here is a brief summary of my goals for the project in the Icehouse cycle. * API service and client library (likely finished before the summit) * Nova driver (blocked, depends on ironic client library) * Finish RPC bindings for power and deploy management * Finish merging bm-deploy-helper with Ironic's PXE driver * PXE boot integration with Neutron * Integrate with TripleO / TOCI for automated testing * Migration script for existing deployments to move off the nova-baremetal driver * Fault tolerance of the ironic-conductor nodes * Translation support * Docs, docs, docs! Beyond this, there are many long-term goals which I would very much like to facilitate, such as: * hardware discovery * better integration with SDN capable hardware * pre-provisioning tools, eg. management of bios, firmware, and raid config, hardware burn-in, etc. * post-provisioning tools, eg. secure-erase * boot from network volume * secure boot (protect deployment against MITM attacks) * validation of signed firmware (protect tenant against prior tenant) Overall, I feel honored to be working with so many talented individuals across the OpenStack community, and know that there is much more to learn as a developer, and as a program lead. (*) http://www.stackalytics.com/?release=havanametric=commitsproject_type=Allmodule=ironic http://russellbryant.net/openstack-stats/ironic-reviewers-30.txt http://russellbryant.net/openstack-stats/ironic-reviewers-180.txt -- Devananda ___ 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] [Ironic] PTL nomination
Hi! I would like to nominate myself for the OpenStack Bare Metal Provisioning (Ironic) PTL position. I have been working with OpenStack for over 18 months, and was a scalability and performance consultant at Percona for four years prior. Since '99, I have worked as a developer, team lead, database admin, and linux systems architect for a variety of companies. I am the current PTL of the Bare Metal Provisioning (Ironic) program, which began incubation during Havana. In collaboration with many fine folks from HP, NTT Docomo, USC/ISI, and VirtualTech, I worked extensively on the Nova Baremetal driver during the Grizzly cycle. I also helped start the TripleO program, which relies heavily on the baremetal driver to achieve its goals. During the Folsom cycle, I led the effort to improve Nova's DB API layer and added devstack support for the OpenVZ driver. Through that work, I became a member of nova-core for a time, though my attention has shifted away from Nova more recently. Once I had seen nova-baremetal and TripleO running in our test environment and began to assess our longer-term goals (eg, HA, scalability, integration with other OpenStack services), I felt very strongly that bare metal provisioning was a separate problem domain from Nova and would be best served with a distinct API service and a different HA framework than what is provided by Nova. I circulated this idea during the last summit, and then proposed it to the TC shortly thereafter. During this development cycle, I feel that Ironic has made significant progress. Starting from the initial git bisect to retain the history of the baremetal driver, I added an initial service and RPC framework, implemented some architectural pieces, and left a lot of #TODO's. Today, with commits from 10 companies during Havana (*) and integration already underway with devstack, tempest, and diskimage-builder, I believe we will have a functional release within the Icehouse time frame. I feel that a large part of my role as PTL has been - and continues to be - to gather ideas from a wide array of individuals and companies interested in bare metal provisioning, then translate those ideas into a direction for the program that fits within the OpenStack ecosystem. Additionally, I am often guiding compromise between the long-term goals, such as firmware management, and the short-term needs of getting the project to a fully-functional state. To that end, here is a brief summary of my goals for the project in the Icehouse cycle. * API service and client library (likely finished before the summit) * Nova driver (blocked, depends on ironic client library) * Finish RPC bindings for power and deploy management * Finish merging bm-deploy-helper with Ironic's PXE driver * PXE boot integration with Neutron * Integrate with TripleO / TOCI for automated testing * Migration script for existing deployments to move off the nova-baremetal driver * Fault tolerance of the ironic-conductor nodes * Translation support * Docs, docs, docs! Beyond this, there are many long-term goals which I would very much like to facilitate, such as: * hardware discovery * better integration with SDN capable hardware * pre-provisioning tools, eg. management of bios, firmware, and raid config, hardware burn-in, etc. * post-provisioning tools, eg. secure-erase * boot from network volume * secure boot (protect deployment against MITM attacks) * validation of signed firmware (protect tenant against prior tenant) Overall, I feel honored to be working with so many talented individuals across the OpenStack community, and know that there is much more to learn as a developer, and as a program lead. (*) http://www.stackalytics.com/?release=havanametric=commitsproject_type=Allmodule=ironic http://russellbryant.net/openstack-stats/ironic-reviewers-30.txt http://russellbryant.net/openstack-stats/ironic-reviewers-180.txt -- Devananda ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
