Re: [openstack-dev] [magnum][heat] spawn a group of nodes on different availability zones

On 07/06/16 23:53, Hongbin Lu wrote: Hi Heat team, A question inline. Best regards, Hongbin -Original Message- From: Steven Hardy [mailto:sha...@redhat.com] Sent: March-03-16 3:57 AM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev]

Re: [openstack-dev] [murano] Nominating Alexander Tivelkov and Zhu Rong for murano cores

+1 Well deserved! Nikolay Starodubtsev Software Engineer Mirantis Inc. Skype: dark_harlequine1 2016-06-15 19:42 GMT+03:00 Serg Melikyan : > +1 > > Finally! > > On Wed, Jun 15, 2016 at 3:33 AM, Ihor Dvoretskyi > wrote: > >> +1 for

Re: [openstack-dev] [nova] Virtuozzo (Compute) CI is incorrectly patching for resize support

Jeremy, thank you for pointing this out! It saved me from such a headache! BTW, is there any plan to workaround this in puppet-jenkins? On 06/15/2016 08:39 PM, Jeremy Stanley wrote: On 2016-06-15 13:17:54 +0300 (+0300), Evgeny Antyshev wrote: [...] This all started yesterday when I updated

[openstack-dev] [tempest][SR-IOV] tempest breaks Mellanox CI

Hi all, A recent change [1] in tempest broke all Mellanox CIs. This is the second time it happened. After the first time it happened we decided that Mellanox CI will comment on tempest. On this time I saw that Mellanox CI was commenting on that patch with a failure but was still got

Re: [openstack-dev] [Neutron][os-vif] Expanding vif capability for wiring trunk ports

On 16 June 2016 at 03:33, Matt Riedemann wrote: > On 6/13/2016 3:35 AM, Daniel P. Berrange wrote: > >> On Thu, Jun 09, 2016 at 05:31:13PM -0600, Carl Baldwin wrote: >> >>> Hi, >>> >>> You may or may not be aware of the vlan-aware-vms effort [1] in >>> Neutron. If

[openstack-dev] [Neutron][LBaaS] Gate broken

Hi, The unitests are failing because of: Captured traceback: ~~~ Traceback (most recent call last): File "neutron_lbaas/tests/unit/db/loadbalancer/test_db_loadbalancerv2.py", line 1020, in test_delete_loadbalancer 'tenant_id': acontext.tenant_id}}) File

[openstack-dev] [QA] Meeting Thursday June 16th at 9:00 UTC

Hello everyone, Please reminder that the weekly OpenStack QA team IRC meeting will be Thursday, June 16th at 9:00 UTC in the #openstack-meeting channel. The agenda for the meeting can be found here:

Re: [openstack-dev] [tempest][SR-IOV] tempest breaks Mellanox CI

On Thu, Jun 16, 2016 at 11:16 AM Moshe Levi wrote: > Hi all, > > > > A recent change [1] in tempest broke all Mellanox CIs. > > This is the second time it happened. > > After the first time it happened we decided that Mellanox CI will > comment on tempest. > > On this

Re: [openstack-dev] [Neutron][os-vif] Expanding vif capability for wiring trunk ports

Can we move the discussion of deprecating veth pairs to here? https://bugs.launchpad.net/neutron/+bug/1587296 https://review.openstack.org/323310 As you can see in the related bugs and linked patches there are some complications. Some of the veth config options were already deprecated and the

Re: [openstack-dev] [tempest][SR-IOV] tempest breaks Mellanox CI

Thanks, We are investigating the failure. From: Andrea Frittoli [mailto:andrea.fritt...@gmail.com] Sent: Thursday, June 16, 2016 2:02 PM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [tempest][SR-IOV] tempest

Re: [openstack-dev] [all][tc] Require a level playing field for OpenStack projects

Matt Riedemann wrote: [...] So is the question does Nova provide a level playing field as a project because it has drivers that can be deployed and used and tested without special hardware, i.e. libvirt? Then yes. Or is it Nova doesn't provide a level playing field because zVM and powervm aren't

Re: [openstack-dev] [Neutron][LBaaS] Gate broken

Proposal for fix is https://review.openstack.org/330368 From: Gary Kotton Reply-To: OpenStack List Date: Thursday, June 16, 2016 at 11:21 AM To: OpenStack List Subject: Re: [openstack-dev]

Re: [openstack-dev] [tempest][nova][defcore] Add option to disable some strict response checking for interop testing

On Wed, Jun 15, 2016 at 11:54 PM, Ken'ichi Ohmichi wrote: > This discussion was expected when we implemented the Tempest patch, > then I sent a mail to defcore comittee[1] > As the above ml, "A DefCore Guideline typically covers three OpenStack > releases". > That means

Re: [openstack-dev] [stable] Stable check of openstack/horizon failed

On 15/06/16 09:22, Matthias Runge wrote: > On 15/06/16 09:20, Matthias Runge wrote: >> On 15/06/16 08:14, A mailing list for the OpenStack Stable Branch test >> reports. wrote: >>> Build failed. >>> >>> - periodic-horizon-docs-liberty >>>

Re: [openstack-dev] [nova] consistency and exposing quiesce in the Nova API

I am hoping support for instance quiesce in the Nova API makes it into OpenStack. To my understanding, this is existing function in Nova, just not-yet exposed in the public API. (I believe Cinder uses this via a private Nova API.) Much of the discussion is around disaster recovery (DR) and NFV -

Re: [openstack-dev] [all] what do you work on upstream of OpenStack?

Doug Hellmann said on Mon, Jun 13, 2016 at 03:11:17PM -0400: > I'm trying to pull together some information about contributions > that OpenStack community members have made *upstream* of OpenStack, > via code, docs, bug reports, or anything else to dependencies that > we have.

Re: [openstack-dev] [Higgins][Zun] Project roadmap

Hello, everyone, Hypernetes has done some work same as this project, that is - Leverate Neutron for container network - Leverate Cinder for storage - Leverate Keystone for auth - Leverate HyperContainer for hypervisor-based container runtime We could help to provide hypervisor-based container

Re: [openstack-dev] [murano] Nominating Alexander Tivelkov and Zhu Rong for murano cores

It’s great to see this happen! +1 for adding both! Well deserved, folks! Also agreed to remove Steve from murano-core. --  Victor Ryzhenkin Quality Assurance Engineer freerunner on #freenode От 16 июня 2016 г. в 14:51:23, Tetiana Lashchova (tlashch...@mirantis.com) написал: +1 for both On

[openstack-dev] [openstack-ansible] What's Happening in OpenStack-Ansible - June 2016

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hello there, One of the feedback items that came out of the OpenStack Summit in Austin was around the constant stream of changes throughout OpenStack-Ansible and how to best keep up with them. That could be said about OpenStack in general as

Re: [openstack-dev] [all][tc] Require a level playing field for OpenStack projects

Thanks Thierry, I did the same (again) :) -amrith > -Original Message- > From: Thierry Carrez [mailto:thie...@openstack.org] > Sent: Wednesday, June 15, 2016 12:22 PM > To: openstack-dev@lists.openstack.org > Subject: Re: [openstack-dev] [all][tc] Require a level playing field for >

[openstack-dev] [nova] A primer on data structures used by Nova to represent block devices

The purpose of this mail is to share what I have learned about the various data structures used by Nova for representing block devices. I compiled this for my own use, but I hope it might be useful for others, and that other might point out any errors. As is usual when I'm reading code like this,

Re: [openstack-dev] [kolla] Stability and reliability of gate jobs

David, The gates are unreliable for a variety of reasons - some we can fix - some we can't directly. RDO rabbitmq introduced IPv6 support to erlang, which caused our gate reliably to drop dramatically. Prior to this change, our gate was running 95% reliability or better - assuming the code

[openstack-dev] [all] [api] running gabbi tests in a concurrent environment

Overnight, gate failures for the gabbi tests in the telemetry projects exposed that I'd done a rather poor job of highlighting the issues with and the proper ways to manage running gabbi tests with a concurrent runner. Gabbi has always worked concurrently as long as the test runner was made

Re: [openstack-dev] [murano] Nominating Alexander Tivelkov and Zhu Rong for murano cores

+1 for both On Thu, Jun 16, 2016 at 11:26 AM, Nikolay Starodubtsev < nstarodubt...@mirantis.com> wrote: > +1 > Well deserved! > > > > Nikolay Starodubtsev > > Software Engineer > > Mirantis Inc. > > > Skype: dark_harlequine1 > > 2016-06-15 19:42 GMT+03:00 Serg Melikyan :

[openstack-dev] networking-sfc: unable to use SFC (ovs driver) with multiple networks

