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

Hi, I was trying to fine tune some keystone policy rules. Basically I want to grant "create_project" action to user in "ops" role. And following are my steps. 1. Adding a new user "usr1" 2. Creating new role "ops" 3. Granting this user a "ops" role in "service" tenant 4. Adding new lines to keyst

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

+1 I'll be there.. Sukhdev On Dec 10, 2013 12:43 PM, "Kyle Mestery" wrote: > OK, looks like we've reached consensus. I've set the time and channel > to 12-12-2013 (Thursday), 1700UTC, on #openstack-meeting-alt. > > Thanks! > Kyle > > On Dec 10, 2013, at 12:59 PM, Gary Duan wrote: > > > I will b

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

Hi, Edgar, Please file a bug on this. Obviously this was introduced by that commit. Thanks, Eugene. On Thu, Dec 12, 2013 at 7:45 AM, Edgar Magana wrote: > In commit: > https://review.openstack.org/#/c/58814/ > > There is an assumption that all "plugins" creates the > plumgrid_neutron.agents w

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

Hi Edgar, Nice catch! I proposed a fix here https://review.openstack.org/#/c/61663/ Could you please test it and and tell us if it fixes your problem? Thanks, Roman On Thu, Dec 12, 2013 at 5:45 AM, Edgar Magana wrote: > In commit: > https://review.openstack.org/#/c/58814/ > > There is an assum

Re: [openstack-dev] [Nova][Cells] compute api and objects

OK thanks for the info, I’ll have a look into these and add some bugs/patches. Cheers, Sam On 11 Dec 2013, at 10:21 am, Chris Behrens wrote: > On Dec 9, 2013, at 2:58 PM, Sam Morrison wrote: > >> Hi, >> >> I’m trying to fix up some cells issues related to objects. Do all compute >> api met

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

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

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

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, 2013 at 3:41 PM, Ryan Petrello < > >> ryan.petre...@dreamhost.com> wrote: > > > >> Hello, > >> > >> I’ve spent the past week experimenting with using Pecan

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

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

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

> > We can involve people in security reviews without having them on the > core review team. They are separate concerns. > Yes, but those people can't ultimately approve the patch. So you'd need to have a security reviewer do their review, and then someone who isn't a security person be able to

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

> 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/p/solum-demystified >>> >>> I am really excited to

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

In commit: https://review.openstack.org/#/c/58814/ There is an assumption that all "plugins" creates the plumgrid_neutron.agents which is not the case. I just tested big switch and plumgrid and they are failing: INFO [alembic.migration] Running upgrade havana -> e197124d4b9, add unique constrain

[openstack-dev] [OSSG][OSSN] Glance allows sharing of images between projects without consumer project approval

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Glance allows sharing of images between projects without consumer project approval - --- ### Summary ### Glance allows images to be shared between projects. In certain API versions, images can be shared without the consumer project's approval. This al

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

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 Mailing List (not for usage questions) Subject: Re:

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

+1 On Thu, Dec 12, 2013 at 9:14 AM, Bryan D. Payne wrote: > Re: Removing Paul McMillan from core > > I would argue that it is critical that each project have 1-2 people on > core that are security experts. The VMT is an intentionally small team. > They are moving to having specifically appoin

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

On 12/11/2013 08:14 PM, Bryan D. Payne wrote: > Re: Removing Paul McMillan from core > > I would argue that it is critical that each project have 1-2 people on > core that are security experts. The VMT is an intentionally small team. > They are moving to having specifically appointed security su

[openstack-dev] [State-Management] Agenda for tomorrow meeting at 2000 UTC

Hi all, The [state-management] project team holds a weekly meeting in #openstack-meeting on thursdays, 2000 UTC. The next meeting is tomorrow, 2013-12-12!!! As usual, everyone is welcome :-) Link: https://wiki.openstack.org/wiki/Meetings/StateManagement Taskflow: https://wiki.openstack.org/Tas

[openstack-dev] [Ironic] Bug list maintenance

