3. Implementation Steps for COMET NAM
- Independent App Directory Representation
- Requirement: Under the new desktop architecture, COMET NAM must be represented and provisioned as an entirely separate application within the global Application Directory.
Action Required: Establish a unique entry featuring its own distinct, isolated configuration link.
Multi-Version Capability Configuration
Requirement: End-users and testers must be able to concurrently run and validate multiple versions of COMET NAM on a single workstation.
Action Required: Instruct targeted users to navigate to their Citi Desktop user preferences menu and explicitly toggle the multi-version setting to On.
NGD Profile and Stream Synchronization
Requirement: The underlying Next Generation Desktop (NGD) runtime layer strictly automates and manages physical local binary installations. The background deployment agent will only pull assets that match a user's exact parameters.
Action Required: Audit and ensure absolute parity across all COMET NAM user metadata tags (specifically mapping designated stream, environment, and user group profiles).
Dynamic Container Detection & Manifest Validation
Requirement: Citi Desktop dynamically determines build availability by scanning local NGD configuration manifests on the host machine. It will restrict visibility and launching capabilities until local deployment is fully complete.
Action Required: Ensuring sufficient local NGD configuration files on the COMET NAM users' machines is a must.
User Group Distinctiveness & Cataloging
Context: Based on a meeting, it was believed we need to keep the existing user groups distinct.
Action Required: Cataloging existing COMET NAM related groups is a must to maintain clear operational boundaries.
Provisioning of Developer Administrative Group
Context: For EMEA, the UI Platform team provisioned a dedicated developer admin group (
app_harness_ls_157514_comet-emea_developer) to manage configurations and handle UAT promotions.Action Required: We need to request the creation and provisioning of a parallel administrative group for our team—specifically:
app_harness_ls_157514_comet-nam_developer—to grant us administrative control over the COMET NAM configuration.Active Directory (AD) Group for Production Promotions
Context: Moving builds to production requires a designated AD group to authorize and execute promotions.
Action Required: The NAM team needs to identify and agree on the correct AD group (likely our production support group) to be mapped for NAM production promotions.
Isolated Standalone Application Configuration
Context: Per the core migration strategy, we are moving away from multi-stream dropdowns. EMEA was successfully configured and troubleshooted as its own isolated application definition.
Action Required: We must initiate the same process for
comet-nam, actively configuring and troubleshooting it as a distinct, standalone application definition in the directory rather than bundling it under shared configurations.
Top comments (0)