<?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/">
  <channel>
    <title>Cloud</title>
    <link>https://www.linuxjournal.com/</link>
    <description/>
    <language>en</language>
    
    <item>
  <title>Delivering Enterprise-Grade Linux for Edge-to-Cloud Deployments with eLxr</title>
  <link>https://www.linuxjournal.com/content/delivering-enterprise-grade-linux-edge-cloud-deployments-elxr</link>
  <description>  &lt;div data-history-node-id="1341191" 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 loading="lazy" src="https://www.linuxjournal.com/sites/default/files/nodeimage/story/windriver-elxr-featured-2.jpg" width="850" height="500" alt="Delivering Enterprise-Grade Linux for Edge-to-Cloud Deployments with eLxr" 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/mark-asselstine" lang="" about="https://www.linuxjournal.com/users/mark-asselstine" typeof="schema:Person" property="schema:name" datatype="" xml:lang=""&gt;Mark Asselstine&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;The eLxr project has launched its initial release of a Debian-based distribution that incorporates the intelligent edge capabilities of Debian, with plans to expand these for a streamlined edge-to-cloud deployment approach. eLxr is an open source, enterprise-grade Linux distribution designed to address the specific challenges of near-edge networks and workloads.&lt;/p&gt;

&lt;h2&gt;What Is the eLxr Project?&lt;/h2&gt;

&lt;p&gt;The eLxr project is a community-driven effort dedicated to expanding access to cutting-edge technologies for both enthusiasts and enterprise users seeking dependable and innovative solutions that scale from edge to cloud. The project produces and maintains an open source, enterprise-grade Debian-based distribution called eLxr that is user-friendly and fully honors the open source philosophy.&lt;/p&gt;

&lt;p&gt;&lt;img alt=" windriver-elxr-content-image-1" data-entity-type="file" data-entity-uuid="5c65be6d-5727-4bde-9df6-b44ba0931ef3" src="https://www.linuxjournal.com/sites/default/files/inline-images/windriver-elxr-content-image-1.jpg" class="align-right" width="400" height="400" loading="lazy" /&gt;The eLxr project's mission focuses on accessibility, innovation, and maintaining the integrity of open source software. Developing these advancements in an enterprise-grade Debian-based distribution ensures that users benefit from a freely available Linux distribution.&lt;/p&gt;

&lt;p&gt;By emphasizing ease of adoption alongside open source principles, eLxr aims to attract a diverse range of users and contributors who value both innovation and community-driven development, fostering collaboration and transparency and the spread of new technologies.&lt;/p&gt;

&lt;p&gt;The eLxr project is implementing a robust strategy for building on Debian's ecosystem while also contributing back to it. As "Debian citizens," eLxr contributors submit innovations and improvements upstream, actively participating in the community's development efforts. This approach not only enhances eLxr's own distribution but also strengthens Debian by expanding its feature set and improving its overall quality.&lt;/p&gt;

&lt;p&gt;The ability to release technologies at various stages of Debian's development cycle and to introduce innovative new content not yet available in Debian highlights eLxr's flexibility and responsiveness to emerging needs. Moreover, the commitment to sustainability ensures that contributions made by eLxr members remain beneficial to the broader Debian community over the long term.&lt;/p&gt;

&lt;h2&gt;A Unified Approach for Intelligent Deployments at the Edge&lt;/h2&gt;

&lt;p&gt;Modern technology demands agility and responsiveness to rapidly changing requirements and operational challenges. By integrating cutting-edge technologies from open source communities and technology companies into its distribution, the eLxr project enables users to leverage innovations that may not yet be widely distributed or easily accessible through other channels.&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/delivering-enterprise-grade-linux-edge-cloud-deployments-elxr" hreflang="en"&gt;Go to Full Article&lt;/a&gt;
&lt;/div&gt;
      
    &lt;/div&gt;
  &lt;/div&gt;

</description>
  <pubDate>Mon, 12 Aug 2024 16:00:00 +0000</pubDate>
    <dc:creator>Mark Asselstine</dc:creator>
    <guid isPermaLink="false">1341191 at https://www.linuxjournal.com</guid>
    </item>
<item>
  <title>The Taloflow Instance Manager (Tim)</title>
  <link>https://www.linuxjournal.com/content/taloflow-instance-manager-tim</link>
  <description>  &lt;div data-history-node-id="1340468" class="layout layout--onecol"&gt;
    &lt;div class="layout__region layout__region--content"&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/petros-koutoupis" lang="" about="https://www.linuxjournal.com/users/petros-koutoupis" typeof="schema:Person" property="schema:name" datatype="" xml:lang=""&gt;Petros Koutoupis&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;
For years, modern workloads have shifted to the cloud, with AWS being
the most popular. And although this shift has cut down
operating costs significantly, millions, if not billions, of dollars still
are wasted to maintain
all those virtual instances—even when they are not in use.
&lt;/p&gt;

&lt;p&gt;
To help alleviate both the burden and headache of managing your cloud-hosted
virtual machines, &lt;a href="https://www.taloflow.ai"&gt;Taloflow&lt;/a&gt;
built the Taloflow Instance Manager (Tim), which can reduce your expenditures by as
much as 40%. Tim monitors your AWS resources and suggests
automations that effortlessly save you money in real time.
&lt;/p&gt;

&lt;p&gt;
Taloflow is a Vancouver- and California-based startup, offering a
Software-as-a-Service (SaaS) platform that seamlessly integrates into
your preferred cloud service provider to set up alerts, capture metrics
and automate a list of useful actions. The company is focused solely
on bringing artificial intelligence (AI) automation and intelligence
to cloud services. Currently, Taloflow is an operation of at least eight
talented engineers coming from all business backgrounds (from startups
to enterprises).
&lt;/p&gt;

&lt;img src="https://www.linuxjournal.com/sites/default/files/styles/max_650x650/public/u%5Buid%5D/Team.png" width="650" height="392" alt="Taloflow team" class="image-max_650x650" /&gt;&lt;p&gt;
&lt;em&gt;Figure 1. The Taloflow Team&lt;/em&gt;
&lt;/p&gt;

&lt;p&gt;
One of the key differences with Tim is that it &lt;em&gt;works in
real time&lt;/em&gt;. Unlike its competition, which is focused primarily on
accountants and finance departments, Tim takes a bottoms-up approach and
shifts that focus onto the engineers and operators pulling the levers
on these cloud virtual instances. Think of it as bot or tool helping
developers manage their resources and monitor their workflows. Tim will
provide recommendations to those same engineers on how to optimize the
performance, as well as the cost in the cloud.
&lt;/p&gt;

&lt;p&gt;
The current implementation of Tim is available under a freemium
model. This is intended to encourage early adoption, and it also allows
users to hit the ground running and get started quickly. Depending on
usage, number of users and the required performance, a paid tier or
Enterprise Model eventually will be offered by
March 2019.
&lt;/p&gt;

&lt;p&gt;
Tim's basic model runs on Taloflow's own cloud, and depending on the
customer's security preferences, the company will offer and provision private
instances for each user (under the Enterprise subscription model). This
will look like a Kubernetes image running on-premises at the customer site.
&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/taloflow-instance-manager-tim" hreflang="en"&gt;Go to Full Article&lt;/a&gt;
&lt;/div&gt;
      
    &lt;/div&gt;
  &lt;/div&gt;

</description>
  <pubDate>Fri, 08 Feb 2019 13:00:00 +0000</pubDate>
    <dc:creator>Petros Koutoupis</dc:creator>
    <guid isPermaLink="false">1340468 at https://www.linuxjournal.com</guid>
    </item>
<item>
  <title>Weekend Reading: Cloud</title>
  <link>https://www.linuxjournal.com/content/weekend-reading-cloud</link>
  <description>  &lt;div data-history-node-id="1339932" class="layout layout--onecol"&gt;
    &lt;div class="layout__region layout__region--content"&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/carlie-fairchild" lang="" about="https://www.linuxjournal.com/users/carlie-fairchild" typeof="schema:Person" property="schema:name" datatype="" xml:lang=""&gt;Carlie Fairchild&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 dir="ltr"&gt;The cloud has become synonymous with all things data storage. It additionally equates to the many web-centric services accessing that same back-end data storage, but the term also has evolved to mean so much more.&lt;/p&gt;

&lt;p dir="ltr"&gt;This weekend join us as we explore the cloud.&lt;/p&gt;

&lt;h2 dir="ltr"&gt;&lt;a href="https://www.linuxjournal.com/content/cloudwatch-devil-i-must-use-it"&gt;CloudWatch Is of the Devil, but I Must Use It&lt;/a&gt;&lt;/h2&gt;

&lt;p dir="ltr"&gt;by &lt;a href="https://www.linuxjournal.com/users/corey-quinn-0"&gt;Corey Quinn&lt;/a&gt;&lt;/p&gt;

&lt;p dir="ltr"&gt;Let's talk about Amazon CloudWatch.&lt;/p&gt;

&lt;h2&gt;&lt;a href="https://www.linuxjournal.com/content/everything-you-need-know-about-cloud-and-cloud-computing-part-i"&gt;Everything You Need to &lt;/a&gt;&lt;a href="https://www.linuxjournal.com/content/everything-you-need-know-about-cloud-and-cloud-computing-part-i"&gt;Know about the Cloud and Cloud Computing, Part I&lt;/a&gt;&lt;/h2&gt;

&lt;p dir="ltr"&gt;by &lt;a href="https://www.linuxjournal.com/users/petros-koutoupis"&gt;Petros Koutoupis&lt;/a&gt;&lt;/p&gt;

&lt;p dir="ltr"&gt;An in-depth breakdown of the technologies involved in making up the cloud and a survey of cloud-service providers.&lt;/p&gt;

&lt;h2&gt;&lt;a href="https://www.linuxjournal.com/content/everything-you-need-know-about-cloud-and-cloud-computing-part-ii-using-cloud"&gt;Everything You Need to Know about the Cloud and Cloud Computing, Part II: Using the Cloud&lt;/a&gt;&lt;/h2&gt;

&lt;p&gt;by &lt;a href="https://www.linuxjournal.com/users/petros-koutoupis"&gt;Petros Koutoupis&lt;/a&gt;&lt;/p&gt;

&lt;p dir="ltr"&gt;How to get started with AWS, install Apache, create an EFS volume and much more.&lt;/p&gt;

&lt;h2&gt;&lt;a href="https://www.linuxjournal.com/content/agony-and-ecstasy-cloud-billing"&gt;The Agony and the Ecstasy of Cloud Billing&lt;/a&gt;&lt;/h2&gt;

&lt;p dir="ltr"&gt;by &lt;a href="https://www.linuxjournal.com/users/corey-quinn-0"&gt;Corey Quinn&lt;/a&gt;&lt;/p&gt;

&lt;p dir="ltr"&gt;Cloud billing is inherently complex; it's not just you.&lt;/p&gt;

&lt;h2&gt;&lt;a href="https://www.linuxjournal.com/content/nextcloud-13-how-get-started-and-why-you-should"&gt;Nextcloud 13: How to Get Started and Why You Should&lt;/a&gt;&lt;/h2&gt;

&lt;p dir="ltr"&gt;by &lt;a href="https://www.linuxjournal.com/users/marco-fioretti"&gt;Marco Fioretti&lt;/a&gt;&lt;/p&gt;

&lt;p dir="ltr"&gt;In its simplest form, the &lt;a href="https://nextcloud.com/"&gt;Nextcloud&lt;/a&gt; server is "just" a personal, free software alternative to services like Dropbox or iCloud. You can set it up so your files are always accessible via the internet, from wherever you are, and share them with your friends. However, Nextcloud can do so much more.&lt;/p&gt;

&lt;h2&gt;&lt;a href="https://www.linuxjournal.com/content/simple-cloud-hardening"&gt;Simple Cloud Hardening&lt;/a&gt;&lt;/h2&gt;

&lt;p dir="ltr"&gt;by &lt;a href="https://www.linuxjournal.com/users/kyle-rankin"&gt;Kyle Rankin&lt;/a&gt;&lt;/p&gt;

&lt;p dir="ltr"&gt;Apply a few basic hardening principles to secure your cloud environment.
 &lt;/p&gt;

&lt;h2&gt;&lt;a href="https://www.linuxjournal.com/content/vendor-lock-now-cloud"&gt;Vendor Lock-in: Now in the Cloud!&lt;/a&gt;&lt;/h2&gt;

&lt;p dir="ltr"&gt;by &lt;a href="https://www.linuxjournal.com/users/kyle-rankin"&gt;Kyle Rankin&lt;/a&gt;&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/weekend-reading-cloud" hreflang="en"&gt;Go to Full Article&lt;/a&gt;
&lt;/div&gt;
      
    &lt;/div&gt;
  &lt;/div&gt;

</description>
  <pubDate>Sat, 22 Dec 2018 12:30:00 +0000</pubDate>
    <dc:creator>Carlie Fairchild</dc:creator>
    <guid isPermaLink="false">1339932 at https://www.linuxjournal.com</guid>
    </item>
<item>
  <title>CloudWatch Is of the Devil, but I Must Use It</title>
  <link>https://www.linuxjournal.com/content/cloudwatch-devil-i-must-use-it</link>
  <description>  &lt;div data-history-node-id="1340200" class="layout layout--onecol"&gt;
    &lt;div class="layout__region layout__region--content"&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/corey-quinn-0" lang="" about="https://www.linuxjournal.com/users/corey-quinn-0" typeof="schema:Person" property="schema:name" datatype="" xml:lang=""&gt;Corey Quinn&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;Let's talk about Amazon CloudWatch.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;
For those fortunate enough to not be stuck in the weeds of Amazon Web
Services (AWS), CloudWatch is, and I quote from the official
&lt;a href="https://aws.amazon.com/cloudwatch"&gt;AWS description&lt;/a&gt;, "a monitoring and
management service built for developers, system operators, site reliability
engineers (SRE), and IT managers." This is all well and good, except for the
part where there isn't a single named constituency who enjoys working with
the product. Allow me to dispense some monitoring heresy.
&lt;/p&gt;

&lt;p&gt;
Better, let me describe this in the context of the 14 &lt;a href="https://www.amazon.jobs/principles"&gt;Amazon
Leadership Principles&lt;/a&gt; that reportedly guide every decision Amazon makes.
When you take a hard look at CloudWatch's complete failure across all
14 Leadership Principles, you wonder how this product ever made it out
the door in its current state.
&lt;/p&gt;

&lt;span class="h3-replacement"&gt;
"Frugality"&lt;/span&gt;

&lt;p&gt;
I'll start with billing. Normally left for the tail end of articles like
this, the CloudWatch billing paradigm is so terrible, I'm leading with
it instead. You get billed per metric, per month. You get billed per
thousand metrics you request to view via the API. You get billed per
dashboard per month. You get billed per alarm per month. You get charged for
logs based upon data volume ingested, data volume stored and "vended logs"
that get published natively by AWS services on behalf of the customer. And,
you get billed per custom event. All of this can be summed up best as
"nobody on the planet understands how your CloudWatch metrics and logs get
billed", and it leads to scenarios where monitoring vendors can inadvertently
cost you thousands of dollars by polling CloudWatch too frequently. When the
AWS charges are larger than what you're paying your monitoring vendor, it's
not a wonderful feeling.
&lt;/p&gt;

&lt;span class="h3-replacement"&gt;
"Invent and Simplify"&lt;/span&gt;

&lt;p&gt;
CloudWatch Logs, CloudWatch Events, Custom Metrics, Vended Logs and Custom
Dashboards all mean different things internally to CloudWatch from what you'd
expect, compared to metrics solutions that actually make some fathomable
level of sense. There are, thus, multiple services that do very different
things, all operating under the "CloudWatch" moniker. For example, it's not
particularly intuitive to most people that scheduling a Lambda function to
invoke once an hour requires a custom CloudWatch Event. It feels overly
complicated, incredibly confusing, and very quickly, you find yourself in a
situation where you're having to build complex relationships to monitor
things that are themselves far simpler.
&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/cloudwatch-devil-i-must-use-it" hreflang="en"&gt;Go to Full Article&lt;/a&gt;
&lt;/div&gt;
      
    &lt;/div&gt;
  &lt;/div&gt;

</description>
  <pubDate>Wed, 31 Oct 2018 11:30:00 +0000</pubDate>
    <dc:creator>Corey Quinn</dc:creator>
    <guid isPermaLink="false">1340200 at https://www.linuxjournal.com</guid>
    </item>
<item>
  <title>Why the Failure to Conquer the Desktop Was Great for GNU/Linux</title>
  <link>https://www.linuxjournal.com/content/why-failure-conquer-desktop-was-great-gnulinux</link>
  <description>  &lt;div data-history-node-id="1339910" class="layout layout--onecol"&gt;
    &lt;div class="layout__region layout__region--content"&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/glyn-moody" lang="" about="https://www.linuxjournal.com/users/glyn-moody" typeof="schema:Person" property="schema:name" datatype="" xml:lang=""&gt;Glyn Moody&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;AI: open source's next big win.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;
