I have a OpenStack deployment running in GCP, Keystone 3 and nova 12 (2.1 API)
If anyone wants to use it for dev and test please email me. I'm going to blow it away in a week so it's just a sandbox. Also, can I point you to our tests which have test fixtures for 90% of our supported clouds, recorded from production deployments. It may come in useful if you're struggling to find real APIs or accounts. Anthony Shaw ________________________________ From: anthony shaw <anthony.p.s...@gmail.com> Sent: Wednesday, May 3, 2017 6:13:57 PM To: dev@jclouds.apache.org Subject: Re: [DISCUSS] OpenStack support from over the fence Interesting and encouraging to see that we're aligned closely. Azure ARM support was a big feature for us in the recent 2.0 release, continuing to support that is a priority. We're also seeing continued support from the community for Google Cloud and of course AWS. We need to add Keystone 3 support, although it hasn't been requested directly from users it is a gap and if we don't fix it now it will continue to widen. Alibaba Cloud, or Aliyun is also becoming quite popular and we have seen lots of contributions as well as I reached out directly to their developers to ask for support. With regards to time and community development support; I'm trying to involve the cloud providers as much as possible since many of them have dedicated open source teams. Google have been actively contributing and even adding API features ahead of their release, which is spectacular for us. Azure and AWS continue to be supported solely by the community. https://libcloud.apache.org/blog/2017/04/25/libcloud-2-0-0-released.html Anthony Shaw _____________________________ From: Ignasi Barrera <n...@apache.org<mailto:n...@apache.org>> Sent: Wednesday, May 3, 2017 5:37 pm Subject: Re: [DISCUSS] OpenStack support from over the fence To: <dev@jclouds.apache.org<mailto:dev@jclouds.apache.org>> Hi Anthony! We currently support Nova 2.0 and Keystone 2.0. We are tracking and looking forward to implement the Keystone v3 API [1], since version 2 has been removed in the last releases of OpenStack and supporting it is becoming a blocker. I have some design ideas in mind to keep compatibility with the current version and I expect to find some cycles to dedicate to this in short, but the main issue we are facing is the lack of resources with the required amount of time to implement the integration with v3 (as noted in the last published board minutes [2]). Another reason for the lack of time is that in the last months we have seen more interest in other providers such as Azure ARM and we've focused our energy there. The two main challenges we are facing with OpenStack are: * Supporting keystone V3 and newer nova versions. * Integrate the Nova API and the ComputeService with Neutron. We have Neutron as a separate API, and we need to make them work together, otherwise the networking experience when using the Nova compute service is quite poor. So yes, we are tracking and trying to keep up to date with OpenStack and will eventually be able to upgrade our providers, but the lack of resources and volunteer hands to implement it is making us move forward slower than we'd like. Cheers, I. [1] https://issues.apache.org/jira/browse/JCLOUDS-114 [2] https://www.apache.org/foundation/records/minutes/2017/board_minutes_2017_01_18.txt On 3 May 2017 at 09:17, anthony shaw <anthonys...@apache.org<mailto:anthonys...@apache.org>> wrote: > Hi, > > It's Anthony from the Apache Libcloud project, I'm looking at our OpenStack > support (in particular Nova), which is really out of date. > > We support 2.0, they are on version 13 > https://docs.openstack.org/releasenotes/nova/mitaka.html# > > I don't understand whether 13 means Keystone 3 and Nova 2.2, it's > challenging to see from the documentation. > > What's the status on jClouds? Are you continuing to support and evolve > OpenStack support? > > Regards > Anthony Shaw, aka @tonybaloney
