HPE Synergy with Helion CloudSystem 10 Reference Architecture

Transcription

1 HPE Synergy with Helion CloudSystem 10 Reference Architecture HPE Helion CloudSystem/HPE OneView/HPE Synergy Integration

2 Contents Executive summary... 3 Overview... 3 Integration of Synergy with Helion CloudSystem Helion CloudSystem Foundation with Synergy... 5 Helion CloudSystem Enterprise with Synergy... 6 Deployment options... 6 Hardware requirements and cloud configuration sizing... 7 Cloud configuration sizing... 7 High availability installation options... 8 Management hypervisor hardware requirements: Physical HA... 8 Overview of Helion CloudSystem networks Example network configuration of ESXi management environment using HPE Synergy Composer.. 12 Preparing HPE Synergy Composer for Helion CloudSystem integration Network configuration for the control plane in HPE Synergy Composer Step 1: Set up the control plane networks in HPE Synergy Composer Step 2: Group networks into network sets Step 3: Create a Server Profile Template Step 4: Create a Server Profile from the Server Profile Template Network Configuration for the compute plane in HPE Synergy Composer Network Configuratiothe control plane and compute plane in vcenter Step 1: Configure the Management host in vcenter Step 2: Configure an ESXi compute cluster in vcenter Helion CloudSystem Installation Deploying Helion CloudSystem in an ESXi management environment Deploying Helion CloudSystem in a KVM management environment Deploying Helion CloudSystem using the CLI Configuring the Management hypervisors and managed resources using HPE Synergy Composer Connecting HPE Synergy Composer and ICsp appliances to Helion CloudSystem Preparation for ESXi compute cluster deployment in the Operations Console Provisioning and auto-activating an ESXi compute cluster using ACE Deleting and unprovisioning an ESXi compute cluster created by ACE Discover and import RHEL KVM hosts and ESXi clusters as compute hosts Auto-create host aggregates based on hardware characteristics Limitations Resources and additional links

3 Executive summary HPE Synergy, the first Composable Infrastructure, empowers IT to create and deliver new value instantly and continuously. This single infrastructure reduces operational complexity for traditional workloads and increases operational velocity for the new breed of applications and services. Through a single interface, HPE Synergy composes compute, storage, and fabric pools into any configuration for any application. It also enables a broad range of applications from bare metal to virtualized to containers, and operational models like hybrid cloud and DevOps. HPE Synergy makes IT an internal partner to rapidly launch new businesses. HPE Synergy Frames contain a management appliance called the HPE Synergy Composer which hosts HPE OneView. HPE Synergy Composer manages the Composable Infrastructure and delivers: Fluid pools of resources, where a single infrastructure of Compute, Storage, and Fabric boots up ready for workloads and demonstrates self-assimilating capacity. Software-defined intelligence, with a single interface that precisely composes logical infrastructures at nearinstant speeds; and demonstrates template-driven, frictionless operations. Unified API access, which enables simple line-of-code programming of every infrastructure element; easily automates IT operational processes; and effortlessly automates applications through infrastructure deployment. HPE Helion CloudSystem is an open, secure, and integrated cloud solution that offers enterprises an easy path to hybrid cloud - to quickly build and manage both traditional and cloud-native workloads. The end-to-end service lifecycle management solution gives the ability to provision applications and their corresponding infrastructure resources. With an open-source approach and support for hybrid service delivery, Helion CloudSystem provides the ability to run on-premises services in the private cloud while simultaneously managing off-premises services or bursting to external public cloud providers. HPE OneView is a converged management application for HPE hardware that eliminates infrastructure complexity with simplicity and automation. HPE OneView is designed to accelerate IT operations for managing servers, storage, and network resources. It is the foundation for managing HPE Converged Infrastructure across servers, storage, and networking. The HPE Helion Cloudystem 10 release provides integration with HPE OneView, thereby offering an end-to-end customer experience to discover, automatically provision, and consume compute and storage servers managed via the HPE OneView unified APIs. Cloud operators can gain greater visibility into the underlying infrastructure topology and have the ability to discover and provision the bare metal servers managed by OneView into the cloud resource pool. With HPE Helion CloudSystem and HPE OneView working together, customers can deploy the hardware, infrastructure management and cloud management stack as a seamless solution. Overview HPE Synergy with HPE Helion CloudSystem 10 brings the power of cloud on the composable platform and is the first hybrid cloud built on the composable platform. While Synergy offers the greatest flexibility in composing the physical resources, Helion CloudSystem builds on it by bringing the composability to virtual instances, containers and applications. Through integration with the Synergy composer, the cloud operator can selectively utilize the Synergy infrastructure to build a private cloud on premise while also having the ability to tap into public cloud resources as needed. Helion CloudSystem consists of two offerings: HPE Helion CloudSystem Foundation and HPE Helion CloudSystem Enterprise. In the following figure, HPE OneView refers to both HPE OneView and HPE Synergy Composer. 3

4 Figure 1: Helion CloudSystem architecture HPE Helion CloudSystem Foundation HPE Helion CloudSystem Foundation is cloud computing software designed for infrastructure services (IaaS) provisioning, and engineered to be easy to install, use, manage and extend. Built on enterprise-grade OpenStack technology, CloudSystem Foundation offers OpenStack Nova (compute), Cinder (block storage services on HPE 3PAR StoreServ Storage and HPE StoreVirtual VSA, and on VMware VMFS datastores), Neutron (networking built on HPE networking Software Defined Network (SDN) technology), Keystone (identity), Glance (image repository on traditional file systems) among other services as well as a Horizon-based dashboard. Helion CloudSystem Foundation allows you to: Provision core infrastructure services within minutes, powered by HPE's enterprise-grade OpenStack technology Utilize open APIs for both administrative and cloud service functions, including OpenStack APIs, enabling highly automated cloud delivery Deploy a fast and easy installation via software appliance delivery model Perform administration tasks simply, integrated with the HPE Synergy Composer console Ability to seamlessly upgrade to HPE Helion CloudSystem Enterprise software HPE Helion CloudSystem Enterprise Helion CloudSystem Enterprise is a hybrid cloud platform for delivering advanced infrastructure and application services in minutes. It features a sleek user interface and integrates capabilities previously delivered through separate products, making holistic management of all cloud services easier than ever before. HPE CloudSystem Enterprise software is cloud management software designed to deliver advanced infrastructure services, as well as platform and application services with an add-on software package. 4

