Giving few updates here:
- we implemented option 1.a), which means that we moved the tripleo CI
scenarios environments and pingtests into tripleo-heat-template.
- we created tripleo-scenarioXXX-puppet jobs that run on some modules.
Some Example:
- puppet-gnocchi now runs tripleo-scenario001, that
On 11/22/2016 09:02 PM, Emilien Macchi wrote:
> == Context
>
> In Newton we added new multinode jobs called "scenarios".
> The challenged we tried to solve was "how to test the maximum of
> services without overloading the nodes that run tests".
>
> Each scenarios deploys a set of services, whi
On Fri, Nov 25, 2016 at 7:22 AM, Gabriele Cerami wrote:
> On 22 Nov, Emilien Macchi wrote:
>> 1) Re-use experience from Puppet OpenStack CI and have environments
>> that are in a branched repository.
>> a) Move CI environments and pingtest into
>> tripleo-heat-templates/environments/ci/(scenarios|
On 22 Nov, Emilien Macchi wrote:
> 1) Re-use experience from Puppet OpenStack CI and have environments
> that are in a branched repository.
> a) Move CI environments and pingtest into
> tripleo-heat-templates/environments/ci/(scenarios|pingtest). This repo
> is branched and we could add a README to
On Thu, Nov 24, 2016 at 11:08 AM, Juan Antonio Osorio
wrote:
> I don't have a strong opinion about any option, as long as we have something
> in place I'm happy.
>
> But regarding option 1.A: what would be done for newton once these templates
> are moved to t-h-t. Would they be backported? What ab
I don't have a strong opinion about any option, as long as we have
something in place I'm happy.
But regarding option 1.A: what would be done for newton once these
templates are moved to t-h-t. Would they be backported? What about mitaka?
On 24 Nov 2016 17:55, "Carlos Camacho Gonzalez" wrote:
>
I think would be cool to go with option, +1 to 1.A
IMHO,
- Easier to read.
- Easier to maintain.
- We don't make backports, instead we guarantee backwards compatibility.
- We'll re-use experience from Puppet OpenStack CI.
On Wed, Nov 23, 2016 at 10:13 PM, Giulio Fidente wrote:
> hi Emilien,
>
>
hi Emilien,
thanks for putting some thought into this. We have a similar problem to
test RGW which was only added in Newton.
On 11/23/2016 03:02 AM, Emilien Macchi wrote:
== Context
In Newton we added new multinode jobs called "scenarios".
The challenged we tried to solve was "how to test th
== Context
In Newton we added new multinode jobs called "scenarios".
The challenged we tried to solve was "how to test the maximum of
services without overloading the nodes that run tests".
Each scenarios deploys a set of services, which allows us to
horizontally scale the number of scenarios to
