[openstack-dev] [nova] Nova API sub-team meeting

Hi, We have weekly Nova API meeting today. The meeting is being held Wednesday UTC1300 and irc channel is #openstack-meeting-4. The proposed agenda and meeting details are here: https://wiki.openstack.org/wiki/Meetings/NovaAPI Please feel free to add items to the agenda. Thanks ___

[openstack-dev] [Neutron][L2GW] New core member

Folks, I am pleased to announce the addition of Ofer Ben-Yakov as new core team member of L2 Gateway team. Ofer has been working hard and contributing to solidify L2GW framework as well adding new features to the L2GW. The team welcomes Ofer on board and look forward to work with him. Thanks a

[openstack-dev] [nova] Confirmation of location for Nova meetup in Hillsboro

In case anyone hasn't booked a hotel yet or hasn't noticed the updates to the wiki [1] we'll be meeting at the Holiday Inn Express now in Hillsboro. There was a scheduling conflict at the Jones Farm campus for Intel such that we couldn't fit everyone into a single room at the Intel site, so w

[openstack-dev] [Neutron][infra] Switch to xenial and Neutron unit tests

Hi Neutrinos, OpenStack infra is in the process of testing OpenStack tests on ubuntu Xenial so that it can be adopted as default platform for testing in the Gate. It is likely that the switch is going to happen sometime next week. It was noted in the channel at [1] that some unit tests are not c

Re: [openstack-dev] [Murano][user-guide][docs] Add section 'Murano applications guide' to the End User Guide

Hi Serg! I've cc'd Joseph into this mail, to make sure he sees it. Joseph looks after the User Guides speciality team within docs. To answer your question, a spec really is the best way to start with this content, it will probably also help you pick up some interested helpers. Once that's appr

Re: [openstack-dev] The future of OpenStack documentation

