Should this code cleanup be done separate from the update volume-Image-metadata
update bp or should be a work item of it?
-Original Message-
From: Duncan Thomas [mailto:duncan.tho...@gmail.com]
Sent: Thursday, June 26, 2014 7:29 PM
To: OpenStack Development Mailing List (not for usage
looks pretty light for Thursday if you want to
add this topic:
https://etherpad.openstack.org/p/glance-team-meeting-agenda
cheers,
brian
From: Maldonado, Facundo N [facundo.n.maldon...@intel.com]
Sent: Tuesday, June 24, 2014 2:34 PM
To: OpenStack Development
Hi folks,
I started working on this blueprint [1] but the work to be done
is not limited to cinder python client.
Volume-image-metadata is immutable in Cinder and Glance has
RBAC image properties and it doesn't provide any way to find out which are
those
Hi folks,
I submitted a new blueprint proposing the addition of a new operator to the
existing ones.
BP:
https://blueprints.launchpad.net/nova/+spec/add-all-in-list-operator-to-extra-spec-ops
Spec review: https://review.openstack.org/#/c/98179/
What do you think?
Thanks,
Facundo.
Hi all,
I have a patch for this bug ready for review:
https://review.openstack.org/#/c/89844/
I also want to know your thought about Santiago's question.
Some time ago I found this bug (https://review.openstack.org/#/c/62088/) where
the decision of deprecate the use
of instance_type_extra_specs
Couple of questions,
- Do you have n-cpu running in every node? (controller and both
computes)
- Which services do you have enabled in both compute nodes?
- To which node corresponds the screen log provided?
- What is the output of nova-manage service
