Re: [openstack-dev] [climate][cafe] Climate and Cafe teams meeting

OK for me too, at the condition the meeting will last at max one hour (till 0700 UTC). -Sylvain 2014/1/14 Dina Belova > Ok for me :) > > > On Tue, Jan 14, 2014 at 9:19 AM, Sergey Lukjanov > wrote: > >> It's ok for me. >> >> P.S. link to the event time - >> http://www.timeanddate.com/worldcloc

Re: [openstack-dev] [climate][cafe] Climate and Cafe teams meeting

One more thing, we can meet up on #openstack-climate (logging available), or we can take a room in #openstack-meeting for starting a formal meeting and get minutes. Both are convenient for me, but with a preference for #openstack-climate. -Sylvain 2014/1/14 Sylvain Bauza > OK for me too, at t

Re: [openstack-dev] [climate][cafe] Climate and Cafe teams meeting

+1 for #openstack-climate Thanks :) On Tue, Jan 14, 2014 at 12:19 PM, Sylvain Bauza wrote: > One more thing, we can meet up on #openstack-climate (logging available), > or we can take a room in #openstack-meeting for starting a formal meeting > and get minutes. > > Both are convenient for me, b

Re: [openstack-dev] [nova] api schema validation pattern changes

On Tue, Jan 14, 2014 at 1:12 PM, Jay Pipes wrote: > On Tue, 2014-01-14 at 11:45 +0800, Christopher Yeoh wrote: > > On Tue, Jan 14, 2014 at 10:59 AM, Jay Pipes > > wrote: > > > > We don't need API extensions and they make our Compute API > > laughably complex and cumbersome. We sh

[openstack-dev] [Climate] 0.1 status meeting

Hi team, As agreed during our last meeting, we need to discuss on the progression before code freeze next Tuesday. I could propose tomorrow Wed 15 1000 UTC on #openstack-climate. +1/-1 to this, please. -Sylvain ___ OpenStack-dev mailing list OpenSt

Re: [openstack-dev] [Climate] 0.1 status meeting

+1 On Tue, Jan 14, 2014 at 12:44 PM, Sylvain Bauza wrote: > Hi team, > > As agreed during our last meeting, we need to discuss on the progression > before code freeze next Tuesday. > > I could propose tomorrow Wed 15 1000 UTC on #openstack-climate. > +1/-1 to this, please. > > -Sylvain > > _

[openstack-dev] [OpenStack-dev] [Trove] Implementing unit-tests and int-tests for heat based instance

Hi, I am writing this mail to shed some light on the implementation of tests for heat based instance creation. I have implemented unit tests and int-tests for the purpose. These tests are needed in trove because there is no criteria for testing the creation of instance using heat or any template

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

On 13/01/14 12:07 -0500, Doug Hellmann wrote: [.] I spent some time trying to think through how we could improve the update script for [1], and I'm stumped on how to figure out *accurately* what state the project repositories are in today. We can't just compute the hash of the m

Re: [openstack-dev] [Climate] 0.1 status meeting

+1 Nikolay Starodubtsev Software Engineer Mirantis Inc. Skype: dark_harlequine1 2014/1/14 Dina Belova > +1 > > > On Tue, Jan 14, 2014 at 12:44 PM, Sylvain Bauza wrote: > >> Hi team, >> >> As agreed during our last meeting, we need to discuss on the progression >> before code freeze next

Re: [openstack-dev] [Climate] 0.1 status meeting

lgtm On Tue, Jan 14, 2014 at 1:26 PM, Nikolay Starodubtsev < nstarodubt...@mirantis.com> wrote: > +1 > > > > Nikolay Starodubtsev > > Software Engineer > > Mirantis Inc. > > > Skype: dark_harlequine1 > > > 2014/1/14 Dina Belova > >> +1 >> >> >> On Tue, Jan 14, 2014 at 12:44 PM, Sylvain Bauza >

Re: [openstack-dev] Meeting time congestion

Matthias Runge wrote: > On 01/13/2014 09:33 PM, Lyle, David wrote: >> With all the warranted meeting time shuffling that has been happening >> recently, and the addition of so many projects and sub-teams, the >> meeting calendar for #openstack-meeting and #openstack-meeting-alt >> [1] is relatively

Re: [openstack-dev] [OpenStack-dev] [Trove] Implementing unit-tests and int-tests for heat based instance

Goodday, Shalini Khandelwal. You brought really good topic. I'd like to make few things clear: 1. https://bugs.launchpad.net/trove/+bug/1267945 there is already registred bug, even before your BP. 2. I see problem in proposed test coverage, since BP is telling us, that the main idea is to improve

Re: [openstack-dev] [nova] [rfc] drop XML from v3 API entirely

On Mon, Jan 13, 2014 at 10:38 PM, Sean Dague wrote: > I know we've been here before, but I want to raise this again while there > is still time left in icehouse. > > I would like to propose that the Nova v3 API removes the XML payload > entirely. It adds complexity to the Nova code, and it requir

Re: [openstack-dev] [nova] [rfc] drop XML from v3 API entirely

+1 for drop xml. But if we can't drop it, can we think about use XMLDictSerializer instead of XmlTemplate? We spend a lot of time to maintain XmlTemplate, and it make xml format inconsistent(some of resouce's attribute is output as xml sub-element, some of them is output as xml element's attribu

Re: [openstack-dev] [qa] negative test generation and testscenarios

Hi Robert, https://review.openstack.org/#/c/64733 is updated and is using testscenarios now. I was wondering if it would make sense to use a decorator instead of a class attribute to mark a test case for a certain test scenario, like: @TestCaseWithScenario(_scenarios1) def test_demo(self)

Re: [openstack-dev] Meeting time congestion

I think that in case of adding additional meeting rooms, we'll need to avoid disparity between them in names. For example, currently we have a lot of folks in #os-meeting and not so many in #os-meeting-alt, if we'll have #os-meeting-alt-2 then we'll have even less folks there and it'll be the same

Re: [openstack-dev] [nova] [rfc] drop XML from v3 API entirely

Hi, 2014/1/14 Alex Xu : > +1 for drop xml. But if we can't drop it, can we think about use > XMLDictSerializer instead of XmlTemplate? We spend a lot of time to maintain > XmlTemplate, and it make xml > format inconsistent(some of resouce's attribute is output as xml > sub-element, some of them is

Re: [openstack-dev] [nova] [rfc] drop XML from v3 API entirely

On 01/14/2014 05:17 AM, Christopher Yeoh wrote: > On Mon, Jan 13, 2014 at 10:38 PM, Sean Dague > wrote: > > I know we've been here before, but I want to raise this again while > there is still time left in icehouse. > > I would like to propose that the Nova v3

Re: [openstack-dev] [infra] javascript templating library choice for status pages

On 01/13/2014 04:28 PM, Michael Krotscheck wrote: > On 01/13/2014 01:12 PM, Sean Dague wrote: >> >> Well, as an expert in the area, particular recommendations would be >> appreciated. I don't feel like we necessarily need one answer, but it >> would be nice knock some of the options off the table.

Re: [openstack-dev] [nova] api schema validation pattern changes

On 01/14/2014 12:12 AM, Jay Pipes wrote: > On Tue, 2014-01-14 at 11:45 +0800, Christopher Yeoh wrote: >> On Tue, Jan 14, 2014 at 10:59 AM, Jay Pipes >> wrote: >> >> We don't need API extensions and they make our Compute API >> laughably complex and cumbersome. We should di

[openstack-dev] writing comments as complete sentences

Ned Batchelder had an interesting post a few days ago about why code comments should be written as complete sentences, rather than fragments. The main point is that with an unterminated phrase or sentence fragment it isn't always clear that the thought has been completed (i.e., maybe the full comme

[openstack-dev] Pre-caching images on nova-compute

Hello everyone,my name is Anastasios Andronidis, I am a Technical student at CERN and I was working on a project that helped CMS experiment to pre-cache images on nova-compute nodes. With the help of my supervisor (Olivier Chaze) we made a blog post[1] on how this system works and we would reall

Re: [openstack-dev] [oslo] need input on new config option for logging translations

On Mon, Jan 13, 2014 at 5:43 PM, Luis A. Garcia wrote: > On 1/13/2014 1:47 PM, Doug Hellmann wrote: > >> There's a review in Oslo to provide a configuration option to turn on >> the ability to log in a second language by specifying the locale >> (https://review.openstack.org/#/c/62508/). >> >> Giv

Re: [openstack-dev] writing comments as complete sentences

