Ansible Automation Platform 2.4 Single Node Installation: ARM-Based Infrastructure Automation

preview_player
Показать описание
Unlocking Seamless Integration, Scalability, and Performance for ARM Architectures.

Join this channel to get access to the perks:

BUY the Complete PDF BOOK to easily Copy and Paste the 200+ Ansible code
200+ Automation Examples For Linux and Windows System Administrators and DevOps

my VIDEO COURSE: Ansible by Examples
200+ Automation Examples For Linux and Windows System Administrators and DevOps
Рекомендации по теме
Комментарии
Автор

Thank you so much for this video, for the past days I was running into the SSH error. The ansible_connection=local was the solution I needed.

DESsimulation
Автор

I have an Error in my Mac would you help me ? the error is ->error al cargar el complemento "config manager":  '*prog'

renexorrg
Автор

Is private automation hub also installed in this mode? can I install ansible automation controller and private automation hub on the same node? do I need to define 2 different hostnames in /etc/hosts? thanks!

danieletrabucco
Автор

Hi, , I dont have domain name I am tried on aws so what would be my hostname

spawar
Автор

Hi Luca, can you please help me how to let node keep connecting with ansible controller when nodes have auotmaitcally ip assigned by dhcp and keep changes when system reboot. Suppose, I have node 1 and want to control it via ansible controller, but users use to reboot and shutdown it every day, so how would i make sure to keep connected with ansible controller with every nodes.? please please please help me on this.

Is it possible to connect nodes with ansible controller if nodes are assigned automatially ip by dhcp server.

NagenderGiri
Автор

Thank you, I was about to chuck my laptop out the window.

hawks
Автор

thank you buddy! Can I install it in Ubuntu 22.04 ? I will try it

davidodav
Автор

Hi this is my inventory which is setup on redhat 9.4 on aws..# control.example node_type=control
# hybrid.example node_type=hybrid
# hybrid2.example <- this will default to hybrid
[automationcontroller]
node_type=hybrid
[automationcontroller:vars]
peers=execution_nodes


# Execution Nodes
# There are two valid node_types that can be assigned for this group.
# A node_type=hop implies that the node will forward jobs to an execution node.
# A node_type=execution implies that the node will be able to run jobs.
# If you do not define the node_type, it defaults to execution.
#
# hop.example node_type=hop
# execution.example node_type=execution
# execution2.example <- this will default to execution
[execution_nodes]

[automationhub]
[automationedacontroller]

[database]

# Single Sign-On
# If sso_redirect_host is set, that will be used for application to connect to
# SSO for authentication. This must be reachable from client machines.
#
# ssohost.example sso_redirect_host=<host/ip>
[sso]

[all:vars]
admin_password='redhat'

pg_host=''
pg_port=5432

pg_database='awx'
pg_username='awx'
pg_password='redhat'
pg_sslmode='prefer' # set to 'verify-full' for client-side enforced SSL

spawar