Re: [openstack-dev] Unified Guest Agent proposal

Agreed, Chatting earlier today on #cloud-init about all of this I think scott convinced me that maybe we (the joint we in the community at large) should think about asking ourselves what do we really want a guest agent for/to do? If it's for software installation or user management then aren't

Re: [openstack-dev] Unified Guest Agent proposal

Excerpts from Sandy Walsh's message of 2013-12-06 12:12:16 -0800: > > On 12/06/2013 03:45 PM, Dmitry Mescheryakov wrote: > > Hello all, > > > > We would like to push further the discussion on unified guest agent. You > > may find the details of our proposal at [1]. > > > > Also let me clarify wh

Re: [openstack-dev] Unified Guest Agent proposal

Excerpts from Joshua Harlow's message of 2013-12-06 12:27:10 -0800: > Another idea that I'll put up for consideration (since I work with the > cloud-init codebase also). > > Cloud-init[1] which currently does lots of little useful initialization > types of activities (similar to the racker agents

Re: [openstack-dev] [TripleO][Tuskar] Questions around Development Process

Hey, you've already got a bunch of answers, but FWIW: a) I think it's fine to do a few big patches deleting stuff you don't want. You can always bring it back from git history. OTOH if you bring it back it will be reviewed again :). b) I think UI + API + pythonclient in parallel is ok, but: - pl

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

> 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 a resource class (M) > >>

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

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 Icehouse, unless marked > > otherwise: > >(M) -

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

Excerpts from Jay Pipes's message of 2013-12-06 16:46:24 -0800: > On 12/06/2013 01:38 PM, Clint Byrum wrote: > > Excerpts from Jay Pipes's message of 2013-12-05 21:32:54 -0800: > >> On 12/05/2013 04:25 PM, Clint Byrum wrote: > >>> Excerpts from Andrew Plunk's message of 2013-12-05 12:42:49 > >>> -0

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

On 7 December 2013 10:55, Matt Wagner wrote: > The 'management node' here is the undercloud node that Anna is > interacting with, as I understand it. (Someone correct me if I'm wrong.) > So it's not a bad idea to show its status, but I guess the mere fact > that she's using it will indicate that

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

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 an end user's point of view…what would they > want to acco

Re: [openstack-dev] New Pycharm License

Andrew, I would greatly appreciate a PyCharm license key. I think I qualify as an OpenStack dev. On 09/26/2013 11:41 AM, Andrew Melton wrote: Hey Devs, It's almost been a year since I sent out the first email and I've been getting a few emails lately about alerts that the current license i

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

On 7 December 2013 09:26, Tzu-Mainn Chen wrote: >> > * Archived nodes (F) >> >> Can you elaborate a bit more on what this is? > > To be honest, I'm a bit fuzzy about this myself; Jarda mentioned that there > was > an OpenStack service in the process of being planned that would handle this >

Re: [openstack-dev] [TripleO] capturing build details in images

On 12/06/2013 02:36 PM, Clint Byrum wrote: Excerpts from Robert Collins's message of 2013-12-04 14:19:44 -0800: So - what about us capturing this information outside the image: we can create a uuid for the build, and write a file in the image with that uuid, and outside the image we can write:

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

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 a resource class (M) >> * acts as filter for

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

Thanks for doing this! On 6 December 2013 15: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

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

On 12/06/2013 01:38 PM, Clint Byrum wrote: Excerpts from Jay Pipes's message of 2013-12-05 21:32:54 -0800: On 12/05/2013 04:25 PM, Clint Byrum wrote: Excerpts from Andrew Plunk's message of 2013-12-05 12:42:49 -0800: Excerpts from Randall Burt's message of 2013-12-05 09:05:44 -0800: On Dec 5,

Re: [openstack-dev] [openstack-tc] Incubation Request for Barbican

>> Just an FYI that I've submitted a pull request [1] to replace Celery >> with oslo.messaging. > > wow. That was quick! > > /me is impressed Ha! Just trying to put the polish on! Thanks for the feedback and hope it is a step in the right direction. I'll look to add testing for it on Monday or b

Re: [openstack-dev] [heat][horizon]Heat UI related requirements & roadmap

On 12/6/13 4:32 PM, "Randall Burt" wrote: >I hope I'm not re-opening worm cans here, and that's not my intent, but I >just wanted to get a little clarification in-line below: > >On Dec 6, 2013, at 3:24 PM, Tim Schnell > wrote: > >> To resolve this thread, I have created 5 blueprints based on th

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

Pasting a few things from IRC here to fill out the context... carl_baldwin: but according to markmcclain and salv-orlando, it isn't possible to trivially use multiple workers for rpc because processing rpc requests out of sequence can be dangerous marun: I think it is already possible to run mo

Re: [openstack-dev] Top Gate Bugs

I had the labels wrong - here's a slightly better link - http://bit.ly/1gdxYeg On Fri, Dec 6, 2013 at 4:31 PM, Davanum Srinivas wrote: > Joe, > > Looks like we may be a bit more stable now? > > Short URL: http://bit.ly/18qq4q2 > > Long URL : > http://graphite.openstack.org/graphlot/?from=-120hou

Re: [openstack-dev] [TripleO] UI Wireframes - close to implementation start (Jaromir Coufal)

Let me know if I can be of assistance in the visual design of this. ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

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

That is great. How this work will be coordinated? I just want to be sure that all assets are covered. Thanks Georgy On Fri, Dec 6, 2013 at 3:15 PM, Randall Burt wrote: > On Dec 6, 2013, at 5:04 PM, Clint Byrum > wrote: > > > Excerpts from Randall Burt's message of 2013-12-06 14:43:05 -0800: >

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

On Fri, Dec 6, 2013 at 2:43 PM, Randall Burt wrote: > I too have warmed to this idea but wonder about the actual implementation > around it. While I like where Edmund is going with this, I wonder if it > wouldn't be valuable in the short-to-mid-term (I/J) to just add /templates > to Glance (/asse

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

On Dec 6, 2013, at 5:04 PM, Clint Byrum wrote: > Excerpts from Randall Burt's message of 2013-12-06 14:43:05 -0800: >> I too have warmed to this idea but wonder about the actual implementation >> around it. While I like where Edmund is going with this, I wonder if it >> wouldn't be valuable in

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

I thought about that, i.e. first step in implementation just adding templates, but like you said, you might end up duplicating 5 of the 7 tables in the Glance database, for every new "asset type" (image, template, etc). Then you would do a similar thing for the endpoints. So, I'm not sure what's a

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

Excerpts from Randall Burt's message of 2013-12-06 14:43:05 -0800: > I too have warmed to this idea but wonder about the actual implementation > around it. While I like where Edmund is going with this, I wonder if it > wouldn't be valuable in the short-to-mid-term (I/J) to just add /templates to

Re: [openstack-dev] [olso] [cinder] upgrade issues in lock_path in cinder after oslo utils sync (was: creating a default for oslo config variables within a project?)

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 update config unless one is forced to do so. > But introducing code tha

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

I too have warmed to this idea but wonder about the actual implementation around it. While I like where Edmund is going with this, I wonder if it wouldn't be valuable in the short-to-mid-term (I/J) to just add /templates to Glance (/assemblies, /applications, etc) along side /images. Initially,

Re: [openstack-dev] [heat][horizon]Heat UI related requirements & roadmap

I hope I'm not re-opening worm cans here, and that's not my intent, but I just wanted to get a little clarification in-line below: On Dec 6, 2013, at 3:24 PM, Tim Schnell wrote: > To resolve this thread, I have created 5 blueprints based on this mailing > list discussion. I have attempted to d

Re: [openstack-dev] [olso] [cinder] upgrade issues in lock_path in cinder after oslo utils sync (was: creating a default for oslo config variables within a project?)

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 update config > > unless one is forced to do so. > > But introducing code that weakens security

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

I agree with what seems to also be the general consensus, that Glance can "become" Heater+Glance (the service that manages images in OS today). Clearly, if someone looks at the Glance DB schema, APIs and service type (as returned by keystone service-list), all of the terminology is about images, s

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

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 skipped because baremetal is not enabled. This > is not terribly s

[openstack-dev] [neutron] Questions on logging setup for development

Hi, For Neutron, I'm creating a module (one of several eventually) as part of a new blueprint I'm working on, and the associated unit test module. I'm in really early development, and just running this UT module as a standalone script (rather than through tox). It allows me to do TDD pretty qui

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

The relevant wiki page is here: https://wiki.openstack.org/wiki/TripleO/Tuskar#Icehouse_Planning - Original Message - > That looks really good, thanks for putting that together! > > I'm going to put together a wiki page that consolidates the various Tuskar > planning documents - require

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

Thanks, Liz! Seeing things this way is really helpful. (I actually feel like wireframes -> requirements -> user stories is exactly the opposite of how this normally goes, but hitting all of the steps either way makes things much clearer.) I've raised some questions below. I think many of them are

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

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 skipped because baremetal is not enabled. This is not terribly surprising but we have had a policy in tempest to only me

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

That looks really good, thanks for putting that together! I'm going to put together a wiki page that consolidates the various Tuskar planning documents - requirements, user stories, wireframes, etc - so it's easier to see the whole planning picture. Mainn - Original Message - > > On Dec

Re: [openstack-dev] [olso] [cinder] upgrade issues in lock_path in cinder after oslo utils sync (was: creating a default for oslo config variables within a project?)

On 2013-12-06 15:14, Yuriy Taraday wrote: > Hello, Sean. > > I get the issue with upgrade path. User doesn't want to update config unless > one is forced to do so. > But introducing code that weakens security and let it stay is an > unconditionally bad idea. > It looks like we have to we

Re: [openstack-dev] [TripleO][Tuskar] Questions around Development Process

On 2013-12-06 12:19, Jay Dobies wrote: a) Because we're essentially doing a tear-down and re-build of the whole architecture (a lot of the concepts in tuskar will simply disappear), it's difficult to do small incremental patches that support existing functionality. Is it okay to have patches t

[openstack-dev] [Neutron][IPv6] Provisioning Support

As part of the discussion around managing IPv6-addressed hosts both within neutron itself and other systems that require address information, Sean Collins and I had had a discussion about the types of addresses that could be supported. Since IPv6 has many modes of provisioning, we will need to pro

Re: [openstack-dev] Top Gate Bugs

Joe, Looks like we may be a bit more stable now? Short URL: http://bit.ly/18qq4q2 Long URL : http://graphite.openstack.org/graphlot/?from=-120hour&until=-0hour&target=color(alias(movingAverage(asPercent(stats.zuul.pipeline.gate.job.gate-tempest-dsvm-full.SUCCESS,sum(stats.zuul.pipeline.gate.job

Re: [openstack-dev] [qa][nova] The document for the changes from Nova v2 api to v3

Hi David, 2013/12/7 David Kranz : > On 12/06/2013 03:57 PM, Ken'ichi Ohmichi wrote: >> >> Hi, >> >> We are implementing Nova v3 API validation with jsonschema. >> The schemas of API parameters are defined under >> nova/api/openstack/compute/schemas/v3/. >> I guess the shemas would be used for chec

Re: [openstack-dev] [heat][horizon]Heat UI related requirements & roadmap

To resolve this thread, I have created 5 blueprints based on this mailing list discussion. I have attempted to distill the proposed specification down to what seemed generally agreed upon but if you feel strongly that I have incorrectly captured something let's talk about it! Here are the blueprin

Re: [openstack-dev] Incubation Request for Barbican

On Mon, Dec 2, 2013 at 9:19 AM, Jarret Raim wrote: > All, > > Barbican is the OpenStack key management service and we’d like to > request incubation for the Icehouse release. A Rackspace sponsored team has > been working for about 9 months now, including following the Havana release > cycle for

Re: [openstack-dev] [olso] [cinder] upgrade issues in lock_path in cinder after oslo utils sync (was: creating a default for oslo config variables within a project?)

Hello, Sean. I get the issue with upgrade path. User doesn't want to update config unless one is forced to do so. But introducing code that weakens security and let it stay is an unconditionally bad idea. It looks like we have to weigh two evils: having troubles upgrading and lessening security. T

Re: [openstack-dev] Unified Guest Agent proposal

Another option is this: https://github.com/cloudbase/cloudbase-init It is python based on windows rather then .NET. Thanks, Kevin From: Sandy Walsh [sandy.wa...@rackspace.com] Sent: Friday, December 06, 2013 12:12 PM To: openstack-dev@lists.openstack.org S

Re: [openstack-dev] [qa][nova] The document for the changes from Nova v2 api to v3

On 12/06/2013 03:57 PM, Ken'ichi Ohmichi wrote: Hi, We are implementing Nova v3 API validation with jsonschema. The schemas of API parameters are defined under nova/api/openstack/compute/schemas/v3/. I guess the shemas would be used for checking the difference between doc and Nova v3 API paramet

Re: [openstack-dev] [tempest] list of negative tests that need to be separated from other tests.

Hi Adalberto, 2013/12/7 Adalberto Medeiros : > Hi! > > In the QA meeting yesterday, we decide to create a blueprint specific for > the negative tests in a separate file: > https://blueprints.launchpad.net/tempest/+spec/negative-test-files and use > it to track the patches. Thank you for pointing

Re: [openstack-dev] [qa][nova] The document for the changes from Nova v2 api to v3

Hi, We are implementing Nova v3 API validation with jsonschema. The schemas of API parameters are defined under nova/api/openstack/compute/schemas/v3/. I guess the shemas would be used for checking the difference between doc and Nova v3 API parameters as another approach. example: https://review

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

On Dec 5, 2013, at 9:31 PM, 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

[openstack-dev] [Neutron][IPv6] Two new blueprints

Hi, stackers: Randy Tuttle created two blueprints as an augment to Sean’s proposal to improve IPv6 readiness. You can find the details here: https://blueprints.launchpad.net/neutron/+spec/dnsmasq-bind-into-qrouter-namespace https://blueprints.launchpad.net/neutron/+spec/allow-multiple-subnets-on

Re: [openstack-dev] Unified Guest Agent proposal

That's an interesting idea to use cloud-init, but it looks like such agent will be unable to provide feedback like results of running commands. On Sat, Dec 7, 2013 at 12:27 AM, Joshua Harlow wrote: > Another idea that I'll put up for consideration (since I work with the > cloud-init codebase als

Re: [openstack-dev] Unified Guest Agent proposal

Another idea that I'll put up for consideration (since I work with the cloud-init codebase also). Cloud-init[1] which currently does lots of little useful initialization types of activities (similar to the racker agents activities) has been going through some of the same questions[2] as to should

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

Thanks for the comments! Responses inline: > 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. > > As I proofread, some of my comments may drift a bit past basic > requirements, so feel free to tell me to take

Re: [openstack-dev] Unified Guest Agent proposal

In addition, here are several related links: etherpad with some collected requirements: https://etherpad.openstack.org/p/UnifiedAgents initial thread about unified agents: http://lists.openstack.org/pipermail/openstack-dev/2013-November/thread.html#18276 Thanks. On Fri, Dec 6, 2013 at 11:45 PM,

Re: [openstack-dev] Unified Guest Agent proposal

On 12/06/2013 03:45 PM, Dmitry Mescheryakov wrote: > Hello all, > > We would like to push further the discussion on unified guest agent. You > may find the details of our proposal at [1]. > > Also let me clarify why we started this conversation. Savanna currently > utilizes SSH to install/confi

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

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. As I proofread, some of my comments may drift a bit past basic requirements, so feel free to tell me to take certain questions out of this thread into specific

Re: [openstack-dev] [TripleO][Tuskar] Questions around Development Process

Excerpts from Tzu-Mainn Chen's message of 2013-12-06 07:37:20 -0800: > Hey all, > > We're starting to work on the UI for tuskar based on Jarda's wireframes, and > as we're doing so, we're realizing that > we're not quite sure what development methodology is appropriate. Some > questions: > > a

[openstack-dev] Unified Guest Agent proposal

Hello all, We would like to push further the discussion on unified guest agent. You may find the details of our proposal at [1]. Also let me clarify why we started this conversation. Savanna currently utilizes SSH to install/configure Hadoop on VMs. We were happy with that approach until recently

Re: [openstack-dev] [TripleO][Tuskar] Questions around Development Process

> >> b) In the past, we allowed parallel development of the UI and API by > >> having well-documented expectations of what the API > > Are these expectations documented yet? I'm new to the project and still > finding my way around. I've seen the wireframes and am going through > Chen's icehouse re

Re: [openstack-dev] [TripleO] capturing build details in images

Excerpts from Robert Collins's message of 2013-12-04 14:19:44 -0800: > So - what about us capturing this information outside the image: we > can create a uuid for the build, and write a file in the image with > that uuid, and outside the image we can write: > - all variables (no security ramificat

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

As a Murano team we will be happy to contribute to Glance. Our Murano metadata repository is a standalone component (with its own git repository)which is not tightly coupled with Murano itself. We can easily add our functionality to Glance as a new component\subproject. Thanks Georgy On Fri, Dec

Re: [openstack-dev] [Tripleo] Core reviewer update Dec

On 12/06/2013 12:26 PM, Clint Byrum wrote: Excerpts from Robert Collins's message of 2013-12-03 23:12:39 -0800: Hi, like most OpenStack projects we need to keep the core team up to date: folk who are not regularly reviewing will lose context over time, and new folk who have been reviewing r

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

On Dec 6, 2013, at 10:38 AM, Clint Byrum wrote: > Excerpts from Jay Pipes's message of 2013-12-05 21:32:54 -0800: >> On 12/05/2013 04:25 PM, Clint Byrum wrote: >>> Excerpts from Andrew Plunk's message of 2013-12-05 12:42:49 -0800: > Excerpts from Randall Burt's message of 2013-12-05 09:05:44

Re: [openstack-dev] [Keystone][Marconi][Oslo] Discoverable home document for APIs (Was: Re: [Nova][Glance] Support of v1 and v2 glance APIs in Nova)

On Mon, Nov 25, 2013 at 4:25 PM, Jamie Lennox wrote: > To most of your questions i don't know the answer as the format was in > place before i started with the project. I know that it is similar (though > not exactly the same) as nova's but not where they are documented (as they > are version inde

Re: [openstack-dev] [Nova] New API requirements, review of GCE

On 12/02/2013 02:06 PM, Eric Windisch wrote: > What more is needed from the blueprint or the patch authors to proceed? I finally got back to looking at this. Here is how I would like to proceed with GCE. 1) Stackforge It seems like this code is pretty self contained. I'd like to see it importe

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

On Dec 6, 2013, at 10:07 AM, Georgy Okrokvertskhov wrote: > Hi, > > 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 did not think in the direction of changing Glance. Spendin

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

Excerpts from Jay Pipes's message of 2013-12-05 21:32:54 -0800: > On 12/05/2013 04:25 PM, Clint Byrum wrote: > > Excerpts from Andrew Plunk's message of 2013-12-05 12:42:49 -0800: > >>> Excerpts from Randall Burt's message of 2013-12-05 09:05:44 -0800: > On Dec 5, 2013, at 10:10 AM, Clint Byru

Re: [openstack-dev] [olso] [cinder] upgrade issues in lock_path in cinder after oslo utils sync (was: creating a default for oslo config variables within a project?)

Excerpts from Sean Dague's message of 2013-12-06 09:47:03 -0800: > So it still seems that we are at an impasse here on getting new olso > lockutils into cinder because it doesn't come with a working default. > > As a recap - https://review.openstack.org/#/c/48935/ (that sync) > > is blocked by fa

[openstack-dev] TransportURL and virtualhost/exchnage (was Re: [Oslo] Layering olso.messaging usage of config)

On 11/18/2013 04:44 PM, Mark McLoughlin wrote: On Mon, 2013-11-18 at 11:29 -0500, Doug Hellmann wrote: IIRC, one of the concerns when oslo.messaging was split out was maintaining support for existing deployments with configuration files that worked with oslo.rpc. We had said that we would use UR

Re: [openstack-dev] [TripleO][Tuskar] Questions around Development Process

a) Because we're essentially doing a tear-down and re-build of the whole architecture (a lot of the concepts in tuskar will simply disappear), it's difficult to do small incremental patches that support existing functionality. Is it okay to have patches that break functionality? Are there good a

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

