HP Cloud OS for Moonshot Setup and Install

HP Cloud OS for Moonshot Install & Configure Your

Cloud

Version 1

‹ PREV | ^ UP | NEXT ›

Install & Configure Your Cloud

Welcome! The following topics explain how to install & configure your cloud with HP Cloud OS for Moonshot.

It's important to read the topics and perform the described steps in order. While some steps are optional, the sequence that you'll follow in the Operational Dashboard is significant, to ensure a proper deployment of your cloud.

Install and set up the Admin node:

Installation Overview Important Tasks Before You Install Install and Set Up the Admin Node Set Admin Node Prerequisites View Connection Settings Customize Networks Complete Admin Node Installation

After you install and set up the Admin node, you can perform additional steps:

Manage Nodes and Create a Cloud Create Compute Regions Enter or Update your License Key Customize User Settings View Updates and Extensions Launch Administration Dashboard for Post-Deployment Tasks

Note: Also see the Operational Dashboard and Administration Dashboard Help topics:

HP Cloud OS for Moonshot Operational Dashboard Help HP Cloud OS for Moonshot Administration Dashboard Help

‹ PREV | ^ UP | NEXT ›

Installation Overview

Welcome! This topic presents an overview of the installation steps.

An HP Cloud OS for Moonshot infrastructure requires advance planning and preparation by IT network administrators. The HP Cloud OS for Moonshot installation deploys the HP Cloud OS for Moonshot Operational Dashboard (used to set up, configure, and install an HP cloud infrastructure) and the HP Cloud OS

for Moonshot Administration Dashboard (used to create and manage cloud resources).

HP Cloud OS for Moonshot Environment

Preview of the Installation Steps

Overall Installation Process and Approximate Time

Components of the HP Cloud OS for Moonshot Environment

Next Step

HP Cloud OS for Moonshot Environment

The HP Cloud OS for Moonshot environment provides you with:

Optimized cloud workloads across cloud providers, with model-once and provision-anywhere capability. These features are combined with repeatable, consistent workload placement across diverse cloud deployment models. This functionality allows you and your customers to optimally align workloads with resources, and to improve resource utilization.

A flexible and open architecture powered by OpenStack technology, giving you an industry leading, vendor neutral, open source cloud architecture.

The HP Cloud OS for Moonshot environment also include an installer, services, and controllers that provide simplified service delivery with automated, live content distribution, and an easier installation and configuration processes. This functionality allows manually intensive operational processes to be reduced from hundreds of steps over multiple packages to a simple, automated process.

Preview of the Installation Steps

Installing and configuring Cloud OS for Moonshot is a multi-step process. Throughout the process you will be prompted to either enter required information or accept the default information.

At a high level, here are the steps to setup and install the Admin node:

The steps shown above feature an automated process in the HP Cloud OS for Moonshot Operational Dashboard. HP Cloud OS for Moonshot handles all of the installation details for you, installing the OpenStack services and the HP Cloud OS for Moonshot value-added services.

Taking a broader view, this next diagram illustrates those steps in a larger context:

Notice how once you've installed and set up the Admin node, you perform steps first in the Operational Dashboard to create your cloud and perform associated tasks. Then from the Operational Dashboard, you will

launch the separate Administration Dashboard to perform a number of post-installation tasks. And from that point forward, you will use the Administration Dashboard to manage your cloud environment, including the Moonshot server cartridges.

The documented post-installation tasks are designed to familiarize you with the Administration Dashboard, which you'll use from that point forward to manage your cloud. The tasks are also designed to help you verify that your recently deployed cloud environment is functioning properly.

Overall Installation Process and Approximate Time

Assuming a typical configuration, the overall setup process involves the following steps. The total time to complete the setup once HW is installed, configured and the hypervisor is ready is four to six hours. In this list, approximate execution times are shown here for reference, once the installation from the HP Cloud OS for Moonshot ISO has begun.

Collect the required information for the network configuration

Setup the Moonshot chassis, cartridges and configure the internal switches

