Re: [openstack-dev] [Kuryr] Need help in jenkins failure

On Fri, Aug 12, 2016 at 11:13 AM, Liping Mao (limao) wrote: > Just guess, Maybe you install "kuryr-lib” by manually from offical repo? > :-) > > Nope, i was not installing manually andwas just doing 'tox -e py27'. I uncommented that and 'recheck' on patch. Lets see :) >

Re: [openstack-dev] [Kuryr] Need help in jenkins failure

Just guess, Maybe you install "kuryr-lib” by manually from offical repo? :-) Regards, Liping Mao From: Vikas Choudhary > Date: 2016年8月12日 星期五 下午1:33 To: Liping Mao > Cc: OpenStack List

Re: [openstack-dev] [Kuryr] Need help in jenkins failure

Thanks Liping, this seems to be the reason for sure. Still wondering how come it works on local system. Let me check again. -Vikas On Fri, Aug 12, 2016 at 10:58 AM, Liping Mao (limao) wrote: > Hi Vikas, > > Not sure , but is it because this line? >

[openstack-dev] [fuel] mcollective configuration on slaves

Guys, Currently, at the time of the first boot Mcollective on slaves is configured by Cloud-init (host, port etc.) and by Nailgun agent when node identity is written. This happens in any order and already caused several problem which were fixed in bounds of

Re: [openstack-dev] [Kuryr] Need help in jenkins failure

Hi Vikas, Not sure , but is it because this line? https://github.com/vikaschoudhary16/kuryr/blob/drop_libnet_specific_code/ku ryr/lib/config.py#L105 Thanks. Regards, Liping Mao From: Vikas Choudhary Date: 2016年8月12日 星期五 下午12:32 To: OpenStack List

Re: [openstack-dev] [Cinder] [stable] [all] Changing stable policy for drivers

On 08/12/2016 04:25 AM, Robert Collins wrote: > On 11 Aug 2016 3:13 PM, "Ben Swartzlander" > wrote: >> >> ... >> >> I still don't agree with this stance. Code doesn't just magically stop > working. Code breaks when things change which aren't

[openstack-dev] What's Up, Doc? 12 August

Hi everyone, I have been struck down with flu yet again this week, so a quiet one from me (I'll be glad when winter is over, let me tell you!). Anne, however, has been kicking it out of the park with her work on the API docs; I suggest you take a look at the update she sent to the mailing

[openstack-dev] [Kuryr] Need help in jenkins failure

Hello Everybody, I am not able to reproduce jenkins failure (tox -e py27) on this,[1] , patch when trying locally. I have tried "recheck" also. There is something wrong which i am not able to catch. I have spent a good effort on analysing this but no clue. Will appreciate if anybody try this

Re: [openstack-dev] [Zun][Higgins] Proposing Sudipta Biswas and Wenzhi Yu for Zun core reviewer team

+1 for both, welcome, Sudipta and Wenzhi :) 2016-08-11 13:55 GMT+08:00 Kumari, Madhuri : > +1 from me for both. > > > > *From:* Hongbin Lu [mailto:hongbin...@gmail.com] > *Sent:* Wednesday, August 10, 2016 8:40 PM > *To:* OpenStack Development Mailing List (not for

Re: [openstack-dev] [Cinder] [stable] [all] Changing stable policy for drivers

On 11 Aug 2016 3:13 PM, "Ben Swartzlander" wrote: > > ... > > I still don't agree with this stance. Code doesn't just magically stop working. Code breaks when things change which aren't version controlled properly or when you have undeclared dependencies. Well this is why

Re: [openstack-dev] [nova] os-capabilities library created

On 08/11/2016 05:50 PM, John Dickinson wrote: On 3 Aug 2016, at 16:47, Jay Pipes wrote: Hi Novas and anyone interested in how to represent capabilities in a consistent fashion. I spent an hour creating a new os-capabilities Python library this evening:

Re: [openstack-dev] [requirements] near term gate optimization opportunity

On Thu, Aug 11, 2016 at 08:59:04PM -0400, Sean Dague wrote: > That seems like a further optimization. Honestly, I would rarely expect > these to be in merge conflict, and at worse, they would be so until the next > requirements push. Cool, we'll try to make it so. Yours Tony. signature.asc

Re: [openstack-dev] [nova] os-capabilities library created

On 08/11/2016 05:25 PM, Ed Leafe wrote: On Aug 3, 2016, at 6:47 PM, Jay Pipes wrote: Please see the README for examples of how the library works and how I'm thinking of structuring these capability strings and symbols. I intend os-capabilities to be the place where the

Re: [openstack-dev] [nova] os-capabilities library created

On 08/11/2016 05:46 PM, Clay Gerrard wrote: On Thu, Aug 11, 2016 at 2:25 PM, Ed Leafe > wrote: Overall this looks good, although it seems a bit odd to have ALL_CAPS_STRINGS to represent all:caps:strings throughout. The example you gave:

Re: [openstack-dev] [requirements] near term gate optimization opportunity

On 08/11/2016 07:56 PM, Tony Breeds wrote: On Thu, Aug 11, 2016 at 09:13:12AM +0200, Andreas Jaeger wrote: On 2016-08-10 23:06, Sean Dague wrote: Based on reading some logs, it looks like requirements updates are getting regenerated on every requirements land for all open patches, even if they

Re: [openstack-dev] [requirements][elections] Requirements PTL Results

On Thu, Aug 11, 2016 at 09:33:29AM -0400, Anita Kuno wrote: > We'd like to thank all those folks who came out to participate in this > election on very brief notice. Thank you. The participation rate is > impressive. > > Thank you to all candidates who put themselves forward, showing their >

Re: [openstack-dev] [nova] os-capabilities library created

Excerpts from Jay Pipes's message of 2016-08-03 19:47:37 -0400: >> Hi Novas and anyone interested in how to represent capabilities in a >> consistent fashion. >> >> I spent an hour creating a new os-capabilities Python library this evening: > >>

Re: [openstack-dev] [requirements] near term gate optimization opportunity

On Thu, Aug 11, 2016 at 09:13:12AM +0200, Andreas Jaeger wrote: > On 2016-08-10 23:06, Sean Dague wrote: > > Based on reading some logs, it looks like requirements updates are > > getting regenerated on every requirements land for all open patches, > > even if they aren't impacted by it - > >

Re: [openstack-dev] [nova] Possible REST API design change for get-me-a-network (2.37)

On Thu, Aug 11, 2016, at 06:54 PM, Chris Friesen wrote: > On 08/11/2016 03:53 PM, Matt Riedemann wrote: > > I wanted to bring this up for awareness since we're getting close to feature > > freeze and want consensus before it gets too late. > > > > Ken'ichi brought up a good question on my REST

Re: [openstack-dev] [magnum] ssh and http connection lost

Hi Yasemin, It sounds like your environment has some special networking customization. The docker0 bridge is used to connect the containers and should have no effect on your network connectivity. In the Swarm bay, it shows up on all the VM's. On your devstack, it should not be there unless

Re: [openstack-dev] [nova] Possible REST API design change for get-me-a-network (2.37)

On 08/11/2016 03:53 PM, Matt Riedemann wrote: I wanted to bring this up for awareness since we're getting close to feature freeze and want consensus before it gets too late. Ken'ichi brought up a good question on my REST API change for the 2.37 microversion:

Re: [openstack-dev] [Cinder] [stable] [all] Changing stable policy for drivers

On 08/11/2016 04:13 PM, Ben Swartzlander wrote: On 08/10/2016 01:57 PM, Matthew Treinish wrote: On Wed, Aug 10, 2016 at 09:52:55AM -0700, Clay Gerrard wrote: On Wed, Aug 10, 2016 at 7:42 AM, Ben Swartzlander wrote: A big source of problems IMO is that tempest doesn't

Re: [openstack-dev] [nova] os-capabilities library created

On Aug 11, 2016, at 5:29 PM, John Dickinson wrote: >> I will let Jay speak for himself (as if I could somehow prevent that!), but >> the intent here is that this won’t be for Nova specifically; it is targeted >> primarily for the forthcoming placement service (you might know it as

Re: [openstack-dev] [nova] os-capabilities library created

On 11 Aug 2016, at 15:14, Ed Leafe wrote: > On Aug 11, 2016, at 4:50 PM, John Dickinson wrote: > >> Is this intended to be a cross-project thing? The message is tagged >> "[nova]", so I'm kinda surprised I saw it, but the library seems to be >> called openstack capabilities. So

Re: [openstack-dev] [Cinder] [stable] [all] Changing stable policy for drivers

On 08/10/2016 01:57 PM, Matthew Treinish wrote: On Wed, Aug 10, 2016 at 09:52:55AM -0700, Clay Gerrard wrote: On Wed, Aug 10, 2016 at 7:42 AM, Ben Swartzlander wrote: A big source of problems IMO is that tempest doesn't have stable branches. We use the master branch

Re: [openstack-dev] [nova] Possible REST API design change for get-me-a-network (2.37)

2016-08-11 14:53 GMT-07:00 Matt Riedemann : > I wanted to bring this up for awareness since we're getting close to feature > freeze and want consensus before it gets too late. > > Ken'ichi brought up a good question on my REST API change for the 2.37 > microversion: > >

Re: [openstack-dev] [nova] os-capabilities library created

On Aug 11, 2016, at 4:50 PM, John Dickinson wrote: > Is this intended to be a cross-project thing? The message is tagged "[nova]", > so I'm kinda surprised I saw it, but the library seems to be called openstack > capabilities. So if this is going to be a big thing for everyone,

Re: [openstack-dev] [all] versioning the api-ref?

On 11 Aug 2016, at 15:02, Brian Rosmaita wrote: > I have a question about the api-ref. Right now, for example, the new > images v1/v2 api-refs are accurate for Mitaka. But DocImpact bugs are > being generated as we speak for changes in master that won't be > available to consumers until Newton

[openstack-dev] [all] versioning the api-ref?

I have a question about the api-ref. Right now, for example, the new images v1/v2 api-refs are accurate for Mitaka. But DocImpact bugs are being generated as we speak for changes in master that won't be available to consumers until Newton is released (unless they build from source). If those bug

Re: [openstack-dev] [all][tc][ptl] establishing project-wide goals

On 10 Aug 2016, at 8:29, Doug Hellmann wrote: > Excerpts from Doug Hellmann's message of 2016-07-29 16:55:22 -0400: >> One of the outcomes of the discussion at the leadership training >> session earlier this year was the idea that the TC should set some >> community-wide goals for accomplishing

[openstack-dev] [nova] Possible REST API design change for get-me-a-network (2.37)

I wanted to bring this up for awareness since we're getting close to feature freeze and want consensus before it gets too late. Ken'ichi brought up a good question on my REST API change for the 2.37 microversion: https://review.openstack.org/#/c/316398/ The way I had written this was to

Re: [openstack-dev] [nova] os-capabilities library created

Excerpts from Jay Pipes's message of 2016-08-03 19:47:37 -0400: > Hi Novas and anyone interested in how to represent capabilities in a > consistent fashion. > > I spent an hour creating a new os-capabilities Python library this evening: > > http://github.com/jaypipes/os-capabilities > > Please

Re: [openstack-dev] [nova] os-capabilities library created

On 3 Aug 2016, at 16:47, Jay Pipes wrote: > Hi Novas and anyone interested in how to represent capabilities in a > consistent fashion. > > I spent an hour creating a new os-capabilities Python library this evening: > > http://github.com/jaypipes/os-capabilities > > Please see the README for

Re: [openstack-dev] [nova] os-capabilities library created

On Thu, Aug 11, 2016 at 2:25 PM, Ed Leafe wrote: > > Overall this looks good, although it seems a bit odd to have > ALL_CAPS_STRINGS to represent all:caps:strings throughout. The example you > gave: > > >>> print os_caps.HW_CPU_X86_SSE42 > hw:cpu:x86:sse42 > > Just to be clear,

Re: [openstack-dev] [nova] os-capabilities library created

On Aug 3, 2016, at 6:47 PM, Jay Pipes wrote: > Please see the README for examples of how the library works and how I'm > thinking of structuring these capability strings and symbols. I intend > os-capabilities to be the place where the OpenStack community catalogs and >

Re: [openstack-dev] [Neutron] Team and Driver meetings for the week of Aug 15th

The Neutron L3 meeting will be canceled. We will still hold the routed networks meeting on Tuesday. Carl On Thu, Aug 11, 2016 at 12:19 PM, Henry Gessau wrote: > Armando M. wrote: > > Hi Neutrinos, > > > > The meetings will be cancelled due to the

Re: [openstack-dev] [puppet] proposal: start gating on puppet4

On Tue, Aug 9, 2016 at 1:39 PM, Emilien Macchi wrote: > Hi, > > Today Puppet OpenStack CI is running unit and functional test jobs > against puppet 3 and puppet 4. > Unit jobs for puppet 4 are currently voting and pretty stable. > Functional jobs for puppet 4 are not voting

[openstack-dev] [release] Release countdown for week R-7, 15-19 Aug

Focus - Major feature work should be well under way as we approach the third milestone. General Notes - Prepare for the non-client library freeze coming up on 25 Aug. by finishing any feature work that requires library changes. We freeze releases of all libraries between the

Re: [openstack-dev] [all][infra] Constraints are ready to be used for tox.ini

> -Original Message- > From: John Dickinson [mailto:m...@not.mn] > Sent: Thursday, August 11, 2016 2:09 PM > To: OpenStack Development Mailing List > Subject: Re: [openstack-dev] [all][infra] Constraints are ready to be used > for tox.ini > > > > On

Re: [openstack-dev] [all][infra] Constraints are ready to be used for tox.ini

On 2016-08-11 20:19:51 +0200 (+0200), Ihar Hrachyshka wrote: > Do I read it right that we can now use constraints for post queue too > (releasenotes, cover, venv targets)? Yes, that was the hardest part to get working, but thanks to tireless efforts on the part of a number of people that has now

Re: [openstack-dev] [Tripleo] Tripleo HA Federation Proof-of-Concept

Nice work Adam, as usual. I'm dropping some comments about how we could automate it in TripleO: # Identity Provider Registration and Metadata This script could be called by Puppet or Heat at the right time, but now I don't have the best answer. # Federation Operations We can achieve it with

Re: [openstack-dev] [sahara] Nominate Telles Mota Vidal Nóbrega for core team

Thanks Vitaly and everyone else. On Thu, Aug 11, 2016 at 3:22 PM, Vitaly Gridnev wrote: > Since it's was discussed at meeting, and there is no objections, welcome! > > On Thu, Aug 11, 2016 at 9:15 PM, Trevor McKay wrote: > >> +2 >> >> On Fri,

Re: [openstack-dev] [Neutron] Team and Driver meetings for the week of Aug 15th

Henry Gessau wrote: Armando M. wrote: Hi Neutrinos, The meetings will be cancelled due to the mid-cycle. The neutron-lib meeting will also skip next week. …and neutron upgrades meeting is NOT going to be skipped. Ihar

Re: [openstack-dev] [sahara] Nominate Telles Mota Vidal Nóbrega for core team

Thank you all!!! On Thu, Aug 11, 2016 at 3:15 PM, Trevor McKay wrote: > +2 > > On Fri, 2016-08-12 at 00:56 +0800, lu jander wrote: > > +2 from me thx Telles > > > > 2016-08-12 0:20 GMT+08:00 Sergey Reshetnyak > > : > > +2 from me > > > >

Re: [openstack-dev] [sahara] Nominate Telles Mota Vidal Nóbrega for core team

Absolutely +2. Telles has been a proven contributor for quite some time now. Thanks for all the work, Telles! On Thu, Aug 11, 2016 at 2:15 PM, Trevor McKay wrote: > +2 > > On Fri, 2016-08-12 at 00:56 +0800, lu jander wrote: > > +2 from me thx Telles > > > > 2016-08-12 0:20

Re: [openstack-dev] [sahara] Nominate Telles Mota Vidal Nóbrega for core team

Since it's was discussed at meeting, and there is no objections, welcome! On Thu, Aug 11, 2016 at 9:15 PM, Trevor McKay wrote: > +2 > > On Fri, 2016-08-12 at 00:56 +0800, lu jander wrote: > > +2 from me thx Telles > > > > 2016-08-12 0:20 GMT+08:00 Sergey Reshetnyak > >

Re: [openstack-dev] [all][infra] Constraints are ready to be used for tox.ini

Do I read it right that we can now use constraints for post queue too (releasenotes, cover, venv targets)? Ihar Andreas Jaeger wrote: TL;DR: upper-constraints can be used now for all tox based jobs With any software package, you will need additional packages to run it.

Re: [openstack-dev] [Neutron] Team and Driver meetings for the week of Aug 15th

Armando M. wrote: > Hi Neutrinos, > > The meetings will be cancelled due to the mid-cycle. The neutron-lib meeting will also skip next week. __ OpenStack Development Mailing List (not for usage

[openstack-dev] [Tripleo] Tripleo HA Federation Proof-of-Concept

http://adam.younglogic.com/2016/08/ooo-ha-fed-poc/ It is painful, sloppy, Mitaka based. Have at it, and lets make Federation a reality for Newton based deployments. Feedback eagerly sought. Thanks for all the people that helped get me through this. Won't list you all, as it would start

Re: [openstack-dev] [sahara] Nominate Telles Mota Vidal Nóbrega for core team

+2 On Fri, 2016-08-12 at 00:56 +0800, lu jander wrote: > +2 from me thx Telles > > 2016-08-12 0:20 GMT+08:00 Sergey Reshetnyak > : > +2 from me > > 2016-08-11 19:15 GMT+03:00 Sergey Lukjanov > : >

Re: [openstack-dev] [all][infra] Constraints are ready to be used for tox.ini

On 11 Aug 2016, at 10:03, Andreas Jaeger wrote: > TL;DR: upper-constraints can be used now for all tox based jobs > > With any software package, you will need additional packages to run it. > Often, there's a tight coupling: The software package will only run with > specific other package

Re: [openstack-dev] [magnum] ssh and http connection lost

Hi I want to use docker swarm bay. i must be configure because of our network system configuration, docker bridge broken my ssh connection. > On Aug 11, 2016, at 4:53 PM, Ton Ngo wrote: > > Hi Yasemin, > How would you like to configure the networking? Which COE are you using?

Re: [openstack-dev] [ironic] Driver composition defaults call

Yesterday as a group (jroll, rloo, dtantsur, matt128, devananda, vdrok, and myself) discussed defaults for driver composition. The options we discussed were: * The existing specification[0] - Global and hardware_type default_FOO_interface configuration, global enabled_FOO_interfaces in configs,

Re: [openstack-dev] [cinder] [neutron] [ironic] [api] [doc] API status report

> > Sorry, in reviewing further today I found another project that does not > have a publish job but has in-tree source files: > > cinder > > Team cinder: can you let me know where you are in your publishing comfort > level? Please add an api-ref-jobs: line with a target of block-storage > to

[openstack-dev] [all][api] POST /api-wg/news

Greetings OpenStack community, Our main new topic for today was making sure that we take a more active role in curating the bugs that are now being kept in launchpad [4] by including review of those bugs in the workshopping that we do in each meeting. If you find issues in the existing

[openstack-dev] [all][infra] Constraints are ready to be used for tox.ini

TL;DR: upper-constraints can be used now for all tox based jobs With any software package, you will need additional packages to run it. Often, there's a tight coupling: The software package will only run with specific other package versions. This dependency information is sometimes found in

Re: [openstack-dev] [sahara] Nominate Telles Mota Vidal Nóbrega for core team

+2 from me thx Telles 2016-08-12 0:20 GMT+08:00 Sergey Reshetnyak : > +2 from me > > 2016-08-11 19:15 GMT+03:00 Sergey Lukjanov : > >> +2 >> >> On Thu, Aug 11, 2016 at 8:48 AM, Elise Gafford >> wrote: >> >>> Hearty +2.

[openstack-dev] [openstack-operators][Sahara] Deprecation notes for Newton cycle

Hello team, The aim of this letter is to provide all needed information about features which were deprecated in Sahara in the Newton release cycle, and several important notes from the Mitaka release cycle. 1. In Mitaka, all old CLI commands were marked as deprecated. We are not removing them in

Re: [openstack-dev] [nova] The deprecation of proxy API related CLI

On 8/10/2016 11:01 PM, Alex Xu wrote: Hi, guys, We have agreement on how to deprecate the CLI for the proxy APIs which were deprecated in 2.36 when mid-cycle. But I still feels that we have something isn't very clear. So I just want to summary the situation at here, and to be clear the final

[openstack-dev] [kolla] FW: [all][ptl][tc] extra ATCs for newton

Koalligans, I can't think of anyone off the top of my head that hasn't submitted a patch for Newton that would qualify for an ATC pass under the bylaws [1] and TC Charter [2], but would like to open up nominations from core reviewers since I am not omnipotent. The only candidates that even come

[openstack-dev] [neutron][taas]

Hi, When we create a tap-service, a VLAN ID will be associated with that tap-service. In case we want to identify the flows associated with that VLAN ID, so that we can add additional filters, the response returned after creating a tap-service must include the VLAN ID information as well. Can

Re: [openstack-dev] [sahara] Nominate Telles Mota Vidal Nóbrega for core team

+2 from me 2016-08-11 19:15 GMT+03:00 Sergey Lukjanov : > +2 > > On Thu, Aug 11, 2016 at 8:48 AM, Elise Gafford > wrote: > >> Hearty +2. Telles has been working on Sahara for years, and has been a >> consistent and incisive reviewer and code

Re: [openstack-dev] [sahara] Nominate Telles Mota Vidal Nóbrega for core team

+2 On Thu, Aug 11, 2016 at 8:48 AM, Elise Gafford wrote: > Hearty +2. Telles has been working on Sahara for years, and has been a > consistent and incisive reviewer and code contributor. > > Congratulations Telles; very well deserved! > > - Elise > > On Thu, Aug 11, 2016 at

[openstack-dev] [Neutron] Team and Driver meetings for the week of Aug 15th

Hi Neutrinos, The meetings will be cancelled due to the mid-cycle. Cheers, Armando __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe

Re: [openstack-dev] [sahara] Nominate Telles Mota Vidal Nóbrega for core team

Hearty +2. Telles has been working on Sahara for years, and has been a consistent and incisive reviewer and code contributor. Congratulations Telles; very well deserved! - Elise On Thu, Aug 11, 2016 at 11:37 AM, Vitaly Gridnev wrote: > Hello core team, > > I'd like to

Re: [openstack-dev] [vitrage] scenario evaluator not enabled by default

This is on purpose. When Vitrage is started, it first runs a "consistency" round where it gets all the resources from its datasources and inserts them into the entity graph. Once this initial phase is over, the evaluator is run over all the entity graph to check for meaningful patterns based

[openstack-dev] [sahara] Nominate Telles Mota Vidal Nóbrega for core team

Hello core team, I'd like to nominate Telles Mota Vidal Nóbrega for core reviewer team. Let's vote with +2/-2 for his candidacy. Review/Commits stats can be found at [0]. [0] http://stackalytics.com/?module=sahara-group_id=tellesmvn -- Best Regards, Vitaly Gridnev, Project Technical Lead of

Re: [openstack-dev] [neutron] Feature Classification

> On Aug 10, 2016, at 1:21 PM, Armando M. wrote: > > > > On 10 August 2016 at 10:20, Gupta, Ankur > wrote: > Hello Neutrinos, > > > > One of the things, that is required to have ease of use, is good >

Re: [openstack-dev] [nova] test strategy for the serial console feature

On Thu, Aug 11, 2016 at 04:46:02PM +0200, Markus Zoeller wrote: > On 11.08.2016 13:31, Daniel P. Berrange wrote: > > On Thu, Aug 11, 2016 at 07:19:42AM -0400, Sean Dague wrote: > >> On 08/11/2016 05:45 AM, Markus Zoeller wrote: > >>> On 26.07.2016 12:16, Jordan Pittier wrote: > Hi Markus >

Re: [openstack-dev] [infra] Project tailored VM image for Jenkins jobs

On 2016-08-11 02:30:07 -0500 (-0500), e...@itsonlyme.name wrote: [...] > So it seems the way to go is: > 1. Upload what we need to e.g.: > http://tarballs.openstack.org/storlet/images/docker/ubuntu_14.04.tar.gz Yep, generally you'd have a CI job build and upload that, not generate it by hand. If

Re: [openstack-dev] [nova] test strategy for the serial console feature

On 11.08.2016 16:46, Markus Zoeller wrote: > On 11.08.2016 13:31, Daniel P. Berrange wrote: >> On Thu, Aug 11, 2016 at 07:19:42AM -0400, Sean Dague wrote: >>> On 08/11/2016 05:45 AM, Markus Zoeller wrote: On 26.07.2016 12:16, Jordan Pittier wrote: > Hi Markus > You don"t really need a

[openstack-dev] [cinder] [neutron] [ironic] [api] [doc] API status report

On Wed, Aug 10, 2016 at 2:49 PM, Anne Gentle wrote: > Hi all, > I wanted to report on status and answer any questions you all have about > the API reference and guide publishing process. > > The expectation is that we provide all OpenStack API information on >

Re: [openstack-dev] [vitrage] scenario evaluator not enabled by default

Sorry for having put a url from forked repo. It should be https://github.com/openstack/vitrage/commit/bdba10cb71b2fa3744e4178494fa860303ae0bbe#diff-6f1a277a2f6e9a567b38d646f19728bcL36 But the content is the same -- Yujun On Thu, Aug 11, 2016 at 10:43 PM Yujun Zhang

Re: [openstack-dev] [tc][cinder] tag:follows-standard-deprecation should be removed

Given the options, I'd agree with Sean and John that removing the tag is a far lesser evil than changing our policy. If we leave broken drivers in the tree, the end user (operator) is no better off - the thing they evaluated won't work - but it will be harder to tell why. The storage vendor won't

Re: [openstack-dev] [nova] test strategy for the serial console feature

On 11.08.2016 13:31, Daniel P. Berrange wrote: > On Thu, Aug 11, 2016 at 07:19:42AM -0400, Sean Dague wrote: >> On 08/11/2016 05:45 AM, Markus Zoeller wrote: >>> On 26.07.2016 12:16, Jordan Pittier wrote: Hi Markus You don"t really need a whole new job for this. Just turn that flag to

Re: [openstack-dev] [tc][cinder] tag:follows-standard-deprecation should be removed

On 11/08/2016 15:35, John Griffith wrote: > > > On Thu, Aug 11, 2016 at 7:14 AM, Erno Kuvaja > wrote: > > On Thu, Aug 11, 2016 at 2:47 PM, Sean McGinnis > > wrote: > >> >> > >> >>

[openstack-dev] [vitrage] scenario evaluator not enabled by default

It seems the scenario evaluator is not enabled when vitrage is started in devstack installer. I dig a bit in the history, it seems the default value for the evaluator is changed from True to False in a history commit [1]. Is it breaking the starting of evaluator or I have missed some steps to

Re: [openstack-dev] [tc][cinder] tag:follows-standard-deprecation should be removed

On Thu, Aug 11, 2016 at 7:14 AM, Erno Kuvaja wrote: > On Thu, Aug 11, 2016 at 2:47 PM, Sean McGinnis > wrote: > >> >> > >> >> As follow up on the mailing list discussion [0], gerrit activity > >> >> [1][2] and cinder 3rd party CI policy [3] I'd like to

Re: [openstack-dev] [octavia] Multi-node controller testing

Hi, "need to have something (tempest-plugin) to make sure that integration works with nova & neutron" - Its easy to write scenarios that will test that octavia works with nova and neutron "I guess rally is more suited to make sure that things work at scale, to uncover any sort of race

Re: [openstack-dev] [nova] Nova mascot - nominations and voting

On 08/10/2016 11:46 AM, Sean Dague wrote: > On 08/10/2016 11:36 AM, Sean Dague wrote: >> On 08/09/2016 07:30 PM, Heidi Joy Tretheway wrote: >>> TL;DR: If you don’t want a mascot, you don’t have to. But Nova, you’ll >>> be missed. :-) >>> >>> A few notes following up on Matt Riedemann, Clint Byrum,

Re: [openstack-dev] [tc][cinder] tag:follows-standard-deprecation should be removed

On Thu, Aug 11, 2016 at 2:47 PM, Sean McGinnis wrote: >> >> >> >> As follow up on the mailing list discussion [0], gerrit activity >> >> [1][2] and cinder 3rd party CI policy [3] I'd like to initiate >> >> discussion how Cinder follows, or rather does not follow, the

Re: [openstack-dev] [ironic] About third-party CI

Noticed something had slipped :) On 2016-08-10 9:21 AM, Jim Rollenhagen wrote: 4) The drivers that use pyghmi (pxe_ipminative and agent_pyghmi) currently are not tested in ironic's CI. We have multiple jobs for each of the ipmitool drivers. Instead of making new jobs, we could just move

