Re: [openstack-dev] [nova][heat][[keystone] RFC: introducing "request identification"

2013-11-27 Thread haruka tanizawa
Hi, all!! I've just summarized mail until now. How to implement "request identification" ? === 1. Enable user to provide his/her own "request identification" within API request. e.g) Using instance-tasks-api 2. Use correlation_id in oslo as "request

[openstack-dev] [ceilometer][horizon] The meaning of "Network Duration"

2013-11-27 Thread Ying Chun Guo
Hello, While I translate Horizon web UI, I'm a little confused with "Network Duration", "Port Duration", and "Router Duration" in the Resources Usage statistics table. What does "Duration" mean here? If I translate it exactly as the meaning of "Duration", my customers cannot understand. Does it

Re: [openstack-dev] [heat][horizon]Heat UI related requirements & roadmap

2013-11-27 Thread Thomas Spatzier
Excerpts from Tim Schnell's message on 27.11.2013 00:44:04: > From: Tim Schnell > To: "OpenStack Development Mailing List (not for usage questions)" > , > Date: 27.11.2013 00:47 > Subject: Re: [openstack-dev] [heat][horizon]Heat UI related > requirements & roadmap > > > That is not the use case

Re: [openstack-dev] [heat][horizon]Heat UI related requirements & roadmap

2013-11-27 Thread Thomas Spatzier
Excerpts from Steve Baker's message on 26.11.2013 23:29:06: > From: Steve Baker > To: [email protected], > Date: 26.11.2013 23:32 > Subject: Re: [openstack-dev] [heat][horizon]Heat UI related > requirements & roadmap > > On 11/27/2013 11:02 AM, Christopher Armstrong wrote: > On Tu

Re: [openstack-dev] tenant or project

2013-11-27 Thread Thierry Carrez
Tim Bell wrote: > Can we get a TC policy that 'project' is the standard and that all projects > using tenant should plan a smooth migration path to project along with the > timescales for implementation and retirement of tenant ? Feel free to propose such policy for TC review. Rules of engagemen

Re: [openstack-dev] [Nova] Proposal to re-add Dan Prince to nova-core

2013-11-27 Thread Bob Ball
> -Original Message- > From: Russell Bryant [mailto:[email protected]] > Sent: 26 November 2013 19:33 > To: OpenStack Development Mailing List > Subject: [openstack-dev] [Nova] Proposal to re-add Dan Prince to nova-core > > I would like to propose that we re-add Dan Prince to the nova-cor

[openstack-dev] [Neutron][LBaaS] Thursday subteam meeting

2013-11-27 Thread Eugene Nikanorov
Hi Neutron folks, LBaaS subteam meeting will be on Thursday, 27, at 14-00 UTC as usual. We'll discuss current progress and continue with feature design. Thanks, Eugene. ___ OpenStack-dev mailing list [email protected] http://lists.openst

Re: [openstack-dev] [Solum] Definition feedback

2013-11-27 Thread Alex Heneveld
Personally "Application" gets my vote as the conceptual "top level" unit, with the best combination of some meaning and not too much ambiguity. At least so far. As Tom notes there is some ambiguity ... not sure we can avoid that altogether but worth some brainstorming. "Project" is what I

[openstack-dev] [diagnostic] Diagnostic/instrumentation API specification v0.1

2013-11-27 Thread Oleg Gelbukh
Greetings, fellow stackers I'm happy to announce that Rubick team has completed draft of Diagnostic API v0.1 spec [1] and started implementation of that API [2]. This draft provides hardware and operating system configuration data from physical nodes of the cluster. If you're interested in instrum

Re: [openstack-dev] [Oslo] Improving oslo-incubator update.py

2013-11-27 Thread Flavio Percoco
On 26/11/13 22:54 +, Mark McLoughlin wrote: On Fri, 2013-11-22 at 12:39 -0500, Doug Hellmann wrote: On Fri, Nov 22, 2013 at 4:11 AM, Flavio Percoco wrote: >1) Store the commit sha from which the module was copied from. >Every project using oslo, currently keeps the list of modules i

Re: [openstack-dev] [Oslo] Improving oslo-incubator update.py

2013-11-27 Thread Mark McLoughlin
On Wed, 2013-11-27 at 11:50 +0100, Flavio Percoco wrote: > On 26/11/13 22:54 +, Mark McLoughlin wrote: > >On Fri, 2013-11-22 at 12:39 -0500, Doug Hellmann wrote: > >> On Fri, Nov 22, 2013 at 4:11 AM, Flavio Percoco wrote: > >> >1) Store the commit sha from which the module was copied from.

Re: [openstack-dev] [Solum] Definition feedback

2013-11-27 Thread Tom Deckers (tdeckers)
Looks like most terms would have some ambiguity to them. Regardless of what we decide on - maybe Application can stay after all - we need a crisp definition of the term, preferably with an example that illustrates the terminology and puts Application in context of different versions of the same

Re: [openstack-dev] [Solum] Definition feedback

2013-11-27 Thread Tom Deckers (tdeckers)
>-Original Message- >From: Adrian Otto [mailto:[email protected]] >Sent: Wednesday, November 27, 2013 0:28 >To: OpenStack Development Mailing List (not for usage questions) >Subject: Re: [openstack-dev] [Solum] Definition feedback > >Tom, > >On Nov 26, 2013, at 12:09 PM, "Tom Deck

Re: [openstack-dev] [Oslo] Improving oslo-incubator update.py

2013-11-27 Thread Flavio Percoco
On 27/11/13 10:59 +, Mark McLoughlin wrote: On Wed, 2013-11-27 at 11:50 +0100, Flavio Percoco wrote: On 26/11/13 22:54 +, Mark McLoughlin wrote: >On Fri, 2013-11-22 at 12:39 -0500, Doug Hellmann wrote: >> On Fri, Nov 22, 2013 at 4:11 AM, Flavio Percoco wrote: >> >1) Store the commit

Re: [openstack-dev] [savanna] summit wrap-up: Heat integration

2013-11-27 Thread Sergey Lukjanov
Hi Steve, Thank you for comments and help. Sincerely yours, Sergey Lukjanov Savanna Technical Lead Mirantis Inc. On Nov 26, 2013, at 3:21 AM, Steve Baker wrote: > On 11/26/2013 06:21 AM, Sergey Lukjanov wrote: >> Hi guys, >> >> There was the Design Summit session in Hong Kong about Heat integ

[openstack-dev] [nova] Maintaining backwards compatibility for RPC calls

2013-11-27 Thread Day, Phil
Hi Folks, I'm a bit confused about the expectations of a manager class to be able to receive and process messages from a previous RPC version. I thought the objective was to always make changes such that the manage can process any previous version of the call that could come from the last re

Re: [openstack-dev] excessively difficult to support both iso8601 0.1.4 and 0.1.8 as deps

2013-11-27 Thread Sean Dague
The problem is you can't really support both iso8601 was dormant for years, and the revived version isn't compatible with the old version. So supporting both means basically forking iso8601 and maintaining you own version of it monkey patched in your own tree. On Wed, Nov 27, 2013 at 1:58 AM, Yagu

[openstack-dev] [neutron] [ml2] Today's ML2 meeting is canceled

2013-11-27 Thread Kyle Mestery (kmestery)
Some of the key people cannot make the meeting today, so we're canceling it for today. I would ask that people review the following two patches this week and we'll discuss them in detail next week if they haven't merged by then: https://review.openstack.org/#/c/21946/ https://review.openstack.org/

Re: [openstack-dev] [Nova] Proposal to re-add Dan Prince to nova-core

2013-11-27 Thread Andrew Laski
+1 On 11/26/13 at 02:32pm, Russell Bryant wrote: Greetings, I would like to propose that we re-add Dan Prince to the nova-core review team. Dan Prince has been involved with Nova since early in OpenStack's history (Bexar timeframe). He was a member of the nova-core review team from May 2011 t

Re: [openstack-dev] [TripleO] Summit session wrapup

2013-11-27 Thread Jaromir Coufal
On 2013/27/11 00:00, Robert Collins wrote: On 26 November 2013 07:41, Jaromir Coufal wrote: Hey Rob, can we add 'Slick Overcloud deployment through the UI' to the list? There was no session about that, but we discussed it afterwords and agreed that it is high priority for Icehouse as well. I

Re: [openstack-dev] [Nova] Proposal to re-add Dan Prince to nova-core

2013-11-27 Thread Gary Kotton
+1 On 11/27/13 3:29 PM, "Andrew Laski" wrote: >+1 > >On 11/26/13 at 02:32pm, Russell Bryant wrote: >>Greetings, >> >>I would like to propose that we re-add Dan Prince to the nova-core >>review team. >> >>Dan Prince has been involved with Nova since early in OpenStack's >>history (Bexar timeframe

Re: [openstack-dev] [nova] Core pinning

2013-11-27 Thread Tuomas Paappanen
On 19.11.2013 20:18, yunhong jiang wrote: On Tue, 2013-11-19 at 12:52 +, Daniel P. Berrange wrote: On Wed, Nov 13, 2013 at 02:46:06PM +0200, Tuomas Paappanen wrote: Hi all, I would like to hear your thoughts about core pinning in Openstack. Currently nova(with qemu-kvm) supports usage of c

Re: [openstack-dev] [Nova] Proposal to re-add Dan Prince to nova-core

2013-11-27 Thread Christopher Yeoh
+1 On Wed, Nov 27, 2013 at 6:02 AM, Russell Bryant wrote: > Greetings, > > I would like to propose that we re-add Dan Prince to the nova-core > review team. > > Dan Prince has been involved with Nova since early in OpenStack's > history (Bexar timeframe). He was a member of the nova-core review

Re: [openstack-dev] excessively difficult to support both iso8601 0.1.4 and 0.1.8 as deps

2013-11-27 Thread Zhi Yan Liu
Yes agreed with Sean, make compatible with both iso8601 is overcomplicated. This is my abandoned try: https://review.openstack.org/#/c/53186/ zhiyan On Wed, Nov 27, 2013 at 8:49 PM, Sean Dague wrote: > The problem is you can't really support both iso8601 was dormant for > years, and the revived

Re: [openstack-dev] tenant or project

