Re: [openstack-dev] [Fuel] Extend FFE for "Disable queue mirroring for RPC queues in RabbitMQ"

Hi Dmitry, as much as I support the change, and glad that we got time for it, my opinion is that we should not extend a FFE. I have following reasons to think this way: 1) Feature Freeze is time based milestone, with the rational "FF ensures that sufficient share of the ReleaseCycle is dedicated t

Re: [openstack-dev] Fwd: [Neutron] Team meeting this Monday at 2100 UTC

> -Original Message- > From: Kevin Benton [mailto:blak...@gmail.com] > > I liked using the meeting for it because it was a nice way for everyone to get > a snapshot of where each thing was at. +1 The idea of discussing everything on meeting is very good. Everyone interested is on the sa

Re: [openstack-dev] [Fuel] [QA] [Tests] MOS integration tests in SWARM test suite

Hi Boris, yes, we will use Rally verify command to run Tempest tests, at least for [1]. It works fine and we want to use it. On Tue, Dec 8, 2015 at 4:12 AM, Boris Pavlovic wrote: > Timur, > > I hope you are going to use for [1] and [2] Rally verify command? > > > Best regards, > Boris Pavlovic

[openstack-dev] [oslo.db][sqlalchemy][mistral] Configuring default transaction isolation level

Hi, We at Mistral want to move from the default transaction isolation level of REPEATABLE READ to READ COMMITTED as part of a bugfix[1]. I did not find a way to pass the isolation level to sqlachemy using oslo.db and the current solution is to use monkey-patching[2] that adds the "isolation_le

[openstack-dev] [Infra][Nova] Request for voting permissions for Third-party Mellanox CI system

Hi all, Mellanox Nova CI[1] is asking for 'voting' permissions on Nova project. We are running as 'non voting' CI more than 6 month already[2] And feel quite confident about its stability. [1] https://wiki.openstack.org/wiki/ThirdPartySystems/Mellanox_CI [2] http://144.76.193.39:8080/job/Nova-ML2-

Re: [openstack-dev] [ironic] RFC: stop using launchpad milestones and blueprints

Hi all, I have a question regarding #1 (Stop using LP for blueprints): what should we now use instead of "specifies" and "implements" Gerrit tags in commit messages? Simple Depends-On: should suffice but is not visually specific enough, and only replaces "implements" tag. Also as a side note, s

[openstack-dev] [vitrage] Next vitrage meeting

Hi, Vitrage next weekly meeting will be tomorrow, Wednesday at 9:00 UTC, on #openstack-meeting-3 channel. Agenda: * Current status and progress from last week * Review action items * Next steps * Open Discussion You are welcome to join. Thanks, Ifat. _

Re: [openstack-dev] [Murano] How to debug a failed deployment?

Hi Vahid, looks like trace in bug should not block engine run, we are currently investigating it. If you are seeing that trace, then you are able to get engine logs :) Can you start your deployment and attach all engine logs even with the trace? Regards, Kate. On Tue, Dec 8, 2015 at 4:12 AM,

[openstack-dev] [midonet] Split up python-midonetclient

Hi, As Takashi Yamamoto raised in another thread [0], python-midonetclient should be split out into its own repo. There's two major reasons for this: 1) (Downstream) packaging: midonet and python-midonetclient are two distinct packages, and therefore should have distinct upstream tarballs - which

Re: [openstack-dev] [Openstack-operators] [keystone] Removing functionality that was deprecated in Kilo and upcoming deprecated functionality in Mitaka

On 8 December 2015 at 07:53, Thomas Goirand wrote: > On 12/01/2015 07:57 AM, Steve Martinelli wrote: > > Trying to summarize here... > > > > - There isn't much interest in keeping eventlet around. > > - Folks are OK with running keystone in a WSGI server, but feel they are > > constrained by Apac

[openstack-dev] [tricircle]Stateless design proposal for Tricircle project

Hi, Managing multiple instances of OpenStack is a headache. Each OpenStack instance is individual silo, with its separate resources, networks, images, etc. Tricircle, the project aiming to address this headache, a Top (aka cascading) minimalist "OpenStack instance" will manages multiple Bottom

[openstack-dev] [nova][doc][tempest] How to handle HTTP203

