We've got help from Google, Microsoft and ProfitBricks to develop their providers, which is great. The Microsoft guys were very kind and helped a lot bootstrapping the ARM provider. If can share the contact we have if you could be interested in getting in touch.
Thanks for the OpenStack env offering! Has it been manually provisioned, or it is a devstack / something that is fully automated? > > 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 > >