Canonical recently launched Ubuntu 18.04 LTS. It's an
important release. In part, that's because Canonical will
support it for five years, making it one of the relatively rare &lt;a href="https://wiki.ubuntu.com/LTS"&gt;LTS&lt;/a&gt; products in Ubuntu's history.
Ubuntu 18.04 also marks a high-profile return to GNOME as the default
desktop, after a few years of controversial experimentation with Unity.
The result is regarded by many as the best desktop Ubuntu so far (that's my
view too, for what it's worth). And yet, the emphasis at launch lay elsewhere. Mark
Shuttleworth, CEO of Canonical and founder of Ubuntu, said:
&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;
Multi-cloud operations are the new normal. Boot-time and
performance-optimised images of Ubuntu 18.04 LTS on every major public
cloud make it the fastest and most efficient OS for cloud computing,
especially for storage and compute-intensive tasks like machine
learning.
&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;
The bulk of &lt;a href="https://insights.ubuntu.com/2018/04/26/ubuntu-18-04-lts-optimised-for-security-multi-cloud-containers-ai"&gt;the
official 18.04 LTS announcement&lt;/a&gt; is about Ubuntu's &lt;a href="https://www.linuxjournal.com/content/everything-you-need-know-about-cloud-and-cloud-computing-part-i"&gt;cloud
computing&lt;/a&gt; features. On the main web site, Ubuntu claims
to be "&lt;a href="https://www.ubuntu.com/cloud"&gt;The standard
OS for cloud computing&lt;/a&gt;", citing (slightly old) research
that shows "70% of public cloud workloads and 54% of OpenStack
clouds" use it. Since Canonical is a privately held company,
it doesn't publish a detailed breakdown of its operations, just &lt;a href="https://beta.companieshouse.gov.uk/company/06870835/filing-history"&gt;a
basic summary&lt;/a&gt;. That means it's hard to tell just how successful
the cloud computing strategy is proving. But, the fact that &lt;a href="https://www.youtube.com/watch?time_continue=235&amp;v=y4lF_fYxvIk"&gt;Shuttleworth
is now openly talking about an IPO&lt;/a&gt;—not something to be undertaken
lightly—suggests that there is enough good news to convince
investors to throw plenty of money at Canonical when the prospectus
spells out how the business is doing.
&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/why-failure-conquer-desktop-was-great-gnulinux" hreflang="en"&gt;Go to Full Article&lt;/a&gt;
&lt;/div&gt;
      
    &lt;/div&gt;
  &lt;/div&gt;

</description>
  <pubDate>Mon, 06 Aug 2018 11:30:00 +0000</pubDate>
    <dc:creator>Glyn Moody</dc:creator>
    <guid isPermaLink="false">1339910 at https://www.linuxjournal.com</guid>
    </item>
<item>
  <title>As Cloud Computing Providers Post Record Profits, One Company Wants to Make Them Obsolete</title>
  <link>https://www.linuxjournal.com/content/cloud-computing-providers-post-record-profits-one-company-wants-make-them-obsolete</link>
  <description>  &lt;div data-history-node-id="1339987" class="layout layout--onecol"&gt;
    &lt;div class="layout__region layout__region--content"&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/graham-templeton" lang="" about="https://www.linuxjournal.com/users/graham-templeton" typeof="schema:Person" property="schema:name" datatype="" xml:lang=""&gt;Graham Templeton&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;Could the world's idle computers make the $200 billion cloud
computing industry obsolete?&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;
In the final years of the Obama administration, it seemed that the world
was witnessing the emergence of an odd alliance between the largest
establishment tech companies and the traditionally anti-establishment
community of independent techies.  The highest profile case involved Apple
and other major corporations siding with civil rights organizations to
advocate against weakening device encryption on behalf of law enforcement,
and it it led to a hope that these companies were finally seeing the
profit potential in having secure, satisfied customers. That hope has
now evaporated in the face of continuous betrayals of user trust, and
rather than take it lying down, tech users are looking into alternative
solutions that put them in control.
&lt;/p&gt;

&lt;p&gt;
The recently passed federal &lt;em&gt;Clarifying Lawful Overseas Use of Data
Act&lt;/em&gt;,
or the CLOUD Act, makes it perfectly clear why this shift away from
self-interested stakeholders is so necessary. The new law &lt;a href="https://blogs.microsoft.com/on-the-issues/2018/04/03/the-cloud-act-is-an-important-step-forward-but-now-more-steps-need-to-follow"&gt;was
motivated by&lt;/a&gt;
a legal demand for Microsoft to hand user data to US law enforcement,
even though that data was stored outside US borders and, thus, in a
different legal jurisdiction. At first, it seemed that Microsoft was
planning to stand up for privacy and national sovereignty by opposing
the demand in court—but, predictably, the corporation rolled over
just as soon as it deemed that its own interests were protected.
&lt;/p&gt;

&lt;p&gt;
The goal of the CLOUD Act is for the US to be able to compel any company
that does business in the country to provide information to US law
enforcement, even if that information is not actually stored within the
US. If it's successful, a company's willingness to fight will become
essentially irrelevant. It makes all cloud computing and cloud storage
companies suspect, simply by virtue of being cloud computing companies.
&lt;/p&gt;

&lt;p&gt;
Groups like the &lt;a href="https://www.eff.org/deeplinks/2018/02/cloud-act-dangerous-expansion-police-snooping-cross-border-data"&gt;Electronic
Frontier Foundation&lt;/a&gt; and the &lt;a href="https://www.aclu.org/blog/privacy-technology/internet-privacy/cloud-act-dangerous-piece-legislation"&gt;American Civil
Liberties Union&lt;/a&gt; believe it also could allow US law enforcement to
seize information in foreign jurisdictions because those regions have
more lenient privacy laws than the US itself.  The reverse, in which
foreign law enforcement agencies operating under &lt;a href="https://global.handelsblatt.com/politics/with-new-us-law-how-safe-is-online-data-in-europe-914956"&gt;more
stringent rules
than the US&lt;/a&gt;, could gain access to protected information stored in the
country, is also a major concern.
&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/cloud-computing-providers-post-record-profits-one-company-wants-make-them-obsolete" hreflang="en"&gt;Go to Full Article&lt;/a&gt;
&lt;/div&gt;
      
    &lt;/div&gt;
  &lt;/div&gt;

</description>
  <pubDate>Thu, 28 Jun 2018 12:00:00 +0000</pubDate>
    <dc:creator>Graham Templeton</dc:creator>
    <guid isPermaLink="false">1339987 at https://www.linuxjournal.com</guid>
    </item>
<item>
  <title>Nextcloud 13: How to Get Started and Why You Should</title>
  <link>https://www.linuxjournal.com/content/nextcloud-13-how-get-started-and-why-you-should</link>
  <description>  &lt;div data-history-node-id="1339843" class="layout layout--onecol"&gt;
    &lt;div class="layout__region layout__region--content"&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/marco-fioretti" lang="" about="https://www.linuxjournal.com/users/marco-fioretti" typeof="schema:Person" property="schema:name" datatype="" xml:lang=""&gt;Marco Fioretti&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;Nextcloud could be the first step toward replacing proprietary services like Dropbox and Skype.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;
In its simplest form, the &lt;a href="https://nextcloud.com"&gt;Nextcloud&lt;/a&gt; server is
"just" a personal, free software alternative to services like Dropbox
or iCloud. You can set it up so your files are always accessible
via the internet, from wherever you are, and share them with your
friends. However, Nextcloud can do so much more.
&lt;/p&gt;

&lt;p&gt;
In this article, I first describe what the Nextcloud server is and
how to install and set it up on GNU/Linux systems. Then I explain how to
configure the optional Nextcloud features, which may be the first
steps toward making Nextcloud the shell of a complete replacement for
many proprietary platforms existing today, such as Dropbox, Facebook and Skype.
&lt;/p&gt;

&lt;img src="https://www.linuxjournal.com/sites/default/files/styles/max_1300x1300/public/u%5Buid%5D/12307f1.png" width="920" height="829" alt="""" class="image-max_1300x1300" /&gt;&lt;p&gt;
&lt;em&gt;Figure 1. A safe home for
all your data that all your devices can reach—that's what Nextcloud
wants to be.&lt;/em&gt;&lt;/p&gt;

&lt;span class="h3-replacement"&gt;
Why Nextcloud and Not ownCloud?&lt;/span&gt;

&lt;p&gt;
Nextcloud, whose version 13 was released in February 2018, was spun off
the popular &lt;a href="https://owncloud.org"&gt;ownCloud&lt;/a&gt; project in 2016, out of
licensing and other disagreements.
See the Resources section for
some of the most complete feature-by-feature comparisons between
Nextcloud and ownCloud.
The most
basic capabilities are still almost identical, two years after the
fork. Some of the functions described here, however, are easier to
integrate in Nextcloud than in its ancestor. In addition,
my personal reasons for recommending Nextcloud over ownCloud are the following:
&lt;/p&gt;

&lt;ul&gt;&lt;li&gt;
Licensing and pricing policies: all the official components of Nextcloud
are both free as in freedom and as in free beer. You pay only for support
and update services. That's not the case with ownCloud.
&lt;/li&gt;

&lt;li&gt;
Long-term roadmap: at the moment, ownCloud seems to be more focused
on corporate customers and more relevant for investors, while Nextcloud seems to be more
focused on
extending "direct" user-to-user communication and cooperation features.
&lt;/li&gt;&lt;/ul&gt;&lt;img src="https://www.linuxjournal.com/sites/default/files/styles/max_1300x1300/public/u%5Buid%5D/12307f2.png" width="653" height="478" alt="""" class="image-max_1300x1300" /&gt;&lt;p&gt;&lt;em&gt;
Figure 2. The Original
Nextcloud/ownCloud Functions: File and Picture Storage, Dropbox-Style&lt;/em&gt;&lt;/p&gt;

&lt;span class="h3-replacement"&gt;
A Word on Security&lt;/span&gt;

&lt;p&gt;
Several good reasons to choose Nextcloud as the online home for your own
files and data are related to security. I don't cover them in detail
in this introductory article, but I want to mention at least some of them.
&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/nextcloud-13-how-get-started-and-why-you-should" hreflang="en"&gt;Go to Full Article&lt;/a&gt;
&lt;/div&gt;
      
    &lt;/div&gt;
  &lt;/div&gt;

</description>
  <pubDate>Mon, 21 May 2018 11:45:00 +0000</pubDate>
    <dc:creator>Marco Fioretti</dc:creator>
    <guid isPermaLink="false">1339843 at https://www.linuxjournal.com</guid>
    </item>
<item>
  <title>Everything You Need to Know about the Cloud and Cloud Computing, Part II: Using the Cloud</title>
  <link>https://www.linuxjournal.com/content/everything-you-need-know-about-cloud-and-cloud-computing-part-ii-using-cloud</link>
  <description>  &lt;div data-history-node-id="1339775" class="layout layout--onecol"&gt;
    &lt;div class="layout__region layout__region--content"&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/petros-koutoupis" lang="" about="https://www.linuxjournal.com/users/petros-koutoupis" typeof="schema:Person" property="schema:name" datatype="" xml:lang=""&gt;Petros Koutoupis&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;How to get started with AWS, install Apache, create an EFS volume and
much more.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;
The cloud is here to stay, regardless of how you access data day to
day. Whether you are uploading and sharing new photos with friends
in your social-media account or updating documents and spreadsheets
alongside your peers in your office or school, chances are
you're connecting to the cloud in some form or another.
&lt;/p&gt;

&lt;p&gt;
In the first part of this series, I explored what makes up the
cloud and how it functions when all of its separate moving pieces come
together. In this article, building from Part I's foundations, I cover using the cloud through some
actual examples.
&lt;/p&gt;

&lt;span class="h3-replacement"&gt;
Getting Started with AWS&lt;/span&gt;

&lt;p&gt;
For the purposes of this article, I'm focusing on a few of the top
offerings provided by Amazon Web Services (AWS). Please know that
I hold no affiliation to or with Amazon, nor am I stating that Amazon
offerings exceed those of its competitors.
&lt;/p&gt;

&lt;p&gt;
If you haven't already, be sure to &lt;a href="https://aws.amazon.com"&gt;register an account&lt;/a&gt;.
But before you do, understand that charges
&lt;em&gt;may&lt;/em&gt; apply. Amazon, may provide a &lt;em&gt;free&lt;/em&gt; tier
of offerings for a limited time, typically a year, to newly registered
users. In most cases, the limitations to these offerings are far less
than ideal for modern use cases. It is a pay-as-you go model, and you'll
be charged only as long as the instance or service continues to be active.
&lt;/p&gt;

&lt;p&gt;
As soon as you are registered and logged in from within your web browser,
you'll be greeted by a fairly straightforward dashboard.
&lt;/p&gt;

&lt;img src="https://www.linuxjournal.com/sites/default/files/styles/max_650x650/public/u%5Buid%5D/12340f1.jpg" width="650" height="367" alt="Screenshot" class="image-max_650x650" /&gt;&lt;p&gt;
&lt;em&gt;Figure 1. The AWS Main Dashboard
of services and resources.&lt;/em&gt;
&lt;/p&gt;

&lt;span class="h3-replacement"&gt;
Compute&lt;/span&gt;

&lt;p&gt;
At first, companies leveraging cloud compute applied a straight
copy-and-paste of their very own data centers for deploying standard
web/application/database servers. The model was the same. There is
nothing wrong with that approach. The transition for most converting
from on-premises to the cloud would have been somewhat seamless—at
least from the perspective of the user accessing those resources. The
only real difference being that it was just in a different data center
and without the headache of maintaining the infrastructure supporting it.
&lt;/p&gt;

&lt;p&gt;
In the world of AWS, virtual compute servers are managed under the
Elastic Cloud Computing (EC2) stack, from whole virtual instances to
containers and more. Let's begin an example EC2 experiment by navigating to
the EC2 dashboard.
&lt;/p&gt;

&lt;img src="https://www.linuxjournal.com/sites/default/files/styles/max_650x650/public/u%5Buid%5D/12340f2.jpg" width="650" height="393" alt="screenshot" class="image-max_650x650" /&gt;&lt;p&gt;
&lt;em&gt;Figure 2. The Elastic Cloud Computing Dashboard&lt;/em&gt;
&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/everything-you-need-know-about-cloud-and-cloud-computing-part-ii-using-cloud" hreflang="en"&gt;Go to Full Article&lt;/a&gt;
&lt;/div&gt;
      
    &lt;/div&gt;
  &lt;/div&gt;

</description>
  <pubDate>Tue, 15 May 2018 11:45:00 +0000</pubDate>
    <dc:creator>Petros Koutoupis</dc:creator>
    <guid isPermaLink="false">1339775 at https://www.linuxjournal.com</guid>
    </item>
<item>
  <title>Everything You Need to Know about the Cloud and Cloud Computing, Part I</title>
  <link>https://www.linuxjournal.com/content/everything-you-need-know-about-cloud-and-cloud-computing-part-i</link>
  <description>  &lt;div data-history-node-id="1339773" class="layout layout--onecol"&gt;
    &lt;div class="layout__region layout__region--content"&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/petros-koutoupis" lang="" about="https://www.linuxjournal.com/users/petros-koutoupis" typeof="schema:Person" property="schema:name" datatype="" xml:lang=""&gt;Petros Koutoupis&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;An in-depth breakdown of the technologies involved in making up
the cloud and a survey of cloud-service providers.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;
The cloud has become synonymous with all things data storage. It
additionally
equates to the many web-centric services accessing that same back-end
data storage. But the term also has evolved to mean so much more.&lt;/p&gt;

&lt;p&gt;
Cloud
computing provides more simplified access to server, storage, database and
application resources, with users provisioning and using the minimum set
of requirements they see fit to host their application needs. In the
past decade alone, the paradigm shift toward a wider and more accessible
network has forced both hardware vendors and service providers to rethink
their strategies and cater to a new model of storing information and
serving application resources. As time continues to pass, more individuals
and businesses are connecting themselves to this greater world of computing.
&lt;/p&gt;

&lt;span class="h3-replacement"&gt;
What Is the Cloud?&lt;/span&gt;

&lt;p&gt;
Far too often, the idea of the "cloud" is confused with the general
internet. Although it's true that various components making up the cloud
can be accessible via the internet, they are not one and the same. In its
most general terms, cloud computing enables companies, service providers
and individuals to provision the appropriate amount of
computing resources dynamically (compute nodes, block or object storage
and so on)
for their needs. These application services are accessed over
a network—and not necessarily a public network. Three
distinct types of cloud deployments exist: public, private and a hybrid of both.
&lt;/p&gt;

&lt;p&gt;
The public cloud differentiates itself from the private cloud in that
the private cloud typically is deployed in the data center and under the
proprietary network using its cloud computing technologies—that is, it
is developed for and maintained by the organization it serves. Resources
for a private cloud deployment are acquired via normal hardware purchasing
means and through traditional hardware sales channels. This is not the
case for the public cloud. Resources for the public cloud are
provisioned dynamically to its user as requested and may be offered under
a pay-per-usage model or for free.
&lt;/p&gt;

&lt;p&gt;
Some of the world's leading public cloud offering platforms include:
&lt;/p&gt;

&lt;ul&gt;&lt;li&gt;
Amazon Web Services (AWS)
&lt;/li&gt;

&lt;li&gt;
Microsoft Azure
&lt;/li&gt;

&lt;li&gt;
Google Cloud Platform
&lt;/li&gt;

&lt;li&gt;
IBM Cloud (formerly SoftLayer)
&lt;/li&gt;&lt;/ul&gt;&lt;p&gt;
As the name implies, the hybrid model allows for seamless access and
transitioning between both public and private deployments, all managed
under a single framework.
&lt;/p&gt;

&lt;p&gt;
For those who prefer either to host their workload internally or partially
on the public cloud—sometimes motivated by security, data sovereignty
or compliance—private and hybrid cloud offerings continue to provide
the same amount of service but all within your control.
&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/everything-you-need-know-about-cloud-and-cloud-computing-part-i" hreflang="en"&gt;Go to Full Article&lt;/a&gt;
&lt;/div&gt;
      
    &lt;/div&gt;
  &lt;/div&gt;

</description>
  <pubDate>Wed, 09 May 2018 13:30:00 +0000</pubDate>
    <dc:creator>Petros Koutoupis</dc:creator>
    <guid isPermaLink="false">1339773 at https://www.linuxjournal.com</guid>
    </item>
<item>
  <title>The Agony and the Ecstasy of Cloud Billing</title>
  <link>https://www.linuxjournal.com/content/agony-and-ecstasy-cloud-billing</link>
  <description>  &lt;div data-history-node-id="1339708" class="layout layout--onecol"&gt;
    &lt;div class="layout__region layout__region--content"&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/corey-quinn-0" lang="" about="https://www.linuxjournal.com/users/corey-quinn-0" typeof="schema:Person" property="schema:name" datatype="" xml:lang=""&gt;Corey Quinn&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;Cloud billing is inherently complex; it's not just you.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;
Back in the mists of antiquity when I started reading &lt;em&gt;Linux Journal&lt;/em&gt;,
figuring out what an infrastructure was going to cost was (although still
obnoxious in some ways) straightforward. You'd sign leases with colocation
providers, buy hardware that you'd depreciate on a schedule and
strike a deal in blood with a bandwidth provider, and you were
more or less set until something significant happened to your scale.
&lt;/p&gt;

&lt;p&gt;
In today's brave new cloud world, all of that goes out the window. The
public cloud providers give with one hand ("Have a full copy of any
environment you want, paid by the hour!"), while taking with the other ("A
single Linux instance will cost you $X per hour, $Y per GB transferred
per month, and $Z for the attached storage; we simplify this pricing
into what we like to call 'We Make It Up As We Go Along'").
&lt;/p&gt;

&lt;p&gt;
In my day job, I'm a consultant who focuses purely on analyzing and
reducing the Amazon Web Services (AWS) bill. As a result, I've seen a
lot of environments doing different things: cloud-native shops spinning
things up without governance, large enterprises transitioning into
the public cloud with legacy applications that don't exactly support
that model without some serious tweaking, and cloud migration projects
that somehow lost their way severely enough that they were declared
acceptable as they were, and the "multi-cloud" label was slapped on to
them. Throughout all of this, some themes definitely have emerged that
I find that people don't intuitively grasp at first. To wit:
&lt;/p&gt;

&lt;ul&gt;&lt;li&gt;&lt;p&gt;
It's relatively straightforward to do the basic arithmetic to figure
out what a current data center would cost to put into the cloud as
is—generally it's a lot! If you do a 1:1 mapping of your existing data center
into the cloudy equivalents, it invariably will cost more; that's a
given. The real cost savings arise when you start to take advantage
of cloud capabilities—your web server farm doesn't need to have 50
instances at all times. If that's your burst load, maybe you can scale
that in when traffic is low to five instances or so? Only once you fall into
a pattern (and your applications support it!) of paying only for what
you need when you need it do the cost savings of cloud become apparent.
&lt;/p&gt;&lt;/li&gt;&lt;/ul&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/agony-and-ecstasy-cloud-billing" hreflang="und"&gt;Go to Full Article&lt;/a&gt;
&lt;/div&gt;
      
    &lt;/div&gt;
  &lt;/div&gt;

</description>
  <pubDate>Tue, 17 Apr 2018 14:40:00 +0000</pubDate>
    <dc:creator>Corey Quinn</dc:creator>
    <guid isPermaLink="false">1339708 at https://www.linuxjournal.com</guid>
    </item>

  </channel>
</rss>