Configure the server hardware and the physical networking as required

Setup a server with either VMware ESXi or Linux KVM as a hypervisor

Configure the networking within the hypervisor to support the required networking configuration

Create three virtual machines to host the Admin, Controller and Compute VMs

Create a VM to use as an access node for installation of the HP Cloud OS for Moonshot software ISO

Install and configure the Admin node (60 minutes)

Add (discover and allocate) the Controller and Compute VMs (30 minutes)

Create a cloud and compute region (60 minutes)

Add and discover the Moonshot chassis (15 min)

Download and import the desired workload(s) (30 to 60 minutes - depending on download time)

Provision a workload (30 minutes)

Components of the HP Cloud OS for Moonshot Environment

The following diagram illustrates the HP Cloud OS for Moonshot environment.

Services

Cloud Infrastructure consists of individual services installed and integrated together across one or more nodes to form a cloud environment. These are composite services that are integrated together into a single cloud solution. Services are exposed or published as RESTful APIs. The list of services that can be deployed for HP Cloud OS for Moonshot are:

Keystone — An OpenStack service to provide identity (domain, project and users) management, access token, and service catalog functionality.

Glance — An OpenStack service to provide for discovering, registering, and retrieving virtual machine images.

Nova — An OpenStack service to provide a compute fabric controller.

Cinder — An OpenStack service to provide volume management.

Neutron — An OpenStack service to create and provision virtual networks.

Apollo — An HP Cloud OS for Moonshot service that provides HP Moonshot Chassis and Server

Management. In addition, it helps to discover HP Moonshot Servers and allocates them for the provisioning.

Graffiti — An HP Cloud OS for Moonshot resource pool registry and capability tagging service. Designed to support diverse functions: discovering, registering, and retrieving resource pool definitions for compute, network, and volume resources; a dictionary of the cloud's capabilities; a searchable directory to find cloud resources based on their capabilities; and dynamic binding, describing the requirements instead of static binding.

Eve — An HP Cloud OS for Moonshot service to provide for provisioning lifecycle of a TOSCA-based infrastructure topology design of the compute, network, and volume resources in a defined resource pool. Also provides security and management.

Focus — An HP Cloud OS for Moonshot service to provide for discovering, registering, versioning, and retrieving of document types necessary to describe TOSCA-based infrastructure topologies.

Administration Node

The HP Cloud OS for Moonshot Administration Node (Admin Node) hosts the Operational Dashboard that deploys private and hybrid-only cloud infrastructure environments by network booting the managed Baremetal servers, which are the Controller and Baremetal host.

Controllers

While each service can be individually deployed, HP Cloud OS for Moonshot groups these services into distinct groups for ease of architectural description.

Cloud Controller: This contains those services that are considered single services for a cloud environment, such as Keystone, Glance, Graffiti, Eve, and Focus, and define the boundaries of the cloud environment from an identity standpoint.

Network Controller: This contains Neutron's server, l3 agent and DHCP services. It is a single service in a cloud and can co-exist with cloud controller services.

Compute Region Controller: A Resource Region is known as a Compute Region. This is a pool of compute resources that can be consumed through a service API by consumers of the cloud, such as Nova. This is responsible for the launch of instances across baremetal hosts. The scheduling is based on varied flavors of instances and available resources on the compute nodes. In a single compute region deployment model, this can coexist with cloud controller services.

Note: HP recommends that you define and use multiple compute regions. For example, you could separate the regions based on different workloads and requirements between development and production. A development team's compute region could provide non-redundant machines with less RAM; the compute region for production could have machines with much more RAM, backed up with heavy compute and fault-tolerant resources. In this scenario, the Compute Region Controller is its own node.

Baremetal Host

The Baremetal Host hosts the cloud instances using a baremetal driver for the OpenStack Nova compute service. Within the OpenStack framework, the baremetal driver has the same role as the drivers for other hypervisors (libvirt, xen, etc.), and yet it is presently unique in that the hardware is not virtualized - there is no hypervisor between the workloads and the physical hardware that includes Moonshot cartridges.

