As-is Services
Incidents
Key | Short Description | Reporter | Created | Resolved | Summary |
|---|---|---|---|---|---|
Requests
Key | Short Description | Reporter | Created | Resolved | Summary |
|---|---|---|---|---|---|
Change Management
This process primarily targets requests that can be handled with current level of effort (LOE) resources. This process is also designed to detect and redirect items to the EVMS process if they exceed LOE resources.
Successful changes proceed through 5 stages:
1 | Business Case & T/CAM Concurrence | Check that the submitter has stated a plausible business case and the relevant T/CAM agrees |
| 2 | Feasibility | Is the change well-formulated, address a project need and |
| 3 | Planning | A detailed implementation plan is created which takes into account impacts, resource needs, testing and verification. |
| 4 | Insertion | The plan is executed to implement the change. |
| 5 | Assessment | Verification of successful change, issues analysis, documentation and close-out. |
Open Change Requests
| Key | Summary | Process Stage† | Reporter | P | Created | Status |
|---|---|---|---|---|---|---|
Heard on the Street This Week, but no Ticket Filed
New
Previous
It was suggested that per-user storage usage for each shared fileset be made available. Preferably readable by any DM member. Issue filed and implemented. (IHS-767)
- Several users expressed a desire to have the Intel compiler suite (icc) available on last-dev
- Increase ssh idle session timeout, which is currently 1 hr. (John Parejko via Slack)
- Suggestion to deploy kubernetes on PDAC, it is assumed that this is being handled through the rolling-wave (EVMS) process
- Tools for parallel programming in batch computing environment (gnu parallel and others)
Change Process Notes
- Paul has contacted corresponding T/CAMs to understand business need, obtain concurrence & document in each LDMCR
- Change process is being exercised, refined and socialized with T/CAMs as well as submitters
Problem Management
A problem registry has been begun here to analyze incidents in an effort to identify root cause, frequency and severity.
Interactions
Next meeting //
Last PDAC meeting 11/16/2017.
Suspended until after the first of the year since Jeff is in Chile. However, I’m linked in to Chile IT.
Next meeting //
Other business
(None)
Action Items
New
From last week