<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="UTF-8">
<title>3. Implementation Steps for COMET NAM Gui Team</title>
<style>
body {
font-family: Calibri, Arial, sans-serif;
font-size: 11pt;
color: #222222;
line-height: 1.4;
margin: 20px;
}
h2 {
color: #1F4E78;
font-size: 16pt;
border-bottom: 2px solid #1F4E78;
padding-bottom: 5px;
margin-bottom: 15px;
}
table {
width: 100%;
border-collapse: collapse;
margin-top: 10px;
font-size: 10.5pt;
}
th {
background-color: #2F5597;
color: #ffffff;
font-weight: bold;
text-align: left;
padding: 10px 12px;
border: 1px solid #1F4E78;
}
td {
padding: 10px 12px;
border: 1px solid #d3d3d3;
vertical-align: top;
}
tr:nth-child(even) {
background-color: #f8f9fa;
}
tr:hover {
background-color: #f1f4f8;
}
.step-num {
font-weight: bold;
text-align: center;
width: 5%;
color: #2F5597;
}
.step-title {
font-weight: bold;
width: 22%;
color: #1a252f;
}
.context-col {
width: 36%;
}
.action-col {
width: 37%;
}
code {
font-family: Consolas, "Courier New", monospace;
background-color: #eef2f5;
padding: 2px 5px;
border-radius: 3px;
font-size: 9.5pt;
color: #c7254e;
}
ul {
margin: 0;
padding-left: 18px;
}
li {
margin-bottom: 4px;
}
</style>
</head>
<body>
<h2>3. Implementation Steps for COMET NAM Gui Team</h2>
<table>
<thead>
<tr>
<th class="step-num">#</th>
<th class="step-title">Implementation Area</th>
<th class="context-col">Requirement / Context</th>
<th class="action-col">Action Required</th>
</tr>
</thead>
<tbody>
<tr>
<td class="step-num">1</td>
<td class="step-title">Independent App Directory Representation</td>
<td>Under the new desktop architecture, <strong>COMET NAM Gui</strong> must be represented and provisioned as an entirely separate application within the global Application Directory.</td>
<td>Establish a unique entry featuring its own distinct, isolated configuration link.</td>
</tr>
<tr>
<td class="step-num">2</td>
<td class="step-title">Multi-Version Capability Configuration</td>
<td>End-users and testers must be able to run and validate multiple versions of COMET NAM Gui on a single workstation.</td>
<td>Instruct targeted users to navigate to their Citi Desktop user preferences menu and explicitly toggle the multi-version setting to <strong>On</strong>.</td>
</tr>
<tr>
<td class="step-num">3</td>
<td class="step-title">NGD Profile & Stream Synchronization</td>
<td>The underlying 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.</td>
<td>Audit and ensure absolute parity across all COMET NAM Gui user metadata tags (specifically mapping designated stream, environment, and user group profiles).</td>
</tr>
<tr>
<td class="step-num">4</td>
<td class="step-title">Dynamic Container Detection & Manifest Validation</td>
<td>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.</td>
<td>Ensure sufficient local NGD configuration files are present on the COMET NAM Gui users' machines.</td>
</tr>
<tr>
<td class="step-num">5</td>
<td class="step-title">User Group Distinctiveness & Cataloging</td>
<td>Based on recent discussions, existing user groups were initially thought to remain distinct. However, the UI Platform team strongly recommends simplifying this into just two groups: <em>one pilot production group</em> and <em>one general production group</em>, eliminating all others.</td>
<td>
<ul>
<li>Catalog existing COMET NAM Gui related groups to maintain clear operational boundaries.</li>
<li>Resolve with UI Platform whether pilot and general groups are still required.</li>
</ul>
</td>
</tr>
<tr>
<td class="step-num">6</td>
<td class="step-title">Provisioning of Developer Administrative Group</td>
<td>For EMEA, the UI Platform team provisioned a dedicated developer admin group (<code>app_harness_ls_157514_comet-emea_developer</code>) to manage configurations and handle UAT promotions.</td>
<td>Request the creation and provisioning of a parallel administrative group for our team: <code>app_harness_ls_157514_comet-nam_developer</code> to grant administrative control over the COMET NAM Gui configuration.</td>
</tr>
<tr>
<td class="step-num">7</td>
<td class="step-title">Active Directory (AD) Group for Production Promotions</td>
<td>Moving builds to production requires a designated AD group to authorize and execute promotions.</td>
<td>Identify and agree on the correct AD group (comparable to our production support group) to be mapped for NAM Gui production promotions.</td>
</tr>
<tr>
<td class="step-num">8</td>
<td class="step-title">Isolated Standalone Application Configuration</td>
<td>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.</td>
<td>Initiate the same process for COMET NAM Gui, actively configuring and troubleshooting it as a distinct, standalone application definition in the directory rather than bundling it under shared configurations.</td>
</tr>
<tr>
<td class="step-num">9</td>
<td class="step-title">Deployment Pipeline Integration</td>
<td>Application deployments will continue to be managed through uDeploy.</td>
<td>Ensure continuation of deployment via uDeploy, unless superseded by LightSpeed Enterprise Harness/Ansible deployment.</td>
</tr>
<tr>
<td class="step-num">10</td>
<td class="step-title">Sequencing of Group Creation</td>
<td>Inquiry raised by Guramrit Kaur Bamrah regarding the sequencing of group creation and user mapping for consolidating groups into a single PROD group:<br>
<em>Clarifying if the mandatory workflow requires:</em>
<ol style="margin-top:5px; padding-left:18px;">
<li>Creating group in Atom</li>
<li>Provisioning/adding appropriate users in Atom</li>
<li>Configuring group settings in AppD portal</li>
</ol>
</td>
<td>
<ul>
<li><strong>Process Verification:</strong> Confirm with Anuj Gakhar and Sumit Mangal the precise execution order required for group consolidation in Atom vs. AppD portal.</li>
<li><strong>Impact Assessment (NAM Group):</strong> Determine if the NAM regional group will be merged into the consolidated PROD group or maintained as a separate entity during Atom launcher migration.</li>
</ul>
</td>
</tr>
</tbody>
</table>
</body>
</html>
Query Filter
Posted on
bridge-43
For further actions, you may consider blocking this person and/or reporting abuse
Top comments (0)