5 HPE Helion CloudSystem Enterprise software includes HPE CloudSystem Foundation software as resource provider as well as HPE Cloud Service Automation and HPE Operations Orchestration for advanced infrastructure services. HPE Helion CloudSystem Enterprise add-on software packages can be included for platform and application services creation and management, including HPE Server Automation, Database and Middleware Automation and IT Executive Scorecard. Helion CloudSystem Enterprise provides an organization with the following benefits to help with their private / hybrid cloud deployments. Automated delivery of advanced infrastructure and application services in minutes A drag-and-drop designer for rapidly defining new multi-tier cloud services A consumer-inspired self-service marketplace portal, powered by HPE Cloud Service Automation, which makes it easy for consumers to request cloud services Enterprise-class lifecycle management for cloud services from initial provisioning, through ongoing scaling, updating, and monitoring, to final service retirement Hybrid cloud management, with out-of-the box support for Amazon Web Services, Microsoft Azure Service portability in hybrid environments with Topology and Orchestration Specification for Cloud Applications (TOSCA) compliant service designs Customizable automation of approvals, service delivery and cloud administration tasks, delivered via the HPE Operations Orchestration workflow engine Figure 2: Helion CloudSystem Enterprise overview Integration of Synergy with Helion CloudSystem 10 Helion CloudSystem Foundation with Synergy Helion CloudSystem Foundation offers the following benefits through the integration with Synergy: Discover list the OneView managed hardware inventory in the cloud operations console Provision create compute clusters and storage resource pools ready to be used as cloud resource pool Activate auto deployment and configuration of OpenStack compute and network agents onto the provisioned clusters. 5

6 Aggregate auto grouping or aggregating compute hardware for class of service scheduling Figure 3: Consumption of bare metal servers as a compute host or a storage resource Helion CloudSystem Enterprise with Synergy CloudSystem Enterprise includes HPE Cloud Service Automation (CSA) which enables configuring HPE Synergy Composer as a provider. This integration provides the following benefits: Physical provisioning HPE CSA can provision server(s) from OneView along with the operating system (through Insight control server provisioning manager) of choice Hybrid (Physical/Virtual/Public cloud) HPE CSA can configure Synergy physical servers as part of a larger hybrid service design or a tiered architecture. This brings the value Synergy in concert with the other infrastructure present on-premises or services in the public cloud Deployment options HPE Helion CloudSystem can be deployed in the following ways: A. Deploy the Helion CloudSystem management plane on standard HPE ProLiant DL rack servers (e.g. DL360) and consume Synergy as the compute and storage resource pool. This is the standard deployment model for Helion CloudSystem and is not specific to Synergy. This follows the deployment best practice of physically separating the cloud management and the compute plane. Since this is the standard CloudSystem deployment option, we will not cover it in detail as part of this reference architecture. It is recommended to have three servers constituting the management plane to ensure high availability of cloud management functions. This deployment can start with a single Synergy frame with two or more compute modules. B. Deploy the Helion CloudSystem management plane on Synergy in this model, a minimum starting configuration of three Synergy frames is recommended to support an HA environment. One compute module from each of the three frames will constitute the cloud management plane. HPE Synergy with HPE Helion CloudSystem is fully tested and supported with VMware ESXi and Red Hat Enterprise Linux KVM as both management and compute hypervisors. 6

7 Figure 4: Synergy with CloudSystem Deployment options Hardware requirements and cloud configuration sizing The hardware requirements for the physical management cluster depend on: The size of the cloud that you plan to deploy The high availability option you configure for the cloud. Cloud configuration sizing Determine the which size cloud you need extra-small, small, medium, or large. The cloud is the total number of compute hosts, virtual machine instances, networks, and the Helion CloudSystem virtual appliances that manage the cloud. Medium and large sizes are supported only in clouds configured with Physical HA in a three host management cluster. Definitions of small, medium, and large cloud configurations Extra-small: Up to 5 compute nodes, 250 virtual machine instances, and 30 tenant and provider networks Small: Up to 20 compute hosts, 1000 virtual machine instances, and 125 tenant and provider networks Medium (default): Up to 80 compute hosts, 5000 virtual machine instances, and 500 tenant and provider networks Large: Up to 200 compute hosts, 10,000 virtual machine instances, and 1100 tenant and provider networks 7

8 High availability installation options Determine the HA installation option you need. Hewlett Packard Enterprise recommends that you configure your cloud with Physical HA. Physical HA Management cluster with three hosts (recommended) Helion CloudSystem virtual appliances are deployed in trios and distributed across three physical servers. This configuration offers high availability and performance benefits for robust production use. Virtual HA Management cluster with a single host Helion CloudSystem virtual appliances are deployed in trios on one physical server. This configuration is supported for small development, test, or production environments where physical high availability is not a requirement. Contact HPE Support for assistance if you want to expand to a three host HA configuration after deployment is complete. For ESXi environments, you can expand to a cluster configuration after deploying Helion CloudSystem. For KVM environments, you can expand to a cluster later only if you originally created a shared volume that can handle three nodes. Non-HA Management cluster with a single host Helion CloudSystem virtual appliances are deployed as singletons on one physical server. If you use this configuration, you cannot expand to a three host HA configuration after deployment. Management hypervisor hardware requirements: Physical HA The following tables show the hardware requirements for each host (physical server) in a three host management cluster (Physical HA). For information about hardware requirements for Virtual HA and Non-HA deployments, see the HPE Helion CloudSystem 10.0 Update 1 Support Matrix at 8

