Foreman 1.3 is out

Support
1

Hello all,

it is finally here. Foreman 1.3 has been released.

Improvements were made in the installation process, API, scalability (for
importing reports and facts see bellow), existing hosts mapping to compute
resources, and more. There is now a new official CLI.

Upgrade needs your attention, please read BEFORE YOU UPGRADE section bellow
first.

Key features:

  • Hammer - Foreman CLI
  • Google Compute Engine as a Compute Resource
  • Installer auto-registers smart-proxy
  • Libvirt Spice support
  • Map between existing VM's and foreman hosts
  • User authentication based on LDAP filter
  • Relax requirement for providing host IP (e.g. when using tokens)
  • foreman-rake command to avoid long SCL commands
  • exciting Plugins are now in a new packaged in the plugins repo
  • API v2 improvements
  • New translations (British English, Chinese Simplified, French, Galcian,
    German and Spanish)

Full release notes:

http://theforeman.org/manuals/1.3/index.html#Releasenotesfor1.3

BEFORE YOU UPGRADE

Database Backup

While its normally recommended to backup your foreman database on a regular
bases, we strongly suggest that you do that prior upgrading, as we now
enforce foreign keys in Foreman database, this means that the update process
will delete all unrequired leftover / orphaned records.

Fact and Report upload changes

In order to reduce load and improve the performance of the foreman server (or
servers) it no longer requires puppet to be installed in order to parse puppet
facts and reports, as a result, the way facts and reports are uploaded was
changed. Specifically, Foreman itself now uses a JSON format, and the ENC
(node.rb) and Puppet report processor (foreman.rb) have been updated to handle
changing Puppet-specific data into JSON. Existing ENC/Reports scripts will
need a change to the latest version, which can be found in the installer git
repository:

  • external_node_v2.rb.erb
  • foreman-report_v2.rb.erb

If reporting is being used, please update these scripts during the upgrade (or
just use our installer).

After upgrade is finished, do check your instance and identify if you are not
missing any records in the database, including things which are not being used
every day. Again, the database migration can delete orphaned records, it is
very important to identify this as early as possible.

Packages

Package repos are available here:

http://yum.theforeman.org/releases/1.3/
http://yum.theforeman.org/plugins/1.3/

http://deb.theforeman.org/ ("stable" component)

Quickstart instructions are here:

http://theforeman.org/manuals/1.3/index.html#2.Quickstart

Tarballs available here:

http://projects.theforeman.org/projects/foreman/files

Installation

There is a new installer for Foreman 1.3, it has many new options that are
taken directly from puppet class parameters. Check the help screen or install
with default options directly:

# foreman-installer

Our new installer now provides many configuration options, or you can still
use interactive mode. Use --help for more info.

Known issues

** Proxy registration happens before Apache is started **

You may encounter failure during proxy registration (Foreman_smartproxy puppet
class). In that case if you see 404 error while registering proxy, please
re-run the installer and the error should disappear.

http://projects.theforeman.org/issues/3083

** Rake task db:convert:prod2dev fails **

Due to foreign keys, prod2dev migration rake task fails. We already have a
patch ready and we will release the fix soon.

http://projects.theforeman.org/issues/3212

** Diff view display style is incorrect **

Diff view in provisioning templates does has incorrect CSS. You can download an
experimental workaround patch already today if you need it.

http://projects.theforeman.org/issues/2816

Reporting issues

Please report issues found in Foreman 1.3 in redmine.

Foreman: Foreman
Proxy: Foreman
Installer: Foreman

Existing bug reports are listed here:
http://projects.theforeman.org/projects/foreman/issues?query_id=24

The new foreman-debug script can be used to collect and provide information
about your setup, and the result attached to bug reports. Also on RHEL 6.5+
you can use sosreport to do the same.

Thanks for using Foreman.

··· -- Later,

Lukas “lzap” Zapletal
irc: lzap #theforeman

2

I have tried to install this using the debian instructions on theforeman
website Quickstart:

http://theforeman.org/manuals/1.1/index.html#3.2.1Installation

and it returns this error when trying to run the ruby file:

ruby /usr/share/foreman-installer/generate_answers.rb
ruby: No such file or directory –
/usr/share/foreman-installer/generate_answers.rb (LoadError)

I tried to find this on the machine and it can't be found anywhere.

Can you help please?

