Re: [openstack-dev] [Nova] Future meeting times

+1, I would make the 14:00 meeting. I often have good intention of making the 21:00 meeting, but it's tough to work in around family life Sent from Samsung Mobile Original message From: Joe Gordon Date: To: OpenStack Development Mailing List Subject: Re: [openstack-dev] [

[openstack-dev] [Heat] [Trove] [Savanna] [Oslo] Unified Agents - what is the actual problem?

So I've seen a lot of really great discussion of the unified agents, and it has made me think a lot about the problem that we're trying to solve. I just wanted to reiterate that we should be trying to solve real problems and not get distracted by doing things "right" or even "better". I actually

Re: [openstack-dev] [Nova][VMware] Deploy from vCenter template

Hi Arnaud, It's really good to know that your team are proposing the vcenter driver with OVA+glance datastore backend support. Thanks for sharing the information. OVA would be a good choice which will benefit users by avoiding only use flat image limited from current driver. But in my opin

Re: [openstack-dev] Subject: [nova][vmware] VMwareAPI sub-team status 2013-12-08

Would it be possible that an additional core please take a look at https://review.openstack.org/#/c/51793/? Thanks Gary From: Shawn Hartsock mailto:harts...@acm.org>> Date: Wednesday, December 18, 2013 6:32 PM To: "OpenStack Development Mailing List (not for usage questions)" mailto:openstack-de

[openstack-dev] [swift][python-switfclient][oslo] bufferedhttp in glance and oslo

Hi, There has been few discussions/patches/reviews on pulling in the bufferedhttp.py (currently in use in swift) to python-swiftclient and even to oslo, so that we can leverage features like buffering http headers and use of 'expect: 100-continue' etc which is currently not suported by the httplib

Re: [openstack-dev] Diversity as a requirement for incubation

On 12/18/2013 12:34 PM, Doug Hellmann wrote: I have more of an issue with a project failing *after* becoming integrated than during incubation. That's why we have the incubation period to begin with. For the same reason, I'm leaning towards allowing projects into incubation without a very diverse

Re: [openstack-dev] [neutron] Re: [Blueprint vlan-aware-vms] VLAN aware VMs

Ian, Could you unlock your doc at https://docs.google.com/document/d/16DDJLYHxMmbCPO5LxW_kp610oj4goiic_oTakJiXjTs? It require a permission to read. Thanks Yi On 12/18/13, 4:20 AM, Ian Wells wrote: A Neutron network is analagous to a wire between ports. We can do almost everything with this wi

Re: [openstack-dev] [devstack]

Thank you Dean and Anne for your response. On Wed, Dec 18, 2013 at 8:27 PM, Dean Troyer wrote: > On Wed, Dec 18, 2013 at 8:23 AM, Anne Gentle < > annegen...@justwriteclick.com> wrote: > >> Also, Dean correct me if I'm wrong, but I don't believe devstack does a >> precise milestone release. To

Re: [openstack-dev] Diversity as a requirement for incubation

On Wed, Dec 18, 2013 at 2:40 AM, Thierry Carrez wrote: > I guess there are 3 options: > > 1. Require diversity for incubation, but find ways to bless or recommend > projects pre-incubation so that this diversity can actually be achieved > > 2. Do not require diversity for incubation, but require i

Re: [openstack-dev] [neutron] Re: [Blueprint vlan-aware-vms] VLAN aware VMs

Hi Ian. I can't see your proposal. Can you please make it public viewable? Some comments inlined below. On Wed, Dec 18, 2013 at 01:20:50PM +0100, Ian Wells wrote: > A Neutron network is analagous to a wire between ports. We can do almost > everything with this wire - we can pass both IP and

Re: [openstack-dev] Incubation Request for Barbican

On Tue, Dec 17, 2013 at 1:59 PM, Mike Perez wrote: > On Tue, Dec 17, 2013 at 11:44 AM, Jarret Raim > wrote: > >> On 12/13/13, 4:50 AM, "Thierry Carrez" wrote: >> >> >> >If you remove Jenkins and attach Paul Kehrer, jqxin2006 (Michael Xin), >> >Arash Ghoreyshi, Chad Lung and Steven Gonzales to R

Re: [openstack-dev] [heat] Nomination for heat-core

On 19/12/13 15:21 +1300, Steve Baker wrote: I would like to nominate Bartosz Górski to be a heat-core reviewer. His reviews to date have been valuable and his other contributions to the project have shown a sound understanding of how heat works. Here is his review history: https://review.opensta