2013-11-27 Thread Steven Hardy
On Tue, Nov 26, 2013 at 10:17:56PM +1030, Christopher Yeoh wrote: > On Mon, Nov 25, 2013 at 7:50 PM, Flavio Percoco wrote: > > On 24/11/13 12:47 -0500, Doug Hellmann wrote: > > > >> On Sun, Nov 24, 2013 at 12:08 AM, Morgan Fainberg > >> wrote: > >> > >>In all honesty it doesn't matter which t

Re: [openstack-dev] tenant or project

2013-11-27 Thread Anne Gentle
Hi Steve, There was a long thread about dropping project ID/tenant ID from the URL at http://openstack.markmail.org/thread/c2wi2uwdsye32z7f Looking back through it, it looks like nova v3 has it removed https://blueprints.launchpad.net/nova/+spec/v3-api-remove-project-id Maybe something in there

Re: [openstack-dev] tenant or project

2013-11-27 Thread Steven Hardy
On Wed, Nov 27, 2013 at 08:17:59AM -0600, Anne Gentle wrote: > Hi Steve, > > There was a long thread about dropping project ID/tenant ID from the URL at > http://openstack.markmail.org/thread/c2wi2uwdsye32z7f > > Looking back through it, it looks like nova v3 has it removed > https://blueprints.l

Re: [openstack-dev] [nova] Core pinning

2013-11-27 Thread Daniel P. Berrange
On Wed, Nov 27, 2013 at 03:50:47PM +0200, Tuomas Paappanen wrote: > >On Tue, 2013-11-19 at 12:52 +, Daniel P. Berrange wrote: > >>I think there are several use cases mixed up in your descriptions > >>here which should likely be considered independantly > >> > >> - pCPU/vCPU pinning > >> > >>

Re: [openstack-dev] [Solum] Definition feedback

2013-11-27 Thread Clayton Coleman
- Original Message - > > Personally "Application" gets my vote as the conceptual "top level" > unit, with the best combination of some meaning and not too much > ambiguity. At least so far. As Tom notes there is some ambiguity ... > not sure we can avoid that altogether but worth some

Re: [openstack-dev] [qa] Major change to tempest.conf.sample coming

2013-11-27 Thread Matthew Treinish
On Wed, Nov 13, 2013 at 02:42:34PM -0500, David Kranz wrote: > This is a heads up that soon we will be auto-generating the > tempest.conf.sample from the tempest code that uses oslo.config. > Following in the footsteps of nova, this should reduce bugs around > failures to keep the config code and t

[openstack-dev] [oslo] rpc concurrency control rfc

2013-11-27 Thread Edward Hope-Morley
Moving this to the ml as requested, would appreciate comments/thoughts/feedback. So, I recently proposed a small patch to the oslo rpc code (initially in oslo-incubator then moved to oslo.messaging) which extends the existing support for limiting the rpc thread pool so that concurrent requests can

Re: [openstack-dev] [Murano] [Neutron] [Fuel] Implementing Elastic Applications

