It's time to spend some time on a tough topic: Information Quality. OpenSLIM implement several functions whose main purpose is to guarant data coherence when one has to deal with certain IT Processes: Provisioning, Repairings, Decommissionings, and so forth. In these cases, Registration Criteria is hard-wired inside OpenSLIM and you don't need to worry about it unless you want to change it.
Unfortunately there still exist rules that you will have to settle if you want to have good levels on your Information Quality. These conventions must be:
- Agreed with your Team(s) and Stakeholders.
- Controlled with regular Sanity Checks.
- Reviewed from time to time for you to make sure that they are still valuable or if they need to be changed or extended with new ones.
The references are only that: a reference or an starting point for Node Information Quality. You will have to make your own way and find what really fits on your particular scenario.
Node Hierarchy:
[ParentNode > NodeName] | [ParentNode > ParentNode > NodeName] | [...]- BladeChassisNodeName > PhysicalClusterNodeName.
- On the “Other Relationships” Tab include the LogicalClusterNodeName to which this PhysicalClusterNodeName belongs using a “Hosting” relationship.
- “NoParentNode” > LogicalClusterNodeName.
- LogicalClusterNodeName is a dummy Node. It doesn't have to be a real Cluster Resource Network Name.
- On the “Other Relationships” Tab register the member of the Cluster adding each PhysicalClusterNodeName using a “HostedBy” relationship.
- This way you will be able to have a clear inventory of how many Clusters you manage.
- “NoParentNode” > ManagementPointNodeName > VirtualMachineNodeName.
- ManagementPointNodeName is not a dummy Node. It is, actually, a DNS alias or a Cluster Resource Network Name.
- This makes it easy to locate and connecto to the Management Point a Virtual Machine depends on: be VMWare VirtualCenter, SystemCenter VMM or whichever.
PhysicalClusterNodeName which are Hypervisors:
SupplierId:HP, IBM, …NodeTypeId:Blade, Regular ServerSystemTypeId:ESX, Windows 2008 R2, …MainProjectId:HWoDMainRoleId:vmware.ESXServer, ms.HyperVServer, ms.VirtualServer, …ClusterType:VMWare HA, MS Cluster
LogicalClusterNodeName assigned to a Physical Cluster of Hypervisors:
SupplierId:The one of its Members. Each Node in the Cluster is supposed to be exactly equal to their partners (i.e. HP, IBM, … )NodeTypeId:Cluster ResourceSystemTypeId:The one of its Members. Each Node in the Cluster is supposed to be exactly equal to their partners (i.e. ESX, Windows 2008 R2, … )MainProjectId:HWoDMainRoleId:The one of its Members. Each Node in the Cluster is supposed to be exactly equal to their partners (i.e. vmware.ESXServer, ms.HyperVServer, … )ClusterType:VMWare HA, MS ClusterServiceIP:If exists, the one assigned to a Cluster Resource Network Name. If it doesn't, the one assigned to the First PhysicalClusterNodeName.AdminIP:0.0.0.0HardwareAdminIP:0.0.0.0
VirtualMachineNodeName:
SupplierId:VMWare, Microsoft, …NodeTypeId:Virtual MachineSystemTypeId:The one installed on the Virtual Machine.MainProjectId:The one hosted on the Virtual Machine.MainRoleId:The one hosted on the Virtual Machine.
Regular LogicalClusterNodeName:
SupplierId:The one of its Members. Each Node in the Cluster is supposed to be exactly equal to their partners (i.e. HP, IBM, … )NodeTypeId:Cluster ResourceSystemTypeId:The one of its Members. Each Node in the Cluster is supposed to be exactly equal to their partners (i.e. Windows 2008 R2, … )MainProjectId:HWoD, The one hosted on one of its Members.MainRoleId:The one hosted on one of its Members.ClusterType:MS Cluster, …ServiceIP:If exists, the one assigned to a Cluster Resource Network Name. If it doesn't, the one assigned to the First PhysicalClusterNodeName.AdminIP:0.0.0.0HardwareAdminIP:0.0.0.0
ManagementPointNodeName:
SupplierId:HP, IBM, VMWare, Microsoft, …NodeTypeId:Management ResourceSystemTypeId:Windows 2008 R2, …MainProjectId:Infrastructure ServicesMainRoleId:vmware.VirtualCenter, ms.SCVMM, ms.SCOM, ms.SCCM, ms.SCDPM, …ClusterType:VMWare HA, MS Cluster
