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

On 2013/06/12 21:26, Tzu-Mainn Chen wrote: * can be allocated as one of four node types It's pretty clear by the current verbiage but I'm going to ask anyway: "one and only one"? Yep, that's right! Confirming. One and only one. My gut reaction is that we want to bite this off sooner rather

[openstack-dev] [Mistral] Community meeting agenda - 12/09/2013

Hi, We’re inviting everyone to participate our community meeting at #openstack-meeting today at 16.00 UTC. Here’s the link to meeting agenda: https://wiki.openstack.org/wiki/Meetings/MistralAgenda Thanks! Renat Akhmerov @ Mirantis Inc. ___ OpenSt

[openstack-dev] [climate] IRC meeting reschedule exceptionnally today

Hi Dina, Forwarding your request to openstack-dev@ as everyone needs to be aware of that. Which time do you propose for meeting us today ? On my side, I'll be travelling tomorrow and the day after, I'll be out of office with limited access, so we need to sync up today. I can propose 2000 UTC

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

On 2013/06/12 22:55, Matt Wagner wrote: - As an infrastructure administrator, Anna wants to review the distribution of the nodes that she has assigned before kicking off the "Deploy" task. What does she expect to see here on the review screen that she didn't see on the previous screens, if anyt

Re: [openstack-dev] [climate] IRC meeting reschedule exceptionnally today

I think it's ok, but not more than a half of hour On Monday, December 9, 2013, Sylvain Bauza wrote: > Hi Dina, > Forwarding your request to openstack-dev@ as everyone needs to be aware > of that. > > Which time do you propose for meeting us today ? On my side, I'll be > travelling tomorrow a

Re: [openstack-dev] [climate] IRC meeting reschedule exceptionnally today

Well, I wouldn't say more, I also have family concerns ;-) I will prepare the meeting by checking all individual actions, so I will only raise the left ones. Hooks clarification can be postponed to the next meeting or discussed directly on chan. I saw you made a first pass on triaging bluepri

Re: [openstack-dev] [climate] IRC meeting reschedule exceptionnally today

Ok, we'll discuss :) On Monday, December 9, 2013, Sylvain Bauza wrote: > Well, I wouldn't say more, I also have family concerns ;-) > > I will prepare the meeting by checking all individual actions, so I will > only raise the left ones. > Hooks clarification can be postponed to the next meeting

Re: [openstack-dev] [Oslo] Layering olso.messaging usage of config

On 06/12/13 15:05 +, Mark McLoughlin wrote: On Fri, 2013-12-06 at 15:41 +0100, Julien Danjou wrote: On Fri, Dec 06 2013, Mark McLoughlin wrote: Hi Mark, > If the goal is "allow applications to use oslo.messaging without using > oslo.config", then what's driving this? I'm guessing some poss

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

On 2013/07/12 02:20, Robert Collins wrote: - As an infrastructure administrator, Anna needs to assign a role to each of the necessary nodes in her OpenStack deployment. The nodes could be either controller, compute, networking, or storage resources depending on the needs of this deployment.

[openstack-dev] [qa][Neutron] grenade fails due to iso8601 version mismatch

Hi, A patch in neutronclient [1] which updates iso8601 requirement to 0.1.8 fails with grenade due to iso8601 version mismatch [2]. (It blocks the patch for a month.) The error occurs in old devstack (i.e., grizzly devstack). I I see both iso8601 requirements of 0.1.4 and 0.1.8 in devstack log. I

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

On 2013/07/12 01:59, Robert Collins wrote: * Creation * Manual registration * hardware specs from Ironic based on mac address (M) Ironic today will want IPMI address + MAC for each NIC + disk/cpu/memory stats For registration it is just Management MAC address which is need

[openstack-dev] [Neutron] Assigning a floating IP to an internal network

Hi all, The extra route extension allows setting up an hierarchical network topology where there is a compute instance or an internal router that separates an internal network from an external router. Traffic can be routed by using extra routes on the external router, however, it is not possible t

Re: [openstack-dev] [Neutron] DHCP Agent Reliability

On Mon, Dec 09, 2013 at 08:43:59AM +1300, Robert Collins wrote: > On 9 December 2013 01:43, Maru Newby wrote: > > > > >>> If AMQP service is set up not to lose notification, notifications will be > >>> piled up > >>> and stress AMQP service. I would say single node failure isn't > >>> catastr

Re: [openstack-dev] [heat] [glance] Heater Proposal

