Definitely document what's been described about - backups, snaps, separation of environments (can you have a QA environment - even just 5 kvm VMs?), etc.
I would also share a categorization of the updates (and why they get updated when they do) with the requestors. - Security: daily (or hourly if need be) for obvious reasons - Kernel, specific drivers, etc: do these need to be daily? What about a weekly patch cycle unless it is critical? - Misc: Whenever. Reason is, if I'm the end user, having someone daily update my systems could be really disruptive. Having knowledge of expected maintenance windows would be great for all involved. Not saying you don't do any of the above wrt notifying the users, but it would be good to include that info in the documentation. It's also hard to know what documentation is needed without the workload of these systems. Are they running web servers? Databases? Batch processing? Each of those would have a different process for updates. Hope this helps, and please elaborate more with your scenario! - wesley On Sun, Oct 25, 2015 at 6:32 AM, Perkins, Jerry <[email protected]> wrote: > On 10/24/2015 11:54 AM, xor wrote: > > Now all of a sudden, someone there is wanting me to document the updates > and how the updates might affect our software before I apply them, etc > etc. Tell me if I am wrong, but I have explained to them this is not a > reasonable request. However, one person in particular with a big business > mainframe mentality can be very stubborn about things such as this. So I > could use a little help. > > > A lot of the documentation may already be in the log files, i.e. > /var/log/dpkg.log.xxx. Also in the individual application documentation. > > -- > Jerry Perkins > Home page http://jperkins.us > > [image: Tux_Christmas_by_D3struct0.png] <http://jperkins.us> > > -- > -- > You received this message because you are subscribed to the Google Groups > "NLUG" group. > To post to this group, send email to [email protected] > To unsubscribe from this group, send email to > [email protected] > For more options, visit this group at > http://groups.google.com/group/nlug-talk?hl=en > > --- > You received this message because you are subscribed to the Google Groups > "NLUG" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- http://www.wesleyduffeebraun.com <http://www.ashevillephotobooth.com> -- -- You received this message because you are subscribed to the Google Groups "NLUG" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/nlug-talk?hl=en --- You received this message because you are subscribed to the Google Groups "NLUG" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
