<?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[Zenko - Medium]]></title>
        <description><![CDATA[Zenko open source multi-cloud data controller that lets you be in control of your data and leverage the efficiency of private and public clouds. - Medium]]></description>
        <link>https://medium.com/zenko?source=rss----eb1c276a165d---4</link>
        <image>
            <url>https://cdn-images-1.medium.com/proxy/1*TGH72Nnw24QL3iV9IOm4VA.png</url>
            <title>Zenko - Medium</title>
            <link>https://medium.com/zenko?source=rss----eb1c276a165d---4</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 20:25:34 GMT</lastBuildDate>
        <atom:link href="https://medium.com/feed/zenko" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[How to use Zenko for Multi-CDN Media Streaming]]></title>
            <link>https://medium.com/zenko/how-to-use-zenko-for-multi-cdn-media-streaming-90bf62c4407a?source=rss----eb1c276a165d---4</link>
            <guid isPermaLink="false">https://medium.com/p/90bf62c4407a</guid>
            <category><![CDATA[videos]]></category>
            <category><![CDATA[aws]]></category>
            <dc:creator><![CDATA[Stefano Maffulli]]></dc:creator>
            <pubDate>Fri, 04 May 2018 08:56:01 GMT</pubDate>
            <atom:updated>2018-05-04T08:56:01.521Z</atom:updated>
            <content:encoded><![CDATA[<p>If you want to see extreme use cases of huge storage and distribution needs you go check the demos at NAB. Our colleagues at <a href="https://www.scality.com/nab-2018/">Scality</a> demonstrated how to use the multi-cloud capabilities of Zenko in a typical workflow, culminating in a multi-CDN distribution of a video. The demo consists in a movie being edited with Adobe Premiere to add some background music and overlays. Once saved, a <a href="https://gist.github.com/obiyann/d990a94f928ddb3e8cd68b7e2197e068">simple Python script</a> is invoked to transcode the movie in multiple versions optimized for different types of devices using <a href="https://www.ffmpeg.org/">FFMpeg</a>. Each resulting file is uploaded to a single Zenko instance where the magic happens: the newly uploaded files are automatically replicated to two different locations, one in Amazon S3 and one in Azure Blob Storage, each with a CDN frontend.</p><p>Looking at the <a href="https://gist.github.com/obiyann/d990a94f928ddb3e8cd68b7e2197e068">Python code</a> that does the upload in Zenko you’ll notice how simple it is: just a RESTful PUT call to what looks just like a S3-compatible bucket. That’s what Zenko does: it keeps your code very simple and abstracts the complexity of managing a multi-cloud environment. The replication rules can be either managed with the <a href="https://zenko.io/admin">Orbit web GUI</a> or by editing <a href="https://github.com/scality/S3/blob/master/docs/USING_PUBLIC_CLOUDS.rst">configuration files</a>. Besides, Zenko won’t mangle the files uploaded in the different clouds: we commit to giving you freedom and control of your data so you can still access the objects as they are uploaded, same file names and attributes.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2F4e0OCDoceZI&amp;src_secure=1&amp;url=http%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3D4e0OCDoceZI&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2F4e0OCDoceZI%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="1280" height="720" frameborder="0" scrolling="no"><a href="https://medium.com/media/c1d5d5367aa7cd6d112c5260722fbe64/href">https://medium.com/media/c1d5d5367aa7cd6d112c5260722fbe64/href</a></iframe><p>Inspired? Excited? Ask questions on <a href="https://forum.zenko.io/">Zenko community forum</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=90bf62c4407a" width="1" height="1" alt=""><hr><p><a href="https://medium.com/zenko/how-to-use-zenko-for-multi-cdn-media-streaming-90bf62c4407a">How to use Zenko for Multi-CDN Media Streaming</a> was originally published in <a href="https://medium.com/zenko">Zenko</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Use Zenko CloudServer as a backend for Docker Registry]]></title>
            <link>https://medium.com/zenko/use-zenko-cloudserver-as-a-backend-for-docker-registry-482df6ec7947?source=rss----eb1c276a165d---4</link>
            <guid isPermaLink="false">https://medium.com/p/482df6ec7947</guid>
            <category><![CDATA[s3]]></category>
            <category><![CDATA[docker]]></category>
            <dc:creator><![CDATA[Stefano Maffulli]]></dc:creator>
            <pubDate>Wed, 11 Apr 2018 23:20:55 GMT</pubDate>
            <atom:updated>2018-04-11T23:21:41.055Z</atom:updated>
            <content:encoded><![CDATA[<p><em>Contributed by </em><a href="https://www.linkedin.com/in/romfreiman/"><em>Rom Freiman,</em></a><em> Dir. R&amp;D at </em><a href="https://www.stratoscale.com/"><em>Stratoscale</em></a></p><p>Docker Registry is a service enabling storage and distribution of private Docker images, useful in corporate settings. Private Docker registries have multiple options for storage configuration and Zenko’s CloudServer is one of them. This tutorial demonstrates how to deploy a private Docker Registry with Zenko as your private on-premises S3 backend.</p><h3>Prerequisites and assumptions</h3><p>You’ll need to have installed the following software:</p><ul><li>Docker daemon (v1.10.3 or above)</li><li>Python (v2.7.12 or above)</li><li>AWS CLI (v1.11.123 or above)</li></ul><pre>$&gt; pip install awscli</pre><p>Configure <em>aws</em> credentials:</p><pre>$&gt; aws configure <br>AWS Access Key ID []: {{YOUR_ACCESS_KEY_ID}}<br>AWS Secret Access Key []: {{YOUR_SECRET_KEY}} <br>Default region name []: us-east-1 <br>Default output format[]: json</pre><p>Assumptions:</p><ol><li>Both S3 and Registry will run on the same physical server, in order to avoid dealing with networking. If you choose to run it on different servers, verify that you have routing from the Registry server towards CloudServer(TCP, port 8000)</li><li>The S3 storage will use the containers storage and will be lost once the container will be stopped. For persistency, you should create appropriate volumes on the host and mount them as Docker volumes for the CloudServer container</li><li>The consumption of the Docker Registry is from localhost, hence we’ll not dive into SSL and certificates generation (<a href="http://s3-server.readthedocs.io/en/latest/GETTING_STARTED/#scality-with-ssl">but you can if you want to</a>).</li></ol><h3>Run Zenko CloudServer container</h3><p>User the <em>docker run</em> utility to start Zenko CloudServer:</p><pre>$&gt; docker run -d --name cloudserver -p 8000:8000 -e \ SCALITY_ACCESS_KEY_ID={{YOUR_ACCESS_KEY_ID}} -e \ SCALITY_SECRET_ACCESS_KEY={{YOUR_SECRET_KEY}} zenko/cloudserver</pre><p>The output will look something like the sample below:</p><pre><em>Unable to find image &#39;zenko/cloudserver:latest&#39; locally<br>latest: Pulling from zenko/cloudserver<br>Digest: sha256:8f640c3399879925809bd703facf128a395444e2d4855334614e58027bcac436<br>Status: Downloaded newer image for zenko/cloudserver:latest<br>4f08be7e77fe8e47b8c09036e9f5fa4e29d7a42b23bd1327a2a4f682c5c48413</em></pre><p>Once Docker has pulled zenko/cloudserver, it will run it so you can use AWS CLI to create a dedicated bucket in Zenko CloudServer:</p><pre>$&gt; aws s3api --endpoint-url=http://127.0.0.1:8000 create-bucket --bucket docker-registry</pre><p>Sample output:</p><pre><em>{<br>    &quot;Location&quot;: &quot;/docker-registry&quot;<br>}</em></pre><p>Verify it exists:</p><pre>aws s3 --endpoint-url=http://127.0.0.1:8000 ls s3://</pre><p>Sample output:</p><pre><em>2017-08-01 23:05:44 docker-registry</em></pre><h3>Configure and run your private Docker Registry hosted in your local CloudServer container</h3><p>Create a config file looking like below, and located at <em>/home/{{YOUR_WORKDIR}}/config.yml</em>:</p><pre>version: 0.1<br>log:<br>  level: debug<br>  formatter: text<br>  fields:<br>    service: registry<br>    environment: staging<br>storage:<br>  s3:<br>    accesskey: newAccessKey<br>    secretkey: newSecretKey<br>    region: us-east-1<br>    regionendpoint: <a href="http://127.0.0.1:8000/">http://127.0.0.1:8000</a><br>    bucket: docker-registry<br>    encrypt: false<br>    secure: false<br>    v4auth: true<br>http:<br>  addr: :5000<br>  headers:<br>    X-Content-Type-Options: [nosniff]<br>health: <br>  storagedriver:<br>    enabled: true<br>    interval: 10s<br>    threshold: 3</pre><p><strong><em>Important fields:</em></strong></p><ol><li><strong>http</strong> : the registry will listed to port 5000;</li><li><strong>s3</strong> : the actual s3 backend configuration, including endpoint, credentials and the bucket name;</li><li><strong>health</strong> : the registry will actively probe the s3 backend (above spawned CloudServer container) to check that it’s active.</li></ol><p>Spawn the registry, while mounting the configuration into the container:</p><pre>docker run -d --name=zenkoregistry --net=host -v /home/{{YOUR_WORKDIR}}/config.yml:/etc/docker/registry/config.yml:z registry:2</pre><p>Sample output (expected private zenkoregistry uuid):</p><pre><em>4f08be7e77fe8e47b8c09036e9f5fa4e29d7a42b23bd1327a2a4f682c5c48413</em></pre><p>Now it’s a time for testing… Let’s pull an Alpine container, push it into the registry, and check it was created:</p><pre>docker pull alpine<br>docker tag alpine:latest 127.0.0.1:5000/alpine:latest<br>docker push 127.0.0.1:5000/alpine:latest  # the actual submission to the newly spawned registry<br>docker rmi alpine:latest; docker rmi 127.0.0.1:5000/alpine:latest # local cleanup before pulling from the registry.<br>docker pull 127.0.0.1:5000/alpine:latest</pre><p><strong>And… voilà!!! </strong>Now, you can list what is inside the docker-registry bucket hosted on CloudServer to check how <em>zenkoregistry</em> actually saved the data:</p><pre>aws s3 --endpoint-url=http://127.0.0.1:8000 ls --recursive s3://docker-registry</pre><p>Sample output:</p><pre><em>2017-08-02 12:21:41        528 docker/registry/v2/blobs/sha256/09/0930dd4cc97ed5771ebe9be9caf3e8dc5341e0b5e32e8fb143394d7dfdfa100e/data<br>2017-08-02 12:21:40    1990402 docker/registry/v2/blobs/sha256/6d/6d987f6f42797d81a318c40d442369ba3dc124883a0964d40b0c8f4f7561d913/data<br>2017-08-02 12:21:40       1520 docker/registry/v2/blobs/sha256/73/7328f6f8b41890597575cbaadc884e7386ae0acc53b747401ebce5cf0d624560/data<br>2017-08-02 12:21:40         71 docker/registry/v2/repositories/alpine/_layers/sha256/6d987f6f42797d81a318c40d442369ba3dc124883a0964d40b0c8f4f7561d913/link<br>2017-08-02 12:21:41         71 docker/registry/v2/repositories/alpine/_layers/sha256/7328f6f8b41890597575cbaadc884e7386ae0acc53b747401ebce5cf0d624560/link<br>2017-08-02 12:21:41         71 docker/registry/v2/repositories/alpine/_manifests/revisions/sha256/0930dd4cc97ed5771ebe9be9caf3e8dc5341e0b5e32e8fb143394d7dfdfa100e/link<br>2017-08-02 12:21:41         71 docker/registry/v2/repositories/alpine/_manifests/tags/latest/current/link<br>2017-08-02 12:21:41         71 docker/registry/v2/repositories/alpine/_manifests/tags/latest/index/sha256/0930dd4cc97ed5771ebe9be9caf3e8dc5341e0b5e32e8fb143394d7dfdfa100e/link</em></pre><h3>Troubleshooting</h3><p>Not working? No problem! Here are a few places to check:</p><ul><li>AWS credentials:</li></ul><pre>cat ~/.aws/credentials</pre><p>Compare them to the one you used to spawn the <em>cloudserver</em> and to those that are written in the s3registry config file;</p><ul><li>CloudServer logs:</li></ul><pre>docker logs cloudserver</pre><p>Check whether the healthcheck is received every 10 sec and the response code to it is 200;</p><ul><li>zenkoregistry logs:</li></ul><pre>docker logs zenkoregistry</pre><p>Check the permissions of the config file, the port it uses (5000), try to run the container in privileged mode, etc.</p><p>Still not working? Still no problem! <a href="http://forum.scality.com/">Reach out to the Zenko team on the forum</a>: we’re very happy to help!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=482df6ec7947" width="1" height="1" alt=""><hr><p><a href="https://medium.com/zenko/use-zenko-cloudserver-as-a-backend-for-docker-registry-482df6ec7947">Use Zenko CloudServer as a backend for Docker Registry</a> was originally published in <a href="https://medium.com/zenko">Zenko</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why the world needs an open source multi-cloud data controller]]></title>
            <link>https://medium.com/zenko/why-the-world-needs-an-open-source-multi-cloud-data-controller-d11d7d63433c?source=rss----eb1c276a165d---4</link>
            <guid isPermaLink="false">https://medium.com/p/d11d7d63433c</guid>
            <category><![CDATA[aws-s3]]></category>
            <category><![CDATA[cloud-computing]]></category>
            <category><![CDATA[hybrid-cloud]]></category>
            <category><![CDATA[azure]]></category>
            <category><![CDATA[cloud-storage]]></category>
            <dc:creator><![CDATA[Stefano Maffulli]]></dc:creator>
            <pubDate>Mon, 02 Apr 2018 16:40:19 GMT</pubDate>
            <atom:updated>2018-04-02T16:39:57.582Z</atom:updated>
            <cc:license>https://creativecommons.org/licenses/by-nd/4.0/</cc:license>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*yzK4HloldrUW4eOFbFg4Xw.jpeg" /></figure><p>The cloud landscape is hazy with buzzwords. One minute, everyone’s talking about hybrid cloud, the next it’s multi-cloud making it near impossible to get a clear outlook on what really matters. I won’t endear myself to folks by introducing another term, but here goes: what companies really need now is a multi-cloud data controller. That’s why we created the open-source multi-cloud data controller called Zenko.</p><p>In our vision, multi cloud is simply the acknowledgment that the enterprise world is application-centric and that each application has its own infrastructure needs that evolve with it over time. It’s only natural to want the freedom to leverage multiple, diverse cloud infrastructures at the same time and over time.</p><p>So when we say multi-cloud, it applies both to private clouds and public clouds. There’s a need to easily and transparently use clouds based on their strengths given that AWS, Azure and Google Cloud each have their own area of expertise.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/320/0*1rloOnM0PMCYQZI2.png" /></figure><p>Multi-cloud differs from hybrid because it takes into consideration that an enterprise runs hundreds of different applications. Hybrid is more focused on tiering of old or lower-value data to the cloud while multi-cloud centers around optimizing work flows and using the right tool for the right job at the right time. Customers tell us that they still like to manage storage locally in their own data centers, but need to use the cloud to leverage the native services they offer. This requires data mobility between clouds, whether private or public cloud services.</p><p>Multi-cloud also includes a notion of freedom. Another recurring refrain that I hear from customers is the fear of being locked into a specific cloud platform, whether public or private. True freedom and data mobility can only arise if different cloud platforms use the same communication protocols and share common abstractions to describe containers, objects, metadata and authentication credentials.</p><p>Because to date the large public cloud providers or the numerous software-defined storage vendors have deserted this area, we started working on Zenko in 2017. That source code is available today as a set of <a href="https://github.com/scality/zenko">open community projects on Github</a> under an Apache 2.0 license.</p><p>Here are four key features of Zenko, our multi-cloud data controller:</p><ul><li><strong>AWS S3 API </strong>— Single API set and 360° access to any cloud<br>Gives developers an abstraction layer to enable freedom to use any cloud, any time. One interface using the S3 API, supporting multi-cloud backend data storage, both on-premises (Scality RING and Docker) and public cloud with AWS S3, Microsoft Azure Blob Storage (and Google Cloud Storage to come soon)</li><li><strong>Native Format — </strong>Data written through Zenko is stored in the native format of the target storage and can be read directly, without the need to go through Zenko. So data written in Azure Blob Store or in Amazon S3 can leverage the advanced services of these public clouds</li><li><strong>Data work flow — </strong>Coming in September 2018, a policy-based data management engine for seamless data replication, data migration services or extended cloud work flow services like cloud analytics and content distribution</li><li><strong>Metadata search — </strong>Provides the ability to subset data based on key attributes. Interpret petabyte-scale data and easily manipulate it on any cloud to separate high-value information from data noise</li></ul><p>Zenko focuses on ease-of-use and operation and relies on Docker Swarm for deployment and high availability with plans to support Kubernetes, too. It runs as a set of containers either locally or in the cloud, anywhere that Docker can run — a laptop, physical servers or any existing cloud provider.</p><p>Please check out our community website, <a href="http://zenko.io/">zenko.io</a>, to learn more about Zenko and its architecture, find out how to contribute to the project or download and use this new open source multi-cloud data controller today.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d11d7d63433c" width="1" height="1" alt=""><hr><p><a href="https://medium.com/zenko/why-the-world-needs-an-open-source-multi-cloud-data-controller-d11d7d63433c">Why the world needs an open source multi-cloud data controller</a> was originally published in <a href="https://medium.com/zenko">Zenko</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What’s Zenko?]]></title>
            <link>https://medium.com/zenko/whats-zenko-96ddd2dbd4a3?source=rss----eb1c276a165d---4</link>
            <guid isPermaLink="false">https://medium.com/p/96ddd2dbd4a3</guid>
            <category><![CDATA[cloud-computing]]></category>
            <category><![CDATA[cloud-storage]]></category>
            <category><![CDATA[s3]]></category>
            <dc:creator><![CDATA[Stefano Maffulli]]></dc:creator>
            <pubDate>Mon, 02 Apr 2018 16:34:35 GMT</pubDate>
            <atom:updated>2018-04-02T16:34:34.939Z</atom:updated>
            <content:encoded><![CDATA[<p>Zenko is the open source multi-cloud data controller, a stack of projects that enables anyone to stay in control of their data, whether they’re stored in private or public clouds.</p><p>Zenko presents the de-facto S3 APIs to any application and is managed using AWS toolset but stores the data on any supported private cloud storage or directly in public cloud.</p><p>The Zenko roadmap includes smart data management services, especially policy-based data mobility, lifecycle management and unified metadata search.</p><p>A piece of Zenko is Orbit, a cloud-based portal that simplifies the management of Zenko’s multi-cloud capabilities for data placement, workflows and global search. <a href="https://zenko.io/admin">Try the public beta of Orbit for free</a>.</p><h3>What makes Zenko?</h3><p>One can think of Zenko as a stack deployed with Docker Swarm or Kubernetes. The main components of the stack are:</p><ul><li><a href="https://github.com/scality/S3">Cloudserver</a> — the open-source Node.js implementation of a server handling the Amazon S3 protocol.</li><li><a href="https://github.com/scality/backbeat">Backbeat</a> — the core engine for asynchronous replication, optimized for queuing metadata updates and dispatching work to long-running tasks in the background.</li><li><a href="https://github.com/scality/clueso">Clueso </a>— the metadata search engine for all your data, stored anywhere on public and private clouds.</li><li><a href="https://github.com/scality/utapi">Utapi </a>— a general purupose API service for tracking resource utilization and reporting metrics.</li><li>And <a href="https://github.com/scality/zenko">Zenko</a> project itself — the deployment and management tool for all the pieces.</li></ul><p>Zenko’s development is sponsored mainly by <a href="https://scality.com/">Scality</a> but <a href="https://zenko.io/community">contributions are welcome</a>.</p><h3>What does the name Zenko mean?</h3><p>Story time! In Asian mythologies (Japanese, Chinese, Thai, and Indian at least), foxes have held a strong role since the 11th century. The Konjaku Monogatarishu, a collection of Ancient Tales from Asia, is the first written reference we have to zenkos.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/0*onHPxbdupDXKgFZx.jpg" /></figure><p>It gains tails as it matures and, after 100 years, when reaching its final stage, it has 9 tails, and may then become a zenko. (fun fact: did you know Tails, the character from Sonic The Hedgehog, is a zenko?)</p><p>Zenkos are celestial, benevolent foxes, who attached themselves to Samurai families, protecting them in exchange for housing. And <a href="https://www.zenko.io/blog/founders-message/">Zenko strives to be a role-model in the open source world</a>, by attaching itself to the open source contributors and users, and protecting their technical endeavors.</p><p>Foxes are, among other things, universal. We talked about zenko as a Japanese word, but there are divine occurrences of the fox globally: in Peru, there was a Fox god for the Andean people; in Egypt, foxes were good omens; in Persia, foxes were the equivalent of Charon; for a number of Native People from North America, the fox spirit was a strong one… And Zenko is global. Its core engineering team is split between France, the USA, and New Zealand, and its contributors come from very diverse backgrounds… object (and file) storage is a universal need, Zenko is aiming at providing a universal answer.</p><p>Finally, foxes are smart, witty, artful, aware, swift, playful, brave… you name it.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=96ddd2dbd4a3" width="1" height="1" alt=""><hr><p><a href="https://medium.com/zenko/whats-zenko-96ddd2dbd4a3">What’s Zenko?</a> was originally published in <a href="https://medium.com/zenko">Zenko</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>