[openstack-dev] [fuel] New gate jobs for 'fuel-agent' and 'python-fuelclient' packages

Hi to all, please be informed that starting from today we're launching additional gating jobs [1] [2]: - for 'fuel-agent' package [3] - for 'python-fuelclient' package [4] Mentioned jobs will be started on each commit and will do following steps: - build packages from the commit - run system

Re: [openstack-dev] [fuel] New gate jobs for 'fuel-agent' and 'python-fuelclient' packages

Hey Dmitry - That's cool, thank you. I wonder you build RPM or DEB or both? - Igor On Thu, Jan 21, 2016 at 12:48 PM, Dmitry Kaiharodsev wrote: > Hi to all, > > please be informed that starting from today we're launching additional > gating jobs [1] [2]: > > - for

Re: [openstack-dev] [all][tc] Stabilization cycles: Elaborating on the idea to move it forward

On Wed, Jan 20, 2016 at 01:23:02PM -0430, Flavio Percoco wrote: > Greetings, > > At the Tokyo summit, we discussed OpenStack's development themes in a > cross-project session. In this session a group of folks started discussing > what > topics the overall community could focus on as a shared

Re: [openstack-dev] [glance][drivers] Re-think the Glance Driver's team

On Wed, Jan 20 2016, Flavio Percoco wrote: Hi, […] > Thoughts? Critics? Improvements? I'm a small contributor on Glance, so take my opinion with the appropriate weight :-), but I think this would be a really good set of improvements. This is going in the right direction. Go team! -- Julien

[openstack-dev] [Openstack-Dev][neutron][TaaS] Suggestion and review of TaaS Specification

Dear All Neutron Members, As you may know, Tap-as-a-service was first demonstrated in the Vancouver summit[1]. Since then it has progressed with the work currently going on in the specification, and its induction as an extension of the Neutron project. Considering the same,we would like to invite

Re: [openstack-dev] [all][tc] Stabilization cycles: Elaborating on the idea to move it forward

On Wed, 20 Jan 2016, Flavio Percoco wrote: - It was mentioned that some folks receive bonuses for landed features In this thread we've had people recoil in shock at this ^ one... - Economic impact on companies/market because no new features were added (?) ...but I have to say it was this

Re: [openstack-dev] [fuel] New gate jobs for 'fuel-agent' and 'python-fuelclient' packages

Hi Igor, according to the script [1] - by default we're building RPM package, and if in a package repository exists 'debian' folder - trying to build DEB as well [1] https://github.com/fuel-infra/jenkins-jobs/blob/master/servers/fuel-ci/builders/build-pkgs.sh On Thu, Jan 21, 2016 at 12:51 PM,

[openstack-dev] [gate] gate-grenade-dsvm-multinode intermittent failures

Hi, Failures for this job has been trending up and is causing the large gate queue as well. I've logged a bug: https://bugs.launchpad.net/openstack-gate/+bug/1536622 and am requesting switching the voting to off for this job: https://review.openstack.org/#/c/270788/ We need to find and fix the

Re: [openstack-dev] [Monasca] collectd-Monasca Python plugin

We are looking into similar plan to have collectd-plugin for Monasca. There are some env. we cannot deploy monasca agent, but want to put data into Monasca. In addition, we wanted to use easily accepted collectd for gathering data from legacy env. It will be interesting to see more detail about

Re: [openstack-dev] [all][tc] Stabilization cycles: Elaborating on the idea to move it forward

On 21/01/16 12:00 +0100, Julien Danjou wrote: On Wed, Jan 20 2016, Flavio Percoco wrote: Hi fellows, Now, "stabilization Cycles" are easy to dream about but really hard to do and enforce. Nonetheless, they are still worth a try or, at the very least, a thought. I'll try to go through some of

Re: [openstack-dev] [all][tc] Stabilization cycles: Elaborating on the idea to move it forward

On Thu, Jan 21 2016, Flavio Percoco wrote: > So, I don't think it has to be the entire cycle. It could also be a couple of > milestones (or even just 1). Thing is, I believe this has to be communicated > and > I want teams to know this is fine and they are encouraged to do so. > > Tl;DR: It's

Re: [openstack-dev] [puppet] [oslo] Proposal of adding puppet-oslo to OpenStack

Excerpts from Cody Herriges's message of 2016-01-19 15:50:05 -0800: > Colleen Murphy wrote: > > On Tue, Jan 19, 2016 at 9:57 AM, Xingchao Yu > > wrote: > > > > Hi, Emilien: > > > > Thanks for your efforts on this topic, I didn't attend V

Re: [openstack-dev] [all][tc] Stabilization cycles: Elaborating on the idea to move it forward

On 21/01/16 11:55 +0100, Thierry Carrez wrote: Flavio Percoco wrote: [...] So, the above sounds quite vague, still but that's the idea. This email is not a formal proposal but a starting point to move this conversation forward. Is this something other teams would be interested in? Is this

Re: [openstack-dev] [TripleO] Deploy Overcloud Keystone in HTTPD

On 01/19/2016 10:07 AM, Adam Young wrote: > On 01/19/2016 07:54 AM, Emilien Macchi wrote: >> >> On 01/18/2016 09:59 PM, Adam Young wrote: >>> I have a review here for switching Keystone to HTTPD >>> >>> https://review.openstack.org/#/c/269377/ >> Adam, I think your patch overlaps with my patch:

Re: [openstack-dev] [fuel][plugin] node_role only need when attribute false - where is the fuel plugin parser code?

Whoops, forgot to add a link, sorry.. Here it is [0] http://paste.openstack.org/show/484552/ On Thu, Jan 21, 2016 at 1:24 PM, Aleksandr Didenko wrote: > Hi, > > I'm working on a plugin for 8.0 atm and this is how it worked for me [0]. > It's a restriction not for node

Re: [openstack-dev] [fuel][plugin] node_role only need when attribute false - where is the fuel plugin parser code?

Hi, I'm working on a plugin for 8.0 atm and this is how it worked for me [0]. It's a restriction not for node role, it's for other plugin setting, but I suppose it should work in your case as well. So in general it should look like: condition: "settings:plugin_name.attribute_name.value == false"

Re: [openstack-dev] [fuel] New gate jobs for 'fuel-agent' and 'python-fuelclient' packages

Thanks. Any plans to add similar job for fuel-web? On Thu, Jan 21, 2016 at 1:34 PM, Dmitry Kaiharodsev wrote: > Hi Igor, > > according to the script [1] - by default we're building RPM package, > and if in a package repository exists 'debian' folder - trying to build

Re: [openstack-dev] [gate] gate-grenade-dsvm-multinode intermittent failures

On 01/21/2016 08:18 AM, Davanum Srinivas wrote: > Hi, > > Failures for this job has been trending up and is causing the large > gate queue as well. I've logged a bug: > https://bugs.launchpad.net/openstack-gate/+bug/1536622 > > and am requesting switching the voting to off for this job: >

Re: [openstack-dev] [all][tc] Stabilization cycles: Elaborating on the idea to move it forward

On Wed, Jan 20 2016, Flavio Percoco wrote: Hi fellows, > Now, "stabilization Cycles" are easy to dream about but really hard to do and > enforce. Nonetheless, they are still worth a try or, at the very least, a > thought. I'll try to go through some of the issues and benefits a > stabilization

Re: [openstack-dev] [all][tc] Stabilization cycles: Elaborating on the idea to move it forward

On 21/01/16 11:22 +, Daniel P. Berrange wrote: On Wed, Jan 20, 2016 at 01:23:02PM -0430, Flavio Percoco wrote: Greetings, At the Tokyo summit, we discussed OpenStack's development themes in a cross-project session. In this session a group of folks started discussing what topics the overall

Re: [openstack-dev] [all][tc] Stabilization cycles: Elaborating on the idea to move it forward

Flavio Percoco wrote: [...] So, the above sounds quite vague, still but that's the idea. This email is not a formal proposal but a starting point to move this conversation forward. Is this something other teams would be interested in? Is this something some teams would be entirely against? Why?

Re: [openstack-dev] [gate] large-ops failure spike

>I also suggest their time has probably come and gone. There is no one >active on them, and the Rally team is. Fully agree with idea to use Rally for large-ops. It was build for testing OpenStack under the scale=) On Wed, Jan 20, 2016 at 9:08 PM, Tony Breeds wrote: >

Re: [openstack-dev] [keystone][neutron][requirements] - keystonemiddleware-4.1.0 performance regression