Vishvananda Ishaya wrote: > On Dec 6, 2013, at 10:07 AM, Georgy Okrokvertskhov > mailto:[email protected]>> wrote: > >> I am really inspired by this thread. Frankly saying, Glance for Murano >> was a kind of sacred entity, as it is a service with a long history in >> OpenStack. We even

Re: [openstack-dev] [climate] IRC meeting reschedule exceptionnally today

Time is ok for me too. @Sylvain, IMO policies could not be high prioritized when nothing else really completed and their support doesn't blocks main functionality. It'll be great to have them in 0.1, but I think that it's a nice to have for 0.1. Thanks. On Mon, Dec 9, 2013 at 1:46 PM, Dina Belo

[openstack-dev] [heat] Core criteria, review stats vs reality

Hi all, So I've been getting concerned about $subject recently, and based on some recent discussions so have some other heat-core folks, so I wanted to start a discussion where we can agree and communicate our expectations related to nomination for heat-core membership (becuase we do need more cor

[openstack-dev] [Horizon] Less compiler dependency

Hey all Horizoners, This is last time I am trying to bring this concern up (well at least last time for a while :)). But... Watching latest progress with updating Bootstrap to v3 and dealing with compiling issues, I am more and more concerned about dependency on lesscpy. Currently the librar

Re: [openstack-dev] [heat] Core criteria, review stats vs reality

Steven Hardy wrote: > [...] > The issues I have are: > - Russell's stats (while very useful) are being used by some projects as > the principal metric related to -core membership (ref TripleO's monthly > cull/name&shame, which I am opposed to btw). This is in some cases > encouraging some st

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

On 12/09/2013 11:56 AM, Jaromir Coufal wrote: On 2013/07/12 01:59, Robert Collins wrote: * Monitoring * assignment, availability, status * capacity, historical statistics (M) Why is this under 'nodes'? I challenge the idea that it should be there. We will need to surface som

Re: [openstack-dev] [qa][tempest] Bug triage and monitoring process

Hi, > -Original Message- > From: Adalberto Medeiros [mailto:[email protected]] > Sent: Friday, December 06, 2013 11:18 PM > To: OpenStack Development Mailing List > Subject: [openstack-dev] [qa][tempest] Bug triage and monitoring process > > Hello all! > > Yesterday, during the

Re: [openstack-dev] [qa][keystone] Keystoneclient tests to tempest

On Sun, Dec 8, 2013 at 5:20 PM, Monty Taylor wrote: > Hi! > > Thanks - I've been wanting to kill this for a long time. Thanks for > starting the discussion... > > On 12/08/2013 07:26 PM, Brant Knudson wrote: > > > > We'd like to get the keystoneclient tests out of keystone. They're > > serving a

[openstack-dev] Not able to ping vm

Hi all, I deployed single node openstack with one NIC card on centos by using redhat packstack quickstart guide, but I am not able to configure network. So please anybody can help me...!!! Thanks & Regards, MArdan ___ OpenStack-dev mailing list

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

Mainn, Thanks for pulling this together. > * NODES >* Management node (where triple-o is installed) >* created as part of undercloud install process I think getting the undercloud installed/deployed should be a requirement for Icehouse. I'm not sure if you meant that or were assumin

[openstack-dev] [oslo][neutron] Post-mortem debugging for tests?

Are any other projects interested in adding back the post-mortem debugging support we lost in the move away from nose? I have a patch in review for neutron and salv-orlando asked whether oslo might be the better place for it. https://review.openstack.org/#/c/43776/ m.

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

On Fri, Dec 6, 2013 at 4:55 PM, Matt Wagner wrote: >> - As an infrastructure administrator, Anna expects that the >> management node for the deployment services is already up and running >> and the status of this node is shown in the UI. > > The 'management node' here is the undercloud node that A

Re: [openstack-dev] [Ceilometer] Compute meter names prefaced by "instance:"

On Fri, Dec 06 2013, Pendergrass, Eric wrote: > Hi, I've been out for nearly 3 weeks and noticed Compute meter names are now > prefaced by "instance:" > > > > http://docs.openstack.org/developer/ceilometer/measurements.html > > > > Not sure when this happened but I was wondering if the chang

Re: [openstack-dev] [oslo][neutron] Post-mortem debugging for tests?