··· On Tuesday, October 15, 2013 1:38:27 AM UTC+10, Lukas Zapletal wrote: > > Hello all, > > it is finally here. Foreman 1.3 has been released. > > Improvements were made in the installation process, API, scalability (for > importing reports and facts see bellow), existing hosts mapping to compute > resources, and more. There is now a new official CLI. > > Upgrade needs your attention, please read BEFORE YOU UPGRADE section > bellow > first. > > Key features: > > * Hammer - Foreman CLI > * Google Compute Engine as a Compute Resource > * Installer auto-registers smart-proxy > * Libvirt Spice support > * Map between existing VM's and foreman hosts > * User authentication based on LDAP filter > * Relax requirement for providing host IP (e.g. when using tokens) > * foreman-rake command to avoid long SCL commands > * exciting Plugins are now in a new packaged in the plugins repo > * API v2 improvements > * New translations (British English, Chinese Simplified, French, > Galcian, > German and Spanish) > > Full release notes: > > http://theforeman.org/manuals/1.3/index.html#Releasenotesfor1.3 > > ## BEFORE YOU UPGRADE ## > > ### Database Backup ### > > While its normally recommended to backup your foreman database on a > regular > bases, we strongly suggest that you do that prior upgrading, as we now > enforce foreign keys in Foreman database, this means that the update > process > *will delete* all unrequired leftover / orphaned records. > > ### Fact and Report upload changes ### > > In order to reduce load and improve the performance of the foreman server > (or > servers) it no longer requires puppet to be installed in order to parse > puppet > facts and reports, as a result, the way facts and reports are uploaded was > changed. Specifically, Foreman itself now uses a JSON format, and the ENC > (node.rb) and Puppet report processor (foreman.rb) have been updated to > handle > changing Puppet-specific data into JSON. Existing ENC/Reports scripts will > need a change to the latest version, which can be found in the installer > git > repository: > > - external_node_v2.rb.erb > - foreman-report_v2.rb.erb > > If reporting is being used, please update these scripts during the upgrade > (or > just use our installer). > > After upgrade is finished, do check your instance and identify if you are > not > missing any records in the database, including things which are not being > used > every day. Again, the database migration can delete orphaned records, it > is > very important to identify this as early as possible. > > ## Packages ## > > Package repos are available here: > > http://yum.theforeman.org/releases/1.3/ > http://yum.theforeman.org/plugins/1.3/ > > http://deb.theforeman.org/ ("stable" component) > > Quickstart instructions are here: > > http://theforeman.org/manuals/1.3/index.html#2.Quickstart > > Tarballs available here: > > http://projects.theforeman.org/projects/foreman/files > > ## Installation ## > > There is a new installer for Foreman 1.3, it has many new options that are > taken directly from puppet class parameters. Check the help screen or > install > with default options directly: > > # foreman-installer > > Our new installer now provides many configuration options, or you can > still > use interactive mode. Use --help for more info. > > ## Known issues ## > > ** Proxy registration happens before Apache is started ** > > You may encounter failure during proxy registration (Foreman_smartproxy > puppet > class). In that case if you see 404 error while registering proxy, please > re-run the installer and the error should disappear. > > http://projects.theforeman.org/issues/3083 > > ** Rake task db:convert:prod2dev fails ** > > Due to foreign keys, prod2dev migration rake task fails. We already have a > patch ready and we will release the fix soon. > > http://projects.theforeman.org/issues/3212 > > ** Diff view display style is incorrect ** > > Diff view in provisioning templates does has incorrect CSS. You can > download an > experimental workaround patch already today if you need it. > > http://projects.theforeman.org/issues/2816 > > ## Reporting issues ## > > Please report issues found in Foreman 1.3 in redmine. > > Foreman: http://projects.theforeman.org/projects/foreman/issues/new > Proxy: http://projects.theforeman.org/projects/smart-proxy/issues/new > Installer: http://projects.theforeman.org/projects/kafo/issues/new > > Existing bug reports are listed here: > http://projects.theforeman.org/projects/foreman/issues?query_id=24 > > The new foreman-debug script can be used to collect and provide > information > about your setup, and the result attached to bug reports. Also on RHEL > 6.5+ > you can use sosreport to do the same. > > Thanks for using Foreman. > > -- > Later, > > Lukas "lzap" Zapletal > irc: lzap #theforeman >
3

Just updated our test server, everything went smooth.

Looking forward to test the new features.

Thanks for such a great product!

