vmware-samples/validated-solutions-for-cloud-foundation

A companion repository for the VMware Validated Solutions for VMware Cloud Foundation.

VMware Validated Solutions for VMware Cloud Foundation

Introduction

A VMware Validated Solution is a technical validated implementation that is built and tested by VMware and VMware partners to help customers resolve common business use cases. VMware Validated Solutions are operationally and cost-effective, reliable, and secure. Each solution contains a detailed design, implementation, and operational guidance.

Learn more at vmware.com/go/vvs.

This repository is a companion to the following validated solutions:

• Health Reporting and Monitoring for VMware Cloud Foundation\

  A validated solution that provides health monitoring for the VMware Cloud Foundation components using HTML reports and custom dashboards, alerts, and notifications using VMware Aria Operations.

  The repository provides:

  • Python Module for VMware Cloud Foundation Health Monitoring in VMware Aria Operations.
  • Custom dashboards, alerts, notifications, and super metric artifacts in VMware Aria Operations.

• Advanced Load Balancing for VMware Cloud Foundation

  A validated solution enables you to build secure, high-performing, resilient, and efficient load balancing infrastructure for applications and workloads deployed on VMware Cloud Foundation. You can leverage this solution to rapidly implement VMware NSX Advanced Load Balancer in a VMware Cloud Foundation environment to increase security, automation, and provide enterprise-grade developer-ready infrastructure for load balancing.

  The repository provides:

  • Infrastructure-as-code examples for the solution. This includes Terraform examples for the deployment and configuration of the solution.

• Private Cloud Automation for VMware Cloud Foundation

  A validated solution which enables you to implement a modern cloud automation platform that delivers self-service automation, DevOps for infrastructure, and orchestration using Aria Automation and VMware Cloud Foundation.

  The repository provides:

  • Infrastructure-as-code examples for the solution. This includes Terraform examples for the deployment and configuration of the solution.

  • Step-by-step implementation guidance to create a sample project in Aria Automation after deploying the solution using both the UI and infrastructure-as-code where applicable.

Get Started

Clone the Repository

Clone main branch for the latest updates.

Example:

git clone https://github.com/vmware-samples/validated-solutions-for-cloud-foundation.git

The directory structure of the repository.

├── LICENSE
├── NOTICE
├── README.md
├── alb
│   ├── ansible-examples
│   ├── orchestrator-examples
│   └── README.md
├── appliance
│   ├── files
│   ├── manual
│   ├── output-appliance
│   ├── scripts
│   ├── appliance-build.sh
│   └── ...
├── hrm
│   ├── images
│   ├── releases
│   ├── source
│   └── README.md
└── pca
    ├── docs
    ├── scripts
    ├── terraform-examples
    └── README.md

Navigate to the Companion Solution Content

• Advanced Load Balancing for VMware Cloud Foundation

• Health Reporting and Monitoring for VMware Cloud Foundation

• Private Cloud Automation for VMware Cloud Foundation

Issues

We welcome you to use the GitHub Issues to report bugs or suggest enhancements.

In order to have a good experience with our community, we recommend that you read the contributing guidelines.

validated-solutions-for-cloud-foundation's Issues

Add ESXi License Health to VCF Compute dashboard

Code of Conduct

• I have read and agree to the project's Code of Conduct.
• Vote on this issue by adding a 👍 reaction to the original issue initial description to help the maintainers prioritize.
• Do not leave "+1" or other comments that do not add relevant information or questions.
• If you are interested in working on this issue or have submitted a pull request, please leave a comment.

Description

Licensing Health is available in reporting module, but we do not have a corresponding table in HRM in the VCF Compute Health.
Below is output from the HTML Report

Update corresponding SM, Alerts and Notifications

Need to add a new table to VCF Compute Health for Licensing Health.
Also include

Use Case(s)

NA

Potential Configuration

No response

References

No response

[HRM] Date on Backups and Snapshot dashboard shown incorrectly

Code of Conduct

