<?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:foaf="http://xmlns.com/foaf/0.1/" xmlns:og="http://ogp.me/ns#" xmlns:rdfs="http://www.w3.org/2000/01/rdf-schema#" xmlns:schema="http://schema.org/" xmlns:sioc="http://rdfs.org/sioc/ns#" xmlns:sioct="http://rdfs.org/sioc/types#" xmlns:skos="http://www.w3.org/2004/02/skos/core#" xmlns:xsd="http://www.w3.org/2001/XMLSchema#" version="2.0" xml:base="https://www.linuxjournal.com/tag/edge">
  <channel>
    <title>Edge</title>
    <link>https://www.linuxjournal.com/tag/edge</link>
    <description/>
    <language>en</language>
    
    <item>
  <title>FOSS Project Spotlight: OpenNebula</title>
  <link>https://www.linuxjournal.com/content/foss-project-spotlight-opennebula</link>
  <description>  &lt;div data-history-node-id="1340649" class="layout layout--onecol"&gt;
    &lt;div class="layout__region layout__region--content"&gt;
      
            &lt;div class="field field--name-field-node-image field--type-image field--label-hidden field--item"&gt;  &lt;img src="https://www.linuxjournal.com/sites/default/files/nodeimage/story/12786c.png" width="427" height="200" alt="OpenNebula" typeof="foaf:Image" class="img-responsive" /&gt;&lt;/div&gt;
      
            &lt;div class="field field--name-node-author field--type-ds field--label-hidden field--item"&gt;by &lt;a title="View user profile." href="https://www.linuxjournal.com/users/michael-abdou" lang="" about="https://www.linuxjournal.com/users/michael-abdou" typeof="schema:Person" property="schema:name" datatype="" xml:lang=""&gt;Michael Abdou&lt;/a&gt;&lt;/div&gt;
      
            &lt;div class="field field--name-body field--type-text-with-summary field--label-hidden field--item"&gt;&lt;p&gt;&lt;em&gt;OpenNebula recently released its latest version, 5.8 "Edge", which now
offers pivotal capabilities to allow users to extend
their cloud infrastructure to the Edge easily and effectively.&lt;/em&gt;&lt;/p&gt;


&lt;h3&gt;
Why OpenNebula?&lt;/h3&gt;


&lt;p&gt;
For anyone looking for an open-source, enterprise solution to orchestrate
data-center virtualization and cloud management with ease and flexibility,
OpenNebula is a fine candidate that includes:
&lt;/p&gt;

&lt;ul&gt;&lt;li&gt;
On-demand provisioning of virtual data centers.&lt;/li&gt;

&lt;li&gt;
Features like capacity management, resource optimization, high
availability and business continuity.&lt;/li&gt;

&lt;li&gt;
The ability to create a multi-tenant cloud layer on various types of
newly built or existing infrastructure management solutions (such as VMware
vCenter).&lt;/li&gt;

&lt;li&gt;
The flexibility to create federated clouds across disparate geographies, as
well as hybrid cloud solutions integrating with public cloud providers like
AWS and Microsoft Azure.&lt;/li&gt;&lt;/ul&gt;&lt;p&gt;
And, it's lightweight, easy to install, infrastructure-agnostic and
thoroughly extensible.&lt;/p&gt;

&lt;img src="https://www.linuxjournal.com/sites/default/files/styles/max_650x650/public/u%5Buid%5D/12786f1.png" width="650" height="311" alt="""" class="image-max_650x650" /&gt;&lt;p&gt;&lt;em&gt;
Figure 1. High-Level Features&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;
&lt;a href="https://opennebula.org/key-features"&gt;Check here&lt;/a&gt; for a more detailed look at OpenNebula features.
&lt;/p&gt;

&lt;h3&gt;
New Features in 5.8 "Edge"&lt;/h3&gt;

&lt;p&gt;
With the current conversation shifting away from centralized cloud
infrastructure and refocusing toward bringing the computing power &lt;em&gt;closer to
the users&lt;/em&gt; in a concerted effort to reduce latency, OpenNebula's 5.8
"Edge" release is a direct response to the evolving computing and
infrastructure needs, and it offers fresh capabilities to extend one's cloud
functionality to the edge. Gaming companies, among others, who have been
using OpenNebula were of the first to push for these features (yet they
don't have the be the only ones to benefit from them).
&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;LXD Container Support&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;
In addition to supporting KVM hypervisors, as well as offering a cloud
management platform for VMware vCenter server components, OpenNebula now
provides native support for LXD containers as well. The virtues offered
by LXD container support allow users and organizations to benefit from:
&lt;/p&gt;

&lt;ul&gt;&lt;li&gt;
A smaller space footprint and smaller memory.
&lt;/li&gt;

&lt;li&gt;
Lack of virtualized hardware.&lt;/li&gt;

&lt;li&gt;
Faster workloads.&lt;/li&gt;

&lt;li&gt;
Faster deployment times.&lt;/li&gt;
&lt;/ul&gt;&lt;p&gt;
From a compatibility perspective, OpenNebula 5.8 and LXD provide the
following:
&lt;/p&gt;&lt;/div&gt;
      
            &lt;div class="field field--name-node-link field--type-ds field--label-hidden field--item"&gt;  &lt;a href="https://www.linuxjournal.com/content/foss-project-spotlight-opennebula" hreflang="en"&gt;Go to Full Article&lt;/a&gt;
&lt;/div&gt;
      
    &lt;/div&gt;
  &lt;/div&gt;

</description>
  <pubDate>Thu, 13 Jun 2019 12:00:00 +0000</pubDate>
    <dc:creator>Michael Abdou</dc:creator>
    <guid isPermaLink="false">1340649 at https://www.linuxjournal.com</guid>
    </item>
<item>
  <title>Linux's Broadening Foundation</title>
  <link>https://www.linuxjournal.com/content/linuxs-broadening-foundation</link>
  <description>  &lt;div data-history-node-id="1340604" class="layout layout--onecol"&gt;
    &lt;div class="layout__region layout__region--content"&gt;
      
            &lt;div class="field field--name-field-node-image field--type-image field--label-hidden field--item"&gt;  &lt;img src="https://www.linuxjournal.com/sites/default/files/nodeimage/story/2019_04_03_ons-san-jose_127_sm.jpg" width="800" height="489" alt="""" typeof="foaf:Image" class="img-responsive" /&gt;&lt;/div&gt;
      
            &lt;div class="field field--name-node-author field--type-ds field--label-hidden field--item"&gt;by &lt;a title="View user profile." href="https://www.linuxjournal.com/users/doc-searls" lang="" about="https://www.linuxjournal.com/users/doc-searls" typeof="schema:Person" property="schema:name" datatype="" xml:lang=""&gt;Doc Searls&lt;/a&gt;&lt;/div&gt;
      
            &lt;div class="field field--name-body field--type-text-with-summary field--label-hidden field--item"&gt;&lt;p&gt;&lt;em&gt;It's time to embrace 5G, starting with the Edge in our homes and hands.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;
In June 1997, &lt;a href="https://www.isen.com"&gt;David Isenberg&lt;/a&gt;, then of
AT&amp;T Labs Research, wrote a landmark
paper titled &lt;a href="https://www.isen.com/stupid.html"&gt;"Rise of the Stupid
Network"&lt;/a&gt;. You can still find it &lt;a href="http://www.hyperorg.com/misc/stupidnet.html"&gt;here&lt;/a&gt;. The
paper argued against phone companies' intent to make their own systems
smarter. He said the internet, which already was subsuming all the world's
phone and cable TV company networks, was succeeding not by being smart, but
by being stupid. By that, he meant the internet "was built for intelligence at
the end-user's device, not in the network".
&lt;/p&gt;

&lt;p&gt;
In a stupid network, he wrote, "the data is boss, bits are essentially free,
and there is no assumption that the data is of a single data rate or data
type." That approach worked because the internet's base protocol, TCP/IP, was
as general-purpose as can be. It supported every possible use by not caring
about any particular use or purpose. That meant it didn't care about data
rates or types, billing or other selfish concerns of the smaller specialized
networks it harnessed. Instead, the internet's only concern was connecting end
points for any of those end points' purposes, over any intermediary networks,
including all those specialized ones, without prejudice. That lack of
prejudice is what we later called neutrality.
&lt;/p&gt;

&lt;p&gt;
The academic term for the internet's content- and purpose-neutral design is
&lt;em&gt;end-to-end&lt;/em&gt;. That design was informed by &lt;a href="http://web.mit.edu/Saltzer/www/publications/endtoend/endtoend.pdf"&gt;"End-to-End Arguments in System
Design"&lt;/a&gt;, a paper by &lt;a href="https://en.wikipedia.org/wiki/Jerry_Saltzer"&gt;Jerome Saltzer&lt;/a&gt;, &lt;a href="https://en.wikipedia.org/wiki/David_P._Reed"&gt;David P. Reed&lt;/a&gt; and &lt;a href="https://en.wikipedia.org/wiki/David_D._Clark"&gt;David D. Clark&lt;/a&gt;,
published in 1980. In 2003, &lt;a href="http://weinberger.org"&gt;David
Weinberger&lt;/a&gt; and I later cited both papers in
&lt;a href="http://worldofends.com"&gt;"World of Ends: What the Internet Is and How to Stop Mistaking It for
Something Else"&lt;/a&gt;. In it, we &lt;a href="http://worldofends.com/#BM7"&gt;explained&lt;/a&gt;:
&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;
When &lt;a href="https://www.craigburton.com"&gt;Craig Burton&lt;/a&gt; &lt;a href="http://www.searls.com/burton_interview.html"&gt;describes&lt;/a&gt; the Net's stupid architecture as a hollow
sphere comprised entirely of ends, he's painting a picture that gets at
what's most remarkable about the Internet's architecture: Take the value out
of the center and you enable an insane flowering of value among the connected
end points. Because, of course, when every end is connected, each to each and
each to all, the ends aren't endpoints at all.
&lt;/p&gt;

&lt;p&gt;
And what do we ends do? Anything that can be done by anyone who wants to
move bits around.
&lt;/p&gt;&lt;/blockquote&gt;&lt;/div&gt;
      
            &lt;div class="field field--name-node-link field--type-ds field--label-hidden field--item"&gt;  &lt;a href="https://www.linuxjournal.com/content/linuxs-broadening-foundation" hreflang="en"&gt;Go to Full Article&lt;/a&gt;
&lt;/div&gt;
      
    &lt;/div&gt;
  &lt;/div&gt;

</description>
  <pubDate>Thu, 06 Jun 2019 11:30:00 +0000</pubDate>
    <dc:creator>Doc Searls</dc:creator>
    <guid isPermaLink="false">1340604 at https://www.linuxjournal.com</guid>
    </item>

  </channel>
</rss>
