Link Search Menu Expand Document

Orchestrator in IaaS - Deploy

If you are installing Orchestrator in IaaS, follow the steps in this topic.

You can deploy Orchestrator as a Virtual Machine (VM) in a Virtual Private Cloud (VPC) in Amazon Web Services (AWS), Azure, or Google Cloud. It is available on the AWS Marketplace, Azure Marketplace, and Google Cloud Marketplace as a Bring Your Own License (BYOL) VM instance. This topic illustrates how to deploy an Orchestrator instance from a cloud service.

Prerequisites

Prior to deployment, you must have the following:

  • An existing account for the cloud service.

  • Permission to deploy a VM from the cloud service into a VPC (for Amazon Web Services and Google Cloud) or VNET (for Azure).

NOTE: If you have an existing VPC, be sure that it can accommodate the Orchestrator deployment. Firewall rules applied to the VPC must allow inbound and outbound HTTPS traffic to and from the internet. If firewall rules are not created to allow inbound and outbound HTTPS traffic, you can create a firewall rule specifically for the Orchestrator VM while deploying it from AWS or the Google Cloud Compute Engine.

Deployment Overview

Deploying Orchestrator in the cloud is a two-step process.

Step 1: Deploy Orchestrator in the cloud service. See the appropriate section below:

Step 2: Log in and upgrade Orchestrator.

Deploy Orchestrator in Amazon Web Services

To deploy Orchestrator in Amazon Web Services:

  1. To locate the Orchestrator AMI on the AWS Marketplace, log into your AWS account, click Services, and select EC2 under Compute.

    The EC2 Dashboard appears.

  2. Click Launch Instance.

  3. Click the AWS Marketplace link, and type silver peak

    The Silver Peak product listings appear.

  4. Select Silver Peak Unity Orchestrator for AWS.

    The Choose an Amazon Machine Image (AMI) page opens.

  5. Click Continue.

    The Choose an Instance Type page opens.

    Refer to the Orchestrator Host System Requirements to find the recommended CPU, RAM, and storage requirements for Orchestrator based on the number of EdgeConnect devices that you are planning to manage from Orchestrator.

  6. After selecting the instance type, click Next: Configure Instance Details.

    The Configure Instance Details page opens.

  7. Refer to the table below to enter settings for each configuration option.

    VPC Configuration Settings
    Number of instances 1
    Purchasing option Keep the default setting.
    Network Select the VPC into which you want to deploy the Orchestrator.
    Subnet Select a subnet.
    Auto-assign Public IP If you are deploying Orchestrator for a short period of time, for instance, for a Proof of Concept, you can select Enable, which assigns a dynamic public IP to the Orchestrator. If you plan to use Orchestrator in a production environment, it is recommended to assign an Elastic (static) IP address to Orchestrator.
    Placement group Keep the default setting.
    IAM role Select an appropriate IAM role. If no IAM roles are created, select None.
    Shutdown behavior Stop
    Capacity Reservation Optional
    Enable termination protection Optional
    Monitoring Optional
    EBS-optimized instance Launch as EBS-optimized instance.
    Tenancy Shared – Run a shared hardware instance.
    Elastic Inference Keep the default setting.
  8. Click Next: Add Storage.

    The Add Storage page opens. Keep the default settings.

  9. Click Next: Add Tags.

    The Add Tag page opens. Optionally, you may assign a tag to the Orchestrator.

  10. Click Next: Configure Security Group.

    The Configure Security Group page opens.

  11. Create a new Security Group or assign an existing Security Group. You should enable inbound TCP port 22 and TCP port 443 from your network to access the Orchestrator. Similarly, allow all outbound traffic.

  12. Click Review and Launch.

    The Review Instance Launch page opens

  13. Click Launch.

    The Select an existing keypair or create a new keypair window opens. As the name suggests, you may select an existing keypair or create a new one.

  14. Select Assign a keypair.

  15. Click Launch instance.

  16. On the Launch Status page, click the instance (AMI) ID.

    The EC2 page opens.

  17. If you assigned a dynamic public IP address while deploying Orchestrator, you will see it on the Description tab of the VM. If you did not assign a public IP address while deploying Orchestrator, click the Elastic IPs page, allocate a new static IP address, and assign it to Orchestrator.

You have now deployed your Orchestrator.

Deploy Orchestrator in Azure