··· On Monday, October 14, 2013 5:38:27 PM UTC+2, Lukas Zapletal wrote: > > Hello all, > > it is finally here. Foreman 1.3 has been released. > > Improvements were made in the installation process, API, scalability (for > importing reports and facts see bellow), existing hosts mapping to compute > resources, and more. There is now a new official CLI. > > Upgrade needs your attention, please read BEFORE YOU UPGRADE section > bellow > first. > > Key features: > > * Hammer - Foreman CLI > * Google Compute Engine as a Compute Resource > * Installer auto-registers smart-proxy > * Libvirt Spice support > * Map between existing VM's and foreman hosts > * User authentication based on LDAP filter > * Relax requirement for providing host IP (e.g. when using tokens) > * foreman-rake command to avoid long SCL commands > * exciting Plugins are now in a new packaged in the plugins repo > * API v2 improvements > * New translations (British English, Chinese Simplified, French, > Galcian, > German and Spanish) > > Full release notes: > > http://theforeman.org/manuals/1.3/index.html#Releasenotesfor1.3 > > ## BEFORE YOU UPGRADE ## > > ### Database Backup ### > > While its normally recommended to backup your foreman database on a > regular > bases, we strongly suggest that you do that prior upgrading, as we now > enforce foreign keys in Foreman database, this means that the update > process > *will delete* all unrequired leftover / orphaned records. > > ### Fact and Report upload changes ### > > In order to reduce load and improve the performance of the foreman server > (or > servers) it no longer requires puppet to be installed in order to parse > puppet > facts and reports, as a result, the way facts and reports are uploaded was > changed. Specifically, Foreman itself now uses a JSON format, and the ENC > (node.rb) and Puppet report processor (foreman.rb) have been updated to > handle > changing Puppet-specific data into JSON. Existing ENC/Reports scripts will > need a change to the latest version, which can be found in the installer > git > repository: > > - external_node_v2.rb.erb > - foreman-report_v2.rb.erb > > If reporting is being used, please update these scripts during the upgrade > (or > just use our installer). > > After upgrade is finished, do check your instance and identify if you are > not > missing any records in the database, including things which are not being > used > every day. Again, the database migration can delete orphaned records, it > is > very important to identify this as early as possible. > > ## Packages ## > > Package repos are available here: > > http://yum.theforeman.org/releases/1.3/ > http://yum.theforeman.org/plugins/1.3/ > > http://deb.theforeman.org/ ("stable" component) > > Quickstart instructions are here: > > http://theforeman.org/manuals/1.3/index.html#2.Quickstart > > Tarballs available here: > > http://projects.theforeman.org/projects/foreman/files > > ## Installation ## > > There is a new installer for Foreman 1.3, it has many new options that are > taken directly from puppet class parameters. Check the help screen or > install > with default options directly: > > # foreman-installer > > Our new installer now provides many configuration options, or you can > still > use interactive mode. Use --help for more info. > > ## Known issues ## > > ** Proxy registration happens before Apache is started ** > > You may encounter failure during proxy registration (Foreman_smartproxy > puppet > class). In that case if you see 404 error while registering proxy, please > re-run the installer and the error should disappear. > > http://projects.theforeman.org/issues/3083 > > ** Rake task db:convert:prod2dev fails ** > > Due to foreign keys, prod2dev migration rake task fails. We already have a > patch ready and we will release the fix soon. > > http://projects.theforeman.org/issues/3212 > > ** Diff view display style is incorrect ** > > Diff view in provisioning templates does has incorrect CSS. You can > download an > experimental workaround patch already today if you need it. > > http://projects.theforeman.org/issues/2816 > > ## Reporting issues ## > > Please report issues found in Foreman 1.3 in redmine. > > Foreman: http://projects.theforeman.org/projects/foreman/issues/new > Proxy: http://projects.theforeman.org/projects/smart-proxy/issues/new > Installer: http://projects.theforeman.org/projects/kafo/issues/new > > Existing bug reports are listed here: > http://projects.theforeman.org/projects/foreman/issues?query_id=24 > > The new foreman-debug script can be used to collect and provide > information > about your setup, and the result attached to bug reports. Also on RHEL > 6.5+ > you can use sosreport to do the same. > > Thanks for using Foreman. > > -- > Later, > > Lukas "lzap" Zapletal > irc: lzap #theforeman >

On Monday, October 14, 2013 5:38:27 PM UTC+2, Lukas Zapletal wrote:

Hello all,

it is finally here. Foreman 1.3 has been released.

Improvements were made in the installation process, API, scalability (for
importing reports and facts see bellow), existing hosts mapping to compute
resources, and more. There is now a new official CLI.

Upgrade needs your attention, please read BEFORE YOU UPGRADE section
bellow
first.

Key features:

  • Hammer - Foreman CLI
  • Google Compute Engine as a Compute Resource
  • Installer auto-registers smart-proxy
  • Libvirt Spice support
  • Map between existing VM’s and foreman hosts
  • User authentication based on LDAP filter
  • Relax requirement for providing host IP (e.g. when using tokens)
  • foreman-rake command to avoid long SCL commands
  • exciting Plugins are now in a new packaged in the plugins repo
  • API v2 improvements
  • New translations (British English, Chinese Simplified, French,
    Galcian,
    German and Spanish)

Full release notes:

Foreman :: Manual

BEFORE YOU UPGRADE

Database Backup

While its normally recommended to backup your foreman database on a
regular
bases, we strongly suggest that you do that prior upgrading, as we now
enforce foreign keys in Foreman database, this means that the update
process
will delete all unrequired leftover / orphaned records.

Fact and Report upload changes

In order to reduce load and improve the performance of the foreman server
(or
servers) it no longer requires puppet to be installed in order to parse
puppet
facts and reports, as a result, the way facts and reports are uploaded was
changed. Specifically, Foreman itself now uses a JSON format, and the ENC
(node.rb) and Puppet report processor (foreman.rb) have been updated to
handle
changing Puppet-specific data into JSON. Existing ENC/Reports scripts will
need a change to the latest version, which can be found in the installer
git
repository:

  • external_node_v2.rb.erb
  • foreman-report_v2.rb.erb

If reporting is being used, please update these scripts during the upgrade
(or
just use our installer).

After upgrade is finished, do check your instance and identify if you are
not
missing any records in the database, including things which are not being
used
every day. Again, the database migration can delete orphaned records, it
is
very important to identify this as early as possible.

Packages

Package repos are available here:

http://yum.theforeman.org/releases/1.3/
http://yum.theforeman.org/plugins/1.3/

http://deb.theforeman.org/ (“stable” component)

Quickstart instructions are here:

Foreman :: Manual

Tarballs available here:

Files - Foreman

Installation

There is a new installer for Foreman 1.3, it has many new options that are
taken directly from puppet class parameters. Check the help screen or
install
with default options directly:

# foreman-installer

Our new installer now provides many configuration options, or you can
still
use interactive mode. Use --help for more info.

Known issues

** Proxy registration happens before Apache is started **

You may encounter failure during proxy registration (Foreman_smartproxy
puppet
class). In that case if you see 404 error while registering proxy, please
re-run the installer and the error should disappear.

Bug #3083: Proxy registration happens before Apache is started - Installer - Foreman

** Rake task db:convert:prod2dev fails **