• I have read and agree to the project's Code of Conduct.
• Vote on this issue by adding a 👍 reaction to the original issue initial description to help the maintainers prioritize.
• Do not leave "+1" or other comments that do not add relevant information or questions.
• If you are interested in working on this issue or have submitted a pull request, please leave a comment.

VMware Cloud Foundation

v4.5

Environment Details

No response

Description

I am sending a custom metrics to vrops called HRM Snapshot status -
I am seeing that when this data goes into vrops, the it gets automatically converted to a number. The data for "statKey":"HRM Snapshot Status|latest",is "Feb 16 15:46:08 2023 GMT" but it is
shown as a number on the UI. I dont understand why this value is getting converted.

{
   "stat-content":[
      {
         "statKey":"HRM Snapshot Status|component",
         "timestamps":[
            1683585928000
         ],
         "values":[
            "SDDC Manager"
         ]
      },
      {
         "statKey":"HRM Snapshot Status|resource",
         "timestamps":[
            1683585928000
         ],
         "values":[
            "SDDC Manager Snapshot"
         ]
      },
      {
         "statKey":"HRM Snapshot Status|element",
         "timestamps":[
            1683586608000
         ],
         "values":[
            "sfo-vcf01.sfo.rainpole.io"
         ]
      },
      {
         "statKey":"HRM Snapshot Status|domain",
         "timestamps":[
            1683585385000
         ],
         "values":[
            "sfo-m01,sfo-w01"
         ]
      },
      {
         "statKey":"HRM Snapshot Status|snapshots",
         "timestamps":[
            1683585517000
         ],
         "values":[
            1
         ]
      },
      {
         "statKey":"HRM Snapshot Status|latest",
         "timestamps":[
            1683585928000
         ],
         "values":[
            "Feb 16 15:46:08 2023 GMT"
         ]
      },
      {
         "statKey":"HRM Snapshot Status|consolidation required",
         "timestamps":[
            1683585928000
         ],
         "values":[
            false
         ]
      },
      {
         "statKey":"HRM Snapshot Status|alert",
         "timestamps":[
            1683585928000
         ],
         "values":[
            "RED"
         ]
      },
      {
         "statKey":"HRM Snapshot Status|alert_code",
         "timestamps":[
            1683585928000
         ],
         "data":[
            2
         ]
      },
      {
         "statKey":"HRM Snapshot Status|message",
         "timestamps":[
            1683585928000
         ],
         "values":[
            "Latest snapshot is greater than 3 days old. A single snapshot exists. "
         ]
      }
   ]
}

Similar issue is seen with Backup dashboard in a customer environment.

Expected Behavior

Date should be shown in correct format.

Note - this issue is not seen in all the environments and all dashboards. Sometimes, the dashboards work as expected with same data. Something on vROps is causing the date field to be changed to a different format. Need to check with vROps team.

Actual Behavior

NA

Steps to Reproduce

No response

Screenshots

References

No response

feat: Add support for the VMware Cloud Foundation cloud account in vRealize Operations v8.10.2

Code of Conduct

• I have read and agree to the project's Code of Conduct.
• Vote on this issue by adding a 👍 reaction to the original issue initial description to help the maintainers prioritize.
• Do not leave "+1" or other comments that do not add relevant information or questions.
• If you are interested in working on this issue or have submitted a pull request, please leave a comment.

Description

Current implementation for IOM uses vCenter Adapters and SDDC Health Management Pack
With the changes in IOM vRealize Operations 8.10.2, we need to use the VCF cloud account and the VCF health management that comes with it. As a result, changes must be made in the way HRM python module pushes the data to vRealize Operations.

This must also include changes to dashboards, supermetrics, alerts and notifications as needed.

Use Case(s)

Customer using HRM with vROps 8.10.2

Potential Configuration

No response

References

No response

[HRM] Fix parsing of SOS Version health data for VxRail Manager VM

Code of Conduct