Next Step

Proceed to the next topic, Important Tasks Before You Install.

‹ PREV | ^ UP | NEXT ›

Important Tasks Before You Install

Before you can start working in the HP Cloud OS for Moonshot Operational Dashboard, you must:

Plan the Infrastructure for a Cloud

Review the Checklist of Values You'll Need in Advance

Plan the Infrastructure for a Cloud

This section defines the minimum infrastructure requirements to standup a cloud. You will need support from your IT administrator to correctly capture information about your environment.

Deployment Architecture

Server Infrastructure

Network Infrastructure

Deployment Architecture

A simple cloud environment would include:

A Cloud Administration Node (Admin Node)

A Controller Node

A Baremetal Host

The following diagram depicts a simplified deployment scenario.

Note: You can add multiple Baremetal Hosts with the same type of network connectivity shown in the diagram.

Server Infrastructure

Refer to the Support Matrix for details about the following:

Server infrastructure for HP Cloud OS for Moonshot Hypervisor recommendations for HP Cloud OS for Moonshot Node requirements for HP Cloud OS for Moonshot Moonshot chassis firmware version Operating systems supported Supported deployment scenario Included software

Network Infrastructure

The following networks are utilized in the HP Cloud OS for Moonshot infrastructure:

Admin Network: Provides connectivity between the Admin node, the Controller node and the Baremetal host. The Admin node provides DHCP and PXE services on this network.

Nova_Flat network: Utilized for connectivity between the Controller and Baremetal hosts and the Moonshot cartridges. The Controller node provides DHCP and PXE services for this network. Workloads are provisioned to the Moonshot cartridges using this network.

IPMI Network: Utilized for communication between the Baremetal host and the Moonshot Chassis Manager. This includes chassis and cartridge discovery, power control of cartridges and nodes, and monitoring of the health of the Moonshot systems.

Public Network: Provides public access to the HP Cloud OS for Moonshot Administration Dashboard and external access to the Internet for the Admin node and Controller node.

Notes:

The Admin node and the Controller node utilize Internet access to obtain updates and workload content from HP. If Internet access is not feasible from your datacenter, then it is possible for updates and workloads to be downloaded locally and then uploaded to your cloud environment.

The Controller node will require a static IP address on the Public network. Please consult with your network administrator to obtain the required static IP address.

Network Configuration

As shown in the deployment scenario diagram, HP Cloud OS for Moonshot will have the following network configuration:

Admin Node: 2 NICs - Admin Network and Public Network

Controller Node: 3 NICs - Admin Network, Nova_Flat Network, and Public Network

Baremetal Host: 3 NICs - Admin Network , Nova_Flat Network, and IPMI Network

The NICs per node/host NIC are as follows:

Admin Node

Admin Network Public Network

eth0 eth1 eth2

Controller Node Baremetal Host

Admin Network Nova_Flat Network Public Network Admin Network Nova_Flat Network IPMI Network

Review the Checklist of Values You'll Need in Advance

In addition to the information presented already in this topic, please review the following checklist before starting the installation. You'll need to specify the following types of information during the installation and configuration process.

Operation Dashboard Checklist

In Environment > Prerequisites, the dialogs will prompt for your external DNS IP details. In Edit Prerequisites > Admin Node Internet Access > Network, you will need to specify your:

NIC details for the public interface Http Proxy information:

Host Port-8080 Non-Proxy Hosts: 10.\*|192.\*|127.0.\*|localhost

In Environment > Networks, for your Public network:

On the Edit Network dialog, you will need to specify your Subnet, Netmask, and Router IP values. On the Edit Network Ranges dialog, you will need to specify your Node Type, IPV4 Start Address, and IPV4 End Address values.

In Environment > Networks, for your IPMI network:

In Environment > Networks, for your Nova_Flat network:

On the Edit Network dialog, you will need to specify your Subnet, Netmask, and Router (mandatory) IP values. On the Edit Network Ranges dialog, you will need to specify your Node Type, IPV4 Start Address, and IPV4 End Address values.

