Re: [Openstack-operators] cannot attach new volume to an instance

For what it's worth, there's a patch series that went into master and is under review for backport to Ocata that might help: https://review.openstack.org/#/q/topic:bug/1686116 Chris On 07/27/2017 12:30 PM, Ignazio Cassano wrote: The instance boots from a volume. Fails attacching a second

Re: [Openstack-operators] cannot attach new volume to an instance

On 07/27/2017 12:30 PM, Ignazio Cassano wrote: The instance boots from a volume. Fails attacching a second volume. A guy suggested to use hw_disk_bus=virtio and it works. Okay...I think this is a known issue with virtio-scsi: https://bugs.launchpad.net/nova/+bug/1702999 Chris

Re: [Openstack-operators] UDP Buffer Filling

Hi Pedro, Thank you for the suggestion. I will look into this. John Petrini Platforms Engineer // *CoreDial, LLC* // coredial.com // [image: Twitter] [image: LinkedIn] [image: Google Plus]

Re: [Openstack-operators] cannot attach new volume to an instance

The instance boots from a volume. Fails attacching a second volume. A guy suggested to use hw_disk_bus=virtio and it works. Regards Il 27/Lug/2017 05:33 PM, "Chris Friesen" ha scritto: > On 07/27/2017 08:44 AM, Ignazio Cassano wrote: > >> Hello All, >> instance

[Openstack-operators] UDP Buffer Filling

Hi List, We are running Mitaka with VLAN provider networking. We've recently encountered a problem where the UDP receive queue on instances is filling up and we begin dropping packets. Moving instances out of OpenStack onto bare metal resolves the issue completely. These instances are running

Re: [Openstack-operators] cannot attach new volume to an instance

On 07/27/2017 08:44 AM, Ignazio Cassano wrote: Hello All, instance created from images with the following metadata: hw_disk_bus=scsi hw_scsi_model=virtio-scsi do not allow to attach new volume. Deletting the above metadata in the image and creating a new instance, it allows new volume

[Openstack-operators] Correction on OS Ops Meetups team weekly IRC - 14:00 UTC official

Hi All, In my recent message about the APAC meet up in 2018 I got our regular meeting time wrong, it was officially confirmed as 14:00 UTC a few weeks back in an effort to meet more team members scheduling needs. I have updated the team wiki with the change now:

[Openstack-operators] cannot attach new volume to an instance

Hello All, instance created from images with the following metadata: hw_disk_bus=scsi hw_scsi_model=virtio-scsi do not allow to attach new volume. Deletting the above metadata in the image and creating a new instance, it allows new volume attachment. I got the same behaviour on all openstack

Re: [Openstack-operators] selection of 1st 2018 OS operators mid-cycle meet-up

Hi Chris, all I think the meeting is now on "1400"UTC weekly. The meeting is on #openstack-operators at 1500 UTC weekly. On 2017/07/26 4:15, Chris Morgan wrote: Hello All, We have a great proposal for the 1st ops meet up of 2018 to be held in Tokyo on March 7th and 8th, please see