2013-11-27 Thread Serg Melikyan
I had added Neutron and Fuel teams to this e-mail thread: Guys what is your thoughts on the subject? We see three possible ways to implement Elastic Applications in Murano: using Heat & Neutron LBaaS, Heat & AWS::ElasticLoadBalancing::LoadBalancer resource and own solution using HAProxy directly (

Re: [openstack-dev] tenant or project

2013-11-27 Thread Dolph Mathews
On Wed, Nov 27, 2013 at 8:12 AM, Steven Hardy wrote: > On Tue, Nov 26, 2013 at 10:17:56PM +1030, Christopher Yeoh wrote: > > On Mon, Nov 25, 2013 at 7:50 PM, Flavio Percoco > wrote: > > > On 24/11/13 12:47 -0500, Doug Hellmann wrote: > > > > > >> On Sun, Nov 24, 2013 at 12:08 AM, Morgan Fainberg

Re: [openstack-dev] [heat][horizon]Heat UI related requirements & roadmap

2013-11-27 Thread Tim Schnell
Ok, I just re-read my example and that was a terrible example. I'll try and create the user story first and hopefully answer Clint's and Thomas's concerns. If the only use case for adding keywords to the template is to help organize the template catalog then I would agree the keywords would go ou

[openstack-dev] [heat] Is it time for a v2 Heat API?

2013-11-27 Thread Steven Hardy
Hi all, Recently we've been skirting around the issue of an API version bump in various reviews, so I thought I'd start a thread where we can discuss the way forward. My view is that we probably should look at creating a v2 API during Icehouse, but we need to discuss what changes make sense, and

Re: [openstack-dev] [oslo] rpc concurrency control rfc

2013-11-27 Thread Mark McLoughlin
Hi, On Wed, 2013-11-27 at 14:45 +, Edward Hope-Morley wrote: > Moving this to the ml as requested, would appreciate > comments/thoughts/feedback. Thanks, I too would appreciate input from others. > So, I recently proposed a small patch to the oslo rpc code (initially in > oslo-incubator then

Re: [openstack-dev] [TripleO] Summit session wrapup

2013-11-27 Thread James Slagle
On Wed, Nov 27, 2013 at 8:39 AM, Jaromir Coufal wrote: > V0: basic slick installer - flexibility and control first > - enable user to auto-discover (or manual register) nodes > - let user decide, which node is going to be controller, which is going to > be compute or storage > - associate images

Re: [openstack-dev] [TripleO] Summit session wrapup

2013-11-27 Thread Tzu-Mainn Chen
- Original Message - > > On 2013/27/11 00:00, Robert Collins wrote: > > > > On 26 November 2013 07:41, Jaromir Coufal wrote: > > > > Hey Rob, > > can we add 'Slick Overcloud deployment through the UI' to the list? There > was no session about that, but we discussed it afterwords

Re: [openstack-dev] [Nova] [Infra] Support for PCI Passthrough

2013-11-27 Thread Jeremy Stanley
On 2013-11-27 11:18:46 +0800 (+0800), yongli he wrote: [...] > if you post -1, you should post testing log somewhere for people > to debug it, so does third party testing can post testing log to > the infra log server? Not at the moment--the "infra log server" is just an Apache name-based virtual

Re: [openstack-dev] [keystone] Service scoped role definition

2013-11-27 Thread Adam Young
On 11/26/2013 06:57 PM, Tiwari, Arvind wrote: Hi Adam, Based on our discussion over IRC, I have updated the below etherpad with proposal for nested role definition Updated. I made my changes Green. It isn't easy being green. https://etherpad.openstack.org/p/service-scoped-role-definiti

Re: [openstack-dev] [oslo] rpc concurrency control rfc

2013-11-27 Thread Daniel P. Berrange
On Wed, Nov 27, 2013 at 02:45:22PM +, Edward Hope-Morley wrote: > Moving this to the ml as requested, would appreciate > comments/thoughts/feedback. > > So, I recently proposed a small patch to the oslo rpc code (initially in > oslo-incubator then moved to oslo.messaging) which extends the exi

Re: [openstack-dev] [heat][horizon]Heat UI related requirements & roadmap

2013-11-27 Thread Zane Bitter
On 26/11/13 22:24, Tim Schnell wrote: Use Case #1 I see valid value in being able to group templates based on a type or +1, me too. keyword. This would allow any client, Horizon or a Template Catalog service, to better organize and handle display options for an end-user. I believe these are

Re: [openstack-dev] [Nova] Proposal to re-add Dan Prince to nova-core

2013-11-27 Thread Russell Bryant
On 11/26/2013 02:32 PM, Russell Bryant wrote: > Greetings, > > I would like to propose that we re-add Dan Prince to the nova-core > review team. > > Dan Prince has been involved with Nova since early in OpenStack's > history (Bexar timeframe). He was a member of the nova-core review team > from

Re: [openstack-dev] [Solum] Definition feedback

2013-11-27 Thread Adrian Otto
On Nov 27, 2013, at 3:23 AM, "Tom Deckers (tdeckers)" wrote: >> -Original Message- >> From: Adrian Otto [mailto:[email protected]] >> Sent: Wednesday, November 27, 2013 0:28 >> To: OpenStack Development Mailing List (not for usage questions) >> Subject: Re: [openstack-dev] [Solu

Re: [openstack-dev] [Nova] Proposal to add Matt Riedemann to nova-core

2013-11-27 Thread Russell Bryant
On 11/22/2013 03:53 PM, Russell Bryant wrote: > Greetings, > > I would like to propose adding Matt Riedemann to the nova-core review team. > > Matt has been involved with nova for a long time, taking on a wide range > of tasks. He writes good code. He's very engaged with the development > commu

Re: [openstack-dev] [heat][horizon]Heat UI related requirements & roadmap

2013-11-27 Thread Zane Bitter
On 26/11/13 23:44, Tim Schnell wrote: A template-validate call would need to return all the group and ordering >information, but otherwise heat can ignore this extra data. I agree with all of your modifications, although bringing up the template-validate call reminded me that the implementation

Re: [openstack-dev] [nova] Maintaining backwards compatibility for RPC calls

2013-11-27 Thread yunhong jiang
On Wed, 2013-11-27 at 12:38 +, Day, Phil wrote: > Doesn’t this mean that you can’t deploy Icehouse (3.0) code into a > Havana system but leave the RPC version pinned at Havana until all of > the code has been updated ? I think it's because this change is for computer manager, not for conduct

[openstack-dev] [Neutron] Stop logging non-exceptional conditions as ERROR

2013-11-27 Thread Maru Newby
Just a heads up, the console output for neutron gate jobs is about to get a lot noisier. Any log output that contains 'ERROR' is going to be dumped into the console output so that we can identify and eliminate unnecessary error logging. Once we've cleaned things up, the presence of unexpected

Re: [openstack-dev] [heat][horizon]Heat UI related requirements & roadmap

2013-11-27 Thread Tim Schnell
On 11/27/13 10:39 AM, "Zane Bitter" wrote: >On 26/11/13 23:44, Tim Schnell wrote: >>> A template-validate call would need to return all the group and >>>ordering >>> >information, but otherwise heat can ignore this extra data. >> I agree with all of your modifications, although bringing up the >

Re: [openstack-dev] [heat][horizon]Heat UI related requirements & roadmap

2013-11-27 Thread Thomas Spatzier
Thanks, that clarified the use case a bit. Bot looking at the use case now, isn't this stack tagging instead of template tagging? I.e. assume that for each stack a user creates, he/she can assign one or more tags so you can do better queries to find stacks later? Regards, Thomas Tim Schnell wrot

Re: [openstack-dev] [Nova] Is there a way for the VM to identify that it is getting booted in OpenStack

2013-11-27 Thread yunhong jiang
On Wed, 2013-11-27 at 01:48 +, Vijay Venkatachalam wrote: > Hi, > > Is there a way for the VM to identify that it is > getting booted in OpenStack? > > As said in the below mail, once the VM knows it is > booting in OpenStack it will alter the boot sequence. >

[openstack-dev] [Solum] [Security]

2013-11-27 Thread Paul Montgomery
I created some relatively high level security best practices that I thought would apply to Solum. I don't think it is ever too early to get mindshare around security so that developers keep that in mind throughout the project. When a design decision point could easily go two ways, perhaps these g

Re: [openstack-dev] [heat][horizon]Heat UI related requirements & roadmap

2013-11-27 Thread Fox, Kevin M
This use case is sort of a providence case. Where did the stack come from so I can find out more about it. You could put a git commit field in the template itself but then it would be hard to keep updated. How about the following: Extend heat to support setting a "scmcommit" metadata item on s

Re: [openstack-dev] [heat] Is it time for a v2 Heat API?

2013-11-27 Thread Zane Bitter
On 27/11/13 16:27, Steven Hardy wrote: I've raised this BP: https://blueprints.launchpad.net/heat/+spec/v2api And started a WIP wiki page where we can all work on refining what changes need to be made: https://wiki.openstack.org/wiki/Heat/Blueprints/V2API The current (v1) API design is based

Re: [openstack-dev] [heat][horizon]Heat UI related requirements & roadmap

2013-11-27 Thread Edmund Troche
You bring up a good point Thomas. I think some of the discussions are mixing template and stack perspectives, they are not the same thing, stack == instance of a template. There likely is room for "tagging" stacks, all under the control of the user and meant for user consumption, vs the long going

Re: [openstack-dev] [Neutron] Stop logging non-exceptional conditions as ERROR

2013-11-27 Thread Salvatore Orlando
Thanks Maru, This is something my team had on the backlog for a while. I will push some patches to contribute towards this effort in the next few days. Let me know if you're already thinking of targeting the completion of this job for a specific deadline. Salvatore On 27 November 2013 17:50, M

Re: [openstack-dev] [heat][horizon]Heat UI related requirements & roadmap

2013-11-27 Thread Clint Byrum
Excerpts from Zane Bitter's message of 2013-11-27 08:09:33 -0800: > In the longer term, there seems to be a lot of demand for some sort of > template catalog service, like Glance for templates. (I disagree with > Clint that it should actually _be_ Glance the project as we know it, for > the reas

Re: [openstack-dev] [heat][horizon]Heat UI related requirements & roadmap

2013-11-27 Thread Tim Schnell
On 11/27/13 10:09 AM, "Zane Bitter" wrote: >On 26/11/13 22:24, Tim Schnell wrote: >> Use Case #1 >> I see valid value in being able to group templates based on a type or > >+1, me too. > >> keyword. This would allow any client, Horizon or a Template Catalog >> service, to better organize and han

Re: [openstack-dev] [heat] Is it time for a v2 Heat API?

2013-11-27 Thread Jay Pipes
On 11/27/2013 12:02 PM, Zane Bitter wrote: On 27/11/13 16:27, Steven Hardy wrote: I've raised this BP: https://blueprints.launchpad.net/heat/+spec/v2api And started a WIP wiki page where we can all work on refining what changes need to be made: https://wiki.openstack.org/wiki/Heat/Blueprints/

Re: [openstack-dev] [heat][horizon]Heat UI related requirements & roadmap

2013-11-27 Thread Tim Schnell
Yes, I guess you could phrase it as stack tagging, focusing on the template was my attempt to solve 2 use cases with one solution but I'M open to alternatives. Are you suggesting that we build the ability to add "tags" to stacks that exist outside of the template? I guess add them directly to Heat'

Re: [openstack-dev] [heat] Is it time for a v2 Heat API?

2013-11-27 Thread Steven Hardy
On Wed, Nov 27, 2013 at 06:02:27PM +0100, Zane Bitter wrote: > On 27/11/13 16:27, Steven Hardy wrote: > >I've raised this BP: > > > >https://blueprints.launchpad.net/heat/+spec/v2api > > > >And started a WIP wiki page where we can all work on refining what changes > >need to be made: > > > >https:/

Re: [openstack-dev] [heat][horizon]Heat UI related requirements & roadmap

2013-11-27 Thread Tim Schnell
On 11/27/13 10:58 AM, "Fox, Kevin M" wrote: >This use case is sort of a providence case. Where did the stack come from >so I can find out more about it. > >You could put a git commit field in the template itself but then it would >be hard to keep updated. > >How about the following: > >Extend he

Re: [openstack-dev] [heat][horizon]Heat UI related requirements & roadmap

2013-11-27 Thread Tim Schnell
From: Edmund Troche mailto:[email protected]>> Reply-To: "OpenStack Development Mailing List (not for usage questions)" mailto:[email protected]>> Date: Wednesday, November 27, 2013 11:08 AM To: "OpenStack Development Mailing List (not for usage questions)" mailto:openstac

[openstack-dev] [Ceilometer] storage driver testing

2013-11-27 Thread Sandy Walsh
Hey! We've ballparked that we need to store a million events per day. To that end, we're flip-flopping between sql and no-sql solutions, hybrid solutions that include elastic search and other schemes. Seems every road we go down has some limitations. So, we've started working on test suite for

Re: [openstack-dev] [oslo] rpc concurrency control rfc

2013-11-27 Thread Edward Hope-Morley
On 27/11/13 15:49, Daniel P. Berrange wrote: > On Wed, Nov 27, 2013 at 02:45:22PM +, Edward Hope-Morley wrote: >> Moving this to the ml as requested, would appreciate >> comments/thoughts/feedback. >> >> So, I recently proposed a small patch to the oslo rpc code (initially in >> oslo-incubator

Re: [openstack-dev] [Nova] Is there a way for the VM to identify that it is getting booted in OpenStack

2013-11-27 Thread Chris Friesen
On 11/26/2013 07:48 PM, Vijay Venkatachalam wrote: Hi, Is there a way for the VM to identify that it is getting booted in OpenStack? As said in the below mail, once the VM knows it is booting in OpenStack it will alter the boot sequence. What does "getting bo

Re: [openstack-dev] [oslo] rpc concurrency control rfc

2013-11-27 Thread Daniel P. Berrange
On Wed, Nov 27, 2013 at 05:39:30PM +, Edward Hope-Morley wrote: > On 27/11/13 15:49, Daniel P. Berrange wrote: > > On Wed, Nov 27, 2013 at 02:45:22PM +, Edward Hope-Morley wrote: > >> Moving this to the ml as requested, would appreciate > >> comments/thoughts/feedback. > >> > >> So, I recen

Re: [openstack-dev] excessively difficult to support both iso8601 0.1.4 and 0.1.8 as deps

2013-11-27 Thread Alan Pevec
2013/11/27 Sean Dague : > The problem is you can't really support both iso8601 was dormant for > years, and the revived version isn't compatible with the old version. > So supporting both means basically forking iso8601 and maintaining you > own version of it monkey patched in your own tree. Right

Re: [openstack-dev] [heat] Is it time for a v2 Heat API?

2013-11-27 Thread Zane Bitter
On 27/11/13 18:16, Jay Pipes wrote: On 11/27/2013 12:02 PM, Zane Bitter wrote: Your proposal on the wiki page retains this URL but removes the tenant ID: GET /v2/stacks/{stack_name} This now no longer uniquely identifies a stack, and is therefore not ReST. It would be along with a Vary:

Re: [openstack-dev] EC2 Filter

2013-11-27 Thread Joe Gordon
On Tue, Nov 26, 2013 at 1:56 AM, Sebastian Porombka < [email protected]> wrote: > Oh hai! > > That's nice to hear! I would like to help by adapting this patch set to > latest and > I will try to work out the tempest test cases. > > Is there any form of documentation for new developers? >

Re: [openstack-dev] [Nova] Is there a way for the VM to identify that it is getting booted in OpenStack

2013-11-27 Thread Daniel P. Berrange
On Wed, Nov 27, 2013 at 01:48:29AM +, Vijay Venkatachalam wrote: > Hi, > Is there a way for the VM to identify that it is getting > booted in OpenStack? The mails you've forwarded below pretty much answer this question already. > As said in the below mail, onc

Re: [openstack-dev] [heat][horizon]Heat UI related requirements & roadmap

2013-11-27 Thread Jason Dunsmore
On Wed, Nov 27 2013, Zane Bitter wrote: >> >> Parameters: >> db_name: >> group: db >> order: 0 >> db_username: >> group: db >> order: 1 >> db_password: >>

Re: [openstack-dev] [heat] Is it time for a v2 Heat API?

2013-11-27 Thread Chris Friesen
On 11/27/2013 11:50 AM, Zane Bitter wrote: Even better would be if we had the keystone domain (instead of the tenant id) incorporated into the endpoint in the keystone catalog and then we could use the tenant^W project *name* in the URL and users would never have to deal with UUIDs and invisible

Re: [openstack-dev] [Nova] Is there a way for the VM to identify that it is getting booted in OpenStack

2013-11-27 Thread yunhong jiang
On Wed, 2013-11-27 at 11:41 -0600, Chris Friesen wrote: > On 11/26/2013 07:48 PM, Vijay Venkatachalam wrote: > > Hi, > > > > Is there a way for the VM to identify that it is > > getting booted in OpenStack? > > > > As said in the below mail, once the VM knows it is

Re: [openstack-dev] [oslo] rpc concurrency control rfc

2013-11-27 Thread Edward Hope-Morley
On 27/11/13 17:43, Daniel P. Berrange wrote: > On Wed, Nov 27, 2013 at 05:39:30PM +, Edward Hope-Morley wrote: >> On 27/11/13 15:49, Daniel P. Berrange wrote: >>> On Wed, Nov 27, 2013 at 02:45:22PM +, Edward Hope-Morley wrote: Moving this to the ml as requested, would appreciate c

Re: [openstack-dev] [oslo] rpc concurrency control rfc

2013-11-27 Thread Daniel P. Berrange
On Wed, Nov 27, 2013 at 06:10:47PM +, Edward Hope-Morley wrote: > On 27/11/13 17:43, Daniel P. Berrange wrote: > > On Wed, Nov 27, 2013 at 05:39:30PM +, Edward Hope-Morley wrote: > >> On 27/11/13 15:49, Daniel P. Berrange wrote: > >>> On Wed, Nov 27, 2013 at 02:45:22PM +, Edward Hope-Mo

Re: [openstack-dev] FreeBSD hypervisor (bhyve) driver

2013-11-27 Thread Rafał Jaworowski
On Mon, Nov 25, 2013 at 3:50 PM, Daniel P. Berrange wrote: > On Fri, Nov 22, 2013 at 10:46:19AM -0500, Russell Bryant wrote: >> On 11/22/2013 10:43 AM, Rafał Jaworowski wrote: >> > Russell, >> > First, thank you for the whiteboard input regarding the blueprint for >> > FreeBSD hypervisor nova driv

Re: [openstack-dev] [Solum] Definition feedback

2013-11-27 Thread Jay Pipes
On 11/27/2013 06:23 AM, Tom Deckers (tdeckers) wrote: I understand the an Assembly can be a larger group of components. However, those together exist to provide a capability which we want to capture in some catalog so the capability becomes discoverable. I'm not sure how the 'listing' mechanism w

Re: [openstack-dev] [heat][horizon]Heat UI related requirements & roadmap

2013-11-27 Thread Zane Bitter
On 27/11/13 18:12, Clint Byrum wrote: Excerpts from Zane Bitter's message of 2013-11-27 08:09:33 -0800: In the longer term, there seems to be a lot of demand for some sort of template catalog service, like Glance for templates. (I disagree with Clint that it should actually _be_ Glance the proje

Re: [openstack-dev] [oslo] rpc concurrency control rfc

2013-11-27 Thread Edward Hope-Morley
On 27/11/13 18:20, Daniel P. Berrange wrote: > On Wed, Nov 27, 2013 at 06:10:47PM +, Edward Hope-Morley wrote: >> On 27/11/13 17:43, Daniel P. Berrange wrote: >>> On Wed, Nov 27, 2013 at 05:39:30PM +, Edward Hope-Morley wrote: On 27/11/13 15:49, Daniel P. Berrange wrote: > On Wed,

[openstack-dev] [Solum] API worker architecture

2013-11-27 Thread Murali Allada
Hi all, I'm working on a new blueprint to define the API service architecture. https://blueprints.launchpad.net/solum/+spec/api-worker-architecture It is still a draft for now. I've proposed a simple architecture for us to get started with implementing a few useful use cases. Please chime in o

[openstack-dev] [neutron] Why neutron-openvswitch-agent use linux-bridge?

2013-11-27 Thread George Shuklin
Good day. I looking at the internals of bridge layout of openvswitch agent at http://docs.openstack.org/network-admin/admin/content/figures/2/figures/under-the-hood-scenario-1-ovs-compute.png and wondering, why this scheme is so complicated and why it use linux bridge and vethes with openvswitc

[openstack-dev] [nova][libvirt] Gate bug 'libvirtError: Unable to read from monitor: Connection reset by peer'

2013-11-27 Thread Joe Gordon
Hi Daniel, all This morning I noticed we are seeing libvirt stacktrace in the gate occasionally. https://bugs.launchpad.net/nova/+bug/1255624 Since your are a libvirt maintainer I was hoping you could take a look at this one. best, Joe P.S. We also have a second libvirt gate bug https://bug

[openstack-dev] [all project] Time to fail tempest gate jobs when new log errors appear

2013-11-27 Thread David Kranz
tl;dr Soon, perhaps next week, tempest gate jobs will start failing if there are any ERROR lines in the logs that are not matched by an entry in https://github.com/openstack/tempest/blob/master/etc/whitelist.yaml. There is an exception for neutron because more work needs to be done there for th

Re: [openstack-dev] [neutron] Why neutron-openvswitch-agent use linux-bridge?

2013-11-27 Thread Lorin Hochstein
Hi George: On Wed, Nov 27, 2013 at 1:45 PM, George Shuklin wrote: > Good day. > > I looking at the internals of bridge layout of openvswitch agent at > http://docs.openstack.org/network-admin/admin/content/ > figures/2/figures/under-the-hood-scenario-1-ovs-compute.png > and wondering, why this

Re: [openstack-dev] [heat][horizon]Heat UI related requirements & roadmap

2013-11-27 Thread Jay Pipes
On 11/27/2013 01:28 AM, Clint Byrum wrote: I propose adding an additional field to the parameter definition: Parameters: : description: This is the name of a nova key pair that will be used to ssh to the compute instance. help: To learn more about nova ke

[openstack-dev] [trove][savanna] summit wrap-up: clustering

2013-11-27 Thread Sergey Lukjanov
Hi folks, There was a thread around the Clustering API [0] and we decided to continue it on summit, so, I’d like to summarize things that was done before and at the summit on this topic. First of all, thanks Michael Basnight (hub_cap) and all Trove folks for productive discussions on Design Su

Re: [openstack-dev] FreeBSD hypervisor (bhyve) driver

2013-11-27 Thread Daniel P. Berrange
On Wed, Nov 27, 2013 at 07:32:13PM +0100, Rafał Jaworowski wrote: > On Mon, Nov 25, 2013 at 3:50 PM, Daniel P. Berrange > wrote: > > I am of course biased, as libvirt project maintainer, but I do agree > > that supporting bhyve via libvirt would make sense, since it opens up > > opportunities bey

Re: [openstack-dev] [all project] Time to fail tempest gate jobs when new log errors appear

2013-11-27 Thread Jay Pipes
On 11/27/2013 01:53 PM, David Kranz wrote: tl;dr Soon, perhaps next week, tempest gate jobs will start failing if there are any ERROR lines in the logs that are not matched by an entry in https://github.com/openstack/tempest/blob/master/etc/whitelist.yaml. There is an exception for neutron becaus

[openstack-dev] [savanna] team meeting *cancelled* Nov 28

2013-11-27 Thread Sergey Lukjanov
Hi folks, Savanna team meeting cancelled this week due to the major US holiday. We’ll be having irc meeting as usual at Dec 5 1800 UTC. Thanks. P.S. Have a nice holiday! Sincerely yours, Sergey Lukjanov Savanna Technical Lead Mirantis Inc. ___ Open

Re: [openstack-dev] [Solum] Definition feedback

2013-11-27 Thread Adrian Otto
Jay, On Nov 27, 2013, at 10:36 AM, Jay Pipes wrote: > On 11/27/2013 06:23 AM, Tom Deckers (tdeckers) wrote: >> I understand the an Assembly can be a larger group of components. >> However, those together exist to provide a capability which we want >> to capture in some catalog so the capability

Re: [openstack-dev] Gate broken right now

2013-11-27 Thread Robert Collins
On 27 November 2013 07:19, James E. Blair wrote: > > There is not, currently, though we would love to have more people on the > infra-core (and infra-root) teams. If you know someone, or you > yourself, or your company are interested in contributing in this area, > please get in contact and we ca

Re: [openstack-dev] [heat][horizon]Heat UI related requirements & roadmap

2013-11-27 Thread Zane Bitter
On 27/11/13 18:16, Tim Schnell wrote: On 11/27/13 10:09 AM, "Zane Bitter" wrote: On 26/11/13 22:24, Tim Schnell wrote: Use Case #1 I see valid value in being able to group templates based on a type or +1, me too. keyword. This would allow any client, Horizon or a Template Catalog service

Re: [openstack-dev] [nova][libvirt] Gate bug 'libvirtError: Unable to read from monitor: Connection reset by peer'

2013-11-27 Thread Daniel P. Berrange
On Wed, Nov 27, 2013 at 10:50:12AM -0800, Joe Gordon wrote: > Hi Daniel, all > > This morning I noticed we are seeing libvirt stacktrace in the gate > occasionally. > > https://bugs.launchpad.net/nova/+bug/1255624 > > Since your are a libvirt maintainer I was hoping you could take a look at > th

Re: [openstack-dev] [nova][libvirt] Gate bug 'libvirtError: Unable to read from monitor: Connection reset by peer'

2013-11-27 Thread Jeremy Stanley
On 2013-11-27 19:18:12 + (+), Daniel P. Berrange wrote: [...] > It would be desirable if the gate logs included details of all software > package versions installed. eg so we can see what libvirt, qemu and > kernel are present. [...] It seems reasonable to me that we could dpkg -l or rpm -

Re: [openstack-dev] [Solum] Definition feedback

2013-11-27 Thread Jay Pipes
On 11/27/2013 02:03 PM, Adrian Otto wrote: Jay, On Nov 27, 2013, at 10:36 AM, Jay Pipes wrote: On 11/27/2013 06:23 AM, Tom Deckers (tdeckers) wrote: I understand the an Assembly can be a larger group of components. However, those together exist to provide a capability which we want to captur

Re: [openstack-dev] [neutron] Why neutron-openvswitch-agent use linux-bridge?

2013-11-27 Thread George Shuklin
Thank you for reply! Few more question: AFAIK bridge tools is not very fast (compare to OVS), so adding them between OVS and tap (instead of yet another OVS switch) is kinda slow everything down. Why just not use yet another openvswitch switch to connect tap to veth devices? Why iptables, not in

[openstack-dev] [nova][vmware] VMwareAPI sub-team status update 2011-11-27

2013-11-27 Thread Shawn Hartsock
Greetings Stackers! We have Icehouse-1 on December 5th! Here's the reviews that the VMwareAPI team has in flight in order of fitness for review by core reviewers. It's also holiday season now so please keep in mind folks may be in and out during this period. Let's see if we can't get some of th

Re: [openstack-dev] [oslo] rpc concurrency control rfc

2013-11-27 Thread Daniel P. Berrange
On Wed, Nov 27, 2013 at 06:43:42PM +, Edward Hope-Morley wrote: > On 27/11/13 18:20, Daniel P. Berrange wrote: > > On Wed, Nov 27, 2013 at 06:10:47PM +, Edward Hope-Morley wrote: > >> On 27/11/13 17:43, Daniel P. Berrange wrote: > >>> On Wed, Nov 27, 2013 at 05:39:30PM +, Edward Hope-Mo

Re: [openstack-dev] [Solum] API worker architecture

2013-11-27 Thread Roshan Agrawal
We should probably include support for asynchronous responses right from the beginning to handle calls that need a long time to process. Is this in line with what you were thinking ? I am referring to your comment in the blueprint "To start things off, we can implement workflow #1 shown above an

  1   2   >