Retain Infrastructure Services Locally

There are good reasons to keep some infrastructure services running in an on-premises environment. If there are existing DDI (DNS, DHCP, and IPAM) solutions, organizations may want to continue to leverage their existing investment. There may also be security and compliance requirements that mandate infrastructure services continue to run in an on-premises location. Workload placement and data gravity can also affect the placement of infrastructure services, not just in the near term but also in the desired future state.

For common networking services such as DHCP and DNS, organizations can take advantage of VMware NSX networking capabilities included in a VMware Cloud SDDC. VMware NSX can forward both DHCP requests and DNS queries from a VMware Cloud SDDC to an organization’s data center, allowing these services to remain on-premises. Similarly, log data can be forwarded to an on-premises logging receiver environment.

An important consideration before configuring infrastructure services is the transmission of data. Note that the amount of data being transferred from a VMware Cloud SDDC is the cost of egress traffic. Costs can vary per region as well as Infrastructure Services Provider. Without proper planning, egress traffic fees can be unpredictable and contribute to an organization’s bill. It is important to understand the utilization for existing infrastructure services and accurately forecast egress utilization and plan accordingly.

When retaining infrastructure services in an on-premises environment, it Is essential to review any new or additional requirements before providing these services to an organization’s VMware Cloud SDDC. Testing, documentation, and a security review are highly recommended before exposing a service to VMware Cloud based workloads.