-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
when run"ansible-playbook aker-freeipa.yml" #3
Comments
i change hosts into this: [freeipa_masters] [freeipa_clients] [aker_servers] [db_servers] [elk_servers] these ip is just like those in vagrantfile. am i correct? |
but these ip addrs is private ipaddr. do i need enter every vm to check another ip addr? cmd "ip addr" show in aker vm. [vagrant@aker ~]$ ip addr |
the private ip is static but ip of another interface is dynamic ,i think. so do i need to modify the hosts file after vms started. or use the private ip addr directly? |
HI @leochan007 You managed to get it I think :) As for your question about the IPs, this IPs in the vagrant file are static like you mentioned they will not change, the other interface however is used for vagrant operation itself, think of it like a management NIC. For interacting with Aker and its components use the IPs you mentioned like for example 192.168.122.10 . Did I miss anything ? |
@anazmy thx 4 your msg. but here is one more thing. how to use this playbook after everything is installed with no error? btw, i think this project is just a quickstart for Aker, and not a project in production. am i right? actually i have my freeipa(389ds server) for auth installed as a independent project with docker and docker-compose. so here come another question. how to config Aker directly with my own FreeIPA? thx. |
@leochan007 indeed you're right, in case you have freeipa already follow the readme in the Aker itself: |
after vagrant up.
then i run ansible-playbook cmd.
get these error:
PLAY ***************************************************************************
TASK [setup] *******************************************************************
fatal: [web2.ipa.example]: UNREACHABLE! => {"changed": false, "msg": "ERROR! SSH encountered an unknown error during the connection. We recommend you re-run the command using -vvvv, which will enable SSH debugging output to help diagnose the issue", "unreachable": true}
fatal: [db1.ipa.example]: UNREACHABLE! => {"changed": false, "msg": "ERROR! SSH encountered an unknown error during the connection. We recommend you re-run the command using -vvvv, which will enable SSH debugging output to help diagnose the issue", "unreachable": true}
fatal: [elasticsearch.ipa.example]: UNREACHABLE! => {"changed": false, "msg": "ERROR! SSH encountered an unknown error during the connection. We recommend you re-run the command using -vvvv, which will enable SSH debugging output to help diagnose the issue", "unreachable": true}
fatal: [aker.ipa.example]: UNREACHABLE! => {"changed": false, "msg": "ERROR! SSH encountered an unknown error during the connection. We recommend you re-run the command using -vvvv, which will enable SSH debugging output to help diagnose the issue", "unreachable": true}
fatal: [web1.ipa.example]: UNREACHABLE! => {"changed": false, "msg": "ERROR! SSH encountered an unknown error during the connection. We recommend you re-run the command using -vvvv, which will enable SSH debugging output to help diagnose the issue", "unreachable": true}
fatal: [master1.ipa.example]: UNREACHABLE! => {"changed": false, "msg": "ERROR! SSH encountered an unknown error during the connection. We recommend you re-run the command using -vvvv, which will enable SSH debugging output to help diagnose the issue", "unreachable": true}
fatal: [db2.ipa.example]: UNREACHABLE! => {"changed": false, "msg": "ERROR! SSH encountered an unknown error during the connection. We recommend you re-run the command using -vvvv, which will enable SSH debugging output to help diagnose the issue", "unreachable": true}
PLAY [Install FreeIPA role] ****************************************************
PLAY [Enroll FreeIPA clients] **************************************************
PLAY [Enroll FreeIPA clients] **************************************************
PLAY [Enroll FreeIPA clients] **************************************************
PLAY [Enroll FreeIPA clients] **************************************************
PLAY [Enroll FreeIPA clients] **************************************************
PLAY [install Elasticsearch] ***************************************************
PLAY [Install Aker] ************************************************************
PLAY RECAP *********************************************************************
aker.ipa.example : ok=0 changed=0 unreachable=1 failed=0
db1.ipa.example : ok=0 changed=0 unreachable=1 failed=0
db2.ipa.example : ok=0 changed=0 unreachable=1 failed=0
elasticsearch.ipa.example : ok=0 changed=0 unreachable=1 failed=0
master1.ipa.example : ok=0 changed=0 unreachable=1 failed=0
web1.ipa.example : ok=0 changed=0 unreachable=1 failed=0
web2.ipa.example : ok=0 changed=0 unreachable=1 failed=0
The text was updated successfully, but these errors were encountered: