leonardo's profile - activity

2015-11-25 04:28:59 -0600 received badge  Famous Question (source)
2015-04-16 03:28:17 -0600 received badge  Student (source)
2014-09-18 01:00:55 -0600 received badge  Famous Question (source)
2014-09-18 01:00:55 -0600 received badge  Notable Question (source)
2014-09-18 01:00:55 -0600 received badge  Popular Question (source)
2014-08-08 04:17:12 -0600 received badge  Famous Question (source)
2014-06-28 00:12:47 -0600 received badge  Famous Question (source)
2014-06-23 11:46:02 -0600 received badge  Notable Question (source)
2014-05-14 14:21:34 -0600 received badge  Popular Question (source)
2014-05-14 06:39:30 -0600 answered a question Manage IPs via nova-network

I found out the approach and that is by using the "v4-fixed-ip" variable while launching an instance.

2014-05-14 05:58:31 -0600 received badge  Notable Question (source)
2014-05-06 00:10:03 -0600 received badge  Popular Question (source)
2014-05-05 11:07:52 -0600 asked a question Manage IPs via nova-network

Hello everyone,

So I have setup two nodes where one is acting as a Controller and the second as a compute node using legacy nova-network (Flat DHCP). The nodes' management subnet is 192.168.0.1/24. I configured the nova controller to use the subnet 10.0.0.0/24 as my (fake) public IP addresses. However, I noticed the following;

1) When my VM boots up, 10.0.0.1 is assigned to the DHCP server (dnsmasq) on my compute node and 10.0.0.2 is assigned to my VM.
2) This would imply that if i start a second VM instance on a second SEPARATE compute host, 10.0.0.3 and 10.0.0.4 would get allocated to the second compute host. 3) This would mean that 4 'public' ip addresses are being used for two compue hosts.

Is there a way around this using the above setup by assigning the IP address to the VMs at nova boot without the DHCP getting involved at all?

2014-05-05 07:12:17 -0600 received badge  Famous Question (source)
2014-05-04 09:29:51 -0600 asked a question Bare metal approach

Hello everyone,

I plan to run openstack ice house using the legacy nova networkapproach (No Neuton). However, I also plan to run only one VM instance per Physical host which brings me to my questions;

1) Judging from this documentation(http://docs.openstack.org/icehouse/config-reference/content/baremetal.html), I have to make some few changes on the nova.conf file of each compute node. Is that all or do I need to run neutron as well as a pre-requisite?
2) I read that it is possible to boot a specific image on a specific compute node. Is it possible to assign a specific ip adress to a compute node as well? If yes, can you please tell me how?

Thanks!

2014-05-04 09:16:19 -0600 received badge  Enthusiast
2014-05-02 12:06:07 -0600 received badge  Notable Question (source)
2014-05-01 23:52:17 -0600 received badge  Scholar (source)
2014-05-01 23:52:09 -0600 received badge  Popular Question (source)
2014-05-01 23:51:53 -0600 asked a question ndnsmasq: failed to create listening socket

Hello all,

While starting the VM instance from the controller, I get the following error;

\'\ndnsmasq: failed to create listening socket for 10.0.0.25: Cannot assign requested address\n\'\n'].

Following is my network config on the compute node;

auto eth0
iface eth0 inet static
address 10.20.30.156
network 10.20.30.0
netmask 255.255.255.0
broadcast 10.20.30.255
gateway 10.20.30.254

auto eth1
iface eth1 inet manual
up ip link set dev $IFACE up
down ip link set dev $IFACE down

netstat -tanpu | grep LISTEN
tcp 0 0 0.0.0.0:111 0.0.0.0:* LISTEN 1988/rpcbind
tcp 0 0 0.0.0.0:53 0.0.0.0:* LISTEN 4016/dnsmasq
tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN 2918/sshd
tcp 0 0 127.0.0.1:25 0.0.0.0:* LISTEN 3282/exim4
tcp 0 0 0.0.0.0:36327 0.0.0.0:* LISTEN 2019/rpc.statd
tcp6 0 0 :::111 :::* LISTEN 1988/rpcbind
tcp6 0 0 :::53 :::* LISTEN 4016/dnsmasq
tcp6 0 0 :::22 :::* LISTEN 2918/sshd
tcp6 0 0 ::1:25 :::* LISTEN 3282/exim4
tcp6 0 0 :::56676 :::* LISTEN 2019/rpc.statd

