[openstack-dev] [tripleo] CI / Tempest Sprint 11 Summary

Greetings, The TripleO squads for CI and Tempest have just completed Sprint 11. The following is a summary of activities during this sprint. The newly formed Tempest Squad has completed its first sprint. Details on the team structure can be found in the spec [1]. Sprint 11 Epic (CI Squad):

Re: [openstack-dev] [tripleo] Recap of Python 3 testing session at PTG

On Fri, Apr 13, 2018 at 9:37 AM, Victor Stinner wrote: > 2018-04-13 15:07 GMT+02:00 Thomas Goirand : > > BTW, any progress on upstream Swift WRT Py3 support? > > There is a voting Python 3.4 gate which runs 902 unit tests. The > Python 2.7 gate runs 5,902

Re: [openstack-dev] [tripleo] Recap of Python 3 testing session at PTG

2018-04-13 15:07 GMT+02:00 Thomas Goirand : > BTW, any progress on upstream Swift WRT Py3 support? There is a voting Python 3.4 gate which runs 902 unit tests. The Python 2.7 gate runs 5,902 unit tests. I compute that 15% of unit tests pass on Python 3.4. I tested locally with

Re: [openstack-dev] [tripleo] Recap of Python 3 testing session at PTG

On 04/13/2018 02:48 PM, Thomas Goirand wrote: > On 03/17/2018 09:34 AM, Emilien Macchi wrote: >> ## Challenges >> >> - Some services aren't fully Python 3 > > To my experience switching everything to Py3 in Debian, the only issues > were: > > - manila-ui > - networking-mlnx Of course, I also

Re: [openstack-dev] [tripleo] Recap of Python 3 testing session at PTG

2018-04-13 14:48 GMT+02:00 Thomas Goirand : > On 03/17/2018 09:34 AM, Emilien Macchi wrote: >> ## Challenges >> >> - Some services aren't fully Python 3 > > To my experience switching everything to Py3 in Debian, the only issues > were: > > - manila-ui > - networking-mlnx What

Re: [openstack-dev] [tripleo] Recap of Python 3 testing session at PTG

On 03/17/2018 09:34 AM, Emilien Macchi wrote: > ## Challenges > > - Some services aren't fully Python 3 To my experience switching everything to Py3 in Debian, the only issues were: - manila-ui - networking-mlnx The Melanox driver will probably be dropped from Debian, so the only collateral is

Re: [openstack-dev] [tripleo] Recap of Python 3 testing session at PTG

On Tue, Mar 20, 2018 at 10:28 AM, Javier Pena wrote: > One point we should add here: to test Python 3 we need some base operating system to work on. For now, our plan is to create a set of stabilized Fedora 28 repositories and use them only for CI jobs. See [1] for details on

Re: [openstack-dev] [tripleo] roadmap on containers workflow

On Thu, Apr 12, 2018 at 1:16 AM, Bogdan Dobrelya wrote: [...] > Deploy own registry as part of UC deployment or use external. For >> instance, for production use I would like to have a cluster of 3-5 >> registries with HAProxy in front to speed up 1k nodes deployments. >> >

Re: [openstack-dev] [tripleo] roadmap on containers workflow

On Thu, Apr 12, 2018 at 1:08 AM, Sergii Golovatiuk wrote: [...] > > One of the great outcomes of this blueprint is that in Rocky, the > operator > > won't have to run all the "openstack overcloud container" commands to > > prepare the container registry and upload the

Re: [openstack-dev] [tripleo][ui] Dependency management

On 2 March 2018 at 22:52, Alan Pevec wrote: > On Mon, Jan 22, 2018 at 9:30 AM, Julie Pichon wrote: >> On 19 January 2018 at 18:43, Honza Pokorny wrote: >>> We've recently discovered an issue with the way we handle dependencies for >>>

Re: [openstack-dev] [tripleo] roadmap on containers workflow

On 4/12/18 12:38 AM, Steve Baker wrote: On 11/04/18 12:50, Emilien Macchi wrote: Greetings, Steve Baker and I had a quick chat today about the work that is being done around containers workflow in Rocky cycle. If you're not familiar with the topic, I suggest to first read the blueprint

Re: [openstack-dev] [tripleo] roadmap on containers workflow

On 4/12/18 12:38 AM, Steve Baker wrote: On 11/04/18 12:50, Emilien Macchi wrote: Greetings, Steve Baker and I had a quick chat today about the work that is being done around containers workflow in Rocky cycle. If you're not familiar with the topic, I suggest to first read the blueprint

