Re: [openstack-dev] Unified Guest Agent proposal

Why the notifications couldn't be handled by Marconi ? That would be up to Marconi's team to handle security issues while it is part of their mission statement to deliver a messaging service in between VMs. Le 12 déc. 2013 22:09, "Fox, Kevin M" a écrit : > Yeah, I think the extra nic is unnecess

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

On Tue, Dec 10, 2013 at 3:59 PM, Julien Danjou wrote: > > Please Julien correct me if I'm wrong. And maybe Ceilometer has > > recommendations for production deployment and I just missed it? > > There's no recommendation per-say, except what we added on the > documentation so far. For reference,

Re: [openstack-dev] Announcing Fuel

On 13 December 2013 03:31, Mike Scherbakov wrote: > 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 prov

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

On 13 December 2013 06:24, Will Foster wrote: > I just wanted to add a few thoughts: Thank you! > For some comparative information here "from the field" I work > extensively on deployments of large OpenStack implementations, > most recently with a ~220node/9rack deployment (scaling up to 42rack

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

On 13 December 2013 10:05, Jay Dobies wrote: >> Maybe this is a valid use case? > You mention three specific nodes, but what you're describing is more likely > three concepts: > - Balanced Nodes > - High Disk I/O Nodes > - Low-End Appliance Nodes > > They may have one node in each, but I think yo

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

On 13 December 2013 06:13, Keith Basil wrote: > On Dec 11, 2013, at 3:42 PM, Robert Collins wrote: >>> My question is - can't we help them now? To enable users to use our app even >>> when we don't have enough smartness to help them 'auto' way? >> >> I understand the question: but I can't answer

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

On 13 December 2013 05:35, Keith Basil wrote: > On Dec 10, 2013, at 5:09 PM, Robert Collins wrote: unallocated | aqvailable | undeployed >>> >>> +1 unallocated >> >> I think available is most accurate, but undeployed works too. I really >> don't like unallocated, sorry! > > Woul

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

On Fri, Dec 13, 2013 at 2:40 AM, Morgan Fainberg wrote: > 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

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] [TripleO][Tuskar] Terminology

On 12 December 2013 21:59, Jaromir Coufal wrote: > 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 ma

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

On Fri, Dec 13, 2013 at 4:12 AM, Jay Pipes wrote: > 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 >>> >> >wrote: >>> >>> On Wed, Dec 11, 201

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

On Fri, Dec 13, 2013 at 8:12 AM, Jonathan LaCour < jonathan-li...@cleverdevil.org> wrote: > > On December 11, 2013 at 2:34:07 PM, Doug Hellmann ( > doug.hellm...@dreamhost.com) wrote: > > > On Wed, Dec 11, 2013 at 3:41 PM, Ryan Petrello wrote: > > > > > 1. It looks like the Nova v3 API is composed

Re: [openstack-dev] [Cinder] Cloning vs copying images

All, I'd like to ask the core reviewers to review both patch sets again since they are now basically the same. I'd like to see either merged so the bug cane closed and improve cinder (and ceph). We can simply determine preference by votes. Thanks Andrew Woodward Mirantis On Fri, Dec 6, 2013 at

Re: [openstack-dev] [Openstack] Friday Dec 20th - Doc Bug Day

Reminder: Friday next week - Doc Bug Day. Current number of doc bugs: 505 On 22/11/13 11:27, Tom Fifield wrote: > All, > > This month, docs reaches 500 bugs, making it the 2nd-largest project by > bug count in all of OpenStack. Yes, it beats Cinder, Horizon, Swift, > Keystone and Glance, and wil

Re: [openstack-dev] [trove] configuration groups and datastores type/versions

Another Example: Datastore Type | Version - MySQL 5.5 | 5.5.35 MySQL 5.5 | 5.5.20 MySQL 5.6 | 5.6.15 A user creates a MySQL 5.5 configuration-group that merely consists of a innodb_buff

[openstack-dev] [Swift] Release of Swift 1.11.0

