Re: [Openstack-operators] [Openstack] Recovering from full outage

Hi, that could be a problem with neutron metadata service, check the logs. Have you considered that the outage might have corrupted your databases, neutron, nova, etc? BR On Thu, Jul 5, 2018 at 9:07 PM Torin Woltjer wrote: > Are IP addresses set by cloud-init on boot? I noticed that cloud-ini

[Openstack-operators] Storage concerns when switching from a single controller to a HA setup

Hi, We’ve been running on Openstack for several years now and our setup has always counted a single controller. We are currently testing switching to a dual controller HA solution, but an unexpected issue has appeared, regarding storage. See, we use Dell compellent SAN for our block devices. I

Re: [Openstack-operators] [openstack-dev] [Openstack] [nova][api] Novaclient redirect endpoint https into http

On 07/05/2018 01:55 PM, melanie witt wrote: +openstack-dev@ On Wed, 4 Jul 2018 14:50:26 +, Bogdan Katynski wrote: But, I can not use nova command, endpoint nova have been redirected from https to http. Here:http://prntscr.com/k2e8s6  (command: nova –insecure service list) First of all, it

Re: [Openstack-operators] [Openstack] Recovering from full outage

Are IP addresses set by cloud-init on boot? I noticed that cloud-init isn't working on my VMs. created a new instance from an ubuntu 18.04 image to test with, the hostname was not set to the name of the instance and could not login as users I had specified in the configuration. Torin Woltjer G

Re: [Openstack-operators] [Openstack] [nova][api] Novaclient redirect endpoint https into http

+openstack-dev@ On Wed, 4 Jul 2018 14:50:26 +, Bogdan Katynski wrote: But, I can not use nova command, endpoint nova have been redirected from https to http. Here:http://prntscr.com/k2e8s6 (command: nova –insecure service list) First of all, it seems that the nova client is hitting /v2.1

Re: [Openstack-operators] [Openstack] Recovering from full outage

You should tcpdump inside the qdhcp namespace to see if the requests make it there, and also check iptables rules on the compute nodes for the return traffic. On Thu, Jul 5, 2018 at 12:39 PM, Torin Woltjer wrote: > Yes, I've done this. The VMs hang for awhile waiting for DHCP and > eventually c

Re: [Openstack-operators] [Openstack] Recovering from full outage

Yes, I've done this. The VMs hang for awhile waiting for DHCP and eventually come up with no addresses. neutron-dhcp-agent has been restarted on both controllers. The qdhcp netns's were all present; I stopped the service, removed the qdhcp netns's, noted the dhcp agents show offline by `neutron

Re: [Openstack-operators] [Openstack] Recovering from full outage

The qrouter netns appears once the lock_path is specified, the neutron router is pingable as well. However, instances are not pingable. If I log in via console, the instances have not been given IP addresses, if I manually give them an address and route they are pingable and seem to work. So the

Re: [Openstack-operators] [Openstack] Recovering from full outage

There is no lock path set in my neutron configuration. Does it ultimately matter what it is set to as long as it is consistent? Does it need to be set on compute nodes as well as controllers? Torin Woltjer Grand Dial Communications - A ZK Tech Inc. Company 616.776.1066 ext. 2006 www.granddial.

Re: [Openstack-operators] [openstack-dev] [publiccloud-wg] Meeting this afternoon for Public Cloud WG

Sorry guys, I'm not available once again. See you next time. Jean-Daniel Bonnetot ovh.com | @pilgrimstack On 05/07/2018 09:59, "Tobias Rydberg" wrote: Hi folks, Time for a new meeting for the Public Cloud WG. Agenda draft can be found at https://etherpad.op

[Openstack-operators] [publiccloud-wg] Meeting this afternoon for Public Cloud WG

Hi folks, Time for a new meeting for the Public Cloud WG. Agenda draft can be found at https://etherpad.openstack.org/p/publiccloud-wg, feel free to add items to that list. See you all at IRC 1400 UTC in #openstack-publiccloud Cheers, Tobias -- Tobias Rydberg Senior Developer Twitter & IRC: