This post covers Stage 4, the customer production environment pre-checks and here we will investigate a number of pro-active checks that can be carried out to ensure your servers and network are ready for the Eucalyptus IaaS installation.
- Network cabling correctly wired
- Are your servers connected to the correct switches? Try out the networking tests in our User Acceptance Testing plan.
- Network switches configured
- Ensure your Network Administrator has updated the switch configuration & firmware.
- Ensure multicast traffic is allowed on the switches. After package installation you can run through the multicast test in step 13.
- VLAN range provided or VLAN clean network
- Are you intending to use MANAGED mode? Run through the Prepare VLAN checks from our installation guide.
- If you cannot allocate the whole VLAN range to Eucalyptus you can configure a specific range using the euca-modify-property command.
- IP addresses and DNS names allocated
- Each server should have a static IP address.
- Each server should have a forward (A) and reverse (PTR) DNS record in your public name server or each system configured with an /etc/hosts entry.
- Pool of public IP addresses allocated
- A range of addresses used to assign to each virtual instance.
- Range of private IP addresses allocated
- An unused class B network is preferred (e.g. 10.10.0.0/255.255.0.0).
- If you intend to use a SAN:
- A supported SAN device; Dell Equallogic, Netapp (FAS2000 or FAS6000 series) or EMC VNX
- Username/Password for Eucalyptus access
- Storage pools configured
- Disk Space on each system
- At least 200GB free disk space on the Storage Controller (/var/lib/eucalyptus/volumes)
- At least 300GB free on the Walrus server (/var/lib/eucalyptus/bukkits)
- At least 200GB free on the Node Controller (/var/lib/eucalyptus)
- See our Reference Architectures for more information on storage requirements.
- See our Storage Controller and Walrus troubleshooting pages for more info.
- RHEL or CentOS 6 x86_64 installed
- SELinux in disabled or permissive mode
- (optional) Network bonding configured
- Bridge interfaces configured on each Node Controller system
- NTP installed & configured
- Direct Internet access from each system
- Alternatively access to a mirror system or proxy with access to:
- Eucalyptus repository (*.eucalyptus.com)
- RHEL or CentOS archive (*.centos.org)
- EPEL (download.fedoraproject.org)
Can you think of any other checks to carry out before cloud installation?
Over on the Eucalyptus Wiki and Eucalyptus-users mailing list we've been discussing the various checklists and tools available, come and join the discussion!