[openstack-dev] [tempest] API testing coverage in tempest

Hi, So i have been tracking API test coverage in tempest in a ad-hoc way where i check the actual tempest tests and the API documentation for that specific component eg. Neutron Is there a better way or documentation maintained by Tempest team for data about API test coverage per OpenStack projec

[openstack-dev] [Cinder] Need +A (workflow +1) for https://review.openstack.org/156940

Hi all, Can someone give +A to https://review.openstack.org/156940 - we have the rest. Need to get this merged for glusterfs CI to pass the snapshot_when_volume_in_use testcases. thanx, deepak __ OpenStack Development Mai

Re: [openstack-dev] auto-abandon changesets considered harmful (was Re: [stable][all] Revisiting the 6 month release cycle [metrics])

On 03/03/15 05:35, Clay Gerrard wrote: > > > On Mon, Mar 2, 2015 at 8:07 AM, Duncan Thomas > wrote: > > Why do you say auto-abandon is the wrong tool? I've no problem with > the 1 week warning if somebody wants to implement it - I can see the > value.

[openstack-dev] [stable] [Glance] Nomination for glance-stable-maint

Hi all, I would like to propose Zhi Yan Liu for the role of stable maintainer for Glance program. Zhi Yan is currently a Glance core member as well as a go-to person for various features in Glance. He is also handling quite well the additional responsibility of Oslo liaison for Glance. Thus,

Re: [openstack-dev] [Glance] Core nominations.

Hi all, After having thoroughly thought about the proposed rotation and evaluating the pros and cons of the same at this point of time, I would like to make an alternate proposal. New Proposal: 1. We should go ahead with adding more core members now. 2. Come up with a plan and give add

[openstack-dev] [gantt] Scheduler sub-group meeting agenda 3/3

Meeting on #openstack-meeting at 1500 UTC (8:00AM MST) 1) Status on cleanup work - https://wiki.openstack.org/wiki/Gantt/kilo (No need to discuss the `Remove direct nova DB access’ spec, it’s been approved ☺ -- Don Dugger "Censeo Toto nos in Kansa esse decisse." - D. Gale Ph: 303/443-37

Re: [openstack-dev] [Devstack] Can't start service nova-novncproxy

Sorry, what you mean " Double-check no make sure that it's enabled " ? I do set the following in my local.conf: enable_service n-nonvc NOVA_VNC_ENABLED=True NOVNCPROXY_URL="http://192.168.6.91:6080/vnc_auto.html"; VNCSERVER_LISTEN=0.0.0.0 VNCSERVER_PROXYCLIENT_

Re: [openstack-dev] [all] Re-evaluating the suitability of the 6 month release cycle

Excerpts from Angus Salkeld's message of 2015-03-02 17:08:15 -0800: > On Tue, Mar 3, 2015 at 9:45 AM, James Bottomley < > james.bottom...@hansenpartnership.com> wrote: > > > On Tue, 2015-02-24 at 12:05 +0100, Thierry Carrez wrote: > > > Daniel P. Berrange wrote: > > > > [...] > > > > The key obser

Re: [openstack-dev] [nova] Shared storage support

-Original Message- From: Jay Pipes Sent Monday, March 02, 2015 16:24 On 02/25/2015 06:41 AM, Daniel P. Berrange wrote: > On Wed, Feb 25, 2015 at 02:08:32PM +, Gary Kotton wrote: >> I understand that this is a high or critical bug but I think that >> we need to discuss more on it and

Re: [openstack-dev] [all] Re-evaluating the suitability of the 6 month release cycle

On Tue, Mar 3, 2015 at 9:45 AM, James Bottomley < james.bottom...@hansenpartnership.com> wrote: > On Tue, 2015-02-24 at 12:05 +0100, Thierry Carrez wrote: > > Daniel P. Berrange wrote: > > > [...] > > > The key observations > > > > > > > > > The first key observation from the

Re: [openstack-dev] [nova] Shared storage support

On 02/25/2015 06:41 AM, Daniel P. Berrange wrote: On Wed, Feb 25, 2015 at 02:08:32PM +, Gary Kotton wrote: I understand that this is a high or critical bug but I think that we need to discuss more on it and try have a more robust model. What I'm not seeing from the bug description is just

Re: [openstack-dev] [all] Re-evaluating the suitability of the 6 month release cycle

