From dmueller at redhat.com Mon May 2 16:44:51 2016 From: dmueller at redhat.com (Diane Mueller-Klingspor) Date: Mon, 2 May 2016 09:44:51 -0700 Subject: [Openshift Commons Image Builders SIG] Reminder to Save the Date: OpenShift Commons Image Builder SIG Meeting 2016/05/04 at 9:00 am Pacific Message-ID: We will be holding our first OpenShift Commons Image Builder SIG meeting on May 4th at 9:00 am Pacific. The Kick-off Image Builder SIG Topic will be "How to Build Redistributable OpenShift-Ready Images" led by Ryan Jarvinen, OpenShift. Please bring your questions and ideas for future topics of discussion to this session. Here are the meeting details: To join the Meeting: https://bluejeans.com/490951869 To join via Browser: https://bluejeans.com/490951869/browser To join with Lync: https://bluejeans.com/490951869/lync To join via Room System: Video Conferencing System: bjn.vc -or-199.48.152.152 Meeting ID : 490951869 To join via phone : 1) Dial: +1 800 451 8679 +1 212 729 5016 (see all numbers - https://www.intercallonline.com/listNumbersByCode.action?confCode=8933049334 ) 2) Enter Conference ID : 8933049334 Kind Regards, Diane Mueller Director, Community Development Red Hat OpenShift @openshiftcommons We have more in Common than you know, learn more at http://commons.openshift.org -------------- next part -------------- An HTML attachment was scrubbed... URL: From dmueller at redhat.com Thu May 5 22:09:21 2016 From: dmueller at redhat.com (Diane Mueller-Klingspor) Date: Thu, 5 May 2016 15:09:21 -0700 Subject: [Openshift Commons Image Builders SIG] OpenShift Commons Image Builder SIG Meeting #1: notes, slides, video and links Message-ID: All, Thanks for attending the first meeting of the Image Builder SIG; if you were not able to attend here's the link to the recording of the session on Youtube: OpenShift Commons Image Builder SIG #1: How to Build Redistributable OpenShift-Ready Images: https://youtu.be/QmnIwcCOuj8 Slides used in the meeting are here: http://gist-reveal.it/1eb09f06768cdb3d60f1300dc255ca0c#/welcome-image-builders There was a good discussion on how to improve the documentation around image building presented in the discussion near the end of the session including the suggestion to have a pair of 'Getting Started' tutorials. The first would walk thru a 'generic' image build tutorial and the second would walk thru using S2I that explained the new terminology that was specific to openshift and kubernetes. Click2Cloud shared the links to their OpenShift Ready .Net images on Docker Hub https://hub.docker.com/search/?isAutomated=0&isOfficial=0&page=1&pullCount=0&q=click2cloud&starCount=0 Also the templates available here: https://github.com/Click2Cloud/DotNetOnOpenShift3 The next session will be held May 18th at 9:00 am Pacific with a presentation from Produban's Cristian Roldan on their Enterprise CI/CD Image Building workflow. Check meeting dial-in details here for https://commons.openshift.org/briefings.html Kind Regards, Diane Mueller Director, Community Development Red Hat OpenShift @openshiftcommons We have more in Common than you know, learn more at http://commons.openshift.org -------------- next part -------------- An HTML attachment was scrubbed... URL: From dmueller at redhat.com Mon May 16 17:41:46 2016 From: dmueller at redhat.com (Diane Mueller-Klingspor) Date: Mon, 16 May 2016 10:41:46 -0700 Subject: [Openshift Commons Image Builders SIG] Next OpenShift Commons Image Builder SIG May 18 at 9:00 am Pacific. Message-ID: All, This week's OpenShift Commons Image Builder SIG meeting will be held on May 18 at 9:00 am Pacific. This will be the 2nd meeting of the Image Builders SIG; we?ll do introductions and have a discussion led by Produban?s Cristian Roldan with a overview of Produban CI/CD workflows for building redistributable OpenShift-ready images. There will be Q/A and we will solicit topics for upcoming meetings and discuss SIG deliverables. We are planning on bi-monthly meetings depending on the group?s schedules and interests. All are welcome to join this session. To join the meeting on a computer or mobile phone : https://bluejeans.com/931931686/3507?src=calendarLink&g=mrwxkzlmnrsxeqdsmvsgqylufzrw63i= Here are the details for the meeting you scheduled: To join from a Red Hat Deskphone or Softphone, dial: 84336. ----------------------------------- Connecting directly from a room system? 1) Dial: 199.48.152.152 or bjn.vc 2) Enter Meeting ID: 931931686 3) Enter Moderator Passcode: 3507 (DO NOT SHARE) Just want to dial in on your phone? 1) +1 800 451 8679 +1 212 729 5016 ( https://www.intercallonline.com/listNumbersByCode.action?confCode=8933049334 ) 2) Enter Meeting ID: 8933049334 Want to test your video connection? http://bluejeans.com/111 -- Kind Regards, Diane Mueller Director, Community Development Red Hat OpenShift @openshiftcommons We have more in Common than you know, learn more at http://commons.openshift.org -------------- next part -------------- An HTML attachment was scrubbed... URL: From dmueller at redhat.com Mon May 16 19:41:06 2016 From: dmueller at redhat.com (Diane Mueller-Klingspor) Date: Mon, 16 May 2016 12:41:06 -0700 Subject: [Openshift Commons Image Builders SIG] Save the Date Reminder: May 18, 2016 Image Builder SIG Meeting at 9:00 am Pacific Message-ID: All, This week's OpenShift Commons Image Builder SIG meeting will be held on May 18 at 9:00 am Pacific. This will be the 2nd meeting of the Image Builders SIG; we?ll do introductions and have a discussion led by Produban?s Cristian Roldan with a overview of Produban CI/CD workflows for building redistributable OpenShift-ready images. There will be Q/A and we will solicit topics for upcoming meetings and discuss SIG deliverables. We are planning on bi-monthly meetings depending on the group?s schedules and interests. All are welcome to join this session. To join the meeting on a computer or mobile phone : https://bluejeans.com/931931686/3507?src=calendarLink&g=mrwxkzlmnrsxeqdsmvsgqylufzrw63i= Here are the details for the meeting you scheduled: To join from a Red Hat Deskphone or Softphone, dial: 84336. ----------------------------------- Connecting directly from a room system? 1) Dial: 199.48.152.152 or bjn.vc 2) Enter Meeting ID: 931931686 3) Enter Moderator Passcode: 3507 (DO NOT SHARE) Just want to dial in on your phone? 1) +1 800 451 8679 +1 212 729 5016 ( https://www.intercallonline.com/listNumbersByCode.action?confCode=8933049334 ) 2) Enter Meeting ID: 8933049334 Want to test your video connection? http://bluejeans.com/111 Kind Regards, Diane Mueller Director, Community Development Red Hat OpenShift @openshiftcommons We have more in Common than you know, learn more at http://commons.openshift.org -------------- next part -------------- An HTML attachment was scrubbed... URL: From dmueller at redhat.com Wed May 18 15:16:52 2016 From: dmueller at redhat.com (Diane Mueller-Klingspor) Date: Wed, 18 May 2016 08:16:52 -0700 Subject: [Openshift Commons Image Builders SIG] Starting Soon: Next Image Builder SIG Call with Produban's Cristian Roldan Message-ID: All, This week's OpenShift Commons Image Builder SIG meeting will be held TODAY (May 18) at 9:00 am Pacific. This will be the 2nd meeting of the Image Builders SIG; we?ll do introductions and have a discussion led by Produban?s Cristian Roldan with a overview of Produban CI/CD workflows for building redistributable OpenShift-ready images. There will be Q/A and we will solicit topics for upcoming meetings and discuss SIG deliverables. We are planning on bi-monthly meetings depending on the group?s schedules and interests. All are welcome to join this session. To join the meeting on a computer or mobile phone : https://bluejeans.com/931931686/3507?src=""> Here are the details for the meeting you scheduled: To join from a Red Hat Deskphone or Softphone, dial: 84336. ----------------------------------- Connecting directly from a room system? 1) Dial: 199.48.152.152 or bjn.vc 2) Enter Meeting ID: 931931686 Just want to dial in on your phone? 1) +1 800 451 8679 +1 212 729 5016 ( https://www.intercallonline.com/listNumbersByCode.action?confCode=8933049334 ) 2) Enter Meeting ID: 8933049334 Want to test your video connection? http://bluejeans.com/111 Kind Regards, Diane Mueller Director, Community Development Red Hat OpenShift @openshiftcommons We have more in Common than you know, learn more at http://commons.openshift.org -------------- next part -------------- An HTML attachment was scrubbed... URL: From smccarty at redhat.com Wed May 18 21:10:03 2016 From: smccarty at redhat.com (Scott McCarty) Date: Wed, 18 May 2016 17:10:03 -0400 Subject: [Openshift Commons Image Builders SIG] Architecting Containers Part 5: Building a Secure and Manageable Container Software Supply Chain Message-ID: This is an article [1] I just published today. I wanted to get it out there today because it's very similar to what was talked about today in the field interlock. I "hope" we can wrap our brain around the fact that: 1. We are a software company 2. We have pain point and desperately need OSBS 3. All customers are becoming software companies 4. They will also feel pain and need cascading builds, a hierarchical supply chain, and access to OSBS... Also, I would love to see ansible-container [2] support in OSE ;-) [1]: http://rhelblog.redhat.com/2016/05/18/architecting-containers-part-5-building-a-secure-and-manageable-container-software-supply-chain/ [2]: Best Regards Scott M -- Scott McCarty, RHCA Technical Product Marketing: Containers Email: smccarty at redhat.com Phone: 312-660-3535 Cell: 330-807-1043 Web: http://crunchtools.com When should you split your application into multiple containers? http://red.ht/22xKw9i -------------- next part -------------- An HTML attachment was scrubbed... URL: From smccarty at redhat.com Tue May 24 13:49:25 2016 From: smccarty at redhat.com (Scott McCarty) Date: Tue, 24 May 2016 09:49:25 -0400 Subject: [Openshift Commons Image Builders SIG] Image Building and Terminology Message-ID: 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. 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. 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). Best Regards Scott M [1]: http://developers.redhat.com/blog/2016/01/13/a-practical-introduction-to-docker-container-terminology/ -- Scott McCarty, RHCA Technical Product Marketing: Containers Email: smccarty at redhat.com Phone: 312-660-3535 Cell: 330-807-1043 Web: http://crunchtools.com When should you split your application into multiple containers? http://red.ht/22xKw9i -------------- next part -------------- An HTML attachment was scrubbed... URL: From bbaude at redhat.com Tue May 24 14:38:18 2016 From: bbaude at redhat.com (Brent Baude) Date: Tue, 24 May 2016 09:38:18 -0500 Subject: [Openshift Commons Image Builders SIG] Image Building and Terminology In-Reply-To: References: Message-ID: <1464100698.3877.14.camel@redhat.com> Comments inline... On Tue, 2016-05-24 at 09:49 -0400, Scott McCarty wrote: > 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. > That is the definition I also tend to favor. ?I also tend to only associate base images with distributions/OS's. > 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. > 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. > 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). > In the dev world, we have called these "layered images." ?But agree, some sort of name could make messaging clearer. > > Best Regards > Scott M > > [1]: http://developers.redhat.com/blog/2016/01/13/a-practical-introdu > ction-to-docker-container-terminology/ > > --? > Scott McCarty, RHCA > Technical Product Marketing: Containers > Email: smccarty at redhat.com > Phone: 312-660-3535 > Cell: 330-807-1043 > Web: http://crunchtools.com > When should you split your application into multiple containers? http > ://red.ht/22xKw9i From smccarty at redhat.com Tue May 24 14:48:51 2016 From: smccarty at redhat.com (Scott McCarty) Date: Tue, 24 May 2016 10:48:51 -0400 Subject: [Openshift Commons Image Builders SIG] Image Building and Terminology In-Reply-To: <1464100698.3877.14.camel@redhat.com> References: <1464100698.3877.14.camel@redhat.com> Message-ID: <0c1c511e-a6ae-0a92-9217-049b9a06cd9a@redhat.com> On 05/24/2016 10:38 AM, Brent Baude wrote: > Comments inline... > > On Tue, 2016-05-24 at 09:49 -0400, Scott McCarty wrote: >> 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. >> > That is the definition I also tend to favor. I also tend to only > associate base images with distributions/OS's. > >> 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. >> > 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. +1 on "layered image" nomenclature +1 on building a tree structure (e.g. MW core build). > >> 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). >> > In the dev world, we have called these "layered images." But agree, > some sort of name could make messaging clearer. +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"... > >> Best Regards >> Scott M >> >> [1]: http://developers.redhat.com/blog/2016/01/13/a-practical-introdu >> ction-to-docker-container-terminology/ >> >> -- >> Scott McCarty, RHCA >> Technical Product Marketing: Containers >> Email: smccarty at redhat.com >> Phone: 312-660-3535 >> Cell: 330-807-1043 >> Web: http://crunchtools.com >> When should you split your application into multiple containers? http >> ://red.ht/22xKw9i -- Scott McCarty, RHCA Technical Product Marketing: Containers Email: smccarty at redhat.com Phone: 312-660-3535 Cell: 330-807-1043 Web: http://crunchtools.com When should you split your application into multiple containers? http://red.ht/22xKw9i -------------- next part -------------- An HTML attachment was scrubbed... URL: From drettori at redhat.com Tue May 24 16:10:38 2016 From: drettori at redhat.com (Diogenes Rettori) Date: Tue, 24 May 2016 12:10:38 -0400 Subject: [Openshift Commons Image Builders SIG] Image Building and Terminology In-Reply-To: References: <1464100698.3877.14.camel@redhat.com> <0c1c511e-a6ae-0a92-9217-049b9a06cd9a@redhat.com> Message-ID: Catching up on this. Yes, the intention is as stated by John Doyle. With regards to using the 'base' name my intention was to make flag it as an image which you should always be building on top, or as a base for your application. or as on Scott's blog *The sole purpose of a base image is to provide a starting place for creating your derivative images. When using a Dockerfile , the choice of which base image you are using is explicit:(...)* Our OpenShift images today have multiple parent images, IIRC, they are: base os, jdk, eap, openshift Maybe drop any definition and just call it 'whatever product' image. As to who should be creating the images, so far the MW images have been created by the Cloud Enablement (Kevin's team), and as I understand the intention is to slowly handover this task to the individual products. I don't se Today we only have images supported under the context of OpenShift, which means they include OpenShift specific bits. I've been getting constant requests, even from OpenShift customers, to provide clean/naked/standalone images of the MW products that contain no runtime specific content, meaning no OpenShift specialization, or thinking from the top-down, EAP should drive what's required in the image, meaning that it would be a JDK, and it's dependencies, and a base os. To your point on what base image (top parent 'base image' meaning), it has been RHEL all along, so I would not worry about that. D. On Tue, May 24, 2016 at 11:03 AM, John Doyle wrote: > On Tue, May 24, 2016 at 10:48 AM, Scott McCarty > wrote: > > > > > > On 05/24/2016 10:38 AM, Brent Baude wrote: > > > > Comments inline... > > > > On Tue, 2016-05-24 at 09:49 -0400, Scott McCarty wrote: > > > > 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. > > > > That is the definition I also tend to favor. I also tend to only > > associate base images with distributions/OS's. > > > > 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. > > > > 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. > > > > > > +1 on "layered image" nomenclature > > I think the idea was to put a name on a particular layer, and then > attach support and maintenance to that named layer. > > > +1 on building a tree structure (e.g. MW core build). > > > > > > 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). > > > > In the dev world, we have called these "layered images." But agree, > > some sort of name could make messaging clearer. > > > > +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"... > > > > Best Regards > > Scott M > > > > [1]: http://developers.redhat.com/blog/2016/01/13/a-practical-introdu > > ction-to-docker-container-terminology/ > > > > -- > > Scott McCarty, RHCA > > Technical Product Marketing: Containers > > Email: smccarty at redhat.com > > Phone: 312-660-3535 > > Cell: 330-807-1043 > > Web: http://crunchtools.com > > When should you split your application into multiple containers? http > > ://red.ht/22xKw9i > > > > > > -- > > > > Scott McCarty, RHCA > > > > Technical Product Marketing: Containers > > > > Email: smccarty at redhat.com > > > > Phone: 312-660-3535 > > > > Cell: 330-807-1043 > > > > Web: http://crunchtools.com > > > > When should you split your application into multiple containers? > > http://red.ht/22xKw9i > -- Di?genes G. Rettori Openshift Product Manager @rettori -------------- next part -------------- An HTML attachment was scrubbed... URL: From jdoyle at redhat.com Tue May 24 14:17:32 2016 From: jdoyle at redhat.com (John Doyle) Date: Tue, 24 May 2016 10:17:32 -0400 Subject: [Openshift Commons Image Builders SIG] Image Building and Terminology In-Reply-To: References: Message-ID: +1 I prefer something like 'primary image', 'basal image', or 'foundation image'. I think we can express Diogenes's concept without overloading the team. ~jd On Tue, May 24, 2016 at 9:49 AM, Scott McCarty wrote: > 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. > > > 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. > > 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). > > > Best Regards > Scott M > > [1]: > http://developers.redhat.com/blog/2016/01/13/a-practical-introduction-to-docker-container-terminology/ > > -- > > Scott McCarty, RHCA > > Technical Product Marketing: Containers > > Email: smccarty at redhat.com > > Phone: 312-660-3535 > > Cell: 330-807-1043 > > Web: http://crunchtools.com > > When should you split your application into multiple containers? > http://red.ht/22xKw9i From jdoyle at redhat.com Tue May 24 15:03:03 2016 From: jdoyle at redhat.com (John Doyle) Date: Tue, 24 May 2016 11:03:03 -0400 Subject: [Openshift Commons Image Builders SIG] Image Building and Terminology In-Reply-To: <0c1c511e-a6ae-0a92-9217-049b9a06cd9a@redhat.com> References: <1464100698.3877.14.camel@redhat.com> <0c1c511e-a6ae-0a92-9217-049b9a06cd9a@redhat.com> Message-ID: On Tue, May 24, 2016 at 10:48 AM, Scott McCarty wrote: > > > On 05/24/2016 10:38 AM, Brent Baude wrote: > > Comments inline... > > On Tue, 2016-05-24 at 09:49 -0400, Scott McCarty wrote: > > 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. > > That is the definition I also tend to favor. I also tend to only > associate base images with distributions/OS's. > > 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. > > 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. > > > +1 on "layered image" nomenclature I think the idea was to put a name on a particular layer, and then attach support and maintenance to that named layer. > +1 on building a tree structure (e.g. MW core build). > > > 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). > > In the dev world, we have called these "layered images." But agree, > some sort of name could make messaging clearer. > > +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"... > > Best Regards > Scott M > > [1]: http://developers.redhat.com/blog/2016/01/13/a-practical-introdu > ction-to-docker-container-terminology/ > > -- > Scott McCarty, RHCA > Technical Product Marketing: Containers > Email: smccarty at redhat.com > Phone: 312-660-3535 > Cell: 330-807-1043 > Web: http://crunchtools.com > When should you split your application into multiple containers? http > ://red.ht/22xKw9i > > > -- > > Scott McCarty, RHCA > > Technical Product Marketing: Containers > > Email: smccarty at redhat.com > > Phone: 312-660-3535 > > Cell: 330-807-1043 > > Web: http://crunchtools.com > > When should you split your application into multiple containers? > http://red.ht/22xKw9i From invite at bluejeans.com Fri May 27 20:41:49 2016 From: invite at bluejeans.com (Diane Mueller via Blue Jeans Network) Date: Fri, 27 May 2016 20:41:49 +0000 (UTC) Subject: [Openshift Commons Image Builders SIG] OpenShift Commons Image Builder SIG Meeting: Centos Container Pipeline Overview and Demo Message-ID: <1800926280.185211464381709476.JavaMail.denimuser@sj1-app-102-13.bluejeansnet.com> To join the meeting on a computer or mobile phone: https://bluejeans.com/350429644?src=textEmail&g=j5ygk3ttnbuwm5bnmnxw23lpnzzs243jm4wws3lbm5ss2ytvnfwgizlsonahezlenbqxiltdn5wq==== Diane Mueller has invited you to a video meeting. To join from a Red Hat Deskphone or Softphone, dial: 84336. Meeting Title: OpenShift Commons Image Builder SIG Meeting: Centos Container Pipeline Overview and Demo Meeting Time: Wednesday June 1, 2016 8 a.m. PDT / 1 hr ------------------------------------------------ Connecting directly from a room system? 1) Dial: 199.48.152.152 or bjn.vc 2) Enter Meeting ID: 350429644 Just want to dial in on your phone? 1) +1 800 451 8679 +1 212 729 5016 (https://www.intercallonline.com/listNumbersByCode.action?confCode=8933049334) 2) Enter Meeting ID: 8933049334 3) Press # ------------------------------------------------ Description: The CentOS Community has developed a workflow for building images. Dharmit Shah and Mohammed Zeeshan will be giving an overview/demo on how the CentOS Community Container Pipeline works and lead a discussion & Q/A session for those interested in learning more. https://github.com/kbsingh/cccp-index Please note that this session will be at 8:00 am Pacific to accommodate their schedules. ------------------------------------------------ Want to test your video connection? http://bluejeans.com/111 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: text/calendar Size: 2675 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: invite.ics Type: application/ics Size: 2675 bytes Desc: not available URL: From dmueller at redhat.com Fri May 27 20:50:19 2016 From: dmueller at redhat.com (Diane Mueller-Klingspor) Date: Fri, 27 May 2016 13:50:19 -0700 Subject: [Openshift Commons Image Builders SIG] Save the Date! Next Image Builder SIG Meeting: Centos Container Pipeline Overview Message-ID: All, Our next Image Builder SIG will be on June 1st at 8:00 am Pacific. The discussion topic will be the CentOS Container Pipeline Overview: The CentOS Community has developed a workflow for building images. Dharmit Shah and Mohammed Zeeshan will be giving an overview/demo on how the CentOS Community Container Pipeline works and lead the discussion & Q/A for this session. For those interested in learning more in advance of the SIG meeting, please check out: https://github.com/kbsingh/cccp-index To join the Meeting: https://bluejeans.com/350429644 To join via Browser: https://bluejeans.com/350429644/browser To join with Lync: https://bluejeans.com/350429644/lync To join via Room System: Video Conferencing System: bjn.vc -or-199.48.152.152 Meeting ID : 350429644 To join via phone : 1) Dial: +1 800 451 8679 +1 212 729 5016 (see all numbers - https://www.intercallonline.com/listNumbersByCode.action?confCode=8933049334 ) 2) Enter Conference ID : 8933049334 -- Kind Regards, Diane Mueller Director, Community Development Red Hat OpenShift @openshiftcommons We have more in Common than you know, learn more at http://commons.openshift.org -------------- next part -------------- An HTML attachment was scrubbed... URL: From jorgemoralespou at gmail.com Sat May 28 05:43:05 2016 From: jorgemoralespou at gmail.com (Jorge Morales Pou) Date: Sat, 28 May 2016 05:43:05 +0000 Subject: [Openshift Commons Image Builders SIG] =?utf-8?b?SW52aXRhY2nDs246?= =?utf-8?q?_OpenShift_Commons_Image_Builder_SIG_Meeting=3A_Centos_C?= =?utf-8?q?onta=2E=2E=2E_mi=C3=A9_1_de_jun_de_2016_17=3A00_-_18=3A0?= =?utf-8?q?0_=28Jorge_gmail=29?= Message-ID: <001a114b6d504d20bb0533e07ff4@google.com> Tienes una invitaci?n para el siguiente evento. T?tulo: OpenShift Commons Image Builder SIG Meeting: Centos Container Pipeline Overview and Demo Cu?ndo: mi? 1 de jun de 2016 17:00 ? 18:00 Madrid Calendario: Jorge gmail Qui?n: * Jorge Morales Pou- organizador * openshift-commons-sig-image-builders at redhat.com * Mohammed Zeeshan * dshah at redhat.com Detalles del evento: https://www.google.com/calendar/event?action=VIEW&eid=Y2xoajZkajY2Y3FqNmI5ZzY4czNnYjlrNmtzNmNiOXBjZ3FtNGI5bWNvcDMwb3BsNmNyMzRjOW9jayBvcGVuc2hpZnQtY29tbW9ucy1zaWctaW1hZ2UtYnVpbGRlcnNAcmVkaGF0LmNvbQ&tok=MjUjam9yZ2Vtb3JhbGVzcG91QGdtYWlsLmNvbWIyYzc3YjkxMjVkM2U5OGFlNDEzOTJkY2Q4YjAxZTQ1ZTY0ZjIyODk&ctz=Europe/Madrid&hl=es Invitaci?n de Google Calendar: https://www.google.com/calendar/ Recibes este mensaje de cortes?a en la direcci?n openshift-commons-sig-image-builders at redhat.com de la cuenta porque eres uno de los participantes de este evento. Si ya no quieres recibir m?s avisos sobre este evento, rech?zalo. Si lo prefieres, solicita una cuenta de Google en https://www.google.com/calendar/ y controla la configuraci?n de las notificaciones de todo tu calendario. Si reenv?as esta invitaci?n, los destinatarios podr?an cambiar tu respuesta de confirmaci?n de asistencia. M?s informaci?n en https://support.google.com/calendar/answer/37135#forwarding -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: text/calendar Size: 1872 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: invite.ics Type: application/ics Size: 1922 bytes Desc: not available URL: From jmorales at redhat.com Tue May 31 21:31:58 2016 From: jmorales at redhat.com (jmorales at redhat.com) Date: Tue, 31 May 2016 21:31:58 +0000 Subject: [Openshift Commons Image Builders SIG] Canceled Event: OpenShift Commons Image Builder SIG Meeting: Centos Conta... @ Wed Jun 1, 2016 5pm - 6pm (Jorge gmail) Message-ID: <001a1141033853818605342a1af0@google.com> This event has been canceled and removed from your calendar. Title: OpenShift Commons Image Builder SIG Meeting: Centos Container Pipeline Overview and Demo When: Wed Jun 1, 2016 5pm ? 6pm Madrid Calendar: Jorge gmail Who: * Jorge Morales Pou - organizer * openshift-commons-sig-image-builders at redhat.com * Mohammed Zeeshan * dshah at redhat.com Invitation from Google Calendar: https://www.google.com/calendar/ You are receiving this courtesy email at the account openshift-commons-sig-image-builders at redhat.com because you are an attendee of this event. To stop receiving future updates for this event, decline this event. Alternatively you can sign up for a Google account at https://www.google.com/calendar/ and control your notification settings for your entire calendar. Forwarding this invitation could allow any recipient to modify your RSVP response. Learn more at https://support.google.com/calendar/answer/37135#forwarding -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: text/calendar Size: 1184 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: invite.ics Type: application/ics Size: 1215 bytes Desc: not available URL: From dmueller at redhat.com Tue May 31 22:51:51 2016 From: dmueller at redhat.com (Diane Mueller-Klingspor) Date: Tue, 31 May 2016 15:51:51 -0700 Subject: [Openshift Commons Image Builders SIG] SIG Meeting Reminder: OpenShift Commons Image Builder SIG Wednesday June 1st 8:00 am Pacific Message-ID: The CentOS Community has developed a workflow for building images. Dharmit Shah and Mohammed Zeeshan will be giving an overview/demo on how the CentOS Community Container Pipeline works and lead a discussion & Q/A session for those interested in learning more. https://github.com/kbsingh/cccp-index The meeting tomorrow will start at 8:00 am Pacific with a presentation from two of the Centos team on their Container Pipeline. Here are the meeting details: To join the Meeting: https://bluejeans.com/350429644 To join via Browser: https://bluejeans.com/350429644/browser To join with Lync: https://bluejeans.com/350429644/lync To join via Room System: Video Conferencing System: bjn.vc -or-199.48.152.152 Meeting ID : 350429644 To join via phone : 1) Dial: +1 800 451 8679 +1 212 729 5016 (see all numbers - https://www.intercallonline.com/listNumbersByCode.action?confCode=8933049334 ) 2) Enter Conference ID : 8933049334 Kind Regards, Diane Mueller Director, Community Development Red Hat OpenShift @openshiftcommons We have more in Common than you know, learn more at http://commons.openshift.org -------------- next part -------------- An HTML attachment was scrubbed... URL: