Re: [openstack-dev] [Keystone][Glance] Hierarchical multitenancy and Glance?

Thanks, I’ll have to read! Do you have a quick summary on what role domains are intended to play in this? Has the following statement been decided? 1. Domains may be modified to exist as top-level projects, or they may still exist solely as containers for users with the project hierarchy re

Re: [openstack-dev] [Keystone][Glance] Hierarchical multitenancy and Glance?

Use cases: https://wiki.openstack.org/wiki/HierarchicalMultitenancy Blueprints: (Kilo): https://blueprints.launchpad.net/keystone/+spec/hierarchical-multitenancy

[openstack-dev] [Fuel] Speed Up RabbitMQ Recovering

Hello, I using Fuel 6.0.1 and find that RabbitMQ recover time is long after power failure. I have a running HA environment, then I reset power of all the machines at the same time. I observe that after reboot it usually takes 10 minutes for RabittMQ cluster to appear running master-slave mode in p

Re: [openstack-dev] [glance] Call to action, revisit CIS state

>On 4/27/15, 05:39, "Kuvaja, Erno" wrote: > >>The spec bluntly states that >>there is no security impact from the implementation >> and the concerns should have been brought up so reviewers would have had >>better chance to catch possible threats. >> >> >>I would like you to look back into tho

Re: [openstack-dev] [Keystone][Glance] Hierarchical multitenancy and Glance?

Geoff, Getting a spec on HMT would be helpful, as Nikhil mentioned. As a general question, what it the current adoption of domains / vs hierarchical projects? Is there a wiki or something that highlights what the desired path forward is with regard to domains? Thanks, Travis On 4/27/15, 7:16 PM

Re: [openstack-dev] [nova] Required data migrations in Kilo, need Turbo Hipster tests updated

On 4/23/15 11:41 PM, Dan Smith wrote: That change works on the dataset. However I was referring to the db/object api (which I have no real knowledge of) that it should be able to get_by_uuid unmigrated instances and in my case I got the traceback given in that paste. It's possible I'm just using

[openstack-dev] install custom middleware via devstack

Hi I'm working on a custom middleware which will place on swift-proxy pipeline, just before the latest proxy-logging. how can I force devstack to install my middleware just as I run ./stack.sh? #The point is that I'm looking for a mature and standard to do it, so I'm not going to just edit the sta

Re: [openstack-dev] [Neutron] [Nova] [Cinder] [tc] Should Openstack project maintained by core team keep only API/DB in the future?

On Fri, Apr 24, 2015 at 9:13 PM, Kyle Mestery wrote: > On Fri, Apr 24, 2015 at 4:06 AM, loy wolfe wrote: >> >> It's already away from the original thread, so I start this new one, >> also with some extra tag because I think it touch some corss-project >> area. >> >> Original discuss and reference

[openstack-dev] [puppet] creating a rubygems mirror for OpenStack

Hi, All Puppet OpenStack jobs (lint, syntax, unit and beaker) are quite often affected by rubygems.org downtimes and make all jobs failing randomly because it can't download some gems during the bootstrap. This is something that really affect our CI and we would really appreciate openstack-infra's

Re: [openstack-dev] TC Candidacy

+1 BR, Eli(Li Yong)Qiao From: David Lyle [mailto:dkly...@gmail.com] Sent: Thursday, April 23, 2015 8:57 AM To: OpenStack Development Mailing List Subject: [openstack-dev] TC Candidacy I'm announcing my candidacy for the Technical Committee elections. I have been contributing to OpenStack since

Re: [openstack-dev] [Neutron][LBaaS] Why do we need to select subnet when creating a pool?

I'm assuming you are using LBaaS V2. With that assumption, I'm not sure how you are having to select subnet on the pool. It's not supposed to be a field at all on the pool object. subnet_id is required on the member object right now, but that's something I and others think should just be opti

Re: [openstack-dev] [Neutron] Bump the RPC version required for port_update - AgentNotifierApi

On 27 April 2015 at 18:16, YAMAMOTO Takashi wrote: > > On 27 April 2015 at 09:09, Rossella Sblendido > wrote: > > > >> Hello all, > >> > >> I am working at the blueprint "Restructure the L2 agent" [1] . > >> One of the work item of this blueprint is to modify the port_update > >> message to incl

Re: [openstack-dev] [all] Question for the TC candidates