On Tue, 2015-02-24 at 12:05 +0100, Thierry Carrez wrote: > Daniel P. Berrange wrote: > > [...] > > The key observations > > > > > > The first key observation from the schedule is that although we have > > a 6 month release cycle, we in fact make 4 releases in that six > > mont

Re: [openstack-dev] auto-abandon changesets considered harmful (was Re: [stable][all] Revisiting the 6 month release cycle [metrics])

On Mon, 2015-03-02 at 13:35 -0800, Clay Gerrard wrote: > I think Tom's suggested "help us help you" is a great pre-abandon > warning. In swift as often as not the last message ended with > something like "you can catch me on freenode in #openstack-swift if > you have any questions" > Good, this

Re: [openstack-dev] auto-abandon changesets considered harmful (was Re: [stable][all] Revisiting the 6 month release cycle [metrics])

Excerpts from Doug Wiegley's message of 2015-03-02 12:47:14 -0800: > > > On Mar 2, 2015, at 1:13 PM, James E. Blair wrote: > > > > Stefano branched this thread from an older one to talk about > > auto-abandon. In the previous thread, I believe I explained my > > concerns, but since the topic sp

Re: [openstack-dev] [all] [api] gabbi: A tool for declarative testing of APIs

On 03/03/15 00:56, Chris Dent wrote: I (and a few others) have been using gabbi[1] for a couple of months now and it has proven very useful and evolved a bit so I thought it would be worthwhile to followup my original message and give an update. Some recent reviews[1] give a sample of how it ca

Re: [openstack-dev] [OSSN 0044] Older versions of noVNC allow session theft

Hi! I just wanted to note that noVNC 0.5.1 is slated to be in Fedora 22 and is currently in EPEL testing for EPEL 6 and EPEL 7 (https://apps.fedoraproject.org/packages/novnc). Best Regards, Solly Ross - Original Message - > From: "Nathan Kinder" > To: "OpenStack Development Mailing List

Re: [openstack-dev] [all] Re-evaluating the suitability of the 6 month release cycle

On Mon, Mar 2, 2015 at 3:38 PM, Joe Gordon wrote: > > > On Mon, Mar 2, 2015 at 9:59 AM, Kyle Mestery wrote: > >> On Mon, Mar 2, 2015 at 9:57 AM, Ihar Hrachyshka >> wrote: >> >>> -BEGIN PGP SIGNED MESSAGE- >>> Hash: SHA1 >>> >>> Hi Daniel, >>> >>> thanks for a clear write-up of the matte

Re: [openstack-dev] [all] Re-evaluating the suitability of the 6 month release cycle

On Mon, Mar 2, 2015 at 9:59 AM, Kyle Mestery wrote: > On Mon, Mar 2, 2015 at 9:57 AM, Ihar Hrachyshka > wrote: > >> -BEGIN PGP SIGNED MESSAGE- >> Hash: SHA1 >> >> Hi Daniel, >> >> thanks for a clear write-up of the matter and food for thought. >> >> I think the idea of having more smooth

Re: [openstack-dev] auto-abandon changesets considered harmful (was Re: [stable][all] Revisiting the 6 month release cycle [metrics])

On Mon, Mar 2, 2015 at 8:07 AM, Duncan Thomas wrote: > Why do you say auto-abandon is the wrong tool? I've no problem with the 1 > week warning if somebody wants to implement it - I can see the value. A > change-set that has been ignored for X weeks is pretty much the dictionary > definition of a

Re: [openstack-dev] [all] Re-evaluating the suitability of the 6 month release cycle

On Mon, Mar 2, 2015 at 11:59 AM, Kyle Mestery wrote: > On Mon, Mar 2, 2015 at 9:57 AM, Ihar Hrachyshka > wrote: > >> -BEGIN PGP SIGNED MESSAGE- >> Hash: SHA1 >> >> Hi Daniel, >> >> thanks for a clear write-up of the matter and food for thought. >> >> I think the idea of having more smoot

[openstack-dev] [OSSN 0044] Older versions of noVNC allow session theft

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Older versions of noVNC allow session theft - --- ### Summary ### Commonly packaged versions of noVNC allow an attacker to hijack user sessions even when TLS is enabled. noVNC fails to set the secure flag when setting cookies containing an authenticat

Re: [openstack-dev] auto-abandon changesets considered harmful (was Re: [stable][all] Revisiting the 6 month release cycle [metrics])

> On Mar 2, 2015, at 1:13 PM, James E. Blair wrote: > > Stefano branched this thread from an older one to talk about > auto-abandon. In the previous thread, I believe I explained my > concerns, but since the topic split, perhaps it would be good to > summarize why this is an issue. > > 1) A co

