[openstack-dev] [nova][cinder] Questions about truncked disk serial number

Hi, I meet a problem like this recently: When attaching a volume to an instance, in the xml, the disk is described as: [image: Inline image 1] where the serial number here is the volume uuid in Cinder. While inside the vm: in /dev/disk/by-id, there is a link for /vdb with the name of

Re: [openstack-dev] [nova][cinder] Questions about truncked disk serial number

Ops, forgot references: [1] https://github.com/torvalds/linux/blob/1cc15701cd89b0ce695bbc5cff3a2bf3e2efd25f/include/uapi/linux/virtio_blk.h#L54 [2] https://github.com/torvalds/linux/blob/1cc15701cd89b0ce695bbc5cff3a2bf3e2efd25f/drivers/block/virtio_blk.c#L363 On Tue, Jan 16, 2018 at 2:35 PM,

Re: [openstack-dev] [mistral] Adding Adriano Petrich to the core team

Adriano, you now have +2 vote and can approve patches :) Welcome! Thanks Renat Akhmerov @Nokia On 16 Jan 2018, 05:03 +0700, Lingxian Kong , wrote: > welcome to the team, Adriano! > > > Cheers, > Lingxian Kong (Larry) > > > On Mon, Jan 15, 2018 at 10:11 PM, Renat Akhmerov

Re: [openstack-dev] [mistral] Adding Adriano Petrich to the core team

welcome to the team, Adriano! Cheers, Lingxian Kong (Larry) On Mon, Jan 15, 2018 at 10:11 PM, Renat Akhmerov wrote: > Hi, > > I’d like to promote Adriano Petrich to the Mistral core team. Adriano has > shown the good review rate and quality at least over the last two

Re: [openstack-dev] [keystone] Stepping down from Keystone core

Boris, Thank you for all the contributions you've made to the project. I always found your reviews extremely thorough and they certainly improved the quality of our code. I'm sad to see you go, but I'm relieved to know that you're not completely leaving us :) This goes without being said, but

[openstack-dev] [keystone] Stepping down from Keystone core

Hey! I don't work on Keystone as much as I used to any more, so i'm stepping down from core reviewers. Don't expect to get rid of me though. I still work on OpenStack-related stuff and i will annoy you all in #openstack-keystone and in other IRC channels.

Re: [openstack-dev] [kuryr][os-vif][nova] os-vif 1.8.0 breaks kuryr-kubernetes

On Mon, 2018-01-15 at 17:21 +, Mooney, Sean K wrote: > > -Original Message- > > From: mdu...@redhat.com [mailto:mdu...@redhat.com] > > Sent: Monday, January 15, 2018 4:46 PM > > To: openstack-dev@lists.openstack.org > > Subject: [openstack-dev] [kuryr][os-vif][nova] os-vif 1.8.0 breaks

Re: [openstack-dev] [kuryr][os-vif][nova] os-vif 1.8.0 breaks kuryr-kubernetes

On Mon, 2018-01-15 at 12:30 -0500, Jay Pipes wrote: > On 01/15/2018 11:45 AM, mdu...@redhat.com wrote: > > Hi, > > > > os-vif commit [1] introduced a non-backward compatible change to the > > Subnet object - removal of ips field. Turns out kuryr-kubernetes were > > depending on that e.g. here [1]

Re: [openstack-dev] [all][tc] Clarifying testing recommendation for interop programs

Excerpts from Erno Kuvaja's message of 2018-01-15 12:59:44 +: > I think the worst case scenario is that we scrape together what ever > we can just to have something to say that we test it and not have > consistency nor clear responsibility of who, what and how. > (Unfortunately I think this

Re: [openstack-dev] [masakari] problems starting up masakari instance monitoring in devstack @ master

Hi Dinesh, Thanks for the info. 'recovery_method' (choose from 'auto', 'reserved_host', 'auto_priority', 'rh_priority') What should be put for Same as the segment host What should be put as , it seems it accepts any arbitrary values. Any more pointers. Much appreciated. Thank you.

Re: [openstack-dev] [pbr] support v_version

Excerpts from Gaetan's message of 2018-01-15 19:29:01 +0100: > > > > > > > I guess it somehow didn't used my build of the pbr package when > > > running in gitlab pipeline. > > > > It sounds like the CE pipeline is not building packages in the same way? > > Or is using an old version of pbr? > > >

Re: [openstack-dev] [pbr] support v_version

> > > > I guess it somehow didn't used my build of the pbr package when > > running in gitlab pipeline. > > It sounds like the CE pipeline is not building packages in the same way? > Or is using an old version of pbr? > > I guess it was the pbr version from pypi.python.org, not my customized build

Re: [openstack-dev] [kuryr][os-vif][nova] os-vif 1.8.0 breaks kuryr-kubernetes

On 01/15/2018 11:45 AM, mdu...@redhat.com wrote: Hi, os-vif commit [1] introduced a non-backward compatible change to the Subnet object - removal of ips field. Turns out kuryr-kubernetes were depending on that e.g. here [1] and we're now broken with os-vif 1.8.0. kuryr-kubernetes is saving the

