weekly refresh: 2026-05-22T19:31Z — 1599 content change(s) across 7 bundle(s)
1599 content change(s) across 7 bundle(s)
1599 sidecar metadata update(s)
7 new bundle(s) added
Bundles with content changes:
morpheus_quickspecs (NEW): 1 page(s)
- a50009231enw
morpheus_release_notes_8_1_0 (NEW): 1 page(s)
- sd00007496en_us
morpheus_release_notes_8_1_1 (NEW): 1 page(s)
- sd00007610en_us
morpheus_release_notes_8_1_2 (NEW): 1 page(s)
- sd00007733en_us
morpheus_user_manual_8_1_0 (NEW): 531 page(s)
- GUID-008B6CB0-CC99-4E40-89CE-2EA5D3389D8F
- GUID-00CE7A1B-7CBC-4227-B285-2E8E4FFC73B1
- GUID-00E2C383-D602-4EAD-BE7F-64E69F5DD5C1
- GUID-014CB518-CCE4-449A-9BCC-241FF8FEA3C5
- GUID-016909A4-5AF9-4DE7-8088-DB62BBC6B00C
... and 526 more
morpheus_user_manual_8_1_1 (NEW): 532 page(s)
- GUID-008B6CB0-CC99-4E40-89CE-2EA5D3389D8F
- GUID-00CE7A1B-7CBC-4227-B285-2E8E4FFC73B1
- GUID-00E2C383-D602-4EAD-BE7F-64E69F5DD5C1
- GUID-014CB518-CCE4-449A-9BCC-241FF8FEA3C5
- GUID-016909A4-5AF9-4DE7-8088-DB62BBC6B00C
... and 527 more
morpheus_user_manual_8_1_2 (NEW): 532 page(s)
- GUID-008B6CB0-CC99-4E40-89CE-2EA5D3389D8F
- GUID-00CE7A1B-7CBC-4227-B285-2E8E4FFC73B1
- GUID-00E2C383-D602-4EAD-BE7F-64E69F5DD5C1
- GUID-014CB518-CCE4-449A-9BCC-241FF8FEA3C5
- GUID-016909A4-5AF9-4DE7-8088-DB62BBC6B00C
... and 527 more
This commit is contained in:
hvm-docs-refresh
@@ -0,0 +1,12 @@
|
||||
{
|
||||
"bundle_id": "morpheus_quickspecs",
|
||||
"page_id": "a50009231enw",
|
||||
"title": "HPE Morpheus Enterprise Software QuickSpecs",
|
||||
"ordinal": 1,
|
||||
"parent_title": null,
|
||||
"doc_id": "a50009231enw",
|
||||
"version": "v1",
|
||||
"product": "QuickSpecs",
|
||||
"source_url": "https://www.hpe.com/psnow/doc/a50009231enw",
|
||||
"fetched_from": "live"
|
||||
}
|
||||
@@ -0,0 +1,111 @@
|
||||
**In an era of digital transformation, speed and agility of application modernization is key to success.**
|
||||
|
||||
Unfortunately, it can take IT weeks to deliver new application stacks when requested because of manual hand-offs across a fragmented set of ‘software-definable’ technologies on-premises. This inefficiency has led internal IT consumers to often bypass IT in favor of public cloud application services which raises cloud costs and opens security holes.
|
||||
|
||||
Born to provide simple and consistent provisioning of VMs, Containers, and Applications into any private or public cloud, HPE Morpheus Enterprise Software enables IT to become a true internal service provider for the business. It brings the cloud experience on-premises, extends governance to the public clouds, and bridges the gaps between technology, people, and process.
|
||||
|
||||
### Overview
|
||||
|
||||
HPE Morpheus Enterprise Software was uniquely engineered for platform engineering; it enables different enterprise teams to each get what they need from hybrid cloud management. IT and platform teams can quickly integrate tooling and dependencies without scripting, standardize cloud management, simplify server builds, and automate lifecycle tasks. Infrastructure and security teams can connect third-party identity providers, map groups & roles, establish role-based access controls, enforce policies, manage and rotate secrets, and more. Development teams, data analytics professionals, and other IT users, get on-demand provisioning of application services and stacks consistently across runtimes and clouds via GUI, ITSM plugin, IaC provider, full API/CLI, and CI/CD pipelines. Lastly, Managed Service Providers can use HPE Morpheus Enterprise as a white-labeled and multi-tenant portal to provide services and meter usage to be used in customer billing.
|
||||
|
||||
|
||||
|
||||
### Standard Features
|
||||
|
||||
#### Features
|
||||
|
||||
**Enable Self-service Provisioning of any Workload into any Cloud On-demand**
|
||||
|
||||
- − Integrate Hypervisors, Public Clouds, Kubernetes Clusters, IP address management, DNS, Load Balancers, IT Service Management, Backup Tools, Automation Tasks, and more into framework to automate workload deployment.
|
||||
- − Turn existing 'brownfield' hypervisors into a true private cloud by easily connecting to VMware, Nutanix, Microsoft, Oracle, OpenStack, etc. Unify public cloud access by connecting to AWS, Azure, GCP, OCI, etc.
|
||||
- − Eliminate manual handoffs and orchestrate the tools and dependencies for catalog-based deployment of Bare Metal (BMaaS), VMs (IaaS / VMaaS), containers (CaaS), App Services (PaaS), multi-tier application stacks, and public cloud services.
|
||||
- − Associate automation tasks to the lifecycle phases of workloads so IT processes can be consistently applied at startup, shutdown, reconfigure, teardown, etc. Task support includes Ansible, Chef, Salt, PowerShell, Bash, and more.
|
||||
- − Trigger provisioning activities through your interface of choice including a simple self-service catalog GUI, powerful advanced GUI interface, full fidelity API/CLI for integration into CI/CD pipelines, or leverage ITSM tools such as ServiceNow®.
|
||||
|
||||
**Provision Built-in KVM and Kubernetes Runtime Options for Flexibility and Choice**
|
||||
|
||||
- − Deploy and manage HPE's HVM hypervisor clusters. Based on KVM, this built-in runtime includes external storage support, VM live migration, storage live migration, data protection, and other features to host virtualized workloads.
|
||||
- − Use the built-in CNCF certified Kubernetes Service (HKS) to deploy K8s on any attached cloud. Includes open-source components such as Prometheus, Grafana, Calico and others to quickly get started with containers.
|
||||
- − Create custom K8s cluster layouts to deploy distributions such as Rancher’s K3s, Red Hat OpenShift, or vanilla upstream K8s as well as enable provisioning of cloud-managed Kubernetes clusters like AWS EKS, Azure AKS and Google GKE.
|
||||
- − Quickly view status and health of VME and Kubernetes clusters across your environment to simplify operations, view cluster metrics and logs, and provide lifecycle management of HPE native VME and HKS cluster types.
|
||||
|
||||
**Set Governance Guardrails so Users and Teams have a Paved Road to Hybrid Cloud**
|
||||
|
||||
- − Govern tenants, teams, and users by connecting to corporate identity providers and using SSO. Map groups and users into fine-grained role-based access control (RBAC) guardrails with dozens of policies for infrastructure and lifecycle.
|
||||
- − Improve your overall security posture by ensuring consistent golden template use, embedding security agents at provision time, locking down access, rotating credentials, managing secrets, and auditing all activity.
|
||||
- − Utilize multi-tenancy to fully segregate which teams and users have access to different cloud environments. Share hypervisors and clouds across multiple tenants or let tenants have their own individual cloud accounts.
|
||||
|
||||
**Embrace FinOps and Lower Cost with Cross Cloud Visibility and Insight**
|
||||
|
||||
- − Automatically discover and inventory existing instances and objects across all private and public clouds, run analytics to find problems and implement guidance recommendations for cloud cost saving.
|
||||
- − Go beyond reporting to fix cost issues at their source. Set budget guardrails and power schedules, limit clouds and plans by role, plus provide cloud cost comparisons at provision time for end-user empowerment.
|
||||
- − Centralize cost and usage data across on-premises and public cloud. Track costs and usage for every tenant, user, group, tag, app, cloud, and more for private infrastructure and public cloud including public cloud invoice synchronization.
|
||||
|
||||
For a complete set of up-to-date technical information and integration guides please visit the:
|
||||
|
||||
[HPE Morpheus Enterprise documentation](https://docs.morpheusdata.com/en/latest) site.
|
||||
|
||||
### Configuration Information
|
||||
|
||||
#### Architecture and Requirements
|
||||
|
||||
HPE Morpheus Enterprise is a software-based appliance installation capable of orchestrating many clouds and hypervisors. Before an installation is started it is important to understand some of the base requirements. HPE Morpheus Enterprise provides a wide array of options when it comes to deployment architectures. It can start as a simple one machine instance where all services run on the same machine, or it can be split off into individual services per machine and configured in a high availability configuration, either in the same region or cross-region.
|
||||
|
||||
There are four primary tiers of services represented within the Morpheus appliance. They are the Application Tier, Transactional Database Tier, Non-Transactional Database Tier, and Message Tier. Each of these tiers have their own recommendations for High availability deployments that we need to cover.
|
||||
|
||||
**Configuration options:**
|
||||
|
||||
- − Single Host (All-In-One/default): All tiers running on a single host. The reconfigure process installs all required services. This is the default configuration.
|
||||
- − Single Hosts with Distributed Service(s): Transactional Database, Non-Transactional Database, and/or Message tiers are externalized, with the remaining services on a single host.
|
||||
- − Clustered Hosts with Distributed Transactional Database (3-Node HA): Application, Message and Non-Transactional tiers are installed and clustered on three or more hosts, with all three hosts pointing to externalized database tier.
|
||||
- − App Host(s) with Distributed Services (Full HA): Application tier is installed on one or more hosts. All UI hosts point to externalized Transactional Database, Non-Transactional Database, and Message Tiers.
|
||||
|
||||
Additional configuration detail available at the [HPE Morpheus Enterprise documentation](https://docs.morpheusdata.com/en/latest/getting_started/getting_started.html) site.
|
||||
|
||||
#### Product, Services, and Licensing Considerations
|
||||
|
||||
Hewlett Packard Enterprise is making the following HPE Morpheus Enterprise Software SKUs available as term-based licensed software, not a fully managed SaaS deployment. This makes HPE Morpheus Enterprise an excellent choice for highly regulated environments with tight security guidelines.
|
||||
|
||||
HPE Morpheus Enterprise Software SKUs are licensed per physical CPU socket for any connected on-premises cloud including Bare Metal (BMaaS) servers, hypervisor hosts, and Kubernetes worker nodes.
|
||||
|
||||
HPE Morpheus Enterprise Software can also be used to provision workloads into public clouds like AWS, Azure, GCP, and more; public cloud workloads are factored at a 15 workload to 1 socket ratio. For example, 15 AWS EC2 instances would consume 1 socket license.
|
||||
|
||||
New installations require installation and configuration services provided by HPE. All software licenses for HPE Morpheus Enterprise include 24x7 support in the form of HPE Tech Care Essentials as part of the license cost. HPE also highly recommends that customers attend the HPE Morpheus Enterprise – Administration training class to fully take advantage of the capabilities of the platform.
|
||||
|
||||
You can upgrade from HPE Morpheus VM Essentials to the full capabilities of HPE Morpheus Enterprise using the upgrade options below. Upgrade licenses can be applied to an existing installation however you should consult with HPE on any suggested architectural considerations. You can also apply additional licenses to an existing installation and ‘stack’ licenses with differing term lengths.
|
||||
|
||||
| | |
|
||||
| --- | --- |
|
||||
| HPE Morpheus Enterprise Software | |
|
||||
| **Description** | **SKU** |
|
||||
| HPE Morpheus Enterprise Software per Socket (15 WLE) 1-year 24x7 Support New Install E-LTU | S6E64AAE |
|
||||
| HPE Morpheus Enterprise Software per Socket (15 WLE) 3-year 24x7 Support New Install E-LTU | S6E66AAE |
|
||||
| HPE Morpheus Enterprise Software per Socket (15 WLE) 5-year 24x7 Support New Install E-LTU | S6E68AAE |
|
||||
| HPE Morpheus Enterprise Software per Socket (15 WLE) 1-year 24x7 Support Extension/Renewal E-LTU | S6E59AAE |
|
||||
| HPE Morpheus Enterprise Software per Socket (15 WLE) 3-year 24x7 Support Extension/Renewal E-LTU | S6E61AAE |
|
||||
| HPE Morpheus Enterprise Software per Socket (15 WLE) 5-year 24x7 Support Extension/Renewal E-LTU | S6E63AAE |
|
||||
| HPE Morpheus VM Essentials to Morpheus Enterprise Software Upgrade 1-year 24x7 Support E-LTU | S6E69AAE |
|
||||
| HPE Morpheus VM Essentials to Morpheus Enterprise Software Upgrade 3-year 24x7 Support E-LTU | S6E71AAE |
|
||||
| HPE Morpheus VM Essentials to Morpheus Enterprise Software Upgrade 5-year 24x7 Support E-LTU | S6E73AAE |
|
||||
| **HPE Morpheus Services** | |
|
||||
| **Description** | **SKU** |
|
||||
| HPE Morpheus Software Installation - standard | HA124A1#V38 |
|
||||
| HPE Morpheus Software High Availability - enhancement | HA124A1#V39 |
|
||||
| HPE Morpheus Enterprise SW Quickstrt SVC | H46SBA1 |
|
||||
| **Notes:** For fully advanced services and custom statements of work, please work with the HPE Advisory and Professional Services (HPE A&PS) team. HPE A&PS have a full set of consulting and services focused on HPE Morpheus Software for multi-cloud management. <https://www.hpe.com/psnow/doc/a00141555enw> | |
|
||||
| **HPE Morpheus Training and Education** | |
|
||||
| **Description** | **SKU** |
|
||||
| HPE Morpheus Software – Administration | H45ZD |
|
||||
| HPE Morpheus Software - Automation & Advanced Provisioning | H45ZC |
|
||||
| HPE Morpheus Software - Advanced Troubleshooting | H45YY |
|
||||
| HPE Morpheus Software - Installation | H45YZ |
|
||||
|
||||
### Summary of Changes
|
||||
|
||||
| **Date** | **Version History** | **Action** | **Description of Change** |
|
||||
| --- | --- | --- | --- |
|
||||
| 16-Mar-2026 | [Version 3](https://www.hpe.com/psnow/doc/a50009231enw.pdf?ver=3) | Changed | New product functionality and SKU information have been added. |
|
||||
| 22-Sep-2025 | [Version 2](https://www.hpe.com/psnow/doc/a50009231enw.pdf?ver=2) | Changed | HPE Rebranding applied |
|
||||
| 05-May-2025 | [Version 1](https://www.hpe.com/psnow/doc/a50009231enw.pdf?ver=1) | New | New QuickSpecs |
|
||||
|
||||
[Have feedback on QuickSpecs? We’re listening](https://hpeexperience.questionpro.com/t/mLrbZLrb?Inform=BotQuickSpecsa50009231enw)
|
||||
@@ -0,0 +1,26 @@
|
||||
{
|
||||
"bundle_id": "morpheus_release_notes_8_1_0",
|
||||
"page_id": "sd00007496en_us",
|
||||
"title": "v8.1.0 Release Notes",
|
||||
"ordinal": 1,
|
||||
"parent_title": null,
|
||||
"doc_id": "sd00007496en_us",
|
||||
"version": "8.1.0",
|
||||
"product": "Release Notes",
|
||||
"source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007496en_us",
|
||||
"topic_cluster": {
|
||||
"clustering_title": "v8.1.0 Release Notes",
|
||||
"clustered_topics": [
|
||||
{
|
||||
"bundle_id": "morpheus_release_notes_8_1_1",
|
||||
"page_id": "sd00007610en_us",
|
||||
"clustering_title": "v8.1.1 Release Notes"
|
||||
},
|
||||
{
|
||||
"bundle_id": "morpheus_release_notes_8_1_2",
|
||||
"page_id": "sd00007733en_us",
|
||||
"clustering_title": "v8.1.2 Release Notes"
|
||||
}
|
||||
]
|
||||
}
|
||||
}
|
||||
@@ -0,0 +1,75 @@
|
||||
# v8.1.0 Release Notes
|
||||
|
||||
# v8.1.0 LTS Release Notes
|
||||
|
||||
- Compatible Plugin API version: 1.3.0
|
||||
- Compatible HPE Morpheus Enterprise Software Worker version: 5.4.8+
|
||||
|
||||
Release Dates
|
||||
|
||||
- v8.1.0 February 2026
|
||||
|
||||
IMPORTANT
|
||||
|
||||
Beginning with HPE Morpheus Enterprise Software 8.1.0, the embedded search service changes from Elasticsearch to OpenSearch. This change only affects HPE Morpheus Enterprise Software as HPE Morpheus VM Essentials already uses OpenSearch. HPE continues to support both ElasticSearch and OpenSearch for external clusters. Consult [this section](https://support.hpe.com/hpesc/docDisplay?docId=sd00007510en_us&page=GUID-ECFD4939-8F53-44BB-B8D7-094E28DFAB7C.html) of the user manual for upgrade, migration, and configuration details.
|
||||
|
||||
IMPORTANT
|
||||
|
||||
HPE Morpheus Enterprise Software version v8.1.0 does not support rolling upgrades. Consult [non-rolling upgrade documentation](https://support.hpe.com/hpesc/docDisplay?docId=sd00007510en_us&page=GUID-5205CDAA-81D9-412F-9DF2-6A2A6CA9D1EC.html) for upgrade process steps.
|
||||
|
||||
IMPORTANT
|
||||
|
||||
After upgrading to v8.1.0, it is required to also upgrade HVM Host agents as well. To upgrade HVM Host agents, navigate to the detail page for each HVM Host, expand the ACTIONS menu, and click "Upgrade Agent." This process must be undertaken on all HVM Hosts. Alternatively, you may select "Download Agent Script" to download a shell script to handle the upgrade. Connect to the HVM Host over a terminal session and run the downloaded script. The scripts are unique to each HVM Host so you must download all required scripts and run the correct script against the correct HVM Host.
|
||||
|
||||
# New Features
|
||||
|
||||
Alletra MP Plugin
|
||||
: - For complete update details, see the [Alletra MP plugin release notes](https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007519en_us)
|
||||
|
||||
Appliance
|
||||
: - There is now a single binary installer for both HPE Morpheus Enterprise Software and HPE Morpheus VM Essentials Software. Feature access is controlled solely by licensing. Previously, HPE Morpheus Enterprise and HPE Morpheus VM Essentials had separate binary packages
|
||||
- For newly-installed environments without a paid license configured, the evaluation period has been extended from 30 to 60 days
|
||||
|
||||
Aruba CX Plugin
|
||||
: - Version 1.9.0 of the plugin has been released
|
||||
- The serial numbers and health status for each switch are now shown within the network tab of the integration detail
|
||||
- Other internal improvements
|
||||
|
||||
Aruba CX DSS Plugin
|
||||
: - Version 1.5.0 of the plugin has been released
|
||||
- Users may now specify a Policy Distribution Target (PDT) when creating a DSS port group
|
||||
|
||||
HVM
|
||||
: - Added vCPU placement (NUMA and L3 boundaries) control for HVM clusters
|
||||
|
||||
Library
|
||||
: - HPE Morpheus VM Essentials now includes a default library of example images that can be provisioned to HVM Clusters or integrated VMware Clouds right out of the box
|
||||
|
||||
Security
|
||||
: - Updates to internal dependency libraries to close potential security vulnerabilities
|
||||
|
||||
Tenants
|
||||
: - Storage volume detail pages now show the volume UUID
|
||||
|
||||
# Fixes
|
||||
|
||||
API & CLI
|
||||
: - Datastores created via API now have the Tenant permissions given in the request payload
|
||||
- Improved the efficiency of making calls to list instances (/api/instances) which, in some environments, could be slow to respond
|
||||
|
||||
Bare Metal
|
||||
: - Added various fixes and hardening improvements for the HPE Bare Metal Plugin (BMaaS). See the updated integration guide for complete information on plugin use and capabilities
|
||||
|
||||
Google Cloud
|
||||
: - When adding Security Groups, the dropdown menu now shows only Security Groups belonging to GCP rather than all Security Groups
|
||||
|
||||
HVM
|
||||
: - Fixed an issue that caused GFS2 to change to a read-only state when rebooting the HVM Host
|
||||
|
||||
NSX
|
||||
: - Adding NSX Firewall Rules from the Network section of an Instance detail now properly shows the special modal for creating NSX Firewall Rules rather than the generic modal for other Firewall Rule types. This is the same expected modal shown when creating NSX Firewall Rules from the integration detail
|
||||
|
||||
Terraform
|
||||
: - When applying Terraform state or taking other actions involving Terraform (ex. creating Catalog Items from Terraform Blueprints), decimal values ending in ".0" are no longer truncated (ex. 1.0 -> 1)
|
||||
|
||||
Published: February 2026
|
||||
@@ -0,0 +1,26 @@
|
||||
{
|
||||
"bundle_id": "morpheus_release_notes_8_1_1",
|
||||
"page_id": "sd00007610en_us",
|
||||
"title": "v8.1.1 Release Notes",
|
||||
"ordinal": 1,
|
||||
"parent_title": null,
|
||||
"doc_id": "sd00007610en_us",
|
||||
"version": "8.1.1",
|
||||
"product": "Release Notes",
|
||||
"source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007610en_us",
|
||||
"topic_cluster": {
|
||||
"clustering_title": "v8.1.1 Release Notes",
|
||||
"clustered_topics": [
|
||||
{
|
||||
"bundle_id": "morpheus_release_notes_8_1_0",
|
||||
"page_id": "sd00007496en_us",
|
||||
"clustering_title": "v8.1.0 Release Notes"
|
||||
},
|
||||
{
|
||||
"bundle_id": "morpheus_release_notes_8_1_2",
|
||||
"page_id": "sd00007733en_us",
|
||||
"clustering_title": "v8.1.2 Release Notes"
|
||||
}
|
||||
]
|
||||
}
|
||||
}
|
||||
@@ -0,0 +1,51 @@
|
||||
# v8.1.1 Release Notes
|
||||
|
||||
# v8.1.1 LTS Release Notes
|
||||
|
||||
- Compatible Plugin API version: 1.3.3
|
||||
- Compatible HPE Morpheus Enterprise Software Worker version: 5.4.8+
|
||||
|
||||
Release Dates
|
||||
|
||||
- v8.1.1 March 2026
|
||||
|
||||
IMPORTANT
|
||||
|
||||
Beginning with HPE Morpheus Enterprise Software 8.1.0, the embedded search service changes from Elasticsearch to OpenSearch. This change only affects HPE Morpheus Enterprise Software as HPE Morpheus VM Essentials already uses OpenSearch. HPE continues to support both ElasticSearch and OpenSearch for external clusters. Consult [this section](https://support.hpe.com/hpesc/docDisplay?docId=sd00007510en_us&page=GUID-ECFD4939-8F53-44BB-B8D7-094E28DFAB7C.html) of the user manual for upgrade, migration, and configuration details.
|
||||
|
||||
IMPORTANT
|
||||
|
||||
HPE Morpheus Enterprise Software version v8.1.1 does not support rolling upgrades. Consult [non-rolling upgrade documentation](https://support.hpe.com/hpesc/docDisplay?docId=sd00007510en_us&page=GUID-5205CDAA-81D9-412F-9DF2-6A2A6CA9D1EC.html) for upgrade process steps.
|
||||
|
||||
IMPORTANT
|
||||
|
||||
After upgrading to v8.1.1, it is required to also upgrade HVM Host agents as well. To upgrade HVM Host agents, navigate to the detail page for each HVM Host, expand the ACTIONS menu, and click "Upgrade Agent." This process must be undertaken on all HVM Hosts. Alternatively, you may select "Download Agent Script" to download a shell script to handle the upgrade. Connect to the HVM Host over a terminal session and run the downloaded script. The scripts are unique to each HVM Host so you must download all required scripts and run the correct script against the correct HVM Host.
|
||||
|
||||
# New Features
|
||||
|
||||
Aruba CX DSS Plugin
|
||||
: - Updated the add/edit DSS port group modal to allow users to select one or more security groups
|
||||
- Renamed "Default Firewall Policy" field to "Firewall"
|
||||
- Users may now (optionally) make a Security Group selection for DSS Port Groups
|
||||
|
||||
Catalog
|
||||
: - Added CentOS 10 Stream image templates for many supported Cloud types (HVM, VMware, Nutanix Element, Nutanix Central, OpenStack, and more)
|
||||
- Added Debian 13 image templates for many supported Cloud types (HVM, VMware, Nutanix Element, Nutanix Central, OpenStack, and more)
|
||||
- Added Alma Linux 10 image templates for many supported Cloud types (HVM, VMware, Nutanix Element, Nutanix Central, OpenStack, and more)
|
||||
- Added Rocky Linux 10 image templates for many supported Cloud types (HVM, VMware, Nutanix Element, Nutanix Central, OpenStack, and more)
|
||||
|
||||
HVM
|
||||
: - HVM Host hardware sensor data can now be surfaced into the UI. See HVM cluster documentation for details on configuring hosts to gather and surface this data
|
||||
|
||||
# Fixes
|
||||
|
||||
Bare Metal
|
||||
: - Fixed provisioning failures when bare metal Instances are provisioned with default unmanaged networks using static IP addresses
|
||||
|
||||
Instances
|
||||
: - Fixed manually added VMs, converted to managed, still appearing as discovered
|
||||
|
||||
Migrations
|
||||
: - Fixed OVA export timeouts in vCenter which were left even after successful migrations
|
||||
|
||||
Published: March 2026
|
||||
@@ -0,0 +1,26 @@
|
||||
{
|
||||
"bundle_id": "morpheus_release_notes_8_1_2",
|
||||
"page_id": "sd00007733en_us",
|
||||
"title": "v8.1.2 Release Notes",
|
||||
"ordinal": 1,
|
||||
"parent_title": null,
|
||||
"doc_id": "sd00007733en_us",
|
||||
"version": "8.1.2",
|
||||
"product": "Release Notes",
|
||||
"source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007733en_us",
|
||||
"topic_cluster": {
|
||||
"clustering_title": "v8.1.2 Release Notes",
|
||||
"clustered_topics": [
|
||||
{
|
||||
"bundle_id": "morpheus_release_notes_8_1_0",
|
||||
"page_id": "sd00007496en_us",
|
||||
"clustering_title": "v8.1.0 Release Notes"
|
||||
},
|
||||
{
|
||||
"bundle_id": "morpheus_release_notes_8_1_1",
|
||||
"page_id": "sd00007610en_us",
|
||||
"clustering_title": "v8.1.1 Release Notes"
|
||||
}
|
||||
]
|
||||
}
|
||||
}
|
||||
@@ -0,0 +1,77 @@
|
||||
# v8.1.2 Release Notes
|
||||
|
||||
# v8.1.2 LTS Release Notes
|
||||
|
||||
- Compatible Plugin API version: 1.3.4
|
||||
- Compatible HPE Morpheus Enterprise Software Worker version: 5.4.8+
|
||||
|
||||
Release Dates
|
||||
|
||||
- v8.1.2 April 2026
|
||||
|
||||
IMPORTANT
|
||||
|
||||
Beginning with HPE Morpheus Enterprise Software 8.1.0, the embedded search service changes from Elasticsearch to OpenSearch. This change only affects HPE Morpheus Enterprise Software as HPE Morpheus VM Essentials already uses OpenSearch. HPE continues to support both ElasticSearch and OpenSearch for external clusters. Consult [this section](https://support.hpe.com/hpesc/docDisplay?docId=sd00007510en_us&page=GUID-ECFD4939-8F53-44BB-B8D7-094E28DFAB7C.html) of the user manual for upgrade, migration, and configuration details.
|
||||
|
||||
IMPORTANT
|
||||
|
||||
Not all HPE Morpheus Enterprise Software upgrade version hops support rolling upgrades. Consult the upgrade table contained within our upgrade documentation for rolling upgrade compatibility information. Then, select the upgrade process steps relevant to your environment and planned upgrade hop.
|
||||
|
||||
IMPORTANT
|
||||
|
||||
After upgrading to v8.1.2, it is recommended to check for HVM Host agent upgrades as well. To upgrade HVM Host agents, navigate to the detail page for each HVM Host, expand the ACTIONS menu, and click "Upgrade Agent." This process must be undertaken on all HVM Hosts. Alternatively, you may select "Download Agent Script" to download a shell script to handle the upgrade. Connect to the HVM Host over a terminal session and run the downloaded script. The scripts are unique to each HVM Host so you must download all required scripts and run the correct script against the correct HVM Host. Though many do, it is possible that some version upgrade hops will not contain an HVM Host agent upgrade.
|
||||
|
||||
# New Features
|
||||
|
||||
Localization
|
||||
: - Added support for the Japanese keyboard layout (101/102 hardware) on hypervisor console sessions using the HPE Morpheus key extension (VMware, vCD, and HVM/KVM). It also includes a new keyboard tips pop-over in the console UI ("?" button). Japanese keyboard layout on 106/109 hardware is a planned future enhancement
|
||||
|
||||
# Fixes
|
||||
|
||||
API & CLI
|
||||
: - Errors are no longer returned when sending valid DELETE calls to `/api/clusters/{cluster_id}/servers/{server_id}`
|
||||
- Added missing parameters to the return payload received when sending a `GET` call to the `/api/apps endpoint`
|
||||
- Instance resizes to add or remove network interfaces (`PUT /api/instances/{id}/resize`) on HVM or VMware Instances no longer return success messages without actually changing the network interface(s)
|
||||
|
||||
Catalog
|
||||
: - Fixed certain Catalog items getting stuck in a pending state indefinitely regardless of the success or failure of provisioning
|
||||
|
||||
HVM
|
||||
: - Fixed VM clones failing when the storage datastore type was changed (ex. local storage to Alletra plugin storage) from the original VM to the clone VM
|
||||
- After restoring a VM from SimpliVity backup and successfully reconfiguring the restored VM, it can now be powered on successfully
|
||||
- HVM Hosts will no longer fail to enter maintenance mode when a VM being live migrated to another Host transitions to a shut off state during migration
|
||||
- Fixed an issue where certain maintenance mode sequences could cause HVM hosts to go offline or become fenced
|
||||
- Disabling networks (unmarking the Active checkbox and saving) will no longer cause spontaneous changes to the "Enable IPV4" and/or the "DHCP Server" checkboxes on the next edit
|
||||
- Volume attach/detach operations on VirtIO controllers no longer fail when attempted while snapshots are in progress
|
||||
- Fixed intermittent provisioning failures when multiple VMs are simultaneously provisioned using the copy operation
|
||||
- Fixed AltGR key input for HVM console sessions
|
||||
|
||||
Invoices
|
||||
: - The method used to purge old invoices now interprets the "Invoice Retainment" value set in Morpheus global settings to be defined in months (as the UI indicates) rather than days, which led to unintended early data purges
|
||||
|
||||
Kubernetes
|
||||
: - Updating worker node counts for Azure AKS clusters now works properly
|
||||
|
||||
Labels
|
||||
: - Fixed Cloud filtering by Label for Clouds shared down to child Tenants from a parent Tenant
|
||||
|
||||
NSX
|
||||
: - When NSX segments are shared across multiple clusters in a VDC, Morpheus can now associate the NSX segment with multiple vCenter segments
|
||||
|
||||
OLVM
|
||||
: - Fixed Oracle Linux Virtualization Manager (OLVM) image sync to Morpheus
|
||||
|
||||
Plugins
|
||||
: - The Upcloud Cloud-type integration has been ported to a plugin. Appliances not already using this integration must download the plugin and add it to the HPE Morpheus Software appliance
|
||||
- The ESXi Cloud-type integration has been ported to a plugin. Appliances not already using this integration must download the plugin and add it to the HPE Morpheus Software appliance
|
||||
|
||||
SCVMM
|
||||
: - Clone actions performed on SCVMM Instances discovered and converted to managed now can be completed successfully
|
||||
|
||||
Security
|
||||
: - Added security enhancements
|
||||
|
||||
Virtual Images
|
||||
: - Creating Windows VMs with static IP addresses when cloudinit (Cloudbase-init) is set on the Virtual Image now works
|
||||
|
||||
Published: April 2026
|
||||
@@ -0,0 +1,26 @@
|
||||
{
|
||||
"bundle_id": "morpheus_user_manual_8_1_0",
|
||||
"page_id": "GUID-008B6CB0-CC99-4E40-89CE-2EA5D3389D8F",
|
||||
"title": "SSL Self-signed Certificate Regeneration",
|
||||
"ordinal": 355,
|
||||
"parent_title": "Troubleshooting",
|
||||
"doc_id": "sd00007510en_us",
|
||||
"version": "8.1.0",
|
||||
"product": "User Manual",
|
||||
"source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-008B6CB0-CC99-4E40-89CE-2EA5D3389D8F.html",
|
||||
"topic_cluster": {
|
||||
"clustering_title": "SSL Self-signed Certificate Regeneration",
|
||||
"clustered_topics": [
|
||||
{
|
||||
"bundle_id": "morpheus_user_manual_8_1_1",
|
||||
"page_id": "GUID-008B6CB0-CC99-4E40-89CE-2EA5D3389D8F",
|
||||
"clustering_title": "SSL Self-signed Certificate Regeneration"
|
||||
},
|
||||
{
|
||||
"bundle_id": "morpheus_user_manual_8_1_2",
|
||||
"page_id": "GUID-008B6CB0-CC99-4E40-89CE-2EA5D3389D8F",
|
||||
"clustering_title": "SSL Self-signed Certificate Regeneration"
|
||||
}
|
||||
]
|
||||
}
|
||||
}
|
||||
@@ -0,0 +1,19 @@
|
||||
# SSL Self-signed Certificate Regeneration
|
||||
|
||||
When Morpheus is deployed it generates a 10 year self-signed non-trusted SSL certificate. Below details the process to regenerate this certificate and key.
|
||||
|
||||
## Replacing both the certificate and private key
|
||||
|
||||
### Procedure
|
||||
|
||||
1. Delete the certificate and key files in `/etc/morpheus/ssl/` that end in `.crt` and `.key`
|
||||
2. Run Reconfigure `morpheus-ctl reconfigure`
|
||||
3. Restart NGINX `morpheus-ctl restart nginx`
|
||||
|
||||
## Replacing only the certificate
|
||||
|
||||
### Procedure
|
||||
|
||||
1. Delete the certificate file in `/etc/morpheus/ssl/` it ends in `.crt`
|
||||
2. Run Reconfigure `morpheus-ctl reconfigure`
|
||||
3. Restart NGINX `morpheus-ctl restart nginx`
|
||||
@@ -0,0 +1,26 @@
|
||||
{
|
||||
"bundle_id": "morpheus_user_manual_8_1_0",
|
||||
"page_id": "GUID-00CE7A1B-7CBC-4227-B285-2E8E4FFC73B1",
|
||||
"title": "Settings",
|
||||
"ordinal": 320,
|
||||
"parent_title": "Administration",
|
||||
"doc_id": "sd00007510en_us",
|
||||
"version": "8.1.0",
|
||||
"product": "User Manual",
|
||||
"source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-00CE7A1B-7CBC-4227-B285-2E8E4FFC73B1.html",
|
||||
"topic_cluster": {
|
||||
"clustering_title": "Settings",
|
||||
"clustered_topics": [
|
||||
{
|
||||
"bundle_id": "morpheus_user_manual_8_1_1",
|
||||
"page_id": "GUID-00CE7A1B-7CBC-4227-B285-2E8E4FFC73B1",
|
||||
"clustering_title": "Settings"
|
||||
},
|
||||
{
|
||||
"bundle_id": "morpheus_user_manual_8_1_2",
|
||||
"page_id": "GUID-00CE7A1B-7CBC-4227-B285-2E8E4FFC73B1",
|
||||
"clustering_title": "Settings"
|
||||
}
|
||||
]
|
||||
}
|
||||
}
|
||||
@@ -0,0 +1,18 @@
|
||||
# Settings
|
||||
|
||||
The Administration > Settings section sets global configuration parameters for the HPE Morpheus Enterprise appliance, whitelabeling, provisioning, monitoring, backups, logs, software licenses, and the license for HPE Morpheus Enterprise itself.
|
||||
|
||||
**Subtopics**
|
||||
|
||||
- **[Appliance](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-FB4FF7B6-7561-456F-8AC9-8415BE11B9E7.html)**
|
||||
- **[Whitelabel](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-CC1053C5-D26A-4139-BDB9-34B3C5F60AB7.html)**
|
||||
- **[Email Templates](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-29661D5A-2426-4114-B839-1242C7A7D6A8.html)**
|
||||
- **[Provisioning](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-DF02CF23-8387-4D00-87AF-5F2054075F18.html)**
|
||||
- **[Monitoring](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-B4134705-AFEC-46A8-92BD-5723ABF491AA_2.html)**
|
||||
- **[Backups](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-2DEB33CC-132A-494C-B242-CA09B02E9333.html)**
|
||||
- **[Guidance](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-B86C6485-C80C-480F-87B4-4352963D74A5_2.html)**
|
||||
- **[Clients](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-10BE13E9-1014-4162-97E7-A1056FED89B3.html)**
|
||||
- **[Environments](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-0A516D6F-CF1A-4470-8ABB-A7432A1E08D5.html)**
|
||||
- **[Software Licenses](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-49494E3A-BB6A-4C0C-95A9-A1BA3989393C.html)**
|
||||
- **[License](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-9BDE2563-18FC-49B0-83D7-47F57E044D97.html)**
|
||||
- **[Utilities](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-0336B7CB-78A8-4980-BF2F-663F5E1B0EF5.html)**
|
||||
@@ -0,0 +1,26 @@
|
||||
{
|
||||
"bundle_id": "morpheus_user_manual_8_1_0",
|
||||
"page_id": "GUID-00E2C383-D602-4EAD-BE7F-64E69F5DD5C1",
|
||||
"title": "Load Balancers",
|
||||
"ordinal": 226,
|
||||
"parent_title": "Load Balancers",
|
||||
"doc_id": "sd00007510en_us",
|
||||
"version": "8.1.0",
|
||||
"product": "User Manual",
|
||||
"source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-00E2C383-D602-4EAD-BE7F-64E69F5DD5C1.html",
|
||||
"topic_cluster": {
|
||||
"clustering_title": "Load Balancers",
|
||||
"clustered_topics": [
|
||||
{
|
||||
"bundle_id": "morpheus_user_manual_8_1_1",
|
||||
"page_id": "GUID-00E2C383-D602-4EAD-BE7F-64E69F5DD5C1",
|
||||
"clustering_title": "Load Balancers"
|
||||
},
|
||||
{
|
||||
"bundle_id": "morpheus_user_manual_8_1_2",
|
||||
"page_id": "GUID-00E2C383-D602-4EAD-BE7F-64E69F5DD5C1",
|
||||
"clustering_title": "Load Balancers"
|
||||
}
|
||||
]
|
||||
}
|
||||
}
|
||||
@@ -0,0 +1,88 @@
|
||||
# Load Balancers
|
||||
|
||||
The Load Balancers tab list currently available Load Balancers, which you can select, edit or delete, and is where you can create new or integrate with external Load Balancers.
|
||||
|
||||
## Configuration parameters to add a new load balancer
|
||||
|
||||
Following parameters are required configure the respective load balancers:
|
||||
|
||||
Amazon ALB
|
||||
: - Scheme
|
||||
- Internal
|
||||
- Internet-Facing
|
||||
- Amazon Subnets (Select + to add additional) \* Specify the subnets to enable for your load balancer. You can specify only one subnet per Availability Zone. You must specify subnets from at least two Availability Zones to increase the availability of your load balancer.
|
||||
- Amazon Security Groups (Select + to add additional)
|
||||
|
||||
For details, see [Add Amazon ALB load balancer](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-4983900F-0A3F-4F61-BB06-8270BE27C886.html).
|
||||
|
||||
Azure load balancer
|
||||
: - Cloud
|
||||
- Resource Group \* Populated from cloud selection
|
||||
|
||||
For details, see [Add Azure load balancer](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-EBE2FE5D-207A-4BDB-BA04-BDDD76873A26.html).
|
||||
|
||||
Citrix NetScaler
|
||||
: - API Host
|
||||
- API Port
|
||||
- Username
|
||||
- Password
|
||||
|
||||
For details, see [Add Citrix NetScaler Integration](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-1CC88F1D-21D7-4715-95BB-47F52C0AED42.html).
|
||||
|
||||
F5 BigIP (v11.4+)
|
||||
: - API Host
|
||||
- API Port
|
||||
- Username
|
||||
- Password
|
||||
- Management URL
|
||||
|
||||
For details, see [Add F5BigIP load balancer](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-5473844F-B09C-4F23-AC2F-A305A384136B.html).
|
||||
|
||||
FortiADC
|
||||
: - API HOST
|
||||
- API PORT
|
||||
- USERNAME
|
||||
- PASSWORD
|
||||
- INTERFACE (synced on auth)
|
||||
|
||||
For details, see [Add FortiADC load balancer](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-E97DD1D7-4888-4CC2-B69E-7F05FA18ED33.html).
|
||||
|
||||
HaProxy Container (Internal, will create a HaProxy container, must have available docker host to provision to)
|
||||
: - Group
|
||||
- Cloud
|
||||
- Name
|
||||
- Description
|
||||
- Plan \* Select the size of HaProxy container to be provisioned
|
||||
|
||||
For details, see [Add HaProxy container load balancer](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-96732ACE-6F43-453A-8F9B-FD0F1C717362.html).
|
||||
|
||||
NSX load balancer
|
||||
: - NSX
|
||||
- Name
|
||||
- Description
|
||||
- Enabled
|
||||
- Admin State
|
||||
- Size
|
||||
- Tier-1 Gateways
|
||||
- Log Level
|
||||
|
||||
For details, see [Add NSX load balancer](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-6427BABA-5ECA-4316-905D-0DC0C8FB0D8A.html).
|
||||
|
||||
NSX Advanced load balancer
|
||||
: - Group
|
||||
- Cloud
|
||||
- Name
|
||||
- Description
|
||||
- API HOST
|
||||
- API PORT
|
||||
- USERNAME
|
||||
- PASSWORD
|
||||
- AVI CLOUD
|
||||
|
||||
For details, see [Add NSX advanced load balancer](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-269D2944-5080-4897-86F5-AC949F4B83F1.html).
|
||||
|
||||
Upon saving, your new load balancer will be added to the load balancers list and available in the load balancer drop-down list under the Provisioning Wizard Automation Section for Instance Types that have scaling enabled.
|
||||
|
||||
### Load Balancer Detail Pages
|
||||
|
||||
In the main Load Balancer page, select an existing Load Balancer to go to that Load Balancers Details Page, which lists Stats, Settings, Actions and Virtual Servers for that load balancer.
|
||||
@@ -0,0 +1,26 @@
|
||||
{
|
||||
"bundle_id": "morpheus_user_manual_8_1_0",
|
||||
"page_id": "GUID-014CB518-CCE4-449A-9BCC-241FF8FEA3C5",
|
||||
"title": "Ansible Troubleshooting",
|
||||
"ordinal": 345,
|
||||
"parent_title": "Troubleshooting",
|
||||
"doc_id": "sd00007510en_us",
|
||||
"version": "8.1.0",
|
||||
"product": "User Manual",
|
||||
"source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-014CB518-CCE4-449A-9BCC-241FF8FEA3C5.html",
|
||||
"topic_cluster": {
|
||||
"clustering_title": "Ansible Troubleshooting",
|
||||
"clustered_topics": [
|
||||
{
|
||||
"bundle_id": "morpheus_user_manual_8_1_1",
|
||||
"page_id": "GUID-014CB518-CCE4-449A-9BCC-241FF8FEA3C5",
|
||||
"clustering_title": "Ansible Troubleshooting"
|
||||
},
|
||||
{
|
||||
"bundle_id": "morpheus_user_manual_8_1_2",
|
||||
"page_id": "GUID-014CB518-CCE4-449A-9BCC-241FF8FEA3C5",
|
||||
"clustering_title": "Ansible Troubleshooting"
|
||||
}
|
||||
]
|
||||
}
|
||||
}
|
||||
@@ -0,0 +1,52 @@
|
||||
# Ansible Troubleshooting
|
||||
|
||||
When a workflow is executed manually, the Ansible run output is available in the Instance History tab. Select the `i` bubble next to the Ansible task to see the output. You can also see the run output in UI logs at `/var/log/morpheus/morpheus-ui/current`. These can be tailed by running `morpheus-ctl tail morpheus-ui`.
|
||||
|
||||
## Verify Ansible is installed on the HPE Morpheus Enterprise Appliance
|
||||
|
||||
Ansible should be automatically installed but certain OS or network conditions can prevent the automated install. You can confirm installation by running `ansible --version` in the HPE Morpheus Enterprise appliance, or by viewing the Ansible integration details page (Administration > Integrations > Select Ansible Integration). We also see it in the Ansible tab of a Group or Cloud scoped to Ansible, just run `--version` as ansible is already included in the command.
|
||||
|
||||
### If Ansible is not installed
|
||||
|
||||
Follow these instructions to install, or use your preferred installation method
|
||||
|
||||
Ubuntu:
|
||||
|
||||
```
|
||||
```
|
||||
sudo apt-get install software-properties-common
|
||||
sudo apt-add-repository ppa:ansible/ansible
|
||||
sudo apt-get update
|
||||
sudo apt-get install ansible python-requests
|
||||
```
|
||||
```
|
||||
|
||||
CentOS:
|
||||
|
||||
```
|
||||
```
|
||||
sudo yum install epel-release
|
||||
sudo yum install ansible python-requests
|
||||
```
|
||||
```
|
||||
|
||||
Then create the working Ansible directory for Morpheus:
|
||||
|
||||
```
|
||||
```
|
||||
sudo mkdir /opt/morpheus/.ansible
|
||||
sudo chown morpheus-app.morpheus-app /opt/morpheus/.ansible
|
||||
```
|
||||
```
|
||||
|
||||
## Validate Git repo authorization and the configured paths
|
||||
|
||||
The public and private SSH keys need to be added to the HPE Morpheus Enterprise appliance via Infrastructure > Keys & Certs and the public key needs to be added to the Git repo via user settings. If both are set up correctly, you will see the playbooks and roles populate in the Ansible Integration details page.
|
||||
|
||||
The Git Ref field on playbook tasks is to specify a different git branch than default. It can be left to use the default branch. If your playbooks are in a different branch you can add the brach name in the Git Ref field.
|
||||
|
||||
When running a playbook that is in a workflow, the additional playbooks fields do not need to be populated, they are for running a different playbook than the one set in the Ansible task in the Workflow, or using a different Git Ref.
|
||||
|
||||
NOTE
|
||||
|
||||
If you are manually running Workflows with Ansible tasks on existing Instances through Actions > Run Workflow and not seeing results, set the Provision Phase on the Ansible task to Provision as there may be issues with executing tasks on other phases when executing manually.
|
||||
@@ -0,0 +1,26 @@
|
||||
{
|
||||
"bundle_id": "morpheus_user_manual_8_1_0",
|
||||
"page_id": "GUID-016909A4-5AF9-4DE7-8088-DB62BBC6B00C",
|
||||
"title": "Provisioning a New Server",
|
||||
"ordinal": 414,
|
||||
"parent_title": "Compute Management",
|
||||
"doc_id": "sd00007510en_us",
|
||||
"version": "8.1.0",
|
||||
"product": "User Manual",
|
||||
"source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-016909A4-5AF9-4DE7-8088-DB62BBC6B00C.html",
|
||||
"topic_cluster": {
|
||||
"clustering_title": "Provisioning a New Server",
|
||||
"clustered_topics": [
|
||||
{
|
||||
"bundle_id": "morpheus_user_manual_8_1_1",
|
||||
"page_id": "GUID-016909A4-5AF9-4DE7-8088-DB62BBC6B00C",
|
||||
"clustering_title": "Provisioning a New Server"
|
||||
},
|
||||
{
|
||||
"bundle_id": "morpheus_user_manual_8_1_2",
|
||||
"page_id": "GUID-016909A4-5AF9-4DE7-8088-DB62BBC6B00C",
|
||||
"clustering_title": "Provisioning a New Server"
|
||||
}
|
||||
]
|
||||
}
|
||||
}
|
||||
@@ -0,0 +1,9 @@
|
||||
# Provisioning a New Server
|
||||
|
||||
Provisioning a new server allows onboarding new, unmanaged HPE ProLiant servers into a Bare Metal Cloud environment, enabling HPE Morpheus to manage their lifecycle, including automated OS deployment and hardware monitoring.
|
||||
|
||||
**Subtopics**
|
||||
|
||||
- **[Importing HPE ProLiant Bare Metal Servers](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-61034B56-5E87-4A7F-A15C-79F82D5BC2ED.html)**
|
||||
- **[Provisioning an Instance](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-F6FA00DA-FD93-4AF1-BA10-BB876D19C6A7.html)**
|
||||
- **[Post-Provisioning](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-910B7DB4-B418-4281-B5FC-3A6C0FC02CD9.html)**
|
||||
@@ -0,0 +1,26 @@
|
||||
{
|
||||
"bundle_id": "morpheus_user_manual_8_1_0",
|
||||
"page_id": "GUID-030A6638-D9C6-492A-A021-8634B29738F7",
|
||||
"title": "CyberArk Conjur",
|
||||
"ordinal": 525,
|
||||
"parent_title": "Trust",
|
||||
"doc_id": "sd00007510en_us",
|
||||
"version": "8.1.0",
|
||||
"product": "User Manual",
|
||||
"source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-030A6638-D9C6-492A-A021-8634B29738F7.html",
|
||||
"topic_cluster": {
|
||||
"clustering_title": "CyberArk Conjur",
|
||||
"clustered_topics": [
|
||||
{
|
||||
"bundle_id": "morpheus_user_manual_8_1_1",
|
||||
"page_id": "GUID-030A6638-D9C6-492A-A021-8634B29738F7",
|
||||
"clustering_title": "CyberArk Conjur"
|
||||
},
|
||||
{
|
||||
"bundle_id": "morpheus_user_manual_8_1_2",
|
||||
"page_id": "GUID-030A6638-D9C6-492A-A021-8634B29738F7",
|
||||
"clustering_title": "CyberArk Conjur"
|
||||
}
|
||||
]
|
||||
}
|
||||
}
|
||||
@@ -0,0 +1,63 @@
|
||||
# CyberArk Conjur
|
||||
|
||||
HPE Morpheus Enterprise supports integration with CyberArk Conjur for stored credential sets as well utilization of Conjur-stored secret values via HPE Morpheus Enterprise Cypher service. This works identically to built-in credential storage and built-in Cypher functionality with the exception that your Conjur server is the storage backend rather than the HPE Morpheus Enterprise appliance itself. In some cases, this may help to consolidate secret management into one central place or it even may be a requirement to satisfy internal security policies at some organizations.
|
||||
|
||||
CyberArk Conjur integration is not included with HPE Morpheus Enterprise out of the box. It is developed as an official plugin and may be applied to any HPE Morpheus Enterprise appliance that needs it. See the HPE Morpheus Enterprise plugin repository website for access to the latest version of the plugin.
|
||||
|
||||
## Applying the Plugin
|
||||
|
||||
The latest version of the CyberArk Conjur plugin is available at the HPE Morpheus Enterprise [plugin share site](https://share.morpheusdata.com/). Select the pane for the correct plugin and click the DOWNLOAD button. The plugin JAR file will be downloaded to the local computer you’re working on.
|
||||
|
||||
|
||||
|
||||
With the plugin downloaded, head back to HPE Morpheus Enterprise to apply the plugin to your appliance. Plugins are added by navigating to Administration > Integrations > Plugins and clicking ADD. Drop the plugin JAR file onto the target and click UPLOAD. It may take a few moments for the plugin to be applied successfully and for the modal to be dismissed after clicking the upload button.
|
||||
|
||||
|
||||
|
||||
Once the plugin is added, we configure the connection details here. Edit the new Conjur plugin by clicking the pencil (✎) icon from its row in the list. Configure the following fields:
|
||||
|
||||
- **NAME:** A friendly name for the new integration to identify it within HPE Morpheus Enterprise
|
||||
- **ENABLED:** Mark the box to make this integration active and available
|
||||
- **CONJUR API URL:** The full URL for the Conjur server, usually listening on port 8443
|
||||
- **CONJUR USERNAME:** The Conjur user account you wish to authenticate with. This user should have read, write, and execute access to the variables configured within the Conjur policy
|
||||
- **CONJUR USERNAME API KEY:** The API key for user entered in the prior field
|
||||
- **CONJUR ORGANIZATION:** The Conjur account in which the user and variables reside
|
||||
- **CLEAR SECRET ON DELETION:** When marked, secret values will be cleared when deleted from HPE Morpheus Enterprise
|
||||
|
||||
IMPORTANT
|
||||
|
||||
Variables are predefined by Conjur policies. This integration does not allow users to create variables but does allow you to read and update their values. If the plugin is configured to clear secrets that are deleted from HPE Morpheus Enterprise, the variable value is updated with an empty value as there is no concept of fully deleting secrets in the Conjur API. If the plugin is configured not to clear secrets on deletion, the secret object is deleted from HPE Morpheus Enterprise without altering it on the Conjur backend.
|
||||
|
||||
By applying and configuring the plugin, the appliance now has the Conjur/Cypher integration available. If you don’t intend to use the credential store integration, you can stop here and look ahead to the feature demonstration further ahead in this guide. If you do intend to use the credential store integration as well, there’s one additional configuration step to take in the next section.
|
||||
|
||||
## Adding A Conjur Trust Integration
|
||||
|
||||
In order to use Conjur with HPE Morpheus Enterprise credentials, we must also add a Conjur-type integration in Infrastructure > Trust > Integrations. By applying the plugin in the previous step, we now have the ability to add this type of integration. From the Trust integrations list page, click + ADD and select “Conjur.” It’s important to note that you **do not** need to again configure the API URL and Conjur login credentials as we just did in the previous step. You may configure them here if you wish, such as if you were making multiple integrations with multiple Conjur appliances, but if you’re simply integrating with the same appliance and user account, this is unnecessary. Simply give the new Trust integration a friendly name for reference in HPE Morpheus Enterprise and indicate the desired mount point for secrets you wish to consume as done in the screenshot below.
|
||||
|
||||
NOTE
|
||||
|
||||
In many cases, you don’t have to configure the connection details when adding a Conjur Trust integration. See the paragraph above.
|
||||
|
||||
|
||||
|
||||
## Conjur and Credential Stores
|
||||
|
||||
With configurations completed, we can take a look at how HPE Morpheus Enterprise is able to interface with Conjur as a credential store. As mentioned at the beginning of this guide, variables are created by Conjur policies and not by HPE Morpheus Enterprise. We can reference existing variables and update the secret values stored within.
|
||||
|
||||
As an example, there is a variable named `BotApp/secretVar` in the target Conjur appliance. When configuring the Trust integration (in the prior section), the `BotApp/` mount point was referenced (see the screenshot in the last section). When creating stored credential sets in HPE Morpheus Enterprise against this Conjur credential store, reference the rest of the variable path as the NAME value on the credential set. In this case, the credential set will be named `secretVar` to complete the `BotApp/secretVar` path as shown in the screenshot below. Be sure to also select Conjur as the CREDENTIAL STORE value rather than the default “Internal.”
|
||||
|
||||
|
||||
|
||||
After saving and going back to the Conjur appliance, the value stored at the referenced variable has been updated. This credential set is also available for use anywhere HPE Morpheus Enterprise allows users to utilize them, such as when integrating new Clouds, authenticating REST calls to populate Option Lists, and many other places.
|
||||
|
||||
## Conjur and Cypher
|
||||
|
||||
In addition to stored credential sets, the CyberArk Conjur plugin also enables integration with HPE Morpheus Enterprise Cypher. Just as calls can be made to internally-stored secret values with Cypher, Conjur variable endpoints may be referenced to onboard secret strings into automation Tasks.
|
||||
|
||||
In the screenshot below, see a simple shell script Task which echoes out a secret value stored in Conjur. As you can see, the `conjur/` mount point is referenced along with the rest of the path to the variable which should be accessed. After executing the Task, we can check the execution history and see that the Conjur-stored value is indeed echoed back out.
|
||||
|
||||
|
||||
|
||||
If desired, the value stored in Conjur could also be updated through the HPE Morpheus Enterprise Cypher UI. Navigate to Tools > Cypher and click + ADD. Note the `conjur` mount point is included in the example list of available mount points shown in the modal. By creating a new Cypher entry at the `conjur` mount point which references an existing Conjur variable path, the value in Conjur can be overwritten. If you’ve configured the plugin to clear secrets on deletion, you can also update the stored value with an empty string when you delete the Cypher object in HPE Morpheus Enterprise. For our example case, we could update the value in Conjur by creating a Cypher entry at the mount point `conjur/BotApp/secretVar`.
|
||||
|
||||
|
||||
@@ -0,0 +1,26 @@
|
||||
{
|
||||
"bundle_id": "morpheus_user_manual_8_1_0",
|
||||
"page_id": "GUID-0336B7CB-78A8-4980-BF2F-663F5E1B0EF5",
|
||||
"title": "Utilities",
|
||||
"ordinal": 330,
|
||||
"parent_title": "Settings",
|
||||
"doc_id": "sd00007510en_us",
|
||||
"version": "8.1.0",
|
||||
"product": "User Manual",
|
||||
"source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-0336B7CB-78A8-4980-BF2F-663F5E1B0EF5.html",
|
||||
"topic_cluster": {
|
||||
"clustering_title": "Utilities",
|
||||
"clustered_topics": [
|
||||
{
|
||||
"bundle_id": "morpheus_user_manual_8_1_1",
|
||||
"page_id": "GUID-0336B7CB-78A8-4980-BF2F-663F5E1B0EF5",
|
||||
"clustering_title": "Utilities"
|
||||
},
|
||||
{
|
||||
"bundle_id": "morpheus_user_manual_8_1_2",
|
||||
"page_id": "GUID-0336B7CB-78A8-4980-BF2F-663F5E1B0EF5",
|
||||
"clustering_title": "Utilities"
|
||||
}
|
||||
]
|
||||
}
|
||||
}
|
||||
@@ -0,0 +1,16 @@
|
||||
# Utilities
|
||||
|
||||
System administrators have access to a utilities panel with the following options:
|
||||
|
||||
- **Reindex all searchable data:** Execute
|
||||
- **Toggle Maintenance Mode:** Enable
|
||||
|
||||
NOTE
|
||||
|
||||
Maintenance mode cleanly places HPE Morpheus Enterprise into a state where maintenance can be performed on the appliance. This drains any active sessions and queues so an auto-scaling group can scale down. It also drains active sessions across services. Restarting HPE Morpheus Enterprise UI disables maintenance mode.
|
||||
|
||||
NOTE
|
||||
|
||||
When using HPE Morpheus Enterprise in a Highly Available (HA) environment, it is important to navigate to a node directly and enable maintenance mode, as opposed to using the load balancer virtual IP (VIP). A local host entry to the specific node may be required to ensure the correct node enters mainteance mode. In fact, it is recommended to use the [analogous API endpoint](https://apidocs.morpheusdata.com/reference/setappliancesettingsmaintenancemode) to toggle a specific node into maintenance mode to avoid redirects back to the VIP address.
|
||||
|
||||
A HPE Morpheus Enterprise node in maintenance mode can still be accessible through the load balancer VIP/target group and can queue requests but will not process anything in queue, while in maintenance mode. A node can be removed/paused from the load balancer VIP or have VIP health checks implemented, if the node UI/API will become inaccessible due to maintenance.
|
||||
@@ -0,0 +1,26 @@
|
||||
{
|
||||
"bundle_id": "morpheus_user_manual_8_1_0",
|
||||
"page_id": "GUID-034C870E-F6DE-4D0B-950B-23A627D33C65",
|
||||
"title": "Storage",
|
||||
"ordinal": 228,
|
||||
"parent_title": "Infrastructure",
|
||||
"doc_id": "sd00007510en_us",
|
||||
"version": "8.1.0",
|
||||
"product": "User Manual",
|
||||
"source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-034C870E-F6DE-4D0B-950B-23A627D33C65.html",
|
||||
"topic_cluster": {
|
||||
"clustering_title": "Storage",
|
||||
"clustered_topics": [
|
||||
{
|
||||
"bundle_id": "morpheus_user_manual_8_1_1",
|
||||
"page_id": "GUID-034C870E-F6DE-4D0B-950B-23A627D33C65",
|
||||
"clustering_title": "Storage"
|
||||
},
|
||||
{
|
||||
"bundle_id": "morpheus_user_manual_8_1_2",
|
||||
"page_id": "GUID-034C870E-F6DE-4D0B-950B-23A627D33C65",
|
||||
"clustering_title": "Storage"
|
||||
}
|
||||
]
|
||||
}
|
||||
}
|
||||
@@ -0,0 +1,14 @@
|
||||
# Storage
|
||||
|
||||
NOTE
|
||||
|
||||
In v3.5.2 STORAGE PROVIDERS has been split out into BUCKETS and FILE SHARES sections.
|
||||
|
||||
**Subtopics**
|
||||
|
||||
- **[Overview](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-DE4B3C05-2C42-42E8-849A-B13E77080955.html)**
|
||||
- **[Storage Buckets](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-30F59A1F-0573-4D88-A679-B5C5168BCE6D.html)**
|
||||
- **[File Shares](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-C5FC61E9-7955-4A9D-8E80-E92683B538AA.html)**
|
||||
- **[Volumes](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-1BF34D63-AEE2-4305-BB8C-B625A1E6B1C4.html)**
|
||||
- **[Data Stores](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-D3548220-4D77-4DBB-8313-CFAD68416264.html)**
|
||||
- **[Servers](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-37CA1665-B331-452A-AA3D-59608D85F006.html)**
|
||||
@@ -0,0 +1,26 @@
|
||||
{
|
||||
"bundle_id": "morpheus_user_manual_8_1_0",
|
||||
"page_id": "GUID-038058DD-CC8D-41F7-AF14-DB01B16993C4",
|
||||
"title": "ARM Blueprints",
|
||||
"ordinal": 132,
|
||||
"parent_title": "App Blueprints",
|
||||
"doc_id": "sd00007510en_us",
|
||||
"version": "8.1.0",
|
||||
"product": "User Manual",
|
||||
"source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-038058DD-CC8D-41F7-AF14-DB01B16993C4.html",
|
||||
"topic_cluster": {
|
||||
"clustering_title": "ARM Blueprints",
|
||||
"clustered_topics": [
|
||||
{
|
||||
"bundle_id": "morpheus_user_manual_8_1_1",
|
||||
"page_id": "GUID-038058DD-CC8D-41F7-AF14-DB01B16993C4",
|
||||
"clustering_title": "ARM Blueprints"
|
||||
},
|
||||
{
|
||||
"bundle_id": "morpheus_user_manual_8_1_2",
|
||||
"page_id": "GUID-038058DD-CC8D-41F7-AF14-DB01B16993C4",
|
||||
"clustering_title": "ARM Blueprints"
|
||||
}
|
||||
]
|
||||
}
|
||||
}
|
||||
@@ -0,0 +1,41 @@
|
||||
# ARM Blueprints
|
||||
|
||||
ARM Blueprints provide a simple and repeatable way of deploying infrastructure-as-code to Azure Clouds. Objects and properties are defined in a JSON file and are provisionable on-demand in |ProApp|
|
||||
|
||||
To create a new ARM Blueprint, navigate to Library > Blueprints > App Blueprints. Click + ADD.
|
||||
|
||||
On the Name tab of the New Blueprint modal, enter a name for your new Blueprint. In the Type dropdown menu, select ARM. NEXT
|
||||
|
||||
In the Blueprint Summary section, complete the following fields as needed:
|
||||
|
||||
- **NAME:** Enter a name for this Blueprint as it will appear in the HPE Morpheus Enterprise Blueprints list
|
||||
- **DESCRIPTION:** An optional description field for your Blueprint
|
||||
- **CATEGORY:** An optional category tag for your Blueprint, such as web, utility, or app
|
||||
- **IMAGE:** An optional image icon to more easily identify your Blueprint from a list. If no image is uploaded, a default image will be used
|
||||
|
||||
The ARM template itself is defined in the ARM Configuration section. Using the Config Type dropdown menu, we can opt to write or paste JSON configuration directly into this modal, or we can choose to bring in a JSON which we’re keeping under version control in a Git repository.
|
||||
|
||||
Depending on whether we need the HPE Morpheus Enterprise Agent installed and/or cloud-init enabled, mark the following boxes in the next section:
|
||||
|
||||
- **INSTALL AGENT**
|
||||
- **CLOUD INIT ENABLED**
|
||||
|
||||
If writing or pasting your configuration JSON directly into the modal, fill out the following fields:
|
||||
|
||||
- **OS TYPE:** Identify the resources to be created as Linux or Windows
|
||||
- **CONFIG TYPE:** ARM Template JSON (.json)
|
||||
- **CONFIG:** Your JSON configuration template
|
||||
|
||||
If bringing in a template from a Git repository, fill out the following fields:
|
||||
|
||||
- **OS TYPE:** Identify the resources to be created as Linux or Windows
|
||||
- **CONFIG TYPE:** “Git Repository”
|
||||
- **SCM INTEGRATION:** If a pre-existing SCM integration is selected here, the available selections in the “Repository” dropdown menu will be filtered to show only those associated with the chosen SCM integration
|
||||
- **REPOSITORY:** Select the repository in which your configuration resides
|
||||
- **BRANCH OR TAG:** The branch in which your configuration resides
|
||||
- **WORKING PATH:** The path to your configuration files
|
||||
- **CONFIG:** Your selected config file
|
||||
|
||||
Once finished, click COMPLETE.
|
||||
|
||||
Your new ARM Blueprint is now saved and should be visible in the list of Blueprints. Blueprints are deployed in the Provisioning > Apps section of HPE Morpheus Enterprise. See the Apps section of HPE Morpheus Enterprise docs for more information on that process.
|
||||
@@ -0,0 +1,26 @@
|
||||
{
|
||||
"bundle_id": "morpheus_user_manual_8_1_0",
|
||||
"page_id": "GUID-0424B3D1-E018-49DD-B584-AEFE6CB4866D",
|
||||
"title": "File Templates",
|
||||
"ordinal": 160,
|
||||
"parent_title": "Templates",
|
||||
"doc_id": "sd00007510en_us",
|
||||
"version": "8.1.0",
|
||||
"product": "User Manual",
|
||||
"source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-0424B3D1-E018-49DD-B584-AEFE6CB4866D.html",
|
||||
"topic_cluster": {
|
||||
"clustering_title": "File Templates",
|
||||
"clustered_topics": [
|
||||
{
|
||||
"bundle_id": "morpheus_user_manual_8_1_1",
|
||||
"page_id": "GUID-0424B3D1-E018-49DD-B584-AEFE6CB4866D",
|
||||
"clustering_title": "File Templates"
|
||||
},
|
||||
{
|
||||
"bundle_id": "morpheus_user_manual_8_1_2",
|
||||
"page_id": "GUID-0424B3D1-E018-49DD-B584-AEFE6CB4866D",
|
||||
"clustering_title": "File Templates"
|
||||
}
|
||||
]
|
||||
}
|
||||
}
|
||||
@@ -0,0 +1,60 @@
|
||||
# File Templates
|
||||
|
||||
File Templates are for generating config files, such as my.cnf, opensearch.yml, morpheus.rb, or any text file. With full config map variable support, Template Files are dynamically generated during a Workflow phase or ad hoc via Instance actions.
|
||||
|
||||
File Templates can also be exposed on Instances in the Settings Tab. Ensure the Instance Type supports settings, and Category is defined in Advance Options on the Library Template config.
|
||||
|
||||
NOTE
|
||||
|
||||
HPE Morpheus Enterprise variables are supported in Library Templates using `<%= variable.var %>` format
|
||||
|
||||
Examples:
|
||||
|
||||
HA Proxy Config (haproxy.cfg)
|
||||
|
||||
- FILE NAME: haproxy.cfg
|
||||
- FILE PATH: /config/haproxy.cfg
|
||||
- PHASE: Pre Provision
|
||||
- TEMPLATE:
|
||||
- SETTING NAME: haproxyConfig
|
||||
- SETTING CATEGORY: haproxy
|
||||
|
||||
```
|
||||
```
|
||||
#!/bin/bash
|
||||
global
|
||||
maxconn 256
|
||||
log /dev/log local0 warning
|
||||
log-tag <%=logTag%>
|
||||
defaults
|
||||
mode http
|
||||
timeout connect 5000ms
|
||||
timeout client 50000ms
|
||||
timeout server 50000ms
|
||||
log global
|
||||
frontend http-in
|
||||
bind *:<%=container.externalPort%>
|
||||
default_backend servers
|
||||
backend servers
|
||||
# server server1 127.0.0.1:80 maxconn 32
|
||||
```
|
||||
```
|
||||
|
||||
mysql config (mysqld.cnf)
|
||||
|
||||
- FILE NAME: mysqld.cnf
|
||||
- FILE PATH: /config/mysqld.cnf
|
||||
- PHASE: Pre Provision
|
||||
|
||||
```
|
||||
```
|
||||
#!/bin/bash
|
||||
[mysqld]
|
||||
pid-file= /var/run/mysqld/mysqld.pid
|
||||
socket= /var/run/mysqld/mysqld.sock
|
||||
datadir= /var/lib/mysql
|
||||
# Disabling symbolic-links is recommended to prevent assorted security risks
|
||||
symbolic-links=0
|
||||
explicit_defaults_for_timestamp = 1
|
||||
```
|
||||
```
|
||||
@@ -0,0 +1,26 @@
|
||||
{
|
||||
"bundle_id": "morpheus_user_manual_8_1_0",
|
||||
"page_id": "GUID-0429DE80-5EF4-4D9F-B617-CB41D31DE60E",
|
||||
"title": "DNS",
|
||||
"ordinal": 482,
|
||||
"parent_title": "Integration Guides",
|
||||
"doc_id": "sd00007510en_us",
|
||||
"version": "8.1.0",
|
||||
"product": "User Manual",
|
||||
"source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-0429DE80-5EF4-4D9F-B617-CB41D31DE60E.html",
|
||||
"topic_cluster": {
|
||||
"clustering_title": "DNS",
|
||||
"clustered_topics": [
|
||||
{
|
||||
"bundle_id": "morpheus_user_manual_8_1_1",
|
||||
"page_id": "GUID-0429DE80-5EF4-4D9F-B617-CB41D31DE60E",
|
||||
"clustering_title": "DNS"
|
||||
},
|
||||
{
|
||||
"bundle_id": "morpheus_user_manual_8_1_2",
|
||||
"page_id": "GUID-0429DE80-5EF4-4D9F-B617-CB41D31DE60E",
|
||||
"clustering_title": "DNS"
|
||||
}
|
||||
]
|
||||
}
|
||||
}
|
||||
@@ -0,0 +1,7 @@
|
||||
# DNS
|
||||
|
||||
**Subtopics**
|
||||
|
||||
- **[AWS Route53](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-B882BBCA-C655-44F1-B570-D8902CDAE0D3.html)**
|
||||
- **[Microsoft DNS](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-F3EE0A66-353F-4987-AE3D-C3F29AFCBE71.html)**
|
||||
- **[PowerDNS](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-367B7FE3-99E0-438C-87C0-43F9A179B552.html)**
|
||||
@@ -0,0 +1,26 @@
|
||||
{
|
||||
"bundle_id": "morpheus_user_manual_8_1_0",
|
||||
"page_id": "GUID-0441F3DD-FF73-49C0-8900-718B95266989",
|
||||
"title": "Policy Types",
|
||||
"ordinal": 318,
|
||||
"parent_title": "Policies",
|
||||
"doc_id": "sd00007510en_us",
|
||||
"version": "8.1.0",
|
||||
"product": "User Manual",
|
||||
"source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-0441F3DD-FF73-49C0-8900-718B95266989.html",
|
||||
"topic_cluster": {
|
||||
"clustering_title": "Policy Types",
|
||||
"clustered_topics": [
|
||||
{
|
||||
"bundle_id": "morpheus_user_manual_8_1_1",
|
||||
"page_id": "GUID-0441F3DD-FF73-49C0-8900-718B95266989",
|
||||
"clustering_title": "Policy Types"
|
||||
},
|
||||
{
|
||||
"bundle_id": "morpheus_user_manual_8_1_2",
|
||||
"page_id": "GUID-0441F3DD-FF73-49C0-8900-718B95266989",
|
||||
"clustering_title": "Policy Types"
|
||||
}
|
||||
]
|
||||
}
|
||||
}
|
||||
@@ -0,0 +1,262 @@
|
||||
# Policy Types
|
||||
|
||||
## Cypher Policies
|
||||
|
||||
HPE Morpheus Enterprise allows administrators to set robust Cypher policies, which determine global, role, and/or specific user access to configured Cypher secret mount points. A number of considerations should be made when deploying Cypher Access policies, including how user role permissions will interact with the policy and how conflicts between overlapping policies are resolved.
|
||||
|
||||
### Role Permissions
|
||||
|
||||
User Role permissions (Administration > Roles) greatly affect Cypher access. Cypher access Role permissions are set from the Features tab of the selected Role under “Tools: Cypher”. The Role permission should be set based on the highest level of access to any one individual Cypher entry needed for the specific Role. For example, if the Role needs no access to any Cypher entries, set the feature permission to “None” and hide the Cypher UI from the Role completely. Alternatively, if the Role needs to use and decrypt even one Cypher entry, set the feature permission to “Full Decrypt”. The complete set of available permissions are below:
|
||||
|
||||
- **NONE:** Cypher UI hidden
|
||||
- **READ:** Cypher UI present, entries can be listed
|
||||
- **USER:** Cypher UI present, user sees and can use their own entries, user can create new entries
|
||||
- **FULL:** Cypher UI present, user sees and can use all entries, user can create new entries, user cannot decrypt any entries
|
||||
- **FULL DECRYPT:** Full access to Cypher features including the ability to decrypt secrets
|
||||
|
||||
### Cypher Access Policies
|
||||
|
||||
Like other Policy types, Cypher Access Policies are created in Administration > Policies. Click + ADD POLICY to create new. Set the type to “Cypher Access” and the relevant configuration options will be displayed. In addition to the type, enter a name for the Policy in the top section.
|
||||
|
||||
|
||||
|
||||
In the next section, enter the key path to which the Policy will apply. In addition to static entries that point to one specific Cypher entry, this field supports pattern matching with regex. For example, enter “.\*” to refer to all Cypher entries or “secret/.\*” to refer to all entries under the secret mount point.
|
||||
|
||||
In addition to the path, set the privileges users in the Policy scope should have on the indicated path.
|
||||
|
||||
- **LIST:** See the entries on the indicated path listed in the Cypher UI
|
||||
- **READ:** Decrypt the entries on the indicated path
|
||||
- **WRITE:** Add new entries on the indicated path
|
||||
- **UPDATE:** Edit Cypher entries on the indicated path
|
||||
- **DELETE:** Delete entries on the indicated path
|
||||
|
||||
|
||||
|
||||
Finally, set the scope for the Policy. Cypher Access Policies support Global, Role, and User scope. For example, you may want to block off sets of Cypher entries for various departments within your organization. If you have existing Roles in HPE Morpheus Enterprise for each department, you can set up Role-scoped Policies to ensure they can only list, use, and add Cypher entries which are relevant to their own department.
|
||||
|
||||
|
||||
|
||||
IMPORTANT
|
||||
|
||||
When Cypher Access Policies conflict, the Policy with the longest path string length (typically the most specific) takes precedence. For example, a Policy giving LIST and READ access to “secret/aws/.\*” would be superseded by a Policy giving NO access to “secret/aws/my-secret-key”. In such a case, the user would see everything at the “secret/aws/.\*” path except the one indicated in the more specific Policy. When Policies targeting the same path differ only in their scope, the following scope precedence is applied: Role > User > Global. For example, if a Role-scoped Policy targeting “.\*” grants LIST and READ while a User-scoped Policy targeting the same path grants LIST, the user would be granted the rights in the Role-scoped Policy.
|
||||
|
||||
### Cloud Profiles
|
||||
|
||||
Terraform Cloud Profiles are created on each Cloud detail page (Infrastructure > Clouds > Selected Cloud > ProfilesTab), encrypted in Cypher, and create a Cypher entry that is visible both on the Profile tab of the Cloud detail page and in Cypher. When added to a Cloud they create a Cypher entry at path tfvars/profile/cloud/$cloudCode/variables. If a Cloud profile Cypher entry is restricted by a Cypher Access policy, it will be (or will not be) listable/readable/deletable as dictated by the Policy but still will be viewable from the Cloud detail page if the user has sufficient permissions. Restricting or granting access to Cloud profiles via Policy does not affect access on the Cloud. Other Role permissions, such as “Admin: Profiles”, “Infrastructure: Clouds”, and Cloud/Group access must be used to restrict access via Cloud detail pages.
|
||||
|
||||
### Example Policy
|
||||
|
||||
In my example organization, I have one department that needs access to AWS-related secrets and another department that needs access to Azure-related secrets. There are many other secrets stored in my appliance but I don’t want either of these departments to access any of those.
|
||||
|
||||
|
||||
|
||||
For the first department, I’ve set up a Policy that allows them to list and read (including use and decryption rights) AWS secrets. A second Policy specifically excludes them from seeing one specific entry. The Policy with the more specific path will supersede the more generic Policy that includes a wildcard.
|
||||
|
||||
|
||||
|
||||
By impersonating the user, we see they indeed have access to just the two desired Cypher entries.
|
||||
|
||||
|
||||
|
||||
For the second department, I have set up a Policy that allows them to list and read (including use and decryption rights) Azure secrets.
|
||||
|
||||
|
||||
|
||||
By impersonating the user once again, we see they indeed have access only to Azure entries.
|
||||
|
||||
|
||||
|
||||
## Expiration Policies
|
||||
|
||||
Expiration policies set an expiration timeframe for any instance provisioned into the cloud, role, group or by the user the policy is added to. When an instance expires, it is terminated and deleted.
|
||||
|
||||
Configuration options for expiration policies:
|
||||
|
||||
Expiration Type
|
||||
: - User Configurable- expiration timeframe is editable during provisioning
|
||||
- Fixed Expiration- user cannot change expiration timeframe
|
||||
|
||||
Expiration Days
|
||||
: Configures the number of days the instance is allowed to exist before being removed.
|
||||
|
||||
Renewal Days
|
||||
: If the instance is renewed, this is the number of days by which the expiration date is increased.
|
||||
|
||||
Notification Days
|
||||
: This allows an email notice to be sent out X days before the instance is set to expire.
|
||||
|
||||
Notification Message
|
||||
: Customizable message for notification emails. The default message is `Instance ${instance?.name} is set to expire on ${instance?.expireDate}`
|
||||
|
||||
Auto Approve Extensions
|
||||
: Enable this to auto-approve extension requests, bypassing approval workflows.
|
||||
|
||||
Instances with expirations show the time until expiration in the instance detail pane. Instances with active expiration policies can be extended by selecting the EXTEND NOW button in the instance detail pane. The extension length is set in the policy by the RENEWAL DAYS field.
|
||||
|
||||
Expirations can also be added to any instance during provisioning by entering the number of days in the EXPIRATION DAYS field in the Lifecycle section of the automation section of the provisioning wizard. Expiration can be added to any instance even if no policies have been created.
|
||||
|
||||
NOTE
|
||||
|
||||
Expiration and Shutdown Policies will be enforced on Instances created when converting a discovered host to managed.
|
||||
|
||||
## Instance and Host Names
|
||||
|
||||
Naming Policies will populate a fixed or editable name for instances, hosts and hostnames. The Name Pattern field uses ${variable} string interpolation.
|
||||
|
||||
NAMING TYPE
|
||||
: User Configurable
|
||||
: Naming pattern will pre-populate during provisioning but can be edited by the user.
|
||||
|
||||
Fixed Name
|
||||
: Naming pattern will pre-populate during provisioning and cannot be changed.
|
||||
|
||||
NAME PATTERN
|
||||
: The Name Pattern field uses Static text and/or `${variable}` string interpolation, such as `morpheus${cloudCode}${type}${sequence+3000}`
|
||||
|
||||
An example Instance Name Policy using a naming pattern with User Initials, Cloud Code, Instance Type, and a sequential number starting at 3000 is `${userInitials}-${cloudCode}-${type}-${sequence+3000}`, resulting in an Instance Name of **md-vmwd3-centos-3001** for the first instance, followed by **md-vmwd3-centos-3002** and so on.
|
||||
|
||||
Commonly used variables for naming patterns include:
|
||||
|
||||
```
|
||||
```
|
||||
${groupName}
|
||||
${groupCode}
|
||||
${cloudName}
|
||||
${cloudCode}
|
||||
${type}
|
||||
${accountId}
|
||||
${account}
|
||||
${accountType}
|
||||
${platform}
|
||||
${platform == 'windows' ? 'w':'l'} # results in `w` for Windows platforms and `l` for Linux Platforms
|
||||
${userId}
|
||||
${username}
|
||||
${userInitials}
|
||||
${provisionType}
|
||||
${instance.instanceContext} # Environment Code
|
||||
${sequence} # results in 1
|
||||
${sequence+100} # results in 101
|
||||
${sequence.toString().padLeft(5,'0')} #results in 00001
|
||||
```
|
||||
```
|
||||
|
||||
Cloud codes and Group codes are fields found in their respective configuration panes.
|
||||
|
||||
AUTO RESOLVE CONFLICTS
|
||||
: HPE Morpheus Enterprise will automatically resolve naming conflicts by appending a sequential -number to the name when enabled.
|
||||
|
||||
## Shutdown Policies
|
||||
|
||||
Shutdown policies dictate the number of days an instance is allowed to run before it is shut down. Shutdown is consistent across cloud types i.e.: in VMware, a VM is powered off. In AWS, an instance is stopped. Etc.
|
||||
|
||||
Configuration options for shutdown policies:
|
||||
|
||||
Shutdown Type
|
||||
: User Configurable
|
||||
: Shutdown timeframe is editable during provisioning.
|
||||
|
||||
Fixed Expiration
|
||||
: User cannot change shutdown timeframe during provisioning.
|
||||
|
||||
Expiration Days
|
||||
: Configures the number of days the instance is allowed to exist before being shut down.
|
||||
|
||||
Renewal Days
|
||||
: If the instance is renewed, this is the number of days by which the shutdown date is increased.
|
||||
|
||||
Notification Days
|
||||
: This allows an email notice to be sent out X days before the instance is set to shut down.
|
||||
|
||||
Notification Message
|
||||
: Customizable message for notification email.
|
||||
|
||||
Auto Approve Extensions
|
||||
: Enable this to auto-approve extension requests, bypassing approval workflows.
|
||||
|
||||
NOTE
|
||||
|
||||
Expiration and Shutdown Policies will be enforced on Instances created when converting a discovered host to managed.
|
||||
|
||||
## Provision Approval
|
||||
|
||||
HPE Morpheus Enterprise Provision Approvals enable an approval workflow via internal HPE Morpheus Enterprise approval or via ServiceNow workflow. If a ServiceNow integration is present, the ServiceNow option is enabled. The Approval workflow to be selected is dynamically created by querying the ServiceNow Workflow table in the integrated ServiceNow instance.
|
||||
|
||||
This ServiceNow approval integration enables users to use the HPE Morpheus Enterprise Self-Service provisioning portal to provision new instances and still respect the required ServiceNow business approval workflow.
|
||||
|
||||
## Power Schedules
|
||||
|
||||
Power Schedules set daily times to shutdown and startup instances. Power schedule can be created and managed in Library > Automation > Power Scheduling
|
||||
|
||||
NOTE
|
||||
|
||||
Power Schedule Policies will apply to Instances created in a Group or Cloud after the Policy is enabled, and will not apply to pre-existing Instances.
|
||||
|
||||
Configuration options for Power Schedule Policies:
|
||||
|
||||
DESCRIPTION
|
||||
: Add details about your Policy for reference in the Policies tab.
|
||||
|
||||
Enabled
|
||||
: Policies can be edited and disabled or enabled at any time. Disabling a Power Schedule Policy will prevent the Power Schedule from running on the Groups Instances until re-enabled.
|
||||
|
||||
ENFORCEMENT TYPE
|
||||
: - User Configurable: Power Schedule choice is editable by User during provisioning.
|
||||
- Fixed Schedule: User cannot change Power Schedule setting during provisioning.
|
||||
|
||||
POWER SCHEDULE
|
||||
: Select Power Schedule to use in the Policy. Power schedule can be added in Library > Automation > Power Scheduling
|
||||
|
||||
TENANTS
|
||||
: Leave blank for the Policy to apply to all Tenants, or search for and select Tenants to enforce the Policy on specific Tenants.
|
||||
|
||||
## Max Resources
|
||||
|
||||
Max Resource policies allow setting quotas for Clouds, Groups, Roles or Users for maximum amount of Memory, Storage, Cores, Hosts, VM’s, or Containers that can be created in the Cloud, Group, Role or by the User the Policy is assigned to.
|
||||
|
||||
Configuration options for Max Resources Policies:
|
||||
|
||||
Max Containers
|
||||
: Sets the maximum combined total of Containers in Instances per Policy Scope.
|
||||
|
||||
Max Cores
|
||||
: Sets the maximum combined total of Cores in Instances per Policy Scope.
|
||||
|
||||
Max Hosts
|
||||
: Sets the maximum total of Hosts per Policy Scope.
|
||||
|
||||
Max Memory
|
||||
: Sets the maximum combined total of RAM (capacity) for Instances per Policy Scope.
|
||||
|
||||
Max Storage
|
||||
: Sets the maximum combined total of Storage (capacity) for Instances per Policy Scope.
|
||||
|
||||
Max VMs
|
||||
: Sets the maximum total of managed Virtual Machines per Policy Scope.
|
||||
|
||||
TENANTS
|
||||
: Leave blank for the Policy to apply to all Tenants, or search for and select Tenants to enforce the Policy on specific Tenants.
|
||||
|
||||
## User Creation
|
||||
|
||||
The User Creation policy controls the “CREATE YOUR USER” flag in the User Config options during provisioning do be always disabled, always enabled, enabled by default, or disabled by default.
|
||||
|
||||
Configuration options for User Creation Policies:
|
||||
|
||||
TYPE
|
||||
: User Creation
|
||||
|
||||
DESCRIPTION
|
||||
: Description to identify the policy config
|
||||
|
||||
Enabled
|
||||
: Policies enforcement can be disabled or enabled at any time.
|
||||
|
||||
ENFORCEMENT TYPE
|
||||
: - User Configurable: User Creation choice is editable by User during provisioning.
|
||||
- Fixed: User cannot change User Creation setting during provisioning.
|
||||
|
||||
CREATE USER
|
||||
: Check to allow or force user creation. Uncheck to disable by default or force no user creation.
|
||||
|
||||
TENANTS
|
||||
: Leave blank for the Policy to apply to all Tenants, or search for and select Tenants to enforce the Policy on specific Tenants.
|
||||
@@ -0,0 +1,26 @@
|
||||
{
|
||||
"bundle_id": "morpheus_user_manual_8_1_0",
|
||||
"page_id": "GUID-064FEBCE-E38F-45E0-9349-4177EBFFF70D",
|
||||
"title": "NSX",
|
||||
"ordinal": 508,
|
||||
"parent_title": "Networking Integrations",
|
||||
"doc_id": "sd00007510en_us",
|
||||
"version": "8.1.0",
|
||||
"product": "User Manual",
|
||||
"source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-064FEBCE-E38F-45E0-9349-4177EBFFF70D.html",
|
||||
"topic_cluster": {
|
||||
"clustering_title": "NSX",
|
||||
"clustered_topics": [
|
||||
{
|
||||
"bundle_id": "morpheus_user_manual_8_1_1",
|
||||
"page_id": "GUID-064FEBCE-E38F-45E0-9349-4177EBFFF70D",
|
||||
"clustering_title": "NSX"
|
||||
},
|
||||
{
|
||||
"bundle_id": "morpheus_user_manual_8_1_2",
|
||||
"page_id": "GUID-064FEBCE-E38F-45E0-9349-4177EBFFF70D",
|
||||
"clustering_title": "NSX"
|
||||
}
|
||||
]
|
||||
}
|
||||
}
|
||||
@@ -0,0 +1,115 @@
|
||||
# NSX
|
||||
|
||||
## Overview
|
||||
|
||||
VMware NSX offers network virtualization allowing for creation and management of software-based virtual networks in an efficient and programmatic way. HPE Morpheus Enterprise offers a full-featured integration with NSX, including Project scoping for NSX 4+ integrations. HPE Morpheus Enterprise will ingest and expose its networking abstractions in the following sections of the HPE Morpheus Enterprise NSX integration:
|
||||
|
||||
- SUMMARY
|
||||
- TRANSPORT ZONES
|
||||
- DHCP
|
||||
- SEGMENTS
|
||||
- FIREWALL
|
||||
- TIER-1 GATEWAYS
|
||||
- TIER-0 GATEWAYS
|
||||
- EDGE CLUSTERS
|
||||
- GROUPS
|
||||
|
||||
This guide goes through the process of integrating an existing NSX installation with HPE Morpheus Enterprise and working with the associated objects synced in with the integration. For more on installing NSX and an overview of its concepts, please review the [NSX overview documentation](https://docs.vmware.com/en/VMware-NSX-Data-Center/2.0/com.vmware.nsxt.install.doc/GUID-10B1A61D-4DF2-481E-A93E-C694726393F9.html) provided by VMware.
|
||||
|
||||
## NSX Tagging
|
||||
|
||||
An NSX integration can apply Instance and VM tags to VMs in NSX, if desired. To apply this, mark the box for “APPLY VM TAGS” when adding or editing an NSX integration.
|
||||
|
||||
|
||||
|
||||
Once this configuration is set on the integration, any tags that are applied to applicable Instances through the provisioning wizard at provision time will be applied to those VMs in NSX. In the example below, I’ve set one tag on the new Instance in the provisioning wizard:
|
||||
|
||||
|
||||
|
||||
Once provisioning is complete, the tags are confirmed to be visible in the NSX console as well:
|
||||
|
||||
|
||||
|
||||
## NSX Projects
|
||||
|
||||
Projects in NSX are analogous to tenants in other products and are a part of NSX version 4+. Projects allow for the isolation of networking abstractions into individual tenants within a single NSX appliance. If your organization is already utilizing NSX Projects, you are probably very familiar with their concept and execution but others can find high-level details about them [here](https://docs.vmware.com/en/VMware-NSX/4.1/administration/GUID-52180BC5-A1AB-4BC2-B1CE-666292505317.html).
|
||||
|
||||
HPE Morpheus Enterprise supports a full-featured integration with NSX, including the ability to scope the HPE Morpheus Enterprise integration to a specific Project the service user can access. Using Project-scoped integrations allows multiple NSX integrations to be made to the same NSX appliance and ensures HPE Morpheus Enterprise users are siloed to only the NSX Projects they can access.
|
||||
|
||||
## Add NSX Integration to HPE Morpheus Enterprise
|
||||
|
||||
### Procedure
|
||||
|
||||
1. Navigate to Infrastructure > Network > Integrations
|
||||
2. Select Select + ADD > VMWare NSX
|
||||
3. Enter the following:
|
||||
|
||||
- NAME: Name for the NSX Integration in HPE Morpheus Enterprise
|
||||
- VISIBILITY: Public (available to all HPE Morpheus Enterprise Tenants) or Private (available only to the current Tenant). This option is shown only in the HPE Morpheus Enterprise Master Tenant
|
||||
- API HOST: URL of the NSX Manager (ex. <https://x.x.x.x/api>)
|
||||
- CREDENTIALS: A pre-stored credential set can be used to create this integration. If “Local Credentials” is selected, USERNAME and PASSWORD fields are presented and must be filled
|
||||
- USERNAME: NSX service account username. Prior to NSX version 4, this is likely an admin account with access to all networking constructs. In NSX version 4 and higher, this could be an admin for access to default space constructs or it could be a Project-specific user depending on the access needs of the integration being created
|
||||
- PASSWORD: The password for the NSX service account entered above
|
||||
- PROJECT: As soon as an API HOST and credentials are provided, HPE Morpheus Enterprise will attempt to authenticate with the NSX appliance. When authentication is successful and a NSX 4+ appliance is detected, a PROJECT field will appear and the dropdown will be pre-populated with Projects accessible to the service user account
|
||||
- VMWARE CLOUD: Select the existing VMware cloud associated with this NSX integration
|
||||
4. Select ADD NETWORK INTEGRATION
|
||||
|
||||
### Results
|
||||
|
||||
Once the NSX Integration is added HPE Morpheus Enterprise will sync in existing Transport Zones, DHCP servers and relays, Segments, firewall groups and rules, Gateways, Edge Clusters, and Groups. We can manage these synced items from within HPE Morpheus Enterprise UI, including the ability to create, edit, and delete them.
|
||||
|
||||
NOTE
|
||||
|
||||
The available tabs on the integration detail page will be dependent on the Project selected when the integration was created. Just like in NSX, the default view (and thus integrations scoped to the default Project) will have access to all constructs whereas individual Projects will not. Integrations scoped to individual Projects can view the DHCP, Segments, Firewall, Tier-1 Gateways, and Groups tabs but not the other tabs described here. These limitations are identical to those in the NSX console UI. More information on NSX Projects is available [here](https://docs.vmware.com/en/VMware-NSX/4.1/administration/GUID-52180BC5-A1AB-4BC2-B1CE-666292505317.html).
|
||||
|
||||
## Summary View
|
||||
|
||||
The SUMMARY tab contains the default view when accessing an NSX integration. From the summary view we can see the status of the NSX server, and details about interfaces and group status.
|
||||
|
||||
## Transport Zones
|
||||
|
||||
Access Transport Zones by selecting the Transport Zones tab. The default view of the Transport Zones tab lists Transport zones and presents some detail about them such as name, traffic type, status, and more. The integration allows for creation of new Transport Zones, editing and deleting.
|
||||
|
||||
|
||||
|
||||
## DHCP
|
||||
|
||||
DHCP servers and relays are displayed on the DHCP tab. View information such as names and server addresses. The integration allows for creation of new servers and relays, editing and deleting.
|
||||
|
||||
|
||||
|
||||
## Segments
|
||||
|
||||
Access Segments by from the Segments tab. The summary view includes high-level information such as status, name, network name and CIDR. The integration allows for creating, editing and deleting NSX Segments
|
||||
|
||||
|
||||
|
||||
## Firewall
|
||||
|
||||
Firewall Groups and Rules are accessible from the Firewall tab. From the summary view, Groups can be expanded to view Rules within. From the ACTIONS menu, create new Groups by selecting “Create Group”. When a Group has been expanded, the “Create Rule” selection within the ACTIONS menu will also be accessible and a new rule can be created within the selcted Group. The integration allows for viewing, creating, editing and deleting Firewall Groups and Rules.
|
||||
|
||||
|
||||
|
||||
## Tier-0 Gateways
|
||||
|
||||
Access Tier-0 Gateways from the Tier-0 Gateways tab. The integration allows creating, editing and deleting Tier-0 Gateways.
|
||||
|
||||
|
||||
|
||||
## Tier-1 Gateways
|
||||
|
||||
Access Tier-1 Gateways from the Tier-1 Gateways tab. The integration allows creating, editing and deleting Tier-1 Gateways.
|
||||
|
||||
|
||||
|
||||
## Edge Clusters
|
||||
|
||||
View Edge Clusters from the Edge Clusters tab. The default view lists each Edge Cluster with name, member type, cluster profile, and more. The integration allows viewing and limited editing of Edge Clusters.
|
||||
|
||||
|
||||
|
||||
## Groups
|
||||
|
||||
NSX Groups are viewed from the Groups tab. The default view lists each Group alone with member details. The HPE Morpheus Enterprise NSX integration allows for creating, editing and deleting Groups.
|
||||
|
||||
|
||||
@@ -0,0 +1,26 @@
|
||||
{
|
||||
"bundle_id": "morpheus_user_manual_8_1_0",
|
||||
"page_id": "GUID-06D232B4-F473-44C5-AD24-AECD128273E5",
|
||||
"title": "Mac Stadium",
|
||||
"ordinal": 461,
|
||||
"parent_title": "Clouds",
|
||||
"doc_id": "sd00007510en_us",
|
||||
"version": "8.1.0",
|
||||
"product": "User Manual",
|
||||
"source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-06D232B4-F473-44C5-AD24-AECD128273E5.html",
|
||||
"topic_cluster": {
|
||||
"clustering_title": "Mac Stadium",
|
||||
"clustered_topics": [
|
||||
{
|
||||
"bundle_id": "morpheus_user_manual_8_1_1",
|
||||
"page_id": "GUID-06D232B4-F473-44C5-AD24-AECD128273E5",
|
||||
"clustering_title": "Mac Stadium"
|
||||
},
|
||||
{
|
||||
"bundle_id": "morpheus_user_manual_8_1_2",
|
||||
"page_id": "GUID-06D232B4-F473-44C5-AD24-AECD128273E5",
|
||||
"clustering_title": "Mac Stadium"
|
||||
}
|
||||
]
|
||||
}
|
||||
}
|
||||
@@ -0,0 +1,136 @@
|
||||
# Mac Stadium
|
||||
|
||||
## Overview
|
||||
|
||||
MacStadium is a provider of enterprise-class hosting solutions for Apple Mac infrastructure. It can be used to deploy a hosted private cloud for large-scale CI/CD or even a single Mac mini to test an iOS app. It allows virtualized Mac build machines
|
||||
|
||||
## Features
|
||||
|
||||
- Virtual Machine Provisioning
|
||||
- Backups / Snapshots
|
||||
- Resource Groups
|
||||
- Datastores and DRS Clusters
|
||||
- Distributed Switches
|
||||
- Datacenter / Cluster scoping
|
||||
- Brownfield VM management and migration
|
||||
- VMware to VMware migrations
|
||||
- VMDK/OVF image conversion support
|
||||
- Hypervisor Remote Console
|
||||
- Periodic Synchronization
|
||||
- Veeam Backup Integration
|
||||
- Lifecycle Management and Resize
|
||||
|
||||
On top of all these features, HPE Morpheus Enterprise also adds additional features to VMware that do not exist out of the box to make it easier to manage in multitenant environments as well as hybrid cloud environments:
|
||||
|
||||
- Cloud-Init Support
|
||||
- VHD to VMDK Image Conversion
|
||||
- QCOW2 to VMDK Image Conversion
|
||||
- Multitenancy resource allocation
|
||||
- Virtual Image management (Blueprints)
|
||||
- Auto-scaling and recovery
|
||||
|
||||
## Getting Started
|
||||
|
||||
To get started with VMware, simply start by adding a Cloud in the Infrastructure > Clouds section.
|
||||
|
||||
To start adding a VMware cloud there will be some things you will need:
|
||||
|
||||
vCenter API Url
|
||||
: Typically this is the url to the vCenter web client with a `/sdk` in the path
|
||||
|
||||
Username/Password
|
||||
: A set of credentials with high level access to VMware (ensure the account has Datacenter level access)
|
||||
|
||||
Once these fields are entered, some selections will start pre-populating. A cloud integration is scoped to a specific data center, and can optionally be scoped down to a single cluster or even a single resource pool. If the drop downs do not populate, please verify the api url is resolvable, morpheus has access to vCenter on 443, and the provided credentials are correct and the user has sufficient permissions.
|
||||
|
||||
Another cool feature provided with the cloud integration is optional Resource Pool scoping. One can choose to allow the cloud to provision into All Resource Pools or a singular Resource Pool. When choosing All, these Resource Pools can be managed from a sub-account and visibility perspective via the Cloud Detail page (multi-tenancy).
|
||||
|
||||
The VMware cloud integration provides a few additional options including allowing users to make host selections or keeping that aspect hidden such that the best host is automatically chosen for the requested provision.
|
||||
|
||||
The RPC Mode feature can be configured to allow HPE Morpheus Enterprise to install its agent on the Guest operating system via either SSH/WinRM or Vmware Tools Guest Process feature. The VMware tools Guest Execution API can be tricky so it is recommended to use SSH/WinRM if possible. However, if it is not possible for the Appliance to have outbound access to all networks in which VMs are being provisioned to the SSH/WinRM ports (22, 5985 respectively) then Guest Execution is the only option.
|
||||
|
||||
The Use VNC console option on the VMware cloud requires special configuration on each ESXI host but allowed hypervisor level remote console support. (See the Advanced Section for details)
|
||||
|
||||
When following this add cloud wizard an option will be presented to create a group or add to an existing group. These groups can be given provisioning permission via role based access control. It is normally recommended that groups are organized such that one cloud exists in one group unless the networks are setup such that internal routing is possible between the clouds. This is very useful for bursting, or hybrid cloud configurations.
|
||||
|
||||
## Windows Provisioning Tips
|
||||
|
||||
By default when provisioning windows templates, HPE Morpheus Enterprise performs guest customizations which initiates a sysprep. This resets the Administrator user and password. HPE Morpheus Enterprise will set the Administrator password from Administration > Settings > Provisioning > Windows Settings > Password.
|
||||
|
||||
Users can also set the username on an image as Administrator and enter a different password if unique passwords are required per image.
|
||||
|
||||
Guest customizations are required when assigning static IP’s manually or using IP pools. They can be disabled per virtual image advanced settings under Library > Virtual Images > Edit Image > Advanced > Uncheck “Force Guest Customization” if using DHCP. However the SID will not be changed from the source template. In addition, new VM’s will not be able to join a domain that had already been joined by the source template or any other VM’s with that SID.
|
||||
|
||||
## Existing Instances
|
||||
|
||||
HPE Morpheus Enterprise provides several features regarding pulling in existing virtual machines and servers in an environment. Most cloud options contain a checkbox titled ‘Inventory Existing Instances’. When this option is selected, all VMs found within the specified scope of the cloud integration will be scanned periodically and Virtual Machines will be synced into HPE Morpheus Enterprise. Users may also choose to onboard only virtual machines that are running within specific Resource Pools. Once the vCenter Cloud is integrated, navigate to the detail page for the specific Cloud (select it from the list at Infrastructure > Clouds). From the Resources tab, locate the Pools section. Click ACTIONS > Editnext to a selected Resource Pool. If INVENTORY is checked, HPE Morpheus Enterprise will automatically onboard virtual machines from that Resource Pool.
|
||||
|
||||
By default these virtual machines are considered ‘unmanaged’ and do not appear in the Provisioning > Instances area but rather Infrastructure > Compute > Virtual Machines. However, a few features are provided with regards to unmanaged instances. They can be assigned to various accounts if using a multitenant master account, however it may be best suited to instead assign the ‘Resource Pool’ to an account and optionally move all servers with regards to that pool (more on this later).
|
||||
|
||||
A server can also be made into a managed server. During this process remote access is requested and an agent install is performed on the guest operating system. This allows for guest operations regarding log acquisition and stats. If the agent install fails, a server will still be marked as managed and an Instance will be created in Provisioning, however certain features will not function. This includes stats collection and logs.
|
||||
|
||||
NOTE
|
||||
|
||||
All Cloud data is resynchronized on a 5 minute interval. This includes Datastores, Resource Pools, Networks, Blueprints, and Virtual Machines.
|
||||
|
||||
## Service Plans
|
||||
|
||||
A default set of Service Plans are created in HPE Morpheus Enterprise for the VMware provisioning engine. These Service Plans can be considered akin to AWS Flavors or Openstack Flavors. They provide a means to set predefined tiers on memory, storage, cores, and cpu. Price tables can also be applied to these so estimated cost per virtual machine can be tracked as well as pricing for customers. By default, these options are fixed sizes but can be configured for dynamic sizing. A service plan can be configured to allow a custom user entry for memory, storage, or cpu. To configure this, simply edit an existing Service Plan tied to VMware or create a new one. These all can be easily managed from the Admin > Plans & Pricing section.
|
||||
|
||||
## Virtual Images / Blueprints
|
||||
|
||||
HPE Morpheus Enterprise will automatically take an inventory of all blueprints configured in vCenter and present them as options during provisioning. However, in order for HPE Morpheus Enterprise to properly provision these virtual machines and provide accurate stats and health of these virtual machines, an agent must be installed during virtual machine startup. This means remote access needs to be granted at the guest operating system level to HPE Morpheus Enterprise . To properly configure these virtual images, find the relevant images in Library > Virtual Images and edit the entry. On this form, a few options are presented. The first is a check box asking whether or not cloud-init is enabled. If cloud-init is enabled, simply provide the default OS username configured (for Ubuntu the username is ubuntu and for CentOS the username is centos). For those looking to add cloud-init to existing blueprints HPE Morpheus Enterprise requires no special configuration and can use the default cloud.cfg settings.
|
||||
|
||||
A global cloud-init username/password can also be configured per account as well as a keypair via the `Admin->Provisioning` settings section. The great benefit of utilizing cloud-init is default blueprints do not need common credential sets thereby increasing provisioning security.
|
||||
|
||||
Windows systems do not typically support cloud-init. So simply turn this checkbox off and provide the Administrator credentials. It should be noted that these credentials are encrypted in the database. If using WinRM for the RPC Mode instead of VMware tools, a Local or Domain Administrator account credential set can be provided instead.
|
||||
|
||||
## Snapshots
|
||||
|
||||
HPE Morpheus Enterprise allows the ability to create a snapshot of a VM in VMware vCenter. From the instance detail page, simply select Actions > Create Snapshot to begin creation of a new Snapshot. Existing snapshots can be viewed in the `BACKUPS` tab on the instance detail page. Snapshots taken in vCenter will sync into HPE Morpheus Enterprise every five minutes. To revert to a previous snapshot, click on the revert icon located on the right side of the Snapshot. Snapshots can be deleted by clicking on the trash can icon.
|
||||
|
||||
NOTE
|
||||
|
||||
Access to Snapshots can be limited or removed entirely for specific user roles as needed. To edit a role’s Snapshots permissions, go to Administration > Roles > (Your selected role) > Snapshots. Users can be given Full, Read-only, or No access.
|
||||
|
||||
IMPORTANT
|
||||
|
||||
HPE Morpheus Enterprise supports the use of SR-IOV network adapters with VMware Clouds. Bear in mind that VMware does not support Snapshots for this network adapter type and for that reason Snapshot and backup-related features will also fail in HPE Morpheus Enterprise for VMs using SR-IOV network adapters.
|
||||
|
||||
## Tagging and Metadata
|
||||
|
||||
As of Morpheus version 4.1.0, tagging support is included for vCenter in addition to the other clouds that have already supported it in past versions. Tags will sync to vCenter from Morpheus and existing tags are also inventoried from vCenter into Morpheus.
|
||||
|
||||
NOTE
|
||||
|
||||
This feature requires a minimum API version of vCenter 6.5. The API version can be edited by navigating to ‘Infrastructure > Clouds’ and clicking the edit (pencil) button in the row for the relevant cloud. The field is labeled ‘VERSION’.
|
||||
|
||||
Tags can be created on-demand when provisioning from the ‘CONFIGURE’ tab of the ‘CREATE INSTANCE’ wizard (Provisioning > Instances). Within the ‘Metadata’ drawer, you will see sets of fields to enter key/value pairs. On creation of the instance, this metadata will be synced into vCenter.
|
||||
|
||||
‘Inputs’ from your library can also be exported as metadata for use with vCenter. When adding or editing a new Input (Library > Options > Inputs), simply mark the box labeled ‘EXPORT AS METADATA’. The ‘FIELD NAME’ becomes the tag category in VMWare.
|
||||
|
||||
|
||||
|
||||
## Docker
|
||||
|
||||
So far this document has covered how to add the VMware cloud integration and has enabled users the ability to provision virtual machine based instances via the Add Instance catalog in Provisioning. Another great feature provided by HPE Morpheus Enterprise out of the box is the ability to use Docker containers and even support multiple containers per Docker host. To do this a Docker Host must first be provisioned into VMware (multiple are needed when dealing with horizontal scaling scenarios).
|
||||
|
||||
To provision a Docker Host simply navigate to the Clusters tab of the Cloud detail page or Infrastructure > Clusters section. From there, click + ADD CLUSTER to add a VMware Docker Host. This host will show up in the Hosts tab next to other ESXi servers that were inventoried by the VMware cloud integration. HPE Morpheus Enterprise views a Docker host just like any other Hypervisor with the caveat being that it is used for running containerized images instead of virtualized ones. Once a Docker Host is successfully provisioned a green checkmark will appear to the right of the host marking it as available for use. In the event of a failure click into the relevant host that failed and an error explaining the failure will be displayed in red at the top.
|
||||
|
||||
Some common error scenarios include network connectivity. For a Docker Host to function properly, it must be able to resolve the HPE Morpheus Enterprise appliance url which can be configured in Administration > Settings. If it is unable to resolve and negotiate with the appliance than the agent installation will fail and provisioning instructions will not be able to be issued to the host.
|
||||
|
||||
## Multitenancy
|
||||
|
||||
A very common scenario for Managed Service Providers is the need to provide access to VMware resources on a customer by customer basis. With VMware several administrative features have been added to ensure customer resources are properly scoped and isolated. For VMware it is possible to assign specific Networks, Datastores, and Resource Pools to customer accounts or even set the public visibility of certain resources, therefore allowing all sub accounts access to the resource.
|
||||
|
||||
## Advanced
|
||||
|
||||
There are several advanced features provided within HPE Morpheus Enterprise that can leverage some cool aspects of VMware. One of these features is Remote Console support directly to the hypervisor. To enable this feature a few prerequisites must be met. First, the HPE Morpheus Enterprise appliance must have network access to the ESXi hosts within VCenter. Secondly, firewall settings need to be adjusted on each ESXi host. This can be done in VSphere under firewall configuration on the host. Simply check the gdbserver option, which will open up the necessary ports (starting at 5900 range).
|
||||
|
||||
IMPORTANT
|
||||
|
||||
Hypervisor Console for vCenter 6.5 requires HPE Morpheus Enterprise v3.2.0+
|
||||
|
||||
Now that the ESXi hosts are ready to utilize remote console, simply edit the cloud in HPE Morpheus Enterprise via Infrastructure > Clouds. Check the option that says Enable Hypervisor Console. It is important to note that currently this functionality only works for newly provisioned vm’s provisioned directly via HPE Morpheus Enterprise. This should change soon however.
|
||||
|
||||
It is also possible to import vm snapshots for backup or conversion purposes from VCenter and also an ESXi host. However, this does require that the ESXi host license has an enterprise level license as it will not allow the appliance to download a virtual image if it is not a paid VMware license.
|
||||
@@ -0,0 +1,26 @@
|
||||
{
|
||||
"bundle_id": "morpheus_user_manual_8_1_0",
|
||||
"page_id": "GUID-06D5442F-AE4E-4DD9-969E-34E1A20C80EC",
|
||||
"title": "To create a Tenant Role:",
|
||||
"ordinal": 305,
|
||||
"parent_title": "Tenant Roles",
|
||||
"doc_id": "sd00007510en_us",
|
||||
"version": "8.1.0",
|
||||
"product": "User Manual",
|
||||
"source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-06D5442F-AE4E-4DD9-969E-34E1A20C80EC.html",
|
||||
"topic_cluster": {
|
||||
"clustering_title": "To create a Tenant Role:",
|
||||
"clustered_topics": [
|
||||
{
|
||||
"bundle_id": "morpheus_user_manual_8_1_1",
|
||||
"page_id": "GUID-06D5442F-AE4E-4DD9-969E-34E1A20C80EC",
|
||||
"clustering_title": "To create a Tenant Role:"
|
||||
},
|
||||
{
|
||||
"bundle_id": "morpheus_user_manual_8_1_2",
|
||||
"page_id": "GUID-06D5442F-AE4E-4DD9-969E-34E1A20C80EC",
|
||||
"clustering_title": "To create a Tenant Role:"
|
||||
}
|
||||
]
|
||||
}
|
||||
}
|
||||
@@ -0,0 +1,14 @@
|
||||
# To create a Tenant Role:
|
||||
|
||||
## Procedure
|
||||
|
||||
1. In the Master Account, navigate to Administration > Roles
|
||||
2. Select + CREATE ROLE
|
||||
3. Enter a name for the Role and optional Description
|
||||
4. For TYPE, select “Tenant Role”
|
||||
5. Optionally select an existing Role to copy in the COPY FROM ROLE dropdown. \* This will configure the new Role with the same configuration as the selected role to copy. A new role that is not copied from another role will be generated with all permissions set to NONE.
|
||||
6. Select SAVE CHANGES
|
||||
|
||||
## Results
|
||||
|
||||
After saving, the Role will be created and you will be redirected to the Roles Permissions settings.
|
||||
@@ -0,0 +1,26 @@
|
||||
{
|
||||
"bundle_id": "morpheus_user_manual_8_1_0",
|
||||
"page_id": "GUID-06F0DB01-64F2-4D07-93F8-38AC80DBB09B",
|
||||
"title": "Workloads: Blueprint Usage",
|
||||
"ordinal": 69,
|
||||
"parent_title": "Analytics",
|
||||
"doc_id": "sd00007510en_us",
|
||||
"version": "8.1.0",
|
||||
"product": "User Manual",
|
||||
"source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-06F0DB01-64F2-4D07-93F8-38AC80DBB09B.html",
|
||||
"topic_cluster": {
|
||||
"clustering_title": "Workloads: Blueprint Usage",
|
||||
"clustered_topics": [
|
||||
{
|
||||
"bundle_id": "morpheus_user_manual_8_1_1",
|
||||
"page_id": "GUID-06F0DB01-64F2-4D07-93F8-38AC80DBB09B",
|
||||
"clustering_title": "Workloads: Blueprint Usage"
|
||||
},
|
||||
{
|
||||
"bundle_id": "morpheus_user_manual_8_1_2",
|
||||
"page_id": "GUID-06F0DB01-64F2-4D07-93F8-38AC80DBB09B",
|
||||
"clustering_title": "Workloads: Blueprint Usage"
|
||||
}
|
||||
]
|
||||
}
|
||||
}
|
||||
@@ -0,0 +1,32 @@
|
||||
# Workloads: Blueprint Usage
|
||||
|
||||
|
||||
|
||||
The Blueprint Usage dashboard lists all provisioned Apps that meet filters set on the dashboard. Once the desired group of Apps is filtered into the dashboard, administrators will see the total provisioned from each Blueprint, total number of Instances created from the Apps, and costing details.
|
||||
|
||||
## Filters
|
||||
|
||||
Filter the Apps pulled into the dashboard by one or more of the following fields:
|
||||
|
||||
- App name (all matching search terms)
|
||||
- Metric (apply to see the top Clouds by workload count, price, memory, storage, or CPU cores)
|
||||
- Group
|
||||
- Cloud
|
||||
- Tenant
|
||||
- Tag (Key)
|
||||
- Value (Tag value)
|
||||
|
||||
## Data Displayed
|
||||
|
||||
The following aggregate totals are compiled for Apps that meet set filters:
|
||||
|
||||
- **TYPES:** The total number of App types represented among Apps meeting the dashboard filters
|
||||
- **APPS:** The total number of Apps represented in the dashboard
|
||||
- **INSTANCES:** The total number of Instances contained in all Apps meeting dashboard filters
|
||||
- **MONTH TO DATE:** The total month-to-date spend for all Apps shown in the dashboard
|
||||
- **MEMORY:** The total memory allotted to selected Apps
|
||||
- **STORAGE:** The total storage allotted to selected Apps
|
||||
|
||||
## Blueprint Usage List
|
||||
|
||||
All Blueprints which have a currently-existing App provisioned from them and selected in the dashboard filters are listed here. The name and type of the Blueprint is listed along with the total number of Instances across all provisionings, total Groups, total Clouds, and the total count of all Apps from that Blueprint.
|
||||
@@ -0,0 +1,26 @@
|
||||
{
|
||||
"bundle_id": "morpheus_user_manual_8_1_0",
|
||||
"page_id": "GUID-07A9C046-F9C9-4C39-BB10-1F2E9D96C2C2",
|
||||
"title": "Docker Clusters",
|
||||
"ordinal": 198,
|
||||
"parent_title": "Clusters",
|
||||
"doc_id": "sd00007510en_us",
|
||||
"version": "8.1.0",
|
||||
"product": "User Manual",
|
||||
"source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-07A9C046-F9C9-4C39-BB10-1F2E9D96C2C2.html",
|
||||
"topic_cluster": {
|
||||
"clustering_title": "Docker Clusters",
|
||||
"clustered_topics": [
|
||||
{
|
||||
"bundle_id": "morpheus_user_manual_8_1_1",
|
||||
"page_id": "GUID-07A9C046-F9C9-4C39-BB10-1F2E9D96C2C2",
|
||||
"clustering_title": "Docker Clusters"
|
||||
},
|
||||
{
|
||||
"bundle_id": "morpheus_user_manual_8_1_2",
|
||||
"page_id": "GUID-07A9C046-F9C9-4C39-BB10-1F2E9D96C2C2",
|
||||
"clustering_title": "Docker Clusters"
|
||||
}
|
||||
]
|
||||
}
|
||||
}
|
||||
@@ -0,0 +1,71 @@
|
||||
# Docker Clusters
|
||||
|
||||
## About this task
|
||||
|
||||
Provisions a new Docker Cluster managed by Morpheus.
|
||||
|
||||
To create a new Docker Cluster:
|
||||
|
||||
## Procedure
|
||||
|
||||
1. Navigate to Infrastructure > Clusters
|
||||
2. Select + ADD CLUSTER
|
||||
3. Select `Docker Cluster`
|
||||
4. Populate the following:
|
||||
|
||||
CLOUD
|
||||
: Select target Cloud
|
||||
|
||||
CLUSTER NAME
|
||||
: Name for the Docker Cluster
|
||||
|
||||
RESOURCE NAME
|
||||
: Name for Docker Cluster resources
|
||||
|
||||
DESCRIPTION
|
||||
: Description of the Cluster
|
||||
|
||||
VISIBILITY
|
||||
: Public
|
||||
: Available to all Tenants
|
||||
|
||||
Private
|
||||
: Available to Master Tenant
|
||||
|
||||
LABELS
|
||||
: Internal label(s)
|
||||
5. Select NEXT
|
||||
6. Populate the following (options depend on Cloud Selection and will vary):
|
||||
|
||||
LAYOUT
|
||||
: Select from available layouts.
|
||||
|
||||
PLAN
|
||||
: Select plan for Docker Host
|
||||
|
||||
VOLUMES
|
||||
: Configure volumes for Docker Host
|
||||
|
||||
NETWORKS
|
||||
: Select the network for Docker Master & Worker VM’s
|
||||
|
||||
NUMBER OF HOSTS
|
||||
: Specify the number of hosts to be created
|
||||
|
||||
User Config
|
||||
: CREATE YOUR USER
|
||||
: Select to create your user on provisioned hosts (requires Linux user config in HPE Morpheus Enterprise User Profile)
|
||||
|
||||
USER GROUP
|
||||
: Select User group to create users for all User Group members on provisioned hosts (requires Linux user config in HPE Morpheus Enterprise User Profile for all members of User Group)
|
||||
|
||||
Advanced Options
|
||||
: DOMAIN
|
||||
: Specify Domain for DNS records
|
||||
|
||||
HOSTNAME
|
||||
: Set hostname (defaults to Instance name)
|
||||
7. Select NEXT
|
||||
8. Select optional Workflow to execute
|
||||
9. Select NEXT
|
||||
10. Review and select COMPLETE
|
||||
@@ -0,0 +1,26 @@
|
||||
{
|
||||
"bundle_id": "morpheus_user_manual_8_1_0",
|
||||
"page_id": "GUID-08DC6ECF-EBF9-43E5-A402-D634F71D6B05",
|
||||
"title": "Volume Management",
|
||||
"ordinal": 441,
|
||||
"parent_title": "Storage Management",
|
||||
"doc_id": "sd00007510en_us",
|
||||
"version": "8.1.0",
|
||||
"product": "User Manual",
|
||||
"source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-08DC6ECF-EBF9-43E5-A402-D634F71D6B05.html",
|
||||
"topic_cluster": {
|
||||
"clustering_title": "Volume Management",
|
||||
"clustered_topics": [
|
||||
{
|
||||
"bundle_id": "morpheus_user_manual_8_1_1",
|
||||
"page_id": "GUID-08DC6ECF-EBF9-43E5-A402-D634F71D6B05",
|
||||
"clustering_title": "Volume Management"
|
||||
},
|
||||
{
|
||||
"bundle_id": "morpheus_user_manual_8_1_2",
|
||||
"page_id": "GUID-08DC6ECF-EBF9-43E5-A402-D634F71D6B05",
|
||||
"clustering_title": "Volume Management"
|
||||
}
|
||||
]
|
||||
}
|
||||
}
|
||||
@@ -0,0 +1,10 @@
|
||||
# Volume Management
|
||||
|
||||
Volume life cycle management can be performed under the Infrastructure > Storage > Volumes tab. It allows the user to perform create/resize/delete operations.
|
||||
|
||||
**Subtopics**
|
||||
|
||||
- **[Adding Volume](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-DD626086-0E0C-460D-85BC-8E654BEEF70A.html)**
|
||||
- **[Deleting Volume](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-E7DD5576-68E3-449D-8606-D2861BF53808.html)**
|
||||
- **[Resizing Volume](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-21AB08DA-EAEF-46C2-8880-8CBC18BC8010.html)**
|
||||
- **[Reconfiguring Volume](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-F6459690-0DE9-48CE-95B2-C7BE033E8088.html)**
|
||||
@@ -0,0 +1,26 @@
|
||||
{
|
||||
"bundle_id": "morpheus_user_manual_8_1_0",
|
||||
"page_id": "GUID-092B4E74-3662-4E21-9DA0-67958362DBE4",
|
||||
"title": "Adding OpenShift Clusters",
|
||||
"ordinal": 206,
|
||||
"parent_title": "OpenShift Clusters",
|
||||
"doc_id": "sd00007510en_us",
|
||||
"version": "8.1.0",
|
||||
"product": "User Manual",
|
||||
"source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-092B4E74-3662-4E21-9DA0-67958362DBE4.html",
|
||||
"topic_cluster": {
|
||||
"clustering_title": "Adding OpenShift Clusters",
|
||||
"clustered_topics": [
|
||||
{
|
||||
"bundle_id": "morpheus_user_manual_8_1_1",
|
||||
"page_id": "GUID-092B4E74-3662-4E21-9DA0-67958362DBE4",
|
||||
"clustering_title": "Adding OpenShift Clusters"
|
||||
},
|
||||
{
|
||||
"bundle_id": "morpheus_user_manual_8_1_2",
|
||||
"page_id": "GUID-092B4E74-3662-4E21-9DA0-67958362DBE4",
|
||||
"clustering_title": "Adding OpenShift Clusters"
|
||||
}
|
||||
]
|
||||
}
|
||||
}
|
||||
@@ -0,0 +1,24 @@
|
||||
# Adding OpenShift Clusters
|
||||
|
||||
NOTE
|
||||
|
||||
Adding an OpenShift cluster requires a pre-existing Group and Private Cloud-type Cloud. See Groups and Clouds documentation elsewhere in this user manual for more details on those constructs.
|
||||
|
||||
To onboard an OpenShift cluster, begin by collecting an API token and API URL from OpenShift. Bear in mind the integration user with HPE Morpheus Enterprise must be a full administrator user.
|
||||
|
||||
1. Log into the OpenShift console
|
||||
2. In the far top-right of the application window, click on the name of the logged in user to expand a small dropdown menu
|
||||
3. Click "Copy login command"
|
||||
4. Click "Display Token"
|
||||
5. On the resulting screen, both the API URL and the API token can be copied. You will need to enter these values directly into the "Add Cluster" modal within HPE Morpheus Enterprise in the next step
|
||||
|
||||
With the authentication details available, head back to HPE Morpheus Enterprise to add a new OpenShift cluster:
|
||||
|
||||
1. Navigate to Infrastructure > Clusters
|
||||
2. Click + Add Cluster
|
||||
3. Select "RED HAT OPENSHIFT CLUSTER" and click Next
|
||||
4. On the Group tab, select the HPE Morpheus Enterprise Group to associate with the cluster and click Next
|
||||
5. On the Name tab, you must at least configure a "Cluster Name" attribute and select a Cloud. The "Cluster Name" is a friendly name to identify the OpenShift cluster in HPE Morpheus Enterprise. The Cloud configuration requires you to select a pre-existing Private Cloud-type Cloud. There are optional configurations here as well, such as applying Labels or adding a description
|
||||
6. On the Configure tab, select the Layout that corresponds closest to the version of OpenShift running on the cluster. Integration with HPE Morpheus Enterprise requires OpenShift version 4.x at minimum. On this tab, you'll also enter the API URL and service token collected earlier. If "Inventory Existing Instances" is checked, HPE Morpheus Enterprise with automatically onboard any virtualized workloads which are currently running on the cluster and any that are provisioned directly from the OpenShift console in the future. Click Next
|
||||
7. On the Review tab, click Complete
|
||||
8. Within a short time, the new OpenShift cluster will appear on the clusters list page alongside any other cluster that may currently be running
|
||||
@@ -0,0 +1,26 @@
|
||||
{
|
||||
"bundle_id": "morpheus_user_manual_8_1_0",
|
||||
"page_id": "GUID-099A151A-FA2C-4C2C-B3C5-5E3DB3DFCDE9",
|
||||
"title": "Common Ports & Requirements",
|
||||
"ordinal": 349,
|
||||
"parent_title": "Troubleshooting",
|
||||
"doc_id": "sd00007510en_us",
|
||||
"version": "8.1.0",
|
||||
"product": "User Manual",
|
||||
"source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-099A151A-FA2C-4C2C-B3C5-5E3DB3DFCDE9.html",
|
||||
"topic_cluster": {
|
||||
"clustering_title": "Common Ports & Requirements",
|
||||
"clustered_topics": [
|
||||
{
|
||||
"bundle_id": "morpheus_user_manual_8_1_1",
|
||||
"page_id": "GUID-099A151A-FA2C-4C2C-B3C5-5E3DB3DFCDE9",
|
||||
"clustering_title": "Common Ports & Requirements"
|
||||
},
|
||||
{
|
||||
"bundle_id": "morpheus_user_manual_8_1_2",
|
||||
"page_id": "GUID-099A151A-FA2C-4C2C-B3C5-5E3DB3DFCDE9",
|
||||
"clustering_title": "Common Ports & Requirements"
|
||||
}
|
||||
]
|
||||
}
|
||||
}
|
||||
@@ -0,0 +1,22 @@
|
||||
# Common Ports & Requirements
|
||||
|
||||
The following chart is useful for troubleshooting Agent install, Static IP assignment, Remote Console connectivity, and Image transfers.
|
||||
|
||||
Table 1. Common Ports & Requirements
|
||||
|
||||
| Feature | Method | OS | Source | Destination | Port | Requirement |
|
||||
| --- | --- | --- | --- | --- | --- | --- |
|
||||
| Agent Communication | All | All | Node | Appliance | 443 | DNS Resolution from node to appliance url |
|
||||
| Agent Install | All | Linux | Node | Appliance | 80 | Used for appliance yum and apt repos |
|
||||
| | SSH | Linux | Appliance | Node | 22 | DNS Resolution from node to appliance url Virtual Images configured SSH Enabled on Virtual Image |
|
||||
| | WinRM | Windows | Appliance | Node | 5985 | DNS Resolution from node to appliance url Virtual Images configured WinRM Enabled on Virtual Image(winrm quickconfig) |
|
||||
| | Cloud‐init | Linux | | | | Cloud‐init installed on template/image Cloud‐init settings populated in User Settings or in Admin – > Provisioning Agent install mode set to Cloud‐Init in Cloud Settings |
|
||||
| | Cloudbase‐init | Windows | | | | Cloudbase‐init installed on template/image Cloud‐init settings populated in User Settings or in Admin – > Provisioning Agent install mode set to Cloud‐Init in Cloud Settings |
|
||||
| | VMtools | All | | | | VMtools installed on template Cloud‐init settings populated in Morpheus user settings or in Administration – > Provisioning when using Static IP’s Existing User credentials entered on Virtual Image when using DHCP RPC mode set to VMtools in VMware cloud settings. |
|
||||
| Static IP Assignment & IP Pools | Cloud‐Init | All | | | | Network configured in Morpheus (Gateway, Primary and Secondary DNS, CIDR populated, DHCP disabled) Cloud‐init/Cloudbase‐init installed on template/image Cloud‐init settings populated in Morpheus user settings or in Administration – > Provisioning |
|
||||
| | VMware Tools | All | | | | Network configured in Morpheus (Gateway, Primary and Secondary DNS, CIDR populated, DHCP disabled) VMtools installed on Template/Virtual Image |
|
||||
| Remote Console | SSH | Linux | Appliance | Node | 22 | ssh enabled on node | user/password set on VM or Host in Morpheus |
|
||||
| | RDP | Windows | Appliance | Node | 3389 | RDP Enabled on node | user/password set on VM or Host in Morpheus |
|
||||
| | Hypervisor Console | All | Appliance | Hypervisor Hosts | 443 | Hypervisor host names resolvable by morpheus appliance |
|
||||
| Morpheus Catalog Image Download | | All | Appliance | AWS S3 | 443 | Available space at `/var/opt/morpheus/` |
|
||||
| Image Transfer | Stream | All | Appliance | Datastore | 443 | Hypervisor Host Names resolvable by Morpheus Appliance |
|
||||
@@ -0,0 +1,26 @@
|
||||
{
|
||||
"bundle_id": "morpheus_user_manual_8_1_0",
|
||||
"page_id": "GUID-09A31CD3-8237-4668-8509-A1C2EA9F3775",
|
||||
"title": "Plans",
|
||||
"ordinal": 286,
|
||||
"parent_title": "Administration",
|
||||
"doc_id": "sd00007510en_us",
|
||||
"version": "8.1.0",
|
||||
"product": "User Manual",
|
||||
"source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-09A31CD3-8237-4668-8509-A1C2EA9F3775.html",
|
||||
"topic_cluster": {
|
||||
"clustering_title": "Plans",
|
||||
"clustered_topics": [
|
||||
{
|
||||
"bundle_id": "morpheus_user_manual_8_1_1",
|
||||
"page_id": "GUID-09A31CD3-8237-4668-8509-A1C2EA9F3775",
|
||||
"clustering_title": "Plans"
|
||||
},
|
||||
{
|
||||
"bundle_id": "morpheus_user_manual_8_1_2",
|
||||
"page_id": "GUID-09A31CD3-8237-4668-8509-A1C2EA9F3775",
|
||||
"clustering_title": "Plans"
|
||||
}
|
||||
]
|
||||
}
|
||||
}
|
||||
@@ -0,0 +1,8 @@
|
||||
# Plans
|
||||
|
||||
**Subtopics**
|
||||
|
||||
- **[Overview](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-F27780CE-E5E8-4E4E-B25A-328CB036BB49.html)**
|
||||
- **[Plans](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-C1E03C38-4DD6-43E9-8310-61A2FE452243.html)**
|
||||
- **[Price Sets](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-3BBE7B0E-83BD-4EC1-B4E5-CE2261569911.html)**
|
||||
- **[Prices](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-6B922BFB-DFAC-4617-8642-DDFDCEB5A775.html)**
|
||||
@@ -0,0 +1,26 @@
|
||||
{
|
||||
"bundle_id": "morpheus_user_manual_8_1_0",
|
||||
"page_id": "GUID-0A516D6F-CF1A-4470-8ABB-A7432A1E08D5",
|
||||
"title": "Environments",
|
||||
"ordinal": 327,
|
||||
"parent_title": "Settings",
|
||||
"doc_id": "sd00007510en_us",
|
||||
"version": "8.1.0",
|
||||
"product": "User Manual",
|
||||
"source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-0A516D6F-CF1A-4470-8ABB-A7432A1E08D5.html",
|
||||
"topic_cluster": {
|
||||
"clustering_title": "Environments",
|
||||
"clustered_topics": [
|
||||
{
|
||||
"bundle_id": "morpheus_user_manual_8_1_1",
|
||||
"page_id": "GUID-0A516D6F-CF1A-4470-8ABB-A7432A1E08D5",
|
||||
"clustering_title": "Environments"
|
||||
},
|
||||
{
|
||||
"bundle_id": "morpheus_user_manual_8_1_2",
|
||||
"page_id": "GUID-0A516D6F-CF1A-4470-8ABB-A7432A1E08D5",
|
||||
"clustering_title": "Environments"
|
||||
}
|
||||
]
|
||||
}
|
||||
}
|
||||
@@ -0,0 +1,34 @@
|
||||
# Environments
|
||||
|
||||
## Overview
|
||||
|
||||
The Environments section is where you create and manage your environment labels, which are available in the Environment dropdown during Instance or App provisioning. An Instance’s environment label can be changed by editing the Instance.
|
||||
|
||||
### Creating Environments
|
||||
|
||||
#### Procedure
|
||||
|
||||
1. Select + Create Environment
|
||||
2. Populate the following for the New Environment:
|
||||
|
||||
Name
|
||||
: The friendly name for the environment in HPE Morpheus Enterprise
|
||||
|
||||
Code
|
||||
: Shortcode used for API and CLI
|
||||
|
||||
Description
|
||||
: Environment description displayed on the Environments list page
|
||||
|
||||
Display Order
|
||||
: The order in which environments are presented when provisioning, a value of “0” will position the environment at the top of the list
|
||||
|
||||
Visibility
|
||||
: - Private: Available only in the Tenant the environment is created in
|
||||
- Public: Available for all Tenants. Public is only applicable for environments created in the the Master Tenant.
|
||||
|
||||
#### Results
|
||||
|
||||
NOTE
|
||||
|
||||
User-created environments can be edited, hidden, or removed from the Actions menu on the environments list page. HPE Morpheus Enterprise-default environments can only be hidden from users during provisioning.
|
||||
@@ -0,0 +1,26 @@
|
||||
{
|
||||
"bundle_id": "morpheus_user_manual_8_1_0",
|
||||
"page_id": "GUID-0A5AD977-07F5-4278-9CB3-F7D8AB8427A3",
|
||||
"title": "Wiki",
|
||||
"ordinal": 72,
|
||||
"parent_title": "Operations",
|
||||
"doc_id": "sd00007510en_us",
|
||||
"version": "8.1.0",
|
||||
"product": "User Manual",
|
||||
"source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-0A5AD977-07F5-4278-9CB3-F7D8AB8427A3.html",
|
||||
"topic_cluster": {
|
||||
"clustering_title": "Wiki",
|
||||
"clustered_topics": [
|
||||
{
|
||||
"bundle_id": "morpheus_user_manual_8_1_1",
|
||||
"page_id": "GUID-0A5AD977-07F5-4278-9CB3-F7D8AB8427A3",
|
||||
"clustering_title": "Wiki"
|
||||
},
|
||||
{
|
||||
"bundle_id": "morpheus_user_manual_8_1_2",
|
||||
"page_id": "GUID-0A5AD977-07F5-4278-9CB3-F7D8AB8427A3",
|
||||
"clustering_title": "Wiki"
|
||||
}
|
||||
]
|
||||
}
|
||||
}
|
||||
@@ -0,0 +1,50 @@
|
||||
# Wiki
|
||||
|
||||
The Morpheus Wiki is a tenant-wide, RBAC-controlled, auditable Wiki that allows easy UI, API and CLI access to information, notes, configurations or any other data needed to be referenced or shared with others. Wiki pages can be created directly from the Wiki tab of the detail page for various resource types, including Clouds, Groups, Servers, Instances, Clusters, and Self-Service Persona Catalog Items. Wiki pages created this way are automatically categorized under the appropriate resource type. Additional Wiki pages and custom categories can be created when viewing the whole Wiki at Operations > Wiki. Here you will also see the complete Wiki, including pages created on various object detail pages which are categorized appropriately.
|
||||
|
||||
|
||||
|
||||
## Highlights
|
||||
|
||||
- Main Wiki section is at Operations > Wiki
|
||||
- Wiki tabs are on Clouds, Groups, Instances, Hosts, VMs, Bare Metal, and Clusters detail pages
|
||||
- Additional Wiki Pages and Categories can be created from Operations > Wiki
|
||||
- When a Wiki tab is populated, a Page is automatically added and accessible at Operations > Wiki
|
||||
- One Wiki is created per Tenant. There is no multi-tenant access to Wikis
|
||||
- The Wiki is accessible from the UI, CLI and API.
|
||||
- Wiki access is RBAC-controlled via the Operations: Wiki permission in User and Tenant Roles (None, Read and Full)
|
||||
- Page updates are stamped with the “Last Updated By” user and the time the edit was made
|
||||
- Wiki pages can be searched from `/operations/wiki` or navigated from `/operations/wiki-page/page-index`
|
||||
- All wiki pages are encrypted using AES 256-bit encryption
|
||||
- Wiki pages use Flexmark for Markdown. Annotate your Wiki pages with headers, text styling, code blocks, hyperlinks, and more as needed
|
||||
- Create a new page with title “Home” to replace the default Wiki landing page that ships with HPE Morpheus Enterprise
|
||||
|
||||
NOTE
|
||||
|
||||
The Wiki replaces Notes. Notes are automatically migrated to corresponding Wiki pages when upgrading HPE Morpheus Enterprise to 4.0.0+.
|
||||
|
||||
## Creating Wikis
|
||||
|
||||
The Wiki service ties into assets throughout the environment. Create pages for Instances, hosts, groups, Clouds, and even clusters directly on their detail pages (see the Wiki tab). Users may also just create general notes pages in the centralized Wiki section (Operations > Wiki) in Markdown format.
|
||||
|
||||
Creating your first page is as simple as clicking the Create Page button from the Wiki home page (Operations > Wiki).
|
||||
|
||||
|
||||
|
||||
Write down some content, give the page a title, and click SAVE. The Wiki will also keep track of who last edited a page and when. The beauty of this Wiki is that it’s clean and easy to write down notes related to various parts of your application deployment or infrastructure without going to an external tool. Many HPE Morpheus Enterprise constructs, such as Instances, hosts, and more, also have their own Wiki page. Navigate to the detail page for the selected construct, open the Wiki tab, and click EDIT to add content.
|
||||
|
||||
IMPORTANT
|
||||
|
||||
All wiki pages are encrypted using AES-256 bit encryption. Though we don’t advise storing passwords in a Wiki document (services like Cypher are for that), role-based access control also can properly restrict access to content related to Instances or hosts which the user may not have access to.
|
||||
|
||||
## Hosting Images
|
||||
|
||||
It’s possible to add images to your Wiki pages and images can be sourced from the Internet, a Cloud storage bucket (like an AWS S3 Bucket), or even from files stored to the HPE Morpheus Enterprise appliance’s local file system. Within your Wiki page markdown, add your image using the following syntax:
|
||||
|
||||
```
|
||||
```
|
||||
|
||||
```
|
||||
```
|
||||
|
||||
The text within the square brackets [] sets the HTML “alt” description for the image and the URL within parentheses () is the “src” URL for the image. The HPE Morpheus Enterprise [Archives](https://docs.morpheusdata.com/en/latest/tools/archives.html) feature is a great resource for hosting images for use in Wiki. Archives can target cloud storage buckets or even file shares on the HPE Morpheus Enterprise appliance local storage. HPE Morpheus Enterprise generates an access URL for each file stored in Archives, simply target this URL in your markdown to show an image stored in HPE Morpheus Enterprise Archives within your Wiki pages.
|
||||
@@ -0,0 +1,26 @@
|
||||
{
|
||||
"bundle_id": "morpheus_user_manual_8_1_0",
|
||||
"page_id": "GUID-0BAF2FE9-97B1-4D4A-9525-ED355C24F870",
|
||||
"title": "Uploading OS Images Using NFS",
|
||||
"ordinal": 410,
|
||||
"parent_title": "Uploading OS Images",
|
||||
"doc_id": "sd00007510en_us",
|
||||
"version": "8.1.0",
|
||||
"product": "User Manual",
|
||||
"source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-0BAF2FE9-97B1-4D4A-9525-ED355C24F870.html",
|
||||
"topic_cluster": {
|
||||
"clustering_title": "Uploading OS Images Using NFS",
|
||||
"clustered_topics": [
|
||||
{
|
||||
"bundle_id": "morpheus_user_manual_8_1_1",
|
||||
"page_id": "GUID-0BAF2FE9-97B1-4D4A-9525-ED355C24F870",
|
||||
"clustering_title": "Uploading OS Images Using NFS"
|
||||
},
|
||||
{
|
||||
"bundle_id": "morpheus_user_manual_8_1_2",
|
||||
"page_id": "GUID-0BAF2FE9-97B1-4D4A-9525-ED355C24F870",
|
||||
"clustering_title": "Uploading OS Images Using NFS"
|
||||
}
|
||||
]
|
||||
}
|
||||
}
|
||||
@@ -0,0 +1,12 @@
|
||||
# Uploading OS Images Using NFS
|
||||
|
||||
## About this task
|
||||
|
||||
NFS allows OS images to be stored on a shared Linux file server.
|
||||
|
||||
## Procedure
|
||||
|
||||
1. Configure an NFSv3 file share under Infrastructure > Storage > File Shares.
|
||||
2. Provide valid credentials for the NFS share.
|
||||
3. Upload the OS ISO through Library > Virtual Images > Add > ISO.
|
||||
4. Verify the image is accessible for provisioning.
|
||||
@@ -0,0 +1,26 @@
|
||||
{
|
||||
"bundle_id": "morpheus_user_manual_8_1_0",
|
||||
"page_id": "GUID-0BBD18FA-91D0-406A-B004-3F068114DE70",
|
||||
"title": "Import Trusted Certificates",
|
||||
"ordinal": 35,
|
||||
"parent_title": "Additional Configuration Options",
|
||||
"doc_id": "sd00007510en_us",
|
||||
"version": "8.1.0",
|
||||
"product": "User Manual",
|
||||
"source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-0BBD18FA-91D0-406A-B004-3F068114DE70.html",
|
||||
"topic_cluster": {
|
||||
"clustering_title": "Import Trusted Certificates",
|
||||
"clustered_topics": [
|
||||
{
|
||||
"bundle_id": "morpheus_user_manual_8_1_1",
|
||||
"page_id": "GUID-0BBD18FA-91D0-406A-B004-3F068114DE70",
|
||||
"clustering_title": "Import Trusted Certificates"
|
||||
},
|
||||
{
|
||||
"bundle_id": "morpheus_user_manual_8_1_2",
|
||||
"page_id": "GUID-0BBD18FA-91D0-406A-B004-3F068114DE70",
|
||||
"clustering_title": "Import Trusted Certificates"
|
||||
}
|
||||
]
|
||||
}
|
||||
}
|
||||
@@ -0,0 +1,61 @@
|
||||
# Import Trusted Certificates
|
||||
|
||||
## About this task
|
||||
|
||||
IMPORTANT
|
||||
|
||||
The following applies to upgrades after modifying the java keystore.
|
||||
|
||||
Steps to import trusted certificates to HPE Morpheus Enterprise after an upgrade.
|
||||
|
||||
## Procedure
|
||||
|
||||
1. Obtain the full SSL certificate chain in PEM format.
|
||||
2. Copy them to each appliance and place them in the `/etc/morpheus/ssl/trusted_certs` directory.
|
||||
3. Run morpheus-ctl reconfigure on each appliance, note you don’t need to stop Morpheus before you run this.
|
||||
4. Run the following command as root:
|
||||
|
||||
```
|
||||
```
|
||||
export PATH=/opt/morpheus/sbin:/opt/morpheus/sbin:/opt/morpheus/embedded/sbin:/opt/morpheus/embedded/bin:$PATH
|
||||
```
|
||||
```
|
||||
5. Run the following command for each certificate in the chain, adjusting the file and alias name as needed. Answer yes for the root certificate when asked it you want to trust it.
|
||||
|
||||
```
|
||||
```
|
||||
/opt/morpheus/embedded/java/jre/bin/keytool -import -keystore /opt/morpheus/embedded/java/jre/lib/security/cacerts -trustcacerts -file /etc/morpheus/ssl/trusted_certs/root_ca.pem -alias some_alias -storepass changeit
|
||||
```
|
||||
```
|
||||
6. Verify by running:
|
||||
|
||||
```
|
||||
```
|
||||
openssl s_client -connect host:port -showcerts -tls1_2
|
||||
```
|
||||
```
|
||||
7. You should get an output similar to:
|
||||
|
||||
```
|
||||
```
|
||||
New, TLSv1/SSLv3, Cipher is ECDHE-RSA-AES256-GCM-SHA384
|
||||
Server public key is 2048 bit
|
||||
Secure Renegotiation IS supported
|
||||
No ALPN negotiated
|
||||
SSL-Session:
|
||||
Protocol : TLSv1.2
|
||||
Cipher : ECDHE-RSA-AES256-GCM-SHA384
|
||||
Session-ID: 5D9E820E4FF2A73A9977BA663E6029AA5415FEE85F49D8B1E541F5997C8E1FB2
|
||||
Session-ID-ctx:
|
||||
Master-Key: 29EEC2E7750C659AECB9942902D9A87B824E571522812B718420FC08F8D2ACE68CB16EC812A7D90B12A86D1970FFD81C
|
||||
Key-Arg : None
|
||||
PSK identity: None
|
||||
PSK identity hint: None
|
||||
SRP username: None
|
||||
Start Time: 1547219217
|
||||
Timeout : 7200 (sec)
|
||||
Verify return code: 0 (ok) #<----------------
|
||||
```
|
||||
```
|
||||
8. If the certificates are installed correctly you should see `Verify return code: 0 (ok)`. If they were not installed correctly then you will see a return similar to: `Verify return code: 21 (unable to verify the first certificate)`
|
||||
9. Repeat for all App Nodes
|
||||
@@ -0,0 +1,26 @@
|
||||
{
|
||||
"bundle_id": "morpheus_user_manual_8_1_0",
|
||||
"page_id": "GUID-0C0FBC8C-5C50-44CF-8872-9C47EF00A8AB",
|
||||
"title": "EfficientIP SOLIDserver",
|
||||
"ordinal": 516,
|
||||
"parent_title": "Networking Integrations",
|
||||
"doc_id": "sd00007510en_us",
|
||||
"version": "8.1.0",
|
||||
"product": "User Manual",
|
||||
"source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-0C0FBC8C-5C50-44CF-8872-9C47EF00A8AB.html",
|
||||
"topic_cluster": {
|
||||
"clustering_title": "EfficientIP SOLIDserver",
|
||||
"clustered_topics": [
|
||||
{
|
||||
"bundle_id": "morpheus_user_manual_8_1_1",
|
||||
"page_id": "GUID-0C0FBC8C-5C50-44CF-8872-9C47EF00A8AB",
|
||||
"clustering_title": "EfficientIP SOLIDserver"
|
||||
},
|
||||
{
|
||||
"bundle_id": "morpheus_user_manual_8_1_2",
|
||||
"page_id": "GUID-0C0FBC8C-5C50-44CF-8872-9C47EF00A8AB",
|
||||
"clustering_title": "EfficientIP SOLIDserver"
|
||||
}
|
||||
]
|
||||
}
|
||||
}
|
||||
@@ -0,0 +1,113 @@
|
||||
# EfficientIP SOLIDserver
|
||||
|
||||
## Features
|
||||
|
||||
- Network Pools synchronization
|
||||
- DNS Zone & Zone record synchronization
|
||||
- Host Record synchronization
|
||||
- Total & Free IP status bar for networks
|
||||
- Network Grid and List view with IP Status and records, date and user tracking
|
||||
- Automatic and manual IP Reservations, DNS A/PTR record creation and deletion
|
||||
|
||||
## Required Role Permissions
|
||||
|
||||
### Add, edit and remove EfficientIP SOLIDserver integrations
|
||||
|
||||
- Infrastructure: Network Integration: Full
|
||||
|
||||
### View and edit synced IP pools
|
||||
|
||||
- Infrastructure: Network IP Pools: Full
|
||||
|
||||
### View networks and add synced IP pools to networks
|
||||
|
||||
- Infrastructure: Networks: Full or Group
|
||||
|
||||
### View and edit synced DNS zones, including creation of zone records
|
||||
|
||||
- Infrastructure: Network Domains: Full
|
||||
|
||||
## Adding EfficientIP SOLIDserver Integration
|
||||
|
||||
### About this task
|
||||
|
||||
The EfficientIP SOLIDserver integration type is a plugin that must be added to HPE Morpheus Enterprise before the option to create one will be available. In the future, users will be able to download this and other plugin types from a centralized marketplace. For now, the plugin jar file can be compiled from a public Github repository or can be requested from your account team. See the [Plugins Section](https://docs.morpheusdata.com/en/latest/administration/integrations/integrations.html#plugins) of HPE Morpheus Enterprise documentation for more on the process of uploading the plugin JAR to your appliance.
|
||||
|
||||
### Procedure
|
||||
|
||||
1. Navigate to Infrastructure > Network > Integrations and click + ADD
|
||||
2. Under the IPAM section, select EfficientIP SOLIDserver
|
||||
3. Configure the following:
|
||||
|
||||
- NAME: Friendly name for this EfficientIP SOLIDserver integration
|
||||
- ENABLED: When checked, this integration will be accessible in HPE Morpheus Enterprise
|
||||
- API URL: The FQDN for the EfficientIP server, not a specific path
|
||||
- USERNAME: The username for an EfficientIP service account. Bear in mind this account will need API access as well as the rights to work with pools, zones, and records you wish to consume from HPE Morpheus Enterprise
|
||||
- PASSWORD: The password for the above named account
|
||||
- THROTTLE RATE: In larger environments, it may be necessary to introduce a rate limit on calls to the EfficientIP API from HPE Morpheus Enterprise. If the EfficientIP console UI becomes less responsive than it was prior to integration with HPE Morpheus Enterprise, it may be due to a high number of API calls in the background from HPE Morpheus Enterprise. In such a case, start with a 50ms throttle rate and adjust accordingly depending on performance
|
||||
- DISABLE SSL SNI VERIFICATION: If necessary, disable the check for a valid SSL certificate on the EfficientIP server
|
||||
- INVENTORY EXISTING: When checked, used IP space will be continually synced between HPE Morpheus Enterprise and EfficientIP. If left unchecked, only IP space claimed (and freed) from HPE Morpheus Enterprise is shown on the detail page for the EfficientIP pool
|
||||
4. Click SAVE CHANGES
|
||||
|
||||
### Results
|
||||
|
||||
Once saved, HPE Morpheus Enterprise will begin to onboard data from EfficientIP. EfficientIP networks are viewable in Infrastructure > Network > IP Pools under the IP Pools tab. Depending on EfficientIP configuration, you may see up to two “types” of Network Pools sync from EfficientIP, SOLIDserver Subnet and SOLIDserver Pool. In EfficientIP, “pools” are an optional construct that subdivides subnets. In HPE Morpheus Enterprise, both constructs are synced which gives an additional layer of organization when linking Network Pools with Networks (described in the next section) for organizations that use the pools construct. Within a selected IP Pool, host records will also sync and can be viewed in a grid or list layout. DNS Zones are synced under Infrastructure > Network > Domains. By clicking into the domain, DNS Zone records can be viewed.
|
||||
|
||||
|
||||
|
||||
## Adding IP Pools to Networks
|
||||
|
||||
### About this task
|
||||
|
||||
At provision time, HPE Morpheus Enterprise can automatically assign the next available IP address in an EfficientIP pool and create the corresponding DNS records. HPE Morpheus Enterprise can also clean up DNS records and free up IP address space on teardown. In order to enable this functionality, add an EfficientIP IP Pool as the Network Pool for an existing network (or networks).
|
||||
|
||||
### Procedure
|
||||
|
||||
1. Navigate to Infrastructure > Network > Networks
|
||||
2. Select a network to view the network detail page and click EDIT
|
||||
3. In the typeahead field for NETWORK POOL, search for and select the EfficientIP pool
|
||||
4. Click SAVE CHANGES
|
||||
|
||||
### Results
|
||||
|
||||
NOTE
|
||||
|
||||
Gateway, DNS and CIDR must be populated for static/pool IP assignment. If desired, select “Allow IP Override” to allow selecting between DHCP, Static entry, and pool selection at provision time. Finally, deselect “DHCP server” if a DHCP server will not be used on the network (only static and/or IP Pool assignment).
|
||||
|
||||
## Creating Host Records
|
||||
|
||||
### Procedure
|
||||
|
||||
1. Select an EfficientIP Network Pool from Infrastructure > Network > IP Pools
|
||||
2. Select + ADD
|
||||
3. Configure the following:
|
||||
|
||||
### Results
|
||||
|
||||
- **HOSTNAME:** The hostname for the record
|
||||
- **IP ADDRESS:** The IP address for the host record
|
||||
- **DOMAIN:** Select an EfficientIP zone
|
||||
- **CREATE DNS RECORDS:** If selected, DNS A and PTR records will be created in EfficientIP
|
||||
|
||||
1. Click SAVE CHANGES
|
||||
|
||||
|
||||
|
||||
## Creating Zone Records
|
||||
|
||||
### Procedure
|
||||
|
||||
1. Select an EfficientIP zone from the domains list at Infrastructure > Network > Domains
|
||||
2. Click + ADD on the Zone Records tab
|
||||
3. Configure the following:
|
||||
|
||||
### Results
|
||||
|
||||
- **NAME:** The name for the records (hostname)
|
||||
- **TYPE:** The record type: A, AAAA, CNAME, MX, NS, PTR, SOA, or TXT
|
||||
- **CONTENT:** The content of the record, such as IP address or A record
|
||||
- **TTL:** The time to live value
|
||||
|
||||
1. Click SAVE CHANGES
|
||||
|
||||
|
||||
@@ -0,0 +1,26 @@
|
||||
{
|
||||
"bundle_id": "morpheus_user_manual_8_1_0",
|
||||
"page_id": "GUID-0DB10170-9557-43A8-BF4B-76F2A2C25FBE",
|
||||
"title": "Common Ports & Requirements",
|
||||
"ordinal": 8,
|
||||
"parent_title": "Requirements",
|
||||
"doc_id": "sd00007510en_us",
|
||||
"version": "8.1.0",
|
||||
"product": "User Manual",
|
||||
"source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-0DB10170-9557-43A8-BF4B-76F2A2C25FBE.html",
|
||||
"topic_cluster": {
|
||||
"clustering_title": "Common Ports & Requirements",
|
||||
"clustered_topics": [
|
||||
{
|
||||
"bundle_id": "morpheus_user_manual_8_1_1",
|
||||
"page_id": "GUID-0DB10170-9557-43A8-BF4B-76F2A2C25FBE",
|
||||
"clustering_title": "Common Ports & Requirements"
|
||||
},
|
||||
{
|
||||
"bundle_id": "morpheus_user_manual_8_1_2",
|
||||
"page_id": "GUID-0DB10170-9557-43A8-BF4B-76F2A2C25FBE",
|
||||
"clustering_title": "Common Ports & Requirements"
|
||||
}
|
||||
]
|
||||
}
|
||||
}
|
||||
@@ -0,0 +1,22 @@
|
||||
# Common Ports & Requirements
|
||||
|
||||
The following chart is useful for troubleshooting Agent install, Static IP assignment, Remote Console connectivity, and Image transfers.
|
||||
|
||||
Table 1. Common Ports & Requirements
|
||||
|
||||
| Feature | Method | OS | Source | Destination | Port | Requirement |
|
||||
| --- | --- | --- | --- | --- | --- | --- |
|
||||
| Agent Communication | All | All | Node | Appliance | 443 | DNS Resolution from node to appliance url |
|
||||
| Agent Install | All | Linux | Node | Appliance | 80 | Used for appliance yum and apt repos |
|
||||
| | SSH | Linux | Appliance | Node | 22 | DNS Resolution from node to appliance url Virtual Images configured SSH Enabled on Virtual Image |
|
||||
| | WinRM | Windows | Appliance | Node | 5985 | Not required for agent installation in VMware vCenter and vCloud Director type clouds. Otherwise, access from HPE Morpheus Enterprise App Nodes to Instance Node on 5985 Virtual Images configured WinRM Enabled on Virtual Image(winrm quickconfig) |
|
||||
| | Cloud‐init | Linux | | | | Cloud‐init installed on template/image Cloud‐init settings populated in User Settings or in Administration > Settings > Provisioning Agent install mode set to Cloud‐Init in Cloud Settings |
|
||||
| | Cloudbase‐init | Windows | | | | Cloudbase‐init installed on template/image Cloud‐init settings populated in User Settings or in Administration > Settings > Provisioning Agent install mode set to Cloud‐Init in Cloud Settings |
|
||||
| | VMtools | All | | | | VMtools installed on template Cloud‐init settings populated in Morpheus user settings or in Administration > Settings > Provisioning when using Static IP’s Existing User credentials entered on Virtual Image when using DHCP RPC mode set to VMtools in VMware cloud settings. |
|
||||
| Static IP Assignment & IP Pools | Cloud‐Init | All | | | | Network configured in Morpheus (Gateway, Primary and Secondary DNS, CIDR populated, DHCP disabled) Cloud‐init/Cloudbase‐init installed on template/image Cloud‐init settings populated in Morpheus user settings or in Administration > Settings > Provisioning |
|
||||
| | VMware Tools | All | | | | Network configured in Morpheus (Gateway, Primary and Secondary DNS, CIDR populated, DHCP disabled) VMtools installed on Template/Virtual Image |
|
||||
| Remote Console | SSH | Linux | Appliance | Node | 22 | ssh enabled on node user/password set on VM or Host in Morpheus |
|
||||
| | RDP | Windows | Appliance | Node | 3389 | RDP Enabled on node user/password set on VM or Host in Morpheus |
|
||||
| | Hypervisor Console | All | Appliance | Hypervisor Hosts | 443 | Hypervisor host names resolvable by morpheus appliance |
|
||||
| Morpheus Catalog Image Download | | All | Appliance | AWS S3 | 443 | Available space at `/var/opt/morpheus/` |
|
||||
| Image Transfer | Stream | All | Appliance | Datastore | 443 | Hypervisor Host Names resolvable by Morpheus Appliance |
|
||||
@@ -0,0 +1,26 @@
|
||||
{
|
||||
"bundle_id": "morpheus_user_manual_8_1_0",
|
||||
"page_id": "GUID-0F66BE6C-8428-458C-BF0B-CD7C075ACC50",
|
||||
"title": "Adding HPE BMaaS Integration",
|
||||
"ordinal": 400,
|
||||
"parent_title": "Compute Management",
|
||||
"doc_id": "sd00007510en_us",
|
||||
"version": "8.1.0",
|
||||
"product": "User Manual",
|
||||
"source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-0F66BE6C-8428-458C-BF0B-CD7C075ACC50.html",
|
||||
"topic_cluster": {
|
||||
"clustering_title": "Adding HPE BMaaS Integration",
|
||||
"clustered_topics": [
|
||||
{
|
||||
"bundle_id": "morpheus_user_manual_8_1_1",
|
||||
"page_id": "GUID-0F66BE6C-8428-458C-BF0B-CD7C075ACC50",
|
||||
"clustering_title": "Adding HPE BMaaS Integration"
|
||||
},
|
||||
{
|
||||
"bundle_id": "morpheus_user_manual_8_1_2",
|
||||
"page_id": "GUID-0F66BE6C-8428-458C-BF0B-CD7C075ACC50",
|
||||
"clustering_title": "Adding HPE BMaaS Integration"
|
||||
}
|
||||
]
|
||||
}
|
||||
}
|
||||
@@ -0,0 +1,21 @@
|
||||
# Adding HPE BMaaS Integration
|
||||
|
||||
## Prerequisites
|
||||
|
||||
This procedure describes how to integrate the HPE BMaaS with your Morpheus Enterprise environment.
|
||||
|
||||
## About this task
|
||||
|
||||
To install the **HPE BMaaS** plugin, perform the following steps:
|
||||
|
||||
## Procedure
|
||||
|
||||
1. Log in to the HPE Morpheus Enterprise Software web interface using your administrator credentials.
|
||||
2. Navigate to Administration > Integrations.
|
||||
3. Select the Plugins tab and click Add button.
|
||||
4. Drag the HPE BMaaS `JAR` file into the Drop Files Here area, or click Add File to select it manually. 
|
||||
5. Click the Upload.
|
||||
|
||||
## Results
|
||||
|
||||
After a successful upload, the HPE BMaaS is available for use.
|
||||
@@ -0,0 +1,26 @@
|
||||
{
|
||||
"bundle_id": "morpheus_user_manual_8_1_0",
|
||||
"page_id": "GUID-10176AA6-4AAE-4480-98BE-D1E4FF3DBB2E",
|
||||
"title": "Creating and Running an SPP Update Job",
|
||||
"ordinal": 425,
|
||||
"parent_title": "Firmware and Driver Lifecycle Management",
|
||||
"doc_id": "sd00007510en_us",
|
||||
"version": "8.1.0",
|
||||
"product": "User Manual",
|
||||
"source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-10176AA6-4AAE-4480-98BE-D1E4FF3DBB2E.html",
|
||||
"topic_cluster": {
|
||||
"clustering_title": "Creating and Running an SPP Update Job",
|
||||
"clustered_topics": [
|
||||
{
|
||||
"bundle_id": "morpheus_user_manual_8_1_1",
|
||||
"page_id": "GUID-10176AA6-4AAE-4480-98BE-D1E4FF3DBB2E",
|
||||
"clustering_title": "Creating and Running an SPP Update Job"
|
||||
},
|
||||
{
|
||||
"bundle_id": "morpheus_user_manual_8_1_2",
|
||||
"page_id": "GUID-10176AA6-4AAE-4480-98BE-D1E4FF3DBB2E",
|
||||
"clustering_title": "Creating and Running an SPP Update Job"
|
||||
}
|
||||
]
|
||||
}
|
||||
}
|
||||
@@ -0,0 +1,54 @@
|
||||
# Creating and Running an SPP Update Job
|
||||
|
||||
## About this task
|
||||
|
||||
This procedure describes how to create and execute a HPE Morpheus Job to perform firmware and driver updates using an HPE SPP image.
|
||||
|
||||
## Procedure
|
||||
|
||||
1. Navigate to Provisioning > Jobs.
|
||||
2. Click Add.
|
||||
3. Enter a name for the job.
|
||||
|
||||
NOTE
|
||||
|
||||
- Separate jobs are required for different server generations (for example, Gen10 vs Gen11).
|
||||
- Create separate jobs for **Dry Run** and **Deploy** executions.
|
||||
4. Select Workflow Job as the Job Type and click Next.
|
||||
5. Select Deploy SPP as the workflow.
|
||||
6. Enter the SPPVIRTUALIMAGE value using the ID of the Virtual Image created earlier.
|
||||
7. Select a DEPLOYMODE:
|
||||
|
||||
- `DryRun`: Performs inventory only
|
||||
- `Deploy`: Applies firmware and/or driver updates
|
||||
8. For SPP Deploy Content, choose one of the following:
|
||||
|
||||
- Firmware only
|
||||
- Drivers only
|
||||
- Firmware and Drivers
|
||||
|
||||
NOTE
|
||||
|
||||
Driver inventory and updates require iSUT and AMS to be running on the target servers.
|
||||
9. In the Nodes field, enter the iLO details for each target server in JSON format (minimum 1 server, maximum 30 servers). For example:
|
||||
|
||||
```
|
||||
```
|
||||
[
|
||||
{
|
||||
"ilo_ip":"1.2.3.4",
|
||||
"ilo_user":"user1",
|
||||
"ilo_password":"password1"
|
||||
},
|
||||
{
|
||||
"ilo_ip":"1.2.3.5",
|
||||
"ilo_user":"user2",
|
||||
"ilo_password":"password2"
|
||||
}
|
||||
]
|
||||
```
|
||||
```
|
||||
10. **Optional:** Create a schedule, or leave the job as Manual.
|
||||
11. Select Run Now if you want to execute the job immediately.
|
||||
12. Click Next, review the settings, and click Complete.
|
||||
13. If the job was not run immediately, click the **gear icon** next to the job and select Execute.
|
||||
@@ -0,0 +1,26 @@
|
||||
{
|
||||
"bundle_id": "morpheus_user_manual_8_1_0",
|
||||
"page_id": "GUID-101B0634-4367-4B11-ACA0-923AC1CA635E",
|
||||
"title": "Jobs",
|
||||
"ordinal": 91,
|
||||
"parent_title": "Jobs",
|
||||
"doc_id": "sd00007510en_us",
|
||||
"version": "8.1.0",
|
||||
"product": "User Manual",
|
||||
"source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-101B0634-4367-4B11-ACA0-923AC1CA635E.html",
|
||||
"topic_cluster": {
|
||||
"clustering_title": "Jobs",
|
||||
"clustered_topics": [
|
||||
{
|
||||
"bundle_id": "morpheus_user_manual_8_1_1",
|
||||
"page_id": "GUID-101B0634-4367-4B11-ACA0-923AC1CA635E",
|
||||
"clustering_title": "Jobs"
|
||||
},
|
||||
{
|
||||
"bundle_id": "morpheus_user_manual_8_1_2",
|
||||
"page_id": "GUID-101B0634-4367-4B11-ACA0-923AC1CA635E",
|
||||
"clustering_title": "Jobs"
|
||||
}
|
||||
]
|
||||
}
|
||||
}
|
||||
@@ -0,0 +1,19 @@
|
||||
# Jobs
|
||||
|
||||
## Required Role Permissions
|
||||
|
||||
Provisioning: Jobs
|
||||
|
||||
- **None:** Cannot access Provisioning > Jobs > Jobs tab
|
||||
- **Read:** Can access Provisioning > Jobs > Jobs tab but cannot create, edit, or delete Jobs
|
||||
- **Full:** Full permissions to create, view, edit, and delete Jobs
|
||||
|
||||
Provisioning: Job Executions
|
||||
|
||||
- **None:** Cannot access Provisioning > Jobs > Job Executions tab
|
||||
- **Read:** Can access and view Provisioning > Jobs > Job Executions tab including job execution history, status, and Job output
|
||||
|
||||
**Subtopics**
|
||||
|
||||
- **[Creating Jobs](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-1F166B04-8BE6-4EF5-82A5-6C981695EC24.html)**
|
||||
- **[Creating and Running Security Scan Jobs](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-D7BD39F5-E0A0-4A89-84C9-CF1443E428D9.html)**
|
||||
@@ -0,0 +1,26 @@
|
||||
{
|
||||
"bundle_id": "morpheus_user_manual_8_1_0",
|
||||
"page_id": "GUID-10BE13E9-1014-4162-97E7-A1056FED89B3",
|
||||
"title": "Clients",
|
||||
"ordinal": 326,
|
||||
"parent_title": "Settings",
|
||||
"doc_id": "sd00007510en_us",
|
||||
"version": "8.1.0",
|
||||
"product": "User Manual",
|
||||
"source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-10BE13E9-1014-4162-97E7-A1056FED89B3.html",
|
||||
"topic_cluster": {
|
||||
"clustering_title": "Clients",
|
||||
"clustered_topics": [
|
||||
{
|
||||
"bundle_id": "morpheus_user_manual_8_1_1",
|
||||
"page_id": "GUID-10BE13E9-1014-4162-97E7-A1056FED89B3",
|
||||
"clustering_title": "Clients"
|
||||
},
|
||||
{
|
||||
"bundle_id": "morpheus_user_manual_8_1_2",
|
||||
"page_id": "GUID-10BE13E9-1014-4162-97E7-A1056FED89B3",
|
||||
"clustering_title": "Clients"
|
||||
}
|
||||
]
|
||||
}
|
||||
}
|
||||
@@ -0,0 +1,24 @@
|
||||
# Clients
|
||||
|
||||
## Overview
|
||||
|
||||
HPE Morpheus Enterprise includes pre-configured OAuth clients and allows the user to create as many additional clients as they’d like. The pre-configured clients are editable but cannot be deleted. Once configured, access tokens may be generated or re-generated from the [API Access section](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-2C366D1B-0426-4F6D-9A1B-CDF97B468FED.html). Their expiration times may be viewed as well. Client settings are available only in the Primary Tenant and affect all Tenants.
|
||||
|
||||
## Creating an OAuth Client
|
||||
|
||||
To create a new OAuth Client, click + ADD and configure the following:
|
||||
|
||||
- **CLIENT ID:** A reference name for the client in HPE Morpheus Enterprise
|
||||
- **SECRET:** An optional OAuth client secret
|
||||
- **ACCESS TOKEN VALIDITY INTERVAL (SECONDS):** The length of time (in seconds) during which the token should be enabled
|
||||
- **REFRESH TOKEN VALIDITY INTERVAL (SECONDS):** The length of time (in seconds) during which the refresh token should be enabled
|
||||
|
||||
Once the client is configured, click SAVE CHANGES.
|
||||
|
||||
## Editing and Deleting OAuth Clients
|
||||
|
||||
From the OAuth client list view (Administration > Settings > Clients), click the pencil (✎) or trash can (🗑) icons to edit or delete the OAuth Client.
|
||||
|
||||
NOTE
|
||||
|
||||
Pre-configured HPE Morpheus Enterprise-default clients may be edited but not deleted. User-created clients may be edited or deleted.
|
||||
@@ -0,0 +1,26 @@
|
||||
{
|
||||
"bundle_id": "morpheus_user_manual_8_1_0",
|
||||
"page_id": "GUID-10D04894-711A-400A-98A7-A3DECE437CDA",
|
||||
"title": "Creating Service Plans for GPU Hardware Passthrough",
|
||||
"ordinal": 194,
|
||||
"parent_title": "Hardware Passthrough",
|
||||
"doc_id": "sd00007510en_us",
|
||||
"version": "8.1.0",
|
||||
"product": "User Manual",
|
||||
"source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-10D04894-711A-400A-98A7-A3DECE437CDA.html",
|
||||
"topic_cluster": {
|
||||
"clustering_title": "Creating Service Plans for GPU Hardware Passthrough",
|
||||
"clustered_topics": [
|
||||
{
|
||||
"bundle_id": "morpheus_user_manual_8_1_1",
|
||||
"page_id": "GUID-10D04894-711A-400A-98A7-A3DECE437CDA",
|
||||
"clustering_title": "Creating Service Plans for GPU Hardware Passthrough"
|
||||
},
|
||||
{
|
||||
"bundle_id": "morpheus_user_manual_8_1_2",
|
||||
"page_id": "GUID-10D04894-711A-400A-98A7-A3DECE437CDA",
|
||||
"clustering_title": "Creating Service Plans for GPU Hardware Passthrough"
|
||||
}
|
||||
]
|
||||
}
|
||||
}
|
||||
@@ -0,0 +1,7 @@
|
||||
# Creating Service Plans for GPU Hardware Passthrough
|
||||
|
||||
When utilizing GPU hardware, it may be most convenient to use a custom Service Plan. This allows administrators to pre-configure the number of discrete hardware cards to attach to the VM at provision time. Once provisioned, the specified number of GPUs will be attached to the VM. For workloads which are provisioned and torn down regularly, this will save additional steps of manually attaching GPUs available from the pool. On teardown, attached devices of all types are released back to the pool. Though in some cases utilizing Service Plans may be most convenient, as you’ll see in the next sections it is not strictly required. It is also possible to manually attach GPUs or other hardware types on any existing VMs running on the HVM Cluster.
|
||||
|
||||
To create a new Service Plan, navigate to Administration > Plans. Click + Add and then Service Plan. In the New Service Plan modal, first set the PROVISION TYPE configuration to “KVM.” This will update the available configuration fields and reveal the GPU COUNT configuration. Use this configuration to set the number of GPU hardware cards which should be attached to provisioned VMs using this Service Plan. All other configuration fields for Service Plans go beyond the scope of this section. When finished, click SAVE CHANGES.
|
||||
|
||||
|
||||
@@ -0,0 +1,26 @@
|
||||
{
|
||||
"bundle_id": "morpheus_user_manual_8_1_0",
|
||||
"page_id": "GUID-1191CCE3-E610-468E-95EE-ED08BA64A6BA",
|
||||
"title": "Blueprints",
|
||||
"ordinal": 125,
|
||||
"parent_title": "Library",
|
||||
"doc_id": "sd00007510en_us",
|
||||
"version": "8.1.0",
|
||||
"product": "User Manual",
|
||||
"source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-1191CCE3-E610-468E-95EE-ED08BA64A6BA.html",
|
||||
"topic_cluster": {
|
||||
"clustering_title": "Blueprints",
|
||||
"clustered_topics": [
|
||||
{
|
||||
"bundle_id": "morpheus_user_manual_8_1_1",
|
||||
"page_id": "GUID-1191CCE3-E610-468E-95EE-ED08BA64A6BA",
|
||||
"clustering_title": "Blueprints"
|
||||
},
|
||||
{
|
||||
"bundle_id": "morpheus_user_manual_8_1_2",
|
||||
"page_id": "GUID-1191CCE3-E610-468E-95EE-ED08BA64A6BA",
|
||||
"clustering_title": "Blueprints"
|
||||
}
|
||||
]
|
||||
}
|
||||
}
|
||||
@@ -0,0 +1,12 @@
|
||||
# Blueprints
|
||||
|
||||
**Subtopics**
|
||||
|
||||
- **[Overview](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-C7D69012-9F80-4ACD-9F6D-985E827DE63D.html)**
|
||||
- **[Blueprint Development Overview](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-C216CC1D-C5ED-4FE8-BCC0-3E3E9870A704.html)**
|
||||
- **[Instance Types](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-6B0F9AE1-F0B9-4E4A-A444-833E9A4BA49C.html)**
|
||||
- **[Layouts](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-A1BFF247-858B-4915-BBF1-FC8CDEA5C8F0.html)**
|
||||
- **[Node Types](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-75D89535-68AE-4507-A961-26CE8914F074.html)**
|
||||
- **[App Blueprints](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-133E4178-5B4C-4BFF-8213-2662774F0B37.html)**
|
||||
- **[Catalog Items](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-A5363EB4-95EC-4901-82B6-4B15C6A7948A.html)**
|
||||
- **[Cluster Layouts](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-A47333AC-3343-485B-BF3D-6C7C71F0F89C.html)**
|
||||
@@ -0,0 +1,26 @@
|
||||
{
|
||||
"bundle_id": "morpheus_user_manual_8_1_0",
|
||||
"page_id": "GUID-12450828-47CC-4F83-9E94-AF80242C2E3A",
|
||||
"title": "Linux Settings",
|
||||
"ordinal": 336,
|
||||
"parent_title": "User Settings",
|
||||
"doc_id": "sd00007510en_us",
|
||||
"version": "8.1.0",
|
||||
"product": "User Manual",
|
||||
"source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-12450828-47CC-4F83-9E94-AF80242C2E3A.html",
|
||||
"topic_cluster": {
|
||||
"clustering_title": "Linux Settings",
|
||||
"clustered_topics": [
|
||||
{
|
||||
"bundle_id": "morpheus_user_manual_8_1_1",
|
||||
"page_id": "GUID-12450828-47CC-4F83-9E94-AF80242C2E3A",
|
||||
"clustering_title": "Linux Settings"
|
||||
},
|
||||
{
|
||||
"bundle_id": "morpheus_user_manual_8_1_2",
|
||||
"page_id": "GUID-12450828-47CC-4F83-9E94-AF80242C2E3A",
|
||||
"clustering_title": "Linux Settings"
|
||||
}
|
||||
]
|
||||
}
|
||||
}
|
||||
@@ -0,0 +1,14 @@
|
||||
# Linux Settings
|
||||
|
||||
When provisioning a Linux-based resource and opting to have your user created during the provisioning process, the credentials entered in this section will be used to seed that user into the provisioned resource.
|
||||
|
||||
- **Username:** The username that will be used with your Linux user
|
||||
- **Password:** The password that will be used with your Linux user (optional if specifying key)
|
||||
- **Confirm:** Confirm your entered password. These must match in order for the new password value to be saved
|
||||
- **SSH Key:** Select a pre-existing SSH key pair object in Morpheus. Required of not specifying password and creating your user during provisioning, or required if ssh password authentication has been disabled.
|
||||
|
||||
WARNING
|
||||
|
||||
If your users Linux Settings password and/or key are not defined, and ‘Create User” is enabled during provisioning (default), a random password will be generated but not exposed and you will not be able to login with your user.
|
||||
|
||||
|
||||
@@ -0,0 +1,26 @@
|
||||
{
|
||||
"bundle_id": "morpheus_user_manual_8_1_0",
|
||||
"page_id": "GUID-127B939B-0C18-40CC-AC49-8DD0D58BE444",
|
||||
"title": "Spec Templates",
|
||||
"ordinal": 159,
|
||||
"parent_title": "Templates",
|
||||
"doc_id": "sd00007510en_us",
|
||||
"version": "8.1.0",
|
||||
"product": "User Manual",
|
||||
"source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-127B939B-0C18-40CC-AC49-8DD0D58BE444.html",
|
||||
"topic_cluster": {
|
||||
"clustering_title": "Spec Templates",
|
||||
"clustered_topics": [
|
||||
{
|
||||
"bundle_id": "morpheus_user_manual_8_1_1",
|
||||
"page_id": "GUID-127B939B-0C18-40CC-AC49-8DD0D58BE444",
|
||||
"clustering_title": "Spec Templates"
|
||||
},
|
||||
{
|
||||
"bundle_id": "morpheus_user_manual_8_1_2",
|
||||
"page_id": "GUID-127B939B-0C18-40CC-AC49-8DD0D58BE444",
|
||||
"clustering_title": "Spec Templates"
|
||||
}
|
||||
]
|
||||
}
|
||||
}
|
||||
@@ -0,0 +1,35 @@
|
||||
# Spec Templates
|
||||
|
||||
Spec Templates allow HPE Morpheus Enterprise users to leverage several major Infrastructure-as-Code solutions. These are typically JSON or YAML-based configuration files which make creating and managing multiple resource types easier. HPE Morpheus Enterprise allows users to create and/or manage a collection of these templates for different solutions and from different sources.
|
||||
|
||||
HPE Morpheus Enterprise currently supports Spec Templates of the following types:
|
||||
|
||||
- Kubernetes Spec
|
||||
- Helm Chart
|
||||
- Terraform
|
||||
- ARM Template
|
||||
- CloudFormation Template
|
||||
- OneView Server Profile Template
|
||||
- UCS Service Profile Template
|
||||
|
||||
HPE Morpheus Enterprise also allows users to leverage templates pulled from URL sources, online repositories (such as GitHub), or you can write a template locally inside the “NEW SPEC TEMPLATE” modal.
|
||||
|
||||
TIP
|
||||
|
||||
To see HPE Morpheus Enterprise Spec Templates in action, take a look at our guide on [creating custom Instance Types using Terraform](https://docs.morpheusdata.com/en/latest/getting_started/guides/terraform_instances.html) or see our [KnowledgeBase](https://support.morpheusdata.com/s/article/How-to-use-Spec-Templates-to-create-a-custom-instance-type?language=en_US) for another example where a CloudFormation Spec Template is used to create a provisionable custom Instance Type.
|
||||
|
||||
## Creating a Spec Template
|
||||
|
||||
### Procedure
|
||||
|
||||
1. Navigate to Library > Templates > Spec Templates
|
||||
2. Click + ADD
|
||||
3. Complete the following fields, then click SAVE CHANGES:
|
||||
|
||||
### Results
|
||||
|
||||
- **NAME**
|
||||
- **TYPE:** See the previous section for a complete list of Spec Template types
|
||||
- **SOURCE:** Local, Repository, or URL
|
||||
- **CONTENT:** If this is a local Spec Template, supply the template in this field. If the template is supplied through a URL or online repository, the CONTENT field will change to allow the user to point HPE Morpheus Enterprise to that resource
|
||||
- **VERSION:** (Only displayed on Terraform Spec Templates) Enter a Terraform version number to force a specific version when provisioning your Terraform Instance Type or App, assuming your Terraform Runtime setting (Administration > Settings > Provisioning Tab) is “auto”. If Terraform Runtime is set to “manual”, HPE Morpheus Enterprise will use the version of Terraform installed on the appliance box
|
||||
@@ -0,0 +1,26 @@
|
||||
{
|
||||
"bundle_id": "morpheus_user_manual_8_1_0",
|
||||
"page_id": "GUID-133E4178-5B4C-4BFF-8213-2662774F0B37",
|
||||
"title": "App Blueprints",
|
||||
"ordinal": 131,
|
||||
"parent_title": "Blueprints",
|
||||
"doc_id": "sd00007510en_us",
|
||||
"version": "8.1.0",
|
||||
"product": "User Manual",
|
||||
"source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-133E4178-5B4C-4BFF-8213-2662774F0B37.html",
|
||||
"topic_cluster": {
|
||||
"clustering_title": "App Blueprints",
|
||||
"clustered_topics": [
|
||||
{
|
||||
"bundle_id": "morpheus_user_manual_8_1_1",
|
||||
"page_id": "GUID-133E4178-5B4C-4BFF-8213-2662774F0B37",
|
||||
"clustering_title": "App Blueprints"
|
||||
},
|
||||
{
|
||||
"bundle_id": "morpheus_user_manual_8_1_2",
|
||||
"page_id": "GUID-133E4178-5B4C-4BFF-8213-2662774F0B37",
|
||||
"clustering_title": "App Blueprints"
|
||||
}
|
||||
]
|
||||
}
|
||||
}
|
||||
@@ -0,0 +1,20 @@
|
||||
# App Blueprints
|
||||
|
||||
App Blueprints support a vast array of providers and configurations with programmatic markup or Infrastructure as Code capabilities. Blueprints configs can be manually added or scoped to a git repo. HPE Morpheus Enterprise blueprints allows for full automation configuration, locked fields, tiered boots, and linked tiers with exported evars. All blueprints have permission settings for controlling group and tenant access.
|
||||
|
||||
App Blueprint Types
|
||||
: - HPE Morpheus Enterprise
|
||||
- Terraform
|
||||
- ARM (Azure)
|
||||
- CloudFormation (AWS)
|
||||
- Kubernetes
|
||||
- Helm
|
||||
|
||||
**Subtopics**
|
||||
|
||||
- **[ARM Blueprints](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-038058DD-CC8D-41F7-AF14-DB01B16993C4.html)**
|
||||
- **[CloudFormation Blueprints](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-EF20CD89-B756-4F84-BC6A-55B2488B5947.html)**
|
||||
- **[Helm Blueprints](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-E02DD704-C987-41BB-AF3F-A23F35C097BD.html)**
|
||||
- **[Kubernetes Blueprints](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-B9F1F6ED-F256-4222-B6F2-6EF83256928C.html)**
|
||||
- **[HPE Morpheus Enterprise Blueprints](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-8A5D661E-2FC1-45BC-8D78-3C7D62B139FD.html)**
|
||||
- **[Terraform Blueprints](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-46A53E20-D2A8-4233-8829-7865C7A434B7.html)**
|
||||
@@ -0,0 +1,26 @@
|
||||
{
|
||||
"bundle_id": "morpheus_user_manual_8_1_0",
|
||||
"page_id": "GUID-13940199-9CEA-485B-87AF-AB47536CD6AE",
|
||||
"title": "Huawei Cloud",
|
||||
"ordinal": 457,
|
||||
"parent_title": "Clouds",
|
||||
"doc_id": "sd00007510en_us",
|
||||
"version": "8.1.0",
|
||||
"product": "User Manual",
|
||||
"source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-13940199-9CEA-485B-87AF-AB47536CD6AE.html",
|
||||
"topic_cluster": {
|
||||
"clustering_title": "Huawei Cloud",
|
||||
"clustered_topics": [
|
||||
{
|
||||
"bundle_id": "morpheus_user_manual_8_1_1",
|
||||
"page_id": "GUID-13940199-9CEA-485B-87AF-AB47536CD6AE",
|
||||
"clustering_title": "Huawei Cloud"
|
||||
},
|
||||
{
|
||||
"bundle_id": "morpheus_user_manual_8_1_2",
|
||||
"page_id": "GUID-13940199-9CEA-485B-87AF-AB47536CD6AE",
|
||||
"clustering_title": "Huawei Cloud"
|
||||
}
|
||||
]
|
||||
}
|
||||
}
|
||||
@@ -0,0 +1,306 @@
|
||||
# Huawei Cloud
|
||||
|
||||
## Features
|
||||
|
||||
- Virtual machine provisioning
|
||||
- Backups
|
||||
- Brownfield VM management and migration
|
||||
- Hypervisor remote console
|
||||
- Cloud sync
|
||||
- Lifecycle management and resizing
|
||||
- Network security group creation
|
||||
- Network security group management
|
||||
- Router and network creation
|
||||
- Load balancer services
|
||||
- Docker host management and configuration
|
||||
- Floating IP assignment
|
||||
- Huawei OBS buckets (create, manage, delete, and discovery)
|
||||
- Huawei SFS (create, manage, and delete)
|
||||
|
||||
## Integrate Huawei Cloud with HPE Morpheus Enterprise
|
||||
|
||||
To integrate Huawei Cloud with HPE Morpheus Enterprise, we’ll gather the following pieces of information:
|
||||
|
||||
- Account Name
|
||||
- Identity (IAM) API URL
|
||||
- Project
|
||||
- Username
|
||||
- Password
|
||||
|
||||
Begin by logging into your [Huawei Cloud console](https://console-intl.huaweicloud.com/console). If you’re not currently logged in, you will be prompted to do so. Once on the console page, hover over your username in the upper-right corner of the application window and select “My Credentials”.
|
||||
|
||||
|
||||
|
||||
From the credentials page, we can gather the Account Name and the Project Name, record them for later when we provide the integration information to HPE Morpheus Enterprise.
|
||||
|
||||
|
||||
|
||||
To gather the API endpoint URL, take a look at the complete list of [endpoints](https://developer.huaweicloud.com/en-us/endpoint). If a specific endpoint exists for your region, use it. In any other case use the endpoint for all regions. It will be formatted like this: <https://iam.myhuaweicloud.com/v3>.
|
||||
|
||||
|
||||
|
||||
With this information gathered, and presuming you know the credentials for the service account you wish to use, we can move back into HPE Morpheus Enterprise-UI.
|
||||
|
||||
IMPORTANT
|
||||
|
||||
Integrating HPE Morpheus Enterprise with Huawei Cloud requires a service account that has programmatic access.
|
||||
|
||||
Navigate to Infrastructure > Clouds and click + ADD. Scroll to Huawei Cloud and click NEXT. The information we’ve gathered will be plugged into the CREATE CLOUD modal. The DOMAIN ID field will accept the Account Name field we gathered. Your completed CREATE CLOUD modal will look similar to the one pictured below:
|
||||
|
||||
|
||||
|
||||
After clicking NEXT, add this new Cloud to a Group or create a new Group. On finalizing the wizard, Huawei Cloud will be integrated into HPE Morpheus Enterprise and ready for provisioning. If you opted to inventory existing workloads, those will be onboarded shortly.
|
||||
|
||||
## Add/Edit Huawei Cloud Modal Fields
|
||||
|
||||
### Cloud Configuration
|
||||
|
||||
NAME
|
||||
: Name of the Cloud in HPE Morpheus Enterprise
|
||||
|
||||
CODE
|
||||
: Unique code used for api/cli, automation and policies.
|
||||
|
||||
LOCATION
|
||||
: Description field for adding notes on the cloud, such as location.
|
||||
|
||||
VISIBILITY
|
||||
: For setting cloud permissions in a multi-tenant environment. Not applicable in single tenant environments.
|
||||
|
||||
TENANT
|
||||
: If Visibility is set to Private, select the Tenant the Cloud resources will assigned to.
|
||||
|
||||
ENABLED
|
||||
: When disabled, automatic Cloud sync is paused and the Cloud will not be selectable for provisioning.
|
||||
|
||||
AUTOMATICALLY POWER ON VMS
|
||||
: When enabled, HPE Morpheus Enterprise will maintain the expected power state of managed VMs. HPE Morpheus Enterprise will power on any managed VMs in the Cloud that have been shut down for unknown reasons (not powered off by HPE Morpheus Enterprise) to ensure availability of services.
|
||||
|
||||
NOTE
|
||||
|
||||
When “AUTOMATICALLY POWER ON VMS” is enabled, the power state of managed VMs should be maintained in HPE Morpheus Enterprise. This setting is not applicable to discovered/unmanaged resources.
|
||||
|
||||
### Details
|
||||
|
||||
IDENTITY API URL
|
||||
: The v3 identity endpoint. See the integration steps above for more detail
|
||||
|
||||
DOMAIN ID
|
||||
: The DOMAIN ID field takes the “Account Name” as shown on the [Basic Informati](https://account-intl.huaweicloud.com/usercenter/?locale=en-us#/userindex/accountInfo) of the account. See the integration steps above for more detail
|
||||
|
||||
PROJECT
|
||||
: The target project name. See the integration steps above for more detail
|
||||
|
||||
USERNAME
|
||||
: The service account username. See the integration steps above for more detail
|
||||
|
||||
PASSWORD
|
||||
: The integration service account password. See the integration steps above for more detail
|
||||
|
||||
IMAGE FORMAT
|
||||
: Select QCOW2, RAW or VMDK image type
|
||||
|
||||
Image Store
|
||||
: Set an OBS bucket as a permanent store location for HPE Morpheus Enterprise virtual images. Users are limited to uploading images of 2GB or less in size if an OBS bucket is not specified here
|
||||
|
||||
Inventory Existing Instances
|
||||
: Select for HPE Morpheus Enterprise to discover and sync existing VMs
|
||||
|
||||
Enable Hypervisor Console
|
||||
: Hypervisor console support for openstack currently only supports novnc. Be sure the novnc proxy is configured properly in your openstack environment.
|
||||
|
||||
TIP
|
||||
|
||||
When using the RAW image format, you can bypass the image conversion service within the cloud leading to quicker performance. Other image formats are converted to RAW format and back when performing various actions. Using the RAW format from the start will bypass these conversion steps.
|
||||
|
||||
#### Advanced Options
|
||||
|
||||
DOMAIN
|
||||
: Specify a default domain for instances provisioned to this Cloud.
|
||||
|
||||
SCALE PRIORITY
|
||||
: Only affects Docker Provisioning. Specifies the priority with which an instance will scale into the cloud. A lower priority number means this cloud integration will take scale precedence over other cloud integrations in the group.
|
||||
|
||||
APPLIANCE URL
|
||||
: Alternate Appliance url for scenarios when the default Appliance URL (configured in admin > settings) is not reachable or resolvable for Instances provisioned in this cloud. The Appliance URL is used for Agent install and reporting.
|
||||
|
||||
TIME ZONE
|
||||
: Configures the time zone on provisioned VM’s if necessary.
|
||||
|
||||
DATACENTER ID
|
||||
: Used for differentiating pricing among multiple datacenters. Leave blank unless prices are properly configured.
|
||||
|
||||
NETWORK MODE
|
||||
: Unmanaged or select a Network Integration (NSX, ACI etc)
|
||||
|
||||
LOCAL FIREWALL
|
||||
: On or Off. Enable to managed Host and VM firewall/IP Table rules (linux only)
|
||||
|
||||
SECURITY SERVER
|
||||
: Security Server setting is for Security Service Integrations such as ACI
|
||||
|
||||
TRUST PROVIDER
|
||||
: Select Internal (Morpheus) or an existing Trust Provider Integration
|
||||
|
||||
STORAGE MODE
|
||||
: Single Disk, LVM or Clustered
|
||||
|
||||
BACKUP PROVIDER
|
||||
: Select a backup provider. Depending on the Cloud type and any currently-configured backup plugins you may select Internal Backups (Morpheus) or another configured backup solution
|
||||
|
||||
REPLICATION PROVIDER
|
||||
: Sets the default Replication Provider for the Cloud. Select an existing Replication Provider Integration
|
||||
|
||||
GUIDANCE
|
||||
: Enable Guidance recommendations on cloud resources.
|
||||
|
||||
COSTING
|
||||
: Enable for HPE Morpheus Enterprise to sync Costing data from the Cloud provider, when available. For on-prem Clouds, enabling costing activates a costing service designed to mirror the live costing experience of public clouds, including invoicing with line items and real-time cost data (Operations > Costing > Invoices). If your organization utilizes reserved instances and you want to pull in related pricing data, some Cloud integrations include the option to select Costing and Reservations. If this is not relevant, select Costing to save money on additional calls to the Cloud provider’s costing API.
|
||||
|
||||
DNS INTEGRATION
|
||||
: Records for instances provisioned in this cloud will be added to selected DNS integration.
|
||||
|
||||
SERVICE REGISTRY
|
||||
: Services for instances provisioned in this cloud will be added to selected Service Registry integration.
|
||||
|
||||
CONFIG MANAGEMENT
|
||||
: Select a Chef, Ansible or Puppet integration to be used with this Cloud.
|
||||
|
||||
CMDB
|
||||
: Select CMDB Integration to automatically update selected CMDB.
|
||||
|
||||
CMDB DISCOVERY
|
||||
: When checked, any automatically discovered (unmanaged) servers onboarded into HPE Morpheus Enterprise from this Cloud will also have CMDB records created for them.
|
||||
|
||||
CHANGE MANAGEMENT
|
||||
: Select an existing Change Management Integration to set on the Cloud. ex: Cherwell
|
||||
|
||||
AGENT INSTALL MODE
|
||||
: - SSH / WINRM / Guest Execution: HPE Morpheus Enterprise will attempt to use SSH, WINRM or Guest Execution for Agent install.
|
||||
- Cloud Init / Unattend (when available): (DEFAULT) HPE Morpheus Enterprise will utilize Cloud-Init or Cloudbase-Init for agent install when provisioning images with Cloud-Init/Cloudbase-Init installed. HPE Morpheus Enterprise will fall back on SSH or WINRM if cloud-init is not installed on the provisioned image. Morpheus will also add Agent installation to Windows unattend.xml data when performing Guest Customizations or utilizing syspreped images.
|
||||
|
||||
VDI GATEWAY
|
||||
: Set a VDI Gateway for outbound communication from the HPE Morpheus Enterprise Appliance to the vdi endpoints. VDI Gateways can be added in `/tools/vdi/gateways`
|
||||
|
||||
#### CUSTOM LOGOS
|
||||
|
||||
When integrating a Cloud, it will appear by default throughout the UI with its standard logo (VMware logo for VMware Clouds, etc.). If desired, you may upload a custom logo that should appear instead. This might be useful for MSPs which might not want to reveal the Cloud type underlying its services. A dark mode version of the logo may also be uploaded if the standard logo doesn’t look right against the HPE Morpheus Enterprise dark mode theme. Checking USE DEFAULT CLOUD LOGOS allows the user to return to the standard logo for the Cloud type without deleting the custom uploaded logo.
|
||||
|
||||
#### INVENTORY OPTIONS
|
||||
|
||||
Inventory options allow you to set a default active or inactive state for certain discovered resources. The list of available resources to configure will vary based on the Cloud type and its supported resources. By default, all possible resources for the Cloud type will be discovered in an active state. Uncheck the box for some or all resources to discover them in an inactive state. The list of potential resources that may appear include:
|
||||
|
||||
- Service Plans
|
||||
- Resource Pools
|
||||
- Networks
|
||||
- Security Groups
|
||||
- Datastores
|
||||
- Folders
|
||||
|
||||
#### Provisioning Command
|
||||
|
||||
PROXY
|
||||
: Set a proxy for inbound communication from Instances to the HPE Morpheus Enterprise Appliance. Proxies can be added in the Infrastructure > Networks > Proxies tab.
|
||||
|
||||
Bypass Proxy for Appliance URL
|
||||
: Enable to bypass proxy settings (if added) for HPE Morpheus Enterprise Agent communication to the Appliance URL.
|
||||
|
||||
NO PROXY
|
||||
: Include a list of IP addresses or name servers to exclude from proxy traversal
|
||||
|
||||
USER DATA (LINUX)
|
||||
: Add cloud-init user data. HPE Morpheus Enterprise 4.1.0 and earlier assumes bash syntax. HPE Morpheus Enterprise 4.1.1 and later supports all User Data formats. Refer to <https://cloudinit.readthedocs.io/en/latest/topics/format.html> for more information.
|
||||
|
||||
## Huawei Scalable File Service (SFS)
|
||||
|
||||
The HPE Morpheus Enterprise integration with Huawei Cloud includes the capability to work with Huawei Scalable File Service (SFS). SFS is shared file storage hosted on Huawei Cloud. By integrating HPE Morpheus Enterprise with Huawei Cloud you can discover, create, manage, and delete SFS servers, as well as view and work with the file shares and files contained therein.
|
||||
|
||||
### SFS Server Discovery and Management
|
||||
|
||||
On integrating Huawei Cloud with HPE Morpheus Enterprise, SFS servers and file shares are discovered automatically after a short time. The server(s) can be viewed in Infrastructure > Storage > Servers. By viewing the server detail page and clicking EDIT, the storage server can be scoped as needed. Administrators can choose to scope to other Huawei Cloud integrations (if more than one relevant integration currently exists), select from synced availability zones, and scope the storage server to specific Tenants if desired.
|
||||
|
||||
|
||||
|
||||
Additionally, Huawei SFS servers can be created from the storage server list page (Infrastructure > Storage > Servers) directly in HPE Morpheus Enterprise. Click + ADD to begin and set the storage server type value to “Huawei SFS”. Just like with existing synced SFS servers, those created from HPE Morpheus Enterprise can be scoped as needed.
|
||||
|
||||
|
||||
|
||||
### SFS File Share Discovery and Management
|
||||
|
||||
Discovered file shares will appear among other file shares synced with HPE Morpheus Enterprise in Infrastructure > Storage > File Shares. Depending on the number of cloud integrations in your HPE Morpheus Enterprise appliance and the number of cloud integrations available to your user account, this list may be quite large. Using the search bar on this page, we can narrow down the list to file shares displayed to those whose names match the search terms.
|
||||
|
||||
|
||||
|
||||
We can drill into individual file shares by clicking on their hyperlinked name in the list of all integrated file shares. From the file share detail page, a list of files will appear on the files tab. Begin the process of adding a new file by clicking + ADD. The Access tab on the file shares detail page allows users to view and manage ACL rules.
|
||||
|
||||
NOTE
|
||||
|
||||
A “Failed to load files from storage provider” is present when the HPE Morpheus Enterprise appliance doesn’t have access to the file share.
|
||||
|
||||
New Huawei SFS file shares can be created directly in HPE Morpheus Enterprise. From the file shares list page, get started by clicking + ADD. Select the type “Huawei SFS Share”. Set the storage service field to a pre-existing Huawei SFS server. A friendly name for the file share in HPE Morpheus Enterprise and selecting from synced availability zones are required fields.
|
||||
|
||||
|
||||
|
||||
## Huawei Object Storage Service (OBS)
|
||||
|
||||
The HPE Morpheus Enterprise integration with Huawei Cloud also supports Object Storage Service (OBS). HPE Morpheus Enterprise will automatically onboard existing OBS servers and buckets shortly after completing the cloud integration. Before you can add a new OBS server from HPE Morpheus Enterprise, you must know or generate a key and secret value from the Huawei console and must provide a Huawei OBS API endpoint.
|
||||
|
||||
### Generate a Key and Secret
|
||||
|
||||
From the Huawei web console, log into the account used to integrate Huawei Cloud with HPE Morpheus Enterprise. Hover over your account name in the upper-right corner of the application window and click “My Credentials”. Select “Access Keys” from the left-hand sidebar. To create a new key, click + Create Access Key. Complete the two-factor authentication steps in the box that appears.
|
||||
|
||||
|
||||
|
||||
Once the key is generated, download or record the key and store it in a safe location. The key will not be viewable or available for download again after this point.
|
||||
|
||||
### Create OBS Server in HPE Morpheus Enterprise
|
||||
|
||||
With the key and secret value in hand from the previous section, navigate to Infrastructure > Storage > Servers. Click + ADD. On changing the server type to Huawei OBS, you will see the fields for the access key and the secret key. OBS API endpoints can be found in [Huawei endpoint documentation](https://developer.huaweicloud.com/en-us/endpoint). Include those three values in the Create Server modal along with a friendly name for use in HPE Morpheus Enterprise UI. Just like with SFS objects, we can choose to scope the server to all or specific Tenants at this time.
|
||||
|
||||
|
||||
|
||||
### Create Huawei OBS Bucket
|
||||
|
||||
With an OBS server onboarded or created in HPE Morpheus Enterprise, you’re able to create and manage Huawei OBS buckets as needed. To create a new bucket, navigate to Infrastructure > Storage > Buckets. Click + ADD and select “Huawei OBS Bucket”. The following fields are required when creating a Huawei OBS bucket:
|
||||
|
||||
- **NAME**: A friendly name for use in HPE Morpheus Enterprise UI
|
||||
- **STORAGE SERVICE**: Choose the OBS server to associate the new bucket with
|
||||
- **BUCKET NAME**: The name of the bucket in Huawei Cloud, this must be unique
|
||||
- **STORAGE CLASS**: If needed, view the [discussion of storage classes](https://support.huaweicloud.com/en-us/eu-west-0-usermanual-obs/en-us_topic_0050937852.html) in Huawei support documentation
|
||||
- **BUCKET ACL**: Public Read, Public Read/Write, or Private
|
||||
- **BUCKET POLICY**: Public Read, Public Read/Write, or Private
|
||||
- **STORAGE QUOTA**: Set to 0 for no quota
|
||||
|
||||
Once finished, click SAVE CHANGES
|
||||
|
||||
|
||||
|
||||
## Network and Router Creation
|
||||
|
||||
Once a Huawei Cloud is integrated into HPE Morpheus Enterprise, new network creation options become available. When adding a new network (Infrastructure > Networks > NetworksTab), a new type labeled “Huawei Private Network” is available when clicking +ADD. When the user creates this network construct in HPE Morpheus Enterprise, a layer two subnet is created but it’s not connected to a Virtual Private Cloud (VPC). This is by design as an Internet-routable network is not always desired. Continue on with this section after creating the network to also create a VPC (router).
|
||||
|
||||
### Create a network
|
||||
|
||||
#### Procedure
|
||||
|
||||
1. Navigate to Infrastructure > Networks
|
||||
2. Click on the Networks tab
|
||||
3. Click +ADD
|
||||
4. Select Huawei Private Network
|
||||
5. Complete the modal based on requirements for the new network
|
||||
6. Click SAVE CHANGES
|
||||
|
||||
### Create a router
|
||||
|
||||
#### Procedure
|
||||
|
||||
1. Navigate to Infrastructure > Networks
|
||||
2. Click on the Routers tab
|
||||
3. Click +ADD
|
||||
4. Select Huawei Router
|
||||
5. Complete the modal based on requirements for the new router
|
||||
6. Click SAVE CHANGES
|
||||
|
||||
#### Results
|
||||
|
||||
When creating a router, it’s helpful to note that the External Network is the floating IP network that has been assigned to the Huawei project. This network will grant your Instances their routes out to the Internet. The Internal Subnet can be a layer two subnet that you may have created in the previous step. In addition, multiple subnets can be added to the router (VPC) and the IP address on the subnet would be the router’s internal IP address.
|
||||
@@ -0,0 +1,26 @@
|
||||
{
|
||||
"bundle_id": "morpheus_user_manual_8_1_0",
|
||||
"page_id": "GUID-139EC691-D4C3-4E3B-98E9-F108FF4E7A7F",
|
||||
"title": "OAuth 2.0 Credentials",
|
||||
"ordinal": 237,
|
||||
"parent_title": "Trust",
|
||||
"doc_id": "sd00007510en_us",
|
||||
"version": "8.1.0",
|
||||
"product": "User Manual",
|
||||
"source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-139EC691-D4C3-4E3B-98E9-F108FF4E7A7F.html",
|
||||
"topic_cluster": {
|
||||
"clustering_title": "OAuth 2.0 Credentials",
|
||||
"clustered_topics": [
|
||||
{
|
||||
"bundle_id": "morpheus_user_manual_8_1_1",
|
||||
"page_id": "GUID-139EC691-D4C3-4E3B-98E9-F108FF4E7A7F",
|
||||
"clustering_title": "OAuth 2.0 Credentials"
|
||||
},
|
||||
{
|
||||
"bundle_id": "morpheus_user_manual_8_1_2",
|
||||
"page_id": "GUID-139EC691-D4C3-4E3B-98E9-F108FF4E7A7F",
|
||||
"clustering_title": "OAuth 2.0 Credentials"
|
||||
}
|
||||
]
|
||||
}
|
||||
}
|
||||
@@ -0,0 +1,22 @@
|
||||
# OAuth 2.0 Credentials
|
||||
|
||||
HPE Morpheus Enterprise supports storage of credential sets for retrieving temporary access tokens, through OAuth 2.0, and using the tokens to access some resource. These credential sets can be used with REST-type Option Lists to retrieve information behind this type of authentication wall. Once stored, the credential can be used with as many Option Lists as needed and potentially in other areas of the product in the future.
|
||||
|
||||
To create a new credential set, click + ADD and then select “OAuth 2.0”. Complete the following, not all fields are present or required in every context:
|
||||
|
||||
- **CREDENTIAL STORE:** Select “Internal” or an integrated external Cypher store (if any). See the next section for instructions on standing up and integrating with an external Cypher store
|
||||
- **NAME:** A name for the credential set in HPE Morpheus Enterprise
|
||||
- **DESCRIPTION:** An optional description for the credential set
|
||||
- **ENABLED:** If checked, the credential set will be available for use
|
||||
- **GRANT TYPE:** Client Credentials or Password Credentials
|
||||
- **ACCESS TOKEN URL:** The authorization server’s token endpoint
|
||||
- **CLIENT ID:** The client ID for an app registered with the target service
|
||||
- **CLIENT SECRET:** The client secret, often needed when requesting access outside the context of a specific user
|
||||
- **USERNAME:** (Only present with “Password Credentials” Grant Type) The username for a user with target data access
|
||||
- **PASSWORD:** (Only present with “Password Credentials” Grant Type) The password for the user indicated above
|
||||
- **SCOPE:** The scope of access requested to the target resource
|
||||
- **CLIENT AUTHENTICATION:** “Send as basic auth header” or “Send client credentials in body” - Indicates how HPE Morpheus Enterprise should issue the token received in requests to the target resource
|
||||
|
||||
Once done, click ADD CREDENTIALS.
|
||||
|
||||
With the OAuth 2.0 credential set stored, they can be set on REST-type Option Lists to source data from behind a compatible authentication wall. With a REST-type Option List open (Library > Options > Option Lists), click the CREDENTIALS dropdown and select the credential set you’ve created. Alternatively, you can add a credential set directly in the add/edit Option List modal if needed. Option Lists can be associated with Select List or Typeahead-type Inputs and applied to Layouts, Instance Types, Workflows, and more to allow for customization at provision or Workflow execution time. Additional details on creating Option Lists can be found in the Library section of HPE Morpheus Enterprise docs.
|
||||
@@ -0,0 +1,26 @@
|
||||
{
|
||||
"bundle_id": "morpheus_user_manual_8_1_0",
|
||||
"page_id": "GUID-13B77F8D-BA84-4649-A4C1-D137357E7A78",
|
||||
"title": "Advanced morpheus.rb Settings",
|
||||
"ordinal": 30,
|
||||
"parent_title": "Additional Configuration Options",
|
||||
"doc_id": "sd00007510en_us",
|
||||
"version": "8.1.0",
|
||||
"product": "User Manual",
|
||||
"source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-13B77F8D-BA84-4649-A4C1-D137357E7A78.html",
|
||||
"topic_cluster": {
|
||||
"clustering_title": "Advanced morpheus.rb Settings",
|
||||
"clustered_topics": [
|
||||
{
|
||||
"bundle_id": "morpheus_user_manual_8_1_1",
|
||||
"page_id": "GUID-13B77F8D-BA84-4649-A4C1-D137357E7A78",
|
||||
"clustering_title": "Advanced morpheus.rb Settings"
|
||||
},
|
||||
{
|
||||
"bundle_id": "morpheus_user_manual_8_1_2",
|
||||
"page_id": "GUID-13B77F8D-BA84-4649-A4C1-D137357E7A78",
|
||||
"clustering_title": "Advanced morpheus.rb Settings"
|
||||
}
|
||||
]
|
||||
}
|
||||
}
|
||||
@@ -0,0 +1,124 @@
|
||||
# Advanced morpheus.rb Settings
|
||||
|
||||
Morpheus allows for additional advanced customizations for system managed services within the morpheus.rb file located in `/etc/morpheus/morpheus.rb`. Below is a list of the supported items available in the `morpheus.rb` file.
|
||||
|
||||
NOTE
|
||||
|
||||
Service configuration settings are not applicable for externalized services such as external MySQL, Opensearch or RabbitMQ clusters. Only connection settings are applicable for external services. Additionally, to configure HPE Morpheus Enterprise to utilize alternate ports for SSL, you may have to take additional configuration steps. If simply appending a port to your `appliance_url` value doesn’t work.
|
||||
|
||||
```
|
||||
```
|
||||
app['encryption_key_suffix'] = '$suffix'
|
||||
# Replace $suffix with the suffix string of your choice. See `https://docs.morpheusdata.com/en/latest/getting_started/additional/encryption.html` for important details and warnings.
|
||||
appliance_url 'https://morpheus.appliance-url.com'
|
||||
# Appending alternate port to appliance_url is supported. ie 'https://morpheus.appliance-url.com:8443'
|
||||
# The appliance_url cannot exceed 64 characters
|
||||
# The appliance_url must not contain a trailing `/`.
|
||||
bitcan['backup_directory'] = '/var/opt/morpheus/bitcan/backups'
|
||||
bitcan['working_directory'] = '/var/opt/morpheus/bitcan/working'
|
||||
opensearch['auth_password'] = 'xxxxxxxxxxxxxxxx'
|
||||
opensearch['auth_user'] = 'morpheus-es-user'
|
||||
opensearch['enable'] = true
|
||||
opensearch['es_hosts'] = {'127.0.0.1' => 9200}
|
||||
opensearch['host'] = "127.0.0.1"
|
||||
opensearch['port'] = "9200"
|
||||
opensearch['tmp_dir'] = '/var/tmp/opensearch'
|
||||
opensearch['use_tls'] = false
|
||||
↓ The following Opensearch settings are only valid for Internal/Embedded Opensearch services
|
||||
opensearch['log_dir'] = '/var/log/morpheus/opensearch'
|
||||
opensearch['memory_alloc_arena_max'] = 2
|
||||
opensearch['memory_map_max'] = 65536
|
||||
opensearch['memory_map_threshold'] = 131072
|
||||
opensearch['memory_top_pad'] = 131072
|
||||
opensearch['memory_trim_threshold'] = 131072
|
||||
opensearch['open_files'] = 204800
|
||||
opensearch['secure_mode'] = false
|
||||
opensearch['xms'] = 0.25 #### Configurable for customers running into high memory issues, values are the percentage of total RAM. Both ui and es xms/xmx config only apply if Opensearch is enabled.
|
||||
opensearch['xmx'] = 0.25
|
||||
guacd['guacamole_enabled'] = false
|
||||
guacd['host'] = localhost #### The host guacd is listening on, if not configured 'localhost' is the default value
|
||||
logging['svlogd_num'] = 30 #### keep 30 rotated log files
|
||||
logging['svlogd_size'] = 209715200 #### 200 MB in bytes
|
||||
logging['svlogd_timeout'] = 86400 #### rotate after 24 hours in seconds
|
||||
mysql['enable'] = true
|
||||
mysql['host'] = {'127.0.0.1' => 3306}
|
||||
mysql['use_tls'] = false
|
||||
mysql['morpheus_db_user'] = 'morpheus-db-user'
|
||||
mysql['morpheus_password'] = 'morpheus-db-password'
|
||||
mysql['morpheus_db'] = 'xxxxxxxxxxxxxxxx'
|
||||
mysql['mysql_url_overide'] = 'jdbc:mysql://10.30.20.10:3306,10.30.20.11:3306,10.30.20.12:3306/morpheusdb?autoReconnect=true&useUnicode=true&characterEncoding=utf8&failOverReadOnly=false&useSSL=false'
|
||||
↓ The following mysql settings are only valid for Internal/Embedded mysql services
|
||||
mysql['tmp_dir'] = '/tmp/mysql'
|
||||
mysql['log_dir'] = '/var/log/morpheus/mysql'
|
||||
mysql['max_active'] = 150 # The combined value off all app node max_active values must be lower than max_connections setting in mysql
|
||||
mysql['max_connections'] = 151
|
||||
mysql['max_allowed_packet'] = 67108864
|
||||
mysql['mysql_connect_timeout'] = 60000
|
||||
mysql['mysql_max_reconnects'] = 2
|
||||
mysql['mysql_queries_before_retry_source'] = 0
|
||||
mysql['mysql_seconds_before_retry_source'] = 300
|
||||
nginx['cache_max_size'] = '5000m'
|
||||
nginx['enable'] = true
|
||||
nginx['loading_pages']['failure_page_h1'] = 'Morpheus Server Error'
|
||||
nginx['loading_pages']['failure_page_h2'] = 'Please contact your system administrator for assistance.'
|
||||
nginx['loading_pages']['failure_page_title'] = 'Morpheus Server Error'
|
||||
nginx['loading_pages']['iteration_time'] = 10000 # milliseconds
|
||||
nginx['loading_pages']['loading_page_h1'] = 'Morpheus is Loading...'
|
||||
nginx['loading_pages']['loading_page_h2'] = 'please wait'
|
||||
nginx['loading_pages']['loading_page_title'] = 'Morpheus Loading'
|
||||
nginx['loading_pages']['max_loops'] = 60 # seconds
|
||||
nginx['loading_pages']['timeout_page'] = '/timeout.html'
|
||||
nginx['loading_pages']['timout_page_h1'] = 'Timeout waiting for Morpheus to load, click below to try again.'
|
||||
nginx['loading_pages']['timout_page_title'] = 'Morpheus timeout, please try again...'
|
||||
nginx['log_format_name'] = 'custom'
|
||||
nginx['log_format'] = '\'$remote_addr - $remote_user [$time_local] "$request" \' \'$status $body_bytes_sent "$http_referer" \' \'"$http_user_agent" "$http_x_forwarded_for" \' \'rt=$request_time uct="$upstream_connect_time" uht="$upstream_header_time" urt="$upstream_response_time"\';'
|
||||
nginx['listen_ipv6'] = nil #### IPv6 will be added to ``morpheus.conf`` and ``morpheus-ssl.conf`` listeners if any value is set in morpheus.rb other than ``nil``, including "off" or false
|
||||
nginx['ssl_ciphers'] = "ECDHE-RSA-AES256-GCM-SHA384:ECDHE-RSA-AES128-GCM-SHA256:DHE-RSA-AES256-GCM-SHA384:DHE-RSA-AES128-GCM-SHA256:ECDHE-RSA-AES256-SHA384:ECDHE-RSA-AES128-SHA256:ECDHE-RSA-AES256-SHA:ECDHE-RSA-AES128-SHA:DHE-RSA-AES256-SHA256:DHE-RSA-AES128-SHA256:DHE-RSA-AES256-SHA:DHE-RSA-AES128-SHA:ECDHE-RSA-DES-CBC3-SHA:EDH-RSA-DES-CBC3-SHA:AES256-GCM-SHA384:AES128-GCM-SHA256:AES256-SHA256:AES128-SHA256:AES256-SHA:AES128-SHA:DES-CBC3-SHA:HIGH:!aNULL:!eNULL:!EXPORT:!DES:!MD5:!PSK:!RC4"
|
||||
nginx['ssl_company_name'] = "Morpheus, LLC"
|
||||
nginx['ssl_country_name'] = "US"
|
||||
nginx['ssl_email_address'] = "personal@email.com"
|
||||
nginx['ssl_locality_name'] = "San Mateo"
|
||||
nginx['ssl_organizational_unit_name'] = "DevOps"
|
||||
nginx['ssl_protocols'] = "TLSv1 TLSv1.1 TLSv1.2"
|
||||
nginx['ssl_session_cache'] = "builtin:1000 shared:SSL:10m"
|
||||
nginx['ssl_session_timeout'] = "5m"
|
||||
nginx['ssl_state_name'] = "CA"
|
||||
nginx['worker_connections'] = 10240
|
||||
nginx['workers'] = integer calculated from number of cpus
|
||||
nginx['ssl_access_ping_log'] = false #### false by default, when true GET requests to the ``/ping`` endpoint are logged in the ``/var/log/morpheus/nginx/morpheus-ssl-access.log`` file on the appliance
|
||||
nginx['access_ping_log'] = false #### false by default, when true GET requests to the ``/ping`` endpoint are logged in the ``/var/log/morpheus/nginx/morpheus-ssl-access.log`` file on the appliance
|
||||
rabbitmq['enable'] = true
|
||||
rabbitmq['host'] = '127.0.0.1'
|
||||
rabbitmq['port'] = '5672'
|
||||
rabbitmq['queue_user_password'] = 'xxxxxxxxxxxxxxxx'
|
||||
rabbitmq['queue_user'] = 'morpheus-rmq-user'
|
||||
rabbitmq['vhost'] = 'morpheus'
|
||||
↓ The following rabbitmq settings are only valid for Internal/Embedded rabbitmq services
|
||||
rabbitmq['heartbeat'] = nil
|
||||
rabbitmq['log_dir'] = '/var/log/morpheus/rabbitmq'
|
||||
rabbitmq['nodename'] = 'rabbit@localhost'
|
||||
rabbitmq['port'] = '5672'
|
||||
rabbitmq['use_tls'] = false
|
||||
repo['repo_host_url'] = 'https://www.hpe.com/support/hpesc'
|
||||
ui['http_client_connect_timeout'] = 10000 #### milliseconds
|
||||
ui['jobs_enabled'] = true #### This option disables the appliance jobs service on the appliance node when set to false. This should be disabled only when configuring jobs to run on specific app nodes in HA environments.
|
||||
ui['kerberos_config'] = nil
|
||||
ui['kerberos_login_config'] = nil
|
||||
ui['log_dir'] = '/var/log/morpheus/morpheus-ui'
|
||||
ui['max_memory_mb'] = nil
|
||||
ui['memory_alloc_arena_max'] = 2
|
||||
ui['memory_map_max'] = 65536
|
||||
ui['memory_map_threshold'] = 131072
|
||||
ui['memory_top_pad'] = 131072
|
||||
ui['memory_trim_threshold'] = 131072
|
||||
ui['pxe_boot_enabled'] = false #### This option disables the PXE service within the app
|
||||
ui['support_links'] = {
|
||||
'name' => ['url', 'i18n'],
|
||||
'name1' => ['url1', i18n1'],
|
||||
'name2' => ['url2', i18n2']
|
||||
} #### The internationalization configuration is optional. The result of this configuration are entries in the support dropdown menu in the upper bar of the application window which override the default entries.
|
||||
ui['vm_images_cdn_url'] = 'https://morpheus-images.morpheusdata.com'
|
||||
ui['xms'] = 0.25 #### Configurable for customers running into high memory issues, values are the percentage of total RAM. Both ui and es xms/xmx config only apply if Opensearch is enabled.
|
||||
ui['xmx'] = 0.25
|
||||
```
|
||||
```
|
||||
@@ -0,0 +1,26 @@
|
||||
{
|
||||
"bundle_id": "morpheus_user_manual_8_1_0",
|
||||
"page_id": "GUID-14A50EED-E11C-47E2-9C35-28B1F09CF6A7",
|
||||
"title": "Overview",
|
||||
"ordinal": 225,
|
||||
"parent_title": "Load Balancers",
|
||||
"doc_id": "sd00007510en_us",
|
||||
"version": "8.1.0",
|
||||
"product": "User Manual",
|
||||
"source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-14A50EED-E11C-47E2-9C35-28B1F09CF6A7.html",
|
||||
"topic_cluster": {
|
||||
"clustering_title": "Overview",
|
||||
"clustered_topics": [
|
||||
{
|
||||
"bundle_id": "morpheus_user_manual_8_1_1",
|
||||
"page_id": "GUID-14A50EED-E11C-47E2-9C35-28B1F09CF6A7",
|
||||
"clustering_title": "Overview"
|
||||
},
|
||||
{
|
||||
"bundle_id": "morpheus_user_manual_8_1_2",
|
||||
"page_id": "GUID-14A50EED-E11C-47E2-9C35-28B1F09CF6A7",
|
||||
"clustering_title": "Overview"
|
||||
}
|
||||
]
|
||||
}
|
||||
}
|
||||
@@ -0,0 +1,31 @@
|
||||
# Overview
|
||||
|
||||
HPE Morpheus Enterprise provisions the following load balancers:
|
||||
|
||||
- Amazon ALB (Application Load Balancer)
|
||||
- Azure Load Balancer
|
||||
- HaProxy Container
|
||||
|
||||
and integrates with the following external load balancers:
|
||||
|
||||
- Citrix NetScaler
|
||||
- F5 BigIP (v11.4+)
|
||||
- FortiADC
|
||||
- NSX
|
||||
- NSX Advanced
|
||||
|
||||
Once created or integrated, load balancers are available as an option to be added during provision time or post-provisioning.
|
||||
|
||||
Once a load balancer is added to an instance, you can manually scale or configure auto-scaling based on thresholds or schedules, and burst across clouds with cloud priority.
|
||||
|
||||
In the load balancers page there are two sections:
|
||||
|
||||
Load Balancers
|
||||
: View or edit existing load balancers, add new load balancers.
|
||||
|
||||
Virtual Servers
|
||||
: View and link to Instances that are attached to load balancers.
|
||||
|
||||
## Group and Tenant Access
|
||||
|
||||
Load balancers can be configured to provide specific Group and Tenant access, if desired. **Group Access** controls which Groups at provision time will have access to the load balancer resource. Only workloads being provisioned to the selected Groups would have visibility to the load balancer. Workloads provisioned to other Groups would not see the load balancer as an available selection. **Tenant Permissions** control which Tenants may see the load balancer. Public visibility allows access to the load balancer for users in all Tenants (subject to additional RBAC controls) while Private visibility allows access only for selected Tenants. Select all that may apply.
|
||||
@@ -0,0 +1,26 @@
|
||||
{
|
||||
"bundle_id": "morpheus_user_manual_8_1_0",
|
||||
"page_id": "GUID-151B596B-EE69-4D4B-8C80-964A90D3523C",
|
||||
"title": "Adding HPE SPP to the Virtual Image Library",
|
||||
"ordinal": 423,
|
||||
"parent_title": "Firmware and Driver Lifecycle Management",
|
||||
"doc_id": "sd00007510en_us",
|
||||
"version": "8.1.0",
|
||||
"product": "User Manual",
|
||||
"source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-151B596B-EE69-4D4B-8C80-964A90D3523C.html",
|
||||
"topic_cluster": {
|
||||
"clustering_title": "Adding HPE SPP to the Virtual Image Library",
|
||||
"clustered_topics": [
|
||||
{
|
||||
"bundle_id": "morpheus_user_manual_8_1_1",
|
||||
"page_id": "GUID-151B596B-EE69-4D4B-8C80-964A90D3523C",
|
||||
"clustering_title": "Adding HPE SPP to the Virtual Image Library"
|
||||
},
|
||||
{
|
||||
"bundle_id": "morpheus_user_manual_8_1_2",
|
||||
"page_id": "GUID-151B596B-EE69-4D4B-8C80-964A90D3523C",
|
||||
"clustering_title": "Adding HPE SPP to the Virtual Image Library"
|
||||
}
|
||||
]
|
||||
}
|
||||
}
|
||||
@@ -0,0 +1,28 @@
|
||||
# Adding HPE SPP to the Virtual Image Library
|
||||
|
||||
## About this task
|
||||
|
||||
This procedure describes how to add an HPE Service Pack for ProLiant (SPP) ISO to the Morpheus Virtual Images library for use in firmware and driver update workflows.
|
||||
|
||||
1. Obtain the appropriate HPE SPP ISO for the target ProLiant server generation.
|
||||
|
||||
NOTE
|
||||
|
||||
A separate ISO is required for each server generation (for example, Gen10 and Gen11).
|
||||
2. In the Morpheus appliance, navigate to Library > Virtual Images.
|
||||
3. Click Add > SPP.
|
||||
4. Enter a name for the image (for example, `HPE Gen10 SPP 2025.09.00`).
|
||||
5. From the Operating System drop-down list, select the appropriate **HPE SPP for Gen…** entry.
|
||||
6. Add the SPP ISO using one of the following methods:
|
||||
- Upload the locally downloaded ISO file, or
|
||||
- Select **URL / PATH** and paste the full URL for the ISO.
|
||||
7. Leave all other properties at their default values.
|
||||
8. Click Save Changes.
|
||||
|
||||
NOTE
|
||||
|
||||
When uploading a local file, wait for the upload to complete.
|
||||
9. In the Virtual Images list, wait until:
|
||||
- Source shows `Uploaded`
|
||||
- Status shows `Active`
|
||||
10. Record the **ID** of the Virtual Image entry. This ID is required when creating the update job.
|
||||
@@ -0,0 +1,26 @@
|
||||
{
|
||||
"bundle_id": "morpheus_user_manual_8_1_0",
|
||||
"page_id": "GUID-151C50C5-5883-4137-A9B0-EAF5F8087117",
|
||||
"title": "Orchestrating Load Balancers",
|
||||
"ordinal": 227,
|
||||
"parent_title": "Load Balancers",
|
||||
"doc_id": "sd00007510en_us",
|
||||
"version": "8.1.0",
|
||||
"product": "User Manual",
|
||||
"source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-151C50C5-5883-4137-A9B0-EAF5F8087117.html",
|
||||
"topic_cluster": {
|
||||
"clustering_title": "Orchestrating Load Balancers",
|
||||
"clustered_topics": [
|
||||
{
|
||||
"bundle_id": "morpheus_user_manual_8_1_1",
|
||||
"page_id": "GUID-151C50C5-5883-4137-A9B0-EAF5F8087117",
|
||||
"clustering_title": "Orchestrating Load Balancers"
|
||||
},
|
||||
{
|
||||
"bundle_id": "morpheus_user_manual_8_1_2",
|
||||
"page_id": "GUID-151C50C5-5883-4137-A9B0-EAF5F8087117",
|
||||
"clustering_title": "Orchestrating Load Balancers"
|
||||
}
|
||||
]
|
||||
}
|
||||
}
|
||||
@@ -0,0 +1,40 @@
|
||||
# Orchestrating Load Balancers
|
||||
|
||||
A large part of application orchestration and automation involves tying various web services and backend services into different load balancer configurations. If the automation tool is unable to communicate or integrate with this aspect of your infrastructure, a lot of gaps will be created in the full orchestrated flow of application deployment. This is why Morpheus provides deep integration with load balancers and explicit definitions with catalog items as to how they are connected to provisioned instances. Some of the functionality includes:
|
||||
|
||||
- Public Cloud Load Balancer Support
|
||||
- Private Cloud Load Balancer Support
|
||||
- Port Type definitions (Profiles like HTTP/HTTPS or UDP)
|
||||
- SSL Certificate Management and SSL Certificate Upload
|
||||
- SSL Passthrough or Forced Redirect
|
||||
|
||||
Not only does Morpheus have an ability to provision HAProxy based load balancer containers for easy consumption in development environments, but also has direct tie ins with several Load Balancer Types:
|
||||
|
||||
- F5 BigIP
|
||||
- Netscaler
|
||||
- NSX Advanced Load Balancer
|
||||
- Amazon ELB
|
||||
- Amazon ALB
|
||||
- Azure Load Balancer
|
||||
- Fortinet
|
||||
- Openstack Octavia
|
||||
- HA Proxy
|
||||
- NSX
|
||||
|
||||
Morpheus exposes configuration options during provisioning of an Instance relevant and common to each supported LB Integration. In some cases, Morpheus also provides direct management and sync support for VIP configurations on the various Load Balancers (such as F5, and NSX Advanced Load Balancer), However in a day to day orchestrated workflow this would not be the ideal means by which a user should consume load balancer services.
|
||||
|
||||
By tying the Load Balancer associations into the provisioning of instances and the definition of the instance catalog item, the lifecycle of the VIP can more easily be maintained throughout the lifecycle of whatever application may be deployed.
|
||||
|
||||
## Setting up an Instance for Load Balancer Consumption
|
||||
|
||||
Several of the provided Morpheus instance types are ready to go with load balancer orchestration out of the box (Apache, Nginx, Tomcat, Node.js, etc). It is also fairly easy to extend existing generic instance types during provisioning to be tied to load balancers or to set up said catalog items in advanced for such functionality.
|
||||
|
||||
When creating a custom Instance Type (in Library), one can define a list of exposed ports that the node type within the instance exposes. When defining these exposed ports it prompts for a Name, Port Number, and LB Type. The LB Type is what enables load-balancer functionality. This can either be HTTP,HTTPS, or TCP. This specification helps build the correct profile for the VIP as well as setup the appropriate types of Health Monitors within the target load balancer integration.
|
||||
|
||||
Now, when a user consumes this custom instance type (either through single instance provisioning or full application blueprint provisioning), a section appears in the Automation phase of provisioning. Each port that is defined that exposes a load-balancer gets a dropdown to choose which load balancer integration attach to the exposed port and various prompts become available.
|
||||
|
||||
These prompts control features ranging from target VIP Address to selecting an SSL Certificate to be applied to the VIP. These SSL Certificates will even go so far as to create SSL Profiles in integrations for things like an F5 automatically for the application.
|
||||
|
||||
Once the instance is provisioned, as part of the final phase, the load balancer configuration will be applied and maintained on the instance. This association can be manipulated after the fact via the “Scale” tab found on the Instance Detail page.
|
||||
|
||||
Another benefit to associating load-balancers this way is that the pool members are automatically maintained during scaling events, either via auto-scaling thresholds or manual node additions / removals.
|
||||
@@ -0,0 +1,26 @@
|
||||
{
|
||||
"bundle_id": "morpheus_user_manual_8_1_0",
|
||||
"page_id": "GUID-1621A716-2765-4655-B4D0-C95B8416F4D3",
|
||||
"title": "Overview",
|
||||
"ordinal": 171,
|
||||
"parent_title": "Clusters",
|
||||
"doc_id": "sd00007510en_us",
|
||||
"version": "8.1.0",
|
||||
"product": "User Manual",
|
||||
"source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-1621A716-2765-4655-B4D0-C95B8416F4D3.html",
|
||||
"topic_cluster": {
|
||||
"clustering_title": "Overview",
|
||||
"clustered_topics": [
|
||||
{
|
||||
"bundle_id": "morpheus_user_manual_8_1_1",
|
||||
"page_id": "GUID-1621A716-2765-4655-B4D0-C95B8416F4D3",
|
||||
"clustering_title": "Overview"
|
||||
},
|
||||
{
|
||||
"bundle_id": "morpheus_user_manual_8_1_2",
|
||||
"page_id": "GUID-1621A716-2765-4655-B4D0-C95B8416F4D3",
|
||||
"clustering_title": "Overview"
|
||||
}
|
||||
]
|
||||
}
|
||||
}
|
||||
@@ -0,0 +1,22 @@
|
||||
# Overview
|
||||
|
||||
Infrastructure > Clusters is for creating and managing Kubernetes Clusters, HPE Morpheus Enterprise manager Docker Clusters, KVM Clusters, or Cloud specific Kubernetes services such as EKS, AKS and GKE.
|
||||
|
||||
## Cluster Types
|
||||
|
||||
Table 1.
|
||||
|
||||
| | | |
|
||||
| --- | --- | --- |
|
||||
| **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 |
|
||||
| Ext Kubernetes | Brings an existing (brownfield) Kubernetes cluster into HPE Morpheus Enterprise | Kubernetes |
|
||||
| GKE Cluster | Google Cloud GKE (Google Kubernetes Engine) Clusters | Kubernetes |
|
||||
| HVM Cluster | A KVM‐based virtualization solution. See the detailed section below on HVM Clusters for complete use documentation. | KVM |
|
||||
|
||||
NOTE
|
||||
|
||||
Refer to clusterLayouts for supported Clouds per Cluster Type.
|
||||
@@ -0,0 +1,26 @@
|
||||
{
|
||||
"bundle_id": "morpheus_user_manual_8_1_0",
|
||||
"page_id": "GUID-173469C2-D5C6-47F6-8A01-41C3D73B679B",
|
||||
"title": "Diagrams",
|
||||
"ordinal": 343,
|
||||
"parent_title": "HPE Morpheus Enterprise",
|
||||
"doc_id": "sd00007510en_us",
|
||||
"version": "8.1.0",
|
||||
"product": "User Manual",
|
||||
"source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-173469C2-D5C6-47F6-8A01-41C3D73B679B.html",
|
||||
"topic_cluster": {
|
||||
"clustering_title": "Diagrams",
|
||||
"clustered_topics": [
|
||||
{
|
||||
"bundle_id": "morpheus_user_manual_8_1_1",
|
||||
"page_id": "GUID-173469C2-D5C6-47F6-8A01-41C3D73B679B",
|
||||
"clustering_title": "Diagrams"
|
||||
},
|
||||
{
|
||||
"bundle_id": "morpheus_user_manual_8_1_2",
|
||||
"page_id": "GUID-173469C2-D5C6-47F6-8A01-41C3D73B679B",
|
||||
"clustering_title": "Diagrams"
|
||||
}
|
||||
]
|
||||
}
|
||||
}
|
||||
@@ -0,0 +1,45 @@
|
||||
# Diagrams
|
||||
|
||||
The HPE Morpheus Enterprise diagram repository contains many diagrams related to HPE Morpheus Enterprise appliance architectures, HPE Morpheus Enterprise concepts, and reference diagrams for integrating HPE Morpheus Enterprise with third-party technologies.
|
||||
|
||||
## Appliance Architectures
|
||||
|
||||
### All-in-one (single node) Installation
|
||||
|
||||
|
||||
|
||||
### 3-node High Availability (HA) Installation
|
||||
|
||||
|
||||
|
||||
### Fully Distributed High Availability (HA) Installation
|
||||
|
||||
|
||||
|
||||
## HPE Morpheus Enterprise Concepts
|
||||
|
||||
### Cloud-Group-Role Relationship
|
||||
|
||||
|
||||
|
||||
### Library Items
|
||||
|
||||
|
||||
|
||||
### Mapping Morpheus Constructs to Public and Private Cloud Constructs
|
||||
|
||||
|
||||
|
||||
## Third-Party Technology Integration
|
||||
|
||||
### Zerto
|
||||
|
||||
|
||||
|
||||
### Veeam
|
||||
|
||||
|
||||
|
||||
### Mapping Identity Source Groups to Morpheus Roles
|
||||
|
||||
|
||||
@@ -0,0 +1,26 @@
|
||||
{
|
||||
"bundle_id": "morpheus_user_manual_8_1_0",
|
||||
"page_id": "GUID-1741A126-636E-4A96-812C-48A8B7A25E88",
|
||||
"title": "Unmanaged Networks",
|
||||
"ordinal": 429,
|
||||
"parent_title": "Network Management",
|
||||
"doc_id": "sd00007510en_us",
|
||||
"version": "8.1.0",
|
||||
"product": "User Manual",
|
||||
"source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-1741A126-636E-4A96-812C-48A8B7A25E88.html",
|
||||
"topic_cluster": {
|
||||
"clustering_title": "Unmanaged Networks",
|
||||
"clustered_topics": [
|
||||
{
|
||||
"bundle_id": "morpheus_user_manual_8_1_1",
|
||||
"page_id": "GUID-1741A126-636E-4A96-812C-48A8B7A25E88",
|
||||
"clustering_title": "Unmanaged Networks"
|
||||
},
|
||||
{
|
||||
"bundle_id": "morpheus_user_manual_8_1_2",
|
||||
"page_id": "GUID-1741A126-636E-4A96-812C-48A8B7A25E88",
|
||||
"clustering_title": "Unmanaged Networks"
|
||||
}
|
||||
]
|
||||
}
|
||||
}
|
||||
@@ -0,0 +1,23 @@
|
||||
# Unmanaged Networks
|
||||
|
||||
The unmanaged Network mode is used when the network infrastructure is not managed by HPE Morpheus.
|
||||
|
||||
In this case, there is a minimal configuration that is created as default when the cloud gets created with the network mode set to `Unmanaged network`. This minimal configuration includes a default Resource Pool that can be used to associate compute servers with, and a default unmanaged network that is available during instance provisioning to attach with compute servers.
|
||||
|
||||
The default unmanaged network is configured as an untagged network with DHCP as the IP allocation method. This allows a compute instance provisioned to come up with network connectivity without any specific network configuration required from the user.
|
||||
|
||||
The unmanaged network assumes:
|
||||
|
||||
- The network infrastructure to be configured correctly for the untagged network to work correctly.
|
||||
- A DHCP server stood up in the infrastructure for that network.
|
||||
|
||||
|
||||
|
||||
Users can create other networks (VLANs) if required, in addition to the default unmanaged network, and use them in their BM instance.
|
||||
|
||||
NOTE
|
||||
|
||||
- If the ALLOW IP OVERRIDE checkbox is selected (allows selection of DHCP or static IP or IP Pool), ensure that the CIDR and GATEWAY fields are configured correctly.
|
||||
- At present, only one physical interface is supported for the unmanaged network mode.
|
||||
|
||||
The network consumption by an instance is the same as for managed networks.
|
||||
@@ -0,0 +1,26 @@
|
||||
{
|
||||
"bundle_id": "morpheus_user_manual_8_1_0",
|
||||
"page_id": "GUID-17B067B3-32C3-4DE7-82DE-B6033C235495",
|
||||
"title": "Library",
|
||||
"ordinal": 101,
|
||||
"parent_title": "HPE Morpheus Enterprise",
|
||||
"doc_id": "sd00007510en_us",
|
||||
"version": "8.1.0",
|
||||
"product": "User Manual",
|
||||
"source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-17B067B3-32C3-4DE7-82DE-B6033C235495.html",
|
||||
"topic_cluster": {
|
||||
"clustering_title": "Library",
|
||||
"clustered_topics": [
|
||||
{
|
||||
"bundle_id": "morpheus_user_manual_8_1_1",
|
||||
"page_id": "GUID-17B067B3-32C3-4DE7-82DE-B6033C235495",
|
||||
"clustering_title": "Library"
|
||||
},
|
||||
{
|
||||
"bundle_id": "morpheus_user_manual_8_1_2",
|
||||
"page_id": "GUID-17B067B3-32C3-4DE7-82DE-B6033C235495",
|
||||
"clustering_title": "Library"
|
||||
}
|
||||
]
|
||||
}
|
||||
}
|
||||
Some files were not shown because too many files have changed in this diff Show More
Reference in New Issue
Block a user