Deleting services from VCF for Classic - Automated instances
You can delete the services that were provisioned for your VMware Cloud Foundation for Classic - Automated instances when you no longer need these services.
Before you delete services from Automated instances
- Deleting services from instances with VMware vSphere® 6.5 is not supported.
- You are billed until the end of the IBM Cloud® infrastructure billing cycle for the deleted services.
Procedure to delete services from Automated instances
- From the VMware Solutions console, click Resources > VCF for Classic from the left navigation pane.
- In the VMware Cloud Foundation for Classic table, click the instance for which you want to delete services.
- Click the Services tab.
- On the Services page, locate the service instance that you want to delete, click the vertical overflow menu next to the Status column, and then click Delete service.
- In the Remove service window, review the considerations or warnings if there are any and select I Understand. Click Delete.
Results after you delete services from Automated instances
After your request to delete a service is accepted, the service status is changed to Removing.
When the service deletion is completed successfully, you are notified by email, and the service is deleted from the Services page of the instance.
You are billed until the end of the IBM Cloud infrastructure billing cycle for the deleted services.
Manually removing the DNS entries for specific services
For specific services, if you installed the service in a VMware Solutions release earlier than V4.0 and you delete that service, you must manually remove the DNS entries.
After you delete the service, unused DNS entries remain in Active Directory™. These entries do not cause any problems. However, in the future, they might create conflicts with reverse lookups. It is recommended that you remove the entries as soon as possible.
The following table shows the services that are affected. The table also shows the pattern for hostnames for various service offerings. The actual hostname might differ from the pattern in various ways. Use the pattern to locate all of the registered DNS hostnames associated with a service. Many services have more than one registered hostname.
Service | Hostname Pattern | Example |
---|---|---|
Caveonix RiskForesight | riskforesight |
riskforesight inst01-riskforesight |
F5 BIG-IP | nickname-bigip1 nickname-bigip2 |
edgefw-bigip1 |
FortigateVM | nickname-fortigate |
edgefw-fortigate01 |
Entrust CloudControl™ | htccnn-id |
htcc02-GY67239 |
Entrust DataControl® | htdcnn-id |
htcc02-GY67239 |
Entrust KeyControl™ | htkcnn-id |
htcc02-GY67239 |
VMware Aria Operations | vrli vrops vrlog |
vrli-master vrops-data1 vrlog-master |
To remove the DNS entires, complete the following steps:
- Log in to the Active Directory appliance and open the DNS tools.
- Go to the instance subdomain, which is the subdomain under the root domain. Its name resembles the name of the Automated instance.
- Remove the hostname entries for the specific deleted service appliances.
- Open the associated reverse lookup table and remove the DNS entries from the table.