9 Glance image sizing Glance images are stored on a shared cluster volume in the Management hypervisor. External storage for Glance images is not supported. You set the size of the Glance disk when you deploy Helion CloudSystem. You can increase the size of the disk after installation. 9

10 Overview of Helion CloudSystem networks Figure 5: Logical network topology (CVR) Table 1: Helion CloudSystem networks Network Description Count Used By Notes CONF (HLM) Dedicated for server OS installation, configuration, and provisioning. Deployer UI 1 Control plane Must be untagged. Used to access mgmt hosts and all appliances in control plane by administrator and Deployer appliance. IPMI/iLO can be reached from this network for physical provisioning. For ESXi mgmt cluster, vcenter must be reachable from this network. If FQDN is used in installation configuration, DNS server is accessible from this network. DCM (ADMIN) Connects services in CS appliances to HPE Synergy Composer, 3PAR, vcenter, vcns, etc. ToR and Operations Console are accessible from this network. 1 Control and mgmt plane Keystone admin endpoint is on this network. NTP server, DNS server, vcenter servers, HPE Synergy Composer, and other datacenter services can be accessed from this network. CAN (PUBLIC) Gives cloud end users access to CloudSystem Foundation user portal, Enterprise Marketplace Portal, OpenStack APIs (public 1 API Keystone public endpoint is on this network if configured; fallback to DCM is supported. 10

11 URLs), and Marketplace Portal APIs. INTERNAL (CLM) Dedicated private network for cloud management that should not be routed with any other networks in the data center. All cloud services communicate with this network. 1 Control plane Keystone internal endpoint is on this network if configured; fallback to DCM if not provided. Do not combine this network with DCM for production environment. EXTERNAL (EXT) PROVIDER Tunnel Underlay (TUL) VLAN Data Trunk (VUL) SWIFT (OBS) Object Proxy (obp) iscsi (bls) OSDI (osdi) OSDC (osdc) FC Neutron external network with floating IP and network node routing/nat ing Neutron provider networks to enable in-cloud services communicate with services in legacy data center networks Underlay network that is VLAN tagged to carry VxLAN traffic from tenant VMs across different hosts Cloud data trunk to support VLAN tenant networks Swift is configured to use this fixed address network for proxy to object traffic and for replication, rebalancing, and other internal Swift traffic. Network used for traffic from the load balancer to the Swift proxy and proxy to object traffic in front of Swift services. Optional iscsi storage network for VSA/3PAR Cinder. It is mandatory when KVM compute nodes are part of the deployment to support VSA/3PAR Cinder volumes. Compute hosts use this fixed address network to connect to block storage volumes for VMs. Other block storage traffic (e.g. snapshots) also use this network Ceph specific network for internal traffic among OSD clusters Ceph specific network for client traffic Optional FC SAN for 3PAR Cinder or hypervisor backing storage 0 to n Neutron VLAN network that is routed externally. The number of EXT networks will depend on NIC configuration (refer to the CS 10 network GUIDE). 0 to n* Neutron Hardware L2 gateway will be used for provider network on VxLAN. 0 to 1 Neutron Can be an existing network in the management trunk, but separate dedicated data trunk is recommended to carry tenant network traffic. 0 to n* Neutron Must be a separate date trunk. Can support more than one such network type per deployment with multiple data trunks. 0 to 1 Swift Required for Swift 0 to 1 Swift Required for Swift. Scale-out Swift is extended into this network. 0 to 1 VSA Required for VSA 0 to 1 Ceph Required for Ceph 0 to 1 Ceph Required for Ceph 0 to 1 * Depends on the Cloud size 11

12 Example network configuration of ESXi management environment using HPE Synergy Composer Environment details This example configuration is an ESXi based implementation that uses HPE ProLiant DL360 Gen9 servers as HPE Helion CloudSystem management servers and an HPE Synergy Frame populated with HPE Synergy BL 480 Gen9 servers for the compute hosts. The Compute host(s) network type is configured as VxLAN and uses the OVSvApp network configuration. In this sample configuration, the Data Center Management Network and Consumer Access Network are using Static IP addresses. Table 2: Servers used in the sample configuration with their roles (configured as Deployment Option A in Deployment options ) Server Role Count Server Model Network Adapters Network Trunk Management Servers 3 HPE ProLiant DL360 Gen9 servers Compute Hosts 10 HPE Synergy 480 Gen9 1 Servers 2x 10Gbps 2x 2Gbps 2x 1Gbps 2x 2Gbps 2x 7Gbps Cloud Data Trunk Management Trunk and VMware vmotion/ha Management Trunk VMware vmotion/ha Cloud Data Trunk NOTE: it is highly recommended to split the Management and vmotion Trunks for the compute hosts. The vmotion network will need to be highly configurable for security reasons and large scale environment. Table 3: Enclosure and network switches used for HPE Helion CloudSystem installation Role Configuration BladeSystem Enclosure 1 HPE Synergy Frame Frame includes: Virtual Connect SE 40Gb F8 Modul Virtual Connect SE 16Gb Fibre Channel Modul Ba ys 1-10 Network Switch HPE 5900 Series Network Switch Important: The network cards and their corresponding configuration for the Storage Trunk are not included as part of this example configuration. Those components are only required to be installed for a Scale-out Swift configuration. This configuration utilizes Active/Active network paths for high availability. The following network components and options were configured to achieve an Active/Active configuration: In the ToR switches, network bonding is configured. In HPE Synergy Composer, two definitions for each network are created with one path being the A path and the other the B path. These A and B paths are then bound to their corresponding A and B interconnects. Network teaming is configured for the vswitches on the ESXi hosts. 12