Re: [openstack-dev] [heat] Nomination for heat-core

Excerpts from Steve Baker's message of 2013-12-18 18:21:46 -0800: > I would like to nominate Bartosz Górski to be a heat-core reviewer. His > reviews to date have been valuable and his other contributions to the > project have shown a sound understanding of how heat works. > > Here is his review h

Re: [openstack-dev] Adding DB migration items to the common review checklist

On 12/18/2013 02:14 PM, Brant Knudson wrote: Matt - Could a test be added that goes through the models and checks these things? Other projects could use this too. Here's an example of a test that checks if the tables are all InnoDB: http://git.openstack.org/cgit/openstack/nova/tree/nova/tests/d

Re: [openstack-dev] [neutron][policy] Policy-Rules discussions based on Dec.12 network policy meeting

Please have a look at the agenda for tomorrow at https://wiki.openstack.org/wiki/Meetings/Neutron_Group_Policy It would be great if we could at least close on the following two items tomorrow: 1. Converged model by allowing policies to have a destination group and a source gro

Re: [openstack-dev] [neutron][qa] test_network_basic_ops and the "FloatingIPChecker" control point

On 12/18/2013 10:21 PM, Brent Eagles wrote: Hi, Yair and I were discussing a change that I initiated and was incorporated into the test_network_basic_ops test. It was intended as a configuration control point for floating IP address assignments before actually testing connectivity. The question

Re: [openstack-dev] [heat] Nomination for heat-core

On 12/18/2013 07:21 PM, Steve Baker wrote: I would like to nominate Bartosz Górski to be a heat-core reviewer. His reviews to date have been valuable and his other contributions to the project have shown a sound understanding of how heat works. Here is his review history: https://review.openst

Re: [openstack-dev] [trove] My thoughts on the Unified Guest Agent

On 12/18/2013 05:57 PM, Tim Simpson wrote: python: consumes 12.5MB of virt memory and 4.3MB of resident memory. Very few Python only processes will take up such a small amount of virtual memory unless the authors are disciplined about not pulling in any dependencies at all and writing code in

Re: [openstack-dev] [Neutron][IPv6] Three SLAAC and DHCPv6 related blueprints

It is up to Sean to make the call, but I would love to see IBM team in the meeting. On Dec 18, 2013, at 7:09 PM, Xuhan Peng wrote: > Shixiong and guys, > > The sub team meeting is too early for china IBM folks to join although we > would like to participate the discussion very much. Any ch

Re: [openstack-dev] [Nova] [Ironic] Get power and temperature via IPMI

Hi, Alan, I think, for nova-scheduler it is better if we gather more information. And In today's DC, power and temperature are very important facts to considering. CPU/Memory utilization is not enough to describe nodes' status. Power/inlet temperature should be noticed. Best Wishes --fengqian

[openstack-dev] [neutron][qa] test_network_basic_ops and the "FloatingIPChecker" control point

Hi, Yair and I were discussing a change that I initiated and was incorporated into the test_network_basic_ops test. It was intended as a configuration control point for floating IP address assignments before actually testing connectivity. The question we were discussing was whether this check

Re: [openstack-dev] [Nova] [Ironic] Get power and temperature via IPMI

Hi, Devananda, I agree with you that new features should be towards Ironic. As you asked why use Ironic instead of lm-sensors, actually I just want to use IPMI instead of lm-sensors. I think it is reasonable to put the IPMI part into Ironic and we already did:). To get the sensors' information,

Re: [openstack-dev] [trove] datastore migration issues

There is the database migration for datastores. We should add a function to back fill the existing data with either a dummy data or set it to 'mysql' as that was the only possibility before data stores. On Dec 18, 2013 3:23 PM, "Greg Hill" wrote: > I've been working on fixing a bug related to m

[openstack-dev] [heat] Nomination for heat-core

I would like to nominate Bartosz Górski to be a heat-core reviewer. His reviews to date have been valuable and his other contributions to the project have shown a sound understanding of how heat works. Here is his review history: https://review.openstack.org/#/q/reviewer:bartosz.gorski%2540ntti3.c

[openstack-dev] [heat] Alternative time for the Heat/orchestration meeting

The Heat meeting is currently weekly on Wednesdays at 2000 UTC. This is not very friendly for contributors in some timezones, specifically Asia. In today's Heat meeting we decided to try having every second meeting at an alternate time. I've set up this poll to gather opinions on some (similar) ti

