Re: [openstack-dev] [puppet] [ceph] Puppet Ceph CI

I finally got around to split the RGW test into 3 steps: 1) mons/osds/keys 2) rgw/apache 3) keystone and got the tests for that to pass on Ubuntu. But it seems there is new EPEL dependency issue since yesterday: https://review.openstack.org/#/c/252664/ David, maybe you wan't to rebase your chang

Re: [openstack-dev] [cinder][nova]Move encryptors to os-brick

> -Original Message- > From: Ben Swartzlander [mailto:b...@swartzlander.org] > Sent: Friday, December 4, 2015 2:45 AM > To: OpenStack Development Mailing List (not for usage questions) > Subject: Re: [openstack-dev] [cinder][nova]Move encryptors to os-brick > > On 12/03/2015 07:40 AM, Dun

Re: [openstack-dev] [Monasca][vitrage] Vitrage project

Hi Roland, We created a blueprint for Vitrage-Monasca integration: https://blueprints.launchpad.net/vitrage/+spec/monasca-integration. We will be happy to get your comments about it. Thanks, Ifat. > -Original Message- > From: Hochmuth, Roland M [mailto:roland.hochm...@hpe.com] > Sent:

[openstack-dev] [ironic]"No valid host was found" when creating node in Ironic

Hi, all I install devstack with Ironic in physical machine. And I want to deploy a another physical machine which IPMI info is "username:root password:12345 ip_address: 192.168.0.100". I use this command "ironic node-create -c d5f2dee1-f5bc-409e-a9be-a3ae5c392cfa -d ipmi_tool -p ipmi_usernam

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

Dmitry Tantsur wrote: > > 2015-12-04 18:26 GMT+01:00 Doug Hellmann >: > > Excerpts from Dmitry Tantsur's message of 2015-12-04 17:38:43 +0100: > > Hi! > > > > As you all probably know, we've switched to reno for managing release > > notes. What i

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

HI Hua, From my point of view, not everything needed to be put in container. Let's make the initial start (be simple)to work and then discussed other options if needed in IRC or weekly meeting. Thanks Best Wishes,

Re: [openstack-dev] [ceilometer][aodh][vitrage] Raising custom alarms in AODH

On Mon, Dec 07 2015, AFEK, Ifat (Ifat) wrote: > Our goal is to get as much information as we can from various data > sources. If you connect Nagios to telemetry project, and we can get > nagios alarms directly from Aodh, it would be great. Is it something > that you planned on doing for Mitaka?

Re: [openstack-dev] [Fuel] Running Fuel node as non-superuser

Hi Dmitry, thank you for an update. I personally think that 2 and 3 must be done in one blueprint as it related to master node only and 2 shouldn't be a rocket science. What you mean by "Non-root accounts on slave nodes"? If we speak about disabling root for ssh, creating new user and adding neede

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

Hey Andrii, I'm totally agree with you about contribution guides, except one thing - we need and should force users to split huge patches into set of small ones. Mostly because it will simplify support and review of patches. Previously we ignored this rule pretty often, and get a lot of troubles d

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

Hi, On Mon, Dec 7, 2015 at 2:28 AM, Andrey Tykhonov wrote: > I believe this is against the code review guidelines. > > «Comments must be meaningful and should help an author to change the > code the right way.» [1] > Could you provide a link that accessible by community? Thanks a lot in advance

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

> What if you're not sure how the improved code should look like, but > you definitely sure that it shouldn't look like proposed one? :) I believe you should ask other people if you are right, as set '-1' to code that you cannot improve is not the best option, so > If you are not sure how the im

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

Ok, so due to the responses I propose to finalise this decision and move the meeting to *16:00 UTC (Tuesdays)*. So tomorrow please join me *on #openstack-performance at 16:00 UTC.* Cheers, Dina P.S. Ryan, I'm suggesting you to come as usually at 15:00, I'll be online - let's prepare possible ques

Re: [openstack-dev] [Fuel] FFE for Ubuntu bootstrap

