[openstack-dev] [stable] freeze exception

Hello Folks, I'd like to request a freeze exception for the following changeset: https://review.openstack.org/169844 I believe that's an unharmful change, I apologize for getting it under review so late :) Ivar. __ OpenStac

Re: [openstack-dev] [TripleO][Heat] Overcloud software updates and ResourceGroups

Hi, On Fri, Apr 3, 2015 at 1:31 AM, Zane Bitter wrote: > A few of us have been looking for a way to perform software updates to > servers in a TripleO Heat/Puppet-based overcloud that avoids an impedance > mismatch with Heat concepts and how Heat runs its workflow. As many > talented TripleO-ers

[openstack-dev] [Nova][QA] Use case of Nova to boot VM from volume only

Hi, This is regarding bug - https://bugs.launchpad.net/tempest/+bug/1436314 When Nova is configured to boot VM from volume only, current Tempest integration tests will fails. We are not sure how feasible and valid this configuration is for Nova and what are the use cases of this. Before starting

Re: [openstack-dev] [TripleO][Heat] Overcloud software updates and ResourceGroups

hi there, thanks for sharing this, I have a On 04/03/2015 12:31 AM, Zane Bitter wrote: A few of us have been looking for a way to perform software updates to servers in a TripleO Heat/Puppet-based overcloud [...] Here's a trivial example of what this deployment might look like: update_c

[openstack-dev] [stable] Call for testing: 2014.2.3 candidate tarballs

Hi all, We are scheduled to publish 2014.2.3 on Thursday April 9th for Ceilometer, Cinder, Glance, Heat, Horizon, Keystone, Neutron, Nova, Sahara and Trove. We'd appreciate anyone who could test the candidate 2014.2.3 tarballs, which include all changes aside from any pending freeze exceptions:

Re: [openstack-dev] [TripleO][Heat] Overcloud software updates and ResourceGroups

I'm not sure how to feel about this... Its clever... It kind of feels like your really trying to be able to register 'actions' in heat so that heat users can poke the vm's to do something... For example "perform a chef run". While using stack updates listed below could be made to work, is that

Re: [openstack-dev] [Keystone] PTL Candidacy

On 2015-04-02 19:32:52 -0400 (-0400), Adam Young wrote: > Please vote for Morgan. Please refrain from distributing campaign literature, placing political advertising or soliciting votes within 25 meters of the polling place. ;) -- Jeremy Stanley __

Re: [openstack-dev] [all][oslo][clients] Let's speed up start of OpenStack libs and clients by optimizing imports with profimp

On 04/02/2015 06:22 PM, Brant Knudson wrote: > On Thu, Apr 2, 2015 at 4:52 PM, Boris Pavlovic wrote: > >> Hi stackers, >> >> Recently, I started working on speeding up Rally cli. >> >> What I understand immediately is that I don't understand why it takes >> 700-800ms >> to just run "rally versio

Re: [openstack-dev] [Keystone] PTL Candidacy

On 04/02/2015 04:31 PM, Morgan Fainberg wrote: Hello Everyone! It’s been an exciting development cycle (Kilo) and it is now time to start looking forward at Liberty and what that will hold. With that said, I’d like to ask for the community’s support to continue as the Keystone PTL for the Li

[openstack-dev] [TripleO][Heat] Overcloud software updates and ResourceGroups

A few of us have been looking for a way to perform software updates to servers in a TripleO Heat/Puppet-based overcloud that avoids an impedance mismatch with Heat concepts and how Heat runs its workflow. As many talented TripleO-ers who have gone before can probably testify, that's surprisingl

Re: [openstack-dev] [all][oslo][clients] Let's speed up start of OpenStack libs and clients by optimizing imports with profimp

On Thu, Apr 2, 2015 at 4:52 PM, Boris Pavlovic wrote: > Hi stackers, > > Recently, I started working on speeding up Rally cli. > > What I understand immediately is that I don't understand why it takes > 700-800ms > to just run "rally version" command and it is impossible hard task to find > what

[openstack-dev] [all][oslo][clients] Let's speed up start of OpenStack libs and clients by optimizing imports with profimp

Hi stackers, Recently, I started working on speeding up Rally cli. What I understand immediately is that I don't understand why it takes 700-800ms to just run "rally version" command and it is impossible hard task to find what takes so much time just by reading the code. I started playing with

Re: [openstack-dev] [openstack][Mistral] DSL improvements - certain and incubating