Re: [openstack-dev] [trove] My thoughts on the Unified Guest Agent

>> python: >> consumes 12.5MB of virt memory and 4.3MB of resident memory. Very few Python only processes will take up such a small amount of virtual memory unless the authors are disciplined about not pulling in any dependencies at all and writing code in a way that isn't necessarily idiomatic.

Re: [openstack-dev] [neutron][policy] Policy-Rules discussions based on Dec.12 network policy meeting

folks, sorry for the late input ... a few additional thoughts... > Hi Prasad, > > Thanks for the comments, please see responses inline. > > On Mon, Dec 16, 2013 at 2:11 PM, Prasad Vellanki > wrote: > > Hi > > Please see inline > > > > > > On Sun, Dec 15, 2013 at 8:49 AM, Stephen Wong

Re: [openstack-dev] [Neutron][IPv6] Three SLAAC and DHCPv6 related blueprints

Shixiong and guys, The sub team meeting is too early for china IBM folks to join although we would like to participate the discussion very much. Any chance to rotate the time so we can comment? Thanks, Xuhan On Thursday, December 19, 2013, Shixiong Shang wrote: > Hi, Ian: > > I agree with you o

[openstack-dev] [Neutron][lbaas] plugin driver

I was going through the latest common agent patch from Eugene. plugin-driver appears to be specific to driver provider, for example haproxy has a plugin driver (in addition to agent driver). How does this work with single common agent and many providers? Would they need to use a separate topic? Wh

Re: [openstack-dev] [Nova] Support for Pecan in Nova

So the short answer: as long as the api samples continue to generate normally I don't think it will. The long answer is more complicated. The V2 API documentation was generated and updated manually. We generate api samples for the documentation automatically but thats it. I've been trying to impro

Re: [openstack-dev] [neutron] [third-party-testing] Reminder: Meeting tomorrow

Wouldn't 2200 UTC be in about 20 mins? On Wed, Dec 18, 2013 at 3:32 PM, Itsuro ODA wrote: > Hi, > > It seems the meeting was not held on 2200 UTC on Wednesday (today). > > Do you mean 2200 UTC on Thursday ? > > Thanks. > > On Thu, 12 Dec 2013 11:43:03 -0600 > Kyle Mestery wrote: > > > Hi every

Re: [openstack-dev] [neutron] [third-party-testing] Reminder: Meeting tomorrow

Hi, It seems the meeting was not held on 2200 UTC on Wednesday (today). Do you mean 2200 UTC on Thursday ? Thanks. On Thu, 12 Dec 2013 11:43:03 -0600 Kyle Mestery wrote: > Hi everyone: > > We had a meeting around Neutron Third-Party testing today on IRC. > The logs are available here [1]. We

Re: [openstack-dev] [Heat] Neutron resources and hidden dependencies

On 18/12/13 05:21, Thomas Herve wrote: At the design summit we had a discussion[1] about redesigning Neutron resources to avoid the need for hidden dependencies (that is to say, dependencies which cannot be inferred from the template). Since then we've got close to fixing one of those issues[2

Re: [openstack-dev] [trove] My thoughts on the Unified Guest Agent

On 12/18/2013 12:27 PM, Tim Simpson wrote: Please provide proof of that assumption or at least a general hypothesis that we can test. I can't prove that the new agent will be larger as it doesn't exist yet. Since nothing was agreed upon anyway, I don't know how you came to that conclusion.

Re: [openstack-dev] [trove] Delivering datastore logs to customers

I think this is a good idea and I support it. In todays meeting [1] there were some questions, and I encourage them to get brought up here. My only question is in regard to the "tail" of a file we discussed in irc. After talking about it w/ other trovesters, I think it doesnt make sense to tail the

Re: [openstack-dev] Horizon and Tuskar-UI codebase merge

>From my experience, directly adding incubated projects to the main Horizon >codebase prior to graduation has been fraught with peril. That said, the >closer they can be together prior to the graduation merge, the better. I like the idea of these types of projects being under the OpenStack Dashb

Re: [openstack-dev] [Neutron] Neutron Tempest code sprint - 2nd week of January, Montreal, QC, Canada

Matt Trenish wins this round of spot Anita's typo to the -dev ml. 9am - 5pm, 8 hours of work (lunch in the middle) for 3 days Thanks Matt, Anita. On 12/18/2013 04:17 PM, Anita Kuno wrote: > Okay time for a recap. > > What: Neutron Tempest code sprint > Where: Montreal, QC, Canada > When: Januar

