<?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 Melvin Hillsman on Medium]]></title>
        <description><![CDATA[Stories by Melvin Hillsman on Medium]]></description>
        <link>https://medium.com/@mrhillsman?source=rss-be128643cc06------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*-FV9g58UTVNeAVJovdUtWg.jpeg</url>
            <title>Stories by Melvin Hillsman on Medium</title>
            <link>https://medium.com/@mrhillsman?source=rss-be128643cc06------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 22:31:39 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@mrhillsman/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[OpenStack Ops Midcycle — Mexico City]]></title>
            <link>https://medium.com/@mrhillsman/openstack-ops-midcycle-mexico-city-e24b5f1c3acb?source=rss-be128643cc06------2</link>
            <guid isPermaLink="false">https://medium.com/p/e24b5f1c3acb</guid>
            <category><![CDATA[containers]]></category>
            <category><![CDATA[cloud-compu]]></category>
            <category><![CDATA[iaas]]></category>
            <category><![CDATA[mexico-city]]></category>
            <category><![CDATA[openstack]]></category>
            <dc:creator><![CDATA[Melvin Hillsman]]></dc:creator>
            <pubDate>Thu, 17 Aug 2017 19:13:40 GMT</pubDate>
            <atom:updated>2017-08-17T19:16:39.502Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9jV13xHr_DZ9fOsbUW387A.jpeg" /><figcaption>Mexico City International Airport</figcaption></figure><p><strong><em>Next Midcycle — March 7–8th 2018, Tokyo, Japan — join #openstack-operators Tuesdays @ 1400UTC for more information</em></strong></p><p>It was great spending time with the OpenStack community in Mexico City. Our host venue — Centro de Cultura Digital — did not disappoint with its interactive light wall, polyvalent space, memorial space with audible art and light, and its theater with seating up to 120 where we held our sessions.</p><p>As is normally the case with the Ops Midcycle we had a good mix of users and developers which made for very interesting and interactive discussions. A full list of the etherpads used for the midcycle can be found here — <a href="https://etherpad.openstack.org/p/MEX-ops-meetup">https://etherpad.openstack.org/p/MEX-ops-meetup</a>.</p><p>We asked some folks who moderated a session to provide a few things that stood out to them during the discussions:</p><p><strong><em>Chris Morgan of Bloomberg | Documentation of Older Versions of OpenStack</em></strong></p><p>I run an older revision of openstack (9 production quality Liberty clusters) and I still need the documents for it, I wanted to share our problems and see who else is in the same boat. We have a full-time contractor working for us (Bloomberg) from Canonical who investigated this and it turns out that the commonly given answer for old documents (“just build from tag”) does not work well at all. I explained that we are pushing for a better solution for the entire community and that work is still in flight. For example there is some acceptance of keeping documentation longer in future, but distinguishing it better from the latest via use of watermarks, for example. We may be able to keep the mitaka-onwards documents longer (they haven’t been taken down yet).</p><p><strong><em>Sampath Priyankara of NTT Communications | Extreme Testing</em></strong></p><p>Since this is a quite new work, it took me most of the time in the session to explain why and what we are doing in extreme testing. We had a good discussion on what we should include in the testing and what other aspects to consider. I started a follow-up ML thread — <a href="http://lists.openstack.org/pipermail/openstack-dev/2017-August/121104.html">http://lists.openstack.org/pipermail/openstack-dev/2017-August/121104.html</a> — to continue this discussion and getting good response.</p><p><strong><em>Robert Starmer of Kumulus Technologies | OpenStack on Containers + Containers on OpenStack</em></strong></p><p><strong>OpenStack on Containers</strong>:<br>Folks are interested in seeing a Kubernetes solution, but in the group, most had only dabbled with some container ops, and saw the value in at least containerization. Some in the group were still happy with, and continuing with the LXC based approach (OpenStack Ansible, or similar), and others are moving on with Kolla (a subset have tried it, a smaller subset have it in production). All saw the value of this mechanism, and those that aren’t on containers would like better guidance on how to migrate from bare metal deploy to container deploy (which was another session)</p><p><strong>Containers on OpenStack</strong>:<br>Still massive confusion on what networking to use, what works, how the pieces are all to come together. Most are not aware if their customers are deploying containers _on_ their OpenStack systems (i.e., there’s no integration between the two domains). Some are investigating how one might manage container deployments (specifically Kubernetes) on OpenStack, and what integration makes sense (without RBAC in K8S that maps to Keystone, that doesn’t integrate well), Cinder -&gt; K8S PVs works, LBaaS-&gt;k8s loadbalancer works, but again, what’s the integration model (is there even LBaaS available, etc.) Magnum is a no-op for the group, Zun is outside of most of the groups scope/interest. Almost no-one had even heard of Kuryr (and the “right” network model didn’t seem to include Neutron anyway, or so I understood from a couple folks in the group).</p><p><strong><em>Shintaro Mizuno of NTT Communications | Telco/NFV</em></strong></p><p>NTT and AT&amp;T shared their experiences on operating VNF in production. Most of the challenges come from the fact that the VNF(i.e. vEPCs) are monster applications, which were brought straight from legacy hardware, and requires full hardware performance. Technical challenges are around SR-IOV, OVS-DPDK, CPU pinning and NUMA placement which is to get performance VNF requires. If we have enough NFV operators in the future Meetups, we can discuss these issues in more detail. NTT is working on upstreaming NFV related features into Blazar (non-official project). Ops Telco/NFV WG is discussing to merge with LCOO WG.</p><p><strong><em>Sean McGinnis of Huawei | TC Feedback</em></strong></p><p>I moderated to talk about the TCs role and stimulate discussion around needs and issues. We answered some questions about what the TC does and does not do. The session ended up being mostly a discussion about having LTS releases. I really pushed that this is something that Red Hat, Canonical, Suse, and Huawei need to collaborate to support. The biggest asks were to help skip level upgrades and longer support for releases.</p><p>These are just a few of the sessions we had during the midcycle. Overall we had a great time and look forward to bringing these discussions to the community and furthering the work of OpenStack.</p><p>We greatly appreciate our sponsors <strong>Bloomberg, Centro de Cultura Digital, Nearsoft, Nearshore, Suse, Meltsan, and Sentinel</strong>. We look forward to seeing as many of you as we can during the <strong>next midcycle — March 7–8th in Tokyo, Japan</strong>, and please remember to visit #openstack-operators IRC channel on Tuesdays @ 1400UTC and/or join the OpenStack Operators mailing list — <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators</a> — to stay updated.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e24b5f1c3acb" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[boston2017-the-takeaway.md]]></title>
            <link>https://medium.com/@mrhillsman/boston2017-the-takeaway-md-3de134f1586d?source=rss-be128643cc06------2</link>
            <guid isPermaLink="false">https://medium.com/p/3de134f1586d</guid>
            <category><![CDATA[openstack]]></category>
            <category><![CDATA[cloud-computing]]></category>
            <category><![CDATA[openstack-summit]]></category>
            <dc:creator><![CDATA[Melvin Hillsman]]></dc:creator>
            <pubDate>Mon, 15 May 2017 05:33:30 GMT</pubDate>
            <atom:updated>2017-05-15T12:22:04.990Z</atom:updated>
            <content:encoded><![CDATA[<h3>The Takeaway — OpenStack Boston 2017</h3><p>Personally, I believe the OpenStack Summit Boston was clearly a shift in the future of OpenStack and IaaS in the world of OSS. With the introduction of OpenSource Days and combining the Design and Ops Summits into the Forum, along with the general sessions, the Summit has content for the beginner to the day-to-day individual contributor. Vendors looking to jump into the foray and those wanting to set themselves apart from the rest, all could find something.</p><h4>The Forum</h4><figure><img alt="The Forum" src="https://cdn-images-1.medium.com/max/933/0*pMmqL8KuarrmnT9P.png" /></figure><p>In years past the OpenStack Summit featured two tracks called the Design Summit and the Ops Summit. Breaking from that tradition this year brought the Forum. What it boils down to is Developers and Non-developers getting together to discuss a range of topics including but not limited to very specific sessions, like feedback sessions for individual projects, hacking rooms, onboarding for new contributors, to sessions covering more community-wide initiatives like unanswered user requirements and working with adjacent communities, like Kubernetes.</p><p>What I found most appealing about the Forum was that it brought a special kind of energy to discussions and I believe set the stage for success going forward as conversations go beyond the Forum.</p><p>For example, in one session we discussed the Operations and Administrations Guides and came to a conclusion that was reasonable for the Documentation team and Operators who use these guides in light of the recent hit to the Documentation team in losing some members. There were numerous attempts to gain consensus in past OpenStack Summits, the Ops Midcycle, IRC meetings, and the ever present mailing lists but none of them seemed to really get to the bottom of the issue, but the Forum allowed a direct coming to grips with the state of things and deciding rather than just discussing. This is the power of the Forum.</p><h4>OpenSource Days</h4><figure><img alt="OpenSource Days" src="https://cdn-images-1.medium.com/max/316/0*cR71o69UaobrHcvj.png" /></figure><p>When some of the sessions specific to OpenStack only were getting to the point my brain was overloaded, it was great to be able to break away and attend an OpenSource Days talk regarding 5G and get the opportunity to meet some of the folks working on the next generation of wireless networks.</p><p>With 11 other communities invited to participate OpenSource Days was a refreshing addition. The OpenStack Summit is attended by folks from many different communities and this year those communities got a chance to have dedicated space to discuss, learn, and teach about how they are a part of the open infrastructure community and what role they play. Ceph and FD.io focusing on storage and data I/O, Kubernetes and CloudFoundry on containers and applications, OPNFV, OpenSwitch, OpenvSwitch, Open Daylight, and OpenContrail tackling aspects of the network, and Ansible and Cloudify zeroing in on automation and orchestration, one could spend their entire OpenStack Summit going from novice to intermediate level technical chops with these tools as well as establish a network and friendships with key contributors.</p><p>As a result of inviting out other communities I was able to spend time with Caleb Miles and Ihor Dvoretskyi from Kubernetes along with Doug Hellmann, Thierry Carrez, and Davanum Srinivas. While we sat around having a time just getting to know more about each other, the conversation shifted to knowledge being shared around governance and understanding the nuances of each community.</p><h4>The Takeaway</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*cYC-R_5_93nYgknW." /></figure><p>I would have to say a quote from someone I am growing to appreciate more and more, Thierry Carrez, sums up my key takeaway:</p><blockquote>Open source communities just want to collaborate globally. World: please stop throwing obstacles and stupid borders at us</blockquote><p>With the OpenStack Summit establishing the clear message that OpenStack is about composable infrastructure and always has been despite what boxes, obstacles, and borders folks tried and still attempt to put around the community, for many years to come the event will thrive and be another place for the OSS community to galvanize and continue to thrive.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3de134f1586d" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[boston2017-infrastructure-for-ideas.md]]></title>
            <link>https://medium.com/@mrhillsman/boston2017-infrastructure-for-ideas-md-a8fe98fa640e?source=rss-be128643cc06------2</link>
            <guid isPermaLink="false">https://medium.com/p/a8fe98fa640e</guid>
            <category><![CDATA[cloud-computing]]></category>
            <category><![CDATA[openstack]]></category>
            <dc:creator><![CDATA[Melvin Hillsman]]></dc:creator>
            <pubDate>Wed, 10 May 2017 14:06:32 GMT</pubDate>
            <atom:updated>2017-05-10T23:10:34.233Z</atom:updated>
            <content:encoded><![CDATA[<h3>OpenStack is Infrastructure for Ideas!</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*knu3ZtPuu1xVGwcpf4qR-Q.jpeg" /><figcaption>Image obtained from goo.gl/OK39EN</figcaption></figure><blockquote>“We need to make sure we are not looking at good enough…we are going to build things for beyond tomorrow” — Edward Snowden</blockquote><h4>OpenStack Continues to THRIVE</h4><p>This is obvious from tools like the user survey assessing environment usage and stackalytics around coding reflecting increases both in number and people. Additional proof of this despite the #openstackisdead campaign(s) of mid to late 2016 is the OpenSource Days activities bringing not only communities we generally all participate in and care about across opensource but also collaboration, communication, and concern for each other as we push towards tomorrow.</p><h4>OpenStack Continues to MATURE</h4><p>Across the first two days of the OpenStack Summit companies with global footprints in one or more industries like GE, Deutsche Telekom, Huawei, and IBM to name a few, have provided insights into their journey to OpenStack for PUBLIC and PRIVATE clouds.</p><h4>OpenStack Continues to ENABLE</h4><p>OpenStack is not just for companies that make it on the list of Fortune’s 100, 500, or X hundred rankings. One of the key themes across the keynotes of day one and day two I heard was around how OpenStack continues to enable. OpenStack is enabling companies like GE to gain valuable insight from the beginning of their cloud journey or as one GE architect put it, “This platform must be made of awesome”.</p><p>Another story of enablement centered around edge computing. Verizon provided a demo of their platform built using OpenStack providing Network-as-a-Service. Beth Cohen talked about how OpenStack enabled them based on five key factors.</p><ol><li>Unified management across the network</li><li>Ability to move workloads between edge and core</li><li>Seamless customer experience</li><li>Flexible toolset delivers new services quickly</li><li>Vendor release coordination</li></ol><p>At the beginning of this article there is a quote from Edward Snowden who was interviewed live on-stage by Mark Collier and it really hit home for me. Honestly, a lot of thoughts I had been tossing around that I did not know would be touched on at multiple times throughout the keynotes really made his quote stick even more and the title of this post sums it up.</p><p>What is the greatest thing so far about OpenStack Summit Boston is the collaboration, communication, and concern that happens is now available for others get to experience it. If you go back and look at the keynote from the 2012 summit in San Diego, you will see that this was always the desire of the community.</p><p>Our journey as a community is a marathon not a sprint and we have rounded yet another corner in the world of opensource. The future is full of possibilities and OpenStack indeed is a key component of our ecosystem and I am an excited about the tomorrow we will see as we work to build beyond it.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a8fe98fa640e" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>