We've been facing some challenges with Morpheus due to its design for public cloud usage. Their main focus is on allowing customers to deploy virtual machines to Azure, Google Cloud, AWS (and other private or public clouds they support). They provide features such as guidance and cost optimization. However, we're using Morpheus for on-prem v center clouds, which is probably not the user base norm. We are very pleased with the dashboard and multi-tenancy capabilities, but there are some challenges when deploying and configuring the more complex Telco workloads that have advanced networking. The integration of the NSX-T needs to be refactored. As I have been working on the API, there are some issues with the workflow engine in the automation that need to be addressed. For example, I need to be able to flag a task as fail or continue on fail if something goes wrong in the workflow. Currently, if one of the tasks in a twenty-task workflow fails, the remaining nineteen are not run, which can be a problem if one of those tasks is critical, such as when patching or doing security tasks. Thus, workflow enhancements and improvements are necessary. Morpheus desires the ability to control the full life cycle of a virtual machine from beginning to end. We have many vendors who want to establish virtual machines, but we want users to access them through Morpheus. We want the VMs to be provisioned from an external system and then be managed in Morpheus so users can only perform limited activities without being able to delete or provision them. We are currently working on resolving this issue, which I refer to as reconciliation. I have asked the developers to implement multi-tenancy, where each tenant has their own landing page at a unique URL. However, we are using groups, not tenants, so there are features we can do with tenants that we cannot do with groups. Specifically, I am trying to get the developers to add notifications support so that when a group member logs in to the Morpheus portal, they can be informed of their VMs' maintenance schedule at a specific time. This is a feature I have requested them to add. We are generally pleased with Morpheus, however, due to some restraints and restrictions, we are utilizing it differently than the majority of its users. This creates some difficulty.