Re: [openstack-dev] [tripleo] roadmap on containers workflow

On 4/12/18 10:08 AM, Sergii Golovatiuk wrote: Hi, Thank you very much for brining up this topic. On Wed, Apr 11, 2018 at 2:50 AM, Emilien Macchi wrote: Greetings, Steve Baker and I had a quick chat today about the work that is being done around containers workflow in

Re: [openstack-dev] [tripleo] roadmap on containers workflow

On 4/12/18 12:38 AM, Steve Baker wrote: On 11/04/18 12:50, Emilien Macchi wrote: Greetings, Steve Baker and I had a quick chat today about the work that is being done around containers workflow in Rocky cycle. If you're not familiar with the topic, I suggest to first read the blueprint

Re: [openstack-dev] [tripleo] roadmap on containers workflow

Hi, Thank you very much for brining up this topic. On Wed, Apr 11, 2018 at 2:50 AM, Emilien Macchi wrote: > Greetings, > > Steve Baker and I had a quick chat today about the work that is being done > around containers workflow in Rocky cycle. > > If you're not familiar with

Re: [openstack-dev] [tripleo] roadmap on containers workflow

On 11/04/18 12:50, Emilien Macchi wrote: Greetings, Steve Baker and I had a quick chat today about the work that is being done around containers workflow in Rocky cycle. If you're not familiar with the topic, I suggest to first read the blueprint to understand the context here:

Re: [openstack-dev] [tripleo] roadmap on containers workflow

On 12/04/18 00:58, Wesley Hayutin wrote: On Tue, 10 Apr 2018 at 20:51 Emilien Macchi > wrote: Greetings, Steve Baker and I had a quick chat today about the work that is being done around containers workflow in Rocky cycle.

Re: [openstack-dev] [tripleo] roadmap on containers workflow

On 04/11/2018 07:58 AM, Wesley Hayutin wrote: On Tue, 10 Apr 2018 at 20:51 Emilien Macchi > wrote: Greetings, Steve Baker and I had a quick chat today about the work that is being done around containers workflow in Rocky cycle.

Re: [openstack-dev] [tripleo] roadmap on containers workflow

On Tue, 10 Apr 2018 at 20:51 Emilien Macchi wrote: > Greetings, > > Steve Baker and I had a quick chat today about the work that is being done > around containers workflow in Rocky cycle. > > If you're not familiar with the topic, I suggest to first read the > blueprint to

Re: [openstack-dev] [tripleo] The Weekly Owl - 16th Edition

On Tue, 10 Apr 2018 at 19:24 Emilien Macchi wrote: > Note: this is the sixteenth edition of a weekly update of what happens in > TripleO. > The goal is to provide a short reading (less than 5 minutes) to learn > where we are and what we're doing. > Any contributions and

[openstack-dev] [tripleo] roadmap on containers workflow

Greetings, Steve Baker and I had a quick chat today about the work that is being done around containers workflow in Rocky cycle. If you're not familiar with the topic, I suggest to first read the blueprint to understand the context here:

[openstack-dev] [tripleo] The Weekly Owl - 16th Edition

Note: this is the sixteenth edition of a weekly update of what happens in TripleO. The goal is to provide a short reading (less than 5 minutes) to learn where we are and what we're doing. Any contributions and feedback are welcome. Link to the previous version:

Re: [openstack-dev] [tripleo][ci] use of tags in launchpad bugs

Thanks for the clarifications about official tags. I was the one creating random/non-official tags for tripleo bugs. Although this may be annoying for some people, it helped me while ruckering/rovering CI to open unique bugs and avoid dups for the first time(s). There isn't a standard way of

Re: [openstack-dev] [tripleo][ci] use of tags in launchpad bugs

On 5.4.2018 21:04, Alex Schultz wrote: On Thu, Apr 5, 2018 at 12:55 PM, Wesley Hayutin wrote: FYI... This is news to me so thanks to Emilien for pointing it out [1]. There are official tags for tripleo launchpad bugs. Personally, I like what I've seen recently with some

Re: [openstack-dev] [tripleo][ci] use of tags in launchpad bugs

On Thu, Apr 5, 2018 at 12:55 PM, Wesley Hayutin wrote: > FYI... > > This is news to me so thanks to Emilien for pointing it out [1]. > There are official tags for tripleo launchpad bugs. Personally, I like what > I've seen recently with some extra tags as they could be

[openstack-dev] [tripleo][ci] use of tags in launchpad bugs

FYI... This is news to me so thanks to Emilien for pointing it out [1]. There are official tags for tripleo launchpad bugs. Personally, I like what I've seen recently with some extra tags as they could be helpful in finding the history of particular issues. So hypothetically would it be "wrong"

Re: [openstack-dev] [TripleO][ci][ceph] switching to config-download by default

On Thu, Apr 5, 2018 at 10:38 AM, James Slagle wrote: > I've pushed up for review a set of patches to switch us over to using > config-download by default: > > https://review.openstack.org/#/q/topic:bp/config-download-default > > I believe I've come up with the proper

[openstack-dev] [TripleO][ci][ceph] switching to config-download by default

I've pushed up for review a set of patches to switch us over to using config-download by default: https://review.openstack.org/#/q/topic:bp/config-download-default I believe I've come up with the proper series of steps to switch things over. Let me know if you have any feedback or foresee any

Re: [openstack-dev] [tripleo] PTG session about All-In-One installer: recap & roadmap

- Original Message - > On Tue, Apr 3, 2018 at 10:00 AM, Javier Pena wrote: > > > >> Greeting folks, > >> > >> During the last PTG we spent time discussing some ideas around an > >> All-In-One > >> installer, using 100% of the TripleO bits to deploy a single node > >>

Re: [openstack-dev] [tripleo] PTG session about All-In-One installer: recap & roadmap

On 4/3/18 9:57 PM, Wesley Hayutin wrote: On Tue, 3 Apr 2018 at 13:53 Dan Prince > wrote: On Tue, Apr 3, 2018 at 10:00 AM, Javier Pena > wrote: > >> Greeting folks, >> >>

Re: [openstack-dev] [tripleo] PTG session about All-In-One installer: recap & roadmap

From: Emilien Macchi <emil...@redhat.com> Reply-To: "OpenStack Development Mailing List (not for usage questions)" <openstack-dev@lists.openstack.org> Date: Thursday, 29 March 2018 at 23:35 To: OpenStack Development Mailing List <openstack-dev@lists.openstack.org

[openstack-dev] [tripleo] The Weekly Owl - 15th Edition

Note: this is the fifteenth edition of a weekly update of what happens in TripleO. The goal is to provide a short reading (less than 5 minutes) to learn where we are and what we're doing. Any contributions and feedback are welcome. Link to the previous version:

Re: [openstack-dev] [tripleo] PTG session about All-In-One installer: recap & roadmap

On Tue, 3 Apr 2018 at 13:53 Dan Prince wrote: > On Tue, Apr 3, 2018 at 10:00 AM, Javier Pena wrote: > > > >> Greeting folks, > >> > >> During the last PTG we spent time discussing some ideas around an > All-In-One > >> installer, using 100% of the TripleO

Re: [openstack-dev] [tripleo] PTG session about All-In-One installer: recap & roadmap

On Tue, Apr 3, 2018 at 10:00 AM, Javier Pena wrote: > >> Greeting folks, >> >> During the last PTG we spent time discussing some ideas around an All-In-One >> installer, using 100% of the TripleO bits to deploy a single node OpenStack >> very similar with what we have today with

Re: [openstack-dev] [tripleo] PTG session about All-In-One installer: recap & roadmap

On Tue, Apr 3, 2018 at 9:23 AM, James Slagle wrote: > On Mon, Apr 2, 2018 at 9:05 PM, Dan Prince wrote: >> On Thu, Mar 29, 2018 at 5:32 PM, Emilien Macchi wrote: >>> Greeting folks, >>> >>> During the last PTG we spent time

Re: [openstack-dev] [tripleo] PTG session about All-In-One installer: recap & roadmap

- Original Message - > On Tue, 3 Apr 2018 at 10:00 Javier Pena < jp...@redhat.com > wrote: > > > Greeting folks, > > > > > > > > During the last PTG we spent time discussing some ideas around an > > > All-In-One > > > > installer, using 100% of the TripleO bits to deploy a single node

Re: [openstack-dev] [tripleo] PTG session about All-In-One installer: recap & roadmap

On Tue, 3 Apr 2018 at 10:00 Javier Pena wrote: > > > Greeting folks, > > > > During the last PTG we spent time discussing some ideas around an > All-In-One > > installer, using 100% of the TripleO bits to deploy a single node > OpenStack > > very similar with what we have today

Re: [openstack-dev] [tripleo] PTG session about All-In-One installer: recap & roadmap