Re: [openstack-dev] [puppet] Why do we have two providers for openstack_config ?

On Thu, Aug 11, 2016 at 9:26 AM, Sofer Athlan-Guyot wrote: > Hi, > > I stumbled on the fact that there are two providers for the > openstack_config type: ruby[1]; ini_setting.rb[2]. > > The ruby's one has a fork of the inifile ruby's provider is there[3]. > > It is currently

Re: [openstack-dev] [puppet] Why do we have two providers for openstack_config ?

Hi, I kinda answered all my question myself. Here a sum up of what I have understood https://review.openstack.org/#/c/354094/ Feel free to review. Regards, Sofer Athlan-Guyot writes: > Hi, > > I stumbled on the fact that there are two providers for the >

Re: [openstack-dev] [nova] The deprecation of proxy API related CLI

On 8/10/2016 11:01 PM, Alex Xu wrote: Hi, guys, We have agreement on how to deprecate the CLI for the proxy APIs which were deprecated in 2.36 when mid-cycle. But I still feels that we have something isn't very clear. So I just want to summary the situation at here, and to be clear the final

Re: [openstack-dev] [vitrage] aodh datasource properties

OK, I have assigned myself for this issue and hope to resolve it soon. -- Yujun On Thu, Aug 11, 2016 at 6:30 PM Afek, Ifat (Nokia - IL) wrote: > Hi Yujun, > > There are few ways to create Aodh alarms. You are referring to > event-alarms, and I believe you are right about

