Skip to main content

Jira Build

 

Epic Summary: Storage Optimization - Snapshot Removal and vSphere Certificate Management

This epic focuses on optimizing storage utilization by removing unnecessary snapshots and ensuring the security of our vSphere environment by managing certificate expiration.  

Tasks:

  1. Snapshot Removal:
    • Identify and remove unused or outdated snapshots post VCSA/ESXi upgrades in XXXXX Lab/Prod.
    • Research Automate removal of Snapshot. (Time/Scheduled)
  2. vSphere Certificate Management:  XXXXX/XXXXXX 
    • Check the expiration status of all vSphere certificates (vCenter Server, ESXi hosts).
    • Provide customer feedback for renew expiring certificates before they become invalid.
    • Establish a process for monitoring certificate validity and timely renewal.

Acceptance Criteria:

  • VCSA has no outdated snapshots. (Y to be defined as a target metric)
  • A report is generated documenting the status of certificates.

==================================================

Jira Summary: Lab Server Cleanup - Snapshot Removal & vSphere Certificate Check

Description:

This task involves cleaning up Lab servers by removing unnecessary snapshots and verifying the health of vSphere certificates.

Tasks:

  1. Snapshot Removal:

    • Identify and remove all unused snapshots on Lab servers.
    • Prioritize removing older snapshots first.
    • Coordinate with Lab server owners for confirmation before deleting critical snapshots (if any).

  2. vSphere Certificate Check:

    • Check the expiration date and validity of vSphere certificates used for server management.
    • If certificates are nearing expiration, initiate the renewal process according to internal procedures.

Acceptance Criteria:

  • All unused snapshots are removed from Lab servers.
  • Free disk space on Lab servers is increased due to snapshot removal.
  • A report is generated documenting the number of snapshots removed from each server.
  • The validity of vSphere certificates is verified.

Comments

Post a Comment

Popular posts from this blog

2 - Dell Open Networking Switch OS10

Managed Object Procedure (MOP) for Upgrading Dell Open Networking Switch OS10 to Latest Firmware on an Air-Gapped System Purpose: This MOP outlines the steps to upgrade the firmware on a Dell Open Networking (OS10) switch to the latest version on an air-gapped system (no internet connection). The upgrade will be performed by transferring the firmware image using Secure Copy (SCP) from a laptop directly connected to the switch's dedicated management interface. Service Impact Summary: The switch's management interface will be unavailable during the upgrade process, which can range from a few minutes to half an hour depending on the switch model and firmware size. Depending on the firmware version being upgraded from, there might be brief service interruptions on data plane ports while the switch reboots after the upgrade. Backup Procedure: Configuration Backup: Connect to the switch using the command-line interface (CLI). Enter the following command to capture the runnin...
Post a Comment
Read more

Swagger

Subject: Next Steps for Troubleshooting Your Filter Issue - Test Scenario with Swagger Subject: Next Steps for Troubleshooting Your Filter Issue - Test Scenario with Swagger Hi [Customer Name], Thank you for your patience as we continue to troubleshoot the filter deletion issue you're experiencing. To further investigate the cause, we'd like your help running a quick test scenario using the Swagger software. Here's what we need you to do: Access Swagger: Open Swagger for our application. You can usually access it through [link to Swagger documentation/interface - replace with specific instructions]. Target Selection: Locate the endpoint related to retrieving filters. This might be named something like "GET /filters". "Try it Out": Click the "Try it out" button associated with the endpoint. Filter Criteria: In the request body section, locate the field for filtering results. Set the criteria to retrieve only filters with an "active...
Post a Comment
Read more

Closure

Closure Criteria: Issue Resolved : The underlying problem has been successfully resolved. Workaround Provided : A temporary solution has been provided, and the user has been informed of the permanent resolution timeline. Issue is Deferred : The customer has agreed to defer resolution to a future release or update. Additional Considerations: Knowledge Base Update : If applicable, the resolution should be documented in the knowledge base for future reference. Follow-up : If necessary, schedule a follow-up ticket to ensure the resolution is holding. Escalation : If the issue cannot be resolved, escalate to BES team.
Post a Comment
Read more