Re: [openstack-dev] [ironic] [infra] RFC: consolidating and extending Ironic CI jobs

On 10/12/2016 05:01 AM, Dmitry Tantsur wrote: > Hi folks! > > I'd like to propose a plan on how to simultaneously extend the coverage of our > jobs and reduce their number. > > Currently, we're running one instance per job. This was reasonable when the > coreos-based IPA image was the default,

Re: [openstack-dev] [tripleo] Setting up to 3rd party CI OVB jobs

On Wed, Oct 12, 2016 at 1:32 PM, Dan Prince wrote: > On Fri, 2016-10-07 at 09:03 -0400, Paul Belanger wrote: >> Greetings, >> >> I wanted to propose a work item, that I am happy to spearhead, about >> setting up >> a 3rd party CI system for tripleo project. The work I am

Re: [openstack-dev] PTG from the Ops Perspective - a few short notes

Excerpts from Jaesuk Ahn's message of 2016-10-12 15:08:24 +: > It can be cheap if you are in the US. However, for Asia folks, it is not > that cheap considering it is all overseas travel. In addition, all-in-one > event like the current summit makes us much easier to get the travel fund > from

Re: [openstack-dev] [keystone][horizon] keystone/horizon integration session in barcelona

This sounds great! Thanks for organising, Steve. Rob On 11 October 2016 at 22:32, Richard Jones > wrote: Thanks, Steve, this will be a valuable session! On 12 October 2016 at 08:14, Steve Martinelli

[openstack-dev] [lbaas] [octavia] Proposing Lubosz Kosnik (diltram) as Octavia Core

+1 good choice! __ OpenStack Development Mailing List (not 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] [lbaas] [octavia] Proposing Lubosz Kosnik (diltram) as Octavia Core

That is quorum from the cores, welcome Lubosz! Michael On Wed, Oct 12, 2016 at 1:26 PM, Doug Wiegley wrote: > +1 > >> On Oct 10, 2016, at 3:40 PM, Brandon Logan >> wrote: >> >> +1 >> >> On Mon, 2016-10-10 at 13:06 -0700, Michael

Re: [openstack-dev] [all][tc] Exposing project team's metadata in README files

On 14:50 Oct 12, Flavio Percoco wrote: > Greetings, > > One of the common complains about the existing project organization in the big > tent is that it's difficult to wrap our heads around the many projects there > are, their current state (in/out the big tent), their tags, etc. > > This

Re: [openstack-dev] [rpm-packaging][chef][puppet][salt][openstack-ansible][HA][tripleo][kolla][fuel] Schema proposal for config file handling for services

Thomas, Kolla does not use systemd fies (bifrost may be different here – I am not certain). Kolla also does not use default configuration files that are shipped with distros. We find this model to be disruptive to reliable development. I get distros want to ship them and that’s fine by us.

Re: [openstack-dev] [tricircle]Tricricle cleanning

Great, all patches are ready now for Tricircle cleaning: Review and Merge order: 1.central and local plugin for l3: https://review.openstack.org/#/c/378476/ 2. remove api gateway code: https://review.openstack.org/#/c/384182/ 3. security group support: https://review.openstack.org/#/c/380054/

Re: [openstack-dev] [devstack] devstack-plugin additional-pkg-repos: ocata summit working session?

On 12.10.2016 10:52, Kashyap Chamarthy wrote: > On Tue, Oct 11, 2016 at 05:53:24PM +0200, Thomas Goirand wrote: >> On 10/11/2016 02:09 PM, Markus Zoeller wrote: >>> * How to create a "*.deb" package out of the source code of >>> libvirt/qemu? (surprisingly enough, I'm still struggling with this)

Re: [openstack-dev] [telemetry][gnocchi]gnocchi resource id has been SHA-1, How to find the resources belong to the monitored items?

On Wed, Oct 12 2016, 冯朝阳 wrote: > such as(The following example is used gnocchi version = 1.3 (L version)): > # gnocchi resource list > a23d72a8-6fa3-545a-8b66-e512cac3aea3 | instance_network_interface | > 12fc4501-8408-43b2-8cb7-6f1e1462d80e | 48d883ba-76d0-4e30-ac6b-ab85d1041c96 | >

Re: [openstack-dev] [tripleo] PTG space request

Emilien Macchi wrote: > I would like to request for some space dedicated to TripleO project > for the first OpenStack PTG. > > https://www.openstack.org/ptg/ > > The event will happen in February 2017 during the next PTG in Atlanta. > Any feedback is welcome, Just a quick note: as you can

Re: [openstack-dev] [QA] Presence at PTG Atlanta in February

Masayuki Igawa wrote: > Hi Ken'ichi, > > Thanks for bring this up. > > On Tue, Oct 11, 2016 at 6:50 AM, Ken'ichi Ohmichi > wrote: >> Hi QA team, >> >> As you know, the first PTG(Project Teams Gathering) happens at Atlanta >> 20th-24th February the next year. >> After

Re: [openstack-dev] [telemetry][gnocchi]gnocchi resource id has been SHA-1, How to find the resources belong to the monitored items?

On Wed, Oct 12 2016, 冯朝阳 wrote: > Thank you very much for your reply, Julien! > We are using the openstack version is liberty(gnocchi version=1.3), no > original_resource_id, Can you tell me what I should do? You should upgrade. :-) Indeed, this original_resource_id has been introduced after 1.3

