Hi,
When we have several users doing admin on NCM jobs, it's a burden to say - for each job - OK, here are the 24 out of 300 devices I need for this job. Then the next job that needs those 24, I need to add them in. I'm not sure where some people have thousands of devices and hundreds in each job how they coordinate that...especially if there's 10 or more admins making jobs!
Sure, I can duplicate the jobs and these include the devices, but that's not optimal. What would make sense - considering we've got a database, to create an object that links X devices and call it "Friday-Upgrade-Targets" or something, and put that in each new or changed job. I'd be able to add multiple of these - so maybe the names would be "AD Domain Controllers", "DHCP Servers", "Juniper Devices", etc.
OK. You say "well, you can make groups in Orion that you use in NCM jobs. But groups tend to be more static than would a job's device list.
And there's dynamic selection, but those are defined aspects of the particular device...not an ad-hoc list. It shouldn't matter that NCM has no grouping or dynamic variable that means "every device with "X" as the 3rd character in the device name". I should just select them in the normal "Choose Nodes" dialog, with an option to "Save and name selected devices."
Then allow that named list to be seen and used in other's jobs, but not let them change the selection I make.
Thanks,
Ambi
