Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
User server supported microversion when nova list services (#160)
* User server supported microversion when nova list services When nova cell enabled, we have two nova-conductor service, one is nova-conductor and another is super nova-super-conductor, they have same name in different databases (nova_cell0 & nova_cell1). The only difference for the agent_state metrics is the service ID, but service ID is actually a db seqNo, they can be same in different tables. In our cases, we met two nova-conductors have the same label, that will cause metrics failed to store. For nova apiversion bigger than 2.53, it will return uuid for service id, so add microversion for nova client. * User server supported microversion when nova list services When nova cell enabled, we have two nova-conductor service, one is nova-conductor and another is super nova-super-conductor, they have same name in different databases (nova_cell0 & nova_cell1). The only difference for the agent_state metrics is the service ID, but service ID is actually a db seqNo, they can be same in different tables. In our cases, we met two nova-conductors have the same label, that will cause metrics failed to store. For nova apiversion bigger than 2.53, it will return uuid for service id, so add microversion for nova client. * User server supported microversion when nova list services When nova cell enabled, we have two nova-conductor service, one is nova-conductor and another is super nova-super-conductor, they have same name in different databases (nova_cell0 & nova_cell1). The only difference for the agent_state metrics is the service ID, but service ID is actually a db seqNo, they can be same in different tables. In our cases, we met two nova-conductors have the same label, that will cause metrics failed to store. For nova apiversion bigger than 2.53, it will return uuid for service id, so add microversion for nova client. * Use server supported microversion when nova list services When nova cell enabled, we have two nova-conductor service, one is nova-conductor and another is super nova-super-conductor, they have same name in different databases (nova_cell0 & nova_cell1). The only difference for the agent_state metrics is the service ID, but service ID is actually a db seqNo, they can be same in different tables. In our cases, we met two nova-conductors have the same label, that will cause metrics failed to store. For nova apiversion bigger than 2.53, it will return uuid for service id, so add microversion for nova client. * Use server supported microversion when nova list services When nova cell enabled, we have two nova-conductor service, one is nova-conductor and another is super nova-super-conductor, they have same name in different databases (nova_cell0 & nova_cell1). The only difference for the agent_state metrics is the service ID, but service ID is actually a db seqNo, they can be same in different tables. In our cases, we met two nova-conductors have the same label, that will cause metrics failed to store. For nova apiversion bigger than 2.53, it will return uuid for service id, so add microversion for nova client. * Update exporter_test.go * Update exporter_test.go Co-authored-by: minsu <minsu@cisco.com> Co-authored-by: Jorge Niedbalski <jnr@metaklass.org>
- Loading branch information