Re: [openstack-dev] [TripleO][infra] HW upgrade for tripleo CI

\o/ On 05/06/2016 09:36 AM, Derek Higgins wrote: > Hi All, >the long awaited RAM and SSD's have arrived for the tripleo rack, > I'd like to schedule a time next week to do the install which will > involve and outage window. We could attempt to do it node by node but > the controller needs to c

Re: [openstack-dev] [TripleO][CI] Elastic recheck bugs

On 05/09/2016 02:32 PM, Clark Boylan wrote: > On Mon, May 9, 2016, at 10:22 AM, Sagi Shnaidman wrote: >> Hi, all >> >> I'd like to enable elastic recheck on TripleO CI and have submitted >> patches >> for refreshing the tracked logs [1] (please review) and for timeout case >> [2]. >> But according

[openstack-dev] [TripleO] Undercloud Configuration Wizard

Hi all, Just wanted to let everyone know that I've ported the undercloud configuration wizard to be a web app so it can be used by people without PyQt on their desktop. I've written a blog post about it here: http://blog.nemebean.com/content/undercloud-configuration-wizard and the tool itself is

Re: [openstack-dev] [TripleO] Removing the Tuskar repos

+1. I've already proposed a patch to remove it from instack-undercloud since the last report I got said it doesn't work anyway. On 12/22/2015 05:38 AM, Dougal Matthews wrote: > Hi all, > > I mentioned this at the meeting last week, but wanted to get wider > input. As far as I can tell from the c

Re: [openstack-dev] [TripleO] Is Swift a good choice of database for the TripleO API?

Can we just do git like I've been suggesting all along? ;-) More serious discussion inline. :-) On 12/22/2015 09:36 AM, Dougal Matthews wrote: > Hi all, > > This topic came up in the 2015-12-15 meeting[1], and again briefly today. > After working with the code that came out of the deployment lib

Re: [openstack-dev] [TripleO] Is Swift a good choice of database for the TripleO API?

On 12/22/2015 11:17 AM, Tomas Sedovic wrote: > On 12/22/2015 04:36 PM, Dougal Matthews wrote: >> Hi all, >> >> This topic came up in the 2015-12-15 meeting[1], and again briefly today. >> After working with the code that came out of the deployment library >> spec[2] I >> had some concerns with how

Re: [openstack-dev] [TripleO] Is Swift a good choice of database for the TripleO API?

On 12/23/2015 03:19 AM, Dougal Matthews wrote: > > > On 22 December 2015 at 17:59, Ben Nemec <mailto:openst...@nemebean.com>> wrote: > > Can we just do git like I've been suggesting all along? ;-) > > More serious discussion inline. :-) > >

Re: [openstack-dev] [TripleO] Is Swift a good choice of database for the TripleO API?

On 12/23/2015 10:26 AM, Steven Hardy wrote: > On Wed, Dec 23, 2015 at 09:28:59AM -0600, Ben Nemec wrote: >> On 12/23/2015 03:19 AM, Dougal Matthews wrote: >>> >>> >>> On 22 December 2015 at 17:59, Ben Nemec >> <mailto:openst...@nemebean.com>> w

Re: [openstack-dev] [all] Austin Summit Panel on Generation of Sample Configuration Option Files

On 01/04/2016 03:50 PM, Kendall J Nelson wrote: > Hello, > > > In brainstorming ideas for talks at the upcoming summit, I thought about > some of the things I had worked on for Cinder and what could still be > improved. One of the things I have been looking into is the generation > of sample conf

Re: [openstack-dev] [TripleO] Should we have a TripleO API, or simply use Mistral?

So I haven't weighed in on this yet, in part because I was on vacation when it was first proposed and missed a lot of the initial discussion, and also because I wanted to take some time to order my thoughts on it. Also because my initial reaction...was not conducive to calm and rational discussion

Re: [openstack-dev] [TripleO] Should we have a TripleO API, or simply use Mistral?

On 01/22/2016 12:30 PM, Ryan Brady wrote: > > > On Fri, Jan 22, 2016 at 12:24 PM, Ben Nemec <mailto:openst...@nemebean.com>> wrote: > > So I haven't weighed in on this yet, in part because I was on vacation > when it was first proposed and missed

Re: [openstack-dev] [TripleO] Should we have a TripleO API, or simply use Mistral?

On 01/22/2016 06:19 PM, Dan Prince wrote: > On Fri, 2016-01-22 at 11:24 -0600, Ben Nemec wrote: >> So I haven't weighed in on this yet, in part because I was on >> vacation >> when it was first proposed and missed a lot of the initial >> discussion, >> and a

Re: [openstack-dev] [TripleO] Should we have a TripleO API, or simply use Mistral?

On 01/25/2016 05:56 AM, Dougal Matthews wrote: > Great post Ben, I largely agree with what you are saying, a lot of your > points > are valid concerns that I share. Just a couple of comments inline as I > try to > avoid what others have said. > > On 22 January 201

