Re: [openstack-dev] [glance] Please stop +Aing glance changes until your doc job is working

On 11/12/13 18:05 -0500, Sean Dague wrote: Dear Glance core, Until this review is sorted - https://review.openstack.org/#/c/60971/2 You won't be able to merge any changes, because of the docs issue with sphinx. http://lists.openstack.org/pipermail/openstack-dev/2013-December/021863.html Which

Re: [openstack-dev] [TripleO] Tuskar CLI after architecture changes

On 12/11/2013 06:15 PM, Jiří Stránský wrote: On 11.12.2013 17:13, Ladislav Smola wrote: Hi, thanks for starting this conversation. I will take it little side ways. I think we should be asking why have we needed the tuskar-api. It has done some more complex logic (e.g. building a heat template)

[openstack-dev] [Ironic] firmware security

Hi Ironic folks, I remembered once seeing that ironic was calling for firmware security. Can anyone elaborate with a little bit details about what Ironic needs for this "firmware security"? I'm wondering if there are some existing technologies(e.g. TPM, TXT, etc) that can be used for this purpo

Re: [openstack-dev] [TripleO][Tuskar] Terminology

On 2013/12/12 01:21, Robert Collins wrote: On 12 December 2013 08:15, Tzu-Mainn Chen * MANAGEMENT NODE - a node that has been mapped with an undercloud role Pedantically, this is 'A node with an instance of a management role running on it'. I think calling it 'management node' is to

Re: [openstack-dev] [TripleO] Tuskar CLI after architecture changes

On 12/11/2013 05:41 PM, Jay Dobies wrote: > I will take it little side ways. I think we should be asking why have > we needed the tuskar-api. It has done some more complex logic (e.g. > > building a heat template) or storing additional info, not supported > > by the services we use (like rack a

Re: [openstack-dev] [Ceilometer] [Rally] Does Ceilometer affect instance creation?

Doug, Sorry for confusing you with 'local' term. I meant that collector is up on the node which is one of the Galera-nodes. Data will be replicated and all the Galera nodes will be synced. Nadya On Thu, Dec 12, 2013 at 2:01 AM, Doug Hellmann wrote: > > > > On Tue, Dec 10, 2013 at 9:47 AM, Nady

Re: [openstack-dev] request-id in API response

On Thu, Dec 12, 2013 at 1:40 AM, Sean Dague wrote: > On 12/11/2013 04:17 PM, Chris Buccella wrote: > > On 12/02/2013 10:18 AM, Joe Gordon wrote: > >> > >> > >> > >> > >> Thanks for bringing this up, and I'd welcome a patch in Swift that > >> would use a common library to generate the tran

Re: [openstack-dev] [Neutron] Fix to agents race condition creates another issue

Ok, I just did it. https://bugs.launchpad.net/neutron/+bug/1260232 It seems that Yong found the same problem for ML2: https://bugs.launchpad.net/bugs/1260224 I am just wondering, how come we did not catch this with ML2 when we are claiming that it is our default plugin. Edgar On Wed, Dec 11,

Re: [openstack-dev] [Neutron] Third-party testing

2013/12/11 Salvatore Orlando : > Hi Yoshihiro, > > In my opinion the use of filters on changes is allowed by the smoketesting > policy we defined. > Notwithstanding that the approach of testing every patch is definitely the > safest, I understand in some cases the volume of patchsets uploaded to >

Re: [openstack-dev] [Neutron] Interfaces file format, was [Tempest] Need to prepare the IPv6 environment for static IPv6 injection test case

Hi Ian and Vish, Thanks for your reply. From your response, I still have some questions, hope you can help me to clear up them. <1> From Vish's response, may I believe that static IPv6 injection using the interface.template will be dropped in future because it is not a correct way to do net c

[openstack-dev] OpenStack Icehouse milestone 1 packages for Ubuntu

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hi All As OpenStack Icehouse milestone 1 is now out, I thought it worth updating everyone on Ubuntu activities during the Icehouse development cycle. For release, Ubuntu will be providing Icehouse packages for both Ubuntu 14.04 and for Ubuntu 12.04

Re: [openstack-dev] [Horizon] Nominations to Horizon Core

Lyle, David wrote: > So again, nothing prevents a non-core security reviewer from reviewing > blueprints and doing code reviews. Believe me any security minded input is > always welcome and weighed carefully. > > Although the principle of having a minimum number of security reviewers in > core

Re: [openstack-dev] [TripleO] Tuskar CLI after architecture changes

On 12.12.2013 09:48, Ladislav Smola wrote: On 12/11/2013 06:15 PM, Jiří Stránský wrote: On 11.12.2013 17:13, Ladislav Smola wrote: Hi, thanks for starting this conversation. I will take it little side ways. I think we should be asking why have we needed the tuskar-api. It has done some more co

Re: [openstack-dev] [Neutron] Fix to agents race condition creates another issue

Hi, So actually these two are different issues: 1) https://review.openstack.org/#/c/61677 fixes the issue with a few mandatory migrations not applying when ML2 plugin is used (the only reason we hadn't seen it before is that those migrations were applied on Jenkins CI nodes because LBaaS service p

