Re: [openstack-dev] [nova] Austin summit priorities session recap
We understand. We¹re willing, ready, and able to assist with all of the upstream items that need to happen in order to get our submission in and more. We just need to know so we can help. Best, ‹Randy On 6/8/16, 6:09 PM, "Matt Riedemann" wrote: >That blueprint is high priority for a single vendor but low >priority when compared to the very large backlog of items that Nova has >for the release as a whole. > __ 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] [nova] Austin summit priorities session recap
I just want to point out that this appears to imply that open source storage backends for OpenStack would be prioritized over closed-source ones and I think that runs counter to the general inclusivity in the community. I assume it¹s just a turn of phrase, but I suspect it could be easily misinterpreted to mean that open source storage projects (external to OpenStack) could be prioritized over open source ones, creating a very uneven playing field, which would potentially be very bad from a perception point of view. Thanks, --Randy VP, Technology, EMC Corporation Top 10 OpenStack & Cloud Pioneer +1 (415) 787-2253 [google voice] TWITTER: twitter.com/randybias LINKEDIN: linkedin.com/in/randybias EXEC ADMIN: inna.k...@emc.com, +1 (415) 601-1168 On 5/10/16, 9:40 AM, "Matt Riedemann" wrote: >A closed-source vendor-specific ephemeral backend for a single virt >driver in Nova isn't a review priority for the release. __ 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] [OpenStack Foundation] Finding people to work on the EC2 API in Nova
As you know we have been driving forward on the stack forge project and it¹s our intention to continue to support it over time, plus reinvigorate the GCE APIs when that makes sense. So we¹re supportive of deprecating from Nova to focus on EC2 API in Nova. I also think it¹s good for these APIs to be able to iterate outside of the standard release cycle. --Randy VP, Technology, EMC Corporation Formerly Founder & CEO, Cloudscaling (now a part of EMC) +1 (415) 787-2253 [google voice] TWITTER: twitter.com/randybias LINKEDIN: linkedin.com/in/randybias ASSISTANT: ren...@emc.com On 1/29/15, 4:01 PM, "Michael Still" wrote: >Hi, > >as you might have read on openstack-dev, the Nova EC2 API >implementation is in a pretty sad state. I wont repeat all of those >details here -- you can read the thread on openstack-dev for detail. > >However, we got here because no one is maintaining the code in Nova >for the EC2 API. This is despite repeated calls over the last 18 >months (at least). > >So, does the Foundation have a role here? The Nova team has failed to >find someone to help us resolve these issues. Can the board perhaps >find resources as the representatives of some of the largest >contributors to OpenStack? Could the Foundation employ someone to help >us our here? > >I suspect the correct plan is to work on getting the stackforge >replacement finished, and ensuring that it is feature compatible with >the Nova implementation. However, I don't want to preempt the design >process -- there might be other ways forward here. > >I feel that a continued discussion which just repeats the last 18 >months wont actually fix the situation -- its time to "break out" of >that mode and find other ways to try and get someone working on this >problem. > >Thoughts welcome. > >Michael > >-- >Rackspace Australia > >___ >Foundation mailing list >foundat...@lists.openstack.org >http://lists.openstack.org/cgi-bin/mailman/listinfo/foundation __ 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