I'd really love to this going forward, I fit perfectly on the category that I usually don't test stuff on tripleO because it can get too complex and it will take a lot of time to deploy, so this seems like a perfect solution for that. Thanks for putting this forward. On Tue, Apr 3, 2018 at 11:00

Re: [openstack-dev] [tripleo] PTG session about All-In-One installer: recap & roadmap

> Greeting folks, > > During the last PTG we spent time discussing some ideas around an All-In-One > installer, using 100% of the TripleO bits to deploy a single node OpenStack > very similar with what we have today with the containerized undercloud and > what we also have with other tools like

Re: [openstack-dev] [tripleo] PTG session about All-In-One installer: recap & roadmap

On Mon, Apr 2, 2018 at 9:05 PM, Dan Prince wrote: > On Thu, Mar 29, 2018 at 5:32 PM, Emilien Macchi wrote: >> Greeting folks, >> >> During the last PTG we spent time discussing some ideas around an All-In-One >> installer, using 100% of the TripleO bits to

Re: [openstack-dev] [tripleo] PTG session about All-In-One installer: recap & roadmap

On Thu, Mar 29, 2018 at 5:32 PM, Emilien Macchi wrote: > Greeting folks, > > During the last PTG we spent time discussing some ideas around an All-In-One > installer, using 100% of the TripleO bits to deploy a single node OpenStack > very similar with what we have today with

Re: [openstack-dev] [TripleO] Prototyping dedicated roles with unique repositories for Ansible tasks in TripleO

On Thu, Mar 29, 2018 at 11:32 AM, David Moreau Simard wrote: > Nice! > > I don't have a strong opinion > about this but what I might recommend would be to chat with the > openshift-ansible [1] and the kolla-ansible [2] folks. > > I'm happy to do the introductions if necessary

Re: [openstack-dev] [tripleo] Blueprints for Rocky

On Tue, Mar 13, 2018 at 7:58 AM, Alex Schultz wrote: > Hey everyone, > > So we currently have 63 blueprints for currently targeted for > Rocky[0]. Please make sure that any blueprints you are interested in > delivering have an assignee set and have been approved. I would

Re: [openstack-dev] [tripleo] PTG session about All-In-One installer: recap & roadmap

And just an aside, the All-in-ones are great tools for new operators to be able to get in and learn how to use OpenStack, even if the underlying configuration isn't a multi-node installation. Amy (spotz) On Fri, Mar 30, 2018 at 10:53 AM, Wesley Hayutin wrote: > > > On Fri,

Re: [openstack-dev] [tripleo] PTG session about All-In-One installer: recap & roadmap

On Fri, 30 Mar 2018 at 08:45 Paul Grist wrote: > On Thu, Mar 29, 2018 at 5:32 PM, Emilien Macchi > wrote: > >> Greeting folks, >> >> During the last PTG we spent time discussing some ideas around an >> All-In-One installer, using 100% of the TripleO bits

Re: [openstack-dev] [tripleo] PTG session about All-In-One installer: recap & roadmap

> -Original Message- > From: Emilien Macchi [mailto:emil...@redhat.com] > Sent: Thursday, March 29, 2018 5:33 PM > To: OpenStack Development Mailing List d...@lists.openstack.org> > Subject: [openstack-dev] [tripleo] PTG session about All-In-One installer:

Re: [openstack-dev] [tripleo] PTG session about All-In-One installer: recap & roadmap

On Thu, Mar 29, 2018 at 5:32 PM, Emilien Macchi wrote: > Greeting folks, > > During the last PTG we spent time discussing some ideas around an > All-In-One installer, using 100% of the TripleO bits to deploy a single > node OpenStack very similar with what we have today with

[openstack-dev] [tripleo] PTG session about All-In-One installer: recap & roadmap

Greeting folks, During the last PTG we spent time discussing some ideas around an All-In-One installer, using 100% of the TripleO bits to deploy a single node OpenStack very similar with what we have today with the containerized undercloud and what we also have with other tools like Packstack or

Re: [openstack-dev] [TripleO] Prototyping dedicated roles with unique repositories for Ansible tasks in TripleO

​Nice! ​ I don't have a strong opinion ​about this but what I might recommend would be to chat with the openshift-ansible [1] and the kolla-ansible [2] folks.​ ​I'm happy to do the introductions if necessary !​ Their models, requirements or context might be different than ours but at the end of

[openstack-dev] [TripleO] Prototyping dedicated roles with unique repositories for Ansible tasks in TripleO

