sarman/tftsr-devops_investigation
1
0
Fork 0
Code Issues 1 Pull Requests Actions 34 Packages Projects 3 Releases 11 Wiki Activity

Searching for the upgrade guide in confluence, the app was not able to retrieve the docuument #33

New Issue
Closed
opened 2026-04-10 16:16:17 +00:00 by jtayeh · 1 comment
jtayeh commented 2026-04-10 16:16:17 +00:00
Copy Link

how do i upgrade vesta nxt to 1.1.9

Based on the internal documentation, I can see there are references to VESTA NXT upgrade procedures, but the specific documentation shown is for version 1.0.12 PATCH1, not version 1.1.9.

The internal documentation references:

For the specific upgrade to version 1.1.9, you should:

  1. Check the internal documentation for version 1.1.9 specific procedures at the Confluence link above, as upgrade steps can vary between versions
  2. Review the training materials mentioned in the VESTA NXT 101 documentation
  3. Follow the established upgrade pattern which typically includes:
    • Management Stack (Harbor/Vault) upgrades first
    • Call Handling System (CHS) upgrades second
    • Proper backup procedures before starting

Since upgrade procedures can be version-specific and may include critical system dependencies, I'd recommend consulting the complete internal upgrade documentation for version 1.1.9 rather than following generic upgrade steps. The internal docs should contain the specific sequence, prerequisites, and any version-specific considerations for 1.1.9.

If you don't find 1.1.9 specific documentation at those links, you may need to contact your internal VESTA NXT team or check for updated documentation in your Confluence system.

what is the process to upgrade VESTA NXT 1.1.9

I can see from the internal documentation that there are references to VESTA NXT deployment processes and management systems, but the specific upgrade process from version 1.1.9 is not detailed in the available documentation.

From the internal docs, I can see that:

  • VESTA NXT has a complex CI/CD pipeline managed through GitHub Actions and the apollo_cicd-control-center repository
  • There's a deployment process that involves multiple environments (DEV → STAGE → STAGE-IOT → PROD)
  • The system uses Kubernetes manifests and deployment scripts for deployments

However, for the specific upgrade process from version 1.1.9, you'll need to:

General Upgrade Process Recommendations:

  1. Review Release Notes: Check the official VESTA NXT release documentation for version-specific upgrade instructions and breaking changes

  2. Backup Current System:

    • Database backups
    • Configuration backups
    • Document current version and configurations

  3. Test in Non-Production Environment:

    • Deploy the upgrade in DEV/STAGE environments first
    • Validate all functionality works as expected

  4. Follow the CI/CD Pipeline:

    • Based on the internal docs, upgrades would likely go through the standard pipeline: DEV → STAGE → STAGE-IOT → PROD

  5. Coordinate with Teams:

    • Plan maintenance windows
    • Notify stakeholders
    • Have rollback procedures ready

Recommended Next Steps:

For the specific 1.1.9 upgrade process, I recommend:

  • Consulting the official VESTA NXT upgrade documentation
  • Contacting the VESTA NXT support team or your system administrator
  • Reviewing any version-specific migration guides or scripts

The internal documentation shows this is a complex system with multiple components (Kubernetes, databases, microservices), so following official upgrade procedures is critical to avoid system issues.

what is the process to upgrade VESTA NXT 1.1.9

I do not have access to specific upgrade processes for VESTA NXT versions. To get detailed instructions on upgrading from VESTA NXT 1.1.9, I recommend the following:

  • Consult the official VESTA NXT documentation: Look for upgrade guides or release notes specific to version 1.1.9 and the target version you are upgrading to.
  • Contact VESTA NXT support: Reach out to the VESTA NXT support team for assistance and specific instructions for your upgrade path.

While I don't have the precise steps, here are some general considerations that usually apply to software upgrades:

  1. Review Release Notes: Understand the changes, new features, bug fixes, and any potential compatibility issues in the target version.
  2. Backup: Create a full backup of your existing VESTA NXT environment, including databases, configurations, and any custom files. This is crucial for rollback purposes if something goes wrong.
  3. Environment Preparation: Ensure your server environment meets the minimum requirements for the new version. This may involve updating operating systems, Java versions, or other dependencies.
  4. Testing: It's highly recommended to perform the upgrade in a test or staging environment that mirrors your production setup. This allows you to identify and resolve any issues before affecting your live system.
  5. Upgrade Process: Follow the documented upgrade procedure, which usually involves running specific scripts or installers.
  6. Verification: After the upgrade, thoroughly test all VESTA NXT functionalities to ensure everything is working as expected.
  7. Monitoring: Keep a close eye on the system's performance and stability after the upgrade.

what is the process to upgrade VESTA NXT 1.1.9 AND TRY LOOKING https://confluence.mot-solutions.com/display/VESTANXT/Vesta+NXT+-+Operating+Procedures+Home

