Page History

Unknown User (gcomoretto)

Margaret Gelman

• The target is to have CMDB that collect all configuratin items involved in the business services, characterize them in all relevant aspects:
  
  • description, implementation, relation with other items, etc
• Three aspects of the CMDB:
  • Impact Analysis (from operations, when an incident happens, to analyze and derive to the proper area (component, configuration item)
  • Understand what t a complete change means: software, document, procedures, protocols... (Auxiliary CIs)
  • The relation of the CMDB to the service catalogue
    • Services maintained in the Service Management Tool that collects everything

Furthermore:

• CMDB is important to understand all source of data, and how to manage the change process on them
• To make available a Sandbox are, where a new configuration is consolidate, without affecting the actual operation configuration
• Financial aspects

CMDB tool under investigation

Service management tool under investivation

The modeling is done in ARCHIMET using the TOGAF language

Key person for CMDB is Margaret Gelman

Unknown User (gcomoretto)

Margaret Gelman

Session with Donald Petravick: 

• The actual product tree at NCSA is managed via https://www.archimatetool.com/ using TOGAS language and is going much more detailed from the model maintained in Magic Draw.
• The same tools is mento to manage low level requirement.
• Need to define a strategy to synchronize Magic Draw with ArchimateTool.
  • • Requirements: LSE-61 source of true in Magic Drow and synchronized in ArchimateTool, Low Level requirements for tools developped at NCSA to be source of true in ArchimateTool and synchronized back into Magic Draw
    • For the model, we need to keep the high level source of true in Magic Draw and the low level in ArchimateTool. Some products may not be needed to be synchronized (like hardware components).
  • Security requirements (from security office) to be kept in account for LSST internally developed SW (more next day)

Unknown User (gcomoretto)

Margaret Gelman

• Model in Magic Draw and document tree (discussed and proposed vay forward the first day)
• Security Plan:
  • There is a security requirement in LSE-30
  • There is a Security plan under preparation at LDM level
  • A security requirement document would be needed at LDM level that clarify the requirements to be applicable to DM
  • Each DM component, should include a requirement in their requirement document that point to the general DM requirement specification
• Data Release production pipeline (session with Hsin-Fang Chiang)
  • There is a pipeline in the development environment at NCSA that implements the DRP payload.
  • this pipeline is deployed by John Swinbank weekly and is used by NCSA people and Developer for testing
  • the SW product to control the pipeline orchestration is `ctrl_pool`. Once Gen3 butler implementation will be consolidated, it will be possible to develop at NCSA a new bath processing application that interfaces
  • In operation NCSA plan to use docker images with Singularity
  • There is a validation environment maintained separated by Hsin-Fang Chiang
    • Unknown User (gcomoretto) suggested to have a joint session (via slack or bluejeans) in order to see how this environment is set-up

Unknown User (gcomoretto)

Margaret Gelman

• Test Management approach review. The plan is to apply it to the Operations Rehearsal 1 (commissioning)
  • lack of information from LDM-503. Leanne Guy suggest to proceed as done for already covered milestones: proactively defined the OR and the test cases. Margaret Gelman's concerns are that this is
• Operation Rehearsal #1 session with Robert Gruendl
  • Try to get a better description on what the activity is involving Leanne Guy or Simon Krughoff
  • Define a list of services (from NCSA point of view) involved in the activity
    • In addition to the modeling activity done at NCSA with ArchimateTool, there is a document, LDM-230 that describes the Operational Concepts from NCSA perspective, from this document can be derived use-cases and requirements
  • Identify the underlying SW products that need to be ready for the OR#1
  • Write the test cases in JIRA
  • Execute the test cases in a test campaign
• Release management from NCSA point of view, if the process to implement in

• operation a change:
  • major change (need a deployment procedure
  • minor change (need a deployment procedure)
  • Routine change that fo not affect the service nor the stakeholders.