Hi, Today, we have virtual API document sprint and we are facing a problem related to HTTP203 (Non-Authoritative Information). The api-site(http://developer.openstack.org/api-ref-compute-v2.1.html) contains HTTP203 as one of valid status codes for each API operation, but nova implementation code d

[openstack-dev] creating docs for different versions

Hi all, Is there a good way to create documentation for various versions of code? I see there's description of how to do it for branches master and stable/release_name, but is that tied to the actual OpenStack releases? Specifically I have in mind security projects like Bandit or Anchor, where we

Re: [openstack-dev] [heat] Rico Lin for heat-core

- Original Message - > Hi all. > > I'd like to nominate Rico Lin for heat-core. He did awesome job with > providing useful and valuable reviews. Also his contribution is really high > [1] . > > [1] http://stackalytics.com/report/contribution/heat-group/60 > > Heat core-team, please vote

Re: [openstack-dev] [Neutron][TaaS] Query regarding TaaS API

On Mon, Dec 07, 2015 at 09:24:02PM EST, reedip banerjee wrote: > Dear Members of Neutron-TaaS community, > > One of the points discussed in the last meeting , was whether we need to > modify the API endpoints from > /v2_0/taas/ to /v2_0 > Most of the Extensions in Neutron are listed under v2_0, a

Re: [openstack-dev] [Neutron][TaaS] Query regarding TaaS API

On Mon, Dec 07, 2015 at 10:26:53PM EST, Sean M. Collins wrote: > FWaaS for example is v2.0/fw/ Sorry - typo v2_0/fw/ -- Sean M. Collins __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack

Re: [openstack-dev] [release][oslo] ImportError: No module named netifaces

As u wish: https://review.openstack.org/#/c/254523/ -Josh Jeremy Stanley wrote: On 2015-12-07 17:37:41 -0800 (-0800), Joshua Harlow wrote: Should be fixed in https://review.openstack.org/#/c/254379/ (once that flushes through all the things); follow ups can tweak that to work in a different m

Re: [openstack-dev] [release][oslo] ImportError: No module named netifaces

I tossed up a patch to release 3.2.0: https://review.openstack.org/#/c/254519/ stevemar From: Jeremy Stanley To: "OpenStack Development Mailing List (not for usage questions)" Date: 2015/12/07 09:56 PM Subject:Re: [openstack-dev] [release][oslo] ImportError: No mo

Re: [openstack-dev] [keystone] Removing functionality that was deprecated in Kilo and upcoming deprecated functionality in Mitaka

On Monday, December 7, 2015, Thomas Goirand wrote: > On 12/01/2015 07:57 AM, Steve Martinelli wrote: > > Trying to summarize here... > > > > - There isn't much interest in keeping eventlet around. > > - Folks are OK with running keystone in a WSGI server, but feel they are > > constrained by Apac

[openstack-dev] 答复: [heat] Rico Lin for heat-core

+ 1 ：） 发件人: Sergey Kraynev [mailto:skray...@mirantis.com] 发送时间: 2015年12月7日 20:39 收件人: OpenStack Development Mailing List (not for usage questions) 主题: [openstack-dev] [heat] Rico Lin for heat-core Hi all. I'd like to nominate Rico Lin for heat-core. He did awesome job with providing useful and

Re: [openstack-dev] [release][oslo] ImportError: No module named netifaces

On 2015-12-07 17:37:41 -0800 (-0800), Joshua Harlow wrote: > Should be fixed in https://review.openstack.org/#/c/254379/ (once that > flushes through all the things); follow ups can tweak that to work in a > different manner. Well, needs a follow-up oslo.utils release tagged (3.2.0?) so that other

Re: [openstack-dev] Documentation containing external resource links & privacy breaches

On Mon, Dec 7, 2015 at 3:18 PM, Cory Benfield wrote: > > > On 7 Dec 2015, at 18:37, Thomas Goirand wrote: > > > > > > The reason why I'd like an env var, is that I could simply modify > > openstack-pkg-tools (which is included in every debian/rules) to set > > that variable once and for all. For

Re: [openstack-dev] [Neutron][TaaS] Query regarding TaaS API

Dear Members of Neutron-TaaS community, One of the points discussed in the last meeting , was whether we need to modify the API endpoints from /v2_0/taas/ to /v2_0 Most of the Extensions in Neutron are listed under v2_0, and do not need any separate Parent ID. I would like to know if there is an

Re: [openstack-dev] Fwd: [Neutron] Team meeting this Monday at 2100 UTC

I liked using the meeting for it because it was a nice way for everyone to get a snapshot of where each thing was at. On Dec 7, 2015 3:14 PM, "Armando M." wrote: > Hi neutrinos, > > During today's meeting [1] we went through the outstanding blueprints, but > we only managed to look at a little ov

Re: [openstack-dev] [release][oslo] ImportError: No module named netifaces

Should be fixed in https://review.openstack.org/#/c/254379/ (once that flushes through all the things); follow ups can tweak that to work in a different manner. Jeremy Stanley wrote: And there's a bug open at https://launchpad.net/bugs/1523706 for this issue as well.

Re: [openstack-dev] [glance] Add Ian Cordasco back into glance-core

+1 from me! Glad to have Ian back. On 12/7/15, 11:36 AM, "Flavio Percoco" wrote: >Greetings, > >Not long ago, Ian Cordasco, sent an email out stepping down from his >core roles as he didn't have the time to dedicate to the project >team's he was part of. > >Ian has contacted me mentioning that

[openstack-dev] Cross-Project Meeting SKIPPED, Tue Dec 8th, 21:00 UTC

Hi all! We will be skipping the cross-project meeting since there are no agenda items to discuss, but someone can add one [1] to call a meeting next time. We also have a new meeting channel which is #openstack-meeting-cp where the cross-project meeting will now take place at it's usual time Tuesd

Re: [openstack-dev] [heat] Rico Lin for heat-core

+1. From: Sergey Kraynev [mailto:skray...@mirantis.com] Sent: Monday, December 07, 2015 6:09 PM To: OpenStack Development Mailing List (not for usage questions) Subject: [openstack-dev] [heat] Rico Lin for heat-core Hi all. I'd like to nominate Rico Lin for heat-core. He did awesome job with pro

Re: [openstack-dev] [Fuel] [QA] [Tests] MOS integration tests in SWARM test suite

Timur, I hope you are going to use for [1] and [2] Rally verify command? Best regards, Boris Pavlovic On Mon, Dec 7, 2015 at 6:09 AM, Timur Nurlygayanov < tnurlygaya...@mirantis.com> wrote: > Hi Fuel team, > > we have a lot of automated integration tests for OpenStack verification > and we wan

Re: [openstack-dev] [Murano] How to debug a failed deployment?

Hi Stan, Not sure how I can enable murano engine log. Anyway, you were right that murano engine was not running. I started it and am now hitting this bug: https://bugs.launchpad.net/murano/+bug/1521087 I guess I'll have to wait until the fix is released. Thanks. Regards, --Vahid ___

Re: [openstack-dev] [nova] no user/project validation in "nova quota-show"?

2015-12-08 8:38 GMT+08:00 Kevin L. Mitchell : > On Mon, 2015-12-07 at 18:21 -0600, Chris Friesen wrote: > > Can someone explain why nova doesn't seem to be doing any validation in > the > > "nova quota-show" command? (At least in kilo/stable.) > > > > If I run: > > nova --debug quota-show --tena

Re: [openstack-dev] [nova] no user/project validation in "nova quota-show"?

On Mon, 2015-12-07 at 18:21 -0600, Chris Friesen wrote: > Can someone explain why nova doesn't seem to be doing any validation in the > "nova quota-show" command? (At least in kilo/stable.) > > If I run: > nova --debug quota-show --tenant aprojectdoesnotexist --user nosuchuser > > the debug in

[openstack-dev] [nova] no user/project validation in "nova quota-show"?

Can someone explain why nova doesn't seem to be doing any validation in the "nova quota-show" command? (At least in kilo/stable.) If I run: nova --debug quota-show --tenant aprojectdoesnotexist --user nosuchuser the debug info shows: DEBUG (connectionpool:383) "GET /v2/ceddf233621f4772a8b

Re: [openstack-dev] [Openstack-operators] [keystone] Removing functionality that was deprecated in Kilo and upcoming deprecated functionality in Mitaka

On 12/01/2015 07:57 AM, Steve Martinelli wrote: > Trying to summarize here... > > - There isn't much interest in keeping eventlet around. > - Folks are OK with running keystone in a WSGI server, but feel they are > constrained by Apache. > - uWSGI could help to support multiple web servers. > > M

[openstack-dev] [neutron] neutron metadata agent config

Hi, I am trying to enable https protocol for communication between neutron metadata agent and nova-metadata-service. Is it required to enable anything on the nova side? Not sure what should be the config values for these fields in the neutron-metadata_agent.ini file. Where do you find these val

Re: [openstack-dev] Documentation containing external resource links & privacy breaches

On 12/07/2015 10:18 PM, Cory Benfield wrote: > >> On 7 Dec 2015, at 18:37, Thomas Goirand wrote: >> >> >> The reason why I'd like an env var, is that I could simply modify >> openstack-pkg-tools (which is included in every debian/rules) to set >> that variable once and for all. For example, just

Re: [openstack-dev] [Openstack-operators] [keystone] Removing functionality that was deprecated in Kilo and upcoming deprecated functionality in Mitaka

On Mon, Dec 07, 2015 at 06:18:04PM -0500, Steve Martinelli wrote: > > ... re-adding the operators mailing list. > > sounds like we should document how to do this, with the assertion that it > is not tested with our CI. > > with that said, we should try to have a job that sets up keystone with >

[openstack-dev] [Tacker] Agenda for tomorrow's IRC meeting

Quick reminder on tomorrow's weekly meeting @ 1700 UTC on IRC #openstack-meeting-4. Here is the planned agenda, https://wiki.openstack.org/wiki/Meetings/Tacker#Meeting_Dec_8.2C_2015 - Midcycle Meetup plans - Mitaka Blueprint Updates - Enhanced VNF Placement - adhoc IRC mtg plan

Re: [openstack-dev] [release][oslo] ImportError: No module named netifaces (was: oslo.utils release 3.1.0)

And there's a bug open at https://launchpad.net/bugs/1523706 for this issue as well. -- Jeremy Stanley __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?sub

Re: [openstack-dev] [Openstack-operators] [keystone] Removing functionality that was deprecated in Kilo and upcoming deprecated functionality in Mitaka

... re-adding the operators mailing list. sounds like we should document how to do this, with the assertion that it is not tested with our CI. with that said, we should try to have a job that sets up keystone with nginx that is run periodically (similar to our eventlet job at the moment). steve

Re: [openstack-dev] [release][oslo] ImportError: No module named netifaces (was: oslo.utils release 3.1.0)

On 2015-12-07 23:03:56 + (+), Jeremy Stanley wrote: [...] > from oslo_utils import netutils [...] FWIW, here's a query for repos following the above pattern: http://codesearch.openstack.org/?q=import%20netutils Any of those not carrying either netifaces or oslo.utils[netiface

[openstack-dev] [release][oslo] ImportError: No module named netifaces (was: oslo.utils release 3.1.0)

On 2015-12-07 22:56:16 +0300 (+0300), dava...@gmail.com wrote: > We are glad to announce the release of: > > oslo.utils 3.1.0: Oslo Utility library [...] > 2abbe1c Move netifaces to extras [...] > Requirements updates > > > diff --git a/requirements.txt b/requirements.txt > i

Re: [openstack-dev] [Openstack-operators] [keystone] Removing functionality that was deprecated in Kilo and upcoming deprecated functionality in Mitaka

On Dec 7, 2015 17:51, "Brant Knudson" wrote: > > > > On Tue, Dec 1, 2015 at 12:57 AM, Steve Martinelli wrote: >> >> Trying to summarize here... >> >> - There isn't much interest in keeping eventlet around. >> - Folks are OK with running keystone in a WSGI server, but feel they are constrained by

Re: [openstack-dev] Nominations open for the N and O names of OpenStack

On 11/09/2015 08:27 AM, Monty Taylor wrote: > Hey everybody! > > It's release naming time, and this time we get to do two at once! > > If you'd like to propose a name, there are two wiki pages: > > For the N release, where the geographic region is "Texas Hill Country": > > https://wiki.openstac

Re: [openstack-dev] [Openstack-operators] [keystone] Removing functionality that was deprecated in Kilo and upcoming deprecated functionality in Mitaka

On Tue, Dec 1, 2015 at 12:57 AM, Steve Martinelli wrote: > Trying to summarize here... > > - There isn't much interest in keeping eventlet around. > - Folks are OK with running keystone in a WSGI server, but feel they are > constrained by Apache. > - uWSGI could help to support multiple web serve

Re: [openstack-dev] [magnum] Mesos Conductor

Hi Bharath, Sorry for late reply. Below is my opinions. For #1, I am not sure if it is a good idea. Currently, container-create is only supported in swarm bay. Its implementation doesn’t support json file (it supports accepting optional flags and mapping them to “docker create”). Therefore, ad

Re: [openstack-dev] [all] [release] New Mitaka release schedule page

On 12/04/2015 05:50 AM, Thierry Carrez wrote: > Hi everyone, > > As part of the effort to move reference information off the wiki to a > more peer-reviewable area, the Mitaka release schedule page was moved to: > > http://docs.openstack.org/releases/schedules/mitaka.html > > One side benefit is

Re: [openstack-dev] [Fuel] Extend FFE for "Disable queue mirroring for RPC queues in RabbitMQ"

Hello Dmitry, I like this idea and very much appreciate it. +1 from me :) A. On Mon, Dec 7, 2015 at 9:48 PM, Dmitry Mescheryakov < dmescherya...@mirantis.com> wrote: > Hello folks, > > I'd like to request extension of current FFE for the feature [1]. During > the three FFE days we merged the spe

