Is it possible to create a file on the target system which indicates the profile that was used by TPMfOSD to build the server?
It can be useful to track the profile name used during deployment for auditing and security purposes.
Yes it is possible. Use the RAD Import wizard to load the attached osd_info.rad into your OSD server. Then bind this SW module during profile deployment. It will do the following:
- create a new file /osd_info/osd_info.txt onto the target system
- osd_info.txt will contain the following information:
User category 0 = val1
System Profile= val2
The user category 0 corresponds to the field in the OS configuration of the system profile:
The system profile corresponds to the name of the System Profile:
To have this SW module automatically bind with all of your linux deployments, follow these steps:
- Using the "OS Version" binding field under the OS deployment section of General TAB of every OS configuration.
- For example, for Rhel 5.8 cloned profiles, this value is "Red Hat Enterprise Linux Server release 5.8, Tikanga".
So, when defining automatic binding rules for software modules, the OS Version field can be filled as "Red Hat Enterprise Linux%5.8%", this will bind the software module only to Rhel 5.8 deployments. If instead you want to bind the software module to every Rhel 5 deployment, this value must be set to "Red Hat Enterprise Linux%5%".
Rate this page:
Copyright and trademark information
IBM, the IBM logo and ibm.com are trademarks of International Business Machines Corp., registered in many jurisdictions worldwide. Other product and service names might be trademarks of IBM or other companies. A current list of IBM trademarks is available on the Web at "Copyright and trademark information" at www.ibm.com/legal/copytrade.shtml.