[openstack-dev] [Fuel] Changing APIs and API versioning

Hi folks, I’d like to touch the aspect of Fuel development process that seems to be as wrong as possible. That aspect is how we change the API. The issue is that in Fuel anyone can change API at any point of time without even warning the rest of the same component’s team. Relying on this kind

Re: [openstack-dev] [nova-compute][nova][libvirt] Extending Nova-Compute for image prefetching

Lingxian Kong wrote on 10/21/2015 06:44:27 AM: > From: Lingxian Kong > To: "OpenStack Development Mailing List (not for usage questions)" > > Date: 10/21/2015 06:44 AM > Subject: Re: [openstack-dev]

Re: [openstack-dev] [rally] Rally boot tests fails with Error Forbidden: It is not allowed to create an interface on external networks

Thanks Yair, I will dig into this more. I did try the "network" context, but same error. regards Behzad On Tue, Oct 20, 2015 at 12:53 PM, Yair Fried wrote: > > > On Tue, Oct 20, 2015 at 8:39 PM, Behzad Dastur > wrote: > >> Hi Yair, >> The rally

[openstack-dev] [puppet] Incompatible default parameters

Greetings, I'd like to discuss bug 1506061 ([1]). The main problem I'm trying to solve here is that using default parameters of classes cinder::api and nova::keystone::auth migration won't work, because Cinder will search for endpoint with different name ('Compute service' instead of

Re: [openstack-dev] [Ceilometer] Meeting cancelled for this week

thanks Ildiko it's also safe to assume the meeting will be cancelled for October 29 and November 5. please use the mailing list (it's actually preferred) for any discussion items. On 21/10/2015 8:22 AM, Ildikó Váncsa wrote: Hi All, I would like to inform you that we cancel the Ceilometer

Re: [openstack-dev] [neutron][sriov] SRIOV-VM could not work well with normal VM

> -Original Message- > From: yujie [mailto:judy_yu...@126.com] > Sent: Tuesday, October 20, 2015 5:34 AM > To: Moshe Levi > Cc: OpenStack Development Mailing List (not for usage questions) > > Subject: Re: [openstack-dev]

[openstack-dev] [Neutron][Kuryr] IRC Meeting - Canceled for next week (10/26)

Hello Everyone, Just wanted to share with anyone that wasn't in the meeting this week, that we decided to cancel the IRC meeting on the 10/26. See you all in the summit. Gal. __ OpenStack Development Mailing List (not for

Re: [openstack-dev] [puppet] Incompatible default parameters

This change [1] introduced the nova_catalog_info and nova_catalog_admin_info parameters. Martin Mágr also mentioned that default values were wrong but the change got merged anyway. I agree that those default values should be changed to "nova" like initially suggested as the 2nd field is the

[openstack-dev] [Monasca] Congress + Monasca Meeting

Guys, We have half slot on Wed 3:40 with the Congress folks: https://wiki.openstack.org/wiki/Design_Summit/Mitaka/Etherpads#Congress These are the topics I proposed: 1. how to integrate Monasca with Congress so then Monasca can provide metrics, logs and event data for policy

Re: [openstack-dev] [puppet] Incompatible default parameters

I think the only people that would be affected by the puppet-openstack module default not matching the keystone default are people that are trying to retrofit puppet into an already running environment. Those people already have a ton of work laid out in front of them, so I’m ok with making it

[openstack-dev] [release] release freeze until after the summit

The release management team is going to hold off on releasing anything else until at least Nov 2, unless there's an emergency, so we can focus on summit-related preparation and activities. Doug __ OpenStack Development

Re: [openstack-dev] [Fuel] [CI] Running fuelclient tests against review requests for fuel-web repo

Sergii, Let's move this discussion to the thread "[Fuel] Changing APIs and API versioning". We need to have this mechanism regardless of our decision on API versioning. 2015-10-21 20:31 GMT+07:00 Sergii Golovatiuk : > Vitaliy, > > Why do merge API changes without: > >

[openstack-dev] [NFV][Telco] FYI telcowg-usecases is now in the openstack/ namespace on git.openstack.org

Hi all, Just an FYI as I had some questions about this, pursuant to a notice James sent out in August [1] the repository has moved from the stackforge/ namespace in git to the openstack/ namespace. Open reviews can now be found here:

Re: [openstack-dev] [Fuel] [CI] Running fuelclient tests against review requests for fuel-web repo

