Data Migration from Insight Control server deployment to Insight Control server provisioning

14
VMware vSphere/ESXi 5.1 u1
hpfeatures\esxi51u1\dist
media\esxi51u1
VMware vSphere/ESXi 5.1
hpfeatures\esxi51\dist
media\esxi51
VMware vSphere/ESXi 5.0 U1
hpfeatures\esxi50u1\dist
media\esxi50u1
VMware vSphere/ESXi 5.0 U2
hpfeatures\esxi50u2\dist
media\esxi50u2
Red Hat Enterprise Linux 6.3 x64
hpfeatures\rhel63-x64\dist
media\rhel63-x64
Red Hat Enterprise Linux 6.4 x64
hpfeatures\rhel64-x64\dist
media\rhel54-x64
Red Hat Enterprise Linux 5.9 x64
hpfeatures\rhel59-x64\dist
media\rhel59-x64
Red Hat Enterprise Linux 5.10 x64
hpfeatures\rhel510-x64\dist
media\rhel510-x64
SUSE Linux Enterprise Server 11 SP2
x64
hpfeatures\sles11sp2-x64\dist
media\sles11sp2-x64
Matrix Service Template Considerations
Existing Matrix environments probably have a number of Matrix OE infrastructure orchestration service templates
defined, many of which may be using software images from the RDP Deployment Server. Those templates can be edited
to use software images from the IC server provisioning appliance, or new templates can be defined. Depending on the
coexistence strategy chosen, RDP and IC server provisioning may be on different deployment networks. Ensure each
service template uses the appropriate network.
If prior to migration, all templates are edited to make use of the IC server provisioning network and software images
instead of RDP, no new services will be created using RDP. If new templates are defined, then appropriate naming and
permissions should be used to ensure administrators/users access the templates as desired. Perhaps the architect
chooses to create new templates for IC server provisioning and unpublishes the templates using RDP, but keeps them
defined for historical reference. Perhaps some Matrix organizations begin using templates with IC server provisioning
while others continue to use service templates with RDP. If published templates include use of both RDP and IC server
provisioning, it is important to ensure suitable coexistence for successful service creation using those templates. For
more details on RDP and IC server provisioning coexistence, refer to the following section on Matrix Service
Considerations.
Matrix Service Considerations
Existing Matrix environments probably have a number of services which were created from the defined Matrix service
templates. If those templates used software from the RDP Deployment Server, then the Matrix services include
information about the RDP IP address and job, as well as references to the target ID. If RDP is not available, certain
lifecycle operations on those services can fail. Those operations include flexing up or adding more servers to a server
group, and erasing disks. Erase disk is an operation performed when a service is deleted to ensure the storage is
scrubbed before reuse. If the Matrix services using software from RDP have been deleted prior to migration, this is not a
concern. But coexistence could still be necessary if Matrix service templates depend on RDP, since new services could be
created from those templates.
RDP coexists with IC server provisioning on separate broadcast domains (LANs, networks)
This is the recommended configuration for the Matrix Operating Environment.
Matrix OE supports the coexistence of RDP and IC server provisioning on separate broadcast domains. In this
configuration, existing services will continue to use RDP deployment, while new Matrix services will be created from
templates configured with IC server provisioning. It is also possible to have existing templates which make use of RDP.
As noted earlier, each service template would use the appropriate deployment network and software images, separate
for RDP and IC server provisioning. The template is dependant on the correct network for the Deployment Server. If the
network customization feature is used at the time of service creation, it cannot be used to change the deployment
network unless the corresponding software image is also changed, as the provisioning/deployment would fail. In this
case, the target servers must not be migrated from RDP to IC server provisioning. Other migration tasks for scripts and
OSBPs can be utilized as necessary. Once all existing Matrix services dependent on RDP have been deleted, the RDP
Deployment Server can be safely removed.