Team, thanks for your input so far, I flashed out one more section, please take a look and comment https://docs.google.com/a/stackstorm.com/document/d/1Gy6V9YBt8W4llyErO_itHetkF1oNYv4ka-_5LdFKA18/edit#heading=h.n1jc8i9qhikt DZ. On Mar 25, 2015, at 9:41 AM, Dmitri Zimine wrote: > Folks, > >

[openstack-dev] [Infra] PTL Candidacy

I would like to announce my candidacy for the Infrastructure PTL. I have developed and operated the project infrastructure for several years and have been honored to serve as the PTL for the Kilo cycle. I was instrumental not only in creating the project gating system and development process, but

Re: [openstack-dev] [cinder] Deadline For Volume Drivers to Be Readded

On 14:14 Thu 02 Apr , Marcus Vinícius Ramires do Nascimento wrote: > Hi Mike, > > I'm working on test coverage improvement for HDS/Hitachi drivers. As I > talked to you in #openstack-cinder channel, I'm facing troubles with 3 > tests (apparently those fails are not related to the driver) and I

Re: [openstack-dev] [OpenStack-Dev] [third-party-ci] Clarifications on the goal and skipping tests

On 00:21 Tue 31 Mar , Rochelle Grober wrote: > Top posting… I believe the main issue was a problem with snapshots that > caused false negatives for most cinder drivers. But, that got fixed. I don't know what you're talking about here. Are you saying there was an issue with the Tempest tests t

[openstack-dev] [Keystone] PTL Candidacy

Hello Everyone! It’s been an exciting development cycle (Kilo) and it is now time to start looking forward at Liberty and what that will hold. With that said, I’d like to ask for the community’s support to continue as the Keystone PTL for the Liberty release cycle. I came to the table last cy

[openstack-dev] [Ceilometer] PTL candidacy

hi, i'd like to announce my candidacy for PTL of Ceilometer. as a quick introduction, i've been a contributor in OpenStack for the past few years and for the majority of that time i've been primarily focused on Ceilometer where i contribute regularly to the project with code[1] and reviews[2]. i

Re: [openstack-dev] [Magnum] PTL Candidacy

confirmed On 04/02/2015 12:36 PM, Adrian Otto wrote: > I respectfully respect your support to continue as your Magnum PTL. > > Here are are my achievements and OpenStack experience and that make me the > best choice for this role: > > * Founder of the OpenStack Containers Team > * Established v

Re: [openstack-dev] [Cinder] PTL Candidacy

confirmed On 04/02/2015 02:46 PM, Mike Perez wrote: > Hello all, > > I'm announcing my candidacy for Cinder PTL for the Liberty release. > > I have contributed to block storage in OpenStack since Bexar back when things > were within nova-volume, before Cinder, and the honor of serving as PTL for

Re: [openstack-dev] The Evolution of core developer to maintainer?

Joe Gordon wrote: On Thu, Apr 2, 2015 at 3:14 AM, Thierry Carrez mailto:thie...@openstack.org>> wrote: Joe Gordon wrote: > > My main objection to the model you propose is its binary nature. You > > bundle "core reviewing" duties with "drivers" duties into a single

Re: [openstack-dev] The Evolution of core developer to maintainer?

On Thu, Apr 2, 2015 at 3:14 AM, Thierry Carrez wrote: > Joe Gordon wrote: > >> My main objection to the model you propose is its binary nature. You > >> bundle "core reviewing" duties with "drivers" duties into a single > >> group. That simplification means that drivers have to be cor

[openstack-dev] [TC][Mistral] Workflow Service project proposal

Hi respected TC members and community: We would like to propose Workflow Service project (code name Mistral), as a project in the OpenStack namespace, in accordance with the new governance changes [1]. The details are on the review: https://review.openstack.org/#/c/170225 Please review the pro

[openstack-dev] [Cinder] PTL Candidacy

Hello all, I'm announcing my candidacy for Cinder PTL for the Liberty release. I have contributed to block storage in OpenStack since Bexar back when things were within nova-volume, before Cinder, and the honor of serving as PTL for Cinder in the Kilo cycle. I've spoke in the past about focused

[openstack-dev] [release] taskflow 0.8.1

We are stoked to announce the *bug-fix* release of: taskflow 0.8.1: Taskflow structured state management library. For more details, please see the git log history below and: http://launchpad.net/taskflow/+milestone/0.8.1 Please report issues through launchpad: http://bugs.launchpad.ne

Re: [openstack-dev] [Magnum] Containers and networking

On 04/02/2015 01:45 PM, Kevin Benton wrote: > +1. I added a suggestion for a container networking suggestion to the > etherpad for neutron. It would be sad if the container solution built > yet another overlay on top of the Neutron networks with yet another > network management workflow. By the tim

Re: [openstack-dev] [Fuel] glusterfs plugin

Well this directory structure is not true for [1] and the suggestion about fpb was for such repos. P. https://github.com/stackforge/fuel-plugin-cinder-netapp On 04/02/2015 04:08 PM, Sergey Kulanov wrote: > I've just print tree with hidden files, so actually it's ok with fpb: > > root@55725ffa6e

Re: [openstack-dev] [Magnum] Containers and networking

Russell, On Apr 2, 2015, at 9:51 AM, Russell Bryant wrote: > On 04/02/2015 12:36 PM, Adrian Otto wrote: >> What to expect in the Liberty release cycle: >> > ... >> * Overlay networking > ... > > This is totally unrelated to your PTL email, but on this point, I'd be > curious what the Magnum t

Re: [openstack-dev] [Magnum] Containers and networking

On 4/2/15, 9:51 AM, "Russell Bryant" wrote: >On 04/02/2015 12:36 PM, Adrian Otto wrote: >> What to expect in the Liberty release cycle: >> >... >> * Overlay networking >... > >This is totally unrelated to your PTL email, but on this point, I'd be >curious what the Magnum team thinks of this pr

[openstack-dev] [Manila] Nominate Clinton Knight for core team

+1 -- Kind Regards Valeriy Ponomaryov www.mirantis.com vponomar...@mirantis.com __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http:/

Re: [openstack-dev] [OpenStack-Infra][cinder] Could you please re-consider Oracle ZFS/SA Cinder drivers (iSCSI and NFS)

Hi Ramy, Thank you for the insight. I have made the changes, Oracle ZFSSA CI should include testr results in html from now on. Diem. On 03/31/2015 05:39 PM, Asselin, Ramy wrote: Hi Diem, Looking at: https://review.openstack.org/#/q/reviewer:%22Oracle+ZFSSA+CI%22,n,z I don't see any issues

Re: [openstack-dev] [Magnum] Containers and networking

+1. I added a suggestion for a container networking suggestion to the etherpad for neutron. It would be sad if the container solution built yet another overlay on top of the Neutron networks with yet another network management workflow. By the time the packets are traveling across the wires, it wou

Re: [openstack-dev] The Evolution of core developer to maintainer?

> On Apr 2, 2015, at 9:02 AM, Thierry Carrez wrote: > > Maru Newby wrote: >>> On Apr 2, 2015, at 3:26 AM, Thierry Carrez wrote: >>> What we need to do instead is reviving the "drivers" concept (we can >>> rename it "maintainers" if you really like that term), separate from the >>> "core reviewe

Re: [openstack-dev] The Evolution of core developer to maintainer?

> On Apr 1, 2015, at 7:19 PM, Jay Pipes wrote: > > On 04/01/2015 12:31 PM, Duncan Thomas wrote: >> On 1 April 2015 at 10:04, Joshua Harlow > > wrote: >> >>+1 to this. There will always be people who will want to work on fun >>stuff and those who don't; it's

Re: [openstack-dev] [tc] Request to adopt security as a project team

Borrowing Jeremy's VMT hat... Yes please! /me hands hat back, and didn't actually wear it. In seriousness, this should happen! Sent via mobile > On Apr 2, 2015, at 09:32, Jeremy Stanley wrote: > >> On 2015-04-02 15:56:31 + (+), Clark, Robert Graham wrote: >> Please consider this requ

Re: [openstack-dev] [cinder] Deadline For Volume Drivers to Be Readded

Hi Mike, I'm working on test coverage improvement for HDS/Hitachi drivers. As I talked to you in #openstack-cinder channel, I'm facing troubles with 3 tests (apparently those fails are not related to the driver) and I'm trying to discover if it's a bug to report it or if it's a infrastructure/conf

Re: [openstack-dev] The Evolution of core developer to maintainer?

Jay Pipes wrote: On 04/01/2015 12:31 PM, Duncan Thomas wrote: On 1 April 2015 at 10:04, Joshua Harlow mailto:harlo...@outlook.com>> wrote: +1 to this. There will always be people who will want to work on fun stuff and those who don't; it's the job of leadership in the community to direct people

Re: [openstack-dev] [Magnum] Containers and networking

On 04/02/2015 12:36 PM, Adrian Otto wrote: > What to expect in the Liberty release cycle: > ... > * Overlay networking ... This is totally unrelated to your PTL email, but on this point, I'd be curious what the Magnum team thinks of this proposal: http://openvswitch.org/pipermail/dev/2015-March

