It's quite a bit more complex now.
The current functionality includes the following:
- It has logic which determines what OS type (x86/x64) you are running based on the system package name
- It has logic which determines what system folder you need to use based on system package name (linux or windows)
- It has logic which determines if the host will use DHCP or a static IP based on the entry in HP Service Desk, and also sets the local properties accordingly
- It follows the progress of the provisioning job, and updates Service Desk depending on whether the provisioning job has finished or not
- It follows the progress of the post-OS batch job and updates Service Desk depending on whether the batch job has finished or not
Attached is a pic of the new workflow.
Picture 115.png 58.8 K
I need to put this in a KB article. At the moment I'm slammed at work, but I'll get to that as soon as I can.
Someone just emailed me a few questions:
+"Need example of System Package creation through CLI -
In order to automate provisioning of AIX servers I need to be able to create System Packages through the CLI or override settings at time of provision through the CLI (Machine Name, OM Server Name, NIM Machine Name, etc).
This automation will be driven by Opalis as recommended by BladeLogic."+
Take a look at the internal forums too, just do a search for something like "SystemPackage" and you'll get a couple hits.
I am unable to browse internal forums, and I receive this error when trying to access your link:
The document specified was not found, or has expired.
If these (and other) settings can be overridden by the properties file, it would be wonderful to have a good document of potential settings for this file available. There appears to be some information in the help regarding provisioning via this method, however the information on AIX leaves a lot to be desired.
It's document 519 in the Knowledge Base.
If that doc is "internal", take a look at the CLI docs for Provision provisionDevice
Christopher was correct - the provisioning doc is inaccessible by BladeLogic's customers. I couldn't tell at the time of his original post because I had privileged access to the forums.
While working on provisioning today I found that Andrew's doc is also available here:
If you have any trouble accessing that, send me an email and I'll get it to you.
My email address is firstname.lastname@example.org.