I'm happy to announce that we've released Swift 1.11.0. You can find the high-level Launchpad details (including a link to the tarball) at https://launchpad.net/swift/icehouse/1.11.0. As always, you can upgrade to this release without any downtime to your users. Swift 1.11.0 is the work of 26 con

[openstack-dev] [neutron] [policy] Policy-group relationship

Continuing the discussion we had earlier today during the Neutron Group Policy weekly meeting [0], I would like to initiate a couple of email threads and follow up on a couple of important issues we need to agree on so we can move forward. In this email thread, I would like to discuss the policy-g

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

Hi 2) UNDEPLOYED NODE - a node that has not been deployed with an instance > > Other suggestions included UNASSIGED, UNMAPPED, FREE, and AVAILABLE. > Some people (I'm one of them) > find AVAILABLE to be a bit of an overloaded term, as it can also be > construed to mean that, say, > a service ins

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

Hi So the idea wasn't the you create a domain with the id of 'domain_admin_id', rather that you create the domain that you plan to use for your admin domain, and then paste its (auto-generated) domain_id into the policy file. Henry On 12 Dec 2013, at 03:11, Paul Belanger wrote: > On 13-12-11

Re: [openstack-dev] Incubation Request for Barbican

On December 12, 2013 at 14:32:36, Dolph Mathews (dolph.math...@gmail.com) wrote: On Thu, Dec 12, 2013 at 2:58 PM, Adam Young  wrote: On 12/04/2013 08:58 AM, Jarret Raim wrote: While I am all for adding a new program, I think we should only add one if we rule out all existing programs as a home.

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

Mathieu, Here are my results for running the unit tests for the agents. I ran `tox -e cover neutron.tests.unit.openvswitch.test_ovs_neutron_agent` at 3b4233873539bad62d202025529678a5b0add412 with the following result: Name Stmts Miss

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

On Thu, Dec 12, 2013 at 12:40 PM, Morgan Fainberg wrote: > 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 th

Re: [openstack-dev] [bugs] definition of triaged

On Thu, Dec 12, 2013 at 3:46 PM, Robert Collins wrote: > Hi, I'm trying to overhaul the bug triage process for nova (initially) > to make it much lighter and more effective. > > I'll be sending a more comprehensive mail shortly but one thing that > has been giving me pause is this: > " > Confirmed

Re: [openstack-dev] Announcing Fuel

Mike, It's great that we are continuing to align fuel with TripleO. I've been toying with the idea of using TripleO components and CEPH to enhance our CI infra for a while now, and this announcement has encouraged me to write it down. I've proposed a BP for "Super fast deploy CI" that would help u

Re: [openstack-dev] Incubation Request for Barbican

On Thu, Dec 12, 2013 at 2:58 PM, Adam Young wrote: > On 12/04/2013 08:58 AM, Jarret Raim wrote: > > While I am all for adding a new program, I think we should only add one > if we > rule out all existing programs as a home. With that in mind why not add > this > to the keystone program? Perhap

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

> From: Russell Bryant > We can involve people in security reviews without having them on the > core review team. They are separate concerns. As I noted in my original mail, this was my primary concern. I just didn't want "not core" to stand in the way of "is appropriate to provide security rev

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

On 12/12/2013 04:25 PM, Keith Basil wrote: On Dec 12, 2013, at 4:05 PM, Jay Dobies wrote: Maybe this is a valid use case? Cloud operator has several core service nodes of differing configuration types. [node1] <-- balanced mix of disk/cpu/ram for general core services [node2] <-- lots of

Re: [openstack-dev] Unified Guest Agent proposal

On 12/12/2013 02:19 PM, Clint Byrum wrote: Excerpts from Steven Dake's message of 2013-12-12 12:32:55 -0800: On 12/12/2013 10:24 AM, Dmitry Mescheryakov wrote: 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

[openstack-dev] [bugs] definition of triaged

Hi, I'm trying to overhaul the bug triage process for nova (initially) to make it much lighter and more effective. I'll be sending a more comprehensive mail shortly but one thing that has been giving me pause is this: " Confirmed The bug was reproduced or confirmed as a genuine bug Triaged The bug

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

On December 11, 2013 at 2:34:07 PM, Doug Hellmann (doug.hellm...@dreamhost.com) wrote: > On Wed, Dec 11, 2013 at 3:41 PM, Ryan Petrello wrote: >  > > 1. It looks like the Nova v3 API is composed *entirely* of > > extensions (including “core” API calls), and that extensions and > > their routes a

Re: [openstack-dev] [Solum] Using Zuul in the Git-pull blueprint

We followed on the Zuul question in this week's git-integration working group meeting. mordred has created an etherpad with a high-level description of Zuul and how it might fit with Solum't git integration workflow https://etherpad.openstack.org/p/ZuulSolum The working group seemed to be comi

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

Thanks for all the replies so far! Let me try and distill the thread down to the points of interest and contention: 1) NODE vs INSTANCE This is a distinction that Robert brings up, and I think it's a good one that people agree with. The various ROLES can apply to either. What isn't clear to

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