[openstack-dev] [Magnum] PTL Candidacy

I respectfully respect your support to continue as your Magnum PTL. Here are are my achievements and OpenStack experience and that make me the best choice for this role: * Founder of the OpenStack Containers Team * Established vision and specification for Magnum * Served as PTL for Magnum since

Re: [openstack-dev] [tc] Request to adopt security as a project team

On 2015-04-02 15:56:31 + (+), Clark, Robert Graham wrote: > Please consider this request to recognize the security team as an > OpenStack project team. > > This is a milestone for the OpenStack Security Group and follows > from our merging with the VMT. [...] With my VMT hat donned, I sec

Re: [openstack-dev] [Heat] [Ceilometer] [depfreeze] bug is unresolved due to requirements freeze

Hi all, my previous update was a bit too hasty indeed - the problem is still there. Steps I took: in two empty virtualenvs I installed cilometerclient 1.0.12 and 1.0.13 and compared "pip freeze" outputs - everything is the same except the ceilometerclient itself. Then I re-installed my DevStack

Re: [openstack-dev] [tc] Request to adopt security as a project team

On 04/02/2015 11:56 AM, Clark, Robert Graham wrote: Technical Committee, Please consider this request to recognize the security team as an OpenStack project team. This is a milestone for the OpenStack Security Group and follows from our merging with the VMT. Over the last few years what started

Re: [openstack-dev] The Evolution of core developer to maintainer?

Maru Newby wrote: >> On Apr 2, 2015, at 3:26 AM, Thierry Carrez wrote: >> What we need to do instead is reviving the "drivers" concept (we can >> rename it "maintainers" if you really like that term), separate from the >> "core reviewers" concept. One can be a project "driver" and a "core >> revie

[openstack-dev] [tc] Request to adopt security as a project team

Technical Committee, Please consider this request to recognize the security team as an OpenStack project team. This is a milestone for the OpenStack Security Group and follows from our merging with the VMT. Over the last few years what started as a small working group has become a team of dedicat

[openstack-dev] [openstack clients] Client bash_completion script discovery

Hello all, Most OS python-xxxclient projects include a tools/xxx.bash_completion file, that is invaluable for working with said clients. Correct me if I’m wrong, but as far as I see the script is not packaged with any of the python packages on the pypi. If the end user wants to install client w

Re: [openstack-dev] [Manila] Nominate Clinton Knight for core team

+1 > On Apr 2, 2015, at 9:21 AM, "Ben Swartzlander" wrote: > > Clinton Knight (cknight on IRC) has been working on OpenStack for the better > part of the year, and starting in February, he shifted his focus from Cinder > to Manila. I think everyone is already aware of his high quality > co

Re: [openstack-dev] [tripleo][puppet] Running custom puppet manifests during overcloud post-deployment

- Original Message - > On Thu, Apr 02, 2015 at 10:34:29AM -0400, Dan Prince wrote: > > On Wed, 2015-04-01 at 21:31 -0400, Tzu-Mainn Chen wrote: > > > Hey all, > > > > > > I've run into a requirement where it'd be useful if, as an end user, I > > > could inject > > > a personal ssh key on

Re: [openstack-dev] [neutron] PTL Candidacy

confirmed On 04/02/2015 10:16 AM, Kyle Mestery wrote: > Hi everyone: > > I'd like to announce my candidacy for another term as the Neutron PTL. I'm > the current Neutron PTL, having been the Neutron PTL for the past two > cycles (Juno and Kilo). I'd like a chance to lead the Neutron team for > an

Re: [openstack-dev] [Glance] PTL Candidacy

confirmed On 04/02/2015 10:53 AM, Flavio Percoco wrote: > Greetings, > > I'd like to put my name out there for the Glance PTL position. > > Few words about me: > > I'm Flavio Percoco (flaper87 on IRC and everywhere). I've been an > OpenStack fellow for the last 2 1/2 years. During this time I'v

Re: [openstack-dev] [Nova] PTL Candidacy

confirmed On 04/02/2015 02:20 AM, Michael Still wrote: > I'd like another term as Nova PTL, if you'll have me. > > I feel Kilo has gone reasonably well for Nova -- our experiment with > priorities has meant that we’ve got a lot of important work done. We > have progressed well with cells v2, our

[openstack-dev] [all] Liberty Design Summit planning

Hello everyone, It's that time of the year again... In less than 7 weeks a lot of us will meet in Vancouver for 4 days of Design Summit craziness. The space we'll be in is pretty awesome, I'm sure you will all like it. Like every design summit, we introduced a number of changes, which I already m

