Skip to main content

Infrastructure

Sharjeel Ahmed Khan
  • Updated

Groups

Overview

Groups in Morpheus define what resources a user has access to. Group access is defined by User Roles. Clouds are added to groups, and a User can only access the Clouds that are in the Groups their Role(s) gives them access to. Resources such as Networks, Datastores, Resources Pools, and Folders have additional Group access settings.

Policies applied to a Group will be enforced on all Instances provisioned or moved into that Group.

Managing Groups

../../_images/group_view.png

To view a Group:

  1. Select the Infrastructure link in the navigation bar

  2. Click the Groups link

  3. Click the Group name to view/modify

Available tabs in group view

Hosts

Lists available hosts in the group and displays power, os, name, type, cloud, ip address, nodes, disc space, memory, and status. You can add a host from this tab panel by clicking Add Host.

Virtual Machines

List all Virtual Machines in the Group.

Bare Metal

List all Bare Metal Hosts added to the Group

Clouds

Lists Clouds added to the Group. Existing Clouds or new Clouds can be added from the Group by clicking Add Cloud.

Policies

Lists and allows creation or management of Policies applied to the Group.

Clouds

Clouds are integrations or connections to public, private, hybrid clouds, or bare metal servers. Clouds can belong to many groups and contain many hosts. The clouds view includes clouds status, statistics, tenant assignment, and provides the option to add, edit, delete new clouds. Morpheus supports most Public Clouds and Private Clouds.

Supported Cloud Types

  • Alibaba Cloud

  • Amazon

  • Azure (Public)

  • Azure Stack (Private)

  • Canonical MaaS

  • Cloud Foundry

  • Dell (Cloud type for PXE and manually added Dell EMC Hosts)

  • DigitalOcean

  • Google Cloud

  • HPE (Cloud type for PXE and manually added HPE Hosts)

  • HPE OneView

  • Huawei

  • Hyper-V

  • IBM Cloud

  • IBM Cloud Platform

  • Kubernetes

  • MacStadium

  • Morpheus (Generic Cloud type for PXE/Bare Metal and manually added Hosts)

  • Nutanix

  • Open Telekom Cloud

  • OpenStack

  • Oracle Public Cloud

  • Oracle VM

  • Platform 9

  • SCVMM

  • Supermicro (Cloud type for PXE and manually added Supermicro Hosts)

  • UCS

  • UpCloud

  • vCloud Air (OVH)

  • VMWare ESXi

  • VMware Fusion

  • VMWare on AWS

  • VMware vCenter

  • VMware vCloud Director

  • XenServer

Clusters

Overview

Infrastructure > Clusters is for creating and managing Kubernetes Clusters, Morpheus manager Docker Clusters, KVM Clusters, or Cloud specific Kubernetes services such as EKS, AKS and GKE.

Cluster Types

Name

Description

Provider Type

Kubernetes Cluster

Provisions by default a Kubernetes cluster consisting of 1 Kubernetes Master and 3 Kubernetes Worker nodes. Additional system layouts available including Master clusters. Custom layouts can be created.

Kubernetes

Docker Cluster

Provisions by default a Morpheus controlled Docker Cluster with 1 host. Additional hosts can be added. Custom layouts can be created. Existing Morpheus Docker Hosts are automatically converted to Clusters upon 4.0.0 upgrade.

Docker

EKS Cluster

Amazon EKS (Elastic Kubernetes Service) Clusters

Kubernetes

AKS Cluster

Azure AKS (Azure Kubernets Service) Clusters

Kubernetes

KVM Cluster

Provisions by default a Morpheus controlled KVM Cluster with 1 host. Additional hosts can be added. Custom layouts can be created. Existing Morpheus KVM Hosts are automatically converted to Clusters upon 4.0.0 upgrade.

KVM

KVM/Docker Cluster

Provisions by default a Morpheus controlled Docker, VM and Functions* Cluster with 1 host. Additional hosts can be added.

Docker & KVM

Ext Kubernetes

Brings an existing (brownfield) Kubernetes cluster into Morpheus

Kubernetes

GKE Cluster

Google Cloud GKE (Google Kubernetes Engine) Clusters

Kubernetes

