[openstack-dev] [Keystone] [Horizon] Havana RC2 available

Hi everyone, Our last two RC2 windows just closed. Due to major issues detected in key features during RC1 testing, we just published new Havana release candidates for OpenStack Identity ("Keystone") and OpenStack Dashboard ("Horizon"). You can find RC2 tarballs and lists of fixed bugs at: https

Re: [openstack-dev] [scheduler] APIs for Smart Resource Placement - Updated Instance Group Model and API extension model - WIP Draft

I have made some edits to the document: https://docs.google.com/document/d/17OIiBoIavih-1y4zzK0oXyI66529f-7JTCVj-BcXURA/edit?pli=1# by updating the Instance Group Model and APIs based on the recent mailing list discussion below and also about the Policy Model in another email thread. An action

[openstack-dev] [Nova] configdrive not presenting IPAddress information

Hi, The configdrive does not have IPAddress information in meta_data.json or in any of the other files. Is this planned for the future? The only other options is for the user to manually pass this information through other parameters like "-meta" or "-fi

[openstack-dev] [Nova] What validation feature is necessary for Nova v3 API

Hi, # I resend this because gmail distinguished my previous mail as spam one.. I'd like to know what validation feature is really needed for Nova v3 API, and I hope this mail will be a kick-off of brain-storming for it. << Introduction >> I have submitted a blueprint "nova-api-validation-fw". T

Re: [openstack-dev] [novaclient]should administrator can see all servers of all tenants by default?

then, what's the conclusion that we can begin to start? 2013/10/15 Christopher Yeoh > On Tue, Oct 15, 2013 at 10:25 AM, Caitlin Bestler < > [email protected]> wrote: > >> On 10/14/2013 8:37 AM, Ben Nemec wrote: >> >>> I agree that this needs to be fixed. It's very counterintuitive, i

[openstack-dev] Reminder: Project & release status meeting - 21:00 UTC

Today we'll have the last release meeting before Havana final release. At the time of this writing no RC window is currently open. For each project we'll look at havana-rc-potential bugs and see if any of them is worth the risk associated with a late respin. We'll also review the state of the Relea

Re: [openstack-dev] [Mistral] Announcing a new task scheduling and orchestration service for OpenStack

Hey Clint, thanks for your question. I think it's been fully answered by this time. You and other people are very welcome to collaborate :) Joshua, as far as renaming the original document I would suggest we keep it as it is for now just to preserve the explicit history of how it's been going so

Re: [openstack-dev] [novaclient]should administrator can see all servers of all tenants by default?

Please don't invert the bug though: if --all-tenants becomes the default nova server behaviour in v3, please ensure there is a --no-all-tenants to unbreak it for non-trivial clouds. Thanks! -Rob On 15 October 2013 20:54, Lingxian Kong wrote: > then, what's the conclusion that we can begin to sta

Re: [openstack-dev] [Heat] Plugin packaging

On 15/10/13 02:18, Sam Alba wrote: Hello, I am working on a Heat plugin that makes a new resource available in a template. It's working great and I will opensource it this week if I can get the packaging right... Awesome! :) Right now, I am linking my module.py file in /usr/lib/heat to get i

[openstack-dev] How to get VXLAN Endpoint IP without agent

Hi, Vxlan endpoint ip is configured in '/etc/neutron/plugins/openvswitch/ovs_neutron_plugin.ini' as 'local_ip' While starting openvswitch agent the above local ip is populated in neutron database. Is there any way to get local_ip of compute node without any agent running? Thanks in advance. R

Re: [openstack-dev] [Mistral] Announcing a new task scheduling and orchestration service for OpenStack

On 14/10/13 21:40, Renat Akhmerov wrote: Hi OpenStackers, I am proud to announce the official launch of the Mistral project. At Mirantis we have a team to start contributing to the project right away. We invite anybody interested in task service & state management to join the initiative. Mistra

Re: [openstack-dev] [novaclient]should administrator can see all servers of all tenants by default?

Have there been any changes in V3 now? 2013/10/15 Robert Collins > Please don't invert the bug though: if --all-tenants becomes the > default nova server behaviour in v3, please ensure there is a > --no-all-tenants to unbreak it for non-trivial clouds. > > Thanks! > -Rob > > On 15 October 2013

Re: [openstack-dev] [Mistral] Announcing a new task scheduling and orchestration service for OpenStack