Re: [openstack-dev] [oslo][openstackclient] transferring maintenance of cliff to the OpenStack client team

On 26/02/15 19:25 -0500, Davanum Srinivas wrote: +1 to the move! +1 from me too On Feb 26, 2015 6:43 PM, "Ben Nemec" wrote: On 02/26/2015 03:57 PM, Doug Hellmann wrote: > The team behind the unified command line tool is preparing to ask the TC to allow us to become an official tea

Re: [openstack-dev] [all] Re-evaluating the suitability of the 6 month release cycle

On Mon, Mar 2, 2015, at 10:57 AM, Ihar Hrachyshka wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > Hi Daniel, > > thanks for a clear write-up of the matter and food for thought. > > I think the idea of having more smooth development mode that would not > make people to wait for 6+

Re: [openstack-dev] Kerberos in OpenStack

Posting response to the mailing list, as I suspect others have these questions. I understand that in the current proposed implementation only keystone runs on apache- httpd. * * *1. My question is that- is it possible to move Nova server on the apache-httpd server just like the way keyst

Re: [openstack-dev] [oslo.policy] guraduation status

On Mon, Mar 2, 2015, at 05:01 AM, Osanai, Hisashi wrote: > oslo.policy folks, > > I'm thinking about realization of policy-based access control in swift > using oslo.policy [1] so I would like to know oslo.policy's status for > graduation. > > [1] > https://github.com/openstack/oslo-specs/blo

[openstack-dev] [Nova] Liberty specs are now open

Hi, this is just a quick note to let you know that Liberty specs are now open for Nova. By open I mean that it is possible to upload such a spec, but I wouldn't expect to see much review effort on these until Kilo is ready. If authors of previously approved specs (Juno or Kilo) want to use the "p

Re: [openstack-dev] auto-abandon changesets considered harmful (was Re: [stable][all] Revisiting the 6 month release cycle [metrics])

On Mon, Mar 2, 2015 at 12:52 PM, James E. Blair wrote: > Doug Wiegley writes: > > > A default query that edited out old, jenkins failing, and -2 stuff > > would be helpful. A default or easy query that highlighted things > > relevant to the current milestone's blueprints and bugs would be SUPER

Re: [openstack-dev] [all] [api] gabbi: A tool for declarative testing of APIs

On 03/02/2015 03:56 AM, Chris Dent wrote: I (and a few others) have been using gabbi[1] for a couple of months now and it has proven very useful and evolved a bit so I thought it would be worthwhile to followup my original message and give an update. Some recent reviews[1] give a sample of how

Re: [openstack-dev] auto-abandon changesets considered harmful (was Re: [stable][all] Revisiting the 6 month release cycle [metrics])

Stefano branched this thread from an older one to talk about auto-abandon. In the previous thread, I believe I explained my concerns, but since the topic split, perhaps it would be good to summarize why this is an issue. 1) A core reviewer forcefully abandoning a change contributed by someone els

Re: [openstack-dev] auto-abandon changesets considered harmful (was Re: [stable][all] Revisiting the 6 month release cycle [metrics])

Doug Wiegley writes: > A default query that edited out old, jenkins failing, and -2 stuff > would be helpful. A default or easy query that highlighted things > relevant to the current milestone's blueprints and bugs would be SUPER > useful to guiding folks towards the most useful reviews to be d

Re: [openstack-dev] auto-abandon changesets considered harmful

On Mon, Mar 2, 2015 at 1:28 PM, Stefano Maffulli wrote: > On Mon, 2015-03-02 at 12:00 -0700, Doug Wiegley wrote: > > Why do you feel the need to keep them? Do your regularly look at > > older patches? Do you know anyone that does? > > > I don't think that's the point. The point is to try improvi

Re: [openstack-dev] auto-abandon changesets considered harmful

On Mon, 2015-03-02 at 12:00 -0700, Doug Wiegley wrote: > Why do you feel the need to keep them? Do your regularly look at > older patches? Do you know anyone that does? > I don't think that's the point. The point is to try improving contributor's life by providing them one last useful comment bef