Re: [openstack-dev] [TripleO] Should we have a TripleO API, or simply use Mistral?

On 01/25/2016 03:56 PM, Steven Hardy wrote: > On Fri, Jan 22, 2016 at 11:24:20AM -0600, Ben Nemec wrote: >> So I haven't weighed in on this yet, in part because I was on vacation >> when it was first proposed and missed a lot of the initial discussion, >> and also bec

Re: [openstack-dev] [TripleO] Should we have a TripleO API, or simply use Mistral?

On 01/26/2016 03:46 AM, Steven Hardy wrote: > On Mon, Jan 25, 2016 at 05:45:30PM -0600, Ben Nemec wrote: >> On 01/25/2016 03:56 PM, Steven Hardy wrote: >>> On Fri, Jan 22, 2016 at 11:24:20AM -0600, Ben Nemec wrote: >>>> So I haven't weighed in on this yet

Re: [openstack-dev] [TripleO] Should we have a TripleO API, or simply use Mistral?

On 01/25/2016 04:36 PM, Dan Prince wrote: > On Mon, 2016-01-25 at 15:31 -0600, Ben Nemec wrote: >> On 01/22/2016 06:19 PM, Dan Prince wrote: >>> On Fri, 2016-01-22 at 11:24 -0600, Ben Nemec wrote: >>>> So I haven't weighed in on this yet, in part because I wa

Re: [openstack-dev] [tripleo] [puppet] move puppet-pacemaker

On 02/09/2016 08:05 AM, Emilien Macchi wrote: > Hi, > > TripleO is currently using puppet-pacemaker [1] which is a module hosted > & managed by Github. > The module was created and mainly maintained by Redhat. It tends to > break TripleO quite often since we don't have any gate. > > I propose to

Re: [openstack-dev] [oslo][neutron] oslo.policy: policy_dirs config option, why deprecated?

On 07/04/2015 12:12 AM, Akihiro Motoki wrote: > Hi Oslo and Neutron folks, > > Why is policy_dirs option deprecated in oslo.policy? > In Neutron we have multiple repositories which consist of Neutron services > and we would like to maintain policy.json separately. > policy_dirs option looks useful

Re: [openstack-dev] [TripleO] Moving instack upstream

On 08/19/2015 12:22 PM, Dougal Matthews wrote: > > > > > - Original Message - >> From: "Dmitry Tantsur" >> To: openstack-dev@lists.openstack.org >> Sent: Wednesday, 19 August, 2015 5:57:36 PM >> Subject: Re: [openstack-dev] [TripleO] Moving instack upstream >> >> On 08/19/2015 06:42 PM

Re: [openstack-dev] [tripleo] CLI and RHEL registration of overcloud nodes

On 08/26/2015 11:00 AM, Steven Hardy wrote: > On Wed, Aug 26, 2015 at 05:28:47PM +0200, Jan Provazník wrote: >> Hi, >> although rdomanager-oscplugin is not yet under TripleO it should be soon, so >> sending this to TripleO audience. >> >> Satellite registration from user's point of view is now done

Re: [openstack-dev] [TripleO] Releasing tripleo-common on PyPI

On 09/09/2015 12:54 PM, Doug Hellmann wrote: > Excerpts from Dmitry Tantsur's message of 2015-09-09 12:58:04 +0200: >> On 09/09/2015 12:15 PM, Dougal Matthews wrote: >>> Hi, >>> >>> The tripleo-common library appears to be registered or PyPI but hasn't yet >>> had >>> a release[1]. I am not famili

Re: [openstack-dev] [TripleO] Core reviewers for python-tripleoclient and tripleo-common

On 09/10/2015 09:06 AM, James Slagle wrote: > TripleO has added a few new repositories, one of which is > python-tripleoclient[1], the former python-rdomanager-oscplugin. > > With the additional repositories, there is an additional review burden > on our core reviewers. There is also the fact that

Re: [openstack-dev] [TripleO] Remove Tuskar from tripleo-common and python-tripleoclient

On 09/15/2015 11:33 AM, Dougal Matthews wrote: > Hi all, > > This is partly a heads up for everyone, but also seeking feedback on the > direction. > > We are starting to move to a more general Heat workflow without the need for > Tuskar. The CLI is already in a position to do this as we can succe

Re: [openstack-dev] [all] Consistent support for SSL termination proxies across all API services

I've been dealing with this issue lately myself, so here's my two cents: It seems to me that solving this at the service level is actually kind of wrong. As you've discovered, that requires changes in a bunch of different places to address what is really an external issue. Since it's the termina

Re: [openstack-dev] [all] Consistent support for SSL termination proxies across all API services

On 09/22/2015 06:00 AM, Sean Dague wrote: > On 09/18/2015 02:30 PM, Ben Nemec wrote: >> I've been dealing with this issue lately myself, so here's my two cents: >> >> It seems to me that solving this at the service level is actually kind >> of wrong. As you&#x

Re: [openstack-dev] [oslo] nominating Brant Knudson for Oslo core

Not sure if my vote still counts, but +1. :-) On 09/24/2015 12:12 PM, Doug Hellmann wrote: > Oslo team, > > I am nominating Brant Knudson for Oslo core. > > As liaison from the Keystone team Brant has participated in meetings, > summit sessions, and other discussions at a level higher than some

Re: [openstack-dev] [TripleO] tripleo.org theme

On 09/25/2015 07:34 AM, Dan Prince wrote: > It has come to my attention that we aren't making great use of our > tripleo.org domain. One thing that would be useful would be to have the > new tripleo-docs content displayed there. It would also be nice to have > quick links to some of our useful reso

Re: [openstack-dev] [TripleO] Defining a public API for tripleo-common

On 2015-09-30 01:08, Dougal Matthews wrote: > Hi, > > What is the standard practice for defining public API's for OpenStack > libraries? As I am working on refactoring and updating tripleo-common I have > to grep through the projects I know that use it to make sure I don't break > anything. >

Re: [openstack-dev] [all] -1 due to line length violation in commit messages

On 10/01/2015 02:56 AM, Ghe Rivero wrote: > If anyone disagrees with the commit format, please, go ahead and fix it (It's > really easy using the gerrit web) For such cosmetic changes (and others > similars), we should not wait for the author to do it. Sometimes, for a stupid > comma, and with all

Re: [openstack-dev] [all] -1 due to line length violation in commit messages

On 10/05/2015 12:12 PM, Jeremy Stanley wrote: > On 2015-10-05 12:00:31 -0500 (-0500), Ben Nemec wrote: > [...] >> Note that it's best to do this once the change is ready to be >> approved. If you do it earlier and the committer pushes a new >> patch set without fixin

[openstack-dev] [TripleO] Auto-abandon bot

Hi OoOers, As discussed in the meeting a week or two ago, we would like to bring back the auto-abandon functionality for old, unloved gerrit reviews. I've got a first implementation of a tool to do that: https://github.com/cybertron/tripleo-auto-abandon It currently follows these rules for determ

Re: [openstack-dev] [TripleO] Auto-abandon bot

On 10/10/2015 08:12 AM, Jeremy Stanley wrote: > On 2015-10-09 17:10:15 -0500 (-0500), Ben Nemec wrote: >> As discussed in the meeting a week or two ago, we would like to bring >> back the auto-abandon functionality for old, unloved gerrit reviews. > [...] >> -WIP pat

Re: [openstack-dev] [TripleO] Auto-abandon bot

On 10/13/2015 08:08 PM, Dan Prince wrote: > On Mon, 2015-10-12 at 11:38 -0500, Ben Nemec wrote: >> On 10/10/2015 08:12 AM, Jeremy Stanley wrote: >>> On 2015-10-09 17:10:15 -0500 (-0500), Ben Nemec wrote: >>>> As discussed in the meeting a week or two ago, we would li

Re: [openstack-dev] [TripleO] Introspection rules aka advances profiles replacement: next steps

On 10/14/2015 06:38 AM, Dmitry Tantsur wrote: > Hi OoO'ers :) > > It's going to be a long letter, fasten your seat-belts (and excuse my > bad, as usual, English)! > > In RDO Manager we used to have a feature called advanced profiles > matching. It's still there in the documentation at > http:/

Re: [openstack-dev] [TripleO] Introspection rules aka advances profiles replacement: next steps

On 10/14/2015 12:18 PM, John Trowbridge wrote: > > > On 10/14/2015 10:57 AM, Ben Nemec wrote: >> On 10/14/2015 06:38 AM, Dmitry Tantsur wrote: >>> Hi OoO'ers :) >>> >>> It's going to be a long letter, fasten your seat-belts (and excuse my &g

Re: [openstack-dev] [TripleO] Show TripleO: A terminal dashboard

Interesting! So this could conceivably be another consumer of the API, right? A sort of CLI UI? On 02/25/2016 01:10 PM, Dougal Matthews wrote: > Hi all, > > Over the past couple of weeks in my spare time I put together a basic > Python urwid dashboard for TripleO. You can see the usage and some

Re: [openstack-dev] [tripleo] CI jobs failures

On 03/07/2016 12:00 PM, Derek Higgins wrote: > On 7 March 2016 at 12:11, John Trowbridge wrote: >> >> >> On 03/06/2016 11:58 AM, James Slagle wrote: >>> On Sat, Mar 5, 2016 at 11:15 AM, Emilien Macchi wrote: I'm kind of hijacking Dan's e-mail but I would like to propose some technical i

Re: [openstack-dev] [tripleo] CI jobs failures

On 03/07/2016 11:33 AM, Derek Higgins wrote: > On 7 March 2016 at 15:24, Derek Higgins wrote: >> On 6 March 2016 at 16:58, James Slagle wrote: >>> On Sat, Mar 5, 2016 at 11:15 AM, Emilien Macchi wrote: I'm kind of hijacking Dan's e-mail but I would like to propose some technical improv

Re: [openstack-dev] [tripleo] CI jobs failures

On 03/08/2016 11:58 AM, Derek Higgins wrote: > On 7 March 2016 at 18:22, Ben Nemec wrote: >> On 03/07/2016 11:33 AM, Derek Higgins wrote: >>> On 7 March 2016 at 15:24, Derek Higgins wrote: >>>> On 6 March 2016 at 16:58, James Slagle wrote: >>>>> On

Re: [openstack-dev] [TripleO] propose ejuaso for core

+1. I've been meaning to suggest this off-list for a while. On 03/14/2016 09:38 AM, Dan Prince wrote: > http://russellbryant.net/openstack-stats/tripleo-reviewers-180.txt > > Our top reviewer over the last half a year ejuaso (goes by Ozz for > Osorio or jaosorior on IRC). His reviews seem consis

Re: [openstack-dev] [TripleO] core cleanup

+1 On 03/14/2016 09:26 AM, Dan Prince wrote: > Looking at the stats for the last 180 days I'd like to propose we > cleanup TripleO core a bit: > > http://russellbryant.net/openstack-stats/tripleo-reviewers-180.txt > > There are a few reviewers with low numbers of reviews (just added to > the tri

Re: [openstack-dev] [tripleO][Neutron] neutron-lbaas agent service placement

On 03/14/2016 10:18 AM, Qasim Sarfraz wrote: > Hi Triple-O folks, > > I was planning to enable neutron-lbaas-agent on a overcloud deployment > but couldn't find any useful documentation. Can someone please point me > to the required documentation? Is there a heat/puppet workflow available > for th

Re: [openstack-dev] [tripleO][Neutron] neutron-lbaas agent service placement

On 03/16/2016 05:29 AM, Qasim Sarfraz wrote: > Thanks Ben. > > On Tue, Mar 15, 2016 at 10:51 PM, Ben Nemec <mailto:openst...@nemebean.com>> wrote: > > On 03/14/2016 10:18 AM, Qasim Sarfraz wrote: > > Hi Triple-O folks, > > > > I was p

Re: [openstack-dev] [tripleo] becoming third party CI

On 03/10/2016 05:24 PM, Jeremy Stanley wrote: > On 2016-03-10 16:09:44 -0500 (-0500), Dan Prince wrote: >> This seems to be the week people want to pile it on TripleO. Talking >> about upstream is great but I suppose I'd rather debate major changes >> after we branch Mitaka. :/ > [...] > > I didn'

Re: [openstack-dev] [tripleo] becoming third party CI

On 03/17/2016 01:13 PM, Paul Belanger wrote: > On Thu, Mar 17, 2016 at 11:59:22AM -0500, Ben Nemec wrote: >> On 03/10/2016 05:24 PM, Jeremy Stanley wrote: >>> On 2016-03-10 16:09:44 -0500 (-0500), Dan Prince wrote: >>>> This seems to be the week people want

Re: [openstack-dev] [tripleo] becoming third party CI

On 03/21/2016 07:33 AM, Derek Higgins wrote: > On 17 March 2016 at 16:59, Ben Nemec wrote: >> On 03/10/2016 05:24 PM, Jeremy Stanley wrote: >>> On 2016-03-10 16:09:44 -0500 (-0500), Dan Prince wrote: >>>> This seems to be the week people want to pile it on TripleO.

Re: [openstack-dev] [tripleo] becoming third party CI

On 03/21/2016 03:52 PM, Paul Belanger wrote: > On Mon, Mar 21, 2016 at 10:57:53AM -0500, Ben Nemec wrote: >> On 03/21/2016 07:33 AM, Derek Higgins wrote: >>> On 17 March 2016 at 16:59, Ben Nemec wrote: >>>> On 03/10/2016 05:24 PM, Jeremy Stanley wrote: >>>

Re: [openstack-dev] [Nova] Requirements.txt and optional requirements

On 01/27/2015 02:18 AM, Silvan Kaiser wrote: > Hello! > Do dependencies required only in some contexts belong into requirements.txt? > > Yesterday we had a short discussion on #openstack-nova regarding how to > handle optional requirements. This was triggered by our quobyte nova driver > (https://

Re: [openstack-dev] [oslo] temporarily disabling python 3.x testing for oslo.messaging and oslo.rootwrap

On 01/27/2015 10:51 AM, Doug Hellmann wrote: > The infra team has been working hard to update our Python 3 testing for all > projects to run on 3.4 instead of 3.3. Two of the last projects to be able to > shift are oslo.messaging and oslo.rootwrap. The test suites for both projects > trigger a s

Re: [openstack-dev] [infra][project-config][oslo.messaging] Pre-driver requirements split-up initiative

On 02/06/2015 10:12 AM, Doug Hellmann wrote: > > > On Fri, Feb 6, 2015, at 07:37 AM, Denis Makogon wrote: >> Hello to All. >> >> >> As part of oslo.messaging initiative to split up requirements into >> certain >> list of per messaging driver dependencies >>

Re: [openstack-dev] [oslo] oslo.versionedobjects repository is ready for pre-import review

Overall looks good to me and the unit tests are passing locally. I'm wondering about some of the stuff that was left commented out without a FIXME and left a couple of comments about them, but I'm mostly assuming they were just things commented for testing that weren't removed later. -Ben On 02/

[openstack-dev] [all][eventlet] Eventlet Best Practices

Hi all, There's recently been quite a bit of discussion in Oslo about what Eventlet use cases we want to support, and this led to the conclusion that an eventlet best practices document would be helpful. Because of the broad applicability of this information, the thought was that a cross-project

Re: [openstack-dev] openstack/requirements failure

On 02/11/2015 11:33 AM, Manickam, Kanagaraj wrote: > Hi > > In horizon I am trying to increase the python-heatclient>=0.3.0 as part of > the review https://review.openstack.org/#/c/154952/ and its failed with > following error: > > > "Requirement python-heatclient>=0.3.0 does not match opensta

Re: [openstack-dev] [all][tc] Lets keep our community open, lets fight for it

On 02/11/2015 11:19 AM, Amrith Kumar wrote: > Stefano, > > You write: > > | This is seriously disturbing. > | > | If you're one of those core reviewers hanging out on a private channel, > | please contact me privately: I'd love to hear from you why we failed as a > | community at convincing you

Re: [openstack-dev] [all][tc] Lets keep our community open, lets fight for it

On 02/11/2015 04:52 AM, Daniel P. Berrange wrote: > On Wed, Feb 11, 2015 at 10:55:18AM +0100, Flavio Percoco wrote: >> Greetings all, >> >> During the last two cycles, I've had the feeling that some of the >> things I love the most about this community are degrading and moving >> to a state that I

Re: [openstack-dev] [Infra] Rebase button enabled for all Gerrit users

On 02/13/2015 11:42 AM, Jeremy Stanley wrote: > For a few months, some project core teams (including Nova's) have > been running with an ACL granting access to the "rebase" button in > Gerrit for all the projects they manage, a permission usually only > exposed to the "owner" of an individual chang

Re: [openstack-dev] [neutron][neutron-*aas] Is lockutils-wrapper needed for tox.ini commands?

All it does is create a temporary lock directory and then set an env var to that path so external locks work properly in tests. If you don't have any external locks or you use https://github.com/openstack/oslo.concurrency/blob/master/oslo_concurrency/fixture/lockutils.py#L55 for any tests that do

[openstack-dev] [all][oslo] Dealing with database connection sharing issues

Hi, Mike Bayer recently tracked down an issue with database errors in Cinder to a single database connection being shared over multiple processes. This is not something that should happen, and it turns out to cause intermittent failures in the Cinder volume service. Full details can be found in t

Re: [openstack-dev] [hacking] disable a check by default

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 02/20/2015 12:07 PM, Ihar Hrachyshka wrote: > Hi, > > I would like to introduce a hacking check that would be disabled > by default: > > https://review.openstack.org/157894 > > I see the following commit in flake8: > > https://gitlab.com/methane

Re: [openstack-dev] [TripleO] Midcycle Summary

Thanks for the summary. A couple of comments inline. On 02/24/2015 08:48 AM, James Slagle wrote: > Hi Everyone, > > TripleO held a midcycle meetup from February 18th-20th in Seattle. Thanks to > HP > for hosting the event! I wanted to send out a summary of what went on. We also > captured some

Re: [openstack-dev] [all] creating a unified developer reference manual

So, I'm wondering how much of this is unnecessarily splitting hairs on what defines a cross-project spec. If you look at the currently merged specs, they are in fact both Guidelines: http://specs.openstack.org/openstack/openstack-specs/ Would renaming mine Eventlet Guidelines make it more palatab

Re: [openstack-dev] [oslo][openstackclient] transferring maintenance of cliff to the OpenStack client team

On 02/26/2015 03:57 PM, Doug Hellmann wrote: > The team behind the unified command line tool is preparing to ask the TC to > allow us to become an official team. The openstack/python-openstackclient > repository will be managed by this "new" team, and I suggested we also > consider transferring

Re: [openstack-dev] [all] creating a unified developer reference manual

On 02/27/2015 03:54 AM, Thierry Carrez wrote: > Doug Hellmann wrote: >> Maybe some of the folks in the meeting who felt more strongly that it >> should be a separate document can respond with their thoughts? > > I don't feel very strongly and could survive this landing in > openstack-specs. My obj

[openstack-dev] [Ironic][TripleO] IPMI controller for OpenStack instances

It's been quite a while since my last QuintupleO update, mostly due to excessive busy-ness, but I've been asked about it enough times since then that I decided to make time for it. I made another blog post with more details [1], but the gist is that I have a pyghmi-based IPMI controller for OpenSt

Re: [openstack-dev] Missing button to send Ctrl+Alt+Del for SPICE Console

On 03/05/2015 09:34 AM, Andy McCrae wrote: > Sorry to resurrect this almost a year later! I've recently run into this > issue, and it does make logging into Windows instances, via the console, > quite challenging. > > On Fri, Jun 6, 2014 at 3:46 PM, Ben Nemec wrote: >

Re: [openstack-dev] [oslo] oslo.concurrency runtime dependency on fixtures/testtools

On 03/12/2015 09:18 AM, Brant Knudson wrote: > On Thu, Mar 12, 2015 at 7:20 AM, Davanum Srinivas wrote: > >> Alan, >> >> We are debating this on: >> https://review.openstack.org/#/c/157135/ >> >> Please hop on :) >> -- dims >> >> On Thu, Mar 12, 2015 at 5:28 AM, Alan Pevec wrote: >>> Hi, >>> >>>

Re: [openstack-dev] [packaging][neutron] --config-dir vs. --config-file

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 03/13/2015 09:11 AM, Ihar Hrachyshka wrote: > Hi all, > > (I'm starting a new [packaging] tag in this mailing list to reach > out people who are packaging our software in distributions and > whatnot.) > > Neutron vendor split [1] introduced situat

[openstack-dev] [TripleO] QuintupleO Overview

So I've successfully done a deployment to a QuintupleO environment. \o/ I don't have a nice polished demo video yet or anything, but I did go ahead and write up some general thoughts about the process I followed here: http://blog.nemebean.com/content/quintupleo-success I realize it's not super de

Re: [openstack-dev] [TripleO][Tuskar] Common library for shared code

On 03/13/2015 05:53 AM, Jan Provaznik wrote: > On 03/10/2015 05:53 PM, James Slagle wrote: >> On Mon, Mar 9, 2015 at 4:35 PM, Jan Provazník wrote: >>> Hi, >>> it would make sense to have a library for the code shared by Tuskar UI and >>> CLI (I mean TripleO CLI - whatever it will be, not tuskarcli

Re: [openstack-dev] [TripleO][Tuskar] Common library for shared code

On 03/17/2015 09:13 AM, Zane Bitter wrote: > On 16/03/15 16:38, Ben Nemec wrote: >> On 03/13/2015 05:53 AM, Jan Provaznik wrote: >>> On 03/10/2015 05:53 PM, James Slagle wrote: >>>> On Mon, Mar 9, 2015 at 4:35 PM, Jan Provazník wrote: >>>>> Hi, >&g

Re: [openstack-dev] [TripleO] QuintupleO Overview

On 03/17/2015 01:59 AM, Smigiel, Dariusz wrote: >> On 17 March 2015 at 09:30, Ben Nemec >> wrote: >>> So I've successfully done a deployment to a QuintupleO environment. \o/ >> >> \o/ >> > > Great news! Congrats! > > @Ben, are you planni

Re: [openstack-dev] [TripleO] QuintupleO Overview

As promised, the demo video: https://www.youtube.com/watch?v=XvCEBWin7eE -Ben On 03/19/2015 02:01 PM, Ben Nemec wrote: > On 03/17/2015 01:59 AM, Smigiel, Dariusz wrote: >>> On 17 March 2015 at 09:30, Ben Nemec >>> wrote: >>>> So I've successfully done a

Re: [openstack-dev] [oslo.messaging][zeromq] 'Subgroup' for broker-less ZeroMQ driver

On 03/24/2015 10:31 AM, Li Ma wrote: > On Mon, Mar 23, 2015 at 9:24 PM, Doug Hellmann wrote: >> The goal we set at the Kilo summit was to have a group of people >> interested in zmq start contributing to the driver, and I had hoped to >> the library overall. How do we feel that is going? > > That

Re: [openstack-dev] [oslo] not running for PTL for liberty cycle

As everyone else has said, you did a fantastic job as PTL. Oslo is in a much better place today because of your leadership. -Ben On 04/03/2015 07:50 AM, Doug Hellmann wrote: > Team, > > I have decided not to run for PTL for Oslo for the next cycle. > > Serving as PTL for the last three release

Re: [openstack-dev] [oslo.utils] allow strutils.mask_password to mask keys dynamically

On 03/20/2015 11:43 AM, Doug Hellmann wrote: > Excerpts from Matthew Van Dijk's message of 2015-03-20 15:06:08 +: >> I’ve come across a use case for allowing dynamic keys to be made >> secret. The hardcoded list is good for common keys, but there will be >> cases where masking a custom value is

Re: [openstack-dev] [TripleO] Consistent variable documentation for diskimage-builder elements

+2 from me. I'm still in favor of killing off most/all input env vars and coming up with a less error-prone way to handle configuration, but in the meantime this is a big step toward sanity for users. On 04/07/2015 04:06 PM, Gregory Haynes wrote: > Hello, > > Id like to propse a standard for con

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

On 04/08/2015 11:25 AM, Dolph Mathews wrote: > On Wed, Apr 8, 2015 at 9:33 AM, Ryan Brown wrote: > >> On 04/08/2015 09:12 AM, Flavio Percoco wrote: >>> On 08/04/15 08:59 -0400, Doug Hellmann wrote: Excerpts from Robert Collins's message of 2015-04-07 10:43:30 +1200: > On 7 April 2015 at

Re: [openstack-dev] [puppet][tc] Adding the Puppet modules to OpenStack

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Just adding the tc tag so this doesn't get overlooked by the relevant people. On 04/09/2015 10:33 AM, Emilien Macchi wrote: > It has been quite some time now that Puppet OpenStack contributors > have wanted to be part of the big tent so we would becom

Re: [openstack-dev] [tripleo] Adventures in QuintupleO

On 04/20/2015 04:39 PM, Steve Baker wrote: > I've been spending some time getting quintupleo working on top of a Juno > RDO OpenStack. I'm at a point now where I think it is worth putting > effort into making it easy for anyone to try this. \o/ > > Ben Nemec has done

Re: [openstack-dev] Please stop reviewing code while asking questions

On 04/24/2015 07:11 AM, Russell Bryant wrote: > On 04/24/2015 07:21 AM, Amrith Kumar wrote: >> We had a hypothesis about why +0 was rarely used (never conclusively >> proved). Our hypothesis was that since Stackalytics didn't count +0's >> it led to an increased propensity to -1 something. It would

Re: [openstack-dev] [oslo] Adding Joshua Harlow to oslo-core

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 +1 from me as well! On 05/05/2015 09:47 AM, Julien Danjou wrote: > Hi fellows, > > I'd like to propose that we add Joshua Harlow to oslo-core. He is > already maintaining some of the Oslo libraries (taskflow, tooz…) > and he's helping on a lot of

Re: [openstack-dev] [TripleO] Core reviewer update proposal

Definite +1 to both On 05/05/2015 06:57 AM, James Slagle wrote: > Hi, I'd like to propose adding Giulio Fidente and Steve Hardy to TripleO Core. > > Giulio has been an active member of our community for a while. He > worked on the HA implementation in the elements and recently has been > making a

Re: [openstack-dev] [puppet] Proposal to configure Oslo libraries

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 I don't know much about the puppet project organization so I won't comment on whether 1 or 2 is better, but a big +1 to having a common way to configure Oslo opts. Consistency of those options across all services is one of the big reasons we pushed

Re: [openstack-dev] [oslo] Exception in rpc_dispatcher

On 05/07/2015 03:34 AM, Vikash Kumar wrote: > I did following in my agent code: > > import eventlet > > eventlet.monkey_patch() > > but still I see same issue. Unfortunately, monkey patching in an agent is probably too late. The monkey patching has to happen at application startup to be done b

Re: [openstack-dev] [oslo] Adding Mehdi Abaakouk (sileht) to oslo-core

+1! On 05/07/2015 09:36 AM, Davanum Srinivas wrote: > Dear Oslo folks, > > I'd like to propose adding Mehdi Abaakouk to oslo-core. He is already > leading the oslo.messaging team and helping with Tooz, and futurist > efforts. > > I am hoping to get Mehdi more involved across the board in Oslo. >

Re: [openstack-dev] [oslo] PTG summary

On 02/27/2017 03:30 PM, Doug Hellmann wrote: Excerpts from ChangBo Guo's message of 2017-02-25 00:07:21 +0800: Oslo folks, This is summary of oslo PTG schedule during one and half days. You can check the details in etherpad link: https://etherpad.openstack.org/p/oslo-ptg-pike 1. oslo.messag

Re: [openstack-dev] [tripleo][diskimage-builder] Status of diskimage-builder

On 03/02/2017 03:31 PM, Emilien Macchi wrote: On Thu, Jan 12, 2017 at 3:06 PM, Yolanda Robla Mota wrote: From my point of view, i've been using that either on infra with puppet-infracloud, glean.. and now with TripleO. So in my opinion, it shall be an independent project, with core contributo

Re: [openstack-dev] [tripleo][diskimage-builder] Status of diskimage-builder

On 03/03/2017 03:25 AM, Ligong LG1 Duan wrote: I am wondering whether DIB can become a component of Glance, as DIB is used to create OS images and Glance to upload OS images. I see a big difference between creating images and storing them. I can't imagine Glance would have any interest in

Re: [openstack-dev] [infra][tripleo] initial discussion for a new periodic pipeline

On 03/13/2017 02:29 PM, Sagi Shnaidman wrote: Hi, all I submitted a change: https://review.openstack.org/#/c/443964/ but seems like it reached a point which requires an additional discussion. I had a few proposals, it's increasing period to 12 hours instead of 4 for start, and to leave it in

[openstack-dev] [dib][heat] dib-utils/dib-run-parts/dib v2 concern

While looking through the dib v2 changes after the feature branch was merged to master, I noticed this commit[1], which bring dib-run-parts back into dib itself. Unfortunately I missed the original proposal to do this, but I have some concerns about the impact of this change. Originally the s

Re: [openstack-dev] [infra][tripleo] initial discussion for a new periodic pipeline

Wed, Mar 15, 2017 at 11:16 PM, Paul Belanger mailto:pabelan...@redhat.com>> wrote: On Wed, Mar 15, 2017 at 03:42:32PM -0500, Ben Nemec wrote: > > > On 03/13/2017 02:29 PM, Sagi Shnaidman wrote: > > Hi, all > > > > I submitted a change: https:

Re: [openstack-dev] [infra][tripleo] initial discussion for a new periodic pipeline

ripleo. That was initially not very successful and we chose to instead focus on upstream. We *do* have it on our list to gate packages from RDO builds with tripleo. In the short term that gate will use rdocloud, in the long term we'd also like to gate w/ multinode nodepool

Re: [openstack-dev] [tripleo] rh1 issues post-mortem

we'll have another 3 months before we have to worry about this again. On 03/24/2017 11:47 AM, Derek Higgins wrote: On 22 March 2017 at 22:36, Ben Nemec wrote: Hi all (owl?), You may have missed it in all the ci excitement the past couple of days, but we had a partial outage of rh1 last

Re: [openstack-dev] [deployment][TripleO][kolla][ansible][fuel] Next steps for cross project collaboration

On 03/02/2017 08:27 PM, Emilien Macchi wrote: On Mon, Feb 27, 2017 at 11:20 AM, Emilien Macchi wrote: On Mon, Feb 27, 2017 at 11:02 AM, Steven Hardy wrote: Hi all, Over the recent PTG, and previously at the design summit in Barcelona, we've had some productive cross-project discussions amo

Re: [openstack-dev] [tripleo] rh1 issues post-mortem

e're still using this environment. On 03/24/2017 12:48 PM, Ben Nemec wrote: To follow-up on this, we've continued to hit this issue on other compute nodes. Not surprising, of course. They've all been up for about the same period of time and have had largely even workloads. It h

Re: [openstack-dev] [TripleO] spec-lite process for tripleo

On 03/28/2017 11:09 AM, Emilien Macchi wrote: Bringing an old topic on the table. We might have noticed: 1. Some tripleo-specs take huge amount of time before getting merged (or even reviewed). We have been asking folks to review them every week but unfortunately they don't get much attractio

Re: [openstack-dev] [tripleo][manila] Ganesha deployment

I'm not really an expert on composable roles so I'll leave that to someone else, but see my thoughts inline on the networking aspect. On 04/10/2017 03:22 AM, Jan Provaznik wrote: 2) define a new VIP (for IP failover) and 2 networks for NfsStorage role: a) a frontend network between users an

Re: [openstack-dev] [tripleo][manila] Ganesha deployment

On 04/11/2017 02:00 PM, Giulio Fidente wrote: On Tue, 2017-04-11 at 16:50 +0200, Jan Provaznik wrote: On Mon, Apr 10, 2017 at 6:55 PM, Ben Nemec wrote: On 04/10/2017 03:22 AM, Jan Provaznik wrote: Well, on second thought it might be possible to make the Storage network only routable within

Re: [openstack-dev] [oslo][infra][pbr] Nominating Stephen Finucane for pbr-core

+1 On 04/12/2017 08:14 AM, Monty Taylor wrote: Hey all, As I'm sure you all know, pbr is both our most pervasively used dependency and our least well understood. Nobody ever wants to look at the code (sorry, I can write ugly code sometimes - but also wow setuptools) or dig in to figure out what

Re: [openstack-dev] [tripleo] pingtest vs tempest

On 04/17/2017 10:51 AM, Emilien Macchi wrote: We haven't got much feedback from TripleO core reviewers, who are usually more involved on this topic. I'll give a chance to let them talk because we take some actions based on the feedback brought in this discussion. I started to write a response

<    1   2   3   4   5   6   7   8   >