yahoo-eng-team team mailing list archive

[Jiang <1685423@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

I have five servers, as shown below. The cell1 and cell2 are two cell
servers, I install the rabbitmq, mysql(nova db), and nova-conductor
service on them.

   controller
     /....\
    /......\
    cell1......cell2
    /............\
  /..............\
compute1..........compute2

When I set the controller's nova.conf/[database]/connection to the cell1's nova db, I just get the compute1.
And if I set the controller's nova.conf/[database]/connection to the cell2's nova db, I just get the compute2.
If I comment out controller's nova.conf/[database]/connection, the nova-scheduler service can't restart.

I think controller's nova.conf/[database]/connection is not necessary,
Because cell's transport_url and database fields have been specified
rabbitmq and nova db.

** Affects: nova
     Importance: Undecided
         Status: New

** Description changed:

  I have five servers, as shown below. The cell1 and cell2 are two cell
  servers, I install the rabbitmq, mysql(nova db), and nova-conductor
  service on them.
  
-             controller
-               /    \
-              /      \
-           cell1    cell2
-            /          \
-           /            \
-       compute1       compute2
+               controller
+               /    \
+               /      \
+              cell1     cell2
+               /          \
+               /            \
+              compute1        compute2
  
- When I set the controller's nova.conf/[database]/connection to the cell1's nova db, I just get the compute1. 
+ When I set the controller's nova.conf/[database]/connection to the cell1's nova db, I just get the compute1.
  And if I set the controller's nova.conf/[database]/connection to the cell2's nova db, I just get the compute2.
  If I comment out controller's nova.conf/[database]/connection, the nova-scheduler service can't restart.
  
  I think controller's nova.conf/[database]/connection is not necessary,
  Because cell's transport_url and database fields have been specified
  rabbitmq and nova db.

** Description changed:

  I have five servers, as shown below. The cell1 and cell2 are two cell
  servers, I install the rabbitmq, mysql(nova db), and nova-conductor
  service on them.
  
                controller
-               /    \
-               /      \
-              cell1     cell2
-               /          \
-               /            \
-              compute1        compute2
+               /....\
+               /......\
+              cell1......cell2
+               /..........\
+               /............\
+              compute1........compute2
  
  When I set the controller's nova.conf/[database]/connection to the cell1's nova db, I just get the compute1.
  And if I set the controller's nova.conf/[database]/connection to the cell2's nova db, I just get the compute2.
  If I comment out controller's nova.conf/[database]/connection, the nova-scheduler service can't restart.
  
  I think controller's nova.conf/[database]/connection is not necessary,
  Because cell's transport_url and database fields have been specified
  rabbitmq and nova db.

** Description changed:

  I have five servers, as shown below. The cell1 and cell2 are two cell
  servers, I install the rabbitmq, mysql(nova db), and nova-conductor
  service on them.
  
                controller
                /....\
                /......\
               cell1......cell2
-               /..........\
-               /............\
-              compute1........compute2
+               /.............\
+               /...............\
+              compute1...........compute2
  
  When I set the controller's nova.conf/[database]/connection to the cell1's nova db, I just get the compute1.
  And if I set the controller's nova.conf/[database]/connection to the cell2's nova db, I just get the compute2.
  If I comment out controller's nova.conf/[database]/connection, the nova-scheduler service can't restart.
  
  I think controller's nova.conf/[database]/connection is not necessary,
  Because cell's transport_url and database fields have been specified
  rabbitmq and nova db.

** Description changed:

  I have five servers, as shown below. The cell1 and cell2 are two cell
  servers, I install the rabbitmq, mysql(nova db), and nova-conductor
  service on them.
  
                controller
                /....\
                /......\
               cell1......cell2
-               /.............\
+               /............\
                /...............\
               compute1...........compute2
  
  When I set the controller's nova.conf/[database]/connection to the cell1's nova db, I just get the compute1.
  And if I set the controller's nova.conf/[database]/connection to the cell2's nova db, I just get the compute2.
  If I comment out controller's nova.conf/[database]/connection, the nova-scheduler service can't restart.
  
  I think controller's nova.conf/[database]/connection is not necessary,
  Because cell's transport_url and database fields have been specified
  rabbitmq and nova db.

** Description changed:

  I have five servers, as shown below. The cell1 and cell2 are two cell
  servers, I install the rabbitmq, mysql(nova db), and nova-conductor
  service on them.
  
                controller
                /....\
                /......\
               cell1......cell2
                /............\
                /...............\
-              compute1...........compute2
+                compute1...........compute2
  
  When I set the controller's nova.conf/[database]/connection to the cell1's nova db, I just get the compute1.
  And if I set the controller's nova.conf/[database]/connection to the cell2's nova db, I just get the compute2.
  If I comment out controller's nova.conf/[database]/connection, the nova-scheduler service can't restart.
  
  I think controller's nova.conf/[database]/connection is not necessary,
  Because cell's transport_url and database fields have been specified
  rabbitmq and nova db.

** Description changed:

  I have five servers, as shown below. The cell1 and cell2 are two cell
  servers, I install the rabbitmq, mysql(nova db), and nova-conductor
  service on them.
  
                controller
                /....\
                /......\
               cell1......cell2
                /............\
                /...............\
-                compute1...........compute2
+                  compute1...........compute2
  
  When I set the controller's nova.conf/[database]/connection to the cell1's nova db, I just get the compute1.
  And if I set the controller's nova.conf/[database]/connection to the cell2's nova db, I just get the compute2.
  If I comment out controller's nova.conf/[database]/connection, the nova-scheduler service can't restart.
  
  I think controller's nova.conf/[database]/connection is not necessary,
  Because cell's transport_url and database fields have been specified
  rabbitmq and nova db.

** Description changed:

  I have five servers, as shown below. The cell1 and cell2 are two cell
  servers, I install the rabbitmq, mysql(nova db), and nova-conductor
  service on them.
  
                controller
                /....\
                /......\
               cell1......cell2
                /............\
-               /...............\
+                /...............\
                   compute1...........compute2
  
  When I set the controller's nova.conf/[database]/connection to the cell1's nova db, I just get the compute1.
  And if I set the controller's nova.conf/[database]/connection to the cell2's nova db, I just get the compute2.
  If I comment out controller's nova.conf/[database]/connection, the nova-scheduler service can't restart.
  
  I think controller's nova.conf/[database]/connection is not necessary,
  Because cell's transport_url and database fields have been specified
  rabbitmq and nova db.

** Description changed:

  I have five servers, as shown below. The cell1 and cell2 are two cell
  servers, I install the rabbitmq, mysql(nova db), and nova-conductor
  service on them.
  
-               controller
-               /....\
-               /......\
-              cell1......cell2
-               /............\
-                /...............\
-                  compute1...........compute2
+     controller
+      /....\
+     /......\
+     cell1......cell2
+     /............\
+    /..............\
+ compute1...........compute2
  
  When I set the controller's nova.conf/[database]/connection to the cell1's nova db, I just get the compute1.
  And if I set the controller's nova.conf/[database]/connection to the cell2's nova db, I just get the compute2.
  If I comment out controller's nova.conf/[database]/connection, the nova-scheduler service can't restart.
  
  I think controller's nova.conf/[database]/connection is not necessary,
  Because cell's transport_url and database fields have been specified
  rabbitmq and nova db.

** Description changed:

  I have five servers, as shown below. The cell1 and cell2 are two cell
  servers, I install the rabbitmq, mysql(nova db), and nova-conductor
  service on them.
  
      controller
       /....\
      /......\
      cell1......cell2
      /............\
-    /..............\
+   /..............\
  compute1...........compute2
  
  When I set the controller's nova.conf/[database]/connection to the cell1's nova db, I just get the compute1.
  And if I set the controller's nova.conf/[database]/connection to the cell2's nova db, I just get the compute2.
  If I comment out controller's nova.conf/[database]/connection, the nova-scheduler service can't restart.
  
  I think controller's nova.conf/[database]/connection is not necessary,
  Because cell's transport_url and database fields have been specified
  rabbitmq and nova db.

** Description changed:

  I have five servers, as shown below. The cell1 and cell2 are two cell
  servers, I install the rabbitmq, mysql(nova db), and nova-conductor
  service on them.
  
      controller
       /....\
      /......\
      cell1......cell2
      /............\
    /..............\
- compute1...........compute2
+ compute1..........compute2
  
  When I set the controller's nova.conf/[database]/connection to the cell1's nova db, I just get the compute1.
  And if I set the controller's nova.conf/[database]/connection to the cell2's nova db, I just get the compute2.
  If I comment out controller's nova.conf/[database]/connection, the nova-scheduler service can't restart.
  
  I think controller's nova.conf/[database]/connection is not necessary,
  Because cell's transport_url and database fields have been specified
  rabbitmq and nova db.

** Description changed:

  I have five servers, as shown below. The cell1 and cell2 are two cell
  servers, I install the rabbitmq, mysql(nova db), and nova-conductor
  service on them.
  
-     controller
+    controller
       /....\
      /......\
      cell1......cell2
      /............\
    /..............\
  compute1..........compute2
  
  When I set the controller's nova.conf/[database]/connection to the cell1's nova db, I just get the compute1.
  And if I set the controller's nova.conf/[database]/connection to the cell2's nova db, I just get the compute2.
  If I comment out controller's nova.conf/[database]/connection, the nova-scheduler service can't restart.
  
  I think controller's nova.conf/[database]/connection is not necessary,
  Because cell's transport_url and database fields have been specified
  rabbitmq and nova db.

-- 
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/1685423

Title:
  Ocata does not support multiple cells

Status in OpenStack Compute (nova):
  New

Bug description:
  I have five servers, as shown below. The cell1 and cell2 are two cell
  servers, I install the rabbitmq, mysql(nova db), and nova-conductor
  service on them.

     controller
       /....\
      /......\
      cell1......cell2
      /............\
    /..............\
  compute1..........compute2

  When I set the controller's nova.conf/[database]/connection to the cell1's nova db, I just get the compute1.
  And if I set the controller's nova.conf/[database]/connection to the cell2's nova db, I just get the compute2.
  If I comment out controller's nova.conf/[database]/connection, the nova-scheduler service can't restart.

  I think controller's nova.conf/[database]/connection is not necessary,
  Because cell's transport_url and database fields have been specified
  rabbitmq and nova db.

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