Hello, I'd need some help with using the SFC implementation in openstack. I use liberty version of devstack + liberty branch of networking-sfc. It's not clear to me if the SFC instance and it's networks should be separated from the remaining virtual network topology or if it should be connected

Re: [openstack-dev] [tempest][nova][defcore] Add option to disable some strict response checking for interop testing

On 16/06/2016 00:30, Matthew Treinish wrote: > On Wed, Jun 15, 2016 at 09:10:30AM -0400, Doug Hellmann wrote: >> Excerpts from Chris Hoge's message of 2016-06-14 16:37:06 -0700: >>> Top posting one note and direct comments inline, I’m proposing >>> this as a member of the DefCore working group,

[openstack-dev] [Neutron][IPAM] Anyone using builtin pluggable IPAM driver?

Hi, Cross posting to the operators and devs. In Liberty, pluggable IPAM was added to Neutron. With it, a built-in pluggable driver, equivalent to the old non-pluggable IPAM was added as a reference implementation. In a greenfield deployment, you could choose to use this driver by setting the

Re: [openstack-dev] [all][tc] Require a level playing field for OpenStack projects

- Original Message - > From: "Amrith Kumar" > To: "OpenStack Development Mailing List (not for usage questions)" > > > Thierry, > > Thanks for writing this up and for the interesting discussion that has come > up in this ML thread.

Re: [openstack-dev] [all][tc] Require a level playing field for OpenStack projects

On 09:35 Jun 14, Ed Leafe wrote: > On Jun 14, 2016, at 8:57 AM, Thierry Carrez wrote: > > > A few months ago we had the discussion about what "no open core" means in > > 2016, in the context of the Poppy team candidacy. With our reading at the > > time we ended up

[openstack-dev] [ironic] IPA DIB Ramdisk needs CI, Documentation

