-
Notifications
You must be signed in to change notification settings - Fork 0
dev10 server config
provisioning virtual machines on cgi
email or call cloud service desk.
1-877-505-2736 – option1 Cloud.ServiceDesk.INFRA@cgi.com
sudo cat yum.log
yum list installed
sudo yum install -y epel-release
sudo yum update -y
sudo yum install -y R
We manage CGI servers through the use of ansible, we have a private repository that contains our ansible configuration scripts. These scripts are deployed on server 7 and can also be used from a machine with the appropriate firewall rules exemptions if ansible is yum/pip installed locally.
We are using 7 as an ansible server within cgi. There is a shell script cgi_server_setup.sh that registers with red hat, updates yum, installs epel and installs ansible so that the ansible tools are available. This repo is currently kept in ~/git/qed_anisible directory.
#confirm installation
cat /etc/redhat-release
ansible --version
Ansible uses a hosts file that creates named keys for controlling hosts. Ours is located here. On servers it may be located in /etc/ansible/hosts.
[cgi1]
172.20.100.11
[cgi3]
172.20.100.13
etc..
Only machines added to the Ansible hosts file can be controlled with Ansible
We can test the ansible hosts by pinging them with the following commands. We do not have keys set up on cgi yet so this needs to be done one at a time.
ansible all -m ping # only if keys set up
ansible cgi3 -k -u cgifadmin -m ping
#-u => username to SSH into server with (cgifadmin)
#-k => prompt for user’s login password (since we do not currently use SSH keys)
ansible-playbook -k -K qed-cgi-environ.yml --extra-vars="host=cgiX"
ansible-playbook -k -K qed-pull-code.yml --extra-vars="host=cgiX"
Enter in SSH password for server 1
enter in sudo password = blank
enter in git credentials for private repos