Re: [openstack-dev] [all][tc] Languages vs. Scope of "OpenStack"

Morgan Fainberg wrote: On Thu, May 19, 2016 at 6:19 AM, Thierry Carrez > wrote: Hi everyone, The discussion on the addition of golang focuses on estimating community costs vs. technical benefits, so that the TC can make the

Re: [openstack-dev] [Heat] Versioned objects upgrade patterns

On 05/18/2016 01:39 PM, Zane Bitter wrote: > On 17/05/16 20:27, Crag Wolfe wrote: >> Now getting very Heat-specific. W.r.t. to >> https://review.openstack.org/#/c/303692/ , the goal is to de-duplicate >> raw_template.files (this is a dict of template filename to contents), >> both in the DB and in

Re: [openstack-dev] [glance] Unable to set metadata_encryption_key

Hello Nikhil, On 19 May 2016 at 04:11, Nikhil Komawar wrote: > > Here's something to get started: > > * Change your tests here glance/tests/functional/__init__.py to > metadata_encryption_key to the value you want to set. > > * See if they pass or fail. > I made the

Re: [openstack-dev] [glance] Unable to set metadata_encryption_key

Hi Djimeli, Thanks for working through this issues. It's a problem indeed with the existing metadata not being set. I think the solution you propose sounds fair -- let's see if existing non-encrypted metadata can be encrypted whenever the key has been set. I do however, want us to ensure that it

Re: [openstack-dev] [release] Re: [Neutron][L2GW] Mitaka release of L2 Gateway now available

On Thu, May 19, 2016 at 7:09 AM, Doug Hellmann wrote: > We have the same issue with version numbers regressing no matter when we > cut the next release, so it's up to the team. It might be easier to deal > with now while it's fresh in our minds. > > I would like to update

Re: [openstack-dev] [all][tc] Languages vs. Scope of "OpenStack"

+1. OpenStack does meet the requirements for being an Operating System at the data center level in my opinion. We just keep trying to beat around that bush for some reason... yes, we do that by Integrating a lot of things together, but thats not what its about.

Re: [openstack-dev] [ironic] usage of ironic-lib

On 05/16/2016 07:14 AM, Lucas Alvares Gomes wrote: > On Mon, May 16, 2016 at 2:57 PM, Loo, Ruby wrote: >> Hi, >> >> A patch to ironic-lib made me wonder about what is our supported usage of >> ironic-lib. Or even the intent/scope of it. This patch changes a method, >>

Re: [openstack-dev] [Mistral][Zaqar] Triggering Mistral workflows from Zaqar messages

On 19/05/16 04:20, Thomas Herve wrote: On Wed, May 18, 2016 at 8:49 PM, Zane Bitter wrote: I've been lobbying the Mistral developers for $SUBJECT since, basically, forever.[1][2][3] I like to think after a couple of years I succeeded in changing their view on it from

Re: [openstack-dev] [neutron] DHCP Agent Scheduling for Segments

On Wed, May 18, 2016 at 1:36 PM, Kevin Benton wrote: >>I may have wrongly assumed that segments MAY have the possibility of being >> l2 adjacent, even if the entire network they are in is not, which would mean >> that viewing and scheduling these in the context of a segment

Re: [openstack-dev] [all][tc] Languages vs. Scope of "OpenStack"

summary: * Defining the scope of OpenStack projects DOES NOT define the languages needed to implement them. The considerations are orthogonal. * We've already defined OpenStack--it's whatever it takes to fulfill its mission statement. On 19 May 2016, at 6:19, Thierry Carrez wrote: >

Re: [openstack-dev] [neutron][stable] proposing Brian Haley for neutron-stable-maint

Ihar, Thanks for the nomination, I'll just chime-in below. On 05/19/2016 03:13 PM, Ihar Hrachyshka wrote: On 19 May 2016, at 13:18, Tony Breeds wrote: On Thu, May 19, 2016 at 10:49:26AM +0200, Ihar Hrachyshka wrote: On 19 May 2016, at 02:12, Tony Breeds

Re: [openstack-dev] [all][tc] Languages vs. Scope of "OpenStack"

John Dickinson wrote: summary: * Defining the scope of OpenStack projects DOES NOT define the languages needed to implement them. The considerations are orthogonal. * We've already defined OpenStack--it's whatever it takes to fulfill its mission statement. On 19 May 2016, at

Re: [openstack-dev] [all][tc] Languages vs. Scope of "OpenStack"