Sergii, 1. We only have auto-doc for developers which should be changed automatically. 2. We do not have proper API versioning. We didn't decide yet how to resolve it. Let's discuss versioning in "[Fuel] Changing APIs and API versioning" thread. Aleksey Kasatkin On Wed, Oct 21, 2015 at 5:26

Re: [openstack-dev] [infra] Upgrade to Gerrit 2.11

On 2015-10-21 10:18:31 -0400 (-0400), Anita Kuno wrote: [...] > If folks are willing to help build Gerrit v3, that is wonderful. > If you would like to talk to Khai on how to get started > contributing to Gerrit, I'm going out on a limb here and will > guess he will be supportive of your efforts.

[openstack-dev] [Fuel] [Puppet] Potential critical issue, due Puppet mix stderr and stdout while execute commands

Hi, guys! Now I observe potential-dangerous situation in the providers of puppet-neutron module. I want share details, because not only puppet-neutron module may be broken by warnings from Openstack CLI utilities. After updating urllib3 library on my lab, commands like 'neutron net list' began

Re: [openstack-dev] [Neutron] HenryG addition to the Neutron Drivers team

Well deserved Henry! Edgar From: "Armando M." > Reply-To: "OpenStack Development Mailing List (not for usage questions)" > Date: Tuesday, October 20, 2015 at 8:14 PM To:

Re: [openstack-dev] [Fuel] [CI] Running fuelclient tests against review requests for fuel-web repo

Vitaliy, Why do merge API changes without: 1. Fixing documentation? 2. bumping API version? -- Best regards, Sergii Golovatiuk, Skype #golserge IRC #holser On Wed, Oct 21, 2015 at 3:08 PM, Vitaly Kramskikh wrote: > Hi, > > It's yet another time we broke fuelclient

Re: [openstack-dev] [infra] Upgrade to Gerrit 2.11

On 10/21/2015 08:37 AM, Markus Zoeller wrote: > "Daniel P. Berrange" wrote on 10/21/2015 11:29:50 > AM: > >> From: "Daniel P. Berrange" >> To: "OpenStack Development Mailing List (not for usage questions)" >> >>

Re: [openstack-dev] [Fuel] Changing APIs and API versioning

JFYI: (re-)start of this discussion was instigated by merge of this change (and here is revert ). And this is actually not the first time when we make backward incompatible changes in our API. AFAIR, the last

[openstack-dev] [Ironic] BIOS Configuration

Hi all, I am interested in remote BIOS configuration. There is "New driver interface for BIOS configuration specification" https://review.openstack.org/#/c/209612/ Is it possible to implement this without REST API endpoint? It would be great to access and configure the stuff without any

Re: [openstack-dev] [security] The first version of the Logo for Openstack Security Project

I had looped some people into a previous version of the thread but they've not replied yet. I think we ran into this problem before and got a firm "maybe, depending on what it is" from the powers-that-be. Perhaps we should look at a rough-draft alternative logo while we await a verdict? >

Re: [openstack-dev] [Neutron] Gerrit permissions and Merge rights

On Wed, Oct 21, 2015 at 7:37 PM, Armando M. wrote: > > > On 21 October 2015 at 04:12, Gal Sagie wrote: > >> Do we also want to consider Project Kuryr part of this? >> > > No, why would we? > [Gal] Because Kuryr is a special project which was created in

Re: [openstack-dev] [release] establishing release liaisons for mitaka

Excerpts from Lingxian Kong's message of 2015-10-21 16:42:32 +0800: > Hi, Doug, > > After conversition with Mistral PTL(Renat), I'm willing to be mistral > liaison to take participate in cross-project release effort on beharf > of mistral team, so please count me in. Great, thank you for

Re: [openstack-dev] [Fuel] [CI] Running fuelclient tests against review requests for fuel-web repo

Hi, Vitaly, there is nothing to prevent us from triggering test based on event in one project but checking out the code from another. So you can setup job triggered for patchset-created event in commit to fuel-web/ repo. Then in this job you checkout both: code from fuel-web and code from

Re: [openstack-dev] [ceilometer][aodh] proposal to add Ryota Mibu to Aodh core

thanks for the feedback folks. i'd like to welcome Ryota to the Aodh core team. thank you for all the continued effort in building alarming functionality in OpenStack! On 16/10/2015 8:59 AM, gord chung wrote: sorry, as we usually do, please comment on gerrit[1]. if you cannot, then please

Re: [openstack-dev] [Magnum] Coe components status

Vikas, Could you clarify what do you mean under ’status’? I don’t seed this command in kubectl, so I assume it is get or describe? Also for Docker, is it info, inspect or stats? We can get app/container details through Marathon API in Mesos, but it’s very depend what information we are looking

Re: [openstack-dev] [rally] Rally boot tests fails with Error Forbidden: It is not allowed to create an interface on external networks

Behzad, please run rally task start with `--debug' option and then provide us with some details (traceback, etc) about this error. Also Yair suggested to put `"auto_assign_nic": true' into scenario config - that is good idea. Get rid of `use_floatingip' - this parameter is not used for this

Re: [openstack-dev] [security] The first version of the Logo for Openstack Security Project

On 10/21/2015 03:54 AM, Michael Xin wrote: Hi, guys: Thanks for your help. We are designing a logo and a flyer for Openstack Security Project. Rachel helped us with the task. Attached is her first version of the logo. Please let us know your feedback.

Re: [openstack-dev] [Neutron] Gerrit permissions and Merge rights

On 21 October 2015 at 04:12, Gal Sagie wrote: > Do we also want to consider Project Kuryr part of this? > No, why would we? > We already started sending Kuryr spec to the Neutron repository and I > think it would make sense to manage it > as part of Neutron spec process.

Re: [openstack-dev] [Neutron] HenryG addition to the Neutron Drivers team

On 21 October 2015 at 02:01, Ihar Hrachyshka wrote: > > > On 21 Oct 2015, at 05:14, Armando M. wrote: > > > > Hi folks, > > > > Henry has been instrumental in many areas of the projects and his crazy > working hours makes even Kevin and I bow in awe. > >

Re: [openstack-dev] [ironic] [horizon] ironic panels

On 21/10/2015 01:48, Jim Rollenhagen wrote: On Tue, Oct 20, 2015 at 04:50:04PM +0100, Beth Elwell wrote: Hi Jim, I have replied inline to your comments below: On 19/10/2015 19:38, Jim Rollenhagen wrote: On Mon, Oct 19, 2015 at 07:05:04PM +0100, Beth Elwell wrote: Hi all, I am currently

Re: [openstack-dev] [Neutron] Gerrit permissions and Merge rights

On Wed, Oct 21, 2015 at 11:37 AM, Armando M. wrote: > > > On 21 October 2015 at 04:12, Gal Sagie wrote: > >> Do we also want to consider Project Kuryr part of this? >> > > No, why would we? > > The reason to consider it is because Kuryr is a sub-project

Re: [openstack-dev] [Fuel] [Puppet] Potential critical issue, due Puppet mix stderr and stdout while execute commands

I spoken with Sergii about this and prepared a patch for get rid of SecurityWarning [0] - it was easy. But we can't get rid from InsecurePlatformWarning so easy way. I see next options: 1. Update python version as [1] said - should be hard task 2. Downgrade urllib version to one without such

Re: [openstack-dev] [Neutron] Gerrit permissions and Merge rights

On 21 October 2015 at 10:29, Kyle Mestery wrote: > On Wed, Oct 21, 2015 at 12:08 PM, Armando M. wrote: > >> >> >> On 21 October 2015 at 09:53, Kyle Mestery wrote: >> >>> On Wed, Oct 21, 2015 at 11:37 AM, Armando M.

[openstack-dev] [cinder] No meeting Oct 28th

It seems someone always asks during the Summit, so this is an attempt to make sure it is known. Due to the Design Summit taking place next week, Cinder will not be holding its regular Wednesday meeting. We will resume normal meetings the following week. Thanks! Sean McGinnis (smcginnis)

Re: [openstack-dev] [Neutron] Gerrit permissions and Merge rights

On Wed, Oct 21, 2015 at 12:34 PM, Armando M. wrote: > > > On 21 October 2015 at 10:29, Kyle Mestery wrote: > >> On Wed, Oct 21, 2015 at 12:08 PM, Armando M. wrote: >> >>> >>> >>> On 21 October 2015 at 09:53, Kyle Mestery

Re: [openstack-dev] [nova] Change from Mitaka: Expected UNIX signal to generate Guru Meditation (error) Reports

Sean, If you are using the GMR code from oslo-incubator, please switch over to the new oslo.service. I don't see any pending reviews. Thanks, -- Dims On Wed, Oct 21, 2015 at 1:29 PM, Sean McGinnis wrote: > On Wed, Oct 21, 2015 at 02:43:39PM +0200, Kashyap Chamarthy

Re: [openstack-dev] [Neutron] Gerrit permissions and Merge rights

On Wed, Oct 21, 2015 at 12:08 PM, Armando M. wrote: > > > On 21 October 2015 at 09:53, Kyle Mestery wrote: > >> On Wed, Oct 21, 2015 at 11:37 AM, Armando M. wrote: >> >>> >>> >>> On 21 October 2015 at 04:12, Gal Sagie

[openstack-dev] AUTO: Alon Marx is out of the office (returning 11/02/2015)

I am out of the office until 11/02/2015. I will be available occasionally on email. For any urgent matters please contact Ohad Atia. Note: This is an automated response to your message "OpenStack-dev Digest, Vol 42, Issue 56" sent on 10/21/15 5:10:27 AM. This is the only notification you

[openstack-dev] [Nova][Cinder] Multi-attach volume help needed

Hi Folks, The work has been ongoing for a while now to implement the feature to support attaching a single volume to multiple VM instances. This work impacts both Nova and Cinder. We are in quite good shape with the implementation, but it is still far for completion and we temporarily ran out

Re: [openstack-dev] openstack-barbican-authenticate-keystone-barbican-command

On Wed, Oct 21, 2015 at 6:26 AM, Dave McCowan (dmccowan) wrote: > Hi Arif-- > Are you using Keystone for authentication? > If so, you need to get an authentication token from Keystone and add > it as a header to your curl command: -H "X-Auth-Token:*$TOKEN*". >

Re: [openstack-dev] [Neutron] Gerrit permissions and Merge rights

On 21 October 2015 at 09:53, Kyle Mestery wrote: > On Wed, Oct 21, 2015 at 11:37 AM, Armando M. wrote: > >> >> >> On 21 October 2015 at 04:12, Gal Sagie wrote: >> >>> Do we also want to consider Project Kuryr part of this? >>> >> >>

Re: [openstack-dev] [Neutron] Gerrit permissions and Merge rights

On 21 October 2015 at 09:52, Gal Sagie wrote: > > > On Wed, Oct 21, 2015 at 7:37 PM, Armando M. wrote: > >> >> >> On 21 October 2015 at 04:12, Gal Sagie wrote: >> >>> Do we also want to consider Project Kuryr part of this? >>> >> >>

[openstack-dev] [Neutron][networking-sfc] no IRC project meeting for service function chaining project this week and next week