13 Figure 6: Physical and logical network configuration ESXi environment (configured as Deployment Option A in Deployment options ) Preparing HPE Synergy Composer for Helion CloudSystem integration You can use HPE Synergy Composer to manage the hardware that hosts both the management hypervisor (control plane) and compute hosts (compute plane) in Helion CloudSystem. Before deploying Helion CloudSystem, the following steps must be completed in the HPE Synergy Composer. High level process overview 1. Install and configure HPE Synergy Composer. 2. Use one of the following certificate management options: Use a trusted Certificate Authority known to Helion CloudSystem (for example, Verisign or Digicert) when configuring HPE Synergy Composer, or Import and install the HPE Synergy Composer self-signed certificate. See HPE Synergy Composer certificate registration with Helion CloudSystem for detailed steps. 13

14 3. Obtain the number of interfaces supported by the hardware that is used to host Helion CloudSystem: Number of physical interfaces Number of virtual connections 4, Define the Helion CloudSystem networks in HPE Synergy Composer. See Network configuration for the control plane in HPE Synergy Composer. a. Assign a VLAN ID to CONF when the network is created. Then, when you add it to the network set, check the Untagged option. b. Apply Logical Interconnect Groups to the appropriate Logical Interconnect, making them available to servers. c. Add Helion CloudSystem networks to Network Sets in HPE Synergy Composer. d. Map Network Sets to the available interfaces, and if needed, make sure a teaming/bonding strategy is in place. 5. Create a Server Profile Template for the Management hypervisor. 6. Create a Server Profile from the Server Profile Template. 7. Create a Server Profile Template for each type of compute resource you plan to add to your cloud. 8. Create a Server Profile Template for each type of storage you plan to add to your cloud. Network configuration for the control plane in HPE Synergy Composer The control plane consists of the management hypervisor cluster, Helion CloudSystem appliances, and their associated networks. The compute plane consists of compute hosts and their associated networks. This paper describes deploying HPE Helion CloudSystem servers on HPE Synergy hardware. Throughout the paper we will reference features in the HPE Synergy Composer console to set up the server profiles, network, and storage. The best practice recommendation is to add the control plane networks to a management network set and connect the network set to the Management hypervisor using one interface with NIC teaming. The networks must each have a unique VLAN ID, unless you are combining some network roles together on a network. An optional configuration is to connect the CONF network to one interface and then add all remaining control plane networks to a Management network set that uses a second interface with NIC teaming. Step 1: Set up the control plane networks in HPE Synergy Composer Log in to the Synergy Composor and create your networks and network sets that will be included in the appropriate Logical Interconnect Group. After you create the networks, associate them with a Logical Interconnect Group by adding them to uplink set. This allows you to use the networks that you created with your blades. Create one network set for each group of networks, all networks must be configured with the correct VLAN ID. The network that will be used to communicate between vcenter and the ESXi compute host must have the Purpose set to Management. This setting instructs the clustering software where to assign an IP from the IP pool. Option 1: Separate the ESXi Management network and Data Center Management network Option 2: Combine the ESXi Management network with the Data Center Management network. In HPE Synergy Composer, select Logical Interconnect Groups and create a new group that contains the networks needed if one does not already exist. 14

15 Figure 7: Logical Interconnect Group that includes the uplink sets and networks 15

16 Step 2: Group networks into network sets In HPE Synergy Composer, add all of the Helion CloudSystem networks to a Network Set. This simplifies configuration while maintaining maximum flexibility, and makes it easier to apply a consistent set of networks to a Server Profile Template. If you need to maintain separation traffic over your two NICs, you can create separate Network Sets with the traffic separated the as desired. (This will require coordination when creating the CS10 deployment to ensure the correct networks are on the correct interfaces). The following map shows how Network Sets are connected to the control plane Server Profile Template (CS10-CP- ESX-TEMPLATE), which is used to configure the Management Trunk (MGMT_2) for the control plane. 16

17 NOTE: Not all VLANs are included. This MAP is merely an example of an ESXi profile template. Control Plane Management Network Set This is the set of networks used for managing the Helion CloudSystem appliances, accessing the management console, and so on. Figure 8: Control Plane Management Network Set HPE recommends that you use NIC bonding for network redundancy and better throughput. Example install options file for configuring ESXi NIC bonding: # For ESX, following bond modes are supported: # virtual-port 17

18 # ip-hash # srcmac-hash # explicit-order # nic-load (Only supported for VDS) # Following are examples of ESX bonding definitions bonds: bond0: devices: - vmnic0 - vmnic1 mode: virtual-port bond1: devices: - vmnic4 - vmnic5 mode: virtual-port CONF network configuration details For each network, specify the required options, such as bandwith. The CONF network is used for HLM configuration. The CONF network must be untagged, even if it is combined with other networks, such as vcenter management network. Make sure the CONF network is untagged when adding it to the Network Set, which enables it to participate in PXE booting functions. 18

19 When used in the installation options yml file, the CONF network options are shown below with example values: # An untagged hlm configuration network # This network cannot shared with any other tagged network. - name: CONF types: - hlm members: cidr: /16 start-address: end-address: gateway-ip: iface: bond0 Data Network Set This set of networks is used for VM workload traffic set on the compute node. The following map shows how Network Sets are connected to the control plane Server Profile Template (CS10-CP- ESX-TEMPLATE), which is used to configure the DATA trunk (DATA_2). 19

20 Example of how the data network is specified in the install options yml file: # A VxLAN underlay network w/tenant VNI range between and name: VxLAN types: - tul members: - vlanid: 501 cidr: /21 start-address: end-address: gateway-ip: iface: bond1 range: "10000:20000" Using VxLAN allows you to support a higher number of tenants; VLAN is limited to a smaller number. Storage Network Set Storage network sets are network uplinks (interfaces) dedicated to cloud storage. You can add all storage networks to one Storage Network Set and use one interface connection. Optionally, you can create a separate Storage Network Set for each type of storage and support each set with a separate interface connection. Figure 9: Sample Storage networks viewed in HPE Synergy Composer 20

