FTE Server updates

[wes hayutin]

I think there was confusion regarding QE and the FTE server. The only
requirement we've had is that changes in the servers code or
availability be announced on imanage-qe-list(a)redhat.com. 

I think the confusion was from the one time test day we hosted two weeks
ago.  I'm sure that updates have been made to the FTE server since the
test day, possibly not the candlepin build itself, but I'm a little
unclear how and why we're now being asked if we want the server
updated.  

Either way, I dont want QE holding up IT or the candlepin team.  If you
guys need to get something done, shoot from the hip.  Just email us ;)
Our preference would be to have FTE use the latest git tag, however I
would not say its a requirement. 

Hopefully this will clear up any confusion on our part, and get updates
deployed faster. If we need to freeze updates to FTE in the future we
will specifically ask for it.  I'll make sure we're more clear once
we're complete. 

Thanks

[Chris Alfonso]

On 07/05/10 10:45 -0400, Wes Hayutin wrote:
> I think there was confusion regarding QE and the FTE server. The only
> requirement we've had is that changes in the servers code or
> availability be announced on imanage-qe-list(a)redhat.com. 
>
> I think the confusion was from the one time test day we hosted two weeks
> ago.  I'm sure that updates have been made to the FTE server since the
> test day, possibly not the candlepin build itself, but I'm a little
> unclear how and why we're now being asked if we want the server
> updated.  
>  
I can probably clarify this a little.  When we set up the FTE machine
I asked what the process should be for you guys to know when updates
are coming and when the updates have finished getting pushed.  From my
perspective, you all need to know what you're testing, and if we just
push an update while you're trying to verify a defect, it's going to
drive you bonkers.  My understanding is that you all would request an
update when your test run was finished.  I'm totally fine with just
pushing an update out as soon as it's available.

I think zeus mentioned he can probably set up a twice a week tagging
of candlepin.

> Either way, I dont want QE holding up IT or the candlepin team.  If
> you
> guys need to get something done, shoot from the hip.  Just email us ;)
> Our preference would be to have FTE use the latest git tag, however I
> would not say its a requirement. 
>
> Hopefully this will clear up any confusion on our part, and get updates
> deployed faster. If we need to freeze updates to FTE in the future we
> will specifically ask for it.  I'll make sure we're more clear once
> we're complete. 
>  
> Thanks
>
>
>

[wes hayutin]

On Fri, 2010-05-07 at 10:52 -0400, Chris Alfonso wrote:
>  On 07/05/10 10:45 -0400, Wes Hayutin wrote:
>  >I think there was confusion regarding QE and the FTE server. The only
>  >requirement we've had is that changes in the servers code or
>  >availability be announced on imanage-qe-list(a)redhat.com. 
>  >
>  >I think the confusion was from the one time test day we hosted two weeks
>  >ago.  I'm sure that updates have been made to the FTE server since the
>  >test day, possibly not the candlepin build itself, but I'm a little
>  >unclear how and why we're now being asked if we want the server
>  >updated.  
>  >
>  I can probably clarify this a little.  When we set up the FTE machine
>  I asked what the process should be for you guys to know when updates
>  are coming and when the updates have finished getting pushed.  From my
>  perspective, you all need to know what you're testing, and if we just
>  push an update while you're trying to verify a defect, it's going to
>  drive you bonkers.  
Initially we were using the git sha on cert.dev.devlab.  Since
the move
to cert-fte there has not any official way of identifying what is
running. I also have to say it has not been a top priority or an issue
for QE.  In the absence of a process we should come to an agreement on
this.  Lets take this offline as a to-do. 

>   My understanding is that you all would request an
>  update when your test run was finished. 
I can understand why you would think that,
however QE has never made
that requirement.  I am not sure where that is coming from, but it does
highlight the lack of communication between the teams.  Again, the only
requirement from QE would be to email imanage-qe-list(a)redhat.com w/
availability or content changes to FTE. 

>    I'm totally fine with just
>  pushing an update out as soon as it's available.
>  I think zeus mentioned he can probably set up a twice a week tagging
>  of candlepin. 
Getting git tags twice a week would be a step in the right direction.

Thanks Chris!
>  
>  >Either way, I dont want QE holding up IT or the candlepin team.  If you
>  >guys need to get something done, shoot from the hip.  Just email us ;)
>  >Our preference would be to have FTE use the latest git tag, however I
>  >would not say its a requirement. 
>  >
>  >Hopefully this will clear up any confusion on our part, and get updates
>  >deployed faster. If we need to freeze updates to FTE in the future we
>  >will specifically ask for it.  I'll make sure we're more clear once
>  >we're complete. 
>  >
>  
>  >Thanks
>  >
>  >
>  >