Today we release the first of our Foreman 1.9 release candidates, and
ask for your help in testing the last four months of new features and
changes.
All help is appreciated to ensure our dot-zero release is solid, either
installing a new instance or upgrading a test server.
Headline features
···
=================
The web UI has had a few small quality-of-life enhancements that we hope
will make it more pleasant to use, such as new search-enabled dropdown
menus throughout the application, allowing you to quickly find one of
many items.
Parameters have gained a new full-screen editor (which was previously
only on provisioning templates) and partition tables also gained the
same features as provisioning templates for editing and revision control.
Foreman’s logging has become more granular so it’s now easier to enable
debugging of specific subsystems, which will expand in time, and you’ll
get more useful backtraces by default for filing bugs.
Two new email notifications, one listing recent audit activities, and
one for notifying when a host has built should give you more insight
into what’s going on.
Lastly, Libvirt has gained a new capability for using cloud-init when
image provisioning rather than only SSH finish scripts, which will make
it easy to use standard distro images.
A full list of the changes in Foreman 1.9 is in our release notes, and
we’ll continue documenting the new features in the coming weeks:
http://theforeman.org/manuals/1.9/index.html#Releasenotesfor1.9
Upgrading or installing
When upgrading, follow these instructions and please take note of any
known issues, we’ll update the manual if they arise.
http://theforeman.org/manuals/1.9/index.html#3.6Upgrade
If you’re installing a new test instance, follow the quickstart:
http://theforeman.org/manuals/1.9/index.html#2.Quickstart
Packages may be found in the 1.9 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:
BEA5 E3F6 AF59 7107 0241 4514 E05F 7157 6E2A 21BF
(Foreman :: Security)
Bug reporting
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.
Foreman: Foreman
Proxy: Foreman
Installer: Foreman
–
Dominic Cleal
Red Hat Engineering
> Today we release the first of our Foreman 1.9 release candidates, and
> ask for your help in testing the last four months of new features and
> changes.
>
> All help is appreciated to ensure our dot-zero release is solid, either
> installing a new instance or upgrading a test server.
>
> Headline features
> =================
> The web UI has had a few small quality-of-life enhancements that we hope
> will make it more pleasant to use, such as new search-enabled dropdown
> menus throughout the application, allowing you to quickly find one of
> many items.
>
> Parameters have gained a new full-screen editor (which was previously
> only on provisioning templates) and partition tables also gained the
> same features as provisioning templates for editing and revision control.
>
> Foreman's logging has become more granular so it's now easier to enable
> debugging of specific subsystems, which will expand in time, and you'll
> get more useful backtraces by default for filing bugs.
>
> Two new email notifications, one listing recent audit activities, and
> one for notifying when a host has built should give you more insight
> into what's going on.
>
> Lastly, Libvirt has gained a new capability for using cloud-init when
> image provisioning rather than only SSH finish scripts, which will make
> it easy to use standard distro images.
>
> A full list of the changes in Foreman 1.9 is in our release notes, and
> we'll continue documenting the new features in the coming weeks:
> Foreman :: Manual
Not exactly a feature but Google Compute Engine support as a compute
resource should work on Foreman 1.9 RC1, it was recently fixed and we
added support for multiple volumes.
http://projects.theforeman.org/issues/4551
Testers appreciated!
···
On 07/06, Dominic Cleal wrote:
>
> Upgrading or installing
> =======================
> When upgrading, follow these instructions and please take note of any
> known issues, we'll update the manual if they arise.
> http://theforeman.org/manuals/1.9/index.html#3.6Upgrade
>
> If you're installing a new test instance, follow the quickstart:
> http://theforeman.org/manuals/1.9/index.html#2.Quickstart
>
> Packages may be found in the 1.9 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:
> BEA5 E3F6 AF59 7107 0241 4514 E05F 7157 6E2A 21BF
> (http://theforeman.org/security.html#GPGkeys)
>
> Bug reporting
> =============
> 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.
>
> 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/puppet-foreman/issues/new
>
> --
> Dominic Cleal
> Red Hat Engineering
>
> --
> 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/d/optout.
–
Daniel Lobato Garcia
@eLobatoss
blog.daniellobato.me
daniellobato.me
GPG: http://keys.gnupg.net/pks/lookup?op=get&search=0x7A92D6DD38D6DE30
Keybase: https://keybase.io/elobato