[openstack-dev] [tricircle]agenda of weekly meeting Oct.12

Agenda of Oct.12 weekly meeting: # Ocata cycle design summit sessions: [1][2] # Atlanta PTG(project team gather) presence # release for stable/newton and tricircle cleaning # open discussion [1]https://www.openstack.org/summit/barcelona-2016/summit-schedule/global-search?t=Tricircle%3A

Re: [openstack-dev] [devstack] devstack-plugin additional-pkg-repos: ocata summit working session?

On 11.10.2016 16:09, Kashyap Chamarthy wrote: > On Tue, Oct 11, 2016 at 02:09:33PM +0200, Markus Zoeller wrote: > > [Snip well-written backrgound detail] > >> Request >> --- >> My question is, if you have interest in this plugin and its >> capabilities, are you at the Summit in Barcelona and

Re: [openstack-dev] PTG from the Ops Perspective - a few short notes

Excerpts from Steven Dake (stdake)'s message of 2016-10-12 06:42:43 +: > Tom, > > No flame, just observation about the reality of these changes. > > I think we missed this communication on the mailing list or in the FAQs or > somewhere else. I think most engineering-focused organizations

Re: [openstack-dev] [QA] Presence at PTG Atlanta in February

Hi Ken'ichi, Thanks for bring this up. On Tue, Oct 11, 2016 at 6:50 AM, Ken'ichi Ohmichi wrote: > Hi QA team, > > As you know, the first PTG(Project Teams Gathering) happens at Atlanta > 20th-24th February the next year. > After Barcelona, OpenStack Summit will be

Re: [openstack-dev] [elections][tc]Thoughts on the TC election process

Ed Leafe wrote: > Why do we need a week to nominate? Open it up a month before the election, > and close it a week before. Or open it for two days, and close it a week > before. I don’t understand why, other than procrastination, we need such a > long period. If you’re serious about serving,

Re: [openstack-dev] PTG from the Ops Perspective - a few short notes

On Tue, Oct 11, 2016 at 10:39:11PM -0500, Michał Jastrzębski wrote: > Hello Tom, > > I must say I think this is bad news - especially for projects like > Kolla - ops centric. > One of reasons we created PTG in the first place is that Summit became > big and expensive, and project developers had

Re: [openstack-dev] [all][tc] Cross Project workshops in Barcelona including "Re-inventing the TC"

Davanum Srinivas wrote: > Please see the cross project schedule over at: > https://www.openstack.org/summit/barcelona-2016/summit-schedule/global-search?t=Cross%20Project%20workshops%3A Note that following the TC meeting yesterday, a small adjustment was pushed to fix a conflict for one of the

Re: [openstack-dev] [QA] Presence at PTG Atlanta in February

Thank you for clarifying Thierry! I got it! I'm looking forward to see the registration:) Best Regards, -- Masayuki Igawa On Wed, 12 Oct 2016 at 18:46 Thierry Carrez wrote: > Masayuki Igawa wrote: > > Hi Ken'ichi, > > > > Thanks for bring this up. > > > > On Tue, Oct 11,

Re: [openstack-dev] [networking-sfc][devstack][mitaka]

Hi Cathy, Thanks for your reply. I have the setup done without any errors with only one vm in the chain. I want to move all the icmp traffic from vm1 to vm3 via vm2. My Flow classifier looks like: "neutron flow-classifier-create --ethertype IPv4 --source-ip-prefix 10.0.0.18/32