[openstack-dev] Fwd: [Neutron] Team meeting this Monday at 2100 UTC

Hi neutrinos, During today's meeting [1] we went through the outstanding blueprints, but we only managed to look at a little over half of them. Would you guys like to continue the conversation during next week's meeting or shall we ask for people's status updates offline? An update on the BP's wh

[openstack-dev] [ironic] weekly subteam status report

Hi, We are pleased to present this week's subteam report for Ironic. As usual, this is pulled directly from the Ironic whiteboard[0] and formatted. Bugs (dtantsur) === (diff with Nov 30) - Open: 175 (+1). 12 new (+1), 61 in progress (+1), 1 critical (+1), 16 high and 9 incomplete

Re: [openstack-dev] Documentation containing external resource links & privacy breaches

> On 7 Dec 2015, at 18:37, Thomas Goirand wrote: > > > The reason why I'd like an env var, is that I could simply modify > openstack-pkg-tools (which is included in every debian/rules) to set > that variable once and for all. For example, just adding in > openstack-pkt-tools's pkgos.make: > >

[openstack-dev] [neutron] Linux Bridge CI is now a voting gate job

It's been a couple months - the last time I posted on this subject we were still working on getting Linux Bridge to become an experimental[1] job. During the Liberty cycle, the Linux Bridge CI was promoted from experimental status, to being run on all Neutron changes, but non-voting. Well, we're f

