HP Helion OpenStack Deployment on HP BladeSystem Blades
In a previous post, we talked about the turnkey solution of HP Helion Rack for building a private cloud based on HP Helion OpenStack software and HP ProLiant DL360 / DL380 Gen9 rack servers. HP also offers other deployment options for HP Helion OpenStack, depending on the needs of the customer and the skill level of its IT staff, including self-deploying the cloud on HP BladeSystem server blades using HP-prepared reference configurations. But before describing the process of installing HP Helion OpenStack on the blades, it’s worth mentioning the very deployment architecture of this software package.
To simplify the deployment process, HP Helion OpenStack includes several ready-to-use images of OpenStack services that are installed on servers that serve the cloud. These images are automatically deployed during the installation of HP Helion OpenStack using TripleO services.
TripleO uses the concept of deploying an OpenStack startup instance, which is then used to install and configure the entire HP Helion OpenStack cloud infrastructure used by end users. This starting instance is called the “lower cloud” (undercloud) and its main purpose is to prepare a productive or upper cloud deployment (overcloud), after which the undercloud is used only to administer overcloud, in which all end-user applications work:
')
HP Helion OpenStack Deployment Model
To start the installation process, HP Helion OpenStack installation uses a seed (seed) virtual machine Seed VM that is deployed on the KVM site (currently, the Ubuntu 13.10 and 14.04LTS operating systems are certified for the KVM host of the launch VM.)
When the Seed VM host virtual machine is installed and loaded, an undercloud instance is deployed with it. Undercloud needs to provide a description of the hardware allocated for the cloud and the required configuration of overcloud, on the basis of which overcloud controllers and necessary services will be deployed (for example, Swift, VSA Cinder software-defined storage nodes and KVM computing nodes).
Overcloud is a productive cloud in which end users request and receive services. It is deployed on dedicated servers and in the minimum configuration consists of:
Configuration overcloud (clickable):
On top of the cloud controllers, the main HP Helion OpenStack services are: Nova, Keystone, Glance, Cinder, Heat, Neutron, Ceilometer and Horizon.
Undercloud is deployed on a single physical server, and only the cloud administrator has access to it. Its functions include the provision of DHCP services and network boot for overcloud controllers, the provision of monitoring and recording of overcloud events, as well as its updating.
The Seed VM virtual machine runs the HP software that is included in the HP Helion OpenStack distribution for deploying the HP Helion OpenStack cloud environment. Also included in the delivery of HP Helion OpenStack are scripts to create a starting VM on the KVM node.
Also, the starting VM runs the backup and recovery scripts of the HP Helion OpenStack management servers, so you need at least 1 TB of disk capacity to store backup images.
In this example, HP BladeSystem blade servers are used to implement the HP Helion OpenStack universal launch cloud. The storage system uses the HP 3PAR 7400 disk array, which is connected to the HP BladeSystem chassis using a Fiber Channel switch and Virtual Connect modules installed in the chassis.
The BL460c Gen9 half-height blades are used to house the compute nodes and manage the cloud infrastructure. The HP BladeSystem c7000 chassis holds 16 such blades, and nine compute nodes are required to deploy the entire HP Helion OpenStack cloud. Thus, a single c7000 chassis is enough to deploy a cloud. Blades are loaded over the network from 3PAR disks.
This configuration includes the initial Swift infrastructure, which is deployed on two BL460c Gen9 blades. The Swift service is mainly used to store Glance images, snapshots, Content Delivery Network (CODN) updates, and Cinder backups.
The main components of this HP Helion OpenStack configuration on the BL460c Gen9 blades are shown in the table below:
In addition to the blades, one to seven c7000 chassis, depending on the size of the system, two 48-port SAN switches and an HP 3PAR 7400 disk array with four controller nodes are required for servicing the cloud infrastructure. In the recommended starting configuration, it is recommended to use an array with 72 10K disks at 1.2 TB and 24 7.2RPM disks at 1 TB.
Below is the layout of the components of the HP Helion OpenStack startup configuration on the HP BladeSystem c7000 blade system:
HP Helion OpenStack Startup Configuration on HP BladeSystem c7000 Blade System
Thanks for attention! Ready to answer your questions in the comments.
Our previous publications:
» HP Helion Rack - solution for the rapid deployment of a private cloud based on OpenStack
» HP OpenStack Helion - First Meet
» HP StormRunner Load. A practical guide. Part II
» HP StormRunner Load. A practical guide. Part I
»The correct bonus for your new server
» Cost-effective HP servers for SMB and providers
» SDN: alternative or addition to traditional networks?
» New network architectures: open or closed solutions?
» Implementing MSA in a virtualized enterprise environment
» HP MSA Disk Arrays as a Basis for Data Consolidation
» Multivendor corporate network: myths and reality
HP Helion OpenStack Deployment Architecture
To simplify the deployment process, HP Helion OpenStack includes several ready-to-use images of OpenStack services that are installed on servers that serve the cloud. These images are automatically deployed during the installation of HP Helion OpenStack using TripleO services.
TripleO uses the concept of deploying an OpenStack startup instance, which is then used to install and configure the entire HP Helion OpenStack cloud infrastructure used by end users. This starting instance is called the “lower cloud” (undercloud) and its main purpose is to prepare a productive or upper cloud deployment (overcloud), after which the undercloud is used only to administer overcloud, in which all end-user applications work:
')
HP Helion OpenStack Deployment Model
To start the installation process, HP Helion OpenStack installation uses a seed (seed) virtual machine Seed VM that is deployed on the KVM site (currently, the Ubuntu 13.10 and 14.04LTS operating systems are certified for the KVM host of the launch VM.)
When the Seed VM host virtual machine is installed and loaded, an undercloud instance is deployed with it. Undercloud needs to provide a description of the hardware allocated for the cloud and the required configuration of overcloud, on the basis of which overcloud controllers and necessary services will be deployed (for example, Swift, VSA Cinder software-defined storage nodes and KVM computing nodes).
Overcloud
Overcloud is a productive cloud in which end users request and receive services. It is deployed on dedicated servers and in the minimum configuration consists of:
- Three cloud controllers that are deployed on separate physical servers for high availability and assembled into a fault-tolerant cluster with data replication and active failover implementation.
- Start-up Failover Cluster Swift, deployed on two physical servers. The Swift cluster is used by the Glance service to store images and instant snapshots of instances, to back up user-defined virtual machines, and also provides the ability to organize horizontally scalable object data storage.
- One or more KVM computing servers or existing VMware ESXi clusters used to host user-defined virtual machines in the cloud.
- Swift Scale-Out horizontally scalable cluster for organizing large object storage (currently, the maximum amount is 0.5 PB).
- Cinder block storage based on StoreVirtual software-defined storage systems VSA (for high availability, you can use two-node and three-node VSA clusters). StoreVirtual VSA storage systems are deployed on ProLiant servers and merge their internal drives into a single disk pool.
- Cinder high-performance block storage based on an HP 3PAR disk array that other Helion OpenStack instances can share. (To implement Cinder block storage, you need VSA, HP 3PAR, HP P4000, or Ceph).
Configuration overcloud (clickable):
On top of the cloud controllers, the main HP Helion OpenStack services are: Nova, Keystone, Glance, Cinder, Heat, Neutron, Ceilometer and Horizon.
Undercloud
Undercloud is deployed on a single physical server, and only the cloud administrator has access to it. Its functions include the provision of DHCP services and network boot for overcloud controllers, the provision of monitoring and recording of overcloud events, as well as its updating.
Starting VM
The Seed VM virtual machine runs the HP software that is included in the HP Helion OpenStack distribution for deploying the HP Helion OpenStack cloud environment. Also included in the delivery of HP Helion OpenStack are scripts to create a starting VM on the KVM node.
Also, the starting VM runs the backup and recovery scripts of the HP Helion OpenStack management servers, so you need at least 1 TB of disk capacity to store backup images.
HP Helion OpenStack Deployment Example on HP BladeSystem with HP Server Blade BL460c Gen9 Blades
In this example, HP BladeSystem blade servers are used to implement the HP Helion OpenStack universal launch cloud. The storage system uses the HP 3PAR 7400 disk array, which is connected to the HP BladeSystem chassis using a Fiber Channel switch and Virtual Connect modules installed in the chassis.
The BL460c Gen9 half-height blades are used to house the compute nodes and manage the cloud infrastructure. The HP BladeSystem c7000 chassis holds 16 such blades, and nine compute nodes are required to deploy the entire HP Helion OpenStack cloud. Thus, a single c7000 chassis is enough to deploy a cloud. Blades are loaded over the network from 3PAR disks.
This configuration includes the initial Swift infrastructure, which is deployed on two BL460c Gen9 blades. The Swift service is mainly used to store Glance images, snapshots, Content Delivery Network (CODN) updates, and Cinder backups.
The main components of this HP Helion OpenStack configuration on the BL460c Gen9 blades are shown in the table below:
| Blade assignment | Number of blades | CPU | Memory | Storage system | Network connections |
| Seed VM host | one | 1 x 6 Core 2.4Ghz Intel Xeon | 16GB | Download by SAN: 2TB LUN to 3PAR | 10Gb FlexFabric LOM |
| Upper Cloud Controller | one | 2 x 6 Core 2.4Ghz Intel Xeon | 64GB | Download by SAN: 2TB LUN to 3PAR | 10Gb FlexFabric LOM |
| Lower Cloud Controller | 3 | 2 x 12 Core 2.6Ghz Intel Xeon | 64GB | Download by SAN: 2TB LUN to 3PAR | 10Gb FlexFabric LOM |
| Starter swift | 2 | 2 x 6 Core 2.4Ghz Intel Xeon | 32GB | Download by SAN: 4TB LUN to 3PAR | 10Gb FlexFabric LOM |
| KVM Compute | 1 - 100 | 2 x 14 Core 2.6Ghz Intel Xeon | From 384GB | Download by SAN: 4TB LUN to 3PAR | 10Gb FlexFabric LOM |
Below is the layout of the components of the HP Helion OpenStack startup configuration on the HP BladeSystem c7000 blade system:
HP Helion OpenStack Startup Configuration on HP BladeSystem c7000 Blade System
Thanks for attention! Ready to answer your questions in the comments.
Our previous publications:
» HP Helion Rack - solution for the rapid deployment of a private cloud based on OpenStack
» HP OpenStack Helion - First Meet
» HP StormRunner Load. A practical guide. Part II
» HP StormRunner Load. A practical guide. Part I
»The correct bonus for your new server
» Cost-effective HP servers for SMB and providers
» SDN: alternative or addition to traditional networks?
» New network architectures: open or closed solutions?
» Implementing MSA in a virtualized enterprise environment
» HP MSA Disk Arrays as a Basis for Data Consolidation
» Multivendor corporate network: myths and reality
Source: https://habr.com/ru/post/258905/
All Articles