Hi, Since most of us are very busy with presentation preparation for the Summit, let's cancel this week's project meeting. We will resume the meeting on 11/5. Thanks, Cathy __ OpenStack Development Mailing List (not for

Re: [openstack-dev] [Fuel] [CI] Running fuelclient tests against review requests for fuel-web repo

Can we do it in OpenStack Infra.. ? On Wed, Oct 21, 2015 at 9:27 AM Aleksandra Fedorova wrote: > Hi, Vitaly, > > there is nothing to prevent us from triggering test based on event in > one project but checking out the code from another. > > So you can setup job triggered

Re: [openstack-dev] [release] establishing release liaisons for mitaka

Doug, I updated the liaisons for Trove on the wiki page. Thanks, -Craig On Wed, Oct 21, 2015 at 11:26 AM Doug Hellmann wrote: > Excerpts from Lingxian Kong's message of 2015-10-21 16:42:32 +0800: > > Hi, Doug, > > > > After conversition with Mistral PTL(Renat), I'm

Re: [openstack-dev] [Fuel][QA][Plugins] Move functional tests from fuel-qa to the plugins

We should fix it everyone. I don't think we need to be too heavy with the process, so I'd just update a single bug vs creating so many bugs... Fuel Infra team - please provide an estimate when script is going to be ready (which adds people automatically to gerrit review). Thanks, On Wed, Oct

[openstack-dev] [cinder] meeting place for event Monday night in Tokyo ...

All, As has been our custom during previous summits, the Cinder team would will be getting together for dinner and drinks on Monday night (11/26) at the Tokyo Summit. Not sure where the evening will take us, but we are planning to meet by registration at the Convention Center. Looking at

[openstack-dev] [ironic] Ironic design summit schedule

Hi Jim, My techtalk is supposed to finish by 2:45pm. However, techtalk schedule is not as well monitored as formal sessions so it could get delayed. That's why I was exploring whether the group management session can be switched to Thursday. Thanks! Wanyen >>* Hi Jim, *> >* Is it possible

Re: [openstack-dev] [cinder] meeting place for event Monday night in Tokyo ...

On 10/21/2015 05:04 PM, Jay S. Bryant wrote: > > > On 10/21/2015 04:00 PM, Anita Kuno wrote: >> On 10/21/2015 04:54 PM, Jay S. Bryant wrote: >>> All, >>> >>> As has been our custom during previous summits, the Cinder team would >>> will be getting together for dinner and drinks on Monday night

[openstack-dev] [Trove] Mitaka Design Summit Sessions

We've updated the Trove Sessions to include some great topics. https://wiki.openstack.org/wiki/Design_Summit/Mitaka/Etherpads#Trove http://mitakadesignsummit.sched.org/overview/type/trove Thanks to everyone involved and looking forward to seeing everyone next week! -Craig Vyvial (cp16net)

Re: [openstack-dev] [cinder] meeting place for event Monday night in Tokyo ...

On 10/21/2015 04:54 PM, Jay S. Bryant wrote: > All, > > As has been our custom during previous summits, the Cinder team would > will be getting together for dinner and drinks on Monday night (11/26) > at the Tokyo Summit. > > Not sure where the evening will take us, but we are planning to meet

Re: [openstack-dev] [security] The first version of the Logo for Openstack Security Project

On 10/21/2015 05:11 PM, Michael Xin wrote: Rob and Michael: Thanks for the update. We will probably not use any Openstack Logo. Here is the first draft of the flyer: http://5a6aa6580e900b8e8020-e5e45c5cb10329ebc9fb69948bb1b1a5.r65.cf1.rackcdn.com/ossp-flag-flyer.pdf Please send us your

Re: [openstack-dev] [nova] Change from Mitaka: Expected UNIX signal to generate Guru Meditation (error) Reports

On Wed, Oct 21, 2015 at 01:58:46PM -0400, Davanum Srinivas wrote: > Sean, > > If you are using the GMR code from oslo-incubator, please switch over to > the new oslo.service. I don't see any pending reviews. > > Thanks, > -- Dims Thanks Dims. I remembered the initial patch from May that added

Re: [openstack-dev] [Nova] Migration state machine proposal.

Question on some things seen in the below paste. What is with 'finished' -> 'reverted' and 'finished' -> 'confirmed'? Why does it jump over 'reverting' or 'confirming'? Should it? The other question is the difference between 'failed' and 'error' in the first diagram, any idea on why/how these

Re: [openstack-dev] Custom Nova scheduler based on CPU queue length (Clint Byrum)

ot for usage questions) > >>>>>> Unsubscribe: > >>>>>> openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > >>>>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > >>>>>> > &

Re: [openstack-dev] [security] The first version of the Logo for Openstack Security Project

Wow, that looks amazing. It's pretty late my time so I'll take a closer look at the text tomorrow but the overall look and style is superb! Thank you for all the effort that's gone into this! > -Original Message- > From: Michael Xin [mailto:michael@rackspace.com] > Sent: 21

[openstack-dev] [fuel] Tests and feedback needed: Fuel ISO with Liberty support

All, In case you've missed the announcement from Alexandra [0], Fuel now supports OpenStack Liberty, and the nightly ISO images [1] are passing our Build Verification Test [2]. [0] http://lists.openstack.org/pipermail/openstack-dev/2015-October/077309.html [1] https://ci.fuel-infra.org/ [2]

Re: [openstack-dev] [cinder] meeting place for event Monday night in Tokyo ...

On 10/21/2015 04:00 PM, Anita Kuno wrote: On 10/21/2015 04:54 PM, Jay S. Bryant wrote: All, As has been our custom during previous summits, the Cinder team would will be getting together for dinner and drinks on Monday night (11/26) at the Tokyo Summit. Not sure where the evening will take

Re: [openstack-dev] [security] The first version of the Logo for Openstack Security Project

Rob and Michael: Thanks for the update. We will probably not use any Openstack Logo. Here is the first draft of the flyer: http://5a6aa6580e900b8e8020-e5e45c5cb10329ebc9fb69948bb1b1a5.r65.cf1.rackcdn.com/ossp-flag-flyer.pdf Please send us your feedback. Yours, Michael On 10/21/15,

[openstack-dev] [kolla] Integrating kollacli as python-kollaclient

Hello Folks, Oracle has developed a CLI tool for managing OpenStack Kolla clusters. Several months ago at our midcycle, the topic was brought up an I suggested to go ahead and get started on the work. We clearly didn't spend enough time discussing how it should be integrated into the code

[openstack-dev] [Ironic] Driver documentation in Ironic