21 NOTE: iscsi and Object Storage networks are not required or used for ESXi. They are optional for use with KVM. Step 3: Create a Server Profile Template Create a Server Profile Template that will contain the Network Sets created in the previous step. In the Server Profile Template, add a connection and select the Network Set. (See the following figures for ESXi and KVM examples.) Connections will be applied to the server in the order they are listed. If you are separating networks between the physical NICs, keep in mind that the first connection is eno1/eth0. NOTE: Server profile templates for Helion CloudSystem must be named with the prefix CS10-. Figure 10: ESXi control plane Server Profile Template 21

22 22

23 23

24 Figure 11: RHEL KVM control plane Server Profile Template 24

25 25

26 Step 4: Create a Server Profile from the Server Profile Template Each server blade must have a Server Profile. The server profile contains all of the networks that were created in the Server Profile Template which will be used on each interface in the server profile. This allows you to configure bonding or to separate traffic depending on how the installation configuration (cs_install_options.yml) file is defined. When you click Create Server, the server is configured based on the Server Profile Template and the server can be powered on and OS installed. The following figure shows a fully configured Server Profile for the control plane ESXi cluster members in HPE Synergy Composer. Figure 12: Server Profile for Control Plane ESXi cluster members 26

27 27

28 Table 4: Network usage, which is defined in the cs-install-options.yml file # Define each network. In CS a network could have following types: # 0. hlm -- CONF network # 1. internal -- CLM network # 2. admin -- DCM network # 3. public -- CAN network # 4. external -- Neutron External network # 5. vul -- VLAN underlay network # 6. tul -- Tunnel underlay network # 7. bls -- Block storage network. Could be used for VSA # 8. obs -- Object storage network such as used by swift backend # 9. pxe -- PXE network #10. osdi -- Ceph internal network #11. osdc -- OSD client is also on this network #12. l2 -- A plain l2 network #13. l3 -- A plain l3 network Example of the External network. Notice that the VLAN ID must match. # An external network trunk to support multiple external networks - name: EXTERNAL - types: - external - members: - vlanid: iface: bond0 Network Configuration for the compute plane in HPE Synergy Composer The following figure shows the compute host operating systems supported for each underlay network type (VxLAN or VLAN) and each virtual router type (DVR or CVR). When deploying Helion CloudSystem, choose the virtual router type that supports the type of compute hosts planned for the cloud environment. Helion CloudSystem supports two types of Data networks: one Tunnel Underlay Network (VxLAN) and multiple VLAN Data Trunks. Add Data networks that support the type of compute hosts planned for the cloud environment. Figure 13: Underlay network and virtual router types for compute hosts In HPE Synergy Composer, create a server profile for each type of compute host you want to include in your cloud. 28

29 The following examples show server profiles for ESXi and RHEL Linux compute hosts. Figure 14: Server profile for ESXi compute cluster 29

30 Figure 16: Server profile for RHEL Linux compute host Network Configuratiothe control plane and compute plane in vcenter Step 1: Configure the Management host in vcenter In the vcenter Datacenter, configure the Helion CloudSystem control plane DV swtich for the Management and Data trunks as specified in the Server Profile Template you created in HPE Synergy Composer. The following figures show the required DV switch configuration for the Management and Data trunks. 30

31 Figure 18: Management Trunk DV Switch NOTE: Only CONF, DCM, and vmotion ports must be created before installing Helion CloudSystem. All other ports are automatically created by the Helion CloudSystem installer. 31

32 Figure 19: Data Trunk DV Switch NOTE: The Data trunks and ports are automatically created by the Helion CloudSystem installer. Step 2: Configure an ESXi compute cluster in vcenter The Management and Data trunk in the vcenter must be configured as specified in the Synergy Composer Server Profile Template. The example below demonstrates the required DV switch configuration. Some ports are automatically created by the Helion CloudSystem activation process. Figure 20: Management and Data distributed switches (ESXi compute cluster) 32

33 Helion CloudSystem Installation Helion CloudSystem 10 allows you to easily install Helion CloudSystem Foundation and Enterprise together, or install Foundation only or Enterprise only. You can also install Foundation, then install Enterprise at a later time. Benefits Deploy Helion CloudSystem as an on-premises, private cloud solution that supports both HPE and non-hpe hardware Configure the virtual appliances with the easy-to-use csdeployer using either a UI or CLI interface Create a highly available, scalable, secure configuration with Helion OpenStack, HPE CSA, OO, and Helion CloudSystem management services deployed as o o Active-Active HA configuration. Non-HA configurations are also supported Refer to the following documents for detailed installation information. These documents are available at HPE Helion CloudSystem 10.0 Update 1 ESXi Installation Guide HPE Helion CloudSystem 10.0 Update 1 KVM Installation Guide Deploying Helion CloudSystem in an ESXi management environment The following examples show the Helion CloudSystem Deployer user interface to install Helion CloudSystem in an ESXi management hypervisor cluster. The the following example demonstrates uploading an options file that includes options that may not be required for your environment. For a list of installation options, see the Helion CloudSystem installation and network planning documentation at 33

34 Figure 21: Installing Helion CloudSystem in an ESXi environment 34

35 35

36 36

37 Deploying Helion CloudSystem in a KVM management environment The following examples show the Helion CloudSystem Deployer user interface to install Helion CloudSystem in a KVM management hypervisor cluster. 37

38 Figure 22: Installing Helion CloudSystem in a KVM environment 38

39 39

40 Deploying Helion CloudSystem using the CLI If you prefer to use csstart (for KVM) and csdeploy (for ESXi and KVM) CLIs to deploy Helion CloudSystem, perform the following high-level steps. Refer to the following documents for detailed installation information. These documents are available at HPE Helion CloudSystem 10.0 Update 1 ESXi Installation Guide HPE Helion CloudSystem 10.0 Update 1 KVM Installation Guide Example installation configuration files TIP: Example installation configuration files are attached to this PDF. To reveal the text files, click the paper clip icon on the left side of the PDF. cs-esxi-install-options.yml cs-kvm-install-options.yml Create the Deployer appliance using csstart (KVM only) 1. Generate the Helion CloudSystem configuration file:./csstart generate-config --path /root/cs10/ The generated config file is named cs-install-options.yml. 2. Add your environment details to the configuration file. 40

