Versions Compared

Key

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

...

The HL7 DaVinci development team delivers automatically built images via the HSPC Docker Logica Docker Hub organization into public repositories corresponding to public GitHub repositories. Every project is built automatically by Docker Hub according to project-specific settings for branching strategy, testing etc. Upon successful builds, Docker Hub uses automated web hooks to notify HSPCLogica's production container management of the new build becoming available, in turn triggering automated update of HSPCs Logica's cloud environment.

Continuous Deployment Stages

  1. Developer tests code and local images on local machine(s) according to DaVinci policies and procedures.
  2. Developer checks in and pushes code to corresponding branch of a DaVinci GitHub repository. (e.g. `git push`)
  3. Developer merges commits into the deployment branch, if necessary. (Most projects are just committing directly to master.)
  4. GitHub automatically notifies HSPC Docker Logica Docker Hub to trigger automated build process.
  5. Upon successful build and regression testing result, Docker Hub notifies HSPC container Logica container management to pull updated image and roll out to a swarm.

...

Applications MUST NOT use sticky sessions, nor any form of 2nd-level caching requiring similar container affinity. HSPCLogica's reverse proxy environment routes pseudo-randomly and has no mechanism for supporting these types of applications.

...

Per the HSP Marketplace specification, all certificate management and SSL crypto is handled outside the image/container. HSPCLogica's internal reverse proxy handles all cryptography and certificate management. Individual services are forwarded appropriate HTTP headers by the reverse proxy such that the base URL of the request in easily detectable by the application. Other than that, applications do not need to worry about SSL/TLS.