Re: [openstack-dev] [TripleO] Tuskar CLI after architecture changes

On 12/12/2013 10:49 AM, Jiří Stránský wrote: On 12.12.2013 09:48, Ladislav Smola wrote: On 12/11/2013 06:15 PM, Jiří Stránský wrote: On 11.12.2013 17:13, Ladislav Smola wrote: Hi, thanks for starting this conversation. I will take it little side ways. I think we should be asking why have we

Re: [openstack-dev] [neutron] Third party Neutron plugin testing meeting

Is the meeting time today 1700UTC? I think this week meeting should be held at the original time to avoid confusion. 2013年12月12日木曜日 Sukhdev Kapur sukhdevka...@gmail.com: > +1 > I'll be there.. > > Sukhdev > On Dec 10, 2013 12:43 PM, "Kyle Mestery" wrote: > > OK, looks like we've reached consensu

Re: [openstack-dev] [TripleO] Tuskar CLI after architecture changes

On 12/11/2013 01:33 PM, Jiří Stránský wrote: Hi all, Hi Jirka, TL;DR: I believe that "As an infrastructure administrator, Anna wants a CLI for managing the deployment providing the same fundamental features as UI." With the planned architecture changes (making tuskar-api thinner and getting

Re: [openstack-dev] [TripleO] Tuskar CLI after architecture changes

On 11/12/13 13:33, Jiří Stránský wrote: [snip] > TL;DR: I believe that "As an infrastructure administrator, Anna wants a > CLI for managing the deployment providing the same fundamental features > as UI." With the planned architecture changes (making tuskar-api thinner > and getting rid of proxyi

Re: [openstack-dev] [TripleO][Tuskar] Terminology

On 12/11/2013 08:59 PM, James Slagle wrote: This is really helpful, thanks for pulling it together. comment inline... On Wed, Dec 11, 2013 at 2:15 PM, Tzu-Mainn Chen wrote: * NODE a physical general purpose machine capable of running in many roles. Some nodes may have hardware layout that is

Re: [openstack-dev] [OpenStack][Heat] AutoScaling scale down issue

On 12/11/2013 11:43 PM, Jay Lau wrote: Greetings, Here come a question related to heat auto scale down. The scenario is as following: I was trying to deploy hadoop cluster with heat Auto Scaling template. When scale up a slave node, I can use user-data to do some post work for configuration f

Re: [openstack-dev] Neutron Distributed Virtual Router

NSX distributed routers behave, from a tenant perspective, exactly like any other router. Beyond the service level factor, which I believe Ian is referring to as well, there is no reason for distinguishing them from standard routers through the API. I believe the same applies distributed router b

[openstack-dev] [Rally] Operations manage of deployments

Hi guys, I want to share about results of improving Rally within the work on blueprint independent-deploy [1]. The motivation for this work was the inability of reusing of one configuration for perform several benchmarking tasks on the same installation. Of course, it's affect only tasks which

Re: [openstack-dev] [Neutron][LBaaS] Vote required for certificate as first-class citizen - SSL Termination (Revised)

Thanks for your review Vijay 1. Pass-Info is for the backend. Used for informing the Back-End regarding SSL termination details. 2. Added cipher-suites groups 3. Added default policy 4. Added SNI support. I think our model should support it, since EC2 supports it. 5. Renamed "Trusted Key" to "T

Re: [openstack-dev] [Neutron] Running multiple neutron-servers

Sadly this patch is now abandoned. As stated in the review I did, the bug is one we should definitely fix, but it is even more important to avoid introducing further race conditions. I will look back at the latest comments from Zhang and see whether we can go ahead and restore that patch or whethe

Re: [openstack-dev] [neutron] Third party Neutron plugin testing meeting

Today's meeting is still at 1700UTC. Kyle agreed next week the meeting should be at an Asia-friendly time, and 2200UTC was voted for that. On Thu, Dec 12, at 5:36 am, Akihiro Motoki wrote: > Is the meeting time today 1700UTC? > I think this week meeting should be held at the original time to avoi

Re: [openstack-dev] Performance Regression in Neutron/Havana compared to Quantum/Grizzly

I believe your analysis is correct and inline with the findings reported in the bug concerning OVS agent loop slowdown. The issue has become even more prominent with the ML2 plugin due to an increased number of notifications sent. Another issue which makes delays on the DHCP agent worse is that i

Re: [openstack-dev] [TripleO][Tuskar] Terminology

On 12/11/2013 08:54 PM, Jay Dobies wrote: So glad we're hashing this out now. This will save a bunch of headaches in the future. Good call pushing this forward. On 12/11/2013 02:15 PM, Tzu-Mainn Chen wrote: Hi, I'm trying to clarify the terminology being used for Tuskar, which may be helpf

Re: [openstack-dev] [Neutron] Interfaces file format, was [Tempest] Need to prepare the IPv6 environment for static IPv6 injection test case

(2) should read 'the data should appear on both metadata and the config drive', I would say. Vish was making a point that this metadata changes (e.g. when running nova interface-attach) and it might be nice if the metadata server updated its information. It might be, and changing metadata has bee

[openstack-dev] State of the Gate - Dec 12

Current Gate Length: 12hrs*, 41 deep (top of gate entered 12hrs ago) It's been an *exciting* week this week. For people not paying attention we had 2 external events which made things terrible earlier in the week. == Event 1: sphinx 1.2 complete breakage - MOSTLY RESOLVED

Re: [openstack-dev] [TripleO] Tuskar CLI after architecture changes

On 12.12.2013 11:49, Radomir Dopieralski wrote: On 11/12/13 13:33, Jiří Stránský wrote: [snip] TL;DR: I believe that "As an infrastructure administrator, Anna wants a CLI for managing the deployment providing the same fundamental features as UI." With the planned architecture changes (making t

Re: [openstack-dev] [TripleO] Tuskar CLI after architecture changes

On 12/12/13 11:49, Radomir Dopieralski wrote: > On 11/12/13 13:33, Jiří Stránský wrote: > > [snip] > >> TL;DR: I believe that "As an infrastructure administrator, Anna wants a >> CLI for managing the deployment providing the same fundamental features >> as UI." With the planned architecture chang

Re: [openstack-dev] [TripleO] Tuskar CLI after architecture changes

On 12.12.2013 14:26, Jiří Stránský wrote: On 12.12.2013 11:49, Radomir Dopieralski wrote: On 11/12/13 13:33, Jiří Stránský wrote: [snip] TL;DR: I believe that "As an infrastructure administrator, Anna wants a CLI for managing the deployment providing the same fundamental features as UI." With

Re: [openstack-dev] [Horizon] Nominations to Horizon Core

On 12/11/2013 11:08 PM, Bryan D. Payne wrote: > We can involve people in security reviews without having them on the > core review team. They are separate concerns. > > > Yes, but those people can't ultimately approve the patch. So you'd need > to have a security reviewer do their revie

Re: [openstack-dev] [TripleO] Tuskar CLI after architecture changes

Agree with this. Though I am an optimist, I believe that this time, we can avoid calling multiple services in one request that depend on each other. About the multiple users at once, this should be solved inside the API calls of the services. So I think we should forbid building these comple

Re: [openstack-dev] [Oslo] First steps towards amqp 1.0

On 11/12/13 09:31 -0500, Andrew Laski wrote: On 12/10/13 at 11:09am, Flavio Percoco wrote: On 09/12/13 17:37 -0500, Russell Bryant wrote: On 12/09/2013 05:16 PM, Gordon Sim wrote: On 12/09/2013 07:15 PM, Russell Bryant wrote: [...] One other pattern that can benefit from intermediated mess

Re: [openstack-dev] OpenStack Icehouse milestone 1 packages for Ubuntu

AWESOME! Do you know if we can start testing IPv6 tenants networks? Tks! On 12 December 2013 07:38, James Page wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA256 > > Hi All > > As OpenStack Icehouse milestone 1 is now out, I thought it worth > updating everyone on Ubuntu activities duri

Re: [openstack-dev] [TripleO] Tuskar CLI after architecture changes

On Thu, Dec 12, 2013 at 03:11:14PM +0100, Ladislav Smola wrote: > Agree with this. > > Though I am an optimist, I believe that this time, we can avoid > calling multiple services in one request that depend on each other. > About the multiple users at once, this should be solved inside the > API c

[openstack-dev] [Nova] All I want for Christmas is one more +2 ...

Hi Cores, The "Stop, Rescue, and Delete should give guest a chance to shutdown" change https://review.openstack.org/#/c/35303/ was approved a couple of days ago, but failed to merge because the RPC version had moved on. Its rebased and sitting there with one +2 and a bunch of +1s -would be r

[openstack-dev] Announcing Fuel

Folks, Most of you by now have heard of Fuel, which we’ve been working on as a related OpenStack project for a period of time - see https://launchpad.net/fuel and https://wiki.openstack.org/wiki/Fuel. The aim of the project is to provide a distribution agno

Re: [openstack-dev] State of the Gate - Dec 12

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 12/12/2013 08:20 AM, Sean Dague wrote: > Current Gate Length: 12hrs*, 41 deep > > (top of gate entered 12hrs ago) > > It's been an *exciting* week this week. For people not paying > attention we had 2 external events which made things terrible > e

Re: [openstack-dev] What's Up Doc? Dec 11 2013

On Wed, Dec 11, 2013 at 5:31 PM, Anne Gentle wrote: > Thanks to new doc patchers Shilla Saebi and Thomas Herve for their clean > up work, especially for the Identity API docs and Heat install! > > Be ready for 12/20/13 Doc Bug Day! Looking forward to it. > > 1. In review and merged this past week

Re: [openstack-dev] [Nova] All I want for Christmas is one more +2 ...

On 12/12/2013 09:22 AM, Day, Phil wrote: > Hi Cores, > > > > The “Stop, Rescue, and Delete should give guest a chance to shutdown” > change https://review.openstack.org/#/c/35303/ was approved a couple of > days ago, but failed to merge because the RPC version had moved on. > Its rebased and

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

On 12/11/2013 10:11 PM, Paul Belanger wrote: On 13-12-11 11:18 AM, Lyle, David wrote: +1 on moving the domain admin role rules to the default policy.json -David Lyle From: Dolph Mathews [mailto:dolph.math...@gmail.com] Sent: Wednesday, December 11, 2013 9:04 AM To: OpenStack Development Mailin

Re: [openstack-dev] State of the Gate - Dec 12

On Thu, Dec 12, 2013 at 08:20:09AM -0500, Sean Dague wrote: > Current Gate Length: 12hrs*, 41 deep > > (top of gate entered 12hrs ago) > > It's been an *exciting* week this week. For people not paying attention > we had 2 external events which made things terrible earlier in the week. > > ==

Re: [openstack-dev] State of the Gate - Dec 12

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 12/12/2013 09:39 AM, Anita Kuno wrote: > On 12/12/2013 08:20 AM, Sean Dague wrote: >> Current Gate Length: 12hrs*, 41 deep > >> (top of gate entered 12hrs ago) > >> It's been an *exciting* week this week. For people not paying >> attention we had

Re: [openstack-dev] [Ceilometer] [Rally] Does Ceilometer affect instance creation?

Ok, that sounds like it would do what you want. Thanks for clarifying. :-) Doug On Thu, Dec 12, 2013 at 4:06 AM, Nadya Privalova wrote: > Doug, > > Sorry for confusing you with 'local' term. I meant that collector is up on > the node which is one of the Galera-nodes. Data will be replicated and

[openstack-dev] Stackalytics 0.4 released!

Hello everyone! Stackalytics team is happy to announce the release of version 0.4. This release is completely dedicated to different types of reports. We added highly demanded top reviewers chart acknowledged as an essential tool for finding most active reviewers (ex. http://stackalytics.com/repor

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

On Wed, Dec 11, 2013 at 6:29 PM, Christopher Yeoh wrote: > On Thu, Dec 12, 2013 at 7:11 AM, Ryan Petrello < > ryan.petre...@dreamhost.com> wrote: > >> Hello, >> >> I’ve spent the past week experimenting with using Pecan for Nova’s API, >> and have opened an experimental review: >> >> https://revi

Re: [openstack-dev] Incubation Request for Barbican

> > >$ git shortlog -s -e | sort -n -r > > 172 John Wood > > 150 jfwood > >65 Douglas Mendizabal > >39 Jarret Raim > >17 Malini K. Bhandaru > >10 Paul Kehrer > >10 Jenkins > > 8 jqxin2006 > > 7 Arash Ghoreyshi > > 5 Chad Lung > > 3 Dolph Mathews >

Re: [openstack-dev] [TripleO] Tuskar CLI after architecture changes

On Wed, 2013-12-11 at 13:33 +0100, Jiří Stránský wrote: > Hi all, > > TL;DR: I believe that "As an infrastructure administrator, Anna wants a > CLI for managing the deployment providing the same fundamental features > as UI." With the planned architecture changes (making tuskar-api thinner > an

Re: [openstack-dev] [Horizon] Nominations to Horizon Core

I just wanted to close the loop here. I understand the position that others are taking and it appears that I'm outnumbered :-) While I disagree with this approach, it sounds like that's where we are at today. Even with this decision, I would encourage the horizon dev team to utilize Paul as a se

[openstack-dev] [Nova] cross-project bug fixes

I am in the process of getting a bug fix approved for a bug found in openstack.common: https://review.openstack.org/#/c/60500/ The bug is present in both nova and cinder. The above patch is under nova; do I need to submit a separate cinder patch covering the same fix, or does the shared nature

[openstack-dev] Generic question: Any tips for 'keeping up' with the mailing lists?

I am a developer who is currently having troubles keeping up with the mailing list due to volume, and my inability to organize it in my client. I am nearly forced to use Outlook 2011 for Mac and I have read and attempted to implement https://wiki.openstack.org/wiki/MailingListEtiquette but it is st

Re: [openstack-dev] Generic question: Any tips for 'keeping up' with the mailing lists?

On 12/12/2013 11:23 AM, Justin Hammond wrote: > I am a developer who is currently having troubles keeping up with the > mailing list due to volume, and my inability to organize it in my client. > I am nearly forced to use Outlook 2011 for Mac and I have read and > attempted to implement > https://w

Re: [openstack-dev] [TripleO][Tuskar] Icehouse Requirements

On Dec 10, 2013, at 5:09 PM, Robert Collins wrote: > On 11 December 2013 05:42, Jaromir Coufal wrote: >> On 2013/09/12 23:38, Tzu-Mainn Chen wrote: >>> The disagreement comes from whether we need manual node assignment or not. >>> I would argue that we >>> need to step back and take a look at the

Re: [openstack-dev] Stackalytics 0.4 released!

On 12/12/2013 04:49 PM, Ilya Shakhat wrote: > Hello everyone! > > Stackalytics team is happy to announce the release of version 0.4. This > release is completely dedicated to different types of reports. We added > highly demanded top reviewers chart acknowledged as an essential tool > for findin

Re: [openstack-dev] Generic question: Any tips for 'keeping up' with the mailing lists?

Russell Bryant wrote: > On 12/12/2013 11:23 AM, Justin Hammond wrote: >> I am a developer who is currently having troubles keeping up with the >> mailing list due to volume, and my inability to organize it in my client. >> I am nearly forced to use Outlook 2011 for Mac and I have read and >> attemp

Re: [openstack-dev] [Nova] cross-project bug fixes

On 12/12/2013 11:21 AM, Hamilton, Peter A. wrote: > I am in the process of getting a bug fix approved for a bug found in > openstack.common: > > https://review.openstack.org/#/c/60500/ > > The bug is present in both nova and cinder. The above patch is under nova; do > I need to submit a separat

Re: [openstack-dev] Generic question: Any tips for 'keeping up' with the mailing lists?

Excerpts from Justin Hammond's message of 2013-12-12 08:23:24 -0800: > I am a developer who is currently having troubles keeping up with the > mailing list due to volume, and my inability to organize it in my client. > I am nearly forced to use Outlook 2011 for Mac and I have read and > attempted t

[openstack-dev] [Nova] [Neutron] How do we know a host is ready to have servers scheduled onto it?

I've been chasing quite a few bugs in the TripleO automated bring-up lately that have to do with failures because either there are no valid hosts ready to have servers scheduled, or there are hosts listed and enabled, but they can't bind to the network because for whatever reason the L2 agent has n

Re: [openstack-dev] [Nova] [Neutron] How do we know a host is ready to have servers scheduled onto it?

On 12/12/2013 12:02 PM, Clint Byrum wrote: > I've been chasing quite a few bugs in the TripleO automated bring-up > lately that have to do with failures because either there are no valid > hosts ready to have servers scheduled, or there are hosts listed and > enabled, but they can't bind to the net

Re: [openstack-dev] [TripleO][Tuskar] Icehouse Requirements

On Dec 11, 2013, at 3:42 PM, Robert Collins wrote: > On 12 December 2013 01:17, Jaromir Coufal wrote: >> On 2013/10/12 23:09, Robert Collins wrote: > The 'easiest' way is to support bigger companies with huge deployments, tailored infrastructure, everything connected properly. >>

Re: [openstack-dev] [Nova] [Neutron] How do we know a host is ready to have servers scheduled onto it?

On 12/12/2013 11:02 AM, Clint Byrum wrote: So I'm asking, is there a standard way to determine whether or not a nova-compute is definitely ready to have things scheduled on it? This can be via an API, or even by observing something on the nova-compute host itself. I just need a definitive signal

Re: [openstack-dev] Incubation Request for Barbican

From: Bryan D. Payne [mailto:bdpa...@acm.org] Sent: 12 December 2013 16:12 To: OpenStack Development Mailing List (not for usage questions) Cc: openstack...@lists.openstack.org; cloudkeep@googlegroups. com; barbi...@lists.rackspace.com Subject: Re: [openstack-dev] Incubation Request for Barbican

[openstack-dev] [Neutron][IPv6] Agenda for the meeting today

The agenda for today is pretty light - if there is anything that people would like to discuss, please feel free to add. https://wiki.openstack.org/wiki/Meetings/Neutron-IPv6-Subteam#Agenda_for_Dec_12._2013 -- Sean M. Collins ___ OpenStack-dev mailing l

Re: [openstack-dev] [Nova] [Neutron] How do we know a host is ready to have servers scheduled onto it?

On 12/12/13 17:19, Chris Friesen wrote: On 12/12/2013 11:02 AM, Clint Byrum wrote: So I'm asking, is there a standard way to determine whether or not a nova-compute is definitely ready to have things scheduled on it? This can be via an API, or even by observing something on the nova-compute hos

Re: [openstack-dev] Unified Guest Agent proposal

Clint, Kevin, Thanks for reassuring me :-) I just wanted to make sure that having direct access from VMs to a single facility is not a dead end in terms of security and extensibility. And since it is not, I agree it is much simpler (and hence better) than hypervisor-dependent design. Then return

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

On Thu, Dec 12, 2013 at 8:50 AM, Adam Young wrote: > On 12/11/2013 10:11 PM, Paul Belanger wrote: > >> On 13-12-11 11:18 AM, Lyle, David wrote: >> >>> +1 on moving the domain admin role rules to the default policy.json >>> >>> -David Lyle >>> >>> From: Dolph Mathews [mailto:dolph.math...@gmail.co

Re: [openstack-dev] [TripleO][Tuskar] Icehouse Requirements

On 12/12/13 09:42 +1300, Robert Collins wrote: On 12 December 2013 01:17, Jaromir Coufal wrote: On 2013/10/12 23:09, Robert Collins wrote: The 'easiest' way is to support bigger companies with huge deployments, tailored infrastructure, everything connected properly. But there are tons of co

Re: [openstack-dev] Unified Guest Agent proposal

Vladik, Thanks for the suggestion, but hypervisor-dependent solution is exactly what scares off people in the thread :-) Thanks, Dmitry 2013/12/11 Vladik Romanovsky > > Maybe it will be useful to use Ovirt guest agent as a base. > > http://www.ovirt.org/Guest_Agent > https://github.com/oVir

Re: [openstack-dev] [Nova] [Neutron] How do we know a host is ready to have servers scheduled onto it?

Excerpts from Chris Friesen's message of 2013-12-12 09:19:42 -0800: > On 12/12/2013 11:02 AM, Clint Byrum wrote: > > > So I'm asking, is there a standard way to determine whether or not a > > nova-compute is definitely ready to have things scheduled on it? This > > can be via an API, or even by ob

Re: [openstack-dev] [Nova] [Neutron] How do we know a host is ready to have servers scheduled onto it?

Excerpts from Russell Bryant's message of 2013-12-12 09:09:04 -0800: > On 12/12/2013 12:02 PM, Clint Byrum wrote: > > I've been chasing quite a few bugs in the TripleO automated bring-up > > lately that have to do with failures because either there are no valid > > hosts ready to have servers sched

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

On 12/11/2013 11:47 PM, Mike Perez wrote: On 10:06 Thu 12 Dec , Christopher Yeoh wrote: On Thu, Dec 12, 2013 at 8:59 AM, Doug Hellmann mailto:doug.hellm...@dreamhost.com>>wrote: On Wed, Dec 11, 2013 at 3:41 PM, Ryan Petrello < ryan.petre...@dreamhost.com

[openstack-dev] [neutron] [third-party-testing] Meeting Minutes for our first meeting

Hi everyone: We had a meeting around Neutron Third-Party testing today on IRC. The logs are available here [1]. We plan to host another meeting next week, and it will be at 2200 UTC on Wednesday in the #openstack-meeting-alt channel on IRC. Please attend and update the etherpad [2] with any items

Re: [openstack-dev] [Nova] [Neutron] How do we know a host is ready to have servers scheduled onto it?

On 12/12/2013 12:36 PM, Clint Byrum wrote: Excerpts from Russell Bryant's message of 2013-12-12 09:09:04 -0800: On 12/12/2013 12:02 PM, Clint Byrum wrote: I've been chasing quite a few bugs in the TripleO automated bring-up lately that have to do with failures because either there are no valid

Re: [openstack-dev] Unified Guest Agent proposal

Excerpts from Dmitry Mescheryakov's message of 2013-12-12 09:24:13 -0800: > Clint, Kevin, > > Thanks for reassuring me :-) I just wanted to make sure that having direct > access from VMs to a single facility is not a dead end in terms of security > and extensibility. And since it is not, I agree i

Re: [openstack-dev] [Nova] [Neutron] How do we know a host is ready to have servers scheduled onto it?

On Dec 12, 2013, at 11:44 AM, Jay Pipes wrote: > On 12/12/2013 12:36 PM, Clint Byrum wrote: >> Excerpts from Russell Bryant's message of 2013-12-12 09:09:04 -0800: >>> On 12/12/2013 12:02 PM, Clint Byrum wrote: I've been chasing quite a few bugs in the TripleO automated bring-up lately t

Re: [openstack-dev] Introducing the new OpenStack service for Containers

Hi all, Was wondering if there's been any more work done on the proposed Container-Service (Capsule?) API? Haven't seen much on the ML on this, so just want to make sure the current plan is still to have a draft of the Capsule API, compare the delta to the existing Nova API, and determine whether

Re: [openstack-dev] Stackalytics 0.4 released!

Hello , On Thu, Dec 12, 2013 at 10:11 PM, Monty Taylor wrote: > > > On 12/12/2013 04:49 PM, Ilya Shakhat wrote: >> Hello everyone! >> >> Stackalytics team is happy to announce the release of version 0.4. This >> release is completely dedicated to different types of reports. We added >> highly dem

Re: [openstack-dev] [Nova] [Neutron] How do we know a host is ready to have servers scheduled onto it?

On 12/12/2013 12:53 PM, Kyle Mestery wrote: On Dec 12, 2013, at 11:44 AM, Jay Pipes wrote: On 12/12/2013 12:36 PM, Clint Byrum wrote: Excerpts from Russell Bryant's message of 2013-12-12 09:09:04 -0800: On 12/12/2013 12:02 PM, Clint Byrum wrote: I've been chasing quite a few bugs in the Trip

Re: [openstack-dev] Unified Guest Agent proposal

On 12/10/2013 03:49 PM, Ian Wells wrote: On 10 December 2013 20:55, Clint Byrum mailto:cl...@fewbar.com>> wrote: If it is just a network API, it works the same for everybody. This makes it simpler, and thus easier to scale out independently of compute hosts. It is also something we a

Re: [openstack-dev] State of the Gate - Dec 12

On 12/12/2013 7:20 AM, Sean Dague wrote: Current Gate Length: 12hrs*, 41 deep (top of gate entered 12hrs ago) It's been an *exciting* week this week. For people not paying attention we had 2 external events which made things terrible earlier in the week. == Event 1: s

Re: [openstack-dev] [Keystone] policy has no effect because of hard coded assert_admin?

The policy file is protecting v3 API calls at the controller layer, but you're calling the v2 API. The policy decorators should be moved to the manager layer to protect both APIs equally... but we'd have to be very careful not to break deployments depending on the trivial "assert_admin" behavior (h

Re: [openstack-dev] How to best make User Experience a priority in every project

On Wed, Dec 11, 2013 at 4:25 PM, Stefano Maffulli wrote: > On 12/06/2013 02:19 AM, Jaromir Coufal wrote: > > We are growing. At the moment we are 4 core members and others are > > coming in. But honestly, contributors are not coming to specific > > projects - they go to reach UX community in a sen

Re: [openstack-dev] [Nova] [Neutron] How do we know a host is ready to have servers scheduled onto it?

Excerpts from Kyle Mestery's message of 2013-12-12 09:53:57 -0800: > On Dec 12, 2013, at 11:44 AM, Jay Pipes wrote: > > On 12/12/2013 12:36 PM, Clint Byrum wrote: > >> Excerpts from Russell Bryant's message of 2013-12-12 09:09:04 -0800: > >>> On 12/12/2013 12:02 PM, Clint Byrum wrote: > I've

Re: [openstack-dev] [Keystone] policy has no effect because of hard coded assert_admin?

As Dolph stated, V3 is where the policy file protects.  This is one of the many reasons why I would encourage movement to using V3 Keystone over V2. The V2 API is officially deprecated in the Icehouse cycle, I think that moving the decorator potentially could cause more issues than not as stated

Re: [openstack-dev] Performance Regression in Neutron/Havana compared to Quantum/Grizzly

Hello Salvatore, Thanks for your feedback. Does the patch https://review.openstack.org/#/c/57420/ which you are working on bug https://bugs.launchpad.net/neutron/+bug/1253993 will help to correct the OVS agent loop slowdown issue? Does this patch address the DHCP agent updating the host file onc

Re: [openstack-dev] Unified Guest Agent proposal

Excerpts from Jay Pipes's message of 2013-12-12 10:15:13 -0800: > On 12/10/2013 03:49 PM, Ian Wells wrote: > > On 10 December 2013 20:55, Clint Byrum > > wrote: > > > > If it is just a network API, it works the same for everybody. This > > makes it simpler, and thu

Re: [openstack-dev] [Nova] cross-project bug fixes

On Thursday, December 12, 2013 10:29:11 AM, Russell Bryant wrote: On 12/12/2013 11:21 AM, Hamilton, Peter A. wrote: I am in the process of getting a bug fix approved for a bug found in openstack.common: https://review.openstack.org/#/c/60500/ The bug is present in both nova and cinder. The

Re: [openstack-dev] State of the Gate - Dec 12

On Thu, Dec 12, 2013 at 7:19 PM, Matt Riedemann wrote: > > > On 12/12/2013 7:20 AM, Sean Dague wrote: > >> Current Gate Length: 12hrs*, 41 deep >> >> (top of gate entered 12hrs ago) >> >> It's been an *exciting* week this week. For people not paying attention >> we had 2 external events which made

Re: [openstack-dev] Stackalytics 0.4 released! [metrics]

On 12/12/2013 07:49 AM, Ilya Shakhat wrote: > Stackalytics team is happy to announce the release of version 0.4. [...] Good job Ilya, congratulations on the release. I may not be able to join the meeting (too early for me) so I leave here some feedback for you. I like the new punchcards in the pe

Re: [openstack-dev] Unified Guest Agent proposal

On 12 December 2013 19:48, Clint Byrum wrote: > Excerpts from Jay Pipes's message of 2013-12-12 10:15:13 -0800: > > On 12/10/2013 03:49 PM, Ian Wells wrote: > > > On 10 December 2013 20:55, Clint Byrum > > > wrote: > > I've read through this email thread with quite a bit

Re: [openstack-dev] [Solum] Plan files and resources

- Original Message - > > > On Dec 11, 2013, at 4:45 PM, "Clayton Coleman" wrote: > > - Original Message - > >> Devdatta, > >> > >> On Dec 10, 2013, at 12:37 PM, devdatta kulkarni > >> wrote: > >> > >>> Hi Adrian, > >>> > >>> Thanks for creating https://etherpad.openstack.org

Re: [openstack-dev] [Neutron][IPv6] Agenda for the meeting today

Can we go over the use cases for the multiple different address allocation techniques, per my comment on the blueprint that suggests we expose different dnsmasq modes? And perhaps also what we're going to do with routers in terms of equivalent behaviour for the current floating-ip versus no-floati

[openstack-dev] [Tempest][Production] Tempest / the gate / real world load

A few times now we've run into patches for devstack-gate / devstack that change default configuration to handle 'tempest load'. For instance - https://review.openstack.org/61137 (Sorry Salvatore I'm not picking on you really!) So there appears to be a meme that the gate is particularly stressful

[openstack-dev] [barbican] Meeting Today at 20:00 UTC (2 Central)

The barbican meeting today will cover our progress on the incubation issues brought up by the TC, test planning and any other issues. If you are interested in barbican and have questions, stop on by #openstack-meeting-alt in 20 minutes. Thanks, -- Jarret Raim @jarretraim smime.p7s Descr

Re: [openstack-dev] Unified Guest Agent proposal

Dmitry, I understand that :) The only hypervisor dependency it has is how it communicates with the host, while this can be extended and turned into a binding, so people could connect to it in multiple ways. The real value, as I see it, is which features this guest agent already implements and

[openstack-dev] [Nova] New official bugtag 'Ironic' ?

We have official tags for most of the hypervisors, but not "ironic" as yet - any objections to adding one? -Rob -- Robert Collins Distinguished Technologist HP Converged Cloud ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://li

Re: [openstack-dev] [Nova] New official bugtag 'Ironic' ?

On 12/12/2013 03:03 PM, Robert Collins wrote: > We have official tags for most of the hypervisors, but not "ironic" as > yet - any objections to adding one? Nope, go ahead. For reference, to add it we need to: 1) Make it an official tag in launchpad 2) Update https://wiki.openstack.org/wiki/Bug

Re: [openstack-dev] [Nova] [Neutron] How do we know a host is ready to have servers scheduled onto it?

On 12/12/2013 12:35 PM, Clint Byrum wrote: > Excerpts from Chris Friesen's message of 2013-12-12 09:19:42 -0800: >> On 12/12/2013 11:02 AM, Clint Byrum wrote: >> >>> So I'm asking, is there a standard way to determine whether or not a >>> nova-compute is definitely ready to have things scheduled on

  1   2   >