<?xml version="1.0" encoding="utf-8"?>
<?xml-stylesheet type="text/xsl" href="../assets/xml/rss.xsl" media="all"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>adam.yml (Posts about SCaLE 15x)</title><link>https://maxamillion.sh/</link><description></description><atom:link href="https://maxamillion.sh/categories/scale-15x.xml" rel="self" type="application/rss+xml"></atom:link><language>en</language><lastBuildDate>Tue, 07 Apr 2026 05:02:31 GMT</lastBuildDate><generator>Nikola (getnikola.com)</generator><docs>http://blogs.law.harvard.edu/tech/rss</docs><item><title>SCaLE 15x</title><link>https://maxamillion.sh/blog/scale-15x/</link><dc:creator>Adam John Miller</dc:creator><description>&lt;section id="scale-15x"&gt;
&lt;h2&gt;SCaLE 15x&lt;/h2&gt;
&lt;p&gt;This year was the 15th Annual &lt;a class="reference external" href="https://www.socallinuxexpo.org"&gt;SCaLE&lt;/a&gt; (Southern California Linux Expo) event
where I was fortunate enough to both attend and speak at. While this is the 15th
year of the, now very well known, conference; it was in fact my first time to
attend. I spent majority of my time floating between working the &lt;a class="reference external" href="https://getfedora.org/"&gt;Fedora&lt;/a&gt;, &lt;a class="reference external" href="https://www.redhat.com"&gt;Red
Hat&lt;/a&gt;, and &lt;a class="reference external" href="https://www.openshift.com/"&gt;OpenShift&lt;/a&gt; booths there in the Expo Hall. I had originally planned
to spend more time at the &lt;a class="reference external" href="https://getfedora.org/"&gt;Fedora&lt;/a&gt; booth than I did, but the &lt;a class="reference external" href="https://www.openshift.com/"&gt;OpenShift&lt;/a&gt; crew
ended up short staffed because of unexpected travel issues of some of their team
members so I filled in the best I could. As expected the interest in containers
is at full tilt and people were very interested to see what is going on with
&lt;a class="reference external" href="https://www.openshift.com/"&gt;OpenShift&lt;/a&gt; as it is a &lt;a class="reference external" href="https://kubernetes.io/"&gt;Kubernetes&lt;/a&gt; distribution with advanced features beyond
core &lt;a class="reference external" href="https://kubernetes.io/"&gt;Kubernetes&lt;/a&gt;, and Kubernetes is easily the &lt;a class="reference external" href="https://cdn.thenewstack.io/media/2016/06/Chart_Top-Orchestration-Products-Based-on-Expected-Usage-Within-Next-Year.png"&gt;most popular container
orchestration platform&lt;/a&gt; around right now. The &lt;a class="reference external" href="https://www.projectatomic.io/"&gt;Project Atomic&lt;/a&gt; Community
manager, &lt;a class="reference external" href="https://twitter.com/fuzzychef"&gt;Josh Berkus&lt;/a&gt; was kind enough to lend his Sub-Atomic Cluster
(Described in this two-part blog series: &lt;a class="reference external" href="https://www.projectatomic.io/blog/2016/06/micro-cluster-part-1/"&gt;Part 1&lt;/a&gt;, &lt;cite&gt;Part 2&lt;/cite&gt;) to the booth
efforts and that made for some very engaging demos of what OpenShift can
accomplish (even though the conference network left something to be desired, but
this is nothing new). Over all I think we were able to provide event goers
a solid booth destination in their Expo Hall travels.&lt;/p&gt;
&lt;p&gt;Every conference I go to, I notice there's a specific "crowd profile" in terms
of what motivates the participants to attend the conference, what their
interests are, etc. Often times these are going to be things like hobbyist,
enthusiast, professional/commercial, developer, sysadmin/ops, DevOps
practitioners, and potentially (and often) some mixture of those categories.
This particular conference was a really solid representation of community
focused people and hobbyists which is always a cool crowd because everyone is
genuinely interested and enthusiastic about the technologies being represented
there. However, from a personal note, something I found rather interesting was
the number of people who came by the &lt;a class="reference external" href="https://www.redhat.com"&gt;Red Hat&lt;/a&gt; booth that had never heard of
the company. This isn't entirely a new phenomenon depending on the "crowd
profile" but it's definitely the first time I've seen such a proliferation of it
at a specifically &lt;strong&gt;Linux&lt;/strong&gt; conference. This is a weird change of pace for me as
for the longest time, Red Hat was a name synonymous with Linux. However, as the
company has focused more on the Enterprise with &lt;a class="reference external" href="https://www.redhat.com/en/technologies/linux-platforms/enterprise-linux"&gt;RHEL&lt;/a&gt;, the community focused
&lt;a class="reference external" href="https://getfedora.org/"&gt;Fedora&lt;/a&gt; and &lt;a class="reference external" href="https://centos.org/"&gt;CentOS&lt;/a&gt; have filled in the void for the community user base and
this was a primarily community focused event. Beyond that though, the number of
people who had no idea that &lt;a class="reference external" href="https://www.redhat.com"&gt;Red Hat&lt;/a&gt; is a major sponsor of and contributor to
&lt;a class="reference external" href="https://getfedora.org/"&gt;Fedora&lt;/a&gt; was surprising to me.&lt;/p&gt;
&lt;p&gt;There are two primary reasons I think lead this situation. First, Linux is so
high quality and pervasive these days that the percentage of people who used to
get off in the weeds early and often with technical issues is fewer and far
between. These systems level technology dives would quickly lead to someone
becoming well versed in topics of their distribution and the reality of
relationships between different entities (such as &lt;a class="reference external" href="https://www.redhat.com"&gt;Red Hat&lt;/a&gt; and &lt;a class="reference external" href="https://getfedora.org/"&gt;Fedora&lt;/a&gt;)
within the scope of the community. This is no longer the case, Linux is so easy
to use and so commonplace that most people don't need (and in many cases don't
want) to dig into the nuts and bolts to the point of having a fundamental
understanding about the resulting project that produces the Distribution they
are using. I think this is great in a lot of ways, I think it's a standing
ovation to the fact that Linux has "made it" and that we collectively in the
upstream communities are providing quality software that attracts users of all
kinds, technical or otherwise. The Second reason I think lead to this is that it
poses an interesting problem in the world of marketing for both &lt;a class="reference external" href="https://getfedora.org/"&gt;Fedora&lt;/a&gt; as an
upstream and &lt;a class="reference external" href="https://www.redhat.com"&gt;Red Hat&lt;/a&gt; as a company to properly communicate to users and
potential users things that are interesting to them since Linux itself isn't
inherently interesting to as wide of an audience as it once was due to popular
tech trends shifting away from the system itself but instead to things you can
run on top of the system (and recently in containers). Now, &lt;a class="reference external" href="https://www.redhat.com"&gt;Red Hat&lt;/a&gt; has done
a great job of making that message clear to it's customer base with material
that covers the entire &lt;a class="reference external" href="https://www.redhat.com/en/technologies"&gt;Red Hat Technology Portfolio&lt;/a&gt;. I also think that
&lt;a class="reference external" href="https://getfedora.org/"&gt;Fedora&lt;/a&gt; in recent years has been doing a really good job of showing off
various features of each Fedora Edition: &lt;a class="reference external" href="https://getfedora.org/en/workstation/"&gt;Workstation&lt;/a&gt;, &lt;a class="reference external" href="https://getfedora.org/en/server/"&gt;Server&lt;/a&gt;, &lt;a class="reference external" href="https://getfedora.org/en/atomic/"&gt;Atomic&lt;/a&gt;
which highlights features beyond just the core distribution that are tailor made
to specific users and potential users. We just need to continue to show up to
user groups, MeetUps, and conferences with good representation to help spread
the word. On that note, a massive thanks to the amazing &lt;a class="reference external" href="https://fedoraproject.org/wiki/Ambassadors"&gt;Fedora Ambassadors&lt;/a&gt;.
I'd also like to find a good way to get the message out to more users of various
online and programming communities, something similar to &lt;a class="reference external" href="https://fedoralovespython.org/"&gt;Fedora Loves Python&lt;/a&gt;
but for various &lt;a class="reference external" href="https://fedoraproject.org/wiki/Category:SIGs"&gt;Special Interest Groups&lt;/a&gt; within Fedora. Just food for thought.&lt;/p&gt;
&lt;p&gt;Over all I think we're doing good work and doing a good job spreading the word,
it's just interesting to see how trends in technology change, how the landscape
changes, and trying to identify how we as a community need to adapt. Kudos to
the whole &lt;a class="reference external" href="http://fedoracommunity.org/northam"&gt;Fedora Community&lt;/a&gt;!&lt;/p&gt;
&lt;p&gt;I also had a chance to make some new friends from &lt;a class="reference external" href="https://www.gnome.org/"&gt;GNOME&lt;/a&gt;, &lt;a class="reference external" href="https://endlessos.com/"&gt;EndlessOS&lt;/a&gt;,
&lt;a class="reference external" href="https://www.opensuse.org/"&gt;OpenSUSE&lt;/a&gt;, &lt;a class="reference external" href="https://www.debian.org/"&gt;debian&lt;/a&gt;, &lt;a class="reference external" href="https://opensource.com/"&gt;opensource.com&lt;/a&gt; and &lt;a class="reference external" href="https://linuxacademy.com/"&gt;LinuxAcademy&lt;/a&gt; as a side effect
of spending so much time in the Expo Hall. In typical Linux Community fashion,
everyone was extremely friendly and I had a great time. :)&lt;/p&gt;
&lt;p&gt;I spent most of my time working the booths, but I was able to make it to
a couple sessions while the Expo Hall was closed. I've taken some notes on those
below.&lt;/p&gt;
&lt;section id="kubernetes-101"&gt;
&lt;h3&gt;Kubernetes 101&lt;/h3&gt;
&lt;p&gt;&lt;a class="reference external" href="https://www.projectatomic.io/"&gt;Project Atomic&lt;/a&gt;'s very own &lt;a class="reference external" href="https://twitter.com/fuzzychef"&gt;Josh Berkus&lt;/a&gt; did a wonderful overview of the
&lt;a class="reference external" href="https://kubernetes.io/"&gt;Kubernetes&lt;/a&gt; architecture, walking the audience both through the various
components of &lt;a class="reference external" href="https://kubernetes.io/"&gt;Kubernetes&lt;/a&gt; as well as how you would take a traditional
application that would be deployed as a "monolith" all on a since physical or
virtual machine with only vertical scaling into a multi-node orchestrated
deployment of containerized services.&lt;/p&gt;
&lt;p&gt;This talk was accompanied by multiple live demos using &lt;a class="reference external" href="https://github.com/kubernetes/minikube"&gt;minikube&lt;/a&gt; (with a tip
of the hat to &lt;a class="reference external" href="https://www.openshift.org/minishift/"&gt;minishift&lt;/a&gt;) in order to show how the concepts presented during
the talk map to real world deployment and configuration within the cluster.&lt;/p&gt;
&lt;/section&gt;
&lt;section id="patterns-and-anti-patterns-in-docker-image-lifecycle"&gt;
&lt;h3&gt;Patterns and Anti-Patterns in Docker Image Lifecycle&lt;/h3&gt;
&lt;p&gt;Speaker from &lt;a class="reference external" href="https://www.jfrog.com/"&gt;JFrog&lt;/a&gt; talking about &lt;a class="reference external" href="https://github.com/docker/docker/"&gt;Docker&lt;/a&gt; image lifecycle management, using
&lt;a class="reference external" href="https://www.jfrog.com/artifactory/"&gt;Artifactory&lt;/a&gt; as an example component.&lt;/p&gt;
&lt;p&gt;The presentation begins with a poll of the room about who's using Docker in dev
vs production. A primary point of concern is the concept of "trust" to know if
there's enough integrity into the process and the images that you pull down to
build your application or CI pipeline on top of.&lt;/p&gt;
&lt;p&gt;"There is no platform without ecosystem" - Solomon Hykes (CEO Docker Inc.)&lt;/p&gt;
&lt;p&gt;Do we have an existing pattern? Do we need to adapt it? CI/CD pipelines? (These
are old news, this has been done for years)&lt;/p&gt;
&lt;p&gt;The speaker mentioned a concept call the "The Promotion Pyramid" which could
basically be turned on it's side and the layers of the pyramid by changed to
boxes with arrows between them and it looks just like a production pipeline
diagram.&lt;/p&gt;
&lt;p&gt;Onward to Dockerfiles! The Dockerfile is extremely powerful, the problem is that
it's a hammer and everything now looks like nails. Fast and cheap builds are not
the way to go.&lt;/p&gt;
&lt;pre class="literal-block"&gt;FROM fedora

