[stork-users] [EXTERNAL] Re: Stork for kea container monitoring

Fri Jul 12 19:39:51 UTC 2024

Hi Slawek,

Thank you very much for the information!

Best Regards,
Yu

From: Slawek Figiel <slawek at isc.org>
Date: Thursday, July 11, 2024 at 3:21 PM
To: Xiao, Yu (CCI-Atlanta) <yu.xiao at cox.com>, stork-users at lists.isc.org <stork-users at lists.isc.org>
Subject: Re: [EXTERNAL] Re: [stork-users] Stork for kea container monitoring
Yu,

 > Yu: Can you please explain the general steps on this?

Start with an empty Dockerfile. On top of the file, add the FROM
directive with the label of the official Kea Dockerfile.

Then, copy the APK package to the container using the COPY directive.

Next, install the packages using the "apk add --allow-untrusted
isc-stork-*.apk" command.

Now, download the
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<https://gitlab.isc.org/isc-projects/stork/-/blob/master/docker/config/supervisor/stork-agent.conf?ref_type=heads>.
Use the COPY directive to copy it to the container to the
"/etc/supervisor/conf.d/ " directory.

Build the image and run the container.

I didn't test it, but I hope it works. ;)

Regards,
Slawek

On 10/07/2024 16:02, Xiao, Yu (CCI-Atlanta) wrote:
> Hi Slawek,
>
> Thank you very much for your detailed explanation! Regarding to your
> response, I have some further questions:
>
> “ You can build the Stork agent for Alpine on
> your own. It is not hard, but you need to do it on a machine with an
> Alpine system because Stork must be linked with libc-musl on Alpine, so
> you cannot use a binary linked with standard libc. You don't need to
> build the package; the executable only should be enough for your needs.”
>
> Yu: Can you please explain the general steps on this?
>
>
> “Alternatively, I can share with you the Alpine package built by our CI
> environment if you like.”
>
>
> Yu: Yes, please! I can use it for my lab for now and wait to figure out
> how to do the above procedures or the formal release.
>
> Best Regards,
>
> Yu
>
> *From: *Slawek Figiel <slawek at isc.org>
> *Date: *Wednesday, July 10, 2024 at 6:16 AM
> *To: *Xiao, Yu (CCI-Atlanta) <yu.xiao at cox.com>,
> stork-users at lists.isc.org <stork-users at lists.isc.org>
> *Subject: *Re: [EXTERNAL] Re: [stork-users] Stork for kea container
> monitoring
>
> Yu,
>
>   > My understanding is current kea docker is based upon Alpine Linux,
> but I don’t see any stork software for that version, only for Debian and
> RHEL.
>
> You are right. I forgot that we haven't published the Alpine packages
> yet. We are blocked by the technical issues with fpm - tool that we use
> to build packages. It has poor support for APK, and the output packages
> are not accepted by CloudSmith.
>
> We plan to handle this situation and migrate to another solution for
> building packages. You can track the progress at
> 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<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<https://gitlab.isc.org/isc-projects/stork/-/issues/1114>> and
> 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<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<https://gitlab.isc.org/isc-projects/stork/-/issues/863>> .
> We discussed your problem at a recent team meeting. I hope it will be
> ready soon, but there are no guarantees.
>
> Today, you have two options: You can build the Stork agent for Alpine on
> your own. It is not hard, but you need to do it on a machine with an
> Alpine system because Stork must be linked with libc-musl on Alpine, so
> you cannot use a binary linked with standard libc. You don't need to
> build the package; the executable only should be enough for your needs.
> Alternatively, I can share with you the Alpine package built by our CI
> environment if you like.
>
>   > Another question I have is that I found I had to pull the repo from
> gitlab to target machine and then run a script. After that I can see
> those images locally. But why Stork doesn’t just have all those images
> in some registry and we can just use docker pull to get them. Isn’t it
> more convenient? Or you want to give us the freedom to create a local
> registry?
>
> Kea images are published in the CloudSmith Docker registry. You don't
> need to build them on your own. See
> 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<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<https://gitlab.isc.org/isc-projects/kea-docker#using-official-kea-images-on-cloudsmith>>
> .
>
> Regards,
> Slawek
>
> On 08/07/2024 15:48, Xiao, Yu (CCI-Atlanta) wrote:
>> Hi Slawek,
>>
>> Thank you for your prompt response and information! I am new to docker,
>> can you tell me more about how to extend the official Kea Docker image
>> and install the Stork agent inside it? My understanding is current kea
>> docker is based upon Alpine Linux, but I don’t see any stork software
>> for that version, only for Debian and RHEL.
>>
>> Best Regards,
>>
>> Yu
>>
>> *From: *Stork-users <stork-users-bounces at lists.isc.org> on behalf of
>> Slawek Figiel <slawek at isc.org>
>> *Date: *Monday, July 8, 2024 at 4:39 AM
>> *To: *stork-users at lists.isc.org <stork-users at lists.isc.org>
>> *Subject: *[EXTERNAL] Re: [stork-users] Stork for kea container monitoring
>>
>> Hello Yu!
>>
>> If you would like to set up Kea with Stork in Docker, you need to extend
>> the official Kea Docker image and install the Stork agent inside it. You
>> should also prepare a second container with the Stork server.
>>
>> Unfortunately, there is no official guide yet on how to do it. We plan
>> to write one and provide Docker images with Kea and Stork together in
>> the near but undetermined future. I can try to help you if you have any
>> questions.
>>
>> You need to do two things to add Kea hooks to the Kea Docker image:
>>
>> 1. Mount the hook files as volumes or extend the Docker image and copy
>> them. The location can be any.
>> 2. Modify the Kea configuration and provide the path to the hook under
>> the `hooks-libraries` node. See
>> 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<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<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%7C638563224873477182%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C0%7C%7C%7C&sdata=M%2BxB5abdW4MHpaXybmqszDrg%2FcF%2BbqsBlGE3W0OJfAI%3D&reserved=0 <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<https://kea.readthedocs.io/en/latest/arm/hooks.html#configuring-hook-libraries>>>
>> .
>>
>> Regards,
>> Slawek
>>
>> On 05/07/2024 16:12, Xiao, Yu (CCI-Atlanta) wrote:
>>> Hi experts,
>>>
>>> I want to use Stork to monitor my kea service which is running in some
>>> docker containers. My understanding is that we need to install Stork
>>> clients inside of those kea docker containers. But I don’t see how this
>>> part in the docker-kea document or Stork document, some indeed mentioned
>>> how to import Hooks. Can you provide some suggestions? Kea experts
>>> suggested me ask in this mailer as well maybe more Stork experts have
>>> considered this use and can answer my question.
>>>
>>> Best Regards,
>>>
>>> Yu
>>>
>>>
>> --
>> Stork-users mailing list
>> Stork-users at lists.isc.org
>> 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<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<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%7C638563224873493523%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C0%7C%7C%7C&sdata=yjGaGhJwzDPovZQrbM8WjWeNJMoNRbdOGpt6O4uz6rg%3D&reserved=0 <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<https://lists.isc.org/mailman/listinfo/stork-users>>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.isc.org/pipermail/stork-users/attachments/20240712/7334877e/attachment-0001.htm>