about satellite-clone-playbook.yml
There are many options for where you can run Satellite Clone from, but we specify and test a simple "one machine" installation. RHEL 7 machines are supported as that is what we test on, but Satellite Clone can run on any machine that has ansible installed and can communicate with your blank target machine you are cloning to. Here are some scenarios:
-
Use the blank target machine as the Ansible Control node. This is the "one machine" approach. You can clone the satellite-clone repo on this server, move the backups to the specified folder on the server, and then run the playbook from the repo. This is the scenario we detail in the docs.
-
Use the Satellite you are cloning as the Ansible Control node. You can clone the satellite-clone repo on the existing Satellite server and use that as the Control Node. The target machine is a blank target machine.
-
Use a separate machine as the Ansible Control Node. This is a machine that is seperate from the blank target machine you are cloning to and the Satellite you are cloning. The backups will have to be copied onto the blank target machine.
We only support and test the 1st scenario (the "one machine" approach detailed in our docs). If you are going to try any of the alternative scenarios, it is at your own risk.
Capsules are not able to be cloned at this time (Feb 2017). This is a planned feature.
Yes, the output of ansible playbook runs are stored in logs/playbook.log.