Mailing-List: contact user-help@karaf.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@karaf.apache.org
From: Nick Baker <nbaker@pentaho.com>
To: user <user@karaf.apache.org>
Subject: Re: Levels of Containerization - focus on Docker and Karaf
Thread-Topic: Levels of Containerization - focus on Docker and Karaf
Thread-Index: AQHSbEZQy1GUMpqBeEqnKdbVwIoFHKE0rDMAgAAeCkc=
Date: Thu, 12 Jan 2017 12:44:46 +0000
Message-ID: <CY1PR0601MB14385A7320FA6DBE69B43612CD790@CY1PR0601MB1438.namprd06.prod.outlook.com>
References: <1484165220006-4049162.post@n3.nabble.com>,<CAA66TppgYQr+ufmrdg+5jm0yw=8NqCsetAq1zZnVzSxPPKjTZg@mail.gmail.com>
In-Reply-To: <CAA66TppgYQr+ufmrdg+5jm0yw=8NqCsetAq1zZnVzSxPPKjTZg@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
received-spf: None (protection.outlook.com: pentaho.com does not designate
 permitted sender hosts)
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: multipart/alternative;
	boundary="_000_CY1PR0601MB14385A7320FA6DBE69B43612CD790CY1PR0601MB1438_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-originalarrivaltime: 12 Jan 2017 12:44:46.5129
 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 5e847f17-91c4-4532-8b86-a98544e1ca8c
X-MS-Exchange-Transport-CrossTenantHeadersStamped: CY1PR0601MB1437
archived-at: Thu, 12 Jan 2017 12:45:24 -0000

--_000_CY1PR0601MB14385A7320FA6DBE69B43612CD790CY1PR0601MB1438_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Thanks Guillaume!


This is perfect for our microservice/containerized Karaf. I'll give this a =
try and see if we can get our features in startup. We've had issues in the =
past here.


-Nick Baker

________________________________
From: Guillaume Nodet <gnodet@apache.org>
Sent: Thursday, January 12, 2017 5:55:24 AM
To: user
Subject: Re: Levels of Containerization - focus on Docker and Karaf

Fwiw, starting with Karaf 4.x, you can build custom distributions which are=
 mostly static, and that more closely map to micro-services / docker images=
.  The "static" images are called this way because you they kinda remove al=
l the OSGi dynamism, i.e. no feature service, no deploy folder, read-only c=
onfig admin, all bundles being installed at startup time from etc/startup.p=
roperties.
This can be easily done by using the karaf maven plugin and configuring sta=
rtupFeatures and referencing the static kar, as shown in:
  https://github.com/apache/karaf/blob/master/demos/profiles/static/pom.xml


2017-01-11 21:07 GMT+01:00 CodeCola <prasenjit@rogers.com<mailto:prasenjit@=
rogers.com>>:
Not a question but a request for comments. With a focus on Java.

Container technology has traditionally been messy with dependencies and no
easy failsafe way until Docker came along to really pack ALL dependencies
(including the JVM) together in one ready-to-ship image that was faster,
more comfortable, and easier to understand than other container and code
shipping methods out there. The spectrum from (Classical) Java EE Container=
s
(e.g. Tomcat, Jetty) --> Java Application Servers that are containerized
(Karaf, Wildfly, etc), Application Delivery Containers (Docker) and
Virtualization (VMWare, Hyper-V) etc. offers a different level of isolation
with different goals (abstraction, isolation and delivery).

What are the choices, how should they play together, should they be used in
conjunction with each other as they offer different kinds of
Containerization?

<http://karaf.922171.n3.nabble.com/file/n4049162/Levels_of_Containerization=
.png>


--
View this message in context: http://karaf.922171.n3.nabble.com/Levels-of-C=
ontainerization-focus-on-Docker-and-Karaf-tp4049162.html
Sent from the Karaf - User mailing list archive at Nabble.com.


--
------------------------
Guillaume Nodet
------------------------
Red Hat, Open Source Integration

Email: gnodet@redhat.com<mailto:gnodet@redhat.com>
Web: http://fusesource.com<http://fusesource.com/>
Blog: http://gnodet.blogspot.com/


--_000_CY1PR0601MB14385A7320FA6DBE69B43612CD790CY1PR0601MB1438_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
</head>
<body>
<style type=3D"text/css" style=3D"display:none;"><!-- P {margin-top:0;margi=
n-bottom:0;} --></style>
<div id=3D"divtagdefaultwrapper" style=3D"font-size:12pt;color:#000000;font=
-family:Calibri,Arial,Helvetica,sans-serif;" dir=3D"ltr">
<p>Thanks Guillaume!&nbsp;</p>
<p><br>
</p>
<p>This is perfect for our&nbsp;microservice/containerized Karaf. I'll give=
 this a try and see if we can get our features in startup. We've had issues=
 in the past here.</p>
<p><br>
</p>
<p>-Nick Baker</p>
</div>
<hr style=3D"display:inline-block;width:98%" tabindex=3D"-1">
<div id=3D"divRplyFwdMsg" dir=3D"ltr"><font face=3D"Calibri, sans-serif" st=
yle=3D"font-size:11pt" color=3D"#000000"><b>From:</b> Guillaume Nodet &lt;g=
nodet@apache.org&gt;<br>
<b>Sent:</b> Thursday, January 12, 2017 5:55:24 AM<br>
<b>To:</b> user<br>
<b>Subject:</b> Re: Levels of Containerization - focus on Docker and Karaf<=
/font>
<div>&nbsp;</div>
</div>
<div>
<div dir=3D"ltr">Fwiw, starting with Karaf 4.x, you can build custom distri=
butions which are mostly static, and that more closely map to micro-service=
s / docker images.&nbsp; The &quot;static&quot; images are called this way =
because you they kinda remove all the OSGi dynamism,
 i.e. no feature service, no deploy folder, read-only config admin, all bun=
dles being installed at startup time from etc/startup.properties.
<div>This can be easily done by using the karaf maven plugin and configurin=
g startupFeatures and referencing the static kar, as shown in:</div>
<div>&nbsp;&nbsp;<a href=3D"https://github.com/apache/karaf/blob/master/dem=
os/profiles/static/pom.xml">https://github.com/apache/karaf/blob/master/dem=
os/profiles/static/pom.xml</a></div>
<div><br>
</div>
</div>
<div class=3D"gmail_extra"><br>
<div class=3D"gmail_quote">2017-01-11 21:07 GMT&#43;01:00 CodeCola <span di=
r=3D"ltr">&lt;<a href=3D"mailto:prasenjit@rogers.com" target=3D"_blank">pra=
senjit@rogers.com</a>&gt;</span>:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
Not a question but a request for comments. With a focus on Java.<br>
<br>
Container technology has traditionally been messy with dependencies and no<=
br>
easy failsafe way until Docker came along to really pack ALL dependencies<b=
r>
(including the JVM) together in one ready-to-ship image that was faster,<br=
>
more comfortable, and easier to understand than other container and code<br=
>
shipping methods out there. The spectrum from (Classical) Java EE Container=
s<br>
(e.g. Tomcat, Jetty) --&gt; Java Application Servers that are containerized=
<br>
(Karaf, Wildfly, etc), Application Delivery Containers (Docker) and<br>
Virtualization (VMWare, Hyper-V) etc. offers a different level of isolation=
<br>
with different goals (abstraction, isolation and delivery).<br>
<br>
What are the choices, how should they play together, should they be used in=
<br>
conjunction with each other as they offer different kinds of<br>
Containerization?<br>
<br>
&lt;<a href=3D"http://karaf.922171.n3.nabble.com/file/n4049162/Levels_of_Co=
ntainerization.png" rel=3D"noreferrer" target=3D"_blank">http://karaf.92217=
1.n3.<wbr>nabble.com/file/n4049162/<wbr>Levels_of_Containerization.png</a><=
wbr>&gt;<br>
<br>
<br>
<br>
--<br>
View this message in context: <a href=3D"http://karaf.922171.n3.nabble.com/=
Levels-of-Containerization-focus-on-Docker-and-Karaf-tp4049162.html" rel=3D=
"noreferrer" target=3D"_blank">
http://karaf.922171.n3.nabble.<wbr>com/Levels-of-<wbr>Containerization-focu=
s-on-<wbr>Docker-and-Karaf-tp4049162.<wbr>html</a><br>
Sent from the Karaf - User mailing list archive at Nabble.com.<br>
</blockquote>
</div>
<br>
<br clear=3D"all">
<div><br>
</div>
-- <br>
<div class=3D"gmail_signature" data-smartmail=3D"gmail_signature">
<div dir=3D"ltr"><font color=3D"#999999">------------------------<br>
Guillaume Nodet<br>
------------------------</font>
<div><font color=3D"#999999">Red Hat,&nbsp;Open Source Integration</font></=
div>
<div><font color=3D"#999999"><br>
</font></div>
<div><font color=3D"#999999">Email:&nbsp;<a href=3D"mailto:gnodet@redhat.co=
m" target=3D"_blank">gnodet@redhat.com</a><br>
Web:&nbsp;<a href=3D"http://fusesource.com/" target=3D"_blank">http://fuses=
ource.com</a><br>
Blog:&nbsp;<a href=3D"http://gnodet.blogspot.com/" target=3D"_blank">http:/=
/gnodet.blogspot.com/</a><br>
</font></div>
<div><br>
</div>
</div>
</div>
</div>
</div>
</body>
</html>

--_000_CY1PR0601MB14385A7320FA6DBE69B43612CD790CY1PR0601MB1438_--