how to make 'networks' table marked as bridge

Asked by Girish L C on 2010-12-22

While doing multi node set up; using this link http://wiki.openstack.org/NovaInstall/MultipleServer
In the Step 4 Setup nova environment:

I have successfully configured the n/w using below command;
/usr/bin/python /usr/bin/nova-manage network create cidr num_networks total_ips

But after this, I have to make
one of the networks listed in the 'networks' table needs to be marked as bridge in order for the code to know that a bridge exists

How to do this? any one can help me??

Thanks,
Girish.L.C

Question information

Language:
English Edit question
Status:
Solved
For:
OpenStack Compute (nova) Edit question
Assignee:
No assignee Edit question
Solved by:
Girish L C
Solved:
2010-12-23
Last query:
2010-12-23
Last reply:
2010-12-22
Vish Ishaya (vishvananda) said : #1

Can you give more details on your issue? I'm not sure exactly what you mean. The network table has a bridge column which should be set. It defaults to br100.

Vish

On Dec 22, 2010, at 5:35 AM, Girish L C wrote:

> New question #138722 on OpenStack Compute (nova):
> https://answers.launchpad.net/nova/+question/138722
>
> While doing multi node set up; using this link http://wiki.openstack.org/NovaInstall/MultipleServer
> In the Step 4 Setup nova environment:
>
> I have successfully configured the n/w using below command;
> /usr/bin/python /usr/bin/nova-manage network create cidr num_networks total_ips
>
> But after this, I have to make
> one of the networks listed in the 'networks' table needs to be marked as bridge in order for the code to know that a bridge exists
>
> How to do this? any one can help me??
>
> Thanks,
> Girish.L.C
>
>
>
>
> --
> You received this question notification because you are a member of Nova
> Core, which is an answer contact for OpenStack Compute (nova).

Girish L C (girish-lc) said : #2

Thanks for your reply,
when I saw the networks table below is the entry which has shown; and in that bridge is mentioned br100, is this correct??

mysql> select * from networks;
+---------------------+------------+------------+---------+----+----------+-----------------+-----------------+--------+--------------+--------------+------+------+--------------------+-----------------+---------------------+--------------+------------+------+
| created_at | updated_at | deleted_at | deleted | id | injected | cidr | netmask | bridge | gateway | broadcast | dns | vlan | vpn_public_address | vpn_public_port | vpn_private_address | dhcp_start | project_id | host |
+---------------------+------------+------------+---------+----+----------+-----------------+-----------------+--------+--------------+--------------+------+------+--------------------+-----------------+---------------------+--------------+------------+------+
| 2010-12-22 13:19:58 | NULL | NULL | 0 | 1 | 0 | 192.168.1.0/29 | 255.255.255.248 | br100 | 192.168.1.1 | 192.168.1.7 | NULL | NULL | NULL | NULL | NULL | 192.168.1.2 | NULL | NULL |
| 2010-12-22 13:19:58 | NULL | NULL | 0 | 2 | 0 | 192.168.1.8/29 | 255.255.255.248 | br100 | 192.168.1.9 | 192.168.1.15 | NULL | NULL | NULL | NULL | NULL | 192.168.1.10 | NULL | NULL |
| 2010-12-22 13:19:58 | NULL | NULL | 0 | 3 | 0 | 192.168.1.16/29 | 255.255.255.248 | br100 | 192.168.1.17 | 192.168.1.23 | NULL | NULL | NULL | NULL | NULL | 192.168.1.18 | NULL | NULL |
| 2010-12-22 13:19:59 | NULL | NULL | 0 | 4 | 0 | 192.168.1.24/29 | 255.255.255.248 | br100 | 192.168.1.25 | 192.168.1.31 | NULL | NULL | NULL | NULL | NULL | 192.168.1.26 | NULL | NULL |
| 2010-12-22 13:19:59 | NULL | NULL | 0 | 5 | 0 | 192.168.1.32/29 | 255.255.255.248 | br100 | 192.168.1.33 | 192.168.1.39 | NULL | NULL | NULL | NULL | NULL | 192.168.1.34 | NULL | NULL |
| 2010-12-22 13:20:00 | NULL | NULL | 0 | 6 | 0 | 192.168.1.40/29 | 255.255.255.248 | br100 | 192.168.1.41 | 192.168.1.47 | NULL | NULL | NULL | NULL | NULL | 192.168.1.42 | NULL | NULL |
| 2010-12-22 13:20:00 | NULL | NULL | 0 | 7 | 0 | 192.168.1.48/29 | 255.255.255.248 | br100 | 192.168.1.49 | 192.168.1.55 | NULL | NULL | NULL | NULL | NULL | 192.168.1.50 | NULL | NULL |
| 2010-12-22 13:20:01 | NULL | NULL | 0 | 8 | 0 | 192.168.1.56/29 | 255.255.255.248 | br100 | 192.168.1.57 | 192.168.1.63 | NULL | NULL | NULL | NULL | NULL | 192.168.1.58 | NULL | NULL |
+---------------------+------------+------------+---------+----+----------+-----------------+-----------------+--------+--------------+--------------+------+------+--------------------+-----------------+---------------------+--------------+------------+------+
8 rows in set (0.00 sec)

Girish L C (girish-lc) said : #3

After this, I restart all nova services but out of 4 services only one service is running successfully;

root@girish-S5520UR:/etc/init.d# ll nova-scheduler nova-network nova-objectstore
lrwxrwxrwx 1 root root 21 2010-12-22 12:05 nova-network -> /lib/init/upstart-job*
lrwxrwxrwx 1 root root 21 2010-12-22 12:05 nova-objectstore -> /lib/init/upstart-job*
lrwxrwxrwx 1 root root 21 2010-12-22 12:05 nova-scheduler -> /lib/init/upstart-job*
root@girishl-S5520UR:/etc/init.d# ps -ef | grep nova*
root@girish-S5520UR:/etc/init.d# service nova-api status
nova-api stop/waiting
root@girish-S5520UR:/etc/init.d# service nova-network status
nova-network stop/waiting
root@girish-S5520UR:/etc/init.d# service nova-objectstore status
nova-objectstore start/running, process 6033
root@igirish-S5520UR:/etc/init.d# service nova-scheduler status
nova-scheduler stop/waiting

root@girish-S5520UR:~# ps -eaf | grep "nova*"
nova 6200 6193 0 13:30 ? 00:00:00 /usr/bin/python /usr/bin/nova-objectstore --uid 115 --gid 65534 --pidfile /var/run/nova/nova-objectstore.pid --flagfile=/etc/nova/nova.conf --nodaemon
root 6210 4896 0 13:30 pts/1 00:00:00 grep --color=auto nova*

Saying only nova-object store is running; any idea where it went wrong?

-Thanks
Girish.L.C

Girish L C (girish-lc) said : #4

Actually the 5th step i.e Step 5: Create nova certs
we have to do it as sudo and not as root
Also we have to copy the nova.zip and novarc files into home directory
Then above issue will not occurs.

intel@girish-S5520UR:~$ . ~/.bashrc
intel@girish-S5520UR:~$ sudo service nova-api restart
nova-api start/running, process 7874
intel@girish-S5520UR:~$ sudo service nova-scheduler restart
nova-scheduler start/running, process 7918
intel@girish-S5520UR:~$ sudo service nova-network restart
nova-network start/running, process 7950
intel@girish-S5520UR:~$ sudo service nova-objectstore restart
nova-objectstore start/running, process 7969

Thanks much; now I'm able to successfully set up Cloud Controller.

-Girish.L.C