Due to foreign keys, prod2dev migration rake task fails. We already have a
patch ready and we will release the fix soon.

Bug #3212: defer MySQL foreign key constraints for rake db:convert:prod2dev - Foreman

** Diff view display style is incorrect **

Diff view in provisioning templates does has incorrect CSS. You can
download an
experimental workaround patch already today if you need it.

Bug #2816: diff view broken - Foreman

Reporting issues

Please report issues found in Foreman 1.3 in redmine.

Foreman: Foreman
Proxy: Foreman
Installer: Foreman

Existing bug reports are listed here:
Foreman 1.3.2 issues - Foreman

The new foreman-debug script can be used to collect and provide
information
about your setup, and the result attached to bug reports. Also on RHEL
6.5+
you can use sosreport to do the same.

Thanks for using Foreman.

–
Later,

Lukas “lzap” Zapletal
irc: lzap #theforeman

On Monday, October 14, 2013 5:38:27 PM UTC+2, Lukas Zapletal wrote:

Hello all,

it is finally here. Foreman 1.3 has been released.

Improvements were made in the installation process, API, scalability (for
importing reports and facts see bellow), existing hosts mapping to compute
resources, and more. There is now a new official CLI.

Upgrade needs your attention, please read BEFORE YOU UPGRADE section
bellow
first.

Key features:

  • Hammer - Foreman CLI
  • Google Compute Engine as a Compute Resource
  • Installer auto-registers smart-proxy
  • Libvirt Spice support
  • Map between existing VM’s and foreman hosts
  • User authentication based on LDAP filter
  • Relax requirement for providing host IP (e.g. when using tokens)
  • foreman-rake command to avoid long SCL commands
  • exciting Plugins are now in a new packaged in the plugins repo
  • API v2 improvements
  • New translations (British English, Chinese Simplified, French,
    Galcian,
    German and Spanish)

Full release notes:

Foreman :: Manual

BEFORE YOU UPGRADE

Database Backup

While its normally recommended to backup your foreman database on a
regular
bases, we strongly suggest that you do that prior upgrading, as we now
enforce foreign keys in Foreman database, this means that the update
process
will delete all unrequired leftover / orphaned records.

Fact and Report upload changes

In order to reduce load and improve the performance of the foreman server
(or
servers) it no longer requires puppet to be installed in order to parse
puppet
facts and reports, as a result, the way facts and reports are uploaded was
changed. Specifically, Foreman itself now uses a JSON format, and the ENC
(node.rb) and Puppet report processor (foreman.rb) have been updated to
handle
changing Puppet-specific data into JSON. Existing ENC/Reports scripts will
need a change to the latest version, which can be found in the installer
git
repository:

  • external_node_v2.rb.erb
  • foreman-report_v2.rb.erb

If reporting is being used, please update these scripts during the upgrade
(or
just use our installer).

After upgrade is finished, do check your instance and identify if you are
not
missing any records in the database, including things which are not being
used
every day. Again, the database migration can delete orphaned records, it
is
very important to identify this as early as possible.

Packages

Package repos are available here:

http://yum.theforeman.org/releases/1.3/
http://yum.theforeman.org/plugins/1.3/

http://deb.theforeman.org/ (“stable” component)

Quickstart instructions are here:

Foreman :: Manual

Tarballs available here:

Files - Foreman

Installation

There is a new installer for Foreman 1.3, it has many new options that are
taken directly from puppet class parameters. Check the help screen or
install
with default options directly:

# foreman-installer

Our new installer now provides many configuration options, or you can
still
use interactive mode. Use --help for more info.

Known issues

** Proxy registration happens before Apache is started **

You may encounter failure during proxy registration (Foreman_smartproxy
puppet
class). In that case if you see 404 error while registering proxy, please
re-run the installer and the error should disappear.

Bug #3083: Proxy registration happens before Apache is started - Installer - Foreman

** Rake task db:convert:prod2dev fails **

Due to foreign keys, prod2dev migration rake task fails. We already have a
patch ready and we will release the fix soon.

Bug #3212: defer MySQL foreign key constraints for rake db:convert:prod2dev - Foreman

** Diff view display style is incorrect **

Diff view in provisioning templates does has incorrect CSS. You can
download an
experimental workaround patch already today if you need it.

Bug #2816: diff view broken - Foreman

Reporting issues

Please report issues found in Foreman 1.3 in redmine.

Foreman: Foreman
Proxy: Foreman
Installer: Foreman

Existing bug reports are listed here:
Foreman 1.3.2 issues - Foreman

The new foreman-debug script can be used to collect and provide
information
about your setup, and the result attached to bug reports. Also on RHEL
6.5+
you can use sosreport to do the same.

Thanks for using Foreman.

–
Later,

Lukas “lzap” Zapletal
irc: lzap #theforeman

4

Also updated our dev boxes, with relatively few issues.

Is there a timeline for the official release of the 1.3 Puppet modules? I
noticed the github repo is up to 1.3, but the Forge versions are still at
1.2.

Thanks!

