page-hp-logo-wrapper page-hp-logo page-title HP Cloud OS for Moonshot Install & Configure Your Cloud page-version 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.
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.
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.
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.
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.
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.
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.
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.
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.
Admin Node Admineth0 Network Public Network eth1 eth2 Controller Node Admin Network Nova_Flat Network Public Network Baremetal Host Admin Network Nova_Flat Network IPMI Network review-checklist 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.
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.
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: 1. 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. 2.
8. Verify your password. 9. The Admin Node Login screen is displayed once the installation completes. Enter your username and password. 10. Click CTRL+ALT to regain the control of your cursor. Note: This step is specific to VMware and might not be necessary in your client. 11. Power DOWN the Admin Node Virtual Machine. 12. Edit the Virtual Machine's settings so that it will not boot from the ISO again. Example: 13. Power up the Virtual Machine again.
At this point, HP Cloud OS for Moonshot is installed on the Admin Node. Launch the Operational Dashboard To launch the Operational Dashboard: 1. From a Windows or Linux client that has access to the Admin Node, open a Mozilla Firefox or Google Chrome browser. 2. Make sure the browser has the following IP addresses set as proxy exceptions: 192.*;10.*;localhost;127.0.* 3. In the browser, enter https://192.168.124.10:9000 to launch the Operational Dashboard user interface, which is running on the Admin node.
prerequisite, you can be alerted by e-mail when each operation completes.
d. If necessary, specify the optional Username and Password. 6. After completing the steps above, click Update Prerequisite. 7. Now click Complete Prerequisite to complete this setup for the Cloud Administration Node Internet Access entry. When this prerequisite completes, a timestamp will be displayed in the Last Updated column. Set the External DNS Server To set the external DNS server: 1. On the Operational Dashboard, select the Environment tab > Prerequisites. 2.
Set the Email Notification To set the email notification: 1. On the Operational Dashboard, select the Environment tab > Prerequisites. 2. For the email notification settings, click Edit Prerequisites. 3. Click the Enable Notification checkbox. 4. Set the SMTP Server to an SMTP server that is valid for your network. 5. Set From Address to an applicable email address for your environment. Most likely, you would add your email address as the person responsible for managing the cloud infrastructure. 6.
Network mode: dual. Dual mode means that all the connections have their own interfaces, where VLAN and bridge are off. Logical Interface values: intf0 (admin) intf1 (nova_flat) intf2 (ipmi, public) Physical Interface values: 1Gb (preferred) on 1st port 1Gb (preferred) on 2nd port 1Gb (preferred) on 3rd port In this case, 1Gb (preferred) on 2nd port means a one gigabit network for port 2, as enumerated by default from the server's BIOS or as overridden in the Server Types panel.
Note: You do not have to customize the Admin Network. Introduction Based on the network infrastructure suggested in the "Plan the Infrastructure for a Cloud" section of Important Tasks Before You Install, you must customize the network settings.
Bridge Enabled = False On the VLAN tab, do not change: VLAN Enabled = False VLANID = 300 On the Router tab, in the Router box, enter the Gateway IP address of your Public IP address range. The Router Preference default value is 5 and is sufficient. Note: The Router Preference value indicates the number of hops to reach the destination; the lesser the value, the higher the priority of the network. Edit the Public Address Ranges To edit the public address ranges: 1.
Edit the Nova_Flat Network To edit the Nova_Flat network: 1. On the Operational Dashboard, select the Environment tab > Networks. 2. Click Edit Network for the public Network Type. 3. Click each tab: Network, VLAN, and Router, one by one, to perform the following actions: On the Network tab, specify the Subnet and Netmask of your dedicated public IP address range.
Note: If you enter invalid address ranges, you will get a validation error, which identifies the incorrect address (start or end) for the corresponding network type. You must fix all errors in the Edit Address Ranges dialog and click Update Address Ranges to validate the addresses are correct. Customize the IPMI Network The IPMI network is used for communication between the Baremetal host and the Moonshot Chassis Manager.
4. (Optional) Click Add Address Range to add a set of address range options to the bottom of the Edit Address Ranges dialog box. Each time you click Add Address Range, you add another set of address range options to be filled in. Note: Provide the IP address range corresponding to the network address. 5. Click Update Address Ranges to save your changes.
failure during this part of the process requires rebuilding the Admin Node through the bootable ISO. 5. (Optional) Click Show Install Log to view the install activity in the /var/log/install.log, which appears on the bottom of the window. 6. (Optional) Click Refresh to monitor the install progress. 7. After the Admin Node is installed, the screen will display the timestamp in the Install Complete column. The Complete Install button is replaced by the Continue... button. 8. Click Continue...
Once the Cloud Controller and the Baremetal Host finish booting up, the nodes display in the table with their alias names set to their MAC address (address of the NIC associated with the Admin network). Each node will be in a Not Allocated state. 4. Select Edit Node for each node to rename the MAC address in the Alias column to a more meaningful name such as cloudcontroller, compute1, compute2. Note: The node name can only be letters (capitalization is allowed) and numbers with no spaces.
Select the Attributes tab to specify property values required to create a Cloud. The following attributes are displayed. Retain the default values. Cloud Type — By default Physical is displayed. Note: Physical implies that Baremetal provisioning is supported. Keystone Signing — Set the Keystone Signing method based upon the authentication scheme: UUID or PKI. PKI (the default setting) is a large token that contains token information such as the user ID and user roles.
Proceed to the next topic, Create Compute Regions. ‹ PREV | ^ UP | NEXT › Create Compute Regions Once the Cloud setup is complete, the Cloud displays in an active state. You can now create one or more regions in the cloud. There are multiple use cases where you would prefer to have separate compute regions, such as: To accommodate a heterogeneous set of hardware configured for different workloads. To distribute the workload across regions to get better response times.
Note: This process takes apoproximately 10 minutes to complete. Next Step Proceed to the next topic, Enter or Update your License Key. ‹ PREV | ^ UP | NEXT › Enter or Update your License Key The HP Cloud OS for Moonshot dashboards require a common, date-based HP Cloud OS for Moonshot license. When you purchase HP Cloud OS for Moonshot, there are two SKUs, for a one-year or three-year license.
3. In the licensing information, note the Instance ID value for your cloud. The HP Support representative will need this value when your new license is generated. 4. Now enter the license key (alphanumeric characters) given to you by the HP Support representative. Next Step Proceed to the next topic, which includes options steps to Customize User Settings. ‹ PREV | ^ UP | NEXT › Customize User Settings You can optionally customize the following user settings to suit your requirements. 1.
This topic explains how to obtain patches and other relevant functionality from the HP Cloud OS Distribution Network (CODN). Note: The same Updates and Extensions functionality is available in the Administration Dashboard, which is the new dashboard that you will use. For introductory information, you can read this topic. It is presented in the Operational Dashboard context. However you can perform the steps later, if you want, in the Administration Dashboard.
Verify the patch installation. Once the job is in its completed state, reopen the patched proposal in the Installation Dashboard. Click Edit. For example, you should see the name of the hot fix, such as "Token-Expiration Hotfix Enabled." To apply the hot fix in your cloud, set its attribute Boolean value to true, click Apply and then Save. New patches may be available periodically. When you use the Administration Dashboard, be sure to revisit the Updates and Extensions panel on a regular basis.
View the Provided Flavor Launch an Instance from an Image Next Steps How to Access the Administration Dashboard You can access the Administration Dashboard in one of two ways: Open a Google Chrome or Firefox browser. Enter the URL of your Cloud Controller node's public IP address. Login with the Admin account's username and password that you specified previously in the Operational Dashboard on the Create Cloud > Attributes dialog.
7. From the left panel, select the Access and Security option again. The keypair is displayed on the page. Upload Cloud Images An image is required to install an Operating System in an instance. To upload cloud images in the Administration Dashboard: 1. Click any of the tabs: Cloud, Region, or Project. The selected tab displays options in the left panel. 2. If you selected the Project tab, select Infrastructure > Images. If you started on the Cloud or Region tab, click Images.
To create an Amazon RAMdisk Image (ARI) 1. 2. 3. 4. 5. 6. 7. 8. 9. 10. 11. Click Create Image to open the Create An Image dialog box. In the Name box, enter a name for the image. (Optional) In the Description box, enter a description for the image. From the Format drop-down list, select ARI. From the Image Source drop-down list, do one of the following: Select Image Location from the drop-down list. In the Image Location box, enter the HTTP URL from which to load the ARI image.
9. 10. 11. 12. 13. the above specification. In the Minimum Disk box, specify a minimum size required to boot the image. If no input is entered, the minimum value defaults to 0. In the Minimum Ram box, specify a minimum size required to boot the image. If no input is entered, the minimum value defaults to 0. Click the checkbox next to Public. This will make the image visible to all users. Click the checkbox next to Protected. This makes the image read-only. Click Create Image.
has been added: Add a Chassis This is a key task during your post-install of HP Cloud OS for Moonshot: adding one or more chassis (one at a time) to the cloud. 1. Click the + Add icon to display the Enter Chassis Details dialog box. 2. In the Display Name box, enter the display name for the chassis. The name should have a minimum of 4 characters. The name should start with an alphabet and may be followed by numbers or an underscore (_).
Warning - When one or more of the cartridges are not in good condition Failed - When the discovery process fails Optimal- When the chassis is discovered and is in good state Once the operation is successful, the Moonshot Chassis is graphically represented on the screen. The information is displayed regarding the cartridges, nodes, and the state of the chassis.
Chassis Snapshot section The Chassis Snapshot visually represents the chassis with all the cartridges and nodes along with power states of the cartridges. Note: A chassis has one or more cartridges, and each cartridge can include one or more nodes. The following table displays a list of icons and their description. These icons are displayed next to the chassis on the right panel. It also displays the complete state of the chassis. Icon Description Displays the chassis UUID. Displays the chassis name.
Displays the power supply status. Displays the temperature status. Also, you can click the following icon to force a refresh of the Chassis status. Note: The Force Refresh option will take a minute to complete. During this time you cannot perform any action on the cartridge and the nodes. Table Views section The Table views section displays the details of all the cartridges and the nodes in a tabular form. The table displays two views - Cartridges View and the Nodes View.
Power Status Instance UUID The Node View displays two new tabs: Workload and Configuration. To view the workload and configuration details of a particular node: Select a node from the table for which you want to view the workload or configuration details. Click the Workload Tab to view the workload details of the selected node. Click the Configuration Tab to view the configuration details of selected node. Notes about the Table Views 1.
Flavor name Server Cartridge Type CPUs: Configuration 2. CPU Architecture: x86_64. hp_moonshot_server HP ProLiant Moonshot Server Cartridge RAM MBs: 8192. Root Disk GBs: 450. hp_moonshot_m300 HP ProLiant m300 Server Cartridge CPUs: 8. CPU Architecture: x86_64. RAM MBs: 32768. Root Disk GBs: 450. As part of your initial post-deployment steps, you do not need to create new flavors to verify that your cloud is operating properly. If you're curious, to see how the flavors are defined already: 1.
Click Launch next to the image listed in the table. 4. A Launch Instance dialog box displays with four tabs: Details, Access & Security, Networking, and Post-Creation. By default, Details is the active tab. 5. On the Details tab: From the Image drop-down list, select the image. In the Instance Name box, enter a name for the instance. From the Flavor drop-down list, select the flavor. In this case, it should be hp_moonshot_server or hp_moonshot_m300, depending on your cartridge server type.
