[openstack-dev] [neutron]: Neutron naming legal issues

Dear Neutrinos, We've been following the project for quite some time. To our satisfaction the project seems to have done well; the base line of features that were available to the networking component of OpenStack (then nova-network) has grown quite a bit and seem to have gained a successful

Re: [openstack-dev] [nova] API priorities in Newton

On Thu, Mar 31, 2016 at 4:47 AM, Matthew Treinish wrote: > On Wed, Mar 30, 2016 at 03:26:13PM -0400, Sean Dague wrote: >> During the Nova API meeting we had some conversations about priorities, >> but this feels like the thing where a mailing list conversation is more >>

Re: [openstack-dev] [searchlight] Add Nova Keypair Plugin

Hiroyuki, Thanks for the update. That sounds like the best course of action. As FYI, Li Yingjun also has a spec up on Nova to get notifications on hypervisors [0], which we briefly discussed in the IRC meeting this morning [1]. The two of you might be able to work together in getting nova

Re: [openstack-dev] [magnum] Proposing Eli Qiao for Magnum core reviewer team

+1 from me. Thanks Eli for your contribution. Regards, Madhuri From: Yuanying OTSUKA [mailto:yuany...@oeilvert.org] Sent: Friday, April 1, 2016 8:13 AM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [magnum]

Re: [openstack-dev] [magnum] Proposing Eli Qiao for Magnum core reviewer team

+1 for Eli Thanks -Yuanying 2016年4月1日(金) 10:59 王华 : > +1 for Eli. > > Best Regards, > Wanghua > > On Fri, Apr 1, 2016 at 9:51 AM, Duan, Li-Gong (Gary, > HPServers-Core-OE-PSC) wrote: > >> +1 for Eli. >> >> >> >> Regards, >> >> Gary Duan >> >> >>

[openstack-dev] [tricircle] cross openstack L2 networking

Hi, Not found you in #openstack-tricircle. We are discussing cross openstack L2 networking in as scheduled in weekly meeting: https://etherpad.openstack.org/p/TricircleCrossPodL2Networking Best Regards Chaoyi Huang ( Joe Huang ) -Original Message- From: Shinobu Kinjo

Re: [openstack-dev] [searchlight] Add Nova Keypair Plugin

Hi Steve Thank you for your advice. Currently It's impossible to sync keystone information between DB and ElasticeSearch. And no useful notification will be send for kaypair state change.(only key_name) So, I try to propose improving keypair notifications against nova-specs. Thanks. Hiroyuki

Re: [openstack-dev] [magnum] Proposing Eli Qiao for Magnum core reviewer team

+1 for Eli. Best Regards, Wanghua On Fri, Apr 1, 2016 at 9:51 AM, Duan, Li-Gong (Gary, HPServers-Core-OE-PSC) wrote: > +1 for Eli. > > > > Regards, > > Gary Duan > > > > *From:* Hongbin Lu [mailto:hongbin...@huawei.com] > *Sent:* Friday, April 01, 2016 2:18 AM > *To:*

Re: [openstack-dev] [magnum] Proposing Eli Qiao for Magnum core reviewer team

+1 for Eli. Regards, Gary Duan From: Hongbin Lu [mailto:hongbin...@huawei.com] Sent: Friday, April 01, 2016 2:18 AM To: OpenStack Development Mailing List (not for usage questions) Subject: [openstack-dev] [magnum] Proposing Eli Qiao for Magnum core reviewer

Re: [openstack-dev] [All][Neutron] Improving development and review velocity - Is it time for a drastic change?

And now I wish I could delete my messages sent to ML. On 3/31/16 9:38 PM, Nikhil Komawar wrote: > 2) is a giveaway it's Apr 1 (in some TZs)! > > > On 3/31/16 9:12 PM, Assaf Muller wrote: >> Have you been negatively impacted by slow development and review >> velocity? Read on. >> >> OpenStack has

Re: [openstack-dev] [All][Neutron] Improving development and review velocity - Is it time for a drastic change?

On Fri, Apr 1, 2016 at 10:12 AM, Assaf Muller wrote: > Have you been negatively impacted by slow development and review > velocity? Read on. > > OpenStack has had a slow review velocity for as long as I can > remember. This has a cascading effect where people take up multiple >

Re: [openstack-dev] [All][Neutron] Improving development and review velocity - Is it time for a drastic change?