Re: [openstack-dev] [nova][libvirt] Block migrations and Cinder volumes

>> Thanks for the clarification, is there a bug tracking this in libvirt >> already? > Actually I don't think there is one, so feel free to file one I took the liberty of doing so: https://bugzilla.redhat.com/show_bug.cgi?id=1208588 On Wed, Mar 18, 2015 at 6:11 PM, Daniel P. Berrange wrote: >

Re: [openstack-dev] The Evolution of core developer to maintainer?

> On Apr 2, 2015, at 3:26 AM, Thierry Carrez wrote: > > Maru Newby wrote: >> [...] Many of us in the Neutron >> community find this taxonomy restrictive and not representative >> of all the work that makes the project possible. > > We seem to be after the same end goal. I just disagree that ren

Re: [openstack-dev] [nova] [scheduler] [gantt] Please stop using "Gantt" for discussing about Nova scheduler

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 04/02/2015 03:10 AM, Sylvain Bauza wrote: > As a meeting is by definition a synchronous thing, should we maybe > try to async that decision using Gerrit ? I could pop up a > resolution in Gerrit so that people could -1 or +1 it. To me, 'Gantt' r

[openstack-dev] [nova] ‘az:force_host:force_node’ validation when booting instance

hi, nova guys: now I am working on this bug[1], and this is my patch[2], but met some problems, so have to bring it here to get suggestions from broader community. In short, the problem is about validation on the ‘az:force_host:force_node’ parameter when booting instance. As we all know that, use

Re: [openstack-dev] [cinder] Deadline For Volume Drivers to Be Readded

We believe we have satisfied the required criteria [1] to have NetApp’s fibre channel drivers included in the Kilo release. We have submitted a revert patch [2] along with posting an ether pad [3] to provide more detail on our progress. Thanks for your consideration. [1] http://lists.openstack.org

Re: [openstack-dev] The Evolution of core developer to maintainer?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 04/02/2015 03:22 AM, Sylvain Bauza wrote: > I was originally pro giving a limited set of merge powers to > subteams for a specific codepath, but my personal experience made > me think that it can't work that way in Nova at the moment - just > bec

Re: [openstack-dev] [Manila] Nominate Clinton Knight for core team

On 4/2/15 9:16 AM, Ben Swartzlander wrote: > Clinton Knight (cknight on IRC) has been working on OpenStack for the > better part of the year, and starting in February, he shifted his focus > from Cinder to Manila. I think everyone is already aware of his high > quality contributions and code review

[openstack-dev] [Glance] PTL Candidacy

Greetings, I'd like to put my name out there for the Glance PTL position. Few words about me: I'm Flavio Percoco (flaper87 on IRC and everywhere). I've been an OpenStack fellow for the last 2 1/2 years. During this time I've spread my efforts on several projects but mainly on Glance, from which

Re: [openstack-dev] [tripleo][puppet] Running custom puppet manifests during overcloud post-deployment

On Thu, Apr 02, 2015 at 10:34:29AM -0400, Dan Prince wrote: > On Wed, 2015-04-01 at 21:31 -0400, Tzu-Mainn Chen wrote: > > Hey all, > > > > I've run into a requirement where it'd be useful if, as an end user, I > > could inject > > a personal ssh key onto all provisioned overcloud nodes. > > > >

Re: [openstack-dev] [Manila] Nominate Clinton Knight for core team

+1 On Thu, Apr 2, 2015 at 10:30 AM, Thomas Bechtold wrote: > On 02.04.2015 15:16, Ben Swartzlander wrote: > > Clinton Knight (cknight on IRC) has been working on OpenStack for the > > better part of the year, and starting in February, he shifted his focus > > from Cinder to Manila. I think every

Re: [openstack-dev] [tripleo][puppet] Running custom puppet manifests during overcloud post-deployment

On Wed, 2015-04-01 at 21:31 -0400, Tzu-Mainn Chen wrote: > Hey all, > > I've run into a requirement where it'd be useful if, as an end user, I could > inject > a personal ssh key onto all provisioned overcloud nodes. > > Obviously this is something that not every user would need or want. I talk

Re: [openstack-dev] [Manila] Nominate Clinton Knight for core team

On 02.04.2015 15:16, Ben Swartzlander wrote: > Clinton Knight (cknight on IRC) has been working on OpenStack for the > better part of the year, and starting in February, he shifted his focus > from Cinder to Manila. I think everyone is already aware of his high > quality contributions and code revi

Re: [openstack-dev] [nova] unit tests result in false negatives on system z platform CI

