The following are some examples of the application of the VMware Support Services Terms & Conditions as applied to various offerings and features.
Operations Manager and stemcell releases should be obtained from Tanzu Network and not from OSS in order for VMware to provide support. The releases on Tanzu Network have gone through further testing than those in the OSS community and will be less susceptible to bugs or other issues.
In Scope | |
Installation / Upgrade of Operations Manager |
Yes |
Usage & Configuration |
Yes |
Installation, configuration, and usage of the OM Utility |
Yes |
Bug reporting |
Yes |
Bug Fix |
Yes [1] |
Debugging Deployment failures |
Yes [2] |
BOSH Releases Downloaded from Tanzu Network |
Yes |
BOSH add-ons Downloaded from Tanzu Network |
Yes |
Operator Maintenance activities such as BBR and Certificate Rotation |
Yes [3] |
Custom cloud-config and runtime-configs uploaded to the BOSH director | No [5] |
In Scope | |
OSS BOSH Stemcells |
No |
OSS BOSH Releases |
No |
Debugging OSS BOSH Deployments |
No [2,4] |
Third-party or community project BOSH add-ons |
No |
Support and Maintenance of open source BOSH |
No |
[1] - Bug fixes are prioritized by VMware Engineering with input from VMware Support and our customers. There is no guarantee of an immediate fix & VMware Support retains the right to close out support tickets if a fix is not immediate.
[2] - Troubleshooting Failed Director deployments VMware supported tile deployments. Third Party Tiles are not directly supported by VMware and require the customer to have vendor support. BOSH OSS deployments are not supported. VMware support will provide best effort support when encountering Third Party Tiles or BOSH OSS deployments, which involves ruling out the supported product components and then referring customers to third party vendor support.
[3] - VMware supports BBR and automated Certificate rotation for BOSH Director and the Tanzu Tile Deployments. These Feature may or may not have an impact on OSS BOSH releases and deployments. Customers are responsible for validating compatibility for each of their OSS deployments. VMware will not support any incompatibility issues.
[4] - Debugging third party OSS failing BOSH jobs is considered best effort. VMware support will provide the necessary steps to rule out the support BOSH components before referring Customer to third party vendor support.
[5] - Customers are able to upload their own cloud and runtime configs to the BOSH director as long as they are not conflicting with ops-manager managed configs, for example to define a new VM type with a unique name. Customers cannot update the existing managed configs.
The Information in this FAQ is not promised or guaranteed to be correct, current, or complete and this FAQ may contain technical inaccuracies or typographical errors. Pivotal assumes no responsibility (and expressly disclaims responsibility) for updating this FAQ to maintain current information or to ensure the accuracy or completeness of any posted information. Accordingly, you should confirm the accuracy and completeness of all posted information before making any decision related to any products, services or other matters described in this FAQ. Pivotal provides no assurances that any reported problems will be resolved by Pivotal, even if Pivotal elects to provide information with the goal of addressing a problem. ALL INFORMATION, SOFTWARE, PRODUCTS, MATERIALS, AND SERVICES PROVIDED IN THIS FAQ ARE PROVIDED “AS IS” AND “WITH ALL FAULTS” WITH NO WARRANTIES OR GUARANTEES OF ANY KIND. PIVOTAL EXPRESSLY DISCLAIMS TO THE FULLEST EXTENT PERMITTED BY LAW ALL EXPRESS, IMPLIED, STATUTORY OR OTHER WARRANTIES, GUARANTEES AND REPRESENTATIONS, INCLUDING, WITHOUT LIMITATION, THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR USE OR PURPOSE, TITLE AND NON-INFRINGEMENT OF PROPRIETARY AND INTELLECTUAL PROPERTY RIGHTS, AND WARRANTIES ARISING FROM A COURSE OF DEALING, USAGE OR TRADE PRACTICE. WITHOUT LIMITING THE GENERALITY OF THE FOREGOING, PIVOTAL MAKES NO WARRANTY THAT THE INFORMATION IN THIS FAQ WILL MEET YOUR REQUIREMENTS OR THAT THIS FAQ WILL BE UNINTERRUPTED, TIMELY, SECURE, ERROR FREE OR THAT THE SERVICES WILL MEET (OR ARE DESIGNED TO MEET) YOUR BUSINESS REQUIREMENTS.
The Information in this FAQ is not promised or guaranteed to be correct, current, or complete and this FAQ may contain technical inaccuracies or typographical errors. Pivotal assumes no responsibility (and expressly disclaims responsibility) for updating this FAQ to maintain current information or to ensure the accuracy or completeness of any posted information. Accordingly, you should confirm the accuracy and completeness of all posted information before making any decision related to any products, services or other matters described in this FAQ. Pivotal provides no assurances that any reported problems will be resolved by Pivotal, even if Pivotal elects to provide information with the goal of addressing a problem. ALL INFORMATION, SOFTWARE, PRODUCTS, MATERIALS, AND SERVICES PROVIDED IN THIS FAQ ARE PROVIDED “AS IS” AND “WITH ALL FAULTS” WITH NO WARRANTIES OR GUARANTEES OF ANY KIND. PIVOTAL EXPRESSLY DISCLAIMS TO THE FULLEST EXTENT PERMITTED BY LAW ALL EXPRESS, IMPLIED, STATUTORY OR OTHER WARRANTIES, GUARANTEES AND REPRESENTATIONS, INCLUDING, WITHOUT LIMITATION, THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR USE OR PURPOSE, TITLE AND NON-INFRINGEMENT OF PROPRIETARY AND INTELLECTUAL PROPERTY RIGHTS, AND WARRANTIES ARISING FROM A COURSE OF DEALING, USAGE OR TRADE PRACTICE. WITHOUT LIMITING THE GENERALITY OF THE FOREGOING, PIVOTAL MAKES NO WARRANTY THAT THE INFORMATION IN THIS FAQ WILL MEET YOUR REQUIREMENTS OR THAT THIS FAQ WILL BE UNINTERRUPTED, TIMELY, SECURE, ERROR FREE OR THAT THE SERVICES WILL MEET (OR ARE DESIGNED TO MEET) YOUR BUSINESS REQUIREMENTS.