Archive for the ‘Server’ Category

Shang Wu

[Oneiric] Ubuntu Orchestra Server: Provision Server Setup

Thanks to Dustin’s formal introduction, I now have a better understanding about what Ubuntu Orchestra is and how this tool can help system administrators deploying Ubuntu in the data center.

Basically, the Ubuntu orchestra server consist of the following components:

1. Provision Server -> Cobbler
2. Monitoring Server -> Nagios
3. Management Server -> Ensemble
4. Logging Server -> Rsyslog

To build the provision part of the environment, you will need to setup and configure the following servers:

1. DHCP server
2. Ubuntu Orchestra Server
3. PXE boot server

Here is how:
1. For DHCP server (

a. Install the dhcp3-server package:

sudo apt-get install dhcp3-server

b. Configure the dhcpd.conf file under /etc/dhcp directory:
(Leave everything as it is but configure the local network and the static IP address for Ubuntu orchestra server and the PXE boot client)

subnet netmask {
option routers;
option broadcast-address;
default-lease-time 600;
max-lease-time 7200;

host Orchestra {
hardware ethernet 08:00:27:05:5D:15;

host PXE-Client {
hardware ethernet 08:00:27:5E:d4:53;
option subnet-mask;
filename “pxelinux.0”;
option domain-name-servers,;

c. Once that is done, restart the DHCP server:

sudo /etc/init.d/isc-dhcp-server restart

2. For Ubuntu Orchestra server (

a. Install the Ubuntu-orchestra-server package:

sudo apt-get install ubuntu-orchestra-server

b. During the installation, you will be asked to configure the password and if you are going to use the server to manage your DNS/DHCP. For the purpose of this example, I did not use Orchestra as my DNS/DHCP server.

c. Once the setup is completed, you can open the browser and take a look at its interface (Looks great, I have to say!!)

Ubuntu Orchestra Web Interface

(In my case)


d. Import the ubuntu iso file:

sudo cobbler-ubuntu-import natty-i386

(This will create the image profile in the Distro and the Profile entry)


e. After the profile is created, you will need to add the preseed file to the profile entry via the web page, if you want to automate everything. The kickstarts file can be found at /var/lib/cobbler/kickstarts/ directory. In my case, I use the /var/lib/cobbler/kickstarts/ubuntu-server.preseed as my preseed file.


f. Create the system that you want to deploy:
Add a new system from the web interface. You are required to have the name and the MAC address for the setup.


g. Start up the PXE boot server, Et VoilĂ !



[1] Couple useful cobbler commands:

sudo cobbler check
– Self check on the configuration and provide
sudo cobbler sync – Apply cobbler configuration changes
sudo restart cobbler – restart cobbler services
sudo cobbler-ubuntu-import – import the Ubuntu ISO file for PXE boot installation
sudo cobbler system add –name=example –mac=$mac-address –profile=$profile-name – Specify the system with its MAC address and the cobber profile which is going to be used

[2] References:

Cobbler –


Create a new blog