[openstack-dev] [puppet] including openstacklib::openstackclient

I found this bug in the liberty branch [1] over the weekend in the handling of openstack client between glance & keystone. As a part of fixing that I've discussed with Clayton and Michael Chapman just what the right way is to include the openstackclient. Keystone does it by conditionally including

[openstack-dev] [Fuel] Extend FFE for "Disable queue mirroring for RPC queues in RabbitMQ"

Hello folks, I'd like to request extension of current FFE for the feature [1]. During the three FFE days we merged the spec [2] after big discussion and made a couple iterations over the implementation [3]. We had a chat with Bogdan on how to progress and here are the action items still need to be

Re: [openstack-dev] [fuel][plugins]Security problem in Fuel 7.0

Alexey, Eugene I understand your concerns, but it is what the plugin is about - we allow to run tasks on the master node for the sake of deployment flexibility. If you are concerned about security complications you should either use certified plugins or even test them by yourselves in a sandbox. S

Re: [openstack-dev] [puppet] proposing Sofer Athlan Guyot part of puppet-keystone core team

On 12/03/2015 03:05 PM, Emilien Macchi wrote: > Hi, > > For some months, Puppet OpenStack group has been very lucky to have > Sofer working with us. > He became a huge contributor to puppet-keystone, he knows the module > perfectly and wrote insane amount of code recently, to bring new > feature

