Re: [openstack-dev] [TripleO][CI] Bridging the production/CI workflow gap with large periodic CI jobs

On 04/17/2017 02:52 PM, Justin Kilpatrick wrote: Because CI jobs tend to max out about 5 nodes there's a whole class of minor bugs that make it into releases. What happens is that they never show up in small clouds, then when they do show up in larger testing clouds the people deploying those

Re: [openstack-dev] Development workflow for bunch of patches

On 04/19/2017 03:11 AM, Sławek Kapłoński wrote: Hello, I have a question about how to deal with bunch of patches which depends one on another. I did patch to neutron (https://review.openstack.org/#/c/449831/) which is not merged yet but I wanted to start also another patch which is depend on t

Re: [openstack-dev] [tripleo][release] release-model of tripleo-common

On 04/18/2017 10:29 PM, Steve Baker wrote: On Wed, Apr 19, 2017 at 1:14 PM, Doug Hellmann mailto:d...@doughellmann.com>> wrote: Excerpts from Steve Baker's message of 2017-04-19 13:05:37 +1200: > Other than being consumed as a library, tripleo-common is the home for a > numbe

Re: [openstack-dev] [TripleO][CI] Bridging the production/CI workflow gap with large periodic CI jobs

TLDR: We have the capacity to do this. One scale job can be absorbed into our existing test infrastructure with minimal impact. On 04/19/2017 07:50 AM, Flavio Percoco wrote: On 18/04/17 14:28 -0400, Emilien Macchi wrote: On Mon, Apr 17, 2017 at 3:52 PM, Justin Kilpatrick wrote: Because CI j

Re: [openstack-dev] [TripleO][CI] Bridging the production/CI workflow gap with large periodic CI jobs

te, but something along those lines should work. It may also need a larger controller flavor so the controller(s) don't OOM with that many computes, but if we've got a custom env for this use case anyway that should be doable too. On Wed, Apr 19, 2017 at 12:30 PM, Ben Nemec wrote

Re: [openstack-dev] [tripleo] Validations before upgrades and updates

On 05/08/2017 06:45 AM, Marios Andreou wrote: Hi folks, after some discussion locally with colleagues about improving the upgrades experience, one of the items that came up was pre-upgrade and update validations. I took an AI to look at the current status of tripleo-validations [0] and posted a

Re: [openstack-dev] [oslo][oslo.messaging] Call to deprecate the 'pika' driver in the oslo.messaging project

On 05/15/2017 01:55 PM, Doug Hellmann wrote: Excerpts from Davanum Srinivas (dims)'s message of 2017-05-15 14:27:36 -0400: On Mon, May 15, 2017 at 2:08 PM, Ken Giusti wrote: Folks, It was decided at the oslo.messaging forum at summit that the pika driver will be marked as deprecated [1] for

Re: [openstack-dev] [oslo][concurrency] lockutils lock fairness / starvation

On 05/15/2017 03:24 PM, Doug Hellmann wrote: Excerpts from Legacy, Allain's message of 2017-05-15 19:20:46 +: -Original Message- From: Doug Hellmann [mailto:d...@doughellmann.com] Sent: Monday, May 15, 2017 2:55 PM <...> Excerpts from Legacy, Allain's message of 2017-05-15 18:35

[openstack-dev] [tripleo] Sample Environment Generator

I've finally gotten back to working on this spec[1] and wanted to send a quick update. The patch series is updated with the changes we discussed at the PTG, and you can find the start of it here: https://review.openstack.org/#/c/253638/ Obviously there are a _lot_ of environments left to conv

Re: [openstack-dev] Security bug in diskimage-builder

On 05/17/2017 10:46 AM, Jeremy Stanley wrote: On 2017-05-17 15:57:16 +0300 (+0300), George Shuklin wrote: There is a bug in diskimage-builder I reported it at 2017-03-10 as 'private security'. I think this bug is a medium severity. So far there was no reaction at all. I plan to change this bu

Re: [openstack-dev] [TripleO] A proposal for hackathon to reduce deploy time of TripleO

On 05/23/2017 05:47 AM, Sagi Shnaidman wrote: Hi, all I'd like to propose an idea to make one or two days hackathon in TripleO project with main goal - to reduce deployment time of TripleO. - How could it be arranged? We can arrange a separate IRC channel and Bluejeans video conference sessi

Re: [openstack-dev] [requirements][tripleo][heat] Projects holding back requirements updates

Tagging with tripleo and heat teams for the os-*-config projects. I'm not sure which owns them now, but it sounds like we need a new release. On 05/22/2017 10:32 AM, Matthew Thode wrote: This is just a friendly reminder that without a release from master, if your project still caps a requireme

Re: [openstack-dev] [requirements][tripleo][heat] Projects holding back requirements updates

On 05/26/2017 04:22 AM, Steven Hardy wrote: On Thu, May 25, 2017 at 03:15:13PM -0500, Ben Nemec wrote: Tagging with tripleo and heat teams for the os-*-config projects. I'm not sure which owns them now, but it sounds like we need a new release. I think they're still owned by t

Re: [openstack-dev] [nova][scheduler] Anyone relying on the host_subset_size config option?

On 05/26/2017 12:17 PM, Edward Leafe wrote: [resending to include the operators list] The host_subset_size configuration option was added to the scheduler to help eliminate race conditions when two requests for a similar VM would be processed close together, since the scheduler’s algorithm w

[openstack-dev] [TripleO] Passing along some field feedback

Hi, As some of you may know, I have a weekly meeting with some of the Red Hat folks who are out in the field using TripleO to deploy OpenStack at customer sites. The past couple of weeks have been particularly interesting, so I thought I'd take a moment to disseminate the comments to the bro

Re: [openstack-dev] Security bug in diskimage-builder

On 05/30/2017 08:00 AM, Emilien Macchi wrote: On Mon, May 29, 2017 at 9:02 PM, Jeremy Stanley wrote: On 2017-05-29 15:43:43 +0200 (+0200), Emilien Macchi wrote: On Wed, May 24, 2017 at 7:45 PM, Ben Nemec wrote: [...] Emilien, I think we should create a tripleo-coresec group in launchpad

Re: [openstack-dev] [TripleO] custom configuration to overcloud fails second time

I think we would need to see what your custom config templates look like as well. Also note that it's generally not recommended to drop environment files from your deploy command unless you explicitly want to stop applying them. So if you applied myconfig_1.yaml and then later want to apply

Re: [openstack-dev] Security bug in diskimage-builder

On 05/30/2017 10:05 AM, Emilien Macchi wrote: On Tue, May 30, 2017 at 3:43 PM, Ben Nemec wrote: On 05/30/2017 08:00 AM, Emilien Macchi wrote: On Mon, May 29, 2017 at 9:02 PM, Jeremy Stanley wrote: On 2017-05-29 15:43:43 +0200 (+0200), Emilien Macchi wrote: On Wed, May 24, 2017 at 7

Re: [openstack-dev] Security bug in diskimage-builder

On 06/01/2017 11:31 AM, Jeremy Stanley wrote: On 2017-06-01 10:40:34 -0500 (-0500), Ben Nemec wrote: [...] Okay, so we're all set up, but now it appears we're all subscribed to every tripleo bug as well. I think oslo-coresec used to be the same way, but at some point it changed so

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

On 03/28/2017 05:01 PM, Ben Nemec wrote: Final (hopefully) update: All active compute nodes have been rebooted and things seem to be stable again. Jobs are even running a little faster, so I'm thinking this had a detrimental effect on performance too. I've set a reminder for

[openstack-dev] [TripleO] PSA: Please WIP your WIP patches

This makes it easier to filter them out when looking for wayward patches. Right now the list of 15 oldest reviews includes at least 5 WIP patches that weren't marked as such in Gerrit. For anyone who's not aware, to mark a patch WIP in Gerrit you set Workflow -1 on it. Anyone can do that to

Re: [openstack-dev] [tripleo] Ansible roles repo and how to inject them into the overcloud

On 06/07/2017 09:25 AM, Juan Antonio Osorio wrote: Hi folks! I would like to know if there are thoughts about where to put tripleo-specific ansible roles. I've been working lately on a role that would deploy ipsec tunnels for most networks in an overcloud [1]. And I think that would be quite us

Re: [openstack-dev] [tripleo] [ci] Adding idempotency job on overcloud deployment.

On 06/08/2017 10:16 AM, Emilien Macchi wrote: On Thu, Jun 8, 2017 at 1:47 PM, Sofer Athlan-Guyot wrote: Hi, Alex Schultz writes: On Wed, Jun 7, 2017 at 5:20 AM, Sofer Athlan-Guyot wrote: Hi, Emilien Macchi writes: On Wed, Jun 7, 2017 at 12:45 PM, Sofer Athlan-Guyot wrote: Hi, I d

Re: [openstack-dev] [tripleo] pike m2 has been released

Hmm, I was expecting an instack-undercloud release as part of m2. Is there a reason we didn't do that? On 06/08/2017 03:47 PM, Emilien Macchi wrote: We have a new release of TripleO, pike milestone 2. All bugs targeted on Pike-2 have been moved into Pike-3. I'll take care of moving the bluepr

Re: [openstack-dev] [heat] Making stack outputs static

On 06/09/2017 03:10 PM, Zane Bitter wrote: History lesson: a long, long time ago we made a very big mistake. We treated stack outputs as things that would be resolved dynamically when you requested them, instead of having values fixed at the time the template was created or updated. This makes

Re: [openstack-dev] [tripleo] pike m2 has been released

On 06/09/2017 05:39 PM, Emilien Macchi wrote: On Fri, Jun 9, 2017 at 5:01 PM, Ben Nemec wrote: Hmm, I was expecting an instack-undercloud release as part of m2. Is there a reason we didn't do that? You just released a new tag: https://review.openstack.org/#/c/471066/ with a new re

Re: [openstack-dev] [tripleo] pike m2 has been released

On 06/12/2017 02:10 PM, Emilien Macchi wrote: On Mon, Jun 12, 2017 at 7:20 PM, Ben Nemec wrote: On 06/09/2017 05:39 PM, Emilien Macchi wrote: On Fri, Jun 9, 2017 at 5:01 PM, Ben Nemec wrote: Hmm, I was expecting an instack-undercloud release as part of m2. Is there a reason we didn&#

Re: [openstack-dev] [tripleo][ci] TripleO OVB check gates to move to third party

On 06/12/2017 06:19 PM, Ronelle Landy wrote: Greetings, TripleO OVB check gates are managed by upstream Zuul and executed on nodes provided by test cloud RH1. RDO Cloud is now available as a test cloud to be used when running CI jobs. To utilize to RDO Cloud, we could either: - continue t

Re: [openstack-dev] [heat] Making stack outputs static

On 06/12/2017 03:53 PM, Zane Bitter wrote: On 12/06/17 16:21, Steven Hardy wrote: I think we wanted to move to convergence anyway so I don't see a problem with this. I know there was some discussion about starting to test with convergence in tripleo-ci, does anyone know what, if anything, hap

Re: [openstack-dev] [tripleo][ci] TripleO OVB check gates to move to third party

On 06/13/2017 12:28 PM, Paul Belanger wrote: On Tue, Jun 13, 2017 at 11:12:08AM -0500, Ben Nemec wrote: On 06/12/2017 06:19 PM, Ronelle Landy wrote: Greetings, TripleO OVB check gates are managed by upstream Zuul and executed on nodes provided by test cloud RH1. RDO Cloud is now available

Re: [openstack-dev] [tc][fuel] Making Fuel a hosted project

Full disclosure: I primarily work on TripleO so I do have a horse in this race. On 06/15/2017 10:33 AM, Jay Pipes wrote: On 06/15/2017 10:35 AM, Jeremy Stanley wrote: On 2017-06-15 10:48:21 +0200 (+0200), Thierry Carrez wrote: [...] I think that, despite the efforts of the Fuel team, Fuel did

Re: [openstack-dev] [tc][fuel] Making Fuel a hosted project

On 06/15/2017 11:05 AM, Jay Pipes wrote: On 06/15/2017 11:56 AM, Ben Nemec wrote: Full disclosure: I primarily work on TripleO so I do have a horse in this race. On 06/15/2017 10:33 AM, Jay Pipes wrote: On 06/15/2017 10:35 AM, Jeremy Stanley wrote: On 2017-06-15 10:48:21 +0200 (+0200

Re: [openstack-dev] [nova] bug triage experimentation

On 06/23/2017 11:52 AM, Sean Dague wrote: The Nova bug backlog is just over 800 open bugs, which while historically not terrible, remains too large to be collectively usable to figure out where things stand. We've had a few recent issues where we just happened to discover upgrade bugs filed 4 m

[openstack-dev] [TripleO] Pt. 2 of Passing along some field feedback

A few weeks later than I had planned, but here's the other half of the field feedback I mentioned in my previous email: * They very emphatically want in-place upgrades to work when moving from non-containerized to containerized. I think this is already the plan, but I told them I'd make sure

Re: [openstack-dev] [TripleO][keystone] Pt. 2 of Passing along some field feedback

On 06/28/2017 02:47 PM, Lance Bragstad wrote: On 06/28/2017 02:29 PM, Fox, Kevin M wrote: I think everyone would benefit from a read-only role for keystone out of the box. Can we get this into keystone rather then in the various distro's? Yeah - I think that would be an awesome idea. John

Re: [openstack-dev] [TripleO] Pt. 2 of Passing along some field feedback

On 06/28/2017 03:03 PM, Steven Hardy wrote: On Wed, Jun 28, 2017 at 8:06 PM, Ben Nemec wrote: A few weeks later than I had planned, but here's the other half of the field feedback I mentioned in my previous email: * They very emphatically want in-place upgrades to work when moving fro

Re: [openstack-dev] [tripleo] Plan description in the create/update plan form

On 06/29/2017 07:25 AM, Ana Krivokapic wrote: Resending with the [tripleo] tag, sorry... On Thu, Jun 29, 2017 at 2:22 PM, Ana Krivokapic mailto:akriv...@redhat.com>> wrote: Hi TripleO devs, I am working on adding a description field to the "Crate Plan" form in the TripleO UI [1].

Re: [openstack-dev] [TripleO][keystone] Pt. 2 of Passing along some field feedback

_______ From: Ben Nemec [openst...@nemebean.com] Sent: Wednesday, June 28, 2017 12:06 PM To: OpenStack Development Mailing List (not for usage questions) Subject: [openstack-dev] [TripleO] Pt. 2 of Passing along some field feedback A few weeks later than I had planned, but here's th

Re: [openstack-dev] [tripleo] [ui] Integration testing in tripleo-ci

On 07/05/2017 10:21 AM, Emilien Macchi wrote: On Wed, Jul 5, 2017 at 7:57 AM, Florian Fuchs wrote: On Tue, Jul 4, 2017 at 7:48 PM, Emilien Macchi wrote: On Fri, Jun 30, 2017 at 10:51 AM, Honza Pokorny wrote: I'd like to write some integration tests for the TripleO UI. Simple configuratio

Re: [openstack-dev] [tripleo] weekly meetings on #tripleo

I don't have a particularly strong opinion one way or another (probably because I tend to skip most of the meetings lately anyway...), but some thoughts inline. On 07/05/2017 11:56 AM, Emilien Macchi wrote: After reading http://lists.openstack.org/pipermail/openstack-dev/2017-June/118899.html

Re: [openstack-dev] [tripleo] proposing Alex Schultz tripleo-core in all projects

+1 for sure On 07/07/2017 12:39 PM, Emilien Macchi wrote: Alex has demonstrated high technical and community skills in TripleO - where he's already core on THT, instack-undercloud, and puppet-tripleo - but also very involved in other repos. I propose that we extend his core status to all TripleO

Re: [openstack-dev] [TripleO] Migration from Neutron ML2OVS to OVN

On 07/11/2017 10:17 AM, Numan Siddique wrote: Hello Tripleo team, I have few questios regarding migration from neutron ML2OVS to OVN. Below are some of the requirements - We want to migrate an existing depoyment from Neutroon default ML2OVS to OVN - We are targetting this for tripleo

Re: [openstack-dev] [oslo] scheduling oslosphinx for retirement at the start of queens

+1 On 07/10/2017 08:10 AM, Doug Hellmann wrote: Oslo team, With all documentation now moving to use the openstackdocs theme, I propose that we retire the oslosphinx repository during Queens. We should go ahead and create the stable/pike branch at the end of this cycle, so that we have a way to

Re: [openstack-dev] [TripleO] Let's use Ansible to deploy OpenStack services on Kubernetes

On 07/14/2017 11:43 AM, Joshua Harlow wrote: Out of curiosity, since I keep on hearing/reading all the tripleo discussions on how tripleo folks are apparently thinking/doing? redesigning the whole thing to use ansible + mistral + heat, or ansible + kubernetes or ansible + mistral + heat + ans

Re: [openstack-dev] [TripleO] Migration from Neutron ML2OVS to OVN

On 07/18/2017 08:18 AM, Numan Siddique wrote: On Thu, Jul 13, 2017 at 3:02 PM, Saravanan KR <mailto:skram...@redhat.com>> wrote: On Tue, Jul 11, 2017 at 11:40 PM, Ben Nemec mailto:openst...@nemebean.com>> wrote: > > > On 07/11/2017 10:17

Re: [openstack-dev] [tripleo][tripleo-heat-template] how to get interface name from network name in service profile

On 07/25/2017 09:53 PM, Zenghui Shi wrote: Hi, Could anyone shed some light on how to get the physical interface name (e.g eth0) from network name (e.g PublicNetwork, ExternalNetwork) in tripleo-heat-template service profile ? for example: I want to add a service profile under puppet/serv

Re: [openstack-dev] [oslo][oslo.db] nominating Jay Pipes for oslo-db-core

+1, always happy to have more contributors, especially to projects like oslo.db that almost everyone uses. On 07/27/2017 09:04 AM, Doug Hellmann wrote: I have noticed that Jay has been very deeply involved in several recent design discussions about oslo.db, and he obviously has a great deal of

Re: [openstack-dev] [TripleO][Heat] using convergence_engine to deploy overcloud stack

On 08/09/2017 05:49 AM, Rabi Mishra wrote: On Wed, Aug 9, 2017 at 1:41 PM, Smigielski, Radoslaw (Nokia - IE) mailto:radoslaw.smigiel...@nokia.com>> wrote: Hi there! I have a question about heat "convergence_engine" option, it's present in heat config since quite a long time

Re: [openstack-dev] [oslo][oslo.messaging] Proposing Andy Smith as an oslo.messaging core reviewers

+1 On 08/14/2017 05:59 AM, ChangBo Guo wrote: I propose that we add Andy Smith to the oslo.messaging team. Andy Smith has been actively contributing to oslo.messaging for a while now, both in helping make oslo.messaging better via code contribution(s) and by helping with the review load when

Re: [openstack-dev] [TripleO][CI] FreeIPA Deployment

On 08/21/2017 01:45 AM, Juan Antonio Osorio wrote: The second option seems like the most viable. Not sure how the TripleO integration would go though. Care to elaborate on what you had in mind? I can't remember if we discussed this when we were first implementing the ci job, but could FreeIP

Re: [openstack-dev] [tripleo] add mistral to the auto-update package list for TripleO CI

I think I'm +0 on this. On the one hand we do have the gating job on Mistral, on the other hand our gate jobs don't exercise all of the functionality of some projects, especially Mistral. I know in the past introspection has been broken by changes in Mistral, and that wouldn't be caught by ga

Re: [openstack-dev] [tripleo] Add support for Neutron NSX driver

On 09/04/2017 11:50 PM, Emilien Macchi wrote: On Fri, Sep 1, 2017 at 2:37 PM, Tong Liu wrote: Hi, In pike release, we added supported for Neutron NSX driver in TripleO [1] by the following patches. This will enable TripleO overcloud deployment to use vmware_nsx as Neutron core_plugin. https:

Re: [openstack-dev] [nova] [neutron] Should we continue providing FQDNs for instance hostnames?

On 09/04/2017 07:48 AM, Stephen Finucane wrote: On Mon, 2017-09-04 at 11:51 +, Gary Kotton wrote: On 9/4/17, 11:18 AM, "Stephen Finucane" wrote: Nova has a feature whereby it will provide instance host names that cloud- init can extract and use inside the guest, i.e. this won't happe

Re: [openstack-dev] [nova] [neutron] Should we continue providing FQDNs for instance hostnames?

On 09/06/2017 04:40 AM, Stephen Finucane wrote: On Tue, 2017-09-05 at 12:30 -0500, Ben Nemec wrote: On 09/04/2017 07:48 AM, Stephen Finucane wrote: On Mon, 2017-09-04 at 11:51 +, Gary Kotton wrote: On 9/4/17, 11:18 AM, "Stephen Finucane" wrote: Nova has a feature where

Re: [openstack-dev] [TripleO][DIB] how create triplo overcloud image with latest kernel?

On 09/26/2017 05:43 AM, Moshe Levi wrote: Hi all, As part of the OVS Hardware Offload [1] [2], we need to create new Centos/Redhat 7 image with latest kernel/ovs/iproute. We tried to use virsh-customize to install the packages and we were able to update iproute and ovs, but for the kerne

Re: [openstack-dev] [tripleo] Newton End-Of-Life (EOL) next month (reminder #1)

On 09/27/2017 11:39 AM, Alex Schultz wrote: On Tue, Sep 26, 2017 at 11:57 PM, Tony Breeds wrote: On Tue, Sep 26, 2017 at 10:31:59PM -0700, Emilien Macchi wrote: On Tue, Sep 26, 2017 at 10:17 PM, Tony Breeds wrote: With that in mind I'd suggest that your review isn't appropriate for If we

Re: [openstack-dev] [tripleo] Newton End-Of-Life (EOL) next month (reminder #1)

On 09/27/2017 08:13 PM, Tony Breeds wrote: On Wed, Sep 27, 2017 at 03:35:43PM -0500, Ben Nemec wrote: It's a little weird because essentially we want to provide a higher level of support for stable branches than most of OpenStack. My understanding is that a lot of the current s

Re: [openstack-dev] [ptg] Simplification in OpenStack

On 09/26/2017 09:13 PM, Rochelle Grober wrote: Clint Byrum wrote: Excerpts from Jonathan Proulx's message of 2017-09-26 16:01:26 -0400: On Tue, Sep 26, 2017 at 12:16:30PM -0700, Clint Byrum wrote: :OpenStack is big. Big enough that a user will likely be fine with learning :a new set of tools

Re: [openstack-dev] [ocata] [nova-api] Nova api stopped working after a yum update

You may want to ask this on rdo-list, assuming RDO is where you got your packages: https://www.redhat.com/mailman/listinfo/rdo-list Generally speaking, a minor update like that should not bring in any new required configuration options. On 09/27/2017 04:51 AM, Avery Rozar wrote: Hello all, I

Re: [openstack-dev] [all][oslo] Retiring openstack/pylockfile

+1. I believe the work we had originally intended to put into pylockfile ended up in the fasteners library instead. On 09/29/2017 10:07 PM, ChangBo Guo wrote: pylockfile was deprecated about two years ago in [1] and it is not used in any OpenStack Projects now [2] , we would like to retire i

Re: [openstack-dev] [nova] key_pair update on rebuild (a whole lot of conversations)

On 10/03/2017 03:16 PM, Sean Dague wrote: = Where I think we are? = I think with all this data we're at the following: Q: Should we add this to rebuild A: Yes, probably - after some enhancement to the spec * * - we really should have much better use cases about the situations it is expected

Re: [openstack-dev] [nova] Should we make rebuild + new image on a volume-backed instance fail fast?

On 10/06/2017 12:22 PM, Matt Riedemann wrote: This came up in IRC discussion the other day, but we didn't dig into it much given we were all (2 of us) exhausted talking about rebuild. But we have had several bugs over the years where people expect the root disk to change to a newly supplied

Re: [openstack-dev] [tripleo] blockquotes in docs

On 10/06/2017 03:01 AM, Markus Zoeller wrote: Just a short reminder that rst puts stuff in blockquotes when you're not careful with the spacing. Example: * item 1 * item 2 That's in blockquotes because of the 1 blank at the beginning. The TripleO docs are full with them, which looks a bit

[openstack-dev] [Oslo][Designate][Congress] Problem with from_dict overrides and new oslo.context release

Hi, I brought up the fix[1] I proposed for [2] in the Oslo meeting today, and it led to some good discussion that we wanted to take to a broader audience. In particular, the projects that are affected by the bug. The oslo.context change I proposed would essentially obsolete the from_dict fu

Re: [openstack-dev] [Oslo][Designate][Congress] Problem with from_dict overrides and new oslo.context release

On 10/10/2017 07:14 AM, Graham Hayes wrote: On 09/10/17 18:03, Ben Nemec wrote: Hi, I brought up the fix[1] I proposed for [2] in the Oslo meeting today, and it led to some good discussion that we wanted to take to a broader audience. In particular, the projects that are affected by the

Re: [openstack-dev] [masakari]oslo.context 2.19.1 is currently blocked

Can you add masakari to https://bugs.launchpad.net/oslo.context/+bug/1721432 so we don't miss it in the process of fixing this problem? At some point we will be releasing a new oslo.context and we need to make sure we get all the broken projects fixed before then. Thanks. -Ben On 10/17/201

Re: [openstack-dev] [TripleO][infra][CI] Moving OVB jobs from RH1 cloud to RDO cloud, plan

Overall sounds good. A couple of comments inline. On 10/23/2017 05:46 AM, Sagi Shnaidman wrote: Hi, as you know we prepare transition of all OVB jobs from RH1 cloud to RDO cloud, also a few long multinode upgrades jobs as well. We prepared a workflow of transition below, please feel free to

[openstack-dev] [tripleo] rh1 outage today

Hi all, As you may or may not have noticed all ovb jobs on rh1 started failing sometime last night. After some investigation today I found a few issues. First, our nova db archiving wasn't working. This was due to the auto-increment counter issue described by melwitt in http://lists.openst

Re: [openstack-dev] [tripleo] rh1 outage today

On 10/28/2017 02:07 AM, Juan Antonio Osorio wrote: Thanks for the postmortem; it's always a good read tp learn stuff :) On 28 Oct 2017 00:11, "Ben Nemec" <mailto:openst...@nemebean.com>> wrote: Hi all, As you may or may not have noticed all ovb jobs on rh1 star

Re: [openstack-dev] [tripleo] rh1 outage today

On 10/30/2017 05:14 PM, Ben Nemec wrote: It turns out this wasn't _quite_ resolved yet. I was still seeing some excessively long stack creation times today and it turns out one of our compute nodes had virtualization turned off. This caused all of its instances to fail and need a

Re: [openstack-dev] [oslo][tripleo][puppet] Logging format: let's discuss a bit about default format, format configuration and so on

Adding tags for the relevant projects. I _think_ this is mostly directed at Puppet/TripleO, but Oslo is obviously relevant as well. On 11/01/2017 08:54 AM, Cédric Jeanneret wrote: Dear Stackers, While working on my locally deployed Openstack (Pike using TripleO), I was a bit struggling with t

Re: [openstack-dev] [tripleo] When to use parameters vs parameter_defaults

On 11/10/2017 03:20 AM, Giulio Fidente wrote: On 11/26/2015 03:17 PM, Jiří Stránský wrote: On 26.11.2015 14:12, Jiří Stránský wrote: [...] It seems TripleO is hitting similar composability and sanity limits with the top-down approach, and the number of parameters which can only be fed via

Re: [openstack-dev] [Tripleo] Composable role OVS-DPDK compute node with single NIC

Your configuration lost all of its indentation, which makes it extremely difficult to read. Can you try sending it a different way, maybe paste.openstack.org? On 11/16/2017 02:43 AM, Samuel Monderer wrote: Hi, I managed to deploy a compute node with ovs-dpdk using two NICs. The first for th

Re: [openstack-dev] [Tripleo] Composable role OVS-DPDK compute node with single NIC

7/ On Tue, Nov 21, 2017 at 8:22 PM Ben Nemec <mailto:openst...@nemebean.com>> wrote: Your configuration lost all of its indentation, which makes it extremely difficult to read.  Can you try sending it a different way, maybe paste.openstack.org <http://paste.openstack.org&g

Re: [openstack-dev] [tacker] [hacking] [requirements] pep8 to pycodestyle

It's probably worth noting here that this is to reflect an upstream rename from pep8 to pycodestyle, not an actual change in the library we use for style checking. It's mentioned in the commit messages, but for anyone just scanning the mailing list it may not be obvious. I left a review on th

Re: [openstack-dev] [tripleo] TripleO CI end of sprint status

On 12/15/2017 10:26 AM, Emilien Macchi wrote: On Fri, Dec 15, 2017 at 5:04 AM, Arx Cruz wrote: [...] The goal on this sprint was to enable into quickstart a way to reproduce upstream jobs, in your personal RDO cloud tenant, making easy to developers to debug and reproduce their code. This p

[openstack-dev] [TripleO] Tis the season...for a cloud reboot

Hi, It's that magical time again. You know the one, when we reboot rh1 to avoid OVS port exhaustion. :-) If all goes well you won't even notice that this is happening, but there is the possibility that a few jobs will fail while the te-broker host is rebooted so I wanted to let everyone kno

Re: [openstack-dev] [tripleo] Removing old baremetal commands from python-tripleoclient

On 12/17/2017 05:55 PM, Tony Breeds wrote: On Fri, Dec 15, 2017 at 01:04:52PM +0100, Dmitry Tantsur wrote: On 12/15/2017 04:49 AM, Tony Breeds wrote: Hi All, In review I01837a9daf6f119292b5a2ffc361506925423f11 I updated ValidateInstackEnv to handle the case when then instackenv.json fil

Re: [openstack-dev] [TripleO] Tis the season...for a cloud reboot

On 12/19/2017 02:43 PM, Brian Haley wrote: On 12/19/2017 11:53 AM, Ben Nemec wrote: The reboot is done (mostly...see below). On 12/18/2017 05:11 PM, Joe Talerico wrote: Ben - Can you provide some links to the ovs port exhaustion issue for some background? I don't know if we ever had

Re: [openstack-dev] [TripleO] Tis the season...for a cloud reboot

On 12/19/2017 05:34 PM, Joe Talerico wrote: On Tue, Dec 19, 2017 at 5:45 PM, Derek Higgins wrote: On 19 December 2017 at 22:23, Brian Haley wrote: On 12/19/2017 04:00 PM, Ben Nemec wrote: On 12/19/2017 02:43 PM, Brian Haley wrote: On 12/19/2017 11:53 AM, Ben Nemec wrote: The

Re: [openstack-dev] [TripleO][Off topic] Merry Christmas to everyone!

I kind of want an owl ornament now. :-) On 12/20/2017 05:42 AM, Carlos Camacho Gonzalez wrote: Hello everyone! Thank you for all your effort and support this year making a better product for our users. I hope you enjoy this holiday time. Here you have a digital TripleO Christmas card :) Mer

Re: [openstack-dev] [oslo] Oslo team updates

A regretful +1. On 01/01/2018 09:53 PM, ChangBo Guo wrote: In last two cycles some people's situation changed, can't focus on Oslo code review, so I propose  some changes in Oslo team.  Remove following people, thanks their past hard wok to make Oslo well, and welcome them back if they want to

Re: [openstack-dev] [tripleo] containers-multinode is broken, what's our plan

This is a situation where having temprevert/pin/cherrypick functionality again would have been really helpful. I realize that doesn't help in the immediate circumstance, but it's something to consider for the future. On 01/02/2018 10:05 PM, Emilien Macchi wrote: Mistral broke us with https://

Re: [openstack-dev] [oslo] proposing Stephen Finucan for oslo-core

Definite +1 On 01/08/2018 08:55 AM, Doug Hellmann wrote: Stephen (sfinucan) has been working on pbr, oslo.config, and oslo.policy and reviewing several of the other Oslo libraries for a while now. His reviews are always helpful and I think he would make a good addition to the oslo-core team. As

Re: [openstack-dev] [tripleo] storyboard evaluation

On 01/16/2018 08:55 AM, Emilien Macchi wrote: Hey folks, Alex and I spent a bit of time to look at Storyboard, as it seems that some OpenStack projects are migrating from Launchpad to Storyboard. I created a dev instance of storyboard and imported all bugs from TripleO so we could have a look

Re: [openstack-dev] Many timeouts in zuul gates for TripleO

On 01/18/2018 09:45 AM, Emilien Macchi wrote: On Thu, Jan 18, 2018 at 6:34 AM, Or Idgar wrote: Hi, we're encountering many timeouts for zuul gates in TripleO. For example, see http://logs.openstack.org/95/508195/28/check-tripleo/tripleo-ci-centos-7-ovb-ha-oooq/c85fcb7/. rechecks won't help a

Re: [openstack-dev] [infra][all] New Zuul Depends-On syntax

On 01/24/2018 02:31 PM, Monty Taylor wrote: On 01/24/2018 02:25 PM, David Shrewsbury wrote: This is a (the?) killer feature. On Wed, Jan 24, 2018 at 11:33 AM, James E. Blair > wrote:     Hi,     We recently introduced a new URL-based syntax for Depends-On: foot

Re: [openstack-dev] [TripleO][docs]: Undercloud install fails with unavailability of oslo::cache

On 07/08/2016 12:27 PM, Paddu Krishnan (padkrish) wrote: > Thanks a lot for the reply. Pls see inline.. > > On 7/8/16, 7:47 AM, "Ben Nemec" wrote: > >> On 07/08/2016 12:58 AM, Paddu Krishnan (padkrish) wrote: >>>> Hello, >>>> I am trying

Re: [openstack-dev] [TripleO][os-net-config] add support for NFV virtual switch

On 07/07/2016 05:45 PM, Xin Wu wrote: > Hi, > > This is Xin from Big Switch. I'm proposing to make os_net_config support > DPDK switch for NFV workloads. > Current os_net_config supports ovs_bridge, linux_bridge, ivs_bridge > and different types of interfaces. The os_net_config's abstraction

Re: [openstack-dev] [DIB] [Ironic] [TripleO] Moving IPA element out of DIB tree

I think this probably makes sense, but some more thoughts inline. On 07/15/2016 03:13 PM, Stephane Miller wrote: > To better support diskimage-builder based IPA images going forward, we'd > like to move the ironic-agent element into the ironic-python-agent > repository. This will involve: > > - I

Re: [openstack-dev] [TripleO] tripleo-common bugs, bug tracking and launchpad tags

On 07/18/2016 06:28 AM, Julie Pichon wrote: > Hi, > > On Friday Dougal mentioned on IRC that he hadn't realised there was a > separate project for tripleo-common bugs on Launchpad [1] and that he'd > been using the TripleO main tracker [2] instead. > > Since the TripleO tracker is also used for c

Re: [openstack-dev] [tripleo] moving tripleo-ci/test-environments into THT

On 07/21/2016 11:31 AM, Steven Hardy wrote: > On Wed, Jul 20, 2016 at 10:32:23PM -0400, Emilien Macchi wrote: >> Hi, >> >> We're currently using tripleo-ci to store our test-environments files >> (ie: multinode.yaml, etc). >> To make it compatible with our different versions of TripleO, we have 2

[openstack-dev] [all][summit] Responding to questions on submitted summit talk?

Hi, I got a question from one of the track chairs on my presentation, but the email came from a noreply address and I don't see anywhere on the submission page that I can respond to feedback. How are we supposed to do that? Thanks. -Ben _

Re: [openstack-dev] [all][summit] Responding to questions on submitted summit talk?

l to summit [at] openstack [dot] org > <mailto:sum...@openstack.org> as required. > > On 7/25/16 10:55 AM, Ben Nemec wrote: >> Hi, >> >> I got a question from one of the track chairs on my presentation, but >> the email came from a noreply address and I don&#

Re: [openstack-dev] [Openstack-track-chairs] [all][summit] Responding to questions on submitted summit talk?

; Thanks for letting us know. >> Cheers, >> Uli >> >> -Original Message- >> From: Ben Nemec [mailto:openst...@nemebean.com] >> Sent: Monday, 25 July, 2016 17:32 >> To: Nikhil Komawar; OpenStack Development Mailing List (not for usage >

Re: [openstack-dev] [TripleO] [UI] Version

On 07/27/2016 11:13 AM, Dougal Matthews wrote: > > > On Wednesday, 27 July 2016, Steven Hardy > wrote: > > On Wed, Jul 27, 2016 at 02:08:08PM +0100, Dougal Matthews wrote: > >On 27 July 2016 at 12:41, Honza Pokorny > wrote: > > > > Hello f

Re: [openstack-dev] [TripleO][DIB] Proposal to move DIB to its own project team

As I noted in the meeting yesterday, I think the lack of response from TripleO regarding this topic is kind of answer enough. TripleO has moved away from having a heavy dependency on diskimage-builder (it's basically used to install some packages and a handful of elements that we haven't been able

Re: [openstack-dev] [tripleo] Progress on overcloud upgrade / update jobs

On 08/05/2016 12:58 PM, Steven Hardy wrote: > On Thu, Aug 04, 2016 at 09:46:20PM -0400, Emilien Macchi wrote: >> Hi, >> >> I'm currently working by iteration to get a new upstream job that test >> upgrades and update. >> Until now, I'm doing baby steps. I bootstrapped the work to upgrade >> undercl

Re: [openstack-dev] [infra][tripleo] status of tripleo-test-cloud-rh1

On 08/06/2016 07:17 PM, Paul Belanger wrote: > Greetings, > > 5 months ago fungi posted: > > [tripleo] becoming third party CI (was: enabling third party CI)[1] > > About having the discussion whether the existing TripleO CI should itself > follow > our third-party integration model instead o

[openstack-dev] [TripleO] Network Template Generator

This is something that has existed for a while, but I had been hesitant to evangelize it until it was a little more proven. At this point I've used it to generate templates for a number of different environments, and it has worked well. I decided it was time to record another demo and throw it ou

<    1   2   3   4   5   6   7   8   >