Remote database support

[johnpmitsch]

it worked! :tada:

TASK [satellite-clone : debug] *******************************************************************************************************************************************************************
Friday 09 October 2020  22:54:21 +0000 (0:00:00.390)       0:49:22.683 ******** 
ok: [localhost] => {
    "msg": "****NOTE**** Your Satellite's hostname is updated to match the original Satellite ****NOTE**** Your Satellite's password is updated to changeme"
}

msg: ****NOTE**** Your Satellite's hostname is updated to match the original Satellite ****NOTE**** Your Satellite's password is updated to changeme

PLAY RECAP ***************************************************************************************************************************************************************************************
localhost                  : ok=74   changed=25   unreachable=0    failed=0   

I still would like to clean up a couple things and have an open question or two, but moving to ready for review as it is testable.

[johnpmitsch]

Passed the automated clones:

PLAY RECAP *********************************************************************
192.168.121.2              : ok=21   changed=16   unreachable=0    failed=0    skipped=3    rescued=0    ignored=0   
192.168.121.217            : ok=21   changed=16   unreachable=0    failed=0    skipped=3    rescued=0    ignored=0   
192.168.121.58             : ok=21   changed=16   unreachable=0    failed=0    skipped=3    rescued=0    ignored=0   
192.168.121.65             : ok=21   changed=16   unreachable=0    failed=0    skipped=3    rescued=0    ignored=0   

[sthirugn]

Great work. @johnpmitsch

[johnpmitsch]

Thanks @sthirugn! I updated the docs with your suggestions

[johnpmitsch]

I'm wondering if we should have some sort of warning about restoring a clone with remote databases. We do recommend all clones happen on an isolated network, but if they aren't able to isolate the network, the clone could try to drop the production database as the hostname will be the same.

I'm thinking we should just caveat the whole procedure as "experimental" and "at your own risk" while mentioning the risk of the clone talking to the production databases. This procedure likely will stay only in the upstream documentation until it's a more polished process.

@sthirugn @jturel thoughts?

[jturel]

@johnpmitsch good catch. how about a prompt which alludes to the severity of the implications of not being on an isolated network?

[johnpmitsch]

@johnpmitsch good catch. how about a prompt which alludes to the severity of the implications of not being on an isolated network?

Are you thinking for all clones or the ones who are cloning with remote databases? The latter may be harder to do as it's all based on passing additional installer options in, which wouldn't necessarily mean a remote database clone.

[jturel]

@johnpmitsch good catch. how about a prompt which alludes to the severity of the implications of not being on an isolated network?

Are you thinking for all clones or the ones who are cloning with remote databases? The latter may be harder to do as it's all based on passing additional installer options in, which wouldn't necessarily mean a remote database clone.

KISS and do it all the time would be my approach!

[sthirugn]

@johnpmitsch great work getting this in :+1: