DPM resource Name and/or description field is used to map an OpenStack object to a DPM resource
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
networking-dpm |
New
|
Undecided
|
Unassigned | ||
nova-dpm |
New
|
Medium
|
Unassigned |
Bug Description
Somehow a mapping between a DPM resource (e.g. partition or NIC) and the corresponding Openstack object (e.g. server or port) must be stored.
At the moment we're using
* The DPM partition name to store the OpenStakc instance UUID and the cpcsubset name
* The DPM NICs name to store the Neutron ports UUIDs and the description to store the cpcsubset name
Both values are of importance
* Openstack UUID - to map the dpm to the openstack object
* cpcsubset (host) name - to show to which cpcsubet a resource (instance, nic) belongs to.
The problem is, that an HMC user can easily change the name. We should rely on something different here!
For nova it could be the following attribute
# openstack instance show xxx
| OS-EXT-
-> this name smells like a libvirt name - maybe we can override and use it somehow with the DPM uuid and cpcsubset?
Or what about having a separate field at each DPM object that can be used for such purposes?
description: | updated |
description: | updated |
description: | updated |
Changed in nova-dpm: | |
importance: | Undecided → High |
Using the HMC to change OpenStack managed partitions is an forbidden by-passing IMO. That's equivalent of using "virsh edit" on a KVM host to change KVM guest information.
Nevertheless, we might want to rethink the design here.