On 23 April 2015 at 09:14, Chris Dent wrote: > > This might be a bit presumptuous, but why not give it a try... > > This cycle's TC elections didn't come with a set of prepackaged > questions and though the self-nomination messages have included some > very interesting stuff I think it would be u

Re: [openstack-dev] [Neutron] Bump the RPC version required for port_update - AgentNotifierApi

> On 27 April 2015 at 09:09, Rossella Sblendido wrote: > >> Hello all, >> >> I am working at the blueprint "Restructure the L2 agent" [1] . >> One of the work item of this blueprint is to modify the port_update >> message to include the attributes of the ports that were modified. This >> is imple

Re: [openstack-dev] [Keystone][Glance] Hierarchical multitenancy and Glance?

Good points. I’ll add some details. I’m sure the Reseller guys will have some comments. Geoff > On Apr 27, 2015, at 3:32 PM, Nikhil Komawar > wrote: > > Thanks Geoff. Added some notes and questions. > > -Nikhil > > > From: Geoff Arnold > Sent: Monda

Re: [openstack-dev] [Neutron] Bump the RPC version required for port_update - AgentNotifierApi

On 27 April 2015 at 09:09, Rossella Sblendido wrote: > Hello all, > > I am working at the blueprint "Restructure the L2 agent" [1] . > One of the work item of this blueprint is to modify the port_update > message to include the attributes of the ports that were modified. This > is implemented in

Re: [openstack-dev] [Neutron] A big tent home for Neutron backend code

> > > Any project that fails to meet the criteria later can be dropped at any > time. For example, if some repo is clearly unmaintained, it can be > removed. > If we open the door to excluding projects down the road, then wouldn't we need to take into account some form of 3rd party CI validation

[openstack-dev] [openstack][nova] Does anyone use Zookeeper, Memcache Nova ServiceGroup Driver ?

Hi, Does anyone use Zookeeper[1], Memcache[2] Nova ServiceGroup Driver ? If yes how has been your experience with it. It was noticed that most of the deployment try to use the default Database driver[3]. Any experiences with Zookeeper, Memcache driver will be helpful. -Vilobh [1] https://github

Re: [openstack-dev] Navigating the ever changing OpenStack codebase

On 2015-04-27 17:38:25 -0500 (-0500), Kevin L. Mitchell wrote: > Unfortunately, there's one problem with that: you can't tell tox to use > a virtualenv that you've built. We need this capability at present, so > we have to run tests using run_tests.sh instead of tox :( I have an > issue open on t

Re: [openstack-dev] Navigating the ever changing OpenStack codebase

Excerpts from Kevin L. Mitchell's message of 2015-04-27 15:38:25 -0700: > On Mon, 2015-04-27 at 21:42 +, Jeremy Stanley wrote: > > I consider it an unfortunate oversight that those files weren't > > deleted a very, very long time ago. > > Unfortunately, there's one problem with that: you can't

Re: [openstack-dev] [Zaqar] Call for adoption (or exclusion?)

Excerpts from Joe Gordon's message of 2015-04-27 10:36:57 -0700: > On Fri, Apr 24, 2015 at 5:05 PM, Zane Bitter wrote: > > > On 24/04/15 19:02, Joe Gordon wrote: > > > >> > >> > >> On Mon, Apr 20, 2015 at 5:54 AM, Flavio Percoco >> > wrote: > >> > >> Greetings, > >>

[openstack-dev] [api] Missing meetings this week

