3.8 KiB
Airship HostConfig Using Ansible Operator
This repo contains the code for Airship HostConfig Application using Ansible Operator
How to Run
Approach 1
If Kubernetes setup is not available please refer to README.md in k8s folder to bring up the kubernetes setup. It uses Vagrant and Virtual Box to bring up 1 master and 2 worker node VMs
After the VMs are up and running, connect to master node
vagrant ssh k8-master
Navigate to airship-host-config folder
cd airship-host-config/airship-host-config/
Execute the create_labels.sh file so that the Kubernetes nodes are labelled accordingly as master and worker nodes. We are also are attaching some sample zones and regions to the kubernetes nodes
./create_labels.sh
Execute the setup.sh script to build and copy the Airship Hostconfig Ansible Operator Image to worker nodes. It also deploys the application on the Kubernetes setup as deployment kind. The below script uses "vagrant" as username and password and executes the ansible host config role using on the Kubernetes Nodes using these credentials when we are create the HostConfig Kubernetes CR objects.
./setup.sh
If you want to execute the ansible playbook in the hostconfig example with a different user, you can also set the username and password of the Kuberntes nodes when executing the setup.sh. This uses the and passed to execute the hostconfig role on the kubernetes nodes when we are create the HostConfig Kubernetes CR objects.
./setup.sh <username> <password>
Approach 2
If Kubernetes setup is already available, please follow the below procedure
** Pre-requisites: Access to kubernetes setup using kubectl **
Set the Kubeconfig variable
export KUBECONFIG=~/.kube/config
Clone the repository
git clone https://github.com/SirishaGopigiri/airship-host-config.git
Navigate to airship-host-config folder
cd airship-host-config/airship-host-config/
Execute the setup.sh script to build and copy the Airship Hostconfig Ansible Operator Image to worker nodes. It also deploys the application on the Kubernetes setup as deployment kind. The below script uses "vagrant" as username and password and executes the ansible host config role using on the Kubernetes Nodes using these credentials when we create the HostConfig Kubernetes CR objects.
./setup.sh
If you want to execute the ansible playbook in the hostconfig example with a different user, you can also set the username and password of the Kuberntes nodes when executing the setup.sh. This uses the and passed to execute the hostconfig role on the kubernetes nodes when we create the HostConfig Kubernetes CR objects.
./setup.sh <username> <password>
Run Examples
After the setup.sh file executed successfully, navigate to demo_examples and execute the desired examples
Before executing the examples keep tailing the logs of the airship-host-config pod to see the ansible playbook getting executed while running the examples
kubectl get pods
kubectl logs -f <airship-host-config-pod-name>
Executing examples
cd demo_examples
kubectl apply -f example.yaml
kubectl apply -f example1.yaml
kubectl apply -f example2.yaml
Apart from the logs on the pod when we execute the hostconfig role we are creating a "tetsing" file on the kubernetes nodes, please check the contents in that file which states the time of execution of the hostconfig role by the HostConfig Ansible Operator Pod.
Execute below command on the kubernetes hosts to get the execution time.
cat /home/vagrant/testing
``
If the setup is configured using a different user, check using the below command
cat /home//testing
## Licensing
[Apache License, Version 2.0](http://opensource.org/licenses/Apache-2.0).