Hi everyone, During the recent PTG in Dublin, it was decided that we'd prototype a way forward with Ansible tasks in TripleO that adhere to Ansible best practises, creating dedicated roles with unique git repositories and RPM packaging per role. With a view to moving in this direction, a couple

[openstack-dev] [tripleo][ci] FYI.. the full tempest execution removed from promotion criteria temporarily

Greetings, The upstream packages for master and queens have not been updated in TripleO in 22 days. We have come very close to a package promotion a number of times, but failed for several different reasons. In this latest issue the full tempest job featureset020 was discussed with both Alex

Re: [openstack-dev] [tripleo] modifications to the tech debt policy

On 16 Feb, Gabriele Cerami wrote: > Hi, > > I started circling around technical debts a few months ago, and recently > started to propose changes in my team (CI) process on how to manage > them. > https://review.openstack.org/545392 Hi, I'd like to draw again some attention on this. I'm adding

[openstack-dev] [tripleo] The Weekly Owl - 14th Edition

Note: this is the fourteenth edition of a weekly update of what happens in TripleO. The goal is to provide a short reading (less than 5 minutes) to learn where we are and what we're doing. Any contributions and feedback are welcome. Link to the previous version:

[openstack-dev] [tripleo][oslo] messaging services update

Hi, I wanted to provide an update on the work that has been ongoing to enhance the deployment of messaging system backends for RPC and Notify communications. https://blueprints.launchpad.net/tripleo/+spec/tripleo-messaging The basis of the change is to introduce oslo messaging RPC and Notify

Re: [openstack-dev] [tripleo] Updates on containerized undercloud

This is an update on what has been achieved the last month with the regard of Containerized Undercloud efforts in TripleO: ## CI - Running OVB (ovs-ha, fs001) with a containerized undercloud: it finally works, with some workarounds, all work in progress. Results can be seen here:

[openstack-dev] [tripleo] TripleO CI Sprint end

*Hello,On March 21 we came the end of sprint using our new team structure, and here’s the highlights.Sprint Review:Due the outage in our infra a few weeks ago, we decided to work on the automation on all the servers used in our CI, in this way, in case of a any outage, we are able to teardown all

Re: [openstack-dev] [TripleO] Alternative to empty string for default values in Heat

On 03/23/2018 11:54 AM, Giulio Fidente wrote: On 03/23/2018 05:43 PM, Wojciech Dec wrote: Hi All, I'm converting a few heat service templates that have been working ok with puppet3 modules to run with Puppet 4, and am wondering if there is a way to pass an "undefined" default via heat to

Re: [openstack-dev] [TripleO] Alternative to empty string for default values in Heat

On 03/23/2018 05:43 PM, Wojciech Dec wrote: > Hi All, > > I'm converting a few heat service templates that have been working ok > with puppet3 modules to run with Puppet 4, and am wondering if there is > a way to pass an "undefined" default via heat to allow "default" values > (eg params.pp) of

[openstack-dev] [TripleO] Alternative to empty string for default values in Heat

Hi All, I'm converting a few heat service templates that have been working ok with puppet3 modules to run with Puppet 4, and am wondering if there is a way to pass an "undefined" default via heat to allow "default" values (eg params.pp) of the puppet modules to be used? The previous (puppet 3

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

On Thu, Mar 22, 2018 at 12:11 PM, Kendall Nelson wrote: > Sounds like we have fungi set to run the migration of tripleO bugs with > the 'ui' tag for tomorrow after he gets done with the ironic migration. So > excited to have you guys start moving over! > Cool, please let

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

Sounds like we have fungi set to run the migration of tripleO bugs with the 'ui' tag for tomorrow after he gets done with the ironic migration. So excited to have you guys start moving over! Any idea what squad will want to go next/when they might want to go? No rush, I'm curious more than

Re: [openstack-dev] [tripleo][infra][dib] Gate "out of disk" errors and diskimage-builder 2.12.0

On Thu, Mar 22, 2018 at 8:33 AM, Wesley Hayutin wrote: > > > On Wed, Mar 21, 2018 at 5:11 PM, Ian Wienand wrote: > >> On 03/21/2018 03:39 PM, Ian Wienand wrote: >> >>> We will prepare dib 2.12.1 with the fix. As usual there are >>> complications, since

Re: [openstack-dev] [tripleo][infra][dib] Gate "out of disk" errors and diskimage-builder 2.12.0