The provided URL leads to a general landing page for VESTA NXT Operating Procedures. To provide a specific upgrade process for VESTA NXT 1.1.9, I would need a document that outlines the exact steps.

However, I can provide a general outline of what a typical upgrade process might involve, based on common software upgrade practices and the information available about VESTA NXT from the other documents. Keep in mind that this is a generalized approach, and the specific steps for VESTA NXT 1.1.9 could differ.

General VESTA NXT Upgrade Process (Conceptual):

  1. Planning and Preparation:

    • Review Release Notes: Obtain and carefully review the release notes for the target VESTA NXT version (e.g., 1.2.0 or later). This document will outline new features, bug fixes, and, most importantly, any breaking changes or compatibility considerations.
    • Compatibility Check: Verify that your current hardware and software environment meets the minimum requirements for the target VESTA NXT version.
    • Backup: Perform a full backup of your existing VESTA NXT system, including databases, configuration files, and any custom scripts or configurations. This is crucial for rollback purposes.
    • Test Environment: Ideally, stage the upgrade in a non-production (staging/testing) environment that mirrors your production setup. This allows you to identify and resolve any issues before affecting live operations.
    • Downtime Planning: Schedule a maintenance window for the upgrade, considering the estimated downtime and potential rollback time.
    • Communication: Notify users about the planned maintenance and potential service interruption.

  2. Upgrade Execution:

    • Stop VESTA NXT Services: Gracefully shut down all VESTA NXT services to ensure data consistency.
    • Install New Version: Install the new VESTA NXT version using the provided installation packages or scripts. Follow the installation instructions in the release notes.
    • Database Migration: If the upgrade involves database schema changes, run the necessary database migration scripts.
    • Configuration Updates: Update configuration files to reflect any changes required by the new version. This may involve merging your existing configurations with the new default configurations.
    • Start VESTA NXT Services: Start the VESTA NXT services in the correct order.
    • Verification: Verify that the core VESTA NXT services are running correctly and that basic functionality is working as expected.

  3. Testing and Validation:

    • Functional Testing: Perform thorough functional testing to ensure that all features and functions of VESTA NXT are working as expected.
    • Regression Testing: Run regression tests to identify any unintended side effects of the upgrade.
    • Performance Testing: Monitor system performance to ensure that the upgrade has not negatively impacted performance.

  4. Production Deployment:

    • Repeat in Production: Once you are confident that the upgrade is successful in the test environment, repeat the process in your production environment.
    • Monitoring: Closely monitor the system after the upgrade to identify and address any issues that may arise.

  5. Rollback (if necessary):

    • If any critical issues are encountered during or after the upgrade, be prepared to roll back to the previous version using your backups.

Specific Considerations based on internal documentation:

  • CI/CD Pipeline: VESTA NXT utilizes a CI/CD pipeline (as mentioned in the CI/CD documentation) which may automate parts of the upgrade process, especially in development and staging environments. Look for specific workflows related to deployments.
  • Environments: The CI/CD documentation mentions different environments (DEV, STAGE, STAGE-IOT, PROD). The upgrade process may involve deploying to these environments sequentially.
  • Artifacts: The build process produces ccch-kubernetes-<commit_sha> artifacts containing Kubernetes manifests and deployment scripts. Upgrades may involve deploying these new artifacts.

To get the precise upgrade procedure, I recommend searching specifically for "upgrade VESTA NXT 1.1.9 to [TARGET VERSION]" within the internal documentation. Also, look for documents related to "release notes" for versions after 1.1.9.