On Thu, May 19, 2016 at 6:19 AM, Thierry Carrez wrote: > Hi everyone, > > The discussion on the addition of golang focuses on estimating community > costs vs. technical benefits, so that the TC can make the right call for > "OpenStack". From that discussion, we established

Re: [openstack-dev] [Mistral][Zaqar] Triggering Mistral workflows from Zaqar messages

Hi Zane, Generally, I think it's a very good idea just like I said in the IRC channel. I will review the spec and thank you for proposing it. On 19/05/16 06:49, Zane Bitter wrote: I've been lobbying the Mistral developers for $SUBJECT since, basically, forever.[1][2][3] I like to think after

Re: [openstack-dev] [ceilometer] [telemetry] ceilometer-specs submodule path is invalid

Hi, On Thu, May 19, 2016 at 3:33 PM, Swapnil Kulkarni wrote: > First of all, you should have included [ceilometer] or [telemetry] in > subject. (which i have done in the reply) so its targetted intended > receipients. I wasn't sure about this, as it doesn't feel like a

Re: [openstack-dev] [Mistral][Zaqar] Triggering Mistral workflows from Zaqar messages

On Wed, May 18, 2016 at 8:49 PM, Zane Bitter wrote: > I've been lobbying the Mistral developers for $SUBJECT since, basically, > forever.[1][2][3] I like to think after a couple of years I succeeded in > changing their view on it from "crazy" to merely "unrealistic".[4] In the

Re: [openstack-dev] [mistral][oslo.messaging] stable/mitaka is broken by oslo.messaging 5.0.0

On Wed, 18 May 2016 08:51:00 -0700 Joshua Harlow wrote: > >> Option #1 > >> > >> Oslo.messaging (and the dispatcher part that does this) stays as is, > >> doing at-most-once for RPC (notifications are in a different > >> category here so let's not discuss them) and doing

Re: [openstack-dev] [release] Re: [Neutron][L2GW] Mitaka release of L2 Gateway now available

> On 18 May 2016, at 23:16, Doug Hellmann wrote: > > Excerpts from Armando M.'s message of 2016-05-17 14:34:22 -0700: >> On 17 May 2016 at 03:25, Ihar Hrachyshka wrote: >> >>> On 16 May 2016, at 21:16, Armando M. wrote:

Re: [openstack-dev] [tc] [all] [glance] On operating a high throughput or otherwise team

On 17 May 2016 at 09:56, Thierry Carrez wrote: > John Garbutt wrote: >> >> [...] >> Agreed that with a shared language, the ML is more effective. >> [...] >> I think some IRC meeting work, in a standup like way, for those with a >> previously established shared context. > >

Re: [openstack-dev] [Heat] Versioned objects upgrade patterns

On 05/18/2016 10:39 PM, Zane Bitter wrote: > On 17/05/16 20:27, Crag Wolfe wrote: >> Now getting very Heat-specific. W.r.t. to >> https://review.openstack.org/#/c/303692/ , the goal is to de-duplicate >> raw_template.files (this is a dict of template filename to contents), >> both in the DB and in

Re: [openstack-dev] [Openstack] [AodhClient] "composite alarm" unit test missing in aodhclient ?