··· On Monday, October 14, 2013 11:38:27 AM UTC-4, Lukas Zapletal wrote: > > Hello all, > > it is finally here. Foreman 1.3 has been released. > > Improvements were made in the installation process, API, scalability (for > importing reports and facts see bellow), existing hosts mapping to compute > resources, and more. There is now a new official CLI. > > Upgrade needs your attention, please read BEFORE YOU UPGRADE section > bellow > first. > > Key features: > > * Hammer - Foreman CLI > * Google Compute Engine as a Compute Resource > * Installer auto-registers smart-proxy > * Libvirt Spice support > * Map between existing VM's and foreman hosts > * User authentication based on LDAP filter > * Relax requirement for providing host IP (e.g. when using tokens) > * foreman-rake command to avoid long SCL commands > * exciting Plugins are now in a new packaged in the plugins repo > * API v2 improvements > * New translations (British English, Chinese Simplified, French, > Galcian, > German and Spanish) > > Full release notes: > > http://theforeman.org/manuals/1.3/index.html#Releasenotesfor1.3 > > ## BEFORE YOU UPGRADE ## > > ### Database Backup ### > > While its normally recommended to backup your foreman database on a > regular > bases, we strongly suggest that you do that prior upgrading, as we now > enforce foreign keys in Foreman database, this means that the update > process > *will delete* all unrequired leftover / orphaned records. > > ### Fact and Report upload changes ### > > In order to reduce load and improve the performance of the foreman server > (or > servers) it no longer requires puppet to be installed in order to parse > puppet > facts and reports, as a result, the way facts and reports are uploaded was > changed. Specifically, Foreman itself now uses a JSON format, and the ENC > (node.rb) and Puppet report processor (foreman.rb) have been updated to > handle > changing Puppet-specific data into JSON. Existing ENC/Reports scripts will > need a change to the latest version, which can be found in the installer > git > repository: > > - external_node_v2.rb.erb > - foreman-report_v2.rb.erb > > If reporting is being used, please update these scripts during the upgrade > (or > just use our installer). > > After upgrade is finished, do check your instance and identify if you are > not > missing any records in the database, including things which are not being > used > every day. Again, the database migration can delete orphaned records, it > is > very important to identify this as early as possible. > > ## Packages ## > > Package repos are available here: > > http://yum.theforeman.org/releases/1.3/ > http://yum.theforeman.org/plugins/1.3/ > > http://deb.theforeman.org/ ("stable" component) > > Quickstart instructions are here: > > http://theforeman.org/manuals/1.3/index.html#2.Quickstart > > Tarballs available here: > > http://projects.theforeman.org/projects/foreman/files > > ## Installation ## > > There is a new installer for Foreman 1.3, it has many new options that are > taken directly from puppet class parameters. Check the help screen or > install > with default options directly: > > # foreman-installer > > Our new installer now provides many configuration options, or you can > still > use interactive mode. Use --help for more info. > > ## Known issues ## > > ** Proxy registration happens before Apache is started ** > > You may encounter failure during proxy registration (Foreman_smartproxy > puppet > class). In that case if you see 404 error while registering proxy, please > re-run the installer and the error should disappear. > > http://projects.theforeman.org/issues/3083 > > ** Rake task db:convert:prod2dev fails ** > > Due to foreign keys, prod2dev migration rake task fails. We already have a > patch ready and we will release the fix soon. > > http://projects.theforeman.org/issues/3212 > > ** Diff view display style is incorrect ** > > Diff view in provisioning templates does has incorrect CSS. You can > download an > experimental workaround patch already today if you need it. > > http://projects.theforeman.org/issues/2816 > > ## Reporting issues ## > > Please report issues found in Foreman 1.3 in redmine. > > Foreman: http://projects.theforeman.org/projects/foreman/issues/new > Proxy: http://projects.theforeman.org/projects/smart-proxy/issues/new > Installer: http://projects.theforeman.org/projects/kafo/issues/new > > Existing bug reports are listed here: > http://projects.theforeman.org/projects/foreman/issues?query_id=24 > > The new foreman-debug script can be used to collect and provide > information > about your setup, and the result attached to bug reports. Also on RHEL > 6.5+ > you can use sosreport to do the same. > > Thanks for using Foreman. > > -- > Later, > > Lukas "lzap" Zapletal > irc: lzap #theforeman >
5

Hello,

··· On Monday 14 of October 2013 18:41:42 Chris Long wrote: > I have tried to install this using the debian instructions on theforeman > website Quickstart: > > http://theforeman.org/manuals/1.1/index.html#3.2.1Installation

you use old manual (which points to old installer), try this
http://theforeman.org/manuals/1.3/index.html#3.2.1Installation

–
Marek

and it returns this error when trying to run the ruby file:

ruby /usr/share/foreman-installer/generate_answers.rb
ruby: No such file or directory –
/usr/share/foreman-installer/generate_answers.rb (LoadError)

I tried to find this on the machine and it can’t be found anywhere.

Can you help please?

On Tuesday, October 15, 2013 1:38:27 AM UTC+10, Lukas Zapletal wrote:

Hello all,

it is finally here. Foreman 1.3 has been released.

Improvements were made in the installation process, API, scalability (for
importing reports and facts see bellow), existing hosts mapping to compute
resources, and more. There is now a new official CLI.

Upgrade needs your attention, please read BEFORE YOU UPGRADE section
bellow
first.

Key features:

  • Hammer - Foreman CLI
  • Google Compute Engine as a Compute Resource
  • Installer auto-registers smart-proxy
  • Libvirt Spice support
  • Map between existing VM’s and foreman hosts
  • User authentication based on LDAP filter
  • Relax requirement for providing host IP (e.g. when using tokens)
  • foreman-rake command to avoid long SCL commands
  • exciting Plugins are now in a new packaged in the plugins repo
  • API v2 improvements
  • New translations (British English, Chinese Simplified, French,

Galcian,

German and Spanish)