Maru: Agree with your assumption about moving this ti oslo, but good luck in communicating with other groups in a timely manner. Also, other project handle the screen a little differently that what I've experienced on the server side, e.g. python-neutronclient. On Mon, Dec 9, 2013 at 7:02 AM, Mar

Re: [openstack-dev] Not able to ping vm

On 12/09/2013 08:38 AM, Mardan Raghuwanshi wrote: > I deployed single node openstack with one NIC card on centos by using > redhat packstack quickstart guide, but I am not able to configure > network. So please anybody can help me...!!! I'm sorry to hear you're having trouble. This mailing list

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

Greetings, As $subject mentions, I'd like to start discussing the support for AMQP 1.0[0] in oslo.messaging. We already have rabbit and qpid drivers for earlier (and different!) versions of AMQP, the proposal would be to add an additional driver for a _protocol_ not a particular broker. (Both Rab

Re: [openstack-dev] [Solum] [Security]

- Original Message - > I created some relatively high level security best practices that I > thought would apply to Solum. I don't think it is ever too early to get > mindshare around security so that developers keep that in mind throughout > the project. When a design decision point co

Re: [openstack-dev] [qa][keystone] Keystoneclient tests to tempest

Monty - Thanks for doing the work already to get the infrastructure set up. Looks like I've got the easy part here. I posted an initial patch that has one test from keystone in https://review.openstack.org/#/c/60724/ . I hope to be able to move all the tests over unchanged. The tricky part is gett

Re: [openstack-dev] [heat] Core criteria, review stats vs reality

On 12/09/2013 07:43 AM, Thierry Carrez wrote: > Steven Hardy wrote: >> [...] >> The issues I have are: >> - Russell's stats (while very useful) are being used by some projects as >> the principal metric related to -core membership (ref TripleO's monthly >> cull/name&shame, which I am opposed to

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

On Dec 9, 2013, at 4:29 AM, Jaromir Coufal wrote: > > On 2013/06/12 22:55, Matt Wagner wrote: >>> - As an infrastructure administrator, Anna wants to review the >>> distribution of the nodes that she has assigned before kicking off >>> the "Deploy" task. >> What does she expect to see here on t

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

On Dec 9, 2013, at 4:57 AM, Jaromir Coufal wrote: > > On 2013/07/12 02:20, Robert Collins wrote: >>> - As an infrastructure administrator, Anna needs to assign a role to each >>> of the necessary nodes in her OpenStack deployment. The nodes could be >>> either controller, compute, networking,

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

On 06/12/13 04:31, Tzu-Mainn Chen wrote: > Hey all, > > I've attempted to spin out the requirements behind Jarda's excellent > wireframes > (http://lists.openstack.org/pipermail/openstack-dev/2013-December/020944.html). > Hopefully this can add some perspective on both the wireframes and the nee

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

On Dec 9, 2013, at 8:58 AM, James Slagle wrote: > On Fri, Dec 6, 2013 at 4:55 PM, Matt Wagner wrote: >>> - As an infrastructure administrator, Anna expects that the >>> management node for the deployment services is already up and running >>> and the status of this node is shown in the UI. >>

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

On Dec 6, 2013, at 8:20 PM, Robert Collins wrote: > On 7 December 2013 09:31, Liz Blanchard wrote: >> This list is great, thanks very much for taking the time to write this up! I >> think a big part of the User Experience design is to take a step back and >> understand the requirements from a

Re: [openstack-dev] [keystone] Service scoped role definition

Thanks David, Let me update the etherpad with this proposal. Arvind -Original Message- From: David Chadwick [mailto:[email protected]] Sent: Friday, December 06, 2013 2:44 AM To: Tiwari, Arvind; Adam Young; OpenStack Development Mailing List (not for usage questions) Cc: Henry Na

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

On 07/12/13 04:42, Tzu-Mainn Chen wrote: >> On 7 December 2013 08:15, Jay Dobies wrote: >>> Disclaimer: I'm very new to the project, so apologies if some of my >>> questions have been already answered or flat out don't make sense. >> >> >> NP :) >> >> * optional node profile for

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

I believe we are still 'fighting' here with two approaches and I believe we need both. We can't only provide a way 'give us resources we will do a magic'. Yes this is preferred way - especially for large deployments, but we also need a fallback so that user can say - no, this node doesn't belong t

Re: [openstack-dev] [qa][keystone] Keystoneclient tests to tempest