41 3. Download and read the license agreement:./csstart save-eula --path /root/cs10/ Deploy the cloud using csdeploy (ESXi and KVM) 1. Using stack credentials, log in to the Deployer virtual appliance. (For KVM environments, you created the appliance using csstart. For ESXi environments, you created the appliance in vcenter.) 2. Open the directory /etc/csdeploy/examples. Select a cloud configuration and update it with your requirements. 3. Run the validate command: csdeploy validate --eula-accepted --config /etc/csdeploy/cs-install-options.yml \ --add-foundation --add-enterprise 4. Run csdeploy, referencing the configuration file you created (cs-install-options.yml). Foundation only installation: csdeploy start --eula-accepted --config /etc/csdeploy/cs-install-options.yml \ --add-foundation 2>&1 tee /home/stack/csdeploy-foundation.log Enterprise only installation: csdeploy start --eula-accepted --config /etc/csdeploy/cs-install-options.yml \ --add-enterprise 2>&1 tee /home/stack/csdeploy-enterprise.log Foundation and Enterprise installation: csdeploy start --eula-accepted --config /etc/csdeploy/cs-install-options.yml \ --add-foundation --add-enterprise 2>&1 tee /home/stack/csdeploy-foundent.log Configuring the Management hypervisors and managed resources using HPE Synergy Composer HPE Synergy Composer provides the physical infrastructure required to support virtualization, cloud computing, big data, and mixed computing environments. Use HPE Synergy Composer to manage your converged infrastructure and support key scenarios such as: auto-discover HPE Synergy Composer compute, storage, and HPE 3PAR storage hardware capabilities auto-annotate discovered capabilities as attributes on OpenStack compute aggregates match annotated flavors against annotated compute aggregates With Helion CloudSystem and HPE Synergy Composer working together, you can: Connect HPE Synergy Composer (as HPE OneView) and HPE Insight Control server provisioning (ICsp) in Helion CloudSystem Automatically discover hardware inventory and topology from HPE Synergy Composer into Helion CloudSystem as compute resources 41

42 Provision and automatically activate bare metal HPE Synergy and other HPE hardware as ESXi compute clusters through the HPE Synergy Composer API and a connected Insight Control server provisioning deployment server Discover and import existing ESXi and Red Hat Enterprise Linux hypervisors found in HPE Synergy Composer. Connecting HPE Synergy Composer and ICsp appliances to Helion CloudSystem Before you use HPE Synergy Composer for ESXi compute cluster provisioning, you must connect HPE Synergy Composer to Helion CloudSystem, and you must connect HPE Insight Control server provisioning (ICsp) to HPE Synergy Composer in Helion CloudSystem. You connect these appliances using the Integrated Tools screen in the Operations Console. For detailed information, see the Integrated tools connectivity and configuration chapter in the HPE Helion CloudSystem 10.0 Update 1 Administrator Guide at Preparation for ESXi compute cluster deployment in the Operations Console HPE Synergy Composer Before setting up HPE Synergy Composer, you must identify and define the network layout. The datacenter administrator configuring HPE Synergy Composer creates the networks based on the decisions made in Network configuration for the control plane in HPE Synergy Composer. Network configuration checklist HPE Synergy Composer configuration o Server profile template name is prefixed with CS10- Add connections to PXE, CLM, CONF and other data center networks Add connections to any SAN o Networking, IP pools, uplink sets are configured to allow access to CS10 networks o Shared storage volumes or storage volume templates are configured o vcenter is connected to HPE Synergy Composer (HPE OneView) in the Operations Console 42

43 o ICsp is connected to HPE Synergy Composer in the Operations Console o Helion CloudSystem can communicate to HPE OneView / ilo over HTTPS Import HPE Synergy Composer certificate into Helion CloudSystem o SAN Manager is configured o HPE 3PAR Storage System and storage pools are configured in HPE Synergy Composer o Volumes required for ESXi clusters are shared Create storage 3PAR SAN volumes or Create storage templates, and volumes will be created on demand ESXi management network IP pool is created in HPE Synergy Composer o Network must be reachable from DCM (can be through routes or addresses outside of the CONF registered DCM range) o These addresses will be used for management (vcenter) o Subnet is created for IP pool associated to the ESXi management network o Regenerate ilo certificates then import into CS Turn off certificate validation when needed for POCs Pre-provisioned hypervisors o No CONF IP, no auto import / activation for KVM hypervisors o No SAN storage in server profile, no discovery of pre-provisioned hypervisor types ICsp configuration o PXE network is isolated from cobbler PXE (Two PXE networks when Cobbler is enabled) o Build plans for CS must be named with the prefix CS10-ESXi- Storage Configuration checklist ESXi compute nodes require shared volumes across the nodes in a cluster. Only 3PAR SAN Storage is supported if the provisioning and activation of ESXi clusters is done automatically from Helion CloudSystem. To facilitate auto zoning, SAN Manager is required. Use the HPE Synergy Composer UI to: Add Storage System - Select the storage pools and select the Storage System ports. Refer to HPE OneView documentation about adding Storage Systems at Add SAN Manager - Refer to HPE Synergy Composer documentation at HPE Integrated Systems Information Library and SAN Manager documentation at HPE Storage Information Library. StoreVirtual VSA can be used for Helion CloudSystem supported data storage (Cinder block storage or ESXi cluster shared datastore) as long it is configured manually or by using the Helion Lifecycle Manager (HLM). For example, the StoreVirtual VSA D3940 module can be configured with a Synergy blade, deployed to Helion CloudSystem, then added as a Cinder driver for block storage. For detailed information, see the Cinder (block) storage configuration and management chapter in the HPE Helion CloudSystem 10.0 Update 1 Administrator Guide at NOTE: Provisioning an ESXi Cluster automatically in the Operations Console through the ACE service is supported only using a 3PAR storage system configured in HPE OneView. Cluster provisioning IP addresses requirement When a cluster is provisioned, the cluster will have an adapter on the network from the Sample Single NIC Configuration section that was given the Management purpose. This management annotated network will be given an IP address from the pool setup below. 43