RUN dnf install -y software-properties-common python
RUN dnf install -y nodejs

RUN mkdir /var/www

ADD app.js /var/www/app.js

CMD ["/usr/bin/node", "/var/www/app.js"]&lt;/pre&gt;
&lt;p&gt;The problem with this is that there's no versioning on anything so each build
may or may not produce the same thing because each &lt;code class="docutils literal"&gt;dnf&lt;/code&gt; command could
install a different version of each component. You can use a SHA sum to refer to
the image version but these are not human readable so it's kind of pointless or
maintain your own base image.&lt;/p&gt;
&lt;p&gt;Pattern to follow to fix this is to promote immutable binary files (&lt;a class="reference external" href="https://martinfowler.com/bliki/ImmutableServer.html"&gt;Martin
Fowler Immutable Server&lt;/a&gt;).&lt;/p&gt;
&lt;p&gt;The promotion patterns between registries and repos it basically the only real
way because the only way to "version" docker images is with tags and the tag has
no concept of version numbers and you can only run one registry per host unless
you use VirtualHosts and many daemons mapped to ports.&lt;/p&gt;
&lt;p&gt;As a side note, the "promotion pipeline" is effectively the exact structure that
&lt;a class="reference external" href="https://docs.pagure.org/releng/layered_image_build_service.html"&gt;Fedora Containers&lt;/a&gt; follow.&lt;/p&gt;
&lt;/section&gt;
&lt;section id="fedora-work-session-and-meetup"&gt;
&lt;h3&gt;Fedora Work Session and Meetup&lt;/h3&gt;
&lt;p&gt;Open session to:&lt;/p&gt;
&lt;ul class="simple"&gt;
&lt;li&gt;&lt;p&gt;Work on development&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Say Hello&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Meet others&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Ask questions about challenges you're facing&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Share knowledge&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Find out how to help&lt;/p&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;This was a really fun grass roots "Birds of a Feather" style session where
everyone in the room made a big circle, went around and introduced themselves,
and briefly talked about what they are using &lt;a class="reference external" href="https://getfedora.org/"&gt;Fedora&lt;/a&gt; for. This spanned from
Workstations and Cloud all the way to use with ARM boards in small embedded
devices that are deployed out in the field. I had a great time learning what
everyone was up to with Fedora and I want to thank &lt;a class="reference external" href="https://fedoraproject.org/wiki/User:Lajuggler"&gt;Perry Rivera&lt;/a&gt; for setting
it up and hosting. Perry was also kind enough to be taking notes and feedback
based on everything that was discussed.&lt;/p&gt;
&lt;/section&gt;
&lt;/section&gt;
&lt;section id="closing-time"&gt;
&lt;h2&gt;Closing time&lt;/h2&gt;
&lt;p&gt;I had a wonderful time (aside from not feeling 100% - I came down with a sinus
infection the day before flying out to SCaLE), the event was fantastic
and I really hope I get the opportunity to go back next year.&lt;/p&gt;
&lt;p&gt;Until next time...&lt;/p&gt;
&lt;/section&gt;</description><category>SCaLE 15x</category><guid>https://maxamillion.sh/blog/scale-15x/</guid><pubDate>Wed, 08 Mar 2017 21:25:15 GMT</pubDate></item></channel></rss>