[openstack-dev] [Ironic] ironic tempest plugin code has been moved to openstack/ironic-tempest-plugin/

The ironic tempest plugin code that was in openstack/ironic and openstack/ironic-inspector has been moved to openstack/ironic-tempest-plugin/ As of 10-Jan-2018 (Wednesday) the plugin code was deleted from openstack/ironic and openstack/ironic-inspector. All users of the tempest plugin code need

Re: [openstack-dev] [kuryr][os-vif][nova] os-vif 1.8.0 breaks kuryr-kubernetes

> -Original Message- > From: mdu...@redhat.com [mailto:mdu...@redhat.com] > Sent: Monday, January 15, 2018 4:46 PM > To: openstack-dev@lists.openstack.org > Subject: [openstack-dev] [kuryr][os-vif][nova] os-vif 1.8.0 breaks > kuryr-kubernetes > > Hi, > > os-vif commit [1] introduced a

Re: [openstack-dev] PTL Election Season

On Mon, Jan 15, 2018 at 5:04 PM, Kendall Nelson wrote: > Election details: https://governance.openstack.org/election/ > > Please read the stipulations and timelines for candidates and electorate > contained in this governance documentation. > > Be aware, in the PTL

[openstack-dev] PTL Election Season

Election details: https://governance.openstack.org/election/ Please read the stipulations and timelines for candidates and electorate contained in this governance documentation. Be aware, in the PTL elections if the program only has one candidate, that candidate is acclaimed and there will be no

[openstack-dev] [FEMDC] Wed. 17 Jan - IRC Meeting 15:00 UTC

Dear all, A gentle reminder for our Wednesday meeting at 15:00 UTC A draft of the 2018 agenda is available, you are very welcome to add any item. https://etherpad.openstack.org/p/massively_distributed_ircmeetings_2018 For the record, the 2017 agenda is still available here:

Re: [openstack-dev] [pbr] support v_version

Excerpts from Gaetan's message of 2018-01-15 17:29:01 +0100: > First, thanks a lot for your support and your kindness ! Really appreciate > that :) > > > > Do you know where I need to hack PBR to fix it? > > > > So 'pbr' correctly parses the prefixed tags, but it's just the output > > packages

[openstack-dev] [kuryr][os-vif][nova] os-vif 1.8.0 breaks kuryr-kubernetes

Hi, os-vif commit [1] introduced a non-backward compatible change to the Subnet object - removal of ips field. Turns out kuryr-kubernetes were depending on that e.g. here [1] and we're now broken with os-vif 1.8.0. kuryr-kubernetes is saving the VIF objects into the K8s resources annotations, so

Re: [openstack-dev] [pbr] support v_version

First, thanks a lot for your support and your kindness ! Really appreciate that :) > > Do you know where I need to hack PBR to fix it? > > So 'pbr' correctly parses the prefixed tags, but it's just the output > packages (sdists, wheels) that always unversioned? If so, this sounds > correct.

Re: [openstack-dev] [glance][oslo][requirements] oslo.serialization fails with glance

On 18-01-13 00:41:28, Matthew Thode wrote: > https://review.openstack.org/531788 is the review we are seeing it in, > but 2.22.0 failed as well. > > I'm guessing it was introduced in either > > https://github.com/openstack/oslo.serialization/commit/c1a7079c26d27a2e46cca26963d3d9aa040bdbe8 > or >

Re: [openstack-dev] [neutron-dev] [neutron] Generalized issues in the unit testing of ML2 mechanism drivers

Hello. Any comments/thoughts? This issue is generic to neutron. not specific to networking-odl. So this should be addressed as Neutron wide, and neutron and sub-project should be addressed uniformly. Thanks, On Mon, Dec 18, 2017 at 12:52:37PM +0200, Mike Kolesnik wrote: >

Re: [openstack-dev] [os-api-ref][doc] Adding openstack-doc-core to os-api-ref

On 2018-01-15 16:11, Stephen Finucane wrote: > On Thu, 2018-01-04 at 15:39 +, Stephen Finucane wrote: >> I'm not sure what the procedure for this is but here goes. >> >> I've noticed that the 'os-api-ref' project seems to have its own group >> of cores [1], many of whom are no longer working

Re: [openstack-dev] [os-api-ref][doc] Adding openstack-doc-core to os-api-ref

On Thu, 2018-01-04 at 15:39 +, Stephen Finucane wrote: > I'm not sure what the procedure for this is but here goes. > > I've noticed that the 'os-api-ref' project seems to have its own group > of cores [1], many of whom are no longer working on OpenStack (at > least, not full-time), and has a

Re: [openstack-dev] [pbr] support v_version

On Tue, 2018-01-09 at 10:25 +0100, Gaetan wrote: > Hello > > I have submitted this patch ([1]) that add support for v_version in > PBR. Basically I can tag v1.0.0 instead of 1.0.0 to release 1.0.0. > > However, after rework it appears PBR does not behaves well, even if > the unit tests pass: >