44 Create an IPv4 subnet and range The addresses from this range will be used in the deployed ESXi nodes and must be within the subnet used by vcenter. Give sufficient range to support enough deployments of ESXi nodes. When an ESXi cluster provisioned using HPE Synergy Composer is deactivated, the address is returned back to the pool. An address pool cannot be modified if a cluster is provisioned and active. If you are running out of addresses, add a new range pool. Identify the network that will be assigned the address from above range. In this case we are using CONF to be our management network. Navigate back to Networks. NOTE: when using the CONF network as the ESXi management network, make sure you obtain the range reserved for compute host provisioning. This range is available on the Deployer node in the file ~helion/my_cloud/definition/data/network_ipam_passthrough.yml under ACE. 44

45 vcenter connection requirement The vcenter must be connected to Helion CloudSystem. To connect a vcenter to Helion CloudSystem, use the Integrated Tools screen in the Operations Console. For detailed information, see the Integrated tools connectivity and configuration chapter in the HPE Helion CloudSystem 10.0 Update 1 Administrator Guide at NOTE: HPE Synergy Composer does not allow you to remove a vcenter if you provisioned a cluster in the vcenter using HPE Synergy Composer. You must remove the provisioned cluster first, which removes the linkages in the HPE Synergy Composer database. ESXi clusters are automatically removed when the vcenter managing the clusters is removed from the Integrated Tools screen. (You cannot remove ESXi clusters in the UI. There is no Delete action in the Operations Console, and removing the cluster in vcenter without cleaning up Helion CloudSystem and HPE OneView is not sufficient.) ICsp requirements 1. Download the ICsp image from the HPE Software Depot. 2. Set up ICsp and Media Server as documented in the HPE Insight Control Server Provisioning Installation Guide at 3. Download the required operating systems and populate Media Server. 4. Copy an existing build plan for ESXi and name it (for example) cs10-esx build-plan. You can include information after the version, but it must include at least cs10-<hypervisor>-<version>-. Only custom build plans in ICsp are displayed in HPE Synergy Composer. HPE provided/default build plans are not displayed in HPE Synergy Composer. Additionally, ACE limits the number of build plans displayed in HPE Synergy Composer by checking the for "CS10-" in the build plan name. 45

46 Follow instructions in the appendix Create a custom build plan in HPE Insight Control server provisioning in the HPE Helion CloudSystem 10.0 Update 1 Administrator Guide at Ensure that you copy a build plan that is closest to your OS version. For example, do not copy an esx5.1 build plan for creating an esx6.0 build plan. HPE Synergy Composer certificate registration with Helion CloudSystem If you plan on using a self-signed certificate, then you must obtain the HPE Synergy Composer certificate and register it with the Helion CloudSystem certificate manager. 1. Export the HPE Synergy Composer cert as a Base-64 encoded : 2. Add the HPE Synergy Composer certificate to Helion CloudSystem. a. Log in to the Deployer appliance using stack credentials. b. Create the required directories. mkdir -p ~/helion/my_cloud/certs/cs-ace/ sudo chmod 750 -R ~/helion/my_cloud/certs c. Copy the HPE Synergy Composer certificate to ~/helion/my_cloud/certs/cs-ace/ The certificate must have a file extension of.crt. 3. Commit the changes. cd ~/helion git add -A git commit -m "Add HPE OneView certificate" 4. Verify that the changes are valid. cd ~/helion/hos/ansible ansible-playbook -i hosts/localhost config-processor-run.yml ansible-playbook -i hosts/localhost ready-deployment.yml 5. Update the Helion CloudSystem ACE service. cd ~/scratch/ansible/next/hos/ansible ansible-playbook -i hosts/verb_hosts cs-ace-certs-setup.yml 46

47 Provisioning and auto-activating an ESXi compute cluster using ACE Log in to the Helion CloudSystem Operations Console and go to Compute, then Hardware. NOTE: The Operations Console requires that you log in to a new session before creating a cluster. If you were previously logged in, log out and log in again to renew the session token. In the HPE OneView/Synergy Servers tab, click the STATE column to sort servers in the Unprovisioned state. This causes the CREATE CLUSTER button to appear, as shown in the figure below: Click Create Cluster, and the dialog opens. The cluster can be activated as a compute host at the time of creation or it can be activated at a later time. Notice the Auto-Activate ESXi Cluster check box in the example below. If you choose to auto activate the cluster then make sure you specify the cloud data trunk switch info. For detailed information, see the Compute host provisioning of HPE OneView managed servers chapter in the HPE Helion CloudSystem 10.0 Update 1 Administrator Guide at TIP: MP4 video files that show how to connect HPE OneView to Helion CloudSystem and create and activate a cluster in the Operations Console are attached to this PDF. To reveal the files, click the paper clip icon on the left side of the PDF. NOTE: If for any reason activation fails, the cluster will not be deleted or rolled back. You will be able to try activation again. The cluster automatically appears on the Compute Hosts screen in the Operations Console. 47

48 Support for cluster provisioning is UI driven only, from the Operations Console Hardware screen. Deleting and unprovisioning an ESXi compute cluster created by ACE Deleting an ESXi cluster that was created by Helion CloudSystem using the Operations Console Hardware screen is not available. Instead, you can use the CLI to delete the cluster from vcenter and unprovision the servers from HPE OneView. Delete an ESXi cluster using the ACE REST API 1. Log in to the Operations Console, and navigate to the Compute Hosts screen. 2. Verify that the ESXi cluster you want to delete is in the Imported state. (Imported can be deactivated or never activated.) If the cluster state is not Imported, deactivate the cluster before continuing. See the section Deactivating a compute cluster in the in the HPE Helion CloudSystem 10.0 Update 1 Administrator Guide at 48

