Clean up of storage focused chapter
Removed common content: User (legal) requirements Implements: blueprint arch-guide Change-Id: Ic75560c690c3151f6e4f510ee73633956bda115b
This commit is contained in:
Suyog Sainkar
parent
79d32c6607
commit
331f2c81e2
@ -70,7 +70,6 @@
|
||||
</listitem>
|
||||
</itemizedlist>
|
||||
|
||||
<xi:include href="storage_focus/section_user_requirements_storage_focus.xml"/>
|
||||
<xi:include href="storage_focus/section_tech_considerations_storage_focus.xml"/>
|
||||
<xi:include href="storage_focus/section_operational_considerations_storage_focus.xml"/>
|
||||
<xi:include href="storage_focus/section_architecture_storage_focus.xml"/>
|
||||
|
||||
@ -1,144 +0,0 @@
|
||||
<?xml version="1.0" encoding="UTF-8"?>
|
||||
<section xmlns="http://docbook.org/ns/docbook"
|
||||
xmlns:xi="http://www.w3.org/2001/XInclude"
|
||||
xmlns:xlink="http://www.w3.org/1999/xlink"
|
||||
version="5.0"
|
||||
xml:id="user-requirements-storage-focus">
|
||||
<?dbhtml stop-chunking?>
|
||||
<title>User requirements</title>
|
||||
<para>Requirements for data define storage-focused clouds. These include:</para>
|
||||
<itemizedlist>
|
||||
<listitem>
|
||||
<para>
|
||||
Performance
|
||||
</para>
|
||||
</listitem>
|
||||
<listitem>
|
||||
<para>
|
||||
Access patterns
|
||||
</para>
|
||||
</listitem>
|
||||
<listitem>
|
||||
<para>
|
||||
Data structures
|
||||
</para>
|
||||
</listitem>
|
||||
</itemizedlist>
|
||||
<para>A balance between cost and user requirements dictate
|
||||
what methods and technologies to use in a cloud architecture.</para>
|
||||
<variablelist>
|
||||
<varlistentry>
|
||||
<term>Cost</term>
|
||||
<listitem>
|
||||
<para>The user pays only for the storage they
|
||||
actually use. This limit typically reflects average
|
||||
user consumption during a month. This does not mean
|
||||
that cloud storage is less expensive, only that it
|
||||
incurs operating expenses rather than capital expenses.</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
<varlistentry>
|
||||
<term>Legal requirements</term>
|
||||
<listitem>
|
||||
<para>Multiple jurisdictions have
|
||||
legislative and regulatory requirements governing the
|
||||
storage and management of data in cloud environments.
|
||||
Common areas of regulation include data retention
|
||||
policies and data ownership policies.</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
</variablelist>
|
||||
|
||||
<section xml:id="legal-requirements-storage-focus">
|
||||
<title>Legal requirements</title>
|
||||
<para>Many jurisdictions have legislative and regulatory
|
||||
requirements governing the storage and management of data in
|
||||
cloud environments. Common areas of regulation include:</para>
|
||||
<note>
|
||||
<para>Examples of such legal frameworks include the <link
|
||||
xlink:href="http://ec.europa.eu/justice/data-protection/">data
|
||||
protection framework</link> of the European Union and the
|
||||
requirements of the <link
|
||||
xlink:href="http://www.finra.org/Industry/Regulation/FINRARules/">Financial
|
||||
Industry Regulatory Authority</link> in the United
|
||||
States. Consult a local regulatory body for more information.
|
||||
</para>
|
||||
</note>
|
||||
<variablelist>
|
||||
<varlistentry>
|
||||
<term>Data retention</term>
|
||||
<listitem>
|
||||
<para>Policies ensuring storage of
|
||||
persistent data and records management to meet data
|
||||
archival requirements.</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
<varlistentry>
|
||||
<term>Data ownership</term>
|
||||
<listitem>
|
||||
<para>Policies governing the possession
|
||||
and responsibility for data.</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
<varlistentry>
|
||||
<term>Data sovereignty</term>
|
||||
<listitem>
|
||||
<para>Policies governing the storage of
|
||||
data in foreign countries or otherwise separate
|
||||
jurisdictions.</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
<varlistentry>
|
||||
<term>Data compliance</term>
|
||||
<listitem>
|
||||
<para>Policies governing types of
|
||||
information that must reside in certain
|
||||
locations due to regulatory issues and cannot reside in
|
||||
other locations for the same reason.</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
</variablelist>
|
||||
</section>
|
||||
|
||||
<section xml:id="technical-requirements-storage-focus">
|
||||
<title>Technical requirements</title>
|
||||
<para>You can incorporate the following technical requirements
|
||||
into the architecture design:</para>
|
||||
<variablelist>
|
||||
<varlistentry>
|
||||
<term>Storage proximity</term>
|
||||
<listitem>
|
||||
<para>In order to provide high
|
||||
performance or large amounts of storage space, the
|
||||
design may have to accommodate storage that is
|
||||
attached to each hypervisor or served from a
|
||||
central storage device.</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
<varlistentry>
|
||||
<term>Performance</term>
|
||||
<listitem>
|
||||
<para>To boost performance, the organization
|
||||
may want to make use of different technologies to
|
||||
cache disk activity.</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
<varlistentry>
|
||||
<term>Availability</term>
|
||||
<listitem>
|
||||
<para>Specific requirements regarding
|
||||
availability influence the technology used to
|
||||
store and protect data. These requirements
|
||||
influence cost and the implemented solution.</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
<varlistentry>
|
||||
<term>Security</term>
|
||||
<listitem>
|
||||
<para>You must protect data both in
|
||||
transit and at rest.</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
</variablelist>
|
||||
</section>
|
||||
</section>
|
||||
Loading…
Reference in New Issue
Block a user