Hi, By the way OSprofiler trace shows how this regression impacts on amount of DB queries done by Keystone (during the boot of VM): http://boris-42.github.io/b2.html Best regards, Boris Pavlovic On Wed, Jan 20, 2016 at 3:30 PM, Morgan Fainberg wrote: > As promised

Re: [openstack-dev] [fuel][plugins] Detached components plugin update requirement

Sergii, I'm also curious, what about plugins which intend to be compatible with both MOS 7 and MOS 8? I've in mind the LMA plugins stable/0.8 BR -- Swann On Wed, Jan 20, 2016 at 8:34 PM, Sergii Golovatiuk wrote: > Plugin master branch won't be compatible with older

Re: [openstack-dev] [fuel] [fuelclient] Pre-release versions of fuelclient for testing purposes

By the way, it would be very helpful for testing external tools if we had 7.0.1 release on PyPI as well. It seems python-fuelclient somehow ended up with a "stable/7.0.1" branch instead of "7.0.1" tag. On Wed, Jan 20, 2016 at 2:49 PM Roman Prykhodchenko wrote: > Releasing a

Re: [openstack-dev] [Neutron] Removing ml2_type_vxlan.vxlan_group parameter?

Convinced :) -- - Andreas (IRC: scheuran) On Mi, 2016-01-20 at 19:58 +, Sean M. Collins wrote: > On Wed, Jan 20, 2016 at 02:24:35PM EST, Sourabh Patwardhan wrote: > > This option is used to configure a global multicast group IP for VXLAN > > networks. > > The Cisco Nexus1000V mech

Re: [openstack-dev] nova cli commands fail with 404. devstack installation from today

Guess it's image-list instead of image list,right?  maybe you can check with nova --debug image-list and see the API which wassend to nova-api server then analyze the nova api log to know what's exactly the error?-"Bob Hansen" wrote: -To:

Re: [openstack-dev] [fuel][plugins] Detached components plugin update requirement

Breakage of anything is probably the last thing I intended to achieve with that patch. Maybe I misunderstand how tasks dependencies works, let me describe *explicit* dependencies I did in tasks.yaml: hiera requires deploy_start hiera is required for setup_repositories setup_repositories is

Re: [openstack-dev] [Fuel] Relieving CI/gate jenkins bottleneck

Let's drop 3.3 as well. 3.4 is oldschool enough for vintage lovers. BP On Thu, Jan 21, 2016 at 11:03 AM, Aleksandr Didenko wrote: > Hi, > > > I also think 3.3 is the version that ships with 14.04. > > 3.4.3 is shipped with Ubuntu-14.04. I think 3.4, 3.8 and 4 should be >

[openstack-dev] [Neutron] L3-HA - Solution for GW not pingable issue bug/1365461

He neutrinos, Currently I'm working on this bug [1]. Almost one year ago Yoni Shafrir prepared a patch to fix this issue but he got in review information that this solution must be changed because it's using only one script to check the GW availability and because of that it cannot be used in

Re: [openstack-dev] [Fuel] Relieving CI/gate jenkins bottleneck

Hi, > I also think 3.3 is the version that ships with 14.04. 3.4.3 is shipped with Ubuntu-14.04. I think 3.4, 3.8 and 4 should be enough. Regards, Alex On Wed, Jan 20, 2016 at 6:38 PM, Sergii Golovatiuk wrote: > +1 for 3.3, 3.4, 3.8 and 4 > > > -- > Best regards, >

[openstack-dev] [Monasca] collectd-Monasca Python plugin

Hello: We are doing (or at least planning) a collectd-Monasca Python plugin. This plugin will receive the data from RPC calls form collectd and will write this data in Monasca, using statsd API. My question is: do you think this development could be useful? Does it worth? Any comment? Thank

Re: [openstack-dev] [fuel] New gate jobs for 'fuel-agent' and 'python-fuelclient' packages

Yes, we have a bug [1] for making similar [2] gate job for 'fuel-web' and we got success run of the job [3] today. Expecting approve from 'fuel-qa' team for moving forward. [1] https://bugs.launchpad.net/fuel/+bug/1532129 [2]

Re: [openstack-dev] [TripleO] Should we have a TripleO API, or simply use Mistral?