As mentioned in the weekly IRC, 3rd-party vendor drivers are ranked lower priority and therefore their code tend to merge at the late cycle of a release. Therefore, it leads little time for driver author to submit document and for upstream to review and approve the document. So, as the result,

[openstack-dev] [Neutron][Nova] Trunk port feature (VLAN aware VMs)

Hi Folks, During Liberty we started the implementation of the VLAN aware VMs blueprint (https://review.openstack.org/#/c/94612/). We had quite a good progress, although we could use some extra hands on Neutron side and some thoughts on the Nova-Neutron interaction aspect of the feature. The

Re: [openstack-dev] [Neutron][Nova] Trunk port feature (VLAN aware VMs)

On 21 October 2015 at 15:40, Ildikó Váncsa wrote: > Hi Folks, > > During Liberty we started the implementation of the VLAN aware VMs > blueprint (https://review.openstack.org/#/c/94612/). We had quite a good > progress, although we could use some extra hands on

[openstack-dev] {Blazar]{Nova] Tokyo meetup and next steps

Hi, The upcoming OpenStack Summit in Tokyo is a great opportunity to discuss open questions, like resource management and resource reservation. The Promise project in OPNFV is working on to identify the use cases and find a solution to this missing piece. For further information about this

[openstack-dev] Logging sessions at the Tokyo summit -- Let's get serious!

Hey operators and other users (and devs), We've got a number of logging sessions scheduled for the Summit. I'm collecting up information on the summit logging etherpad: https://etherpad.openstack.org/p/TYO-ops-logging and it will get fleshed out a lot more during the flight;-) Two goals of

Re: [openstack-dev] [ironic] Ironic design summit schedule

On Wed, Oct 21, 2015 at 02:24:08PM -0700, Wan-yen Hsu wrote: > Hi Jim, > >My techtalk is supposed to finish by 2:45pm. However, techtalk schedule > is not as well monitored as formal sessions so it could get delayed. > That's why I was exploring whether the group management session can be >

[openstack-dev] [Senlin] Weekly meeting 10/27 cancelled, resuming after summit

Since most developers will attend the summit next week. The weekly Senlin meeting next Tuesday will be skipped. We will resume on 11/03/2015. Right. We have more than 10 days to prepare an agenda, :) https://wiki.openstack.org/wiki/Meetings/SenlinAgenda Best Wishes, Qiming

Re: [openstack-dev] [Nova] Migration state machine proposal.

Hi Joshua, On 10/22/2015 05:17 AM, Joshua Harlow wrote: Question on some things seen in the below paste. What is with 'finished' -> 'reverted' and 'finished' -> 'confirmed'? Let's take confirm as an example. Please refer to function confirm_resize(). Resize is one type of migration in the

Re: [openstack-dev] [nova] Change from Mitaka: Expected UNIX signal to generate Guru Meditation (error) Reports

On Wed, Oct 21, 2015 at 02:43:39PM +0200, Kashyap Chamarthy wrote: > Background > -- > > Oslo Guru Meditation (error) Reports (GMR)[*] are a useful debugging > mechanism that allows one to capture the current state of a Nova > process/executable (e.g. `nova-compute`, `nova-api`, etc). >

[openstack-dev] [Congress] Congress social night

Hi Congress folks, Congress team plans to get-together on Wednesday night to be acquainted. If you are interested, please fill out quick RSVP [1] by the end of the week since I want to know a roughly estimated head count. If the number is big, I'll book sports bar, Japanese style bar called

Re: [openstack-dev] [Ironic] Driver documentation in Ironic

On Wed, Oct 21, 2015 at 03:30:05PM -0700, Wan-yen Hsu wrote: > As mentioned in the weekly IRC, 3rd-party vendor drivers are ranked lower > priority and therefore their code tend to merge at the late cycle of a > release. Therefore, it leads little time for driver author to submit > document and

[openstack-dev] [ironic] Next meeting is November 9

Hi folks, Since we'll all be at the summit next week, and presumably recovering the following week, the next Ironic meeting will be on November 9, in the usual place and time. See you there! :) // jim __ OpenStack

Re: [openstack-dev] [tc] [watcher] New project: Watcher

hi, seems like a neat idea, i had a few questions after watching the presentation from Vancouver. - is Watcher streaming the data captured by Ceilometer or is it querying the Ceilometer db? - is it utilising the Event data captured by Ceilometer or metric data? both? - i notice there's a

Re: [openstack-dev] [Fuel] Assigning VIPs on network config serialization

> Then we should close [1] as invalid, shoudn’t we? AFAIC, no. We should check whether there is enough IPs for nodes / VIPs with current network configuration. I'd propose to add a handler for allocation of VIPs if VIPs can be useful before deployment. I'm not sure what are the cases. Aleksey

Re: [openstack-dev] [infra] Upgrade to Gerrit 2.11

"Daniel P. Berrange" wrote on 10/21/2015 11:29:50 AM: > From: "Daniel P. Berrange" > To: "OpenStack Development Mailing List (not for usage questions)" > > Date: 10/21/2015 11:42 AM > Subject: Re: [openstack-dev]

Re: [openstack-dev] [Heat] core team nomination

- Original Message - > Congrats Rabi and Peter :) > > -Original Message- > From: Sergey Kraynev [mailto:skray...@mirantis.com] > Sent: Wednesday, October 21, 2015 12:57 PM > To: OpenStack Development Mailing List (not for usage questions) > Subject: Re: [openstack-dev] [Heat] core

