[openstack-dev] [tripleo] Pike deployment times VS Ocata

2017-12-11 Thread Justin Kilpatrick
This week on science confirms the obvious, containerized deployments are faster, more reliable, and scale better. Really great work everyone, TripleO deployment at 50 nodes is starting to get boring! Here's the report, comment if you find anything confusing or inaccessible. https://docs.google.c

Re: [openstack-dev] [tripleo][ironic] Hardware provisioning testing for Ocata

2017-06-09 Thread Justin Kilpatrick
On Fri, Jun 9, 2017 at 5:25 AM, Dmitry Tantsur wrote: > This number of "300", does it come from your testing or from other sources? > If the former, which driver were you using? What exactly problems have you > seen approaching this number? I haven't encountered this issue personally, but talking

Re: [openstack-dev] [tripleo][ironic] Hardware provisioning testing for Ocata

2017-06-08 Thread Justin Kilpatrick
Hi Emilien, I'll try and get a list of the Perf&Scale teams TripleO deployment bugs and bring them to the deployment hackfest. I look forward to participating! - Justin On Thu, Jun 8, 2017 at 11:10 AM, Emilien Macchi wrote: > On Thu, Jun 8, 2017 at 2:21 PM, Justin Kilpa

[openstack-dev] [tripleo][ironic] Hardware provisioning testing for Ocata

2017-06-08 Thread Justin Kilpatrick
Morning everyone, I've been working on a performance testing tool for TripleO hardware provisioning operations off and on for about a year now and I've been using it to try and collect more detailed data about how TripleO performs in scale and production use cases. Perhaps more importantly YODA (Y

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

2017-04-19 Thread Justin Kilpatrick
: >> >> On 18/04/17 14:28 -0400, Emilien Macchi wrote: >>> >>> On Mon, Apr 17, 2017 at 3:52 PM, Justin Kilpatrick >>> wrote: >>>> >>>> Because CI jobs tend to max out about 5 nodes there's a whole class of >>>> minor bu

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

2017-04-17 Thread Justin Kilpatrick
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 simply work around the issue and get onto what they w

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

2017-04-17 Thread Justin Kilpatrick
>>>> with >>>> very limited resources. Actually we are pretty close to full utilizing >>>> these >>>> resources when deploying openstack, so very little is available for >>>> test. >>>> It's not a problem to run tempest API

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

2017-04-06 Thread Justin Kilpatrick
Maybe I'm getting a little off topic with this question, but why was Tempest removed last time? I'm not well versed in the history of this discussion, but from what I understand Tempest in the gate has been an off and on again thing for a while but I've never heard the story of why it got removed.