On 21 January 2016 at 14:46, Dougal Matthews wrote: > > > On 20 January 2016 at 20:05, Tzu-Mainn Chen wrote: > >> - Original Message - >> > On 18.1.2016 19:49, Tzu-Mainn Chen wrote: >> > > - Original Message - >> > >> On Thu, 2016-01-14 at

Re: [openstack-dev] [TripleO] Should we have a TripleO API, or simply use Mistral?

- Original Message - > On 21 January 2016 at 14:46, Dougal Matthews < dou...@redhat.com > wrote: > > On 20 January 2016 at 20:05, Tzu-Mainn Chen < tzuma...@redhat.com > wrote: > > > > - Original Message - > > > > > > > On 18.1.2016 19:49, Tzu-Mainn Chen wrote: > > > > > > >

Re: [openstack-dev] [gate] gate-grenade-dsvm-multinode intermittent failures

On 1/21/2016 7:33 AM, Sean Dague wrote: On 01/21/2016 08:18 AM, Davanum Srinivas wrote: Hi, Failures for this job has been trending up and is causing the large gate queue as well. I've logged a bug: https://bugs.launchpad.net/openstack-gate/+bug/1536622 and am requesting switching the

Re: [openstack-dev] [TripleO] Should we have a TripleO API, or simply use Mistral?

On 20 January 2016 at 20:05, Tzu-Mainn Chen wrote: > - Original Message - > > On 18.1.2016 19:49, Tzu-Mainn Chen wrote: > > > - Original Message - > > >> On Thu, 2016-01-14 at 16:04 -0500, Tzu-Mainn Chen wrote: > > >>> > > >>> - Original Message - > >

Re: [openstack-dev] [all][tc] Stabilization cycles: Elaborating on the idea to move it forward

On 01/21/2016 06:23 AM, Chris Dent wrote: On Wed, 20 Jan 2016, Flavio Percoco wrote: - It was mentioned that some folks receive bonuses for landed features In this thread we've had people recoil in shock at this ^ one... - Economic impact on companies/market because no new features were

Re: [openstack-dev] [TripleO] Removing the Tuskar repos

On 22 December 2015 at 11:38, Dougal Matthews wrote: > Hi all, > > I mentioned this at the meeting last week, but wanted to get wider input. > As far as I can tell from the current activity, there is no work going into > Tuskar and it isn't being tested with CI. This means the

[openstack-dev] [vitrage] Vitrage Demo - Get Topology Use Case

Hi, We are happy to share with you all our first Vitrage demo, showing the "get topology" api and horizon UI. Here it is: https://www.youtube.com/watch?v=GyTnMw8stXQ=youtu.be For more details about Vitrage, please visit our wiki here: https://wiki.openstack.org/wiki/Vitrage Thanks, Alexey

Re: [openstack-dev] nova cli commands fail with 404. devstack installation from today

Yes, it is image-list not image list. I don't seem to be able to find any other hints in any of the nova logs. nova --debug image-list shows this: DEBUG (extension:157) found extension EntryPoint.parse('token = keystoneauth1.loading._plugins.identity.generic:Token') DEBUG (extension:157) found

Re: [openstack-dev] [nova] Feature suggestion - API for creating VM without powering it up

On 1/20/2016 10:57 AM, Shoham Peller wrote: Hi, I would like to suggest a feature in nova to allow creating a VM, without powering it up. If the user will be able to create a stopped VM, it will allow for better flexibility and user automation. I can personally say such a feature would

Re: [openstack-dev] [gate] gate-grenade-dsvm-multinode intermittent failures

On 1/21/2016 7:33 AM, Sean Dague wrote: On 01/21/2016 08:18 AM, Davanum Srinivas wrote: Hi, Failures for this job has been trending up and is causing the large gate queue as well. I've logged a bug: https://bugs.launchpad.net/openstack-gate/+bug/1536622 and am requesting switching the

Re: [openstack-dev] [all][tc] Stabilization cycles: Elaborating on the idea to move it forward

Flavio Percoco wrote: On 21/01/16 11:55 +0100, Thierry Carrez wrote: As you said, projects can already decide to restrict feature development in a given cycle, so this is nothing new. We only need to communicate more aggressively that it is perfectly fine (and even encouraged) to define the

Re: [openstack-dev] Tip: jsonformatter site for parsing/debugging logs

