Open hopewise opened 8 years ago
http_proxy would be used if you are behind a corporate firewall. If you're behind a firewall, you oftentimes need to proxy http requests to reach the internet and therefore access yum. You would get the proxy info from your network admin. You can use an IP if you need to.
If you aren't behind a firewall or your router handles proxying requests for you, you can omit it or set it blank.
yea, thank you
What about: machine_un: root machine_pw: password
I am suing AWS, thus, I am using SSH keys, does your playbook support this option?
Not out of the box, but it should be a relatively easy modification. You would omit machine password and add the contents of your key to the private_key key in provision.json. Note that I've never tested this, I only deploy to physical hardware in a private datacenter.
Since you're on AWS, the OpsCenter API has a method of provisioning EC2 nodes but I've never tested that either, you can read about it here if you'd like to modify the role.. https://docs.datastax.com/en/opscenter/5.1/api/docs/provisioning.html#provisioning
Can you please describe the usage of httpproxy variable? why it's used for? I mean, why to add yum proxy anyway?
And can it be an IP address?