VMware is not going further with VMware Cloud Director. They are integrating the VMware Cloud Director feature with Aria Automation only for the upcoming versions, primarily with the VCF 9, and slowly they are integrating some of the parts they have already integrated, and they might not continue with VMware Cloud Director in the future. They can make it more granular to ensure hardware-level segregation, the underlying infrastructure level of segregation for the end user, and a separate security boundary where users can access the end-to-end layer. End-to-end layer means my software layer along with the hardware layer. If they want to do a certain level of troubleshooting primarily on the ESXi part, that is what I feel is lacking for now because for an end user accessing the SSP, the underlying infrastructure is a kind of black box for them. For VMware Cloud Director, it can be more comprehensive if we enable public cloud integration as well. In today's date, customers are adopting a multi-cloud environment where VMware Cloud Director is much feasible to leverage the underlying VMware backend architecture. If VMware Cloud Director could be made to have more integration with the public cloud and do the day one, day two jobs for public cloud interface as well, that would be beneficial. Additionally, I recommend leveraging the VMware Cloud Director layer if a customer has a multi-cloud environment and is planning some cross-cloud migration capability. Cross-cloud migration refers to if a customer has something on Azure, wanting to bring it up on VMware or maybe from VMware to AWS, vice versa. In that case, VMware Cloud Director should provide some cross-cloud migration capability as well.