Dear All, The consensus in comments to both patches seems to be that the decision to clone an image based on disk format should be made in each driver, instead of being imposed on all drivers by the flow. Edward has updated his patch to follow the same logic as my patch, and I have updated my patc

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

Hi, 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 did not think in the direction of changing Glance. Spending a night with these ideas, I am kind of having a dream about unified cata

Re: [openstack-dev] Behavior change around the PyPI mirror and openstack/requirements

On 2013-12-06 18:58:36 +0200 (+0200), Monty Taylor wrote: [...] > Anywho - gate selection will now be tied to the projects.txt file in > openstack/requirements. Essentially, if you receive automatic > requirements sync commits, your commits will be tested with the mirror. > If you are tied to the m

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

Could jsonschema[1] be used here to do the options schema part? It works on dictionaries (and really isn't tied to json). But maybe I am missing some greater context/understanding (see other emails). [1] https://pypi.python.org/pypi/jsonschema Sent from my really tiny device... > On Dec 6, 201

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

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 change applies across all OpenStack. Will Nova use the change for i

Re: [openstack-dev] [neutron] only one subnet_id is allowed behind a router for vpnservice object

Thanks! Commented on bp whiteboard. 2013/12/5 Yongsheng Gong : > ok, My pleasure to help, > I created a bp for it: > https://blueprints.launchpad.net/neutron/+spec/vpn-multiple-subnet > > > On Fri, Dec 6, 2013 at 2:11 PM, Nachi Ueno wrote: >> >> Hi Yong >> >> Yes, to support multiple subnet is on

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

Forgive me for not understanding your precious email (which I guess was confusing for me to understand). This one clears that up. If only we all had Vulcan mind meld capabilities, haha. Thanks for helping me understand, no need to get frustrated. Not everyone is able to decipher your email in t

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

Previous not precious, ha, durn autocorrect, lol. Sent from my really tiny device... > On Dec 6, 2013, at 9:50 AM, "Joshua Harlow" wrote: > > Forgive me for not understanding your precious email (which I guess was > confusing for me to understand). This one clears that up. If only we all had

Re: [openstack-dev] [olso] [cinder] upgrade issues in lock_path in cinder after oslo utils sync (was: creating a default for oslo config variables within a project?)

So it still seems that we are at an impasse here on getting new olso lockutils into cinder because it doesn't come with a working default. As a recap - https://review.openstack.org/#/c/48935/ (that sync) is blocked by failing upgrade testing, because lock_path has no default, so it has to land co

Re: [openstack-dev] [Tripleo] Core reviewer update Dec

Excerpts from Robert Collins's message of 2013-12-03 23:12:39 -0800: > Hi, > like most OpenStack projects we need to keep the core team up to > date: folk who are not regularly reviewing will lose context over > time, and new folk who have been reviewing regularly should be trusted > with -core

Re: [openstack-dev] [Tripleo] Core reviewer update Dec

On 12/06/2013 05:36 PM, Ben Nemec wrote: On 2013-12-06 03:22, Ladislav Smola wrote: On 12/06/2013 09:56 AM, Jaromir Coufal wrote: On 2013/04/12 08:12, Robert Collins wrote: Hi, like most OpenStack projects we need to keep the core team up to date: folk who are not regularly reviewing w

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

On Fri, 2013-12-06 at 16:55 +, Joshua Harlow wrote: > I really have to agree with this. It's especially important if > oslo.messaging is also used in libraries like taskflow. If > oslo.messaging imposes that users of it must use oslo.config then by > using it in taskflow, taskflow then imposes

Re: [openstack-dev] [nova] Do we have some guidelines for mock, stub, mox when writing unit test?

On 2013-12-05 21:38, Jay Pipes wrote: On 12/04/2013 12:10 PM, Russell Bryant wrote: On 12/04/2013 11:16 AM, Nikola Đipanov wrote: Resurrecting this thread because of an interesting review that came up yesterday [1]. It seems that our lack of a firm decision on what to do with the mocking fra

Re: [openstack-dev] [tempest] list of negative tests that need to be separated from other tests.

Hi! In the QA meeting yesterday, we decide to create a blueprint specific for the negative tests in a separate file: https://blueprints.launchpad.net/tempest/+spec/negative-test-files and use it to track the patches. I added the etherpad link Ken'ichi pointed to this bp. Ken'ichi, should yo

Re: [openstack-dev] [ceilometer] [marconi] Notifications brainstorming session tomorrow @ 1500 UTC

That’s a good question. IMO, this is an important use case, and should be considered within scope of the project. Rackspace uses a precursor to Marconi for its Cloud Backup product, and it has worked out well for showing semi-realtime updates, e.g., progress on an active backup jobs. We have a

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

On Thu, Dec 5, 2013 at 9:32 PM, Jay Pipes wrote: > On 12/05/2013 04:25 PM, Clint Byrum wrote: > >> Excerpts from Andrew Plunk's message of 2013-12-05 12:42:49 -0800: >> >>> Excerpts from Randall Burt's message of 2013-12-05 09:05:44 -0800: > On Dec 5, 2013, at 10:10 AM, Clint Byrum

[openstack-dev] Behavior change around the PyPI mirror and openstack/requirements

Hey all! Things keep getting more complex around here, so we keep doing more stuffs. Up until today, a project's forced participation on the OpenStack PyPI Mirror (pypi.openstack.org) while in the gate was controllled by the project being prefixed with openstack/. Well, that's clearly not rich en

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

I really have to agree with this. It's especially important if oslo.messaging is also used in libraries like taskflow. If oslo.messaging imposes that users of it must use oslo.config then by using it in taskflow, taskflow then imposes the same oslo.config usage. This makes all libraries that use

[openstack-dev] [qa] Changes slipping through the nova v2->v3 port

I have been trying to review all of the nova v3 changes. Many of these patches have been around for awhile and have not kept up with changes that were made to the v2 tests after a v2 test file was copied to v3. I think any one submitting a patch to the nova v2 test code needs to file a bug tick

Re: [openstack-dev] [Tripleo] Core reviewer update Dec

On 2013-12-06 03:22, Ladislav Smola wrote: > On 12/06/2013 09:56 AM, Jaromir Coufal wrote: > > On 2013/04/12 08:12, Robert Collins wrote: > > Hi, > like most OpenStack projects we need to keep the core team up to > date: folk who are not regularly reviewing will lose context over > time, a

Re: [openstack-dev] Top Gate Bugs

On Wednesday, December 04, 2013 7:22:23 AM, Joe Gordon wrote: TL;DR: Gate is failing 23% of the time due to bugs in nova, neutron and tempest. We need help fixing these bugs. Hi All, Before going any further we have a bug that is affecting gate and stable, so its getting top priority here. e

Re: [openstack-dev] [Nova][Docker] What are the plans or thoughts about providing volumes aka folder mounts

On 12/06/2013 10:54 AM, Daniel Kuffner wrote: > Hi All, > > We are using in our company for a prototype the docker hypervisor on > openstack. We have the need to mount a folder inside of a container. > To achieve this goal I have implemented a hack which allows to specify > a folder mount via nov

Re: [openstack-dev] [TripleO][Tuskar] Questions around Development Process

On 2013-12-06 09:37, Tzu-Mainn Chen wrote: Hey all, We're starting to work on the UI for tuskar based on Jarda's wireframes, and as we're doing so, we're realizing that we're not quite sure what development methodology is appropriate. Some questions: a) Because we're essentially doing a tear-do

Re: [openstack-dev] [openstack-qa] [qa][nova] The document for the changes from Nova v2 api to v3

Hi all, Now that you've got a decent start, how about checking it in as a doc/source/ document in the nova repository? Seems better than keeping it in the wiki so that you can update with code changes. Anne On Wed, Nov 13, 2013 at 11:11 PM, Alex Xu wrote: > On 2013年11月14日 07:09, Christopher Ye

Re: [openstack-dev] [openstack-tc] Incubation Request for Barbican

On 12/06/2013 08:35 AM, John Wood wrote: > Hello folks, > > Just an FYI that I've submitted a pull request [1] to replace Celery > with oslo.messaging. wow. That was quick! /me is impressed Since you jumped on that - I went ahead and jumped on a pbr-ification patch for you. It may not work ye

Re: [openstack-dev] [qa][nova] The document for the changes from Nova v2 api to v3

On 11/13/2013 06:09 PM, Christopher Yeoh wrote: On Thu, Nov 14, 2013 at 7:52 AM, David Kranz > wrote: On 11/13/2013 08:30 AM, Alex Xu wrote: Hi, guys This is the document for the changes from Nova v2 api to v3: https://wiki.openstack.org/wiki/NovaAPIv2

[openstack-dev] [Nova][Docker] What are the plans or thoughts about providing volumes aka folder mounts

Hi All, We are using in our company for a prototype the docker hypervisor on openstack. We have the need to mount a folder inside of a container. To achieve this goal I have implemented a hack which allows to specify a folder mount via nova metadata. For example a heat template could look like:

[openstack-dev] [TripleO][Tuskar] Questions around Development Process

Hey all, We're starting to work on the UI for tuskar based on Jarda's wireframes, and as we're doing so, we're realizing that we're not quite sure what development methodology is appropriate. Some questions: a) Because we're essentially doing a tear-down and re-build of the whole architecture

Re: [openstack-dev] [Keystoneclient] [Keystone] [Solum] Last released version of keystoneclient does not work with python33

On Wed, Dec 4, 2013 at 7:48 PM, David Stanek wrote: > On Wed, Dec 4, 2013 at 6:44 PM, Adrian Otto wrote: > >> Jamie, >> >> Thanks for the guidance here. I am checking to see if any of our >> developers might take an interest in helping with the upstream work. At the >> very least, it might be nic

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

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 possible > > answers: > > > > 5) But I wa

  1   2   >