Re: [openstack-dev] [Fuel] Patch size limit

On Mon, Dec 7, 2015 at 3:32 AM Roman Prykhodchenko wrote: > Maciej, thanks for bringing this topic up for the discussion! > > I absolutely agree with the idea that at this point we have a problem with > patch size. Patches that are too big usually have two major issues: they > either don’t get re

Re: [openstack-dev] [magnum]storage for docker-bootstrap

Until I see evidence to the contrary, I think adding some bootstrap complexity to simplify the process of bay node image management and customization is worth it. Think about where most users will focus customization efforts. My guess is that it will be within these docker images. We should ask

Re: [openstack-dev] [glance] Add Ian Cordasco back into glance-core

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 +1 welcome back! On 08/12/15 05:36, Flavio Percoco wrote: > Greetings, > > Not long ago, Ian Cordasco, sent an email out stepping down from his > core roles as he didn't have the time to dedicate to the project > team's he was part of. > > Ian has co

Re: [openstack-dev] [fuel][plugins]Security problem in Fuel 7.0

Guys, we can not create any limitations on plugins ability to do things that we allow with the 'core' system. We need to be lees strict and more flexible with the plugin framework not constrict it randomly because there is a way to execute dangerous code. We are in the business of buiding, deployin

Re: [openstack-dev] [glance] Add Ian Cordasco back into glance-core

+1 Glad to see this happen. Thanks, Lin. -Original Message- From: Flavio Percoco [mailto:fla...@redhat.com] Sent: Monday, December 7, 2015 10:36 AM To: openstack-dev@lists.openstack.org Subject: [openstack-dev] [glance] Add Ian Cordasco back into glance-core Greetings, Not long ago, Ia

Re: [openstack-dev] [glance] Add Ian Cordasco back into glance-core

+2 That's awesome :D - Sabari On Mon, Dec 7, 2015 at 11:25 AM, Yang, Lin A wrote: > +1 > Glad to see this happen. > > Thanks, > Lin. > > -Original Message- > From: Flavio Percoco [mailto:fla...@redhat.com] > Sent: Monday, December 7, 2015 10:36 AM > To: openstack-dev@lists.openstack.org

Re: [openstack-dev] [fuel][plugins]Security problem in Fuel 7.0