Re: [openstack-dev] [Neutron] HenryG addition to the Neutron Drivers team

On Wed, Oct 21, 2015 at 4:01 AM, Ihar Hrachyshka wrote: > > > On 21 Oct 2015, at 05:14, Armando M. wrote: > > > > Hi folks, > > > > Henry has been instrumental in many areas of the projects and his crazy > working hours makes even Kevin and I bow in awe.

Re: [openstack-dev] [Fuel][QA][Plugins] Move functional tests from fuel-qa to the plugins

Mike, thanks for the clarification! I've filed a bug against fuel-qa [0] and submitted a patch [1]. Note that after a quick look, many Fuel projects have the same issue with the format of the MAINTAINERS file. Do you think we need one bug per project or do we piggy-back on the fuel-qa bug? BR,

Re: [openstack-dev] [Neutron] Gerrit permissions and Merge rights

On Wed, Oct 21, 2015 at 6:12 AM, Gal Sagie wrote: > Do we also want to consider Project Kuryr part of this? > We already started sending Kuryr spec to the Neutron repository and I > think it would make sense to manage it > as part of Neutron spec process. > > Any opinions on

Re: [openstack-dev] [Neutron] HenryG addition to the Neutron Drivers team

Congratulations Henry! On Wed, Oct 21, 2015 at 6:33 PM, Kyle Mestery wrote: > On Wed, Oct 21, 2015 at 4:01 AM, Ihar Hrachyshka > wrote: > >> >> > On 21 Oct 2015, at 05:14, Armando M. wrote: >> > >> > Hi folks, >> > >> > Henry has

[openstack-dev] [Fuel] [CI] Running fuelclient tests against review requests for fuel-web repo

Hi, It's yet another time we broke fuelclient by merging a change in fuel-web repo. Since we are considering moving Fuel UI to a separate repo, and we need to run UI functional tests against changes in nailgun anyway, I think we should start to change

[openstack-dev] [Nova] Scheduler based on CPU queue length

Hi All, I am fairly new to the OpenStack community and is trying to create a custom scheduler for Nova. A scheduler based on CPU queue length of the physical hosts. Kindly apologize if there are any inaccuracies in my statements. As I understand a weigher for the filter scheduler that weighs

Re: [openstack-dev] [neutron][sriov] SRIOV-VM could not work well with normal VM

I assume by Intel cards you mean something that is running ixgbe? If so and you are trying to use SR-IOV with OVS and VLANs running on top of the PF it will fail. The issue is that OVS requires the ability to place the PF in promiscuous mode to support VLAN trunking, and ixgbe driver prevents

[openstack-dev] [api][ironic] some questions about tags

Hi guys, Ironic is implementing the tags stuff: https://review.openstack.org/#/q/status:open+project:openstack/ironic+branch:master+topic:bp/nodes-tagging,n,z And this work is follow the guidelines of API Workgroup: http://specs.openstack.org/openstack/api-wg/guidelines/tags.html But I have two

[openstack-dev] [Solum] No meeting on October 27, 2015

