So if I understand you correctly, you essentially have two editors to a given installed package configuration - the tenant who presumably owns the server being managed and responsibility for it and you, who has some base responsibility - maybe just making sure the rope isn't long enough to hang themselves by right?
That's actually a pretty standard arrangement - the parties call themselves different things but the idea is consistent.
so looking at your comments:
1) I don't want to modify the default cdm package
You never should. Probes are updated frequently and you don't want to have to rework your changes every single time.
You should create a new package (either completely new or the drag from probe to archive method). The completely new method is a difficult starting point unless you know what you want. The drag probe to archive method gives you a fully functional package that will require editing.
The following is a general process we use:
In a package you can add multiple tabs in the lower half of the editor. We typically add a "dependency" tab where we list all the probes this package is dependant on.
That will ensure that cdm gets installed before your configuration changes - you can leave the version blank if all you want is any version of cdm installed.
2) Tenants have standard cdm configs which means modifying the standard cdm (we copy it to a new name)
Like commented above, don't modify or rename the standard packages. If nothing else it really confuses maintenance. Better to create a package with the dependency. Also there seems to be some value you are attaching to names of things here and that might be misleading you a bit. The names provide some record keeping but they don't identify what's installed. Only the name of the thing that did the installing. One of the misconceptions that happens with packages is that they are "what get's installed" - they are not. They are instead a set of instructions on how to modify the existing environment to get to the new. That's important.
3) I want cfg separate from the default so that if the cdm probe is updated we can deploy it separately.
Following on the comment above, you are not distributing cfg files. You are distributing a file (cfx) (and maybe more) that includes instructions on how to change the existing file to the new result. As an example, you may dictate that everyone needs a log level of 3 set for the cdm probe to make later diagnosing easier. So building on the cdm example, you would then add a second tab to the package - right click on the existing tab (maybe the "dep" one) and choose "add section", name it something reasonable (I usually use the target OS since that seems to be 98% of all the reasons why I might have more tabs than the two - in this case mine is "ALL") and select the "Configuration of existing probe" box.
That will give you a new tab. Make sure you select it. (As a general rule, the UIM windows dialogs operate on the selected item, not the one that's in front. In logmon for instance you can select a profile, select delete, and it will go away. Then logmon will display one of the other profiles but in the list to the left, a different profile will be selected. If you then select delete again expecting the profile that's displayed to go away, it won't because while it was displayed it wasn't the one selected. And the right click to get the context menu doesn't move the selection so even if you right click on the one you want gone, the selected one goes instead.)
You can't create files in this editor, you can only add and edit them. So, on your desktop or wherever use notepad to create a blank file named cdm.cfx. Generally the name of the cfx file will be the same as the probe but not always - that's where the "drag back to archive" process is helpful because it gets you the correct names. You can then select the "files" tab and right click in the white space to get the "add file" option. choose your cdm.cfx file.
You can then right click on that file and choose edit to open the file in the package editor.
If you looked through
https://ca-broadcom.wolkenservicedesk.com/external/article?articleId=34027&_ga=2.124119500.718443530.1570389780-1299565110.1557421559 it has some good information but the thing again to keep in mind is that the cfx files are just a list of changes. So if all you wanted to change was the log level then you can add to this file the following:
<setup> overwrite
loglevel = 3
</setup>
Close the editor and "OK" out of the package editor and you're all set. You have a package that will ensure that cdm is installed and regardless of what's in the configuration currently will set the log level to 3 without touching anything else.
Hope that helps.
-Garin
Original Message:
Sent: 10-08-2019 09:29 AM
From: Keith Clay
Subject: Configuration Only packages
Here is my thinking on this:
1) I don't want to modify the default cdm package
2) Tenants have standard cdm configs which means modifying the standard cdm (we copy it to a new name)
3) I want cfg separate from the default so that if the cdm probe is updated we can deploy it separately.
I was looking at super packages. If the cdm probe were to change, could that be dragged to the super package and replace the current cdm in the package or would I need to delete the old cdm and add the new one.
Hope this makes sense.
Original Message:
Sent: 10-07-2019 05:41 PM
From: Garin Walsh
Subject: Configuration Only packages
Yes, that's to be expected.
What you see listed in IM are only the probes packages that included executable code (effectively).
On the controller, on the status button, there's a "List installed packages" button that might help answer the what's installed question.
And these packages are extremely powerful. And fairly poorly documented. You can learn some things by looking at some of the GA probes but it doesn't cover everything.
If you posted a description of what you are trying to achieve and maybe a copy of what you have done so far, I'm sure that you'll get a number of comments that will provide some significant enlightenment.
I;ve also posted some on this topic in the last couple months - it might be worth searching for.
-Garin
Original Message:
Sent: 10-07-2019 03:45 PM
From: Keith Clay
Subject: Configuration Only packages
When you push the config only change, the cdm package name doesn't change but the config does. Is that to be expected?
Original Message:
Sent: 10-07-2019 03:18 PM
From: David MICHEL
Subject: Configuration Only packages
Maybe one of these KBs will help
Change Probe Configuration Setting On Multiple Robots
Article Id: 35048
https://ca-broadcom.wolkenservicedesk.com/external/article?articleId=35048
Article title: Editing probe packages (probe configuration files and templates, e.g., .cfx and .cfg, and tips on modification)
Article Id: 34027
https://ca-broadcom.wolkenservicedesk.com/external/article?articleId=34027
Create a cdm Superpackage for Multiple Operating Systems
Article Id: 35030
https://ca-broadcom.wolkenservicedesk.com/external/article?articleId=35030
------------------------------
Support Engineer
Broadcom
Original Message:
Sent: 10-07-2019 03:13 PM
From: Keith Clay
Subject: Configuration Only packages
Folks,
I'm testing creating configuration only package for the cdm probe so rather than copy everything we just copy the cfx filee.
I'm having issues getting to work correctly. here is what I am doing:
1) copy probe from robot to archive and select config only
2) for the one OS tab that is copied, I simply copy the updated cdm.gfx. No other tabs under the OS have anything
3) When I deploy, the package names doesn't change so not sure how to know what package is actually there
If I try filling in the probe definition, the package doesn't a cfg file/data file so it deploys but when I click on it, I don't get the correct screen coming up.
What am I doing wrong?
thanks