49 3. Log in to the first Management appliance using stack credentials. 4. Obtain an Auth token: source ~/service.osrc openstack token issue 5. Find the endpoint for the ACE service. openstack endpoint list -service hpe-hardware \ --interface public c URL 6. Remove the vcenter cluster and unprovision the servers in HPE OneView. a. Identify the cluster that you want to remove. curl -H "X-Auth-Token:<Auth_token>" \ <endpoint_for_ace>/clusters python -m json.tool Example curl H "X-Auth-Token:234e0ee08c874ff48cf1d1e4e4aa6def" \ python -m json.tool [ { "cluster_name":"ov4vc-i3s-test-cluster2", "vcenter_host":" ", "ov_cluster_profile_id":"a55352b bd26-6ff0ba87ce5b", "form_factor":"", "id":"09f02ddd-57af-4e35-98c5-509d d_domain-c450", "capability":{ "max_mbps":10000, "ha_enabled":"true", "hypervisor":"esx", "local_storage":[ },...] ], "storage_raid":[ ], "SAN_storage":[ ], "memory_mb":65536, "storage_type":[ ], "drs_enabled":"true", "GPU":"No", "model":"synergy 480 Gen9", "core_count":32, "drive_bay":"false", "processor_speed_mhz":2100, "processor_type":"intel(r) Xeon(R) CPU E GHz" }, "datacenter_path":"mydc", "vcenter_id":"09f02ddd-57af-4e35-98c5-509d d" 49

50 b. Delete the cluster by calling the ACE RESTful API, specifying the cluster ID as shown in the above example. curl -H "X-Auth-Token: <Auth_token>" -X DELETE \ <endpoint_for_ace>/clusters/{id} python -m json.tool Example curl -H "X-Auth-Token:b650eb ddb9eccf2a7fdf33ad" -X "DELETE" \ python -m json.tool { "locationuri": "/tasks/43e92626-df46-11e6-a0d ad2599" } 7. Monitor the progress of the task. curl H X-Auth-Token: <Auth token> X GET \ <endpoint_for_ace>/<locationuri_returned> python m json.tool Example curl -H "X-Auth-Token:b650eb ddb9eccf2a7fdf33ad X GET \ " \ python m json.tool { "txn_id":"43e8fffc-df46-11e6-a0d ad2599", "class_name":"pool_service.model.cluster_task.clusterprofiledeletetask", "utc_crush_start_time":" :25: ", "utc_crush_stop_time":" :25: ", "state":"done", "result":"delete hypervisor cluster profile complete", "percent_complete":100, "type":"deletecluster", "id":"43e92626-df46-11e6-a0d ad2599" } Discover and import RHEL KVM hosts and ESXi clusters as compute hosts Helion CloudSystem automatically discovers hypervisor hosts and allows the administrator to activate them as compute resouces. The hypervisors may have been provisioned manually by the administrator or by using deployment tools (including the Image Streamer when it becomes available). Helion CloudSystem can discover hosts if it can determine the type and identify the CONF IP address or the vcenter clusters. Importing an ESXi cluster The vcenter clusters are automatically discovered by Helion CloudSystem as long as the vcenter is connected to Helion CloudSystem. Discovering CONF IP addresses IP address discovery is used to verify that a provisioned compute host has a CONF network address set on the host. CONF CIDR is set in the installation options file during deployment. The KVM compute host server IP address must have a CONF addres that comes from within the CONF CIDR range. This IP is used to 50

51 determine if the host can be activated by the Helion CloudSystem activation service. The CONF IP must be returned in the ilo blob. IP address discovery is necessary for activation of non-esxi servers. IP addresses are discovered by Helion CloudSystem if the host OS is on a blade that is running ilo4 and has a host OS agent running (Refer to the CloudSystem Admin Guid for details on the KVM AMS agent). The agent can be installed after provisioning. You can verify that the agent is working from the ilo web interface. If the agent is not working, you will see a warning under the System Information similar to: Configuring Block Storage Devices of the 3PAR Storage Systems discovered in the connected HPE Synergy Composer Auto-discover and configure 3PAR storage systems as Block Storage Devices. Once connected to HPE OneView, the ACE service discovers 3PAR storage systems that have been registered in OneView using the OneView console. You can register a 3PAR storage device from the Storage Block Storage Devices screen in the Operations Console. Make sure you select Auto-discover Device from HPE Synergy Composer. 51

52 Figure 23: HPE OneView Storage Systems that have been auto-discovered by Helion CloudSystem Figure 24: Helion CloudSystem Operations Console Block Storage Device registration 52

53 Auto-create host aggregates based on hardware characteristics Helion CloudSystem deploys instances to compute hosts based on the optional availability zone you specify when you launch an instance in the OpenStack user portal. Host aggregates Host aggregates enable the cloud administrator to partition compute deployments into logical groups for load balancing and instance distribution. A host aggregate is a group of hosts with associated metadata. A host can be part of more than one host aggregate. A common use of host aggregates is to provide information for use with the Nova-scheduler, which deploys instances on specific hosts. For example, you might use a host aggregate to group a set of hosts that share specific flavors or images. You can also use host aggregates to separate different classes of hardware or servers on a separate power source. Activating an ESXi or RHEL KVM compute host which are provisioned or discovered by HPE Synergy Composer managed servers will automatically adds metadata to the server. You can create host aggregates using this metadata in the OpenStack user portal. These host aggregates allow you to: Control the hardware on which an instance is provisioned in a heterogeneous server environment with different backing storage. Offer specialized instances in the private cloud and ensure that the backing hardware can meet their needs. Aggregate differentiated hardware and offer it as a separate class of service with a different SLA/QoS. Utilize a different cloud resource tier for different tenants. 53