yahoo-eng-team team mailing list archive

[Corey Bryant <corey.bryant@xxxxxxxxxxxxx>]

Public bug reported:

I'm not seeing that nova-manage cell_v2 provides a way to update the
transport_url (or database) for a cell.  It's possible that I'm missing
something here but I've not found a way to do this.

This is a problem when scaling rabbitmq, for example.  If I have a cell
associated with a single rabbitmq instance and I want to scale to 2 rmq
instances, then there needs to be a way to update the database for the
cell.

Running 'nova-manage cell_v2 create_cell --name cell1' twice, 1st time
with the transport_url in nova.conf having one rmq server, and 2nd time
with the transport_url in nova.conf having two rmq servers is
successful.  After this, there are two cell_mappings records for
"cell1", and it appears that the first entry is what ends up being used
for ensuing commands (ie. if I take the the original rmq out of
active/active HA, I can't deploy an instance).

Here's what the cell_mappings table looks like after the 2nd create_cell
call:

mysql> select * from cell_mappings;
+---------------------+------------+----+--------------------------------------+-------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+----------------------------------------------------------------------+
| created_at          | updated_at | id | uuid                                 | name  | transport_url                                                                      | database_connection                                                  |
+---------------------+------------+----+--------------------------------------+-------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+----------------------------------------------------------------------+
| 2017-02-14 21:06:49 | NULL       |  1 | 00000000-0000-0000-0000-000000000000 | cell0 | none:///                                                                      | mysql://nova:7Jf4sgRNqbfzR8d3hxyWKYpzFfY6gK95@10.5.30.174/nova_cell0 |
| 2017-02-14 21:06:56 | NULL       |  2 | 1499460c-41f2-422d-b452-03b7995907c4 | cell1 | rabbit://nova:PtPFqF24ZxsB5GqCRN77Pbrp4h3cCYgJJ9XJwBThPhF2kz9M2Trbg8CSpFVcjY5L@10.5.30.169:/openstack                                                                      | mysql://nova:7Jf4sgRNqbfzR8d3hxyWKYpzFfY6gK95@10.5.30.174/nova       |
| 2017-02-14 22:35:48 | NULL       |  5 | 4b363076-7d89-451d-be99-057b0ad67e73 | cell1 | rabbit://nova:PtPFqF24ZxsB5GqCRN77Pbrp4h3cCYgJJ9XJwBThPhF2kz9M2Trbg8CSpFVcjY5L@10.5.30.169:,nova:PtPFqF24ZxsB5GqCRN77Pbrp4h3cCYgJJ9XJwBThPhF2kz9M2Trbg8CSpFVcjY5L@10.5.30.187:/openstack | mysql://nova:7Jf4sgRNqbfzR8d3hxyWKYpzFfY6gK95@10.5.30.174/nova       |
+---------------------+------------+----+--------------------------------------+----

It seems as if the 2nd cell_create call should update the original cell1
record, or there should be an cell_update subcommand.

** Affects: nova
     Importance: Undecided
         Status: New

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1664759

Title:
  cells v2 can't update cell transport_url

Status in OpenStack Compute (nova):
  New

Bug description:
  I'm not seeing that nova-manage cell_v2 provides a way to update the
  transport_url (or database) for a cell.  It's possible that I'm
  missing something here but I've not found a way to do this.

  This is a problem when scaling rabbitmq, for example.  If I have a
  cell associated with a single rabbitmq instance and I want to scale to
  2 rmq instances, then there needs to be a way to update the database
  for the cell.

  Running 'nova-manage cell_v2 create_cell --name cell1' twice, 1st time
  with the transport_url in nova.conf having one rmq server, and 2nd
  time with the transport_url in nova.conf having two rmq servers is
  successful.  After this, there are two cell_mappings records for
  "cell1", and it appears that the first entry is what ends up being
  used for ensuing commands (ie. if I take the the original rmq out of
  active/active HA, I can't deploy an instance).

  Here's what the cell_mappings table looks like after the 2nd
  create_cell call:

  mysql> select * from cell_mappings;
  +---------------------+------------+----+--------------------------------------+-------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+----------------------------------------------------------------------+
  | created_at          | updated_at | id | uuid                                 | name  | transport_url                                                                      | database_connection                                                  |
  +---------------------+------------+----+--------------------------------------+-------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+----------------------------------------------------------------------+
  | 2017-02-14 21:06:49 | NULL       |  1 | 00000000-0000-0000-0000-000000000000 | cell0 | none:///                                                                      | mysql://nova:7Jf4sgRNqbfzR8d3hxyWKYpzFfY6gK95@10.5.30.174/nova_cell0 |
  | 2017-02-14 21:06:56 | NULL       |  2 | 1499460c-41f2-422d-b452-03b7995907c4 | cell1 | rabbit://nova:PtPFqF24ZxsB5GqCRN77Pbrp4h3cCYgJJ9XJwBThPhF2kz9M2Trbg8CSpFVcjY5L@10.5.30.169:/openstack                                                                      | mysql://nova:7Jf4sgRNqbfzR8d3hxyWKYpzFfY6gK95@10.5.30.174/nova       |
  | 2017-02-14 22:35:48 | NULL       |  5 | 4b363076-7d89-451d-be99-057b0ad67e73 | cell1 | rabbit://nova:PtPFqF24ZxsB5GqCRN77Pbrp4h3cCYgJJ9XJwBThPhF2kz9M2Trbg8CSpFVcjY5L@10.5.30.169:,nova:PtPFqF24ZxsB5GqCRN77Pbrp4h3cCYgJJ9XJwBThPhF2kz9M2Trbg8CSpFVcjY5L@10.5.30.187:/openstack | mysql://nova:7Jf4sgRNqbfzR8d3hxyWKYpzFfY6gK95@10.5.30.174/nova       |
  +---------------------+------------+----+--------------------------------------+----

  It seems as if the 2nd cell_create call should update the original
  cell1 record, or there should be an cell_update subcommand.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1664759/+subscriptions