Note: You will be able to skip the Edit options for the Admin Network. In Environment > Complete Install, you will be asked to enter the top-level domain name for your cloud. The name you'll provide must consist of lowercase characters with no numbers or special characters. It may end in any valid web domain type, such as (but not limited to) .com, .org, .net, .edu, .mil, .gov. In Cloud > Manage Clouds > Create Cloud, you will only need to enter a Name for your cloud. You

can use default values for other options; however, plan ahead to specify new, non-default passwords for the Admin user, Arch user, and Trash user. In Cloud > Manage Clouds > Create Compute Region dialog, you will need to enter a Name for your region. Recommended: create multiple regions. On each Create Compute Region dialog, on the Controller & Compute Nodes tab, you will need to enter the number of nodes that participate in the region.

Administration Dashboard Checklist

In Project > Access and Security > Create Keypair, you will just need to enter the Keypair name. Note: You will not need to define flavors to complete the post-install steps. As explained later in

Launch Administration Dashboard for Post-Deployment Tasks, a flavor will be generated automatically

for you based on your Moonshot server cartridge type: hp_moonshot_server (for an HP ProLiant Moonshot Server Cartridge) and hp_moonshot_m300 (for an HP ProLiant m300 Server Cartridge). In Project > Infrastructure > Images, you will need to create images, and the associated Kernel and RAM disk images. You will not need to specify the Description, Minimum Disk, and Minimum RAM values. In Project > Moonshot Management, you will need to specify the chassis display name, Chassis Manager IP, Chassis Manager password, and Managing Host Name. In Project > Infrastructure > Images > Launch > Launch Instance dialog, you will need to specify the image, instance name, networking, and (pre-defined) flavor.

Next Step

Proceed to the next topic, Install and Set Up the Admin Node.

‹ PREV | ^ UP | NEXT ›

Install and Set Up the Admin Node

This topic explains how to install the Admin Node, which launches the Operational Dashboard and helps in setting up the environment to create a cloud.

Set Up the Admin Node

Boot the Admin Node Using the Cloud OS ISO

Launch the Operational Dashboard

Set Up the Admin Node

You can install the Admin Node only on a virtual machine. Use the following steps to create a virtual machine in an existing or a new hypervisor infrastructure:

Configure the hypervisor host's networking as shown in the Deployment Architecture. The host must provide connectivity to the Admin Node (virtual machine) on an isolated private network and also to all the nodes' port eth0. The Admin Node must also have connectivity to a routable network for Internet access.

Create a virtual machine (Admin Node) with the hardware configuration suggested in Cloud Infrastructure section. The following configuration must be reviewed during this step:

Ensure the Admin Node's primary NIC is bridged or connected to the admin network and the second NIC is bridged or connected to a routable network for Internet access. On a KVM based VM, for the disk configuration, ensure you set it to the IDE/SCSI type as this is the supported type.

Download the HP Cloud OS for Moonshot ISO to the host's local file system or data store.

Configure the Virtual Machine (VM) Admin Node to point to the HP Cloud OS for Moonshot ISO as a CD/DVD drive or install media ISO image.

Boot the Admin Node Using the HP Cloud OS for Moonshot ISO

The Admin Node is booted using HP Cloud OS for Moonshot *.iso. Follow these steps:

Ensure that ISO image is located in the host's local file system or data store.

Edit the settings of the Admin Node (Virtual Machine) so that the CD ROM points to the Cloud OS ISO image.

Switch on the power for the Admin Node. The machine begins to boot.

To view the boot process, select the Console Tab of the Virtual Machine.

In the Full Name of the new user box, enter the name. This is the name that will be used while sending emails or will be used at any other place where the full user name is displayed.

In the Username for your account box, enter a user name. This is the name with which you can log into your Admin Node. Note: The user name should start with a lowercase alphabet and can include numbers also.

In the Password box, enter the password. Note: The password should be a mix of letters, numbers and special characters and should be changed at regular intervals.

+ 30 hidden pages