Re: [openstack-dev] [magnum] ssh and http connection lost

Hi Yasemin, How would you like to configure the networking? Which COE are you using? You may want to consult the Networking section in the user guide: https://github.com/openstack/magnum/blob/master/doc/source/userguide.rst#networking Ton Ngo, From: Yasemin DEMİRAL (BİLGEM BTE)

Re: [openstack-dev] [tc][cinder][stable] tag:follows-standard-deprecation should be removed

Excerpts from Erno Kuvaja's message of 2016-08-11 13:59:54 +0100: > On Thu, Aug 11, 2016 at 1:32 PM, Doug Hellmann wrote: > > Excerpts from Erno Kuvaja's message of 2016-08-11 12:26:59 +0100: > >> Hi all, > >> > >> As follow up on the mailing list discussion [0], gerrit

Re: [openstack-dev] [tc][cinder] tag:follows-standard-deprecation should be removed

> >> > >> As follow up on the mailing list discussion [0], gerrit activity > >> [1][2] and cinder 3rd party CI policy [3] I'd like to initiate > >> discussion how Cinder follows, or rather does not follow, the standard > >> deprecation policy [4] as the project has been tagged on the assert > >>

Re: [openstack-dev] [tc][cinder][stable] tag:follows-standard-deprecation should be removed

