Re: [openstack-dev] [fuel] [QA] running Fuel tests using nodepool

On 2016-05-10 15:54:34 +0300 (+0300), Vladimir Eremin wrote: [...] > 1. Automate overlay networking setup. I've used > https://www.tinc-vpn.org/ as a L2 > switching overlay, but OpenVPN could be tool of choice. Action > items: > - overlay networking setup should be i

Re: [openstack-dev] [puppet] Watcher module for Puppet

Hi Daniel, You can join the puppet team in #puppet-openstack, the weekly meeting is every Tuesdays at 15 UTC in #openstack-meeting-4 This documentation can help you http://docs.openstack.org/developer/puppet-openstack-guide/new-module.html 2016-05-10 11:25 GMT-03:00 Daniel Pawlik : > Hello, >

Re: [openstack-dev] [tc] supporting Go

On Tue, May 10, 2016 at 2:42 AM, Tim Bell wrote: > I hope that the packaging technologies are considered as part of the TC evaluation of a new language. While many alternative approaches are available, a language which could not be packaged into RPM or DEB would be an additional burden for distro

Re: [openstack-dev] [puppet] Stepping down from core

great work Yanis! (i am talking about your ping pong skills). all the best in your new adventure. On 10/05/2016 3:52 AM, Yanis Guenane wrote: > Hello all, > > After the Mitaka summit, my main area of focus at work changed and I > couldn't find the necessary time to help anymore on the puppet modu

Re: [openstack-dev] Making changes to gerrit's presentation

On 2016-05-10 07:19:12 -0400 (-0400), Sean Dague wrote: [...] > Once a change is pushed, that ref also exists in github (given how all > our mirroring works). Often times it's easiest to link to things there > by permalink. [...] And git.openstack.org too, e.g.: http://git.openstack.org/cgit/open

[openstack-dev] [puppet] Watcher module for Puppet

Hello, I'm working on implementation of a new puppet module for Openstack Watcher (https://launchpad.net/watcher). I'm already creating this module and I would like to share it when it will be done. Could someone tell me how can I proceed to join puppet team's workflow ? By the way, Watcher

Re: [openstack-dev] [api] [senlin] [keystone] [ceilometer] [telemetry] Questions about api-ref launchpad bugs

On Tue, May 10, 2016 at 7:53 AM, Anne Gentle wrote: > Great questions, so I'm copying the -docs and -dev lists to make sure > people know the answers. > > On Tue, May 10, 2016 at 5:14 AM, Atsushi SAKAI > wrote: > >> Hello Anne >> >> I have several question when I am reading through etherpad's

Re: [openstack-dev] [neutron] [designate] multi-tenancy in Neutron's DNS integration

"Hayes, Graham" wrote on 05/10/2016 09:30:26 AM: > ... > > Ah, that may be what I want. BTW, I am not planning to use Nova. I am > > planning to use Swarm and Kubernetes to create containers attached to > > Neutron private tenant networks. What DNS server would I configure > > those container

Re: [openstack-dev] [api] [senlin] [keystone] [ceilometer] [telemetry] Questions about api-ref launchpad bugs

On Tue, May 10, 2016 at 8:12 AM, Julien Danjou wrote: > On Tue, May 10 2016, Anne Gentle wrote: > > > Ceilometer -- sorry, Julien, I hadn't reached out individually to you. > > Could you let me know your plans for the RST API reference docs? > > For Gnocchi and Aodh, we want to move to whatever t

Re: [openstack-dev] [nova] api-ref sprint today & wed

Including the filename in the commit message seems like I good plan. I started doing that now. On 05/10/2016 08:58 AM, Chen CH Ji wrote: > +1 to include .inc in the commit message, I also have to manually search > in the open list > > > > - Original message - > From: Augustina

Re: [openstack-dev] Cinder as generic volume manager

Hi Team, I'd get several requests about this features in IRC last weeks. I didn't stop working on it but any help is welcome:). Here is the list of proposed patched that are related to 'Use Cinder without Nova' feature: https://etherpad.openstack.org/p/use-cinder-without-nova Regards, Ivan Kolod

Re: [openstack-dev] [neutron] [designate] multi-tenancy in Neutron's DNS integration

On 09/05/2016 21:48, Mike Spreitzer wrote: > "Hayes, Graham" wrote on 05/09/2016 04:08:07 PM: > > > ... > > On 09/05/2016 20:55, Mike Spreitzer wrote: > > ... > > > Oh, right, the network gets to specify the rest of the FQDN. In my > case > > > I am interested in Neutron Ports on tenant netw

Re: [openstack-dev] [oslo] Austin summit session recap(s)

