Ansible role to configure a Red Hat Satellite Server for provisioning of Red Hat CoreOS nodes as part of an OpenShift 4 install
Any pre-requisites that may not be covered by Ansible itself or the role should be mentioned here. For instance, if the role uses the EC2 module, it may be a good idea to mention in this section that the boto package is required.
Variable | Default | Comments |
---|---|---|
ocp_version | "4.5.8" | OpenShift 4 Version Number |
rhcos_version | "4.5.6" | Red Hat CoreOS Version Number |
ocp_cluster_name | "caas" | OpenShift Cluster Name |
ocp_base_domain | "example.com" | OpenShift Base Domain Name |
sat_server | 'https://localhost' | Red Hat Satellite Server Url |
sat_ssl_enabled | false | Enable SSL with Satellite Server |
sat_username | 'admin' | Satellite Server User Name |
sat_password | 'password' | Satellite Server Password |
sat_org | "Disconnected Organization" | Satellite Server Organization |
sat_loc | "Disconnected Zone" | Satellite Server Location |
sat_compute_resource | "baremetal" | Satellite Server Compute Resource |
sat_compute_profile | "2-Medium" | Satellite Server Compute Profile |
sat_domain | "example.com" | Satellite Server Domain |
sat_subnet | "Private" | Satellite Server Subnet |
sat_hostgroup | "Coreos dev" | Satellite Server Hostgroup name |
coreos_ignition_url | "" | URL for ignition file |
coreos_install_dev | "vda" | CoreOS installation device |
A list of other roles hosted on Galaxy should go here, plus any details in regards to parameters that may need to be set for other roles, or variables that are used from other roles.
theforeman.foreman
role is required
Including an example of how to use your role (for instance, with variables passed in as parameters) is always nice for users too:
- hosts: servers
roles:
- { role: username.rolename, x: 42 }
2-clause BSD license, see LICENSE.md
- Dan Clark (maintainer)
- Calvin Smith (contributor)