Merge "Arch Design edits"

This commit is contained in:
Jenkins 2014-07-28 05:28:09 +00:00 committed by Gerrit Code Review
commit b19a256724
2 changed files with 131 additions and 79 deletions

View File

@ -6,72 +6,123 @@
xml:id="arch-design-references">
<?dbhtml stop-chunking?>
<title>References</title>
<para>Data Protection framework of the European Union:
http://ec.europa.eu/justice/data-protection/Guidance on Data
Protection laws governed by the EU</para>
<para>Depletion of IPv4 Addresses:
http://www.internetsociety.org/deploy360/blog/2014/05/goodbye-ipv4-iana-starts-allocating-final-address-blocks/Article
describing how IPv4 addresses and the migration to IPv6 is
inevitable</para>
<para>Ethernet Switch Reliability:
http://www.garrettcom.com/techsupport/papers/ethernet_switch_reliability.pdf
Research white paper on Ethernet Switch reliability</para>
<para>Financial Industry Regulatory Authority:
http://www.finra.org/Industry/Regulation/FINRARules/ Requirements
of the Financial Industry Regulatory Authority in the USA</para>
<para>Image Service property keys:
http://docs.openstack.org/cli-reference/content/chapter_cli-glance-property.html Glance
API property keys allows the administrator to attach custom
characteristics to images</para>
<para>LibGuestFS Documentation: http://libguestfs.orgOfficial
LibGuestFS documentation</para>
<para>Logging and Monitoring
http://docs.openstack.org/openstack-ops/content/logging_monitoring.html Official
OpenStack Operations documentation</para>
<para>ManageIQ Cloud Management Platform: http://manageiq.org/ An
Open Source Cloud Management Platform for managing multiple
clouds</para>
<para>N-Tron Network Availability:
http://www.n-tron.com/pdf/network_availability.pdfResearch
white paper on network availability</para>
<para>Nested KVM:
http://davejingtian.org/2014/03/30/nested-kvm-just-for-funBlog
Post on how to nest KVM under KVM.</para>
<para>Open Compute Project: http://www.opencompute.org/The Open
Compute Project Foundations mission is to design and enable the
delivery of the most efficient server, storage and data center
hardware designs for scalable computing.</para>
<para>OpenStack Flavors:
http://docs.openstack.org/openstack-ops/content/flavors.htmlOfficial
OpenStack documentation</para>
<para>OpenStack High Availability Guide:
http://docs.openstack.org/high-availability-guide/content/Information
on how to provide redundancy for the OpenStack components</para>
<para>OpenStack Hypervisor Support
Matrix:https://wiki.openstack.org/wiki/HypervisorSupportMatrix
Matrix of supported hypervisors and capabilities when used with
OpenStack</para>
<para>OpenStack Object Store (Swift) Replication Reference:
http://docs.openstack.org/developer/swift/replication_network.html
Developer documentation of Swift replication</para>
<para>OpenStack Operations Guide:
http://docs.openstack.org/openstack-ops/The OpenStack Operations
Guide provides information on setting up and installing
OpenStack</para>
<para>OpenStack Security
Guide:http://docs.openstack.org/security-guide/The OpenStack
Security Guide provides information on securing OpenStack
deployments</para>
<para>OpenStack Training Marketplace:
http://www.openstack.org/marketplace/trainingThe OpenStack Market
for training and Vendors providing training on OpenStack.</para>
<para>PCI passthrough:
https://wiki.openstack.org/wiki/Pci_passthrough#How_to_check_PCI_status_with_PCI_api_paches
The PCI api patches extends the servers/os-hypervisor to show PCI
information for instance and compute node, and also provides a
resource endpoint to show PCI information.</para>
<para>TripleO: https://wiki.openstack.org/wiki/TripleOTripleO is a
program aimed at installing, upgrading and operating OpenStack
clouds using OpenStack's own cloud facilities as the
foundation.</para>
<para>
<link
xlink:href="http://ec.europa.eu/justice/data-protection/">Data
Protection framework of the European Union</link>: Guidance on
Data Protection laws governed by the EU.
</para>
<para>
<link
xlink:href="http://www.internetsociety.org/deploy360/blog/2014/05/goodbye-ipv4-iana-starts-allocating-final-address-blocks/Article">Depletion
of IPv4 Addresses</link>: describing how IPv4 addresses and the
migration to IPv6 is inevitable.
</para>
<para>
<link
xlink:href="http://www.garrettcom.com/techsupport/papers/ethernet_switch_reliability.pdf">Ethernet
Switch Reliability</link>: Research white paper on Ethernet Switch
reliability.
</para>
<para>
<link
xlink:href="http://www.finra.org/Industry/Regulation/FINRARules/">Financial
Industry Regulatory Authority</link>: Requirements of the
Financial Industry Regulatory Authority in the USA.
</para>
<para>
<link
xlink:href="http://docs.openstack.org/cli-reference/content/chapter_cli-glance-property.html">Image
Service property keys</link>: Glance API property keys allows the
administrator to attach custom characteristics to images.
</para>
<para>
<link xlink:href="http://libguestfs.org">LibGuestFS
Documentation</link>: Official LibGuestFS documentation.
</para>
<para>
<link
xlink:href="http://docs.openstack.org/openstack-ops/content/logging_monitoring.html">Logging
and Monitoring</link>: Official OpenStack Operations
documentation.
</para>
<para>
<link xlink:href="http://manageiq.org/">ManageIQ Cloud Management
Platform</link>: An Open Source Cloud Management Platform for
managing multiple clouds.
</para>
<para>
<link
xlink:href="http://www.n-tron.com/pdf/network_availability.pdf">N-Tron
Network Availability</link>: Research white paper on network
availability.
</para>
<para>
<link
xlink:href="http://davejingtian.org/2014/03/30/nested-kvm-just-for-funBlog">Nested
KVM</link>: Post on how to nest KVM under KVM.
</para>
<para>
<link xlink:href="http://www.opencompute.org/">Open Compute
Project</link>: The Open Compute Project Foundations mission is
to design and enable the delivery of the most efficient server,
storage and data center hardware designs for scalable
computing.
</para>
<para>
<link
xlink:href="http://docs.openstack.org/openstack-ops/content/flavors.html">OpenStack
Flavors</link>: Official OpenStack documentation.
</para>
<para>
<link
xlink:href="http://docs.openstack.org/high-availability-guide/content/">OpenStack
High Availability Guide</link>: Information on how to provide
redundancy for the OpenStack components.
</para>
<para>
<link
xlink:href="https://wiki.openstack.org/wiki/HypervisorSupportMatrix">OpenStack
Hypervisor Support Matrix</link>: Matrix of supported hypervisors
and capabilities when used with OpenStack.
</para>
<para>
<link
xlink:href="http://docs.openstack.org/developer/swift/replication_network.html">OpenStack
Object Store (Swift) Replication Reference</link>: Developer
documentation of Swift replication.
</para>
<para>
<link
xlink:href="http://docs.openstack.org/openstack-ops/">OpenStack
Operations Guide</link>: The OpenStack Operations Guide provides
information on setting up and installing OpenStack.
</para>
<para>
<link
xlink:href="http://docs.openstack.org/security-guide/">OpenStack
Security Guide</link>: The OpenStack Security Guide provides
information on securing OpenStack deployments.
</para>
<para>
<link
xlink:href="http://www.openstack.org/marketplace/training">OpenStack
Training Marketplace</link>: The OpenStack Market for training and
Vendors providing training on OpenStack.
</para>
<para>
<link
xlink:href="https://wiki.openstack.org/wiki/Pci_passthrough#How_to_check_PCI_status_with_PCI_api_paches">PCI
passthrough</link>: The PCI API patches extend the
servers/os-hypervisor to show PCI information for instance and
compute node, and also provides a resource endpoint to show PCI
information.
</para>
<para>
<link
xlink:href="https://wiki.openstack.org/wiki/TripleO">TripleO</link>:
TripleO is a program aimed at installing, upgrading and operating
OpenStack clouds using OpenStack's own cloud facilities as the
foundation.
</para>
</chapter>

