[openstack-dev] [Ironic] Adopting ironic-lib in Ironic

2015-06-16 Thread Ramakrishnan G
Hi All, Some time back we created a new repository[1] to move all the reusable code components of Ironic to a separate library. The branched out code has changed and there has been a review out to sync it [2]. But unfortunately, it has got stale again as some more changes have gone in to the bra

Re: [openstack-dev] [api][nova][ironic] Microversion API HTTP header

2015-06-16 Thread Dmitry Tantsur
On 06/15/2015 10:31 PM, Jay Pipes wrote: On 06/15/2015 02:09 PM, Dmitry Tantsur wrote: 2015-06-15 19:50 GMT+02:00 Clint Byrum mailto:cl...@fewbar.com>>: Excerpts from Jay Pipes's message of 2015-06-15 10:07:39 -0700: > It has come to my attention in [1] that the microversion spec fo

Re: [openstack-dev] [Ironic] Adopting ironic-lib in Ironic

2015-06-16 Thread Dmitry Tantsur
On 06/16/2015 08:58 AM, Ramakrishnan G wrote: Hi All, Some time back we created a new repository[1] to move all the reusable code components of Ironic to a separate library. The branched out code has changed and there has been a review out to sync it [2]. But unfortunately, it has got stale a

Re: [openstack-dev] [javascript] [horizon] [merlin] [refstack] Javascript Linting

2015-06-16 Thread Rob Cresswell (rcresswe)
So my view here is that I don’t particularly mind which plugin/ set of plugins Horizon uses, but the biggest deterrent is the workload. We’re already cleaning everything up quite productively, so I’m reluctant to swap. That said, the cleanup from JSCS/ JSHint should be largely relevant to ESLint

Re: [openstack-dev] [all][release] summit session summary: Release Versioning for Server Applications

2015-06-16 Thread Thierry Carrez
Doug Hellmann wrote: > [...] > I still need to chat with Kyle about some of the neutron spin-out > projects, since their repositories have the old neutron tags but I don't > think it's appropriate to use the same version number as neutron for > newer projects. > [...] > neutron 8.0.0 > neutron-fwaa

Re: [openstack-dev] [Magnum] Add periodic task threading for conductor server

2015-06-16 Thread 大塚元央
Hi, folks. At the last summit, we decided to support pluggable conductor for multi backend [1]. So, if we choose #3, new service (instance of periodic task) also should support plugin. I think this will be a little complicated to implement a plugin. [1]: https://etherpad.openstack.org/p/liberty-w

[openstack-dev] Cross-Project meeting, Tue Jun 16th, 21:00 UTC

2015-06-16 Thread Thierry Carrez
Dear PTLs, cross-project liaisons and anyone else interested, We'll have a cross-project meeting today at 21:00 UTC, with the following agenda: * Horizontal teams announcements * Server versioning changes (dhellmann) * Clarification on the return code when a server has a hard coded length limit [

Re: [openstack-dev] [OpenStack-Infra] Nominating Joshua Hesketh for infra-root

2015-06-16 Thread Antoine Musso
Le 11/06/2015 18:54, James E. Blair a écrit : > The Infrastructure program has a unique three-tier team structure: > contributors (that's all of us!), core members (people with +2 ability > on infra projects in Gerrit) and root members (people with > administrative access). Read all about it here:

Re: [openstack-dev] [api][nova][ironic] Microversion API HTTP header

2015-06-16 Thread Alex Xu
2015-06-16 5:58 GMT+08:00 Ed Leafe : > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA512 > > On 06/15/2015 04:30 PM, Michael Davies wrote: > > > On Tue, Jun 16, 2015 at 5:15 AM, Kevin L. Mitchell > > > > wrote: > > > > Given the disagreement evinced by the res

Re: [openstack-dev] [api][nova][ironic] Microversion API HTTP header

2015-06-16 Thread Ken'ichi Ohmichi
2015-06-16 2:07 GMT+09:00 Jay Pipes : > It has come to my attention in [1] that the microversion spec for Nova [2] > and Ironic [3] have used the project name -- i.e. Nova and Ironic -- instead > of the name of the API -- i.e. "OpenStack Compute" and "OpenStack Bare > Metal" -- in the HTTP header t

Re: [openstack-dev] [Openstack-operators] [ops][tags][packaging] ops:packaging tag - a little common sense, please

2015-06-16 Thread Thomas Goirand
Thanks Jay for this. I basically agree with all you wrote. On 06/10/2015 07:51 PM, Jay Pipes wrote: > I don't believe the Ops Tags team should be curating the packaging tags > -- the packaging community should do that, and do that under the main > openstack/governance repository. > > Packagers,

Re: [openstack-dev] [api][nova][ironic] Microversion API HTTP header

2015-06-16 Thread Alex Xu
2015-06-16 5:24 GMT+08:00 Clint Byrum : > Excerpts from Sean Dague's message of 2015-06-15 14:00:43 -0700: > > On 06/15/2015 04:50 PM, Jim Rollenhagen wrote: > > > On Mon, Jun 15, 2015 at 01:07:39PM -0400, Jay Pipes wrote: > > >> It has come to my attention in [1] that the microversion spec for >

Re: [openstack-dev] stackforge projects are not second class citizens

2015-06-16 Thread gordon chung
i won't speak to whether this confirms/refutes the usefulness of the big tent. that said, probably as a by-product of being in non-stop meetings with sales/marketing/managers for last few days, i think there needs to be better definitions (or better publicised definitions) of what the goals of

Re: [openstack-dev] [all] [stable] No longer doing stable point releases

2015-06-16 Thread Ihar Hrachyshka
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 06/15/2015 11:24 PM, Thomas Goirand wrote: > On 06/15/2015 05:19 PM, Ian Cordasco wrote: >> On 6/15/15, 09:24, "Thomas Goirand" wrote: >> >>> On 06/08/2015 01:55 PM, Kuvaja, Erno wrote: One thing I like about plan D is that it would give al

Re: [openstack-dev] [all][release] summit session summary: Release Versioning for Server Applications

2015-06-16 Thread Ihar Hrachyshka
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 06/16/2015 09:44 AM, Thierry Carrez wrote: > Doug Hellmann wrote: >> [...] I still need to chat with Kyle about some of the neutron >> spin-out projects, since their repositories have the old neutron >> tags but I don't think it's appropriate to u

Re: [openstack-dev] [api][nova][ironic] Microversion API HTTP header

2015-06-16 Thread Lucas Alvares Gomes
Hi, >> Actually that makes an alternative implementation more valuable. Without >> microversions those alternative implementations would have to wait a long >> time to implement fixes to the API, but now can implement and publish >> the fix as soon as the microversion lands. This means that altern

[openstack-dev] [Horizon] [tests] [dsvm] Tests failed because of timeout during the images upload

2015-06-16 Thread Timur Nurlygayanov
Hi team, I investigated the latest failed Horizon integration dsvm jobs [1] and found that many of them failed because of timeouts during the upload of image (in function 'create_image' [2]), on step '_wait_till_spinner_disappears' [3], where we wait while 'div.*modal-backdrop*' will disappear. In

[openstack-dev] [Security] Nominating Travis McPeak for Security CoreSec

2015-06-16 Thread Clark, Robert Graham
I'd like to nominate Travis for a CoreSec position as part of the Security project. - CoreSec team members support the VMT with extended consultation on externally reported vulnerabilities. Travis has been an active member of the Security project for a couple of years he's a part of the bandit

Re: [openstack-dev] [Horizon] [tests] [dsvm] Tests failed because of timeout during the images upload

2015-06-16 Thread Matthias Runge
On 16/06/15 11:20, Timur Nurlygayanov wrote: In this method integration tests try to upload image by the following link [4]: http://download.cirros-cloud.net/0.3.1/cirros-0.3.1-x86_64-uec.tar.gz Imho it would be better to host this somewhere internal in infra rather than getting it from the

Re: [openstack-dev] [all][release] summit session summary: Release Versioning for Server Applications

2015-06-16 Thread Sergey Lukjanov
I have a question regarding proposed release versions - are we starting to count releases from zero? And 2015.1 (Kilo) missed in all projects in etherpad. So, it means if we're starting from 0.0.0 then the proposed versions are correct, but if we want to start from 1.0.0 (IMO it's better), we shoul

Re: [openstack-dev] [all][release] summit session summary: Release Versioning for Server Applications

2015-06-16 Thread Thierry Carrez
Doug Hellmann wrote: > [...] > I put together a little script [1] to try to count the previous > releases for projects, to use that as the basis for their first > SemVer-based version number. I pasted the output into an etherpad > [2] and started making notes about proposed release numbers at the >

Re: [openstack-dev] [puppet] [zaqar] Adding puppet-zaqar Module to Puppet Modules Project

2015-06-16 Thread Flavio Percoco
On 15/06/15 12:48 -0700, Richard Raseley wrote: Here are the two changes I submitted for review to get puppet-zaqar added to the project: https://review.openstack.org/#/c/191942/ https://review.openstack.org/#/c/191946/ I am not sure these are 100% correct, but I followed the guide[0] as well

Re: [openstack-dev] [all][release] summit session summary: Release Versioning for Server Applications

2015-06-16 Thread Timur Nurlygayanov
Hi Doug, I suggest to use some version for neutron-*aas plugins, probably, 1.0.0 just to have one pattern for all components. If we will not use numbers for the first releases (or release candidates) it will be hard to understand what the version it is. What do you think about it? Thank you! On

Re: [openstack-dev] [all][release] summit session summary: Release Versioning for Server Applications

2015-06-16 Thread Sergey Lukjanov
Agree with Thierry, IMO it sounds more consistent On Tue, Jun 16, 2015 at 12:45 PM, Thierry Carrez wrote: > Doug Hellmann wrote: > > [...] > > I put together a little script [1] to try to count the previous > > releases for projects, to use that as the basis for their first > > SemVer-based vers

Re: [openstack-dev] [designate] and [lbaas] - GSLB API and backend support

2015-06-16 Thread Hayes, Graham
That's fine with me. - Graham On 16 Jun 2015 6:06 am, Doug Wiegley wrote: Hi all, We don’t have a rough draft API doc yet, so I’m suggesting that we postpone tomorrow morning’s meeting until next week. Does anyone have any other agenda items, or want the meeting tomorrow? Thanks, doug > On