I have tried both with and without the dnsmasq service but still the same problem. I have a traditional two node setup using nova legacy network. Any hints?

2014-05-01 13:31:53 -0600 commented answer compute node default network configuration

my compute node has two NICs and the controller has one NIC. :) Plus, I hope OpenStack does not complain that I SHOULD have two NICs on the controller....

2014-05-01 12:59:55 -0600 answered a question compute node default network configuration

HI fifeldt,

Thanks for your answer. The interface configuration should look like this on both nodes then;

Controller

auto lo
iface lo inet loopback
auto eth0
iface eth0 inet static
address 192.168.30.2
network 192.168.30.0
netmask 255.255.255.0
broadcast 192.168.30.255
gateway 192.168.30.1

Compute Node

auto lo
iface lo inet loopback
auto eth0
iface eth0 inet static
address 192.168.30.3
network 192.168.30.0
netmask 255.255.255.0
broadcast 192.168.30.255
gateway 192.168.30.1

auto eth1
iface eth1 inet manual
up ip link set dev eth1 up
down ip link set dev eth1 down

Correct?

2014-05-01 10:48:27 -0600 asked a question compute node default network configuration

Hello all,

I am setting up an openstack cloud with legacy nova network. I have the following setup,

1) Controller (1 NIC card with the follwing network configuration)

auto lo
iface lo inet loopback

iface eth0 inet static
address 192.168.30.2
network 192.168.30.0
netmask 255.255.255.0
broadcast 192.168.30.255
gateway 192.168.30.1

2) On the compute node, I have two NICs (eth0 and eth1)

auto lo
iface lo inet loopback

iface eth0 inet static
address 192.168.30.3
network 192.168.30.0
netmask 255.255.255.0
broadcast 192.168.30.255
gateway 192.168.30.1

Question; I got several errors while trying to launch an instance. The errors happening after trying to set the gateway on the VM and the readable error is "Device not found". I am guessing that it is due to the fact that I have not setup the bridge. Can anyone guide me that how the network configuration should look like after the bridge has been setup. Below is my relevant nova network config;

network_manager=nova.network.manager.FlatDHCPManager
network_size = 254
allow_same_net_traffic = False
multi_host = True
send_arp_for_ha = True
share_dhcp_address = True
force_dhcp_release = True
flat_network_bridge = br100
flat_interface = eth1
public_interface = eth1

I will appreciate the help.

2014-04-30 22:53:41 -0600 received badge  Notable Question (source)
2014-04-30 09:13:36 -0600 received badge  Popular Question (source)
2014-04-30 02:08:00 -0600 answered a question Nova cannot create network

Hello,

So I finally managed to run the command. The solution is quite simple. My compute node was not fully setup and it also needs to be setup as well if we intend to run the Nova legacy network. Hope it helps anyone who might run into a similar situation.

2014-04-29 12:17:22 -0600 received badge  Editor (source)
2014-04-29 12:14:52 -0600 asked a question Nova cannot create network

Hello All,

I followed all the steps of installing openstack on Debian Wheezy using this documentation. I am trying to setup the legacy network scenario where I have two nodes (one acting as controller and the latter acting as compute node). I have successfully setup Keystone, Image service and Nova controller. However, when the time comes to create the network by using legacy nova-network scenario, the following happens (i am just pasting the highlight of the logs);

2014-04-29 18:59:59.295 4844 DEBUG nova.api.openstack.compute.contrib.os_networks [req-54fef079-4796-4b5c-851f-0960d6a2e323 3f31b75b621d42849e6f90983120ac81 2188d77d01974be99f0390a273dff8e3] Creating network with label demo-net create /usr/lib/python2.7/dist-packages/nova/api/openstack/compute/contrib/os_networks.py:126

2014-04-29 18:59:59.308 4844 INFO oslo.messaging._drivers.impl_rabbit [-] Connected to AMQP server on localhost:5672