On Wed, Mar 21, 2018 at 5:11 PM, Ian Wienand wrote: > On 03/21/2018 03:39 PM, Ian Wienand wrote: > >> We will prepare dib 2.12.1 with the fix. As usual there are >> complications, since the dib gate is broken due to unrelated triple-o >> issues [2]. In the mean time,

Re: [openstack-dev] [tripleo][infra][dib] Gate "out of disk" errors and diskimage-builder 2.12.0

On 03/21/2018 03:39 PM, Ian Wienand wrote: We will prepare dib 2.12.1 with the fix. As usual there are complications, since the dib gate is broken due to unrelated triple-o issues [2]. In the mean time, probably avoid 2.12.0 if you can. [2] https://review.openstack.org/554705 Since we

Re: [openstack-dev] [tripleo] The Weekly Owl - 13th Edition

On 20/03/2018 20:16, Emilien Macchi wrote: > On Tue, Mar 20, 2018 at 9:01 AM, Emilien Macchi > wrote: > +--> Matt is John and ruck is John. Please let them know any new CI > issue. > so I double checked and Matt isn't John but in fact he's

Re: [openstack-dev] [tripleo] The Weekly Owl - 13th Edition

On Tue, Mar 20, 2018 at 9:01 AM, Emilien Macchi wrote: > > +--> Matt is John and ruck is John. Please let them know any new CI issue. > so I double checked and Matt isn't John but in fact he's the rover ;-) -- Emilien Macchi

Re: [openstack-dev] [tripleo] Recap of Python 3 testing session at PTG

On 03/17/2018 03:34 AM, Emilien Macchi wrote: That way, we'll be able to have some early testing on python3-only environments (thanks containers!) without changing the host OS. All hail our new python3-only overlords!!!

Re: [openstack-dev] [tripleo] Recap of Python 3 testing session at PTG

On Sat, Mar 17, 2018 at 9:34 AM, Emilien Macchi wrote: > During the PTG we had some nice conversations about how TripleO can make > progress on testing OpenStack deployments with Python 3. > In CC, Haikel, Alfredo and Javier, please complete if I missed something. > > > ##

Re: [openstack-dev] [tripleo] Recap of Python 3 testing session at PTG

- Original Message - > During the PTG we had some nice conversations about how TripleO can make > progress on testing OpenStack deployments with Python 3. > In CC, Haikel, Alfredo and Javier, please complete if I missed something. > ## Goal > As an OpenStack distribution, RDO would like

[openstack-dev] [tripleo] The Weekly Owl - 13th Edition

Note: this is the thirteenth edition of a weekly update of what happens in TripleO. The goal is to provide a short reading (less than 5 minutes) to learn where we are and what we're doing. Any contributions and feedback are welcome. Link to the previous version:

[openstack-dev] [tripleo] Bug status

Hey everyone, In today's IRC meeting, I brought up[0] that we've been having an increase in the number of open bugs of the last few weeks. We're currently at about 635 open bugs. It would be beneficial for everyone to take a look at the bugs that they are currently assigned to and ensure they

[openstack-dev] [tripleo] Tripleo CI Community meeting tomorrow

Hello We are going to have a TripleO CI Community meeting tomorrow 03/20/2018 at 3 pm UTC time. The meeting is going to happen on BlueJeans [1] and also on IRC on #tripleo channel. After that, we will hold Office Hours starting at 4PM UTC in case someone from community have any questions

[openstack-dev] [tripleo] Ceph integration topics discussed at PTG

Hi, I wanted to share a short summary of the discussions happened around the Ceph integration (in TripleO) at the PTG. In no particular order: - ceph-{container,ansible} branching together with John Fulton and Guillaume Abrioux (and after PTG, Sebastien Han) we put some thought into how to

[openstack-dev] [tripleo] Recap of Python 3 testing session at PTG

During the PTG we had some nice conversations about how TripleO can make progress on testing OpenStack deployments with Python 3. In CC, Haikel, Alfredo and Javier, please complete if I missed something. ## Goal As an OpenStack distribution, RDO would like to ensure that the OpenStack services

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

On Fri, Mar 16, 2018 at 11:15 PM, Jason E. Rist wrote: > > I just tried this but I think I might be doing something wrong... > > http://storyboard.macchi.pro:9000/ Sorry I removed the VM a few weeks ago (I needed to clear up some resources for my dev env). > This URL

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