Cluster Permissions

  • Cluster Permissions

    Each Cluster has Group, Tenant and Service Plan access permissions settings (“MORE” > Permissions on the Clusters list page).

  • Namespace Permissions

    Individual Namespaces also have Group, Tenant and Service Plan access permissions settings.

    Kubernetes Clusters

    Requirements

    • Agent installation is required for Master and Worker Nodes. Refer to Morpheus Agent section for additional information.

    • Access to Cloud Front, Image copy access and permissions for System and Uploaded Images used in Cluster Layouts

      Image(s) used in Cluster Layouts must either exist in destination cloud/resource or be able to be copied to destination by Morpheus, typically applicable for non-public clouds. For the initial provision, Morpheus System Images are streamed from Cloud Front through Morpheus to target destination. Subsequent provisions clone the local Image.

    • System Kubernetes Layouts require Master and Worker nodes to access to the following over 443 during K8s install and configuration:

      • Morpheus Appliance url (443)

    Creating Kubernetes Clusters

    Provisions a new Kubernetes Cluster in selected target Cloud using selected Layout.

    System (Morpheus provided) Kubernetes Layouts at time of v6.1.0 release. AKS & GKE Kubernetes versions will dynamically update to the providers supported versions.

    To create a new Kubernetes Cluster:

    1. Navigate to Infrastructure > Clusters

    2. Select + ADD CLUSTER

    3. Select Kubernetes Cluster

    4. Select a Group for the Cluster

    5. Select NEXT.

    Intra-Kubernetes Cluster Port Requirements

    The table below includes port requirements for the machines within the cluster (not for the Morpheus appliance itself). Check that the following ports are open on Control-plane and Worker nodes:

    Control-plane node(s)

    Protocol

    Direction

    Port Range

    Purpose

    Used By

    TCP

    Inbound

    6443

    Kubernetes API Server

    All

    TCP

    Inbound

    6783

    Weaveworks

    		  

    TCP

    Inbound

    2379-2380

    etcd server client API

    kube-apiserver, etcd

    TCP

    Inbound

    10250

    kubelet API

    Self, Control plane

    TCP

    Inbound

    10251

    kube-scheduler

    Self

    TCP

    Inbound

    10252

    kube-controller-manager

    Self
    Worker node(s)

    Protocol

    Direction

    Port Range

    Purpose

    Used By

    TCP

    Inbound

    10250

    kubelet API

    Self, Control plane

    TCP

    Inbound

    30000-32767

    NodePort Services

    All

    Adding Worker Nodes

    1. Navigate to Infrastructure - Clusters

    2. Select v MORE for the target cluster

    3. Select ADD (type) Kubernetes Worker

      NAME

      Name of the Worker Node. Auto=populated with ${cluster.resourceName}-worker-${seq}

      DESCRIPTION

      Description of the Worker Node, displayed in Worker tab on Cluster Detail pages, and on Worker Host Detail page

      CLOUD

      Target Cloud for the Worker Node.

    4. Select NEXT.

    Kubernetes Cluster summary tab contains:

    • More Cluster metadata including Name, Type, Created By, Worker CPU, Worker Memory (used/max), Worker Storage (used/max), Enabled: Yes/No, and Description.

    • Memory chart with total Cluster Free and Used Memory over last 24 hours

    • Storage chart with total Cluster Reserved and Used Storage over last 24 hours

    • CPU chart with total Cluster CPU Utilization over last 24 hours

    • IOPS Chart with total Cluster IOPS over last 24 hours

    • IOPS Chart with total Cluster Network utilization over last 24 hours.

    Docker Clusters

    Provisions a new Docker Cluster managed by Morpheus.

    To create a new Docker Cluster:

    1. Navigate to Infrastructure > Clusters

    2. Select + ADD CLUSTER

    3. Select Docker Cluster

    EKS Clusters

    Provisions a new Elastic Kubernetes Service (EKS) Cluster in target AWS Cloud.

    EKS Cluster provisioning is different than creating a Kubernetes Cluster type in AWS EC2, which creates EC2 instances and configures Kubernetes, outside of EKS.

    GKE Clusters

    Provisions a new Google Kubernetes Engine (GKE) Cluster in target Google Cloud.

    Ensure proper permissions exist for the Google Clouds service account to create, inventory and manage GKE clusters.

    Compute

    ../../_images/infra_compute_header_5.4.3.png

    The Infrastructure > Compute section provides a universal stage for viewing and managing Hosts, Virtual Machines, Containers, Resources, and Bare Metal across Clouds.

    In this section you can:

    • View & Manage and Hosts, Virtual Machines, Containers, Resources, Bare Metal and Hypervisors

    • Add manual Virtual Machines and Bare Metal Hosts

    • Convert Hosts, Virtual Machines and Bare Metal to Managed

    Hosts

    ../../_images/infra_compute_header_hosts_5.3.1.png

    Section Features & Filters RECORD SEARCH CUSTOM VIEWS CSV EXPORT JSON EXPORT PAGING CONFIG

    • Standard Filters: OS TYPE

    • Advanced Filters: STATUS MANAGED SERVER TYPE

    Hosts in Morpheus are Hypervisors and Container hosts that VMs and Containers are hosted on, such as ESXi Hosts and Kubernetes Master and Workers. These hosts are populated from integrated clouds, hosts and clusters provisioned from Morpheus, or manually added hosts.

    Provisioning new hosts takes place in the Infrastructure > Clusters section of Morpheus. For example, provisioning a new Docker cluster in that section will begin the process of creating a Morpheus-managed Docker cluster with one host (by default). Additional hosts and custom layouts can also be created. See the Clusters section of Morpheus docs for more information.

    Virtual Machines

    ../../_images/infra_compute_header_vms_5.3.1.png

    Section Features & Filters RECORD SEARCH CUSTOM VIEWS CSV EXPORT JSON EXPORT PAGING CONFIG

    • Standard Filters: OS TYPE

    • Advanced Filters: STATUS MANAGED SERVER TYPE

    The Virtual Machines tab lists all managed and unmanaged VMs across Morpheus. Managed VMs are either provisioned by Morpheus, or are inventoried/discovered VMs that have been converted to managed. Unmanaged VMs are typically inventoried/discovered VMs from Cloud integrations.

    • Virtual Machine Change Cloud

       

    Containers

    ../../_images/infra_compute_header_containers_5.3.1.png

    Section Features & Filters RECORD SEARCH CUSTOM VIEWS CSV EXPORT JSON EXPORT PAGING CONFIG

    • Standard Filters: CONTAINER TYPE CLOUD

    The containers tab lists all Containers associated with Morpheus Instances accessible to the user. Note additional system level containers from Kubernetes and Docker Clusters are not listed here but are acceessible in Cluster detail secitons.

    Resources

    ../../_images/infra_compute_header_resources_5.3.1.png

    Section Features & Filters RECORD SEARCH CUSTOM VIEWS CSV EXPORT JSON EXPORT PAGING CONFIG

    • Standard Filters: RESOURCE TYPE CLOUD

    Resources represent objects that do not map to VM or Container types in Morpheus, such as IAC resources from Terraform, Cloudformation or ARM Templates like VPC’s, Gateways, Users, Policies, Brokers, API’s, Endpoints, Directories, ACL’s, Routes… well anything really. All resources created from IAC Templates map to iac provider resource types and Morpheus maintains a resource object record from the mapped resource.

    Expand the Resource Types table below to see all Resource types that will be mapped to Resource objects in Morpheus:

    • Resource Types Click to Expand/Hide

       

    Bare Metal

    ../../_images/infra_compute_header_bm_5.3.1.png

    Section Features & Filters RECORD SEARCH CUSTOM VIEWS CSV EXPORT JSON EXPORT PAGING CONFIG

    • Standard Filters: OS TYPE

    • Advanced Filters: STATUS MANAGED SERVER TYPE

    Bare Metal hosts are from discovered, PXE Boot or manually added Bare Metal hosts. Bare Metal hosts that are also Hypervisors will be listed in the Hosts section.

    Networks

    Overview

    The Networks section is for configuring networks across all clouds in Morpheus. Existing networks from Clouds added in Morpheus will auto-populate in the Networks section.

    Networks can be configured for DHCP or Static IP assignment, assigned IP pools, and configured for visibility and account assignment for multi-tenancy usage. Inactive Networks are unavailable for provisioning use. In addition, Morpheus allows administrators to restrict management of Morpheus-created Networks through Role permissions.

    Configuring Networks

    DHCP

    To configure a network for DHCP:

    1. Navigate to Infrastructure > Network > Networks

    2. Search for the target network

    3. Edit the Network by either:

      • Select Actions > Edit

      • Select the Network, then select Edit

    4. In the Network Config modal, set the DHCP flag as Active (default)

    5. Save Changes.

    Static and IP Pools

    To configure a network for Static IP Assignment:

    1. Navigate to Infrastructure > Network > Networks

    2. Search for the target network

    3. Edit the Network by either:

      • Select Actions > Edit

      • Select the Network, then select Edit

    4. In the Network Config modal, add the following:

      • Gateway

      • DNS Primary

      • DNS Secondary

      • CIDR ex 10.10.10.0/22

      • VLAN ID (if necessary)

      • Network Pool * Leave as “choose a pool” for entering a static IP while provisioning * Select a Pool to use a pre-configured Morpheus or IPAM Integration IP Pool

      • The Permissions settings are used for Multi-Tenant resource configuration

        • Leave settings as default if used in a single-tenant environment (only one Tenant in your Morpheus appliance)

        • To share this network across all accounts in a multi-tenant environment, select the Master Tenant and set the Visibility to Public

        • To assign this network to be used by only one account in a multi-tenant environment, select the account and set visibility to Private

      • Active

        • Leave as enabled to use this network

        • Disable the active flag to remove this network from available network options

    5. Save Changes.

    Add Security Group Rule

    1. Navigate to Infrastructure > Network - Security Groups

    2. Click the name of the Security Group you wish to add a rule to.

    3. From the Security Group page click the + Add Rule button.

    4. From the Rule Wizard select the rule type and input source and depending on the type selected protocol and input a port range.

    5. Save Changes

    Edit Security Group rule

    1. Navigate to Infrastructure > Network - Security Groups

    2. Click the name of the Security Group you wish to edit a rule in.

    3. Click the edit icon on the row of the Security Group rule you wish to edit.

    4. Modify information as needed.

    5. Save Changes

    Delete Security Group rule

    1. Navigate to Infrastructure > Network - Security Groups

    2. Click the name of the Security Group you wish to delete a rule from.

    3. Click the delete icon on the row of the Security Group rule you wish to delete.

    Add Cloud Security Group

    To add Cloud Security Group

    1. Navigate to Infrastructure > Clouds

    2. Click the name of the desired cloud to add a Security Group

    3. Click the Networks tab

    4. Within the “Security Groups” section, click on a Security Group to edit its rules

    5. Alternatively, click + ADD SECURITY GROUP to create a new one

    Remove Cloud Security Group

    1. Navigate to Infrastructure > Clouds

    2. Click the name of the cloud to remove the Security Group from.

    3. Click the Security Groups tab.

    4. Click the Edit Security Groups button.

    5. Click the - (Minus) button of the Security Group from the Added Security Groups list to remove.

    6. Save Changes.

    Storage

    Overview

    Infrastructure > Storage is for adding and managing Storage Buckets, File Shares, Volumes, Data Stores and Storage Servers for use with other Services in Morpheus.

    Role Requirements

    There are two Role permissions for the Infrastructure > Storage section: Infrastructure: Storage and Infrastructure: Storage Browser. Infrastructure: Storage give Full, Read or No access to the Infrastructure > Storage sections, while Infrastructure: Storage Browser is specific to Buckets and Files Shares. Full Infrastructure: Storage Browser permissions allows Buckets and Files Shares to be browsed and files and folders to be added, downloaded and deleted from the Buckets and Files Shares. Read Infrastructure: Storage Browser permissions allows Buckets and Files Shares to be browsed only.

    Default Storage

    The default Storage path for Virtual Images, Backups, Deployment Archives, Archive Service, and Archived Snapshots is var/opt/morpheus/morpheus-ui/. Its is recommended to add Storage Buckets and File Shares for these targets in the Infrastructure > Storage section to avoid running out of disk space on the Morpheus Appliance.

    Storage Buckets

    Storage Buckets are for Backup, Archives, Deployment and Virtual Images storage targets. Buckets can be browsed and files and folders can be uploaded, downloaded or deleted from the Bucket section. Retention Policies can be set on Storage Buckets for files to be deleted or backed up to another bucket after a set amount of time.

    Supported Bucket Types

    • Alibaba

    • Amazon S3

    • Azure

    • Google Cloud Storage

    • Openstack Swift

    • Rackspace CDN

     

Related articles

Comments

0 comments

Please sign in to leave a comment.