Re: [openstack-dev] [Manila] Ceph native driver for manila

What is the status on virtfs? I am not sure if it is being maintained. Does anyone know? - Luis - Original Message - From: "Danny Al-Gaaf" To: "OpenStack Development Mailing List (not for usage questions)" , ceph-de...@vger.kernel.org Sent: Sunday, March 1, 2015 9:07:36 AM Subject: R

Re: [openstack-dev] auto-abandon changesets considered harmful (was Re: [stable][all] Revisiting the 6 month release cycle [metrics])

> On Mar 2, 2015, at 11:44 AM, James E. Blair wrote: > > Duncan Thomas writes: > >> Why do you say auto-abandon is the wrong tool? I've no problem with the 1 >> week warning if somebody wants to implement it - I can see the value. A >> change-set that has been ignored for X weeks is pretty muc

Re: [openstack-dev] auto-abandon changesets considered harmful (was Re: [stable][all] Revisiting the 6 month release cycle [metrics])

Duncan Thomas writes: > Why do you say auto-abandon is the wrong tool? I've no problem with the 1 > week warning if somebody wants to implement it - I can see the value. A > change-set that has been ignored for X weeks is pretty much the dictionary > definition of abandoned, and restoring it is o

Re: [openstack-dev] Hyper-V Nova CI Infrastructure

On 03/01/2015 09:13 PM, kwon-ho lee wrote: > Hello, OpenStack dev members, > > Is there any problem on "Hyper-V Nova CI Infrastructure"? > > I don't know why i failed my petch set. > > My first patch set was succeeded , and then i changed the commit message, > then failed on Hyper-V test. > > C

Re: [openstack-dev] [cinder][horizon]Proper error handling/propagation to UI

Thanks Avishay. In our case the middle layer (our storage appliance) doesn't allow a snapshot to be deleted if it has clones due to an internal implementation that tries to optimize storage by using a "Dependency tree" where the base volume is the root of the tree and snapshots or clones are nodes

Re: [openstack-dev] [cinder][horizon]Proper error handling/propagation to UI

Sorry, I meant to say that the expected behavior is that volumes are independent entities, and therefore you should be able to delete a snapshot even if it has volumes created from it (just like you should be able to delete a volume that has clones from it). The exception is that Cinder will not p

[openstack-dev] [Ironic][TripleO] IPMI controller for OpenStack instances

It's been quite a while since my last QuintupleO update, mostly due to excessive busy-ness, but I've been asked about it enough times since then that I decided to make time for it. I made another blog post with more details [1], but the gist is that I have a pyghmi-based IPMI controller for OpenSt

Re: [openstack-dev] [all] Re-evaluating the suitability of the 6 month release cycle

On Mon, Mar 2, 2015 at 9:57 AM, Ihar Hrachyshka wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > Hi Daniel, > > thanks for a clear write-up of the matter and food for thought. > > I think the idea of having more smooth development mode that would not > make people to wait for 6+ month

[openstack-dev] [Infra] Meeting Tuesday March 3rd at 19:00 UTC

Hi everyone, The OpenStack Infrastructure (Infra) team is having our next weekly meeting on Tuesday March 3rd, 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 intereste

[openstack-dev] [all] oslo.log 0.4.0 release

The Oslo team is pleased to announce the release of: oslo.log 0.4.0: oslo.log library This release includes a critical bug fix for nova. For more details, please see the git log history below and: http://launchpad.net/oslo.log/+milestone/0.4.0 Please report issues through launchpad: h

Re: [openstack-dev] [Congress][Delegation] Initial workflow design

Hi Ramki, Good suggestion. I added a paragraph at the top of the doc in the Overview section to explain what Delegation means and mentioned that some policies won’t be delegated. Tim On Feb 26, 2015, at 3:15 PM, Ramki Krishnan mailto:r...@brocade.com>> wrote: Hi Tim, All, The document is i

Re: [openstack-dev] [Congress][Delegation] Initial workflow design

Inline. On Feb 26, 2015, at 3:32 PM, Ramki Krishnan mailto:r...@brocade.com>> wrote: 1) Ruby: One of the issues highlighted in OpenStack (scheduler) and also elsewhere (e.g. Omega scheduler by google) is : Reading “host utilization” state from the data bases and DB (nova:host table) updates a

Re: [openstack-dev] [Congress][Delegation] Initial workflow design