So, I've dug into the bug list in the past few days, and want to share what I've observed. Over the Havana cycle, we all used the bug list as a way to earmark work we needed to come back to. Some of those earmarks are stale. Perhaps the status is incorrect, or we fixed it but didn't close the bug,

[openstack-dev] [Metrics] Communicating how to interpret community data

Hello folks I wrote a blog post today after noticing again that reporters take the data published on Activity Board and Stackalytics as true, without asking questions to the protagonists. The problem is that at the moment none of the systems we have can guarantee that the data is presenting at any

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

Re: Removing Paul McMillan from core I would argue that it is critical that each project have 1-2 people on core that are security experts. The VMT is an intentionally small team. They are moving to having specifically appointed security sub-teams on each project (I believe this is what I heard

Re: [openstack-dev] Neutron Distributed Virtual Router

Are these NSX routers *functionally* different? What we're talking about here is a router which, whether it's distributed or not, behaves *exactly the same*. So as I say, maybe it's an SLA thing, but 'distributed' isn't really user meaningful if the user can't actually prove he's received a distr

[openstack-dev] [Ironic] Project status update

Hi all! I realize it's been a while since I've posted an update about the project -- it's high time I do so! And there are several things to report... We tagged an Icehouse-1 milestone, though we did not publish a tarball just yet. That should happen at the Icehouse-2 milestone. http://git.open

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

On 2013-12-11 18:28:14 +0100 (+0100), Monty Taylor wrote: > On 12/11/2013 03:51 PM, Russell Bryant wrote: > > On 12/10/2013 05:57 PM, Paul McMillan wrote: > > [...] > > > If you don't have anyone else who is a web security specialist > > > on the core team, I'd like to stay. Since I'm also a member

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

+1 for Tatiana and the clean-up. On 11 December 2013 07:24, Lyle, David wrote: > I would like to nominate Tatiana Mazur to Horizon Core. Tatiana has been a > significant code contributor in the last two releases, understands the code > base well and has been doing a significant number of revie

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

+1 for both Tatiana and cleaning up the core list. On Wed, Dec 11, 2013 at 5:24 AM, Lyle, David wrote: > I would like to nominate Tatiana Mazur to Horizon Core. Tatiana has been a > significant code contributor in the last two releases, understands the code > base well and has been doing a si

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

On 12/11/2013 04:17 PM, Chris Buccella wrote: > On 12/02/2013 10:18 AM, Joe Gordon wrote: >> >> >> >> >> Thanks for bringing this up, and I'd welcome a patch in Swift that >> would use a common library to generate the transaction id, if it >> were installed. I can see that there would

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

On 2013年12月12日 04:41, Ryan Petrello wrote: Hello, I’ve spent the past week experimenting with using Pecan for Nova’s API, and have opened an experimental review: https://review.openstack.org/#/c/61303/6 …which implements the `versions` v3 endpoint using pecan (and paves the way for other ext

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

On Wed, Dec 11, 2013 at 3:05 PM, Sean Dague wrote: > Dear Glance core, > > Until this review is sorted - https://review.openstack.org/#/c/60971/2 Or this one https://review.openstack.org/#/c/61600/ rather > > > You won't be able to merge any changes, because of the docs issue with > sphinx. >

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

On 12 December 2013 08:15, Tzu-Mainn Chen wrote: > Hi, > > I'm trying to clarify the terminology being used for Tuskar, which may be > helpful so that we're sure > that we're all talking about the same thing :) I'm copying responses from > the requirements thread > and combining them with curre

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

Hi, I think BP is a right way to organize this. I will submit BP for metadata service from our side too. Thanks Georgy On Wed, Dec 11, 2013 at 3:53 PM, Randall Burt wrote: > On Dec 11, 2013, at 5:44 PM, Georgy Okrokvertskhov < > gokrokvertsk...@mirantis.com> > wrote: > > > Hi, > > > > To keep

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

> -Original Message- > From: Monty Taylor [mailto:mord...@inaugust.com] > Sent: Wednesday, December 11, 2013 10:28 AM > To: openstack-dev@lists.openstack.org > Subject: Re: [openstack-dev] [Horizon] Nominations to Horizon Core > > > > On 12/11/2013 03:51 PM, Russell Bryant wrote: > > On

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

On Dec 11, 2013, at 5:44 PM, Georgy Okrokvertskhov wrote: > Hi, > > To keep this thread alive I would like to share the small screencast I've > recorded for Murano Metadata repository. I would like to share with you what > we have in Murano and start a conversation about metadata repository

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

Hi, To keep this thread alive I would like to share the small screencast I've recorded for Murano Metadata repository. I would like to share with you what we have in Murano and start a conversation about metadata repository development in OpenStack. Here is a link to screencast http://www.youtube.

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

On Thu, Dec 12, 2013 at 8:59 AM, Doug Hellmann wrote: > > > > On Wed, Dec 11, 2013 at 3:41 PM, 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://re

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

Thanks to new doc patchers Shilla Saebi and Thomas Herve for their clean up work, especially for the Identity API docs and Heat install! Be ready for 12/20/13 Doc Bug Day! Looking forward to it. 1. In review and merged this past week: The Install Guide is still the most worked-on document. I'd l

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

On Thu, Dec 12, 2013 at 7:11 AM, Ryan Petrello wrote: > Hello, > > I’ve spent the past week experimenting with using Pecan for Nova’s API, > and have opened an experimental review: > > https://review.openstack.org/#/c/61303/6 > > …which implements the `versions` v3 endpoint using pecan (and paves

[openstack-dev] [TripleO] getting back on the train post-summit

Hey everyone! So the summit was a month back, but on the TripleO side we've kindof slumped: there is great design work on the console side happening (yay), but the CD side - where Nova rebuild support is the current blocker - is basically stalled. Folk are doing good work on related bits of plumb

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

Hi Neutron team, I haven't been involved in neutron meetings for quite some time so I'm not sure where we are on this at this point. It is often recommended in OpenStack guides and other operational materials to run multiple neutron-servers to deal with the API load from Nova. Things like the _hea

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

Dear Glance core, Until this review is sorted - https://review.openstack.org/#/c/60971/2 You won't be able to merge any changes, because of the docs issue with sphinx. http://lists.openstack.org/pipermail/openstack-dev/2013-December/021863.html Which means right now every glance patch that goes

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

- Original Message - > Devdatta, > > On Dec 10, 2013, at 12:37 PM, devdatta kulkarni > wrote: > > > Hi Adrian, > > > > Thanks for creating https://etherpad.openstack.org/p/solum-demystified > > > > I am really excited to see the examples. Especially cool is how > > examples 2 and 3 d

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

On Wed, Dec 11, 2013 at 3:41 PM, Ryan Petrello wrote: > Hello, > > I’ve spent the past week experimenting with using Pecan for Nova’s API, > and have opened an experimental review: > > https://review.openstack.org/#/c/61303/6 > > …which implements the `versions` v3 endpoint using pecan (and paves

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

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 sense - OK this is awesome > effort, how can I help? What can I work

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

On Wed Dec 11 14:15:22 2013, Tzu-Mainn Chen wrote: > Hi, > > I'm trying to clarify the terminology being used for Tuskar, which > may be helpful so that we're sure that we're all talking about the > same thing :) I'm copying responses from the requirements thread and > combining them with current

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

On Tue, Dec 10, 2013 at 9:47 AM, Nadya Privalova wrote: > Julien, > > Yes, I use the same SQL for Nova and Ceilometer. Thanks for pointing this > out. My bad, I didn't take it into account. So if we want to use Ceilometer > + MySQL in production (in theory :) ) we need to use separate controllers

Re: [openstack-dev] [heat] Stack preview

On 11/12/13 11:59, Randall Burt wrote: On Dec 10, 2013, at 3:46 PM, Zane Bitter wrote: On 10/12/13 15:10, Randall Burt wrote: On Dec 10, 2013, at 1:27 PM, Zane Bitter wrote: On 10/12/13 12:46, Richard Lee wrote: Hey all, We're working on a blueprint

Re: [openstack-dev] [keystone][heat] ec2tokens, v3 credentials and request signing

On Tue, Dec 10, 2013 at 9:13 AM, Steven Hardy wrote: > On Tue, Dec 10, 2013 at 08:12:17AM -0600, Dolph Mathews wrote: > > On Mon, Dec 9, 2013 at 9:08 PM, Adam Young wrote: > > > > > > > > > > > > > > On 12/09/2013 05:34 PM, Steven Hardy wrote: > > > > > >> Hi all, > > >> > > >> I have some queri

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

On 12/02/2013 10:18 AM, Joe Gordon wrote: Thanks for bringing this up, and I'd welcome a patch in Swift that would use a common library to generate the transaction id, if it were installed. I can see that there would be huge advantage to operators to trace requests through multi

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

the coverage is quite good on the ML2 plugin. it looks like the biggest effort should be done on the ovs and lb agents, no? On Wed, Dec 11, 2013 at 9:00 PM, Amir Sadoughi wrote: > From today’s ML2 meeting, I had an action item to produce coverage report > for ML2 unit tests. > > Here is the comma

Re: [openstack-dev] [QA] Tempest blueprints status update and rationale, input demanded

On 12/11/2013 02:42 PM, Matthew Treinish wrote: On Wed, Dec 11, 2013 at 01:44:19PM +0100, Giulio Fidente wrote: hi, I'm attempting to rationalize on the status of tempest blueprints. I need your help so I organized questions in a few open points. * (1) I'm looking for input here on the actual

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

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 companies/users who are running on ol

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

Hello, I’ve spent the past week experimenting with using Pecan for Nova’s API, and have opened an experimental review: https://review.openstack.org/#/c/61303/6 …which implements the `versions` v3 endpoint using pecan (and paves the way for other extensions to use pecan). This is a *potential*

Re: [openstack-dev] [QA] Tempest blueprints status update and rationale, input demanded

First, thanks for this! Much appreciated. On 12/11/2013 07:44 AM, Giulio Fidente wrote: > hi, > > I'm attempting to rationalize on the status of tempest blueprints. I > need your help so I organized questions in a few open points. > > > * (1) I'm looking for input here on the actual status of t

[openstack-dev] stevedore moved to launchpad and stackforge

The stevedore library source repository is now hosted on stackforge ( https://git.openstack.org/cgit/stackforge/stevedore/) and I am in the process of moving the bug tracker to launchpad ( https://launchpad.net/python-stevedore). Doug ___ OpenStack-dev m

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

>From today’s ML2 meeting, I had an action item to produce coverage report for >ML2 unit tests. Here is the command line output of the tests and report I produced: http://paste.openstack.org/show/54845/ Amir Sadoughi ___ OpenStack-dev mailing list Ope

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

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

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

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

[openstack-dev] [QA] Meeting Thursday December 12th at 22:00 UTC

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

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

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

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

> >Hi, > > > >I'm trying to clarify the terminology being used for Tuskar, which may be > >helpful so that we're sure > >that we're all talking about the same thing :) I'm copying responses from > >the requirements thread > >and combining them with current requirements to try and create a unified

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

On 11/12/13 14:15 -0500, Tzu-Mainn Chen wrote: Hi, I'm trying to clarify the terminology being used for Tuskar, which may be helpful so that we're sure that we're all talking about the same thing :) I'm copying responses from the requirements thread and combining them with current requirement

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

Hi! This list is for discussion of ongoing bugs and features in Heat. For user-centric discussions, please use the main "openstack" mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack Thanks! Excerpts from Haiming Yang's message of 2013-12-11 09:40:32 -0800: > I think it

Re: [openstack-dev] [QA] Tempest blueprints status update and rationale, input demanded

On Wed, Dec 11, 2013 at 01:44:19PM +0100, Giulio Fidente wrote: > hi, > > I'm attempting to rationalize on the status of tempest blueprints. I > need your help so I organized questions in a few open points. > > > * (1) I'm looking for input here on the actual status of the > following blueprints

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

https://blueprints.launchpad.net/keystone/+spec/update-policy-to-cloud On 12/11/2013 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:

Re: [openstack-dev] [Ceilometer] Nomination of Sandy Walsh to core team

> To that end, I would like to nominate Sandy Walsh from Rackspace to > ceilometer-core. Sandy is one of the original authors of StackTach, and > spearheaded the original stacktach-ceilometer integration. He has been > instrumental in many of my codes reviews, and has contributed much of the > exi

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

Hi, I'm trying to clarify the terminology being used for Tuskar, which may be helpful so that we're sure that we're all talking about the same thing :) I'm copying responses from the requirements thread and combining them with current requirements to try and create a unified view. Hopefully,

[openstack-dev] [nova][vmware] VMwareAPI sub-team status update 2013-12-11

Greetings Stackers! The VMwareAPI subteam is still working out a few priorities, but we should have these mostly ironed out by next week's IRC meeting. If you need to comment or adjust expectations be sure to show up and let us know. We had a very active discussion in this week's IRC meeting. I th

Re: [openstack-dev] [QA] Tempest blueprints status update and rationale, input demanded

On 12/12/2013 01:44 AM, Giulio Fidente wrote: > hi, > > I'm attempting to rationalize on the status of tempest blueprints. I > need your help so I organized questions in a few open points. > > > * (1) I'm looking for input here on the actual status of the following > blueprints, which are already a

[openstack-dev] 答复: [Scheduler] about scheduler-as-a-service

It looks to me this schedule as a service is not a service, and it more like an function with some changeable parameters. It needs many nova and cinder functions done first. -原始邮件- 发件人: "Qiu Yu" 发送时间: ‎2013/‎12/‎11 14:41 收件人: "OpenStack Development Mailing List (not for usage questions)

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

I'm going to reply to Dean's and James' posts in one shot because it imho makes most sense. On 11.12.2013 17:00, Dean Troyer wrote: On Wed, Dec 11, 2013 at 9:35 AM, James Slagle wrote: On Wed, Dec 11, 2013 at 7:33 AM, Jiří Stránský wrote: Previously, we had planned Tuskar arcitecture like t

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

I think it might be useful to think about how to integrate savana into heat. When auto scale usually the first created node will be removed first. -原始邮件- 发件人: "Jay Lau" 发送时间: ‎2013/‎12/‎11 23:46 收件人: "OpenStack Development Mailing List" 主题: [openstack-dev] [OpenStack][Heat] AutoScaling s

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

On 12/11/2013 03:51 PM, Russell Bryant wrote: > On 12/10/2013 05:57 PM, Paul McMillan wrote: >> +1 on Tatiana Mazur, she's been doing a bunch of good work lately. >> >> I'm fine with me being removed from core provided you have someone else >> qualified to address security issues as they come up

[openstack-dev] [Ceilometer][Glance][Oslo]Notification issue with Glance

Hello, guys! We faced with Glance notifications issue during Tempest tests for Ceilometer. We tried to send notification by ourselves (during investigation we've found that Glance uses almost the same code): from oslo.config import cfg from oslo import messaging CONF.rabbit_host = 'localhost' C

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

On 11.12.2013 17:13, Ladislav Smola wrote: Hi, thanks for starting this conversation. I will take it little side ways. I think we should be asking why have we needed the tuskar-api. It has done some more complex logic (e.g. building a heat template) or storing additional info, not supported by t

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

On 12/10/2013 08:41 PM, Devananda van der Veen wrote: Tue, Dec 10, 2013 at 12:43 PM, David Kranz > wrote: On 12/09/2013 01:37 PM, Devananda van der Veen wrote: On Fri, Dec 6, 2013 at 2:13 PM, Clark Boylan mailto:clark.boy...@gmail.com>> wrote: On

Re: [openstack-dev] [heat] Stack preview

On Dec 10, 2013, at 3:46 PM, Zane Bitter wrote: > On 10/12/13 15:10, Randall Burt wrote: >> On Dec 10, 2013, at 1:27 PM, Zane Bitter >> wrote: >> >>> On 10/12/13 12:46, Richard Lee wrote: Hey all, We're working on a blueprint

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

On Wed, Dec 11, 2013 at 10:41 AM, Jay Dobies wrote: > > I'm still fuzzy on what OpenStack means when it says *client. Is that just > a bindings library that invokes a remote API or does it also contain the > CLI bits? For the older python-*client projects they are both Python API bindings and a t

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

Configuration Groups is currently developed to associate the datastore version with a configuration that is created. If a datastore version is not presented it will use the default similar to the way instances are created now. This looks like a way of associating the configuration with a datastore

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

On 12/11/2013 04:35 PM, James Slagle wrote: On Wed, Dec 11, 2013 at 7:33 AM, 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 change

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

On 11.12.2013 16:43, Tzu-Mainn Chen wrote: Thanks for writing this all out! - Original Message - Disclaimer: I swear I'll stop posting this sort of thing soon, but I'm new to the project. I only mention it again because it's relevant in that I missed any of the discussion on why proxyin

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

> I will take it little side ways. I think we should be asking why have > we needed the tuskar-api. It has done some more complex logic (e.g. > > building a heat template) or storing additional info, not supported > > by the services we use (like rack associations). > That is a perfectly fine u

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

+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 Mailing List (not for usage questions) Subject: Re: [openstack-dev] [keystone] domain admin ro

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

Hi, thanks for starting this conversation. I will take it little side ways. I think we should be asking why have we needed the tuskar-api. It has done some more complex logic (e.g. building a heat template) or storing additional info, not supported by the services we use (like rack association

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

On Tue, Dec 10, 2013 at 10:49 PM, Jamie Lennox wrote: > Using the default policies it will simply check for the admin role and not > care about the domain that admin is limited to. This is partially a left > over from the V2 api when there wasn't domains to worry about. > > A better example of pol

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

On Wed, Dec 11, 2013 at 9:35 AM, James Slagle wrote: > On Wed, Dec 11, 2013 at 7:33 AM, Jiří Stránský wrote: > > Previously, we had planned Tuskar arcitecture like this: > > > > tuskar-ui <-> tuskarclient <-> tuskar-api <-> heat-api|ironic-api|etc. > > To be clear, tuskarclient is just a library

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

On Wed, Dec 11, 2013 at 10:35 AM, James Slagle wrote: > On Wed, Dec 11, 2013 at 7:33 AM, Jiří Stránský wrote: >> 1) Make a thicker python-tuskarclient and put the business logic there. Make >> it consume other python-*clients. (This is an unusual approach though, i'm >> not aware of any python-*c

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

> On 2013/10/12 19:39, Tzu-Mainn Chen wrote: > >> > >> Ideally, we don't. But with this approach we would take out the > >> possibility to change something or decide something from the user. > >> > >> The 'easiest' way is to support bigger companies with huge deployments, > >> tailored infrastructu

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

Thanks for writing this all out! - Original Message - > Disclaimer: I swear I'll stop posting this sort of thing soon, but I'm > new to the project. I only mention it again because it's relevant in > that I missed any of the discussion on why proxying from tuskar API to > other APIs is loo

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

Greetings, Here come a question related to heat auto scale down. The scenario is as following: I was trying to deploy hadoop cluster with heat Auto Scaling template. When scale up a slave node, I can use user-data to do some post work for configuration file on hadoop master node base on the info

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

On Wed, Dec 11, 2013 at 7:33 AM, 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 and getti

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

UTC 22:00 works for me. Really appreciated. On Wed, Dec 11, 2013 at 12:13 PM, Yongsheng Gong wrote: > UTC 22:00+, which is 6:am beijing time，but if there are guys from Israel > alike, I can get up one hour earlier, just like what I do for neutron > meeting. > > > On Wed, Dec 11, 2013 at 11:08 AM,

[openstack-dev] [Neutron][LBaaS] Weekly subteam meeting at Thursday, 12.12, 14-00 UTC

Hi lbaas folks, Let's meet as usual at #openstack-meeting on Thursday, 12 at 14-00 UTC. The primary discussion points should be: 1) Third party testing 2) L7 rules 3) Loadbalancer instance 4) HA for agents and HA for HAProxy Thanks, Eugene. ___ OpenStac

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

On 12/10/2013 05:57 PM, Paul McMillan wrote: > +1 on Tatiana Mazur, she's been doing a bunch of good work lately. > > I'm fine with me being removed from core provided you have someone else > qualified to address security issues as they come up. My contributions have > lately been reviewing and

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

Disclaimer: I swear I'll stop posting this sort of thing soon, but I'm new to the project. I only mention it again because it's relevant in that I missed any of the discussion on why proxying from tuskar API to other APIs is looked down upon. Jiri and I had been talking yesterday and he mention

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

On 12/10/13 at 11:09am, Flavio Percoco wrote: On 09/12/13 17:37 -0500, Russell Bryant wrote: On 12/09/2013 05:16 PM, Gordon Sim wrote: On 12/09/2013 07:15 PM, Russell Bryant wrote: [...] One other pattern that can benefit from intermediated message flow is in load balancing. If the processi

Re: [openstack-dev] [Gating-Failures] Docs creation is failing

Hi, The <1.2 rule for Sphinx doesn't help, as pointed out by Sean Dague here: http://lists.openstack.org/pipermail/openstack-dev/2013-December/021921.html  The <1.1.99 rule he proposes works for me (on python-swiftclient): https://review.openstack.org/#/c/61378/ Regards, Florent Flament

Re: [openstack-dev] [Gating-Failures] Docs creation is failing

Hey, doc jobs fails because sphinx 1.2 used, all project are now applying <1.2 rule for sphinx to fix it. Here is a thread with additional info: http://lists.openstack.org/pipermail/openstack-dev/2013-December/021863.html Thanks. On Wed, Dec 11, 2013 at 1:30 PM, Wangpan wrote: > +1 > > http

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

A few clarifications added, next time i'll need to triple-read after myself :) On 11.12.2013 13:33, 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 plan

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

+1 for Tatiana Mazur to Horizon Core not sure if only cores should do the vote, but Tatiana has been very active, so it will be well deserved. :-) On 12/11/2013 01:09 PM, Jiri Tomasek wrote: +1 for Tatiana Mazur to Horizon Core On 12/10/2013 09:24 PM, Lyle, David wrote: I would like to no

[openstack-dev] [QA] Tempest blueprints status update and rationale, input demanded

hi, I'm attempting to rationalize on the status of tempest blueprints. I need your help so I organized questions in a few open points. * (1) I'm looking for input here on the actual status of the following blueprints, which are already approved or in a good progress state: https://blueprin

Re: [openstack-dev] Sphinx 1.2 incompatibility (failing -docs jobs)

On 12/10/2013 05:57 PM, James E. Blair wrote: > Hi, > > Sphinx 1.2 was just released and it is incompatible with distutils in > python 2.7. See these links for more info: > > > https://bitbucket.org/birkenfeld/sphinx/pull-request/193/builddoc-shouldnt-fail-on-unicode-paths/diff > http://bug

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

Hi Salvatore, Thank you for your reply. 2013/12/11 Salvatore Orlando : > Hi Yoshihiro, > > In my opinion the use of filters on changes is allowed by the smoketesting > policy we defined. > Notwithstanding that the approach of testing every patch is definitely the > safest, I understand in some ca

  1   2   >