BMC Network Automation enhancement for physical server support
In the previous release, BMC Atrium Orchestrator callouts were required to create pod and container physical access switch nodes for connecting physical servers to the network. In this release, these callouts are no longer required. Instead, the <nodeBlueprint> tag for pods and containers has been enhanced with xsi:type value of podPhysicalSwitchBlueprint and containerPhysicalSwitchBlueprint respectively.
When defining a container node for a physical access switch, as shown in the second example below, you must specify a custom action to enable the port on the switch that the physical server will connect to using the <configureActionInfoBlueprint> tag.
For details, see Pod-blueprint-XML-reference and Container-blueprint-XML-reference. Search for "PhysicalSwitch" in these two topics for the relevant information.
Example of defining a pod node for a physical access switch
The following example shows how to define a pod node for a physical access switch:
<nodeBlueprint xsi:type="podPhysicalSwitchBlueprint" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<balancedParamBlueprints/>
<category>2</category>
<defaultShareableFlag>false</defaultShareableFlag>
<name>PhysicalAccess</name>
<optionalFlag>false</optionalFlag>
<paramBlueprints/>
<role>PhysicalAccess</role>
</nodeBlueprint>
Example of defining a container node for a physical access switch
The following example shows how to define a container node for a physical access switch:
<nodeBlueprint xsi:type="containerPhysicalSwitchBlueprint" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<category>2</category>
<configureActionInfoBlueprints>
<configureActionInfoBlueprint xsi:type="mergeActionInfoBlueprint">
<templateGroups>
<item>…</item>
</templateGroups>
</configureActionInfoBlueprint>
</configureActionInfoBlueprints>
<name>PhysicalAccess</name>
<role>PhysicalAccess</role>
<unconfigureActionInfoBlueprints>
<unconfigureActionInfoBlueprint xsi:type="mergeActionInfoBlueprint">
<templateGroups>
<item>…</item>
</templateGroups>
</unconfigureActionInfoBlueprint>
</unconfigureActionInfoBlueprints>
<provisionSwitchGuid>58A6E8FC-BB30-4F7A-A3CD-528A9A72571E</provisionSwitchGuid>
</nodeBlueprint>