On 12/07/16 09:45, Matt Kassawara wrote: > Inline... > > On Sun, Jul 10, 2016 at 5:22 PM, Lana Brindley > wrote: > > On 09/07/16 07:02, Matt Kassawara wrote: > > Currently, OpenStack provides central documentation (primarily in the > openstack-manuals

[openstack-dev] [neutron] Keystone V3 alignment: renaming tenant_id columns to project_id

In accordance with the Blueprint [1] and the spec [2], we are in the process of deprecating the use of the term 'tenant' in favor of 'project'. The code change [3] with the biggest impact on Neutron developers is currently out for review and will merge quite soon (shortly after N-2). This change r

Re: [openstack-dev] [TripleO][os-net-config] add support for NFV virtual switch

On 07/07/2016 05:45 PM, Xin Wu wrote: > Hi, > > This is Xin from Big Switch. I'm proposing to make os_net_config support > DPDK switch for NFV workloads. > Current os_net_config supports ovs_bridge, linux_bridge, ivs_bridge > and different types of interfaces. The os_net_config's abstraction

Re: [openstack-dev] [kolla] New specs process - a dicussion

Something for consideration to make the specs process not to painful and one that I think (?) glance pioneered is to have a 'bigger spec' and a 'smaller spec' template. https://github.com/openstack/glance-specs/blob/master/specs/lite-specs.rst (smaller) https://github.com/openstack/glance-sp

Re: [openstack-dev] Mascot/logo for your project

On Mon, Jul 11, 2016 at 2:30 PM, Heidi Joy Tretheway wrote: > Answering a few questions: > > Snip: "Just a little strange for a community-driven open source project to > be replacing community-created mascots with top-down designs. I'm not > terribly opposed to it, but would have definitely prefer

[openstack-dev] [TripleO] Making TripleO CI easier to consume outside of TripleO CI

Howdy folks, In the TripleO meeting two weeks ago, it came up that tripleo-quickstart is being used as a CI tool in RDO. This came about organically, because we needed to use RDO CI to self-gate quickstart (it relies on having a baremetal virthost). It displaced another ansible based CI tool there

Re: [openstack-dev] [nova] focused review pipeline of bug fix changes?

On 12.07.2016 19:46, Augustina Ragwitz wrote: > I like the idea of having a list because it makes it easy for people to > see what's up for review. Anything that allows people to easily point > and click will increase visibility and participation. I also prefer the > list maintenance be as automagi

Re: [openstack-dev] [openstack-ansible] Nominating Jean-Philippe Evrard for core in openstack-ansible and all openstack-ansible-* roles

+1 and thanks for all the great work. On Tue, Jul 12, 2016 at 11:33 AM, Truman, Travis wrote: > Jean-Philippe has been providing great code reviews and patches for some > time. His recent commitment to running bug triage every week shows his > willingness to step up and take responsibilities wit

[openstack-dev] [openstack-ansible] Nominating Jean-Philippe Evrard for core in openstack-ansible and all openstack-ansible-* roles

Jean-Philippe has been providing great code reviews and patches for some time. His recent commitment to running bug triage every week shows his willingness to step up and take responsibilities within the community. He's also found an opportunity to innovate by introducing an improved bug triage

Re: [openstack-dev] [nova] focused review pipeline of bug fix changes?

On 2016-07-12 10:46:54 -0700 (-0700), Augustina Ragwitz wrote: [...] > I like #3 but I worry about the comments getting spammy if things are > dropped from and added to the list repeatedly. Would tagging the bugs in > Launchpad work? We can easily remove tags in Launchpad, it's a > query-able list,

Re: [openstack-dev] [nova] focused review pipeline of bug fix changes?

I like the idea of having a list because it makes it easy for people to see what's up for review. Anything that allows people to easily point and click will increase visibility and participation. I also prefer the list maintenance be as automagic as possible so the burden doesn't fall on one or two

Re: [openstack-dev] [Heat][Senlin] Deprecation roadmap for Heat's Autoscaling resources?

On 04/07/16 08:06, Johannes Grassler wrote: Hello, I just noticed the note at the top of : | The content on this page is obsolete. The autoscaling solution is offloaded from Heat to Senlin since Mitaka. That isn't a page about how Autoscaling

Re: [openstack-dev] [kolla] New specs process - a dicussion

+1 I agree 2016-07-12 13:55 GMT-03:00 Paul Bourke : > Sounds reasonable +1 > > > On 12/07/16 15:32, Michał Jastrzębski wrote: > >> Hey guys, >> >> Since our project matured, we decided that we should have a discussion >> regarding our spec process. >> >> https://etherpad.openstack.org/p/kolla-N-m

[openstack-dev] [Murano][user-guide][docs] Add section 'Murano applications guide' to the End User Guide

Hi, folks! I'm working on user guide about developing and using custom Murano applications. As far as I'm concerned End User Guide [1] would be a perfect fit for this document. Mainly because, it demonstarates one more way to regular cloud users, how they can consume services provided by OpenStack

Re: [openstack-dev] [ironic] why do we need setting network driver per node?

Thanks Devananda and Dmitry and Sam! From my point of view, I wanted to make sure that: 1. we agreed on whether the 'network_interface' was, or was not, an interface that was similar to the existing power, deploy, ... interfaces so that it fit into the driver composition work 2. we agreed on h

Re: [openstack-dev] [kolla] New specs process - a dicussion

Sounds reasonable +1 On 12/07/16 15:32, Michał Jastrzębski wrote: Hey guys, Since our project matured, we decided that we should have a discussion regarding our spec process. https://etherpad.openstack.org/p/kolla-N-midcycle-specs Currently we do specs for most critical things, and they requi

Re: [openstack-dev] [nova] focused review pipeline of bug fix changes?

On 12.07.2016 18:19, Chris Friesen wrote: > On 07/12/2016 01:59 AM, Markus Zoeller wrote: >> After closing the old (>18months) bug reports nobody is working on a few >> days ago [1], it became clear that the "in progress" reports are the >> majority [2]. After asking Gerrit how long it usually take

Re: [openstack-dev] [nova] focused review pipeline of bug fix changes?

On 12.07.2016 17:39, Sahid Orentino Ferdjaoui wrote: > On Tue, Jul 12, 2016 at 09:59:12AM +0200, Markus Zoeller wrote: >> After closing the old (>18months) bug reports nobody is working on a few >> days ago [1], it became clear that the "in progress" reports are the >> majority [2]. After asking Ge

Re: [openstack-dev] [kolla] New specs process - a dicussion

One thing Michal left out is we are not planning to make this change until we branch Newton, assuming there is a majority vote reached. As typical, voting will remain open for one week until either a majority has been reached or the time has expired. The deadline to vote is Tuesday 19th of July.

Re: [openstack-dev] [nova] focused review pipeline of bug fix changes?

On 07/12/2016 01:59 AM, Markus Zoeller wrote: After closing the old (>18months) bug reports nobody is working on a few days ago [1], it became clear that the "in progress" reports are the majority [2]. After asking Gerrit how long it usually takes to get a fix merged [3], this is the result:

[openstack-dev] [kosmos] new meeting time?

Hi all, The Kosmos team has shuffled a lot, and we have some prospective new members. The current meeting time of 1600 UTC may not be optimal anymore. If you’re interested in attending, can you post what times work for you? I’m in the U.S. mountain time zone, so 1500 - 2300 UTC are optimal (plu

[openstack-dev] [sahara] selecting mascot for sahara project

Hi, I've created an etherpad [0] to discuss mascots for sahara project. All details located at the etherpad. [0] https://etherpad.openstack.org/p/sahara-mascot -- Best Regards, Vitaly Gridnev, Project Technical Lead of OpenStack DataProcessing Program (Sahara) Mirantis, Inc __

Re: [openstack-dev] [nova] focused review pipeline of bug fix changes?

On Tue, Jul 12, 2016 at 09:59:12AM +0200, Markus Zoeller wrote: > After closing the old (>18months) bug reports nobody is working on a few > days ago [1], it became clear that the "in progress" reports are the > majority [2]. After asking Gerrit how long it usually takes to get a fix > merged [3],

[openstack-dev] [glance] selecting project mascot

Hi, Please find this etherpad [1] for helping collaboratively choose Glance project mascot. All the information needed to help understand the process is in the etherpad. There are quite a few proposals already. Please note the poll closes Monday July 18th so please cast your votes as soon as po

[openstack-dev] [puppet] mascot/logo ideas

Hey, During the meeting we decided to use etherpad to submit new ideas for our mascot / logo [1]: https://etherpad.openstack.org/p/puppet-openstack-mascot-logo Feel free to use your imagination as long you stay SFW :-) Thanks, [1] http://osdir.com/ml/openstack-dev/2016-07/msg00456.html -- Emil

Re: [openstack-dev] [kolla] New specs process - a dicussion

On Jul 12, 2016 8:04 PM, "Michał Jastrzębski" wrote: > > Hey guys, > > Since our project matured, we decided that we should have a discussion > regarding our spec process. > > https://etherpad.openstack.org/p/kolla-N-midcycle-specs > > Currently we do specs for most critical things, and they requi

[openstack-dev] [kolla] New specs process - a dicussion

Hey guys, Since our project matured, we decided that we should have a discussion regarding our spec process. https://etherpad.openstack.org/p/kolla-N-midcycle-specs Currently we do specs for most critical things, and they require majority vote. We want to introduce another way, to enable non-nu

Re: [openstack-dev] [Swift] xbcloud with Swift Mitaka

Hi Tim, How are you? Thanks a lot for the quick response. I've change the cmd to point to the VIP of the KEYSTONE cluster and now I'm getting another error msg: *# innobackupex ... | xbcloud put --storage=swift --swift-auth-url=http://VIP-KEYSTONE:8080/ --swift-auth

Re: [openstack-dev] [Swift] xbcloud with Swift Mitaka

Hi German, It looks like you're using the Swift proxy server in your auth URL. Since Keystone is handling user authentication, you'll want to use that server. As part of the auth response, Keystone will provide a catalog of services which should include Swift, and I expect your client will use

Re: [openstack-dev] [Nova] Quick poll for live migration meeting this week

Just to confirm, next meeting will be after the mid cycle, I will update the agenda nearer the time: https://wiki.openstack.org/wiki/Meetings/NovaLiveMigration Paul From: Murray, Paul (HP Cloud) Sent: 11 July 2016 13:32 To: openstack-dev@lists.openstack.org Subject: [openstack-dev] [Nova] Quick

[openstack-dev] [neutron][qos][drivers] RFE about QoS extended validation

I'd like to ask for some prioritization on this RFE [1], since it's blocking one of the already existing RFEs for RFE (ingress bandwidth limiting), and we're trying to enhance the operator experience on the QoS service. It's been discussed on previous driver meetings, and it seems to have some con

Re: [openstack-dev] [cinder] [nova] os-brick privsep failures and an upgrade strategy?

On 7/12/2016 6:29 AM, Ivan Kolodyazhny wrote: Hi team, Do we have any decision on this issue? I've found few patches but both of them are -1'ed. From Cinder perspective, it blocks us to release new os-brick with features, which are needed for other projects like Cinder and python-brick-cindercl

[openstack-dev] [Swift] xbcloud with Swift Mitaka

Hi all, I've a new Swift cluster with Mitaka release using Fernet tokens. Everything works fine for now, but I want to try to backup some MySQL databases using Percona xbcloud, and I'm having some issues there, has anyone use this tool with Swift Mitaka? Basically I'm using the following syntax:

Re: [openstack-dev] [ironic] why do we need setting network driver per node?

Thanks for writing this up, minor comments inline. On 07/11/2016 10:57 PM, Devananda van der Veen wrote: We spent the majority of today's weekly IRC meeting [1] discussing the finer points of this question. I agreed to post a summary of those to the list (it's below the break). tldr; * we don'

Re: [openstack-dev] [cinder] [nova] os-brick privsep failures and an upgrade strategy?

Hi team, Do we have any decision on this issue? I've found few patches but both of them are -1'ed. >From Cinder perspective, it blocks us to release new os-brick with features, which are needed for other projects like Cinder and python-brick-cinderclient-ext. Regards, Ivan Kolodyazhny, http://bl

[openstack-dev] [ironic][neutron][nova] Sync port state changes.

Hello Community, I'm working to make Ironic be aware about Neutron port state changes [0]. The issue consists of two parts: - Neutron ports for baremetal instances remain in DOWN state [1]. The issue occurs because there is no mechanism driver that binds ports. To solve it we need to cr

Re: [openstack-dev] [Bilean][CloudKitty][Telemetry] Opendiscussionaround Bilean and existing OpenStack components

On Fri, Jul 08 2016, Stéphane Albert wrote: > About your health check, we've got an API on top of the storage and a > way to generate report, you can easily get the current total for a > specific user (1 API call). You can implement this with a simple cron > querying the API with the user_id, and

Re: [openstack-dev] [Openstack] Naming polls - and some issues

On 07/12/2016 05:58 PM, Daniel P. Berrange wrote: > On Tue, Jul 12, 2016 at 05:40:07PM +0800, Monty Taylor wrote: >> Hey all! >> >> The poll emails for the P and Q naming have started to go out - and >> we're experiencing some difficulties. Not sure at the moment what's >> going on ... but we'll ke

Re: [openstack-dev] [Openstack] Naming polls - and some issues

On Tue, Jul 12, 2016 at 05:40:07PM +0800, Monty Taylor wrote: > Hey all! > > The poll emails for the P and Q naming have started to go out - and > we're experiencing some difficulties. Not sure at the moment what's > going on ... but we'll keep working on the issues and get ballots to > everyone a

[openstack-dev] Naming polls - and some issues

Hey all! The poll emails for the P and Q naming have started to go out - and we're experiencing some difficulties. Not sure at the moment what's going on ... but we'll keep working on the issues and get ballots to everyone as soon as we can. Sorry for any confusion. Monty __

[openstack-dev] [nova] focused review pipeline of bug fix changes?

After closing the old (>18months) bug reports nobody is working on a few days ago [1], it became clear that the "in progress" reports are the majority [2]. After asking Gerrit how long it usually takes to get a fix merged [3], this is the result: number of merged bug fixes within the last 365

Re: [openstack-dev] [Nova] [RFC] ResourceProviderTags - Manage Capabilities with ResourceProvider

Some thoughts of “Capability” use cases: 1. Nova-compute service can discover host capabilities and tag them into its compute-node resource provider record. 2. Other services such as ironic and cinder may want to manage its resource pool, and they can tag capabilities themselves to that pool. 3.

Re: [openstack-dev] [Fuel] New version of fuel-devops (2.9.21)

On 07/12/2016 09:24 AM, Bogdan Dobrelya wrote: > Thank you for a hard work, that's a really great tool. > > Anyone who is interested, please note that fuel-devops, despite of the > name, may be used outside of Fuel and OpenStack as a really fast and > easy way to spin up VMs for a dev envs. Almost

Re: [openstack-dev] [Fuel] New version of fuel-devops (2.9.21)

Thank you for a hard work, that's a really great tool. Anyone who is interested, please note that fuel-devops, despite of the name, may be used outside of Fuel and OpenStack as a really fast and easy way to spin up VMs for a dev envs. Almost like a Vagrant, although it gives you advanced templates

[openstack-dev] [nova] Can not rebuild boot-from-volume instance

Hi, all I booted a new instance from a volume and then attached an other volume to it, and created image for the instance whos block_device_mapping like this: | block_device_mapping | [{"guest_format": null, "boot_index": 0, "delete_on_termination": false, | | "no_devic