| 2017-02-14 14:06:57 |
Andreas Scheuring |
bug |
|
|
added bug |
| 2017-02-14 14:07:25 |
Andreas Scheuring |
bug task added |
|
networking-dpm |
|
| 2017-02-14 14:12:16 |
Andreas Scheuring |
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
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-SRV-ATTR:instance_name | instance-00000015
-> this name smells like a libvirt name - probably we can override it somehow? |
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
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-SRV-ATTR:instance_name | instance-00000015
-> this name smells like a libvirt name - maybe we can override and use it somehow? |
|
| 2017-02-14 14:14:12 |
Andreas Scheuring |
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
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-SRV-ATTR:instance_name | instance-00000015
-> this name smells like a libvirt name - maybe we can override and use it somehow? |
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-SRV-ATTR:instance_name | instance-00000015
-> this name smells like a libvirt name - maybe we can override and use it somehow with the DPM uuid? |
|
| 2017-02-14 14:15:03 |
Andreas Scheuring |
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-SRV-ATTR:instance_name | instance-00000015
-> this name smells like a libvirt name - maybe we can override and use it somehow with the DPM uuid? |
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-SRV-ATTR:instance_name | instance-00000015
-> 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? |
|
| 2017-02-17 15:27:50 |
Markus Zoeller (markus_z) |
tags |
|
ocata-rc-potential |
|
| 2017-02-21 15:15:49 |
Markus Zoeller (markus_z) |
tags |
ocata-rc-potential |
|
|
| 2017-03-03 08:13:53 |
Prabhat Ranjan |
nova-dpm: importance |
Undecided |
High |
|
| 2017-03-03 13:34:51 |
Andreas Scheuring |
nova-dpm: importance |
High |
Medium |
|
