📄️ Installing
System Requirements
📄️ Managing Host Groups
These should be structured similar to how you would structure an AD infrastructure
📄️ Managing Configurations
This is done using Puppet. A git repository should be configured to store the code. This will provide you with a log of who changed the configuration and when. Syncing the repository can be done using R10k.
🗃️ Puppet
1 items
📄️ Provisioning
There a few choices to get everything started, but the processes have fairly similar dependencies
📄️ Kickstart in Azure
Using Kickstart in Azure gives you a way to utilize all of your existing on-prem processes in the Cloud. However, you can't directly boot an ISO. Instead you need to convert it to a VHD. Here are the steps to convert the bootdisk Satellite creates in to a VHD that you can then use in Azure.
📄️ Remote Execution
Remote Exection Jobs can be used to accomplish tasks remotely. Satellite supports jobs written in either Bash or Ansible. I would recommend you write them in Ansible. Because Ansible is idempotent, you don't need to worry about running it multiple times against the same machine and is less likely to cause an issue with your machines. The version of Ansible built in to Satellite does have some limitations but is a good starting point. As your usage of Ansible expands, you may want to look in to AAP. Satellite and AAP can share information so actions are taken on AAP while the inventory is stored in Satellite.