HP Matrix Operating Environment Software User Manual
Page 43
Infrastructure orchestration requires the SA OS Build Plan Management permissions to be enabled.
If these permissions are not set, IO will not retrieve the SA software list.
Enable OS Build Plan permissions in SA:
1.
Log in to the SA web client as Admin.
2.
In the SA user interface, select By Folder.
3.
Right click on the OS Provisioning folder name.
4.
Ensure that the Execute Objects Within Folder permission is selected.
5.
Select Users & Groups from the Navigation panel.
6.
Select the IO user for SA (typically hpiosa).
7.
Click Edit in the upper right corner.
8.
Select the Client Features tab.
9.
Scroll to the section OS Build Plan Management.
10. Set the radio button Manage OS Build Plan to Read.
11. Set the radio button Allow Execute OS Build Plan to Yes.
12. Click Save at the top of the page.
To make the OS Build Plan available for infrastructure users (for example: hpiosa), create the
following custom attributes on each of the OS Build Plans:
1.
Set OSType to any one of the following values:
Windows Server 2003
Windows Server 2003 x64
Windows Server 2008
Windows Server 2008 x64
Windows Server 2008 R2 x64
Red Hat Enterprise Linux Server 5
Red Hat Enterprise Linux Server 5 X86_64
Red Hat Enterprise Linux Server 6
Red Hat Enterprise Linux Server 6 X86_64
2.
Set archType to one of the following values:
x86 (for 32-bit systems)
x64 (for 64-bit systems)
See the Application Automation section in the HP Server Automation User Guide for more information
about creating custom attributes.
Communication between infrastructure orchestration and SA is done through the SA core. Only
the SA core is registered in IO, and all requests are made through the SA core. The core then
directs the satellite(s) to deploy software. This occurs automatically, and requires only that a network
is selected that has been configured to use SA.
The IO network is defined as a deployment network and as connected to the SA core. This network
might be available an any or all of the secondary CMSs.
Additional deployment networks must either be connected to the SA core or to an SA satellite
managed by the SA core. The additional deployment subnets are defined as deployment networks
for the SA core, even if they are for a SA satellite network.
Any service containing the IO subnet defined as the deployment network for the SA core can be
deployed with that SA core.
To configure a network to use an SA deployment server:
1.
From the infrastructure orchestration console, select the Networks tab.
2.
Select a network from the list, and click Edit.
3.
From the Deployment Server list, select an SA satellite (for example, 10.0.0.10 (SA).)
4.
In Boot Network, select Yes, and save the configuration.
Configuring deployment servers
43