Re: [openstack-dev] [Glance][Glare] External locations design

Hi Kairat, I think it's great to try and tease through the various issues here. I added some comments to the etherpad. -Stuart Hello all, I would like to start to describe some design decisions we made in Glare code (https://review.openstack.org/#/q/topic:bp/glare-api+status:open). If you

Re: [openstack-dev] Nominate Vladimir Khlyunev for fuel-qa core

+1 On Tue, Aug 2, 2016 at 12:51 PM, Artur Svechnikov wrote: > +1 > > Best regards, > Svechnikov Artur > > On Tue, Aug 2, 2016 at 12:40 PM, Andrey Sledzinskiy < > asledzins...@mirantis.com> wrote: > >> Hi, >> I'd like to nominate Vladimir Khlyunev for fuel-qa [0] core.

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

On 2016-08-01 3:25 PM, Julia Kreger wrote: Greetings! As discussed in our meeting today[0], we would like to try and schedule a time for a VoIP call so we can discuss driver composition[1] defaults with the goal of reaching a consensus on defaults. Reading a January meeting log surprised

[openstack-dev] 答复: How to change openstack ID email

I never register with my gmail address, When I login with my gmail address, it prints "we are sorry, your username and password does not match an existing record". I think the question is my new email is not verified, can you tell me who can help to verify it? -邮件原件- 发件人: Tom Fifield

[openstack-dev] 答复: [neutron][dvr][fip] fg device allocated private ip address

Hi, You can leverage neutron-dynamic-routing to advertise floating ip to external router. https://github.com/openstack/neutron-dynamic-routing/blob/master/doc/source/functionality/route-advertisement.rst 发件人: huangdenghui [mailto:hdh_1...@163.com] 发送时间: 2016年8月2日 20:16 收件人: John Davidge 抄送:

[openstack-dev] Nominate Vladimir Khlyunev for fuel-qa core

Hi, I'd like to nominate Vladimir Khlyunev for fuel-qa [0] core. Vladimir has become a valuable member of fuel-qa project in quite short period of time. His solid expertise and constant contribution gives me no choice but to nominate him for fuel-qa core. If anyone has any objections, speak now

Re: [openstack-dev] Nominate Vladimir Khlyunev for fuel-qa core

+1 Best regards, Svechnikov Artur On Tue, Aug 2, 2016 at 12:40 PM, Andrey Sledzinskiy < asledzins...@mirantis.com> wrote: > Hi, > I'd like to nominate Vladimir Khlyunev for fuel-qa [0] core. > > Vladimir has become a valuable member of fuel-qa project in quite short > period of time. His solid

Re: [openstack-dev] [tc] persistently single-vendor projects

On Mon, 1 Aug 2016, James Bottomley wrote: Making no judgments about the particular exemplars here, I would just like to point out that one reason why projects exist with very little diversity is that they "just work". Usually people get involved when something doesn't work or they need

Re: [openstack-dev] [docker] [magnum] Magnum account on Docker Hub

Ton, I may or may not have set it up early in Magnum's development. I just don't remember. My recommendation is to file a support ticket with docker and see if they will tell you who it belongs to (as in does it belong to one of the founders of Magnum) or if it belongs to some other third

Re: [openstack-dev] 回复： [neutron]dragonflow deployment incorrectness

If you deploy dragonflow by devstack, please provide local.conf. Dragonflow uses df-l3-agent for SNAT only. On Thu, Jul 28, 2016 at 11:45 AM, shihanzhang wrote: > As I know, now dragonflow still use neutron l3-agent for snat, so the > l3-agent is enabled and router

Re: [openstack-dev] Nominate Vladimir Khlyunev for fuel-qa core

A huge +1, Vladimir make a great job! On Tue, Aug 2, 2016 at 1:52 PM, Dmitry Tyzhnenko wrote: > +1 > > On Tue, Aug 2, 2016 at 12:51 PM, Artur Svechnikov < > asvechni...@mirantis.com> wrote: > >> +1 >> >> Best regards, >> Svechnikov Artur >> >> On Tue, Aug 2, 2016 at

Re: [openstack-dev] How to change openstack ID email

Hi, Did you try logging in with your @gmail.com address ? :) Regards, Tom On 02/08/16 19:04, zhuna wrote: Dear, I had an openstack ID with my company email address(na...@cn.ibm.com), I change my company recently, so I add an company affiliation with my new company name. Now the question

