This section includes the following information:
A “custom” fact is one that is not internally defined in the Orchestration Server as a common or “well-known” fact. You can determine whether a fact is well known by looking at the list of facts for a given Grid Object using the Orchestration Console. If you select the tab in the admin view of any object, the custom fact is displayed in the fact table in bold face type, indicating that it was set by non-core components such as provisioning adapters or by extensions or jobs set up by a Cloud Manager Orchestration administrator or developer.
Many custom facts are set and are used by the Orchestration provisioning adapter code, across most of the grid object types. You should consider these as “internal” to the system and not to be modified under normal circumstances. For example, the vsphere and xen provisioning adapters use certain custom facts to hold internal information used by their implementations to configure and discover virtual network interface card (vNIC) devices. The same is true for VMs, VM hosts, vDisks, and other Grid Objects.
You can set up a custom facts directly in JDL code or by editing a policy associated with an object. For example, in vSphere client hosts (where the SDK is available for use by Cloud Manager Orchestration) you would associate the vsphere_client policy to that physical (or virtual) resource. Within that policy, you would use the Policy Editor in the Orchestration Console to set the vsphere.client Boolean fact to true.
Under normal circumstances, a custom fact has deletable and read/write attributes set by default. These are the only attributes that you can set in the Policy Editor; however, it is possible to set the attributes by using the Java API.