On 4/2/2015 2:37 AM, Markus Zoeller wrote: Michael Still wrote on 04/01/2015 11:01:51 PM: From: Michael Still To: "OpenStack Development Mailing List (not for usage questions)" Date: 04/01/2015 11:06 PM Subject: Re: [openstack-dev] [nova] unit tests result in false negatives on system z pl

[openstack-dev] [ceilometer] Stepping down as PTL

Hi Folks, Just a quick note to say that I won't be running again for ceilometer PTL over the liberty cycle. I've taken on a new role internally that won't realistically allow me the time that the PTL role deserves. But y'all haven't seen the last of me, I'll be sticking around as a contributor,

Re: [openstack-dev] [cinder] Issue for backup speed

Just curious. What is the overhead of compression and other backup processes? How much time does it take to upload a simple 50GB file to swift compare to backup of 50 GB to swift? From: Duncan Thomas [mailto:duncan.tho...@gmail.com] Sent: Wednesday, April 01, 2015 6:13 AM To: OpenStack Developm

[openstack-dev] [neutron] PTL Candidacy

Hi everyone: I'd like to announce my candidacy for another term as the Neutron PTL. I'm the current Neutron PTL, having been the Neutron PTL for the past two cycles (Juno and Kilo). I'd like a chance to lead the Neutron team for another cycle of development. During the Kilo cycle, we worked hard

Re: [openstack-dev] [Fuel] glusterfs plugin

I've just print tree with hidden files, so actually it's ok with fpb: root@55725ffa6e80:~# tree -a test/ test/ |-- .gitignore |-- LICENSE |-- README.md |-- deployment_scripts | `-- deploy.sh |-- environment_config.yaml |-- metadata.yaml |-- pre_build_hook *|-- repositories| |-- centos|

Re: [openstack-dev] [Fuel] glusterfs plugin

Well then either we need to fix fuel-plugin-builder to accept such situations. Actually it is an issue with fpb since git does not accepty empty directories [1] so pulling fresh from such repo will result in 'repositories' dir missing even when the developer had it. I hope no files were accidenta

Re: [openstack-dev] [all][oslo] oslo.log hacking rules

I created issue in Launchpad: https://bugs.launchpad.net/hacking/+bug/1439709 Regards, Ivan Kolodyazhny, Software Engineer, Mirantis Inc. On Wed, Apr 1, 2015 at 1:38 PM, Ihar Hrachyshka wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > On 03/31/2015 09:19 PM, Ivan Kolodyazhny wrote:

Re: [openstack-dev] [Heat][Horizon] What we can do for Heat in Horizon else?

+1. I have to copy/paste in nested stack uuids all the time. :/ Thanks, Kevin From: Pavlo Shchelokovskyy Sent: Thursday, April 02, 2015 3:05:14 AM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [Heat][Horizon] What we

Re: [openstack-dev] [Fuel] glusterfs plugin

Hi, Przemyslaw 1) There should be two repositories folders. Please check the correct structure (marked with bold): mkdir -p repositories/{ubuntu,centos} root@55725ffa6e80:~/fuel-plugin-cinder-netapp# tree . |-- LICENSE |-- README.md |-- cinder_netapp-1.0.0.fp |-- deployment_scripts | |-- puppe

Re: [openstack-dev] [Nova] PTL Candidacy

On 02/04/15 07:20, Michael Still wrote: > I'd like another term as Nova PTL, if you'll have me. > ... > > I think its a good idea also to examine briefly some statistics about specs: > > Juno: >approved but not implemented: 40 >implemented: 49 > > Kilo: >approved but not implement

Re: [openstack-dev] [Fuel] glusterfs plugin

Investigating the cinder-netapp plugin [1] (a 'certified' one) shows fuel-plugin-build error: (fuel)vagrant@ubuntu-14:/sources/fuel-plugin-cinder-netapp$ fpb --build . Unexpected error Cannot find directories ./repositories/ubuntu for release "{'repository_path': 'repositories/ubuntu', 'version'

[openstack-dev] [Manila] Nominate Clinton Knight for core team

Clinton Knight (cknight on IRC) has been working on OpenStack for the better part of the year, and starting in February, he shifted his focus from Cinder to Manila. I think everyone is already aware of his high quality contributions and code reviews. I would like to nominate him to join the Man

Re: [openstack-dev] [Heat] [Ceilometer] [depfreeze] bug is unresolved due to requirements freeze

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 04/02/2015 01:58 PM, Eoghan Glynn wrote: > >> Pavlo Shchelokovskyy wrote: >>> unfortunately, in Heat we do not have yet integration tests for >>> all the Heat resources (creating them in real OpenStack), and >>> Ceilometer alarms are in those not c

