<html xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:PMingLiU;
panose-1:2 2 5 0 0 0 0 0 0 0;}
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Aptos;
panose-1:2 11 0 4 2 2 2 2 2 4;}
@font-face
{font-family:"\@PMingLiU";
panose-1:2 1 6 1 0 1 1 1 1 1;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
font-size:10.0pt;
font-family:"Aptos",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
span.EmailStyle19
{mso-style-type:personal-reply;
font-family:"Aptos",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;
mso-ligatures:none;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style>
</head>
<body lang="EN-US" link="blue" vlink="purple" style="word-wrap:break-word">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt">Hi Slawek,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">Thank you very much for the information!
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Best Regards,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Yu<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<div id="mail-editor-reference-message-container">
<div>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal" style="margin-bottom:12.0pt"><b><span style="font-size:12.0pt;color:black">From:
</span></b><span style="font-size:12.0pt;color:black">Slawek Figiel <slawek@isc.org><br>
<b>Date: </b>Thursday, July 11, 2024 at 3:21</span><span style="font-size:12.0pt;font-family:"Arial",sans-serif;color:black"> </span><span style="font-size:12.0pt;color:black">PM<br>
<b>To: </b>Xiao, Yu (CCI-Atlanta) <yu.xiao@cox.com>, stork-users@lists.isc.org <stork-users@lists.isc.org><br>
<b>Subject: </b>Re: [EXTERNAL] Re: [stork-users] Stork for kea container monitoring<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt">Yu,<br>
<br>
> Yu: Can you please explain the general steps on this?<br>
<br>
Start with an empty Dockerfile. On top of the file, add the FROM <br>
directive with the label of the official Kea Dockerfile.<br>
<br>
Then, copy the APK package to the container using the COPY directive.<br>
<br>
Next, install the packages using the "apk add --allow-untrusted <br>
isc-stork-*.apk" command.<br>
<br>
Now, download the <br>
<a href="https://gitlab.isc.org/isc-projects/stork/-/blob/master/docker/config/supervisor/stork-agent.conf?ref_type=heads">https://nam02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgitlab.isc.org%2Fisc-projects%2Fstork%2F-%2Fblob%2Fmaster%2Fdocker%2Fconfig%2Fsupervisor%2Fstork-agent.conf%3Fref_type%3Dheads&data=05%7C02%7Cyu.xiao%40cox.com%7C5a78e5065ba54c1390a908dca1dea775%7C9feebc97ff0442c9a152767073872118%7C1%7C0%7C638563224873423584%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C0%7C%7C%7C&sdata=h78%2FsAu9kI%2BDBKQRrG6suwu3DFe5TEiCPFM41iMuGq0%3D&reserved=0</a>.
<br>
Use the COPY directive to copy it to the container to the <br>
"/etc/supervisor/conf.d/ " directory.<br>
<br>
Build the image and run the container.<br>
<br>
I didn't test it, but I hope it works. ;)<br>
<br>
Regards,<br>
Slawek<br>
<br>
On 10/07/2024 16:02, Xiao, Yu (CCI-Atlanta) wrote:<br>
> Hi Slawek,<br>
> <br>
> Thank you very much for your detailed explanation! Regarding to your <br>
> response, I have some further questions:<br>
> <br>
> “ You can build the Stork agent for Alpine on<br>
> your own. It is not hard, but you need to do it on a machine with an<br>
> Alpine system because Stork must be linked with libc-musl on Alpine, so<br>
> you cannot use a binary linked with standard libc. You don't need to<br>
> build the package; the executable only should be enough for your needs.”<br>
> <br>
> Yu: Can you please explain the general steps on this?<br>
> <br>
> <br>
> “Alternatively, I can share with you the Alpine package built by our CI<br>
> environment if you like.”<br>
> <br>
> <br>
> Yu: Yes, please! I can use it for my lab for now and wait to figure out <br>
> how to do the above procedures or the formal release.<br>
> <br>
> Best Regards,<br>
> <br>
> Yu<br>
> <br>
> *From: *Slawek Figiel <slawek@isc.org><br>
> *Date: *Wednesday, July 10, 2024 at 6:16</span><span style="font-size:11.0pt;font-family:"Arial",sans-serif"> </span><span style="font-size:11.0pt">AM<br>
> *To: *Xiao, Yu (CCI-Atlanta) <yu.xiao@cox.com>, <br>
> stork-users@lists.isc.org <stork-users@lists.isc.org><br>
> *Subject: *Re: [EXTERNAL] Re: [stork-users] Stork for kea container <br>
> monitoring<br>
> <br>
> Yu,<br>
> <br>
> > My understanding is current kea docker is based upon Alpine Linux,<br>
> but I don’t see any stork software for that version, only for Debian and<br>
> RHEL.<br>
> <br>
> You are right. I forgot that we haven't published the Alpine packages<br>
> yet. We are blocked by the technical issues with fpm - tool that we use<br>
> to build packages. It has poor support for APK, and the output packages<br>
> are not accepted by CloudSmith.<br>
> <br>
> We plan to handle this situation and migrate to another solution for<br>
> building packages. You can track the progress at<br>
> <a href="https://gitlab.isc.org/isc-projects/stork/-/issues/1114">https://nam02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgitlab.isc.org%2Fisc-projects%2Fstork%2F-%2Fissues%2F1114&data=05%7C02%7Cyu.xiao%40cox.com%7C5a78e5065ba54c1390a908dca1dea775%7C9feebc97ff0442c9a152767073872118%7C1%7C0%7C638563224873435301%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C0%7C%7C%7C&sdata=NavRoE4DuSRRG4x6oHj%2BIclKiz10vdhoOztnLfm0mZ4%3D&reserved=0</a>
<<a href="https://gitlab.isc.org/isc-projects/stork/-/issues/1114">https://nam02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgitlab.isc.org%2Fisc-projects%2Fstork%2F-%2Fissues%2F1114&data=05%7C02%7Cyu.xiao%40cox.com%7C5a78e5065ba54c1390a908dca1dea775%7C9feebc97ff0442c9a152767073872118%7C1%7C0%7C638563224873441966%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C0%7C%7C%7C&sdata=R2jrkeQWZfUMN7hNwud%2FbuPvFebiIzj6LmTIFQD6R0I%3D&reserved=0</a>>
and<br>
> <a href="https://gitlab.isc.org/isc-projects/stork/-/issues/863">https://nam02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgitlab.isc.org%2Fisc-projects%2Fstork%2F-%2Fissues%2F863&data=05%7C02%7Cyu.xiao%40cox.com%7C5a78e5065ba54c1390a908dca1dea775%7C9feebc97ff0442c9a152767073872118%7C1%7C0%7C638563224873449630%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C0%7C%7C%7C&sdata=c4lmEvYfYiGR24wd6Bi7AV%2FkDZ0xsXlBwj6UNqI%2FflU%3D&reserved=0</a>
<<a href="https://gitlab.isc.org/isc-projects/stork/-/issues/863">https://nam02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgitlab.isc.org%2Fisc-projects%2Fstork%2F-%2Fissues%2F863&data=05%7C02%7Cyu.xiao%40cox.com%7C5a78e5065ba54c1390a908dca1dea775%7C9feebc97ff0442c9a152767073872118%7C1%7C0%7C638563224873455145%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C0%7C%7C%7C&sdata=N%2F5q7hgsngKhTZCmNQZIdGY7zKJ5A03v7xyKpn7RoZw%3D&reserved=0</a>>
.<br>
> We discussed your problem at a recent team meeting. I hope it will be<br>
> ready soon, but there are no guarantees.<br>
> <br>
> Today, you have two options: You can build the Stork agent for Alpine on<br>
> your own. It is not hard, but you need to do it on a machine with an<br>
> Alpine system because Stork must be linked with libc-musl on Alpine, so<br>
> you cannot use a binary linked with standard libc. You don't need to<br>
> build the package; the executable only should be enough for your needs.<br>
> Alternatively, I can share with you the Alpine package built by our CI<br>
> environment if you like.<br>
> <br>
> > Another question I have is that I found I had to pull the repo from<br>
> gitlab to target machine and then run a script. After that I can see<br>
> those images locally. But why Stork doesn’t just have all those images<br>
> in some registry and we can just use docker pull to get them. Isn’t it<br>
> more convenient? Or you want to give us the freedom to create a local<br>
> registry?<br>
> <br>
> Kea images are published in the CloudSmith Docker registry. You don't<br>
> need to build them on your own. See<br>
> <a href="https://gitlab.isc.org/isc-projects/kea-docker#using-official-kea-images-on-cloudsmith">
https://nam02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgitlab.isc.org%2Fisc-projects%2Fkea-docker%23using-official-kea-images-on-cloudsmith&data=05%7C02%7Cyu.xiao%40cox.com%7C5a78e5065ba54c1390a908dca1dea775%7C9feebc97ff0442c9a152767073872118%7C1%7C0%7C638563224873459839%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C0%7C%7C%7C&sdata=69xcElYSKMTmdKnHLEh8HoFkST6kVZGFbEgXgq1rDm8%3D&reserved=0</a>
<<a href="https://gitlab.isc.org/isc-projects/kea-docker#using-official-kea-images-on-cloudsmith">https://nam02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgitlab.isc.org%2Fisc-projects%2Fkea-docker%23using-official-kea-images-on-cloudsmith&data=05%7C02%7Cyu.xiao%40cox.com%7C5a78e5065ba54c1390a908dca1dea775%7C9feebc97ff0442c9a152767073872118%7C1%7C0%7C638563224873464222%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C0%7C%7C%7C&sdata=WoJIHsyV726yz%2Bk9HGQI6Kl2XHb3pnUMXJIUGSoVQGc%3D&reserved=0</a>><br>
> .<br>
> <br>
> Regards,<br>
> Slawek<br>
> <br>
> On 08/07/2024 15:48, Xiao, Yu (CCI-Atlanta) wrote:<br>
>> Hi Slawek,<br>
>> <br>
>> Thank you for your prompt response and information! I am new to docker, <br>
>> can you tell me more about how to extend the official Kea Docker image <br>
>> and install the Stork agent inside it? My understanding is current kea <br>
>> docker is based upon Alpine Linux, but I don’t see any stork software <br>
>> for that version, only for Debian and RHEL.<br>
>> <br>
>> Best Regards,<br>
>> <br>
>> Yu<br>
>> <br>
>> *From: *Stork-users <stork-users-bounces@lists.isc.org> on behalf of <br>
>> Slawek Figiel <slawek@isc.org><br>
>> *Date: *Monday, July 8, 2024 at 4:39</span><span style="font-size:11.0pt;font-family:"Arial",sans-serif"> </span><span style="font-size:11.0pt">AM<br>
>> *To: *stork-users@lists.isc.org <stork-users@lists.isc.org><br>
>> *Subject: *[EXTERNAL] Re: [stork-users] Stork for kea container monitoring<br>
>> <br>
>> Hello Yu!<br>
>> <br>
>> If you would like to set up Kea with Stork in Docker, you need to extend<br>
>> the official Kea Docker image and install the Stork agent inside it. You<br>
>> should also prepare a second container with the Stork server.<br>
>> <br>
>> Unfortunately, there is no official guide yet on how to do it. We plan<br>
>> to write one and provide Docker images with Kea and Stork together in<br>
>> the near but undetermined future. I can try to help you if you have any<br>
>> questions.<br>
>> <br>
>> You need to do two things to add Kea hooks to the Kea Docker image:<br>
>> <br>
>> 1. Mount the hook files as volumes or extend the Docker image and copy<br>
>> them. The location can be any.<br>
>> 2. Modify the Kea configuration and provide the path to the hook under<br>
>> the `hooks-libraries` node. See<br>
>> <a href="https://kea.readthedocs.io/en/latest/arm/hooks.html#configuring-hook-libraries">
https://nam02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fkea.readthedocs.io%2Fen%2Flatest%2Farm%2Fhooks.html%23configuring-hook-libraries&data=05%7C02%7Cyu.xiao%40cox.com%7C5a78e5065ba54c1390a908dca1dea775%7C9feebc97ff0442c9a152767073872118%7C1%7C0%7C638563224873468456%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C0%7C%7C%7C&sdata=RIXtlu9YMI4BkOMzBgUAg5NaGiLsAblWMkmhX56VRl8%3D&reserved=0</a>
<<a href="https://kea.readthedocs.io/en/latest/arm/hooks.html#configuring-hook-libraries">https://nam02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fkea.readthedocs.io%2Fen%2Flatest%2Farm%2Fhooks.html%23configuring-hook-libraries&data=05%7C02%7Cyu.xiao%40cox.com%7C5a78e5065ba54c1390a908dca1dea775%7C9feebc97ff0442c9a152767073872118%7C1%7C0%7C638563224873472933%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C0%7C%7C%7C&sdata=pe8n2J61Oal5uFZ2GmnO5UmfhzmNib3yzi%2BPaXTWXtU%3D&reserved=0</a>>
<https://nam02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fkea.readthedocs.io%2Fen%2Flatest%2Farm%2Fhooks.html%23configuring-hook-libraries&data=05%7C02%7Cyu.xiao%40cox.com%7C5a78e5065ba54c1390a908dca1dea775%7C9feebc97ff0442c9a152767073872118%7C1%7C0%7C638563224873477182%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C0%7C%7C%7C&sdata=M%2BxB5abdW4MHpaXybmqszDrg%2FcF%2BbqsBlGE3W0OJfAI%3D&reserved=0
<<a href="https://kea.readthedocs.io/en/latest/arm/hooks.html#configuring-hook-libraries">https://nam02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fkea.readthedocs.io%2Fen%2Flatest%2Farm%2Fhooks.html%23configuring-hook-libraries&data=05%7C02%7Cyu.xiao%40cox.com%7C5a78e5065ba54c1390a908dca1dea775%7C9feebc97ff0442c9a152767073872118%7C1%7C0%7C638563224873481383%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C0%7C%7C%7C&sdata=5erYxjNe%2FjDF4Ves18%2F1%2FXVwZpp6gj3ewoLRYOmkOIs%3D&reserved=0</a>>><br>
>> .<br>
>> <br>
>> Regards,<br>
>> Slawek<br>
>> <br>
>> On 05/07/2024 16:12, Xiao, Yu (CCI-Atlanta) wrote:<br>
>>> Hi experts,<br>
>>> <br>
>>> I want to use Stork to monitor my kea service which is running in some <br>
>>> docker containers. My understanding is that we need to install Stork <br>
>>> clients inside of those kea docker containers. But I don’t see how this <br>
>>> part in the docker-kea document or Stork document, some indeed mentioned <br>
>>> how to import Hooks. Can you provide some suggestions? Kea experts <br>
>>> suggested me ask in this mailer as well maybe more Stork experts have <br>
>>> considered this use and can answer my question.<br>
>>> <br>
>>> Best Regards,<br>
>>> <br>
>>> Yu<br>
>>> <br>
>>> <br>
>> -- <br>
>> Stork-users mailing list<br>
>> Stork-users@lists.isc.org<br>
>> <a href="https://lists.isc.org/mailman/listinfo/stork-users">https://nam02.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.isc.org%2Fmailman%2Flistinfo%2Fstork-users&data=05%7C02%7Cyu.xiao%40cox.com%7C5a78e5065ba54c1390a908dca1dea775%7C9feebc97ff0442c9a152767073872118%7C1%7C0%7C638563224873485455%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C0%7C%7C%7C&sdata=mG4NC9aOXpnOk%2BSFDNU6ZNJyaD54P1XopBMcfBOVcAk%3D&reserved=0</a>
<<a href="https://lists.isc.org/mailman/listinfo/stork-users">https://nam02.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.isc.org%2Fmailman%2Flistinfo%2Fstork-users&data=05%7C02%7Cyu.xiao%40cox.com%7C5a78e5065ba54c1390a908dca1dea775%7C9feebc97ff0442c9a152767073872118%7C1%7C0%7C638563224873489495%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C0%7C%7C%7C&sdata=3j8L5tdO%2Bs2LBIswuDGFRTADw0yuCLHqrhbJvZKutT0%3D&reserved=0</a>>
<https://nam02.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.isc.org%2Fmailman%2Flistinfo%2Fstork-users&data=05%7C02%7Cyu.xiao%40cox.com%7C5a78e5065ba54c1390a908dca1dea775%7C9feebc97ff0442c9a152767073872118%7C1%7C0%7C638563224873493523%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C0%7C%7C%7C&sdata=yjGaGhJwzDPovZQrbM8WjWeNJMoNRbdOGpt6O4uz6rg%3D&reserved=0
<<a href="https://lists.isc.org/mailman/listinfo/stork-users">https://nam02.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.isc.org%2Fmailman%2Flistinfo%2Fstork-users&data=05%7C02%7Cyu.xiao%40cox.com%7C5a78e5065ba54c1390a908dca1dea775%7C9feebc97ff0442c9a152767073872118%7C1%7C0%7C638563224873497583%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C0%7C%7C%7C&sdata=zIYdhqBAE7N8vwhxzkgK5K%2FS%2BnO1Z9prpqHXYROLoS4%3D&reserved=0</a>>><br>
>> <br>
> <o:p></o:p></span></p>
</div>
</div>
</div>
</div>
</body>
</html>