On 12/09/2013 10:12 AM, Brant Knudson wrote: > Monty - > > Thanks for doing the work already to get the infrastructure set up. > Looks like I've got the easy part here. I posted an initial patch that > has one test from keystone in https://review.openstack.org/#/c/60724/ . > I hope to be able to m

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

On 12/09/2013 10:05 AM, Flavio Percoco wrote: > Greetings, > > As $subject mentions, I'd like to start discussing the support for > AMQP 1.0[0] in oslo.messaging. We already have rabbit and qpid > drivers for earlier (and different!) versions of AMQP, the proposal > would be to add an additional

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

On 12/06/2013 09:39 PM, Tzu-Mainn Chen wrote: Thanks for the comments and questions! I fully expect that this list of requirements will need to be fleshed out, refined, and heavily modified, so the more the merrier. Comments inline: *** Requirements are assumed to be targeted for Icehous

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

On 09/12/13 18:01, Jay Dobies wrote: >> I believe we are still 'fighting' here with two approaches and I believe >> we need both. We can't only provide a way 'give us resources we will do >> a magic'. Yes this is preferred way - especially for large deployments, >> but we also need a fallback so th

Re: [openstack-dev] [qa][Neutron] grenade fails due to iso8601 version mismatch

On 12/09/2013 05:16 AM, Akihiro Motoki wrote: > Hi, > > A patch in neutronclient [1] which updates iso8601 requirement to 0.1.8 > fails with grenade due to iso8601 version mismatch [2]. > (It blocks the patch for a month.) > > The error occurs in old devstack (i.e., grizzly devstack). > I I see b

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

> > - As an infrastructure administrator, Anna wants to be able to unallocate a > > node from a deployment. > > > Why? Whats her motivation. One plausible one for me is 'a machine > > > needs to be serviced so Anna wants to remove it from the deployment to > > > avoid causing user visible downti

Re: [openstack-dev] [oslo][neutron] Post-mortem debugging for tests?

On 2013-12-09 08:02, Maru Newby wrote: Are any other projects interested in adding back the post-mortem debugging support we lost in the move away from nose? I have a patch in review for neutron and salv-orlando asked whether oslo might be the better place for it. https://review.openstack.org/#

Re: [openstack-dev] [olso] [cinder] upgrade issues in lock_path in cinder after oslo utils sync

On 12/06/2013 05:40 PM, Ben Nemec wrote: > On 2013-12-06 16:30, Clint Byrum wrote: >> Excerpts from Ben Nemec's message of 2013-12-06 13:38:16 -0800: >>> >>> >>> On 2013-12-06 15:14, Yuriy Taraday wrote: >>> >>> > Hello, Sean. >>> > >>> > I get the issue with upgrade path. User doesn't want to upda

Re: [openstack-dev] [keystone] Service scoped role definition

Ack On 09/12/2013 15:54, Tiwari, Arvind wrote: > Thanks David, > > Let me update the etherpad with this proposal. > > Arvind > > -Original Message- > From: David Chadwick [mailto:[email protected]] > Sent: Friday, December 06, 2013 2:44 AM > To: Tiwari, Arvind; Adam Young; OpenSt

Re: [openstack-dev] [Nova][Schduler] Volunteers wanted for a modest proposal for an external scheduler in our lifetime

Hi All, Last couple of month Mirantis team was working on new scalable scheduler architecture. The main concept was proposed by Boris Pavlovic in the following blue print https://blueprints.launchpad.net/nova/+spec/no-db-scheduler and Alexey Ovchinnikov prepared a bunch of patches https://review.

Re: [openstack-dev] [qa][Neutron] grenade fails due to iso8601 version mismatch

Thanks for the clarification. After I posted the mail, I found the bug [1] due to the same cause and ongoing work. [1] https://bugs.launchpad.net/openstack-ci/+bug/1255419 jenkins tests fails for neutron/grizzly duo to iso8601 version requirement conflict On Tue, Dec 10, 2013 at 1:14 AM, Sean Dag

[openstack-dev] [Solum] Second working group meeting on language packs today

Hi, We will hold our second Git Integration working group meeting on IRC in #solum on Monday, December 9, 2013 1700 UTC / 0900 PST. Agenda for today's meeting: * Administrative: * Decide whether to continue this meeting at the same time in January * Topics:

Re: [openstack-dev] [olso] [cinder] upgrade issues in lock_path in cinder after oslo utils sync

Excerpts from Sean Dague's message of 2013-12-09 08:17:45 -0800: > On 12/06/2013 05:40 PM, Ben Nemec wrote: > > On 2013-12-06 16:30, Clint Byrum wrote: > >> Excerpts from Ben Nemec's message of 2013-12-06 13:38:16 -0800: > >>> > >>> > >>> On 2013-12-06 15:14, Yuriy Taraday wrote: > >>> > >>> > Hell

Re: [openstack-dev] Unified Guest Agent proposal

On Sat, Dec 7, 2013 at 11:09 PM, Monty Taylor wrote: > > > On 12/08/2013 07:36 AM, Robert Collins wrote: > > On 8 December 2013 17:23, Monty Taylor wrote: > >> > > > >> I suggested salt because we could very easily make trove and savana into > >> salt masters (if we wanted to) just by having the

Re: [openstack-dev] [Solum] Second working group meeting on language packs today

- Original Message - > Hi, > > We will hold our second Git Integration working group meeting on IRC in > #solum on Monday, December 9, 2013 1700 UTC / 0900 PST. > > Agenda for today's meeting: > * Administrative: > * Decide whether to continue this meeting at the same

Re: [openstack-dev] [Nova][Schduler] Volunteers wanted for a modest proposal for an external scheduler in our lifetime

Excerpts from Herman Narkaytis's message of 2013-12-09 08:18:17 -0800: > Hi All, > Last couple of month Mirantis team was working on new scalable scheduler > architecture. The main concept was proposed by Boris Pavlovic in the > following blue print > https://blueprints.launchpad.net/nova/+spec/n

Re: [openstack-dev] [Nova][TripleO] Nested resources

On Dec 5, 2013, at 8:11 PM, Fox, Kevin M wrote: > I think the security issue can be handled by not actually giving the > underlying resource to the user in the first place. > > So, for example, if I wanted a bare metal node's worth of resource for my own > containering, I'd ask for a bare metal

Re: [openstack-dev] [olso] [cinder] upgrade issues in lock_path in cinder after oslo utils sync

On 12/09/2013 11:38 AM, Clint Byrum wrote: > Excerpts from Sean Dague's message of 2013-12-09 08:17:45 -0800: >> On 12/06/2013 05:40 PM, Ben Nemec wrote: >>> On 2013-12-06 16:30, Clint Byrum wrote: Excerpts from Ben Nemec's message of 2013-12-06 13:38:16 -0800: > > > On 2013-12-06

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

> -Original Message- > From: Krishna Raman [mailto:[email protected]] > Sent: Sunday, December 08, 2013 11:24 PM > To: OpenStack Development Mailing List (not for usage questions) > Subject: [openstack-dev] [Solum] Using Zuul in the Git-pull blueprint > > Hi all, > > We had a very good me

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

On Sunday, December 08, 2013 11:32:50 PM, Yoshihiro Kaneko wrote: Hi Neutron team, I'm working on building Third-party testing for Neutron Ryu plugin. I intend to use Jenkins and gerrit-trigger plugin. It is required that Third-party testing provides verify vote for all changes to a plugin/dr

[openstack-dev] [Mistral] Community meeting minutes and logs - 12/09/2013

Hi, Thanks for joining today’s Mistral community meeting. Here are the links to meeting minutes and log: Minutes: http://eavesdrop.openstack.org/meetings/mistral/2013/mistral.2013-12-09-16.01.html Log: http://eavesdrop.openstack.org/meetings/mistral/2013/mistral.2013-12-09-16.01.log.html Join

Re: [openstack-dev] [qa][keystone] Keystoneclient tests to tempest

Responses inline. On Mon, Dec 9, 2013 at 10:07 AM, Sean Dague wrote: > On 12/09/2013 10:12 AM, Brant Knudson wrote: > > Monty - > > > > Thanks for doing the work already to get the infrastructure set up. > > Looks like I've got the easy part here. I posted an initial patch that > > has one test

Re: [openstack-dev] [qa][keystone] Keystoneclient tests to tempest

On 2013-12-09 11:07:50 -0600 (-0600), Brant Knudson wrote: [...] > Is testing multiple versions of keystoneclient actually worth it? > If the other projects don't feel the need for this then why does > Keystone? It's actually caught problems so it's proved useful to > Keystone, and we're making cha

Re: [openstack-dev] [olso] [cinder] upgrade issues in lock_path in cinder after oslo utils sync

On 2013-12-09 10:55, Sean Dague wrote: On 12/09/2013 11:38 AM, Clint Byrum wrote: Excerpts from Sean Dague's message of 2013-12-09 08:17:45 -0800: On 12/06/2013 05:40 PM, Ben Nemec wrote: On 2013-12-06 16:30, Clint Byrum wrote: Excerpts from Ben Nemec's message of 2013-12-06 13:38:16 -0800:

Re: [openstack-dev] [Nova][TripleO] Nested resources

I'm thinking more generic: The cloud provider will provide one or more "suballocating" images. The one Triple O uses to take a bare metal node and make vm's available would be the obvious one to make available initially. I think that one should not have a security concern since it is already be

Re: [openstack-dev] Unified Guest Agent proposal

On 12/09/2013 09:41 AM, David Boucha wrote: On Sat, Dec 7, 2013 at 11:09 PM, Monty Taylor > wrote: On 12/08/2013 07:36 AM, Robert Collins wrote: > On 8 December 2013 17:23, Monty Taylor mailto:[email protected]>> wrote: >> > >> I suggested sa

[openstack-dev] [marconi] Team meeting agenda for tomorrow @ 1500 UTC

The Marconi project team holds a weekly meeting in #openstack-meeting-alt on Tuesdays, 1500 UTC. The next meeting is Tomorrow, Dec. 10. Everyone is welcome, but please take a minute to review the wiki before attending for t

Re: [openstack-dev] [qa][keystone] Keystoneclient tests to tempest

On Mon, Dec 9, 2013 at 11:18 AM, Jeremy Stanley wrote: > On 2013-12-09 11:07:50 -0600 (-0600), Brant Knudson wrote: > [...] > > Is testing multiple versions of keystoneclient actually worth it? > > If the other projects don't feel the need for this then why does > > Keystone? It's actually caught

Re: [openstack-dev] [Nova][TripleO] Nested resources

Excerpts from Fox, Kevin M's message of 2013-12-09 09:34:06 -0800: > I'm thinking more generic: > > The cloud provider will provide one or more "suballocating" images. The one > Triple O uses to take a bare metal node and make vm's available would be the > obvious one to make available initially

Re: [openstack-dev] [heat] Core criteria, review stats vs reality

On 09/12/13 06:31, Steven Hardy wrote: Hi all, So I've been getting concerned about $subject recently, and based on some recent discussions so have some other heat-core folks, so I wanted to start a discussion where we can agree and communicate our expectations related to nomination for heat-cor

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

On 12/09/2013 04:10 PM, Russell Bryant wrote: From looking it appears that RabbitMQ's support is via an experimental plugin. I don't know any more about it. Has anyone looked at it in detail? I believe initial support was added in 3.1.0: http://www.rabbitmq.com/release-notes/README-3.1.0.txt

Re: [openstack-dev] [Solum] Second working group meeting on language packs today

- Original Message - > - Original Message - > > Hi, > > > > We will hold our second Git Integration working group meeting on IRC in > > #solum on Monday, December 9, 2013 1700 UTC / 0900 PST. > > > > Agenda for today's meeting: > > * Administrative: > > * Decide wh

Re: [openstack-dev] [Neutron][LBaaS] L7 model - an alternative

Sorry for the broken link Here is a better one: https://docs.google.com/drawings/d/119JV_dG_odWVVKTcn51qyRh3rW-253uUqfcg9CFQDtg/pub?w=960&h=720 Sent from my iPhone On 8 בדצמ 2013, at 17:31, "Avishay Balderman" mailto:[email protected]>> wrote: Hi I was thinking about a different way for L7

Re: [openstack-dev] Unified Guest Agent proposal

Excerpts from Steven Dake's message of 2013-12-09 09:41:06 -0800: > On 12/09/2013 09:41 AM, David Boucha wrote: > > On Sat, Dec 7, 2013 at 11:09 PM, Monty Taylor > > wrote: > > > > > > > > On 12/08/2013 07:36 AM, Robert Collins wrote: > > > On 8 December 2013 1

Re: [openstack-dev] Unified Guest Agent proposal

> If I am correct of my parsing of the salt nomenclature, Salt provides a Master (eg a server) and minions (eg agents that connect to the salt server).  The salt server tells the minions what to do. Almost - salt can use master, but it can also use the local filesystem (or other providers of data)

Re: [openstack-dev] Unified Guest Agent proposal

This list of features makes me very nervous from a security standpoint. Are we talking about giving an agent an arbitrary shell command or file to install, and it goes and does that, or are we simply triggering a preconfigured action (at the time the agent itself was installed)? From: Steven Da

Re: [openstack-dev] Unified Guest Agent proposal

On Mon, Dec 9, 2013 at 10:41 AM, Steven Dake wrote: > On 12/09/2013 09:41 AM, David Boucha wrote: > > On Sat, Dec 7, 2013 at 11:09 PM, Monty Taylor wrote: > >> >> >> On 12/08/2013 07:36 AM, Robert Collins wrote: >> > On 8 December 2013 17:23, Monty Taylor wrote: >> >> >> > >> >> I suggested sa

[openstack-dev] [infra] Meeting Tuesday December 10th at 19:00 UTC

The OpenStack Infrastructure (Infra) team is hosting our weekly meeting tomorrow, Tuesday December 10th, at 19:00 UTC in #openstack-meeting Meeting agenda available here: https://wiki.openstack.org/wiki/Meetings/InfraTeamMeeting (anyone is welcome to to add agenda items) Everyone interested in in

[openstack-dev] Is there anyway to contribute to "Settings" from your own dashboard plugin.

I am trying to enhance openstack horizon and would like to have my own settings in the top level panel of "Settings". Is there a way to enhance and contribute to this in my own django plugin. Thanks for your help -- pat ___ OpenStack-dev mailing list Open

Re: [openstack-dev] Unified Guest Agent proposal

On Mon, Dec 9, 2013 at 11:19 AM, Clint Byrum wrote: > Excerpts from Steven Dake's message of 2013-12-09 09:41:06 -0800: > > On 12/09/2013 09:41 AM, David Boucha wrote: > > > On Sat, Dec 7, 2013 at 11:09 PM, Monty Taylor > > > wrote: > > > > > > > > > > > > On 12/

Re: [openstack-dev] [ironic][qa] How will ironic tests run in tempest?

On Fri, Dec 6, 2013 at 2:13 PM, Clark Boylan wrote: > On Fri, Dec 6, 2013 at 1:53 PM, David Kranz wrote: > > It's great that tempest tests for ironic have been submitted! I was > > reviewing https://review.openstack.org/#/c/48109/ and noticed that the > tests > > do not actually run. They are sk

[openstack-dev] Retiring "reverify no bug"

Hi, On Wednesday December 11, 2013 we will remove the ability to use "reverify no bug" to re-trigger gate runs for changes that have failed tests. This was previously discussed[1] on this list. There are a few key things to keep in mind: * This only applies to "reverify", not "recheck". That i

[openstack-dev] [Nova] Design proposals for blueprints to record scheduler information

Hi, ALL Recently I've been working on two blueprints[1][2], both involved with recording scheduling information. And would like to hear some comments for several design choices. Problem Statement -- * NoValidHost exception might masked out real failure reason to spin up an instance. Consider fol

Re: [openstack-dev] [heat] Core criteria, review stats vs reality

Excerpts from Steven Hardy's message of 2013-12-09 03:31:36 -0800: > Hi all, > > So I've been getting concerned about $subject recently, and based on some > recent discussions so have some other heat-core folks, so I wanted to start > a discussion where we can agree and communicate our expectation

Re: [openstack-dev] [heat] Core criteria, review stats vs reality

Excerpts from Zane Bitter's message of 2013-12-09 09:52:25 -0800: > On 09/12/13 06:31, Steven Hardy wrote: > > Hi all, > > > > So I've been getting concerned about $subject recently, and based on some > > recent discussions so have some other heat-core folks, so I wanted to start > > a discussion w

Re: [openstack-dev] Unified Guest Agent proposal

2013/12/9 Clint Byrum > Excerpts from Steven Dake's message of 2013-12-09 09:41:06 -0800: > > On 12/09/2013 09:41 AM, David Boucha wrote: > > > On Sat, Dec 7, 2013 at 11:09 PM, Monty Taylor > > > wrote: > > > > > > > > > > > > On 12/08/2013 07:36 AM, Robert Colli

Re: [openstack-dev] [qa][keystone] Keystoneclient tests to tempest

On 2013-12-09 11:50:31 -0600 (-0600), Brant Knudson wrote: [...] > I don't know of any specific testing that verifies that the > client works against older (stable/*) servers. Maybe it happens > when you submit a change to stable/ later. When a change is submitted or approved for a stable/foo serv

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