On 16-08-11 09:36 AM, Doug Hellmann wrote: Excerpts from Erno Kuvaja's message of 2016-08-11 13:59:54 +0100: On Thu, Aug 11, 2016 at 1:32 PM, Doug Hellmann wrote: Excerpts from Erno Kuvaja's message of 2016-08-11 12:26:59 +0100: Hi all, As follow up on the mailing

[openstack-dev] [requirements][elections] Requirements PTL Results

We'd like to thank all those folks who came out to participate in this election on very brief notice. Thank you. The participation rate is impressive. Thank you to all candidates who put themselves forward, showing their enthusiasm for the role. It is plain to see this new team has a lot of

[openstack-dev] [puppet] Why do we have two providers for openstack_config ?

Hi, I stumbled on the fact that there are two providers for the openstack_config type: ruby[1]; ini_setting.rb[2]. The ruby's one has a fork of the inifile ruby's provider is there[3]. It is currently used by those 6 types: - neutron_lbaas_service_config - nova_config -

Re: [openstack-dev] [puppet] proposal: start gating on puppet4

+1, Awesome idea Emilien. 2016-08-11 9:45 GMT-03:00 Sofer Athlan-Guyot : > +1 for me also. We have to push forward to have puppet 4 as a first > class citizen. > > Matt Fischer writes: > > > +1 from me also. This will help everyone who is trying to