[openstack-dev] [tripleo] Default the HA scenario to Ceph

hi, we introduced support for the deployment of Ceph in the liberty release so that it could optionally be used as backend for one or more of Cinder, Glance, Nova and more recently Gnocchi. We used to deploy Ceph MONs on the controller nodes and Ceph OSDs on dedicated ceph-storage nodes so

Re: [openstack-dev] [tricircle]Tricricle cleanning

Hello, patch for installation guide update of multi-node deployment has just been submitted. Here is the link: https://review.openstack.org/#/c/385306/ BR Zhiyuan On Wed, 12 Oct 2016 at 10:17 joehuang wrote: > Hello, Team, > > Understand this period is keeping us quite

Re: [openstack-dev] Event notification descriptors/schemas (? swagger ?)

On Tue, Oct 11 2016, Joshua Harlow wrote: > Has there been any ideas from folks to split those 'event_definitions.yaml' > into something else (a notifications schema repo?)? I'd be up for helping do > that (nice to have would be an included ability/code-gen(?) to turn those > schemas into code

Re: [openstack-dev] [tripleo] Default the HA scenario to Ceph

On Wed, Oct 12 2016, Giulio Fidente wrote: > Also using Swift as backend for Glance and Gnocchi is enough to cover the > availability issue for the data, but it also means we're storing that data on > the controller nodes which might or might not be wanted; I don't see a strong > reason for

Re: [openstack-dev] [devstack] devstack-plugin additional-pkg-repos: ocata summit working session?

