aker-gateway / aker-freeipa-playbook

GNU General Public License v3.0
13 stars 3 forks source link

when run"ansible-playbook aker-freeipa.yml" #3

Open leochan007 opened 7 years ago

leochan007 commented 7 years ago

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

leochan007 commented 7 years ago

i change hosts into this:

[freeipa_masters] 192.168.122.21

[freeipa_clients] 192.168.122.10 192.168.122.31 192.168.122.32 192.168.122.41 192.168.122.42

[aker_servers] 192.168.122.10

[db_servers] 192.168.122.41 192.168.122.42

[elk_servers] 192.168.122.50

these ip is just like those in vagrantfile.

am i correct?

leochan007 commented 7 years ago

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 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: ens5: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000 link/ether 52:54:00:2f:e4:d9 brd ff:ff:ff:ff:ff:ff inet 192.168.121.60/24 brd 192.168.121.255 scope global dynamic ens5 valid_lft 3104sec preferred_lft 3104sec inet6 fe80::4d99:287d:c74d:5573/64 scope link valid_lft forever preferred_lft forever 3: ens6: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000 link/ether 52:54:00:fd:d9:2f brd ff:ff:ff:ff:ff:ff inet 192.168.122.10/24 brd 192.168.122.255 scope global ens6 valid_lft forever preferred_lft forever inet6 fe80::5054:ff:fefd:d92f/64 scope link valid_lft forever preferred_lft forever

leochan007 commented 7 years ago

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?

anazmy commented 7 years ago

HI @leochan007 You managed to get it I think :) the hostnames should be resolvable, that's the reason of the first error you reported, you can just add entries in /etc/hosts to point to the right IPs from the vagrant file.

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 ?

leochan007 commented 7 years ago

@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.

anazmy commented 7 years ago

@leochan007 indeed you're right, in case you have freeipa already follow the readme in the Aker itself: https://github.com/aker-gateway/Aker