Automate Satellite Installation and Configuration using Ansible Roles
redhat.satellite
| Documentationredhat.satellite_operations
| Documentation
Both roles require the variable satellite_content_views
defined in different ways. To workaround this, the role task for content_view_publish
can be adjusted.
--- .ansible/collections/ansible_collections/redhat/satellite/roles/content_view_publish/tasks/main.yml 2023-03-15 22:34:42.626174482 +0100
+++ main.yml 2023-03-15 22:34:35.401170571 +0100
@@ -5,7 +5,7 @@
password: "{{ satellite_password | default(omit) }}"
server_url: "{{ satellite_server_url | default(omit) }}"
validate_certs: "{{ satellite_validate_certs | default(omit) }}"
- content_view: "{{ content_view }}"
+ content_view: "{{ content_view.name | default(content_view) }}"
organization: "{{ satellite_organization }}"
loop: "{{ satellite_content_views }}"
loop_control:
The fix is addressed upstream in Pullrequest #1571.
CPU: 4 cores
Memory: 20G
Disk: 100G
I used Red Hat Enterprise Linux 8.7 KVM Guest Image to install the basic operating system.
- Register the system at Red Hat Customer Portal, using an Activation-Key
- Configure required repositories
- Setup and Install Satellite dependencies
- Run basic installation of Satellite using
satellite-installer
- Download and import Subscirption Manifest
- Configure Lifecycle Environments
- Configure Red Hat Repositories
- Synchronize Red Hat Repositories (If tag
sync
is defined) - Configure content-views
- Publish content-views (If tag
publish
is defined) - Housekeeping of content-views (default: Only keep 1 additional version)
- Setup additional Satellite Settings
- Configure Activation Keys
To execute this playbook, run nfollwing command.
$ ansible-playbook satellite-dev.yml -K -b --ask-vault-pass --tags sync,publish