Excerpts from Alexis Lee's message of 2016-05-10 10:25:24 +0100: > Joshua Harlow said on Mon, May 02, 2016 at 05:30:32PM -0700: > > Mutable config progress + mutable logging + mutable > > *** > > > > Etherpad @ https://etherpad.openstack.org/p/newton

Re: [openstack-dev] [api] [senlin] [keystone] [ceilometer] [telemetry] Questions about api-ref launchpad bugs

On Tue, May 10 2016, Anne Gentle wrote: > Ceilometer -- sorry, Julien, I hadn't reached out individually to you. > Could you let me know your plans for the RST API reference docs? For Gnocchi and Aodh, we want to move to whatever the new format is and build a reference description in our tree (so

[openstack-dev] [Smaug] Meeting time change

Hi everyone, We would like to make the Smaug meeting weekly instead of biweekly and make it so that one week is in an appropriate time is preferable for the eastern side of the globe and one week for the western side of the globe. current time is Tuesdays at 14:00 UTC which is 22:00 in China

Re: [openstack-dev] [all] summit session recap - getting API Docs off WADL and into RST

All docs are migrated off of WADL now, but not all are publishing. Please see https://wiki.openstack.org/wiki/Documentation/Migrate#API_Reference_Plan and my post that high-fived with Sean's just minutes ago for the latest status. http://lists.openstack.org/pipermail/openstack-dev/2016-May/094478.

Re: [openstack-dev] [nova] api-ref sprint today & wed

+1 to include .inc in the commit message, I also have to manually search in the open list     - Original message -From: Augustina Ragwitz To: OpenStack Development Mailing List (not for usage questions)Cc:Subject: Re: [openstack-dev] [nova] api-ref sprint today & wedDate: Tue, May 10, 2016

[openstack-dev] [api] [senlin] [keystone] [ceilometer] [telemetry] Questions about api-ref launchpad bugs

Great questions, so I'm copying the -docs and -dev lists to make sure people know the answers. On Tue, May 10, 2016 at 5:14 AM, Atsushi SAKAI wrote: > Hello Anne > > I have several question when I am reading through etherpad's (in > progress). > It would be appreciated to answer these questi

[openstack-dev] [fuel] [QA] running Fuel tests using nodepool

Hi, I've investigated status of nodepool multi node testing and fuel-qa approaches, and I wanna share my opinion on moving Fuel testing on OpenStack and nodepool. Our CI pipeline consists of next stages: 1. Artifact building and publishing 2. QA jobs: 2.1. Master node installation from

Re: [openstack-dev] [all] summit session recap - getting API Docs off WADL and into RST

Sean Dague wrote: > Part of the cross project session track - > https://etherpad.openstack.org/p/newton-api-docs-rst > > The first half of the session was spent going over the background issues > and the work so far. The TL;DR > > * We need to get off WADL, it's a dead spec, and it's use is inhi

Re: [openstack-dev] Making changes to gerrit's presentation

On 05/10/2016 06:32 AM, Chris Dent wrote: > On Tue, 10 May 2016, Sean Dague wrote: > >> Gerrit's is a GWT app, which means the entire thing is Java which >> compiles to HTML/JS, for anything deep, you have to dive down that >> rabbit hole. > > Thanks for the response, this is pretty much what I f

Re: [openstack-dev] [kolla] [bifrost] bifrost container.

@ Mark What we discussed at the summit were to actions. 1 create a optional bifrost container to provision the os on a node 2 create a generic playbook that will configure the provisioned node with the deploy dependencies. The playbook should be reusable regardless of how the system is provisione

Re: [openstack-dev] [Cinder] Nominating Micha?? Dulko to Cinder Core

It has been one week and all very positive feedback. I have now added Michał to the cinder-core group. Welcome Michał! Glad to have your expertise in the group. Sean On Tue, May 03, 2016 at 01:16:59PM -0500, Sean McGinnis wrote: > Hey everyone, > > I would like to nominate Michał Dulko to the C

Re: [openstack-dev] [puppet] Stepping down from core

Thank you Yanis for your work on puppets! Good luck in your next projects! 2016-05-10 16:14 GMT+04:00 Emilien Macchi : > On Tue, May 10, 2016 at 3:52 AM, Yanis Guenane > wrote: > > Hello all, > > > > After the Mitaka summit, my main area of focus at work changed and I > > couldn't find the nece

[openstack-dev] [all] summit session recap - getting API Docs off WADL and into RST

Part of the cross project session track - https://etherpad.openstack.org/p/newton-api-docs-rst The first half of the session was spent going over the background issues and the work so far. The TL;DR * We need to get off WADL, it's a dead spec, and it's use is inhibiting contributions * We *need*