+1 for FFE toll Tuesday 8th of December. -- Best regards, Sergii Golovatiuk, Skype #golserge IRC #holser On Fri, Dec 4, 2015 at 4:43 PM, Dmitry Klenov wrote: > Hi Mike and Igor, > > Thank you for the opinions. > > We already talked to Matt and he is fine with Fuel Menu commit. We will > target

[openstack-dev] [Fuel] CentOS7: merge freeze is lifted

Hi All, Centos7 patches were successfully integrated into Fuel 8.0, so we are removing merge freeze from all repositories according to our plan [1]. Please continue merge as usual. [1] - http://lists.openstack.org/pipermail/openstack-dev/2015-December/081026.html Regards, Andrey Maximov Fuel Pro

Re: [openstack-dev] [Fuel][library] CI gate for regressions detection in deployment data

On 02.12.2015 17:03, Bogdan Dobrelya wrote: > On 01.12.2015 11:28, Aleksandr Didenko wrote: >> Hi, >> >>> pregenerated catalogs for the Noop tests to become the very first >>> committed state in the data regression process has to be put in the >>> *separate repo* >> >> +1 to that, we can put this n

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

On 7 December 2015 at 12:20, Sergii Golovatiuk wrote: > Hi, > > On Mon, Dec 7, 2015 at 2:28 AM, Andrey Tykhonov > wrote: > >> I believe this is against the code review guidelines. >> >> «Comments must be meaningful and should help an author to change the >> code the right way.» [1] >> > > Could

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

Le 07/12/2015 11:27, Dina Belova a écrit : Ok, so due to the responses I propose to finalise this decision and move the meeting to *16:00 UTC (Tuesdays)*. So tomorrow please join me *on #openstack-performance at 16:00 UTC.* Why are you not using the meeting channels? You should also provide

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

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 reviewed for a very long time or get random +1s from people who don’t

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

Following up on my previous email: Every blueprint specification has a Work items section. That section should describe granular work items, not just things in general. We should encourage components leads to put their attention to this aspect. > 7 груд. 2015 р. о 12:23 Roman Prykhodchenko н

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

On 04/12/15 19:24, Henry Gessau wrote: > Sean M. Collins wrote: >> I've noticed that a lot of features are now being documented as RSTs >> inside of devref. Like the following: >> >> https://review.openstack.org/#/c/251859/ >> >> But there are lots already present. Can someone point out to me what

[openstack-dev] [client][all][neutron] client option removal policy

Hi, neutronclient is now dropping XML support and as a result "--request-format" option is no longer needed as JSON is the only format now. What is the recommended way for options no longer needed? Does bumping major version of CLI allow us to drop an option without deprecation? - Deprecate such

[openstack-dev] [nova][glance] Nova using service tokens with protected properties in Glance

Hi, There is the following spec for review: https://review.openstack.org/#/c/249950/ for allowing the modification of protected properties with service tokens in Glance. John & Stuart suggest using service tokens for the following Nova spec: https://review.openstack.org/#/c/206431/ (Inheritable a

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

On 12/07/2015 10:48 AM, Thierry Carrez wrote: Dmitry Tantsur wrote: 2015-12-04 18:26 GMT+01:00 Doug Hellmann mailto:d...@doughellmann.com>>: Please don't delete anything older than Mitaka. Do you have any hints how to not confuse users in this case? I think what Doug means is you

Re: [openstack-dev] [client][all][neutron] client option removal policy

The Neutron API dropped XML support quite some time ago. Therefore specifying --request-format xml already produces an error. Even if this parameter is already vestigial and should be abruptly removed. We don't know whether anyone is using it. For instance one could have a set of scripts that expl

Re: [openstack-dev] [TripleO] Summary of In-Progress TripleO Workflow and REST API Development

On 12/07/2015 04:33 AM, Tzu-Mainn Chen wrote: On 04/12/15 23:04, Dmitry Tantsur wrote: On 12/03/2015 08:45 PM, Tzu-Mainn Chen wrote: 5. In-Progress Development The initial spec fo

Re: [openstack-dev] [client][all][neutron] client option removal policy

On 07/12/15 12:01, Akihiro Motoki wrote: > Hi, > > neutronclient is now dropping XML support and as a result > "--request-format" option is no longer needed as JSON is the only format now. > > What is the recommended way for options no longer needed? > Does bumping major version of CLI allow us to