Hi All, I’ll be out the next few days and will be missing our meetings. Specifically the cross-project meeting [1] and our API WG meeting [2]. On the plus side I got to my action items from the last meeting and “froze” the 3 guidelines up for review and proposed a cross-project session [3] (row

Re: [openstack-dev] [heat] Stack/Resource updated_at conventions

On 27/04/15 13:38, Steven Hardy wrote: On Mon, Apr 27, 2015 at 04:46:20PM +0100, Steven Hardy wrote: AFAICT there's two options: 1. Update the stack.Stack so we store "now" at every transition (e.g in state_set) 2. Stop trying to explicitly control updated_at, and just allow the oslo Timestamp

Re: [openstack-dev] Navigating the ever changing OpenStack codebase

On Mon, 2015-04-27 at 21:42 +, Jeremy Stanley wrote: > I consider it an unfortunate oversight that those files weren't > deleted a very, very long time ago. Unfortunately, there's one problem with that: you can't tell tox to use a virtualenv that you've built. We need this capability at prese

[openstack-dev] [nova-scheduler] Scheduler sub-group (gantt) meeting agenda 4/28

Meeting on #openstack-meeting at 1500 UTC (9:00AM MDT) 1) Liberty specs (tracking page - https://wiki.openstack.org/wiki/Gantt/liberty ) 2) Vancouver design summit - more thoughts? 3) Opens -- Don Dugger "Censeo Toto nos in Kansa esse decisse." - D. Gale Ph: 303/443-3786 _

Re: [openstack-dev] [Keystone][Glance] Hierarchical multitenancy and Glance?

Thanks Geoff. Added some notes and questions. -Nikhil From: Geoff Arnold Sent: Monday, April 27, 2015 5:50 PM To: OpenStack Development Mailing List (not for usage questions) Subject: [openstack-dev] [Keystone][Glance] Hierarchical multitenancy and

Re: [openstack-dev] [all] Question for the TC candidates

On Mon, 27 Apr 2015, Doug Hellmann wrote: I believe all of the posts were on the main OpenStack foundation blog under the "technical committee" tag [1], and they also went to planet.openstack.org for folks who subscribe to the entire community feed. Ah. Some things about that: * in the right

[openstack-dev] [kolla] Alternating Meeting Schedules - Doodle poll inside

Hi, We would like to expand the core team and developers that can participate. Our current 2000 UTC meeting time is not ideal for APAC participants. I am considering moving the meeting to alternating schedules of 1600 UTC and 200 UTC. If you would like to attend the Kolla IRC meeting please f

[openstack-dev] [all] Dependency management summit sessions

Hi, so - https://libertydesignsummit.sched.org/event/4da45ec1390dadcfc1d8a73decbf3f19#.VT6urd_va00 Is an ops track session about dependencies - focusing on the operational side (mysql, mongo, rabbit etc). I'd love to have some developer centric folk in the room, though I'll be doing my best to c

[openstack-dev] [Keystone][Glance] Hierarchical multitenancy and Glance?

In preparation for Vancouver, I’ve been looking for blueprints and design summit discussions involving the application of the Keystone hierarchical multitenancy work to other OpenStack projects. One obvious candidate is Glance, where, for example, we might want domain-local resource visibility a

Re: [openstack-dev] Navigating the ever changing OpenStack codebase

On 2015-04-27 17:07:56 -0400 (-0400), Ronald Bradford wrote: [...] > Specifically, the following two code snippets have become SOP (Standard > Operating Procedure) jumping around VMs and projects and I suspect if you > are a developer of this project, something you are very familiar with. [...] > p

Re: [openstack-dev] [Neutron][Keystone] [Nova] How to validate teanant-id for admin operation

On Mon, Apr 27, 2015 at 6:46 AM, Ajaya Agrawal wrote: > On Mon, Apr 27, 2015 at 6:05 AM, Jamie Lennox > wrote: > >Not to speak for Brant, but i think the confusion here is why you are > doing this. From my perspective you should never be in >a position where > the admin has to enter a raw proje

[openstack-dev] Navigating the ever changing OpenStack codebase

Hi All, I have recently become involved in OpenStack development. After installing a few devstacks (and buying some H/W for my own physical cloud) I settled into learning, reviewing and debugging the Python OpenStack Client (seemed an easy access point). I even published a blog post just 7 days ag

Re: [openstack-dev] [all] Question for the TC candidates

Excerpts from Richard Raseley's message of 2015-04-27 12:55:11 -0700: > Doug Hellmann wrote: > > I think we chose blog posts for their relative permanence, and > > retweetability. Maybe we should post to the mailing list instead, > > if the contributor community follows the list more regularly than

Re: [openstack-dev] [Neutron] A big tent home for Neutron backend code

On 04/22/2015 02:19 PM, Russell Bryant wrote: > a) Adopt these as repositories under the Neutron project team. > > In this case, I would see them operating with their own review teams as > they do today to avoid imposing additional load on the neutron-core or > neutron-specs-core teams. However,

[openstack-dev] [barbican] Storing and retrieving secrets.

Hello. I have a question concerning the creation and retrieval of a secret. I used the orders resource to request a key to be generated of type text/plain. However, I cannot retrieve it of type text/plain. It appears I can only retrieve it of type octet-stream. I just wanted to clarify this is th