On Tue, Oct 11, 2016 at 05:53:24PM +0200, Thomas Goirand wrote: > On 10/11/2016 02:09 PM, Markus Zoeller wrote: > > * How to create a "*.deb" package out of the source code of > > libvirt/qemu? (surprisingly enough, I'm still struggling with this) > > What version of libvirt / qemu are you trying

[openstack-dev] [telemetry][gnocchi]gnocchi resource id has been SHA-1, How to find the resources belong to the monitored items?

Hello All, When the ceilometer sent over the data to gnocchi, Gnocchi will use uuid.uuid5 for resource id, how to find it through the resource id belongs to the virtual machine, monitoring items? Will not be able to deal with resource id? such as(The following example is used gnocchi version

Re: [openstack-dev] PTG from the Ops Perspective - a few short notes

Qiming Teng wrote: > On Tue, Oct 11, 2016 at 10:39:11PM -0500, Michał Jastrzębski wrote: >> One of reasons we created PTG in the first place is that Summit became >> big and expensive, and project developers had harder and harder time >> attending it due to budget issues. > > So a trip to PTG is

Re: [openstack-dev] PTG from the Ops Perspective - a few short notes

On 10/12/2016 11:59 AM, Thierry Carrez wrote: Qiming Teng wrote: On Tue, Oct 11, 2016 at 10:39:11PM -0500, Michał Jastrzębski wrote: One of reasons we created PTG in the first place is that Summit became big and expensive, and project developers had harder and harder time attending it due to

Re: [openstack-dev] [telemetry][gnocchi]gnocchi resource id has been SHA-1, How to find the resources belong to the monitored items?

Thank you very much for your reply, Julien! We are using the openstack version is liberty(gnocchi version=1.3), no original_resource_id, Can you tell me what I should do? -- Original -- From: "Julien Danjou"; Date: Wed, Oct 12, 2016

Re: [openstack-dev] [release][ansible][fuel][kolla][puppet][tripleo] proposed deadlines for cycle-trailing projects

Excerpts from Steven Dake (stdake)'s message of 2016-10-07 20:39:04 +: > Doug, > > We have already tagged rc1 long ago, but ack on rc2 (we are targeting 12th at > present) and ack on 20th for retag of final rc. We expect our rc2 to be > final. Right, I should have phrased that as a

[openstack-dev] [ironic] [infra] RFC: consolidating and extending Ironic CI jobs

Hi folks! I'd like to propose a plan on how to simultaneously extend the coverage of our jobs and reduce their number. Currently, we're running one instance per job. This was reasonable when the coreos-based IPA image was the default, but now with tinyipa we can run up to 7 instances (and

Re: [openstack-dev] [tripleo] Default the HA scenario to Ceph

On 10/12/2016 07:10 AM, Giulio Fidente wrote: hi, we introduced support for the deployment of Ceph in the liberty release so that it could optionally be used as backend for one or more of Cinder, Glance, Nova and more recently Gnocchi. We used to deploy Ceph MONs on the controller nodes

Re: [openstack-dev] PTG from the Ops Perspective - a few short notes

On Wed, 12 Oct 2016, Clint Byrum wrote: So, while I do want to make sure enough of our architects and designers go to the summit to truly understand user needs, I also think it has been proven ineffective to also throw all of the coders into that mix and expect them to be productive. I

Re: [openstack-dev] [all][tc] Exposing project team's metadata in README files

Excerpts from Flavio Percoco's message of 2016-10-12 14:50:03 +0200: > Greetings, > > One of the common complains about the existing project organization in the big > tent is that it's difficult to wrap our heads around the many projects there > are, their current state (in/out the big tent),

Re: [openstack-dev] PTG from the Ops Perspective - a few short notes

  -Original Message- From: Chris Dent Reply: OpenStack Development Mailing List (not for usage questions) Date: October 12, 2016 at 09:10:45 To: OpenStack Development Mailing List (not for usage questions)

Re: [openstack-dev] [Zun] ERROR: Not Authorized

You right the log files should be there. So i went back to start the exercise afresh, so run the stack.sh script again And i realised it didn't finish because the database password was wrong and also connection problems. So After successfully running the file. i can now create containers

[openstack-dev] [api] [searchlight] Duplicate parameter names

Hi, This issue came up during our meeting last week and it was suggested to ask the API working group for its opinion, so any comments welcome. Searchlight was born out of the Glance codebase, and so implemented "offset" and "limit" as paging parameters [1]. Where possible we've tried to map

Re: [openstack-dev] [tripleo] Default the HA scenario to Ceph

On Wed, Oct 12, 2016 at 7:10 AM, Giulio Fidente wrote: > hi, > > we introduced support for the deployment of Ceph in the liberty release so > that it could optionally be used as backend for one or more of Cinder, > Glance, Nova and more recently Gnocchi. > > We used to deploy

Re: [openstack-dev] PTG from the Ops Perspective - a few short notes

Steve, Why just the one summit? Each cycle has a PTG and a summit, which makes 4 events per year. John From: "Steven Dake (stdake)" > Reply-To: "OpenStack Development Mailing List (not for usage questions)"

Re: [openstack-dev] [Doc] Inclusion of microversion API support in CLI reference

We added this patch to the cinderclient: b76f5944130e29ee1bf3095c966a393c489c05e6 Which basically only shows help for the features available at the requested API version. It is by design. From: Sean McGinnis Sent: Wednesday, October 12,

Re: [openstack-dev] PTG from the Ops Perspective - a few short notes

Clint, RE 3 - I do understand purpose of PTGs. Prior many engineering orgs didn’t send many people to midcycles (where a lot of work got done – more so than summit even). The 3 events are 2 PTGS + 1 summit (although I don’t know the length of the PTGs) Regards -steve From: Clint Byrum

Re: [openstack-dev] PTG from the Ops Perspective - a few short notes

It can be cheap if you are in the US. However, for Asia folks, it is not that cheap considering it is all overseas travel. In addition, all-in-one event like the current summit makes us much easier to get the travel fund from the company, since the company only need to send everyone (tech, ops,

Re: [openstack-dev] [all][tc] Exposing project team's metadata in README files

I've been interacting recently with several new contributors (to Trove) and I can certainly attest to the fact that people appear to browse the source repository and read the README's. Flavio makes a good point that it would be good to provide a short summary of the project's capabilities in

Re: [openstack-dev] [tripleo] PTG space request

On Wed, Oct 12, 2016 at 5:28 AM, Thierry Carrez wrote: > Emilien Macchi wrote: >> I would like to request for some space dedicated to TripleO project >> for the first OpenStack PTG. >> >> https://www.openstack.org/ptg/ >> >> The event will happen in February 2017 during the

Re: [openstack-dev] [ovn][neutron] networking-ovn 1.0.0 release (newton) -- port-security

Murali R wrote on 10/11/2016 01:47:24 PM: > From: Murali R > To: "OpenStack Development Mailing List (not for usage questions)" > , discuss > Date: 10/11/2016 01:50 PM > Subject:

Re: [openstack-dev] [release][ansible][fuel][kolla][puppet][tripleo] proposed deadlines for cycle-trailing projects

Excerpts from Alexey Shtokolov's message of 2016-10-11 00:18:24 +0300: > Doug, > > We've finally fixed the blockers and tagged RC1 for all our repos. > We're going to have final RC this Friday (Oct14). > > Could I ask you to create stable/newton branches for repos: > - openstack/fuel-agent > -

Re: [openstack-dev] [all][tc] Exposing project team's metadata in README files

On 12/10/2016 16:08, Doug Hellmann wrote: > Excerpts from Flavio Percoco's message of 2016-10-12 14:50:03 +0200: >> Greetings, >> >> One of the common complains about the existing project organization in the >> big >> tent is that it's difficult to wrap our heads around the many projects there >>

[openstack-dev] [sahara][qa] Unblocking Sahara gate

Hi all, the removal of the Sahara tests from Tempest [1] broke the tests now in sahara-tests, and basically I underestimated the fall-out of the removal. Apart from a minor issue due to the wrong exception [2], the key issue comes from the option groups in tempest.conf, which are defined as

Re: [openstack-dev] [ironic] [infra] RFC: consolidating and extending Ironic CI jobs

On Wed, Oct 12, 2016 at 4:10 PM, Dmitry Tantsur wrote: > On 10/12/2016 03:01 PM, Vasyl Saienko wrote: > >> Hello Dmitry, >> >> Thanks for raising this question. I think the problem is deeper. There >> are a lot >> of use-cases that are not covered by our CI like cleaning,

Re: [openstack-dev] [tripleo] Default the HA scenario to Ceph

On 10/12/2016 06:10 AM, Giulio Fidente wrote: hi, we introduced support for the deployment of Ceph in the liberty release so that it could optionally be used as backend for one or more of Cinder, Glance, Nova and more recently Gnocchi. We used to deploy Ceph MONs on the controller nodes and

Re: [openstack-dev] [ironic] [infra] RFC: consolidating and extending Ironic CI jobs

On 10/12/2016 04:02 PM, Jim Rollenhagen wrote: On Wed, Oct 12, 2016 at 8:01 AM, Dmitry Tantsur wrote: Hi folks! I'd like to propose a plan on how to simultaneously extend the coverage of our jobs and reduce their number. Currently, we're running one instance per job.

Re: [openstack-dev] PTG from the Ops Perspective - a few short notes

On 12 October 2016 at 08:53, John Davidge wrote: > On 10/12/16, 11:18 AM, Dmitry Tantsur wrote: > >>On 10/12/2016 11:59 AM, Thierry Carrez wrote: >>> >>> PTGs happen in more cost-effective locations, airport hubs with cheaper >>> hotels, which should lower the cost of

Re: [openstack-dev] [ironic] [infra] RFC: consolidating and extending Ironic CI jobs

On Wed, Oct 12, 2016 at 8:01 AM, Dmitry Tantsur wrote: > Hi folks! > > I'd like to propose a plan on how to simultaneously extend the coverage of > our jobs and reduce their number. > > Currently, we're running one instance per job. This was reasonable when the > coreos-based

Re: [openstack-dev] [ironic] [infra] RFC: consolidating and extending Ironic CI jobs

On 10/12/2016 03:01 PM, Vasyl Saienko wrote: Hello Dmitry, Thanks for raising this question. I think the problem is deeper. There are a lot of use-cases that are not covered by our CI like cleaning, adoption etc... This is nice, but here I'm trying to solve a pretty specific problem: we can't

Re: [openstack-dev] PTG from the Ops Perspective - a few short notes

On 10/12/16, 11:18 AM, Dmitry Tantsur wrote: >On 10/12/2016 11:59 AM, Thierry Carrez wrote: >> >> PTGs happen in more cost-effective locations, airport hubs with cheaper >> hotels, which should lower the cost of attending. Yes, I'm pretty sure >> traveling to Atlanta downtown for a week will be

Re: [openstack-dev] [elections][tc]Thoughts on the TC election process

Top-posting as I'll try to summarize/re-start/reword/whatever the right word is, this thread: It seems to me that the problem we're trying to solve here is how we can help voters to make more thoughtful choices (note that I'm not saying they currently don't. I'm not judging the voters but, as

Re: [openstack-dev] [heat] [magnum] Subjects to discuss during the summit

On 10/10/16 11:11, Spyros Trigazis wrote: 4. Finally, a thought under investigation is replacing the nodes one by one using a different image. e.g. Upgrade from fedora 24 to 25 with new versions of packages all in a new qcow2 image. How could we update the stack for this? This should

Re: [openstack-dev] [tripleo] Default the HA scenario to Ceph

On 10/12/2016 02:29 PM, Thiago da Silva wrote: On 10/12/2016 07:10 AM, Giulio Fidente wrote: hi, we introduced support for the deployment of Ceph in the liberty release so that it could optionally be used as backend for one or more of Cinder, Glance, Nova and more recently Gnocchi. We used

[openstack-dev] [all][tc] Exposing project team's metadata in README files

Greetings, One of the common complains about the existing project organization in the big tent is that it's difficult to wrap our heads around the many projects there are, their current state (in/out the big tent), their tags, etc. This information is available on the governance website[0].

[openstack-dev] [Doc] Inclusion of microversion API support in CLI reference

Just getting this out there to either get educated or to start a conversation... While going through some of the DocImpact generated bugs for python-cinderclient I noticed a few that added new parameters to existing CLI commands. As Cinder has now moved to using microversions for all API changes,

Re: [openstack-dev] [ironic] [infra] RFC: consolidating and extending Ironic CI jobs

Hello Dmitry, Thanks for raising this question. I think the problem is deeper. There are a lot of use-cases that are not covered by our CI like cleaning, adoption etc... The main problem is that we need to change ironic configuration to apply specific use-case. Unfortunately tempest doesn't

Re: [openstack-dev] [ironic] [infra] RFC: consolidating and extending Ironic CI jobs

On 10/12/2016 03:54 PM, Vasyl Saienko wrote: On Wed, Oct 12, 2016 at 4:10 PM, Dmitry Tantsur > wrote: On 10/12/2016 03:01 PM, Vasyl Saienko wrote: Hello Dmitry, Thanks for raising this question. I think the problem is

Re: [openstack-dev] [elections][tc]Thoughts on the TC election process

On Wed, Oct 5, 2016 at 4:09 PM Sean Dague wrote: > On 10/03/2016 12:46 PM, Edward Leafe wrote: > > > > > We are fortunate in that all of the candidates are exceptionally > well-qualified, and those elected have put in excellent service while on > the TC. But one thing I'm afraid

[openstack-dev] [nova] Nova New Contributor Update

During the Newton Design Summit the Nova team had a session regarding new contributor activities (https://etherpad.openstack.org/p/newton-nova-getting-started). We agreed that we should update the Mentoring wiki page (https://wiki.openstack.org/wiki/Nova/Mentoring) with a list of projects and

Re: [openstack-dev] [lbaas] [octavia] Proposing Lubosz Kosnik (diltram) as Octavia Core

+1 > On Oct 10, 2016, at 3:40 PM, Brandon Logan > wrote: > > +1 > > On Mon, 2016-10-10 at 13:06 -0700, Michael Johnson wrote: >> Greetings Octavia and developer mailing list folks, >> >> I propose that we add Lubosz Kosnik (diltram) as an OpenStack Octavia >>

Re: [openstack-dev] PTG from the Ops Perspective - a few short notes

Tom, No flame, just observation about the reality of these changes. I think we missed this communication on the mailing list or in the FAQs or somewhere else. I think most engineering-focused organizations are looking at the PTGs only and not really considering the summit for budget planning.

Re: [openstack-dev] [Karbor] Questions about algorithm of building resource graph

Hi karbor guys: Yesterday, I had discussed this question with other guys on the weekly meeting. Maybe I have not described the question clearly. Today, I discussed with chenying and reached an agreement with him. I update the question again in the attached file and hope for the ideas

Re: [openstack-dev] [Doc] Inclusion of microversion API support in CLI reference

On 10/12/2016 05:23 PM, Scott D'Angelo wrote: > We added this patch to the cinderclient: > > b76f5944130e29ee1bf3095c966a393c489c05e6 > > > Which basically only shows help for the features available at the > requested API version. It is by design. The question that Sean raises is how the user

Re: [openstack-dev] [ironic] [infra] RFC: consolidating and extending Ironic CI jobs

> On Oct 12, 2016, at 5:01 AM, Dmitry Tantsur wrote: > > Hi folks! > > I'd like to propose a plan on how to simultaneously extend the coverage of > our jobs and reduce their number. > > Currently, we're running one instance per job. This was reasonable when the >

Re: [openstack-dev] Multinode testing with devstack and neutron broken

Not much to add here - I commented in review.openstack.org/378063 that they could set the default value of the flag to revert behaviour. - Matt On Oct 11, 2016, at 10:21 PM, Armando M. > wrote: On 11 October 2016

Re: [openstack-dev] PTG from the Ops Perspective - a few short notes

> On Oct 12, 2016, at 4:09 AM, Qiming Teng wrote: > >> On Tue, Oct 11, 2016 at 10:39:11PM -0500, Michał Jastrzębski wrote: >> Hello Tom, >> >> I must say I think this is bad news - especially for projects like >> Kolla - ops centric. >> One of reasons we created

[openstack-dev] [TripleO][CI] Isolated Network Testing

I recently evaluated our needs for testing coverage for TripleO isolated networking. I wanted to post my thoughts on the matter for discussion, which will hopefully lead to a shared understanding of what improvements we need to make. I think we can cover the majority of end-user requirements by

Re: [openstack-dev] [all][tc] Exposing project team's metadata in README files

On 12/10/16 05:43 PM, Mike Perez wrote: > Besides the governance site, there is also the project navigator [1] which is > a more friendly landing page on projects and their tags. Although it does not > today capture separate deliverables. > > Assuming the README files aren't being manually

[openstack-dev] [new][networking-cisco]

The networking-cisco development team are grateful to announce the release of: networking-cisco 4.0.0 This release is compatible with OpenStack Mitaka and Newton Download the package from: https://pypi.python.org/pypi/networking-cisco

Re: [openstack-dev] [tripleo] PTG space request

> Emilien Macchi wrote: > > I would like to request for some space dedicated to TripleO project > > for the first OpenStack PTG. > > > > https://www.openstack.org/ptg/ > > > > The event will happen in February 2017 during the next PTG in Atlanta. > > Any feedback is welcome, > > Just a quick

[openstack-dev] [QA][Ironic]Removal of Ironic tests from Tempest

Hi guys, As you may know we are pushing projects to use Tempest plugins and we are only keeping "core" projects tests in Tempest tree. There has been several attempts to remove Ironic from Tempest so I guess it doesn't come as a surprise (hopefully). I am starting to work on the removal now, as

Re: [openstack-dev] [networking-sfc][devstack][mitaka]

Navdeep, Post port-chain, port-pair-group, port-pair config to questions at https://launchpad.net/networking-sfc Use these commands to determine traffic flow and post results also. sudo ovs-ofctl -O openflow13 dump-flows br-int sudo ovs-ofctl -O Openflow13 dump-groups br-int -

[openstack-dev] [all] planning the PTG -- lessons from Swift's midcycles

The Swift team has been doing midcycles for a while now, and as the new PTG gets closer, I want to write down our experience with what has worked for us. I hope it is beneficial to other teams, too. ## Logistics of the event - 2 rooms is ideal, but can make due with one larger room - move

Re: [openstack-dev] [ovs-discuss] [ovn][neutron] networking-ovn 1.0.0 release (newton) -- port-security

On Tue, Oct 11, 2016 at 2:47 PM, Murali R wrote: > Hi, > > Please clarify if port security is required to be enabled with newton > release when installing OVN. The install.rst says it must be. In many of my > use cases I want to disable port security which is how I do

Re: [openstack-dev] [tripleo] Setting up to 3rd party CI OVB jobs

On Fri, 2016-10-07 at 09:03 -0400, Paul Belanger wrote: > Greetings, > > I wanted to propose a work item, that I am happy to spearhead, about > setting up > a 3rd party CI system for tripleo project. The work I am proposing, > wouldn't > actually affect anything today about tripleo-ci but

Re: [openstack-dev] [QA][Ironic]Removal of Ironic tests from Tempest

On Wed, Oct 12, 2016 at 1:01 PM, Jordan Pittier wrote: > Hi guys, > As you may know we are pushing projects to use Tempest plugins and we are > only keeping "core" projects tests in Tempest tree. > > There has been several attempts to remove Ironic from Tempest so I

Re: [openstack-dev] [tripleo] Setting up to 3rd party CI OVB jobs

On Tue, Oct 11, 2016 at 05:37:54PM +0100, Derek Higgins wrote: > On 7 October 2016 at 14:03, Paul Belanger wrote: > > Greetings, > > > > I wanted to propose a work item, that I am happy to spearhead, about > > setting up > > a 3rd party CI system for tripleo project. The

Re: [openstack-dev] PTG from the Ops Perspective - a few short notes

Excerpts from Chris Dent's message of 2016-10-12 15:08:48 +0100: > On Wed, 12 Oct 2016, Clint Byrum wrote: > > > So, while I do want to make sure enough of our architects and designers > > go to the summit to truly understand user needs, I also think it has > > been proven ineffective to also

Re: [openstack-dev] [Doc] Inclusion of microversion API support in CLI reference

On 10/12/2016 03:03 PM, Sean McGinnis wrote: > Just getting this out there to either get educated or to start a > conversation... > > While going through some of the DocImpact generated bugs for > python-cinderclient I noticed a few that added new parameters to > existing CLI commands. As Cinder

Re: [openstack-dev] [ironic] [infra] RFC: consolidating and extending Ironic CI jobs

On 10/12/2016 05:53 PM, Jay Faulkner wrote: On Oct 12, 2016, at 5:01 AM, Dmitry Tantsur wrote: Hi folks! I'd like to propose a plan on how to simultaneously extend the coverage of our jobs and reduce their number. Currently, we're running one instance per job. This

Re: [openstack-dev] PTG from the Ops Perspective - a few short notes

Michał Jastrzębski wrote: > On 12 October 2016 at 08:53, John Davidge wrote: >> [...] >> Also, unless I've missed something, we still don't know the registration >> fees for the PTG and the new Summit do we? Last I remember, there was talk >> of a registration fee for

Re: [openstack-dev] [tripleo] Default the HA scenario to Ceph

On Wednesday, October 12, 2016, Emilien Macchi wrote: > On Wed, Oct 12, 2016 at 7:10 AM, Giulio Fidente > wrote: > > hi, > > > > we introduced support for the deployment of Ceph in the liberty release > so > > that it could optionally be

Re: [openstack-dev] [elections][tc]Thoughts on the TC election process

On Wed, Oct 12, 2016 at 02:16:42PM +0200, Flavio Percoco wrote: > Top-posting as I'll try to summarize/re-start/reword/whatever the right word > is, > this thread: > > It seems to me that the problem we're trying to solve here is how we can help > voters to make more thoughtful choices (note

Re: [openstack-dev] [devstack] devstack-plugin additional-pkg-repos: ocata summit working session?

On Tue, Oct 11, 2016 at 05:53:24PM +0200, Thomas Goirand wrote: > On 10/11/2016 02:09 PM, Markus Zoeller wrote: > > * How to create a "*.deb" package out of the source code of > > libvirt/qemu? (surprisingly enough, I'm still struggling with this) > > What version of libvirt / qemu are you trying

[openstack-dev] [gnocchi] host field information flapping for instance resource-type

Hi all! We've been trying to get gnocchi working us, and have been hitting some performance bottlenecks. It seems that the 'host' field for the instance resource-type flaps between host id and host names. This makes the gnocchi dispatcher calls an update per resource which is a HTTP PATCH call.

Re: [openstack-dev] PTG from the Ops Perspective - a few short notes

For most of contributors in the Tricircle project from Asia, I would like to know whether it's possible for the project to have PTG in Asia somewhere before the PTG in Atlanta, and then some representatives from the project to attend the PTG in Atlanta if there are cross project topics to be

[openstack-dev] [vitrage] about aodh notifier to create a event alarm

Hi vitrages, In aodh notifier plugin, we receive a ACTIVATE_DEDUCED_ALARM_EVENT and then create a aodh event alarm. The event alarm with a `event_rule`, it should be include `event_type` and `query` which Aodh used to evaluator a alarm when it receives a specify event to filter with the query

Re: [openstack-dev] [devstack] devstack-plugin additional-pkg-repos: ocata summit working session?

On Tue, Oct 11, 2016 at 02:09:33PM +0200, Markus Zoeller wrote: > Backstory > - > Some time ago, tonyb and I started the work on a gate testing job which > can install additional packages onto the testing node: I think it'd be great to talk about and get a few people interested in helping

Re: [openstack-dev] Event notification descriptors/schemas (? swagger ?)

Julien Danjou wrote: On Tue, Oct 11 2016, Joshua Harlow wrote: Has there been any ideas from folks to split those 'event_definitions.yaml' into something else (a notifications schema repo?)? I'd be up for helping do that (nice to have would be an included ability/code-gen(?) to turn those

Re: [openstack-dev] [devstack] devstack-plugin additional-pkg-repos: ocata summit working session?

On Wed, Oct 12, 2016 at 10:52:25AM +0200, Kashyap Chamarthy wrote: > I think what Markus is talking about is to the ability to produce > packages from arbitrary Git commits to be able to test Nova with certain > new features from libvirt / QEMU which won't be available until a formal > release is