Excerpts from Matt Riedemann's message of 2016-01-21 10:09:32 -0600: > Are you tired of trying to strain your eyes to parse something like this > in the logs [1]? > > vif=VIF({'profile': {}, 'ovs_interfaceid': > u'ac3ca8e7-c22d-4f63-9620-ce031bf3eaac', 'preserve_on_delete': False, > 'network':

Re: [openstack-dev] [all][tc] Stabilization cycles: Elaborating on the idea to move it forward

On 21/01/16 16:50 +0100, Thierry Carrez wrote: Flavio Percoco wrote: On 21/01/16 11:55 +0100, Thierry Carrez wrote: As you said, projects can already decide to restrict feature development in a given cycle, so this is nothing new. We only need to communicate more aggressively that it is

Re: [openstack-dev] Tip: jsonformatter site for parsing/debugginglogs

T From: Doug Hellmann To: openstack-dev Date: 01/21/2016 10:38 AM Subject:Re: [openstack-dev] Tip: jsonformatter site for parsing/debugging logs Excerpts from Matt Riedemann's message of 2016-01-21

Re: [openstack-dev] [glance][drivers] Re-think the Glance Driver's team

On 20/01/16 13:16 -0430, Flavio Percoco wrote: Yo! Glancers, Gonna cut the chase: I think we would do a better job on the specs (and light specs) side if we get rid of the Glance Drivers team and encourage everyone (especially from the core team) to weight in. Thoughts? Critics?

Re: [openstack-dev] [puppet] [oslo] Proposal of adding puppet-oslo to OpenStack

On 01/21/2016 08:15 AM, Doug Hellmann wrote: > Excerpts from Cody Herriges's message of 2016-01-19 15:50:05 -0800: >> Colleen Murphy wrote: >>> On Tue, Jan 19, 2016 at 9:57 AM, Xingchao Yu >> > wrote: >>> >>> Hi, Emilien: >>> >>> Thanks

Re: [openstack-dev] [neutron][api] GET call with huge argument list

More inline, Salvatore On 20 January 2016 at 16:51, Shraddha Pandhe wrote: > Thank you all for the comments. > > The client that we expect to call this API with thousands of network-ids > is nova-scheduler. > > Since this call is happening in the middle of

Re: [openstack-dev] [all][tc] Stabilization cycles: Elaborating on the idea to move it forward

Flavio Percoco wrote on 01/21/2016 09:13:02 AM: > From: Flavio Percoco > To: "Daniel P. Berrange" > Cc: "OpenStack Development Mailing List \(not for usage questions\)" > > Date: 01/21/2016 01:47 PM

Re: [openstack-dev] [magnum] Planning Magnum Midcycle

Team, We have selected Feb 18-19 for the Midcycle, and will be hosted by HPE. Please save the date. The exact location is forthcoming, and is expected to be Sunnyvale. Thanks, Adrian > On Jan 11, 2016, at 11:29 AM, Adrian Otto wrote: > > Team, > > We are

Re: [openstack-dev] [all][tc] Stabilization cycles: Elaborating on the idea to move it forward

Excerpts from Markus Zoeller's message of 2016-01-21 18:37:00 +0100: > Flavio Percoco wrote on 01/21/2016 09:13:02 AM: > > > From: Flavio Percoco > > To: "Daniel P. Berrange" > > Cc: "OpenStack Development Mailing List \(not for usage

Re: [openstack-dev] Tip: jsonformatter site for parsing/debugging logs

On 21/01/2016 11:27 AM, Doug Hellmann wrote: You can also do this using Python's json module from the command line: $ echo '{"json":"obj"}' | python -m json.tool { "json": "obj" } Doug very useful... if you want a site, i use http://pro.jsonlint.com/ (vladikr told me about it... he

Re: [openstack-dev] [nova] Feature suggestion - API for creating VM without powering it up

The nova instance user spec has a use case. https://review.openstack.org/#/c/93/ Thanks, Kevin From: Matt Riedemann [mrie...@linux.vnet.ibm.com] Sent: Thursday, January 21, 2016 7:32 AM To: openstack-dev@lists.openstack.org Subject: Re: [openstack-dev]

Re: [openstack-dev] nova cli commands fail with 404. devstack installation from today

Found it. The contents of the admin file (e.g. ../devstack/accrc/admin/admin) that I sourced for the admin credentials do not work with the nova cli. This combination of OS_* variables produced the error. export OS_PROJECT_NAME="admin" export OS_AUTH_URL="http://127.0.0.1:35357; export

