VME Worker

[hlago]

Hi, I have Morpheus Enterprise installed on AWS and I want to control a VME (VMware Engine/Environment) installed on-premises. What is the proper procedure for installing the worker on the VME? Thank you very much.

Be regards

[controles]

Hi,

In this scenario, the key point is that VME integration in Morpheus does not always require a worker in the same way as traditional VMware environments.

For on-prem VME, the recommended approach is to integrate it as a cloud in Morpheus using the appropriate VMware or VME integration method, depending on how your environment is exposed.

If your VME environment is reachable from Morpheus (network connectivity, API access), you can often connect it directly without deploying a worker inside VME.

A worker is typically required only when:
- There is no direct network connectivity between Morpheus and the target environment
- You need a local execution point for automation tasks
- You are working in restricted or segmented networks

In hybrid scenarios like AWS to on-prem, the most important step is to validate:
- Network connectivity between Morpheus and VME
- API accessibility
- Proper credentials and endpoint configuration

If connectivity is already in place, try adding the environment directly first. Only consider deploying a worker if you run into connectivity or execution limitations.

Hope this helps.

[cbunge]

@hlago 

HVM hosts require the Morpheus Agent.  This requirese 7443 connectivity from Morpheus > Hosts.  Also, initial configuration requires 22 (SSH) from Morpheus to the HVM Hosts.

If you do not have a direct connect or some means to have those ports allowed from AWS (totally understand), then you would configure the Worker on a host.  To do so:

1. Install HVM ISO on all of your hosts. This configures Ubuntu 24.04 with the required packages on your hosts.
2. bootstrat 1 host in your datacenter with the VME Manager installer.  Instead of choosing VME, there is an option to configure a distributed worker. This will install the worker on that host and allow you to connect it to your Morpheus Enterprise in AWS
3. Once the worker is connected, create/add your hosts to a HVM cluster in your Morpheus UI.

If you run into issues, just lmk.

[controles]

Thank you for the clarification.

This aligns with the behavior we are seeing. Since HVM hosts require the Morpheus Agent, direct connectivity from Morpheus to the target hosts is essential, including HTTPS on port 7443 and SSH access during initial configuration.

In hybrid environments such as AWS to on premise, validating network reachability, allowed ports, and credentials upfront is indeed a critical step. When direct connectivity is restricted, deploying the worker on a reachable intermediate host is a practical and supported approach.

This provides a flexible way to extend Morpheus execution while maintaining control in segmented or restricted network scenarios. Thanks for outlining the recommended workflow.

Best regards,
Carlos Parra Solano
Infrastructure Consultant