Re: [openstack-dev] [kolla] Why base image always be built each time build a specific image.

Zhijiang, You will see lines relating to the base image each time you build, however, they should be cached so will add almost no additional time to the build. -Paul On 21/07/16 09:48, hu.zhiji...@zte.com.cn wrote: Hi, When I use the following command to build keystone image, I saw

Re: [openstack-dev] [neutron][dvr][fip] fg device allocated private ip address

hi john and brain thanks for your information, if we get patch[1],patch[2] merged,then fg can allocate private ip address. after that, we need consider floating ip dataplane, in current dvr implementation, fg is used to reachment testing for floating ip, now,with subnet types bp,fg has

[openstack-dev] [requirements] race in keystone unit tests

One of my concerns about stacking up project unit tests in the requirements jobs, is the unit tests aren't as free of races as you would imagine. Because they only previously impacted the one project team, those teams are often just fast to recheck instead of get to the bottom of it. Cross testing

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

We discussed the possible technical solutions but didn't get attention if we see the need to do that. As none of the core reviewers or subteam leaders reacted to the proposal, I conclude that this is not an issue where we need to put our limited resources at. This post is just informational to

Re: [openstack-dev] Nominate Vladimir Khlyunev for fuel-qa core

+1 On Tue, Aug 2, 2016 at 1:52 PM, Dmitry Tyzhnenko wrote: > +1 > > On Tue, Aug 2, 2016 at 12:51 PM, Artur Svechnikov < > asvechni...@mirantis.com> wrote: > >> +1 >> >> Best regards, >> Svechnikov Artur >> >> On Tue, Aug 2, 2016 at 12:40 PM, Andrey Sledzinskiy < >>

[openstack-dev] [nova] [scheduler] Use ResourceProviderTags instead of ResourceClass?

Chris have a thought about using ResourceClass to describe Capabilities with an infinite inventory. In the beginning we brain storming the idea of Tags, Tan Lin have same thought, but we say no very quickly, due to the ResourceClass is really about Quantitative stuff. But Chris give very good

Re: [openstack-dev] [tc] persistently single-vendor projects

On 08/02/2016 06:16 AM, Chris Dent wrote: > On Mon, 1 Aug 2016, James Bottomley wrote: > >> Making no judgments about the particular exemplars here, I would just >> like to point out that one reason why projects exist with very little >> diversity is that they "just work". Usually people get

Re: [openstack-dev] [gnocchi] Support for other drivers - influxdb

On Tue, Aug 02 2016, Sam Morrison wrote: Hi Sam! > We have been using gnocchi for a while now with the influxDB driver > and are keen to get the influxdb driver back into upstream. > > However looking into the code and how it’s arranged it looks like > there are a lot of assumptions that the

[openstack-dev] [nova] bugs team IRC meeting: biweekly-odd timeslot?

2 months ago I moved the biweekly-odd timeslot from 1000 to 0800 UTC [1] in the hope to be more accessible for folks in Asia. After these 2 months it got evident that this didn't work out. The number of participating people decreased. I'd like to move that meeting to another timeslot which fits

[openstack-dev] error when restarting new driver

Hi all, I am getting the following error when I try to create a new cinder volume 2016-08-02 15:26:06.445 DEBUG cinder.scheduler.base_filter [req-cce76948-5eac-44d0-9d0c-115cfc03cb57 42ba08e7a7544cd28812de21aa5ce39e de3f38612acd4ec7a24c0325bd11389f] Starting with 0 host(s) from (pid=3023)

[openstack-dev] How to change openstack ID email