[openstack-dev] [release][documentation] fairy-slipper release HEAD (independent)

We are delighted to announce the release of: fairy-slipper HEAD: A project to make OpenStack API's self documententing. This release is part of the independent release series. With source available at: https://git.openstack.org/cgit/openstack/fairy-slipper With package available at:

Re: [openstack-dev] [gate] gate-grenade-dsvm-multinode intermittent failures

On Thu, Jan 21, 2016 at 08:18:14AM -0500, Davanum Srinivas wrote: > Hi, > > Failures for this job has been trending up and is causing the large > gate queue as well. I've logged a bug: > https://bugs.launchpad.net/openstack-gate/+bug/1536622 > > and am requesting switching the voting to off for

Re: [openstack-dev] [gate] gate-grenade-dsvm-multinode intermittent failures

On 01/21/2016 11:00 AM, Matthew Treinish wrote: > On Thu, Jan 21, 2016 at 08:18:14AM -0500, Davanum Srinivas wrote: >> Hi, >> >> Failures for this job has been trending up and is causing the large >> gate queue as well. I've logged a bug: >> https://bugs.launchpad.net/openstack-gate/+bug/1536622

Re: [openstack-dev] [TripleO] Should we have a TripleO API, or simply use Mistral?

On Thu, Jan 21, 2016 at 10:29 AM, Tzu-Mainn Chen wrote: > > > > > On 21 January 2016 at 14:46, Dougal Matthews wrote: >> >> >> >> On 20 January 2016 at 20:05, Tzu-Mainn Chen wrote: >>> >>> -

[openstack-dev] [release][documentation] fairy-slipper release 0.1.0 (independent)

We are chuffed to announce the release of: fairy-slipper 0.1.0: A project to make OpenStack API's self documententing. This release is part of the independent release series. With source available at: https://git.openstack.org/cgit/openstack/fairy-slipper With package available at:

Re: [openstack-dev] [all][tc] Stabilization cycles: Elaborating on the idea to move it forward

On 20/01/16 12:53, Flavio Percoco wrote: Greetings, At the Tokyo summit, we discussed OpenStack's development themes in a cross-project session. In this session a group of folks started discussing what topics the overall community could focus on as a shared effort. One of the things that was

Re: [openstack-dev] [all][tc] Stabilization cycles: Elaborating on the idea to move it forward

Julien Danjou wrote: On Thu, Jan 21 2016, Flavio Percoco wrote: So, I don't think it has to be the entire cycle. It could also be a couple of milestones (or even just 1). Thing is, I believe this has to be communicated and I want teams to know this is fine and they are encouraged to do so.

Re: [openstack-dev] [Monasca] collectd-Monasca Python plugin

Hi Rodolfo, I think this would be useful work. Collectd has a lot of metrics that aren't supported in Monasca yet. How would you map the metric names and fields in collectd to a monasa name and dimensions? Regards --Roland From: Jaesuk Ahn >

[openstack-dev] [TripleO] add support for other types of virtual switches in os_net_config

Hi, all This is Xin from Big Switch. I'm proposing to make os_net_config support more types of virtual switches. Current os_net_config supports ovs_bridge, linux_bridge and different types of interfaces associated with ovs and linux bridge. Current os_net_config's abstraction is perfect

Re: [openstack-dev] [Monasca] alarms based on events

Hi Prema, SNMP isn't handled in Monasca and I have little experience in that area. This would be new development. It is possible to map binary data, such as health/status of a system or component. The usual way is to use the value 0 for up/OK and 1 for down/NOT_OK. A component would need to be

Re: [openstack-dev] [all][tc] Stabilization cycles: Elaborating on the idea to move it forward

On Thu, Jan 21, 2016 at 06:37:00PM +0100, Markus Zoeller wrote: > Flavio Percoco wrote on 01/21/2016 09:13:02 AM: [...] First, positive remark(s): Thanks for writing this up. FWIW, I support the notion of having milestones focusing on stability, as opposed to explicitly

[openstack-dev] [watcher] DevStack plugin

Hi all, Watcher now has a DevStack plugin that can be used to easily stand up the Watcher services for development. Documentation can be found at [0] and example local.conf files are provided for both controller and compute nodes. If you're interested in working on Watcher, then please try out

