Re: [Openstack-operators] Best kernel options for openvswitch on network nodes on a large setup

Thank you, I will try it next week (since today is Friday) and update this thread if it has fixed my issues. We are indeed using the latest RDO Pike, so ovsdbapp 0.4.3.1 . Jean-Philippe Méthot Openstack system administrator Administrateur système Openstack PlanetHoster inc. > Le 28 s

Re: [Openstack-operators] Best kernel options for openvswitch on network nodes on a large setup

r, I don’t think it’s max open file since the number of open files is nowhere close to what I’ve set it. Ideas? Jean-Philippe Méthot Openstack system administrator Administrateur système Openstack PlanetHoster inc. > Le 26 sept. 2018 à 15:16, Jean-Philippe Méthot > a écrit : >

Re: [Openstack-operators] Best kernel options for openvswitch on network nodes on a large setup

constantly under load. Jean-Philippe Méthot Openstack system administrator Administrateur système Openstack PlanetHoster inc. > Le 26 sept. 2018 à 11:48, Simon Leinen a écrit : > > Jean-Philippe Méthot writes: >> This particular message makes it sound as if openvswitch is getting

Re: [Openstack-operators] Best kernel options for openvswitch on network nodes on a large setup

almost instantly though. I’ve done some research about that particular message, but it didn’t give me anything I can use to fix it. Jean-Philippe Méthot Openstack system administrator Administrateur système Openstack PlanetHoster inc. > Le 25 sept. 2018 à 19:37, Erik McCormick a éc

[Openstack-operators] Best kernel options for openvswitch on network nodes on a large setup

and thus minimize the impact of such an attack, or whatever it was. Best regards, Jean-Philippe Méthot Openstack system administrator Administrateur système Openstack PlanetHoster inc. ___ OpenStack-operators mailing list OpenStack-operators

[Openstack-operators] Network metadata+userdata and rate limits

receive metadata? We currently use Pike on centos 7. Jean-Philippe Méthot Openstack system administrator Administrateur système Openstack PlanetHoster inc. ___ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http

[Openstack-operators] Cinder-volume and high availability

. In such a configuration, would I still need to have only one cinder-volume service running at a time? Also, the backend is a Dell compellent SAN, if that makes a difference. Jean-Philippe Méthot Openstack system administrator Administrateur système Openstack PlanetHoster inc

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

their block device. I know this issue doesn’t happen on Ceph, so I’ve been wondering, is this a limitation of Openstack or the SAN driver? Also, is there actually a way to reach even active-passive high availability with this current storage solution? Jean-Philippe Méthot Openstack system

Re: [Openstack-operators] New project creation fails because of a Nova check in a multi-region cloud

> Le 11 mai 2018 à 08:36, Matt Riedemann <mriede...@gmail.com> a écrit : > > On 5/10/2018 6:30 PM, Jean-Philippe Méthot wrote: >> 1.I was talking about the region-name parameter underneath >> keystone_authtoken. That is in the pike doc you linked, but I am unawa

Re: [Openstack-operators] New project creation fails because of a Nova check in a multi-region cloud

>> >>> I currently operate a multi-region cloud split between 2 geographic >>> locations. I have updated it to Pike not too long ago, but I've been >>> running into a peculiar issue. Ever since the Pike release, Nova now >>> asks Keystone if a new project exists in Keystone before configuring

[Openstack-operators] New project creation fails because of a Nova check in a multi-region cloud

the code for the Nova check) Jean-Philippe Méthot Openstack system administrator Administrateur système Openstack PlanetHoster inc. ___ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman

Re: [Openstack-operators] Strange behaviour change in cinder with a Dell compellent backend

that was in-use previously. That was my main concern and now it does make the process of fixing this simpler. Jean-Philippe Méthot Openstack system administrator Administrateur système Openstack PlanetHoster inc. > Le 25 avr. 2018 à 00:22, Sean McGinnis <sean.mcgin...@gmx.com> a écrit :

[Openstack-operators] Strange behaviour change in cinder with a Dell compellent backend

in the SAN has changed? Jean-Philippe Méthot Openstack system administrator Administrateur système Openstack PlanetHoster inc. ___ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman

Re: [Openstack-operators] Inverted drive letters on block devices that use virtio-scsi

or migration. Probably better to wait before I start converting my multi-disk instances to virtio-scsi. If I am not mistaken, this should also be an issue in Pike and master, right? Jean-Philippe Méthot Openstack system administrator Administrateur système Openstack PlanetHoster inc. > Le 26 janv. 2

Re: [Openstack-operators] Inverted drive letters on block devices that use virtio-scsi

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. <lo...@protiumit.com> a écrit : > > https://bugs.launchpad.net/nova/+bug/17

[Openstack-operators] Inverted drive letters on block devices that use virtio-scsi

Hi, Lately, we’ve been converting our VMs block devices (cinder block devices) to use the virtio-scsi driver instead of virtio-blk by modifying the database. This works great, however, we’ve run into an issue with an instance that has more than one drive. Essentially, the root device has

[Openstack-operators] Converting existing instances from virtio-blk to virtio-scsi

this in the openstack database? What parameters would I need to change? Is there an easier, less likely to break everything way? Jean-Philippe Méthot Openstack system administrator Administrateur système Openstack PlanetHoster inc. ___ OpenStack-operators mailing

[Openstack-operators] Best practice against DDoS on openstack

configuration to reduce the impact of a DDoS on the whole compute node and thus, prevent it from going down? I understand that increasing the size of the conntrack table is one, but outside of that? Best regards, Jean-Philippe Méthot Openstack system administrator Administrateur système Openstack