Thanks for the links and thoughtful comments James!
In the Heat documentation, is the subnet ID being treated as optional (or
is the documentation not correct)? I think it is a required argument in the
REST API. Ref:
Tried the below way, still able to access other AVzones also
nova aggregate-set-metadata aggregate_ID filter_tenant_id=tenant_ID
Thanks for all your replies, appreciate it.
On Wed, Aug 26, 2015 at 9:55 PM, gustavo panizzo gfa g...@zumbi.com.ar
wrote:
On Thu, Aug 27, 2015 at 11:26:42 +1000,
Just a gentle reminder since we bumped it a week for the mid-cycle. I'll be
hopping on from OpenStack Silicon Valley. If I am late joining, someone start
the meeting for me.
Thanks!
VW
Sent from my iPhone
___
OpenStack-operators mailing list
I am not going to be too picky either and play the role of the defender of
the REST principles.
While we can surely think about a solution that fits nicely in current APis
and also gives you the ability of querying all the subnets at once, I also
realise there as a practical matter thinking about
Hello Sam and David,
Thank your for the responses, I really appreciate them.
With clients the only issue I’ve had is with the designate client not being
backwards compatible between icehouse and juno. Ceilometer changed the way
they signed messaged between Icehouse and Juno which was a pain
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
I'd like to announce that we have stamped stable/kilo.
I'd like to congratulate everyone who has committed and helped the
OpenStack-Chef project get to this milestone.
We have made tremendous progress with the limited resources our project has.
