I'm not following what the issue is... with implementation? some error message?
You're not really using Patch Analysis here, why not use the actual Patch Analysis Job?
What is the issue ?
Patch Analysis Job works against a Patch Repository downloaded from vendor.
Here I'm trying to provide a different service.
I have, say, 10 globals, each of one hosts from 5 to 20 zones (actually in scope of the project). My aim is to check packages installed on each one of those globals and create an audit job against the zones hosted on them, without going mad in creating servers smart groups to define manually which zones are on which globals.
Do I make myself clearer?
Please let me know if not, I'll try to be even more specific!
So you are trying to compare the patches installed on the global w/ the patches installed on the child zones hosted on that particular global to see if they match?
Have you run a virtual infrastructure discovery job – that should at least get the association of global zone to child zone available in bsa.
I sort of understood that past, but I did not understand where the issue is. So is the issue simply that you do not wish to create too many smartg groups?
I suppose the entire process could be scripted potentially. We have blclis to get the list of zones attached to the global, we have blclis to run jobs against a list of targets ... all this can be glued together to make your solution
Yes, I see that my aim is not possible without a couple of preliminary steps.
Do you guys have a way to create smart groups that contain zones related to a global? I thought of a NSH script that poulate a server property, but I don't know the way to print Global from a Zone prompt.
1 of 1 people found this helpful
I believe if you have agents on the globals and the child zones, and you run the virtual infrastructure discovery job, there will be a server property populated (VM_HOST I think) w/ the hostname of the host server. you could use this to create your smart groups, one group for each global, which could be done from the blcli.
I don’t have any solaris boxes handy w/ zones on them – if you have agents on the global and child zones, can you run the VIDJ ?
I run the job checking the "Update Virtual Infrastructure" option but VM_HOST property didn't populate..
Actually, I think it populates the VIRTUALATION.VIRTUAL_ENTITY_* properties:
Run the VIDJ, then open the property dictionary and open the ‘Virtualization’ property class. look on the ‘instances’ tab for an instance named after one of your child zones. Open that instance and look at those virtualization_entity properties. do any of those contain the hostname of the host system ?
Amazing..The Property Virtualization_entity_container now shows host name.
Thank you as usual, Bill!
So – we can use the blcli to create smart groups – one for each host – where VIRTUALIZATION.VIRTUALIZATION_ENTITY_CONTAINTER = blah.
Then do your audit jobs from there.
How many global zone boxes do you have ?
I've created server and component smart groups, now I'm proceeding to templates and then to discover, snapshot and audit jobs.