Re: [openstack-dev] [tc][ec2-api] EC2 API Future
> On Mar 21, 2016, at 2:33 PM, Tim Bell wrote: > > >> On 21/03/16 17:23, "Doug Hellmann" wrote: >> >> >> >>> On Mar 20, 2016, at 3:26 PM, Tim Bell wrote: >>> >>> >>> Doug, >>> >>> Given that the EC2 functionality is currently in use by at least 1/6th of >>> production clouds >>> (https://www.openstack.org/assets/survey/Public-User-Survey-Report.pdf page >>> 34), this is a worrying situation. >> >> I completely agree. >> >>> >>> The EC2 functionality was recently deprecated from Nova on the grounds that >>> the EC2 API project was the correct way to proceed. With the proposal now >>> to not have an EC2 API project at all, this will leave many in the >>> community confused. >> >> That wasn't the proposal. We have lots of unofficial projects. My suggestion >> was that if the EC2 team wasn't participating in the community governance >> process, we should not list them as official. That doesn't mean disbanding >> the project, just updating our reference materials to reflect reality and >> clearly communicat expectations. It sounds like that was a misunderstanding >> which has been cleared up, though, so I think we're all set to continue >> considering it an official project. > > There is actually quite a lot of activity going on to get the EC2 API to an > easy state to deploy. CERN has been involved in the puppet-ec2api and RDO > packaging which currently does not count as participation in the EC2 API > project given the split of repositories. However, it is critical for > deployment of a project that it can be installed and configured. That's a great point, and in the future I'll look at packaging and other related repos when trying to gauge activity. Doug > > Tim > >> >> Doug >> >>> >>> Tim >>> >>> >>> >>> On 20/03/16 17:48, "Doug Hellmann" wrote: ... The EC2-API project doesn't appear to be very actively worked on. There is one very recent commit from an Oslo team member, another couple from a few days before, and then the next one is almost a month old. Given the lack of activity, if no team member has volunteered to be PTL I think we should remove the project from the official list for lack of interest. >>> __ >>> 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 >> >> __ >> 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 > __ > 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 __ 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] [tc][ec2-api] EC2 API Future
On 21/03/16 17:23, "Doug Hellmann" wrote: > > >> On Mar 20, 2016, at 3:26 PM, Tim Bell wrote: >> >> >> Doug, >> >> Given that the EC2 functionality is currently in use by at least 1/6th of >> production clouds >> (https://www.openstack.org/assets/survey/Public-User-Survey-Report.pdf page >> 34), this is a worrying situation. > >I completely agree. > >> >> The EC2 functionality was recently deprecated from Nova on the grounds that >> the EC2 API project was the correct way to proceed. With the proposal now to >> not have an EC2 API project at all, this will leave many in the community >> confused. > >That wasn't the proposal. We have lots of unofficial projects. My suggestion >was that if the EC2 team wasn't participating in the community governance >process, we should not list them as official. That doesn't mean disbanding the >project, just updating our reference materials to reflect reality and clearly >communicat expectations. It sounds like that was a misunderstanding which has >been cleared up, though, so I think we're all set to continue considering it >an official project. There is actually quite a lot of activity going on to get the EC2 API to an easy state to deploy. CERN has been involved in the puppet-ec2api and RDO packaging which currently does not count as participation in the EC2 API project given the split of repositories. However, it is critical for deployment of a project that it can be installed and configured. Tim > >Doug > >> >> Tim >> >> >> >> >>> On 20/03/16 17:48, "Doug Hellmann" wrote: >>> >>> ... >>> >>> The EC2-API project doesn't appear to be very actively worked on. >>> There is one very recent commit from an Oslo team member, another >>> couple from a few days before, and then the next one is almost a >>> month old. Given the lack of activity, if no team member has >>> volunteered to be PTL I think we should remove the project from the >>> official list for lack of interest. >> __ >> 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 > >__ >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 __ 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] [tc][ec2-api] EC2 API Future
> On Mar 20, 2016, at 3:26 PM, Tim Bell wrote: > > > Doug, > > Given that the EC2 functionality is currently in use by at least 1/6th of > production clouds > (https://www.openstack.org/assets/survey/Public-User-Survey-Report.pdf page > 34), this is a worrying situation. I completely agree. > > The EC2 functionality was recently deprecated from Nova on the grounds that > the EC2 API project was the correct way to proceed. With the proposal now to > not have an EC2 API project at all, this will leave many in the community > confused. That wasn't the proposal. We have lots of unofficial projects. My suggestion was that if the EC2 team wasn't participating in the community governance process, we should not list them as official. That doesn't mean disbanding the project, just updating our reference materials to reflect reality and clearly communicat expectations. It sounds like that was a misunderstanding which has been cleared up, though, so I think we're all set to continue considering it an official project. Doug > > Tim > > > > >> On 20/03/16 17:48, "Doug Hellmann" wrote: >> >> ... >> >> The EC2-API project doesn't appear to be very actively worked on. >> There is one very recent commit from an Oslo team member, another >> couple from a few days before, and then the next one is almost a >> month old. Given the lack of activity, if no team member has >> volunteered to be PTL I think we should remove the project from the >> official list for lack of interest. > __ > 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 __ 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] [tc][ec2-api] EC2 API Future
Thank you Randy, you've summed up what I explained in the other thread. Yes I promise to keep up a good work as EC2 PTL in the next cycle if I'm appointed. Best regards, Alex Levine On 3/21/16 2:07 AM, Bias, Randy wrote: Hello, First of all, let me apologize for answering on Alex Levine's behalf, but it's late night/early morning in Moscow, so I'm taking the liberty. Second, Alex Levine was recently made PTL of the EC2-API project when it was formally accepted as an official project, but failed to understand that he would need to nominate himself again during the election process, since there was such a short gap. Third, as Tim points out, there is still significant usage of the EC2 APIs in OpenStack. In fact, usage has been increasing. We have also begun to see greater participation in the development process. Finally, it is true that my team has not been as active on the APIs recently; however, there is a very good reason for that. We are small and recently focused on working with the RefStack team on adding new capabilities to RefStack and new tests to Tempest to create a way to test for EC2 API interoperability and compatibility. While this isn't work on the EC2 APIs themselves, it is adjacent and important for their uptake, usage, and evaluation, particularly by teams who want to integrate them into their products. My team is small, 5 people, but we're focused exclusively on OpenStack at EMC, and the EC2 APIs will continue to be a top 3 priority for us for the foreseeable future. Ideally what we would do is put Alex in as PTL for the EC2 APIs and give us some more time to make progress. From our perspective, things in this area have actually been going swimmingly lately. Best, --Randy From: Tim Bell [tim.b...@cern.ch] Sent: Sunday, March 20, 2016 12:26 PM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [tc][ec2-api] EC2 API Future Doug, Given that the EC2 functionality is currently in use by at least 1/6th of production clouds (https://www.openstack.org/assets/survey/Public-User-Survey-Report.pdf page 34), this is a worrying situation. The EC2 functionality was recently deprecated from Nova on the grounds that the EC2 API project was the correct way to proceed. With the proposal now to not have an EC2 API project at all, this will leave many in the community confused. Tim On 20/03/16 17:48, "Doug Hellmann" wrote: ... The EC2-API project doesn't appear to be very actively worked on. There is one very recent commit from an Oslo team member, another couple from a few days before, and then the next one is almost a month old. Given the lack of activity, if no team member has volunteered to be PTL I think we should remove the project from the official list for lack of interest. __ 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 __ 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 __ 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] [tc][ec2-api] EC2 API Future
Hello, First of all, let me apologize for answering on Alex Levine's behalf, but it's late night/early morning in Moscow, so I'm taking the liberty. Second, Alex Levine was recently made PTL of the EC2-API project when it was formally accepted as an official project, but failed to understand that he would need to nominate himself again during the election process, since there was such a short gap. Third, as Tim points out, there is still significant usage of the EC2 APIs in OpenStack. In fact, usage has been increasing. We have also begun to see greater participation in the development process. Finally, it is true that my team has not been as active on the APIs recently; however, there is a very good reason for that. We are small and recently focused on working with the RefStack team on adding new capabilities to RefStack and new tests to Tempest to create a way to test for EC2 API interoperability and compatibility. While this isn't work on the EC2 APIs themselves, it is adjacent and important for their uptake, usage, and evaluation, particularly by teams who want to integrate them into their products. My team is small, 5 people, but we're focused exclusively on OpenStack at EMC, and the EC2 APIs will continue to be a top 3 priority for us for the foreseeable future. Ideally what we would do is put Alex in as PTL for the EC2 APIs and give us some more time to make progress. From our perspective, things in this area have actually been going swimmingly lately. Best, --Randy From: Tim Bell [tim.b...@cern.ch] Sent: Sunday, March 20, 2016 12:26 PM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [tc][ec2-api] EC2 API Future Doug, Given that the EC2 functionality is currently in use by at least 1/6th of production clouds (https://www.openstack.org/assets/survey/Public-User-Survey-Report.pdf page 34), this is a worrying situation. The EC2 functionality was recently deprecated from Nova on the grounds that the EC2 API project was the correct way to proceed. With the proposal now to not have an EC2 API project at all, this will leave many in the community confused. Tim On 20/03/16 17:48, "Doug Hellmann" wrote: >... > >The EC2-API project doesn't appear to be very actively worked on. >There is one very recent commit from an Oslo team member, another >couple from a few days before, and then the next one is almost a >month old. Given the lack of activity, if no team member has >volunteered to be PTL I think we should remove the project from the >official list for lack of interest. > __ 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 __ 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] [tc][ec2-api] EC2 API Future
Doug, Given that the EC2 functionality is currently in use by at least 1/6th of production clouds (https://www.openstack.org/assets/survey/Public-User-Survey-Report.pdf page 34), this is a worrying situation. The EC2 functionality was recently deprecated from Nova on the grounds that the EC2 API project was the correct way to proceed. With the proposal now to not have an EC2 API project at all, this will leave many in the community confused. Tim On 20/03/16 17:48, "Doug Hellmann" wrote: >... > >The EC2-API project doesn't appear to be very actively worked on. >There is one very recent commit from an Oslo team member, another >couple from a few days before, and then the next one is almost a >month old. Given the lack of activity, if no team member has >volunteered to be PTL I think we should remove the project from the >official list for lack of interest. > __ 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