+1 to Eugene here. Eventually we will need to more strictly define Plugins framework and SDK and limit possible actions to the set of supported ones. This is required not only for security and/or stability reasons, but for upgrade purposes as well. On the other hand, we need to retain certain flex

Re: [openstack-dev] [heat] Rico Lin for heat-core

On 08/12/15 01:39, Sergey Kraynev wrote: Hi all. I'd like to nominate Rico Lin for heat-core. He did awesome job with providing useful and valuable reviews. Also his contribution is really high [1] . [1] http://stackalytics.com/report/contribution/heat-group/60 Heat core-team, please vote w

Re: [openstack-dev] [heat] Rico Lin for heat-core

+1 :) On Mon, Dec 7, 2015, 17:12 Thomas Herve wrote: > On Mon, Dec 7, 2015 at 1:39 PM, Sergey Kraynev > wrote: > >> >> Hi all. >> >> I'd like to nominate Rico Lin for heat-core. He did awesome job with >> providing useful and valuable reviews. Also his contribution is really high >> [1] . >> >>

Re: [openstack-dev] [fuel][plugins]Security problem in Fuel 7.0

For future Fuel versions we could/should develop kind of RBAC model for accessing internal components. I'm not sure if current nailgun/astute provides any capability like this. Also plugins often interacts with operating system itself, which is another area of concern. IMO we could only rely on plu

Re: [openstack-dev] Documentation containing external resource links & privacy breaches

On 12/07/2015 06:07 PM, Cory Benfield wrote: > >> On 7 Dec 2015, at 16:10, Thomas Goirand wrote: >> >> Cory, >> >> Thanks a lot for this patch. >> >> If I understand well, in Debian, I'd have to remove the: >> >> [options] >> analytics_tracking_code = UA-17511903-1 >> >> from the default theme.co

Re: [openstack-dev] [fuel][plugins]Security problem in Fuel 7.0

Stas, I fear that often even developer of a code cannot verify his own code completely, let alone some third-party validation teams. Does the ability to strictly limit plugin actions by the list of intended environments looks nonviable to you? On 07.12.2015 20:38, Stanislaw Bogatkin wrote:

Re: [openstack-dev] [Manila] Tempest scenario tests vs. gate condition

On Mon, Dec 7, 2015 at 6:14 PM, Ben Swartzlander wrote: > On 12/03/2015 06:38 AM, John Spray wrote: >> >> Hi, >> >> We're working towards getting the devstack/CI parts ready to test the >> forthcoming ceph native driver, and have a question: will a driver be >> accepted into the tree if it has CI

Re: [openstack-dev] [fuel][plugins]Security problem in Fuel 7.0

Yes, I am aware that this is the expected behavior, at least from the developer point of view. Still, some functionality to confine plugin actions within the environment where it is supposed to run would be an useful option, what do you think? On 07.12.2015 20:19, Andrew Woodward wrote: I'd

Re: [openstack-dev] [Manila] Tempest scenario tests vs. gate condition

On 12/03/2015 06:38 AM, John Spray wrote: Hi, We're working towards getting the devstack/CI parts ready to test the forthcoming ceph native driver, and have a question: will a driver be accepted into the tree if it has CI for running the api/ tempest tests, but not the scenario/ tempest tests?

[openstack-dev] [Infra] Meeting Tuesday December 8th at 19:00 UTC

Hi everyone, The OpenStack Infrastructure (Infra) team is having our next weekly meeting on Tuesday December 8th, at 19:00 UTC in #openstack-meeting Meeting agenda available here: https://wiki.openstack.org/wiki/Meetings/InfraTeamMeeting#Agenda_for_next_meeting Anyone is welcome to to add agenda

Re: [openstack-dev] [neutron] Multiple locations for documentation of features

On Mon, Dec 07, 2015 at 12:18:29PM EST, Carl Baldwin wrote: > On Fri, Dec 4, 2015 at 12:22 PM, Henry Gessau wrote: > > 1. RFE: "I want X" > > 2. Spec: "I plan to implement X like this" > > 3. devref: "How X is implemented and how to extend it" > > 4. OS docs: "API and guide for using X" > > > > On

Re: [openstack-dev] [fuel][plugins]Security problem in Fuel 7.0

+1 to Andrew. Plugins created for run some code and plugin verification is the source of trust there. On Mon, Dec 7, 2015 at 8:19 PM, Andrew Woodward wrote: > I'd have to say that this is expected behavior. I'm not sure what you > would hope to prohibit when these kinds of things are necessary f

Re: [openstack-dev] [glance] Add Ian Cordasco back into glance-core

On Mon, Dec 07, 2015 at 12:06:03PM -0430, Flavio Percoco wrote: > Greetings, > > Not long ago, Ian Cordasco, sent an email out stepping down from his > core roles as he didn't have the time to dedicate to the project > team's he was part of. > > Ian has contacted me mentioning that he's gotten cl

[openstack-dev] ML2 TypeManager question

Hello, Recently I was checking something in code of ML2 Type manager (neutron.plugins.ml2.managers) and I found in TypeManager class in method create_network_segments that to this method as argument is passed "tenant_id" but I can't find where it is used. Can someone more experienced explain me

Re: [openstack-dev] [glance] Add Ian Cordasco back into glance-core

+1 ☺ From: Nikhil Komawar [mailto:nik.koma...@gmail.com] Sent: Monday, December 07, 2015 8:55 AM To: Flavio Percoco ; OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [glance] Add Ian Cordasco back into glance-core +2 Great to see this happen. On 12/7/

Re: [openstack-dev] [glance] Auth_version from 'old style' URLs in the database

Excerpts from Flavio Percoco's message of 2015-12-04 07:00:53 -0800: > On 03/12/15 16:24 +, Bunting, Niall wrote: > >Hi, > > > >Currently glance will use an auth_url if in the database. Eg. > >10.0.0.8:5000/v2.0 > > > >However glance currently takes the auth_version from the config > >files. T

Re: [openstack-dev] [all] [tc] [ironic] Picking an official name for a subproject (ironic-inspector in this case)

I also vote for baremetal-inspection - punning names are fun, but increase the amount of stuff new developers have to learn. I'm totally in for the Peter Sellers marathon, though. Miles - Original Message - > From: "Jay Pipes" > To: openstack-dev@lists.openstack.org > Sent: Saturday, 5

Re: [openstack-dev] [fuel][plugins]Security problem in Fuel 7.0

I'd have to say that this is expected behavior. I'm not sure what you would hope to prohibit when these kinds of things are necessary for the deployment. We also can't prohibit this from being done in a plugin, this is what the plugin verification is supposed to help combat. If you just go download

Re: [openstack-dev] [neutron] Multiple locations for documentation of features

On Fri, Dec 4, 2015 at 12:22 PM, Henry Gessau wrote: > 1. RFE: "I want X" > 2. Spec: "I plan to implement X like this" > 3. devref: "How X is implemented and how to extend it" > 4. OS docs: "API and guide for using X" > > Once X is implemented I don't want to have to go to 1 or 2 to find informati

Re: [openstack-dev] [fuel][plugins]Security problem in Fuel 7.0

As far as I know this feature is planned for the next releases. But I think the main problem is: it's not obvious that just by installing a plugin, even without enabling the plugin in Fuel user could break or somehow alter already existing environments. It could be done by malicious attacker

Re: [openstack-dev] [glance] Auth_version from 'old style' URLs in the database

On Thu, Dec 3, 2015 at 10:24 AM, Bunting, Niall wrote: > Hi, > > Currently glance will use an auth_url if in the database. Eg. > 10.0.0.8:5000/v2.0 > > However glance currently takes the auth_version from the config > files. Therefore this can lead to a mismatch of keystone version to be used > b

Re: [openstack-dev] Documentation containing external resource links & privacy breaches

> On 7 Dec 2015, at 16:10, Thomas Goirand wrote: > > Cory, > > Thanks a lot for this patch. > > If I understand well, in Debian, I'd have to remove the: > > [options] > analytics_tracking_code = UA-17511903-1 > > from the default theme.conf to make the GA code go away. Right? Would > there b

Re: [openstack-dev] [Openstack-operators] [Performance][Proposal] Moving IRC meeting from 15:00 UTC to 16:00 UTC