Yes, right, the "composite_rule" should be None in def test_alarm_from_args :-) In addition, read the unit tests in "test_alarm_cli.py", there is no composite test, (like "def test_validate_args_composite", similar with "test_validate_args_threshold,

Re: [openstack-dev] [ceilometer] [telemetry] ceilometer-specs submodule path is invalid

On Thu, May 19 2016, Gerard Braad wrote: > I wasn't sure about this, as it doesn't feel like a ceilometer > specific problem, but rather an out-dated submodule list for the > OpenStack tracking repository. > >> Second you can open a bug at [1] or > > Anyways, I filed it...

Re: [openstack-dev] [neutron][stable] proposing Brian Haley for neutron-stable-maint

> On 19 May 2016, at 02:12, Tony Breeds wrote: > > On Tue, May 17, 2016 at 01:07:48PM +0200, Ihar Hrachyshka wrote: >> Hi stable-maint-core and all, >> >> I would like to propose Brian for neutron specific stable team. > > +1 > > It'd be nice to see some comments on

[openstack-dev] [puppet] Proposing Ivan Berezovskiy for puppet-openstack-core

Hi, I don't need to introduce Ivan Berezovskiy (iberezovskiy on IRC), he's been doing tremendous work in Puppet OpenStack over the last months, in a regular way. Some highlights about his contributions: * Fantastic work on puppet-oslo! I really mean it... Thanks to you and others, we have now

Re: [openstack-dev] [OpenStack-docs] [API] os-api-ref HTTP Response code formating

On 19/05/2016 14:09, Anne Gentle wrote: > > > On Wed, May 18, 2016 at 1:42 PM, Hayes, Graham > wrote: > > I was moving Designate to the os-api-ref extension, and I spotted > something I thought we could do to improve the readability. > >

[openstack-dev] 答复: [Heat][Glance] Can't migrate to glance v2 completely

Thanks very much and sorry to reply so late. Comments inline. -邮件原件- 发件人: Nikhil Komawar [mailto:nik.koma...@gmail.com] 发送时间: 2016年5月11日 22:03 收件人: OpenStack Development Mailing List (not for usage questions) 抄送: Huangtianhua 主题: Re: [openstack-dev] [Heat][Glance] Can't migrate to glance

Re: [openstack-dev] [tricircle] Coding style guidelines

Hi Zhipeng, Please have a look at the following script. e.g., import orders. ./tricirlce/db/core.py Cheers, Shinobu On Fri, May 20, 2016 at 12:41 PM, Zhipeng Huang wrote: > Hi shinobu, could you provide an example of which part of code need > modification to fit the

Re: [openstack-dev] [tricircle] Coding style guidelines

Hi Chaoyi, Thank you for your double-check. On Fri, May 20, 2016 at 1:12 PM, joehuang wrote: > Hello, Shinobu, > > We have gate test for pep8 in the CI pipeline, This is what I missed completely -; Cheers, Shinobu > for import orders, if it's incorrect, pep8 gate check

Re: [openstack-dev] How to single sign on with windows authentication with Keystone

On 05/19/2016 07:40 AM, Rodrigo Duarte wrote: Hi, So you are trying to use keystone to authorize your users, but want to avoid having to authenticate via keystone, right? Check if the Federated Identity feature [1] covers your use case. [1]

Re: [openstack-dev] [aodhclient] does the aodh have the feature for import/export batch alarms?

batch alarm is not supported, and I think it is a burden instead of good feature to implement it in aodh import/export alarm is not supported, considering dump db and restore it in new env? or you can get alarm list from old env and create new alarm in new env via REST API if data set is not too

[openstack-dev] [aodhclient] does the aodh have the feature for import/export batch alarms?

HI All, in the aodh/aodhclient, I not find the feature for import/export batch alarms. I mainly want to use it to implement the following requirement: In "migrate alarms from one openstack env to another openstack env" scenario, I would like to do this requirement

[openstack-dev] [infra] [tracking] Renames and verification; was Re: ceilometer-specs submodule path is invalid

Hi, On Thu, May 19, 2016 at 9:33 PM, Jeremy Stanley wrote: > I've audited the .gitmodules file in openstack/openstack and > submitted https://review.openstack.org/318661 to update it. Thanks > for pointing that out. I've also submitted > https://review.openstack.org/318665 to

[openstack-dev] [tricircle] Coding style guidelines

Hi Team, Please make sure that your coding style follows OpenStack style guidelines. [1] I understand that it's really painful but readability, and maintenanceability point of view, it is very important to follow standard. Working through code bases, some of them do not follow the guidelines.

[openstack-dev] [heat] enabled convergence background

Hi Team, I noticed that heat enabled convergence.Could someone tell me about the background about the convergence. or some specs to introduce it? Thank you. Best Regards, xiangxinyong__ OpenStack Development Mailing

Re: [openstack-dev] [Neutron][L2GW][Tricircle]Border Gateway support

Hi, Sean, Ofer and others have worked on this spec almost half year In the summit session not me call for action, but some guys who are currently not working in Tricircle call for action, the speakers from HPE/Intel/BT. Best Regards Chaoyi Huang ( Joe Huang ) -Original Message-

Re: [openstack-dev] [tricircle] Coding style guidelines

Hi shinobu, could you provide an example of which part of code need modification to fit the guideline ? On Fri, May 20, 2016 at 11:04 AM, Shinobu Kinjo wrote: > Hi Team, > > Please make sure that your coding style follows OpenStack style > guidelines. [1] > > I understand

Re: [openstack-dev] [tricircle] Coding style guidelines

Hello, Shinobu, We have gate test for pep8 in the CI pipeline, for import orders, if it's incorrect, pep8 gate check will give -1 in the result. I checked the core.py in the repository, the import order is ok, first import system level, then OSLO, then projects level with blank line between

Re: [openstack-dev] [aodhclient] does the aodh have the feature for import/export batch alarms?

Hi, I also agree with ZhiQiang. How about using Heat Template which improve portability of app and configs? Cheers, Ryota > -Original Message- > From: ZhiQiang Fan [mailto:aji.zq...@gmail.com] > Sent: Friday, May 20, 2016 11:42 AM > To: li.yuanz...@zte.com.cn > Cc: OpenStack

[openstack-dev] What's Up, Doc? 20 May 2016

Hi everyone, I've been struck down by the dreaded flu this week, so it's been a bit quiet around here. I have, however, crawled out from under the tissues, throat lozenges, and episodes of Containment to pen my regular newsletter for you. See how dedicated I am to the cause? ;) The biggest