Hey all, I recently tried to do some testing with the DIB ramdisk in devstack, and found there were several bugs (I filed three yesterday) in the build process, and additionally, no documentation or guidance on how to build or test the images devstack in IPA developer docs (although inspector

Re: [openstack-dev] [tempest][nova][defcore] Add option to disable some strict response checking for interop testing

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On Jun 16, 2016, at 2:25 PM, Matthew Treinish wrote: On Thu, Jun 16, 2016 at 02:15:47PM -0400, Doug Hellmann wrote: Excerpts from Matthew Treinish's message of 2016-06-16 13:56:31 -0400: On Thu, Jun 16, 2016 at 12:59:41PM

Re: [openstack-dev] [all][tc] Require a level playing field for OpenStack projects

On 2016-06-16 16:04:28 -0400 (-0400), Steve Gordon wrote: [...] > This is definitely a point worth clarifying in the general case, > but tangentially for the specific case of the RHEL operating > system please note that RHEL is available to developers for free: > >

[openstack-dev] There is no Jenkins, only Zuul

Since its inception, the OpenStack project has used Jenkins to perform its testing and artifact building. When OpenStack was two git repos, we had one Jenkins master, a few slaves, and we configured all of our jobs manually in the web interface. It was easy for a new project like OpenStack to

Re: [openstack-dev] Invitation to join Hangzhou Bug Smash

On 6/14/2016 9:03 PM, Anita Kuno wrote: I'll reply in private first because I am a core reviewer on the project-config repo, which was not mentioned in your list but you might consider useful to you at the bug smash nonetheless. Let me know if you would like me to attend and I'll reply in

Re: [openstack-dev] There is no Jenkins, only Zuul

James E. Blair wrote: Since its inception, the OpenStack project has used Jenkins to perform its testing and artifact building. When OpenStack was two git repos, we had one Jenkins master, a few slaves, and we configured all of our jobs manually in the web interface. It was easy for a new

Re: [openstack-dev] There is no Jenkins, only Zuul

On 06/17/2016 12:41 AM, James E. Blair wrote: > Since its inception, the OpenStack project has used Jenkins to perform > its testing and artifact building. When OpenStack was two git repos, > we had one Jenkins master, a few slaves, and we configured all of our > jobs manually in the web

[openstack-dev] [Infra] publish-to-pypi not working in Tricircle stable/mitaka branch

Hello, The publish-to-pypi job is configured for Tricircle[1], and already gave "openstackci" the role to "Owner"[3][2]. After push a new tag v2.0.1 in stable/mitaka branch of : https://github.com/openstack/tricircle, the tagging is successfully applied to the repository, but the

Re: [openstack-dev] Invitation to join Hangzhou Bug Smash

On 06/16/2016 07:03 PM, Matt Riedemann wrote: > On 6/14/2016 9:03 PM, Anita Kuno wrote: >> >> I'll reply in private first because I am a core reviewer on the >> project-config repo, which was not mentioned in your list but you might >> consider useful to you at the bug smash nonetheless. >> >> Let

Re: [openstack-dev] [OpenStack-Infra] There is no Jenkins, only Zuul

On 2016-06-17 01:48:08 +0200 (+0200), Thomas Goirand wrote: > What will be the faith of jenkins job builder then? It is already used > by lots of people, including some Debian folks. Will it be maintained? Jenkins Job Builder is very actively maintained by contributors and reviewers from many

[openstack-dev] Upcoming changes now that Jenkins has retired

Now that we have retired Jenkins, we have some upcoming changes: * Console logs are now available via TCP The status page now has "telnet" protocol links to running jobs. If you connect to the host and port specified in that link, you will be sent the console log for that job up to that

Re: [openstack-dev] [OpenStack-Infra] There is no Jenkins, only Zuul

On 2016-06-16 16:15:34 -0700 (-0700), Joshua Harlow wrote: [...] > Is the goal/idea that there would be something like a > '.travis.yml' (file or directory) that would contain the job > configuration (and any special jobs or commands or tasks) in the > project repository that zuul would then use

Re: [openstack-dev] [nova] Virtuozzo (Compute) CI is incorrectly patching for resize support

On 2016-06-16 11:57:11 +0300 (+0300), Evgeny Antyshev wrote: > Jeremy, thank you for pointing this out! It saved me from such a headache! > BTW, is there any plan to workaround this in puppet-jenkins? Probably not in puppet-jenkins since there are alternative workarounds such as declaring the

Re: [openstack-dev] [Openstack-operators] [glance] Proposal for a mid-cycle virtual sync on operator issues

Fei Long and I have followed up on our action item from the glance/ops mid-cycle sync, namely, to start a discussion among the operators and product working group so that the Glance team can get a better understanding of what "Better image lifecycle support" means. Please leave comments on this

[openstack-dev] Recommended ways to find compute node's bandwidth (physical NIC)

I am writing a nova filter that will check for the compute node (max, avg) bandwidth, before instantiating an instance. What are some of the recommended tools that can provide this info in real time? Does any openstack component hold this info already? Thanks, Adnan

Re: [openstack-dev] [nova] consistency and exposing quiesce in the Nova API

Comments inline. On Thu, Jun 16, 2016 at 10:13 AM, Matt Riedemann wrote: > On 6/16/2016 6:12 AM, Preston L. Bannister wrote: > >> I am hoping support for instance quiesce in the Nova API makes it into >> OpenStack. To my understanding, this is existing function in

[openstack-dev] [kolla] Potential direction proposal - unified OpenStack containers

Hi folks, I'd like to share some thoughts about the OpenStack containerization in the form of a specification for Kolla and have some discussion on the proposed items in the review. In general it's a meta spec to describe potential direction for Kolla to provide Unified deployment tool agnostic

Re: [openstack-dev] [Higgins] Call for contribution for Higgins API design

Hi, We have created an etherpad page for API design https://etherpad.openstack.org/p/zun-containers-service-api Please have a look and write your suggestions. Regards, Madhuri From: Yuanying OTSUKA [mailto:yuany...@oeilvert.org] Sent: Tuesday, June 14, 2016 9:39 AM To: OpenStack Development

[openstack-dev] [neutron] Cannot setup IPSEC transport mode between VMS

Hi all, In Liberty, i want to setup a IPSEC between VMS using transport mode with ESP protocol, Just as the diagram above descried, only 10.0.0.4 access 10.0.0.5/10.0.0.6. If i setup the IPSEC using manually configured key management, ipsec-tools(setkey) under ubuntu, the vm of 10.0.0.4 cannot

[openstack-dev] [networking-ovs-dpdk] suggested devStack local.conf settings for OpenStack Mitaka with DPDK

Hi, I would like to install with DevStack (on a single node) OpenStack Mitaka with neutron using OVS+DPDK (so far I managed to create with devstack a Mitaka stack using neutron with "vanilla" OVS). To be clear, I checked out the stable/mitaka devstack branch: git clone

[openstack-dev] [requirements][all] VOTE to expand the Requirements Team

Folks, At Austin the Release Management team reached a consensus to spin off with some new volunteers to take care of the requirements process and repository [1]. The following folks showed up and worked with me on getting familiar with the issues/problems/tasks (see [1] and [2]) and help with

[openstack-dev] [telemetry] Panko has been imported

Hi team, Panko has been imported and is now ready to be worked on. Our next steps should be to set up devstack jobs for testing. The devstack plugin should be working, it just misses an integration from Ceilometer so the event dispatcher is set to 'panko' if panko is installed via devstack

Re: [openstack-dev] [TripleO] Proposed TripleO core changes

On Thu, 2016-06-09 at 15:03 +0100, Steven Hardy wrote: > Hi all, > > I've been in discussion with Martin André and Tomas Sedovic, who are > involved with the creation of the new tripleo-validations repo[1] > > We've agreed that rather than create another gerrit group, they can > be > added to

Re: [openstack-dev] [nova] consistency and exposing quiesce in the Nova API

On 6/16/2016 6:12 AM, Preston L. Bannister wrote: I am hoping support for instance quiesce in the Nova API makes it into OpenStack. To my understanding, this is existing function in Nova, just not-yet exposed in the public API. (I believe Cinder uses this via a private Nova API.) I'm assuming

Re: [openstack-dev] [Neutron][LBaaS] Gate broken

Hi, The reason is https://review.openstack.org/#/c/327413/ Thanks Gary From: Gary Kotton Reply-To: OpenStack List Date: Thursday, June 16, 2016 at 10:47 AM To: OpenStack List Subject: [openstack-dev]

Re: [openstack-dev] [all][tc] Require a level playing field for OpenStack projects

Robert Collins wrote: [...] From an upstream perspective, I see us as being in the business of providing open collaboration playing fields in order to build projects to reach the OpenStack Mission. We collectively provide resources (infra, horizontal teams, events...) in order to enable that

Re: [openstack-dev] [cinder] No middle-man - when does/will Nova directly connect iSCSI volumes?

One major disadvantage is lack of multipath support. Multipath is still done outside of qemu and there is no native multipath support inside of qemu from what I can tell. Another disadvantage is that qemu iSCSI support is all s/w based. There are hardware iSCSI initiators that are supported

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

Greetings OpenStack community, No new guidelines this week but we did have a very productive time creating launchpad bugs for all the TODOs that are in the existing guidelines. The idea is that using launchpad will help to keep the TODOs visible and encourage action. See them at

Re: [openstack-dev] [tacker] Proposing Kanagaraj Manickam to Tacker core team

+1 -Sripriya From: Sridhar Ramaswamy [mailto:sric...@gmail.com] Sent: Wednesday, June 15, 2016 6:32 PM To: OpenStack Development Mailing List (not for usage questions) Subject: [openstack-dev] [tacker] Proposing Kanagaraj Manickam to Tacker core team

Re: [openstack-dev] [ironic] Proposing two new cores

On 06/16/2016 08:12 AM, Jim Rollenhagen wrote: > Hi all, > > I'd like to propose Jay Faulkner (JayF) and Sam Betts (sambetts) for the > ironic-core team. > > Jay has been in the community as long as I have, has been IPA and > ironic-specs core for quite some time. His background is operations,

[openstack-dev] [Monasca] monasca-agent, flake8 version change on Jenkins

Hi, Flake 8 version seems to have changed since yesterday on the Jenkins node. was: flake8==2.5.5 now: flake8==2.6.0 It (apparently) causes gate-monasca-agent-pep8 checks to fail, since the old code does not pass the check. Has anyone started addressing this issue? BR, Laszlo

Re: [openstack-dev] [nova] A primer on data structures used by Nova to represent block devices

On Thu, Jun 16, 2016 at 12:48:18PM +0100, Matthew Booth wrote: > The purpose of this mail is to share what I have learned about the various > data structures used by Nova for representing block devices. I compiled > this for my own use, but I hope it might be useful for others, and that > other

Re: [openstack-dev] [ironic] Proposing two new cores

Hi, > Both Sam and Jay are to the point where I consider their +1 or -1 as > highly as any other core, so I think it's past time to allow them to +2 > as well. > > Current cores, please reply with your vote. > Great work Sam and Jay! +1 for both Cheers, Lucas

Re: [openstack-dev] [ironic] Proposing two new cores

+1 from me, both Jay and Sam are doing very good job :) On Thu, Jun 16, 2016 at 6:20 PM, Lucas Alvares Gomes wrote: > Hi, > > > Both Sam and Jay are to the point where I consider their +1 or -1 as > > highly as any other core, so I think it's past time to allow them to +2

