Re: [Openstack] Recovering from full outage

2018-07-06 Thread Torin Woltjer
I explored creating a second "selfservice" vxlan to see if DHCP would work on it as it does on my external "provider" network. The new vxlan network shares the same problems as the old vxlan network. Am I having problems with VXLAN in particular? Torin Woltjer Grand Dial Communications - A ZK

Re: [Openstack] NUMA some of the time?

2018-07-06 Thread Jay Pipes
Hi Tony, The short answer is that you cannot do that today. Today, each Nova compute node is either "all in" for NUMA and CPU pinning or it's not. This means that for resource-constrained environments like "The Edge!", there are not very good ways to finely divide up a compute node and make

Re: [Openstack] Recovering from full outage

2018-07-06 Thread Torin Woltjer
Interestingly, I can ping the neutron router at 172.16.1.1 just fine, but DHCP (located at 172.16.1.2 and 172.16.1.3) fails. The instance that I manually added the IP address to has a floating IP, and oddly enough I am able to ping DHCP on the provider network, which suggests that DHCP may be wo

Re: [Openstack] Recovering from full outage

2018-07-06 Thread George Mihaiescu
Can you manually assign an IP address to a VM and once inside, ping the address of the dhcp server? That would confirm if there is connectivity at least. Also, on the controller node where the dhcp server for that network is, check the "/var/lib/neutron/dhcp/d85c2a00-a637-4109-83f0-7c2949be4cad/l

Re: [Openstack] Recovering from full outage

2018-07-06 Thread Torin Woltjer
I have done tcpdumps on both the controllers and on a compute node. Controller: `ip netns exec qdhcp-d85c2a00-a637-4109-83f0-7c2949be4cad tcpdump -vnes0 -i ns-83d68c76-b8 port 67` `tcpdump -vnes0 -i any port 67` Compute: `tcpdump -vnes0 -i brqd85c2a00-a6 port 68` For the first command on the cont