Hello Andreas,
I was wandering if you could help me with something. I seem to be having the
same issue you had with openstack when trying to launch an instance.
http://lists.openstack.org/pipermail/openstack/2014-July/008627.html
What was your conclusion to this problem or anything you can h
Against the Pike placement API endpoint, make sure you send the
following HTTP header:
OpenStack-API-Version: placement 1.10
Best,
-jay
On 10/03/2017 02:01 PM, Ramu, MohanX wrote:
Please refer attached original one.
-Original Message-
From: Jay Pipes [mailto:jaypi...@gmail.com]
Sent
On 10/03/2017 12:12 PM, Ramu, MohanX wrote:
Thanks for reply Jay.
No Jay,
I have installed Pike. There also I face the same problem.
No, you haven't installed Pike (or at least not properly). Otherwise,
the max_version returned from the Pike placement API would be 1.10, not 1.4.
Best,
-jay
Thanks for reply Jay.
No Jay,
I have installed Pike. There also I face the same problem.
Thanks & Regards,
Mohan Ramu
-Original Message-
From: Jay Pipes [mailto:jaypi...@gmail.com]
Sent: Tuesday, October 3, 2017 9:26 PM
To: openstack@lists.openstack.org
Subject: Re: [Openstack] Traits
On 10/03/2017 11:34 AM, Ramu, MohanX wrote:
Hi,
We have implemented OpenStack Ocata and Pike releases, able to consume
Placement resource providers API, not able to consume resource class APIs’.
I tried to run Triats API in Pike set up too. I am not able to run any
Traits API.
As per the O
Hi Jim,
It's possible to change the amount of space required for base system, but
it will require to change partitioning schema in release model.
You can retrieve it from Nailgun using:
curl -H "X-Auth-Token: $(fuel token)"
http://172.29.194.19:8000/api/v1/releases// | python -m
json.tool > rel.j