Re: [openstack-dev] [nova]Libvirt error code for failing volume in nova

Hi! Regarding 1. I'd start with giving a generic message, e.g. "error while attaching volume" that does not point to a specific reason. Regarding 2., if the reason is identifiable throwing the corresponding exception would come in handy. Only use the generic failure if there's no specific error

[openstack-dev] [charms] Juju Charms for OpenStack

Hi All tl;dr Juju is a great way of deploying OpenStack, and we'd like the OpenStack Charms for Juju to become a official OpenStack Project read on if you want the full details Juju [0] is a service modelling tool that's been around since about 2010; developed primarily by Canonical, Juju

Re: [openstack-dev] [nova] Thoughts on deprecating the legacy bdm v1 API support

On Tue, May 17, 2016 at 09:48:02AM -0500, Matt Riedemann wrote: > In the live migration meeting today mdbooth and I were chatting about how > hard it is to follow the various BDM code through nova, because you have the > three block_device modules: > > * nova.block_device - dict that does some

Re: [openstack-dev] [tc] supporting Go

On 05/19/2016 12:58 PM, Robert Collins wrote: On 19 May 2016 at 22:40, Dmitry Tantsur wrote: You are correct that my position is subjective, but it is based on my experiences trying to operate and deploy OpenStack in addition to writing code. The draw of Go, in my

Re: [openstack-dev] How to single sign on with windows authentication with Keystone

Hi, So you are trying to use keystone to authorize your users, but want to avoid having to authenticate via keystone, right? Check if the Federated Identity feature [1] covers your use case. [1] http://docs.openstack.org/security-guide/identity/federated-keystone.html On Thu, May 19, 2016 at

[openstack-dev] [Zaqar] Nominate XiYuan Wang and Hao Wang for Zaqar core

Hi team, I would like to propose adding XiYuan Wang(wxy) and Hao Wang(wanghao) for the Zaqar core team. They have been awesome contributors since joining the Zaqar team about 6 months ago. And now they are currently the most active non-core reviewers on Zaqar projects for the last 90 days[1].

[openstack-dev] How to single sign on with windows authentication with Keystone

Link: https://openstack.nimeyo.com/85057/?show=85057#q85057 From: imocha I have to call the keystone APIs and want to use the windows authentication using Active Directory. Keystone provides integration with AD at the back end. To get the initial token to use OpenStack APIs, I

Re: [openstack-dev] [tc] supporting Go

On 19 May 2016 at 22:40, Dmitry Tantsur wrote: > >> You are correct that my position is subjective, but it is based on my >> experiences trying to operate and deploy OpenStack in addition to >> writing code. The draw of Go, in my experience, has been easily >> deploying a

Re: [openstack-dev] [Openstack] [AodhClient] "composite alarm" unit test missing in aodhclient ?

Agree, we should have it. Could you propose the change, adding liusheng as a reviewer? He made this composite alarm and can check your patch properly. /Ryota > -Original Message- > From: li.yuanz...@zte.com.cn [mailto:li.yuanz...@zte.com.cn] > Sent: Thursday, May 19, 2016 5:36 PM > To:

Re: [openstack-dev] [neutron][stable] proposing Brian Haley for neutron-stable-maint

On Thu, May 19, 2016 at 10:49:26AM +0200, Ihar Hrachyshka wrote: > > > On 19 May 2016, at 02:12, Tony Breeds wrote: > > > > On Tue, May 17, 2016 at 01:07:48PM +0200, Ihar Hrachyshka wrote: > >> Hi stable-maint-core and all, > >> > >> I would like to propose Brian for

Re: [openstack-dev] [tc] supporting Go

On 05/19/2016 12:42 AM, Eric Larson wrote: Dmitry Tantsur writes: This is pretty subjective, I would say. I personally don't feel Go (especially its approach to error handling) any natural (at least no more than Rust or Scala, for example). If familiarity for Python developers is an argument