Inline. On Feb 27, 2015, at 6:40 AM, ruby.krishnasw...@orange.com wrote: My first suggestion: why don’t we set up call together with Ramki, Yathi, Debo, as soon as possible ? - How to go forward concretely with the 8 steps for the PoC (details wit

Re: [openstack-dev] olso.db 1.5.0 release

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 03/02/2015 05:51 PM, Mike Bayer wrote: > > > Matt Riedemann wrote: > >> >> >> On 2/26/2015 3:22 AM, Victor Sergeyev wrote: >>> Hi folks! >>> >>> The Oslo team is pleased to announce the release of: oslo.db - >>> OpenStack common DB library >>

Re: [openstack-dev] [all] Re-evaluating the suitability of the 6 month release cycle

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 02/26/2015 01:06 AM, Thomas Goirand wrote: > On 02/24/2015 12:27 PM, Daniel P. Berrange wrote: >> I'm actually trying to judge it from the POV of users, not just >> developers. I find it pretty untenable that in the fast moving >> world of cloud,

Re: [openstack-dev] [Devstack] Can't start service nova-novncproxy

Double-check no make sure that it's enabled. A couple months ago, noVNC got removed from the standard install because devstack was installing it from GitHub. - Original Message - > From: "Chen Li" > To: "OpenStack Development Mailing List (not for usage questions)" > > Sent: Sunday,

Re: [openstack-dev] olso.db 1.5.0 release

Matt Riedemann wrote: > > > On 2/26/2015 3:22 AM, Victor Sergeyev wrote: >> Hi folks! >> >> The Oslo team is pleased to announce the release of: oslo.db - OpenStack >> common DB library >> >> Changes from the previous release: >> >> $ git log --oneline --no-merges 1.4.1..1.5.0 >> 7bfdb6a M

[openstack-dev] [mistral] Team meeting minutes - 03/02/2015

Thanks for coming to our team meeting today. Meeting minutes: http://eavesdrop.openstack.org/meetings/mistral/2015/mistral.2015-03-02-16.00.html Full log: http://eavesdrop.openstack.org/meetings/mistral/2015/m

Re: [openstack-dev] [Murano] Should we run tests on all supported database engines?

What kind of layer do you mean? Right now we have some kind of isolation in the form of separate functions for DB lookups. For example for this case its murano.db.catalog.api.package_search [1]. [1] https://github.com/stackforge/murano/blob/b4918b512010875b9cf3b59d65ff1fbfeaf5f197/murano/db/catal

Re: [openstack-dev] [tempest][glusterfs] Online Snapshot fails with GlusterFS

Duncan, Attila, Thanks for your response. We found a issue when using os_priviledge_user_name which is when we sent this patch https://review.openstack.org/#/c/156940/ Post that we used admin user, its password and admin tenant in cinder.conf to make it work But we thought that using admin cr

[openstack-dev] python-novaclient 2.22.0 released

This is a bug fix and feature release. Available here: http://tarballs.openstack.org/python-novaclient/python-novaclient-2.22.0.tar.gz https://pypi.python.org/pypi/python-novaclient/2.22.0 Changes: mriedem@ubuntu:~/git/python-novaclient$ git log --oneline --no-merges 2.21.0..2.22.0 5f3f52

Re: [openstack-dev] auto-abandon changesets considered harmful (was Re: [stable][all] Revisiting the 6 month release cycle [metrics])

Why do you say auto-abandon is the wrong tool? I've no problem with the 1 week warning if somebody wants to implement it - I can see the value. A change-set that has been ignored for X weeks is pretty much the dictionary definition of abandoned, and restoring it is one mouse click. Maybe put someth

Re: [openstack-dev] [Murano] Should we run tests on all supported database engines?

Hi Andrew, I think we should isolate DB access layer and test this layer extensively on MySQL & PostgreSQL. On Mon, Mar 2, 2015 at 6:57 PM, Andrew Pashkin wrote: > There is a bug: > https://bugs.launchpad.net/murano/+bug/1419743 > > It's about that search on packages is failing if use Postgres

Re: [openstack-dev] [all] Re-evaluating the suitability of the 6 month release cycle

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi Daniel, thanks for a clear write-up of the matter and food for thought. I think the idea of having more smooth development mode that would not make people to wait for 6+ months to release a new feature is great. It's insane to expect that feature

[openstack-dev] [Murano] Should we run tests on all supported database engines?

There is a bug: https://bugs.launchpad.net/murano/+bug/1419743 It's about that search on packages is failing if use Postgres as DB backend. The fix is pretty easy there, but how this bug should be tested? I see such options: 1) Run all tests for all DBs that we support. 2) Run some tests for some

Re: [openstack-dev] [Congress]How to add tempest tests for testing murano driver

Hi Hong, Aaron started working on this, but we don’t have anything in place yet, as far as I know. He’s a starting point. https://review.openstack.org/#/c/157166/ Tim On Feb 26, 2015, at 2:56 PM, Wong, Hong mailto:hong.w...@hp.com>> wrote: Hi Aaron, I am new to congress and trying to write

Re: [openstack-dev] [nova] how safe is it to change NoAuthMiddlewareBase?

On 02/28/2015 11:51 AM, Jay Pipes wrote: > On 02/26/2015 04:27 AM, Sean Dague wrote: >> In trying to move the flavor manage negative tests out of Tempest and >> into the Nova functional tree, I ran into one set of tests which are >> permissions checking. Basically that a regular user isn't allowed

Re: [openstack-dev] auto-abandon changesets considered harmful (was Re: [stable][all] Revisiting the 6 month release cycle [metrics])

John Griffith writes: > For what it's worth, at one point the Cinder project setup an auto-abandon > job that did purge items that had a negative mark either from a reviewer or > from Jenkins and had not been updated in over two weeks. This had > absolutely nothing to do with metrics or statisti

Re: [openstack-dev] [Ironic] Adding vendor drivers in Ironic

On 02/28/2015 09:36 PM, Ramakrishnan G wrote: >> You may not realize you do a disservice to those reading this post and >> those reviewing future patches if you set unreasonable expectations. > >> Telling others that they can expect a patch merged in the same day is >> not reasonable, even if that

Re: [openstack-dev] [cinder][horizon]Proper error handling/propagation to UI

@Duncan: I tried with lvmdriver-1, fails with error: ImageCopyFailure: Failed to copy image to volume: qemu-img: /dev/mapper/stack--volumes--lvmdriver--1-volume--e8323fc5--8ce4--4676--bbec--0a85efd866fc: error while converting raw: Could not open device: Permission denied It's been configured with

Re: [openstack-dev] [Ironic] Adding vendor drivers in Ironic

On Sun, Mar 1, 2015 at 4:32 AM, Gary Kotton wrote: > Hi, > I am just relaying pain-points that we encountered in neutron. As I have > said below it makes the development process a lot quicker for people > working on external drivers. I personally believe that it fragments the > community and feel

Re: [openstack-dev] Fwd: [Neutron] ML2 + Nexus :: update_port_precommit ERROR

Hi Adam – Please email me directly w/ the log information. Thanks, Rich From: Adam Lawson [mailto:alaw...@aqorn.com] Sent: Sunday, March 01, 2015 11:02 PM To: OpenStack Development Mailing List (not for usage questions) Subject: [openstack-dev] Fwd: [Neutron] ML2 + Nexus :: update_port_precommit

Re: [openstack-dev] [Fuel] Change diagnostic snapshot compression algoritm

Actually, we have some improvements with snapshots size and we are going to rethink our snapshots in upcoming releases. Miroslav, could you clarify the importance of this change in 6.1? On Thu, Jan 29, 2015 at 2:30 PM, Tomasz Napierala wrote: > Guys, > > We have requests for this improvement. It

Re: [openstack-dev] [nova][ec2-api] Functional tests for EC2-API in nova

Alex, It's better do a experimental one first before trying to a non-voting: http://git.openstack.org/cgit/openstack-infra/project-config/tree/zuul/layout.yaml#n1509 -- dims On Mon, Mar 2, 2015 at 7:24 AM, Alexandre Levine wrote: > All, > > We've finished setting up the functional testing for t

[openstack-dev] [nova][ec2-api] Functional tests for EC2-API in nova

All, We've finished setting up the functional testing for the stackforge EC2 API project. New test suite consists of 96 API and scenario tests covering almost (tags functionality and client tokens absent) all of the functionality initially covered by original EC2 API tests in Tempest and much

Re: [openstack-dev] [all] [api] gabbi: A tool for declarative testing of APIs

I (and a few others) have been using gabbi[1] for a couple of months now and it has proven very useful and evolved a bit so I thought it would be worthwhile to followup my original message and give an update. Some recent reviews[1] give a sample of how it can be used to validate an existing API

Re: [openstack-dev] [tempest][glusterfs] Online Snapshot fails with GlusterFS

I'm assuming your mean the following lines in nova policy.js: "compute_extension:os-assisted-volume-snapshots:create":"rule:admin_api", "compute_extension:os-assisted-volume-snapshots:delete":"rule:admin_api" These 2 calls are not intended to be made directly via an end user, but via cinder, as a

Re: [openstack-dev] [tempest][glusterfs] Online Snapshot fails with GlusterFS

I think here we should use the same approach as with neutron and nova. Neutron[1] uses the nova admin service user declared here[2]. The 'nova_admin_username' looks like a similar parameter to the 'os_privileged_user_name' declared with [3]. Later we may switch to dedicated per service `admin i

[openstack-dev] [nova] what's the merge plan for current proposed microversions?

This change for the additional attributes for ec2 looks like it's basically ready to go, except it has the wrong microversion on it (as they anticipated the other changes landing ahead of them) - https://review.openstack.org/#/c/155853 What's the plan for merging the outstanding microversions? I b

Re: [openstack-dev] [Keystone] How to check admin authentication?

On 02/03/15 08:53, Dmitry Tantsur wrote: 2015-02-27 17:27 GMT+01:00 Dolph Mathews >: On Fri, Feb 27, 2015 at 8:39 AM, Dmitry Tantsur mailto:dtant...@redhat.com>> wrote: Hi all! This (presumably) pretty basic question tortures me for

Re: [openstack-dev] Need help in configuring keystone

Akshik, When you are beginning an adventure with saml, shibboleth and so on, it's helpful to start with fetching auto-generated shibboleth2.xml file from testshib.org . This should cover most of your use-cases, at least in the testing environment. Marek ___

Re: [openstack-dev] [oslo.policy] guraduation status

Hi, FYI there might be something related to what you plan : https://github.com/stackforge/swiftpolicy/ https://review.openstack.org/#/c/89568/ The project is abandoned but the initial goal was to have the code somehow proposed to be merged in Openstack Swift. Feel free to have a look a continue th

Re: [openstack-dev] Need help in configuring keystone

Hi Akshik, if you look at the log you find these lines: 2015-02-27 22:36:38 CRIT Shibboleth.Application : no MetadataProvider available, configuration is probably unusable 2015-02-27 22:36:38 INFO Shibboleth.Application : no TrustEngine specified or installed, using default chain {ExplicitKey

[openstack-dev] [oslo.policy] guraduation status

oslo.policy folks, I'm thinking about realization of policy-based access control in swift using oslo.policy [1] so I would like to know oslo.policy's status for graduation. [1] https://github.com/openstack/oslo-specs/blob/master/specs/kilo/graduate-policy.rst Thanks in advance, Hisashi Osanai

[openstack-dev] New Driver for LBaaS enhancement

Hello,everyone: we come from China, we have implemented a LBaaS driver for openstack. This driver can drive an LoadBalancer device which also has a security filter functionality for vm instance, including DDos shield, web access control and so on . We provide security through LoadBalancer for p

Re: [openstack-dev] [Keystone] How to check admin authentication?

2015-02-27 17:27 GMT+01:00 Dolph Mathews : > > On Fri, Feb 27, 2015 at 8:39 AM, Dmitry Tantsur > wrote: > >> Hi all! >> >> This (presumably) pretty basic question tortures me for several months >> already, so I kindly seek for help here. >> >> I'm working on a Flask-based service [1] and I'd like

Re: [openstack-dev] [Ironic] Adding vendor drivers in Ironic

On 02/28/2015 07:28 AM, Ramakrishnan G wrote: Hello All, Hi! This is about adding vendor drivers in Ironic. In Kilo, we have many vendor drivers getting added in Ironic which is a very good thing. But something I noticed is that, most of these reviews have lots of hardware-specific code in

[openstack-dev] [Fuel] A new wiki page is created for Fuel Plugins

Hi to everyone, I'd like to inform you that a new wiki page was created for Fuel Plugins - https://wiki.openstack.org/wiki/Fuel/Plugins. Beginning with 6.0 release, Fuel supports Pluggable Architecture; that means, you can download and install plugins for Fuel or even develop your own. The wiki