Re: [openstack-dev] [Heat][tripleo] Tripleo holding on to old, bad data

Adam, not only "available", Nova would also not schedule to Ironic nodes which have maintenance==True regardless of their provisioning state. Also, you might have orphaned Ironic nodes, when node is available, but still has instance_uuid assigned without actual instance in Nova. These AFAIK would

[openstack-dev] [Nova] Questions about instance actions' update and finish

Hi all, I'm working on add pagination and timestamp filter for os-instance-actions API: https://review.openstack.org/#/c/326326/ As Alex_xu pointed out that it will be better to filter by `updated_at` for timestamp filter which is reasonable, but when I tried to modify the patch I found out that:

Re: [openstack-dev] [Cinder] Nominating Scott D'Angelo to Cinder core

+2 Congrats Scott!! On 27/06, Sean McGinnis wrote: > I would like to nominate Scott D'Angelo to core. Scott has been very > involved in the project for a long time now and is always ready to help > folks out on IRC. His contributions [1] have been very valuable and he > is a thorough reviewer [

[openstack-dev] [mistral] Test and Manage Openstack actions in Mistral

Hi folks, In Mistral, we face issues related managing openstack actions. Currently we have mapping.json file which should be updated manually using tools/get_actions_list.py. However, this script cannot be useful for neutron, zaqar, swift etc. Also, our unit test cases are not so efficient. S

Re: [openstack-dev] [Kuryr] Refactoring into common library and kuryr-libnetwork + Nested_VMs

On Mon, Jun 27, 2016 at 11:10 AM, Vikas Choudhary < [email protected]> wrote: > > > On Mon, Jun 27, 2016 at 2:22 PM, Fawad Khaliq wrote: > >> Vikas, >> >> Thanks for starting this. Where would you classify the Segmentation >> (VLANID etc) allocation engine. Currently, the libnetwork plug

Re: [openstack-dev] [mistral] Test and Manage Openstack actions in Mistral

> On 28 Jun 2016, at 15:13, Hardik wrote: > > Hi folks, > > In Mistral, we face issues related managing openstack actions. > > Currently we have mapping.json file which should be updated manually using > tools/get_actions_list.py. > However, this script cannot be useful for neutron, zaqar, sw

[openstack-dev] [storlets] Docker images re-structuring

Currently, our Docker images are built form the following layers: 1. Ubuntu 14.04 2. JRE 8 3. Storlets stuff 4. Dummy layer having the tenant id as a name. Only yesterday (after more then 2 years...), it occurred to me that the 3rd layer is a bit of a (understatement) mistake. Why not place t

Re: [openstack-dev] [Kuryr] Refactoring into common library and kuryr-libnetwork + Nested_VMs

On Tue, Jun 28, 2016 at 1:53 PM, Antoni Segura Puimedon < [email protected]> wrote: > > > On Mon, Jun 27, 2016 at 11:10 AM, Vikas Choudhary < > [email protected]> wrote: > >> >> >> On Mon, Jun 27, 2016 at 2:22 PM, Fawad Khaliq wrote: >> >>> Vikas, >>> >>> Thanks for starting

Re: [openstack-dev] [Fuel] - Nominate Maksim Malchuk to Fuel Library Core

+1 On Tue, Jun 28, 2016 at 1:16 AM, Matthew Mosesohn wrote: > +1. Maksim is an excellent reviewer. > > On Mon, Jun 27, 2016 at 6:06 PM, Alex Schultz > wrote: > > +1 > > > > On Mon, Jun 27, 2016 at 9:04 AM, Bogdan Dobrelya > > > wrote: > >> > >> On 06/27/2016 04:54 PM, Sergii Golovatiuk wrote:

Re: [openstack-dev] [Kuryr] Refactoring into common library and kuryr-libnetwork + Nested_VMs

On Tue, Jun 28, 2016 at 11:54 AM, Vikas Choudhary < [email protected]> wrote: > > > On Tue, Jun 28, 2016 at 1:53 PM, Antoni Segura Puimedon < > [email protected]> wrote: > >> >> >> On Mon, Jun 27, 2016 at 11:10 AM, Vikas Choudhary < >> [email protected]> wrote: >> >>>

Re: [openstack-dev] [Kuryr] Refactoring into common library and kuryr-libnetwork + Nested_VMs

On Tue, Jun 28, 2016 at 3:41 PM, Antoni Segura Puimedon < [email protected]> wrote: > > > On Tue, Jun 28, 2016 at 11:54 AM, Vikas Choudhary < > [email protected]> wrote: > >> >> >> On Tue, Jun 28, 2016 at 1:53 PM, Antoni Segura Puimedon < >> [email protected]> wrot

