Ask Your Question

tomwaterhouse's profile - activity

2014-04-27 03:42:22 -0500 received badge  Famous Question (source)
2014-04-27 03:42:22 -0500 received badge  Notable Question (source)
2014-04-14 00:17:47 -0500 received badge  Famous Question (source)
2014-03-10 14:56:02 -0500 received badge  Popular Question (source)
2014-03-10 14:56:02 -0500 received badge  Notable Question (source)
2014-01-24 18:38:14 -0500 received badge  Student (source)
2014-01-24 18:38:07 -0500 received badge  Popular Question (source)
2014-01-21 18:51:49 -0500 asked a question '.' in ethernet device name causing packstack parse error

I am attempting to install Havana with GRE in a multi-node environment. My data network device is eth1.1200. I get the following error when the neutron script is being run.

 Error: Could not parse for environment production: Syntax error at '.'; expected '}' at /var/tmp/packstack/f8e1377ccde54cb3af8320b1ca559833/manifests/10.93.235.86_neutron.pp:31

I haven't been able to find any information regarding this issue. I believe the offending lines in neutron.pp are:

if "eth1.1200" {
  $localip = $ipaddress_eth1.1200
} else {
  $localip = '10.93.235.86'
}

Before I log a bug I'm hoping someone can tell me this should work, or offer up a work-around.

Cheers,

Tom

2014-01-14 19:47:21 -0500 asked a question No instance IP address for second and subsequent instances

I am new to OpenStack and advanced networking, so may be missing something obvious.

I've setup OpenStack Havana on CentOS 6.5 using RDO. I have configured it as a multi-node deployment on Cisco UCS blades. I am using Neutron networking.

The short version of the story is that when I create a single instance in OpenStack that instance is able to get an IP address. When I create a subsequent instances each instance does NOT get an IP address. OpenStack does allocate the address but the VM instance cannot reach the DHCP server.

Example - I create the following network: neutron net-create private-network neutron subnet-create private-network 10.0.0.0/24 --name private-subnet

Then I create two instances via the UI: test1 - 10.0.0.2 test2 - 10.0.0.4

When getting information for the network from the OpenStack UI I see that 10.0.0.3 is allocated for DHCP.

Using 'ip netns exec <network namespace=""> tcpdump -i any' I can see DHCP traffic for 10.0.0.2. I don't see any for 10.0.0.4. </network>

Using 'ip netns exec <network namesapece=""> ping 10.0.0.2' is successful but not for 10.0.0.4.</network>

I have also done the above but with network 192.168.1.0 and get the same results. My goal was to create a second network and see if I could replicate the issue.

Any suggestions would be appreciated, and I would be more than happy to generate any logs/output necessary to troubleshoot this.

Regards,

Tom