For the full release notes, see the Changelog.
The installer has been updated to use the foreman-installer with a new feature known as scenarios. Scenarios provide a way to capture a precise set of installation options that can be re-used to install anything from a bare Foreman, to Katello to a Capsule. The initial scenarios being released are: Foreman, Katello and Caspule. For more information and examples, see the installation instructions.
Prior to Katello 2.0, Hosts were represented by two objects, Hosts and Content Hosts. Under some circumstances these two objects would be linked together but under other workflows they were not. In addition only one Host could exist with a given hostname but many Content Hosts could be registered with the same hostname. As part of Katello 3.0 we have attempted to unify hosts and content hosts into a single object. The “Content Hosts” page still exists but eventually everything there would be integrated into a unified Hosts ui.
As a result of Host Unification there are many subtle changes:
Users can now manage OSTree content through Katello in the same ways that RPM content can be managed. This includes creating OSTree repositories, syncing those repositories and adding them to content views. Similar to RPM content, Atomic machines can be provisioned from local OSTree content.
A new field has been added to repositories called download policy. With it, users can speed up repository synchronization by downloading only the repository’s metadata and deferring the download of content until later. The three values for download policy are immediate, on demand, and background. For on demand synchronization, only the metadata is downloaded during sync and packages are fetched and stored on the filesystem when clients request them. For background syncs, a background task will download all packages after the initial sync. The immediate option is what Katello currently provides where all metadata and packages are downloaded during sync. Currently, lazy sync is only available for yum repositories.
The management of Docker content has been upgraded to support Docker v2. This continues to involve the management of Docker content with repositories, syncing those repositories from an upstream registry and then publishing and promoting them through life cycle environments using content views. Docker v2 does, however, provide some fundamental differences with Docker v1. For example, rather than syncing Docker images and tags, the content synced will include manifests, tags and blobs. In addition, with Docker v2, there is no longer the ability to upload Docker content to a repository; therefore, repository syncing is the means to get that content in to Katello.
Repositories now have the option to be used in a “mirror on sync” state where the state of the repository mirrors that of the upstream repository at sync time. This results in packages no longer in the upstream repository being removed.
It is possible now to use Foreman remote execution plugin to execute the content actions (install package, errata etc.). This acts as an alternative to the current katello-agent capabilities and allows to execute the actions over SSH (or other providers that will by the remote execution plugin later). It also allows to customize the script to be run when executing the content action as well as some advanced execution options (delayed run, recurring, splay time etc.). See http://theforeman.org/plugins/foreman_remote_execution/ for more details on the remote execution plugin.
Proxy detail page was extended to provide statistics about synchronized content grouped by lifecycle environments, usage of pulp storage to warn users when the capsule is running out of disc space and information about synchronization status. The latter displays progress of current tasks when the synchronization is running. It also allows for starting and cancelling the synchronization process.
The ability to cancel synchronizations as well as showing the content counts are now reflected in the cli. You can find it in commands hammer capsule content cancel-synchronization and hammer capsule content info. Please note that the command capsule has became an alias to proxy and they share the same subcommands.
Users may now perform exports and imports of yum repositories to disk, either as a series of directories or as ISO files. This is especially useful for users in “air-gapped” network environments, where a Katello server might not have access to the Internet. Note that Inter-Server Sync (ISS) replaces the katello-disconnected tool. Additional information is available at (http://www.katello.org/plugins/katello/user_guide/disconnected/)[http://www.katello.org/plugins/katello/user_guide/disconnected/].
Adam Price firstname.lastname@example.org Adam Ruzicka Brad Buckingham email@example.com Bryan Kearney firstname.lastname@example.org Chris Duryee email@example.com Chris Peters firstname.lastname@example.org Christine Fouant email@example.com Daniel Lobato García firstname.lastname@example.org David Davis email@example.com Eric D Helms firstname.lastname@example.org Ivan Nečas email@example.com John Mitsch firstname.lastname@example.org Justin Sherrill email@example.com Kazuo Moriwaka Marek Hulan Martin Bačovský firstname.lastname@example.org Neil Miao email@example.com Ondrej Prazak firstname.lastname@example.org Partha Aji email@example.com Pavel Moravec firstname.lastname@example.org Ranjan Kumar Roman Plevka email@example.com Shlomi Zadok firstname.lastname@example.org Stephen Benjamin email@example.com Tom McKay firstname.lastname@example.org Tomas Strachota email@example.com Walden Raines firstname.lastname@example.org Zach Huntington-Meath thomasmckay email@example.com