[openstack-dev] [neutron] mid cycle details

Hi all, Where: Minnesota (great planning for winter!) When:Feb 23-26 Details: https://etherpad.openstack.org/p/neutron-mitaka-midcycle Please RSVP. And yell at Kyle for using that shade of red. Thanks, doug __ OpenStack

Re: [openstack-dev] [all][tc] Stabilization cycles: Elaborating on the idea to move it forward

Devananda van der Veen, on January 21, 2016 5:14 PM wrote: On Wed, Jan 20, 2016 at 9:53 AM, Flavio Percoco > wrote: Greetings, At the Tokyo summit, we discussed OpenStack's development themes in a cross-project session. In this session a group of

[openstack-dev] What's Up, Doc? 22 January 2016

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hi everyone, We seem to be more or less back into the swing of things here in docs land this week, with our meeting schedule back up and running, and now our very first full-length newsletter for 2016! We only have two and a half months until

Re: [openstack-dev] [all][tc] Stabilization cycles: Elaborating on the idea to move it forward

On Wed, Jan 20, 2016 at 9:53 AM, Flavio Percoco wrote: > Greetings, > > At the Tokyo summit, we discussed OpenStack's development themes in a > cross-project session. In this session a group of folks started discussing > what > topics the overall community could focus on as a

[openstack-dev] [release] release countdown for week R-10, Jan 25-29

Focus - With the second milestone behind us, project teams should be focusing on wrapping up new feature work and stabilizing recent additions. Release Actions --- We will be more strictly enforcing the library release freeze before M3 in 5 weeks. Please review client libraries,

Re: [openstack-dev] nova cli commands fail with 404. devstack installation from today

On Thu, Jan 21, 2016 at 1:48 PM, Bob Hansen wrote: > Found it. The contents of the admin file (e.g. > ../devstack/accrc/admin/admin) that I sourced for the admin credentials do > not work with the nova cli. This combination of OS_* variables produced the > error. > > export

Re: [openstack-dev] [all][tc] Stabilization cycles: Elaborating on the idea to move it forward

On 21 January 2016 at 07:38, Ian Cordasco wrote: > > I think this is a solid proposal but I'm not sure what (if anything) the TC > needs to do about this. This is something most non-corporate open source > projects do (and even some corporate open source projects).

[openstack-dev] Dynamically adding Extra Specs

Hi, I had a few queries regarding adding extra specs for VM requests. According to my understanding if I want to add extra specs to requests then I need to change that in different flavors adding those capabilities by setting them in the flavors. But if the requests that I get have varying

Re: [openstack-dev] [cross-project]How to make use of x-openstack-request-id

Thanks Kebane, I test glance/neutron/keystone with ``x-openstack-request-id`` and find something interesting. I am able to pass ``x-openstack-request-id`` to glance and it will use the UUID as its request-id. But it failed with neutron and keystone. Here is my test:

[openstack-dev] [devstack] Failure on installing openstack with latest devstack.

Hi There, Can someone please me to resolve below devstack error? 2016-01-22 07:00:29.802 | 6134 INFO keystone.cmd.cli [-] Domain default already exists, skipping creation. 2016-01-22 07:00:29.952 | 6134 INFO keystone.cmd.cli [-] Created project admin 2016-01-22 07:00:29.959 | 6134 DEBUG

[openstack-dev] [heat][heat-client] Question about heat command: deployment-list and deployment-metadata-show

Hi: When using heat command: heat deployment-list and heat deloyment-metadata-show like this: # heat deployment-list -s non-exist-server-id ++---+---+++---+---+ | id | config_id | server_id | action | status | creation_time |

[openstack-dev] [Neutron][l2-gateway] Kindly ask for review for this RFE

Hello, This RFE[1] “extend l2gw api to support multi-site connectivity” needs review after it’s registered several weeks ago. There are several projects looking forward for the feature of extending L2 network across Neutron, or say, across sites. For example: OPNFV multisite[2]: VNF(Telecom

Re: [openstack-dev] [keystone] Let's get together and fix all the bugs

Hi all, We've been consistently chipping away at keystone bugs for a while now every Friday. We've also refactored some of the information around the bug day [0] and built a couple dashboards to help people get started with reviews [1] [2]. I wanted to send out this note just to update everyone