Re: [openstack-dev] [TripleO] workflow

On 12/06/2015 05:33 PM, John Trowbridge wrote: On 12/03/2015 03:47 PM, Dan Prince wrote: On Tue, 2015-11-24 at 15:25 +, Dougal Matthews wrote: On 23 November 2015 at 14:37, Dan Prince wrote: There are lots of references to "workflow" within TripleO conversations these days. We are at (o

[openstack-dev] [puppet] weekly meeting #62

Hello! Here's an initial agenda for our weekly meeting, tomorrow at 1500 UTC in #openstack-meeting-4: https://etherpad.openstack.org/p/puppet-openstack-weekly-meeting-20151208 Thanks, -- Emilien Macchi signature.asc Description: OpenPGP digital signature _

[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 valuable reviews. Also his contribution is really high [1] . [1] http://stackalytics.com/report/contribution/heat-group/60 Heat core-team, please vote with: +1 - if you agree -1 - if you disagree

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

On 12/04/2015 03:23 PM, Anne Gentle wrote: > > > On Fri, Dec 4, 2015 at 8:09 AM, Thomas Goirand > wrote: > > Hi, > > I've investigated a bit the openstackdocstheme, and tried to remove some > of the (numerous) javascript with external references. And it's *v

Re: [openstack-dev] [client][all][neutron] client option removal policy

Thanks for the replies. I totally agree that we should deprecate it. We forgot to mark --request-format as deprecated. The way we should go is to deprecate --request-format. Akihiro 2015-12-07 21:24 GMT+09:00 Neil Jerram : > On 07/12/15 12:01, Akihiro Motoki wrote: >> Hi, >> >> neutronclient is n

Re: [openstack-dev] [ironic]"No valid host was found" when creating node in Ironic

On 12/07/2015 10:45 AM, Zhi Chang wrote: Hi, all I install devstack with Ironic in physical machine. And I want to deploy a another physical machine which IPMI info is "username:root password:12345 ip_address: 192.168.0.100". I use this command "ironic node-create -c d5f2dee1-f5bc-409e-a9be-

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

Excerpts from Dmitry Tantsur's message of 2015-12-07 13:18:22 +0100: > On 12/07/2015 10:48 AM, Thierry Carrez wrote: > > Dmitry Tantsur wrote: > >> > >> 2015-12-04 18:26 GMT+01:00 Doug Hellmann >> >: > >> > > >> > >> Please don't delete anything older than Mitak

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

"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 December 2015 at 05:56, Ryan Moats wrote: > > I pretty much agree with

Re: [openstack-dev] [kolla][nova] Orchiestrated upgrades in kolla

Jay's approach is really neat and that how it done in big productions, sadly there is a problem with implementation of it in Kolla. I'd consider to dig into it, maybe there is nice way to do so. If not, original approach is ok too. On Mon, Dec 7, 2015 at 10:06 AM, Steven Dake (stdake) wrote: > >

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

On 12/07/2015 02:42 PM, Doug Hellmann wrote: Excerpts from Dmitry Tantsur's message of 2015-12-07 13:18:22 +0100: On 12/07/2015 10:48 AM, Thierry Carrez wrote: Dmitry Tantsur wrote: 2015-12-04 18:26 GMT+01:00 Doug Hellmann mailto:d...@doughellmann.com>>: Please don't delete anythin

Re: [openstack-dev] [nova][docs][api] Propose Virtual Nova API Doc Sprint on Dec 8 and 9

On 12/04/2015 09:48 AM, Alex Xu wrote: > Just reminder the event which close the time, the virtual doc sprint is > right next week. Welcome to join us! Please include the details of your virtual sprint on the virtual sprints wikipage: https://wiki.openstack.org/wiki/VirtualSprints Thank you, Anit

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

On Mon, Dec 7, 2015 at 7:54 AM, Thomas Goirand wrote: > On 12/04/2015 03:23 PM, Anne Gentle wrote: > > > > > > On Fri, Dec 4, 2015 at 8:09 AM, Thomas Goirand > > wrote: > > > > Hi, > > > > I've investigated a bit the openstackdocstheme, and tried to remove > some

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

Hi Fuel team, we have a lot of automated integration tests for OpenStack verification and we want to add execution of these tests to Fuel SWARM test suite (to run these tests on daily basis and on per commit basis). We used our own bash scripts to deploy OpenStack environments with Fuel before, b

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

On 07/12/15 07: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 with

Re: [openstack-dev] [cinder][nova]Move encryptors to os-brick

On 12/2/15, 4:01 PM, "Ben Swartzlander" wrote: >On 11/30/2015 09:04 AM, Coffman, Joel M. wrote: >> >> >> On 11/25/15, 11:33 AM, "Ben Swartzlander" > > wrote: >> >> On 11/24/2015 03:27 PM, Nathan Reller wrote: >> >> the cinder admin and the nova admin

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

On 2015-12-07 09:04:20 -0500 (-0500), Morgan Fainberg wrote: [...] > * We should not (regardless of free/non-free/etc) make sure that the docs > are fully self-contained when built locally. This would address the privacy > and security issues for the local docs. (Again Analytics can be enabled as >

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

+1 Original message From: Sergey Kraynev Date:12/07/2015 6:41 AM (GMT-06:00) 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 pr

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

On Mon, Dec 7, 2015 at 8:04 AM, Morgan Fainberg wrote: > > > On Mon, Dec 7, 2015 at 7:54 AM, Thomas Goirand wrote: > >> On 12/04/2015 03:23 PM, Anne Gentle wrote: >> > >> > >> > On Fri, Dec 4, 2015 at 8:09 AM, Thomas Goirand > > > wrote: >> > >> > Hi, >> > >> > I'

Re: [openstack-dev] [Nova] notification subteam meeting

Hi, The next meeting of the nova notification subteam will happen 2015-12-08 Tuesday 20:00 UTC [1] on #openstack-meeting-alt on freenode Agenda: - Status of the outstanding specs and code reviews - AOB See you there. Cheers, Gibi [1] https://www.timeanddate.com/worldclock/fixedtime.html?is

Re: [openstack-dev] [nova][docs][api] Propose Virtual Nova API Doc Sprint on Dec 8 and 9

Anita, thanks for the reminder, so cool we have such wiki, just add my one. 2015-12-07 21:49 GMT+08:00 Anita Kuno : > On 12/04/2015 09:48 AM, Alex Xu wrote: > > Just reminder the event which close the time, the virtual doc sprint is > > right next week. Welcome to join us! > > Please include the

Re: [openstack-dev] [kolla][nova] Orchiestrated upgrades in kolla

>> 1. Nova bootstrap will be called and it will perform db-migration. Since >> current approach to nova code is add-only we shouldn't need to stop >> services and old services should keep working on newer database. Also >> for minor version upgrades there will be no action here unless there is >> m

Re: [openstack-dev] [ironic]"No valid host was found" when creatingnode in Ironic

Hi, thanks for your reply. You are right, I forgot to load some drivers in Ironic. But there is another problem. When I run the command "ironic node-set-power-state xxx off", ironic conductor displays an error, says "IPMI Error while attempting ipmitool -I lanplus -H 10.0.8.65 -L ADMINISTRATOR -

Re: [openstack-dev] [nova][docs][api] Propose Virtual Nova API Doc Sprint on Dec 8 and 9

On 12/07/2015 09:45 AM, Alex Xu wrote: > Anita, thanks for the reminder, so cool we have such wiki, just add my one. Thank you Alex, I hope you have a good sprint. Anita. > > 2015-12-07 21:49 GMT+08:00 Anita Kuno : > >> On 12/04/2015 09:48 AM, Alex Xu wrote: >>> Just reminder the event which c

Re: [openstack-dev] [Fuel] Running Fuel node as non-superuser

Stanislaw, the reason why I'm considering splitting the blueprint is that along with implementing the feature, CI jobs and OSTF must be fixed as well. On Mon, Dec 7, 2015 at 4:03 AM, Stanislaw Bogatkin wrote: > Hi Dmitry, > > thank you for an update. > I personally think that 2 and 3 must be do

Re: [openstack-dev] [ceilometer][aodh][vitrage] Raising custom alarms in AODH

> -Original Message- > From: Julien Danjou [mailto:jul...@danjou.info] > Sent: Monday, December 07, 2015 12:00 PM > > I find it odd to have UI use cases first, as their terribly large for a > MVP. Unless Vitrage already exists and you have all the code figured > out. :) We have most of it

Re: [openstack-dev] [TripleO] workflow

On Thu, 2015-12-03 at 15:47 -0500, Dan Prince wrote: > On Tue, 2015-11-24 at 15:25 +, Dougal Matthews wrote: > > On 23 November 2015 at 14:37, Dan Prince > > wrote: > > > There are lots of references to "workflow" within TripleO > > > conversations > > > these days. We are at (or near) the

Re: [openstack-dev] [kolla][nova] Orchiestrated upgrades in kolla

So Dan, correct me if I'm wrong, but after this merges (we're working on L->M upgrade) we can simply go with version=auto on every node and just hit SIGHUP on conductors once we're done with all of compute nodes right? Also, are there any other nice things that you guys plan for M and we could use

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

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] . > > [1] http://stackalytics.com/report/contribution/heat-group/60 > > He

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

