I checked "OS-EXT-SRV-ATTR:instance_name" attribute is not storing into the database. It's something like creating at run time probably using id of instance. 1. https://ask.openstack.org/en/question/26295/how-does-nova-maps-the-display-name-of-vm-or-instance-in-openstack-to-instance-name-in-kvmesx-etc/ 2. https://github.com/openstack/nova/blob/master/nova/api/openstack/compute/extended_server_attributes.py#L49
Probably we can use follow. In 'nova' database there is a table called 'instance_extra'. mysql> show columns from instance_extra; +-------------------+-------------+------+-----+---------+----------------+ | Field | Type | Null | Key | Default | Extra | +-------------------+-------------+------+-----+---------+----------------+ | created_at | datetime | YES | | NULL | | | updated_at | datetime | YES | | NULL | | | deleted_at | datetime | YES | | NULL | | | deleted | int(11) | YES | | NULL | | | id | int(11) | NO | PRI | NULL | auto_increment | | instance_uuid | varchar(36) | NO | MUL | NULL | | | numa_topology | text | YES | | NULL | | | pci_requests | text | YES | | NULL | | | flavor | text | YES | | NULL | | | vcpu_model | text | YES | | NULL | | | migration_context | text | YES | | NULL | | | keypairs | text | YES | | NULL | | | device_metadata | text | YES | | NULL | | +-------------------+-------------+------+-----+---------+----------------+ 13 rows in set (0.00 sec)
My suggestion is we can use column 'device_metadata'.
I checked "OS-EXT- SRV-ATTR: instance_ name" attribute is not storing into the database. It's something like creating at run time probably using id of instance. /ask.openstack. org/en/ question/ 26295/how- does-nova- maps-the- display- name-of- vm-or-instance- in-openstack- to-instance- name-in- kvmesx- etc/ /github. com/openstack/ nova/blob/ master/ nova/api/ openstack/ compute/ extended_ server_ attributes. py#L49
1. https:/
2. https:/
Probably we can use follow. ------- ------+ ------- ------+ ------+ -----+- ------- -+----- ------- ----+ ------- ------+ ------- ------+ ------+ -----+- ------- -+----- ------- ----+ ------- ------+ ------- ------+ ------+ -----+- ------- -+----- ------- ----+
In 'nova' database there is a table called 'instance_extra'.
mysql> show columns from instance_extra;
+------
| Field | Type | Null | Key | Default | Extra |
+------
| created_at | datetime | YES | | NULL | |
| updated_at | datetime | YES | | NULL | |
| deleted_at | datetime | YES | | NULL | |
| deleted | int(11) | YES | | NULL | |
| id | int(11) | NO | PRI | NULL | auto_increment |
| instance_uuid | varchar(36) | NO | MUL | NULL | |
| numa_topology | text | YES | | NULL | |
| pci_requests | text | YES | | NULL | |
| flavor | text | YES | | NULL | |
| vcpu_model | text | YES | | NULL | |
| migration_context | text | YES | | NULL | |
| keypairs | text | YES | | NULL | |
| device_metadata | text | YES | | NULL | |
+------
13 rows in set (0.00 sec)
My suggestion is we can use column 'device_metadata'.