Re: [openstack-dev] RegionOne vs. regionOne

> On Apr 27, 2015, at 14:35, Christopher Aedo wrote: > >> On Mon, Apr 27, 2015 at 10:52 AM, Sean M. Collins wrote: >> Oh, I should actually mention which way I think we should go with. >> >> RegionOne should be the convention. > > This came up in January[1][2] relating to case sensitivity in

Re: [openstack-dev] [all] Question for the TC candidates

Doug Hellmann wrote: I think we chose blog posts for their relative permanence, and retweetability. Maybe we should post to the mailing list instead, if the contributor community follows the list more regularly than blogs? I like blog posts for the reasons you mentioned. Perhaps sending a mess

Re: [openstack-dev] [all] Question for the TC candidates

Excerpts from Chris Dent's message of 2015-04-27 17:32:12 +0100: > On Mon, 27 Apr 2015, Doug Hellmann wrote: > > > For outgoing communication, during Kilo (and possibly Juno) we tried > > blogging meeting summaries. Did folks notice? Were the posts useful? > > Is there a TC specific blog place of

Re: [openstack-dev] [glance] Why no DB index on sort parameters

At the very least, an index on the default sort column (created_at) would be appropriate, IMO. Best, -jay On 04/27/2015 01:42 PM, Rushi Agrawal wrote: Now that raises a question: do we really need sorting based on arbitrary keys in our API (e.g. listing images, volumes, instances)? If we have

Re: [openstack-dev] RegionOne vs. regionOne

On Mon, Apr 27, 2015 at 10:52 AM, Sean M. Collins wrote: > Oh, I should actually mention which way I think we should go with. > > RegionOne should be the convention. This came up in January[1][2] relating to case sensitivity in MySQL, Keystone and TripleO, and there's a bug noted[3] as well. I'm

Re: [openstack-dev] change jenkins CI to distinguish different types of failures?

On 2015-04-27 11:38:09 -0600 (-0600), Chris Friesen wrote: [...] > In circumstances like this I wonder if it might make sense to have Jenkins > "abstain" rather than mark it -1. We could then have a job that went around > and re-ran Jenkins tests for cases where it "abstained" previously. [...] I

[openstack-dev] [chef] Openstack-Chef has officially moved to this mailing list

Hey everyone! Per moving to the OpenStack namespace[1] the OpenStack Chef community has moved from our Google Group[2] to this mailing list. This is just a notification to the wider audience that this has happened. -JJ Asghar [1]: https://review.openstack.org/#/c/175000/

[openstack-dev] [Neutron][LBaaS] Why do we need to select subnet when creating a pool?

So when I use Haproxy for LBaaS for Juno, there is a subnet mandatary field that I need to fill in when creating a pool, and later on when I add members, I can use a different subnet(or simply just enter the ip of the member), when adding vip, I can still select a third subnet. So what is the u

Re: [openstack-dev] RegionOne vs. regionOne

Oh, I should actually mention which way I think we should go with. RegionOne should be the convention. -- Sean M. Collins __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@li

Re: [openstack-dev] [Manila] Mount automation using Zeroconf

Hi Clinton, I think there are two main parts that are needed to automatically mount Manila shares. One is the share discovery model, and the other is enabling the virtual machine to mount the share. I think the only benefit to using zeroconf would be as a standard way to broadcast availabili

Re: [openstack-dev] [Zaqar] Call for adoption (or exclusion?)

On Fri, Apr 24, 2015 at 5:19 PM, Zane Bitter wrote: > On 24/04/15 20:00, Joe Gordon wrote: > >> >> >> On Fri, Apr 24, 2015 at 4:35 PM, Fox, Kevin M > > wrote: >> >> Notification might be a good way to integrate with nova. Individual >> tenants might want to do t

Re: [openstack-dev] [glance] Why no DB index on sort parameters

Now that raises a question: do we really need sorting based on arbitrary keys in our API (e.g. listing images, volumes, instances)? If we have this feature in our API, we're bound to run into problems by creating or not creating indexes, at large volumes -- hurts our motive to be easily-implementab

Re: [openstack-dev] [heat] Stack/Resource updated_at conventions

