[Pulp-list] Automatic Updates

[Jay Dobies]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 12/21/2010 05:51 PM, Todd B Sanders wrote:
> Beginning to think about Automatic Updates....
> 
> https://fedorahosted.org/pulp/wiki/AutomaticUpdates
> 
> Comments Please....
> 
> -Todd

I like option 2. I think having it driven by the pulp APIs makes sense
given the rest of the functionality pulp provides.

The more of this type of stuff we add the more I'm starting to want an
alert subsystem in place. It'd be really slick if we had a good
infrastructure to set up notifications if a consumer update/repo
sync/cds sync failed. There are a ton of places we could go with it, but
I'm off topic from this original email.

"# We would not recommend configuring automatic updates on the client
(above) and configuring a maintenance window on a client "

I'm not sure I follow. The two seem to go hand in hand to me; we'd want
to say "automatically update the client during its window." Or are you
saying its effectively duplicate functionality that we don't want in
play at the same time?

"# For consumer groups, we need to stagger these operations to ensure
that we don't create a demand spike on the server. "

+1. We may even want to enhance the views on maintenance windows to be
able to show something like "X% of your consumers all share the same
maintenance window, you may want to rethink that."




- -- 
Jay Dobies
RHCE# 805008743336126
Freenode: jdob
http://pulpproject.org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.14 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/

iQEcBAEBAgAGBQJNEiEQAAoJEOMmcTqOSQHC4pQH/3MNCPgCLdKr1GXWKzo3qcDs
7dNm/iRgjDYdwPdKcP04uVczYfTPcWpUBpXi2Z37eNqLHEyM3AotyP5WjB/5Ev3R
S5g+Lcp74xjUm853nYcsuHMzkUbg7CwWfWR0jPlnsZT6EWkgrSOGAu2L3WN/vxvv
rOXV8go/tA+pI241roy/gMV1B7T8w/yjtIc7PCbOpzCSG6FgVOLnHHogm0Ve2BQN
6i39aAk8J2FeBn5Qg8EGVnJSp+rVkkw9YsEV0MVdg2vJZjPeMxJSmVMVO+FtD5Rh
n47Kt9H2NIwoVSjCIyAWuPIx8mctyT+4uiy9yT4pDd2erX2Pfc27ifaCh+oM1jI=
=cs6B
-----END PGP SIGNATURE-----