Hi Adrian,
Then we have the odd thing where most of the client list commands return
lists of objects, while some (I'm looking at you glance), returns a
generator.
After short period of use, I completely agree with this and other your
statements re client libraries. Thanks for pointing on ways t
I don't disagree that the SDK lacks feature parity, which is oddly
enough one of the main reasons I'm actually using it, to find those
missing features, document them, maybe fix them, or if I can't fix them
annoy the right people who can. With the SDK there is at least always a
way to get around th
Hi Adrian,
at the moment, "wildly different" python clients provide more, than
Unified SDK. Not sure about all clients, but what I found and what
finally turned me to client libraries is inability to to do actions on
stack (e.g. suspend/resume) using Unified SDK (neither doc not source
code c
On 04/20/2018 01:48 AM, Adrian Turjak wrote:
What version of the SDK are you using?
Originally I just used what was installed in my devstack VM, which seems to be
0.9.17. Upgrading to 0.12.0 allowed it to work.
Thanks,
Chris
___
Mailing list: htt
What version of the SDK are you using?On 20 Apr. 2018 19:28, Chris Friesen wrote:On 04/19/2018 09:19 PM, Adrian Turjak wrote:
> On 20/04/18 01:46, Chris Friesen wrote:
>> On 04/19/2018 07:01 AM, Jeremy Stanley wrote:
>>> Or, for that matter, leverage OpenStackSDK's ability to pass
>>> arbitrary ca
On 04/19/2018 09:19 PM, Adrian Turjak wrote:
On 20/04/18 01:46, Chris Friesen wrote:
On 04/19/2018 07:01 AM, Jeremy Stanley wrote:
Or, for that matter, leverage OpenStackSDK's ability to pass
arbitrary calls to individual service APIs when you need something
not exposed by the porcelain layer
As someone who used to use all the standalone clients, I'm leaning very
heavily these days to using only the SDK and think we should encourage
most projects to treat the SDK as their first point of implementation
rather than all the wildly different python clients.
So if you are new to OpenStack,
On 04/19/2018 07:01 AM, Jeremy Stanley wrote:
On 2018-04-19 12:24:48 +1000 (+1000), Joshua Hesketh wrote:
There is also nothing stopping you from using both. For example,
you could use the OpenStack SDK for most things but if you hit an
edge case where you need something specific you can then im
On 2018-04-19 12:24:48 +1000 (+1000), Joshua Hesketh wrote:
> There is also nothing stopping you from using both. For example,
> you could use the OpenStack SDK for most things but if you hit an
> edge case where you need something specific you can then import
> the particular client lib.
[...]
Or
There is also nothing stopping you from using both. For example, you could
use the OpenStack SDK for most things but if you hit an edge case where you
need something specific you can then import the particular client lib.
Cheers,
Josh
On Thu, Apr 19, 2018 at 1:05 AM, Chris Friesen
wrote:
> I sh
I should preface this with the fact that I don't use OpenStack SDK, so you may
want to check with the project developers.
One example is that a bit over a year ago nova added a microversion to include
the flavor information directly in the server information rather than returning
a link to a f
Hi Chris and colleagues,
based on your experience, can you specify an average delay between new
OS release / new feature introduction and appearance of corresponding
support in Unified Openstack SDK if you were experiencing such issues?
Thanks.
On 4/17/18 7:23 PM, Chris Friesen wrote:
On 04
On 04/17/2018 07:13 AM, Jeremy Stanley wrote:
The various "client libraries" (e.g. python-novaclient,
python-cinderclient, et cetera) can also be used to that end, but
are mostly for service-to-service communication these days, aren't
extremely consistent with each other, and tend to eventually
On 2018-04-17 15:38:03 +0300 (+0300), Volodymyr Litovka wrote:
[...]
> 1) Openstack SDK (https://docs.openstack.org/openstacksdk/latest )
> 2) Openstack Clients (https://wiki.openstack.org/wiki/OpenStackClients )
>
> The question is which one to use in terms of support Openstack APIs,
> developmen
Hi colleagues,
I need to write client app (Python v3) to work with Openstack. At the
moment, I need to work with Keystone (of course), Heat, Nova and Cinder.
Support for other modules may be required later.
Keeping in mind direct API calls, I, nevertheless, prefer to use SDK and
there are tw
15 matches
Mail list logo