Installing the IBM Cloud Manager with OpenStack Hyper-V Agent

Follow these steps to install the IBM Cloud Manager with OpenStack Hyper-V Agent on Microsoft Windows Server 2012 R2 or Microsoft Hyper-V Server 2012 R2.

Overview of the installation

The installation completes the following steps:

  • Create a product installation directory
  • Create a Hyper-V external virtual switch (optional)
  • Configure Hyper-V Live Migration settings for this host (optional)
  • Install an independent Python environment to avoid conflicts with existing applications
    Note: This embedded Python environment is only intended for use by the IBM Cloud Manager with OpenStack Hyper-V Agent. Do not attempt to access this environment from any other application. This independent environment is designed to coexist with any preexisting Python environments that might already be installed on the system. Do not install new Python modules into the embedded Python environment.
  • Install the required Python modules/packages required by the application
  • Install and configure the OpenStack Nova Compute service
  • Install and configure the OpenStack Hyper-V Neutron agent for networking
  • Register two Windows services, which are set to auto-start by default:
    • IBM Cloud Manager with OpenStack Network Service
    • IBM Cloud Manager with OpenStack Compute Service
Important:
  • The 4.2 Hyper-V agent installer supports two message queue types, RabbitMQ and Qpid. You must select a message queue type that is consistent with the controller node.
  • IBM Cloud Manager with OpenStack by default enables Platform Resource Scheduler in the controller node. To complete the installation, update nova.conf file by appending ibm_notifications to notification_topics like “notification_topics=notifications,ibm_notifications”, and then restart the IBM Cloud Manager with OpenStack compute service.
  • If you migrate IBM SmartCloud® Entry 3.2 to IBM Cloud Manager with OpenStack 4.1, the neutron password is neutron by default. If you install a new Hyper-V Agent, you must change the default password for neutron to neutron to be consistent with the controller node.
  • The 3.1 Hyper-V agent installer does not prevent users from installing a previous version over the more recent Hyper-V agent.