When will orcharhino 6.0 be released?

• Depending on the findings of our beta-testers, we are aiming to release orcharhino 6.0 in May 2022.

Will there be a migration path from Pulp 2 to Pulp 3 for existing smart proxies?

• There will be no migration like on orcharhino but different scenarios are possible.
• To keep the existing smart proxy: delete the content, upgrade and re-sync everything, Pulp 2 proxy will continue to work (needs orcharhino version >= 5.12.1) during orcharhino 6.0 → you do not need to switch to Pulp 3 immediately.

What is a good concept to follow in terms of content views, for base OS mixed in with add-ons and end-user repos?

• If possible keep it simple → one content view for all repos for one OS including add ons and third party repos.
• In case independent upgrades are needed → use Composite Content Views in components as needed.

How do you add an existing host properly?

• This depends on operating system and what you want to manage.
• In all Linux cases the easiest way would be bootstrapping (register host page will be the follow up solution to bootstrap script → works only for CentOS / RHEL at the moment).
• If done manually or with other tools → register via subscription-manager + ssh keys for remote execution (+ configuration management like Puppet / Salt)

When will Ubuntu 22.04 be available in orcharhino?

• Approximately mid May.
• It will be part of orcharhino 5.12.2
• And will be available in orcharhino 6.0

• • Errata will be available shortly.
  • There will be a separate client upon release.

Will there be RHEL 9 support for the release?

• RHEL 9 will be supported as managed system.

Are separate Content Views necessary for RHEL 7 and RHEL 8?

• We recommend to create separate Content Views for each version.

How is orcharhino client managed in Content Views?

• orcharhino client together with the respective OS should be packed in one Content View.
• Depending on the number of special cases / use cases, creating Composite Content Views makes sense or not.

If you have multiple locations, do you have to enter the virtualization settings for each location separately?

• Yes, but could also be automated with hammer-script or Ansible, if the settings are always the same.