[openstack-dev] [trove] datastore migration issues

I've been working on fixing a bug related to migrating existing installations to the new datastore code: https://bugs.launchpad.net/trove/+bug/1259642 The basic gist is that existing instances won't have any data in the datastore_version_id field in the database unless we somehow populate that

Re: [openstack-dev] [Neutron] Neutron Tempest code sprint - 2nd week of January, Montreal, QC, Canada

Okay time for a recap. What: Neutron Tempest code sprint Where: Montreal, QC, Canada When: January 15, 16, 17 2014 Location: I am about to sign the contract for Salle du Parc at 3625 Parc avenue, a room in a residence of McGill University. Time: 9am - 5am I am expecting to see the following peopl

[openstack-dev] [neutron] [third-party-testing] Reminder: Meeting tomorrow

Just a reminder, we'll be meeting at 2200 UTC on #openstack-meeting-alt. We'll be looking at this etherpad [1] again, and continuing discussions from last week. Thanks! Kyle [1] https://etherpad.openstack.org/p/multi-node-neutron-tempest ___ OpenStack-

[openstack-dev] [trove] next two weekly meetings

We are canceling our next two weekly meetings. They occur on Dec 25 and Jan 1. See you all on the 8th for our next regularly scheduled trove meeting. ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailm

Re: [openstack-dev] [Neutron][ML2] Unit test coverage

I’ve run the tests again with `coverage report -m` to show the line-by-line numbers of statements that weren’t executed. (.venv)amir@dev:~/neutron$ git log HEAD --pretty=oneline | head -n 1 51bef83fecfd6ccf7bf1f9ba3d14bbab0c205949 Merge "Midonet plugin: Fix source NAT” fox -e cover neutron.test

Re: [openstack-dev] Adding DB migration items to the common review checklist

On 12/18/2013 2:11 PM, Dan Prince wrote: - Original Message - From: "Matt Riedemann" To: "OpenStack Development Mailing List (not for usage questions)" Sent: Wednesday, December 18, 2013 12:27:49 PM Subject: [openstack-dev] Adding DB migration items to the common review checklist

Re: [openstack-dev] Adding DB migration items to the common review checklist

On 12/18/2013 1:14 PM, Brant Knudson wrote: Matt - Could a test be added that goes through the models and checks these things? Other projects could use this too. Here's an example of a test that checks if the tables are all InnoDB: http://git.openstack.org/cgit/openstack/nova/tree/nova/tests/

Re: [openstack-dev] [Neutron][IPv6] Three SLAAC and DHCPv6 related blueprints

Hi, Ian: I agree with you on the point that the way we implement it should be app agnostic. In addition, it should cover both CLI and Dashboard, so the system behavior should be consistent to end users. The keywords is just one of the many ways to implement the concept. It is based on the real

[openstack-dev] [QA] Meeting Thursday December 19th at 17:00 UTC

Just a reminder that the weekly OpenStack QA team IRC meeting will be tomorrow, December 19th at 17:00 UTC in the #openstack-meeting channel. The meeting agenda can be found here: https://wiki.openstack.org/wiki/Meetings/QATeamMeeting Anyone is welcome to add an item to the agenda. -Matt Treinish

Re: [openstack-dev] Adding DB migration items to the common review checklist

- Original Message - > From: "Matt Riedemann" > To: "OpenStack Development Mailing List (not for usage questions)" > > Sent: Wednesday, December 18, 2013 12:27:49 PM > Subject: [openstack-dev] Adding DB migration items to the common review > checklist > > I've seen this come up

Re: [openstack-dev] [trove] My thoughts on the Unified Guest Agent

How about a different approach then... OpenStack has thus far been very successful providing an API and plugins for dealing with things that cloud providers need to be able to switch out to suit their needs. There seems to be two different parts to the unified agent issue: * How to get rpc mess

Re: [openstack-dev] [keystone] domain admin role query

Thanks Dolph, It worked now. I specified domain id in the scope. -Ravi. On Wed, Dec 18, 2013 at 12:05 PM, Ravi Chunduru wrote: > Hi Dolph, > I dont have project yet to use in the scope. The intention is to get a > token using domain admin credentials and create project using it. > > Thanks,

Re: [openstack-dev] [keystone] domain admin role query

Hi Dolph, I dont have project yet to use in the scope. The intention is to get a token using domain admin credentials and create project using it. Thanks, -Ravi. On Wed, Dec 18, 2013 at 11:39 AM, Dolph Mathews wrote: > > On Wed, Dec 18, 2013 at 12:48 PM, Ravi Chunduru wrote: > >> Thanks all