[openstack-dev] Admin user creating servers for other users using Nova api

Link: https://openstack.nimeyo.com/85058/?show=85058#q85058 From: imocha The servers created by nova api is owned by the user who created the server. i.e. based on the token used at the time of calling the Nova API. If I want to have an admin create the server and assign

Re: [openstack-dev] [tc] supporting Go

On 05/18/2016 06:42 PM, Eric Larson wrote: > > Dmitry Tantsur writes: > >> This is pretty subjective, I would say. I personally don't feel Go >> (especially its approach to error handling) any natural (at least no >> more than Rust or Scala, for example). If familiarity for Python >> developers is

[openstack-dev] Neutron upgrade from Kilo to Mitaka

Hi, I’m have a Fuel 7.0 based environment [kilo], wanted to upgrade the Neutron to Mitaka version. is it possible to upgrade Neutron alone to the Mitaka version. if so can someone point me to right direction. __ OpenStack

Re: [openstack-dev] [Neutron][L2GW][Tricircle]Border Gateway support

joehuang wrote: > And one session[3] in Austin summit called for action in the community to > prioritize and accelerate Tricircle development. > > [1]https://review.openstack.org/#/c/270786/ > [2]https://review.openstack.org/#/c/304540/ >

Re: [openstack-dev] [puppet] Proposing Ivan Berezovskiy for puppet-openstack-core

+1 from me! On Thu, May 19, 2016 at 8:17 AM, Emilien Macchi wrote: > Hi, > > I don't need to introduce Ivan Berezovskiy (iberezovskiy on IRC), he's > been doing tremendous work in Puppet OpenStack over the last months, > in a regular way. > > Some highlights about his

Re: [openstack-dev] [API] os-api-ref HTTP Response code formating

On 18/05/2016 20:12, Sean Dague wrote: > On 05/18/2016 02:42 PM, Hayes, Graham wrote: >> I was moving Designate to the os-api-ref extension, and I spotted >> something I thought we could do to improve the readability. >> >> Currently we have the HTTP Response Codes as a single >> line on the page

Re: [openstack-dev] [TripleO] Austin summit - session recap/summary

On 18 May 2016 at 13:34, Paul Belanger wrote: > On Wed, May 18, 2016 at 12:22:55PM +0100, Derek Higgins wrote: >> On 6 May 2016 at 14:18, Paul Belanger wrote: >> > On Tue, May 03, 2016 at 05:34:55PM +0100, Steven Hardy wrote: >> >> Hi all, >> >> >>

Re: [openstack-dev] [ironic] usage of ironic-lib

Hi, > So… how does any library get ready to be used by others? Clearly it is being > used now by the fuel-agent. Do we say ‘sorry fuel-agent, we don’t guarantee > yet that we won’t break you’? Or ‘fuel-agent, just so you know. Ironic-lib > isn’t quite ready to be used so we cannot guarantee that

Re: [openstack-dev] Neutron upgrade from Kilo to Mitaka

I will recommend you to move your question to the ops mailing list. openstack-operat...@lists.openstack.org Thanks, Edgar From: Akshik dbk Reply-To: "OpenStack Development Mailing List (not for usage questions)"

[openstack-dev] [tc][ansible][ironic] Reusing Ansible code in OpenStack projects

Hi all, I have a question re FOSS licenses interplay. I am pretty sure that OpenStack community (e.g. openstack-ansible) has already faced such questions and I would really appreciate any advice. We are developing a new ansible-based deployment driver for Ironic [0] and would like to use some

Re: [openstack-dev] [javascript] [infra] NPM Mirrors (IMPORTANT)

Well, my current theory is that npm's default timeout and retries are set too permissively for cold AFS caches (2 retries, 10 second mintimeout, 1 minute maxtimeout). We _just_ landed this patch ( https://review.openstack.org/#/c/318279/) which increases both the # of retries and the timeouts,

Re: [openstack-dev] [ironic] usage of ironic-lib

Ooo, thanks for that data point Pavlo! Thanks Lucas, Sam, Shivanand and Pavlo for commenting. From the replies, it seems like the original intent of ironic-lib was to solely be used by ironic and ironic-python-agent projects. But that doesn’t seem to have been communicated properly (because I

Re: [openstack-dev] [puppet] Proposing Ivan Berezovskiy for puppet-openstack-core

+1 from my side :) well deserved. 2016-05-19 17:17 GMT+03:00 Emilien Macchi : > Hi, > > I don't need to introduce Ivan Berezovskiy (iberezovskiy on IRC), he's > been doing tremendous work in Puppet OpenStack over the last months, > in a regular way. > > Some highlights about