Sylvain, in fact we just used the same practice LDT team is having - they do have their meeting on openstack-operators channel, for instance. We were choosing the time slot available for different people from different company, due to the Doodle vote it was chosen 15:00 UTC Tuesdays (and as you ca

Re: [openstack-dev] [glance] Add Ian Cordasco back into glance-core

+2 Great to see this happen. On 12/7/15 11:36 AM, Flavio Percoco wrote: > Greetings, > > Not long ago, Ian Cordasco, sent an email out stepping down from his > core roles as he didn't have the time to dedicate to the project > team's he was part of. > > Ian has contacted me mentioning that he's g

Re: [openstack-dev] [fuel][plugins]Security problem in Fuel 7.0

My two cents. It would be useful to have a role that could execute on the Fuel Master host itself rather than a container. -- Javeria On Dec 7, 2015 9:49 PM, "Roman Prykhodchenko" wrote: > Alexey, > > thank you for bringing this up. IMO discussing security problems is better > to be done in a sp

Re: [openstack-dev] [fuel][plugins]Security problem in Fuel 7.0

Alexey, thank you for bringing this up. IMO discussing security problems is better to be done in a special kind of Launchpad bugs. - romcheg > 7 груд. 2015 р. о 17:36 Alexey Elagin написав(ла): > > Hello all, > > We have a security problem in Fuel 7.0. It's related to plugin > development a

[openstack-dev] Mistral team meeting minutes - 12/07/2015

Hi, Thank you for coming us today! Meeting minutes: http://eavesdrop.openstack.org/meetings/mistral/2015/mistral.2015-12-07-15.59.html Log: http://eavesdrop.openstack.org/meetings/mistral/2015/mistral.2015-12-07-15.59.log.html Best Regards, Nikolay Makhotkin ___

[openstack-dev] [release][all] bugs will now close automatically when patches merge

As mentioned previously [1], as part of deprecating our use of Launchpad for tracking completed work we have changed the default behavior so that when a patch with "Fixes-Bug" in the commit message merges the bug will move to "Fix Released" (a closed state) instead of "Fix Committed" (a "still open

[openstack-dev] [glance] Add Ian Cordasco back into glance-core

Greetings, Not long ago, Ian Cordasco, sent an email out stepping down from his core roles as he didn't have the time to dedicate to the project team's he was part of. Ian has contacted me mentioning that he's gotten clearance, and therefore, time to dedicate to Glance and other activities aroun

[openstack-dev] [fuel][plugins]Security problem in Fuel 7.0

Hello all, We have a security problem in Fuel 7.0. It's related to plugin development and allows to execute code in mcollective docker container on Fuel master node. Any fuel plugin may contains a yaml file with deployment tasks (tasks.yaml, deployment_tasks.yaml etc) and there is an ability to ru

[openstack-dev] [horizon] Updated High Definition Logo for Alternate Theme

Hi All, I am currently working on updating the OpenStack logo being used in the *alternate* theme of Horizon to show that Horizon can easily support both PNG and SVG logos. I have found the correct logo assets for our Splash screen, however, I do not see a corresponding high definition asset to r

[openstack-dev] [mistral] bugfix for "Fix concurrency issues by using READ_COMMITTED" unveils / creates a different bug

Hi all, The current bugfix I am working on[1] have unveiled / created a bug. Test "WorkflowResumeTest.test_resume_different_task_states" sometimes fails because "task4" is executed twice instead of once (See unit test output and workflow below). This happens because task2 on-complete is running

Re: [openstack-dev] openstackdocstheme to be considered (very) harmful for your generated sphinx docs

On 12/07/2015 03:04 PM, Morgan Fainberg wrote: > Lets keep the accusations/defence of wording choices > out of the rest of the thread and focus on getting the docs to a place > that works for all the parties. Yes please. > I did see the earlier comment that the > external resources (due to nation

[openstack-dev] [Congress] Mid-cycle meet-up

Hi all, We're having a mid-cycle meet-up January 26-28 in the Bay Area. Here's a tentative schedule. Comments, suggestions, questions? Tue Jan 26: Discussion with Monasca team about integration. - Intro to Congress (slides or whiteboard) - Intro to Monasca (slides or whiteboard) - Design discus

Re: [openstack-dev] [Neutron][DVR]

On 7 December 2015 at 05:41, Ryan Moats wrote: > "Armando M." wrote on 12/04/2015 03:43:29 PM: > > > From: "Armando M." > > To: "OpenStack Development Mailing List (not for usage questions)" > > > > Date: 12/04/2015 03:44 PM > > Subject: Re: [openstack-dev] [Neutron][DVR] > > > > > On 4 Decemb

Re: [openstack-dev] Documentation containing external resource links & privacy breaches

On 12/04/2015 05:46 PM, Cory Benfield wrote: > >> On 4 Dec 2015, at 13:20, Anne Gentle > > wrote: >> >> Great, thanks! This would work well for both oslosphinx and >> openstackdocstheme: >> >> http://git.openstack.org/cgit/openstack/openstackdocstheme/ >> >> A

Re: [openstack-dev] [Fuel] Current Fuel CI status and issues related to CentOS7 migration

Hi, On Mon, Dec 7, 2015 at 4:29 PM, Aleksandra Fedorova wrote: > Hi everyone, > > let me describe CI status and changes in CI caused by CentOS7 > migration. Please read carefully as your local and custom test > environments might be affected as well. > > > * CentOS7 in docker with aufs on Ubunt

Re: [openstack-dev] [puppet] [tripleo] stop maintaining puppet-tuskar

On 2 December 2015 at 16:38, Emilien Macchi wrote: > Hi, > > I don't find any official statement on the Internet, but I've heard > Tuskar is not going to be maintained anymore (tell me if I'm wrong). > I was hoping to raise this question at the TripleO meeting this week. The question being; Shou

  1   2   >