Hi,
I’ve noticed that in the high-availability guide, it is not recommended to run
cinder-volume in an active-active configuration. However, I have built an
active-passive setup that uses keepalived and a virtual IP to redirect API
traffic to only one controller at a time. In such a
Thanks Amy... I ll do that and post the result
Cheers
On Thu, Jul 12, 2018 at 4:42 PM Amy Marrich wrote:
> Alfredo,
>
> I've added the operators list but in Newton you should be able to use the
> OpenStack CLI for this as well. Checkout 'openstack server backup create
> --help' if you get an
Hi Melvin. Thanks for that. Anyway I was able to install the packages with
the repo.
Cheers
On Wed, Jul 11, 2018 at 1:16 AM Melvin Hillsman
wrote:
> May I suggest install python-pip and then pip install python-swiftclient
> (python-openstackclient, python-whateverclient, etc at that point)
>
Checking iptables for the metadata-proxy inside of qrouter provides the
following:
$ip netns exec qrouter-80c3bc40-b49c-446a-926f-99811adc0c5e iptables-save -c |
grep 169
[0:0] -A neutron-l3-agent-PREROUTING -d 169.254.169.254/32 -i qr-+ -p tcp -m
tcp --dport 80 -j REDIRECT --to-ports 9697
Alfredo,
I've added the operators list but in Newton you should be able to use the
OpenStack CLI for this as well. Checkout 'openstack server backup create
--help' if you get an error again add --debug to the end to get some more
information to troubleshoot.
Thanks,
Amy (spotz)
On Thu, Jul 12,
You might want to try giving the neutron-dhcp and metadata agents a restart.
___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
I tested this on two instances. The first instance has existed since before I
began having this issue. The second is created from a cirros test image.
On the first instance:
The route exists: 169.254.169.254 via 172.16.1.1 dev ens3 proto dhcp metric 100.
curl returns information, for example;
Are you instances receiving a route to the metadata service
(169.254.169.254) from DHCP? Can you curl the endpoint? curl
http://169.254.169.254/latest/meta-data
___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
