I'm happy to announce that we've reached the start of the Foreman 1.7
cycle, and it's time to ask for your help in testing and
battle-hardening our new release candidates.
All help is appreciated to ensure our dot-zero release is solid, either
installing a new instance or upgrading a test server.
···================= Foreman 1.7 features a handful of exciting enhancements to smart class parameters, providing better control over default values and merging of values across matchers.
A new build review page helps you check for common errors when switching
a host into build mode, such as template rendering problems.
Networking has been a big focus over the past few months, with support
for specifying bonds, VLANs and aliased interfaces on a host, importing
them from facts and using that information in provisioning templates and
via the ENC.
Two existing features have been moved into plugins, so they can be
developed outside of Foreman’s release cycle. If you’re using the
Rundeck integration, you should install the foreman_host_rundeck plugin,
and if you’re using the Chef Proxy feature then install the
smart_proxy_chef plugin to replace it.
This also marks the end of Debian 6 (Squeeze) support, and Ruby 1.8.7 in
the Foreman application (not the proxy or installer).
Much more information about the changes in Foreman 1.7 is available in
our release notes:
Upgrading or installing
When upgrading, follow these instructions and please take note of the
known issues and warnings (especially Ubuntu 12.04 users):
If you’re installing a new test instance, follow the quickstart:
Packages may be found in the 1.7 directories on both deb.foreman.org and
yum.theforeman.org, and tarballs are on downloads.theforeman.org.
The GPG key used for RPMs and tarballs has the following fingerprint:
730A 9338 F93E E729 2EAC 2052 4C25 8BD4 2D76 2E88
(Foreman :: Security)
If you come across a bug in your testing, please file it and note the
version of Foreman that you’re using in the report.
Red Hat Engineering