Migrated from legacy playbook repo into Ansible collection format: Roles (171 total): - common: 44 roles (fact gathering, SSH setup, utilities) - configuration: 32 roles (system config, networking, satellite) - provisioning: 16 roles (VMware, Azure, physical server deployment) - security: 15 roles (OpenSCAP hardening, certificates, AD integration) - monitoring: 12 roles (Zabbix, logging agents, metrics) - networking: 12 roles (DNS, DHCP, network interfaces) - satellite: 4 roles (Pulp/Satellite management) - misc: 36 roles (various utilities) Playbooks (159 total): - provisioning: 14 playbooks - azure: 13 playbooks - configuration: 22 playbooks - maintenance: 10 playbooks - security: 10 playbooks - monitoring: 9 playbooks - vcenter: 6 playbooks - networking: 7 playbooks - misc: 65 playbooks
Role Name
This role will publish a new version under a content view and promote it to a lifecycle environment. It should be run on the satellite server using a systemd timer.
On the DMZ content view:
primo.yml should run on the first Monday of the month
medio.yml should run on the third Monday of the month
custom.yml can be used to promote one content view to one lifecycle environment
Requirements
N/A
Role Variables
# Used by the primo.yml and medio.yml roles:
stage_short=Stage-Short2
prod_short=Prod-Short2
stage_long=Stage-Long2
prod_long=Prod-Long2
# Used by the custom.yml role:
custom_lifecycle_env=Production
# Used by all
content_view=ccta
Dependencies
N/A
Example
[servers]
servers.EXAMPLE-CORP.COM
[servers:vars]
stage_short=Stage-Short2
prod_short=Prod-Short2
stage_long=Stage-Long2
prod_long=Prod-Long2
content_view=dmz
# Run on the first Monday of the month:
ansible-playbook -l satellite satellite-push-updates.yml --tags "primo,untagged" --ask-pass --vault-password-file .vault_pass.txt
# Run on the third Monday of the month:
ansible-playbook -l satellite satellite-push-updates.yml --tags "medio,untagged" --ask-pass --vault-password-file .vault_pass.txt
License
BSD
Author Information
Created by the UFST Linux team