|
Size: 296
Comment:
|
Size: 1275
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 11: | Line 11: |
| First, Orchestra manages DHCP/DNS for our environment. So we answered yes to the following question: | |
| Line 12: | Line 13: |
| {{attachment:orchestra-provisioning-server-dchp-dns-yes.png}} Second, we specified the IP range that our the Orchestra DHCP range is going to handle: {{attachment:ubuntu-orchestra-provisioning-server-dhcp-range.png}} Third, we specify the default gateway, which is not the Orchestra Server (tamarind is). {{attachment:ubuntu-orchestra-provisioning-dnsmasq-gateway.png}} Finally, we specify the domain for DNS: {{attachment:ubuntu-orchestra-provisioning-server-domain.png}} '''NOTE:''' Installing orchestra, will also run a script to import all the Ubuntu ISO's and create the necessary cobbler profiles for the systems that will be used for ensemble. In our case, the profile is: * oneiric-x86_64-ensemble The script will also create the management classes to be used by ensemble. * orchestra-ensemble-available * orchestra-ensemble-acquired |
Installing Orchestra
sudo apt-get install ubuntu-orchestra-server
Managing DNS/DHCP
First, Orchestra manages DHCP/DNS for our environment. So we answered yes to the following question:
Second, we specified the IP range that our the Orchestra DHCP range is going to handle:
Third, we specify the default gateway, which is not the Orchestra Server (tamarind is).
Finally, we specify the domain for DNS:
NOTE: Installing orchestra, will also run a script to import all the Ubuntu ISO's and create the necessary cobbler profiles for the systems that will be used for ensemble. In our case, the profile is:
- oneiric-x86_64-ensemble
The script will also create the management classes to be used by ensemble.
- orchestra-ensemble-available
- orchestra-ensemble-acquired