View File

@ -1,4 +1,8 @@
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE section [
<!ENTITY % openstack SYSTEM "../../common/entities/openstack.ent">
%openstack;
]>
<section xmlns="http://docbook.org/ns/docbook"
xmlns:xi="http://www.w3.org/2001/XInclude"
xmlns:xlink="http://www.w3.org/1999/xlink"
@ -54,12 +58,13 @@
<para>1600 = (16 x (number of physical cores)) / 2</para>
</listitem>
<listitem>
<para>storage required = 50 GB x 1600</para>
<para>storage required = 50&nbsp;GB x 1600</para>
</listitem>
</itemizedlist>
<para>On the surface, the equations reveal the need for 200
physical cores and 80 TB of storage for
/var/lib/nova/instances/. However, it is also important to
physical cores and 80&nbsp;TB of storage for
<filename>/var/lib/nova/instances/</filename>. However,
it is also important to
look at patterns of usage to estimate the load that the API
services, database servers, and queue servers are likely to
encounter.</para>
@ -94,12 +99,8 @@
(CPU/core).</para>
<para>The cloud resource calculator is a useful tool in examining
the impacts of different hardware and instance load outs. It
is available at:</para>
<itemizedlist>
<listitem>
<para>https://github.com/noslzzp/cloud-resource-calculator/blob/master/cloud-resource-calculator.ods</para>
</listitem>
</itemizedlist>
is available at: <link xlink:href="https://github.com/noslzzp/cloud-resource-calculator/blob/master/cloud-resource-calculator.ods">https://github.com/noslzzp/cloud-resource-calculator/blob/master/cloud-resource-calculator.ods</link>
</para>
<section xml:id="expansion-planning-compute-focus">
<title>Expansion planning</title>
<para>A key challenge faced when planning the expansion of cloud
@ -144,7 +145,7 @@
workloads with both Hyper-Threading on and off can help
determine what is more appropriate in any particular
case.</para>
<para>If the Libvirt/KVM Hypervisor driver are the intended use
<para>If the Libvirt/KVM hypervisor driver are the intended use
cases, then the CPUs used in the compute nodes must support
virtualization by way of the VT-x extensions for Intel chips
and AMD-v extensions for AMD chips to provide full
@ -408,7 +409,7 @@
processing, this cloud will utilize mainly memory or CPU, so
the need for add-on storage to each instance is not a likely
requirement. This does not mean the OpenStack Block Storage
service (Cinder) will not be used in the infrastructure, but
service (cinder) will not be used in the infrastructure, but
typically it will not be used as a central component.</para>
<itemizedlist>
<listitem>