• I have read and agree to the project's Code of Conduct.
• Vote on this issue by adding a 👍 reaction to the original issue initial description to help the maintainers prioritize.
• Do not leave "+1" or other comments that do not add relevant information or questions.
• If you are interested in working on this issue or have submitted a pull request, please leave a comment.

VMware Cloud Foundation

v4.5.2

Environment Details

VxRail Testbed

Description

Issue parsing Version Health Data for VxRail Manager.

Expected Behavior

Script should run without errors.

Actual Behavior

[2024-03-25 18:57:51] DEBUG - body has been passed to this api {"stat-content": [{"statKey": "SOS Version Health Summary|area", "timestamps": [1711392868000], "values": ["VXRAILMGR: sfo-m01-vxm01.sfo.rainpole.io"]}, {"statKey": "SOS Version Health Summary|title", "timestamps": [1711392868000], "values": [["7.0.452-28122244"]]}, {"statKey": "SOS Version Health Summary|state", "timestamps": [1711392868000], "values": ["YELLOW"]}, {"statKey": "SOS Version Health Summary|timestamp", "timestamps": [1711392868000], "values": ["Mon Mar 25 18:54:28 2024"]}, {"statKey": "SOS Version Health Summary|message", "timestamps": [1711392868000], "values": ["Warning: Version mismatch found for VXRAILMGR:sfo-m01-vxm01.sfo.rainpole.io. BOM version ['7.0.452-28122244'], Component Running installed version 7.0.452-28152920 and VCF Inventory version 7.0.452-28152920 are not as expected."]}, {"statKey": "SOS Version Health Summary|status", "timestamps": [1711392868000], "values": ["failed"]}, {"statKey": "SOS Version Health Summary|alert", "timestamps": [1711392868000], "values": ["YELLOW"]}, {"statKey": "SOS Version Health Summary|alert_code", "timestamps": [1711392868000], "data": [1]}]}
[2024-03-25 18:57:52] DEBUG - https://xint-vrops01.rainpole.io:443 "POST /suite-api/api/resources/560220a2-03a0-4b40-bc86-6f35879846ee/stats?_no_links=true HTTP/1.1" 400 None
[2024-03-25 18:57:52] DEBUG - Going to call https://xint-vrops01.rainpole.io/suite-api/api/auth/token/acquire
[2024-03-25 18:57:52] DEBUG - API URL is /suite-api/api/auth/token/acquire
[2024-03-25 18:57:52] DEBUG - body has been passed to this api {"username": "admin", "password": "****"}
[2024-03-25 18:57:52] DEBUG - Resetting dropped connection: xint-vrops01.rainpole.io
[2024-03-25 18:57:52] DEBUG - https://xint-vrops01.rainpole.io:443 "POST /suite-api/api/auth/token/acquire?_no_links=true HTTP/1.1" 200 None
[2024-03-25 18:57:52] DEBUG - https://xint-vrops01.rainpole.io:443 "POST /suite-api/api/resources/560220a2-03a0-4b40-bc86-6f35879846ee/stats?_no_links=true HTTP/1.1" 400 None
[2024-03-25 18:57:52] ERROR - Error - [send-data-to-vrops.py:41] - Exception occurred. Details -
[2024-03-25 18:57:52] ERROR - Traceback (most recent call last):
File "C:\python3\Lib\site-packages\nagini-2.0-py3.12.egg\nagini\nagini.py", line 310, in _do_safe_request
return self._do_request(url, client_method, params, data, binary, files, api_url, token)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "C:\python3\Lib\site-packages\nagini-2.0-py3.12.egg\nagini\nagini.py", line 366, in _do_request
raise e
File "C:\python3\Lib\site-packages\nagini-2.0-py3.12.egg\nagini\nagini.py", line 359, in _do_request
raise ClientSideException(result.status_code, result.reason, response_obj)
nagini.nagini.ClientSideException: Http error code = 400
Reason = 400. Error object = {'apiErrorCode': 400,
'httpStatusCode': 400,
'message': 'Invalid input format.',
'moreInformation': [{'name': 'api-uri',
'value': '/suite-api/api/resources/560220a2-03a0-4b40-bc86-6f35879846ee/stats'}]}

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
File "C:\vmware\hrm\main\send-data-to-vrops.py", line 38, in inner_function
func(*args, **kwargs)
File "C:\vmware\hrm\main\send-data-to-vrops.py", line 1706, in push_sddc_versions
self.push_data_to_vrops(category, resource_id, hostname, metrics_payload_json)
File "C:\vmware\hrm\main\send-data-to-vrops.py", line 373, in push_data_to_vrops
self.vrops.add_stats(metrics_payload_json, id=resource_id)
File "C:\python3\Lib\site-packages\nagini-2.0-py3.12.egg\nagini\nagini.py", line 399, in
new_method = lambda self, *args, **kwargs: self._rest_request(rest_method, params=kwargs, content=args)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "C:\python3\Lib\site-packages\nagini-2.0-py3.12.egg\nagini\nagini.py", line 295, in _rest_request
return self._do_safe_request(templated_url, client_method, encoded_params, data, binary, files, api_url,
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "C:\python3\Lib\site-packages\nagini-2.0-py3.12.egg\nagini\nagini.py", line 314, in _do_safe_request
return self._do_request(url, client_method, params, data, binary, files, api_url, token)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "C:\python3\Lib\site-packages\nagini-2.0-py3.12.egg\nagini\nagini.py", line 366, in _do_request
raise e
File "C:\python3\Lib\site-packages\nagini-2.0-py3.12.egg\nagini\nagini.py", line 359, in _do_request
raise ClientSideException(result.status_code, result.reason, response_obj)
nagini.nagini.ClientSideException: Http error code = 400
Reason = 400. Error object = {'apiErrorCode': 400,
'httpStatusCode': 400,
'message': 'Invalid input format.',
'moreInformation': [{'name': 'api-uri',
'value': '/suite-api/api/resources/560220a2-03a0-4b40-bc86-6f35879846ee/stats'}]}

[2024-03-25 18:57:52] ERROR - Error - [send-data-to-vrops.py:42] - Http error code = 400
Reason = 400. Error object = {'apiErrorCode': 400,
'httpStatusCode': 400,
'message': 'Invalid input format.',
'moreInformation': [{'name': 'api-uri',
'value': '/suite-api/api/resources/560220a2-03a0-4b40-bc86-6f35879846ee/stats'}]}

[2024-03-25 18:57:52] ERROR - Traceback (most recent call last):
File "C:\python3\Lib\site-packages\nagini-2.0-py3.12.egg\nagini\nagini.py", line 310, in _do_safe_request
return self._do_request(url, client_method, params, data, binary, files, api_url, token)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "C:\python3\Lib\site-packages\nagini-2.0-py3.12.egg\nagini\nagini.py", line 366, in _do_request
raise e
File "C:\python3\Lib\site-packages\nagini-2.0-py3.12.egg\nagini\nagini.py", line 359, in _do_request
raise ClientSideException(result.status_code, result.reason, response_obj)
nagini.nagini.ClientSideException: Http error code = 400
Reason = 400. Error object = {'apiErrorCode': 400,
'httpStatusCode': 400,
'message': 'Invalid input format.',
'moreInformation': [{'name': 'api-uri',
'value': '/suite-api/api/resources/560220a2-03a0-4b40-bc86-6f35879846ee/stats'}]}

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
File "C:\vmware\hrm\main\send-data-to-vrops.py", line 38, in inner_function
func(*args, **kwargs)
File "C:\vmware\hrm\main\send-data-to-vrops.py", line 1706, in push_sddc_versions
self.push_data_to_vrops(category, resource_id, hostname, metrics_payload_json)
File "C:\vmware\hrm\main\send-data-to-vrops.py", line 373, in push_data_to_vrops
self.vrops.add_stats(metrics_payload_json, id=resource_id)
File "C:\python3\Lib\site-packages\nagini-2.0-py3.12.egg\nagini\nagini.py", line 399, in
new_method = lambda self, *args, **kwargs: self._rest_request(rest_method, params=kwargs, content=args)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "C:\python3\Lib\site-packages\nagini-2.0-py3.12.egg\nagini\nagini.py", line 295, in _rest_request
return self._do_safe_request(templated_url, client_method, encoded_params, data, binary, files, api_url,
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "C:\python3\Lib\site-packages\nagini-2.0-py3.12.egg\nagini\nagini.py", line 314, in _do_safe_request
return self._do_request(url, client_method, params, data, binary, files, api_url, token)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "C:\python3\Lib\site-packages\nagini-2.0-py3.12.egg\nagini\nagini.py", line 366, in _do_request
raise e
File "C:\python3\Lib\site-packages\nagini-2.0-py3.12.egg\nagini\nagini.py", line 359, in _do_request
raise ClientSideException(result.status_code, result.reason, response_obj)
nagini.nagini.ClientSideException: Http error code = 400
Reason = 400. Error object = {'apiErrorCode': 400,
'httpStatusCode': 400,
'message': 'Invalid input format.',
'moreInformation': [{'name': 'api-uri',
'value': '/suite-api/api/resources/560220a2-03a0-4b40-bc86-6f35879846ee/stats'}]}

Steps to Reproduce

Run the python script send-data-to-vrops.py in an vxrail environment

Screenshots

No response

References

No response

[HRM] Add additional health checks

Code of Conduct

• I have read and agree to the project's Code of Conduct.
• Vote on this issue by adding a 👍 reaction to the original issue initial description to help the maintainers prioritize.
• Do not leave "+1" or other comments that do not add relevant information or questions.
• If you are interested in working on this issue or have submitted a pull request, please leave a comment.

Description

Add checks for SSO, ESXi Connection, Free pool and Connected CD-ROM to python code and to dashboards on vROps.
These were not included for the initial release.

Use Case(s)

NA

Potential Configuration

No response

References

No response

Update formatting of date column on backup dashboard

Code of Conduct

• I have read and agree to the project's Code of Conduct.
• Vote on this issue by adding a 👍 reaction to the original issue initial description to help the maintainers prioritize.
• Do not leave "+1" or other comments that do not add relevant information or questions.
• If you are interested in working on this issue or have submitted a pull request, please leave a comment.

Description

Date column in backup dashboard is in improper format.
Currently it is T

Fix the formatting to make it same as other dashboard

Example format - see date column

Use Case(s)

Backups dashboard

Potential Configuration

No response

References

No response

Add support for additional vSAN cluster health checks

From powershell-module-for-vmware-cloud-foundation-reporting created by tenthirtyam: vmware/powershell-module-for-vmware-cloud-foundation-reporting#103

Code of Conduct

• I have read and agree to the project's Code of Conduct.
• Vote on this issue by adding a 👍 reaction to the original issue initial description to help the maintainers prioritize.
• Do not leave "+1" or other comments that do not add relevant information or questions.
• If you are interested in working on this issue or have submitted a pull request, please leave a comment.

Description

Add support for including the results of the following in the vSAN section of the Health Report.

• vSAN Capacity Utilization
• Cluster Disk Status
• Active ReSync Objects

{
...
    "vSAN": {
        "vSAN Capacity Utilization": {},
        "Cluster Disk Status": {},
        "Active ReSync Objects": {},
        ...
}

Use Case(s)

Improve support for health checks added to SoS in v4.4 and later.

Potential Configuration

To be determined.

References

No response

[CBA] Update all documentation and Terraform code samples for Aria Automation rebarnding

Code of Conduct

• I have read and agree to the project's Code of Conduct.
• Vote on this issue by adding a 👍 reaction to the original issue initial description to help the maintainers prioritize.
• Do not leave "+1" or other comments that do not add relevant information or questions.
• If you are interested in working on this issue or have submitted a pull request, please leave a comment.

Description

Earlier in April, the vRealize Automation Cloud SaaS offering was rebranded to Aria Automation and as a result the Cloud-Based Automation for VMware Cloud Foundation validated solution needs to be updated to support the new Aria branding.

Updated include:

• Validated Solution Guide
• Supporting Terraform code exampled

Use Case(s)

Rebranding of vRealize Automation Cloud to Aria Automation

Potential Configuration

No response

References

No response

Remove dependency for `FQDN` as suffix in `Account Name` when configuring `NSX-T account` in VMware Aria Operations

Code of Conduct

• I have read and agree to the project's Code of Conduct.
• Vote on this issue by adding a 👍 reaction to the original issue initial description to help the maintainers prioritize.
• Do not leave "+1" or other comments that do not add relevant information or questions.
• If you are interested in working on this issue or have submitted a pull request, please leave a comment.

Encountered When?

When you setup HRM for the first time and if the name of the cloud account configured for NSX-T does not include the FQDN of NSX Manager, then the NSX related data will not show up on dashboards. Hence you must follow the below steps to resolve this issue.

Description

For the python script to send data to vRealize Operations, it is needed that the name of the cloud account configured for NSX-T must include the FQDN of NSX Manager. e.g if your name is NSX MGMT Domain, then it needs to be updated to NSX MGMT Domain - sfo-m01-nsx01.sfo.rainpole.io where sfo-m01-nsx01.sfo.rainpole.io is the FQDN of NSX Manager.

If the name of the cloud account already has FQDN, then you don't need to do anything.

Updating the name can be performed by:

1. Log in to the vRealize Operations Manager operations interface at https://<vrealize_operations_manager_fqdn>​ with a user assigned the Administrator​ role.
2. On the left pane navigate to Data Sources > Integrations
3. Expand NSX-T, and select the Management Domain account from the list.
4. On the Add Account - NSX-T page, update the Name by adding the FQDN as suffix.
   e.g if your name is NSX MGMT Domain, then it needs to be updated to NSX MGMT Domain - sfo-m01-nsx01.sfo.rainpole.io where sfo-m01-nsx01.sfo.rainpole.io is the FQDN of NSX Manager.
5. Click Save
6. Repeat the above steps for Workload Domain NSX account as well.

Below is an example of how the name should look like.

Use Case(s)

When running send-data-to-vrops.py python script, above steps are needed so that the script can send data to NSX objects on vRealize Operations.

Potential Configuration

No response

References

No response

[HRM] Storage reporting fails when running `send-data-to-vrops.py`

Code of Conduct

• I have read and agree to the project's Code of Conduct.
• Vote on this issue by adding a 👍 reaction to the original issue initial description to help the maintainers prioritize.
• Do not leave "+1" or other comments that do not add relevant information or questions.
• If you are interested in working on this issue or have submitted a pull request, please leave a comment.

VMware Cloud Foundation

4.5.1

Environment Details

VCF 4.5.1
vCenter 7.0.3 Update l
Aria Operations 8.12.0
Multi-site, 2 x SDDC Manager, 2 x Workload Domains per sit - 4 x vCenter.

Description

When the send-data-to-vrops.py script is run no storagecapacityhealth-status.json is created.

No obvious errors in connectivity.

Only errors reported in the script are when the script reports it cannot find the file.

Logon using the local vcf account does report as successful.

Expected Behavior

storagecapacityhealth-status.json created and the VCF Storage Health Dashboards populated.

Actual Behavior

No file created, dashboards empty.

Steps to Reproduce

Run the send-data-to-vrops.py script.

Screenshots

No response

References

No response

feat: format `notifications.json` file to make it readable

Code of Conduct

• I have read and agree to the project's Code of Conduct.
• Vote on this issue by adding a 👍 reaction to the original issue initial description to help the maintainers prioritize.
• Do not leave "+1" or other comments that do not add relevant information or questions.
• If you are interested in working on this issue or have submitted a pull request, please leave a comment.

Description

The Notifications.json file is not in a readable format. The formatting for the file must be fixed.

Use Case(s)

NA

Potential Configuration

No response

References

No response

Update the main `README.md` directory structure

Code of Conduct

• I have read and agree to the project's Code of Conduct.
• Vote on this issue by adding a 👍 reaction to the original issue initial description to help the maintainers prioritize.
• Do not leave "+1" or other comments that do not add relevant information or questions.
• If you are interested in working on this issue or have submitted a pull request, please leave a comment.

Description

The main README for the repo includes a directory structure, but this does not include the new HRM solution and needs to be updated.

Use Case(s)

• Health Reporting and Monitoring

Potential Configuration

No response

References

No response

Missing values in variables.yml in ALB ansible remote authentication playbook

Code of Conduct

• I have read and agree to the project's Code of Conduct.
• Vote on this issue by adding a 👍 reaction to the original issue initial description to help the maintainers prioritize.
• Do not leave "+1" or other comments that do not add relevant information or questions.
• If you are interested in working on this issue or have submitted a pull request, please leave a comment.

VMware Cloud Foundation

5.0.0

Environment Details

ALB 22.1.4

Description

ALB ansible remote authentication playbook's variables.yaml is missing AUTH_MAPPING_PROF_NAME & AUTH_MAPPING_PROF_TYPE definitions which causes the playbook to fail.

Happy to contribute a fix back, along with some typo corrections and YAML validation fixes.

Expected Behavior

Playbook execution completes successfully

Actual Behavior

Playbook execution fails with:
fatal: [localhost]: FAILED! => {"msg": "The task includes an option with an undefined variable. The error was: 'AUTH_MAPPING_PROF_NAME' is undefined. 'AUTH_MAPPING_PROF_NAME' is undefined\n\nThe error appears to be in '/home/user/vvs/validated-solutions-for-cloud-foundation/alb/ansible-examples/remote-authentication-playbook/remote_auth.yaml': line 96, column 5, but may\nbe elsewhere in the file depending on the exact syntax problem.\n\nThe offending line appears to be:\n\n\n - name: Create Group Mapping for 22.x+\n ^ here\n"}

Steps to Reproduce

Use ALB ansible remote authentication playbook against ALB 22.1.4

Screenshots

No response

References

No response

Adjust thresholds for certificates health expiry date

Code of Conduct

• I have read and agree to the project's Code of Conduct.
• Vote on this issue by adding a 👍 reaction to the original issue initial description to help the maintainers prioritize.
• Do not leave "+1" or other comments that do not add relevant information or questions.
• If you are interested in working on this issue or have submitted a pull request, please leave a comment.

VMware Cloud Foundation

v4.4 and v4.5

Environment Details

No response

Description

While testing the solution, we encountered that -

With VCF 4.4 SOS reports RED for certificates if it expires in < 1 day. else its GREEN.

The threhsolds have been updated in VCF 4.5 SOS Utility for Certificates Health data to -

<15 days -- RED
15-30 days -- YELLOW
>30 days -- GREEN

For HRM, set the alert_code based on expiry date of certificates. The thresholds should be same for 4.4 and 4.5.

This needs to be handled in python code so that the alert and alert_code are set appropriately.
Without this, there will be inconsistency in the data reported and alerts raised and the rollup dashboard.

Expected Behavior

Thresholds for Certificates health should be -

<15 days -- RED
15-30 days -- YELLOW
>30 days -- GREEN

Actual Behavior

Currently thresholds are <1 - RED and >1 GREEN. These were set based on values in VCF 4.4

Steps to Reproduce

No response

Screenshots

No response

References

No response

[HRM] Remove SDDC Manager `root` password from Python module

Code of Conduct

• I have read and agree to the project's Code of Conduct.
• Vote on this issue by adding a 👍 reaction to the original issue initial description to help the maintainers prioritize.
• Do not leave "+1" or other comments that do not add relevant information or questions.
• If you are interested in working on this issue or have submitted a pull request, please leave a comment.

Description

With the upcoming release 2.0.0 of VMware.CloudFoundation.Reporting module we no longer need the user to enter the SDDC Manager root password.

Python code must be updated to support 2.0.0 release for VMware.CloudFoundation.Reporting.

Use Case(s)

NA

Potential Configuration

Remove any references to sddc manager root password from the code.

References

vmware/powershell-module-for-vmware-cloud-foundation-reporting#96

Add Guidance on Installing Pythin to the HRM README.md

Code of Conduct

• I have read and agree to the project's Code of Conduct.
• Vote on this issue by adding a 👍 reaction to the original issue initial description to help the maintainers prioritize.
• Do not leave "+1" or other comments that do not add relevant information or questions.
• If you are interested in working on this issue or have submitted a pull request, please leave a comment.

Description

The existing README.md for the Health Reporting and Monitoring for VMware Cloud Foundation provides now guidance or direction on the implementation of Python 3 but its called out as a pre-requisite for the solution.

We should add some direction within the README to help guide the user along with the dependency modules so that we can simply direct the reader in the Validated Solution guide to the README.md so that we keep the content maintained in a single location.

Use Case(s)

• Help the customer install and configure Python 3

Potential Configuration

No response

References

No response

Add vSphere Single Sign-on ring topology to VCF Health Compute dashboard

Code of Conduct

• I have read and agree to the project's Code of Conduct.
• Vote on this issue by adding a 👍 reaction to the original issue initial description to help the maintainers prioritize.
• Do not leave "+1" or other comments that do not add relevant information or questions.
• If you are interested in working on this issue or have submitted a pull request, please leave a comment.

VMware Cloud Foundation

v5.1

Environment Details

No response

Description

VCF Compute Health is missing the data for Ring topology. Even though data is available on Aria Operations under sddc manager VM custom metrics - SOS General Health, it is missing from the dashboard.

Create a view and a link it to the VCF Compute Health dashboard.

Expected Behavior

na

Actual Behavior

na

Steps to Reproduce

No response

Screenshots

No response

References

No response

[HRM] Exception while sending Backup status data to vROps

Code of Conduct

• I have read and agree to the project's Code of Conduct.
• Vote on this issue by adding a 👍 reaction to the original issue initial description to help the maintainers prioritize.
• Do not leave "+1" or other comments that do not add relevant information or questions.
• If you are interested in working on this issue or have submitted a pull request, please leave a comment.

VMware Cloud Foundation

v4.5

Environment Details

NA

Description

This is the error seen in the logs. (See attached logs).

[2023-05-04 01:24:27] INFO - [send-data-to-vrops.py:934] - Pushing Backup status data to vrops
[2023-05-04 01:24:27] INFO - [send-data-to-vrops.py:946] - hostname = sddc-manager.vcf.sddc.lab, component = SDDC Manager
[2023-05-04 01:24:27] INFO - [send-data-to-vrops.py:51] - Exception occurred. Details -
[2023-05-04 01:24:27] INFO - [send-data-to-vrops.py:52] - 'NoneType' object has no attribute 'group'
send-data_2023-05-04_01-17-15.zip

Expected Behavior

Data should be pushed successfully, but an error is raised while parsing the backup JSON.

Actual Behavior

Error in the description.

Steps to Reproduce

Run the script send-data-to-vrops.py

Screenshots

No response

References

No response

Add support for Dell EMC VxRail

Code of Conduct

• I have read and agree to the project's Code of Conduct.
• Vote on this issue by adding a 👍 reaction to the original issue initial description to help the maintainers prioritize.
• Do not leave "+1" or other comments that do not add relevant information or questions.
• If you are interested in working on this issue or have submitted a pull request, please leave a comment.

Description

Add support for VxRail environments

Use Case(s)

VxRail Environments

Potential Configuration

No response

References

No response