uld it be as easy
> as changing the drive order in the database?
>
>
> Jean-Philippe Méthot
> Openstack system administrator
> Administrateur système Openstack
> PlanetHoster inc.
>
>
>
>
> Le 26 janv. 2018 à 13:06, Logan V.
If you are running Ocata or later, please see
https://bugs.launchpad.net/nova/+bug/1729584
There seems to be a broken series of patches related to virtio-scsi
that were backported to Ocata resulting in some unresolved virtio-scsi
drive ordering bugs. I see it primarily on virtio-scsi based instanc
We upgraded our control plane to 4.4.0-109 + intel-microcode
3.20180108.0~ubuntu16.04.2 several days ago, and are about 1/2 of the
way thru upgrading our compute hosts with these changes. We use Ocata
for all services, and no issue like this has been observed yet on our
env. Control hosts are E5-26
Hello,
Yes openstack-ansible does support deploying keepalived along with
haproxy. The keepalived role is run just before the haproxy role in
this playbook:
https://github.com/openstack/openstack-ansible/blob/master/playbooks/haproxy-install.yml#L27-L31
You can see an example keepalived configur
I think this actually started in Newton. Yes it ships blank, however
there is still a default policy implemented as before with similar
defaults separating the admin and user roles. The default policy is
implemented in the nova code base
(https://github.com/openstack/nova/tree/stable/newton/nova/po
It is also possible to use oslo_middleware ssl filter in your API paste
file with cinder like:
[filter:ssl]
paste.filter_factory = oslo_middleware.ssl:SSLMiddleware.factory
[pipeline:apiversions]
pipeline = ssl faultwrap osvolumeversionapp
On Wed, Feb 22, 2017 at 2:54 PM Mathieu Gagné wrote:
>
Hi Andreas,
Thanks for reporting this. I just pushed a patch to resolve this here
https://review.openstack.org/#/c/431110/. If you are able to start
with a fresh environment this should resolve the issue. The unbound
service should only be installed in the containers, not the hosts, so
that was th
Have been using it since kilo. It was a clean pick into Liberty and worked
great for me.
Logan
On Friday, September 2, 2016, Saverio Proto wrote:
> Hello,
>
> this is merged upstream in Mitaka:
>
> https://review.openstack.org/#/c/287954/
>
> anyone already did a cherry pick in Liberty and is r
I recently needed to do this for a very limited number of volumes, so
I used this manual process:
-deattach the old volume from instance
-prep a volume in the new instance of the same size
- rbd mv pool/volume-$NEW_UUID pool/volume-$NEW_UUID-delete
- rbd mv pool/volume-$OLD_UUID pool/volume-$NEW_U