Re: [openstack-dev] [Fuel] - Nominate Maksim Malchuk to Fuel Library Core

+1 On Tue, Jun 28, 2016 at 1:12 PM, Kyrylo Galanov wrote: > +1 > > On Tue, Jun 28, 2016 at 1:16 AM, Matthew Mosesohn > wrote: > >> +1. Maksim is an excellent reviewer. >> >> On Mon, Jun 27, 2016 at 6:06 PM, Alex Schultz >> wrote: >> > +1 >> > >> > On Mon, Jun 27, 2016 at 9:04 AM, Bogdan Dobrel

[openstack-dev] [Fuel] Deprecate fuel-upgrade repository

Dear colleagues, Please be informed that fuel-upgrade [1] repository is going to be deprecated. We used to develop Fuel admin node upgrade scenarios in this repo, but now all upgrade related stuff is in fuel-octane [2] repo. So, fuel-upgrade is to be removed from the list of official Fuel repos [3

Re: [openstack-dev] [Cinder] Nominating Scott D'Angelo to Cinder core

+1 Not a core but surely is well deserved. Congrats Scott!! On Tue, Jun 28, 2016 at 5:06 AM, Gorka Eguileor wrote: > > +2 > > Congrats Scott!! > > > On 27/06, Sean McGinnis wrote: > > I would like to nominate Scott D'Angelo to core. Scott has been very > > involved in the project for a long time

Re: [openstack-dev] [Fuel] - Nominate Maksim Malchuk to Fuel Library Core

Although I'm not Fuel core, +1 from me to Maksim. Maksim is not only excellent engineer but also very friendly and helpful folk. On Tue, Jun 28, 2016 at 12:19 PM, Georgy Kibardin wrote: > +1 > > On Tue, Jun 28, 2016 at 1:12 PM, Kyrylo Galanov > wrote: > >> +1 >> >> On Tue, Jun 28, 2016 at 1:16

[openstack-dev] [new][oslo] oslo.cache 1.10.0 release (newton)

We are happy to announce the release of: oslo.cache 1.10.0: Cache storage for Openstack projects. This release is part of the newton release series. With source available at: http://git.openstack.org/cgit/openstack/oslo.cache With package available at: https://pypi.python.org/pypi/osl

[openstack-dev] [new][oslo] oslo.concurrency 3.11.0 release (newton)

We are eager to announce the release of: oslo.concurrency 3.11.0: Oslo Concurrency library This release is part of the newton release series. With source available at: http://git.openstack.org/cgit/openstack/oslo.concurrency With package available at: https://pypi.python.org/pypi/oslo

[openstack-dev] [new][oslo] oslo.config 3.12.0 release (newton)

We are pleased to announce the release of: oslo.config 3.12.0: Oslo Configuration API This release is part of the newton release series. With source available at: http://git.openstack.org/cgit/openstack/oslo.config With package available at: https://pypi.python.org/pypi/oslo.config P

[openstack-dev] [new][oslo] oslo.policy 1.11.0 release (newton)

We are gleeful to announce the release of: oslo.policy 1.11.0: Oslo Policy library This release is part of the newton release series. With source available at: http://git.openstack.org/cgit/openstack/oslo.policy With package available at: https://pypi.python.org/pypi/oslo.policy Plea

[openstack-dev] [new][oslo] oslo.serialization 2.10.0 release (newton)

We are tickled pink to announce the release of: oslo.serialization 2.10.0: Oslo Serialization library This release is part of the newton release series. With source available at: http://git.openstack.org/cgit/openstack/oslo.serialization With package available at: https://pypi.python.

[openstack-dev] [new][oslo] oslo.log 3.11.0 release (newton)

We are overjoyed to announce the release of: oslo.log 3.11.0: oslo.log library This release is part of the newton release series. With source available at: http://git.openstack.org/cgit/openstack/oslo.log With package available at: https://pypi.python.org/pypi/oslo.log Please report

[openstack-dev] [new][oslo] oslo.reports 1.11.0 release (newton)

We are delighted to announce the release of: oslo.reports 1.11.0: oslo.reports library This release is part of the newton release series. With source available at: http://git.openstack.org/cgit/openstack/oslo.reports With package available at: https://pypi.python.org/pypi/oslo.reports

[openstack-dev] [new][oslo] oslo.versionedobjects 1.12.0 release (newton)

We are stoked to announce the release of: oslo.versionedobjects 1.12.0: Oslo Versioned Objects library This release is part of the newton release series. With source available at: http://git.openstack.org/cgit/openstack/oslo.versionedobjects With package available at: https://pypi.pyt

[openstack-dev] [new][oslo] oslosphinx 4.5.0 release (newton)

We are excited to announce the release of: oslosphinx 4.5.0: OpenStack Sphinx Extensions and Theme This release is part of the newton release series. With source available at: http://git.openstack.org/cgit/openstack/oslosphinx With package available at: https://pypi.python.org/pypi/os

[openstack-dev] [new][oslo] oslo.middleware 3.14.0 release (newton)

We are jubilant to announce the release of: oslo.middleware 3.14.0: Oslo Middleware library This release is part of the newton release series. With source available at: http://git.openstack.org/cgit/openstack/oslo.middleware With package available at: https://pypi.python.org/pypi/oslo

[openstack-dev] [new][oslo] oslo.utils 3.14.0 release (newton)

We are delighted to announce the release of: oslo.utils 3.14.0: Oslo Utility library This release is part of the newton release series. With source available at: http://git.openstack.org/cgit/openstack/oslo.utils With package available at: https://pypi.python.org/pypi/oslo.utils Plea

[openstack-dev] [new][oslo] oslo.vmware 2.10.0 release (newton)

We are eager to announce the release of: oslo.vmware 2.10.0: Oslo VMware library This release is part of the newton release series. With source available at: http://git.openstack.org/cgit/openstack/oslo.vmware With package available at: https://pypi.python.org/pypi/oslo.vmware Please

Re: [openstack-dev] [Fuel] Failed to build the bootstrap image

Hi all, I tried to create ubuntu bootstrap using [0] but the slave can still not booting. You can find the bootstrap log following [1]. Noticed that I've deleted the depot [2] from fuelmenu because it generated an error "URL for repository mos is not accessible". Regards, [0] fuel-bootstrap bui

[openstack-dev] [new][oslo] tooz 1.40.0 release (newton)

We are psyched to announce the release of: tooz 1.40.0: Coordination library for distributed systems. This release is part of the newton release series. With source available at: http://git.openstack.org/cgit/openstack/tooz With package available at: https://pypi.python.org/pypi/tooz

[openstack-dev] [new][oslo] oslo.messaging 5.5.0 release (newton)

We are glad to announce the release of: oslo.messaging 5.5.0: Oslo Messaging API This release is part of the newton release series. With source available at: http://git.openstack.org/cgit/openstack/oslo.messaging With package available at: https://pypi.python.org/pypi/oslo.messaging

[openstack-dev] [kolla] version of python2-oslo-config

Hi Kolla team, Base upon requirement.txt, Kolla needs oslo-config version 3.10. But CentOS Mitaka uses 3.9 ,which is python2-oslo-config-3.9.0-1.el7.noarch.rpm. I want to know if Kolla can also work on oslo-config-3.9.0. If it can, then will be a benefit because pip is conflict with rpm on py

Re: [openstack-dev] [Fuel] Failed to build the bootstrap image

You have an issue with connectivity from the Fuel master node to http://archive.ubuntu.com from the log: > Command: debootstrap --include=ca-certificates,apt-transport-https --verbose > --no-check-gpg --arch=amd64 trusty /tmp/tmp1K2haC.fuel-agent-image > http://archive.ubuntu.com/ubuntu > Exit c

Re: [openstack-dev] [tripleo] glance backend: replace swift by file in CI

TL;DR Makes absolutely sense to run file backend on single node undercloud at CI. Few more comments inline. On Mon, Jun 27, 2016 at 8:49 PM, Emilien Macchi wrote: > On Mon, Jun 27, 2016 at 3:46 PM, Clay Gerrard wrote: >> There's probably some minimal gain in cross compatibility testing to >> s

[openstack-dev] 答复: [probably forge email可能是仿冒邮件] [kolla] version of python2-oslo-config

Sorry I used the wrong branch of Kolla, in stable/Mitaka , Kolla only requires oslo-config ver 3.7 发件人: [email protected] 收件人: "OpenStack Development Mailing List (not for usage questions)" , 日期: 2016-06-28 19:34 主题: [probably forge email可能是仿冒邮件][openstack-dev] [koll

[openstack-dev] [nova][SR-IOV] PCI/SR-IOV meeting today is canceled 06/28/16

Sorry for the late mail, but I won't be able to chair the meeting today __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: [email protected]?subject:unsubscribe http://lists.o

Re: [openstack-dev] [cinder] [keystone] cinder quota behavior differences after Keystone mitaka upgrade

On Tue, Jun 28, 2016 at 3:38 AM, Henry Nash wrote: > Hi Matt, > > So the keystone changes were intentional. From Mitaka onwards, a domain is > represented as a project which is “acting as a domain” (it has an attribute > “is_domain” set to true). The situation you describe, where what were top >

Re: [openstack-dev] [Nova] Questions about instance actions' update and finish

On Tue, Jun 28, 2016, at 03:26 AM, Zhenyu Zheng wrote: > Hi all, > > I'm working on add pagination and timestamp filter for os-instance- > actions API: > https://review.openstack.org/#/c/326326/ > As Alex_xu pointed out that it will be better to filter by > `updated_at` for timestamp filter w

[openstack-dev] [kolla] Usage of Reno - all devs please read

Hey folks, We have had reno in place since the end of Mitaka, yet folks aren't using it very often. I am guilty myself of not thinking of it when reviewing changes. Core reviewers: Please -1 any review of significant work that doesn't include a reno release note. Developers: If you have made

[openstack-dev] [telemetry] Ceilometer and Aodh install guide(s)

Hi, I'm currently working on to move the Install Guide for Ceilometer [1] and Aodh [2] under the project trees. I faced with a few difficulties so far about which I would like to ask your opinion. First of all these two projects are under the Telemetry umbrella, so they are not completely sepa

Re: [openstack-dev] [Fuel] Failed to build the bootstrap image

I've removed /var/log/fuel-bootstrap-image-build.log, created new bootstrap ubuntu again after setting proxy parameters and reboot. After the there is no /var/log/fuel-bootstrap-image-build.log create from the new bootstrap but slave doesn't boot correctly. Is there another way to detect slave node

Re: [openstack-dev] [OpenStack-docs] [telemetry] Ceilometer and Aodh install guide(s)

On 2016-06-28 14:55, Ildikó Váncsa wrote: > [...] > I have a third less urgent question. The install-guide has it's own folder at > the same level where these two projects have their 'doc' folder. I would > assume other projects have the same or similar folder for the developer docs. > Would tha

Re: [openstack-dev] [kolla] Usage of Reno - all devs please read

Hi, Steven Do you mind giving some example of such reno release note? Thanks. - Hui On Tue, Jun 28, 2016 at 8:46 AM, Steven Dake (stdake) wrote: > Hey folks, > > We have had reno in place since the end of Mitaka, yet folks aren't using it > very often. I am guilty myself of not thinking of it w

[openstack-dev] [charms] inclusion of charm-helpers (LGPL licensed)

Hi All Whilst working on the re-licensing of the OpenStack charms to Apache 2.0, its apparent that syncing and inclusion of the charm-helpers python module directly into the charm is not going to work from a license compatibility perspective. charm-helpers is LGPL v3 (which is OK for a runtime dep

Re: [openstack-dev] [OpenStack-docs] [telemetry] Ceilometer and Aodh install guide(s)

Hi Ildikó, Please take a look at the tooling in https://review.openstack.org/#/c/317152/ - I tried preserving the ‘only::’ tags because I had a similar concern about all the common parts to someone compiling the install guide from time to time. We were discussing whether this was a good soluti

Re: [openstack-dev] [telemetry] Ceilometer and Aodh install guide(s)

> -Original Message- > From: Ildikó Váncsa [mailto:[email protected]] > Sent: Tuesday, June 28, 2016 7:56 AM > To: [email protected] > Cc: [email protected] > Subject: [OpenStack-docs] [telemetry] Ceilometer and Aodh install > guide(s) snip > > T

Re: [openstack-dev] [mistal] Mistral logo ideas?

On 28 June 2016 at 06:38, Jason Rist wrote: > On 06/27/2016 06:57 AM, Dougal Matthews wrote: > > On 27 June 2016 at 07:45, Renat Akhmerov > wrote: > > > > > > > >> Ideally it would be nice to have something that matches the meaning of > > > the > > >> name. Maybe we can combine wind with one of

Re: [openstack-dev] [Fuel] Failed to build the bootstrap image

You can start build command with debug options enabled for example and copy/paste output: > > fuel-bootstrap --verbose --debug build --activate > Very bad idea to remove logfile, it's better to empty it not remove. If you don't have the logfile, so recreate it with command: > touch /var/log/fue

Re: [openstack-dev] [tricircle] About registering and loading a plugin

Hi all, Thanks a lot for your valuable advice. I have already succeed in registering and loading a self-defined plugin. The entry_point is generated by executing setup.py, and found in .egg-info/entry_points.txt, which is different from using setup.cfg in https://review.openstack.org/#/c/331638/.

Re: [openstack-dev] [mistal] Mistral logo ideas?

On Tue, Jun 28, 2016 at 1:38 AM, Jason Rist wrote: > On 06/27/2016 06:57 AM, Dougal Matthews wrote: > > On 27 June 2016 at 07:45, Renat Akhmerov > wrote: > > > > > > > >> Ideally it would be nice to have something that matches the meaning of > > > the > > >> name. Maybe we can combine wind with

[openstack-dev] [Smaug]- IRC Meeting today (28/06) - 1500 UTC SM,

Hi All, We will hold our weekly IRC meeting today (Tuesday, 28/06) at 1500 UTC in #openstack-meeting Please review the proposed meeting agenda here: https://wiki.openstack.org/wiki/Meetings/smaug Please feel free to add to the agenda any subject you would like to discuss. Thanks, Saggi

Re: [openstack-dev] Change in openstack/trove[master]: Ophaned Volume Not Removed on Instance Delete

Hi all, I'd like to make sure should the volume, which is attached to an instance, be *detached* or be *deleted* after the instance is deleted? Thanks. On Tue, Jun 28, 2016 at 10:16 PM Ali Asgar Adil (Code Review) < [email protected]> wrote: > Ali Asgar Adil has posted comments on this chang

Re: [openstack-dev] [telemetry] Ceilometer and Aodh install guide(s)

On Tue, Jun 28 2016, Ildikó Váncsa wrote: > I have a third less urgent question. The install-guide has it's own folder at > the same level where these two projects have their 'doc' folder. I would > assume > other projects have the same or similar folder for the developer docs. Would > that be re

Re: [openstack-dev] [Cinder] Nominating Scott D'Angelo to Cinder core

+2. Welcome to the team! Regards, Ivan Kolodyazhny, http://blog.e0ne.info/ On Tue, Jun 28, 2016 at 1:48 PM, Erlon Cruz wrote: > +1 > Not a core but surely is well deserved. Congrats Scott!! > > On Tue, Jun 28, 2016 at 5:06 AM, Gorka Eguileor > wrote: > >> >> +2 >> >> Congrats Scott!! >> >> >>

Re: [openstack-dev] [cinder] [keystone] cinder quota behavior differences after Keystone mitaka upgrade

Thanks Henry, >From a Keystone POV I think it makes sense, but it's causing some operational headaches, so I'm curious what the cinder team thinks about this. Not being able to see or set someone's quota as an admin is frustrating for dealing with support requests. On Tue, Jun 28, 2016 at 12:38

Re: [openstack-dev] Change in openstack/trove[master]: Ophaned Volume Not Removed on Instance Delete

Hi Scott, many thanks for your figuration. Thanks and +1 for your nomination to nova core:) Hi aadil, we should DETACH the volume, instead of DELETE. Please help enhance your code which is really a helpful fix to the bug. Thanks. On Tue, Jun 28, 2016 at 10:51 PM D'Angelo, Scott wrote: > If a v

Re: [openstack-dev] Change in openstack/trove[master]: Ophaned Volume Not Removed on Instance Delete

If a volume is attached to an instance, and the instance is deleted, the volume will be DETACHED, but the volume will still exist, it will NOT be DELETED. It is up to the volume owner to delete the volume if they wish. From: Will Zhou Sent: Tuesday, June 28, 201

[openstack-dev] [Neutron][DVR] - No IRC Meeting this week

Hi Folks, We will not have a DVR sub-team meeting this week since neither Swami nor myself will be there to chair it. We will resume our meetings next week on July 6th. If you have any questions please ping us on IRC or send an email to the list. https://wiki.openstack.org/wiki/Meetings/Neut

Re: [openstack-dev] [Cinder] Nominating Scott D'Angelo to Cinder core

On 06/27/2016 01:27 PM, Sean McGinnis wrote: > I would like to nominate Scott D'Angelo to core. Scott has been very > involved in the project for a long time now and is always ready to help > folks out on IRC. His contributions [1] have been very valuable and he > is a thorough reviewer [2]. > > P

Re: [openstack-dev] [puppet] weekly meeting #86

Meeting cancelled again, no topic this week. See you next week! On Mon, Jun 27, 2016 at 8:39 AM, Emilien Macchi wrote: > Hi, > > If you have any topic for our meeting tomorrow, please add them on the > etherpad: > https://etherpad.openstack.org/p/puppet-openstack-weekly-meeting-2

Re: [openstack-dev] [Fuel] Deprecate fuel-upgrade repository

This patch [1] is a part of project retirement procedure [2]. Review is welcome. [1] https://review.openstack.org/#/c/335085/ [2] http://docs.openstack.org/infra/manual/drivers.html#retiring-a-project Vladimir Kozhukalov On Tue, Jun 28, 2016 at 1:41 PM, Vladimir Kozhukalov < vkozhuka...@mirantis

Re: [openstack-dev] [telemetry] Ceilometer and Aodh install guide(s)

+1 on the modular approach by Rodrigo Caballero I'm writing magnum's guide and I'm working on the debian guide. Debian's guide will have a couple of differences and I plan to move them in other files or/and break the existing common config files. IMO, one of the goals of the project specific guid

Re: [openstack-dev] [mistal] Mistral logo ideas?

Hi, Attached another draft based on Michal's idea (it probably should be more colourful) Maybe we can upload them to some online survey and vote… From: Ryan Brady mailto:[email protected]>> Reply-To: "OpenStack Development Mailing List (not for usage questions)" mailto:[email protected]

Re: [openstack-dev] [Fuel] Failed to build the bootstrap image

Maksim, The bootstrap process woks fine without error but the slave can boot from network. I think that the issue is due TFTP process, it tries to reach http://10.20.0.2/cobbler/boot, I used my web browser but there is not directory named boot in cobbler folder. Should the bootstrap create this dir

[openstack-dev] [ironic] why do we need setting network driver per node?

Hi folks! I was reviewing https://review.openstack.org/317391 and realized I don't quite understand why we want to have node.network_interface. What's the real life use case for it? Do we expect some nodes to use Neutron, some - not? Do we expect some nodes to benefit from network separation

[openstack-dev] [murano] Load murano Apps

Hi all, I've downloaded murano apps from [1] and I would like to upload them as package. I would like to know which folders into murano-apps to zip and load from "Package Definition" ? How to add these apps with murano package-import ? Regards, [1] https://github.com/openstack/murano-apps _

Re: [openstack-dev] [Cinder] Nominating Scott D'Angelo to Cindercore

Congratulations Scott :) All the Best, Kendall J. Nelson Software Engineer & OpenStack Contributor

[openstack-dev] [Nova][Neutron][Live-Migration] Cross l2 agent migration and solving Nova-Neutron live migration bugs

Hi, I'm currently working on solving Nova-Neutron issues during Live Migration. This mail is intended to raise awareness cross project and get things kicked off. The issues == #1 When portbinding fails, instance is migrated but stuck in error state #2 Macvtap agent live Migration when so

Re: [openstack-dev] [murano] Load murano Apps

Hi Alione, you need to archive content of the "package" folder, e.g. MySQL [0]. Make sure that manifest.yaml is on the root level. References: [0] https://github.com/openstack/murano-apps/tree/master/MySQL/package On Tue, Jun 28, 2016 at 8:36 AM, Alioune wrote: > Hi all, > I've downloaded mura

Re: [openstack-dev] [kolla] Usage of Reno - all devs please read

On Tue, Jun 28, 2016 at 9:23 PM, Hui Kang wrote: > Do you mind giving some example of such reno release note? Thanks. ​like this https://review.openstack.org/#/c/235398/ .​ -- Regards, Jeffrey Zhang Blog: http://xcodest.me

Re: [openstack-dev] [kolla] version of python2-oslo-config

The mitaka branch of Kolla requires 3.7 or later. Git checkout stable/mitaka Master may require 3.10, but that happens via the global requirements update process, of which RDO will surely address in the future. Regards

Re: [openstack-dev] [kolla] Usage of Reno - all devs please read

On Tue, Jun 28, 2016 at 11:47:58PM +0800, Jeffrey Zhang wrote: > On Tue, Jun 28, 2016 at 9:23 PM, Hui Kang wrote: > > > Do you mind giving some example of such reno release note? Thanks. > > ​like this https://review.openstack.org/#/c/235398/ .​ The instructions are also very good: http://docs

Re: [openstack-dev] [ironic] why do we need setting network driver per node?

Following discussion on IRC, here are my thoughts: The proposed network_interface allows choosing a "driver" for the network part of a node. The values could be something like "nobody", "neutron-flat networking" and "neutron-tenant separation". I think this choice should be left per-node. My

Re: [openstack-dev] [telemetry] Ceilometer and Aodh install guide(s)

Hi, @Julien: +1 to the one 'doc' folder. I think it's not yet decided whether it should be modular, using '.. only::' or we can/will have both. I use the modular approach as well right now, I have many files containing the common things and the distro specific steps. For Ceilometer it resulted

Re: [openstack-dev] [OpenStack-docs] [telemetry] Ceilometer and Aodh install guide(s)

snip > > Do you have a good proposal for structuring things? [] I am assuming that you have distro specific instructions mixed with non-specific ones. I can only suggest what has worked for me in the past. I created a common file describing the process devoid of any instructions, distro specifi

Re: [openstack-dev] [mistral] [murano] [yaql] yaqluator bug

Hi, Thank you for the kind words, Alexey. I was able to reproduce your bug and I have also found the issue. The problem is that we did not create the parser with the engine_options used in the yaql library by default when using the CLI. Specifically, the "yaql.limitIterators" was missing… I am

Re: [openstack-dev] [Fuel] Failed to build the bootstrap image

1. Show the logfile to see the bootstrap process is finished without any errors. 2. It depends on the Fuel version, http://10.20.0.2/cobbler/boot in some cases can't be seen through the web browser. 3. You shouldn't do anything only reboot the slave node. If fuel-bootstrap executed correctly - your

Re: [openstack-dev] [kolla] Usage of Reno - all devs please read

Hi, Jeffrey and Nate, Thanks for the links. I will update my PS. - Hui On Tue, Jun 28, 2016 at 12:15 PM, Nate Johnston wrote: > On Tue, Jun 28, 2016 at 11:47:58PM +0800, Jeffrey Zhang wrote: >> On Tue, Jun 28, 2016 at 9:23 PM, Hui Kang wrote: >> >> > Do you mind giving some example of such reno

Re: [openstack-dev] [all] Proposal: Architecture Working Group

Thanks everyone for participating and remaining positive and focused on improving OpenStack. I've posted a review, and I'd like to encourage everyone to move any future discussion of the Architecture Working group to that review. https://review.openstack.org/335141 Excerpts from Clint Byrum's mes

Re: [openstack-dev] [ironic] why do we need setting network driver per node?

Thanks for bringing this up Dmitry, here are my thoughts on this. Another case is an out-of-tree network driver, that can basically do whatever an operator needs to, and may have some parameters defined in driver_info as is the case for most of other interfaces ironic drivers have. I think neutro

Re: [openstack-dev] [nova] Do we require the 'next' link for paging, always?

On 6/27/2016 9:57 PM, Alex Xu wrote: Matt, thanks for the email, I +1 on the next page link. Then user needn't build up link by themself. I also have one more question after review those pagination patches: As those pagination proposes change the default sort order. So should we keep the sort o

Re: [openstack-dev] [OpenStack-docs] [telemetry] Ceilometer and Aodh install guide(s)

Hi Goutham, Thanks, I already checked your solution briefly. I will wait until there is some decision about the global way forward. If '.. only::' remains an option I might change the Ceilometer setup back. Best Regards, /Ildikó > -Original Message- > From: Ravi, Goutham [mailto:goutha

Re: [openstack-dev] [OpenStack-docs] [telemetry] Ceilometer and Aodh install guide(s)

Hi Andreas, If we would end up moving more guides to the project tree then it will be confusing having multiple top level docs folder in a basically code repository. Can that be an option to have a top level 'doc' folder and having sub-folders under like 'doc/developer', 'doc/install-guide', et

Re: [openstack-dev] [OpenStack-docs] [telemetry] Ceilometer and Aodh install guide(s)

Hi Rodrigo, Thanks for sharing your view on this. I will consider what other way I have to organize the docs. I tried to extract the common parts and use '.. include::' as much as possible. The patch was huge already. I'm afraid what you're saying would result in even more duplication which is

Re: [openstack-dev] [cinder] [keystone] cinder quota behavior differences after Keystone mitaka upgrade

Hi all, I did some digging into this on the cinder side, and it gets a little complicated. So, before the target and context are passed into the _authorize_show method, they’re retrieved through the get_project_hierarchy method in cinder.quota_utils [1]. In that method, they will only have thei

Re: [openstack-dev] [Cinder] Nominating Scott D'Angelo to Cinder core

+1, also not a core but I agree, all I’ve seen from Scott has been super knowledgeable and helpful! -Nate From: Erlon Cruz [mailto:[email protected]] Sent: Tuesday, June 28, 2016 3:48 AM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [Cinder] Nom

Re: [openstack-dev] [nova] Do we require the 'next' link for paging, always?

On Tue, Jun 28, 2016, at 02:09 PM, Matt Riedemann wrote: > On 6/27/2016 9:57 PM, Alex Xu wrote: > > Matt, thanks for the email, I +1 on the next page link. Then user > > needn't build up link by themself. > > > > I also have one more question after review those pagination patches: > > > > As thos

Re: [openstack-dev] [cinder] [keystone] cinder quota behavior differences after Keystone mitaka upgrade

On Tue, Jun 28, 2016 at 12:32 PM, Potter, Nathaniel < [email protected]> wrote: > Hi all, > > > > I did some digging into this on the cinder side, and it gets a little > complicated. So, before the target and context are passed into the > _authorize_show method, they’re retrieved through

Re: [openstack-dev] [OpenStack-docs] [telemetry] Ceilometer and Aodh install guide(s)

On 06/28/2016 08:23 PM, Ildikó Váncsa wrote: > Hi Andreas, > > If we would end up moving more guides to the project tree then it will be > confusing having multiple top level docs folder in a basically code > repository. > > Can that be an option to have a top level 'doc' folder and having sub-

[openstack-dev] [craton] Midcycle meetup to discuss fleet management - Aug 23-26 in NYC

The Craton fleet management midcycle meetup will be held in New York City, August 23-26, using the following two events to provide structure/meeting support: - OpenStack East - developer-focused discussion on Craton core, along with further development of integration points; http://www.op

[openstack-dev] [craton] No IRC meeting on Monday July 4

Many of us will be celebrating the July 4 holiday in the US, so we will not be having our regularly scheduled meeting in #openstack-meeting-4 this coming Monday. Craton meetings are planned here: https://etherpad.openstack.org/p/craton-meetings - Jim __

[openstack-dev] [Magnum] Want to know our users

Hi all, FYI. The Magnum team is collecting a list of Magnum users. If you are using Magnum, we would like to have your name and organization recorded in our wiki [1]. Please note that this is totally optional, but we hope you will let us know if you are our users. [1] https://wiki.openstack.or

Re: [openstack-dev] [tripleo] ha & upgrade jobs are broken

On Mon, Jun 27, 2016 at 10:47 PM, Emilien Macchi wrote: > CI is still in bad shape, even if we fixed non-ha job [1]. > > See https://bugs.launchpad.net/tripleo/+bug/1596758 for the new issue > (ha & upgrade job look broken), it seems related to Pacemaker. > I investigated a little bit (late here)

[openstack-dev] [docs] [install-guide] Move launch-instance instructions in project repos

Hi. I'd like to propose to move the "launch-instance" section [1] in project repos along with the install-guide. If we won't move it, we must find an appropriate place for it. Cheers, Spyros [1] http://docs.openstack.org/mitaka/install-guide-ubuntu/launch-instance.html __

[openstack-dev] [Zun][Higgins] IRC channel rename notice

Hi all, Here is a notice that we have moved our IRC channel from #openstack-higgins to #openstack-zun . Right now, all the bots have been moved to the new channel [1]. The old channel is no longer used anymore. [1] https://review.openstack.org/#/c/330017/ Best regards, Hongbin

[openstack-dev] Troubleshooting and ask.openstack.org

Recently, the Keystone team started brainstormin a troubleshooting document. While we could, eventually put this into the Keystone repo, it makes sense to also be gathering troubleshooting ideas from the community at large. How do we do this? I think we've had a long enough run with the ask

Re: [openstack-dev] [grenade] upgrades vs rootwrap

On 06/28/2016 01:46 AM, Angus Lees wrote: Ok, thanks for the in-depth explanation. My take away is that we need to file any rootwrap updates as exceptions for now (so releasenotes and grenade scripts). That is definitely the fall back if there is no better idea. However, we should try really

[openstack-dev] [TripleO] TripleO deep dive hour?

We've got some new contributors around TripleO recently, and I'd like to offer up a "TripleO deep dive hour". The idea is to spend 1 hour a week in a high bandwidth environment (Google Hangouts / Bluejeans / ???) to deep dive on a TripleO related topic. The topic could be anything TripleO related,

Re: [openstack-dev] Troubleshooting and ask.openstack.org

-Original Message- From: Adam Young Reply: OpenStack Development Mailing List (not for usage questions) Date: June 28, 2016 at 16:47:26 To: OpenStack Development Mailing List Subject:  [openstack-dev] Troubleshooting and ask.openstack.org > Recently, the Keystone team started brainstorm

Re: [openstack-dev] [TripleO] TripleO deep dive hour?

+2, that would be great. On Wednesday, June 29, 2016, James Slagle wrote: > We've got some new contributors around TripleO recently, and I'd like > to offer up a "TripleO deep dive hour". > > The idea is to spend 1 hour a week in a high bandwidth environment > (Google Hangouts / Bluejeans / ???)

Re: [openstack-dev] Change in openstack/trove[master]: Ophaned Volume Not Removed on Instance Delete

Hi Will, Trove is a managed database service. Once you delete the database, all associated volumes with it are also deleted, as is the Nova instance. One of the key benefits of using Trove is that you don’t have to manage servers/volumes/security_groups etc. Also, depending on the provider’s

  1   2   >