Re: [openstack-dev] [all][requirements] Refresher on how to use global requirements process

Excerpts from Dirk Müller's message of 2016-05-19 15:38:45 +0200: > Hi Doug, > > > Cleaning up the readme makes a lot of sense. If we end up wanting to > > split it a lot, I'd suggest moving some of the "consumer" facing info to > > the project team guide, but it's moderately less easy to change

Re: [openstack-dev] [API] os-api-ref HTTP Response code formating

On 05/19/2016 10:37 AM, Hayes, Graham wrote: > On 18/05/2016 20:12, Sean Dague wrote: >> On 05/18/2016 02:42 PM, Hayes, Graham wrote: >>> I was moving Designate to the os-api-ref extension, and I spotted >>> something I thought we could do to improve the readability. >>> >>> Currently we have the

Re: [openstack-dev] [nova] Thoughts on deprecating the legacy bdm v1 API support

> -Original Message- > From: Matt Riedemann [mailto:mrie...@linux.vnet.ibm.com] > Sent: 17 May 2016 15:48 > To: OpenStack Development Mailing List (not for usage questions) > > Subject: [openstack-dev] [nova] Thoughts on deprecating the legacy bdm v1 >

[openstack-dev] [Neutron][L2GW][Tricircle]Border Gateway support

Hello, L2GW team, Congratulation on L2GW Mitaka Release! Would you team please help to move “Border Gateway support” [1] forward? There is one key feature (cross-OpenStack L2 Networking automation) in Tricircle has dependency on L2GW’s Border Gateway in Newton release. And one session[3] in

Re: [openstack-dev] [charms] Juju Charms for OpenStack

+1 from me (as an OpenStack contributor, and one of those 'developers at SDN and storage vendors' :-) ). Neil On Thu, May 19, 2016 at 11:38 AM James Page wrote: > Hi All > > tl;dr Juju is a great way of deploying OpenStack, and we'd like the > OpenStack Charms for

Re: [openstack-dev] [all][requirements] Refresher on how to use global requirements process

2016-05-19 1:08 GMT+02:00 Robert Collins : > It's already fully documented in the requirements repo README; if > there is no link to that from the project-guide, we should add one, > but I would not duplicate the content. Agreed. The project driver guide is not very

[openstack-dev] [ironic] Virtual midcycle date poll

Hi Ironickers, We decided in our last meeting that the midcycle for Newton will again be virtual. Now, we need to choose a date. Please indicate which options work for you (more than one may be selected): http://doodle.com/poll/gpug7ynd9fn4rdfe I'll close this poll two Mondays from now, May 30.

Re: [openstack-dev] [Congress] driver (authentication issue)

Hi Tim, Thanks a lot. Sorry I missed that part previously, now it is successed. *Regards,* *Yue* On 18 May 2016 at 17:42, Tim Hinrichs wrote: > When you're doing testing like this, the easiest solution is to disable > authentication. Here are the instructions from the

[openstack-dev] [Fuel] [Plugins] Netconfig tasks changes

Hi all, please be aware that now we have two netconfig tasks (in Fuel 9.0+): - netconfig-controller - executed on controllers only - netconfig - executed on all other nodes puppet manifest is the same, but tasks are different. We had to do this [0] in order to fix network idempotency issues

Re: [openstack-dev] [release] Re: [Neutron][L2GW] Mitaka release of L2 Gateway now available

Excerpts from Ihar Hrachyshka's message of 2016-05-19 10:21:48 +0200: > > > On 18 May 2016, at 23:16, Doug Hellmann wrote: > > > > Excerpts from Armando M.'s message of 2016-05-17 14:34:22 -0700: > >> On 17 May 2016 at 03:25, Ihar Hrachyshka wrote: >

Re: [openstack-dev] [OpenStack-docs] [API] os-api-ref HTTP Response code formating

On Wed, May 18, 2016 at 1:42 PM, Hayes, Graham wrote: > I was moving Designate to the os-api-ref extension, and I spotted > something I thought we could do to improve the readability. > Thank you! > > Currently we have the HTTP Response Codes as a single > line on the

Re: [openstack-dev] ceilometer-specs submodule path is invalid

On 2016-05-19 15:17:01 +0800 (+0800), Gerard Braad wrote: > Doing: > > $ git clone https://github.com/openstack/openstack.git > $ git submodule init > $ git submodule update > > fails on: > > Cloning into 'ceilometer-specs'... > fatal: remote error: Git repository not found > fatal: clone