On Mon, Apr 27, 2015 at 04:46:20PM +0100, Steven Hardy wrote: > AFAICT there's two options: > > 1. Update the stack.Stack so we store "now" at every transition (e.g in > state_set) > > 2. Stop trying to explicitly control updated_at, and just allow the oslo > TimestampMixin to do it's job and upd

[openstack-dev] change jenkins CI to distinguish different types of failures?

Hi, I was recently hit with a couple of Jenkins -1 votes due to underlying failures in the test framework which never even completed the installation of the test framework. In circumstances like this I wonder if it might make sense to have Jenkins "abstain" rather than mark it -1. We could

[openstack-dev] [Infra] Meeting Tuesday April 28th at 19:00 UTC

Hi everyone, The OpenStack Infrastructure (Infra) team is having our next weekly meeting on Tuesday April 28th, 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 interest

Re: [openstack-dev] [Zaqar] Call for adoption (or exclusion?)

On Fri, Apr 24, 2015 at 5:05 PM, Zane Bitter wrote: > On 24/04/15 19:02, Joe Gordon wrote: > >> >> >> On Mon, Apr 20, 2015 at 5:54 AM, Flavio Percoco > > wrote: >> >> Greetings, >> >> I'd like my first action as Zaqar's PTL to be based on reflections and >> t

[openstack-dev] RegionOne vs. regionOne

Hi, Currently we have some parts of OpenStack that use "regionOne" while others use "RegionOne" Now, I know that "consistency is the hobgoblin of little minds"[1], but I think in this situation it's worth going through and settling on one way. I've pushed a patch to the install guide fixing the c

Re: [openstack-dev] [heat] Stack/Resource updated_at conventions

On Mon, Apr 27, 2015 at 04:45:10PM +, Randall Burt wrote: > 2 sounds right to me, but does the in-memory representation get updated or > are we forced into a refetch at every change? Yeah, we probably would be, digging some more there's historical context here: https://bugs.launchpad.net/hea

Re: [openstack-dev] [Infra][Cinder] get voting permissions for Infortrend 3rd-party CI

On 03:42 Apr 27, Ryan.Chiang(江明哲) wrote: > Dear Sirs, https://wiki.openstack.org/wiki/Cinder/tested-3rdParty-drivers#When_thirdparty_CI_voting_will_be_required.3F -- Mike Perez __ OpenStack Development Mailing List (not for

Re: [openstack-dev] [glance] Call to action, revisit CIS state

On 4/27/15, 05:39, "Kuvaja, Erno" wrote: >Hi all, > >As you probably know CIS was expanded from Juno metadefs work this cycle >based on spec [1] provided. The implementation was merged in quite a rush >just before feature freeze. > >During the spec review [2] for client functionality for CIS it

[openstack-dev] [puppet] Weekly meeting #33

Hi, Tomorrow is our weekly meeting. Please look at the agenda [1]. Feel free to bring new topics and reviews/bugs if needed. Also, if you had any action, make sure you can give a status during the meeting or in the etherpad directly. See you tomorrow, [1] https://etherpad.openstack.org/p/puppet

Re: [openstack-dev] COMMERCIAL: [heat] Stack/Resource updated_at conventions

2 sounds right to me, but does the in-memory representation get updated or are we forced into a refetch at every change? On Apr 27, 2015, at 10:46 AM, Steven Hardy wrote: > Hi all, > > I've been looking into $subject recently, I raised this bug: > > https://bugs.launchpad.net/heat/+bug/144815

[openstack-dev] [release] keystonemiddleware 1.5.1

The Keystone development team is happy to announce the 1.5.1 release of keystonemiddleware. Barring any last minute bugs, this release will be the keystonemiddleware release that coincides with the Kilo release of OpenStack. This release can be installed from the following locations: * http://tarb

[openstack-dev] [release] python-keystoneclient 1.3.1

The Keystone development team is happy to announce the 1.3.1 release of python-keystoneclient. Barring any last minute bugs, this release will be the keystoneclient release that coincides with the Kilo release of OpenStack. This release can be installed from the following locations: * http://tarba

Re: [openstack-dev] [all] Question for the TC candidates

On Mon, 27 Apr 2015, Doug Hellmann wrote: For outgoing communication, during Kilo (and possibly Juno) we tried blogging meeting summaries. Did folks notice? Were the posts useful? Is there a TC specific blog place of interest? I sometimes stumble on blog postings from people I know are TC peop