2014-04-29 18:59:59.324 4844 INFO oslo.messaging._drivers.impl_rabbit [-] Connected to AMQP server on localhost:5672

2014-04-29 19:00:59.385 4844 TRACE nova.api.openstack MessagingTimeout: Timed out waiting for a reply to message ID 38c920b0890341069d85556bd28f07a0

2014-04-29 19:00:59.385 4844 TRACE nova.api.openstack 

2014-04-29 19:00:59.389 4844 INFO nova.api.openstack [req-54fef079-4796-4b5c-851f-0960d6a2e323 3f31b75b621d42849e6f90983120ac81 2188d77d01974be99f0390a273dff8e3] http://10.20.30.113:8774/v2/2188d77d01974be99f0390a273dff8e3/os-networks returned with HTTP 500

2014-04-29 19:00:59.390 4844 DEBUG nova.api.openstack.wsgi [req-54fef079-4796-4b5c-851f-0960d6a2e323 3f31b75b621d42849e6f90983120ac81 2188d77d01974be99f0390a273dff8e3] Returning 500 to user: The server has either erred or is incapable of performing the requested operation. __call__ /usr/lib/python2.7/dist-packages/nova/api/openstack/wsgi.py:1215

2014-04-29 19:00:59.390 4844 INFO nova.osapi_compute.wsgi.server [req-54fef079-4796-4b5c-851f-0960d6a2e323 3f31b75b621d42849e6f90983120ac81 2188d77d01974be99f0390a273dff8e3] 10.20.30.113 "POST /v2/2188d77d01974be99f0390a273dff8e3/os-networks HTTP/1.1" status: 500 len: 335 time: 60.7838590

I am using the following command;

nova network-create demo-net --bridge br100 --multi-host T   --fixed-range-v4 203.0.113.24/29

Following is the output to make sure OpenStack has been setup correctly as per the guide till this point;

**# keystone user-list<br>**
+----------------------------------+-------+---------+----------------+
|                id                |  name | enabled |     email      |
+----------------------------------+-------+---------+----------------+
| 3f31b75b621d42849e6f90983120ac81 | admin |   True  | root@localhost |
+----------------------------------+-------+---------+----------------+


**# glance image-list<br>**
+--------------------------------------+---------------------+-------------+------------------+----------+--------+
| ID                                   | Name                | Disk Format | Container Format | Size     | Status |
+--------------------------------------+---------------------+-------------+------------------+----------+--------+
| 88dfb568-92b5-4112-9eba-a36a39f3641b | cirros-0.3.2-x86_64 | qcow2       | bare             | 13167616 | active |
+--------------------------------------+---------------------+-------------+------------------+----------+--------+


**#nova image-list<br>**
+--------------------------------------+---------------------+--------+--------+
| ID                                   | Name                | Status | Server |
+--------------------------------------+---------------------+--------+--------+
| 88dfb568-92b5-4112-9eba-a36a39f3641b | cirros-0.3.2-x86_64 | ACTIVE |        |
+--------------------------------------+---------------------+--------+--------+

**#  nova network-create demo-net --bridge br100 --multi-host T --fixed-range-v4 203.0.113.24/29
ERROR: The server has either erred or is incapable of performing the requested operation. (HTTP 500) (Request-ID: req-2acbaa01-b401-43d4-8360-9d58cf12ae05)**

My hosts file is correctly setup as the guide suggests. What I have done so far;

1) Rebooted the controller
2) restarted RabbitMQ multiple times
3) Checked/Resetted the rabbitMQ passord (log tells it is connected)

Following is the rabbitMQ config from nova.conf;

############
**# RABBITMQ #**
############
rabbit_host = localhost
fake_rabbit=false
rabbit_virtual_host=/
rabbit_userid = guest
rabbit_password = guest
rabbit_port=5672
rabbit_use_ssl=false
rabbit_retry_interval=3
**# The messaging module to use, defaults to kombu (works for rabbit).
**# You can also use qpid: nova.rpc.impl_qpid****
rpc_backend = nova.openstack.common.rpc.impl_kombu

Neutron is not setup since I intend to use legacy network. Any hints?