<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Hansika Wanniarachchi on Medium]]></title>
        <description><![CDATA[Stories by Hansika Wanniarachchi on Medium]]></description>
        <link>https://medium.com/@HansikaWanniarachchi?source=rss-66afe512868e------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/2*R20uCvDyFbmL4qG_oVb9Rg.jpeg</url>
            <title>Stories by Hansika Wanniarachchi on Medium</title>
            <link>https://medium.com/@HansikaWanniarachchi?source=rss-66afe512868e------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 19:41:07 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@HansikaWanniarachchi/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[GSoC 2020 — Work Summary]]></title>
            <link>https://medium.com/@HansikaWanniarachchi/gsoc-2020-work-summary-70c9db9a5e1c?source=rss-66afe512868e------2</link>
            <guid isPermaLink="false">https://medium.com/p/70c9db9a5e1c</guid>
            <category><![CDATA[scorelab]]></category>
            <category><![CDATA[summary]]></category>
            <category><![CDATA[gsoc-2020]]></category>
            <category><![CDATA[open-source]]></category>
            <dc:creator><![CDATA[Hansika Wanniarachchi]]></dc:creator>
            <pubDate>Wed, 26 Aug 2020 08:21:31 GMT</pubDate>
            <atom:updated>2020-08-26T08:26:14.626Z</atom:updated>
            <content:encoded><![CDATA[<h3>GSoC 2020 — Work Summary</h3><p>Hi everyone….</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*sag7ihEq2aHdbqxAejH8_A.png" /></figure><p>I’m writing this article to summarize the work that I carried out during the Google Summer of Code 2020 work period. I have written an article for each work explaining the work carried out.</p><ul><li><strong>Week 1:</strong> <a href="https://medium.com/scorelab/gsoc-2020-coding-phase-begins-week-4-be2c5c0ccf80">Project environment setup and basic scaffolding</a></li><li><strong>Week 2:</strong> <a href="https://medium.com/scorelab/gsoc20-coding-phase-week-5-1f02015cd35c">Implement ukiyo webhook listener</a></li><li><strong>Week 3: </strong><a href="https://medium.com/scorelab/gsoc20-coding-phase-week-6-ebcbbaebab43">Build ukiyo agent as a docker image</a></li><li><strong>Week 4: </strong><a href="https://medium.com/scorelab/gsoc20-coding-phase-week-7-b30f4ce779fb">Implement pull manager feature</a></li><li><strong>Week 5: </strong><a href="https://medium.com/scorelab/gsoc20-coding-phase-week-8-5d7d615eb53b">Getting to know about the zero-downtime container updaters</a></li><li><strong>Week 6: </strong><a href="https://medium.com/scorelab/gsoc20-coding-phase-week-9-c34605efee68">Starting implementation of the push manager component</a></li><li><strong>Week 7:</strong> <a href="https://medium.com/scorelab/gsoc20-coding-phase-week-10-80dc068b6445">ukiyo apply the latest container by removing existing containers</a></li><li><strong>Week 8: </strong><a href="https://medium.com/scorelab/gsoc20-coding-phase-week-11-63bba119ae1e">Add feature validation and unit testing</a></li><li><strong>Week 9: </strong><a href="https://medium.com/@HansikaWanniarachchi/gsoc20-coding-phase-week-12-2cbc568aefc9">Add deployed container status viewer</a></li><li><strong>Week 10:</strong> <a href="https://medium.com/scorelab/gsoc20-coding-phase-week-13-9e2c7f451c1c">Starting implementation of the scheduler component</a></li><li><strong>Week 11: </strong><a href="https://medium.com/scorelab/gsoc20-coding-phase-week-13-bee3c3845928">Event scheduler and ukiyo documentation</a></li><li><strong>Week 12:</strong> <a href="https://medium.com/@HansikaWanniarachchi/gsoc20-coding-phase-week-15-6c6199504060">Finishing up</a></li></ul><p>Also following is a video that I created demoing the above-listed work.</p><p><a href="https://drive.google.com/file/d/1AsjIcbLw9I8kf_h2IHG2exAr12GpW5Gs/view?usp=drivesdk">Project Demo Video</a></p><p>Thanks for reading! Good Bye…🙇</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=70c9db9a5e1c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[GSoC’20 — Coding phase | Week 15]]></title>
            <link>https://medium.com/@HansikaWanniarachchi/gsoc20-coding-phase-week-15-6c6199504060?source=rss-66afe512868e------2</link>
            <guid isPermaLink="false">https://medium.com/p/6c6199504060</guid>
            <category><![CDATA[docker]]></category>
            <category><![CDATA[scorelab]]></category>
            <category><![CDATA[open-source]]></category>
            <category><![CDATA[gsoc-2020]]></category>
            <dc:creator><![CDATA[Hansika Wanniarachchi]]></dc:creator>
            <pubDate>Mon, 24 Aug 2020 16:46:55 GMT</pubDate>
            <atom:updated>2020-08-26T08:17:34.966Z</atom:updated>
            <content:encoded><![CDATA[<p><em>This is a summary of my 12th week of the coding period and the most exciting thing is, this is the last week before the final evaluation phase.</em>☺️</p><p>I am happy that I was able to achieve the goals mentioned in my proposal a week before the GSoC officially ends. Now ukiyo can run as a docker container or separate background process a deamon. I have attached the ukiyo log files into the volume mounted path, therefore though that path user will be able to find the logs in text format. Further, ukiyo maintain the logs in table format for that I have used awesome opensource <a href="https://github.com/olekukonko/tablewriter">go-table writer </a>packages that generate ASCII table on the fly. The ukiyo caching table will refresh every 30 sec and identify new events. finally completed the event scheduling and container manager features with possible unit test cases.</p><p>I opened a Pull Request with the above changes, which can be viewed at</p><p><a href="https://github.com/leopardslab/ukiyo/pull/12">Adding ukiyo scheduler component by HansikaW · Pull Request #12 · leopardslab/ukiyo</a></p><p>Also, I started writing my GSoC final report following the SCoRe Lab markdown template to briefly mention the project details, work done with PR links, log files, weekly blogs, and other required artifacts. This document will hold complete details of my GSoC 2020 work. I will anyways keep updating this until the GSoC ends. Further, I have worked with the <a href="https://github.com/HansikaW/ukiyo/wiki">ukiyo wiki</a>.</p><p>It has been an amazing week for me with a lot of new things and I was able to achieve my milestones, during the past week. Final submission deadlines are near. Thanks for bearing with me for 15 weeks 🙇</p><p>So I’m gonna stop here concluding the last episode of my GSoC project.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6c6199504060" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[GSoC’20 — Coding phase | Week 13]]></title>
            <link>https://medium.com/scorelab/gsoc20-coding-phase-week-13-bee3c3845928?source=rss-66afe512868e------2</link>
            <guid isPermaLink="false">https://medium.com/p/bee3c3845928</guid>
            <category><![CDATA[scorelab]]></category>
            <category><![CDATA[gsoc-2020]]></category>
            <dc:creator><![CDATA[Hansika Wanniarachchi]]></dc:creator>
            <pubDate>Tue, 18 Aug 2020 07:38:49 GMT</pubDate>
            <atom:updated>2020-08-18T07:38:49.715Z</atom:updated>
            <content:encoded><![CDATA[<h3>GSoC’20 — Coding phase | Week 14</h3><p><em>This is a summary of my 11th week of the coding period.</em></p><p>Finally, one of the most challenging milestones was completed which is the implementation of the scheduler component. That configures the deployment time by holding events in a queue. Previously I use to deploy the containers without setting deployment time therefore, that kind of a scenario ukiyo identified deployment time as the time when the image is pushed, but now ukiyo can deploy the container at any scheduled future time.</p><p>Further, I involved with the scheduler feature validation, then deployment should be scheduled at least before five minutes and any given future time can be scheduled. I have used system millisecond to handle time more accurately but still, there can be seen 30-sec delay to show the completeness of deployment. As there is no ukiyo dashboard, we can go with curl commands or API development tools like Postman to make API calls. The scheduled time was set in the standard date-time format like “scheduledTime”: “Aug 15 2020 00:00:00 AM” and the scheduled event will be saved in a mounted secrete file and until the scheduled time the push image will be pulled in to the cache. Incase if the ukiyo container was killed, the user would not able to make the deployment at the scheduled time because the cache has been clear, and the pulled image cannot be able to find. further, there is one restriction in time scheduling because still the time can be set in an IST zone. After I focus on ukiyo documentation and I started to write the ukiyo wiki with introduction and user guide.</p><p>That’s it for this week. Keep in touch to read more updates about my GSOC’20 experiences. Thanks for reading! 🙇</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bee3c3845928" width="1" height="1" alt=""><hr><p><a href="https://medium.com/scorelab/gsoc20-coding-phase-week-13-bee3c3845928">GSoC’20 — Coding phase | Week 13</a> was originally published in <a href="https://medium.com/scorelab">SCoRe Lab</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[GSoC’20 — Coding phase | Week 13]]></title>
            <link>https://medium.com/scorelab/gsoc20-coding-phase-week-13-9e2c7f451c1c?source=rss-66afe512868e------2</link>
            <guid isPermaLink="false">https://medium.com/p/9e2c7f451c1c</guid>
            <category><![CDATA[gsoc-2020]]></category>
            <category><![CDATA[docker]]></category>
            <category><![CDATA[scorelab]]></category>
            <category><![CDATA[docker-swarm]]></category>
            <dc:creator><![CDATA[Hansika Wanniarachchi]]></dc:creator>
            <pubDate>Wed, 12 Aug 2020 00:31:37 GMT</pubDate>
            <atom:updated>2020-08-12T00:31:37.317Z</atom:updated>
            <content:encoded><![CDATA[<h3>GSoC’20 — Coding phase | Week 13</h3><p><em>This is a summary of my 10th week of the coding period.</em></p><p>The milestones for the Third evaluation are,</p><ul><li>Implement scheduler component</li><li>Implement the container status log</li><li>Write test cases for implemented features</li><li>Test all the implemented component with execution modes</li><li>Complete documentation</li><li>Add automation tools to integrate with Github to automate code quality checks, builds.</li></ul><p>I look into produce the required output according to the milestones with improving code quality. As a first task, I started the implementation of the scheduler feature. This component identified the deployment time as the time when the image is pushed. For time identification I convert the configured deployment time into system millisecond and hold events in queue until the deployed time. Finally, within the week I was able to complete the scheduler feature. Now ukiyo can set time to deploy the containers and need to add further feature validation next week.</p><p>That’s it for this week. Keep in touch to read more updates about my GSOC’20 experiences. Thanks for reading! 🙇</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9e2c7f451c1c" width="1" height="1" alt=""><hr><p><a href="https://medium.com/scorelab/gsoc20-coding-phase-week-13-9e2c7f451c1c">GSoC’20 — Coding phase | Week 13</a> was originally published in <a href="https://medium.com/scorelab">SCoRe Lab</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[GSoC’20 — Coding phase | Week 12]]></title>
            <link>https://medium.com/@HansikaWanniarachchi/gsoc20-coding-phase-week-12-2cbc568aefc9?source=rss-66afe512868e------2</link>
            <guid isPermaLink="false">https://medium.com/p/2cbc568aefc9</guid>
            <category><![CDATA[gsoc-2020]]></category>
            <category><![CDATA[docker]]></category>
            <category><![CDATA[scorelab]]></category>
            <dc:creator><![CDATA[Hansika Wanniarachchi]]></dc:creator>
            <pubDate>Mon, 10 Aug 2020 14:49:08 GMT</pubDate>
            <atom:updated>2020-08-10T14:49:08.051Z</atom:updated>
            <content:encoded><![CDATA[<h3>GSoC’20 — Coding phase | Week 12</h3><p><em>This is a summary of my 9th week of the coding period.</em></p><p>Up to now, all the milestones related to phase II have completed. This week I mainly focus on the implementation of a new feature that can list the history of deployed containers with the status. This can be used to view the status of containers when a ukiyo dashboard is added in the future, thus I expose the APIs to get the history details.</p><p>In the next stage, one of my main milestones is to implement the scheduler component which can configure the deployment time by holding events in a queue. Then I involved with some background research on container scheduling and time setting. As feature validation was a much essential part of the implementation phase, therefore, I looked into validation stuff.</p><p>Another happiest news is I have passed the second evaluation for GSoC 2020. Thanks for the great mentoring and support from SCoRe mentors Rajika Imal, Pratik Dhanave, Milidu S. Kumarage, Rumesh Hapuarchchi. I will try to keep up my work the same way.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2cbc568aefc9" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[GSoC’20 — Coding phase | Week 11]]></title>
            <link>https://medium.com/scorelab/gsoc20-coding-phase-week-11-63bba119ae1e?source=rss-66afe512868e------2</link>
            <guid isPermaLink="false">https://medium.com/p/63bba119ae1e</guid>
            <category><![CDATA[docker]]></category>
            <category><![CDATA[scorelab]]></category>
            <category><![CDATA[gsoc-2020]]></category>
            <category><![CDATA[open-source]]></category>
            <dc:creator><![CDATA[Hansika Wanniarachchi]]></dc:creator>
            <pubDate>Sat, 01 Aug 2020 06:00:23 GMT</pubDate>
            <atom:updated>2020-08-10T14:49:29.116Z</atom:updated>
            <content:encoded><![CDATA[<h3>GSoC’20 — Coding phase | Week 11</h3><p><em>This is a summary of my 8th week of the coding period and the most exciting thing is this is the last week before the second evaluation phase.</em>☺️</p><p>As an evaluation milestone, I ‘m in the phase of completing the last task, of implementing the push manager feature with ukiyo deamon. More than half of the push manager feature has been completed, so this week I looked more into the validation and unit testing. The container downtime was not zero, hench I integrate the scheduler feature with ukiyo container runner.</p><p>Next, I added a new feature that can list the history of deployed containers. That feature can be used to view the status of containers when a ukiyo dashboard is added in the future and for that, I have exposed an API. Finally, the push manager feature was successfully implemented. Now ukiyo can access any docker registry and apply the latest container into a live docker environment by killing and removing the existing container.</p><p>Up to now, all the milestones related to phase 2 have completed. I opened a PR to add all the implemented features with the validations.</p><ul><li><a href="https://github.com/leopardslab/ukiyo/pull/10">Adding push manager feature with validations by HansikaW · Pull Request #10 · leopardslab/ukiyo</a></li><li><a href="https://github.com/leopardslab/ukiyo/pull/11">Fixing unit testing and path issue by HansikaW · Pull Request #11 · leopardslab/ukiyo</a></li></ul><p><em>Finally,</em></p><ul><li>ukiyo do trigger for a new image via webhook and pull the images from the docker registry.</li><li>ukiyo can create docker images with docker.HostConfig</li><li>ukiyo will remove the existing container version and run the latest container.</li><li>ukiyo provides the facility to expose multiple ports.</li><li>ukiyo will list the history of deployed containers.</li><li>ukiyo push manager only identifies the latest tag according to the time that the image is pushed and not consider the versioning of the docker tag</li></ul><p>That’s it for this week. I was in a tight schedule though this week, and I was able to complete my second evaluation milestones. Keep in touch to read more updates about my GSOC’20 experiences. Thanks for reading! 🙇</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=63bba119ae1e" width="1" height="1" alt=""><hr><p><a href="https://medium.com/scorelab/gsoc20-coding-phase-week-11-63bba119ae1e">GSoC’20 — Coding phase | Week 11</a> was originally published in <a href="https://medium.com/scorelab">SCoRe Lab</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[GSoC’20 — Coding phase | Week 10]]></title>
            <link>https://medium.com/scorelab/gsoc20-coding-phase-week-10-80dc068b6445?source=rss-66afe512868e------2</link>
            <guid isPermaLink="false">https://medium.com/p/80dc068b6445</guid>
            <category><![CDATA[scorelab]]></category>
            <category><![CDATA[docker]]></category>
            <category><![CDATA[gsoc-2020]]></category>
            <dc:creator><![CDATA[Hansika Wanniarachchi]]></dc:creator>
            <pubDate>Fri, 24 Jul 2020 02:14:50 GMT</pubDate>
            <atom:updated>2020-07-24T02:14:50.701Z</atom:updated>
            <content:encoded><![CDATA[<h3>GSoC’20 — Coding phase | Week 10</h3><p><em>This is a summary of my 7th week of the coding period.</em></p><p>My university exam was finished and I devoted more time to the GSoC from this week. As I mentioned in the <a href="https://medium.com/scorelab/gsoc20-coding-phase-week-9-c34605efee68">previous blog,</a> currently I’m working with the push manager feature, so first I look into how to remove existing containers before pushing the latest. According to my proposal, remove an existing container is a feature of the container manager component. also, it is a task related to the next phase, but since I have to remove the existing containers before pushing the latest, will implement that in this phase. Ukiyo identifies and kills the existing image by querying unique keys, for that I used the “ — name “ flag.</p><p>I wasn’t able to remove the containers which have already killed. That was a huge problem because ukiyo cannot up the latest containers while the ports have used in killed containers. Tried to figure out that issue and after I involved with the task of applying and running the latest container to the environment. Finally was able to handle the mentioned issue.</p><p>Next, I run the latest containers by exposing multiple ports. Now ukiyo can apply the latest container by removing the existing container, but still not push within zero-downtime. Although the downtime was not 0, the downtime could be minimized. I will look into it further.</p><p>That’s it for this week. So little has done and there is a lot more to do. Keep in touch to read more updates about my GSOC’20 experiences.</p><p>Thanks for reading! 🙇</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=80dc068b6445" width="1" height="1" alt=""><hr><p><a href="https://medium.com/scorelab/gsoc20-coding-phase-week-10-80dc068b6445">GSoC’20 — Coding phase | Week 10</a> was originally published in <a href="https://medium.com/scorelab">SCoRe Lab</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[GSoC’20 — Coding phase | Week 9]]></title>
            <link>https://medium.com/scorelab/gsoc20-coding-phase-week-9-c34605efee68?source=rss-66afe512868e------2</link>
            <guid isPermaLink="false">https://medium.com/p/c34605efee68</guid>
            <category><![CDATA[docker]]></category>
            <category><![CDATA[gsoc-2020]]></category>
            <category><![CDATA[scorelab]]></category>
            <dc:creator><![CDATA[Hansika Wanniarachchi]]></dc:creator>
            <pubDate>Sun, 19 Jul 2020 03:48:14 GMT</pubDate>
            <atom:updated>2020-07-19T03:48:14.432Z</atom:updated>
            <content:encoded><![CDATA[<h3>GSoC’20 — Coding phase | Week 9</h3><p><em>This is a summary of my 6th week of the coding period.</em></p><p>First, I started the implementation of the push manager feature. As my idea is to apply images within zero downtime, I looked into run the pulled container within ukiyo and then apply it to the live environment. Then went through the stuff related to docker image creation with the docker host.config.</p><p>Docker provides an API for interacting with the Docker daemon (called the Docker Engine API), as well as SDKs for Go and Python. The SDKs allow build and scale Docker apps and solutions quickly and easily. Instead of the official SDK, I used <a href="https://github.com/fsouza/go-dockerclient">go-dockerclient</a> which is an opensource Go package that presents a client for the Docker remote API. Finally, I was able to create a container in ukiyo itself.</p><p>I was busy with my university exams over this week, thus I could not contribute to a satisfactory level. Also, it took a little time for me to write this blog. Later, I will be allocated more time to the project after the 14th of July. Thanks to my mentors for being supportive.</p><p>The coming week will be more interesting because I plan to work on more implementation parts in the push manager feature. That’s it for this week. So little has done and there is a lot more to do next week.</p><p>Keep in touch to read more updates about my GSOC’20 experiences. Thanks for reading! 🙇</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c34605efee68" width="1" height="1" alt=""><hr><p><a href="https://medium.com/scorelab/gsoc20-coding-phase-week-9-c34605efee68">GSoC’20 — Coding phase | Week 9</a> was originally published in <a href="https://medium.com/scorelab">SCoRe Lab</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[GSoC’20 — Coding phase | Week 8]]></title>
            <link>https://medium.com/scorelab/gsoc20-coding-phase-week-8-5d7d615eb53b?source=rss-66afe512868e------2</link>
            <guid isPermaLink="false">https://medium.com/p/5d7d615eb53b</guid>
            <category><![CDATA[gsoc-2020]]></category>
            <category><![CDATA[scorelab]]></category>
            <category><![CDATA[documentary]]></category>
            <dc:creator><![CDATA[Hansika Wanniarachchi]]></dc:creator>
            <pubDate>Tue, 14 Jul 2020 08:10:51 GMT</pubDate>
            <atom:updated>2020-07-14T08:10:51.089Z</atom:updated>
            <content:encoded><![CDATA[<h3>GSoC’20 — Coding phase | Week 8</h3><p><em>This is a summary of my 5th week of the coding period.</em></p><p>Over this week, I was busy with important university assignments, and also from next week, university mid-semester examinations will begin. Therefore, It was not possible to make a good contribution though this week. Later, I will be allocated more time to the project after the 14th july. Thanks for my mentors for being supportive. This week I focused on the research part rather than the coding.</p><p>The milestones for the second evaluation as follows:</p><ul><li>Implement push manager component</li><li>Implement Ukiyo deamon</li><li>Write test cases for implemented features.</li></ul><p>I look into produce the required output according to the milestones with improving code quality. As a first task, I started the implementation of the push manager feature to apply the latest images into a live environment. My idea is to apply images within zero downtime, thus I went through the existing methodologies. I have learned that it is possible to apply images in a zero downtime if ukiyo could round the pulled images within the ukiyo container and apply it to the environment.</p><p>It is necessary to focus on validation as ukiyo developing as a tool. My initial plan is to implement the push manager feature under the following tasks,</p><ul><li>create the docker images with docker.HostConfig</li><li>remove the existing container version</li><li>run the container</li><li>allow multiple export ports.</li></ul><p>The blog provides just an overview of what I have planned to do. This week mostly I involved with research-based stuff but the coming week will be more interesting because I plan to work on more implementation.</p><p>Keep in touch to read more updates about my GSOC’20 experiences. Thanks for reading! 🙇</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5d7d615eb53b" width="1" height="1" alt=""><hr><p><a href="https://medium.com/scorelab/gsoc20-coding-phase-week-8-5d7d615eb53b">GSoC’20 — Coding phase | Week 8</a> was originally published in <a href="https://medium.com/scorelab">SCoRe Lab</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[GSoC’20 — Coding phase|Week 7]]></title>
            <link>https://medium.com/scorelab/gsoc20-coding-phase-week-7-b30f4ce779fb?source=rss-66afe512868e------2</link>
            <guid isPermaLink="false">https://medium.com/p/b30f4ce779fb</guid>
            <category><![CDATA[gsoc-2020]]></category>
            <category><![CDATA[docker]]></category>
            <category><![CDATA[scorelab]]></category>
            <dc:creator><![CDATA[Hansika Wanniarachchi]]></dc:creator>
            <pubDate>Fri, 03 Jul 2020 12:12:23 GMT</pubDate>
            <atom:updated>2020-07-03T12:12:23.572Z</atom:updated>
            <content:encoded><![CDATA[<h3>GSoC’20 — Coding phase|Week 7</h3><p><em>This is the last week before the evaluation phase...</em></p><p>As a first evaluation milestone, I had to complete my last task, of implementing the pull manager feature to pull the images from the docker registry.</p><p>Ukiyo can access any container registry and do trigger for a new image via webhook but to pull the image need access for the credentials or token keys of the registry. As mentors suggest, I went with a file-based approach to store the token keys for that I used a JSON file as a data storage. Next, I focused on the implementation of pull manager feature. Once pulled, my idea is to apply the image to the environment with zero downtime, hence I involved with small researching part on that.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*a6kbXoyiT8VDX52rjPQIsQ.png" /><figcaption>ukiyo successfully pull the images.</figcaption></figure><p>The feature was successfully implemented but in the docker live environment, there was an issue in — — . That error occurs because the ukiyo code needs to interact with the Docker API in order to pull the containers, therefore need to mount /var/run/docker.sock into the container with the -v flag when the run the agent. After I wrote the possible unit test cases for the implemented feature and created a PR with Dev Setup Guide.</p><p><a href="https://github.com/leopardslab/ukiyo/pull/7">Add pull manager feature by HansikaW · Pull Request #7 · leopardslab/ukiyo</a></p><p>Finally… all the milestones related to Phase 1 are completed,</p><ul><li>ukiyo can access any container registry and do trigger for a new image via webhook.</li><li>ukiyo pull the images from DockerHub using ukiyo API the docker token send by any user</li><li>Build ukiyo agent as a container running alongside other containers</li></ul><p>That’s it for this week. I was in a tight schedule though this week, and I was able to complete my first evaluation milestones. Keep in touch to read more updates about my GSOC’20 experiences. Thanks for reading! 🙇</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b30f4ce779fb" width="1" height="1" alt=""><hr><p><a href="https://medium.com/scorelab/gsoc20-coding-phase-week-7-b30f4ce779fb">GSoC’20 — Coding phase|Week 7</a> was originally published in <a href="https://medium.com/scorelab">SCoRe Lab</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>