Re: [openstack-dev] I want to consult ironic problems

Hi Paul, It seems you are having issues running Ironic and as Jeremy pointed out in a previous reply, the proper mailing list for this is openst...@lists.openstack.org. On the technical side, keep in mind the kernel and ramdisks are part of a complete solution and should be used by Ironic

Re: [openstack-dev] [tc][cinder] tag:follows-standard-deprecation should be removed

On Thu, Aug 11, 2016 at 1:32 PM, Doug Hellmann wrote: > Excerpts from Erno Kuvaja's message of 2016-08-11 12:26:59 +0100: >> Hi all, >> >> As follow up on the mailing list discussion [0], gerrit activity >> [1][2] and cinder 3rd party CI policy [3] I'd like to initiate >>

Re: [openstack-dev] [puppet] proposal: start gating on puppet4

+1 for me also. We have to push forward to have puppet 4 as a first class citizen. Matt Fischer writes: > +1 from me also. This will help everyone who is trying to transition > to it. > > On Wed, Aug 10, 2016 at 1:46 AM, Javier Pena > wrote: > >

Re: [openstack-dev] [tc][cinder] tag:follows-standard-deprecation should be removed

Excerpts from Erno Kuvaja's message of 2016-08-11 12:26:59 +0100: > Hi all, > > As follow up on the mailing list discussion [0], gerrit activity > [1][2] and cinder 3rd party CI policy [3] I'd like to initiate > discussion how Cinder follows, or rather does not follow, the standard > deprecation

[openstack-dev] [new][oslo] osprofiler 1.4.0 release (newton)

We are happy to announce the release of: osprofiler 1.4.0: OpenStack Profiler Library This release is part of the newton release series. With source available at: http://git.openstack.org/cgit/openstack/osprofiler With package available at: https://pypi.python.org/pypi/osprofiler

Re: [openstack-dev] [TripleO] additional git repo(s) for tripleo-quickstart

On Wed, Aug 10, 2016 at 9:45 PM, Lars Kellogg-Stedman wrote: > On Wed, Aug 10, 2016 at 03:26:18PM -0400, Wesley Hayutin wrote: > > I'm proposing the creation of a repo called tripleo-quickstart-extras > that > > would contain some or all of the current third party roles used

Re: [openstack-dev] [puppet] [tripleo] Host configuration for CPUAffinity and IRQ Pinning

Hi, maybe [1] and [2]/[3]? [2]/[3] however states "On $::osfamily == 'RedHat', no attempt is made to manage /etc/sysconfig/irqbalance. This is arguably a bug." BR, Konstantin [1] https://github.com/camptocamp/puppet-systemd [2] https://forge.puppet.com/jhoblitt/irqbalance [3]

  1   2   >