Dear, I had an openstack ID with my company email address(na...@cn.ibm.com), I change my company recently, so I add an company affiliation with my new company name. Now the question is I can not login openstack (https://openstackid.org/accounts/user/login) by

Re: [openstack-dev] [ironic] [nova] [neutron] get_all_bw_counters in the Ironic virt driver

On 29 July 2016 at 19:58, Sean Dague wrote: > On 07/29/2016 02:29 PM, Jay Pipes wrote: >> On 07/28/2016 09:02 PM, Devananda van der Veen wrote: >>> On 07/28/2016 05:40 PM, Brad Morgan wrote: I'd like to solicit some advice about potentially implementing

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

On 29/07/2016 21:59, Doug Hellmann wrote: > One of the outcomes of the discussion at the leadership training > session earlier this year was the idea that the TC should set some > community-wide goals for accomplishing specific technical tasks to > get the projects synced up and moving in the same

[openstack-dev] [neutron][upgrades] Bi-weekly upgrades work status. 8/2/2016

Hi Neutrinos, As we are progressing with object implementation for neutron database resources, I would like to summarize the status. Please find the etherpad as up-to-date work status on object progress, TODOs/In progress/Done items: https://etherpad.openstack.org/p/newton-ovo-progress This

Re: [openstack-dev] [tc] persistently single-vendor projects

On 8/1/16, 8:38 AM, "Doug Hellmann" wrote: >Excerpts from Adrian Otto's message of 2016-08-01 15:14:48 +: >> I am struggling to understand why we would want to remove projects from >>our big tent at all, as long as they are being actively developed under >>the

[openstack-dev] [juju charms] How to configure glance charm for specific cnider backend?

Hi All, I need to add glance support via storing images in cinder instead of local files. (This works only from Mitaka version due to glance-store package) First step I've made here - https://review.openstack.org/#/c/348336/ This patchset adds ability to relate glance-charm to cinder-charm (it's

[openstack-dev] [nova][tempest] testing different configurations by exploiting the mutate attribute?

IIUC, each gate testing job has a *fixed configuration* which will never be changed when executing *all* tempest tests. If I need to test a specific configuration, a new testing job is needed. As we have a limited amount of test nodes, this creates testing gaps as we cannot test all

[openstack-dev] [ironic] weekly subteam status report

Hi, We are yodelling to present this week's subteam report for Ironic. As usual, this is pulled directly from the Ironic whiteboard[0] and formatted. Bugs (dtantsur) === - Stats (diff with 18 July 2016) - Ironic: 216 bugs (+15) + 204 wishlist items (+3). 21 new (+8), 160 in progress

Re: [openstack-dev] [kolla] Why base image always be built each time build a specific image.

Paul, I think the cache isn't working exactly as you described for the base image. Not sure what is going on there - it could just be my misperception. However, as you point out the time spent "rebuilding" the base image is very small (under 30 seconds) so I don't believe its a pressing

[openstack-dev] pydotplus (taskflow) vs pydot-ng (fuel)

Hi, Fuel uses pydot-ng, and (at least) taskflow uses pydotplus. I believe both aren't using pydot because that's dead upstream. Could we have a bit of consistency here, and have one or the other component to switch, so we could get rid of one more package that does the same thing in downstream

Re: [openstack-dev] [Nova] Does this api modification need Microversion?

On Aug 2, 2016, at 1:11 AM, han.ro...@zte.com.cn wrote: > Allow "revert_resize" to recover error instance after resize/migrate. > > When resize/migrate instance, if error occurs on source compute node, > instance state can rollback to active currently. But if error occurs in > "finish_resize"

Re: [openstack-dev] [tc] persistently single-vendor projects

On 8/2/16, 7:17 AM, "Ed Leafe" wrote: >On Aug 2, 2016, at 8:50 AM, Steven Dake (stdake) wrote: > >> For example tripleo is single-vendor, but is doing all the right things >>to >> dig out of single vendor by doing actual community building. They >>aren't >>

Re: [openstack-dev] [tripleo] service validation during deployment steps

What about ability of service expert to plug-in remediation module? If remediation action succeed - proceed, if not then stop. Remediation module can be extended independently from main flow. Thanks, Arkady -Original Message- From: Steven Hardy [mailto:sha...@redhat.com] Sent: Wednesday,

Re: [openstack-dev] [tc] persistently single-vendor projects

Excerpts from Chris Dent's message of 2016-08-02 11:16:29 +0100: > On Mon, 1 Aug 2016, James Bottomley wrote: > > > Making no judgments about the particular exemplars here, I would just > > like to point out that one reason why projects exist with very little > > diversity is that they "just

[openstack-dev] [horizon] Angular panel enable/disable not overridable in local_settings

Hi all, So we seem to be adopting a pattern of using UPDATE_HORIZON_CONFIG in the enabled files to add a legacy/angular toggle to the settings. I don't like this, because in settings.py the enabled files are processed *after* local_settings.py imports, meaning the angular panel will always be

Re: [openstack-dev] [ironic] [nova] [neutron] get_all_bw_counters in the Ironic virt driver

On 8/2/2016 6:22 AM, John Garbutt wrote: On 29 July 2016 at 19:58, Sean Dague wrote: On 07/29/2016 02:29 PM, Jay Pipes wrote: On 07/28/2016 09:02 PM, Devananda van der Veen wrote: On 07/28/2016 05:40 PM, Brad Morgan wrote: I'd like to solicit some advice about potentially

Re: [openstack-dev] [tc] persistently single-vendor projects

On Aug 2, 2016, at 8:50 AM, Steven Dake (stdake) wrote: > For example tripleo is single-vendor, but is doing all the right things to > dig out of single vendor by doing actual community building. They aren't > just trying, but are trying *very* hard with their activities.

Re: [openstack-dev] pydotplus (taskflow) vs pydot-ng (fuel)

Hi Thomas, If I'm not mistaken, pydot-ng [1] has been made by ex-fueler in order to overcome some limitations of pydot ( and do not change much. If pydotplus is alive project and do the same thing, I vote for using it in Fuel. Thanks, Igor [1]: https://pypi.io/project/pydot-ng/ On Tue, Aug 2,

Re: [openstack-dev] [puppet] weekly meeting #89

first agenda: > https://etherpad.openstack.org/p/puppet-openstack-weekly-meeting-20160802 > > Feel free to add topics, and any outstanding bug and patch. > > See you tomorrow! > Thanks, > -- > Emilien Macchi -- Emilien Macchi

Re: [openstack-dev] [nova] os-virtual-interfaces isn't deprecated in 2.36

On 8/2/2016 2:41 AM, Alex Xu wrote: A little strange we have two API endpoints, one is '/servers/{uuid}/os-interfaces', another one is '/servers/{uuid}/os-virtual-interfaces'. I prefer to keep os-attach-interface. Due to I think we should deprecate the nova-network also. Actually we deprecate

Re: [openstack-dev] [tc] persistently single-vendor projects

On 02/08/2016 15:42, Flavio Percoco wrote: > On 01/08/16 10:19 -0400, Sean Dague wrote: >> On 08/01/2016 09:58 AM, Davanum Srinivas wrote: >>> Thierry, Ben, Doug, >>> >>> How can we distinguish between. "Project is doing the right thing, but >>> others are not joining" vs "Project is actively

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

Excerpts from Shamail's message of 2016-08-01 22:37:28 -0500: > Thanks Doug, > > > On Aug 1, 2016, at 10:44 AM, Doug Hellmann wrote: > > > > Excerpts from Shamail Tahir's message of 2016-08-01 09:49:35 -0500: > >>> On Mon, Aug 1, 2016 at 7:58 AM, Doug Hellmann

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

Excerpts from Hayes, Graham's message of 2016-08-02 11:53:37 +: > On 29/07/2016 21:59, Doug Hellmann wrote: > > One of the outcomes of the discussion at the leadership training > > session earlier this year was the idea that the TC should set some > > community-wide goals for accomplishing

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

On 02/08/2016 14:37, Doug Hellmann wrote: > Excerpts from Hayes, Graham's message of 2016-08-02 11:53:37 +: >> On 29/07/2016 21:59, Doug Hellmann wrote: >>> One of the outcomes of the discussion at the leadership training >>> session earlier this year was the idea that the TC should set some

Re: [openstack-dev] [requirements] race in keystone unit tests

Hi Sean, Thanks for the information. This obviously looks Fernet-related and I would be happy to spend some cycles on it. We recently landed a bunch of refactors in keystone to improve Fernet test coverage. This could be related to those refactors. Just double checking - but you haven't opened a

Re: [openstack-dev] [tc] persistently single-vendor projects

On 02/08/16 09:17 -0500, Ed Leafe wrote: On Aug 2, 2016, at 8:50 AM, Steven Dake (stdake) wrote: For example tripleo is single-vendor, but is doing all the right things to dig out of single vendor by doing actual community building. They aren't just trying, but are trying

[openstack-dev] [puppet] Temporarily unstable Fuel deployment test jobs

Dear colleagues, Please be informed that we are going to merge some patches on 08/02/2016 to Fuel repositories to switch from Mitaka to Newton packages. These patches will likely distabilize Fuel deployment tests for several days. We are going fix all major features till 08/08/2016 and get these

Re: [openstack-dev] [docker] [magnum] Magnum account on Docker Hub

I just filed a ticket to acquire the username openstackmagnum. I included Hongbin's contact information explaining that he's the project's PTL. Thanks Steve, Spyros On 2 August 2016 at 13:29, Steven Dake (stdake) wrote: > Ton, > > I may or may not have set it up early in

Re: [openstack-dev] [tc] persistently single-vendor projects

On 01/08/16 10:19 -0400, Sean Dague wrote: On 08/01/2016 09:58 AM, Davanum Srinivas wrote: Thierry, Ben, Doug, How can we distinguish between. "Project is doing the right thing, but others are not joining" vs "Project is actively trying to keep people out"? I think at some level, it's not

[openstack-dev] [nova] Removal of live_migration_flag and block_migration_flag config options

In Mitaka development cycle 'live_migration_flag' and 'block_migration_flag' have been marked as deprecated for removal. I'm working on a patch [1] to remove both of them and want to ask what we should do with live_migration_tunnelled logic. The default configuration of both flags contain

Re: [openstack-dev] [tc] persistently single-vendor projects

On 01/08/16 10:28 -0400, Davanum Srinivas wrote: Sean, So we will programatically test the metrics (if we are not doing that already) to apply/remove "team:single-vendor" tag: https://governance.openstack.org/reference/tags/team_single-vendor.html And trigger exit when the tag is present for

Re: [openstack-dev] [infra] Switch 'all?' openstack bots to errbot plugins?

On 29/07/16 13:57 -0400, Doug Hellmann wrote: Excerpts from Joshua Harlow's message of 2016-07-29 10:35:18 -0700: I prefer 'one bucket repo for OpenStack community Errbot plug-ins' since I don't like a bunch of repos (seems like a premature optimization ~at this time~), but I could see either

Re: [openstack-dev] [Neutron][IPAM] Pluggable IPAM rollback issue

On Aug 2, 2016 6:52 PM, "Kevin Benton" wrote: > > >It might be the wrong impression, but it was already given and there are drivers which have been written under it. That's why I tend toward fixing rollback instead of eliminating it. > > The reason I thought it was relevant to

Re: [openstack-dev] [neutron][dvr][fip] fg device allocated private ip address

On Tue, Aug 2, 2016 at 6:15 AM, huangdenghui wrote: > hi john and brain >thanks for your information, if we get patch[1],patch[2] merged,then fg > can allocate private ip address. after that, we need consider floating ip > dataplane, in current dvr implementation, fg is

Re: [openstack-dev] [Neutron][IPAM] Pluggable IPAM rollback issue

>It might be the wrong impression, but it was already given and there are drivers which have been written under it. That's why I tend toward fixing rollback instead of eliminating it. The reason I thought it was relevant to bring up is because it's going to be difficult to actually fix it. If any

Re: [openstack-dev] [nova] Removal of live_migration_flag and block_migration_flag config options

If operator haven't explicitly defined live_migration_tunnelled param in nova.conf, after upgrade is done it's default value will be set to False. If operator set this param explicitly, everything will be unchanged. To notify about this change I'm proposing to use release notes, as It's usually

[openstack-dev] How to create a image using http img file

refer to: glance client Python API v2 http://docs.openstack.org/developer/python-glanceclient/ref/v2/images.html add_location(image_id, url, metadata) Add a new location entry to an image’s list of locations. It is an error to add a URL that is already present in the list of locations.

Re: [openstack-dev] [TripleO] Improving Swift deployments with TripleO

On Tue, Aug 02, 2016 at 09:36:45PM +0200, Christian Schwede wrote: > Hello everyone, > > I'd like to improve the Swift deployments done by TripleO. There are a > few problems today when deployed with the current defaults: Thanks for digging into this, I'm aware this has been something of a

Re: [openstack-dev] [horizon] Angular panel enable/disable not overridable in local_settings

On 3 August 2016 at 00:32, Rob Cresswell wrote: > Hi all, > > So we seem to be adopting a pattern of using UPDATE_HORIZON_CONFIG in the > enabled files to add a legacy/angular toggle to the settings. I don't like > this, because in settings.py the enabled files are

Re: [openstack-dev] How to create a image using http img file

As the error said, you need to see the disk_format and container_format. I haven't digged the code, but I think you should try to set the container_format and disk_format when you create the image like this: image = self.glance.images.create(name="myNewImage",

[openstack-dev] [ironic] Priorities for the rest of the cycle

Hey all, There's some deadlines coming up: * non-client library freeze in 3 weeks * client library freeze in 4 weeks * final releases in 8 weeks http://releases.openstack.org/newton/schedule.html As usual, we don't do a hard feature freeze at the normal feature freeze date (4 weeks from now),

Re: [openstack-dev] [nova] os-virtual-interfaces isn't deprecated in 2.36

On 8/2/2016 9:09 AM, Matt Riedemann wrote: On 8/2/2016 2:41 AM, Alex Xu wrote: A little strange we have two API endpoints, one is '/servers/{uuid}/os-interfaces', another one is '/servers/{uuid}/os-virtual-interfaces'. I prefer to keep os-attach-interface. Due to I think we should deprecate

Re: [openstack-dev] [Neutron][IPAM] Pluggable IPAM rollback issue

On Tue, Aug 2, 2016 at 2:50 AM, Kevin Benton wrote: > >Given that it shares the session, it wouldn't have to do anything. But, > again, it wouldn't behave like an external driver. > Why not? The only additional thing an external driver would be doing at > this step is calling

Re: [openstack-dev] [nova] Removal of live_migration_flag and block_migration_flag config options

Hi, Taking into account everything above I'd prefer to see live_migration_tunnelled(that corresponds to VIR_MIGRATE_TUNNELLED) defaulted to False. We just need to make a release note for this change, and on the host startup do LOG.warning to notify the operator that there are no tunnels for

Re: [openstack-dev] [juju charms] How to configure glance charm for specific cnider backend?

Hi Andrey On Tue, 2 Aug 2016 at 15:59 Andrey Pavlov wrote: > I need to add glance support via storing images in cinder instead of > local files. > (This works only from Mitaka version due to glance-store package) > OK > First step I've made here - >

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

Doug Hellmann wrote: > [...] >> Likewise, what if the Manila project team decides they aren't interested >> in supporting Python 3.5 or a particular greenlet library du jour that >> has been mandated upon them? Is the only filesystem-as-a-service project >> going to be booted from the tent? >

Re: [openstack-dev] [nova][ironic] A couple feature freeze exception requests

> Multitenant networking > == I haven't reviewed this one much either, but it looks smallish and if other people are good with it then I think it's probably something we should do. > Multi-compute usage via a hash ring > === I'm obviously +2

Re: [openstack-dev] [juju charms] How to configure glance charm for specific cnider backend?

James, thank you for your answer. I'll file bug to glance - but in current releases glance-charm have to do it himself, right? I'm not sure that I'm correctly understand your question. I suppose that deployment will have glance and cinder on different machines. Also there will be one relation

Re: [openstack-dev] [tc] persistently single-vendor projects

> On 02 Aug 2016, at 17:13, Hayes, Graham wrote: > > On 02/08/2016 15:42, Flavio Percoco wrote: >> On 01/08/16 10:19 -0400, Sean Dague wrote: >>> On 08/01/2016 09:58 AM, Davanum Srinivas wrote: Thierry, Ben, Doug, How can we distinguish between. "Project is

Re: [openstack-dev] [tc] persistently single-vendor projects

On 02/08/2016 16:48, Steven Dake (stdake) wrote: > Responses inline: > > On 8/2/16, 8:13 AM, "Hayes, Graham" wrote: > >> On 02/08/2016 15:42, Flavio Percoco wrote: >>> On 01/08/16 10:19 -0400, Sean Dague wrote: On 08/01/2016 09:58 AM, Davanum Srinivas wrote: >

Re: [openstack-dev] [nova][ironic] A couple feature freeze exception requests

On 8/1/2016 4:20 PM, Jim Rollenhagen wrote: Yes, I know this is stupid late for these. I'd like to request two exceptions to the non-priority feature freeze, for a couple of features in the Ironic driver. These were not requested at the normal time as I thought they were nowhere near ready.

Re: [openstack-dev] [tc] persistently single-vendor projects

Responses inline: On 8/2/16, 8:13 AM, "Hayes, Graham" wrote: >On 02/08/2016 15:42, Flavio Percoco wrote: >> On 01/08/16 10:19 -0400, Sean Dague wrote: >>> On 08/01/2016 09:58 AM, Davanum Srinivas wrote: Thierry, Ben, Doug, How can we distinguish between.

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

On 08/02/2016 11:29 AM, Thierry Carrez wrote: Doug Hellmann wrote: [...] Likewise, what if the Manila project team decides they aren't interested in supporting Python 3.5 or a particular greenlet library du jour that has been mandated upon them? Is the only filesystem-as-a-service project

Re: [openstack-dev] [neutron][dvr][fip] fg device allocated private ip address

I still have a problem about the fg device with private ip address. In DVR mode, there is a external ip address in fq device, because we need to figure out the default route. If the fg device with a private ip address, how do we figure out the default route in fip namespace? Default route is

Re: [openstack-dev] [Openstack-operators] [neutron][horizon][announce] Introducing DON

Great! This is much needed. We will be glad to help in anyway possible. Regards, Amit On Wed, Aug 3, 2016 at 12:02 AM, Ihar Hrachyshka wrote: > Amit Kumar Saha (amisaha) wrote: > > Hi, >> >> We would like to introduce the community to a new Python based

[openstack-dev] [meghdwar] use case for meghdwar API irc call agenda

Hi all, Please join the meeting  for API and codes decision  Meeting Wednesday 3rd August      (14 Hr-15 Hr UTC )   [7AM-8AM PDT] irc #openstck-megdwar Follow up on same points with updates aslast meeting.Since we had a irc issues last week we plan to conduct this meeting instead of skipping and

Re: [openstack-dev] [Openstack] [networking-sfc] Flow classifier conflict logic

Please send the tenant ids of all six neutron ports. >From admin:neutron port-show | grep tenant_id Thanks,Farhad. On Monday, August 1, 2016 7:44 AM, Artem Plakunov wrote: Thanks. You said though that classifier must be unique within a tenant. I tried

[openstack-dev] [Manila] Migration APIs 2-phase vs. 1-phase

It occurred to me that if we write the 2-phase migration APIs correctly, then it will be fairly trivial to implement 1-phase migration outside Manila (in the client, or even higher up). I would like to propose that we change the migration API to actually work that way, because I think it will

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

Excerpts from Hayes, Graham's message of 2016-08-02 16:30:06 +: > On 02/08/2016 16:37, Doug Hellmann wrote: > > Excerpts from Hayes, Graham's message of 2016-08-02 13:49:06 +: > >> On 02/08/2016 14:37, Doug Hellmann wrote: > >>> Excerpts from Hayes, Graham's message of 2016-08-02 11:53:37

[openstack-dev] [neutron][horizon][announce] Introducing DON

Hi, We would like to introduce the community to a new Python based project called DON - Diagnosing OpenStack Networking. More details about the project can be found at https://github.com/openstack/python-don. DON, written primarily in Python, and available as a dashboard in OpenStack Horizon,

Re: [openstack-dev] [HA] RFC: High Availability track at future Design Summits

Hi Thierry, Thierry Carrez wrote: > Adam Spiers wrote: > > I doubt anyone would dispute that High Availability is a really > > important topic within OpenStack, yet none of the OpenStack > > conferences or Design Summits so far have provided an "official" track > > or

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

On 02/08/2016 16:37, Doug Hellmann wrote: > Excerpts from Hayes, Graham's message of 2016-08-02 13:49:06 +: >> On 02/08/2016 14:37, Doug Hellmann wrote: >>> Excerpts from Hayes, Graham's message of 2016-08-02 11:53:37 +: On 29/07/2016 21:59, Doug Hellmann wrote: > One of the

Re: [openstack-dev] [nova] Belated nova newton midcycle recap (part 2)

On Mon, Aug 01, 2016 at 09:15:46PM -0500, Matt Riedemann wrote: > > > > * Placement API for resource providers > > Jay's personal goal for Newton is for the resource tracker to be writing > inventory and allocation data via the placement API. We want to get the data > writing into the

[openstack-dev] [new][oslo] oslo.concurrency 3.13.0 release (newton)

We are eager to announce the release of: oslo.concurrency 3.13.0: Oslo Concurrency library This release is part of the newton release series. With source available at: http://git.openstack.org/cgit/openstack/oslo.concurrency With package available at:

[openstack-dev] [new][oslo] mox3 0.18.0 release (newton)

We are glad to announce the release of: mox3 0.18.0: Mock object framework for Python This release is part of the newton release series. With source available at: http://git.openstack.org/cgit/openstack/mox3 With package available at: https://pypi.python.org/pypi/mox3 Please report

[openstack-dev] [new][oslo] debtcollector 1.7.0 release (newton)

We are glowing to announce the release of: debtcollector 1.7.0: A collection of Python deprecation patterns and strategies that help you collect your technical debt in a non- destructive manner. This release is part of the newton release series. With source available at:

[openstack-dev] [new][oslo] oslo.cache 1.12.0 release (newton)

We are enthusiastic to announce the release of: oslo.cache 1.12.0: Cache storage for Openstack projects. This release is part of the newton release series. With source available at: http://git.openstack.org/cgit/openstack/oslo.cache With package available at:

[openstack-dev] [new][oslo] oslo.versionedobjects 1.14.0 release (newton)

We are satisfied to announce the release of: oslo.versionedobjects 1.14.0: Oslo Versioned Objects library This release is part of the newton release series. With source available at: http://git.openstack.org/cgit/openstack/oslo.versionedobjects With package available at:

[openstack-dev] [new][oslo] oslo.serialization 2.12.0 release (newton)

We are jazzed to announce the release of: oslo.serialization 2.12.0: Oslo Serialization library This release is part of the newton release series. With source available at: http://git.openstack.org/cgit/openstack/oslo.serialization With package available at:

[openstack-dev] [new][oslo] oslo.vmware 2.12.0 release (newton)

We are happy to announce the release of: oslo.vmware 2.12.0: Oslo VMware library This release is part of the newton release series. With source available at: http://git.openstack.org/cgit/openstack/oslo.vmware With package available at: https://pypi.python.org/pypi/oslo.vmware

Re: [openstack-dev] Nominate Vladimir Khlyunev for fuel-qa core

+1 On Tue, Aug 2, 2016 at 2:56 PM, Artem Panchenko wrote: > +1 > > On Tue, Aug 2, 2016 at 1:52 PM, Dmitry Tyzhnenko > wrote: > >> +1 >> >> On Tue, Aug 2, 2016 at 12:51 PM, Artur Svechnikov < >> asvechni...@mirantis.com> wrote: >> >>> +1 >>> >>>

[openstack-dev] [new][oslo] oslo.middleware 3.16.0 release (newton)

We are grateful to announce the release of: oslo.middleware 3.16.0: Oslo Middleware library This release is part of the newton release series. With source available at: http://git.openstack.org/cgit/openstack/oslo.middleware With package available at:

[openstack-dev] [new][oslo] oslo.policy 1.13.0 release (newton)

We are thrilled to announce the release of: oslo.policy 1.13.0: Oslo Policy library This release is part of the newton release series. With source available at: http://git.openstack.org/cgit/openstack/oslo.policy With package available at: https://pypi.python.org/pypi/oslo.policy

[openstack-dev] [new][oslo] oslo.log 3.13.0 release (newton)

We are stoked to announce the release of: oslo.log 3.13.0: oslo.log library This release is part of the newton release series. With source available at: http://git.openstack.org/cgit/openstack/oslo.log With package available at: https://pypi.python.org/pypi/oslo.log Please report

[openstack-dev] [new][oslo] stevedore 1.17.0 release (newton)

We are mirthful to announce the release of: stevedore 1.17.0: Manage dynamic plugins for Python applications This release is part of the newton release series. With source available at: http://git.openstack.org/cgit/openstack/stevedore With package available at:

[openstack-dev] [new][oslo] oslo.service 1.14.0 release (newton)

We are happy to announce the release of: oslo.service 1.14.0: oslo.service library This release is part of the newton release series. With source available at: http://git.openstack.org/cgit/openstack/oslo.service With package available at: https://pypi.python.org/pypi/oslo.service

[openstack-dev] [new][oslo] taskflow 2.4.0 release (newton)

We are exuberant to announce the release of: taskflow 2.4.0: Taskflow structured state management library. This release is part of the newton release series. With source available at: http://git.openstack.org/cgit/openstack/taskflow With package available at:

[openstack-dev] [new][oslo] oslotest 2.8.0 release (newton)

We are excited to announce the release of: oslotest 2.8.0: Oslo test framework This release is part of the newton release series. With source available at: http://git.openstack.org/cgit/openstack/oslotest With package available at: https://pypi.python.org/pypi/oslotest Please report

  1   2   >