Re: [openstack-dev] [trove] My thoughts on the Unified Guest Agent

Tim, we definitely don't want to force projects to migrate to the unified agent. I've started making the PoC with the idea that Savanna needs the agent anyway, and we want it to be ready for Icehouse. On the other side, I believe, it will be much easier to drive the discussion further with the PoC

Re: [openstack-dev] Adding DB migration items to the common review checklist

I don't have a problem with any of these requirements, but I'd like to explore automating the checks. Would it be possible to write a unit test that verified this for all migrations? Then we don't need to add it to the checklist... Michael On Thu, Dec 19, 2013 at 4:27 AM, Matt Riedemann wrote: >

Re: [openstack-dev] [keystone] domain admin role query

On Wed, Dec 18, 2013 at 12:48 PM, Ravi Chunduru wrote: > Thanks all for the information. > I have now v3 policies in place, the issue is that as a domain admin I > could not create a project in the domain. I get 403 unauthorized status. > > I see that when as a 'domain admin' request a token, th

Re: [openstack-dev] [Nova] Future meeting times

> I am fine with this, but I will never be attending the 1400 UTC > meetings, as I live in utc-8 I too will miss the 1400UTC meetings during the majority of the year. During PDT I will be able to make them, but will be uncaffeinated. --Dan ___ OpenStac

Re: [openstack-dev] API spec for OS-NS-ROLES extension