Re: [openstack-dev] [ironic] Proposing two new cores

> -Original Message- > From: Jim Rollenhagen [mailto:j...@jimrollenhagen.com] > Sent: Thursday, June 16, 2016 08:13 > To: openstack-dev@lists.openstack.org > Subject: [openstack-dev] [ironic] Proposing two new cores > > Hi all, > > I'd like to propose Jay Faulkner (JayF) and Sam Betts

[openstack-dev] [ironic] Proposing two new cores

Hi all, I'd like to propose Jay Faulkner (JayF) and Sam Betts (sambetts) for the ironic-core team. Jay has been in the community as long as I have, has been IPA and ironic-specs core for quite some time. His background is operations, and he's getting good with Python. He's given great reviews

Re: [openstack-dev] [kolla] Potential direction proposal - unified OpenStack containers

Sergey, Thanks for reaching out to the community! I think there is a lot to discuss. I added some comments on the spec and I'm sure many kolla folks will follow up. Thanks, Ryan - Original Message - From: "Sergey Lukjanov" To: "OpenStack Development Mailing

Re: [openstack-dev] [nova] A primer on data structures used by Nova to represent block devices

On Thu, Jun 16, 2016 at 4:20 PM, Kashyap Chamarthy wrote: [...] > > BlockDeviceMapping > > === > > > > The 'top level' data structure is the block device mapping object. It is > a > > NovaObject, persisted in the db. Current code creates a BDM object for > >