2) is a giveaway it's Apr 1 (in some TZs)! On 3/31/16 9:12 PM, Assaf Muller wrote: > Have you been negatively impacted by slow development and review > velocity? Read on. > > OpenStack has had a slow review velocity for as long as I can > remember. This has a cascading effect where people take

[openstack-dev] [refstack] configuration user story

Per our discussion at midcycle, I had submitted user story for configuration info use cases. https://review.openstack.org/#/c/300057/ Looking forward to reviews. Once user story settles we will start the work on blueprints. Thanks, Arkady Arkady Kanevsky, Ph.D. Director of SW Development Dell

Re: [openstack-dev] 答复: [Heat] Re-evaluate conditions specification

On 31/03/16 18:10, Zane Bitter wrote: I'm in favour of some sort of variable-based implementation for a few reasons. One is that (5) seems to come up fairly regularly in a complex deployment like TripleO. Another is that Fn::If feels awkward compared to get_variable. I actually have to revise

[openstack-dev] What's Up, Doc? Mitaka Release Edition

Hi everyone, While it was very tempting to write something something shocking here for April Fools', I thought everyone might have already had their heart rate raised enough by the fact that Mitaka is only five days away! This will be my final docs newsletter before the release, and the docs

[openstack-dev] [All][Neutron] Improving development and review velocity - Is it time for a drastic change?

Have you been negatively impacted by slow development and review velocity? Read on. OpenStack has had a slow review velocity for as long as I can remember. This has a cascading effect where people take up multiple tasks, so that they can work on something while the other is being reviewed. This

[openstack-dev] [Neutron] Adding amuller to the neutron-drivers team

Hi folks, Assaf's tenacity is a great asset for the Neutron team at large. I believe that the drivers team would benefit from that tenacity, and therefore I would like to announce him to be a new member of the Neutron Drivers team [1]. At the same time, I would like to thanks mestery as he steps

[openstack-dev] [all][elections] Voting for the TC Election is now open

Voting for the TC Election is now open and will remain open until 23:59 April 7th, 2016 UTC. We are selecting 7 TC members, please rank all candidates in your order of preference. You are eligible to vote if you are a Foundation individual member[2] that also has committed to one of the official

[openstack-dev] [Docs] Austin Design Summit Sessions - Docs

Hi everyone, First of all, thanks for the amazing feedback on what docs sessions you would like to see at the Austin Design Summit! We have filled our entire allocation (and then some), and the schedule so far looks something like this: Fishbowls (40 min slot) x 4 Mitaka retro - Wed 11

[openstack-dev] [election][tc] tc candidacy

hi folks, i'd like to announce my candidacy for the OpenStack Technical Committee. as a quick introduction, i've been a contributor in OpenStack for the past few years, focused primarily on various Telemetry and Oslo related projects. i was recently the Project Team Liaison for the Telemetry

[openstack-dev] [release][designate] Designate Mitaka RC2 available

Due to release-critical issues spotted in Designate during RC1 testing, a new release candidate was created for Mitaka. You can find the RC2 source code tarball at: https://tarballs.openstack.org/designate/designate-2.0.0.0rc2.tar.gz Unless new release-critical issues are found that warrant a

Re: [openstack-dev] Floating IPs and Public IPs are not equivalent

Cross posting to the Ops ML as one/some of them might have a test cloud like this. Operators: If you respond to this thread, please only respond to the openstack-dev list? They could use your input;-) --Rocky -Original Message- From: Sean Dague [mailto:s...@dague.net] Sent:

Re: [openstack-dev] [all] Newton Summit: cross-project session for deployment tools projects

Good idea Emilien! Working in both tripleo and Kolla, I'd like to be a part of the conversation. -Ryan - Original Message - From: "Samuel Cassiba" To: "OpenStack Development Mailing List (not for usage questions)" Sent: Thursday,

Re: [openstack-dev] 答复: [Heat] Re-evaluate conditions specification

On 31/03/16 10:10, Thomas Herve wrote: On Thu, Mar 31, 2016 at 2:25 PM, Huangtianhua wrote: The conditions function has been requested for a long time, and there have been several previous discussions, which all ended up in debating the implementation, and no result.

Re: [openstack-dev] [TripleO][Heat][Kolla][Magnum] The zen of Heat, containers, and the future of TripleO

Kevin, This is how our playbooks are designed to operate (using serial 30%) but it is unclear if workloads can be scheduled during this upgrade because I haven't personally seen it tested with Kolla yet. I have only tested upgrades with vms and no workload which works fantastically well.