Re: [openstack-dev] [pbr] support v_version

Excerpts from Jeremy Stanley's message of 2018-01-15 14:40:14 +: > On 2018-01-09 10:25:56 +0100 (+0100), Gaetan wrote: > > I have submitted this patch ([1]) that add support for v_version > > in PBR. Basically I can tag v1.0.0 instead of 1.0.0 to release > > 1.0.0. > [...] > > Looks like the

Re: [openstack-dev] [storyboard] need help figuring out how to use auth with storyboard client

Excerpts from Adam Coldrick's message of 2018-01-15 11:26:14 +: > On Fri, 2018-01-12 at 21:30 +, Jeremy Stanley wrote: > > On 2018-01-12 15:57:44 -0500 (-0500), Doug Hellmann wrote: > > > The storyboard client docs mention an "access token" [1] as > > > something > > > a client needs in

Re: [openstack-dev] [pbr] support v_version

On 2018-01-09 10:25:56 +0100 (+0100), Gaetan wrote: > I have submitted this patch ([1]) that add support for v_version > in PBR. Basically I can tag v1.0.0 instead of 1.0.0 to release > 1.0.0. [...] Looks like the patch you linked has since merged. Any issues with it so far? > Second point, to

[openstack-dev] Notification update week 3

Hi, Here is the status update / focus settings mail for 2018 w3. Bugs [High] https://bugs.launchpad.net/nova/+bug/1742935TestServiceUpdateNotificationSample fails intermittently: u'host2' != u'host1': path: root.payload.nova_object.data.host The openstack-tox-functional (and

Re: [openstack-dev] [oslo] proposing Stephen Finucan for oslo-core

Excerpts from Doug Hellmann's message of 2018-01-08 09:55:26 -0500: > Stephen (sfinucan) has been working on pbr, oslo.config, and > oslo.policy and reviewing several of the other Oslo libraries for > a while now. His reviews are always helpful and I think he would > make a good addition to the

[openstack-dev] [monasca] RE: alarm transition events are missing in kafka queue - mysql alarm state is updated properly

Hi Yuan, please compare similar issue described in this bug report [1] and the corresponding fix [2]. As Craig explained in his comment to patch set 4, Kafka server closes idle connections after around 10 minutes, which causes first write to the topic fail. I hope it helps. Witek [1]

Re: [openstack-dev] [mistral] Adding Adriano Petrich to the core team

+1! On Mon, 15 Jan 2018 at 09:12, Renat Akhmerov wrote: > Hi, > > I’d like to promote Adriano Petrich to the Mistral core team. Adriano has > shown the good review rate and quality at least over the last two cycles > and implemented several important features

Re: [openstack-dev] [all][tc] Clarifying testing recommendation for interop programs

On Thu, Jan 11, 2018 at 4:36 PM, Colleen Murphy wrote: > Hi everyone, > > We have governance review under debate[1] that we need the community's help > on. > The debate is over what recommendation the TC should make to the Interop team > on where the tests it uses for the

Re: [openstack-dev] Retirement of astara repos?

On 2018-01-11 22:55, Mark McClain wrote: > Sean, Andreas- > > Sorry I missed Andres’ message earlier in December about retiring astara. > Everyone is correct that development stopped a good while ago. We attempted > in Barcelona to find others in the community to take over the day-to-day >

Re: [openstack-dev] [storyboard] need help figuring out how to use auth with storyboard client

On Fri, 2018-01-12 at 21:30 +, Jeremy Stanley wrote: > On 2018-01-12 15:57:44 -0500 (-0500), Doug Hellmann wrote: > > The storyboard client docs mention an "access token" [1] as > > something > > a client needs in order to create stories and make other sorts of > > changes.  They don't explain

Re: [openstack-dev] [tc][ptl][goals][storyboard] tracking the rocky goals with storyboard

Emilien Macchi wrote: > On Fri, Jan 12, 2018 at 12:37 PM, Doug Hellmann wrote: >> [...] >> How does this sound as an approach? Does anyone have any reservations >> about using storyboard this way? > > Sounds like a good idea, and will help to "Eat Our Own Dog Food" (if >

Re: [openstack-dev] [tripleO] quickstart with containers deployment failed

On Sun, Jan 14, 2018 at 7:46 AM, Moshe Levi wrote: > Hi, > > > > We are trying to add container support ovs hw offload. > > We were able to do the deployment a few weeks ago, but now we getting an > errors . > > Jan 14 07:14:32 localhost os-collect-config: "2018-01-14

[openstack-dev] [mistral] Adding Adriano Petrich to the core team

Hi, I’d like to promote Adriano Petrich to the Mistral core team. Adriano has shown the good review rate and quality at least over the last two cycles and implemented several important features (including new useful YAQL/JINJA functions). Please vote whether you agree to add Adriano to the