To deploy Orchestrator in Azure:

  1. Log in to the Azure portal, navigate to the Resource Groups page, and open your resource group.

    Guide example: SP-Tech

  2. Click + Add in the menu bar at the top of the page.

    The Azure Marketplace page opens.

  3. In the Search the Marketplace text box, begin typing silver peak, and select Silver Peak Unity Orchestrator after the text box auto-populates.

    The Silver Peak Unity Orchestrator page opens.

  4. Click Create.

    The Create a virtual machine page opens.

  5. Verify that Basics is selected in the menu bar and enter the following settings:

    • Subscription: (drop-down) Select your subscription type.

      Guide example: Pay-As-You-Go

    • Resource Group: (drop-down) Enter an existing resource group (data field), or click Create new (below the data field) and create a new group.

      Guide example: SP-Tech

    • Virtual machine name: Enter a descriptive name for Orchestrator.

      Guide example: orch-Device-1

    • Region: (drop-down) Select the Azure region where you want to deploy your Orchestrator.

      Guide example: (US) West US

    • Availability options: (drop-down) Select No infrastructure redundancy required.

    • Image: (drop-down) Select a Silver Peak Unity Orchestrator version option.

    • Azure Spot instance: (radio button) Select No.

    • Size: (drop-down) Select a VM size.

      Refer to the Orchestrator Host System Requirements to find the recommended CPU, RAM, and storage requirements for Orchestrator based on the number of EdgeConnect devices that you are planning to manage from Orchestrator.

    • Authentication type: (radio button) Select SSH public key.

    • Username: Enter the username that you will use for the initial SSH session.

      Guide example: user-1

    • SSH public key source: Select generate a new key pair or Use an existing key.

      Guide example: Use existing public key

    • SSH public key: Either enter a name for the new key (generate a new key pair) or enter the public key of the existing key pair.

      Guide example: See the figure below.

      img

  6. Click Next: Disks to open the Disks page and enter the following settings:

    • OS disk type: (drop-down) Select Standard HDD or Premium SSD.

      Guide example: Premium SSD

    • Encryption type: Select (Default) Encryption at-rest with a platform-managed key.

    • Data Disks: Create and attach new disks as required.

      Guide example: No additional disks are created.

  7. Click Next: Networking to open the Networking page and enter the following settings:

    • Virtual Network: (drop-down) Select a VNet from the list.

      Guide example: SP-Tech-vnet

    • Subnet: (drop-down) Select a subnet to deploy the MGMT0 interface.

      Guide example: default (10.0.0.0/24)

    • Public IP: (drop-down) Click Create new (below the data field) to open the Create public IP address panel and enter the following to create a static public IP address.

      1. Name: Enter an IP address name.

        Guide example: tech-1-ip

      2. SKU: (radio button) Select Basic.

      3. Assignment: (radio button) Select Static.

      4. Click OK (bottom of panel).

    • NIC network security group: (radio button) Select Advanced (default setting).

    • Configure network security group: (drop-down) Retain default group.

      The default Network Security Group assigned to the instance allows inbound traffic from TCP port 22, TCP port 443, and all outbound traffic.

      IMPORTANT: It is highly recommended that you update the default Network Security Group and allow only inbound traffic from your network.

    • Accelerated networking: (radio button) Select Off.

    • Place this virtual machine behind an existing load balancing solution?: (radio button) Select No.

  8. Click Next: Management to open the Management page and enter the following settings:

    • Boot Diagnostics: Select On.

    • OS guest diagnostics: Select Off.

    • Diagnostics storage account: Select a diagnostic storage account or create a new one.

    • System assigned managed identity: Select Off.

    • Login with AAD credentials: Optional.

      Some images do not support this option.

    • Enable auto-shutdown: Select Off.

  9. Click Next: Advanced to open the Advanced page and retain the default settings.

  10. Click Next: Tags to open the Tags page. Assign tags (optional) to Orchestrator as desired.

  11. Click Next: Review + Create.

  12. Review VM details, and click Create.

    The Azure Dashboard appears as Orchestrator begins to deploy. To view the progress of the deployment, go to your Resource Group and click the Orchestrator VM.

You have now deployed your Orchestrator.

Deploy Orchestrator in Google Cloud

To deploy Orchestrator in Google Cloud:

  1. Log in to the Google Cloud console (dashboard) and select the project where you want to deploy Orchestrator.

  2. Click the navigation menu at the top left of the page, then click Compute Engine under COMPUTE.

  3. Click VM instances.

  4. Click CREATE INSTANCE at the top of the VM instances page.

    The Create an instance page opens.

  5. Click Marketplace and begin typing silver peak in the search menu.

  6. Click Silver Peak Unity Orchestrator when it appears.

  7. Click Launch.

  8. Configure the following options in the virtual machine deployment page:

    • Deployment name: Select a name for Orchestrator.

    • Zone: Select the zone of the VPC that Orchestrator will be deployed.

    • Machine type: Select a machine type for the Orchestrator. Refer to the Orchestrator Host System Requirements document to find the recommended CPU, RAM, and storage requirements of Orchestrator based on the number of EdgeConnect devices that you are planning to manage from Orchestrator.

    • Boot Disk:

      • Boot disk type: Select SSD Persistent Disk.

      • Boot disk size in GB: 1023.

    • Networking:

      • Network interfaces:

        1. Click Edit to open the Network interface page.

        2. For Network, select the VPC where Orchestrator will be deployed.

        3. For Subnetwork, select the subnet.

        4. For External IP, select Ephemeral.

        5. Click Done.

    • Firewall: Select the Allow HTTPS traffic from the Internet check box if you don’t have a firewall rule on the VPC subnet to allow inbound HTTPS traffic to Orchestrator.

    • Source IP ranges for HTTPS traffic: Enter the source IP address of your network.

  9. Click Deploy.

    The Deployment Manager page opens.

  10. In the details window on the right, click the instance name link to view the Orchestrator VM being deployed on the Compute Engine page.

You have now deployed the Orchestrator VM.


Back to top

© Copyright 2024 Hewlett Packard Enterprise Development LP. The information contained herein is subject to change without notice. The only warranties for Hewlett Packard Enterprise products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. Hewlett Packard Enterprise shall not be liable for technical or editorial errors or omissions contained herein. Aruba Networks and the Aruba logo are registered trademarks of Aruba Networks, Inc. Third-party trademarks mentioned are the property of their respective owners. To view the end-user software agreement, go to HPE Aruba Networking EULA.

Open Source Code:

Hewlett Packard Enterprise Company
Attn: General Counsel
WW Corporate Headquarters
1701 E Mossy Oaks Rd Spring, TX 77389
United States of America