[openstack-dev] [heat] Kubernetes AutoScaling with Heat AutoScalingGroup and Ceilometer

Hi All, Deploying Kubernetes(k8s) cluster on any OpenStack based cloud for container based workload is a standard deployment pattern. However, auto-scaling this cluster based on load would require some integration between k8s OpenStack components. While looking at the option of leveraging Heat

Re: [openstack-dev] [Neutron] Bump the RPC version required for port_update - AgentNotifierApi

On 04/27/2015 12:09 PM, Rossella Sblendido wrote: > Hello all, > > I am working at the blueprint "Restructure the L2 agent" [1] . > One of the work item of this blueprint is to modify the port_update > message to include the attributes of the ports that were modified. This > is implemented in this

Re: [openstack-dev] [all] Question for the TC candidates

On Apr 27, 2015, at 9:20 AM, Jay Pipes wrote: > = Have a monthly "Feedback from Operators" conversation = > > Dedicate part or all of one TC IRC meeting time per month to discuss operator > feedback. Invite the operator community to come and tell us what has > improved, what needs improving, a

Re: [openstack-dev] [puppet] Moving forward with puppet-keystone CI (beaker tests)

On 04/22/2015 08:03 PM, Emilien Macchi wrote: * shell testing: yes because it's the way we wrote our providers. We don't necessary need to shell out, but instead implement resources for Serverspec which will use openstackclient to test Keystone/Nova/... resources. I'm currently in process of m

[openstack-dev] [Neutron] Bump the RPC version required for port_update - AgentNotifierApi

Hello all, I am working at the blueprint "Restructure the L2 agent" [1] . One of the work item of this blueprint is to modify the port_update message to include the attributes of the ports that were modified. This is implemented in this patch [2] . The client side of the RPC is in AgentNotifierAp

[openstack-dev] [heat] Stack/Resource updated_at conventions

Hi all, I've been looking into $subject recently, I raised this bug: https://bugs.launchpad.net/heat/+bug/1448155 Basically we've got some historically weird and potentially inconsistent behavior around updated_at, and I'm trying to figure out the best way to proceed. Now, we selectively update

Re: [openstack-dev] KVM Forum 2015 Call for Participation

A friendly reminder that KVM Forum 2015 accepts proposal submissions until this coming Friday. Thanks on behalf of the KVM Forum 2015 Program Committee. Daniel On Wed, Mar 18, 2015 at 09:51:31AM +, Daniel P. Berrange wrote: > =

[openstack-dev] [release] python-ceilometerclient 1.0.14

We are jazzed to announce the (KIlo) release of: python-ceilometerclient 1.0.14: OpenStack Telemetry API Client Library For more details, please see the git log history below and:     https://launchpad.net/python-ceilometerclient/+milestone/1.0.14 Please report issues through launchpad:     ht

Re: [openstack-dev] [glance] Call to action, revisit CIS state

Thanks for your response Kamil, I think the first lesson learnt (again) is when there is >=1 non-native speakers involved make sure you understand the message as it's meant to, not as it has been written or you apprehend it. I'm happy I did not write what I had in my mind at Thu night or Fri mo

Re: [openstack-dev] [Zaqar] Call for adoption (or exclusion?)

On 24/04/15 09:32 +1200, Fei Long Wang wrote: On 24/04/15 06:02, Richard Raseley wrote: Flavio Percoco wrote: I think getting operators to adopt it is key to getting other openstack projects to also adopt it. There is something of a chicken and the egg problem with the integration. Some of th

Re: [openstack-dev] [all] Question for the TC candidates

Chris, apologies for the late reply. No real excuse other than I wanted to hear what the other candidates had to say and listen a bit before I responded. On 04/23/2015 12:14 PM, Chris Dent wrote: Here's the question: What can and should the TC at large, and you specifically, do to ensure qual

Re: [openstack-dev] [all] Question for the TC candidates

On 27/04/15 08:46 -0400, Doug Hellmann wrote: Excerpts from Flavio Percoco's message of 2015-04-27 08:52:01 +0200: On 23/04/15 17:14 +0100, Chris Dent wrote: > >This might be a bit presumptuous, but why not give it a try... > >This cycle's TC elections didn't come with a set of prepackaged >ques

Re: [openstack-dev] [neutron] Need guidance - functional tests and rootwrap

