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
- 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.
Wiki Markup |
---|
{scrollbar:icons=false} |
...