Re: [openstack-dev] [ironic] Proposing two new cores

Jim, Thanks for the proposal. +2 +A. Err, +2 :) --ruby On 2016-06-16, 11:12 AM, "Jim Rollenhagen" > wrote: Both Sam and Jay are to the point where I consider their +1 or -1 as highly as any other core, so I think it's past time to

Re: [openstack-dev] [Higgins][Zun] Project roadmap

Welcome! Please feel free to ping us in IRC (#openstack-zun) or join our weekly meeting (https://wiki.openstack.org/wiki/Zun#Meetings). I am happy to discuss how to collaborate further. Best regards, Hongbin From: Pengfei Ni [mailto:feisk...@gmail.com] Sent: June-16-16 6:36 AM To: OpenStack

Re: [openstack-dev] [UX] [TripleO] TripleO UI Initial Wireframes

I left some comments on the wireframes themselves. One general concept I would like to see capture is to make sure that things across the UI and CLI have parity. Specifically things like if I register nodes on the CLI we use a JSON file format:

[openstack-dev] [Fuel] It is impossible to queue UpdateDnsmasqTask

Hi All, Currently we can only run one instance of subj. at time. An attempt to run second one causes an exception. This behaviour at least may cause a cluster to stuck forever in "removing" state (reproduces here https://bugs.launchpad.net/fuel/+bug/1544493) or just produce incomprehensible "task

Re: [openstack-dev] [ironic] Proposing two new cores

On 06/16/2016 05:12 PM, Jim Rollenhagen wrote: Hi all, I'd like to propose Jay Faulkner (JayF) and Sam Betts (sambetts) for the ironic-core team. Jay has been in the community as long as I have, has been IPA and ironic-specs core for quite some time. His background is operations, and he's

Re: [openstack-dev] [kolla] Potential direction proposal - unified OpenStack containers

Hey, welcome back to Kolla guys!:) We've missed you! I'm sure we can figure out together best way to meet everyones needs, I'm happy to help! Also reviewed spec. Thanks. On 16 June 2016 at 10:23, Ryan Hallisey wrote: > Sergey, > > Thanks for reaching out to the community!

Re: [openstack-dev] [tempest][nova][defcore] Add option to disable some strict response checking for interop testing

Excerpts from Matthew Treinish's message of 2016-06-15 19:27:13 -0400: > On Wed, Jun 15, 2016 at 09:10:30AM -0400, Doug Hellmann wrote: > > Excerpts from Chris Hoge's message of 2016-06-14 16:37:06 -0700: > > > Top posting one note and direct comments inline, I’m proposing > > > this as a member

Re: [openstack-dev] [requirements][all] VOTE to expand the Requirements Team

Excerpts from Davanum Srinivas (dims)'s message of 2016-06-16 07:44:50 -0700: > Folks, > > At Austin the Release Management team reached a consensus to spin off > with some new volunteers to take care of the requirements process and > repository [1]. The following folks showed up and worked with

Re: [openstack-dev] [tempest][nova][defcore] Add option to disable some strict response checking for interop testing

On Thu, Jun 16, 2016 at 12:59:41PM -0400, Doug Hellmann wrote: > Excerpts from Matthew Treinish's message of 2016-06-15 19:27:13 -0400: > > On Wed, Jun 15, 2016 at 09:10:30AM -0400, Doug Hellmann wrote: > > > Excerpts from Chris Hoge's message of 2016-06-14 16:37:06 -0700: > > > > Top posting one

Re: [openstack-dev] [tempest][nova][defcore] Add option to disable some strict response checking for interop testing

Excerpts from Matthew Treinish's message of 2016-06-16 13:56:31 -0400: > On Thu, Jun 16, 2016 at 12:59:41PM -0400, Doug Hellmann wrote: > > Excerpts from Matthew Treinish's message of 2016-06-15 19:27:13 -0400: > > > On Wed, Jun 15, 2016 at 09:10:30AM -0400, Doug Hellmann wrote: > > > > Excerpts

Re: [openstack-dev] [tempest][nova][defcore] Add option to disable some strict response checking for interop testing

On Thu, Jun 16, 2016 at 02:15:47PM -0400, Doug Hellmann wrote: > Excerpts from Matthew Treinish's message of 2016-06-16 13:56:31 -0400: > > On Thu, Jun 16, 2016 at 12:59:41PM -0400, Doug Hellmann wrote: > > > Excerpts from Matthew Treinish's message of 2016-06-15 19:27:13 -0400: > > > > On Wed,

Re: [openstack-dev] [tacker] Proposing Kanagaraj Manickam to Tacker core team

+1. Great addition to the team indeed! On Wed, Jun 15, 2016 at 6:31 PM, Sridhar Ramaswamy wrote: > Tackers, > > It gives me great pleasure to propose Kanagaraj Manickam to join the > Tacker core team. In a short time, Kanagaraj has grown into a key member of > the Tacker

[openstack-dev] [QA][Infra] Newton Code Sprint

Hi Everyone, As we've done the past 3 cycles we'll be having another QA/Infra code sprint this cycle. Previous code sprints were amazing, and we could concentrate on the development with working together directly. At this time, we have gotten an opportunity to hold a code sprint with QA team and

Re: [openstack-dev] [tacker] Proposing Kanagaraj Manickam to Tacker core team

+1. Thanks Kanagaraj for making such a great impact during the Newton cycle. From: Sripriya Seetharam [mailto:ssee...@brocade.com] Sent: Thursday, June 16, 2016 10:35 AM To: OpenStack Development Mailing List (not for usage questions) Subject: Re:

Re: [openstack-dev] [qa] Tempest pre-provisioned credentials in the gate

2016-06-14 17:00 GMT-07:00 Andrea Frittoli : > Dear all, > > TL;DR: I'd like to propose to start running some of the existing dsvm > check/gate jobs using Tempest pre-provisioned credentials. > > Full Text: > Tempest provides tests with two mechanisms to acquire test

Re: [openstack-dev] [all][tc] Require a level playing field for OpenStack projects

- Original Message - > From: "Jeremy Stanley" > To: "OpenStack Development Mailing List (not for usage questions)" > > Sent: Thursday, June 16, 2016 5:04:43 PM > Subject: Re: [openstack-dev] [all][tc] Require a level playing field

Re: [openstack-dev] Invitation to join Hangzhou Bug Smash

Anita, sorry about replying to you slowly. Because we are a committee from a couple of companies, and need discussion, which causes slowness. I am not the only decision maker. Thanks Anita;) Regards. -- Shane -Original Message- From: Anita Kuno [mailto:ante...@anteaya.info] Sent:

Re: [openstack-dev] [daisycloud-core] IRC weekly meeting logistics

Hi Daisy Team, It is my honor to become a part of team,Unfortunately i had to leave the town for Client meeting urgently today as told to me so it might not be possible to attend the meeting :( , but i would surely follow up through logs and Irc Daisy Channel. I regret for the inconvenience

Re: [openstack-dev] [Infra] publish-to-pypi not working in Tricircle stable/mitaka branch

On Fri, Jun 17, 2016 at 01:15:13AM +, joehuang wrote: > Hello, > > The publish-to-pypi job is configured for Tricircle[1], and already gave > "openstackci" the role to "Owner"[3][2]. > > After push a new tag v2.0.1 in stable/mitaka branch of : > https://github.com/openstack/tricircle, the

Re: [openstack-dev] [cinder] No middle-man - when does/will Nova directly connect iSCSI volumes?

On Wed, Jun 15, 2016 at 5:59 PM, Preston L. Bannister wrote: > QEMU has the ability to directly connect to iSCSI volumes. Running the > iSCSI connections through the nova-compute host *seems* somewhat > inefficient. > ​I know tests I've run in the past virt-io actually

Re: [openstack-dev] [Infra] publish-to-pypi not working in Tricircle stable/mitaka branch

Hello, Tony, Yes, just follow the [2] to tag a release. Maybe the issue is the version naming, using "v2.0.0 " is the problem, I guess, only number no character is allowed. Thank you, will try again. Best Regards Chaoyi Huang ( Joe Huang ) -Original Message- From: Tony Breeds

[openstack-dev] What's Up, Doc? 17 June 2016

Hi everyone, This week I've very pleased to announce that we have our first project-specific Install Guide published! Petr Kovar got Heat over the line in first place, and it's looking great: http://docs.openstack.org/project-install-guide/orchestration/draft/index.html Well done Petr, and

Re: [openstack-dev] Invitation to join Hangzhou Bug Smash

I heard that from Doug, the best timing is before July 11. Thank you for the reminder. Regards. -- Shane -Original Message- From: Daniel P. Berrange [mailto:berra...@redhat.com] Sent: Monday, June 13, 2016 5:46 PM To: OpenStack Development Mailing List (not for usage questions) Cc:

Re: [openstack-dev] [release] Invitation to join Hangzhou Bug Smash

That is what I want. It is better to map the day into the release schedule in the future. Can we make it since Otaca? And everyone is encouraged. Regards. -- Shane -Original Message- From: Rochelle Grober [mailto:rochelle.gro...@huawei.com] Sent: Wednesday, June 15, 2016 9:53 AM To:

Re: [openstack-dev] [tempest][nova][defcore] Add option to disable some strict response checking for interop testing

On Jun 14, 2016 14:42, "Doug Hellmann" wrote: > > Excerpts from Matthew Treinish's message of 2016-06-14 15:12:45 -0400: > > On Tue, Jun 14, 2016 at 02:41:10PM -0400, Doug Hellmann wrote: > > > Excerpts from Matthew Treinish's message of 2016-06-14 14:21:27 -0400: > > > >

Re: [openstack-dev] [keystone][security] Service User Permissions

Thanks everyone for your input. I generally agree that there is something that doesn't quite feel right about purely trusting this information to be passed from service to service, this is why i was keen for outside input and I have been rethinking the approach. To this end i've proposed

Re: [openstack-dev] Invitation to join Hangzhou Bug Smash

Welcome to join us, Duncan. Regards. -- Shane From: Duncan Thomas [mailto:duncan.tho...@gmail.com] Sent: Monday, June 13, 2016 4:14 PM To: OpenStack Development Mailing List (not for usage questions) Cc: Zhuangzhen; anni@huawei.com; Liang, Maggie Subject: Re: [openstack-dev] Invitation to

Re: [openstack-dev] Invitation to join Hangzhou Bug Smash

OK, Got you, Sean, will let you know if there is any change. Regards. -- Shane -Original Message- From: Sean McGinnis [mailto:sean.mcgin...@gmx.com] Sent: Tuesday, June 14, 2016 3:10 AM To: OpenStack Development Mailing List (not for usage questions) Cc: Zhuangzhen; anni@huawei.com;

Re: [openstack-dev] Invitation to join Hangzhou Bug Smash

Yes, sure, we encourage every company to host bug smash at its city globally, as the company wants, but should align with us. Actually last time it followed the model, for example, we have SUSE to host at Germany, and in the last minute we have Taiwan. For Hangzhou in PRC, we are also calling

Re: [openstack-dev] [tempest][nova][defcore] Add option to disable some strict response checking for interop testing

This discussion was expected when we implemented the Tempest patch, then I sent a mail to defcore comittee[1] As the above ml, "A DefCore Guideline typically covers three OpenStack releases". That means the latest guideline needs to cover Mitaka, Liberty and Kilo, right? In the Kilo development,

[openstack-dev] [vitrage] Template Structure Change

Hi All, Please note that from today the id field in metadata section is renamed and from now it is called name. After updating your code, you should also update the templates which you are using in your setups. Any question is welcome, Liat