Re: [openstack-dev] [TripleO] Upstream backwards compatibility job for Newton oooq

2017-01-17 Thread Ben Nemec
On 01/17/2017 09:57 AM, mathieu bultel wrote: On 01/17/2017 04:42 PM, Emilien Macchi wrote: On Tue, Jan 17, 2017 at 9:34 AM, mathieu bultel wrote: Hi Adriano On 01/17/2017 03:05 PM, Adriano Petrich wrote: So I want to make a backwards compatibility job upstream so from last scrum I got the

Re: [openstack-dev] [TripleO] Upstream backwards compatibility job for Newton oooq

2017-01-17 Thread mathieu bultel
On 01/17/2017 05:19 PM, Emilien Macchi wrote: > On Tue, Jan 17, 2017 at 10:57 AM, mathieu bultel wrote: >> On 01/17/2017 04:42 PM, Emilien Macchi wrote: >>> On Tue, Jan 17, 2017 at 9:34 AM, mathieu bultel wrote: Hi Adriano On 01/17/2017 03:05 PM, Adriano Petrich wrote: So

Re: [openstack-dev] [TripleO] Upstream backwards compatibility job for Newton oooq

2017-01-17 Thread Steven Hardy
On Tue, Jan 17, 2017 at 10:42:18AM -0500, Emilien Macchi wrote: > On Tue, Jan 17, 2017 at 9:34 AM, mathieu bultel wrote: > > Hi Adriano > > > > On 01/17/2017 03:05 PM, Adriano Petrich wrote: > > > > So I want to make a backwards compatibility job upstream so from last scrum > > I got the feeling t

Re: [openstack-dev] [TripleO] Upstream backwards compatibility job for Newton oooq

2017-01-17 Thread Steven Hardy
On Tue, Jan 17, 2017 at 02:48:27PM +, Adriano Petrich wrote: >Mathieu, >    That sounds exactly what we need. Do we run tempest or something on >those to validate it? It doesn't currently run tempest, only some basic sanity tests (crud operations where we create some resources fo

Re: [openstack-dev] [TripleO] Upstream backwards compatibility job for Newton oooq

2017-01-17 Thread Emilien Macchi
On Tue, Jan 17, 2017 at 10:57 AM, mathieu bultel wrote: > On 01/17/2017 04:42 PM, Emilien Macchi wrote: >> On Tue, Jan 17, 2017 at 9:34 AM, mathieu bultel wrote: >>> Hi Adriano >>> >>> On 01/17/2017 03:05 PM, Adriano Petrich wrote: >>> >>> So I want to make a backwards compatibility job upstream

Re: [openstack-dev] [TripleO] Upstream backwards compatibility job for Newton oooq

2017-01-17 Thread mathieu bultel
On 01/17/2017 04:42 PM, Emilien Macchi wrote: > On Tue, Jan 17, 2017 at 9:34 AM, mathieu bultel wrote: >> Hi Adriano >> >> On 01/17/2017 03:05 PM, Adriano Petrich wrote: >> >> So I want to make a backwards compatibility job upstream so from last scrum >> I got the feeling that we should not be add

Re: [openstack-dev] [TripleO] Upstream backwards compatibility job for Newton oooq

2017-01-17 Thread Emilien Macchi
On Tue, Jan 17, 2017 at 9:34 AM, mathieu bultel wrote: > Hi Adriano > > On 01/17/2017 03:05 PM, Adriano Petrich wrote: > > So I want to make a backwards compatibility job upstream so from last scrum > I got the feeling that we should not be adding more stuff to the > experimental jobs due to lack

Re: [openstack-dev] [TripleO] Upstream backwards compatibility job for Newton oooq

2017-01-17 Thread Adriano Petrich
Mathieu, That sounds exactly what we need. Do we run tempest or something on those to validate it? On Tue, Jan 17, 2017 at 2:34 PM, mathieu bultel wrote: > Hi Adriano > > On 01/17/2017 03:05 PM, Adriano Petrich wrote: > > So I want to make a backwards compatibility job upstream so from last

Re: [openstack-dev] [TripleO] Upstream backwards compatibility job for Newton oooq

2017-01-17 Thread mathieu bultel
Hi Adriano On 01/17/2017 03:05 PM, Adriano Petrich wrote: > So I want to make a backwards compatibility job upstream so from last > scrum I got the feeling that we should not be adding more stuff to the > experimental jobs due to lack of resources (and large queues) > What kind of "test" do you w

[openstack-dev] [TripleO] Upstream backwards compatibility job for Newton oooq

2017-01-17 Thread Adriano Petrich
So I want to make a backwards compatibility job upstream so from last scrum I got the feeling that we should not be adding more stuff to the experimental jobs due to lack of resources (and large queues) Is that so? I was thinking about using nonha-multinode-oooq that seems to be working. Is that