Re: [openstack-dev] Fwd: [Senlin]Support more complicatedscalingscenario

On 2015/11/24 16:41, Qiming Teng wrote: After debugging, I found that former result is not overridden by another policy. http://git.openstack.org/cgit/openstack/senlin/tree/senlin/engine/actions/base.py#n441 I think you are not referring to a correct location in the source code. That line was

Re: [openstack-dev] [nova] Nova meeting this Thursday

John Garbutt wrote on 11/24/2015 04:51:08 PM: > From: John Garbutt > To: OpenStack Development Mailing List > Date: 11/24/2015 04:52 PM > Subject: [openstack-dev] [nova] Nova meeting this Thursday > > Hi, > > I just wanted to share my plan for Thursday's meeting. > > As it is thanksgiving i

[openstack-dev] [all] how to add/list drivers @ https://www.openstack.org/marketplace/drivers/

Hi Team, In the following link, i can see only some vendor plug-ins, not all is listed here! .. https://www.openstack.org/marketplace/drivers/ So [1] what is the criteria to get a vendor plug-in listed on this page? [2] where can i see the supported vendor plugins/drivers for a given Opensta

Re: [openstack-dev] [nova] Nova meeting this Thursday

+1 Best regards, Silvan Kaiser 2015-11-25 9:25 GMT+01:00 Markus Zoeller : > John Garbutt wrote on 11/24/2015 04:51:08 PM: > > > From: John Garbutt > > To: OpenStack Development Mailing List > > > Date: 11/24/2015 04:52 PM > > Subject: [openstack-dev] [nova] Nova meeting this Thursday > > > >

Re: [openstack-dev] [all] Thoughts on python-future?

On Tue, Nov 24 2015, Eric Kao wrote: > I¹ve been using the python-future library for Python 3 porting and want to > see what people think of it. http://python-future.org/overview.html#features > > The end result is standard Python3 code made compatible with Python2 through > library imports. The g

Re: [openstack-dev] [release] process change for closing bugs when patches merge

Thomas Goirand wrote: > On 11/23/2015 10:58 PM, Doug Hellmann wrote: >> Right now, when a patch with Closes-Bug in the commit message merges, >> the bug status is updated to "Fix Committed" to indicate that the change >> is in git, but not a formal release, and we rely on the release tools to >> up

Re: [openstack-dev] [all] Time to increase our IRC Meetings infrastructure?

Tony Breeds wrote: >>> [...] >>> Confusion >>> = >>> So this is really quite trivial. As you can see above we don't have an >>> #openstack-meeting-2 channel the ...-alt is clearly that, but still people >>> are >>> confused. How would people feel about creating #openstack-meeting-2 a

[openstack-dev] [networking-ovs-dpdk]