Hi team, In this week's IRC meeting we decided to cancel next week's meeting (on October 27, 2015) due to Tokyo summit. We will convene again on November 3. Regards, Devdatta __ OpenStack Development Mailing List (not for

Re: [openstack-dev] [Fuel] [Puppet] Potential critical issue, due Puppet mix stderr and stdout while execute commands

I thought we had code in other places that split out stderr and only logged it if there was an actual error but I cannot find the reference now. I think that matches the original proposal. Not sure I like idea #3. On Wed, Oct 21, 2015 at 9:21 AM, Stanislaw Bogatkin wrote:

Re: [openstack-dev] [all][heat] Which repo to use in docs -- git.openstack.org or github.com?

On 20/10/15 18:34 +, Jeremy Stanley wrote: On 2015-10-20 13:20:34 -0500 (-0500), Dolph Mathews wrote: [...] +1 I would never direct anyone new straight to git.openstack.org because it makes a poor first impression relative to github.com. I assume that's the reason why we keep github.com as

Re: [openstack-dev] [Fuel][QA][Plugins] Move functional tests from fuel-qa to the plugins

2015-10-21 8:11 GMT+02:00 Mike Scherbakov : > > Simon is asking a valid request: if you add his folder in the file, he > will be always added to the review request by script, once it's > implemented. Only in the case when contribution is made to his particular > area of

Re: [openstack-dev] [mistral] How to call 3rd-party tools(such as Ansible) in Mistral

> On 20 Oct 2015, at 14:58, WANG, Ming Hao (Tony T) > wrote: > > Another question is: > If I use custom action to run Ansible, the Ansible playbook should be stored > on the same server of Mistral. Is it right? Depends on how this action is implemented (it

Re: [openstack-dev] [mistral] How to call 3rd-party tools(such as Ansible) in Mistral

> On 19 Oct 2015, at 13:18, WANG, Ming Hao (Tony T) > wrote: > > I like your > option2(https://blueprints.launchpad.net/mistral/+spec/action-providers > ). J > Any schedule for this? Looks like

Re: [openstack-dev] [Heat] core team nomination

+1 to both. Qiming On Tue, Oct 20, 2015 at 04:38:12PM +0300, Sergey Kraynev wrote: > I'd like to propose new candidates for heat core-team: > Rabi Mishra > Peter Razumovsky > > According statistic both candidate made a big effort in Heat as > reviewers and as contributors [1][2]. > They were

Re: [openstack-dev] Custom Nova scheduler based on CPU queue length

Excerpts from Rahul Nair's message of 2015-10-20 18:53:09 -0700: > ​Hi All, > > I am fairly new to the OpenStack community and is trying to create a custom > scheduler for Nova. A scheduler based on CPU queue length. Kindly apologize > if there are any inaccuracies in my statements. > > As I

[openstack-dev] openstack-barbican-authenticate-keystone-barbican-command

Link: https://openstack.nimeyo.com/62868/?show=62868#q62868 From: marif82 Hi Asha, I am also getting the same error when I am executing the curl command to create secret. bash-4.2$ curl -X POST -H 'content-type:application/json' -H 'X-Project-Id:12345' -d '{"payload":

Re: [openstack-dev] [Neutron] HenryG addition to the Neutron Drivers team

Congratulations Henry! On Wed, Oct 21, 2015 at 8:49 AM, Kevin Benton wrote: > Excellent addition! Remember everyone, if the feature you want doesn't > make it into Neutron, it's now Henry's fault. :) > > On Tue, Oct 20, 2015 at 8:14 PM, Armando M. wrote: >

Re: [openstack-dev] [Fuel][Plugins] Plugin deployment questions

Hi, Can we ignore the problem above and remove this limitation? Or should > we improve it somehow so it would work for one nodes, and will be > ignored for others? > I think that this validation needs to be accomplished in a different way, we don't need 1 controller for the sake of 1 controller,

Re: [openstack-dev] [Fuel][Plugins] Plugin deployment questions

Hi Dmitry, > Insert required metadata into roles that relies on another roles, for > compute it will be something like: > > compute: > requires: controller > 1 Yeah, that's actually what I was thinking about when I wrote: > Or should we improve it somehow so it would work for one

[openstack-dev] [ANNOUNCE] [HA] [Pacemaker] new, maintained openstack-resource-agents repository

[cross-posting to openstack-dev and pacemaker user lists; please consider trimming the recipients list if your reply is not relevant to both communities] Hi all, Back in June I proposed moving the well-used but no longer maintained https://github.com/madkiss/openstack-resource-agents/ repository

Re: [openstack-dev] [infra] Upgrade to Gerrit 2.11

On Tue, Oct 13, 2015 at 05:08:29PM -0700, Zaro wrote: > Hello All, > > The openstack-infra team would like to upgrade from our Gerrit 2.8 to > Gerrit 2.11. We are proposing to do the upgrade shortly after the > Mitaka summit. The main motivation behind the upgrade is to allow us > to take

  1   2   >