Re: [openstack-dev] [all] [stable] No longer doing stable point releases

2015-06-16 Thread Thierry Carrez
Thomas Goirand wrote: > On 06/10/2015 03:46 PM, Thierry Carrez wrote: >> So we could do what you're asking (option B) for Kilo stable releases, >> but I think it's not really a viable option for stable/liberty onward. > > I fail to understand how version numbers are related to doing > synchronized

[openstack-dev] [Ceilometer][Gnocchi] question on integration with time-series databases

2015-06-16 Thread Simon Pasquier
Hi, Originally, I posted this question on the review [0] that adds InfluxDB support to Gnocchi but Julien felt that it wasn't relevant in the scope of the review. Still I think that it deserves some discussion... The current implementation of the InfluxDB driver for Gnocchi doesn't follow the rec

[openstack-dev] [Murano] Cloud Foundry Service Broker Api in Murano

2015-06-16 Thread Nikolay Starodubtsev
Hi all, I've started a work on bp: https://blueprints.launchpad.net/murano/+spec/cloudfoundry-api-support I plan to publish a spec in a day or two. If anyone interesting to cooperate please drop me a message here or in IRC: Nikolay_St Nikolay Starodubtsev Software Engineer Mirantis Inc. Skyp

Re: [openstack-dev] stackforge projects are not second class citizens

2015-06-16 Thread Flavio Percoco
On 16/06/15 04:39 -0400, gordon chung wrote: i won't speak to whether this confirms/refutes the usefulness of the big tent. that said, probably as a by-product of being in non-stop meetings with sales/ marketing/managers for last few days, i think there needs to be better definitions (or better p

Re: [openstack-dev] [packaging] Adding packaging as an OpenStack project

2015-06-16 Thread James Page
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hi Thomas On 15/06/15 19:48, Thomas Goirand wrote: [...] > During our discussions at the Summit, you seemed to be > enthusiastic about pushing our packaging to Stackforge. Then others > told me to "push it to the /openstack namespace" to make it "mo

Re: [openstack-dev] [api][nova][ironic] Microversion API HTTP header

2015-06-16 Thread Sean Dague
On 06/15/2015 03:45 PM, Kevin L. Mitchell wrote: > On Mon, 2015-06-15 at 13:07 -0400, Jay Pipes wrote: >> The original spec said that the HTTP header should contain the name of >> the service type returned by the Keystone service catalog (which is also >> the official name of the REST API). I don

Re: [openstack-dev] [api][nova][ironic] Microversion API HTTP header

