Official docker images for deployment?

[preston]

It's good to see that there is some effort in providing containers for deployment. Are official images available? Folks generally don't expect to build their own when only wanting to deploy a service. :)

[hsbauer]

We are starting to see some interest in providing containers, but the containers in this project are part of a system test that works through testing the interdependencies of a number of services used and offered by the entire set of LexEVS/CTS2 services. They aren't meant to be used independently or otherwise as part of a deployment package. However, I'll pass along your interest to our sponsors. There is a movement towards this type of deployment, but I it's not an immediate priority. Hopefully comments like yours will step that priority up a little.

[preston]

Would you accept patches if we put in the effort to make this more generic?

[craigstancl]

Preston, thanks for the offer. If you wish to contribute your efforts back to our project we'd gladly review. Can you share a bit more about what you have in mind? (I'm the lead for this project with Scott Bauer).

[preston]

CC @msmtms

[craigstancl]

Preston, would you be willing to meet with us to briefly discuss what you are suggesting? I'd be glad to set up time we could all talk.

[preston]

@craigstancl @msmtms For sure. Early next week? Let me get one of our project leads to set this up.

[preston]

@craigstancl @hsbauer To answer your prior question though, what tends to work really well is if individual application images are both treated as ephemeral and where dependencies on external or environment-specific things -- such as database URLs, usernames, passwords, API keys etc -- are injected via the native environment variable mechanism. This allows developers to build a release, fully test it, and then release the byte-identical image to customers knowing that it is exactly what has been verified and is trivially reconfigurable by the customer at runtime based on the local environment.

This request is on behalf of the AppWorks team at Arizona State University, though I'd really like to get LexEVS (particularly JPA builds) published to the future HSPC Marketplace at well, such that it can be distributed and deployed automatically by member provider organizations. The "Service Qualities" section here has some content on best practices: https://healthservices.atlassian.net/wiki/display/PE/Platform+Engineering

[preston]

CC @mohitkm ^-- the meeting I mentioned.

[mohitkm]

Thank you @preston. @craigstancl As Preston mentioned, we would like to set up the meeting as soon as possible. Could you indicate your availability for next week? @msmtms

[craigstancl]

We would be available Tuesday and Thursday (May 16,18) afternoon (noon to 5PM CDT).
Would either of those days work for you?

It may be easier to email me directly at [email protected].