On 15.10.2013, at 14:45, Zane Bitter wrote: > That said, can we please, please, please not invent a *third* meaning of > "orchestration"? The proposal, as I understand it, is Workflow as a Service, > so let's call it that. The fact that orchestration uses a workflow does not > make them the s

Re: [openstack-dev] Scheduler meeting and Icehouse Summit

Hi Debo, > I was wondering if we are shooting for too much to discuss by clubbing. > i) Group Scheduling / Smart Placement / Heat and Scheduling (1), (2), (3), & > (7) >- How do you schedule something more complex that a single VM ? I agree it's a lot to get through, but we're working

Re: [openstack-dev] Scheduler meeting and Icehouse Summit

Hi Alex, My understanding is that the 17th is the deadline and that Russell needs to be planning the sessions from that point onwards. If we delay in giving him our suggestions until the 22nd I think it would be too late.We've had weeks if not months now of discussing possible scheduler se

[openstack-dev] [nova] libvirt+xen support and compute driver hypervisor matrix

Hi there. I would like to know which is the criteria for the inclusion of a new driver column in the Hypervisor Support Matrix [1]. We are happy users of libvirt+Xen so we were thinking in the needed steps to promote it from group C to B (and eventually A) for Icehouse (with Russell's mail in min

[openstack-dev] Doc Team meeting - in an hour

Hi all, The OpenStack Doc team meeting will take place in #openstack-meeting on IRC at 13:00 UTC - about an hour from now. The Agenda is here: https://wiki.openstack.org/wiki/Meetings/DocTeamMeeting#Agenda_for_next_meeting Please add items of interest to you and join us. Regards, Tom __

Re: [openstack-dev] [nova] [tempest] [ceilometer] Defining Diagnotics API Schema (was: looking for clarification...)

"Open Ended API" isn't really an API. An API has a contract, otherwise it isn't an API. The diagnostics REST call currently seems to have no contract at all, and is just implemented by the underlying driver to whatever seems like a good idea today (also, no versioning on things, so what libvirt ret

Re: [openstack-dev] how can i get volume name in create snapshot call

Dinakar, The driver's create_snapshot function gets a dictionary that describes the snapshot. In that dictionary, you have the "volume_name" field that has the source volume's name: snapshot['volume_name']. You can get other details via snapshot['volume'], which is a dictionary containing the vol

Re: [openstack-dev] [Nova] UpgradeImpact commit message tag

Good idea, I'd only ask that you post back here when you have something up in the wiki so we can remember to review it. This is more for me so I have this in mind when doing reviews, i.e. does the change fall into this category but doesn't tag it. Thinking maybe DB migration issues, backwards

Re: [openstack-dev] [nova] [tempest] [ceilometer] Defining Diagnotics API Schema (was: looking for clarification...)

On Tue, Oct 15, 2013 at 8:13 AM, Sean Dague wrote: > "Open Ended API" isn't really an API. An API has a contract, otherwise it > isn't an API. > I need that saying on a t-shirt. > The diagnostics REST call currently seems to have no contract at all, and > is just implemented by the underlying

Re: [openstack-dev] [qa] Update: Nova API List for Missing Tempest Tests

On Tue, Oct 15, 2013 at 06:25:28AM +, Masayuki Igawa wrote: > Hi, > > First, thank you to an anonymous for updating this list! > -> GET /{project_id}/servers/:server_id/diagnostics > > And, I have updated: Nova API List for Missing Tempest Tests. > > https://docs.google.com/spreadshee

Re: [openstack-dev] [Mistral] Announcing a new task scheduling and orchestration service for OpenStack

Maybe add a link to the Mistral page from the Convention page? On Oct 15, 2013 4:22 AM, "Renat Akhmerov" wrote: > Hey Clint, thanks for your question. I think it's been fully answered by > this time. You and other people are very welcome to collaborate :) > > Joshua, as far as renaming the origin

Re: [openstack-dev] [Mistral] Announcing a new task scheduling and orchestration service for OpenStack

Yes, will do. Thanks! On 15.10.2013, at 18:37, Nick Chase wrote: > Maybe add a link to the Mistral page from the Convention page? > > On Oct 15, 2013 4:22 AM, "Renat Akhmerov" wrote: > Hey Clint, thanks for your question. I think it's been fully answered by this > time. You and other people a

Re: [openstack-dev] [Nova] configdrive not presenting IPAddress information

Hi, There is some information in the EC2 metadata, or at least I have a patch up for that: https://review.openstack.org/#/c/46286/ I am raising some ideas to improve things here: http://summit.openstack.org/cfp/details/191 John On 15 October 2013 08:24, Vijay Venkatachalam wrote: > Hi, > >

Re: [openstack-dev] [Hyper-V] Havana status

On 11 October 2013 15:41, Alessandro Pilotti wrote: > Current reviews require: > > +1 "de facto" driver X mantainer(s) > +2 core reviewer > +2A core reviewer > > While with the proposed scenario we'd get to a way faster route: > > +2 driver X mantainer > +2A another driver X mantainer or a core

Re: [openstack-dev] [Ceilometer] Notifications from non-local exchanges

> -Original Message- > From: Sandy Walsh [mailto:[email protected]] > Sent: Thursday, October 10, 2013 6:20 PM > To: [email protected] > Subject: Re: [openstack-dev] [Ceilometer] Notifications from non-local > exchanges > > > On 10/10/2013 06:16 PM, Neal, Phil wr

Re: [openstack-dev] [Hyper-V] Havana status

On Oct 15, 2013, at 18:14 , Duncan Thomas mailto:[email protected]>> wrote: On 11 October 2013 15:41, Alessandro Pilotti mailto:[email protected]>> wrote: Current reviews require: +1 "de facto" driver X mantainer(s) +2 core reviewer +2A core reviewer While with the propos

Re: [openstack-dev] [Heat] Plugin packaging

On Tue, Oct 15, 2013 at 2:31 AM, Zane Bitter wrote: > On 15/10/13 02:18, Sam Alba wrote: >> >> Hello, >> >> I am working on a Heat plugin that makes a new resource available in a >> template. It's working great and I will opensource it this week if I >> can get the packaging right... > > > Awesome

Re: [openstack-dev] [Hyper-V] Havana status

Sorry to pile on, but: "this was not particularly the case for what our driver is concerned. As I already wrote, almost all the reviews so far have been related to unit tests or minor formal corrections." As was pointed out by me in patch set 1 here: https://review.openstack.org/#/c/43592/ T

Re: [openstack-dev] [Hyper-V] Havana status

On 11 October 2013 20:51, Rochelle.Grober wrote: > Proposed solution: > > There have been a couple of solutions proposed. I’m presenting a > merged/hybrid solution that may work > > · Create a new repository for the extra drivers: > > o Keep kvm and Xenapi in the Nova project as “refere

[openstack-dev] Hyper-V meeting agenda.

Hi All, The following will be discussed in today's hyper-v meeting. * Splitting the hyper-v driver options and discussion * Bug Status * Puppet modules Peter J. Pouliot, CISSP Senior SDET, OpenStack Microsoft New England Research & Development Center One Memorial Driv

Re: [openstack-dev] Keystone Apache2 Installation Question

Since negotiate isn't supported, at least basic auth support allows authenticating against our domain rather then users needing to come up with another password. The basic auth support is not specific to kerberos either, so its more generally useful. Thanks, Kevin __

[openstack-dev] Scheduler meeting minutes

Thanks everyone for a great meeting. Minutes: http://eavesdrop.openstack.org/meetings/scheduler/2013/scheduler.2013-10-15-15.01.html Minutes (text): http://eavesdrop.openstack.org/meetings/scheduler/2013/scheduler.2013-10-15-15.01.txt Log: http://eavesdrop.openstack.org/meetings/scheduler/2013

Re: [openstack-dev] [Hyper-V] Havana status

On 13 October 2013 00:19, Alessandro Pilotti wrote: > If you don't like any of the options that this already long thread is > providing, I'm absolutely open to discuss any constructive idea. But please, > let's get out of this awful mess. > > OpenStack is still a young project. Let's make sure th

[openstack-dev] Hyper-V meeting Minutes

Hi Everyone, Here are the minutes from today's hyper-v meeting. Minutes: http://eavesdrop.openstack.org/meetings/hyper_v/2013/hyper_v.2013-10-15-16.03.html Minutes (text): http://eavesdrop.openstack.org/meetings/hyper_v/2013/hyper_v.2013-10-15-16.03.txt Log: http://eavesdrop.

[openstack-dev] Keystone RC1 Bug Question 1209440

Hello, I have a generic question about the logic now available for LDAP users in association with bug 1209440. How do you associate a read-only LDAP user with a domain? LDAP users are not entered into the keystone user table so the only way I can see to associate a user with a domain is to give

Re: [openstack-dev] Keystone RC1 Bug Question 1209440

On Tue, Oct 15, 2013 at 12:05 PM, Miller, Mark M (EB SW Cloud - R&D - Corvallis) wrote: > Hello, > > I have a generic question about the logic now available for LDAP users in > association with bug 1209440. How do you associate a read-only LDAP user with > a domain? I suppose it depends on your

Re: [openstack-dev] [keystoneclient] self-signed keystone not accessible from other services

On Mon, Oct 14, 2013 at 7:20 PM, Jamie Lennox wrote: > On Mon, 2013-10-14 at 18:36 -0700, Bhuvan Arumugam wrote: > > Just making sure i'm not the only one facing this problem. > > https://bugs.launchpad.net/nova/+bug/1239894 > > Yep, we thought this may raise some issues but insecure by default wa

Re: [openstack-dev] [Hyper-V] Havana status

On Oct 15, 2013, at 19:18 , Duncan Thomas wrote: > On 13 October 2013 00:19, Alessandro Pilotti > wrote: > >> If you don't like any of the options that this already long thread is >> providing, I'm absolutely open to discuss any constructive idea. But please, >> let's get out of this awful m

Re: [openstack-dev] [Hyper-V] Havana status

On Oct 15, 2013, at 19:03 , Duncan Thomas wrote: > On 11 October 2013 20:51, Rochelle.Grober wrote: >> Proposed solution: >> >> There have been a couple of solutions proposed. I’m presenting a >> merged/hybrid solution that may work >> >> · Create a new repository for the extra driv

Re: [openstack-dev] [Hyper-V] Havana status

On Oct 15, 2013, at 18:59 , Matt Riedemann mailto:[email protected]>> wrote: Sorry to pile on, but: "this was not particularly the case for what our driver is concerned. As I already wrote, almost all the reviews so far have been related to unit tests or minor formal corrections." As was

Re: [openstack-dev] [keystoneclient] self-signed keystone not accessible from other services

On 10/15/2013 01:20 PM, Bhuvan Arumugam wrote: On Mon, Oct 14, 2013 at 7:20 PM, Jamie Lennox > wrote: On Mon, 2013-10-14 at 18:36 -0700, Bhuvan Arumugam wrote: > Just making sure i'm not the only one facing this problem. > https://bugs.launchpad.net/n

[openstack-dev] One question to the fakelibvirt in nova test

Hi, stackers, I have a question to followed code in nova/tests/virt/libvirt/test_libvirt.py. My question is, when will the 'import libvirt' success and the fake libvirt not used? try: import libvirt except ImportError: import nova.tests.virt.libvirt.fakelibvirt as libvirt libvirt

[openstack-dev] [Metrics] Working on affiliations details: Activity Board

Hi!, During the last days we've been improving the Activity Board [1] where you can find updated development activity and affiliation information. For this purpose, we have finally created (sorry for the delay u_u ) an affiliation file [2]. This is a csv file with the following information:

Re: [openstack-dev] One question to the fakelibvirt in nova test

I thought it will be used when use local environment for ./run_test.sh, but./run_test.sh -N will have several failure and seems not supported anymore. Thanks for any input/suggestions. --jyh > -Original Message- > From: Jiang, Yunhong [mailto:[email protected]] > Sent: Tuesday, Oc

Re: [openstack-dev] Hyper-V meeting Minutes

On 10/15/2013 12:52 PM, Peter Pouliot wrote: > Hi Everyone, > > > Here are the minutes from today’s hyper-v meeting. > > > > Minutes: > http://eavesdrop.openstack.org/meetings/hyper_v/2013/hyper_v.2013-10-15-16.03.html > > Minutes (text): > http://eavesdrop.openstack.org/meetings/hype

Re: [openstack-dev] [Ceilometer] Notifications from non-local exchanges

On 10/15/2013 12:28 PM, Neal, Phil wrote: > > >> -Original Message- >> From: Sandy Walsh [mailto:[email protected]] >> Sent: Thursday, October 10, 2013 6:20 PM >> To: [email protected] >> Subject: Re: [openstack-dev] [Ceilometer] Notifications from non-local >> e

Re: [openstack-dev] [infra] Meeting Tuesday October 15th at 19:00 UTC

On Mon, Oct 14, 2013 at 10:43 AM, Elizabeth Krumbach Joseph wrote: > The OpenStack Infrastructure (Infra) team is hosting our weekly > meeting tomorrow, Tuesday October 15th, at 19:00 UTC in > #openstack-meeting Meeting minutes and log: Minutes: http://eavesdrop.openstack.org/meetings/infra/201

Re: [openstack-dev] Hyper-V meeting Minutes

Hi Everyone, I've been following this conversation and weighing the different sides. This is a tricky issue but I think it is important to decouple further and extend our circle of trust. When nova started it was very easy to do feature development. As it has matured the pace has slowed. This

Re: [openstack-dev] [Metrics] Working on affiliations details: Activity Board

On 10/15/2013 08:07 PM, Daniel Izquierdo wrote: Hi!, During the last days we've been improving the Activity Board [1] where you can find updated development activity and affiliation information. For this purpose, we have finally created (sorry for the delay u_u ) an affiliation file [2]. Thi

Re: [openstack-dev] Hyper-V meeting Minutes

From: Vishvananda Ishaya [mailto:[email protected]] Hi Everyone, I've been following this conversation and weighing the different sides. This is a tricky issue but I think it is important to decouple further and extend our circle of trust. When nova started it was very easy to do

[openstack-dev] [oslo] icehouse summit session planning

I will be reviewing the summit session proposals starting some time Friday 18th of October. If you have any topics you would like covered, please submit the details by 10:00:00 AM UTC. Thanks, Doug ___ OpenStack-dev mailing list [email protected]

Re: [openstack-dev] Hyper-V meeting Minutes

On 16 October 2013 09:54, Vishvananda Ishaya wrote: > Hi Everyone, > > I've been following this conversation and weighing the different sides. This > is a tricky issue but I think it is important to decouple further and extend > our circle of trust. > > When nova started it was very easy to do f

[openstack-dev] [oslo] i18n Message improvements

As requested in the last Oslo meeting, I created a blueprint for further discussion on the i18n work in Icehouse here: https://blueprints.launchpad.net/oslo/+spec/i18n-messages There were some ideas from the meeting that I'm sure I wasn't quite fully understanding, so please take a look and let

[openstack-dev] [Heat] HOT Software configuration proposal

I've just written some proposals to address Heat's HOT software configuration needs, and I'd like to use this thread to get some feedback: https://wiki.openstack.org/wiki/Heat/Blueprints/hot-software-config https://wiki.openstack.org/wiki/Heat/Blueprints/native-tools-bootstrap-config Please read t

[openstack-dev] [Keystone] stabilizing internal APIs

Hi Fellow Developers (and those who interface with keystone at the code level), I wanted to reach out to the ML and see what the opinions were about starting to stabilize the internal APIs (wherever possible) for the keystone project (I would also like to see similar work done in the other fully i

Re: [openstack-dev] Hyper-V meeting Minutes

On 2013-10-15 17:02, Robert Collins wrote: On 16 October 2013 09:54, Vishvananda Ishaya wrote: Hi Everyone, I've been following this conversation and weighing the different sides. This is a tricky issue but I think it is important to decouple further and extend our circle of trust. When no

Re: [openstack-dev] [Heat] Plugin packaging

Hi Sam, We wrote a Heat resource plugin as well [1] The trick to getting heat to auto-discover a module is to install it to the /usr/lib/heat (or possibly, but unlikely, /usr/lib64/heat) directory. I have found that the setuptools incantation: sudo python setup.py install --install-purelib=/usr

Re: [openstack-dev] [Keystone] stabilizing internal APIs

On Tue, Oct 15, 2013 at 6:05 PM, Morgan Fainberg wrote: > Hi Fellow Developers (and those who interface with keystone at the code > level), > > I wanted to reach out to the ML and see what the opinions were about > starting to stabilize the internal APIs (wherever possible) for the keystone > proj

Re: [openstack-dev] Hyper-V meeting Minutes

On 10/15/2013 04:54 PM, Vishvananda Ishaya wrote: Hi Everyone, I've been following this conversation and weighing the different sides. This is a tricky issue but I think it is important to decouple further and extend our circle of trust. When nova started it was very easy to do feature develo

[openstack-dev] [Heat] Meeting agenda for Wed Oct 16th at 2000 UTC

The Heat team holds a weekly meeting in #openstack-meeting, see https://wiki.openstack.org/wiki/Meetings/HeatAgenda for more details The next meeting is on Wed Oct 16th at 2000 UTC Current topics for discussion: * Review last week's actions * Havana release status * https://wiki.openstack.org/wi

[openstack-dev] [TripleO] Bug triage for TripleO - all ATC's please read.

Hey everyone, during the meeting today we observed folk who are active contributors were filing bugs without triaging them. Triage is a team responsibility : we need to triage bugs that folk who aren't familiar with TripleO file, but for bugs *we* file, it just makes work for someone else on the t

Re: [openstack-dev] Hyper-V meeting Minutes

On 10/15/2013 08:36 PM, Sean Dague wrote: > On 10/15/2013 04:54 PM, Vishvananda Ishaya wrote: >> Hi Everyone, >> >> I've been following this conversation and weighing the different >> sides. This is a tricky issue but I think it is important to decouple >> further and extend our circle of trust.

Re: [openstack-dev] [Metrics] Working on affiliations details: Activity Board

Thank you Daniel. On 10/15/2013 11:07 AM, Daniel Izquierdo wrote: > ps: not sure if it's a good idea to resend this to the general list > without the topic [metrics] nah, I don't think it's needed. > http://activity.openstack.org/dash/browser/data/affs/openstack-community-affs.csv This is usefu

Re: [openstack-dev] [Keystone] stabilizing internal APIs

On Tue, Oct 15, 2013 at 7:05 PM, Morgan Fainberg wrote: > Hi Fellow Developers (and those who interface with keystone at the code > level), > > I wanted to reach out to the ML and see what the opinions were about > starting to stabilize the internal APIs (wherever possible) for the > keystone pro

Re: [openstack-dev] [Heat] Plugin packaging

On 15/10/13 16:05 -0700, Tim Smith wrote: Hi Sam, We wrote a Heat resource plugin as well [1] The trick to getting heat to auto-discover a module is to install it to the /usr/lib/heat (or possibly, but unlikely, /usr/lib64/heat) directory. I have found that the setuptools incantation: sudo py

[openstack-dev] [TripleO] Reviews: tweaking priorities, and continual-deployment approvals

Hi, during the TripleO meeting today we had two distinct discussions about reviews. Firstly, our stats have been slipping: http://russellbryant.net/openstack-stats/tripleo-openreviews.html Stats since the last revision without -1 or -2 (ignoring jenkins): Average wait time: 2 days, 16 hours, 18

[openstack-dev] [TripleO] Retrospective up

https://wiki.openstack.org/wiki/TripleO/TripleOCloud/MVP1and2Retrospective If you're a TripleO contributor, please take the time to eyeball it - thanks! -Rob -- Robert Collins Distinguished Technologist HP Converged Cloud ___ OpenStack-dev mailing l

Re: [openstack-dev] [Keystone] stabilizing internal APIs

On Tue, Oct 15, 2013 at 5:05 PM, Doug Hellmann wrote: > > > Making updates easier would be nice, and the abstract base class work > should help with that. On the other hand, as a deployer who has had to > rewrite our custom integration a few times in the past 6 months or so, I > would also welcome

Re: [openstack-dev] [Keystone] stabilizing internal APIs

I think everyone will have opinions :). I suggest proving it in keystone and then bringing in a larger audience; we've had discussions about graceful evolution for some time now but little concrete action - I think because we're too ambitious, and the costs that result are perceived to be too high.

Re: [openstack-dev] [Heat] HOT Software configuration proposal

Steve Baker wrote on 10/15/2013 06:48:53 PM: > From: Steve Baker > To: [email protected], > Date: 10/15/2013 06:51 PM > Subject: [openstack-dev] [Heat] HOT Software configuration proposal > > I've just written some proposals to address Heat's HOT software > configuration needs

Re: [openstack-dev] Hyper-V meeting Minutes

Monty Taylor wrote: On 10/15/2013 08:36 PM, Sean Dague wrote: > On 10/15/2013 04:54 PM, Vishvananda Ishaya wrote: >> Hi Everyone, >> >> I've been following this conversation and weighing the different >> sides. This is a tricky issue but I think it is important to decouple >> further a

Re: [openstack-dev] [Heat] HOT Software configuration proposal

On 10/16/2013 02:21 PM, Mike Spreitzer wrote: > Steve Baker wrote on 10/15/2013 06:48:53 PM: > > > From: Steve Baker > > To: [email protected], > > Date: 10/15/2013 06:51 PM > > Subject: [openstack-dev] [Heat] HOT Software configuration proposal > > > > I've just written some prop

Re: [openstack-dev] Hyper-V meeting Minutes

> The last thing that OpenStack needs ANY more help with is velocity. I > mean, let's be serious - we land WAY more patches in a day than is > even close to sane. Thanks for saying this -- it doesn't get said enough. I find it totally amazing that we're merging 34 changes in a day (yesterday) whic

[openstack-dev] How does the libvirt domain XML get created?

Hello everyone, I'm trying to figure out how "" makes it into the libvirt domain XML when creating a new instance. I see where much of the content of the XML is created by the libvirt driver under nova/nova/virt/libvirt. However, I am unable to find where this makes it in there. Could someon

Re: [openstack-dev] How does the libvirt domain XML get created?

Hi Clark, I'm not familiar with nova, as usual, you can use 'virsh dumpxml ' to show domain XML configuration, I assume you have installed libvirt-client rpm package, or if you successfully defined a domain then you also may find its XML configuration under the /etc/libvirt/qemu/.xml, I hope it's h

Re: [openstack-dev] [qa] Update: Nova API List for Missing Tempest Tests

Hi, Matthew Thank you very much for your reply. > I'm glad that others have an interest in this topic. I've started an etherpad > for that discussion here: > > https://etherpad.openstack.org/p/icehouse-summit-qa-coverage-tooling > > Right now it's a very rough outline, without much on it. I'm pl

Re: [openstack-dev] How does the libvirt domain XML get created?

On Wed, Oct 16, 2013 at 2:08 PM, Clark Laughlin wrote: > Hello everyone, > > I'm trying to figure out how " heads='1'/>" makes it into the libvirt domain XML when creating a new > instance. I see where much of the content of the XML is created by the > libvirt driver under nova/nova/virt/libvir

Re: [openstack-dev] How does the libvirt domain XML get created?

I can see in config.py where VNC gets added (the element), but I can't find any place where a element gets added. In fact, I've grepped the entire nova tree for "cirrus" or "video" and can only find it here: ./nova/tests/virt/libvirt/fakelibvirt.py - Clark L On Oct 15, 2013, at 10:58 PM, M

[openstack-dev] problem fetching volume details in snapshot creation

hi, I am implementing a driver for cinder services and I am stuck with a problem in creation of snapshot , I have a need to fetch the volume details in snapshot creation. I am using Openstack-Grizzly I am trying to use this line of code def create_snapshot(self, snapshot_ref): ..

Re: [openstack-dev] [novaclient]should administrator can see all servers of all tenants by default?

--all-tenants would only be turned on if --tenant was specified, not a general default. Do you see that causing any problems for non trivial clouds? Chris On Tue, Oct 15, 2013 at 7:26 PM, Robert Collins wrote: > Please don't invert the bug though: if --all-tenants becomes the > default nova ser

Re: [openstack-dev] [novaclient]should administrator can see all servers of all tenants by default?

On Tue, Oct 15, 2013 at 9:34 PM, Lingxian Kong wrote: > Have there been any changes in V3 now? > > > I'm currently having a look at it. There's a bit other general breakage with all_tenants in there that should be fixed first. Chris ___ OpenStack-dev m

Re: [openstack-dev] [Heat] HOT Software configuration proposal

The threading in the archive includes this discussion under the "HOT Software orchestration proposal for workflows" heading, and the overall ordering in the archive looks very mixed up to me. I am going to reply here, hoping that the new subject line will be subject to less strange ordering in

Re: [openstack-dev] [novaclient]should administrator can see all servers of all tenants by default?

I think that would be fine: --tenant FOO implying 'show me results from FOO if I have access to that' makes total sense to me. On 16 October 2013 17:52, Christopher Yeoh wrote: > > --all-tenants would only be turned on if --tenant was specified, not a > general default. Do you see that causing an

Re: [openstack-dev] [Openstack] problem fetching volume details in snapshot creation

Hi DInakar, Please use volume_name, volume_size,etc. These are volume related parameters frequently used in snapshots. You can always do *dir* to get any specific values you need. Best Regards, Swapnil On Wed, Oct 16, 2013 at 10:11 AM, Dinakar Gorti Maruti < [email protected]> wrote: > h

[openstack-dev] [Glance] Team Meeting Reminder

Hi Glance folks, There will be a team meeting this week on Thursday at 20:00 UTC in #openstack-meeting-alt. That is, in your timezone: http://www.timeanddate.com/worldclock/fixedtime.html?msg=Glance+Meeting&iso=20131017T20&ah=1 The agenda is posted here https://etherpad.openstack.org/p/glance-tea

Re: [openstack-dev] [Openstack] problem fetching volume details in snapshot creation

Hi Swapnil, I had tried it before , it is returning a string "volume" followed by volume id Thanks Dinakar On Wed, Oct 16, 2013 at 10:31 AM, Swapnil Kulkarni < [email protected]> wrote: > Hi DInakar, > > Please use volume_name, volume_size,etc. These are volume rela

Re: [openstack-dev] Hyper-V meeting Minutes

On Oct 16, 2013, at 02:36 , Sean Dague mailto:[email protected]>> wrote: On 10/15/2013 04:54 PM, Vishvananda Ishaya wrote: Hi Everyone, I've been following this conversation and weighing the different sides. This is a tricky issue but I think it is important to decouple further and extend our

Re: [openstack-dev] [Openstack] problem fetching volume details in snapshot creation

display_name parameter of volume On Wed, Oct 16, 2013 at 10:55 AM, Swapnil Kulkarni < [email protected]> wrote: > What exact parameters are you looking for? > > > > On Wed, Oct 16, 2013 at 10:48 AM, Dinakar Gorti Maruti < > [email protected]> wrote: > >> Hi Swapnil, >> >>

Re: [openstack-dev] [Openstack] problem fetching volume details in snapshot creation

I think snapshot[volume_name] is what you are looking for, pls see below link for ref. https://github.com/openstack/cinder/blob/stable/grizzly/cinder/volume/drivers/lvm.py#L233 Best Regards, Swapnil On Wed, Oct 16, 2013 at 10:57 AM, Dinakar Gorti Maruti < [email protected]> wrote: > displ

Re: [openstack-dev] [Openstack] problem fetching volume details in snapshot creation

What exact parameters are you looking for? On Wed, Oct 16, 2013 at 10:48 AM, Dinakar Gorti Maruti < [email protected]> wrote: > Hi Swapnil, > > I had tried it before , it is returning a string "volume" > followed by volume id > > Thanks > Dinakar > > > On Wed, Oct 16, 2013

Re: [openstack-dev] [Openstack] problem fetching volume details in snapshot creation

Correcting the typo, snapshot_ref['volume_name'] in your case. On Wed, Oct 16, 2013 at 10:59 AM, Swapnil Kulkarni < [email protected]> wrote: > I think snapshot[volume_name] is what you are looking for, pls see below > link for ref. > > > https://github.com/openstack/cinder/blob/stab

Re: [openstack-dev] [Openstack] problem fetching volume details in snapshot creation

check Snapshot class , that is the one passed as snapshot_ref https://github.com/openstack/cinder/blob/stable/grizzly/cinder/db/sqlalchemy/models.py On Wed, Oct 16, 2013 at 11:02 AM, Swapnil Kulkarni < [email protected]> wrote: > Correcting the typo, snapshot_ref['volume_name'] in

Re: [openstack-dev] Hyper-V meeting Minutes

Hi Sean, I'm going to top post because my response is general. I totally agree that we need people that understand the code base and we should encourage new people to be cross-functional. I guess my main issue is with how we get there. I believe in encouragment over punishment. In my mind givin

Re: [openstack-dev] Hyper-V meeting Minutes

On Oct 16, 2013, at 05:48 , Dan Smith mailto:[email protected]>> wrote: The last thing that OpenStack needs ANY more help with is velocity. I mean, let's be serious - we land WAY more patches in a day than is even close to sane. Thanks for saying this -- it doesn't get said enough. I find it

Re: [openstack-dev] Scheduler meeting and Icehouse Summit

Hi, I agree with Phil. This has been on the agenda of the scheduling meetings for over a month now. Thanks Gary On 10/15/13 2:40 PM, "Day, Phil" wrote: >Hi Alex, > >My understanding is that the 17th is the deadline and that Russell needs >to be planning the sessions from that point onwards. If