Page History

...

...

• Scott described considerations for cloud usage
  
  • Auto deploy
  • Auto Scale resources
  • Uptime
  • Sharable instances
• Kevin noted that technical is starting to provide ability to deliver what cloud promises.   Cloud is more about changing your development lifecycle than hardware.   Cloud is not server virtualization.  
• Kevin demo'ed the use of Docker with LexEVS
  • Sara asked if it is possible to take a docker image and use it on different tiers - by passing in a variable to let the application know what to configure at that tier.  
    • Kevin - this is the idea - and those variables can be stored in version control.  This simplifies the process.
  • Micro-architectures and micro-services is what is important today.  LexEVS fits this model well.
  • Attempting to document a LexEVS install is complex.  
  • Docker Example has:
    • LexEVS
    • LexEVS-cts2
    • LexEVS-remote
    • mysql
    • uriresolver
  • This docker container configures a complete LexEVS environment .
  • Kevin described the use of a Nexus server.  Similar to maven, docker images can be hosted on a private or public nexus repository.  Nexus has expanded to include docker support - internal docker repositories.
  • Sarah - The tomcat, mysql and os come from public repositories.
  • Application versions can be specified or simply pull the latest from the docker server.
  • Sarah - CBIIT is not ready to support Docker and won't be available by March 2016.  
  • The goal is to provide docker images for on premise (NCI) installation or install to external cloud services as required by NCI. 

...

• • Sara - considerations for storing configuration files - we need to consider how passwords and other information

Discussion: Build and Deployment Process and Discussion: Value Set Editor (Authoring)

Attendees:  Cory, Craig, Scott, Jason, Kim, Larry, Gilberto, Rob

• Dev Ops Discussions carried over from earlier this morning.
  
  • Continuous Integration
    • Cory discussed the Continuous Integration Server usage and how it is used by the Mayo development team.
    • There was discussion about how to include CI server functionality to provide value to both the browser team and LexEVS team.  
    • Currently Jenkins is unofficially supported at NCI, but they are supporting what is needed by the project teams.  
    • Mayo does have Travis and Jenkins, but suggests the use of Jenkins.  
    • Jason - there is interest and some value, but limited given few (one) developers.  It was suggested that it would be best to discuss with the Dev Ops group before setting up something else.  
• Value Set Editor
  • Requirements 
    • Ability to maintain collections and sub-collections of value sets
      • https://nciterms.nci.nih.gov/ncitbrowser/ajax?action=create_src_vs_tree&nav_type=valuesets#

Image Added

• • • • Ability to efficiently load the resolved value sets
  • Tracy - Value Set authoring doesn't occur often.  The value set resolution happens every time there is a new version of NCIT.  
  • FDA and CDISC value sets are based on NCIT concepts.
    • Report writer templates are used for individual value sets.
  • Further review of value set workflow (including resolution) is needed to determine requirements and proposed changes.  

Discussion: The Future of lbGUI

Attendees:  Cory, Craig, Scott, Jason, Kim, Larry, Gilberto, Rob

• Current usage of lbGUI:
  • Mayo team uses the GUI to verify loads. (Development)
  • Tracy uses when the admin scripts aren't working.  (Admin)
  • Rob uses to cleanup  (Admin)
  • Gilberto uses to determine if data is loaded correctly. (Data)
• Scott noted that the representation of data in lbGUI isn't always correct.  It is better to look at DB to determine how things are loaded.   
• Technology needs to be updated
  • Usage is becoming unstable 
  • There are several know bugs.  
• The focus should be on expanding the admin scripts and move away from lbGUI.
• Further review of admin workflow is needed to determine requirements and proposed admin script changes and additions.
  
• lbGUI will continue to be minimally supported as needed by the development team.
• Consider ability to provide viewing additional metadata in the GUI.

Debrief

Attendees:  Cory, Craig, Scott, Jason, Kim, Larry, Gilberto

• Reviewed and prioritized 2015.12 Technical Face-To-Face Prioritization List with the group