Re: [openstack-dev] [openstack-ansible][security] Creating a CA for openstack-ansible deployments?

On 29/10/2015 21:43, "Major Hayden" wrote: >On 10/29/2015 04:33 AM, McPeak, Travis wrote: >> The only potential security drawback is that we are introducing a new >> asset to protect. If we create the tools that enable a deployer to >> easily create and administer a

Re: [openstack-dev] [openstack-ansible][security] Creating a CA for openstack-ansible deployments?

On 10/29/2015 04:33 AM, McPeak, Travis wrote: > The only potential security drawback is that we are introducing a new > asset to protect. If we create the tools that enable a deployer to > easily create and administer a lightweight CA, that should add > significant value to OpenStack, especially

Re: [openstack-dev] [cinder][nova] gate-cinder-python34 failing test_nova_timeout after novaclient 2.33 release

On 10/29/2015 5:55 AM, Andrey Kurilin wrote: >But it was released with 2961e82 which was the backward incompatible requests exception change, which we now have a fix for that we want to release, but would include 0cd5812. I suppose we need to revert 0cd5812 change too, cut new release and

Re: [openstack-dev] [magnum][kolla] Stepping down as a Magnum core reviewer

Hi Steve, It is really a big loss to Magnum and thanks very much for your help in my Magnum journey. Wish you good luck in Kolla! On Tue, Oct 27, 2015 at 2:29 PM, 大塚元央 wrote: > Hi Steve, > > I'm very sad about your stepping down from Magnum core. Without your help, > I

[openstack-dev] [Fuel][puppet] CI gate for regressions detection in deployment data

Hello. There are few types of a deployment regressions possible. When changing a module version to be used from upstream (or internal module repo), for example from Liberty to Mitaka. Or when changing the composition layer (modular tasks in Fuel). Specifically, adding/removing/changing classes and

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

On 29.10.2015 15:24, Bogdan Dobrelya wrote: > Hello. > There are few types of a deployment regressions possible. When changing > a module version to be used from upstream (or internal module repo), for > example from Liberty to Mitaka. Or when changing the composition layer > (modular tasks in

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

Bogdan, I don't want to maintain catalog resources 10 (or 20) times. It's an incredible amount of work to upkeep. There has to be a better way to ensure we don't lose some things. The approach I had in mind would have covered these cases: 1 - track all hiera lookups and make sure we catch

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

Hi everyone, I'm interested in starting up a puppet module that will handle the Magnum containers project. Would this be something the community might want? Thanks! Best, Nate Potter __ OpenStack Development Mailing List

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

inking on should we check the data state for *all* classes and >> defines of each deployment task, or should we do this only for some of >> the classes. The latter one would drastically decrease the amount of >> auto-generated data templates. But the former one would allo

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

Hi Adrian, Basically it would fall under the same umbrella as all of the other puppet-openstack projects, which use puppet automation to configure as well as manage various OpenStack projects. An example of a mature one is here for the Cinder project:

[openstack-dev] Performance Team summit session results

Hey folks! On Tuesday we had great summit session about performance team kick-off and yesterday it was a great LDT session as well and I’m really glad to see how much does the OpenStack performance topic is important for all of us. 40 minutes session surely was not enough to analyse everyone’s

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

On 10/29/2015 11:26 PM, Potter, Nathaniel wrote: > Hi everyone, > > > > I’m interested in starting up a puppet module that will handle the > Magnum containers project. Would this be something the community might > want? Thanks! If this module is about deploying Magnum service(s) and

Re: [openstack-dev] Performance Team summit session results

On 10/29/2015 9:30 AM, Dina Belova wrote: Hey folks! On Tuesday we had great summit session about performance team kick-off and yesterday it was a great LDT session as well and I’m really glad to see how much does the OpenStack performance topic is important for all of us. 40 minutes session

[openstack-dev] [Rally][Meeting][Agenda]

Hi, its a friendly reminder that if you what to discuss some topics at Rally meetings, please add you topic to our Meeting agenda https://wiki.openstack.org/wiki/Meetings/Rally#Agenda. Don't forget to specify who will lead topic discussion. Add some information about topic(links, etc.) Thank you

Re: [openstack-dev] [Fuel] network_checker code freeze

Dear colleagues, We still can not say that network-checker is a separate project now. I'm still working on related issues. Current status is Network-checker - Launchpad bug https://bugs.launchpad.net/fuel/+bug/1506896 - project-config patch https://review.openstack.org/235822 (DONE) -

Re: [openstack-dev] What's up with functional testing?

On 10/27/2015 9:55 PM, Emilien Macchi wrote: As a user[1], I would like to functionally test OpenStack services. I'm using Tempest (which is AFIK [2] the official OpenStack project for functional testing) and am able to validate that Puppet OpenStack module actually deploy services & make

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

Why do you use [puppet] tag? Is there anything related to Puppet OpenStack modules we should take care of? Good luck, On 10/29/2015 11:24 PM, Bogdan Dobrelya wrote: > Hello. > There are few types of a deployment regressions possible. When changing > a module version to be used from upstream (or

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

Nate, On Oct 29, 2015, at 11:26 PM, Potter, Nathaniel > wrote: Hi everyone, I’m interested in starting up a puppet module that will handle the Magnum containers project. Would this be something the community might want? Thanks!

[openstack-dev] [Fuel] Bugs status

Here is our current stats. Overall situation looks ok. We have manageable number of high priority bugs. Number of medium bugs is going down. It doesn't look like we will fix all medium bugs by end of release but it seems to be acceptable. High priority technical debt is under control. Features

Re: [openstack-dev] Performance Team summit session results

On 10/29/2015 10:55 AM, Matt Riedemann wrote: On 10/29/2015 9:30 AM, Dina Belova wrote: Hey folks! On Tuesday we had great summit session about performance team kick-off and yesterday it was a great LDT session as well and I’m really glad to see how much does the OpenStack performance

Re: [openstack-dev] [Infra][Nova][Neutron] 6WIND Networking CI - approval for posting comments

On 10/29/2015 12:13 PM, Francesco Santoro wrote: Dear Infra team, According to the requirements specified in [1] posting comments on patches needs approval from core maintainers of projects. Here at 6WIND we deployed and successfully tested [2] (using ci-sandbox project) our third party CI

[openstack-dev] [Infra][Nova][Neutron] 6WIND Networking CI - approval for posting comments

Dear Infra team, According to the requirements specified in [1] posting comments on patches needs approval from core maintainers of projects. Here at 6WIND we deployed and successfully tested [2] (using ci-sandbox project) our third party CI system [4] following all the steps defined in [1]. We

[openstack-dev] [swift] re-implementation in golang - hummingbird details

Hi All, I was reading about the "hummingbird" re-implementation of some parts of swift in golang, can someone kindly point to documentation/blogs on the changes made, where I can understand the new implementation before going into the code. ​Thanks, Rahul U Nair

[openstack-dev] Neutron sub-project release association with Liberty?

Hi, Once the Neutron's sub-project is released to pyPI, where does it show that this sub-project release is associated with Liberty release of Openstack?.. I tried to see it in the Liberty Release notes, but it doesn't have any info about the supported/released vendor plug-ins/drivers. I see the

Re: [openstack-dev] [nova] Change from Mitaka: Expected UNIX signal to generate Guru Meditation (error) Reports

On 10/21/2015 7:43 AM, Kashyap Chamarthy wrote: Background -- Oslo Guru Meditation (error) Reports (GMR)[*] are a useful debugging mechanism that allows one to capture the current state of a Nova process/executable (e.g. `nova-compute`, `nova-api`, etc). The way to generate the error

Re: [openstack-dev] Openstack disaster recover with CloudFerry, other tools?

Hi Jonathan, We are using Freezer for backup restore and disaster recovery (http://wiki.openstack.org/wiki/Freezer). It gives us flexibility as multiple storage media are supported (swift, ssh, local fs). So for example you may want to use ssh, to recover in case keystone or swift are not

[openstack-dev] [Neutron] Routed Networks meetup in Tokyo

Sorry for the late notice. I fell asleep yesterday before sending this out. I'd like to get together at the afternoon session of the Neutron contributors meetup today to discuss the next steps for addressing operators' routed networks use case during the Mitaka cycle. If you are interested in

Re: [openstack-dev] [nova] Change from Mitaka: Expected UNIX signal to generate Guru Meditation (error) Reports

Matt, Yes, Sean already opened a critical bug - https://bugs.launchpad.net/oslo.reports/+bug/1510740 Please note that this change was added to oslo.reports *after* the liberty release in support of Mitaka. So i am not sure why we need to add it to liberty release notes. Also this is a

Re: [openstack-dev] [nova] Change from Mitaka: Expected UNIX signal to generate Guru Meditation (error) Reports

Right, the crux of the problem is the move by the library from SIGUSR1 -> SIGUSR2 with no overlap and deprecation period breaks the ability to have any tooling use this without atomically updating that tooling, and this library, in all environments, all at the same time. We need the SIGUSR1

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

Good point, replaced the tag with fuel-library. On Oct 30, 2015 12:53 AM, "Emilien Macchi" wrote: > Why do you use [puppet] tag? > Is there anything related to Puppet OpenStack modules we should take > care of? > > Good luck, > > On 10/29/2015 11:24 PM, Bogdan Dobrelya

[openstack-dev] [Neutron] IRC weekly meeting

A reminder that we won't have the meeting next week. Safe journey back from Tokyo, for who has travelled to the Summit. Cheers, Armadno __ OpenStack Development Mailing List (not for usage questions) Unsubscribe:

Re: [openstack-dev] [Infra][Nova][Neutron] 6WIND Networking CI - approval for posting comments

On 30 October 2015 at 02:49, Matt Riedemann wrote: > > > On 10/29/2015 12:13 PM, Francesco Santoro wrote: > >> Dear Infra team, >> >> According to the requirements specified in [1] posting comments on >> patches needs approval from core maintainers of projects. >> >>

Re: [openstack-dev] [Heat] userdata empty when using software deployment/config in Kilo

On 29/10/15 06:12, Gabe Black wrote: Using my own template or the example template: https://github.com/openstack/heat-templates/blob/master/hot/software-config/example-templates/example-deploy-sequence.yaml results in the VM's /var/lib/cloud/instance/script/userdata being empty. The only

[openstack-dev] [Cinder] Sessions on openstack-cinder YouTube channel

Hey everyone, We recently created a YouTube channel for Cinder related activity. We are hoping to use this to build up a library of recordings over time. https://www.youtube.com/channel/UCJ8Koy4gsISMy0qW3CWZmaQ Starting with this Summit, Walt Boring has done a lot of work making sure each

[openstack-dev] [watcher] meetup on friday 10am in Prince room Tokyo Design Summit

Hi, We will have a contributors meetup on Watcher at 10am tomorrow in Prince room. Thanks, Antoine __ OpenStack Development Mailing List (not for usage questions) Unsubscribe:

Re: [openstack-dev] [puppet][keystone] Choose domain names with 'composite namevar' or 'meaningless name'?

On 16/10/15 00:14, Emilien Macchi wrote: > This thread is really huge and only 3 people are talking. > Why don't you continue on an etherpad and do some brainstorm on it? > If you do so, please share the link here. > > It would be much more effective in my opinion. I think we're almost there

Re: [openstack-dev] [Neutron] Neutron Social Meetup in Tokyo

Although the restaurant is announced, the place is hard to go for us. I and Akihiro will take you to the place. Please gather in registration hall at 6:30. Don’t mind about RSVP. You can come freely. IMPORTANT THING: Don’t leave your wallet. We don’t have sponsor ;) > On 2015/10/27, at 15:07,

Re: [openstack-dev] [openstack-ansible][security] Creating a CA for openstack-ansible deployments?

This does seem to make a lot of sense. Basically what we will get is an improved lowest common denominator when it comes to intra-node TLS. This probably also fits in nicely with work others in OpenStack Security have recently discussed regarding the creation of a super-lightweight CA. The only

Re: [openstack-dev] [Fuel] [Puppet] Potential critical issue, due Puppet mix stderr and stdout while execute commands

On 10/23/2015 02:17 PM, Dmitry Ilyin wrote: Here is the implementation of the puppet "command" that outputs only stdout and drops the stderr unless an error have happened. https://github.com/dmitryilyin/puppet-neutron/commit/b55f36a8da62fc207a91b358c396c03c8c58981b +1 I believe such logic

Re: [openstack-dev] What's up with functional testing?

On 10/28/2015 01:12 PM, Chris Dent wrote: > On Wed, 28 Oct 2015, Emilien Macchi wrote: > >> As a user[1], I would like to functionally test OpenStack services. > > Bless you. Let's all be more like that. > >> Until now I was happy, until this bug [4] (TL;DR: Aodh can't be testing >> with

Re: [openstack-dev] [cinder][nova] gate-cinder-python34 failing test_nova_timeout after novaclient 2.33 release

>But it was released with 2961e82 which was the backward incompatible requests exception change, which we now have a fix for that we want to release, but would include 0cd5812. I suppose we need to revert 0cd5812 change too, cut new release and then revert revert of 0cd5812 :) On Wed, Oct 28,

[openstack-dev] [Neutron] Weekly DVR Meeting starting next week

A few of us had a discussion this week at Summit and decided to re-start the weekly Neutron Distributed Virtual Router (DVR) meeting. The goal is to help: - Stabilize DVR - fix the bugs - Address performance/scalability issues - Get the DVR jobs voting again Meetings will be on Wednesdays

[openstack-dev] [Horizon] Meetings Canceled for Nov 4

Due to recent summit and many folks being on vacation, both the Horizon and Horizon Drivers meeting are canceled for Nov 4. We will resume on November 11. David __ OpenStack Development Mailing List (not for usage

Re: [openstack-dev] [puppet][keystone] Choose domain names with 'composite namevar' or 'meaningless name'?

On 29/10/15 17:32, Gilles Dubreuil wrote: > > > On 16/10/15 00:14, Emilien Macchi wrote: >> This thread is really huge and only 3 people are talking. >> Why don't you continue on an etherpad and do some brainstorm on it? >> If you do so, please share the link here. >> >> It would be much more

[openstack-dev] [swift] Plan to add Python 3 support to Swift

Hi, We talked about Python 3 with Christian Schwede, Alistair Coles, Samuel Meritt, Jaivish Kothari and others (sorry, I don't recall all names :-/) during Swift contributor meetup. It looks like we had an agreement on how to add Python 3 support to Swift. The plan is: 1) Fix the

Re: [openstack-dev] [Infra][Nova][Neutron] 6WIND Networking CI - approval for posting comments

Hi Matt, Armando, On Fri, Oct 30, 2015 at 1:17 AM, Armando M. wrote: >> >> Do you have any code in nova that's specific to your configuration? >> This CI is testing against our ML2 mechanism driver. This one uses the vhostuser vif_type. So the specific code related to Nova is

[openstack-dev] [heat] Friday afternoon heat social

The heat team is planning to meet this afternoon from 5pm for drinks, eating and chat. The Craftsman beer bistro is 15 minutes walk from here: https://goo.gl/maps/hviv4HK1Wor http://craftsman-craftbeerbistro.jp/ It opens at 5pm, the food is a variety of small plates to share. It would

Re: [openstack-dev] [swift] Plan to add Python 3 support to Swift

Thanks for the update. This seems like a reasonable way forward, but also one that will take a long time. Thank you for your work. I think this will result in larger and larger chunks of work, and so it will eventually result in large patches to move different components to py3. So you'll be

Re: [openstack-dev] Learning to Debug the Gate

On 10/29/2015 08:27 AM, Anita Kuno wrote: > On 10/28/2015 12:14 AM, Matt Riedemann wrote: >> >> >> On 10/27/2015 4:08 AM, Anita Kuno wrote: >>> Learning how to debug the gate was identified as a theme at the >>> "Establish Key Themes for the Mitaka Cycle" cross-project session: >>>

Re: [openstack-dev] correction: Re: [puppet][keystone] Keystone resource naming with domain support - no '::domain' if 'Default'

On 02/09/15 12:26, Rich Megginson wrote: > Slight correction below: > > On 09/01/2015 10:56 AM, Rich Megginson wrote: >> To close this thread: >> http://lists.openstack.org/pipermail/openstack-dev/2015-August/072878.html >> >> >> puppet-openstack will support Keystone domain scoped resource

[openstack-dev] [keystone] Update on Reseller

Hi At the design summit we have had a number of discussions on how to complete the reseller functionality (original spec: https://review.openstack.org/#/c/139824 ). We all agreed that we should split the implementation into: 1) Refactor the way domains

[openstack-dev] What's Up, Doc? 三鷹 Summit Edition

Hi everyone, Welcome to the Summit edition of the docs newsletter! Docs have had a wonderfully productive week here in Tokyo, and we've now established a plan for Mitaka. This newsletter covers the more important announcements, and the main points we want to hit in the next release. Karin has

[openstack-dev] [Nova] Details for the Nova Mitaka mid-cycle

Hi, It has been decided that the Nova Mitaka mid-cycle would be in Bristol, UK between 26 and 28 January. You can register at: https://www.eventbrite.com.au/e/openstack-mitaka-nova-mid-cycle-meetup-tickets-19326224257 Details of hotel discounts etc will be added to this thread when they are