On 2016-04-05 00:45:20 -0400 (-0400), Jay Pipes wrote:
> The proposal is to have the hardware companies donate hardware and
> sysadmins to setup and maintain a *single* third-party CI lab
> environment running the *upstream infra CI toolset* in one
> datacenter at first, moving to multiple
On 04/04/2016 08:45 PM, Jeremy Stanley wrote:
On 2016-04-04 20:06:03 -0400 (-0400), Jay Pipes wrote:
I'm really not sure why you are being so hostile to my proposal.
Essentially, I wanted to involve the upstream Infra team in this
so they can advise on the project and ensure that the 3rd party
On 2016-04-04 20:06:03 -0400 (-0400), Jay Pipes wrote:
> I'm really not sure why you are being so hostile to my proposal.
> Essentially, I wanted to involve the upstream Infra team in this
> so they can advise on the project and ensure that the 3rd party CI
> system that gets built matches what is
On 04/04/2016 06:56 PM, Jeremy Stanley wrote:
On 2016-04-04 13:54:34 -0400 (-0400), Jay Pipes wrote:
On 03/30/2016 11:00 PM, Robert Collins wrote:
On 26 March 2016 at 09:08, Jeremy Stanley wrote:
On 2016-03-25 15:20:00 -0400 (-0400), Jay Pipes wrote:
[...]
3) The upstream
On 2016-04-04 13:54:34 -0400 (-0400), Jay Pipes wrote:
> On 03/30/2016 11:00 PM, Robert Collins wrote:
> >On 26 March 2016 at 09:08, Jeremy Stanley wrote:
> >>On 2016-03-25 15:20:00 -0400 (-0400), Jay Pipes wrote:
> >>[...]
> >>>3) The upstream Infrastructure team works with
On 03/30/2016 11:00 PM, Robert Collins wrote:
On 26 March 2016 at 09:08, Jeremy Stanley wrote:
On 2016-03-25 15:20:00 -0400 (-0400), Jay Pipes wrote:
[...]
3) The upstream Infrastructure team works with the hired system
administrators to create a single CI system that can
>-Original Message-
>From: Monty Taylor [mailto:mord...@inaugust.com]
>Sent: Saturday, March 26, 2016 3:27 PM
>To: openstack-dev@lists.openstack.org
>Subject: Re: [openstack-dev] [nova] [infra] The same SRIOV / NFV CI failures
>missed a regression, why?
>
&g
On 26 March 2016 at 09:08, Jeremy Stanley wrote:
> On 2016-03-25 15:20:00 -0400 (-0400), Jay Pipes wrote:
> [...]
>> 3) The upstream Infrastructure team works with the hired system
>> administrators to create a single CI system that can spawn
>> functional test jobs on the lab
On 03/29/2016 08:56 AM, Znoinski, Waldemar wrote:
> Hi Jay, Matt, Levi et al,
>
> The Intel NFV CI problems were fixed last week.
> Also, I think if the CIs would have voting right it would attract more
> attention.
>
> I'd be happy to work with OpenStack Infra team on getting our NFV CI the
>
Hi Jay, Matt, Levi et al,
The Intel NFV CI problems were fixed last week.
Also, I think if the CIs would have voting right it would attract more
attention.
I'd be happy to work with OpenStack Infra team on getting our NFV CI the voting
level/rights. To do it right, though, it'd be great to
On 03/25/2016 03:52 PM, Jeremy Stanley wrote:
On 2016-03-25 16:33:44 -0400 (-0400), Jay Pipes wrote:
[...]
What I'm proposing isn't using or needing a custom OpenStack
deployment. There's nothing non-standard at all about the PCI or
NFV stuff besides the hardware required to functionally test
On 2016-03-25 16:33:44 -0400 (-0400), Jay Pipes wrote:
[...]
> What I'm proposing isn't using or needing a custom OpenStack
> deployment. There's nothing non-standard at all about the PCI or
> NFV stuff besides the hardware required to functionally test it.
What you _are_ talking about though is
On 03/25/2016 04:08 PM, Jeremy Stanley wrote:
On 2016-03-25 15:20:00 -0400 (-0400), Jay Pipes wrote:
[...]
3) The upstream Infrastructure team works with the hired system
administrators to create a single CI system that can spawn
functional test jobs on the lab hardware and report results back
On 2016-03-25 15:20:00 -0400 (-0400), Jay Pipes wrote:
[...]
> 3) The upstream Infrastructure team works with the hired system
> administrators to create a single CI system that can spawn
> functional test jobs on the lab hardware and report results back
> to upstream Gerrit
[...]
This bit is
14 matches
Mail list logo