You are viewing an old version of this page. View the current version.
Compare with Current
View Page History
« Previous
Version 2
Next »
To set-up the QA system from scratch needs a *lot* of time and familiarity with CI tools. Tools like Cobbler have been chosen for this purpose so that tasks like PXE server set-up, and Puppet interaction, is made easier. The steps involved to set-up a system for scratch would be :
- Create a QACloud VM on XenServer host
- Configure private network switch with VLANs etc.
- Install the following on QACloud
- Cobbler
- Puppet
- DNSMASQ
- ipmitool
- Squid
- NFS server
- Import Hypervisor images (XenServer, KVM, ESXi) into Cobbler
- (TODO - Insert instructions to import here. They are tricky)
- Import Management Server OS into Cobbler (CentOs etc.)
- Configure MAC address for baremetal hosts in Cobbler for PXE provisioning
- Configure DNSMASQ for the above MAC addresses
- Use this sample config
- Set-up Puppet master to enable provisioning services like mysql etc. on management server VM in an automated way.
- Use this sample config
- Use puppet recipies from here
- Set-up NFS server for secondary storage
- Seed systemVM templates on NFS
- Set-up Squid HTTP Proxy server. This is required since QACloud is the only one expected to have public internet link. All other hosts live on a completely isolated network which is dedicated for testing. However, tasks like yum package download may need internet access, and thus the proxy server.
- Add QACloud to Jenkins master by providing IP address, login and password.
- (OPTIONALLY) add Windows VM to host vCenter, and manage a ESXi host running NetScalar, SRX etc.