nova-dpm cannot create partitions when len(cfg.default.host) > 17
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
nova-dpm |
New
|
High
|
Prabhat Ranjan |
Bug Description
Since [1], nova-dpm stores the cfg.default.host in the partitions name field. Partition creation will fail once the hostname is too long.
Along the DPM API reference, the name field is a string with a max len of 64.
The partition name gets constructed like this
<Openstack prefix>
OpenStack prefix = 'OpenStack'; len = 9
2x separator = '-'; len = 2
uuid = '0a5cb3b6-
already used: 36 + 2 + 9 = 47
left for hostname: 64-47 = 17
We have the following options:
* Live with that: Document it and have a something in the drivers init method that terminates the n-cpu when the hostname is longer
* Move the hostname to the description:
-> that's how it is done in networking-dpm at the moment. It's using the following fomrat
CPCSubset=
Having the additional identifier "CPCSubset=" might make sense to avoid issues where simple hostnames like "foo" or "test" are used which might also be part of the name of some other parition. But as the code [1] is checking for the whole format Prefix-
However we decide, I will adapt the way networking-dpm is handling that accordingly!
Ideas?
description: | updated |
summary: |
- nova-dpm cannot create paritions when len(cfg.default.host) > 17 + nova-dpm cannot create partitions when len(cfg.default.host) > 17 |
Changed in nova-dpm: | |
importance: | Undecided → Critical |
importance: | Critical → High |
tags: | added: ocata-rc-potential |
tags: |
added: ocata-backport-potential removed: ocata-rc-potential |
tags: | removed: ocata-backport-potential |
tags: | added: ocata-backport-potential |
Changed in nova-dpm: | |
assignee: | nobody → Prabhat Ranjan (pranjank) |