1 of 1 people found this helpful
You can use BladeLogic for :-
- Creating/Provisioning New VM
- You can use the Post- provisiong batch jobs to do a compliance /configuration stuff.
- You can use the post batch install/jobs to configure the BPPM server. I am not sure what steps are involved in that.
- For CMDB integration, you will have to use reporting solution, where in there is integration possible to extract new information about the new server/VM and creation of CI in CMDB. Check forums for more details.
For all the above stuff, you can use the Atrium Orchestrator with a workflow to do all this stuff with proper integration with approval/change management system.
You can discover your existing VM;s as well.
Thanks for the feedback Rohit.
What you describe sounds like a basic outline of much of what is provided by the BMC Cloud Solution...
What is provisioning the VM ? BBSA, manual, or some other tool ? if it’s not BBSA, you’d need to have BAO or some other system set to alert on the VM being created. maybe vCenter can do this ? then based on that alert, you can trigger the bao workflow to do whatever you need to.
I am wondering some of the same things. How do you use a "post-provisioning" batch job when using a VGP to create a new VM? I understand that you can batch jobs together, but how would the jobs know what the target name is for the new VM without adding the hostname into BladeLogic first? I see how this is done with a provisioning job but not for a VGP job. Any help you can provide is greatly appreciate.
We just installed 8.2 in our dev environment and this is where this is being tested.
You are correct, the post provision tasks cannot be in use for a VGP,
The server gets automatically enrolled at end of a successful VGP job.
So, You can have a batch job set to sequential and abort on VGP failure.
it can have,
a script based job which checks the newly added server, and may be check or set some configuration and then trigger any post jobs you want. These jobs will act as template jobs and will get executed against the newly added server.
This is the most simplest of a flow I can think of, there can be a more clever and smarter way to do this.
Have a look at this : You require a support id to see this, but the online docs now at BMC opens up a lot of information and help. There are some interesting use cases and very good white papers and recommendations for best practices.
the BMC CLM solution as suggested above in thread gives you more to do.