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

[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] [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] [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] [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

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] [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] 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] 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

[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] [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

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] 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] [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 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

[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] [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] 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] [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

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] [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] 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] 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

[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] Team blogs

> -Original Message- > From: Sean Dague [mailto:[email protected]] > Sent: Monday, May 09, 2016 7:46 PM > To: [email protected] > 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

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] [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

[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

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

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] [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] 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] [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

[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

[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

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

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.

[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] [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

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] [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] 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] [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] [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] [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 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

[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] 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

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] [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] 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] [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] [OVN] [networking-ovn] [networking-sfc] SFC and OVN

John McDowall wrote on 05/09/2016 10:46:41 AM: > From: John McDowall > To: Ryan Moats/Omaha/IBM@IBMUS > Cc: "[email protected]" , "OpenStack > Development Mailing List" > Date: 05/09/2016 10:46 AM > Subject: Re: [OVN] [networking-ovn] [networking-sfc] SFC and OVN > > Ryan, > > Thanks –

Re: [openstack-dev] [Smaug] Meeting time change

About the Smaug meeting time, - 09:00 UTC for east, biweekly-odd This time is very good for the eastern side of the globe. Thanks saggi. Best Regards, xiangxinyong -- Original -- From: "Saggi Mizrahi";; Date: Tue, May 10, 2016 09:04 PM To: "openstac

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

Hi Jeremy, Yep, I saw it. Unfortunately, because Fuel deployment scenarios is about setting up OVS too, it could be kinda freaky to provide overlay networking for OVS on OVS. That's why I was looking on other L2 overlays (kernel space mcast vxlan was in scope too). But yes, we still can use th

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

On 10/05/2016 9:36 AM, Anne Gentle wrote: > > It's a small set of files: > https://github.com/openstack/api-site/tree/master/api-ref/source/telemetry/v2 > How about I ask someone to do the conversion and add it to > https://github.com/openstack/ceilometer? I have someone in mind who's > looking f

[openstack-dev] [Watcher] Meeting time change

Hi Watcher team, As discussed in Austin, I would like to make our team meeting more appropriate for people from Asia. I suggest to keep the current time (14:00 UTC) on even weeks and switch to 9:00 UTC for odd weeks. We can still meet on #openstack-meeting-4 for both meetings. Do you have any su

Re: [openstack-dev] [nova] api-ref sprint: Tuesday status

On 05/09/2016 08:23 AM, Sean Dague wrote: > There is a lot of work to be done to get the api-ref into a final state. > > Review / fix existing patches - > https://review.openstack.org/#/q/project:openstack/nova+file:api-ref+status:open > shows patches not yet merged. Please review them, and if the

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

I’d like to step down as a core reviewer for the OpenStack Puppet modules. For the last cycle I’ve had very little time to spend reviewing patches, and I don’t expect that to change in the next cycle. In addition, it used to be that I was contributing regularly because we were early upgraders and

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

Julien, Project or framework... regardless of the word, consumers of OpenStack (without additional knowledge) see it as a single entity. Anyway, especially after implementing the big tent, the documentation team is not large enough to assign one or more people to manage documentation in each proje

Re: [openstack-dev] [ironic] Midcycle: virtual or physical?

The poll closes Sunday night/Monday morning. Ie, whenever Jim gets around to looking at the numbers Monday (May 16) morning, before our weekly ironic meeting :) ‹ruby On 2016-05-09, 6:24 PM, "Jim Rollenhagen" wrote: >Hey all, > >In this morning's meetings we discussed having a virtual midcy

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

On 05/09/2016 06:27 PM, Augustina Ragwitz wrote: > Currently it's really hard to tell (at least to me) which files have > patches against them and which don't. I've had to manually make a > spreadsheet because it's not obvious to me, at a glance, from the > current commit messages, and I've acciden

[openstack-dev] [OpenStackClient] Meeting change reminder

This is a reminder that the OSC even week team meetings have changed time to Thursdays at 13:00 UTC in #openstack-meeting-3. See the eavesdrop meeting page [0] for complete information. dt [0] http://eavesdrop.openstack.org/#OpenStackClient_Team_Meeting -- Dean Troyer [email protected] __

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

opics: > https://etherpad.openstack.org/p/puppet-openstack-weekly-meeting-20160510 > > Feel free to add more and also submit any outstanding bug or patch. > > Thanks, > > On Tue, May 3, 2016 at 7:58 AM, Emilien Macchi wrote: >> Hi, >> >> If you have any topic th

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

On Tue, May 10, 2016 at 11:11 AM, Clayton O'Neill wrote: > I’d like to step down as a core reviewer for the OpenStack Puppet > modules. For the last cycle I’ve had very little time to spend > reviewing patches, and I don’t expect that to change in the next > cycle. In addition, it used to be tha

Re: [openstack-dev] [requirements] Bootstrapping new team for Requirements.

Excerpts from Davanum Srinivas (dims)'s message of 2016-05-07 11:02:23 -0400: > Dirk, Haïkel, Igor, Alan, Tony, Ghe, > > Please see brain dump here - > https://etherpad.openstack.org/p/requirements-tasks > > Looking at time overlap, it seems that most of you are in one time > range and Tony and

Re: [openstack-dev] Team blogs

Jeremy Stanley wrote: 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

Re: [openstack-dev] [tripleo] composable roles team

On Fri, 2016-04-29 at 15:27 -0500, Emilien Macchi wrote: > Hi, > > One of the most urgent tasks we need to achieve in TripleO during > Newton cycle is the composable roles support. > So we decided to build a team that would focus on it during the next > weeks. > > We started this etherpad: > http

Re: [openstack-dev] Wiki

Thierry Carrez wrote: 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 w

Re: [openstack-dev] [ironic][nova][horizon] Serial console support for ironic instances

Hi all, I'm working with Tien who is a submitter of one[1] of console specs. I joined the console session in Austin. In the session, we got the following consensus. - focus on serial console in Newton - use nova-serial proxy as is We also got some requirements[2] for this feature in the session.

Re: [openstack-dev] Team blogs

On Tue, May 10, 2016 at 8:05 AM, Jeremy Stanley wrote: > 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 foreve

Re: [openstack-dev] [kolla] CentOS binary and source gate failed due to the rabbitmq

I have a debug job open atm to try and investigate this: https://review.openstack.org/#/c/300988/ If anyone is handy with strace here is a run with the output: http://logs.openstack.org/88/300988/6/check/gate-kolla-dsvm-deploy-centos-binary/726c3b1/console.html On 09/05/16 18:23, Hui Kang wrot

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

ack on my side. So you'll need to create a governance patch like: https://review.openstack.org/#/c/252959/ and project-config patch to create the repo like: https://review.openstack.org/#/c/251857/ Once it's done, PTL (currently me) will review it. Once the module is created, we will use cookiec

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

On 05/10/2016 08:54 AM, Vladimir Eremin wrote: > 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. Awesome! This is a great writeup - and hopefully will be useful as we validat

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

On Tue, May 10, 2016, at 07:50 AM, Vladimir Eremin wrote: > Hi Jeremy, > > Yep, I saw it. Unfortunately, because Fuel deployment scenarios is about > setting up OVS too, it could be kinda freaky to provide overlay > networking for OVS on OVS. That's why I was looking on other L2 overlays > (kernel

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

As a frequent tinc user I'd be interested to see the code you are using to manage tinc into doing this. Is that code available somewhere? On Tue, May 10, 2016, at 09:02 AM, Monty Taylor wrote: > On 05/10/2016 08:54 AM, Vladimir Eremin wrote: > > Hi, > > > > I've investigated status of nodepool mu

Re: [openstack-dev] [OVN] [networking-ovn] [networking-sfc] SFC and OVN

Ryan, Let me do that - I assume adding them to plugin.py is the right approach. I have cleaned up https://github.com/doonhammer/networking-ovn and did a merge so it should be a lot easier to see the changes. I am going to cleanup ovs/ovn next. Once I have everything cleaned up and make sure it

Re: [openstack-dev] [nova] Austin summit priorities session recap

Hi Matt, Sorry I couldn't reply earlier - was away. I'm worrying about ScaleIO ephemeral storage backend (https://blueprints.launchpad.net/nova/+spec/scaleio-ephemeral-storage-backend) which is not in this list but various clients are very interested in having it working along with or instead

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

On Tue, May 10, 2016 at 9:11 AM, Clayton O'Neill wrote: > I’d like to step down as a core reviewer for the OpenStack Puppet > modules. For the last cycle I’ve had very little time to spend > reviewing patches, and I don’t expect that to change in the next > cycle. In addition, it used to be tha

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

Thanks for your work Clayton! =D 2016-05-10 13:30 GMT-03:00 Matt Fischer : > On Tue, May 10, 2016 at 9:11 AM, Clayton O'Neill > wrote: > >> I’d like to step down as a core reviewer for the OpenStack Puppet >> modules. For the last cycle I’ve had very little time to spend >> reviewing patches, a

Re: [openstack-dev] [nova] Austin summit priorities session recap

On 5/10/2016 11:24 AM, Alexandre Levine wrote: Hi Matt, Sorry I couldn't reply earlier - was away. I'm worrying about ScaleIO ephemeral storage backend (https://blueprints.launchpad.net/nova/+spec/scaleio-ephemeral-storage-backend) which is not in this list but various clients are very intereste

Re: [openstack-dev] Wiki

>> Hmm... that's unfortunate, as we were trying to get some of our less >> ephemeral items out of random etherpads and into the wiki (which has the >> value of being google indexed). Yeah, I'm kinda surprised anyone would consider a wiki-less world. I'm definitely bummed at the thought of losing i

Re: [openstack-dev] [kolla] CentOS binary and source gate failed due to the rabbitmq

Paul, Please run strace with -f (trace child processes). What you have there is not sufficient to do the job. FWIW erlang -16 is totally busted in CentOS because of logging, and erlang -17 is ready for testing which fixes the erlang crashes. Erlang-15 introduced ipv6 which could also be the cau

Re: [openstack-dev] Wiki

On 05/10/2016 12:48 PM, Dan Smith wrote: >>> Hmm... that's unfortunate, as we were trying to get some of our less >>> ephemeral items out of random etherpads and into the wiki (which has the >>> value of being google indexed). > > Yeah, I'm kinda surprised anyone would consider a wiki-less world.

[openstack-dev] [barbican]barbican github installation failing

Hi, I have a 4 node working setup of openstack (1 controller, 1 network node, 2 compute node). I am trying to use ssl offload feature of lbaas v2. For that I need tls containers, hence barbican. I did a git clone of barbican repo from https://github.com/openstack/barbican Then ./bin/barbican.sh ins

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

Excerpts from Rayson Ho's message of 2016-05-10 07:19:23 -0700: > 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 n

Re: [openstack-dev] [Openstack-operators] [barbican]barbican github installation failing

Uwsgi is a way to run the API portion of a python code base. You most likely need to install uwsgi for you operating system. http://uwsgi-docs.readthedocs.io/en/latest/ ___ Kris Lindgren Senior Linux Systems Engineer GoDaddy From:

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

Forget package management for a moment; we can figure it out if we need to. The question is "Why Go" which I've pondered for a while. If you need to write a multithreaded app, Python's GIL makes it very hard to do. It is one reason why I pushed for HTTPD as the Keystone front end. Python

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

On 05/10/2016 07:46 AM, Sean McGinnis wrote: > 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 Thank you all for mentoring and support! I'll do my best to fulfill the exp

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

> > 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 questions. > > 1)Should api-ref launchpad **bugs** be moved to each modules > (like keystone, nova

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

On 10/05/2016 01:01, Gregory Haynes wrote: > > On Mon, May 9, 2016, at 03:54 PM, John Dickinson wrote: >> On 9 May 2016, at 13:16, Gregory Haynes wrote: >>> >>> This is a bit of an aside but I am sure others are wondering the same >>> thing - Is there some info (specs/etherpad/ML thread/etc) that h

[openstack-dev] [third-party] Are you getting value from the 8:00 utc Tuesday meeting?

I've been chairing this meeting for about 3 releases now and in this last release it has mostly been myself and lennyb, who also attends the Monday 15:00 utc third-party meeting that I chair. Are you getting value from the Tuesday 8:00 utc third-party meeting? If yes, please make yourself known. I

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

neutron subnet-show with the UUID of the subnet they have a port on will tell you. On Tue, May 10, 2016 at 6:40 AM, Mike Spreitzer wrote: > "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

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

It is always hard to find a day and time that is good for everyone around the globe:-) The first meeting will still be UTC 1700 ~ UTC 1800 May 17 on Neutron channel. In the meeting, we can see if we can reach consensus on a new meeting time. Cathy -Original Message- From: Takashi Yamam

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

Whoops. What I just said was wrong if it hadn't been explicitly overwritten. I think you will end up having to do a port-list looking for the DHCP port(s). http://paste.openstack.org/show/496604/ On Tue, May 10, 2016 at 11:28 AM, Kevin Benton wrote: > neutron subnet-show with the UUID of the s

[openstack-dev] [Infra] Newton Summit Infra Sessions Recap

I'm Cc'ing this to the openstack-infra ML but setting MFT to direct subsequent discussion to the openstack-dev ML so we can hopefully avoid further cross-posting as much as possible. If you're replying on a particular session topic, please update the Subject so that the subthreads are easier to kee

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

On 15:54 May 09, John Dickinson wrote: > On 9 May 2016, at 13:16, Gregory Haynes wrote: > > > > This is a bit of an aside but I am sure others are wondering the same > > thing - Is there some info (specs/etherpad/ML thread/etc) that has more > > details on the bottleneck you're running in to? Given

Re: [openstack-dev] [OpenStack-Infra] [Infra] Newton Summit Infra Sessions Recap

On 05/10/2016 09:00 PM, Jeremy Stanley wrote: > [...] > Another outcome of this is that Andreas Jaeger put together some > project-config specific reviewing guidelines: > http://git.openstack.org/cgit/openstack-infra/project-config/plain/README.rst > In the future, that will be extended to mention

Re: [openstack-dev] [oslo][mistral] Saga of process than ack and where can we go from here...

Another data point: at this summit session we discussed delivering to users notifications about events in the cloud: https://etherpad.openstack.org/p/newton-alternatives-to-polling It's pretty critical that this have at-least-once delivery semantics, because in future people will be using this

Re: [openstack-dev] Team blogs

On 5/9/2016 6:46 PM, Sean Dague wrote: On 05/09/2016 06:37 PM, 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 i

  1   2   >