On Tue, 2014-01-14 at 08:01 -0500, Doug Hellmann wrote: > Ned Batchelder had an interesting post a few days ago about why code > comments should be written as complete sentences, rather than > fragments. The main point is that with an unterminated phrase or > sentence fragment it isn't always clear

Re: [openstack-dev] [wsme] Undefined attributes in WSME

On Mon, Jan 13, 2014 at 9:36 PM, Jamie Lennox wrote: > On Mon, 2014-01-13 at 10:05 -0500, Doug Hellmann wrote: > > > > > > > > > > On Sun, Jan 12, 2014 at 6:33 PM, Jamie Lennox > > wrote: > > On Fri, 2014-01-10 at 10:23 -0500, Doug Hellmann wrote: > > > > > > > > >

Re: [openstack-dev] [wsme] Undefined attributes in WSME

On Mon, Jan 13, 2014 at 9:52 PM, Kenichi Oomichi wrote: > > Hi Doug, > > > -Original Message- > > From: Doug Hellmann [mailto:doug.hellm...@dreamhost.com] > > Sent: Tuesday, January 14, 2014 12:07 AM > > To: OpenStack Development Mailing List (not for usage questions) > > Subject: Re: [ope

[openstack-dev] Hyper-V Meeting: Cancelled for this week.

Hi Everyone, I will be cancelling the Hyper- V meeting today.Too many key individuals are unable to attend. We will resume next week. p Peter J. Pouliot CISSP Sr. SDET OpenStack Microsoft New England Research & Development Center 1 Memorial Drive Cambridge, MA 02142 P: 1.(857).4536436 E: p

Re: [openstack-dev] [nova] api schema validation pattern changes

On Tue, Jan 14, 2014 at 3:36 AM, Christopher Yeoh wrote: > On Tue, Jan 14, 2014 at 1:12 PM, Jay Pipes wrote: > >> On Tue, 2014-01-14 at 11:45 +0800, Christopher Yeoh wrote: >> > On Tue, Jan 14, 2014 at 10:59 AM, Jay Pipes >> > wrote: >> > >> > We don't need API extensions and they make

[openstack-dev] [ironic] some notes on ironic functional testing

Hello, We (agordeev and vkozhukalov) had a discussion about functional testing flow described here https://etherpad.openstack.org/p/IronicDevstackTesting.From our perspective it has some non-critical, but still notable flaws. If you ask me, it looks a bit strange to create testing networks and VMs

Re: [openstack-dev] [neutron] [third-party-testing] Sharing information

Thanks for sending this note Mohammad. I am all in favor of another 3rd party testing meeting on IRC. How about if we shoot for tomorrow, Wednesday the 15, at 2200 UTC? Please ack if that works for everyone. Thanks, Kyle On Jan 13, 2014, at 5:08 PM, Mohammad Banikazemi wrote: > Hi everybody, >

Re: [openstack-dev] [heat] Sofware Config progress

On 01/14/2014 12:23 AM, Prasad Vellanki wrote: On Thu, Jan 9, 2014 at 6:14 AM, Steven Dake > wrote: that Steve Thanks for detailed email. Apologize for the delayed response but we have been thinking about how does software config fit into configuring network an

Re: [openstack-dev] [Nova] Detect changes in object model

> Hi Dan, are you going to cook a patch to expand the base class? Or we can do > that ourselves? Yeah, I'll try to get to that today. --Dan ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/lis

Re: [openstack-dev] [OpenStack][Nova][Cold Migration] What about enable cold migration with taraget host

hi Jay: Could you send me the relational bp or bug reference if you have proposed? Thanks very much! and by the way, is the code of the HA service you have implemented open source? 2014/1/13 Jay Lau > Thanks Russell, will add this to V3 api ad leave V2 API as it is. > > Regards, > > Jay > > >

Re: [openstack-dev] [neutron] [third-party-testing] Sharing information

I like it and I am in favor. Some of us, will be in Montreal attending the sprint tempest session. Hopefully we can all take it from there. Edgar > On Jan 14, 2014, at 6:31 AM, Kyle Mestery wrote: > > Thanks for sending this note Mohammad. I am all in favor of another > 3rd party testing mee

Re: [openstack-dev] Pre-caching images on nova-compute

hi Anastasios: please check the url, can't open it on my brower. maybe you could move it to google doc? 2014/1/14 Anastasis Andronidis > Hello everyone, > > my name is Anastasios Andronidis, I am a Technical student at CERN and I > was working on a project that helped CMS experiment to pre-cac

[openstack-dev] centralized notifications?

Is there any project or proposed project for centralizing notifications from openstack services to alert tenants when things go wrong (or right)? Say, for example, a nova instance failed to finish the build process, and the customer wants an email alert when that happens, or a trove database fa

Re: [openstack-dev] [Neutron] Availability of external testing logs

Can we get the -1 from Tail-F cleared from this review? https://review.openstack.org/#/c/56184/17 -- Sean M. Collins ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [OpenStack][Nova][Cold Migration] What about enable cold migration with taraget host

The bug was filed: https://bugs.launchpad.net/nova/+bug/1268622 The HA service was still under development and not open sourced. Thanks, Jay 2014/1/14 Lingxian Kong > hi Jay: > > Could you send me the relational bp or bug reference if you have proposed? > Thanks very much! > > and by the wa

Re: [openstack-dev] centralized notifications?

On Tue, Jan 14 2014, Greg Hill wrote: > Is there any project or proposed project for centralizing notifications from > openstack services to alert tenants when things go wrong (or right)? Say, > for example, a nova instance failed to finish the build process, and the > customer wants an email aler

Re: [openstack-dev] Pre-caching images on nova-compute

Hello, here[1] is a google doc link:Cheers,Anastasis[1] https://docs.google.com/document/d/1mWWSyftZYXxfXKzOBVeVma8KJbQRmYNPnns3oixHVMk/edit?usp=sharing Date: Tue, 14 Jan 2014 23:03:47 +0800 From: anlin.k...@gmail.com To: openstack-dev@lists.openstack.org Subject: Re: [openstack-dev] Pre-caching

Re: [openstack-dev] [Neturon][CI] Embrane CI is attacking gerrit

Ivar, can you contact Jeremy Stanley (fungi on Freenode, I believe) to get the contact details for your Gerrit account updated? Thanks. Just in case you missed it: http://lists.openstack.org/pipermail/openstack-dev/2014-January/024222.html -Ben On 2014-01-13 17:48, Ivar Lazzaro wrote: Hi N

Re: [openstack-dev] [neutron] [third-party-testing] Sharing information

Sounds good. Thanks. Mohammad From: Kyle Mestery To: Mohammad Banikazemi/Watson/IBM@IBMUS, Cc: "OpenStack Development Mailing List (not for usage questions)" Date: 01/14/2014 09:31 AM Subject:Re: [openstack-dev] [neutron] [third-party-testing] Sharing

Re: [openstack-dev] centralized notifications?

Hi Greg, The Marconi project (OpenStack Queueing and Notifications Service - https://wiki.openstack.org/wiki/Marconi) has a blueprint currently drafted to provide notifications to users. You can read the blueprint here: https://blueprints.launchpad.net/marconi/+spec/notifications Note the Marcon

Re: [openstack-dev] [neutron] [third-party-testing] Sharing information

Hi Kyle: I want to confirm about the meeting time(Wednesday the 15, at 2200 UTC). Some of colleagues are trying to setup the testing infra, they are very interested in this topic and would like to attend the meeting. 2014/1/14 Edgar Magana > I like it and I am in favor. > Some of us, will be i

Re: [openstack-dev] centralized notifications?

Thanks. Is there any more detail about what that is going to look like and how far along it might be? Greg On Jan 14, 2014, at 9:13 AM, Julien Danjou wrote: > On Tue, Jan 14 2014, Greg Hill wrote: > >> Is there any project or proposed project for centralizing notifications from >> openstack

Re: [openstack-dev] [nova] [rfc] drop XML from v3 API entirely

On 01/13/2014 10:38 PM, Sean Dague wrote: > I know we've been here before, but I want to raise this again while > there is still time left in icehouse. > > I would like to propose that the Nova v3 API removes the XML payload > entirely. It adds complexity to the Nova code, and it requires > duplic

Re: [openstack-dev] Pre-caching images on nova-compute

Thanks, Anastasios! 2014/1/14 Anastasis Andronidis > Hello, here[1] is a google doc link: > > Cheers, > Anastasis > > [1] > https://docs.google.com/document/d/1mWWSyftZYXxfXKzOBVeVma8KJbQRmYNPnns3oixHVMk/edit?usp=sharing > > -- > Date: Tue, 14 Jan 2014 23:03:47 +0800

Re: [openstack-dev] centralized notifications?

On Tue, Jan 14 2014, Greg Hill wrote: > Thanks. Is there any more detail about what that is going to look like > and how far along it might be? Nothing more yet. It's on the roadmap, but nobody had time so far to work on it, sorry. -- Julien Danjou ;; Free Software hacker ; independent consulta

[openstack-dev] [Nova] icehouse-2 code proposal deadline - EOD today

Greetings, We already have a long list of blueprints with code ready for review to be merged for the icehouse-2 milestone. There's an even longer list of blueprints that are not in "Needs Code Review" yet. If you want to land your blueprint in icehouse-2, please have all of the code proposed by

Re: [openstack-dev] [neutron] [third-party-testing] Sharing information

Hi, I will also be available for a meeting tomorrow. @Mohammad, we are still working on our 3rd party testing setup so do not take Midokura CI Bot votes too seriously yet. So far I have followed the links on the etherpad to have the jenkins+gerrit trigger plugin working with the current setup that'

Re: [openstack-dev] [nova] [rfc] drop XML from v3 API entirely

On 01/14/2014 10:37 AM, Thomas Goirand wrote: On 01/13/2014 10:38 PM, Sean Dague wrote: I know we've been here before, but I want to raise this again while there is still time left in icehouse. I would like to propose that the Nova v3 API removes the XML payload entirely. It adds complexity to

Re: [openstack-dev] [nova] [rfc] drop XML from v3 API entirely

On 01/14/2014 10:50 AM, David Kranz wrote: > On 01/14/2014 10:37 AM, Thomas Goirand wrote: >> On 01/13/2014 10:38 PM, Sean Dague wrote: >>> I know we've been here before, but I want to raise this again while >>> there is still time left in icehouse. >>> >>> I would like to propose that the Nova v3

Re: [openstack-dev] [oslo] need input on new config option for logging translations

On 1/14/2014 6:59 AM, Doug Hellmann wrote: [snip] I think the reason for this is simply user convenience. It's easier for the user to just set one of those log properties from the project.conf, and the "heavy lifting" such the creation of specific: Logger, LogHandler, LogFormatt

Re: [openstack-dev] [neutron] [third-party-testing] Sharing information

Given the Tempest Sprint in Montreal, I still think we should have this meeting on IRC. So, lets nail down the time as 2200 UTC on #openstack-meeting-alt for tomorrow. If you can’t make it, I’ll send the meeting logs out. Thanks, look forward to seeing people there tomorrow! Kyle On Jan 14, 2014

Re: [openstack-dev] [Neutron] Availability of external testing logs

On 01/14/2014 10:04 AM, Collins, Sean wrote: > Can we get the -1 from Tail-F cleared from this review? > > https://review.openstack.org/#/c/56184/17 > I thought we had confirmed that all Tail-F -1s prior to now had been cleared or only remained on abandoned or merged patches, I guess we missed on

Re: [openstack-dev] [nova] api schema validation pattern changes

Jay Pipes wrote: > On Tue, 2014-01-14 at 11:45 +0800, Christopher Yeoh wrote: >> On Tue, Jan 14, 2014 at 10:59 AM, Jay Pipes >> wrote: >> >> We don't need API extensions and they make our Compute API >> laughably complex and cumbersome. We should ditch entirely the >> concept

Re: [openstack-dev] [heat] Sofware Config progress

Hey Steve, it has taken me about a month to get enough time to go through this. Thanks for doing it, comments in-line. Excerpts from Steve Baker's message of 2013-12-13 15:46:48 -0800: > I've been working on a POC in heat for resources which perform software > configuration, with the aim of implem

Re: [openstack-dev] [neutron] [third-party-testing] Sharing information

On 01/14/2014 11:34 AM, Kyle Mestery wrote: > Given the Tempest Sprint in Montreal, I still think we should have this > meeting > on IRC. Shouldn't this be, "given OpenStack is an open project [0], this meeting will take place on irc, just like all our other meetings."? Thanks, Anita. [0] https:

[openstack-dev] [savanna] savannaclient v2 api

https://blueprints.launchpad.net/savanna/+spec/v2-api I've finished a review of the v1.0 and v1.1 APIs with an eye to making them more consistent and RESTful. Please use this thread to comment on my suggestions for v1.0 & v1.1, or to make further suggestions. Best, matt _

Re: [openstack-dev] [savanna] client release 0.4.1

On 01/13/2014 02:27 PM, Sergey Lukjanov wrote: Hi folks, I'm planning to release python-savannaclient Jan 14/15 due to the number of important fixes and improvements including, for example, basic impl of CLI. This changes are needed for updating savanna-dashboard, integration tests, for adding s

Re: [openstack-dev] [savanna] client release 0.4.1

Ok, looks like everything is ready now for pushing the tag, I'm planning to do it later today. On Tue, Jan 14, 2014 at 9:32 PM, Matthew Farrellee wrote: > On 01/13/2014 02:27 PM, Sergey Lukjanov wrote: > >> Hi folks, >> >> I'm planning to release python-savannaclient Jan 14/15 due to the number

Re: [openstack-dev] [heat] Sofware Config progress

Excerpts from Prasad Vellanki's message of 2014-01-13 23:23:15 -0800: > On Thu, Jan 9, 2014 at 6:14 AM, Steven Dake wrote: > > > that > > > Steve > Thanks for detailed email. Apologize for the delayed response but we have > been thinking about how does software config fit into configuring netwo

Re: [openstack-dev] [oslo] need input on new config option for logging translations

On Tue, Jan 14, 2014 at 11:27 AM, Luis A. Garcia wrote: > On 1/14/2014 6:59 AM, Doug Hellmann wrote: > >> >> [snip] >> >> >> I think the reason for this is simply user convenience. It's easier >> for the user to just set one of those log properties from the >> project.conf, and the "he

[openstack-dev] [oslo] dependency analysis for graduating more oslo libraries

I've spent some time over the past day or two looking at the dependencies between modules in the oslo incubator, trying to balance the desire to have a small number of libraries with themes that make sense and the need to eliminate circular dependencies. The results of all of this are posted to ht

Re: [openstack-dev] [TripleO] [Tuskar] Deployment Management section - Wireframes

Hi Jaromir, 2014/1/13 Jaromir Coufal > So what we can do at the moment (until there is some way to specify which > node to remove) is to inform user, which nodes were removed in the end... > at least. > > In the future, I'd like to enable user to have both ways available - just > decrease number

Re: [openstack-dev] [oslo] dependency analysis for graduating more oslo libraries

You mention some concerns with processutils on that wiki page that I was unaware of. I can't find bugs for them either. Do you have any pointers to what is being referred to there? Thanks, Michael On Wed, Jan 15, 2014 at 6:48 AM, Doug Hellmann wrote: > I've spent some time over the past day or t

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

In the release meeting today, Russell proposed that we at least include the hash of the HEAD when the merge is done, to indicate how far along the oslo changes are. More detail is obviously better. So, let's consider this as a new policy. Does anyone foresee issues with making this work? Doug

Re: [openstack-dev] [oslo] dependency analysis for graduating more oslo libraries

The notes are from the summit discussion, and I didn't open the bugs. I'll do that this week. Should I assign them to you? Doug On Tue, Jan 14, 2014 at 3:58 PM, Michael Still wrote: > You mention some concerns with processutils on that wiki page that I > was unaware of. I can't find bugs for t

[openstack-dev] [gantt] Sync up patches

All- As threatened, I've pushed 24 patches to sync up the gantt tree to recent changes to the nova tree. They're all linked in a dependency chain starting at: https://review.openstack.org/66717 It's be good if we can get those reviewed soon. -- Don Dugger "Censeo Toto nos in K

Re: [openstack-dev] Proposal for instance-level snapshots in Nova

* Vishvananda Ishaya wrote: > > On Jan 6, 2014, at 3:50 PM, Jon Bernard wrote: > > > Hello all, > > > > I would like to propose instance-level snapshots as a feature for > > inclusion in Nova. An initial draft of the more official proposal is > > here [1], blueprint is here [2]. > > > > In

Re: [openstack-dev] [gantt] Sync up patches

All- I want to clear up some confusion I'm seeing in the reviews of these syncup patches. These patches merely bring recent changes from the nova tree over to the gantt tree. There is no attempt to actually change the code for gantt, that is a separate task. Our first goal is to have the sch

Re: [openstack-dev] Proposal for instance-level snapshots in Nova

* Mark Washenberger wrote: > On Mon, Jan 6, 2014 at 3:50 PM, Jon Bernard wrote: > > > Hello all, > > > > I would like to propose instance-level snapshots as a feature for > > inclusion in Nova. An initial draft of the more official proposal is > > here [1], blueprint is here [2]. > > > > In a n

Re: [openstack-dev] Proposal for instance-level snapshots in Nova

* Christopher Yeoh wrote: > On Tue, Jan 7, 2014 at 7:50 AM, Jon Bernard wrote: > > > Hello all, > > > > I would like to propose instance-level snapshots as a feature for > > inclusion in Nova. An initial draft of the more official proposal is > > here [1], blueprint is here [2]. > > > > In a nu

Re: [openstack-dev] [oslo] dependency analysis for graduating more oslo libraries

On 2014-01-14 13:48, Doug Hellmann wrote: > I've spent some time over the past day or two looking at the dependencies > between modules in the oslo incubator, trying to balance the desire to have a > small number of libraries with themes that make sense and the need to > eliminate circular

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

On 2014-01-14 15:26, Doug Hellmann wrote: > In the release meeting today, Russell proposed that we at least include the > hash of the HEAD when the merge is done, to indicate how far along the oslo > changes are. More detail is obviously better. > > So, let's consider this as a new policy.

Re: [openstack-dev] [gantt] Sync up patches

Thanks Don for raising the point, I was about to send an email after finishing up to review. To me, it appears I have to give -1 when either : 1. Change is related to API documentation or WSGI framework. AIUI, Gantt will be plugged to Nova thanks to its RPC interface, it makes no sense to ship any

Re: [openstack-dev] [oslo] dependency analysis for graduating more oslo libraries

On Wed, Jan 15, 2014 at 8:28 AM, Doug Hellmann wrote: > The notes are from the summit discussion, and I didn't open the bugs. I'll > do that this week. Should I assign them to you? If you assign them to me I will take a look at them. Michael -- Rackspace Australia

Re: [openstack-dev] [oslo] dependency analysis for graduating more oslo libraries

On Wed, Jan 15, 2014 at 9:27 AM, Ben Nemec wrote: > It would be nice to get lockutils graduated to solve some of the issues > mentioned in the oslo.db section, but I believe we do have an outstanding > question regarding its behavior without lock_path being set. I think Clint > was on board with

Re: [openstack-dev] [Glance][All] Pecan migration strategies

Hi folks, I would vote for implementing the existing version, i.e, 2.0 instead of creating a new one. The reasons I consider are the following: 1. Introducing a new version of the API means making some changes to the specification. In the case of changing the major version those changes should

[openstack-dev] [Neutron] About ports backing floating IPs

TL;DR; I have been looking back at the API and found out that it's a bit weird how floating IPs are mapped to ports. This might or might not be an issue, and several things can be done about it. The rest of this post is a boring description of the problem and a possibly even more boring list of pot

Re: [openstack-dev] [Glance][All] Pecan migration strategies

On Fri, Jan 10, 2014 at 4:51 AM, Flavio Percoco wrote: > Greetings, > > More discussions around the adoption of Pecan. > > I'd like to know what is the feeling of other folks about migrating > existing APIs to Pecan as opposed to waiting for a new API version as > an excuse to migrate the API imp

Re: [openstack-dev] [Glance][All] Pecan migration strategies

This time, with content! On Fri, Jan 10, 2014 at 4:51 AM, Flavio Percoco wrote: > Greetings, > > More discussions around the adoption of Pecan. > > I'd like to know what is the feeling of other folks about migrating > existing APIs to Pecan as opposed to waiting for a new API version as > an ex

Re: [openstack-dev] Implementing VPNaas in Openstack Grizzly release

On Mon 13 Jan 2014 11:04:01 PM PST, Ashwini Babureddy wrote: > I have added all the configurations mentioned below in the mail but > getting the same error while executing the command Please move this thread to the General mailing list or the Operators list or https://ask.openstack.org. Reserve t

Re: [openstack-dev] [Neutron] About ports backing floating IPs

for all ports: user can change the device_id and device owner easily, it will cause mess in particularly for system ports, such as router interface and gateway ports, dhcp ports etc. dhcp port: there is not point of updating its security groups, and I don't know the effect when we update its Ip ad

Re: [openstack-dev] [Neutron] About ports backing floating IPs

Option 5: If the implementation works good, but its just a confusing ui, you could always change the code so it filters out the floating-ip ports from view. Make them a pure implementation detail that a user never sees. Kevin From: Salvatore Orlando [sorla...@ni

Re: [openstack-dev] [wsme] Undefined attributes in WSME

Hi Doug, > -Original Message- > From: Doug Hellmann [mailto:doug.hellm...@dreamhost.com] > Sent: Tuesday, January 14, 2014 11:10 PM > To: OpenStack Development Mailing List (not for usage questions) > Subject: Re: [openstack-dev] [wsme] Undefined attributes in WSME > > On Mon, Jan 13, 20

Re: [openstack-dev] [heat] Sofware Config progress

Steve I did not mean to have custom solution at all. In fact that would be terrible. I think Heat model of software config and deployment is really good. That allows configurators such as Chef, Puppet, Salt or Ansible to be plugged into it and all users need to write are modules for those. What

Re: [openstack-dev] [infra] Meeting Tuesday January 14th at 19:00 UTC

On Mon, Jan 13, 2014 at 7:18 PM, Elizabeth Krumbach Joseph wrote: > The OpenStack Infrastructure (Infra) team is hosting our weekly > meeting tomorrow, Tuesday January 14th, at 19:00 UTC in > #openstack-meeting Meeting minutes and log: Minutes: http://eavesdrop.openstack.org/meetings/infra/2014

Re: [openstack-dev] [ironic] [QA] some notes on ironic functional testing

Hi Alexander, Vladimir, First of all, thanks for working on testing Ironic! Functional testing is critical to our project, and I'm very happy you're looking into it. On Tue, Jan 14, 2014 at 6:28 AM, Alexander Gordeev wrote: > We (agordeev and vkozhukalov) had a discussion about functional testin

Re: [openstack-dev] [heat] Sofware Config progress

Excerpts from Prasad Vellanki's message of 2014-01-14 18:41:46 -0800: > Steve > > I did not mean to have custom solution at all. In fact that would be > terrible. I think Heat model of software config and deployment is really > good. That allows configurators such as Chef, Puppet, Salt or Ansible

Re: [openstack-dev] Proposal for instance-level snapshots in Nova

On Jan 14, 2014, at 2:10 PM, Jon Bernard wrote: > > >> As you’ve defined the feature so far, it seems like most of it could >> be implemented client side: >> >> * pause the instance >> * snapshot the instance >> * snapshot any attached volumes > > For the first milestone to offer crash-consi

[openstack-dev] What's the status about Instance Resource Quota now ??

Hi list, I find a page on wiki : https://wiki.openstack.org/wiki/InstanceResourceQuota It is said we can set CPU, disk IO and bandwidth consumption limit for instances But the blueprint page returns error, while the patch is abandoned in early last year. Anyone can help me to know the current s

[openstack-dev] [novalcient]Proposal for removing 'bash_completion'

Now, novaclient supports 'bash-completion' and 'bash_completion' commands at the same time, after I checked the commit history, I found that the '_add_bash_completion_subparser' function and 'do_bash_completion' function were added in at 2011/12/16 by Rick Harris, with the Change-Id: If882f7a822ef6

Re: [openstack-dev] [novalcient]Proposal for removing 'bash_completion'

Hello Lingxian, Actually I'm planning to remove both of them. I'm working on integration of argcomplete (https://github.com/kislyuk/argcomplete) library to openstack clients: https://review.openstack.org/#/c/65863/ https://review.openstack.org/#/c/65864/ https://review.openstack.org/#/c/65865/

Re: [openstack-dev] [TripleO] [Tuskar] Deployment Management section - Wireframes

Excerpts from Vitaly Kramskikh's message of 2014-01-14 12:35:43 -0800: > Hi Jaromir, > > 2014/1/13 Jaromir Coufal > > > So what we can do at the moment (until there is some way to specify which > > node to remove) is to inform user, which nodes were removed in the end... > > at least. > > > > In

[openstack-dev] Support for VMware vCenter Server in Ceilometer

Hi all, We have filed the following blueprint to extend Ceilometer support for VMware vCenter Server: https://blueprints.launchpad.net/ceilometer/+spec/vmware-vcenter-server/ We are moving ahead with the implementation and have provided the details about the architectural decisions in the wik