Full release notes:

Foreman :: Manual

BEFORE YOU UPGRADE

Database Backup

While its normally recommended to backup your foreman database on a
regular
bases, we strongly suggest that you do that prior upgrading, as we now
enforce foreign keys in Foreman database, this means that the update
process
will delete all unrequired leftover / orphaned records.

Fact and Report upload changes

In order to reduce load and improve the performance of the foreman server
(or
servers) it no longer requires puppet to be installed in order to parse
puppet
facts and reports, as a result, the way facts and reports are uploaded was
changed. Specifically, Foreman itself now uses a JSON format, and the ENC
(node.rb) and Puppet report processor (foreman.rb) have been updated to
handle
changing Puppet-specific data into JSON. Existing ENC/Reports scripts will
need a change to the latest version, which can be found in the installer
git

repository:

  • external_node_v2.rb.erb
  • foreman-report_v2.rb.erb

If reporting is being used, please update these scripts during the upgrade
(or
just use our installer).

After upgrade is finished, do check your instance and identify if you are
not
missing any records in the database, including things which are not being
used
every day. Again, the database migration can delete orphaned records, it
is
very important to identify this as early as possible.

Packages

Package repos are available here:

http://yum.theforeman.org/releases/1.3/
http://yum.theforeman.org/plugins/1.3/

http://deb.theforeman.org/ (“stable” component)

Quickstart instructions are here:

Foreman :: Manual

Tarballs available here:

Files - Foreman

Installation

There is a new installer for Foreman 1.3, it has many new options that are
taken directly from puppet class parameters. Check the help screen or
install

with default options directly:
# foreman-installer

Our new installer now provides many configuration options, or you can
still
use interactive mode. Use --help for more info.

Known issues

** Proxy registration happens before Apache is started **

You may encounter failure during proxy registration (Foreman_smartproxy
puppet
class). In that case if you see 404 error while registering proxy, please
re-run the installer and the error should disappear.

Bug #3083: Proxy registration happens before Apache is started - Installer - Foreman

** Rake task db:convert:prod2dev fails **

Due to foreign keys, prod2dev migration rake task fails. We already have a
patch ready and we will release the fix soon.

Bug #3212: defer MySQL foreign key constraints for rake db:convert:prod2dev - Foreman

** Diff view display style is incorrect **

Diff view in provisioning templates does has incorrect CSS. You can
download an
experimental workaround patch already today if you need it.

Bug #2816: diff view broken - Foreman

Reporting issues

Please report issues found in Foreman 1.3 in redmine.

Foreman: Foreman
Proxy: Foreman
Installer: Foreman

Existing bug reports are listed here:
Foreman 1.3.2 issues - Foreman

The new foreman-debug script can be used to collect and provide
information
about your setup, and the result attached to bug reports. Also on RHEL
6.5+
you can use sosreport to do the same.

Thanks for using Foreman.

Lukas “lzap” Zapletal
irc: lzap #theforeman

–
Marek

6

Hey,

I will do that today.

LZ

