search

cloudera / cloudera-playbook

Cloudera deployment automation with Ansible
Apache License 2.0
198 stars 187 forks source link

Edit readme - playbook must be run from CM server #9

Closed alexbleakley closed 5 years ago

alexbleakley commented 6 years ago

Playbook must be run from the host designated as the CM server, else the user will run into issues with cm-api not being installed in the right place. Amended readme to add this info and to make clear that all steps must be taken from that same host.

lhoss commented 5 years ago

else the user will run into issues with cm-api not being installed in the right place

Of course' I just run into that issue, because I run the deployment from my laptop, onto a remote (AWS) node. But rather than to live with this hardly acceptable constraint, you just have to ensure that you got the cm-api (pip module) installed on the ansible controller node, as first explained here https://github.com/cloudera/cloudera-playbook/issues/15#issuecomment-399983171

If you run your deployment as root (or user with passwordless sudo), following 1-line fix will ensure that: github.com/ramencloud/cloudera-playbook-public/commit/d7cee4a92cf0b66e1754bcf1f6a190896759dbd2

roczei commented 5 years ago

Hi @alexbleakley,

You need to first sign and return an ICLA and CCLA before we can accept and redistribute your contribution. Once these are submitted you are free to start contributing to cloudera-playbook. Submit these to CLA@cloudera.com

Here you can find the pdf files:

https://github.com/cloudera/cloudera-playbook/tree/master/icla

Please update this issue (9) if you receive the confirmation from our CLA team.

Thank you!

dbeech commented 5 years ago

Closing this PR in favour of alternative solution proposed by @lhoss in comments. Will open separate issue/PR for this soon.