2015-06-16 Thread Alex Xu
2015-06-16 18:57 GMT+08:00 Sean Dague : > On 06/15/2015 03:45 PM, Kevin L. Mitchell wrote: > > On Mon, 2015-06-15 at 13:07 -0400, Jay Pipes wrote: > >> The original spec said that the HTTP header should contain the name of > >> the service type returned by the Keystone service catalog (which is al

Re: [openstack-dev] stackforge projects are not second class citizens

2015-06-16 Thread Jay Pipes
You may also find my explanation about the Big Tent helpful in this interview with Niki Acosta and Jeff Dickey: http://blogs.cisco.com/cloud/ospod-29-jay-pipes Best, -jay On 06/16/2015 06:09 AM, Flavio Percoco wrote: On 16/06/15 04:39 -0400, gordon chung wrote: i won't speak to whether this

Re: [openstack-dev] [api][nova][ironic] Microversion API HTTP header

2015-06-16 Thread Jay Pipes
On 06/16/2015 04:36 AM, Alex Xu wrote: So if our min_version is 2.1 and the max_version is 2.50. That means alternative implementations need implement all the 50 versions api...that sounds pain... Yes, it's pain, but it's no different than someone who is following the Amazon EC2 API, which cut

Re: [openstack-dev] [api][nova][ironic] Microversion API HTTP header

2015-06-16 Thread Jay Pipes
On 06/16/2015 04:12 AM, Ken'ichi Ohmichi wrote: 2015-06-16 2:07 GMT+09:00 Jay Pipes : It has come to my attention in [1] that the microversion spec for Nova [2] and Ironic [3] have used the project name -- i.e. Nova and Ironic -- instead of the name of the API -- i.e. "OpenStack Compute" and "Op

Re: [openstack-dev] [api][nova][ironic] Microversion API HTTP header

2015-06-16 Thread Dmitry Tantsur
16 июня 2015 г. 13:52 пользователь "Jay Pipes" написал: > > On 06/16/2015 04:36 AM, Alex Xu wrote: >> >> So if our min_version is 2.1 and the max_version is 2.50. That means >> alternative implementations need implement all the 50 versions >> api...that sounds pain... > > > Yes, it's pain, but it'

Re: [openstack-dev] [api][nova][ironic] Microversion API HTTP header

2015-06-16 Thread Sean Dague
On 06/16/2015 07:38 AM, Alex Xu wrote: > > > 2015-06-16 18:57 GMT+08:00 Sean Dague >: > > On 06/15/2015 03:45 PM, Kevin L. Mitchell wrote: > > On Mon, 2015-06-15 at 13:07 -0400, Jay Pipes wrote: > >> The original spec said that the HTTP header should contain t

Re: [openstack-dev] [api][nova][ironic] Microversion API HTTP header

2015-06-16 Thread Jay Pipes
On 06/16/2015 08:00 AM, Dmitry Tantsur wrote: 16 июня 2015 г. 13:52 пользователь "Jay Pipes" mailto:jaypi...@gmail.com>> написал: > > On 06/16/2015 04:36 AM, Alex Xu wrote: >> >> So if our min_version is 2.1 and the max_version is 2.50. That means >> alternative implementations need impleme

Re: [openstack-dev] [Horizon] [tests] [dsvm] Tests failed because of timeout during the images upload

2015-06-16 Thread Timur Sufiev
Timur, If old jQuery code (not AngularJS) is still used for processing 'Create Image' form, then the spinner is shown just before submitting the form contents [1] and hidden right after the request completes [2] in case the form is being redrawn or the whole page is redrawn in case of redirect - w

Re: [openstack-dev] [api][nova][ironic] Microversion API HTTP header

2015-06-16 Thread Lucas Alvares Gomes
Hi >> So if our min_version is 2.1 and the max_version is 2.50. That means >> alternative implementations need implement all the 50 versions >> api...that sounds pain... > > > Yes, it's pain, but it's no different than someone who is following the > Amazon EC2 API, which cuts releases at a regular

Re: [openstack-dev] [fuel] Fuel API settings reference

2015-06-16 Thread Oleg Gelbukh
Andrew, I've also noticed that incompatible changes are being introduced in JSON schemas for different objects in almost every release. I hope that explicit reference that lists and explains all parameters will discourage such modifications, or at least will increase their visibility and allow to

[openstack-dev] [ceilometer] When do we import aodh?

2015-06-16 Thread Julien Danjou
Hi there, The alarm code split blueprint¹ has been approved, and I finished the split of the code base. It's available online at: https://github.com/jd/aodh tox -e pep8,py27,docs passes. To me the next step is to: 1. Someone cares and review what I've done in the repository 2. import the code

Re: [openstack-dev] [puppet] drop monolithic plugins in neutron module

2015-06-16 Thread Emilien Macchi
The patch has been merged: https://review.openstack.org/#/c/190395 These plugins are now deleted from puppet-neutron: * monolithic OVS (replaced in favor of ML2 with openvswitch mechanism driver) * monolithic Linux Bridge (replaced in favor of ML2 with linuxbridge mechanism driver) On 06/12/2015

Re: [openstack-dev] [api][nova][ironic] Microversion API HTTP header

2015-06-16 Thread Sean Dague
On 06/16/2015 08:38 AM, Lucas Alvares Gomes wrote: > Hi > >>> So if our min_version is 2.1 and the max_version is 2.50. That means >>> alternative implementations need implement all the 50 versions >>> api...that sounds pain... >> >> >> Yes, it's pain, but it's no different than someone who is fol

[openstack-dev] [release] Release announcements convergence

2015-06-16 Thread Thierry Carrez
Hi everyone, Release announcements in OpenStack come in various forms and shapes. So far we had: - Integrated release "service" components being announced on openstack-announce and openstack general lists. - Other "service" components sometimes being announced on openstack-dev - Oslo libraries

Re: [openstack-dev] [api][nova][ironic] Microversion API HTTP header

2015-06-16 Thread Salvatore Orlando
On 16 June 2015 at 14:38, Lucas Alvares Gomes wrote: > Hi > > >> So if our min_version is 2.1 and the max_version is 2.50. That means > >> alternative implementations need implement all the 50 versions > >> api...that sounds pain... > > > > > > Yes, it's pain, but it's no different than someone w

Re: [openstack-dev] [nova] Online Migrations.

2015-06-16 Thread Mike Bayer
On 6/15/15 8:34 PM, Philip Schwartz wrote: I discussed this a bit earlier with John and we came up with a thought that I was going to present after getting a little bit more documentation and spec around. With out going into too much detail, here is the basics of the idea. Add a new column t

Re: [openstack-dev] [all][release] summit session summary: Release Versioning for Server Applications

2015-06-16 Thread Doug Hellmann
Excerpts from Thierry Carrez's message of 2015-06-16 11:45:51 +0200: > Doug Hellmann wrote: > > [...] > > I put together a little script [1] to try to count the previous > > releases for projects, to use that as the basis for their first > > SemVer-based version number. I pasted the output into an

[openstack-dev] [all] FYI - dropping non RabbitMQ support in devstack

2015-06-16 Thread Sean Dague
FYI, One of the things that came out of the summit for Devstack plans going forward is to trim it back to something more opinionated and remove a bunch of low use optionality in the process. One of those branches to be trimmed is all the support for things beyond RabbitMQ in the rpc layer. Rabbit

Re: [openstack-dev] [all][release] summit session summary: Release Versioning for Server Applications

2015-06-16 Thread Doug Hellmann
Excerpts from Timur Nurlygayanov's message of 2015-06-16 12:49:02 +0300: > Hi Doug, > > I suggest to use some version for neutron-*aas plugins, probably, 1.0.0 > just to have one pattern for all components. If we will not use numbers for > the first releases (or release candidates) it will be hard

[openstack-dev] Device {UUID}c not defined on plugin

2015-06-16 Thread Alvise Dorigo
Hi after a migration of Havana to IceHouse (using controller and network services/agents on the same physical node, and using OVS/GRE) we started facing some network-related problems (the internal tag of the element shown by ovs-vsctl show was set to 4095, which is wrong AFAIK). At the beginni

Re: [openstack-dev] [Nova] [Cinder] [Tempest] Regarding deleting snapshot when instance is OFF

2015-06-16 Thread Jordan Pittier
On Thu, Apr 9, 2015 at 6:10 PM, Eric Blake wrote: > On 04/08/2015 11:22 PM, Deepak Shetty wrote: > > + [Cinder] and [Tempest] in the $subject since this affects them too > > > > On Thu, Apr 9, 2015 at 4:22 AM, Eric Blake wrote: > > > >> On 04/08/2015 12:01 PM, Deepak Shetty wrote: > >>> > >>> Qu

Re: [openstack-dev] [Magnum] TLS Support in Magnum

2015-06-16 Thread Fox, Kevin M
Out of the box, vms usually can contact the controllers though the routers nat, but not visa versa. So its preferable for guest agents to make the connection, not the controller connect to the guest agents. No floating ips, security group rules or special networks are needed then. Thanks, Kevin

Re: [openstack-dev] [all][requirements] Proposing a slight change in requirements.txt syncing output.

2015-06-16 Thread Doug Hellmann
Excerpts from Robert Collins's message of 2015-06-16 11:18:55 +1200: > At the moment we copy the global-requirements lines verbatim. > > So if we have two lines in global-requirements.txt: > oslotest>=1.5.1 # Apache-2.0 > PyECLib>=1.0.7 # BSD > with very different layouts

Re: [openstack-dev] [api] [Nova] [Ironic] [Magnum] Microversion guideline in API-WG

2015-06-16 Thread Jim Rollenhagen
On Tue, Jun 16, 2015 at 08:56:37AM +0200, Dmitry Tantsur wrote: > On 06/04/2015 08:58 AM, Xu, Hejie wrote: > >Hi, guys, > >I’m working on adding Microversion into the API-WG’s guideline which > >make sure we have consistent Microversion behavior in the API for user. > >The Nova and Ironic already h

Re: [openstack-dev] [QA] [openstack-qa] [tempest] UUIDs and names in tempest.conf file

2015-06-16 Thread Matthew Treinish
So I need to point out that the openstack-qa list isn't used anymore. We only keep it around so we have a place to send for periodic test results. In the future you should just send things to the openstack-dev ML with a [QA] tag in the subject. On Tue, Jun 16, 2015 at 05:25:30AM +, Tikkanen, V

Re: [openstack-dev] [murano] python versions

2015-06-16 Thread Serg Melikyan
Stan, +100500 On Fri, Jun 12, 2015 at 3:13 PM, Stan Lagun wrote: > > I'd rather go with Heat approach (job first) because it makes easier to track > what is left to port to Py34 and track progress in this area > > Sincerely yours, > Stan Lagun > Principal Software Engineer @ Mirantis > > > On Mo

Re: [openstack-dev] [api] [Nova] [Ironic] [Magnum] Microversion guideline in API-WG

2015-06-16 Thread Dmitry Tantsur
On 06/16/2015 08:56 AM, Dmitry Tantsur wrote: On 06/04/2015 08:58 AM, Xu, Hejie wrote: Hi, guys, I’m working on adding Microversion into the API-WG’s guideline which make sure we have consistent Microversion behavior in the API for user. The Nova and Ironic already have Microversion implementati

Re: [openstack-dev] [all] FYI - dropping non RabbitMQ support in devstack

2015-06-16 Thread Davanum Srinivas
+1 Sean. -- dims On Tue, Jun 16, 2015 at 9:22 AM, Sean Dague wrote: > FYI, > > One of the things that came out of the summit for Devstack plans going > forward is to trim it back to something more opinionated and remove a > bunch of low use optionality in the process. > > One of those branches t

Re: [openstack-dev] Device {UUID}c not defined on plugin

2015-06-16 Thread Alvise Dorigo
Hi, I forgot to attach some relevant config files: /etc/neutron/plugins/ml2/ml2_conf.ini : [ml2] type_drivers = gre tenant_network_types = gre mechanism_drivers = openvswitch [ml2_type_flat] [ml2_type_vlan] [ml2_type_gre] tunnel_id_ranges = 1:1000 [ml2_type_vxlan] [securitygroup] firewall_driver

Re: [openstack-dev] [Openstack-operators] Device {UUID}c not defined on plugin

2015-06-16 Thread Alvise Dorigo
Hi, I forgot to attach some relevant config files: /etc/neutron/plugins/ml2/ml2_conf.ini : [ml2] type_drivers = gre tenant_network_types = gre mechanism_drivers = openvswitch [ml2_type_flat] [ml2_type_vlan] [ml2_type_gre] tunnel_id_ranges = 1:1000 [ml2_type_vxlan] [securitygroup] firewall_driver

Re: [openstack-dev] [api] [Nova] [Ironic] [Magnum] Microversion guideline in API-WG

2015-06-16 Thread Dmitry Tantsur
On 06/16/2015 03:47 PM, Jim Rollenhagen wrote: On Tue, Jun 16, 2015 at 08:56:37AM +0200, Dmitry Tantsur wrote: On 06/04/2015 08:58 AM, Xu, Hejie wrote: Hi, guys, I’m working on adding Microversion into the API-WG’s guideline which make sure we have consistent Microversion behavior in the API fo

Re: [openstack-dev] [kolla] Proposal for new core-reviewer Harm Waites

2015-06-16 Thread Andre Martin
On Jun 15, 2015, at 02:48, Steven Dake (stdake) mailto:std...@cisco.com>> wrote: I am proposing Harm Waites for the Kolla core team. +1 Harm did excellent work on the designate container and does very thorough reviews, the cinder container review being just one example among many. Martin

[openstack-dev] [nova] [neutron] Re: [Openstack-operators] How do your end users use networking?

2015-06-16 Thread Jay Pipes
Adding -dev because of the reference to the Neutron "Get me a network spec". Also adding [nova] and [neutron] subject markers. Comments inline, Kris. On 05/22/2015 09:28 PM, Kris G. Lindgren wrote: During the Openstack summit this week I got to talk to a number of other operators of large Open

Re: [openstack-dev] [javascript] [horizon] [merlin] [refstack] Javascript Linting

2015-06-16 Thread Michael Krotscheck
Just for the sake of clarity- did the Horizon team discuss the tool selection for JSCS with the greater community? I can't find anything on the dev list. Furthermore, there've been situations before (karma) where a patch was landed without appropriate upstream notifications and/or discussion, which

Re: [openstack-dev] [kolla] Proposal for new core-reviewer Harm Waites

2015-06-16 Thread Steven Dake (stdake)
Its unanimous! Welcome to the core reviewer team Harm! Regards -steve From: Steven Dake mailto:std...@cisco.com>> Reply-To: "OpenStack Development Mailing List (not for usage questions)" mailto:openstack-dev@lists.openstack.org>> Date: Sunday, June 14, 2015 at 10:48 AM To: "OpenStack Developme

[openstack-dev] [Ironic] ironic-lib library

2015-06-16 Thread Ruby Loo
Hi, I haven't paid any attention to ironic-lib; I just knew that we wanted to have a library of common code so that we didn't cut/paste. I just took a look[1] and there are files there from 2 months ago. So far, everything is under ironic_lib (ie, no subdirectories to group things). Going forward,

Re: [openstack-dev] [ceilometer] When do we import aodh?

2015-06-16 Thread Chris Dent
On Tue, 16 Jun 2015, Julien Danjou wrote: To me the next step is to: 1. Someone cares and review what I've done in the repository 2. import the code into openstack/aodh Assuming that we'll do whatever is required to finish things after moving it under openstack/ then whatever you've done in st

Re: [openstack-dev] [Ironic] Adopting ironic-lib in Ironic

2015-06-16 Thread Ruby Loo
On 16 June 2015 at 03:12, Dmitry Tantsur wrote: > On 06/16/2015 08:58 AM, Ramakrishnan G wrote: > >> >> Hi All, >> >> Some time back we created a new repository[1] to move all the reusable >> code components of Ironic to a separate library. The branched out code >> has changed and there has been

[openstack-dev] [oslo][all] Request from Oslo team for Liberty Cycle

2015-06-16 Thread Davanum Srinivas
Hello fellow stackers, The Oslo team came up with a handful of requests to the projects that use Oslo-*. Here they are: 0. Check if your project has a Oslo Liaison Please see https://wiki.openstack.org/wiki/CrossProjectLiaisons#Oslo and volunteer for your project. We meet once a week to go over

Re: [openstack-dev] [taskflow] Returning information from reverted flow

2015-06-16 Thread Joshua Harlow
Dulko, Michal wrote: -Original Message- From: Joshua Harlow [mailto:harlo...@outlook.com] Sent: Friday, June 12, 2015 5:49 PM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [taskflow] Returning information from reverted flow Dulko, Michal wr

Re: [openstack-dev] [all][requirements] Proposing a slight change in requirements.txt syncing output.

2015-06-16 Thread Joshua Harlow
Doug Hellmann wrote: Excerpts from Robert Collins's message of 2015-06-16 11:18:55 +1200: At the moment we copy the global-requirements lines verbatim. So if we have two lines in global-requirements.txt: oslotest>=1.5.1 # Apache-2.0 PyECLib>=1.0.7 # BSD with very diffe

[openstack-dev] [Fuel] Improvement of the blueprint specs template

2015-06-16 Thread Roman Prykhodchenko
Hi folks! I was reviewing one of specs for Fuel 7.0 and realized the information there is messed up and it’s pretty hard to put it all together. The reason for that is basically that Fuel is a multicomponent project but the template does not consider that — there is a Proposed change section wh

Re: [openstack-dev] [ceilometer] When do we import aodh?

2015-06-16 Thread Julien Danjou
On Tue, Jun 16 2015, Chris Dent wrote: > 5. anything in tempest to worry about? Yes, we need to adapt and reenable tempest after. > 6. what's that stuff in the "ceilometer" dir? >6.1. Looks like migration artifacts, what about migration in > general? That's a rest of one of the many

[openstack-dev] [kolla] Add your name and TZ to wiki

2015-06-16 Thread Paul Bourke
Hi all, Steve suggested adding a new table to the Kolla wiki to help us keep track of who's actively working on Kolla along with relevant info such as timezones and IRC names. I'm missing lots of names and timezones so if you'd like to be on this please feel free to update it at https://wik

Re: [openstack-dev] How does instance's tap device macaddress generate?

2015-06-16 Thread Tapio Tallgren
On 11.06.2015 18:52, Andreas Scheuring wrote: Maybe this helps (taken from [1]) "Actually there is one way that the MAC address of the tap device affects proper operation of guest networking - if you happen to set the tap device's MAC identical to the MAC used by the guest, you will get errors f

Re: [openstack-dev] [Murano] Cloud Foundry Service Broker Api in Murano

2015-06-16 Thread Nikolay Starodubtsev
Here is a draft spec for this: https://review.openstack.org/#/c/192250/ Nikolay Starodubtsev Software Engineer Mirantis Inc. Skype: dark_harlequine1 2015-06-16 13:11 GMT+03:00 Nikolay Starodubtsev : > Hi all, > I've started a work on bp: > https://blueprints.launchpad.net/murano/+spec/clo

Re: [openstack-dev] [Solum] Should logs be deleted when we delete an app?

2015-06-16 Thread Randall Burt
+1 Murali. AFIAK, there is no precedent for what Keith proposes, but that doesn't mean its a bad thing. On Jun 16, 2015, at 12:21 AM, Murali Allada wrote: > I agree, users should have a mechanism to keep logs around. > > I implemented the logs deletion feature after we got a bunch of requests

[openstack-dev] [neutron][db] online schema upgrades

2015-06-16 Thread Ihar Hrachyshka
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hi neutron folks, I'd like to discuss a plan on getting support for online db schema upgrades in neutron. *What is it even about?* Currently, any major version upgrade, or master-to-master upgrade, requires neutron-server shutdown. After shutdown,

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

2015-06-16 Thread Emilien Macchi
On 06/15/2015 08:06 PM, Emilien Macchi wrote: > Hi everyone, > > Here's an initial agenda for our weekly meeting tomorrow at 1500 UTC in > #openstack-meeting-4: > > https://etherpad.openstack.org/p/puppet-openstack-weekly-meeting-20150616 > > Please add additiona

[openstack-dev] [puppet] (officially) deprecate stable/{grizzly, havana} branches

2015-06-16 Thread Emilien Macchi
Hi, Some of our modules have stable/grizzly and stable/havana branches. Some of them have the CI broken due to rspec issues that would require some investigation and time if we wanted to fix it. We would like to know who plan to backport some patches in these branches? If nobody plans to do that

Re: [openstack-dev] [Ironic] ironic-lib library

2015-06-16 Thread Lucas Alvares Gomes
Hi, > I haven't paid any attention to ironic-lib; I just knew that we wanted to > have a library of common code so that we didn't cut/paste. I just took a > look[1] and there are files there from 2 months ago. So far, everything is > under ironic_lib (ie, no subdirectories to group things). Going

Re: [openstack-dev] [all][release] summit session summary: Release Versioning for Server Applications

2015-06-16 Thread Thierry Carrez
Doug Hellmann wrote: > Excerpts from Thierry Carrez's message of 2015-06-16 11:45:51 +0200: >> We also traditionally "managed" the previously-incubated projects. That >> would add the following to the mix: >> >> barbican 1.0.0 >> designate 1.0.0 >> manila 1.0.0 >> zaqar 1.0.0 >> > > Those didn't h

Re: [openstack-dev] [neutron][db] online schema upgrades

2015-06-16 Thread Mike Bayer
On 6/16/15 11:41 AM, Ihar Hrachyshka wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 - - instead of migrating data with alembic rules, migrate it in runtime. There should be a abstraction layer that will make sure that data is migrated into new schema fields and objects, while preservin

[openstack-dev] [Glance] [all] Proposal for Glance Artifacts Sub-Team meeting.

2015-06-16 Thread Nikhil Komawar
Hi all, We have planned a fast track development for Glance Artifacts; also it would be our v3 API. To balance pace, knowledge sharing, synchronous discussion on ideas and opinions as well as seeing this great feature through in Liberty: We hereby propose a non-mandatory, open to all, sub-team me

[openstack-dev] [devstack] apache wsgi application support

2015-06-16 Thread Sean Dague
I was just looking at the patches that put Nova under apache wsgi for the API, and there are a few things that I think are going in the wrong direction. Largely I think because they were copied from the lib/keystone code, which we've learned is kind of the wrong direction. The first is the fact th

[openstack-dev] [Keystone][OSC] Keystone v3 user create --project $projid does not add user to project?

2015-06-16 Thread Rich Megginson
Using admin token credentials with the Keystone v2.0 API and the openstackclient, doing this: # openstack project create bar --enable # openstack user create foo --project bar --enable ... The user will be added to the project. Using admin token credentials with the Keystone v3 API and the op

Re: [openstack-dev] [packaging] Adding packaging as an OpenStack project

2015-06-16 Thread Allison Randal
On 06/15/2015 01:43 PM, Paul Belanger wrote: > While I agree those points are valid, and going to be helpful, moving > under OpenStack (even Stackforge) does also offer the chance to get more > test integration upstream (not saying this was the original scope). > However, this could also be achieve

Re: [openstack-dev] [packaging] Adding packaging as an OpenStack project

2015-06-16 Thread Paul Belanger
On 06/16/2015 12:41 PM, Allison Randal wrote: On 06/15/2015 01:43 PM, Paul Belanger wrote: While I agree those points are valid, and going to be helpful, moving under OpenStack (even Stackforge) does also offer the chance to get more test integration upstream (not saying this was the original sc

Re: [openstack-dev] [neutron] Mechanism drivers and Neutron server forking?

2015-06-16 Thread Terry Wilson
> Right now I'm leaning toward "parent always does nothing" + PluginWorker. > Everything is forked, no special case for workers==0, and explicit > designation of the "only one" case. Of course, it's still early in the day > and I haven't had any coffee. I have updated the patch (https://review.ope

[openstack-dev] CLI problem

2015-06-16 Thread Ali Reza Zamani
Hi all, I have a problem in creating the instances. When I create the instances using GUI web interface everything is fine. But when I do it using CLI after spawning it says Error. And the error is: ne __ OpenStack Developmen

Re: [openstack-dev] [devstack] apache wsgi application support

2015-06-16 Thread Morgan Fainberg
Long term we want to see Keystone move to http:///identity. However the reason for choosing 5000/35357 for ports was compatibility and avoiding breaking horizon. At the time we did the initial change over, sharing the root 80/443 ports with horizon was more than "challenging" since horizon neede

Re: [openstack-dev] [all] FYI - dropping non RabbitMQ support in devstack

2015-06-16 Thread Clint Byrum
Excerpts from Sean Dague's message of 2015-06-16 06:22:23 -0700: > FYI, > > One of the things that came out of the summit for Devstack plans going > forward is to trim it back to something more opinionated and remove a > bunch of low use optionality in the process. > > One of those branches to be

Re: [openstack-dev] [Neutron] Quota enforcement

2015-06-16 Thread Carl Baldwin
On Thu, Jun 11, 2015 at 2:45 PM, Salvatore Orlando wrote: > I have been then following a different approach. And a set of patches, > including a devref one [2], if up for review [3]. This hardly completes the > job: more work is required on the testing side, both as unit and functional > tests. >

[openstack-dev] [grenade] future direction on partial upgrade support

2015-06-16 Thread Sean Dague
Back when Nova first wanted to test partial upgrade, we did a bunch of slightly odd conditionals inside of grenade and devstack to make it so that if you were very careful, you could just not stop some of the old services on a single node, upgrade everything else, and as long as the old services di

Re: [openstack-dev] [Neutron] Quota enforcement

2015-06-16 Thread Carl Baldwin
On Tue, Jun 16, 2015 at 12:33 AM, Kevin Benton wrote: >>Do these kinds of test even make sense? And are they feasible at all? I >> doubt we have any framework for injecting anything in neutron code under >> test. > > I was thinking about this in the context of a lot of the fixes we have for > othe

Re: [openstack-dev] CLI problem

2015-06-16 Thread Steve Martinelli
What was the command you used? What was the output? Can you try running it with --debug? More information is needed here. It would also probably be quicker to jump on IRC and ask around. Thanks, Steve Martinelli OpenStack Keystone Core "Ali Reza Zamani" wrote on 06/16/2015 12:46:16 PM: > Fr

Re: [openstack-dev] CLI problem

2015-06-16 Thread Ali Reza Zamani
It is weired. I deleted my devstack and redo everything. I am using the same command and everything is fine. Thanks, Regards, On 06/16/2015 01:03 PM, Steve Martinelli wrote: What was the command you used? What was the output? Can you try running it with --debug? More information is needed here

Re: [openstack-dev] [all] FYI - dropping non RabbitMQ support in devstack

2015-06-16 Thread Sean Dague
On 06/16/2015 12:49 PM, Clint Byrum wrote: > Excerpts from Sean Dague's message of 2015-06-16 06:22:23 -0700: >> FYI, >> >> One of the things that came out of the summit for Devstack plans going >> forward is to trim it back to something more opinionated and remove a >> bunch of low use optionality

Re: [openstack-dev] [javascript] [horizon] [merlin] [refstack] Javascript Linting

2015-06-16 Thread Tripp, Travis S
I’m copying and pasting from the other thread some info below. I think agreeing on rules is the bigger problem here and I don’t think all the projects should have to agree on rules. We’ve spent a good portion of liberty 1 getting the code base cleaned up to meet the already adopted horizon rules a

  1   2   >