Re: [openstack-dev] [all] Newton Summit: cross-project session for deployment tools projects

On Thu, Mar 31, 2016 at 2:40 PM, Emilien Macchi wrote: > Hi, > > OpenStack big tent has different projects for deployments: Puppet, > Chef, Ansible, Kolla, TripleO, (...) but we still have some topics in > common. > I propose we use the Cross-project day to meet and talk

Re: [openstack-dev] [all] Newton Summit: cross-project session for deployment tools projects

Ahh I never run from good flame war;) Just kidding ofc. I personally think this is brilliant and should be somewhat tradition per release as we all deal with things like upgrades and deployment changes (yes, I'm looking at you nova-api-database). Please consider me a volunteer from Kolla:)

Re: [openstack-dev] [all] Newton Summit: cross-project session for deployment tools projects

On 31 March 2016 at 22:40, Emilien Macchi wrote: > > OpenStack big tent has different projects for deployments: Puppet, > Chef, Ansible, Kolla, TripleO, (...) but we still have some topics in > common. > I propose we use the Cross-project day to meet and talk about our >

Re: [openstack-dev] [all] Newton Summit: cross-project session for deployment tools projects

+1 This is great and I look forward to meeting and talking with folks at the summit. On 03/31/2016 04:42 PM, Emilien Macchi wrote: > Hi, > > OpenStack big tent has different projects for deployments: Puppet, > Chef, Ansible, Kolla, TripleO, (...) but we still have some topics in > common. > I

[openstack-dev] [all] Newton Summit: cross-project session for deployment tools projects

Hi, OpenStack big tent has different projects for deployments: Puppet, Chef, Ansible, Kolla, TripleO, (...) but we still have some topics in common. I propose we use the Cross-project day to meet and talk about our common topics: CI, doc, release, backward compatibility management, etc. Feel

[openstack-dev] [Glance] Newton virtual pre-summit sync

Hi all, I'm excited to see you all Glancers at the Austin summit and discuss more on our project. Nevertheless, I feel that our summit conversations will have a lot more value if we establish some prior-context to the discussions and prepare ourselves for some of the sessions. Hence, I would

Re: [openstack-dev] [magnum] Proposing Eli Qiao for Magnum core reviewer team

+1 On Mar 31, 2016, at 11:18 AM, Hongbin Lu > wrote: Hi all, Eli Qiao has been consistently contributed to Magnum for a while. His contribution started from about 10 months ago. Along the way, he implemented several important blueprints and

Re: [openstack-dev] [magnum] Proposing Eli Qiao for Magnum core reviewer team

+1 On Mar 31, 2016, at 11:18 AM, Hongbin Lu > wrote: Hi all, Eli Qiao has been consistently contributed to Magnum for a while. His contribution started from about 10 months ago. Along the way, he implemented several important blueprints and

Re: [openstack-dev] [release][all][ptls] the plan for the final week of the Mitaka release

On 3/30/2016 8:03 AM, Doug Hellmann wrote: Folks, We are approaching the final week of the Mitaka release cycle, and the release team wants to make sure everyone is clear about what will be happening and what the policies for changes are. First, a few dates: * Tomorrow 31 March is the

[openstack-dev] [release][stable][winstackers] os-win 0.4.1 release (mitaka)

We are pleased to announce the release of: os-win 0.4.1: Windows / Hyper-V library for OpenStack projects. This release is part of the mitaka stable release series. With source available at: http://git.openstack.org/cgit/openstack/os-win Please report issues through launchpad:

Re: [openstack-dev] [Neutron] Segments, subnet types, and IPAM

On 03/28/2016 07:17 PM, Carl Baldwin wrote: On Fri, Mar 11, 2016 at 10:04 PM, Salvatore Orlando wrote: On 11 March 2016 at 23:15, Carl Baldwin wrote: I wonder if we could satisfy this requirement with tags - as it seems these subnets are anyway

[openstack-dev] [Mistral] Mitaka RC2 available

Hi, OpenStackers: Due to release-critical issues spotted in Mistral during RC1 testing, a new release candidate was created for Mitaka. You can find the RC2 source code tarballs at: https://tarballs.openstack.org/mistral/mistral-2.0.0.0rc2.tar.gz Unless new release-critical issues are found

Re: [openstack-dev] [election][tc] Not Running for Re-Election

Excerpts from Mark McClain's message of 2016-03-31 16:17:42 -0400: > All- > > I wanted to drop a note to let everyone know that I will not seek re-election > to the TC for this cycle. I’ve really enjoyed working with everyone in our > community through the TC the past three years. I’m super

[openstack-dev] [fuel][ConfigDB] Separating node and cluster serialized data

One of the problems we've faced with trying to plug-in ConfigDB is trying to separate the cluster attributes from the node attributes in the serialized output (ie astute.yaml) I started talking with Alex S about how we could separate them after astute.yaml is prepared trying to ensure which was

[openstack-dev] [election][tc] Not Running for Re-Election

All- I wanted to drop a note to let everyone know that I will not seek re-election to the TC for this cycle. I’ve really enjoyed working with everyone in our community through the TC the past three years. I’m super excited by the candidates who are running where they’ll lead our community.

[openstack-dev] [tc][election] TC Candidacy

Hi Everyone, I'd like to submit my candidacy for the OpenStack Technical Committee. I've been involved with OpenStack since the Folsom cycle. In that time I've worked on a lot of varied parts of OpenStack. During this time I have started and led several key initiatives and projects (mostly

Re: [openstack-dev] Floating IPs and Public IPs are not equivalent

On 03/31/2016 01:23 PM, Monty Taylor wrote: > Just a friendly reminder to everyone - floating IPs are not synonymous > with Public IPs in OpenStack. > > The most common (and growing, thank you to the beta of the new > Dreamcompute cloud) configuration for Public Clouds is directly assign > public

[openstack-dev] [all] Cross Project Session proposals due by Apr 2nd

Reminder that cross project session proposals are due by Apr 2nd - https://etherpad.openstack.org/p/newton-cross-project-sessions We've got 15 proposals at this point, and I expect a bunch to come in later this week. Also, if you aren't sure whether or not your proposal is "cross project

Re: [openstack-dev] [kolla][tc] [security] threat analysis, tags, and the road ahead

Including tc and kolla Michael, Sounds good. I'll get the governance changes rolling for debate at the next TC meeting. Note I added this cross project topic for discussion Tuesday at summit (last item in the list) https://etherpad.openstack.org/p/newton-cross-project-sessions Regards, -steve

[openstack-dev] [election][tc] TC Candidacy

Friends, Colleagues, and Fellow Community Members, lend me your ears (or eyes as the case may be). I am pleased to submit for your consideration my candidacy for the technical committee (TC). You may know me from such projects as Keystone, and the “From Camera to Couch” segment of Jonathan

[openstack-dev] [security] threat analysis, tags, and the road ahead

hey all, at the most recent ossp meeting[1], there was some extended discussion about threat analysis and the work that is being done to push this forward. in this discussion, there were several topics brought up around the process for doing these analyses on current projects and how the

Re: [openstack-dev] [magnum] Proposing Eli Qiao for Magnum core reviewer team

+1 for Eli Ton Ngo, From: Hongbin Lu To: "OpenStack Development Mailing List (not for usage questions)" Date: 03/31/2016 11:21 AM Subject:[openstack-dev] [magnum] Proposing Eli Qiao for Magnum core

[openstack-dev] PTL communication of offline time

I proposed a resolution to the TC regarding PTL leave of absences, outlining a workflow of communication: https://review.openstack.org/#/c/290141/ The proposal was struck down in favour of a change to the Project Team Guide: https://review.openstack.org/#/c/293170/ I recently was contacted by a

Re: [openstack-dev] [neutron] OVSDB native interface as default in gate jobs

On Tue, Mar 29, 2016, at 07:34 PM, Kevin Benton wrote: > I'm not aware of any issues. Perhaps you can propose a patch to just > change > the default in Neutron to that interface and people can -1 if there are > any > concerns. Yes, please do. This is one of the nice things about pre merge

Re: [openstack-dev] [TC] TC Non-candidancy

Excerpts from Robert Collins's message of 2016-03-31 15:56:33 +1300: > Hi everyone - I'm not submitting my hat for the ring this cycle - I > think its important we both share the work, and bring more folk up > into the position of having-been-on-the-TC. I promise to still hold > strong opinions

Re: [openstack-dev] [magnum] Proposing Eli Qiao for Magnum core reviewer team

+1 from me for Eli Thanks, Dims On Thu, Mar 31, 2016 at 2:18 PM, Hongbin Lu wrote: > Hi all, > > > > Eli Qiao has been consistently contributed to Magnum for a while. His > contribution started from about 10 months ago. Along the way, he implemented > several important

[openstack-dev] [magnum] Proposing Eli Qiao for Magnum core reviewer team

Hi all, Eli Qiao has been consistently contributed to Magnum for a while. His contribution started from about 10 months ago. Along the way, he implemented several important blueprints and fixed a lot of bugs. His contribution covers various aspects (i.e. APIs, conductor, unit/functional tests,

[openstack-dev] [release][horizon] Horizon Mitaka RC2 available

Due to release-critical issues spotted in Horizon during RC1 testing, a new release candidate was created for Mitaka. You can find the RC2 source code tarball at: https://tarballs.openstack.org/horizon/horizon-9.0.0.0rc2.tar.gz Unless new release-critical issues are found that warrant a

Re: [openstack-dev] 答复: [Heat] Re-evaluate conditions specification

+1. This sounds good. The lack of any conditionals at all has caused a lot of pain. Thanks, Kevin From: Huangtianhua Sent: Thursday, March 31, 2016 5:25:29 AM To: OpenStack Development Mailing List (not for usage questions) Subject: [openstack-dev] 答复: [Heat]

Re: [openstack-dev] [Heat] Re-evaluate conditions specification

My initial reaction is that sounds good, but how is it different then params, or maybe a hidden param? Maybe they are conditionally assigned? Conditional params would be awesome too though. If param 1 is not set, then param 2 is required... Thanks, Kevin From:

Re: [openstack-dev] [TripleO][Heat][Kolla][Magnum] The zen of Heat, containers, and the future of TripleO

Ideally it can roll the services one instance at a time while doing the appropriate load balancer stuff to make it seamless. Our experience has been even though services should retry, they dont always do it right. So better to do it with the lb proper if you can. Between ansible/container

[openstack-dev] Floating IPs and Public IPs are not equivalent

Just a friendly reminder to everyone - floating IPs are not synonymous with Public IPs in OpenStack. The most common (and growing, thank you to the beta of the new Dreamcompute cloud) configuration for Public Clouds is directly assign public IPs to VMs without requiring a user to create a

Re: [openstack-dev] [magnum] Are Floating IPs really needed for all nodes?

A few things: Public IPs and Floating IPs are not the same thing. Some clouds have public IPs. Some have floating ips. Some have both. I think it's important to be able to have magnum work with all of the above. If the cloud does not require using a floating IP (as most do not) to get

Re: [openstack-dev] [magnum] Are Floating IPs really needed for all nodes?

Hongbin, It's correct, I was involved in two big OpenStack private cloud deployments and we never had public ips.In such case Magnum shouldn't create any private networks, operator need to provide network id/name or it should use default  (we used to have networking selection logic in

Re: [openstack-dev] [nova] API priorities in Newton

2016-03-30 12:54 GMT-07:00 Matt Riedemann : >>> - Microversion Testing in Tempest (underway) > > How much coverage do we have today? This could be like novaclient where > people just start hacking on adding tests for each microversion (assuming > gmann would be working

Re: [openstack-dev] [nova] API priorities in Newton

2016-03-30 12:26 GMT-07:00 Sean Dague : > > One other issue that we've been blocking on for a while has been > Capabilities discovery. Some API proposed adds like live resize have > been conceptually blocked behind this one. Once upon a time there was a > theory that JSON Home was

Re: [openstack-dev] [docs] [api] Oh Swagger, where art thou?

On Thu, Mar 31, 2016 at 09:50:48AM -0400, Sean Dague wrote: > On 03/31/2016 09:43 AM, Jim Rollenhagen wrote: > > On Thu, Mar 31, 2016 at 08:43:29AM -0400, Sean Dague wrote: > >> Some more details on progress, because this is getting closer every day. > >> > >> There is now an api-ref target on the

Re: [openstack-dev] [tempest] Implementing tempest test for Keystone federation functional tests

On Thu, Mar 31, 2016 at 11:38:55AM -0400, Minying Lu wrote: > Hi all, > > I'm working on resource federation at the Massachusetts Open Cloud. We want > to implement functional test on the k2k federation, which requires > authentication with both a local keystone and a remote keystone (in a >

[openstack-dev] [Neutron] Mitaka RC3 available

Due to release-critical issues spotted in Neutron during RC2 testing, a new release candidate was created for Mitaka. You can find the RC3 source code tarballs at: https://tarballs.openstack.org/neutron/neutron-8.0.0.0rc3.tar.gz

Re: [openstack-dev] [fuel] Component Leads Elections

Hi fuelers, only few hours left until period of self-nomination will be closed, but so far we don't have neither consensus regarding how to proceed further nor candidates. I've increased period of self-nomination for another week (until April 7, 23:59 UTC) and expect to have decision about how

[openstack-dev] [tempest] Implementing tempest test for Keystone federation functional tests

Hi all, I'm working on resource federation at the Massachusetts Open Cloud. We want to implement functional test on the k2k federation, which requires authentication with both a local keystone and a remote keystone (in a different cloud installation). It also requires a K2K/SAML assertion

Re: [openstack-dev] [horizon] - oAuth tab proposal

Could you put up a blueprint for discussion? We have a weekly meeting to review blueprints: https://wiki.openstack.org/wiki/Meetings/HorizonDrivers The blueprint template is here: https://blueprints.launchpad.net/horizon/+spec/template Thanks! Rob On 31 Mar 2016, at 10:57, Marcos Fermin Lobo

Re: [openstack-dev] 答复: [Heat] Re-evaluate conditions specification

On Thu, Mar 31, 2016 at 09:21:43AM -0400, Rabi Mishra wrote: > If I understand the suggestion correctly, the only relation it has with > conditions is, > conditions are nothing but variables(boolean). > > conditions: { > 'for_prod': {equals: [{get_param: env_type}, 'prod']} > } > >

Re: [openstack-dev] [networking guide meeting] Meeting Tomorrow!

Hello Folks, Friendly reminder email that we have our networking guide team meeting in few minutes #openstack-meeting Matt will be chairing the meeting. Thanks, Edgar __ OpenStack Development Mailing List (not for usage

Re: [openstack-dev] [magnum] Discuss the blueprint"support-private-registry"

Ricardo, Thanks for the willingness to implement the blueprint. I am looking forward to reviewing the implementation. Best regards, Hongbin From: Ricardo Rocha [mailto:rocha.po...@gmail.com] Sent: March-30-16 10:59 AM To: OpenStack Development Mailing List (not for usage questions) Subject:

[openstack-dev] [Fuel] CI may be broken for about 2 hours

We’ve organized a tiger team in order to merge two patches with a series of patches [1,2] in order to fix a swarm blocker. Our plan is the following: 1) Merge [1] and [2] 2) Trigger a build 3) Upload the new ISO to the CI system while it lasses the BVT 4) If the BVT is fine, switch the CI system

Re: [openstack-dev] [magnum] Are Floating IPs really needed for all nodes?

Egor, I agree with what you said, but I think we need to address the problem that some clouds are lack of public IP addresses. It is not uncommon that a private cloud is running without public IP addresses, and they already figured out how to route traffics in and out. In such case, a bay

Re: [openstack-dev] [nova] Is the Intel SRIOV CI running and if so, what does it test?

On 03/31/2016 10:34 AM, Anita Kuno wrote: > On 03/31/2016 08:31 AM, Znoinski, Waldemar wrote: >> >> >> >-Original Message- >> >From: Matt Riedemann [mailto:mrie...@linux.vnet.ibm.com] >> >Sent: Wednesday, March 30, 2016 4:22 PM >> >To: OpenStack Development Mailing List (not for usage

Re: [openstack-dev] [Sahara][QA] Notes about the move of the Sahara Tempest API test to sahara-tests

On Sunday 20 of March 2016 21:07:06 Luigi Toscano wrote: > Hi, Small update on the plan: > > as discussed in the last (two) Sahara meetings, I'm working on moving the > Tempest API tests from the Tempest repository to the new sahara-tests > repository, which contains only (non-tempest) scenario

Re: [openstack-dev] [nova] Is the Intel SRIOV CI running and if so, what does it test?

On 03/31/2016 08:31 AM, Znoinski, Waldemar wrote: > > > >-Original Message- > >From: Matt Riedemann [mailto:mrie...@linux.vnet.ibm.com] > >Sent: Wednesday, March 30, 2016 4:22 PM > >To: OpenStack Development Mailing List (not for usage questions) >

Re: [openstack-dev] [kolla][vote] Just make Mitaka deploy Liberty within the Liberty branch

So, a plan. My idea about this backport is to: 1. We write Mitaka code deploying Liberty, just liberty (remove deploy_liberty nonsense from patchset above) 2. We mark this code as Kolla 1.1.0 effectively deprecating what we call liberty today 3. Most of bugs found in master/stable-mitaka will

Re: [openstack-dev] [nova][cinder] Fix nova swap volume (updating an attached volume) function

On 3/31/2016 5:58 AM, Duncan Thomas wrote: I *think* it is significantly semanticist different to do detach, attach; with swap volume, no events are generated in the guest; that is why it is dangerous to expose to the tenant - if the volume contents is not identical, you get weird corruption

Re: [openstack-dev] 答复: [Heat] Re-evaluate conditions specification

On Thu, Mar 31, 2016 at 2:25 PM, Huangtianhua wrote: > The conditions function has been requested for a long time, and there have > been several previous discussions, which all ended up in debating the > implementation, and no result. >

Re: [openstack-dev] [kolla][vote] Nominating Vikram Hosakot for Core Reviewer

+1 On Tue, Mar 29, 2016 at 12:07 PM, Steven Dake (stdake) wrote: > Hey folks, > > Consider this proposal a +1 in favor of Vikram joining the core reviewer > team. His reviews are outstanding. If he doesn’t have anything useful to > add to a review, he doesn't pile on the

Re: [openstack-dev] [nova] Is the Intel SRIOV CI running and if so, what does it test?

As approved in [1] we've added Nova-Macvtap job as part of Mellanox Nova non-voting CI Our wiki page is [2] [1] http://eavesdrop.openstack.org/irclogs/%23openstack-nova/%23openstack-nova.2016-03-30.log.html [2] https://wiki.openstack.org/wiki/ThirdPartySystems/Mellanox_CI Best Regards Lenny

Re: [openstack-dev] [TripleO] tripleo-quickstart import

On 03/30/2016 02:16 PM, Paul Belanger wrote: > On Tue, Mar 29, 2016 at 08:30:22PM -0400, John Trowbridge wrote: >> Hola, >> >> With the approval of the tripleo-quickstart spec[1], it is time to >> actually start doing the work. The first work item is moving it to the >> openstack git. The spec

Re: [openstack-dev] [docs] [api] Oh Swagger, where art thou?

On 03/31/2016 09:43 AM, Jim Rollenhagen wrote: > On Thu, Mar 31, 2016 at 08:43:29AM -0400, Sean Dague wrote: >> Some more details on progress, because this is getting closer every day. >> >> There is now an api-ref target on the Nova project. The entire work in >> progress stream has been rebased

Re: [openstack-dev] [nova][neutron] What to do about booting into port_security_enabled=False networks?

On Wed, Mar 30, 2016 at 09:46:45PM -0500, Matt Riedemann wrote: > > > On 3/30/2016 5:55 PM, Armando M. wrote: > > > > > >On 29 March 2016 at 18:55, Matt Riedemann >> wrote: > > > > > > > >On 3/29/2016 4:44 PM, Armando M. wrote:

Re: [openstack-dev] [docs] [api] Oh Swagger, where art thou?

On Thu, Mar 31, 2016 at 08:43:29AM -0400, Sean Dague wrote: > Some more details on progress, because this is getting closer every day. > > There is now an api-ref target on the Nova project. The entire work in > progress stream has been rebased into 2 patches to a top level api-ref/ > directory

Re: [openstack-dev] [telemetry] Rescheduling IRC meetings

Hi Gordon, > > ie. the new PTL should checkpoint with subteam leads regularly to review spec > status or identify missing resources on high-priority > items? I would say anything that we feel as useful information to people who read this mailing list. In this sense features that got

Re: [openstack-dev] [Fuel][library] CI gate for regressions detection in deployment data

It is time for update! The previous idea with the committed state and automatic cross-repo merge hooks in zuul seems too complex to implement. So, the "CI gate for blah blah" magically becomes now a manual helper tool for reviewers/developers, see the docs update [0], [1]. You may start using it

Re: [openstack-dev] 答复: [Heat] Re-evaluate conditions specification

> The conditions function has been requested for a long time, and there have > been several previous discussions, which all ended up in debating the > implementation, and no result. > https://review.openstack.org/#/c/84468/3/doc/source/template_guide/hot_spec.rst >

Re: [openstack-dev] [Ironic][Neutron] Integration status

On Thu, Mar 31, 2016 at 03:37:53PM +0300, Vasyl Saienko wrote: > Hello Community, > > I'm happy to announce that new experimental job > 'ironic-multitenant-network' is stabilized and working. This job allows to > test Ironic multitenancy patches at the gates with help of >

Re: [openstack-dev] [all] Austin Design Summit track layout

OK, please find attached the final layout. Changes: - Swapped Oslo and Stable fishbowl sessions on Thursday afternoon. - Swapped Fuel and Swift workroom sessions on Thursday afternoon This will be pushed to the official schedule ASAP and then PTLs will be able to tweak titles and descriptions

Re: [openstack-dev] [TripleO][Heat][Kolla][Magnum] The zen of Heat, containers, and the future of TripleO

On Thu, Mar 31, 2016 at 12:12 AM, Fox, Kevin M wrote: > The main issue is one of upgradability, not stability. We all know tripleo > is stable. Tripleo cant do upgrades today. We're looking for ways to get > there. So "upgrading" to ansible isnt nessisary for sure since folks

Re: [openstack-dev] [nova] API priorities in Newton

2016-03-31 19:21 GMT+08:00 Sean Dague : > On 03/31/2016 04:55 AM, Alex Xu wrote: > > > > > > 2016-03-31 5:36 GMT+08:00 Matt Riedemann > > As discussed in IRC today, first steps (I think) are removing the > > deprecated 'osapi_v21.enabled'

[openstack-dev] [Heat] Mitaka RC3 available

Due to new release-critical issues spotted in Heat during RC2 testing, a new release candidate was created for Mitaka. You can find the RC3 source code tarball at: https://tarballs.openstack.org/heat/heat-6.0.0.0rc3.tar.gz Unless new release-critical issues are found that warrant a

[openstack-dev] [Nova] Mitaka RC3 available

Due to new release-critical issues spotted in Nova during RC2 testing, a new release candidate was created for Mitaka. You can find the RC3 source code tarball at: https://tarballs.openstack.org/nova/nova-13.0.0.0rc3.tar.gz Unless new release-critical issues are found that warrant a

[openstack-dev] [Sahara] Mitaka RC2 available

Due to one release-critical issue spotted in Sahara during RC1 testing, a new release candidate was created for Mitaka. You can find the RC2 source code tarballs at: https://tarballs.openstack.org/sahara/sahara-4.0.0.0rc2.tar.gz

[openstack-dev] [Ironic][Neutron] Integration status

Hello Community, I'm happy to announce that new experimental job 'ironic-multitenant-network' is stabilized and working. This job allows to test Ironic multitenancy patches at the gates with help of networking-generic-switch [1]. Unfortunately depends-on doesn't work for python-ironicclient [2]

Re: [openstack-dev] [telemetry] Rescheduling IRC meetings

On Thu, Mar 31 2016, Ildikó Váncsa wrote: > +1 on the on demand meeting schedule. Maybe we can also have some news flash > mails week to summarize the progress in our sub-modules when we don't have the > meeting. Just to keep people up to date. That sounds a good idea. If anyone is motivated to

[openstack-dev] [Trove] Mitaka RC2 available

Due to one release-critical issue spotted in Trove during RC1 testing, a new release candidate was created for Mitaka. You can find the RC2 source code tarball at: https://tarballs.openstack.org/trove/trove-5.0.0.0rc2.tar.gz Unless new release-critical issues are found that warrant a

Re: [openstack-dev] [nova] Is the Intel SRIOV CI running and if so, what does it test?

>-Original Message- >From: Matt Riedemann [mailto:mrie...@linux.vnet.ibm.com] >Sent: Wednesday, March 30, 2016 4:22 PM >To: OpenStack Development Mailing List (not for usage questions) > >Cc: Feng, Shaohe >Subject:

[openstack-dev] [Barbican] Mitaka RC2 available

Due to one release-critical issue spotted in Barbican during RC1 testing, a new release candidate was created for Mitaka. You can find the RC2 source code tarball at: https://tarballs.openstack.org/barbican/barbican-2.0.0.0rc2.tar.gz Unless new release-critical issues are found that warrant a

Re: [openstack-dev] [Nova] No rejoin-stack.sh script in my setup

Hi, rejoin-stack.sh has been removed 14 days ago by https://review.openstack.org/#/c/291453/ You should use the "screen" command now. (e.g screen -R) On Thu, Mar 31, 2016 at 1:06 PM, Ouadï Belmokhtar < ouadi.belmokh...@gmail.com> wrote: > Hi everyone, > > Could you give any help to my question

  1   2   >