On 12/09/2013 12:56 PM, Gordon Sim wrote: >> In the case of Nova (and others that followed Nova's messaging >> patterns), I firmly believe that for scaling reasons, we need to move >> toward it becoming the norm to use peer-to-peer messaging for most >> things. For example, the API and conductor s

Re: [openstack-dev] Unified Guest Agent proposal

2013/12/9 Kurt Griffiths > This list of features makes me *very* nervous from a security > standpoint. Are we talking about giving an agent an arbitrary shell command > or file to install, and it goes and does that, or are we simply triggering > a preconfigured action (at the time the agent itse

Re: [openstack-dev] [heat] Core criteria, review stats vs reality

On 09/12/13 14:03, Clint Byrum wrote: Excerpts from Zane Bitter's message of 2013-12-09 09:52:25 -0800: On 09/12/13 06:31, Steven Hardy wrote: Hi all, So I've been getting concerned about $subject recently, and based on some recent discussions so have some other heat-core folks, so I wanted to

Re: [openstack-dev] [qa][keystone] Keystoneclient tests to tempest

On 12/09/2013 11:07 AM, Sean Dague wrote: On 12/09/2013 10:12 AM, Brant Knudson wrote: Monty - Thanks for doing the work already to get the infrastructure set up. Looks like I've got the easy part here. I posted an initial patch that has one test from keystone in https://review.openstack.org/#/

Re: [openstack-dev] [neutron] Creating "recipes" for mimicking behavior of nova-networking network managers.

On 12/04/2013 07:56 PM, Tom Fifield wrote: On 05/12/13 01:14, Brent Eagles wrote: Hi, < snip > I think that's a great idea. What kind of format would you like to see the recepies in? Regards, Tom I think a wiki is the right way to start. It will allow us to include diagrams and access

Re: [openstack-dev] [heat] Core criteria, review stats vs reality

On 10 December 2013 00:31, Steven Hardy wrote: > Hi all, > > So I've been getting concerned about $subject recently, and based on some > recent discussions so have some other heat-core folks, so I wanted to start > a discussion where we can agree and communicate our expectations related to > nomin

Re: [openstack-dev] [keystone] Service scoped role definition

On 12/06/2013 04:44 AM, David Chadwick wrote: Another alternative is to change role name into role display name, indicating that the string is only to be used in GUIs, is not guaranteed to be unique, is set by the role creator, can be any string in any character set, and is not used by the system

[openstack-dev] [climate] IRC meeting exceptionnally today 2000 UTC

As per https://wiki.openstack.org/wiki/Meetings there is no meeting at 2000 UTC, so let's meet up together on #openstack-meeting in 10 mins. Thanks, -Sylvain 2013/12/9 Sergey Lukjanov > Time is ok for me too. > > @Sylvain, IMO policies could not be high prioritized when nothing else > really c

Re: [openstack-dev] [keystone] Service scoped role definition

On 09/12/2013 19:37, Adam Young wrote: > On 12/06/2013 04:44 AM, David Chadwick wrote: >> Another alternative is to change role name into role display name, >> indicating that the string is only to be used in GUIs, is not guaranteed >> to be unique, is set by the role creator, can be any string i

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

On 9 December 2013 23:56, Jaromir Coufal wrote: > > On 2013/07/12 01:59, Robert Collins wrote: > >* Creation > * Manual registration > * hardware specs from Ironic based on mac address (M) > > Ironic today will want IPMI address + MAC for each NIC + disk/cpu/memory > stats > > F

Re: [openstack-dev] [keystone] Service scoped role definition

On 12/09/2013 03:04 PM, David Chadwick wrote: On 09/12/2013 19:37, Adam Young wrote: On 12/06/2013 04:44 AM, David Chadwick wrote: Another alternative is to change role name into role display name, indicating that the string is only to be used in GUIs, is not guaranteed to be unique, is set by

[openstack-dev] [Climate] Minutes from today meeting

Huge thanks for our Russian peers who did exceptional efforts for joining us exceptionnally today at 2000 UTC (midnight their time), I owe you a beer :-) You can find our weekly meeting minutes on http://eavesdrop.openstack.org/meetings/climate/2013/climate.2013-12-09-20.01.html Thanks, -Sylvain

Re: [openstack-dev] [keystone] Service scoped role definition

Hi David, I have updated the ether pad with below comments. Regards, Arvind "Another alternative is to change role name into role display name, indicating that the string is only to be used in GUIs, is not guaranteed to be unique, is set by the role creator, can be any string in any charact

  1   2   >