DEV Community

Query Filter
Query Filter

Posted on

bridge-37

Welcome to the project! This migration can feel like a lot of moving parts, but when you look at the core strategy and these meeting notes together, the big picture becomes very clear.

The strategy is all about moving off the legacy Atom Launcher and onto Citi Desktop. The meeting notes from your new image show the real-world, hands-on implementation of that strategy—specifically focusing on migrating the COMET application (specifically the comet-emea stream).

1. Summary of the Meeting Notes (The Image)

The meeting notes capture technical hurdles, configuration decisions, and permission updates for the COMET EMEA application migration:

  • Entitlement Issue Resolved: An issue where users couldn't launch the app because of an incorrect environment variable (ngd_env) was fixed. Because of this, the comet-emea stream can now be successfully launched in the Development (DEV) environment from Citi Desktop.
  • Deployment Tooling: Application deployments will continue to be managed through uDeploy.
  • The User Group Bottleneck:
  • The Problem: Citi Desktop currently only allows one user group per application configuration. If COMET tried to keep all of its existing production user groups, it would force the team to create over 20+ separate application configurations.

  • The Solution: The UI Platform team strongly recommends simplifying this to just two groups: one pilot production group and one general production group, eliminating all the others.

  • User Visibility & Bulk Migration: Users only see an app configuration if they are added to its corresponding EEMS group. The UI Platform team has offered to handle the bulk migration of these users.

  • Administrative Access Granted: The UI Platform team added an admin group (app_harness_ls_157514_comet-emea_developer) to the COMET EMEA configuration. This allows the team to modify configurations and promote builds to UAT (User Acceptance Testing).

  • Version Visibility: Previous versions of the GUI will remain visible to users; Citi Desktop allows displaying up to three versions.

  • Next Steps:

  • The Global COMET team needs to discuss how they will consolidate and migrate their existing user groups.

  • The COMET EMEA team must determine the correct Active Directory (AD) group to use for promoting builds to production (likely a production support group).

  • Schedule a follow-up call with the UI Platform team to resolve any remaining roadblocks.

2. Correlation: Meeting Notes vs. Core Migration Strategy

Here is how the specific points from the team's meeting align with the master migration blueprint you saw earlier:

Core Migration Strategy (What was planned) Meeting Discussion (What is actually happening)
Separating Streams into Individual Apps


The strategy mandates that regional "streams" (like NAM, APAC, EMEA) must be split into distinct, independently defined applications in the App Directory. | Applying the Rule to COMET


The team is actively configuring and troubleshooting comet-emea as its own isolated app configuration rather than a sub-option in a dropdown. |
| User Groups & Phased Rollouts


The strategy highlights using "user groups within streams" to handle phased rollouts (such as pilot or beta users). | Consolidating User Groups


Because Citi Desktop only allows one user group per config, the team is following the strategy's exact philosophy by consolidating down to exactly two groups: one pilot group and one general group. |
| NGD System Integration


The strategy relies on the local NGD system and local configuration environment variables to pull and run the correct client builds. | Fixing the NGD Environment


The first roadblock resolved in the meeting was a misconfigured ngd_env variable, which was directly blocking the NGD system from launching the app in DEV. |
| Multi-Version Launching


Citi Desktop is built to allow users to see and choose between multiple deployed versions of the GUI. | Confirming Version Limits


The meeting confirms this operational capability is working, noting that Citi Desktop will display up to three previous versions of the GUI to the users. |

What this means for you as a newcomer:

  1. The Architecture is Modular: Instead of managing one massive COMET installation with regional settings, you are managing independent regional app configurations (like EMEA).
  2. Watch the Environment Variables: The transition depends heavily on local NGD configurations (ngd_env). If an app won't launch on your machine or a user's machine, this is the first place to look.
  3. Keep Permissions Simple: Be mindful of the "one user group per configuration" limitation in Citi Desktop. We are actively trying to avoid creating dozens of duplicate configurations by keeping user groups strictly limited to Pilot and General.

Top comments (0)