Overall Software / Records - Maintenance / Upgrading

Support
1

Hello,

 I'm in the final stages of the vetting process  for the usage of

Foreman and Puppet. As I start to get ready to deploy this solution
in Prod, I'd like to know what are the best practices to deal with
overall records and software up-keeping.

  1. Software: I intend to distribute via RPM package. If I want to
    upgrade the Foreman RPM (rpm -Uvh foreman-x), do I need to do a rake
    db:migrate every time, or is this something the RPM would do for me?
    Basically, I'm looking to identify the best way possible to keep the
    Foreman SW up to date, using default package management for my OS (RPM/
    CentOS).

  2. Records: What's the best policy with regards to backups? Would a
    Mysqldump Suffice? Is there a procedure for how to recuperate all my
    records should I need to re-install Foreman ?

Thanks,

Henry

2

> Hello,
>
> I'm in the final stages of the vetting process for the usage of
> Foreman and Puppet. As I start to get ready to deploy this solution
> in Prod, I'd like to know what are the best practices to deal with
> overall records and software up-keeping.
>
> 1) Software: I intend to distribute via RPM package. If I want to
> upgrade the Foreman RPM (rpm -Uvh foreman-x), do I need to do a rake
> db:migrate every time, or is this something the RPM would do for me?
> Basically, I'm looking to identify the best way possible to keep the
> Foreman SW up to date, using default package management for my OS (RPM/
> CentOS).
>
The rpm upgrade process will take care for the migration, assuming that your
database settings are correct.
there is a specific case when you upgrade from source/git to rpm, and you
would need to migrate manually, as in the initial rpm the database setting
file is not pointing to your actual db.

>
> 2) Records: What's the best policy with regards to backups? Would a
> Mysqldump Suffice? Is there a procedure for how to recuperate all my
> records should I need to re-install Foreman ?
>
> mysqldump should suffice, and of course, keep your configuration files :slight_smile:

Ohad

··· On Thu, Dec 2, 2010 at 8:53 PM, CraftyTech wrote:
3

Thanks Ohad… I'm starting new in my prod environment… I'm doing
things by the book now… :slight_smile:

··· On Dec 6, 11:36 am, Ohad Levy wrote: > On Thu, Dec 2, 2010 at 8:53 PM, CraftyTech wrote: > > Hello, > > > I'm in the final stages of the vetting process for the usage of > > Foreman and Puppet. As I start to get ready to deploy this solution > > in Prod, I'd like to know what are the best practices to deal with > > overall records and software up-keeping. > > > 1) Software: I intend to distribute via RPM package. If I want to > > upgrade the Foreman RPM (rpm -Uvh foreman-x), do I need to do a rake > > db:migrate every time, or is this something the RPM would do for me? > > Basically, I'm looking to identify the best way possible to keep the > > Foreman SW up to date, using default package management for my OS (RPM/ > > CentOS). > > The rpm upgrade process will take care for the migration, assuming that your > database settings are correct. > there is a specific case when you upgrade from source/git to rpm, and you > would need to migrate manually, as in the initial rpm the database setting > file is not pointing to your actual db. > > > > > 2) Records: What's the best policy with regards to backups? Would a > > Mysqldump Suffice? Is there a procedure for how to recuperate all my > > records should I need to re-install Foreman ? > > > mysqldump should suffice, and of course, keep your configuration files :) > > Ohad