Fedora Cloud Infrastructure SOP
Fedora Cloud computing
Owner: Fedora Infrastructure Team
Contact: #fedora-admin, sysadmin-cloud group
Persons: mmcgrath, SmootherFrOgZ, G
Location: Phoenix ?
Servers: capp1.fedoraproject.org, cnode[1-5].fedoraproject.org, store[1-4]
Purpose: Provide Virtual Machine for Fedora contributors.
Rebuild capp1 (ovirt-server)
Log into cnode1
Check that no capp1 domain is running
sudo virsh list
If there is a capp1 running, proceed as follow
sudo virsh destroy capp1 sudo virsh undefine capp1
Format capp1 disk for a better new virtual install
sudo /sbin/mkfs.ext3 -j /dev/VolGroup00/appliance1
You can now start install a new fresh capp1 virtual system
sudo virt-install -n capp1 -r 1024 --vcpus=2 --os-variant fedora11 --os-type linux \ -l http://mirrors.kernel.org/fedora/releases/11/Fedora/x86_64/os/ \ --disk="path=/dev/VolGroup00/appliance1" --nographics --noacpi --hvm --network=bridge:br2 \ --accelerate -x "console=ttyS0 ks=http://infrastructure.fedoraproject.org/rhel/ks/fedora ip=22.214.171.124 netmask=255.255.254.0 gateway=126.96.36.199 dns=188.8.131.52"
Note: If the network messes up during the prompt install, just configure it manually. NM will takes care of it then.
Note2: The above ks file seems to have graphical install as install method. Rebuild one or do a manual install to continue.
capp1 network interfaces will need to be setup manually in order to work against physical one.
Here is how to proceed, create your network interface
sudo vi /etc/sysconfig/network-scripts/ifcfg-eth1
Then add this following configuration to the file
DEVICE=eth1 BOOTPROTO=static ONBOOT=yes PEERNTP=yes IPADDR=$physical_br_IP NETMASK=$physical_br_NETMASK HWADDR=$random_mac_addr
Reproduce the above for eth3 against br3
You can get br? IP and netmask on cnode1 with <ifconfig> cd-line.
VMs can't receive tasks anymore
If for some reason VM appear to not receive tasks, this's because it's not reachable anymore.
Reload you browser will show the VM as state <no reachable> in the ovirt UI.
At first, check that hosts are still available. If so, you gonna have to do a manual reload on the broker connectivity.
Log in to capp1 and restart services in this order (hold few sec for each)
sudo service qpidd restart sudo service ovirt-db-omatic restart sudo service ovirt-taskomatic restart