Freeze Break Request: enable package-specific tasks for Taskotron production

[Tim Flink]

This has been pending for a long time and now that the bureaucratic
stuff has been figured out and our dev/stg instances are running well,
we'd like to enable package-specific tasks in Taskotron production.

This will involve:
 - Updating to latest execdb
    * This involves a db change of one column from String(20) to Text()
 - Updating to latest taskotron-trigger
 - Configuring trigger to look for tasks in dist-git on koji_build

The primary risks are:
 - Something goes wrong with the execdb db update (unlikely)
   * This is easily mitigated by either replacing the db (the data in
     it isn't critical) or reverting

 - New Trigger doesn't work properly
   * Revert to older trigger build and config

This setup is running in both our dev and stg environments. We have
not seen any stability issues as the change on our systems is rather
small.

I have attached diffs for the execdb, trigger and ansible changes.

+1s?

Tim

[Kevin Fenzi]

Thats quite a pile of change, but it sounds like you have a pretty good
backout plan in case something goes wrong. 

So, +1 here

kevin

[Stephen John Smoogen]

Same comments as Kevin. Thanks for the thorough plan.

On 16 March 2017 at 15:26, Kevin Fenzi <kevin(a)scrye.com&gt; wrote:
>  Thats quite a pile of change, but it sounds like you have a pretty
> good
>  backout plan in case something goes wrong.
>
>  So, +1 here
>
>  kevin
>
>  _______________________________________________
>  infrastructure mailing list -- infrastructure(a)lists.fedoraproject.org
>  To unsubscribe send an email to infrastructure-leave(a)lists.fedoraproject.org
>  


-- 
Stephen J Smoogen.

[Pierre-Yves Chibon]

On Thu, Mar 16, 2017 at 12:44:37PM -0600, Tim Flink wrote:
>  This has been pending for a long time and now that the bureaucratic
>  stuff has been figured out and our dev/stg instances are running well,
>  we'd like to enable package-specific tasks in Taskotron production.
>  
>  This will involve:
>   - Updating to latest execdb
>      * This involves a db change of one column from String(20) to Text()
>   - Updating to latest taskotron-trigger
>   - Configuring trigger to look for tasks in dist-git on koji_build
>  
>  The primary risks are:
>   - Something goes wrong with the execdb db update (unlikely)
>     * This is easily mitigated by either replacing the db (the data in
>       it isn't critical) or reverting
>  
>   - New Trigger doesn't work properly
>     * Revert to older trigger build and config
>  
>  This setup is running in both our dev and stg environments. We have
>  not seen any stability issues as the change on our systems is rather
>  small.
>  
>  I have attached diffs for the execdb, trigger and ansible changes.
>  
>  +1s? 
+1 for me as well,


Pierre

[Tim Flink]

On Fri, 17 Mar 2017 09:37:07 +0100
Pierre-Yves Chibon <pingou(a)pingoured.fr&gt; wrote:

>  On Thu, Mar 16, 2017 at 12:44:37PM -0600, Tim Flink wrote:
>  > This has been pending for a long time and now that the bureaucratic
>  > stuff has been figured out and our dev/stg instances are running
>  > well, we'd like to enable package-specific tasks in Taskotron
>  > production. 
<snip>

This was pushed to production last night and everything seems to be
running fine.

Thanks,

Tim

[Pierre-Yves Chibon]

On Fri, Mar 17, 2017 at 08:37:19AM -0600, Tim Flink wrote:
>  On Fri, 17 Mar 2017 09:37:07 +0100
>  Pierre-Yves Chibon <pingou(a)pingoured.fr&gt; wrote:
>  
>  > On Thu, Mar 16, 2017 at 12:44:37PM -0600, Tim Flink wrote:
>  > > This has been pending for a long time and now that the bureaucratic
>  > > stuff has been figured out and our dev/stg instances are running
>  > > well, we'd like to enable package-specific tasks in Taskotron
>  > > production.
>  <snip>
>  
>  This was pushed to production last night and everything seems to be
>  running fine.
>  
>  Thanks, 
\ó/