Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

As-is Services

Incidents

  • N created, M resolved.

Created: 

Key

Short Description
SummaryStatusIHS-xxx

Quisque vel arcu cursus, dapibus nisl quis,

l quis, lobortis neque. In eget pretium leo. Cras ut urna tellus. Duis et ipsum auctor sem porttitor dignissim id non justo. Ut ac enim feugiat, scelerisque urna eu, ullamcorper leo.

Status
colourGreen
titleDone

Resolved:

KeyShort Description


Reporter

Created

Resolved

Summary








Requests


SummaryIHS-xxx

Quisque vel arcu cursus, dapibus nisl quis,

l quis, lobortis neque. In eget pretium leo. Cras ut urna tellus. Duis et ipsum auctor sem porttitor dignissim id non justo. Ut ac enim feugiat, scelerisque urna eu, ullamcorper leo.

Discussion of Notable Issues

    • Issue (linked to JIRA ticket)

Requests

Created:

Key

Short Description
SummaryStatusIHS-xxx

Quisque vel arcu cursus, dapibus nisl quis,

l quis, lobortis neque. In eget pretium leo. Cras ut urna tellus. Duis et ipsum auctor sem porttitor dignissim id non justo. Ut ac enim feugiat, scelerisque urna eu, ullamcorper leo.

Status
colourGreen
titleDone

Resolved:

KeyShort Description
SummaryIHS-xxx

Quisque vel arcu cursus, dapibus nisl quis,

l quis, lobortis neque. In eget pretium leo. Cras ut urna tellus. Duis et ipsum auctor sem porttitor dignissim id non justo. Ut ac enim feugiat, scelerisque urna eu, ullamcorper leo.


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 ConcurrenceCheck that the submitter has stated a plausible business case and the relevant T/CAM agrees
2FeasibilityIs the change well-formulated, address a project need and
3PlanningA detailed implementation plan is created which takes into account impacts, resource needs, testing and verification.
4InsertionThe plan is executed to implement the change.
5AssessmentVerification of successful change, issues analysis, documentation and close-out.


Open Change Requests


Key  SummaryProcess Stage†ReporterPCreatedStatus














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

Report format under developmentA problem registry has been begun here to analyze incidents in an effort to identify root cause, frequency and severity.

Interactions

  1. T/CAM interactions


    ITSC

    1. Next meeting //


  1. PDAC

    1. Last PDAC meeting 11/16/2017.  

  2. Summit-base Tiger Team

    1. Suspended until after the first of the year since Jeff is in Chile.  However, I’m linked in to Chile IT.


  3. Infrastructure

Next meeting //

Other business

(None)

Action Items

New


From last week