Re: [openstack-dev] [mistral][oslo.messaging] stable/mitaka is broken by oslo.messaging 5.0.0

Excerpts from Renat Akhmerov's message of 2016-05-19 13:19:54 +0700: > https://github.com/openstack/requirements/blame/master/README.rst#L95-L100 > > > Doug, Is it still relevant? I’m just trying to understand how to

Re: [openstack-dev] [tc][ansible][ironic] Reusing Ansible code in OpenStack projects

Excerpts from Pavlo Shchelokovskyy's message of 2016-05-19 15:28:03 +0300: > Hi all, > > I have a question re FOSS licenses interplay. I am pretty sure that > OpenStack community (e.g. openstack-ansible) has already faced such > questions and I would really appreciate any advice. > > We are

[openstack-dev] [tripleo] Nodes management in our shiny new TripleO API

Hi all! We started some discussions on https://review.openstack.org/#/c/300200/ about the future of node management (registering, configuring and introspecting) in the new API, but I think it's more fair (and convenient) to move it here. The goal is to fix several long-standing design flaws

Re: [openstack-dev] [all][requirements] Refresher on how to use global requirements process

Hi Doug, > Cleaning up the readme makes a lot of sense. If we end up wanting to > split it a lot, I'd suggest moving some of the "consumer" facing info to > the project team guide, but it's moderately less easy to change there > because the reviewer group is different. .. which is a good thing,

[openstack-dev] [ironic] process for making decisions?

Hi, I think it would be good if we came up with some general guidelines wrt the processes by which decisions are made. By ³decisions², I mean decisions that we, as a community, will try to abide by ? I have noticed in the past, that discussions in the mailing list (ML) sometimes peter out

Re: [openstack-dev] [javascript] [infra] NPM Mirrors (IMPORTANT)

It seems this issue started to affect us on OpenStack infra about 13 hours ago. The main 2 reasons of failing tests are "Unexpected end of input"/"registry error parsing json" (example ) and "Error: socket

Re: [openstack-dev] [all][requirements] Refresher on how to use global requirements process

Excerpts from Dirk Müller's message of 2016-05-19 15:12:40 +0200: > 2016-05-19 1:08 GMT+02:00 Robert Collins : > > > It's already fully documented in the requirements repo README; if > > there is no link to that from the project-guide, we should add one, > > but I would

[openstack-dev] [all][tc] Languages vs. Scope of "OpenStack"

Hi everyone, The discussion on the addition of golang focuses on estimating community costs vs. technical benefits, so that the TC can make the right call for "OpenStack". From that discussion, we established that the costs for cross-project teams (Infra...) seem to be workable. There is

[openstack-dev] [all] [requirements] Global Requirements Team contact point - #openstack-requirements

Hi all, I've updated https://wiki.openstack.org/wiki/Requirements#Contact (and also the rest of the wiki page) with newer information about global-requirements handling. Please if you find issues related to the global requirements update process in your project don't hesitate to join the

[openstack-dev] [nova] race condition with resize

Hi all, While I was working on fixing the resize for pci passthrough [1] I have notice the following issue in resize. If you are using small image and you resize-confirm it very fast the old resources are not getting freed. After debug this issue I found out the root cause of it. A

Re: [openstack-dev] [TripleO] Austin summit - session recap/summary

On Wed, May 18, 2016 at 08:34:40AM -0400, Paul Belanger wrote: > On Wed, May 18, 2016 at 12:22:55PM +0100, Derek Higgins wrote: > > On 6 May 2016 at 14:18, Paul Belanger wrote: > > > On Tue, May 03, 2016 at 05:34:55PM +0100, Steven Hardy wrote: > > >> Hi all, > > >> > > >>

Re: [openstack-dev] [API] os-api-ref HTTP Response code formating

On 19/05/2016 16:11, Sean Dague wrote: > On 05/19/2016 10:37 AM, Hayes, Graham wrote: >> On 18/05/2016 20:12, Sean Dague wrote: >>> On 05/18/2016 02:42 PM, Hayes, Graham wrote: I was moving Designate to the os-api-ref extension, and I spotted something I thought we could do to improve

Re: [openstack-dev] [nova]Libvirt error code for failing volume in nova

On Wed, May 18, 2016 at 07:57:17PM +, Radhakrishnan, Siva wrote: > Hi All! > Currently I am working on this bug > https://bugs.launchpad.net/nova/+bug/1168011 which says we have to change > error message displayed when attaching a volume fails. Currently it catches > all operation errors