··· On Thu, Oct 24, 2013 at 01:58:06PM -0700, jcmcken@gmail.com wrote: > Also updated our dev boxes, with relatively few issues. > > Is there a timeline for the official release of the 1.3 Puppet modules? I > noticed the github repo is up to 1.3, but the Forge versions are still at > 1.2. > > Thanks! > > On Monday, October 14, 2013 11:38:27 AM UTC-4, Lukas Zapletal wrote: > > > > Hello all, > > > > it is finally here. Foreman 1.3 has been released. > > > > Improvements were made in the installation process, API, scalability (for > > importing reports and facts see bellow), existing hosts mapping to compute > > resources, and more. There is now a new official CLI. > > > > Upgrade needs your attention, please read BEFORE YOU UPGRADE section > > bellow > > first. > > > > Key features: > > > > * Hammer - Foreman CLI > > * Google Compute Engine as a Compute Resource > > * Installer auto-registers smart-proxy > > * Libvirt Spice support > > * Map between existing VM's and foreman hosts > > * User authentication based on LDAP filter > > * Relax requirement for providing host IP (e.g. when using tokens) > > * foreman-rake command to avoid long SCL commands > > * exciting Plugins are now in a new packaged in the plugins repo > > * API v2 improvements > > * New translations (British English, Chinese Simplified, French, > > Galcian, > > German and Spanish) > > > > Full release notes: > > > > http://theforeman.org/manuals/1.3/index.html#Releasenotesfor1.3 > > > > ## BEFORE YOU UPGRADE ## > > > > ### Database Backup ### > > > > While its normally recommended to backup your foreman database on a > > regular > > bases, we strongly suggest that you do that prior upgrading, as we now > > enforce foreign keys in Foreman database, this means that the update > > process > > *will delete* all unrequired leftover / orphaned records. > > > > ### Fact and Report upload changes ### > > > > In order to reduce load and improve the performance of the foreman server > > (or > > servers) it no longer requires puppet to be installed in order to parse > > puppet > > facts and reports, as a result, the way facts and reports are uploaded was > > changed. Specifically, Foreman itself now uses a JSON format, and the ENC > > (node.rb) and Puppet report processor (foreman.rb) have been updated to > > handle > > changing Puppet-specific data into JSON. Existing ENC/Reports scripts will > > need a change to the latest version, which can be found in the installer > > git > > repository: > > > > - external_node_v2.rb.erb > > - foreman-report_v2.rb.erb > > > > If reporting is being used, please update these scripts during the upgrade > > (or > > just use our installer). > > > > After upgrade is finished, do check your instance and identify if you are > > not > > missing any records in the database, including things which are not being > > used > > every day. Again, the database migration can delete orphaned records, it > > is > > very important to identify this as early as possible. > > > > ## Packages ## > > > > Package repos are available here: > > > > http://yum.theforeman.org/releases/1.3/ > > http://yum.theforeman.org/plugins/1.3/ > > > > http://deb.theforeman.org/ ("stable" component) > > > > Quickstart instructions are here: > > > > http://theforeman.org/manuals/1.3/index.html#2.Quickstart > > > > Tarballs available here: > > > > http://projects.theforeman.org/projects/foreman/files > > > > ## Installation ## > > > > There is a new installer for Foreman 1.3, it has many new options that are > > taken directly from puppet class parameters. Check the help screen or > > install > > with default options directly: > > > > # foreman-installer > > > > Our new installer now provides many configuration options, or you can > > still > > use interactive mode. Use --help for more info. > > > > ## Known issues ## > > > > ** Proxy registration happens before Apache is started ** > > > > You may encounter failure during proxy registration (Foreman_smartproxy > > puppet > > class). In that case if you see 404 error while registering proxy, please > > re-run the installer and the error should disappear. > > > > http://projects.theforeman.org/issues/3083 > > > > ** Rake task db:convert:prod2dev fails ** > > > > Due to foreign keys, prod2dev migration rake task fails. We already have a > > patch ready and we will release the fix soon. > > > > http://projects.theforeman.org/issues/3212 > > > > ** Diff view display style is incorrect ** > > > > Diff view in provisioning templates does has incorrect CSS. You can > > download an > > experimental workaround patch already today if you need it. > > > > http://projects.theforeman.org/issues/2816 > > > > ## Reporting issues ## > > > > Please report issues found in Foreman 1.3 in redmine. > > > > Foreman: http://projects.theforeman.org/projects/foreman/issues/new > > Proxy: http://projects.theforeman.org/projects/smart-proxy/issues/new > > Installer: http://projects.theforeman.org/projects/kafo/issues/new > > > > Existing bug reports are listed here: > > http://projects.theforeman.org/projects/foreman/issues?query_id=24 > > > > The new foreman-debug script can be used to collect and provide > > information > > about your setup, and the result attached to bug reports. Also on RHEL > > 6.5+ > > you can use sosreport to do the same. > > > > Thanks for using Foreman. > > > > -- > > Later, > > > > Lukas "lzap" Zapletal > > irc: lzap #theforeman > >

–
Later,

Lukas “lzap” Zapletal
irc: lzap #theforeman

7

Hi, everyone, can i find api to update or add lookup_values for a host？

··· On Fri, Oct 25, 2013 at 4:58 AM, wrote:

Also updated our dev boxes, with relatively few issues.

Is there a timeline for the official release of the 1.3 Puppet modules? I
noticed the github repo is up to 1.3, but the Forge versions are still at
1.2.

Thanks!

On Monday, October 14, 2013 11:38:27 AM UTC-4, Lukas Zapletal wrote:

Hello all,

it is finally here. Foreman 1.3 has been released.

Improvements were made in the installation process, API, scalability (for
importing reports and facts see bellow), existing hosts mapping to
compute
resources, and more. There is now a new official CLI.

Upgrade needs your attention, please read BEFORE YOU UPGRADE section
bellow
first.

Key features:

  • Hammer - Foreman CLI
  • Google Compute Engine as a Compute Resource
  • Installer auto-registers smart-proxy
  • Libvirt Spice support
  • Map between existing VM’s and foreman hosts
  • User authentication based on LDAP filter
  • Relax requirement for providing host IP (e.g. when using tokens)
  • foreman-rake command to avoid long SCL commands
  • exciting Plugins are now in a new packaged in the plugins repo
  • API v2 improvements
  • New translations (British English, Chinese Simplified, French,
    Galcian,
    German and Spanish)

Full release notes:

http://theforeman.org/manuals/**1.3/index.html#**Releasenotesfor1.3http://theforeman.org/manuals/1.3/index.html#Releasenotesfor1.3

BEFORE YOU UPGRADE

Database Backup

While its normally recommended to backup your foreman database on a
regular
bases, we strongly suggest that you do that prior upgrading, as we now
enforce foreign keys in Foreman database, this means that the update
process
will delete all unrequired leftover / orphaned records.

Fact and Report upload changes

In order to reduce load and improve the performance of the foreman server
(or
servers) it no longer requires puppet to be installed in order to parse
puppet
facts and reports, as a result, the way facts and reports are uploaded
was
changed. Specifically, Foreman itself now uses a JSON format, and the ENC
(node.rb) and Puppet report processor (foreman.rb) have been updated to
handle
changing Puppet-specific data into JSON. Existing ENC/Reports scripts
will
need a change to the latest version, which can be found in the installer
git
repository:

  • external_node_v2.rb.erb
  • foreman-report_v2.rb.erb

If reporting is being used, please update these scripts during the
upgrade (or
just use our installer).