how do i upgrade vesta nxt to 1.1.9 Based on the internal documentation, I can see there are references to VESTA NXT upgrade procedures, but the specific documentation shown is for version 1.0.12 PATCH1, not version 1.1.9. The internal documentation references: - **VESTA NXT Upgrade procedures**: https://confluence.mot-solutions.com/display/VESTANXT/MAN-VXT-010+VESTA+NXT+Upgrade+v1.0.12+PATCH1 - **Training materials** covering upgrade processes: https://drive.google.com/drive/folders/1mPTWUe-oQka44TIvC61-cnVRlX9rjjdW For the specific upgrade to version 1.1.9, you should: 1. **Check the internal documentation** for version 1.1.9 specific procedures at the Confluence link above, as upgrade steps can vary between versions 2. **Review the training materials** mentioned in the VESTA NXT 101 documentation 3. **Follow the established upgrade pattern** which typically includes: - Management Stack (Harbor/Vault) upgrades first - Call Handling System (CHS) upgrades second - Proper backup procedures before starting Since upgrade procedures can be version-specific and may include critical system dependencies, I'd recommend consulting the complete internal upgrade documentation for version 1.1.9 rather than following generic upgrade steps. The internal docs should contain the specific sequence, prerequisites, and any version-specific considerations for 1.1.9. If you don't find 1.1.9 specific documentation at those links, you may need to contact your internal VESTA NXT team or check for updated documentation in your Confluence system. what is the process to upgrade VESTA NXT 1.1.9 I can see from the internal documentation that there are references to VESTA NXT deployment processes and management systems, but the specific upgrade process from version 1.1.9 is not detailed in the available documentation. From the internal docs, I can see that: - VESTA NXT has a complex CI/CD pipeline managed through GitHub Actions and the apollo_cicd-control-center repository - There's a deployment process that involves multiple environments (DEV → STAGE → STAGE-IOT → PROD) - The system uses Kubernetes manifests and deployment scripts for deployments However, for the specific upgrade process from version 1.1.9, you'll need to: ## General Upgrade Process Recommendations: 1. **Review Release Notes**: Check the official VESTA NXT release documentation for version-specific upgrade instructions and breaking changes 2. **Backup Current System**: - Database backups - Configuration backups - Document current version and configurations 3. **Test in Non-Production Environment**: - Deploy the upgrade in DEV/STAGE environments first - Validate all functionality works as expected 4. **Follow the CI/CD Pipeline**: - Based on the internal docs, upgrades would likely go through the standard pipeline: DEV → STAGE → STAGE-IOT → PROD 5. **Coordinate with Teams**: - Plan maintenance windows - Notify stakeholders - Have rollback procedures ready ## Recommended Next Steps: For the specific 1.1.9 upgrade process, I recommend: - Consulting the official VESTA NXT upgrade documentation - Contacting the VESTA NXT support team or your system administrator - Reviewing any version-specific migration guides or scripts The internal documentation shows this is a complex system with multiple components (Kubernetes, databases, microservices), so following official upgrade procedures is critical to avoid system issues. what is the process to upgrade VESTA NXT 1.1.9 I do not have access to specific upgrade processes for VESTA NXT versions. To get detailed instructions on upgrading from VESTA NXT 1.1.9, I recommend the following: * **Consult the official VESTA NXT documentation:** Look for upgrade guides or release notes specific to version 1.1.9 and the target version you are upgrading to. * **Contact VESTA NXT support:** Reach out to the VESTA NXT support team for assistance and specific instructions for your upgrade path. While I don't have the precise steps, here are some general considerations that usually apply to software upgrades: 1. **Review Release Notes:** Understand the changes, new features, bug fixes, and any potential compatibility issues in the target version. 2. **Backup:** Create a full backup of your existing VESTA NXT environment, including databases, configurations, and any custom files. This is crucial for rollback purposes if something goes wrong. 3. **Environment Preparation:** Ensure your server environment meets the minimum requirements for the new version. This may involve updating operating systems, Java versions, or other dependencies. 4. **Testing:** It's highly recommended to perform the upgrade in a test or staging environment that mirrors your production setup. This allows you to identify and resolve any issues before affecting your live system. 5. **Upgrade Process:** Follow the documented upgrade procedure, which usually involves running specific scripts or installers. 6. **Verification:** After the upgrade, thoroughly test all VESTA NXT functionalities to ensure everything is working as expected. 7. **Monitoring:** Keep a close eye on the system's performance and stability after the upgrade. what is the process to upgrade VESTA NXT 1.1.9 AND TRY LOOKING https://confluence.mot-solutions.com/display/VESTANXT/Vesta+NXT+-+Operating+Procedures+Home The provided URL leads to a general landing page for VESTA NXT Operating Procedures. To provide a specific upgrade process for VESTA NXT 1.1.9, I would need a document that outlines the exact steps. However, I can provide a general outline of what a typical upgrade process might involve, based on common software upgrade practices and the information available about VESTA NXT from the other documents. Keep in mind that this is a generalized approach, and the specific steps for VESTA NXT 1.1.9 could differ. **General VESTA NXT Upgrade Process (Conceptual):** 1. **Planning and Preparation:** * **Review Release Notes:** Obtain and carefully review the release notes for the target VESTA NXT version (e.g., 1.2.0 or later). This document will outline new features, bug fixes, and, most importantly, any breaking changes or compatibility considerations. * **Compatibility Check:** Verify that your current hardware and software environment meets the minimum requirements for the target VESTA NXT version. * **Backup:** Perform a full backup of your existing VESTA NXT system, including databases, configuration files, and any custom scripts or configurations. This is crucial for rollback purposes. * **Test Environment:** Ideally, stage the upgrade in a non-production (staging/testing) environment that mirrors your production setup. This allows you to identify and resolve any issues before affecting live operations. * **Downtime Planning:** Schedule a maintenance window for the upgrade, considering the estimated downtime and potential rollback time. * **Communication:** Notify users about the planned maintenance and potential service interruption. 2. **Upgrade Execution:** * **Stop VESTA NXT Services:** Gracefully shut down all VESTA NXT services to ensure data consistency. * **Install New Version:** Install the new VESTA NXT version using the provided installation packages or scripts. Follow the installation instructions in the release notes. * **Database Migration:** If the upgrade involves database schema changes, run the necessary database migration scripts. * **Configuration Updates:** Update configuration files to reflect any changes required by the new version. This may involve merging your existing configurations with the new default configurations. * **Start VESTA NXT Services:** Start the VESTA NXT services in the correct order. * **Verification:** Verify that the core VESTA NXT services are running correctly and that basic functionality is working as expected. 3. **Testing and Validation:** * **Functional Testing:** Perform thorough functional testing to ensure that all features and functions of VESTA NXT are working as expected. * **Regression Testing:** Run regression tests to identify any unintended side effects of the upgrade. * **Performance Testing:** Monitor system performance to ensure that the upgrade has not negatively impacted performance. 4. **Production Deployment:** * **Repeat in Production:** Once you are confident that the upgrade is successful in the test environment, repeat the process in your production environment. * **Monitoring:** Closely monitor the system after the upgrade to identify and address any issues that may arise. 5. **Rollback (if necessary):** * If any critical issues are encountered during or after the upgrade, be prepared to roll back to the previous version using your backups. **Specific Considerations based on internal documentation:** * **CI/CD Pipeline:** VESTA NXT utilizes a CI/CD pipeline (as mentioned in the CI/CD documentation) which may automate parts of the upgrade process, especially in development and staging environments. Look for specific workflows related to deployments. * **Environments:** The CI/CD documentation mentions different environments (DEV, STAGE, STAGE-IOT, PROD). The upgrade process may involve deploying to these environments sequentially. * **Artifacts:** The build process produces `ccch-kubernetes-<commit_sha>` artifacts containing Kubernetes manifests and deployment scripts. Upgrades may involve deploying these new artifacts. To get the precise upgrade procedure, I recommend searching specifically for "upgrade VESTA NXT 1.1.9 to \[TARGET VERSION]" within the internal documentation. Also, look for documents related to "release notes" for versions after 1.1.9.
sarman self-assigned this 2026-04-10 16:16:39 +00:00
sarman added this to the Bugs project 2026-04-10 16:16:43 +00:00
sarman added this to the Release Candidit milestone 2026-04-10 16:16:47 +00:00
sarman added the
Kind/Bug
 label 2026-04-10 16:16:51 +00:00
sarman commented 2026-04-15 00:39:17 +00:00
Owner
Copy Link

This issue has been fixed in PR #44 which implements query expansion across all integration search functions. The search now finds semantically related content (product name variants like VNXT, Vesta NXT, and version number variations) instead of just exact query matches.

PR: #44

This issue has been fixed in PR #44 which implements query expansion across all integration search functions. The search now finds semantically related content (product name variants like VNXT, Vesta NXT, and version number variations) instead of just exact query matches. PR: https://gogs.tftsr.com/sarman/tftsr-devops_investigation/pulls/44
sarman added reference feature/integration-search-expansion 2026-04-15 01:37:26 +00:00
Sign in to join this conversation.
feature/integration-search-expansion
Branches Tags
Labels
Clear labels   
Compat/Breaking

Breaking change that won't be backward compatible

  
Kind/Bug

Something is not working

  
Kind/Documentation

Documentation changes

  
Kind/Enhancement

Improve existing functionality

  
Kind/Feature

New functionality

  
Kind/Security

This is security issue

  
Kind/Testing

Issue or pull request related to testing

  
Priority
Critical
The priority is critical

  
Priority
High
The priority is high

  
Priority
Low
The priority is low

  
Priority
Medium
The priority is medium

  
Reviewed
Confirmed
Issue has been confirmed

  
Reviewed
Duplicate
This issue or pull request already exists

  
Reviewed
Invalid
Invalid issue

  
Reviewed
Won't Fix
This issue won't be fixed

  
Status
Abandoned
Somebody has started to work on this but abandoned work

  
Status
Blocked
Something is blocking this issue or pull request

  
Status
Need More Info
Feedback is required to reproduce issue or to continue work

No Label
Compat/Breaking
Kind/Bug
Kind/Documentation
Kind/Enhancement
Kind/Feature
Kind/Security
Kind/Testing
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Reviewed
Confirmed
Reviewed
Duplicate
Reviewed
Invalid
Reviewed
Won't Fix
Status
Abandoned
Status
Blocked
Status
Need More Info
Milestone
Clear milestone
No items
No Milestone
Release Candidit
Projects
Clear projects
No project
Bugs
Assignees
Clear assignees
No Assignees
sarman
2 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Depends on
#44 feat(integrations): implement query expansion for semantic search
sarman/tftsr-devops_investigation
Reference: sarman/tftsr-devops_investigation#33
No description provided.
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?