Services already own their own policy enforcement, and therefore own their own definitions of roles. A service deployment can already require roles that are prefixed by a specific string (compute-*), and can already map actual capabilities onto those roles ({"compute-create": "role:compute-manager"

Re: [openstack-dev] [trove] My thoughts on the Unified Guest Agent

Thanks for the summary Dmitry. I'm ok with these ideas, and while I still disagree with having a single, forced standard for RPC communication, I should probably let things pan out a bit before being too concerned. - Tim From: Dmitry Mescheryakov [dmescherya...

Re: [openstack-dev] [Nova] Future meeting times

On Dec 18, 2013 6:38 AM, "Russell Bryant" wrote: > > Greetings, > > The weekly Nova meeting [1] has been held on Thursdays at 2100 UTC. > I've been getting some requests to offer an alternative meeting time. > I'd like to try out alternating the meeting time between two different > times to allow

Re: [openstack-dev] [trove] My thoughts on the Unified Guest Agent

>> Please provide proof of that assumption or at least a general hypothesis >> that we can test. I can't prove that the new agent will be larger as it doesn't exist yet. >> Since nothing was agreed upon anyway, I don't know how you came to that >> conclusion. I would suggest that any agent fr

Re: [openstack-dev] Adding DB migration items to the common review checklist

Matt - Could a test be added that goes through the models and checks these things? Other projects could use this too. Here's an example of a test that checks if the tables are all InnoDB: http://git.openstack.org/cgit/openstack/nova/tree/nova/tests/db/test_migrations.py?id=6e455cd97f04bf26bbe022b

Re: [openstack-dev] [nova] How do we format/version/deprecate things from notifications?

On 12/18/2013 03:00 PM, Russell Bryant wrote: > We really need proper versioning for notifications. We've had a > blueprint open for about a year, but AFAICT, nobody is actively working > on it. > > https://blueprints.launchpad.net/nova/+spec/versioned-notifications > IBM is behind this effo

Re: [openstack-dev] [nova] How do we format/version/deprecate things from notifications?

On 12/18/2013 01:44 PM, Nikola Đipanov wrote: > On 12/18/2013 06:17 PM, Matt Riedemann wrote: >> >> >> On 12/18/2013 9:42 AM, Matt Riedemann wrote: >>> The question came up in this patch [1], how do we deprecate and remove >>> keys in the notification payload? In this case I need to deprecate an

Re: [openstack-dev] [Heat] hybrid cloud & bursting question

On 18/12/13 04:26, 이준원 wrote: Hi, stackers, I know only little about Heat, and I can't wholly follow recent discussions around multi-region support in this mailing list. Please help me understand the roadmap or plan about hybrid cloud and "bursting" in particular. I'd like to ask the following

Re: [openstack-dev] [Nova] [Ironic] Get power and temperature via IPMI

On Tue, Dec 17, 2013 at 10:00 PM, Gao, Fengqian wrote: > Hi, all, > > I am planning to extend bp > https://blueprints.launchpad.net/nova/+spec/utilization-aware-schedulingwith > power and temperature. In other words, power and temperature can be > collected and used for nova-scheduler just as CP

Re: [openstack-dev] [nova] How do we format/version/deprecate things from notifications?

On 12/18/2013 12:44 PM, Nikola Đipanov wrote: > On 12/18/2013 06:17 PM, Matt Riedemann wrote: >> >> >> On 12/18/2013 9:42 AM, Matt Riedemann wrote: >>> The question came up in this patch [1], how do we deprecate and remove >>> keys in the notification payload? In this case I need to deprecate and

Re: [openstack-dev] [keystone] domain admin role query

Thanks all for the information. I have now v3 policies in place, the issue is that as a domain admin I could not create a project in the domain. I get 403 unauthorized status. I see that when as a 'domain admin' request a token, the response did not have any roles. In the token request, I couldn

Re: [openstack-dev] Diversity as a requirement for incubation

On 12/18/2013 07:01 AM, Dolph Mathews wrote: > Options 2 and 3 sound identical to me, when realistically applied. > Option 3 just makes the common sense aspect mandatory. Indeed, Option 3 gets my vote. One aspect I'd like to mention regarding diversity of contributors in any open source project is

Re: [openstack-dev] [trove] My thoughts on the Unified Guest Agent

Someone's gotta make/maintain the trove/savanna images though. They usually are built from packages. If there is a unified agent, then it only has to be packaged once. If there is one per special type of agent, its one package per special type of agent. I don't think there is a free lunch here,

Re: [openstack-dev] [Nova] [Ironic] Get power and temperature via IPMI

Hi Gao What is the reason why you see it would be important to have these two additional metrics "power and temperature" for Nova to base scheduling on? Alan From: Gao, Fengqian [mailto:fengqian@intel.com] Sent: December-18-13 1:00 AM To: openstack-dev@lists.openstack.org Subject: [openstac

Re: [openstack-dev] [Heat] hybrid cloud & bursting question

Excerpts from =?ks_c_5601-1987?B?wMzB2L/4?='s message of 2013-12-18 01:26:22 -0800: > Hi, stackers, > > I know only little about Heat, and I can't wholly follow recent > discussions around multi-region support in this mailing list. > Please help me understand the roadmap or plan about hybrid clo

Re: [openstack-dev] Unified Guest Agent proposal

That sounds like a very good idea, I'll do it. 2013/12/18 Clint Byrum > Excerpts from Dmitry Mescheryakov's message of 2013-12-18 09:32:30 -0800: > > Clint, do you mean > > * use os-collect-config and its HTTP transport as a base for the PoC > > or > > * migrate os-collect-config on PoC aft

Re: [openstack-dev] [trove] My thoughts on the Unified Guest Agent

2013/12/18 Steven Dake > On 12/18/2013 08:34 AM, Tim Simpson wrote: > > I've been following the Unified Agent mailing list thread for awhile now > and, as someone who has written a fair amount of code for both of the two > existing Trove agents, thought I should give my opinion about it. I like

Re: [openstack-dev] [cinder] weekly meeting

For me, 4/5 is currently 6/7AM. An hour later when daylight savings messes things up. Exactly wake up/get ready/kid to school/me to work time. I'd rather leave it as is (6/7PM depending on daylight savings). If you alternate, I may have to miss some. Thanks, Avishay From: John Griffith T

Re: [openstack-dev] [trove] My thoughts on the Unified Guest Agent

Tim, The unified agent we proposing is based on the following ideas: * the core agent has _no_ functionality at all. It is a pure RPC mechanism with the ability to add whichever API needed on top of it. * the API is organized into modules which could be reused across different projects. * th

Re: [openstack-dev] Diversity as a requirement for incubation

On 18/12/13 12:35 -0500, Doug Hellmann wrote: On Wed, Dec 18, 2013 at 10:58 AM, Sean Dague wrote: On 12/18/2013 10:37 AM, Steven Dake wrote: > But I can tell you one thing for certain, an actual incubation > commitment from the OpenStack Technical Committee has a huge impact - it >

Re: [openstack-dev] [nova] How do we format/version/deprecate things from notifications?

On 12/18/2013 06:17 PM, Matt Riedemann wrote: > > > On 12/18/2013 9:42 AM, Matt Riedemann wrote: >> The question came up in this patch [1], how do we deprecate and remove >> keys in the notification payload? In this case I need to deprecate and >> replace the 'instance_type' key with 'flavor' pe

Re: [openstack-dev] Unified Guest Agent proposal

Excerpts from Dmitry Mescheryakov's message of 2013-12-18 09:32:30 -0800: > Clint, do you mean > * use os-collect-config and its HTTP transport as a base for the PoC > or > * migrate os-collect-config on PoC after it is implemented on > oslo.messaging > > I presume the later, but could you cla

Re: [openstack-dev] [trove] My thoughts on the Unified Guest Agent

Excerpts from Steven Dake's message of 2013-12-18 08:05:09 -0800: > On 12/18/2013 08:34 AM, Tim Simpson wrote: > > I've been following the Unified Agent mailing list thread for awhile > > now and, as someone who has written a fair amount of code for both of > > the two existing Trove agents, thou

Re: [openstack-dev] [trove] My thoughts on the Unified Guest Agent

Excerpts from Tim Simpson's message of 2013-12-18 07:34:14 -0800: > I've been following the Unified Agent mailing list thread for awhile > now and, as someone who has written a fair amount of code for both of > the two existing Trove agents, thought I should give my opinion about > it. I like the i

Re: [openstack-dev] Diversity as a requirement for incubation

On Wed, Dec 18, 2013 at 10:20 AM, Jarret Raim wrote: > > It is a difficult thing to measure, and I don't think the intent is to > set > a hard % > > for contributions. I think the numbers for Barbican were just > illustrating > the > > fact that the concrete contributions are very coming very heav

Re: [openstack-dev] Diversity as a requirement for incubation

On Wed, Dec 18, 2013 at 10:58 AM, Sean Dague wrote: > On 12/18/2013 10:37 AM, Steven Dake wrote: > > On 12/18/2013 03:40 AM, Thierry Carrez wrote: > >> Hi everyone, > >> > >> The TC meeting yesterday uncovered an interesting question which, so > >> far, divided TC members. > >> > >> We require th

Re: [openstack-dev] Unified Guest Agent proposal

Clint, do you mean * use os-collect-config and its HTTP transport as a base for the PoC or * migrate os-collect-config on PoC after it is implemented on oslo.messaging I presume the later, but could you clarify? 2013/12/18 Clint Byrum > Excerpts from Dmitry Mescheryakov's message of 2013-

[openstack-dev] Adding DB migration items to the common review checklist

I've seen this come up a few times in reviews and was thinking we should put something in the general review checklist wiki for it [1]. Basically I have three things I'd like to have in the list for DB migrations: 1. Unique constraints should be named. Different DB engines and SQLAlchemy dia

[openstack-dev] API spec for OS-NS-ROLES extension

Hi Adam, I would like to request you to revisit the below link and provide your opinion, so that we can move forward and try to find a common ground where everyone. https://review.openstack.org/#/c/61897 Below is my justification for service_id in role model: In a public cloud deployment model

Re: [openstack-dev] [nova] How do we format/version/deprecate things from notifications?

On 12/18/2013 9:42 AM, Matt Riedemann wrote: The question came up in this patch [1], how do we deprecate and remove keys in the notification payload? In this case I need to deprecate and replace the 'instance_type' key with 'flavor' per the associated blueprint. [1] https://review.openstack.o

Re: [openstack-dev] Diversity as a requirement for incubation

On 18/12/13 11:40 +0100, Thierry Carrez wrote: Hi everyone, The TC meeting yesterday uncovered an interesting question which, so far, divided TC members. We require that projects have a number of different developers involved before they apply for incubation, mostly to raise the bus factor. But

Re: [openstack-dev] Diversity as a requirement for incubation

On Wed, Dec 18 2013, Thierry Carrez wrote: > 1. Require diversity for incubation, but find ways to bless or recommend > projects pre-incubation so that this diversity can actually be achieved > > 2. Do not require diversity for incubation, but require it for > graduation, and remove projects from

[openstack-dev] Subject: [nova][vmware] VMwareAPI sub-team status 2013-12-08

Greetings Stackers! BTW: Reviews by fitness at the end. It's Wednesday so it's time for me to cheer-lead for our VMwareAPI subteam. Go team! Our normal Wednesday meetings fall on December 25th and January 1st coming up so, no meetings until January 8th. If there's a really strong objection to tha

Re: [openstack-dev] [Nova] Future meeting times

On 12/18/2013 03:29 PM, Russell Bryant wrote: > Greetings, > > The weekly Nova meeting [1] has been held on Thursdays at 2100 UTC. > I've been getting some requests to offer an alternative meeting time. > I'd like to try out alternating the meeting time between two different > times to allow more

Re: [openstack-dev] [trove] My thoughts on the Unified Guest Agent

On 12/18/2013 08:34 AM, Tim Simpson wrote: I've been following the Unified Agent mailing list thread for awhile now and, as someone who has written a fair amount of code for both of the two existing Trove agents, thought I should give my opinion about it. I like the idea of a unified agent, but

Re: [openstack-dev] Incubation Request for Barbican

On 12/18/2013 10:23 AM, Jarret Raim wrote: >> -Original Message- >> From: Steven Dake [mailto:sd...@redhat.com] >> In this particular case, I believe Barbican is not ready for incubation > because >> of their dependence on celery, but ultimately I don't make the decision :) > > We've lande

Re: [openstack-dev] [Horizon] Weekly meeting time

Thanks Liz for setting up the poll. I'm not sure we're locked to Tuesday as the meeting day either. On Tuesdays, 20:00 UTC (TC meeting) and 21:00 UTC (Project) are meetings I don't want to schedule over. Those times are more attractive on other days. -David > -Original Message- > Fro

Re: [openstack-dev] Diversity as a requirement for incubation

On 12/18/2013 10:37 AM, Steven Dake wrote: > On 12/18/2013 03:40 AM, Thierry Carrez wrote: >> Hi everyone, >> >> The TC meeting yesterday uncovered an interesting question which, so >> far, divided TC members. >> >> We require that projects have a number of different developers involved >> before t

Re: [openstack-dev] olso.config error on running Devstack

Also forgot to mention I can access the dashboard but I am unable to retrieve any information about the volumes. On Dec 18, 2013 8:56 PM, "Sayali Lunkad" wrote: > Hello, > > I get the following error when I run stack.sh on Devstack > > Traceback (most recent call last): > File "/usr/local/bin/c

Re: [openstack-dev] [cinder] weekly meeting

On Wed, Dec 18, 2013 at 8:35 AM, Duncan Thomas wrote: > 04:00 or 05:00 UTC would basically preclude European participation for > most people... that's 4 am for Dosaboy and myself for example. > > Alternating meetings on different weeks would probably work, though we > would need to encourage peopl

Re: [openstack-dev] olso.config error on running Devstack

Hey, I do need ceilometer so making changes to localrc won't help me here. And no corporate proxy! What could possibly be the issue because my Devstack had been working fine till now. Thanks, Sayali On Dec 18, 2013 9:14 PM, "iKhan" wrote: > If you are behind corporate proxy, make sure the proxy

Re: [openstack-dev] [Solum] Git workflow meeting reminder & agenda

Hi Ibad, The Solum Git workflow meeting will be on #solum channel on IRC (freenode). —Kr On Dec 18, 2013, at 7:30 AM, iKhan wrote: > I am newbie here and I am from +5:30 GMT. Can any one direct me how to attend > this meeting? > > > On Wed, Dec 18, 2013 at 12:46 PM, Krishna Raman wrote: >

Re: [openstack-dev] [Solum] Git workflow meeting reminder & agenda

Use IRC to connect to irc.freenode.net Join the #solum channel The meeting starts in roughly 15 minutes from now. On Dec 18, 2013, at 7:30 AM, iKhan mailto:ik.ibadk...@gmail.com>> wrote: I am newbie here and I am from +5:30 GMT. Can any one direct me how to attend thi

[openstack-dev] [nova] How do we format/version/deprecate things from notifications?

The question came up in this patch [1], how do we deprecate and remove keys in the notification payload? In this case I need to deprecate and replace the 'instance_type' key with 'flavor' per the associated blueprint. [1] https://review.openstack.org/#/c/62430/ -- Thanks, Matt Riedemann _

Re: [openstack-dev] Diversity as a requirement for incubation

On 12/18/2013 03:40 AM, Thierry Carrez wrote: Hi everyone, The TC meeting yesterday uncovered an interesting question which, so far, divided TC members. We require that projects have a number of different developers involved before they apply for incubation, mostly to raise the bus factor. But

Re: [openstack-dev] [cinder] weekly meeting

04:00 or 05:00 UTC would basically preclude European participation for most people... that's 4 am for Dosaboy and myself for example. Alternating meetings on different weeks would probably work, though we would need to encourage people to get stuff on the agenda in advance rather than an hour befo

  1   2   >