After upgrade is finished, do check your instance and identify if you are
not
missing any records in the database, including things which are not being
used
every day. Again, the database migration can delete orphaned records, it
is
very important to identify this as early as possible.

Packages

Package repos are available here:

http://yum.theforeman.org/**releases/1.3/http://yum.theforeman.org/releases/1.3/
http://yum.theforeman.org/**plugins/1.3/http://yum.theforeman.org/plugins/1.3/

http://deb.theforeman.org/ (“stable” component)

Quickstart instructions are here:

http://theforeman.org/manuals/**1.3/index.html#2.Quickstarthttp://theforeman.org/manuals/1.3/index.html#2.Quickstart

Tarballs available here:

http://projects.theforeman.**org/projects/foreman/fileshttp://projects.theforeman.org/projects/foreman/files

Installation

There is a new installer for Foreman 1.3, it has many new options that
are
taken directly from puppet class parameters. Check the help screen or
install
with default options directly:

# foreman-installer

Our new installer now provides many configuration options, or you can
still
use interactive mode. Use --help for more info.

Known issues

** Proxy registration happens before Apache is started **

You may encounter failure during proxy registration (Foreman_smartproxy
puppet
class). In that case if you see 404 error while registering proxy, please
re-run the installer and the error should disappear.

http://projects.theforeman.**org/issues/3083http://projects.theforeman.org/issues/3083

** Rake task db:convert:prod2dev fails **

Due to foreign keys, prod2dev migration rake task fails. We already have
a
patch ready and we will release the fix soon.

http://projects.theforeman.**org/issues/3212http://projects.theforeman.org/issues/3212

** Diff view display style is incorrect **

Diff view in provisioning templates does has incorrect CSS. You can
download an
experimental workaround patch already today if you need it.

http://projects.theforeman.**org/issues/2816http://projects.theforeman.org/issues/2816

Reporting issues

Please report issues found in Foreman 1.3 in redmine.

Foreman: http://projects.theforeman.**org/projects/foreman/issues/**newhttp://projects.theforeman.org/projects/foreman/issues/new
Proxy: http://projects.theforeman.**org/projects/smart-proxy/**issues/newhttp://projects.theforeman.org/projects/smart-proxy/issues/new
Installer: http://projects.theforeman.**org/projects/kafo/issues/newhttp://projects.theforeman.org/projects/kafo/issues/new

Existing bug reports are listed here:
http://projects.theforeman.**org/projects/foreman/issues?**query_id=24http://projects.theforeman.org/projects/foreman/issues?query_id=24

The new foreman-debug script can be used to collect and provide
information
about your setup, and the result attached to bug reports. Also on RHEL
6.5+
you can use sosreport to do the same.

Thanks for using Foreman.

–
Later,

Lukas “lzap” Zapletal
irc: lzap #theforeman

–
You received this message because you are subscribed to the Google Groups
"Foreman users" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to foreman-users+unsubscribe@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at http://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/groups/opt_out.

–
Wentian Jiang
UnitedStack Inc.

8

> > I have tried to install this using the debian instructions on theforeman
> > website Quickstart:
> >
> > Foreman :: Manual
>
> you use old manual (which points to old installer), try this
> Foreman :: Manual

Right, out of my curiosity, how did you get there? Maybe I missed some
link that is pointing to 1.1 manual.

Thanks.

··· -- Later,

Lukas “lzap” Zapletal
irc: lzap #theforeman

9

Yes, this is new in Foreman 1.3 in APIv2. v2's still in development so
you'll find the format may change a little between major releases. Be
sure to use the "Accept: application/json; version=2" header to access it.

I uploaded the APIv2 docs here for now, until we can publish them:
http://people.redhat.com/~dcleal/apiv2/apidoc.html

The API you want for lookup_values if it's a smart class parameter is:
/api/puppetclasses/:class_name/smart_class_parameters/:parameter_name/override_values
(http://people.redhat.com/~dcleal/apiv2/apidoc/override_values.html)

As an example:

GET
http://0.0.0.0:3000/api/puppetclasses/activemq::config/smart_class_parameters/server_config/override_values
{
"override_values":
[
{
"id": 6,
"match": "hostgroup=Test1",
"value": "test"
}
]
}

Then you can POST to create new ones, or PUT to overwrite.

POST
http://0.0.0.0:3000/api/puppetclasses/activemq::config/smart_class_parameters/server_config/override_values
{
"match": "environment=production",
"value": "test2"
}

Hope that helps.

··· On 25/10/13 04:09, Wentian Jiang wrote: > Hi, everyone, can i find api to update or add lookup_values for a host？

–
Dominic Cleal
Red Hat Engineering

10

If you click on manual at the top it will show a drop down menu with the
various versions :slight_smile:

··· On Tuesday, October 15, 2013 10:05:48 AM UTC+2, Lukas Zapletal wrote: > > > > I have tried to install this using the debian instructions on > theforeman > > > website Quickstart: > > > > > > http://theforeman.org/manuals/1.1/index.html#3.2.1Installation > > > > you use old manual (which points to old installer), try this > > http://theforeman.org/manuals/1.3/index.html#3.2.1Installation > > Right, out of my curiosity, how did you get there? Maybe I missed some > link that is pointing to 1.1 manual. > > Thanks. > > -- > Later, > > Lukas "lzap" Zapletal > irc: lzap #theforeman >