Re: [openstack-dev] [puppet] Stepping down from core

On Tue, May 10, 2016 at 3:52 AM, Yanis Guenane wrote: > Hello all, > > After the Mitaka summit, my main area of focus at work changed and I > couldn't find the necessary time to help anymore on the puppet modules. > > After a cycle I don't see my situation changing anytime soon, therefor > I'd lik

Re: [openstack-dev] Team blogs

On 2016-05-09 19:46:14 -0400 (-0400), Sean Dague wrote: > Honestly, I'm really liking that more of them are hitting the > mailing list proper this time around. Discoverability is key. The > mailing list is a shared medium, archived forever. I feel the same (says the guy who is still in the process

Re: [openstack-dev] Team blogs

> -Original Message- > From: Sean Dague [mailto:s...@dague.net] > Sent: Monday, May 09, 2016 7:46 PM > To: openstack-dev@lists.openstack.org > Subject: Re: [openstack-dev] Team blogs > > On 05/09/2016 06:37 PM, Joshua Harlow wrote: > > After seeing the amount of summit recaps and the scatt

[openstack-dev] [horizon] Midcycle Dates Poll

Hi all, Quick poll to get a preferred date for the Newton midcycle: http://doodle.com/poll/xvchsbbs4qz9tzr7 If you'd like a reference point, the release schedule is here: http://releases.openstack.org/newton/schedule.html. Planning should be finalised within the next week, so please respond pr

Re: [openstack-dev] Making changes to gerrit's presentation

On Tue, 10 May 2016, Sean Dague wrote: Gerrit's is a GWT app, which means the entire thing is Java which compiles to HTML/JS, for anything deep, you have to dive down that rabbit hole. Thanks for the response, this is pretty much what I feared. If I find some some cycles I may go exploring ove

Re: [openstack-dev] Making changes to gerrit's presentation

On 05/10/2016 06:42 AM, Chris Dent wrote: > > There are many things to complain about in gerrit but one of the > things I like the least is the inability to link to a specific chunk > of a review. Or at least I can't find one. > > What I'd like to be able to do is: > > * someone make a comment i

Re: [openstack-dev] [mistral] Promoting Hardik Parekh to core reviewers

+1 to Hardik :-) Regards! --- Lingxian Kong On Tue, May 10, 2016 at 8:49 PM, Renat Akhmerov wrote: > I’d like to promote Hardik Parekh to Mistral core reviewers. > > He was #1 by number of commits and #3 by number of reviews in Mitaka cycle > and I think he deserv

Re: [openstack-dev] [vitrage] [congress] Vitrage-Congress Collaboration

Hi Masahito, In addition, I wanted to add that the reason Congress needs to get the data from Vitrage by a pushing mechanism and not via polling, is so there won't be a delay from when the event occurs and when Congress receives it. Using polling, it will take a number of seconds (the polling i

Re: [openstack-dev] [vitrage] [congress] Vitrage-Congress Collaboration

Hi Masahito, Thanks for your question. There are two main reasons why we need to get alarms from Vitrage initially. First, there are alarms that Vitrage generates ("deduced alarms") based on its user-defined templates and topology. Also, there are alarms that come from external sources outsi

[openstack-dev] Making changes to gerrit's presentation

There are many things to complain about in gerrit but one of the things I like the least is the inability to link to a specific chunk of a review. Or at least I can't find one. What I'd like to be able to do is: * someone make a comment in gerrit that I would like to discuss in IRC * I want t

Re: [openstack-dev] [nova][ironic] Specs matcher and its journey through time

On 09/05/16 23:14, Joshua Harlow wrote: Anyways, after doing that I wanted to get any thoughts from people on the ML about that code, if they can see anything obviously bad about having more formality in the matching/spec DSL and/or other usages of things that I am not aware of that might be prob

[openstack-dev] [kuryr] Port binding query

I'm trying Kuryr with networking-calico and think I've hit an unhelpful inconsistency. A Neutron port has 'id' and 'device_id' fields that are usually different. When Nova does VIF binding for a Neutron port, it generates the Linux device name from 'tap' + port['id']. But when Kuryr does VIF bin

Re: [openstack-dev] Easing contributions to central documentation

On Mon, May 09 2016, Matt Kassawara wrote: > So, before developer frustrations drive some or all projects to move > their documentation in-tree which which negatively impacts the goal of > presenting a coherent product, I suggest establishing an agreement > between developers and the documentation

Re: [openstack-dev] [mistral] Promoting Hardik Parekh to core reviewers

Welcome to Mistral cores, Hardik Parekh! My vote is +1. On Tue, May 10, 2016 at 11:49 AM, Renat Akhmerov wrote: > I’d like to promote Hardik Parekh to Mistral core reviewers. > > He was #1 by number of commits and #3 by number of reviews in Mitaka cycle > and I think he deserved it. His statist

Re: [openstack-dev] Easing contributions to central documentation

On 09/05/16 22:57, Matt Kassawara wrote: > At each summit, I speak with a variety of developers from different > projects about the apparent lack of contributions to the central > documentation. At previous summits, the most common complaint involved > using DocBook. After converting most of the do

Re: [openstack-dev] [oslo] Austin summit session recap(s)

Joshua Harlow said on Mon, May 02, 2016 at 05:30:32PM -0700: > Mutable config progress + mutable logging + mutable > *** > > Etherpad @ https://etherpad.openstack.org/p/newton-oslo-mutables Sorry for missing this session :| No travel funding this ti

Re: [openstack-dev] [mistral] Promoting Hardik Parekh to core reviewers

I fully support this idea! It is my +1 for Hardik . On Tue, May 10, 2016 at 11:49 AM, Renat Akhmerov wrote: > I’d like to promote Hardik Parekh to Mistral core reviewers. > > He was #1 by number of commits and #3 by number of reviews in Mitaka cycle > and I think he deserved it. His statistics f

[openstack-dev] [mistral] Promoting Hardik Parekh to core reviewers

I’d like to promote Hardik Parekh to Mistral core reviewers. He was #1 by number of commits and #3 by number of reviews in Mitaka cycle and I think he deserved it. His statistics for Mitaka is at [1]. Please vote. [1] http://stackalytics.com/?release=mitaka&module=mistral-group&metric=marks&us

Re: [openstack-dev] Team blogs

On 9 May 2016 at 23:37, Joshua Harlow wrote: > After seeing the amount of summit recaps and the scattered nature of these > (some on the ML, some on etherpads, some on personal blogs); I am starting > to wonder if we should again bring up the question of having infra (and I > guess the foundation

Re: [openstack-dev] Wiki (was: Team blogs)

Sean Dague wrote: On 05/09/2016 06:53 PM, Monty Taylor wrote: On 05/09/2016 05:45 PM, Robert Collins wrote: IIRC mediawiki provides RSS of changes... maybe just using the wiki more would be a good start, and have zero infra costs? We'd actually like to start using the wiki less, per the most

Re: [openstack-dev] [vitrage] [congress] Vitrage-Congress Collaboration

Hi Alexey, This use case sounds interesting. To be clarified it, I have a question. On 2016/05/10 0:17, Weyl, Alexey (Nokia - IL) wrote: Hi Tim, I agree – creating a datasource from Vitrage to Congress is the first step, and we should have some concrete use case in mind to help guide this proc

Re: [openstack-dev] [tc] supporting Go

On 05/05/16 02:25, Tom Fifield wrote: > Not a TC member, and this might not even be the right place for this, > but ... I think it would be nice if someone has a think about how moving > from a primarily single language community to a > multiple-languages-allowed-in-a-bigger-way community impacts

Re: [openstack-dev] [tc] supporting Go

On 10/05/16 08:57, Angus Lees wrote: > No, it doesn't. Several applications written in go are already packaged > for Debian (for example). > > Indeed the equivalent of "installing from master/pip" (ie: not using > distro packages) is _much_ easier in go, since there is no need for the > equivalen

[openstack-dev] [puppet] Stepping down from core

Hello all, After the Mitaka summit, my main area of focus at work changed and I couldn't find the necessary time to help anymore on the puppet modules. After a cycle I don't see my situation changing anytime soon, therefor I'd like to step down as a core-reviewer. Reading about the Austin summit

Re: [openstack-dev] [neutron] work on Common Flow Classifier and OVS Agent extension for Newton cycle

On Tue, May 10, 2016 at 12:41 AM, wrote: > Hi Cathy, > > Cathy Zhang: >> >> I will tentatively set the meeting time to UTC 1700 ~ UTC 1800 Tuesday. >> Hope this time is good for all people who have interest and like to >> contribute to this work. We plan to start the first meeting on May 17. > >

[openstack-dev] [Rally] Could you share reference for Mitaka Upadates

To: Mr. Boris cc: OpenStacker who is interested in Rally Hello, Mr Boris. I was attend your session on Austin Summit "Rally: Overview of Mitaka results and Newton Goals". And I want to recheck out your presentation material in order to grasp current rally status. So could you share the presen

Re: [openstack-dev] [tc] supporting Go

No, it doesn't. Several applications written in go are already packaged for Debian (for example). Indeed the equivalent of "installing from master/pip" (ie: not using distro packages) is _much_ easier in go, since there is no need for the equivalent of venvs. Like all compiled languages, there i

<    1   2