Along with a host of new features and capabilities, Novell Service Desk v6.5 also brings with it a new deployment option; the virtual appliance.
There's a lot been written already about virtual appliances, addressing what they are and why they have become popular with software vendors and their customers. I'm not going to regurgitate all of the propaganda here, just to say that virtual appliance is a virtual machine with Just Enough Operating System ( JeOS ) to run an application. This simplifies deployment as the customer doesn't need to worry about installing the operating system, applying updates, pre-reqs etc... in a methodological way to the meet requirements set by the vendor.
To put it simply, virtual appliances are easier to deploy, avoid application installation issues and are a win-win for both the vendor and customer.
With Novell Service Desk appliance, you get a
Virtual machine built for ESX / ESXi servers delivered using the OVF format.
Uses cut down version of SLES 11 SP1 64-bit edition.
Configured Postgresql database.
Novell Service Desk 6.5 using the embedded Postgresql database.
Simple text mode menu system to manage the appliance, Novell Service Desk services and perform upgrades / migrations.
Ready to use as soon the deployment is finished. Typically this is sub 3 minutes.
And all of this in a download under 700Mb. Or as I like to think of it, 487 3.5 inch floppy disks ( for those too young to remember, this type of floppy disk had a hard case. So it was more like a semi-floppy. ).
Deploying the Novell Service Desk appliance is straight forward. Even a product manager like myself can do it.
The appliance will then finish off the remaining first boot tasks. When the appliance menu pops ups, all is complete.
Now for some post deployment activities, namely networking information and ensuring that time is accurately kept.
The default setting for networking with Novell Service Desk appliance is to use DHCP. Although fine for end user devices, most organizations prefer to use static IP addresses for servers. At this time, we should also set the host name to our desired value rather than the random name which was generated during the first boot process. To do this, we use the appliance menu functions.
At the main menu, 1 – Appliance and then 2 – Alter Network Configuration. This causes YaST to be loaded at the point where network settings can be changed. Here you can set the IP address, hostname and enter a gateway address. When you've done all of this, press F10 to save and Exit and you'll be returned to the appliance menu.
Now select 3 – Alter Date and Time zone. This also causes YaST to be loaded to allow these options to be changed. Use the TAB key to move to Change within the Data and Time panel and then press the Enter key.
Select Synchronize with NTP server and enter pool.ntp.org for the NTP server address. Alternatively you can use any of the suggested external time sources or use an internal NTP server. Make sure that you select Save NTP Configuration and then press F10.
Press F10 again to return to the appliance menu
That's it. The appliance is deployed and ready to serve up Novell Service Desk. You now can point your browser directly at the IP address shown in the appliance menu or use the DNS name that you entered previously.
What next? Well that's the subject of the next article where we look at taking our first steps with Novell Service Desk.