<html> <head> <meta content="text/html; charset=utf-8" http-equiv="Content-Type"> </head> <body bgcolor="#FFFFFF" text="#000000"> <div class="moz-cite-prefix">On 05/24/2016 10:38 AM, Brent Baude wrote: </div> <blockquote cite="mid:1464100698.3877.14.camel@redhat.com" type="cite"> <pre wrap="">Comments inline... On Tue, 2016-05-24 at 09:49 -0400, Scott McCarty wrote: </pre> <blockquote type="cite"> <pre wrap="">All, Last week at the container interlock, one of you (sorry, can't remember who, maybe Diogones?) was talking about the Middleware team building "base images" which contained VMs. As a follow up, I wanted to understand what was meant by that. I think one of two things could be happening, but I didn't want to rat hole the presentation. 1. We are not using the word base image correctly? 2. We are planning on releasing Middleware base images? 3. More complicated. Relies on RHEL, but squashed (still has a base image of RHEL) If #1, check out this article [1] which I did a ton of homework on and references Docker's documentation, which defines a base image as an image with no parent layer. </pre> </blockquote> <pre wrap="">That is the definition I also tend to favor. I also tend to only associate base images with distributions/OS's. </pre> <blockquote type="cite"> <pre wrap="">If #2, I think the RHEL team and the middleware team should talk. I believe we really need to make sure all software in Red Hat products rely on the RHEL "base image" and should probably NOT be creating their own base images. </pre> </blockquote> <pre wrap=""> Agree completely. However, if all RH middleware images contained a significant, similar set of additional packages/configuration, it might make sense to have a RH middleware layered image based on the official base-image. This theoretically could make life easier for folks.</pre> </blockquote> +1 on "layered image" nomenclature +1 on building a tree structure (e.g. MW core build). <blockquote cite="mid:1464100698.3877.14.camel@redhat.com" type="cite"> <pre wrap=""> </pre> <blockquote type="cite"> <pre wrap="">If #3, I think we should discuss what we message to the world (especially customers) about how these are built and we should probably be careful calling them base images. Perhaps, something like an Application Image or Composed Image? Perhaps talking about how they an be used as base images, but are actually rely on a RHEL base image? It might not seem important in this small case, but I foresee massive confusion if we don't perfectly align now before we 1000s of images (currently at just over 100 and growing fast). </pre> </blockquote> <pre wrap=""> In the dev world, we have called these "layered images." But agree, some sort of name could make messaging clearer.</pre> </blockquote> +1 I have used these in my vocabulary for a while. Also, use that in my public articles. I would be more than happy to standardize on that. Just left it a bit open as I know that "nameing" things can drive people into a tailspin, and I am open to peoples ideas. That said, I think the ship has sailed and I am not sure Red Hat is "really" in a place to dictate the nomenclature. Much easier to just "go with the flow" and make sure we all start using the same language as not to confuse each other. Per my first three items, I genuinely wasn't sure what was meant by "base image"... <blockquote cite="mid:1464100698.3877.14.camel@redhat.com" type="cite"> <pre wrap=""> </pre> <blockquote type="cite"> <pre wrap=""> Best Regards Scott M [1]: <a class="moz-txt-link-freetext" href="http://developers.redhat.com/blog/2016/01/13/a-practical-introdu">http://developers.redhat.com/blog/2016/01/13/a-practical-introdu</a> ction-to-docker-container-terminology/ -- Scott McCarty, RHCA Technical Product Marketing: Containers Email: <a class="moz-txt-link-abbreviated" href="mailto:smccarty@redhat.com">smccarty@redhat.com</a> Phone: 312-660-3535 Cell: 330-807-1043 Web: <a class="moz-txt-link-freetext" href="http://crunchtools.com">http://crunchtools.com</a> When should you split your application into multiple containers? http ://red.ht/22xKw9i </pre> </blockquote> </blockquote> <div class="moz-signature">-- Scott McCarty, RHCA Technical Product Marketing: Containers Email: <a class="moz-txt-link-abbreviated" href="mailto:smccarty@redhat.com">smccarty@redhat.com</a> Phone: 312-660-3535 Cell: 330-807-1043 Web: <a href="http://crunchtools.com">http://crunchtools.com</a> When should you split your application into multiple containers? <a href="http://red.ht/22xKw9i">http://red.ht/22xKw9i</a> </div> </body> </html>