Re: [openstack-dev] [Fuel] glusterfs plugin

Hello, Done, added you. I already created something that should fix the tests for glusterfs: [1] Also the fuel-qa is not entirely correct for testing the glusterfs plugin: here's the proposed fix [2]. Unfortunately the tests still fail with this message: [3] I had an error about GLUSTER_CLUSTE

[openstack-dev] What's Up Doc? Apr 2 2015

_ Doc team meeting APAC/Pacific edition _ Thanks to Joseph Robinson for running the APAC doc team meeting this week. You can get logs and minutes: Minutes: http://eavesdrop.openstack.org/meetings/docteam/2015/docteam.2015-04-01-01.01.html Log: http://eavesdrop.openstack.org/meetings/docteam/2015

Re: [openstack-dev] [Heat] [Ceilometer] [depfreeze] bug is unresolved due to requirements freeze

> Pavlo Shchelokovskyy wrote: > > unfortunately, in Heat we do not have yet integration tests for all the > > Heat resources (creating them in real OpenStack), and Ceilometer alarms > > are in those not covered. In unit tests the real client is of course > > mocked out. When we stumbled on this is

[openstack-dev] Announcement - "The Security Team" for OpenStack

The OpenStack Security Group (OSSG) and the OpenStack Vulnerability Management Team (VMT) have historically operated as independent teams, each with a focus on different aspects of OpenStack security. To present a more coherent security posture we are pleased to announce that the OSSG and VMT will

Re: [openstack-dev] The Evolution of core developer to maintainer?

On 02/04/15 12:26 +0200, Thierry Carrez wrote: Maru Newby wrote: [...] Many of us in the Neutron community find this taxonomy restrictive and not representative of all the work that makes the project possible. We seem to be after the same end goal. I just disagree that renaming "core reviewers

[openstack-dev] [Elections] Nominations for OpenStack PTLs (Program Technical Leads) are now open

Nominations for OpenStack PTLs (Program Technical Leads) are now open and will remain open until April 9, 2015 05:59 UTC. To announce your candidacy please start a new openstack-dev at lists.openstack.org mailing list thread with the program name as a tag, example [Glance] PTL Candidacy with the b

Re: [openstack-dev] [Heat] [Ceilometer] [depfreeze] bug is unresolved due to requirements freeze

Pavlo Shchelokovskyy wrote: > unfortunately, in Heat we do not have yet integration tests for all the > Heat resources (creating them in real OpenStack), and Ceilometer alarms > are in those not covered. In unit tests the real client is of course > mocked out. When we stumbled on this issue during

Re: [openstack-dev] [Heat] [Ceilometer] [rc1] bug is unresolved due to requirements freeze

Hi all, a (may be hasty) update. I just tried using a quite fresh devstack master that somehow still (PIP_UPGRADE=False?) has ceilometerclient as 1.0.12, and ceilometer alarms do work as expected, template is [1]. May be the actual bug/backward incompatibility was somewhere in oslo-incubator and

Re: [openstack-dev] Reducing noise of the ML

On 02/04/15 06:19 -0400, Sean Dague wrote: On 04/02/2015 05:37 AM, Thierry Carrez wrote: Michael Still wrote: Actually, for some projects the +1 is part of a public voting process and therefore required. Could that "public voting process" happen somewhere else ? Like at an IRC meeting ? For

Re: [openstack-dev] [nova] bug expiration

On Thu, 2015-04-02 at 07:03 -0400, Sean Dague wrote: > On 04/02/2015 06:54 AM, James Bottomley wrote: > > On Thu, 2015-04-02 at 06:45 -0400, Sean Dague wrote: > >> On 04/02/2015 06:33 AM, James Bottomley wrote: > >>> On Thu, 2015-04-02 at 11:32 +0200, Thierry Carrez wrote: > Sean Dague wrote:

Re: [openstack-dev] [nova] bug expiration

On 04/02/2015 06:54 AM, James Bottomley wrote: > On Thu, 2015-04-02 at 06:45 -0400, Sean Dague wrote: >> On 04/02/2015 06:33 AM, James Bottomley wrote: >>> On Thu, 2015-04-02 at 11:32 +0200, Thierry Carrez wrote: Sean Dague wrote: > I just spent a chunk of the morning purging out some real

Re: [openstack-dev] [nova] bug expiration

On Thu, 2015-04-02 at 06:45 -0400, Sean Dague wrote: > On 04/02/2015 06:33 AM, James Bottomley wrote: > > On Thu, 2015-04-02 at 11:32 +0200, Thierry Carrez wrote: > >> Sean Dague wrote: > >>> I just spent a chunk of the morning purging out some really old > >>> Incomplete bugs because about 9 month

Re: [openstack-dev] [Heat] [Ceilometer] [rc1] bug is unresolved due to requirements freeze

Sean, unfortunately, in Heat we do not have yet integration tests for all the Heat resources (creating them in real OpenStack), and Ceilometer alarms are in those not covered. In unit tests the real client is of course mocked out. When we stumbled on this issue during normal Heat usage, we promptl

Re: [openstack-dev] [Heat] [Ceilometer] [rc1] bug is unresolved due to requirements freeze

Hi Guys. > A couple of concerns: > > #1 - would have been really nice if the commit message for the review > included the above block of text. The current commit message is not > clear that Heat *can not* work. > I will update commit message regarding info mentioned in this thread. > > #2 - wh

Re: [openstack-dev] [nova] bug expiration

On 04/02/2015 06:33 AM, James Bottomley wrote: > On Thu, 2015-04-02 at 11:32 +0200, Thierry Carrez wrote: >> Sean Dague wrote: >>> I just spent a chunk of the morning purging out some really old >>> Incomplete bugs because about 9 months ago we disabled the auto >>> expiration bit in launchpad - >>

Re: [openstack-dev] [nova] bug expiration

On Thu, 2015-04-02 at 11:32 +0200, Thierry Carrez wrote: > Sean Dague wrote: > > I just spent a chunk of the morning purging out some really old > > Incomplete bugs because about 9 months ago we disabled the auto > > expiration bit in launchpad - > > https://bugs.launchpad.net/nova/+configure-bugtr

Re: [openstack-dev] [nova] [scheduler] [gantt] Please stop using "Gantt" for discussing about Nova scheduler

Gantt is a dead and abandoned source tree, it also means nothing to new people joining into helping with the nova scheduler. It keeps generating confusion. Gantt is dead, the current effort is nova-scheduler improvement. Please just call it that. -Sean On 04/02/2015 04:10 AM, Sylvain Bau

Re: [openstack-dev] The Evolution of core developer to maintainer?

Maru Newby wrote: > [...] Many of us in the Neutron > community find this taxonomy restrictive and not representative > of all the work that makes the project possible. We seem to be after the same end goal. I just disagree that renaming "core reviewers" to "maintainers" is a positive step toward

Re: [openstack-dev] Reducing noise of the ML

On 04/02/2015 05:37 AM, Thierry Carrez wrote: > Michael Still wrote: >> Actually, for some projects the +1 is part of a public voting process >> and therefore required. > > Could that "public voting process" happen somewhere else ? Like at an > IRC meeting ? For global teams there is no IRC meeti

Re: [openstack-dev] The Evolution of core developer to maintainer?

Joe Gordon wrote: >> My main objection to the model you propose is its binary nature. You >> bundle "core reviewing" duties with "drivers" duties into a single >> group. That simplification means that drivers have to be core reviewers, >> and that core reviewers have to be drivers.

Re: [openstack-dev] [Heat] [Ceilometer] [rc1] bug is unresolved due to requirements freeze

On 04/02/2015 05:42 AM, Eoghan Glynn wrote: > > >> Hi all, >> >> we have a problem with dependencies for the kilo-rc1 release of Heat - see >> bug [1]. Root cause is ceilometerclient was not updated for a long time and >> just got an update recently. We are sure that Heat in Kilo would not work >

Re: [openstack-dev] [Fuel] glusterfs plugin

Hi Przemyslaw, I would be glad to be core reviewer to fuel-plugin-glusterfs as long as seems than I was only one person who push some commits to it. On Thu, Apr 2, 2015 at 10:47 AM, Przemyslaw Kaminski wrote: > Since there is no reply here I have taken steps to become core reviewer > of the (orp

Re: [openstack-dev] [Heat][Horizon] What we can do for Heat in Horizon else?

Hi folks, there is another not covered feature that jumps at me: say you have a stack containing an autoscaling group (a nested stack) where the scaled resource is also a nested stack. I can click on the uuid of the asg to get a page similar to other stacks showing me the structure of the nested

[openstack-dev] 答复: [heat] Application level HA via Heat

If we replace a autoscaling group member, we can't make sure the attached resources keep the same, why not to call the evacuate or rebuild api of nova, just to add meters for ha(vm state or host state) in ceilometer, and then signal to HA resource(such as HARestarter)? -邮件原件- 发件人: Steven

  1   2   >