-
Notifications
You must be signed in to change notification settings - Fork 29
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
Need explanations to use the installation part #38
Comments
First I will warn you that the install part is the least worked out and while it does work in my lab I probably could improve it some more.
We have this lab (it is outdated) but maybe if you review it, it will help explain how some of the parts work (we don't get into install) and then from there help you with your template. If you still have questions let me know. |
@djdanielsson thanks a lot for taking the time to explain everything! I'll need to check your answer of the 3rd item next week. I got an SSH error when the script attempt to connect to others nodes despite my key been on every nodes. I hope I can find time to create a step by step guide that would help newcomers like me. |
@djdanielsson I tried using a RHEL install instead of Fedora but haven't go much further. I searched a bit on console.redhat.com but was unable to find how to create a token for the I found why Also, I'm using the following EE: registry.redhat.io/ansible-automation-platform-24/ee-supported-rhel9 and I get the following error: Please install By fixing build_ee.yml file by adding "connection: local" in the header, I now get this error: Failed to find required executable "podman" in paths: /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin" And of course, podman is not installed in the EE I use. I'm starting to think I should not use ansible-navigator for the first installation. But follow the lab and use ansible-playbook instead. But after logging to the future control node, when running I compared the lab and the current state of the repo, I see a major difference. In the lab you didn't use the group "dev" with 127.0.0.1 and local connection. I think it's the root of my issues since the playbook is now attempting to install stuff inside de EE instead of the control node. Maybe the solution to all this would be to create a custom EE for this project designed to provision AAP and publish this in a public registry? |
@laurent-indermuehle are you in our matrix channel? |
@djdanielsson I'm in many ansible rooms. Is it #awx:ansible.com? I'm also on forum.ansible.com |
Also, I'm wondering what the It is only present in: Do we want to use the same password for the admin accounts of the controller and hub? Or are they supposed to be different? Because in the vault we have both |
Thanks to @djdanielsson, @sean-m-sullivan for your time during the Office Hours today. |
Hi and thanks to all the contributors for this template! It is exactly what I needed.
I thinks the documentation for the installation of AAP could be more explanatory. I'm having trouble using this template to install Ansible Automation Platform and think additional explanations would help. I may offer a pull request once I've sorted this out but first I need your help to understand how this repo works please.
It's unclear where the playbooks are meant to be run from - the server hosting one of the controllers or a workstation? I tried running them from my workstation but now have AAP uncompressed in /var/tmp. Not what I wanted.
The inventory_env.yml files are new to me. I previously configured the setup.sh inventory for AAP/AWX node types and placements. How do these files work with bundle installation or the Technical Preview containerized installer? I see I need to add aap_setup_down_type: setup-bundle but details would help.
Without step-by-step SSH key generation guidance, getting all AAP nodes to communicate is difficult. Do I create a key on a controller node, copy the private key to other controllers, and add the public key to all nodes? More details would help ensure proper setup. As I'm getting permission denied even though the key are in place and work properly. Do I need to mount my .ssh folder inside the EE?
I've added a role preparing requirements like firewall and NTP - would you be interested in that contribution once I have the SSH keys working? I can then document the full process. Or is it intentionally left out of the scope of this template?
The text was updated successfully, but these errors were encountered: