If enabled, existing Virtual Machines will be inventoried and appear as unmanaged Virtual Machines in Morpheus .

NOTE: Multiple Organizations/VDC’s can be added by creating additional Clouds in Morpheus.

DOMAIN

Specify a default domain for instances provisioned to this Cloud.

SCALE PRIORITY

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.

Defines if Morpheus will control local firewall of provisioned servers and hosts.

Important

When local firewall management is enabled, Morpheus will automatically set an IP table rule to allow incoming connections on tcp port 22 from the Morpheus Appliance.

STORAGE MODE

Single Disk, LVM or Clustered

GUIDANCE

Enable Guidance recommendations on cloud resources.

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, Salt, Ansible or Puppet integration to be used with this Cloud.

CMDB

Select CMDB Integration to automatically update selected CMDB.

AGENT INSTALL MODE

SSH / WINRM: Morpheus will use SSH or WINRM for Agent install.

Cloud-Init (when available): Morpheus will utilize Cloud-Init or Cloudbase-Init for agent install when provisioning images with Cloud-Init/Cloudbase-Init installed. Morpheus will fall back on SSH or WINRM if cloud-init is not installed on the provisioned image.

API PROXY

Required when a Proxy Server blocks communication between the Morpheus Appliance and the Cloud. Proxies can be added in the Infrastructure -> Networks -> Proxies tab.

PROXY

Required when a Proxy Server blocks communication between an Instance and the Morpheus Appliance. Proxies can be added in the Infrastructure -> Networks -> Proxies tab.

If enabled, existing Virtual Machines will be inventoried and appear as unmanaged Virtual Machines in Morpheus .

NOTE: Multiple Organizations/VDC’s can be added by creating additional Clouds in Morpheus.

DOMAIN

Specify a default domain for instances provisioned to this Cloud.

SCALE PRIORITY

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.

Defines if Morpheus will control local firewall of provisioned servers and hosts.

Important

When local firewall management is enabled, Morpheus will automatically set an IP table rule to allow incoming connections on tcp port 22 from the Morpheus Appliance.

STORAGE MODE

Single Disk, LVM or Clustered

GUIDANCE

Enable Guidance recommendations on cloud resources.

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, Salt, Ansible or Puppet integration to be used with this Cloud.

CMDB

Select CMDB Integration to automatically update selected CMDB.

AGENT INSTALL MODE

SSH / WINRM: Morpheus will use SSH or WINRM for Agent install.

Cloud-Init (when available): Morpheus will utilize Cloud-Init or Cloudbase-Init for agent install when provisioning images with Cloud-Init/Cloudbase-Init installed. Morpheus will fall back on SSH or WINRM if cloud-init is not installed on the provisioned image.

API PROXY

Required when a Proxy Server blocks communication between the Morpheus Appliance and the Cloud. Proxies can be added in the Infrastructure -> Networks -> Proxies tab.

PROXY

Required when a Proxy Server blocks communication between an Instance and the Morpheus Appliance. Proxies can be added in the Infrastructure -> Networks -> Proxies tab.

To do this, under local computer Administrator, open a command prompt and run winrmquickconfig

Install VMware tools

Install .Net at least 4.5

Enable remote PowerShell this can be done in PowerShell.

Enable-PSremoting

Shutdown the virtual machine and convert to a template.

Note

Do not run sysprep

Create a new machine in VMware vCenter and install a base version of your preferred Linux distro build. If you are using cloud init as part of your image you will need to ensure your virtual machine has a cdrom.

Before installing the operating system setup a single ext or xfs partition without a swap disk (This is so that growpart can extend the disk. growpart currently does not support lvm)

Install the distro and apply any updates to the operating system and security updates

selinux set to permissive (enforced can cause problems with cloud-init)

Create a new machine in VMware vCenter and install a base version of your preferred Linux distro build. If you are using cloud init as part of your image you will need to ensure your virtual machine has a cdrom.

Before installing the operating system setup a single ext partition without a swap disk (This is so that growpart can extend the disk. growpart currently does not support lvm)

Install the distro and apply any updates to the operating system and security updates

Ensure you have set a root password

Install cloud-init by running sudoaptinstallcloud-init

Install cloud-utils-growpart sudoaptinstallcloud-utils

Install desired hypervisor drivers (Virto, Open-VM Tools)

Install git by running sudoaptinstallgit

As Debian 9 includes network manager ensure this is disabled. Change the below file

To import your template into vCloud director you will need to login as either an administrator or organisation administrator.

Once logged into vCloud director you will then need select ManageOrganizations and then select your organization.

From within the organisation click on Catalogues > select an existing catalogue or create a new catalogue.

Note

Please note once you connect Morpheus to your vCD environment, it will create a catalogue called Auto Morpheus. This is a working catalogue and is ignored by Morpheus when searching for images, so any images in the catalogue will not be synced into Morpheus

Open the catalogue and select the import template from vCenter and then browse the data stores for your templates. Select your template and the type in a new name and description then check the copy template into vCloud director.

Once you click ok the import process will begin. When the import has completed the template will appear in Morpheus within Provisioning>VirtualImages

If the image does not appear within the virtual images you may need to use the filters to filter the virtual images by the vmware ( vmdk / ovf / ova) type.

You may also need to refresh the cloud. To do this go to Infrastructure>Clouds
> select the vCloud Director cloud > select Refresh.