Hello Everyone, Now that we have installed ovs-dpdk along with all necessary prerequisite repo (ovs,dpdk,libvirt etc) from devstack setup, we would like to install it via *puppet*. I see a puppet folder in networking-ovs ( https://github.com/openstack/networking-ovs-dpdk/tree/master/puppet) but d

Re: [openstack-dev] [all] Time to increase our IRC Meetings infrastructure?

+1, It's always very confusing the first time. Thierry Carrez wrote: Tony Breeds wrote: [...] Confusion = So this is really quite trivial. As you can see above we don't have an #openstack-meeting-2 channel the ...-alt is clearly that, but still people are confused. How would peop

Re: [openstack-dev] [all] how to add/list drivers @ https://www.openstack.org/marketplace/drivers/

Community-maintained list of drivers exists within the project DriverLog. The UI is available at http://stackalytics.com/report/driverlog , it has all options to filter the data. Thanks, Ilya 2015-11-25 11:48 GMT+03:00 Mohan Kumar : > Hi Team, > > In the following link, i can see only some ven

Re: [openstack-dev] [tricircle]Tokyo Summit Summary

Hi All, We will hold our regular meeting today starting UTC1300 at #openstack-meeting, and we will chat about the new architecture discussed during the Tokyo Design Summit On Sat, Nov 21, 2015 at 10:20 AM, Zhipeng Huang wrote: > Hi Team, > > We had very great sessions re Tricircle at Tokyo Summ

Re: [openstack-dev] [all] Thoughts on python-future?

On 11/25/2015 03:33 AM, Eric Kao wrote: > Hi all, > > I’ve been using the python-future library for Python 3 porting and want > to see what people think of it. > http://python-future.org/overview.html#features > > The end result is standard Python3 code made compatible with Python2 > through lib

Re: [openstack-dev] [Murano] 'NoMatchingFunctionException: No function "#operator_." matches supplied arguments' error when adding an application to an environment

Hi Vahid, Forms are rended after app is added to the environment in accordance with the UI definition. UI definition contains yaql expressions and one of your expression is incorrect. Please, share UI yaml so we can find out what's the problem. You can also create a bug that it's not obvious which

Re: [openstack-dev] Licenses

On Mon, Nov 23, 2015 at 11:15 PM, Armando Dominguez < armando.doming...@rackspace.com> wrote: > Hey All, > > > > Sorry for hitting the entire list, I’m just trying to find out who took > over the license handling from Andrew Melton? I’m looking for a Pycharm > license. > I have sent information f

Re: [openstack-dev] [Magnum] Why set DEFAULT_DOCKER_TIMEOUT = 10 in docker client?

Hi, I think out docker all call, use docker_for_bay, which use CONF.docker.default_timeout. And default_timeout can be changed any value. User can customized it per case. For why set 10, maybe it was because someone local test OK. So use that value. I think for jenkins, it can use CONF overr

Re: [openstack-dev] [Neutron] Call for review focus

On 11/24/2015 06:53 PM, Armando M. wrote: On 24 November 2015 at 04:13, Rossella Sblendido mailto:rsblend...@suse.com>> wrote: On 11/23/2015 06:38 PM, Armando M. wrote: On 23 November 2015 at 04:02, Rossella Sblendido mailto:rsblend...@suse.com>

[openstack-dev] [Horizon] Bug Day: The Aftermath

Hi all, Bug day was great! We categorised around 140 bugs, reducing the Undecided count to 466 from ~600, and also removed around 50 bugs that were no longer valid. This is a step in the right direction, and I think it would be worth organising more bug days in the cycle, spread out so as not t

Re: [openstack-dev] [Murano] 'NoMatchingFunctionException: No function "#operator_." matches supplied arguments' error when adding an application to an environment

Hi Vahid, you can find generated UI definitions for the package here: /tmp/muranodashboard-cache/apps/.../ui/ui.yaml On Wed, Nov 25, 2015 at 12:54 PM, Ekaterina Chernova wrote: > > Hi Vahid, > > Forms are rended after app is added to the environment in accordance with the > UI definition. > UI

Re: [openstack-dev] [all][glance] Add Sabari Kumar Murugesan

> -Original Message- > From: Flavio Percoco [mailto:fla...@redhat.com] > Sent: Monday, November 23, 2015 8:21 PM > To: openstack-dev@lists.openstack.org > Cc: Sabari Kumar Murugesan > Subject: [openstack-dev] [all][glance] Add Sabari Kumar Murugesan > > > Greetings, > > I'd like to propo

Re: [openstack-dev] [ceph] DevStack plugin for Ceph required for Mitaka-1 and beyond?

The patch just landed, as soon as I have the repo I’ll move the code and do some testing. > On 24 Nov 2015, at 16:20, Sebastien Han wrote: > > Hi Ramana, > > I’ll resurrect the infra patch and put the project under the right namespace. > There is no plugin at the moment. > I’ve figured out tha

Re: [openstack-dev] [Horizon] Bug Day: The Aftermath

Nice Job From: "Rob Cresswell (rcresswe)" mailto:rcres...@cisco.com>> Reply-To: OpenStack List mailto:openstack-dev@lists.openstack.org>> Date: Wednesday, November 25, 2015 at 6:23 AM To: OpenStack List mailto:openstack-dev@lists.openstack.org>> Subject: [openstack-dev] [Horizon] Bug Day: The Af

Re: [openstack-dev] [Fuel][Infra] HA deployment tests on nodepool

(I moved the description of Fuel CI to wiki page [0] for future references.) Why i think option with predeployed Fuel node is better for us: Currently Fuel Build team works on stripping off as much content as possible from a Fuel node (and, thus, Fuel ISO). We already have a possibility to use ex

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

Hi all, I am working on containerizing etcd and flannel. But I met a problem. As described in [1], we need a docker-bootstrap. Docker and docker-bootstrap can not use the same storage, so we need some disk space for it. The docker in master node stores data in /dev/mapper/atomicos-docker--data and

Re: [openstack-dev] [Horizon][Neutron] dashboard repository for neutron subprojects

I like the idea of doing a Horizon plugin, similar to a devstack plugin... So choice (c) is my preference, given my current understanding. May be good to try it on one subproject and see how it works out. Would give a concrete example to discuss. Regards, Paul Michali (pc_m) On Wed, Nov 25, 2015

[openstack-dev] Unable to login to the instance

Hi, I have installed the openstack on a single node and was trying to access to the instance through ssh and was unable to do so In the nova.conf file I have the default firewall settings as firewall_driver = nova.virt.libvirt.firewall.IptablesFirewallDriver and I have changed to firewall_driv

Re: [openstack-dev] [nova]New Quota Subteam on Nova

Hi Kevin, Thanks for your interest! In the current implementation for Nested Quota, we want to provide a better way to handle with Hierarchical Multitenancy on Nova, like we did on Cinder . Also, I already create

Re: [openstack-dev] [Fuel][Infra] HA deployment tests on nodepool

Hi All W dniu 25.11.2015 o 14:00, Aleksandra Fedorova pisze: ... Thus the test layout as i see it should be the following: - one "manager vm" which will be responsible for the main test flow. On this vm we will: - build fuel-library package, - generate a repository, - get fuel-qa

Re: [openstack-dev] [keystone] Diagnostic APIs for Keystone

On 11/24/2015 10:50 AM, Henry Nash wrote: Some good ideas here, Adam. I would think that some of the real “diagnostic APIs” might only be available via keystone-manage, rather than an exposed API. I'd like to get away from the assumption that you have physical access to the machines to do o

[openstack-dev] [neutron][fwaas] No IRC meeting due to US holiday

We'll start again next week at the 18:30 UTC time -- 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] [release] process change for closing bugs when patches merge

Excerpts from Thierry Carrez's message of 2015-11-25 10:19:44 +0100: > Thomas Goirand wrote: > > On 11/23/2015 10:58 PM, Doug Hellmann wrote: > >> Right now, when a patch with Closes-Bug in the commit message merges, > >> the bug status is updated to "Fix Committed" to indicate that the change > >>

Re: [openstack-dev] [Horizon][Neutron] dashboard repository for neutron subprojects

On Wed, Nov 25, 2015 at 1:06 AM, Armando M. wrote: > > > On 24 November 2015 at 21:46, Akihiro Motoki wrote: > >> Hi, >> >> Neutron has now various subprojects and some of them would like to >> implement Horizon supports. Most of them are additional features. >> I would like to start the discuss

[openstack-dev] Encouraging first-time contributors through bug tags/reviews

Hi everyone, Andrew Mitry recently shared a medium post[1] by Kent C. Dobbs which discusses how one open-source project is encouraging contributions by new open-source contributors through a combination of a special tag (which is associated with work that is needed but can only be completed by som

Re: [openstack-dev] [tripleo] When to use parameters vs parameter_defaults

I think at the same time we add a mechanism to distinguish between internal and external parameters, we need to add something to indicate required v. optional. With a nested stack, anything that's not part of the top-level parameter contract is defaulted. The problem is that it loses information

[openstack-dev] Fwd: Fernet token Implementation

-- Forwarded message -- From: Max Yatsenko Date: Wed, Nov 25, 2015 at 1:47 PM Subject: Fernet token Implementation To: mos-dev Hello Everyone, Please be notified that today "Fernet token" implementation was added to fuel-library. The following patches were merged: #Add a funct

Re: [openstack-dev] [Openstack-i18n] DocImpact Changes

These changes have merged now, Andreas On 2015-11-23 23:33, Lana Brindley wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hi everyone, The DocImpact flag was implemented back in Havana to make it easier for developers to notify the documentation team when a patch might cause a change

[openstack-dev] [openstak-dev][Fuel] Not properly merged specifications

Hi Fuelers, Today, I noticed that many specifications are merged without +1/+2 from different components [1]. Please add components leads to all specifications. Please add SME to make sure the specification covers all fuel components. [1] https://review.openstack.org/#/c/229063/ -- Best regards,

Re: [openstack-dev] Rally as A Service?

Awesome. I’m taking a look on it. I’ll see how I can contribute to this. Thanks Boris. -- Obed N Munoz Cloud Engineer @ ClearLinux Project Open Source Technology Center From: Boris Pavlovic Reply-To: "OpenStack Development Mailing List (not for usage questions)" Date: Tuesday, November 24, 2015 a

Re: [openstack-dev] [Horizon] Bug Day: The Aftermath

Rob Cresswell (rcresswe) wrote: > Bug day was great! We categorised around 140 bugs, reducing the > Undecided count to 466 from ~600, and also removed around 50 bugs that > were no longer valid. This is a step in the right direction, and I think > it would be worth organising more bug days in the c

Re: [openstack-dev] [tripleo] When to use parameters vs parameter_defaults

On Fri, 2015-11-20 at 16:53 +0100, Jiri Tomasek wrote: > On 11/16/2015 04:25 PM, Steven Hardy wrote: > > Hi all, > > > > I wanted to start some discussion re $subject, because it's been > > apparrent > > that we have a lack of clarity on this issue (and have done ever > > since we > > started usin

[openstack-dev] [Heat] Heat specs re-organization

Hi all. This mail is announcement of changes in heat-specs repository, which were *partially* discussed on the last Heat weekly meeting. There are following list of planned changes: - Create one main directory for all specs with name, e.g. scope - Move all not implemented specs from previous rel

Re: [openstack-dev] [tripleo] When to use parameters vs parameter_defaults

On Thu, 2015-11-19 at 16:16 +, Steven Hardy wrote: > On Mon, Nov 16, 2015 at 08:15:48PM +0100, Giulio Fidente wrote: > > On 11/16/2015 04:25 PM, Steven Hardy wrote: > > > Hi all, > > > > > > I wanted to start some discussion re $subject, because it's been > > > apparrent > > > that we have a l

[openstack-dev] [Ironic][Neutron] Testing of Ironic/Neutron integration on devstack

Hello Community, As you know Ironic/Neutron integration is planned in Mitaka. And at the moment we don't have any CI that will test it. Unfortunately we can't test Ironic/Neutron integration on HW as we don't have it. So probably the best way is to develop ML2 driver that will work with OVS. At t

Re: [openstack-dev] [keystone][all] Move from active distrusting model to trusting model

Tom brings up a good point. With a clear direction and support from the foundation/Thierry I'm confident we can make any version of these models work. I know in the situation I described if the policy was clear that it was okay and if I knew we could pull in Thierry to help resolve any disputes

Re: [openstack-dev] New [puppet] module for Magnum project

Hi. We've started implementing a similar module here, i just pushed it to: https://github.com/cernops/puppet-magnum It already does a working magnum-api/conductor, and we'll add configuration for additional conf options this week - to allow alternate heat templates for the bays. I've done some w

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

From: 王华 mailto:wanghua.hum...@gmail.com>> Reply-To: "OpenStack Development Mailing List (not for usage questions)" mailto:openstack-dev@lists.openstack.org>> Date: Wednesday, November 25, 2015 at 5:00 AM To: "OpenStack Development Mailing List (not for usage questions)" mailto:openstack-dev@li

Re: [openstack-dev] [all] Time to increase our IRC Meetings infrastructure?

Thanks Tony for leading the effort. As you know, neutron-upgrades team (well, me) actually confused -alt/-2 thing, and I registered a meeting for -2. I am generally for adding more channels assuming they are used wisely (like: organizers check in advance they don’t overlap with related in

[openstack-dev] [Horizon][Access and Security] ICMP type, ICMP code 'ValidationError' query

While inputing 'ICMP type' and 'ICMP code' at [1], validation is done which raises 'ValidationError', at [2] so if validation fails corresponding value is set to None. Then why is ValidationError raised again in [3]. Where is 'ValidationError' at [3] caught? [1] openstack_dashboard/dashboards/p

Re: [openstack-dev] [neutron][fwaas] No IRC meeting due to US holiday

In the meantime please keep reviewing the FWaaS V2 API spec - https://review.openstack.org/#/c/243873/7 - so we can close on that next Wednesday. Thanks, German On 11/25/15, 6:01 AM, "Sean M. Collins" wrote: >We'll start again next week at the 18:30 UTC time >-- >Sean M. Collins > >___

Re: [openstack-dev] [Neutron] Call for review focus

On 25 November 2015 at 03:09, Rossella Sblendido wrote: > > > On 11/24/2015 06:53 PM, Armando M. wrote: > >> >> >> On 24 November 2015 at 04:13, Rossella Sblendido > > wrote: >> >> >> >> On 11/23/2015 06:38 PM, Armando M. wrote: >> >> >> >> On 23 November 2

Re: [openstack-dev] [tripleo] When to use parameters vs parameter_defaults

On 11/25/2015 09:13 AM, Dan Prince wrote: > On Fri, 2015-11-20 at 16:53 +0100, Jiri Tomasek wrote: >> On 11/16/2015 04:25 PM, Steven Hardy wrote: >>> Hi all, >>> >>> I wanted to start some discussion re $subject, because it's been >>> apparrent >>> that we have a lack of clarity on this issue (and

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

On 11/24/2015 03:27 PM, Nathan Reller wrote: the cinder admin and the nova admin are ALWAYS the same people There is interest in hybrid clouds where the Nova and Cinder services are managed by different providers. The customer would place higher trust in Nova because you must trust the compute

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

Here is a bit more context. Currently, at k8s and swarm bay, some required binaries (i.e. etcd and flannel) are built into image and run at host. We are exploring the possibility to containerize some of these system components. The rationales are (i) it is infeasible to build custom packages in

Re: [openstack-dev] [nova][neutron][upgrade] Grenade multinode partial upgrade

The first run for the multinode grenade job completed. http://logs.openstack.org/35/187235/11/experimental/gate-grenade-dsvm-neutron-multinode/011124b/logs/ I'm still getting my bearings in the grenade log output, but if I understand it correctly, after upgrading Neutron, when spawning a new inst

Re: [openstack-dev] [all] how to add/list drivers @ https://www.openstack.org/marketplace/drivers/

That reminds me of a follow-on question, as I added my driver's data to the driverlog project a few weeks ago [1]: when does the content at https://www.openstack.org/marketplace/drivers/ get rebuilt? Thanks, Neil [1] https://review.openstack.org/#/c/240830/ On 25/11/15 09:42, Ilya Shakhat w

Re: [openstack-dev] Encouraging first-time contributors through bug tags/reviews

This is an awesome idea!!! On 11/25/15 16:15, Shamail Tahir wrote: Hi everyone, Andrew Mitry recently shared a medium post[1] by Kent C. Dobbs which discusses how one open-source project is encouraging contributions by new open-source contributors through a combination of a special tag (

Re: [openstack-dev] [nova][neutron][upgrade] Grenade multinode partial upgrade

On 25 November 2015 at 08:42, Sean M. Collins wrote: > The first run for the multinode grenade job completed. > > > http://logs.openstack.org/35/187235/11/experimental/gate-grenade-dsvm-neutron-multinode/011124b/logs/ > > I'm still getting my bearings in the grenade log output, but if I > underst

Re: [openstack-dev] [nova][neutron][upgrade] Grenade multinode partial upgrade

I have run the multimode grenade job twice: Failed: [1] http://logs.openstack.org/69/143169/60/experimental/gate-grenade-dsvm-neutron-multinode/bf6bae1/ Success: [2] http://logs.openstack.org/69/143169/60/experimental/gate-grenade-dsvm-neutron-multinode/7c05ff0/ The [1] failed because it couldn'

Re: [openstack-dev] [Horizon][Neutron] dashboard repository for neutron subprojects

Sent from Nine From: Kyle Mestery Sent: Nov 25, 2015 8:18 AM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [Horizon][Neutron] dashboard repository for neutron subprojects On Wed, Nov 25, 2015 at 1:06 AM, Armando M. mai

Re: [openstack-dev] [nova][neutron][upgrade] Grenade multinode partial upgrade

From what I understand – the Sean case did not get to upgrade [1]– it has ended after creating the VM and trying to ping/ssh it. So we do not have restart logs of q-agt and no logs in new [2] The subnode will have only ‘old’ logs because the grenade multimode scenario assumes that subnode will n

Re: [openstack-dev] [nova][neutron][upgrade] Grenade multinode partial upgrade

Yeah looks like I read it wrong - the failure occurred during the initial resource creation phase, based on comparing the logs that Artur posted. -- Sean M. Collins __ OpenStack Development Mailing List (not for usage questio

Re: [openstack-dev] Encouraging first-time contributors through bug tags/reviews

Have a tag for first time contributor is a great idea. On the other hand we should not take out the "low hanging fruit" tag. I contribute to OpenStack on my spare time and in my current situation I can only work on the low hanging fruits. If the first time tag is replacing the low hanging fruit

Re: [openstack-dev] [nova][neutron][upgrade] Grenade multinode partial upgrade

On Wed, Nov 25, 2015 at 12:29:49PM EST, Korzeniewski, Artur wrote: > I have run the multimode grenade job twice: > Failed: [1] > http://logs.openstack.org/69/143169/60/experimental/gate-grenade-dsvm-neutron-multinode/bf6bae1/ > Success: [2] > http://logs.openstack.org/69/143169/60/experimental/ga

Re: [openstack-dev] [nova][neutron][upgrade] Grenade multinode partial upgrade

On 25 November 2015 at 09:49, Sean M. Collins wrote: > Yeah looks like I read it wrong - the failure occurred during the > initial resource creation phase, based on comparing the logs that Artur > posted. > I see. I got confused by this: http://logs.openstack.org/69/143169/60/experimental/gate-

Re: [openstack-dev] [nova][neutron][upgrade] Grenade multinode partial upgrade

On Wed, Nov 25, 2015 at 12:53:56PM EST, Armando M. wrote: > On 25 November 2015 at 09:49, Sean M. Collins wrote: > > > Yeah looks like I read it wrong - the failure occurred during the > > initial resource creation phase, based on comparing the logs that Artur > > posted. > > > > I see. I got co

Re: [openstack-dev] [Horizon][Neutron] dashboard repository for neutron subprojects

Getting additional packages through distro channels can be surprisingly difficult for new packages. :/ So having one new package for neutron-subprojects-dashboard rather then many might be much easier. Thanks, Kevin From: Akihiro Motoki [amot...@gmail.c

Re: [openstack-dev] [nova][neutron][upgrade] Grenade multinode partial upgrade

I'll have to run some rechecks - but perhaps the issue is stable/kilo faceplanting on creating the initial resources (which is what, a 30% success rate? 1 out of 3 runs?) - the only run where we got far enough to upgrade we were actually successful? -- Sean M. Collins __

Re: [openstack-dev] Encouraging first-time contributors through bug tags/reviews

Excerpts from Shamail Tahir's message of 2015-11-25 09:15:54 -0500: > Hi everyone, > > Andrew Mitry recently shared a medium post[1] by Kent C. Dobbs which > discusses how one open-source project is encouraging contributions by new > open-source contributors through a combination of a special tag

Re: [openstack-dev] [all] Thoughts on python-future?

Julien Danjou wrote: On Tue, Nov 24 2015, Eric Kao wrote: I¹ve been using the python-future library for Python 3 porting and want to see what people think of it. http://python-future.org/overview.html#features The end result is standard Python3 code made compatible with Python2 through library

Re: [openstack-dev] [nova][neutron][upgrade] Grenade multinode partial upgrade

Yes, this file is complete fine. The Grenade is running smoke test before resource creation. The workflow is like this: 1. Install old devstack on main and subnode 2. Run tempest smoke 3. Create resources 4. Verify resources 5. Shutdown the services 6. Verify if shutdown does not affect the resou

[openstack-dev] [gnocchi][rating] Issues regarding gnocchi support in CloudKitty

Hi, We've started implementing gnocchi support in CloudKitty. But we're facing some issues. Some problems where client sided and are now fixed, but for some others it might doing wrong requests or not using gnocchi's full potential. Here are some problems we're actually facing: We can't directly

[openstack-dev] [release] better linting of release notes

We noticed today that I left out a setting in the original instructions I sent to explain how to configure reno. We want to ensure that the release notes render properly and without warnings, and to do that we need to turn on the option to Sphinx to treat warnings as errors by adding "-W" to the s

Re: [openstack-dev] [gnocchi][rating] Issues regarding gnocchi support in CloudKitty

On Wed, Nov 25 2015, Stéphane Albert wrote: Hi Stéphane, > We can't directly query gnocchi resource indexer for a specific resource > revision. Let me explain it, if you want to search for every instances > active for a specific timeframe you'll get a result but the revision > will be the latest,

Re: [openstack-dev] [Murano] 'NoMatchingFunctionException: No function "#operator_." matches supplied arguments' error when adding an application to an environment

Kate, Serg, Thank you very much for your quick responses. I am attaching the requested yaml file. For Hot2 plugin, the only difference with hot_package.py is that I changed the UI translation version to 2.2 and removed predefined_fields in _translate_ui_parameters method. The ui.yaml file is a

Re: [openstack-dev] [nova][neutron][upgrade] Grenade multinode partial upgrade

On 25 November 2015 at 10:03, Sean M. Collins wrote: > On Wed, Nov 25, 2015 at 12:53:56PM EST, Armando M. wrote: > > On 25 November 2015 at 09:49, Sean M. Collins > wrote: > > > > > Yeah looks like I read it wrong - the failure occurred during the > > > initial resource creation phase, based on

[openstack-dev] [searchlight] [release] Searchlight client launchpad project

Hello all, We have started building out the python client and OpenStack client plugin for Searchlight. We’ve now encountered the question of whether or not to manage the client change tracking through another Launchpad project specific to the client [2] or continue to manage it through the curr

[openstack-dev] [release] Release countdown for week R-18, Nov 30 - Dec 4

Focus - R-18 is the Mitaka 1 milestone deadline. All projects following the cycle-with-milestones release model should be preparing for the milestone tag. Release Actions --- All deliverables must have reno configured before adding a Mitaka 1 milestone tag. We will be using the

Re: [openstack-dev] [nova][neutron][upgrade] Grenade multinode partial upgrade

On 25 November 2015 at 10:15, Korzeniewski, Artur < artur.korzeniew...@intel.com> wrote: > Yes, this file is complete fine. The Grenade is running smoke test before > resource creation. > The workflow is like this: > 1. Install old devstack on main and subnode > 2. Run tempest smoke > 3. Create re

Re: [openstack-dev] [Fuel] Getting rid of Docker containers on the Fuel master node

IMO, removing the docker containers is a mistake v.s. fixing them and using them properly. They provide an isolation that is necessary (and that we mangle) to make services portable and scaleable. We really should sit down and document how we really want all of the services to interact before we r

Re: [openstack-dev] [nova][neutron][upgrade] Grenade multinode partial upgrade

On 25 November 2015 at 11:33, Armando M. wrote: > > > On 25 November 2015 at 10:15, Korzeniewski, Artur < > artur.korzeniew...@intel.com> wrote: > >> Yes, this file is complete fine. The Grenade is running smoke test before >> resource creation. >> The workflow is like this: >> 1. Install old dev

Re: [openstack-dev] [nova][neutron][upgrade] Grenade multinode partial upgrade

On Wed, Nov 25, 2015 at 02:31:26PM EST, Armando M. wrote: > So we fail before even attempting an upgrade? Yeah I think so, I think we were failing at step 3 of Artur's list, creating the resources. > It looks like we're testing 7.0.1.dev114, shouldn't we test from 7.0.0? I think Grenade checks o

[openstack-dev] [Sahara] Instance customization for Bootstrapping the cluster nodes

Hello Everyone, I am looking for a way to customize my Cluster nodes at cluster creation time. This is something like: AWS EMR BootStrap Action: http://docs.aws.amazon.com/ElasticMapReduce/latest/DeveloperGuide/emr-plan-bootstrap.html While creating an instance through nova boot command / UI, the

Re: [openstack-dev] Encouraging first-time contributors through bug tags/reviews

Hi, > On Nov 25, 2015, at 10:51 PM, Anthony Chow wrote: > > Have a tag for first time contributor is a great idea. > > On the other hand we should not take out the "low hanging fruit" tag. I > contribute to OpenStack on my spare time and in my current situation I can > only work on the low h

Re: [openstack-dev] Encouraging first-time contributors through bug tags/reviews

Hi, > On Nov 25, 2015, at 11:05 PM, Doug Hellmann wrote: > > Excerpts from Shamail Tahir's message of 2015-11-25 09:15:54 -0500: >> Hi everyone, >> >> Andrew Mitry recently shared a medium post[1] by Kent C. Dobbs which >> discusses how one open-source project is encouraging contributions by ne

[openstack-dev] [pbr][oslo] volunteer needed to increase pbr test coverage of sphinx

Hi, so pbr has some glue that revolves around running sphinx, and it got messy and broken with Sphinx 1.3. Its been broken in a subtle way since then - warnerrors has no effect, and previous attempts to get it working have broken things in a hard visible way. Doug has a patch up - https://review.

Re: [openstack-dev] Encouraging first-time contributors through bug tags/reviews

Excerpts from Shamail's message of 2015-11-26 01:22:48 +0500: > Hi, > > > On Nov 25, 2015, at 11:05 PM, Doug Hellmann wrote: > > > > Excerpts from Shamail Tahir's message of 2015-11-25 09:15:54 -0500: > >> Hi everyone, > >> > >> Andrew Mitry recently shared a medium post[1] by Kent C. Dobbs whi

Re: [openstack-dev] [ironic][security] what is OK to put in DEBUG logs?

On Mon, 2015-11-23 at 11:43 -0500, Ruby Loo wrote: > On 20 November 2015 at 18:32, Ben Nemec > wrote: > > On 11/19/2015 06:00 AM, Lucas Alvares Gomes wrote: > > > Hi, > > > > > >> Also keep in mind that DEBUG logging, while still should have > > some masking > > >> of data, since it is explicitly

Re: [openstack-dev] [Ironic][Neutron] Testing of Ironic/Neutron integration on devstack

This is cool. I didn't know you were working on an OVS driver for testing in CI as well. :) Does this work by getting the port wired into OVS so the agent recognizes it like a regular port so it can be put into VXLAN/VLAN or whatever the node is configured with? From what I can tell it looks like

Re: [openstack-dev] [Ironic][Neutron] Testing of Ironic/Neutron integration on devstack

Hi Vasyl, This is great. Kevin and I was working on the similar thing. I just finished testing his patch and gave a +1. This is a missing (and needed) functionality for getting the Ironic/Neutron integration completed. As Kevin suggests, it will be best if we can combine these approaches and come

Re: [openstack-dev] Encouraging first-time contributors through bug tags/reviews

> On Nov 26, 2015, at 1:42 AM, Doug Hellmann wrote: > > OK, reserving bugs for new contributors does reduce the number of > people contending for them, but it doesn't eliminate the need to > figure out if someone else is already working on a bug before you > start. Encouraging folks to assign b

Re: [openstack-dev] [all] Thoughts on python-future?

I think the main benefit of python-future is that the library helps us write straight Python 3 code instead of special bridged code. For example, instead of writing six.iteritems(dict0), one could write simply dict0.items() and expect Python 3 behavior across Python 2 & 3. This way, whenever Pytho

Re: [openstack-dev] [all] Thoughts on python-future?

Thanks for sharing your thoughts and experiences everyone! It’s really too bad that the library causes all this headache. The goal is laudable: enable Python 3 code to run on Python 2 with minimal modification. It’d be really nice to write clean, standard Python 3 code [e.g., dict0.items() ] rathe

[openstack-dev] [Security] Cancelling the weekly IRC meeting for thanks giving

Hi all, As the vast majority of the Security Project members are US based we are cancelling the IRC meeting tomorrow. I’ll send out an ether pad agenda early next week and we can catch up then! Kind Regards -Rob __ OpenStac

Re: [openstack-dev] [all] Thoughts on python-future?

On 26 November 2015 at 10:08, Eric Kao wrote: > I think the main benefit of python-future is that the library helps us > write straight Python 3 code instead of special bridged code. > > For example, instead of writing six.iteritems(dict0), one could write > simply dict0.items() and expect Python

Re: [openstack-dev] [all] Time to increase our IRC Meetings infrastructure?

On Wed, Nov 25, 2015 at 05:15:48PM +0100, Ihar Hrachyshka wrote: > Thanks Tony for leading the effort. As you know, neutron-upgrades team > (well, me) actually confused -alt/-2 thing, and I registered a meeting for > -2. I now have tools that will chack that human error in CI. It's just a matter

Re: [openstack-dev] [tripleo] Location of TripleO REST API

On 11/23/2015 06:50 AM, Dmitry Tantsur wrote: > On 11/17/2015 04:31 PM, Tzu-Mainn Chen wrote: >> >> >> >> >> >> On 10 November 2015 at 15:08, Tzu-Mainn Chen > > wrote: >> >> Hi all,

Re: [openstack-dev] [keystone] Mid-Cycle Meetup Planning

23 responses later and it's settled, we'll be having the midcycle in Austin TX between January 27-29. I've updated the wiki to reflect this update: https://wiki.openstack.org/wiki/Sprints/KeystoneMitakaSprint Looking forward to seeing everyone there! - Steve Steve Martinelli/Toronto/IBM@IBMCA wr

Re: [openstack-dev] Encouraging first-time contributors through bug tags/reviews

Excerpts from Shamail's message of 2015-11-26 02:07:55 +0500: > > > On Nov 26, 2015, at 1:42 AM, Doug Hellmann wrote: > > > > OK, reserving bugs for new contributors does reduce the number of > > people contending for them, but it doesn't eliminate the need to > > figure out if someone else is a

Re: [openstack-dev] [Neutron] Call for review focus

On Mon, Nov 23, 2015 at 7:02 AM, Rossella Sblendido wrote: > > > On 11/20/2015 03:54 AM, Armando M. wrote: >> >> >> >> On 19 November 2015 at 18:26, Assaf Muller > > wrote: >> >> On Wed, Nov 18, 2015 at 9:14 PM, Armando M. > > wrote: >>

[openstack-dev] [ironic] Releases and things

Hi all, We're approaching OpenStack's M-1 milestone, and as we have lots of good stuff in the master branch, and no Mitaka release yet, I'd like to make a release next Thursday, December 3. First, I've caught us up (best I can tell) on missing release notes since our last release. Please do revie

[openstack-dev] [magnum] Using docker container to run COE daemons

Hi, It is becoming more and more popular to use docker container run some applications, so what about leveraging this in Magnum? What I want to do is that we can put all COE daemons running in docker containers, because now Kubernetes, Mesos and Swarm support running in docker container and there

  1   2   >