+1 2015-12-07 15:39 GMT+03:00 Sergey Kraynev : > 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-t

[openstack-dev] [nova] Nova API sub-team meeting

Hi, We have weekly Nova API meeting this week. The meeting is being held Tuesday UTC1200. The proposed agenda and meeting details are here: https://wiki.openstack.org/wiki/Meetings/NovaAPI Please feel free to add items to the agenda. Thanks _

Re: [openstack-dev] [neutron][docs] Third Party Neutron Drivers

Thanks for the advance notice. Sounds good to me. -- Sean M. Collins __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.open

Re: [openstack-dev] [neutron][docs] Third Party Neutron Drivers

On 12/07/2015 10:17 AM, Sean M. Collins wrote: > Thanks for the advance notice. Sounds good to me. > I announced this at Monday's third party meeting. Thanks Lana, Anita. __ OpenStack Development Mailing List (not for usage

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

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 Ubuntu Trusty host is not stable Containers of such type are required for Fuel ISO b

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

On Mon, Dec 7, 2015 at 8:25 AM, Jeremy Stanley wrote: > On 2015-12-07 09:04:20 -0500 (-0500), Morgan Fainberg wrote: > [...] > > * We should not (regardless of free/non-free/etc) make sure that the docs > > are fully self-contained when built locally. This would address the > privacy > > and secu

Re: [openstack-dev] [TripleO] Summary of In-Progress TripleO Workflow and REST API Development

- Original Message - > On 12/07/2015 04:33 AM, Tzu-Mainn Chen wrote: > > > > > > On 04/12/15 23:04, Dmitry Tantsur wrote: > > > > On 12/03/2015 08:45 PM, Tzu-Mainn Chen wrote: > > > > > > > > >

Re: [openstack-dev] [kolla][nova] Orchiestrated upgrades in kolla

> So Dan, correct me if I'm wrong, but after this merges (we're working > on L->M upgrade) we can simply go with version=auto on every node and > just hit SIGHUP on conductors once we're done with all of compute > nodes right? You need to hit all the nodes with SIGHUP. The api, conductor and compu

Re: [openstack-dev] [TripleO] workflow

On 7 December 2015 at 14:59, Dan Prince wrote: > > > > On Thu, 2015-12-03 at 15:47 -0500, Dan Prince wrote: > > On Tue, 2015-11-24 at 15:25 +, Dougal Matthews wrote: > > > On 23 November 2015 at 14:37, Dan Prince > > > wrote: > > > > There are lots of references to "workflow" within TripleO

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

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] 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] [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

[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] 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] [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

[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] [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] [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] [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] 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 ___

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

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] [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] [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] 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] [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] [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] [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

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] [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] [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] [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/

[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

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

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] [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

[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] [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?

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 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

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] 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

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] [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] [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

  1   2   >