On Dec 12, 2013, at 4:05 PM, Jay Dobies wrote: >> Maybe this is a valid use case? >> >> Cloud operator has several core service nodes of differing configuration >> types. >> >> [node1] <-- balanced mix of disk/cpu/ram for general core services >> [node2] <-- lots of disks for Ceilometer data s

Re: [openstack-dev] Unified Guest Agent proposal

Excerpts from Steven Dake's message of 2013-12-12 12:32:55 -0800: > On 12/12/2013 10:24 AM, Dmitry Mescheryakov wrote: > > 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 se

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

On Thu, Dec 12, 2013 at 3:17 PM, Mike Perez wrote: > On 10:06 Thu 12 Dec , Christopher Yeoh wrote: > > On Thu, Dec 12, 2013 at 8:59 AM, Doug Hellmann > > wrote: > > > > So for compatibility testing I think what will probably happen is that > > we'll be defining a minimum set (API_V3_CORE_EXTE

Re: [openstack-dev] [Ironic] firmware security

On Thu, Dec 12, 2013 at 12:50 AM, Lu, Lianhao wrote: > 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 > t

Re: [openstack-dev] Unified Guest Agent proposal

Yeah, I think the extra nic is unnecessary too. There already is a working route to 169.254.169.254, and a metadata proxy -> server running on it. So... lets brainstorm for a minute and see if there are enough pieces already to do most of the work. We already have: * An http channel out from

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

Maybe this is a valid use case? Cloud operator has several core service nodes of differing configuration types. [node1] <-- balanced mix of disk/cpu/ram for general core services [node2] <-- lots of disks for Ceilometer data storage [node3] <-- low-end "appliance like" box for a specialized/c

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

Maybe time to revive something like: https://review.openstack.org/#/c/12759/ >From experience, all sites (and those internal to yahoo) provide a /status (or equivalent) that is used for all sorts of things (from basic load-balancing up/down) to other things like actually introspecting the state

Re: [openstack-dev] Incubation Request for Barbican

On 12/04/2013 08:58 AM, Jarret Raim wrote: While I am all for adding a new program, I think we should only add one if we rule out all existing programs as a home. With that in mind why not add this to the keystone program? Perhaps that may require a tweak to keystones mission statement, but that

Re: [openstack-dev] Unified Guest Agent proposal

On 12/12/2013 10:24 AM, Dmitry Mescheryakov wrote: 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

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

On 12/12/2013 01:36 PM, Clint Byrum wrote: > 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/

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

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

[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] 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] [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

[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

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

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] 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] 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] 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] [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] 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] 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] [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] [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] 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] [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] 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] 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] [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] 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] 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] [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] 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 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

[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] 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

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] [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] 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] [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

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] [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

[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] 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

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] [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 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

[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] 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

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] 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] [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] 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] [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

[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

[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

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

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] 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] [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

[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] [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

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] 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] [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

  1   2   >