Re: [openstack-dev] [Neutron][DevStack] Do we still need the neutron-debug command?

Assaf Muller wrote: > As far as I know Devstack is/was the only user. From my perspective, > I've never heard anyone using neutron-debug, reporting a bug against > it or asking any questions about it. I think it's reasonable to remove > it. OK - I pushed a patch that just takes it out of the

Re: [openstack-dev] [Neutron][DevStack] Do we still need the neutron-debug command?

On Thu, May 19, 2016 at 11:36 AM, Sean M. Collins wrote: > Ryan Moats and I chatted a week or so ago about neutron-debug in the > context of DevStack. > > Ryan pushed a patch to see what it actually does[1]. > > Currently, it's not clear what it is used for, and in some

Re: [openstack-dev] [puppet] Proposing Ivan Berezovskiy for puppet-openstack-core

+1 great job Ivan On Thu, May 19, 2016 at 8:32 AM, Matt Fischer wrote: > +1 from me! > > On Thu, May 19, 2016 at 8:17 AM, Emilien Macchi > wrote: > >> Hi, >> >> I don't need to introduce Ivan Berezovskiy (iberezovskiy on IRC), he's >> been doing

[openstack-dev] [all][api] New guidelines ready for cross project review

The following proposed API guidelines are available for broader review by interested parties. * https://review.openstack.org/#/c/301846 Description of how to use etags to avoid lost updates * https://review.openstack.org/#/c/281511 Delete multiple metadata items with a single request these

Re: [openstack-dev] [TripleO] Austin summit - session recap/summary

On Thu, May 19, 2016 at 03:50:15PM +0100, Derek Higgins wrote: > On 18 May 2016 at 13:34, Paul Belanger wrote: > > On Wed, May 18, 2016 at 12:22:55PM +0100, Derek Higgins wrote: > >> On 6 May 2016 at 14:18, Paul Belanger wrote: > >> > On Tue, May 03,

[openstack-dev] [Neutron][DevStack] Do we still need the neutron-debug command?

Ryan Moats and I chatted a week or so ago about neutron-debug in the context of DevStack. Ryan pushed a patch to see what it actually does[1]. Currently, it's not clear what it is used for, and in some instances it seems to be more trouble than it is really worth. Instead of going through and

Re: [openstack-dev] [Neutron][DevStack] Do we still need the neutron-debug command?

On 19 May 2016 at 08:56, Sean M. Collins wrote: > Assaf Muller wrote: > > As far as I know Devstack is/was the only user. From my perspective, > > I've never heard anyone using neutron-debug, reporting a bug against > > it or asking any questions about it. I think it's

Re: [openstack-dev] [tc][ansible][ironic] Reusing Ansible code in OpenStack projects

Excerpts from Pavlo Shchelokovskyy's message of 2016-05-19 15:28:03 +0300: > Hi all, > > I have a question re FOSS licenses interplay. I am pretty sure that > OpenStack community (e.g. openstack-ansible) has already faced such > questions and I would really appreciate any advice. > > We are

[openstack-dev] Neutron: Octavia: LBaaS: RFE created for DVR support for unbound allowed_address_pair port with FIP which are associated with multiple VMs that are active.

Hi Folks, There has been recently a lot of requests for Neutron DVR to support unbound allowed_address_pair port with FIP which are associated with multiple VMs that are ACTIVE to provide High Availability to the VMs. This use case is being heavily used by Octavia. Based on the request and the

Re: [openstack-dev] [TripleO] Austin summit - session recap/summary

On 19 May 2016 5:38 pm, "Paul Belanger" wrote: > > On Thu, May 19, 2016 at 03:50:15PM +0100, Derek Higgins wrote: > > On 18 May 2016 at 13:34, Paul Belanger wrote: > > > On Wed, May 18, 2016 at 12:22:55PM +0100, Derek Higgins wrote: > > >> On 6 May

Re: [openstack-dev] [ironic] usage of ironic-lib

On Thu, May 19, 2016 at 6:16 PM, Lucas Alvares Gomes wrote: > Hi, > > > So… how does any library get ready to be used by others? Clearly it is > being > > used now by the fuel-agent. Do we say ‘sorry fuel-agent, we don’t > guarantee > > yet that we won’t break you’? Or

Re: [openstack-dev] [heat] api-ref gate job is active

Hi guys, just for clarification: do I correctly understand, that now we store all API related docs in local (Heat) repository and we have not copy of this staff somewhere else? so we can easily update it ourself and don't push the same commit to another repository ? And also library mentioned in

  1   2   >