On 03/02/2018 02:24 AM, Emilien Macchi wrote: > A quick update: > > - Discussed with Jiri Tomasek from TripleO UI squad and he agreed that his > squad would start to use Storyboard, and experiment it. > - I told him I would take care of making sure all UI bugs created in > Launchpad would be

Re: [openstack-dev] [TripleO][CI][QA][HA][Eris][LCOO] Validating HA on upstream

Hi All, Sorry, Late to the party... I have added myself. --- Regards, Sampath On Fri, Mar 16, 2018 at 9:31 AM, Ghanshyam Mann wrote: > On Thu, Mar 15, 2018 at 9:45 PM, Adam Spiers wrote: > > Raoul Scarazzini wrote: > >> > >> On

Re: [openstack-dev] [TripleO][CI][QA][HA][Eris][LCOO] Validating HA on upstream

On Thu, Mar 15, 2018 at 9:45 PM, Adam Spiers wrote: > Raoul Scarazzini wrote: >> >> On 15/03/2018 01:57, Ghanshyam Mann wrote: >>> >>> Thanks all for starting the collaboration on this which is long pending >>> things and we all want to have some start on

Re: [openstack-dev] [tripleo] TLS by default

On 03/15/2018 12:51 AM, Julia Kreger wrote: On Wed, Mar 14, 2018 at 4:52 AM, Dmitry Tantsur wrote: Just to clarify: only for public endpoints, right? I don't think e.g. ironic-python-agent can talk to self-signed certificates yet. For what it is worth, it is possible

Re: [openstack-dev] [tripleo] FFE - Feuture Freeze Exception request for Routed Spine and Leaf Deployment

Hi, It has come to my attention that I missed one detail for the routed spine and leaf support. There is an issue with introspection and the filtering used to ensure only specified nodes are introspected. Apparently we are still using the iptables based PXE filtering in ironic-inspecter. (I

Re: [openstack-dev] [TripleO][CI][QA][HA][Eris][LCOO] Validating HA on upstream

Raoul Scarazzini wrote: On 15/03/2018 01:57, Ghanshyam Mann wrote: Thanks all for starting the collaboration on this which is long pending things and we all want to have some start on this. Myself and SamP talked about it during OPS meetup in Tokyo and we talked about below

Re: [openstack-dev] [TripleO][CI][QA][HA][Eris][LCOO] Validating HA on upstream

On 15/03/2018 01:57, Ghanshyam Mann wrote: > Thanks all for starting the collaboration on this which is long pending > things and we all want to have some start on this. > Myself and SamP talked about it during OPS meetup in Tokyo and we talked > about below draft plan- > - Update the Spec - 

Re: [openstack-dev] [TripleO][CI][QA][HA][Eris][LCOO] Validating HA on upstream

Thanks all for starting the collaboration on this which is long pending things and we all want to have some start on this. Myself and SamP talked about it during OPS meetup in Tokyo and we talked about below draft plan- - Update the Spec - https://review.openstack.org/#/c/443504/. which is

Re: [openstack-dev] [tripleo] TLS by default

On Wed, Mar 14, 2018 at 4:52 AM, Dmitry Tantsur wrote: > Just to clarify: only for public endpoints, right? I don't think e.g. > ironic-python-agent can talk to self-signed certificates yet. > > For what it is worth, it is possible for IPA to speak to a self signed

Re: [openstack-dev] [tripleo] Blueprints for Rocky

Hi Alex, The tripleo-messaging blueprint is pending approval: https://blueprints.launchpad.net/tripleo/+spec/tripleo-messaging Good progress has been made and working towards being ready for Rocky-1. Thanks, Andy On Wed, Mar 14, 2018 at 8:11 AM, Dmitry Tantsur wrote: >

Re: [openstack-dev] [tripleo] Blueprints for Rocky

Hi Alex, I have two small ironic-related blueprints pending approval: https://blueprints.launchpad.net/tripleo/+spec/ironic-rescue https://blueprints.launchpad.net/tripleo/+spec/networking-generic-switch and one larger: https://blueprints.launchpad.net/tripleo/+spec/ironic-inspector-overcloud

Re: [openstack-dev] [tripleo] TLS by default

Correct, only public endpoints. On Wed, Mar 14, 2018 at 1:52 PM, Dmitry Tantsur wrote: > Just to clarify: only for public endpoints, right? I don't think e.g. > ironic-python-agent can talk to self-signed certificates yet. > > > On 03/14/2018 07:03 AM, Juan Antonio Osorio

Re: [openstack-dev] [tripleo] TLS by default

Just to clarify: only for public endpoints, right? I don't think e.g. ironic-python-agent can talk to self-signed certificates yet. On 03/14/2018 07:03 AM, Juan Antonio Osorio wrote: Hello, As part of the proposed changed by the Security Squad [1], we'd like the deployment to use TLS by

[openstack-dev] [tripleo] TLS by default

Hello, As part of the proposed changed by the Security Squad [1], we'd like the deployment to use TLS by default. The first target is to get the undercloud to use it, so a patch has been proposed recently [2] [3]. So, just wanted to give a heads up to people. This should be just fine from a

Re: [openstack-dev] [tripleo] Blueprints for Rocky

On Tue, Mar 13, 2018 at 07:58:48AM -0600, Alex Schultz wrote: > Hey everyone, > > So we currently have 63 blueprints for currently targeted for > Rocky[0]. Please make sure that any blueprints you are interested in > delivering have an assignee set and have been approved. I would like > to have

[openstack-dev] [tripleo] The Weekly Owl - 12th Edition

Note: this is the twelfth edition of a weekly update of what happens in TripleO. The goal is to provide a short reading (less than 5 minutes) to learn where we are and what we're doing. Any contributions and feedback are welcome. Link to the previous version:

[openstack-dev] [tripleo] Blueprints for Rocky

Hey everyone, So we currently have 63 blueprints for currently targeted for Rocky[0]. Please make sure that any blueprints you are interested in delivering have an assignee set and have been approved. I would like to have the ones we plan on delivering for Rocky to be updated by April 3, 2018.

[openstack-dev] [TripleO] ansible/config-download PTG session recap

During the PTG, TripleO held a session about moving forward with config-download as the default deployment mechanism during Rocky. We captured our notes in this etherpad: https://etherpad.openstack.org/p/tripleo-ptg-config-download There was wide agreement to continue moving forward with this

Re: [openstack-dev] [TripleO] Proposal for quickstart devmode replacement

On Mon, Mar 12, 2018 at 2:18 PM, Gabriele Cerami wrote: > Hi, > > we recently changed our set of scripts to uniform the users workflow > with the CI workflow. > One of the results of this change was the reproducer script, that is now > the official way to spawn a live

[openstack-dev] [TripleO] Proposal for quickstart devmode replacement

Hi, we recently changed our set of scripts to uniform the users workflow with the CI workflow. One of the results of this change was the reproducer script, that is now the official way to spawn a live environment to debug a set of changes. One of the negative results of this changes was the

[openstack-dev] [tripleo] Upgrades squad Rocky PTG session

Hi all, Sofer (chem), Jirka (jistr), Lucas (social) and myself (marios) ran the Upgrades squad session during the Rocky PTG in Dublin. Here is a brief summary: * session etherpad at https://etherpad.openstack.org/p/tripleo-ptg-rocky-upgrades * current/ongoing + more in Rocky...

Re: [openstack-dev] [TripleO][CI][QA][HA][Eris][LCOO] Validating HA on upstream

On 3/8/18 6:44 PM, Raoul Scarazzini wrote: On 08/03/2018 17:03, Adam Spiers wrote: [...] Yes agreed again, this is a strong case for collaboration between the self-healing and QA SIGs.  In Dublin we also discussed the idea of the self-healing and API SIGs collaborating on the related topic of

[openstack-dev] [tripleo] Queens retrospective (PTG session)

We kicked-off the PTG by a 45 minutes retrospective about our work during Queens cycle. Here is a short summary of what has been said: - Keep doing: weekly updates and encourage squads to update their etherpads; squads (and adjust our squads every cycle when needed); use #tripleo for IRC

Re: [openstack-dev] [TripleO][CI][QA][HA][Eris][LCOO] Validating HA on upstream

Raoul Scarazzini wrote: On 08/03/2018 17:03, Adam Spiers wrote: [...] Yes agreed again, this is a strong case for collaboration between the self-healing and QA SIGs.  In Dublin we also discussed the idea of the self-healing and API SIGs collaborating on the related topic of

Re: [openstack-dev] [TripleO][CI][QA][HA][Eris][LCOO] Validating HA on upstream

On 08/03/2018 17:03, Adam Spiers wrote: [...] > Yes agreed again, this is a strong case for collaboration between the > self-healing and QA SIGs.  In Dublin we also discussed the idea of the > self-healing and API SIGs collaborating on the related topic of health > check APIs. Guys, thanks a ton

<    3   4   5   6   7   8   9   10   11   12   >