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
While its normally recomended 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.
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.
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
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.
** 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
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 and please do spread the word.