Infrastructure/infra-docs-fpo
1
0
Fork 0
Code Issues 100 Pull requests 6 Projects Releases Packages Wiki Activity Actions

Add the process for adding a new VM

Browse source 
Signed-off-by: Michal Konecny <mkonecny@redhat.com>
This commit is contained in:
Michal Konecny 2023-09-19 18:18:02 +02:00
parent 0599c31e93
commit 2d9b0e8538
3 changed files with 16 additions and 10 deletions
Download patch file Download diff file Expand all files Collapse all files

5
modules/sysadmin_guide/pages/ansible.adoc
View file

@ -225,8 +225,9 @@ Templates use the jinja2 syntax.
== Libvirt virtuals == Libvirt virtuals
* TODO: add steps to make new libvirt virtuals in staging and production === Add new virtual machine
* TODO: merge in new-hosts.txt
See xref:new-hosts.adoc[]
== Cloud Instances == Cloud Instances

2
modules/sysadmin_guide/pages/dns.adoc
View file

@ -62,7 +62,7 @@ $ git clone /srv/git/dns
=== Adding a new Host === Adding a new Host
Adding a new host requires to add it to DNS and to ansible, see Adding a new host requires to add it to DNS and to ansible, see
new-hosts.rst for the details. xref:new-hosts.adoc[] for the details.
=== Editing the domain(s) === Editing the domain(s)

19
modules/sysadmin_guide/pages/new-hosts.adoc
View file

@ -88,10 +88,10 @@ Once that is committed, you need to run a script to build the zones and
then push them to the dns servers.: then push them to the dns servers.:
.... ....
./do-domains # This builds the files sudo ./do-domains # This builds the files
git add . git add .
git commit -a -m 'done build' git commit -a -m 'done build'
git push sudo git push
$ sudo -i ansible ns\* -a '/usr/local/bin/update-dns' # This tells the dns servers to load the new files $ sudo -i ansible ns\* -a '/usr/local/bin/update-dns' # This tells the dns servers to load the new files
.... ....
@ -217,10 +217,6 @@ for example for _elections01.iad2.fedoraproject.org_ that would be:
ifconfig-push 192.168.1.44 192.168.0.44 ifconfig-push 192.168.1.44 192.168.0.44
.... ....
== Work in progress
From here to the end of file is still being worked on
=== host_vars and group_vars === host_vars and group_vars
ansible consults files in ansible consults files in
@ -263,6 +259,15 @@ The host will need vmhost declaration. There is a script in
how many free cpus each vmhost has. You can use that to inform your how many free cpus each vmhost has. You can use that to inform your
decision. By convention, staging hosts go on virthost12. decision. By convention, staging hosts go on virthost12.
[NOTE]
====
The `vhost-info` needs to be executed as `root` user on `batcave01`
....
python3.11 /srv/web/infra/ansible/scripts/vhost-info --host <ansible list of hosts or groups>
# for example virthost
....
====
Each vmhost has a different volume group. To figure out what volume Each vmhost has a different volume group. To figure out what volume
group that is, execute the following command on the virthost.: group that is, execute the following command on the virthost.:
@ -312,7 +317,7 @@ The host playbook is rather basic
* Most things won't change much * Most things won't change much
.... ....
ansible-playbook /srv/web/infra/ansible/infra/ansible/playbooks/grous/mailman.yml ansible-playbook /srv/web/infra/ansible/infra/ansible/playbooks/groups/mailman.yml
.... ....
== Adding a new proxy or webserver == Adding a new proxy or webserver