<?xml version="1.0" encoding="utf-8" standalone="yes"?><?xml-stylesheet href="/feed_style.xsl" type="text/xsl"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:media="https://www.rssboard.org/media-rss">
  <channel>
    <title>Hugo and GitLab Pages on Eva Winterschon</title>
    <link>https://winterschon.gitlab.io/en/</link>
    <description>Recent content in Hugo and GitLab Pages on Eva Winterschon</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en</language>
    <copyright>Some copyright notice - [my license](https://example.com/license)</copyright>
    <lastBuildDate>Thu, 23 Jul 2026 16:07:54 +0000</lastBuildDate><atom:link href="https://winterschon.gitlab.io/en/index.xml" rel="self" type="application/rss+xml" /><icon>https://winterschon.gitlab.io/logo.svg</icon>
    
    
    <item>
      <title>Purpose</title>
      <link>https://winterschon.gitlab.io/en/purpose/</link>
      <pubDate>Sat, 14 Jun 2025 04:28:22 +0000</pubDate>
      
      <guid>https://winterschon.gitlab.io/en/purpose/</guid>
      <description><![CDATA[<p>There is no purpose but that which we make for ourselves*. Without getting into the deeper implications of <em>&ldquo;purpose and intention&rdquo;</em>, a simple question which asks <em>&ldquo;why does this site exist?&rdquo;</em> may be answered similarly.</p>
<p>Prose exists so that I do not forget the beautiful moments, memories, and meandering thoughts. Its intention is to facilitate a greater degree of accuracy in referential recall, for my own purposes, and to share one person&rsquo;s experiences via photos and writings about where the many actions took me along the way.</p>
<h3 id="still-though-why">Still though, Why?</h3>
<p>Because of the coma, and the life-support machines, and everything involved with rebuilding cognition after being brought back to life. There are years of events which may never be recalled, whole sections of life which I&rsquo;ll never fully remember having lost. Perhaps it&rsquo;s better that way, but I will never know in either case, and that&rsquo;s okay.</p>
<p>Priorities shifted, and now the freight train never stops. Sleep is difficult, rest can be fleeting, both bringing a challenging reality to the oft&rsquo; heard phrase, <em>&ldquo;I&rsquo;ll sleep when I&rsquo;m dead.&rdquo;</em> Most people don&rsquo;t know how that feels, and I do not think they would use the term so lightly if so.</p>
<p>I never want to forget this beautiful realm, its struggles and trials, <em>kuschelig-weich süße küsse</em>, the hugs and naps – and occasionally the complexities of corporate decision-trees too. This everything of being, in its infinitesimal grandiosity and minutia of glory, graced from Hashem or Lilith or the forever over-watching mountain gods too, perhaps?</p>
<h3 id="on-spirituality-or-nothingness">On Spirituality or Nothingness</h3>
<p>My sense of spirituality has no names and no demands of dogmatic mindlessness; it is this everything of every-day and every-time that I close my eyes to drift back into the nothingness of the Void. The nothingness of everything is always there, carrying me, calling for an eventual return, but not right now – give me one more day, one more adventure, one more embrace. Then, in-so-the interim of variable time, I may share them with you too.</p>
<h3 id="time-and-timelessness">Time and Timelessness</h3>
<p>So then, this site is in some ways a grasp on the finite experience of time. A catalogue of imagery and concepts and concerns and emotions which exist only for temporary purposefulness, or ultimately meaninglessness. I&rsquo;m not sure which, but here we are, and often times it&rsquo;s just for the simple enjoyment of writing. A game which my mind plays with grammatical phrases, of equations and variables made of linguistics, of inference driven convolutional intentionality from the <a href="https://qbi.uq.edu.au/brain/brain-anatomy/lobes-brain">frontal-temporal lobes</a> and <a href="https://en.wikipedia.org/wiki/Dopaminergic_pathways">dopaminergic pathways</a>.</p>
<p>Since waking up those many years ago, a commonality of mind has been to focus on the present as much as possible; an exercise in occasional futility combined with a mostly Zen aligned stateful detachment. Day-to-day involves a meditative awareness of the senses while distanced cognition-threads process a long-held buffer of <a href="https://en.wikipedia.org/wiki/Parasympathetic_nervous_system">Parasympathetic Nervous System</a> synapse firings, neurotransmitter floods and waves, accelerated <a href="https://en.wikipedia.org/wiki/Dopamine_transporter">DAT transport</a> queues.</p>
<hr>
<h2 id="from-the-void">From the Void</h2>
<p>From the void you awaken, into this body from which consciousness departed some lifetime ago. Inside the void all is null, an absence of existence, sensory nothingness, until the timelessness becomes a single photon of light. In an unknown span of time it expands, drawing consciousness back into the this shared realm of existence, back into the world of the living. From that void, an endless timeless realm where pain does not exist, the conscious mind <em>&ldquo;awakens&rdquo;</em>, and as it does the senses begin to scream in electrical amperage everywhere there is Aware.</p>
<p>The light expands and becomes the world, gaining contrast, and with that light appear shapes and structures without color. At first all is gray-scale, until slowly color dawns upon the senses, eventually distance and depth are concepts once-more, but there is no other sensory world. Scent, sound, touch, space and time, all remain back in the void.</p>
<h3 id="burning-searing-oxygen">Burning Searing Oxygen</h3>
<p>Emotions, that conceptual link between awareness based feedback loops and knowledge of experiences did not come back immediately, if only to say that there was one binding sensory flood of continuity: anger laced despair. When the conscious mind re-appeared sufficiently to respond to its awareness of circumstance, the first thing I noticed was the burning of oxygen in my lungs - fed by tubes from the respirator machine, controlled by computer at the bedside.</p>
<p>Next was the burning in my neck, where the tubes were routed into a stoma - not through my mouth or nose - rather than the second incision crudely sewn two inches higher in the tracheal zone. An EMT had to slice open my throat for respiration, and through one set of vocal chord nerves the scalpel went, an emergent surgery on the floor in the dark of night. Only later, at the ER/OR was the stoma incised, the vertically sliced tracheal chasm zig-zaggedly sewn. The nerves never healed, and so my voice is soft but often fails, worn out as the day progresses. One set of muscles doing the work of two, but often not sufficient for anything at all.</p>
<p>Over time the senses came alive, mostly to their former capacity, except for memory. With memory it comes in chunks, as though an array is rebuilding, scanning, but often finding nulls. Short term memory was gone, with the weeks prior to the coma almost entirely missing from recall. Over time, STM Consolidation - the process by which our brains receive sensory data and filter/sort/prioritize aspects and elements and concepts of time from short to medium-term, then assessing and contextualizing and cross-referencing these into long-term memory. That process has improved with specialized medication and meditation, though this is a neuroscience topic for another day.</p>
<h3 id="hyperalgesic-nociceptive-reaction-instinct">Hyperalgesic-Nociceptive Reaction Instinct</h3>
<p>In the earliest days of awakening, still horizontal in the ICU, as my head would nod-off in a morphine haze <em>(so much pain)</em>, the autonomic system would take over, and one or two hands would immediately race to attempt their forever game: trying to tear the hoses out of the stoma in my neck.</p>
<p>Surely, that did not go over well with the ICU staff, and eventually whenever my tired eyes would drift, a nurse would restrain my wrists to prevent the next autonomic attempt - those tubes <strong>HURT.</strong> Regardless, that type of physiological action was determined to be a neurologically positive sign which indicated that parts of the brain were coming back online for instinctual action <em>(reduce pain immediately, even if doing so unintentionally ends breathing machine hookup)</em>.</p>
<h3 id="the-knowledge-reset---via-reinforcement-learning">The Knowledge Reset - via Reinforcement Learning</h3>
<p>Of course, I couldn&rsquo;t speak with the hoses still connected through the port in my neck, and once they were eventually out I still couldn&rsquo;t speak. Either the brain didn&rsquo;t remember how to contact the muscles, or the nerves controlling the voice box wouldn&rsquo;t connect to the muscles - either due to pain or due to half of them being severed.</p>
<blockquote>
<p><em>Eventually I would relearn how to speak, through a long and painful process</em> over months, though it still fails on a near daily basis.</p>
</blockquote>
<p>Inquiring with a specialist four years later, even experimental options would not apply, as the severed vocal chords&rsquo; nerves were too distant to reconnect end to end. Perhaps one day that will be resolved; until then my voice is soft and sometimes no-op.</p>
<blockquote>
<p><strong>Walking</strong>, all <strong>gone</strong>.<br>
<strong>Dexterity</strong> by hand, also <strong>gone</strong>.<br>
<strong>Balance</strong>, certainly <strong>gone</strong>.</p>
</blockquote>
<p>The first time I was able to pull my legs over the side of the bed, while holding onto a nurse, the nanosecond either foot struck the ground, lightning surged upward — through the femur, spiraling along the thoracic spine, climbing into cervical vertebrae, and erupting through the cerebellum and corpus callosum, detonating across the cerebral cortex. There was no thought, no other sensation; existence narrowed to one unbearable truth: PAIN.</p>
<hr>
<h3 id="electrical-signaling">Electrical Signaling</h3>
<p>In medical research and case studies there is a distinct lack of detail from patient perspectives on the topic of this process: awakening the somatosensory network of the Central Nervous System after a flatlined coma, not a medically induced coma, and not a short term coma. The CNS is an electrical system foremost, followed by chemical messenger pathways, both interwoven in a complexity which science has yet to fully model or simulate.</p>
<p>Part of not being able to walk, or to hold things, to speak, was the sheer inability for my brain to process the electrical signals unmoderated, ungoverned; in short, the signals were shorting out the sensory and processing equipment. Without sufficient memory the simplest actions and abilities are devoid of action.</p>
<h3 id="healing-processes">Healing Processes</h3>
<p>Part of the physical healing process was one of intense and ongoing patience and more patience and endless patient patient patience and more of being both concurrently in what seemed to be an endless forever. I was not a patient child; this was my least tuned skill set, but it is now my most etched-in-stone capacity, though everyone surely has their limits.</p>
<p>Sense of smell was deemed the least critical, as determined by whatever engines were managing the recovery process. Light sensitivity never stopped being a problem, to which no doctor has had answers. All of these abilities, so often and so easily taken for granted by so many, they form the foundation - the core of a person&rsquo;s interactions with their world, and with those senses we define existence, what it means to be alive, what it means to engage with others, and by eventual extrapolation what it means to find and have purpose and meaning and definition and identity.</p>
<h3 id="referential-integrity">Referential Integrity</h3>
<p>The ability to confirm the integration of data into the whole - not only a unit as its unique entry - but with its reference to which all else maintains interrelated definitions; Referential Integrity is not solely a term from the database engineering world, it is a way to see how the brain shapes the Self, how it infers meaning minute by minute from the individual experience with relationships (comparative, contrasting) to the whole of the experience. Our brains are processing and defining and redefining all of our sensory inputs trillions of times per day, moving memory chunks around according to some grander-than-awareness algorithm which necessitates the conversion of short term events into long term storage for retrieval years or decades later. This fascinating biological computer is the most beautiful and capable equipment which our species has ever come across - and so gods help me if I ever take that for granted in any breath until my last. The void is not going anywhere, it&rsquo;s there always and forever, that much is knowable in my experience. So then, what purpose is there? The question has no definitive or singular notion to provide an answer; purpose is evolving and changing at all times, until there is nothing left.</p>
<hr>
<h2 id="finally-then">Finally then..</h2>
<p>So, philosophy of death and meaning and all of that.. in any case, Prose is a site for reflections upon a woven existence, one which has routinely provided awakenings into substantially altered facets of bicameral perceptions. These descriptions may not resonate with many, though this is not a site for mass consumption or awareness, and so that is okay.</p>
<p>In part, this site is an archive for those memories of fleeting years gone by, of present experiences which sooner than realized will forever and perpetually become that passing of time. Memories are a complex game, a puzzle of neurons - firing and transporting their transmitters to waiting receptors, remnants of the Central Nervous System&rsquo;s programming as it was trained, over time and years - consciously and otherwise.. but that&rsquo;s a story for another page, at another time.</p>
<p>[*] Unless there is no Free Will, in which case <a href="https://plato.stanford.edu/entries/determinism-causal/">Causal Determinism</a> implies that our consciousness correlates sentience as the role of an observer more so than one of pre-defined actional executor.</p>
]]></description>
      
    </item>
    
    
    
    <item>
      <title>Profiles</title>
      <link>https://winterschon.gitlab.io/en/profiles/</link>
      <pubDate>Fri, 13 Jun 2025 04:26:35 +0000</pubDate>
      
      <guid>https://winterschon.gitlab.io/en/profiles/</guid>
      <description><![CDATA[<h2 id="the-internet-age-of-days-long-passed">The Internet Age of Days Long Passed</h2>
<p>Yes, quite so, I miss the internet of the &rsquo;90s. The original idealism which prioritized being kind, helpful, welcoming, and infinitely curious about all things technical and complex and challenging.. instead we have mostly an internet where the experience has become &ldquo;garbage in - garbage out&rdquo;, and a wider array of assholerly than I expected to see three decade prior.</p>
<p>Nevertheless, we&rsquo;re no longer in that era, and so here are my modern life accounts from a variety of networks. Often one may find my username existing as <em><strong>&ldquo;winterschon&rdquo;</strong></em>, though my active presence wavers and wanes - periodic silence, staccato quipped sarcasm and critique, and the inevitable return to torrential expressions. Can we have more Gopher, XMPP, USENET, and maybe even IRC + OTR over the ISDN.</p>
<hr>
<h2 id="verification-and-validity-identity-defined">Verification and Validity, Identity Defined</h2>
<p>Generally speaking, if you don&rsquo;t see a profile listed here, then it&rsquo;s probably not a real account of my own. Do not engage and do not inquire to the unknown account - it only feeds the trolls and makes everything worse.</p>
<blockquote>
<p><strong>Ignore the Impersonators, Stalkers, Liars, and the Jüdenhasser Pseudo-Activists</strong></p>
</blockquote>
<p>Specifically, Twitter/X have the most egregious examples <em>(which I am not back-linking), and of course their support team refuses to take those shitheel accounts down)</em>. If in doubt, please contact me on one of the networks below.</p>
<h3 id="can-i-send-you-an-encrypted-email-instead">Can I send you an encrypted email instead?</h3>
<p>Yes, and here is my PGP / GPG key from the MIT Keyserver:</p>
<ul>
<li><a href="https://keys.openpgp.org/vks/v1/by-fingerprint/A3E24F7A3AFE90AAC9DDD82807769C89CD9AD67C">Personal GPG PubKey (A3E24F7A)</a></li>
</ul>
<hr>
<h2 id="the-many-names-of-who-are-you">The Many Names of &lsquo;Who Are You&rsquo;?</h2>
<p>Some people know me by one or two or four different names. I didn&rsquo;t choose this life, so what else is there to say? People get married, divorced, stalked, adopted, disowned, disavowed, etc.. some people go into witness protection programs, some do not. Some get tired of doing so, and some must have online presence for their career - and for some there is simply no other choice.</p>
<h3 id="where-is-madeline">Where is Madeline?</h3>
<p>That&rsquo;s my middle name. If you know me, likely you already know this, and if you know me very well, then you know that you know that you know that I know that you know this already. So double check your double-8, five-by-five, it&rsquo;s too long passed and now&rsquo;s TTGTFG - the endless slog, the Long Slow Distance, bekons just one more belay from the great beyond.</p>
<h3 id="where-is-annaliese">Where is Annaliese**?**</h3>
<p>If you know me extra-more, from the sandstone expanses of Monument Valley, the Canyonlands, all of those falls on El Cap, the backcountry avalances we unstuck-ourselves from, to the summits of Sierra 14&rsquo;ers.. then you may know my <em>&ldquo;what&rsquo;s your wall name?&rdquo;</em>, or perhaps from the portaledges and frozen bivys and smashed scorpions carried-off in your stupid empty tequilla bottle <em>(&ldquo;no glass on the wall, asssssshoooooleeeee!&rdquo;)&hellip;</em> then Annaliese and Anja say hallo and hola and shalom from <em><strong>above and beyond the great so-long</strong></em>. 👋🌄💝</p>
<hr>
<h2 id="industry">Industry</h2>
<ul>
<li><strong>Consulting Services</strong>: <a href="https://consulting.winterschon.com">consulting.winterschon.com</a></li>
<li><strong>Ai Storage/Infra R&amp;D:</strong> <a href="https://yukon.systems">yukon.systems</a></li>
</ul>
<h2 id="networks">Networks</h2>
<ul>
<li><strong>Mastodon (<strong>bridge</strong>)</strong>:@eva@prose.winterschon.com</li>
<li><strong>LinkedIn (<strong>new-acct</strong>)</strong>: <a href="https://linkedin.com/in/eva-winterschon">linkedin.com/in/eva-winterschon</a></li>
<li><strong>SubStack</strong>: <a href="https://substack.com/@winterschon">substack.com/@winterschon</a></li>
<li><strong>Instagram</strong>: <a href="https://www.instagram.com/winterschon/">instagram.com/winterschon</a></li>
</ul>
<h2 id="asynchronous-comms">Asynchronous Comms</h2>
<ul>
<li><strong>Matrix</strong>: <a href="https://matrix.to/#/@winterschon:matrix.org">@winterschon:matrix.org</a></li>
<li><strong>Zoom</strong>: <a href="https://zoom.us/launch/chat?src=direct_chat_link&amp;email=eva@winterschon.com">eva @\ winterschon.com</a></li>
<li><strong>Teams</strong>: <a href="https://teams.microsoft.com/l/chat/0/0?users=eva@winterschon.com">eva @\ winterschon.com</a></li>
</ul>
<h2 id="codes-and-repos">Codes and Repos</h2>
<ul>
<li><strong>GitHub (personal)</strong>: <a href="https://github.com/em-winterschon">github.com/em-winterschon</a></li>
<li><strong>GitHub (startup)</strong>: <a href="https://github.com/yukon-systems">github.com/yukon-systems</a></li>
<li><strong>GitLab</strong>: <a href="https://gitlab.com/winternull">gitlab.com/winternull</a></li>
<li><strong>CodeBerg (self)</strong>: <a href="https://codeberg.org/winterschon">codeberg.org/winterschon</a></li>
<li><strong>CodeBerg (proj)</strong>: <a href="https://codeberg.org/rfc1918">codeberg.org/rfc1918</a></li>
<li><strong>CodeBerg (proj)</strong>: <a href="https://codeberg.org/yukon-systems">codeberg.org/yukon-systems</a></li>
</ul>
<h2 id="dots-of-inconsequence">Dots of (in)Consequence</h2>
<p>Most engineers who come from a <a href="https://www.opengroup.org/membership/forums/platform/unix">UNIX background</a>, and maybe the newer generations who did not grow up using <a href="https://en.wikipedia.org/wiki/Single_UNIX_Specification">literal UNIX®</a> [2], tend to travel their years with at least one personal repo for their range of &lsquo;dot files&rsquo; - configurations for text editors, terminals, terminal emulators, shell configs, and so forth. Maybe that repo started out using UNIX&rsquo;s <a href="https://en.wikipedia.org/wiki/Source_Code_Control_System">SCCS</a>, or the 90s winrar <a href="https://en.wikipedia.org/wiki/Concurrent_Versions_System">CVS</a>, perhaps <a href="https://en.wikipedia.org/wiki/Revision_Control_System">RCS</a>, then <a href="https://en.wikipedia.org/wiki/Subversion_(software)">SVN</a> or <a href="https://en.wikipedia.org/wiki/Mercurial_(software)">Mercurial</a> or <a href="https://en.wikipedia.org/wiki/Fossil_(software)">Fossil</a>, a big-check jaunt with <a href="https://en.wikipedia.org/wiki/Perforce#P4">Perforce</a>, forced to use <a href="https://en.wikipedia.org/wiki/Git">Git</a> (it&rsquo;s not great! quick, back to Perforce P4)!</p>
<p>Well you get the point, there are many ways to deal with challenges wrought by engineering&rsquo;s evolving needs for multiple concurrent and distributed instances of source code control management. I&rsquo;ve used all of the ones listed plus a handful of others, and while Git is less headache than CVS and SVN, it&rsquo;s from the mind of a self-proclaimed dictator for life, and I don&rsquo;t want to use it - but the industry demands ecosystem compatibility. So, the usual bitching aside, here&rsquo;s my current dot-files repo.</p>
<ul>
<li><strong>Dot-Files</strong>: <a href="https://codeberg.org/winterschon/dot-files">codeberg.org/winterschon/dot-files</a></li>
<li><strong>Dot-Blumenkrieg</strong> [3]: <a href="https://codeberg.org/rfc1918/dotfiles-blumenkrieg">codeberg.org/rfc1918/dotfiles-blumenkrieg</a></li>
</ul>
<h2 id="technical-domains">Technical Domains</h2>
<ul>
<li><strong>Hugging Face</strong>: <a href="https://huggingface.co/winterschon">huggingface.co/winterschon</a></li>
</ul>
<hr>
<h2 id="reference-points">Reference Points</h2>
<ul>
<li>[*] If so, please message me via a valid profile from this page and let me know - as there exist impostors who&rsquo;ve stolen my personal photos, professional likeness, and should be dealt with accordingly.</li>
<li>[2] &ldquo;The UNIX® trademark is owned by The Open Group, an industry standards consortium, which acquired it from Novell in 1993. It is used to certify that operating systems comply with the Single UNIX Specification <em>{&ldquo;SUS, that is suss..&rdquo;}</em>. The brand separates the trademark from any single company&rsquo;s code, allowing multiple, independent implementations to be certified.&rdquo;</li>
<li>[3] Blumenkrieg translates to &ldquo;Flower War&rdquo;, and is mostly an inside joke about the <a href="https://en.wikipedia.org/wiki/Anschluss">near-immediate capitulation of Austria</a> during the inevitable rearmament of the Kaiser&rsquo;s German Empire as it evolved into the &ldquo;Thousand Year Reich&rdquo; which lasted about six. What kind of Jew isn&rsquo;t capable of laughing at the ease by which the world looked on as my lineage and so many others&rsquo; were whole-sale slaughtered and exterminated at <a href="https://en.wikipedia.org/wiki/Mauthausen_concentration_camp">Mauthausen</a>, condeming the part of my ancestral lineage to a brutal and inescapably horrific death - who had re-located at the time in <a href="https://en.wikipedia.org/wiki/Passau">Passau</a> after escaping from <a href="https://jewisheritage.org/history-of-jews-in-belarus">Belarus pogroms</a>.They all died, except for the very few who strived forward and managed to escape through the frosted-frozen Alps during storms of mourning and endless searching.</li>
</ul>
]]></description>
      
    </item>
    
    
    
    <item>
      <title>The Lexicon</title>
      <link>https://winterschon.gitlab.io/en/lexicon/</link>
      <pubDate>Fri, 02 May 2025 14:12:00 +0000</pubDate>
      
      <guid>https://winterschon.gitlab.io/en/lexicon/</guid>
      <description><![CDATA[<p>A Lexicon, A Glossary, a Definitoon of Terms, and so on&hellip;</p>
<h3 id="systems-storage-networking">Systems, Storage, Networking</h3>
<p>The following list of terms is never complete. New concepts added and adapted over time, you know the routine. Some things change, some.. do not.. and so we have language to reconcile those shared terms and meanings to convey and communicate the substance and substrates of lexicographical context.</p>
<h4 id="acl-access-control-list">ACL (Access Control List)</h4>
<p>A list of permissions attached to an object (file/folder) specifying which users or system processes can access it and what operations are allowed. NFSv4 ACLs and Windows ACLs are two types (the former more POSIX-oriented, the latter more detailed). ACLs are often used as rules defining access permissions on an object (file/directory). In storage systems, ACLs specify which users or groups can read, write, or execute a file. NFSv4 and Windows filesystems support ACLs beyond basic owner/group/mode bits.</p>
<h4 id="afm-active-file-management">AFM (Active File Management)</h4>
<p>A feature of IBM Spectrum Scale that allows caching and sync of data between clusters (for multi-site or hierarchical storage).</p>
<h4 id="all-flash">All-Flash</h4>
<p>Refers to storage systems that use all flash memory (SSD/NVMe) as opposed to spinning hard disks. Provides much higher IOPS and throughput, beneficial for HPC and low-latency needs.</p>
<h4 id="csi-container-storage-interface">CSI (Container Storage Interface)</h4>
<p>Not explicitly covered above, but contextually, CSI drivers allow these storage systems to integrate with container orchestration (e.g., Kubernetes) for dynamic provisioning.</p>
<h4 id="common-criteria-niap">Common Criteria (NIAP)</h4>
<p>A framework (with Evaluation Assurance Levels, EAL) to certify IT products’ security. NIAP is U.S.’s National Information Assurance Partnership. e.g., an EAL2 certification might be required for government use of a storage device.</p>
<h4 id="deduplication--compression">Deduplication &amp; Compression</h4>
<p>Data reduction techniques. Dedup finds identical blocks and stores one copy, saving space. Compression algorithmically reduces data size. Effective in reducing cost per logical stored TB, especially on systems like VAST, Pure.</p>
<h4 id="disaggregated-architecture">Disaggregated Architecture</h4>
<p>A design where compute (protocol processing) is separated from storage media enclosures. For example, VAST uses disaggregated compute nodes (CNodes) and storage boxes (DBOXes) connected via NVMeoF.</p>
<h4 id="erasure-coding">Erasure Coding</h4>
<p>A data protection method that breaks data into parts, encodes it with redundancy, and stores across multiple disks/nodes such that it can withstand some failures. Provides space efficiency vs full replicas. This method for spreading data and parity across drives/nodes also allows data recovery if some parts are lost. More space-efficient than mirroring, used by Scality, Ceph, etc.</p>
<h4 id="fips-140-2--140-3">FIPS 140-2 / 140-3</h4>
<p>U.S. government standards (older 140-2 and newer 140-3) for validating cryptographic modules. If a product is <em>FIPS 140-3 validated</em>, its encryption has been tested and approved for use in government systems (high assurance).</p>
<h4 id="gpfs-general-parallel-file-system">GPFS (General Parallel File System)</h4>
<p>The old name for IBM Spectrum Scale, a distributed filesystem known for high performance in HPC.</p>
<h4 id="gpudirect-storage">GPUDirect Storage</h4>
<p>A technology by NVIDIA that allows GPUs to directly perform IO to storage (bypassing CPU) if the storage and network support it. Reduces latency for GPU training data ingestion.</p>
<h4 id="iops-inputoutput-operations-per-second">IOPS (Input/Output Operations Per Second)</h4>
<p>A metric of how many read/write operations can be done in a second. Often used for measuring performance with small blocks (e.g., 4K). High IOPS with low latency indicates a system good for random small file workloads.</p>
<h4 id="iso-27001">ISO 27001</h4>
<p>An international standard for information security management. A product isn’t certified per se, but companies can certify their processes. Vendors adhering to 27001 ensure their product development and support follow security best practices.</p>
<h4 id="immutable-snapshot">Immutable Snapshot</h4>
<p>A point-in-time copy of data that cannot be altered or deleted until certain conditions are met (used for WORM compliance, ransomware protection).</p>
<h4 id="infiniband-aka-ib">InfiniBand (aka IB)</h4>
<p>Infiniband, a lovely networking protocol for low-latency RDMA enabled grid networks. Often used in clusters for HPC, OLTP, Ai/LLM Training and Inference, and Top-500 supercomputers. Often the leading protocol for high-speed networking, with encapsulation support for Ethernet (IPoIB) and others.</p>
<h4 id="kms-key-management-system">KMS (Key Management System)</h4>
<p>External system to manage encryption keys (e.g., HashiCorp Vault, Thales). Many storage products integrate with KMS via KMIP (Key Management Interoperability Protocol).</p>
<h4 id="latency-storage-context">Latency (storage context)</h4>
<p>The time it takes to complete an I/O operation (e.g., read or write). Low latency is critical for small random IOPS-heavy workloads (like database or AI metadata). Usually measured in milliseconds or microseconds.</p>
<h4 id="nfs-network-file-system">NFS (Network File System)</h4>
<p>A client-server file sharing protocol allowing file access over a network. Common in UNIX/Linux environments for shared storage. A distributed file system protocol allowing remote file access as if local. v3 is stateless, v4 adds state, ACLs, and optional pNFS for parallel access.</p>
<h4 id="nist-sp-800-53">NIST SP 800-53</h4>
<p>A catalog of security and privacy controls for federal information systems. Being “aligned to NIST 800-53” means the system supports many of the controls (like AC- access control, IA- identification &amp; authentication, etc).</p>
<h4 id="nvme-non-volatile-memory-express">NVMe (Non-Volatile Memory Express)</h4>
<p>A high-performance interface for SSDs (especially PCIe SSDs). NVMe drives have low latency and high throughput, extensively used in modern flash arrays.</p>
<h4 id="nvme-of-nvme-over-fabrics">NVMe-oF (NVMe over Fabrics)</h4>
<p>A protocol to use NVMe (fast flash interface) over a network fabric like Ethernet or InfiniBand, allowing remote NVMe drives to be accessed with near-local performance. Extends NVMe protocol over network fabrics (Ethernet, InfiniBand) so that remote NVMe devices can be accessed with similar efficiency to local NVMe.</p>
<h4 id="object-storage">Object Storage</h4>
<p>Storage that manages data as objects (with a unique key, metadata, and data), accessible via APIs like S3 or Swift rather than as a file hierarchy. Scalable to very large capacities and often easier to distribute than filesystems.</p>
<h4 id="posix">POSIX</h4>
<p>A family of standards for Unix-like operating systems. “POSIX file system” implies traditional semantics (hierarchical directories, byte-addressable files, etc.). HPC codes often assume POSIX compliance for file I/O. The standard for maintaining compatibility among operating systems. In file systems, POSIX compliance means supporting expected behaviors of a UNIX file system (permissions, atomic operations, etc.).</p>
<h4 id="qos-quality-of-service">QoS (Quality of Service)</h4>
<p>The ability to manage and guarantee certain performance levels (throughput or IOPS) to certain workloads or clients. For storage, some systems allow QoS limits or reservations per user/share.</p>
<h4 id="rbac-role-based-access-control">RBAC (Role-Based Access Control)</h4>
<p>Admin/users roles with certain permissions within a system’s management (e.g., admin, read-only admin, security officer roles). Many storage systems have RBAC in their management UI.</p>
<h4 id="rdma-remote-direct-memory-access">RDMA (Remote Direct Memory Access)</h4>
<p>Technology to directly transfer data between computers’ memory over network, bypassing CPU to reduce latency (used in InfiniBand, RoCE networks).</p>
<h4 id="roce-rdma-over-converged-ethernet">RoCE (RDMA over Converged Ethernet)</h4>
<p>A protocol to run RDMA over Ethernet networks by making them lossless (using priority flow control). Provides InfiniBand-like performance on Ethernet gear.</p>
<h4 id="s3-simple-storage-service-api">S3 (Simple Storage Service API)</h4>
<p>An object storage protocol (originally from AWS S3) for storing/retrieving whole objects (files) via HTTP. Many systems implement S3 for scale-out storage.</p>
<h4 id="smb-server-message-block">SMB (Server Message Block)</h4>
<p>A network file sharing protocol predominantly used by Windows. SMB3 supports encryption and signing for security. Also known as CIFS in older versions. Allows file and printer sharing in LAN.</p>
<h4 id="spc-1--spec-sfs">SPC-1 / SPEC SFS</h4>
<p>Industry benchmarks for storage. SPC-1 measures IOPS in a database-like workload. SPEC SFS measures NFS or SMB throughput and IOPS for different workloads (like SPEC SFS2014_swbuild, etc. for software build, VDA for video streaming).</p>
<h4 id="stig-security-technical-implementation-guide">STIG (Security Technical Implementation Guide)</h4>
<p>Guidelines used by U.S. DoD to secure systems (specific configurations to harden OS/applications).</p>
<h4 id="scale-out-vs-scale-up">Scale-Out vs Scale-Up</h4>
<p>Scale-out means increasing capacity/performance by adding more nodes (horizontal scaling), whereas scale-up means using bigger hardware (vertical scaling). Scale-out is generally preferred for very large systems (e.g., Spectrum Scale, Scality, Qumulo are scale-out; Oracle ZFS is scale-up).</p>
<h4 id="snapshot">Snapshot</h4>
<p>A read-only (sometimes read-write) copy of the filesystem state at a point in time. Useful for backups, quick recovery, or cloning datasets.</p>
<h4 id="throughputbandwidth">Throughput/Bandwidth</h4>
<p>The rate of data transfer, typically measured in GB/s for these systems. Important for large file reads/writes (like streaming datasets for training or writing simulation output).</p>
<h4 id="tiering-data-storage">Tiering, Data Storage</h4>
<p>Storage medium resource management design involving algorithmic methods for moving data between different storage performance types, with the goal of combining performance and capacity scaling into a model-able system with predictable KPIs.</p>
<p>OpenZFS and its ARC (Adaptive Replacement Cache) is the best example of tiered data structure design in OSS filesystems:</p>
<ul>
<li>L1-ARC == DRAM</li>
<li>L2-ARC <em>(Persistent Cache, Low-Latency)</em>
<ul>
<li>CXL, PMem, or NVDIMM</li>
<li>NVMe <em>(SLC NAND)</em></li>
</ul>
</li>
<li>3rd Tier <em>(Moderate Density, High-Write)</em>
<ul>
<li>NVMe <em>(MLC, TLC NAND)</em></li>
<li>Enterprise SSD <em>(SAS3, SAS4)</em></li>
<li>Workloads: Write-Centric / Mixed, High-TBW</li>
<li>Write-IO/Day Specs: DWPD &gt; 1.0</li>
</ul>
</li>
<li>4th Tier <em>(High-Density, Low-Write)</em>
<ul>
<li>NVMe <em>(QLC NAND)</em></li>
<li>Enterprise Dual-Head: <em>SAS3 / SAS4</em></li>
<li>Enterprise Dual-Actuator: E<em>XOS Mach.2</em></li>
<li>Enterprise Single-Head: SATA3 / <em>SAS3 / SAS4</em></li>
<li>Workloads: Read-Centric, Low-TBW</li>
<li>Write-IO/Day Specs: DWPD &lt; 1.0</li>
</ul>
</li>
</ul>
<h4 id="tiering-hsm">Tiering, HSM</h4>
<p>The &ldquo;Hierarchical Storage Management&rdquo; concept where data moves between tiers (hot data on DRAM (eg L1ARC on ZFS), cache-warm on SSD or NVMe, plus dual-head SAS for cold/large block storage, optionally with archive data on tape or object). Implemented in Spectrum Scale (as ILM policies), Weka (to object), etc.</p>
<h4 id="worm-write-once-read-many">WORM (Write Once Read Many)</h4>
<p>A storage feature where data, once written, cannot be altered or deleted for a defined retention period. Used for compliance (financial records, medical data archiving). Implemented often via immutable snapshots or object lock.</p>
<h4 id="zero-trust-architecture">Zero Trust Architecture</h4>
<p>A security model where no implicit trust is given; even internal components must authenticate/authorize. In storage, features like requiring tokens for mount, or rootless admin, align with zero trust principles (assume breach and minimize attack surface).</p>
<h4 id="write-benchmarking-mdtest--ior--fio">Write Benchmarking (mdtest / IOR / FIO)</h4>
<p>Common benchmarking tools for storage systems.</p>
<ul>
<li><em>Generally &ldquo;mdtest&rdquo; is used for</em> testing small file metadata I/O.</li>
<li><em>IOR</em> (Interleaved Or Random) simulates parallel I/O bandwidth.</li>
<li>FIO is a &ldquo;Flexible I/O&rdquo; simulator for common storage patterns.</li>
</ul>
<h4 id="pnfs-parallel-nfs">pNFS (Parallel NFS)</h4>
<p>An extension to NFSv4.1 that allows clients to directly access storage server nodes in parallel, rather than funneling all data through a single server.</p>
<p>pNFS improves throughput by eliminating bottleneck at a single NFS server. Part of NFSv4.1 that allows parallel data access from multiple storage servers to improve performance. Not widely implemented by all vendors, but conceptually eliminates single NFS server bottleneck.</p>
]]></description>
      
    </item>
    
    
    
    <item>
      <title>About</title>
      <link>https://winterschon.gitlab.io/en/about/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://winterschon.gitlab.io/en/about/</guid>
      <description><![CDATA[<figure><img src="/images/Victor_Hugo-Hunchback.jpg"><figcaption>
      <h4>Illustration from Victor Hugo et son temps (1881)</h4>
    </figcaption>
</figure>

<p><em>The Hunchback of Notre-Dame</em> (French: <em>Notre-Dame de Paris</em>) is a French Romantic/Gothic novel by Victor Hugo, published in 1831. The original French title refers to Notre Dame Cathedral, on which the story is centered. English translator Frederic Shoberl named the novel The Hunchback of Notre Dame in 1833 because at the time, Gothic novels were more popular than Romance novels in England. The story is set in Paris, France in the Late Middle Ages, during the reign of Louis XI.</p>
]]></description>
      
    </item>
    
    
  </channel>
</rss>