I just checked with another run and the log shows that the vpnaas.filters file is indeed in the .tox area. So, still stumped as to why the rootwrap daemon is looking for the config file in /etc/neutron/rootwrap.d/ Any ideas? PCM On Mon, Apr 27, 2015 at 7:21 AM Paul Michali wrote: > The latter

Re: [openstack-dev] [oslo] eventlet 0.17.3 is now fully Python 3 compatible

Hi, > Keystone client version of the middleware is deprecated and only receiving > minimal security updates. This code is unlikely to see any real changes due > it its deprecation and frozen state. > > We are evaluating how to remove it from the client lib. I wrote a patch to remove keystonecl

Re: [openstack-dev] [nova] Policy rules are killed by the context admin check

Le 23/04/2015 09:10, Sylvain Bauza a écrit : Le 23 avr. 2015 04:49, "Alex Xu" > a écrit : > > > > 2015-04-23 6:55 GMT+08:00 Matt Riedemann >: >> >> >> >> On 4/22/2015 8:32 AM, Sylvain Bauza wrote: >>> >>> Hi, >>> >>> By discussing

Re: [openstack-dev] [cinder] cinder support matrix, chap support?

Yes On Mon, Apr 27, 2015 at 9:49 AM, Jordan Pittier wrote: > Hi, > Isn't CHAP iscsi-specific ? > > Jordan > > On Mon, Apr 27, 2015 at 2:41 PM, Dave Walker wrote: > >> Hi, >> >> Recently I have been curious as to which Cinder drivers support >> authentication. It seems that only a subset do. I

Re: [openstack-dev] [cinder] cinder support matrix, chap support?

Hi, Isn't CHAP iscsi-specific ? Jordan On Mon, Apr 27, 2015 at 2:41 PM, Dave Walker wrote: > Hi, > > Recently I have been curious as to which Cinder drivers support > authentication. It seems that only a subset do. I wondered, is this > something that would be useful on the CinderSupportMatrix

Re: [openstack-dev] [all] Question for the TC candidates

Excerpts from Flavio Percoco's message of 2015-04-27 08:52:01 +0200: > On 23/04/15 17:14 +0100, Chris Dent wrote: > > > >This might be a bit presumptuous, but why not give it a try... > > > >This cycle's TC elections didn't come with a set of prepackaged > >questions and though the self-nomination

[openstack-dev] [cinder] cinder support matrix, chap support?

Hi, Recently I have been curious as to which Cinder drivers support authentication. It seems that only a subset do. I wondered, is this something that would be useful on the CinderSupportMatrix wiki page? Thanks -- Kind Regards, Dave Walker __

Re: [openstack-dev] [all] Proposed Liberty release schedule

@ttx, +1 from me. -- dims On Mon, Apr 27, 2015 at 8:19 AM, Thierry Carrez wrote: > Thierry Carrez wrote: >> [...] >> In summary, here is the proposed Liberty "common" schedule: >> >> liberty-1: June 25th >> liberty-2: July 30th >> liberty-3: September 3rd >> final release: October 15th >> >> Let

Re: [openstack-dev] [all] Proposed Liberty release schedule

Thierry Carrez wrote: > [...] > In summary, here is the proposed Liberty "common" schedule: > > liberty-1: June 25th > liberty-2: July 30th > liberty-3: September 3rd > final release: October 15th > > Let me know if you see issues with it, like crazy holidays somewhere > that would ruin it. No f

Re: [openstack-dev] [glance] Call to action, revisit CIS state

Hi, I'm responsible for the spec for supporting CIS in the glanceclient, as well as the comments which brought some fuss, so would like to clarify some things. 1) That's right - following scenario hasn't been included at the `Security Impact` section. That's because there is no real secur

Re: [openstack-dev] [cinder] Is there any way to put the driver backend error message to the horizon

Alex, Any scratch of the solution you plan to propose? On Mon, Apr 27, 2015 at 5:57 AM, liuxinguo wrote: > Thanks for your suggestion, George. But when I looked into > python-cinderclient (not very deep), I can not find the “wrapper around the > python-cinderclient” you have mentioned. > > Cou

Re: [openstack-dev] [Neutron][Keystone] [Nova] How to validate teanant-id for admin operation

On Mon, Apr 27, 2015 at 6:05 AM, Jamie Lennox wrote: >Not to speak for Brant, but i think the confusion here is why you are doing this. From my perspective you should never be in >a position where the admin has to enter a raw project id like that. Sometimes you have to do just that. For e.g. add

Re: [openstack-dev] [neutron] Need guidance - functional tests and rootwrap

The latter. If you look at Jenkins results for 168115, it shows that there is an invalid config file at /etc/neutron/rootwrap.conf. However, it should be accessing /opt/stack/new/neutron-vpnaas/.tox/dsvm-functional-sswan/etc/neutron/rootwrap.conf. The deploy_rootwrap.sh call in tox.ini should plac

[openstack-dev] [glance] Call to action, revisit CIS state

Hi all, As you probably know CIS was expanded from Juno metadefs work this cycle based on spec [1] provided. The implementation was merged in quite a rush just before feature freeze. During the spec review [2] for client functionality for CIS it came to our attention that the implementation ex

Re: [openstack-dev] [fuel][plugin] What should go in environment_config.yaml when no additional attributes are desired in the Fuel Web UI?

Thanks Evgeniy. From: Evgeniy L [mailto:e...@mirantis.com] Sent: 24 April 2015 16:39 To: OpenStack Development Mailing List (not for usage questions) Cc: Joe Marshall Subject: Re: [openstack-dev] [fuel][plugin] What should go in environment_config.yaml when no additional attributes are desired in

Re: [openstack-dev] [nova][python-novaclient] microversion implementation on client side

I see these changes as really important. We need to establish good patterns other SDKs can copy. On 24 April 2015 at 12:05, Alex Xu wrote: > 2015-04-24 18:15 GMT+08:00 Andrey Kurilin : >> >When user execute cmd without --os-compute-version. The nova client >> > should discover the nova server >s

Re: [openstack-dev] [Neutron][Keystone] [Nova] How to validate teanant-id for admin operation

I believe German is referring to the case where a user performs an operation on behalf of some other project to whom it bears no relationship. In this case the user performing the operation authenticates with keystone with a project_id which is not the one for which the operation is being performed

[openstack-dev] [mistral] Cancelling today's team meeting - 04/27/2015

Team, We decided to cancel today’s meeting because a number of key members won’t be able to attend. Renat Akhmerov @ Mirantis Inc. __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-de

Re: [openstack-dev] [cinder] Is there any way to put the driver backend error message to the horizon

Thanks for your suggestion, George. But when I looked into python-cinderclient (not very deep), I can not find the “wrapper around the python-cinderclient” you have mentioned. Could you please give me a little more hint to find the “wrapper”? Thanks, Liu 发件人: George Peristerakis [mailto:gperi.

[openstack-dev] [all] End of DepFreeze, no more hold on library releases

Hi everyone, Thanks to the efforts of the Release team (special thanks to Doug Hellmann and Sean Dague) and Jeremy Stanley from the Infra team, we finally fixed the stable/kilo and master requirements gate. The following freezes are therefore lifted: - No more DepFreeze[1], master requirements up

Re: [openstack-dev] [nova] Need more suggestion about nova-scheduler patch/147048

Thanks for your comments on the patch I see what you are trying to do now, I think. However, still a bit concerned about the unit tests, but its probably easier to discuss that in gerrit. Thanks, johnthetubaguy On 24 April 2015 at 04:25, Rui Chen wrote: > Hi all: > > I'm working on the patc

Re: [openstack-dev] [all] Gerrit currently down

Thanks to Sergey and Joshua, gerrit is up again! All changes that were done today between around 2:50 UTC and 8:15 UTC, need to be requeued. We've just run those manually for all jobs where a check event was missing, so this should cover all new uploads. If not, add "recheck" to trigger this

[openstack-dev] [all] Gerrit restarted due to the internal issues

Hi folks, I've just restarted review.openstack.org gerrit to fix issue with sending events. It means that some of your patches needs to be rechecked to receive votes from CI. 3rd party CIs maintainers, you probably should restart your Zuul service to ensure it reconnected after gerrit restart. T

Re: [openstack-dev] [OpenStack-Infra] [all] Gerrit currently down

Gerrit has been restarted and it works ok now. On Mon, Apr 27, 2015 at 8:25 AM, Andreas Jaeger wrote: > Our CI system is currently not processing any events. This means that no > new check or gate jobs get started. > > Uploading new patches and reviewing is working fine. > > But new patches uplo