Fix broken links
Change-Id: I5787531c3034c070bbdff6f1b904f391b40f2031
This commit is contained in:
parent
fb6fc0df5b
commit
d647a8d0d9
|
@ -45,7 +45,7 @@ facilitator Adam Hyde. Without his tireless support and encouragement,
|
|||
we would have thought a book of this scope was impossible in five days.
|
||||
Adam has proven the book sprint method effectively again and again. He
|
||||
creates both tools and faith in collaborative authoring at
|
||||
`www.booksprints.net <http://www.booksprints.net/>`_.
|
||||
`www.booksprints.net <https://www.booksprints.net/>`_.
|
||||
|
||||
We couldn't have pulled it off without so much supportive help and
|
||||
encouragement.
|
||||
|
|
|
@ -213,10 +213,10 @@ its lease and all of the sudden I found a bunch of OpenStack and dnsmasq
|
|||
discussions that were identical to the problem we were seeing!
|
||||
|
||||
`Problem with Heavy Network IO and
|
||||
Dnsmasq <http://www.gossamer-threads.com/lists/openstack/operators/18197>`_.
|
||||
Dnsmasq <https://www.gossamer-threads.com/lists/openstack/operators/18197>`_.
|
||||
|
||||
`instances losing IP address while running, due to No
|
||||
DHCPOFFER <http://www.gossamer-threads.com/lists/openstack/dev/14696>`_.
|
||||
DHCPOFFER <https://www.gossamer-threads.com/lists/openstack/dev/14696>`_.
|
||||
|
||||
Seriously, Google.
|
||||
|
||||
|
@ -245,7 +245,7 @@ Disappearing Images
|
|||
At the end of 2012, Cybera (a nonprofit with a mandate to oversee the
|
||||
development of cyberinfrastructure in Alberta, Canada) deployed an
|
||||
updated OpenStack cloud for their `DAIR
|
||||
project <http://www.canarie.ca/cloud/>`_. A few days into
|
||||
project <https://www.canarie.ca/cloud/>`_. A few days into
|
||||
production, a compute node locks up. Upon rebooting the node, I checked
|
||||
to see what instances were hosted on that node so I could boot them on
|
||||
behalf of the customer. Luckily, only one instance.
|
||||
|
|
|
@ -16,14 +16,13 @@ OpenStack
|
|||
|
||||
- `OpenStack Administrator Guide <https://docs.openstack.org/admin-guide/>`_
|
||||
|
||||
- `OpenStack Cloud Computing Cookbook (Packt
|
||||
Publishing) <http://www.packtpub.com/openstack-cloud-computing-cookbook-second-edition/book>`_
|
||||
- `OpenStack Cloud Computing Cookbook <https://openstackcookbook.com/>`_
|
||||
|
||||
Cloud (General)
|
||||
~~~~~~~~~~~~~~~
|
||||
|
||||
- `The NIST Definition of Cloud
|
||||
Computing <http://nvlpubs.nist.gov/nistpubs/Legacy/SP/nistspecialpublication800-145.pdf>`_
|
||||
Computing <https://nvlpubs.nist.gov/nistpubs/Legacy/SP/nistspecialpublication800-145.pdf>`_
|
||||
|
||||
Python
|
||||
~~~~~~
|
||||
|
@ -34,29 +33,29 @@ Networking
|
|||
~~~~~~~~~~
|
||||
|
||||
- `TCP/IP Illustrated, Volume 1: The Protocols, 2/E
|
||||
(Pearson) <http://www.pearsonhighered.com/educator/product/TCPIP-Illustrated-Volume-1-The-Protocols/9780321336316.page>`_
|
||||
(Pearson) <https://www.pearsonhighered.com/educator/product/TCPIP-Illustrated-Volume-1-The-Protocols/9780321336316.page>`_
|
||||
|
||||
- `The TCP/IP Guide (No Starch
|
||||
Press) <http://www.nostarch.com/tcpip.htm>`_
|
||||
Press) <https://www.nostarch.com/tcpip.htm>`_
|
||||
|
||||
- `A tcpdump Tutorial and
|
||||
Primer <http://danielmiessler.com/study/tcpdump/>`_
|
||||
Primer <https://danielmiessler.com/study/tcpdump/>`_
|
||||
|
||||
Systems Administration
|
||||
~~~~~~~~~~~~~~~~~~~~~~
|
||||
|
||||
- `UNIX and Linux Systems Administration Handbook (Prentice
|
||||
Hall) <http://www.admin.com/>`_
|
||||
Hall) <https://www.admin.com/>`_
|
||||
|
||||
Virtualization
|
||||
~~~~~~~~~~~~~~
|
||||
|
||||
- `The Book of Xen (No Starch
|
||||
Press) <http://www.nostarch.com/xen.htm>`_
|
||||
Press) <https://nostarch.com/releases/xen.html>`_
|
||||
|
||||
Configuration Management
|
||||
~~~~~~~~~~~~~~~~~~~~~~~~
|
||||
|
||||
- `Puppet Labs Documentation <http://docs.puppetlabs.com/>`_
|
||||
- `Puppet Labs Documentation <https://docs.puppet.com/>`_
|
||||
|
||||
- `Pro Puppet (Apress) <http://www.apress.com/9781430230571>`_
|
||||
- `Pro Puppet (Apress) <https://www.apress.com/9781430230571>`_
|
||||
|
|
|
@ -40,13 +40,8 @@ to 10 percent back-ported code from trunk and modifications.
|
|||
Resources
|
||||
---------
|
||||
|
||||
- `OpenStack.org case
|
||||
study <https://www.openstack.org/user-stories/nectar/>`_
|
||||
|
||||
- `NeCTAR-RC GitHub <https://github.com/NeCTAR-RC/>`_
|
||||
|
||||
- `NeCTAR website <https://www.nectar.org.au/>`_
|
||||
|
||||
MIT CSAIL
|
||||
~~~~~~~~~
|
||||
|
||||
|
@ -110,7 +105,7 @@ based networks.
|
|||
Resources
|
||||
---------
|
||||
|
||||
- `CSAIL homepage <http://www.csail.mit.edu/>`_
|
||||
- `CSAIL homepage <https://www.csail.mit.edu/>`_
|
||||
|
||||
DAIR
|
||||
~~~~
|
||||
|
@ -151,7 +146,7 @@ controller.
|
|||
Resources
|
||||
---------
|
||||
|
||||
- `DAIR homepage <http://www.canarie.ca/cloud/>`__
|
||||
- `DAIR homepage <https://www.canarie.ca/cloud/>`__
|
||||
|
||||
CERN
|
||||
~~~~
|
||||
|
@ -183,7 +178,7 @@ Resources
|
|||
---------
|
||||
|
||||
- `OpenStack in Production: A tale of 3 OpenStack
|
||||
Clouds <http://openstack-in-production.blogspot.de/2013/09/a-tale-of-3-openstack-clouds-50000.html>`_
|
||||
Clouds <https://openstack-in-production.blogspot.de/2013/09/a-tale-of-3-openstack-clouds-50000.html>`_
|
||||
|
||||
- `Review of CERN Data Centre
|
||||
Infrastructure <http://cds.cern.ch/record/1457989/files/chep%202012%20CERN%20infrastructure%20final.pdf?version=1>`_
|
||||
|
|
|
@ -182,8 +182,8 @@ Documentation feedback
|
|||
|
||||
To provide feedback on documentation, join our IRC channel ``#openstack-doc``
|
||||
on the Freenode IRC network, or `report a bug in Launchpad
|
||||
<https://bugs.launchpad.net/openstack/+filebug>`_ and choose the particular
|
||||
project that the documentation is a part of.
|
||||
<https://bugs.launchpad.net/openstack/+filebug/+login>`_ and choose
|
||||
the particular project that the documentation is a part of.
|
||||
|
||||
The OpenStack IRC channel
|
||||
~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||
|
@ -194,7 +194,7 @@ feedback for urgent and pressing issues. To install an IRC client or use
|
|||
a browser-based client, go to
|
||||
`https://webchat.freenode.net/ <https://webchat.freenode.net>`_. You can
|
||||
also use `Colloquy <http://colloquy.info/>`_ (Mac OS X),
|
||||
`mIRC <http://www.mirc.com/>`_ (Windows),
|
||||
`mIRC <https://www.mirc.com/>`_ (Windows),
|
||||
or XChat (Linux). When you are in the IRC channel
|
||||
and want to share code or command output, the generally accepted method
|
||||
is to use a Paste Bin. The OpenStack project has one at `Paste
|
||||
|
|
|
@ -8,14 +8,14 @@ Abstract
|
|||
This guide provides information about operating OpenStack clouds.
|
||||
|
||||
We recommend that you turn to the `Installation Tutorials and Guides
|
||||
<https://docs.openstack.org/project-install-guide/ocata/>`_,
|
||||
<https://docs.openstack.org/install/>`_,
|
||||
which contains a step-by-step guide on how to manually install the
|
||||
OpenStack packages and dependencies on your cloud.
|
||||
|
||||
While it is important for an operator to be familiar with the steps
|
||||
involved in deploying OpenStack, we also strongly encourage you to
|
||||
evaluate `OpenStack deployment tools
|
||||
<https://docs.openstack.org/developer/openstack-projects.html>`_
|
||||
<https://docs.openstack.org/rocky/projects.html>`_
|
||||
and configuration-management tools, such as :term:`Puppet` or
|
||||
:term:`Chef`, which can help automate this deployment process.
|
||||
|
||||
|
|
|
@ -34,7 +34,7 @@ different tuning requirements.
|
|||
<https://docs.openstack.org/ocata/config-reference/compute/hypervisors.html>`__.
|
||||
You can see a matrix of the various features in OpenStack Compute
|
||||
(nova) hypervisor drivers at the `Hypervisor support matrix
|
||||
page <https://docs.openstack.org/developer/nova/support-matrix.html>`_.
|
||||
page <ttps://docs.openstack.org/nova/latest/user/support-matrix.html>`_.
|
||||
|
||||
The point we are trying to make here is that just because an option
|
||||
exists doesn't mean that option is relevant to your driver choices.
|
||||
|
@ -146,6 +146,6 @@ quickly based on the closest data center. You configure a default region
|
|||
with one zone for each cluster, but be sure your network (WAN) can
|
||||
handle the additional request and response load between zones as you add
|
||||
more zones and build a ring that handles more zones. Refer to
|
||||
`Geographically Distributed Clusters
|
||||
<https://docs.openstack.org/developer/swift/admin_guide.html#geographically-distributed-clusters>`_
|
||||
`Geographically Distributed Swift Considerations
|
||||
<https://docs.openstack.org/swift/latest/admin_guide.html#geographically-distributed-swift-considerations>`_
|
||||
in the documentation for additional information.
|
||||
|
|
|
@ -150,7 +150,7 @@ load-balancing method (DNS round robin, hardware load balancer, or
|
|||
software such as Pound or HAProxy). One caveat with dashboard is the VNC
|
||||
proxy, which uses the WebSocket protocol— something that an L7 load
|
||||
balancer might struggle with. See also `Horizon session storage
|
||||
<https://docs.openstack.org/developer/horizon/topics/deployment.html#session-storage>`_.
|
||||
<https://docs.openstack.org/horizon/latest/admin/sessions.html>`_.
|
||||
|
||||
You can configure some services, such as ``nova-api`` and
|
||||
``glance-api``, to use multiple processes by changing a flag in their
|
||||
|
|
|
@ -5,4 +5,4 @@ Customizing the Dashboard (Horizon)
|
|||
The dashboard is based on the Python
|
||||
`Django <https://www.djangoproject.com/>`_ web application framework.
|
||||
To know how to build your Dashboard, see `Building a Dashboard using Horizon
|
||||
<https://docs.openstack.org/developer/horizon/tutorials/dashboard.html>`_.
|
||||
<https://docs.openstack.org/horizon/latest/>`_.
|
||||
|
|
|
@ -8,4 +8,4 @@ builds an OpenStack development environment for you. You use it to
|
|||
create such an environment for developing a new feature.
|
||||
|
||||
For more information on installing DevStack, see the
|
||||
`DevStack <https://docs.openstack.org/developer/devstack/>`_ website.
|
||||
`DevStack <https://docs.openstack.org/devstack/latest/>`_ website.
|
||||
|
|
|
@ -3,9 +3,9 @@ Customizing Object Storage (Swift) Middleware
|
|||
=============================================
|
||||
|
||||
OpenStack Object Storage, known as swift when reading the code, is based
|
||||
on the Python `Paste <http://pythonpaste.org/>`_ framework. The best
|
||||
introduction to its architecture is `A Do-It-Yourself
|
||||
Framework <http://pythonpaste.org/do-it-yourself-framework.html>`_.
|
||||
on the Python `Paste <https://pypi.org/project/Paste/>`_ framework.
|
||||
The best introduction to its architecture is on `Read The
|
||||
Docs <https://paste.readthedocs.io/en/latest/>`_.
|
||||
Because of the swift project's use of this framework, you are able to
|
||||
add features to a project by placing some custom code in a project's
|
||||
pipeline without having to change any of the core code.
|
||||
|
|
|
@ -217,9 +217,9 @@ Common areas of regulation include:
|
|||
This is an example of such legal frameworks:
|
||||
|
||||
Data storage regulations in Europe are currently driven by provisions of
|
||||
the `Data protection framework <http://ec.europa.eu/justice/data-protection/>`_.
|
||||
the `Data protection board <https://edpb.europa.eu/>`_.
|
||||
`Financial Industry Regulatory Authority
|
||||
<http://www.finra.org/Industry/Regulation/FINRARules/>`_ works on this in
|
||||
<http://finra.complinet.com/>`_ works on this in
|
||||
the United States.
|
||||
|
||||
Privacy and security are spread over different industry-specific laws and
|
||||
|
@ -262,7 +262,7 @@ Corrective controls:
|
|||
system is an example of a corrective control.
|
||||
|
||||
For more information, see See also `NIST Special Publication 800-53
|
||||
<https://web.nvd.nist.gov/view/800-53/home>`_.
|
||||
<https://web.nvd.nist.gov/view/800-53/>`_.
|
||||
|
||||
|
||||
Software licensing
|
||||
|
|
|
@ -18,7 +18,7 @@ tab with a :guilabel:`System Panel` and an :guilabel:`Identity` tab.
|
|||
These interfaces give you access to system information and usage as
|
||||
well as to settings for configuring what
|
||||
end users can do. Refer to the `OpenStack Administrator
|
||||
Guide <https://docs.openstack.org/admin-guide/dashboard.html>`__ for
|
||||
Guide <https://docs.openstack.org/latest/admin/>`__ for
|
||||
detailed how-to information about using the dashboard as an admin user.
|
||||
|
||||
Command-Line Tools
|
||||
|
@ -40,9 +40,8 @@ Install OpenStack command-line clients
|
|||
--------------------------------------
|
||||
|
||||
For instructions on installing, upgrading, or removing command-line clients,
|
||||
see the `Install the OpenStack command-line clients
|
||||
<https://docs.openstack.org/user-guide/common/cli-install-openstack-command-line-clients.html>`_
|
||||
section in OpenStack End User Guide.
|
||||
see the `Install the OpenStack command-line client
|
||||
<https://docs.openstack.org/python-openstackclient/latest/>`_.
|
||||
|
||||
.. note::
|
||||
|
||||
|
@ -209,7 +208,7 @@ Underlying the use of the command-line tools is the OpenStack API, which
|
|||
is a RESTful API that runs over HTTP. There may be cases where you want
|
||||
to interact with the API directly or need to use it because of a
|
||||
suspected bug in one of the CLI tools. The best way to do this is to use
|
||||
a combination of `cURL <http://curl.haxx.se/>`_ and another tool,
|
||||
a combination of `cURL <https://curl.haxx.se/>`_ and another tool,
|
||||
such as `jq <http://stedolan.github.io/jq/>`_, to parse the JSON from
|
||||
the responses.
|
||||
|
||||
|
@ -589,5 +588,5 @@ Summary
|
|||
We hope you have enjoyed this quick tour of your working environment,
|
||||
including how to interact with your cloud and extract useful
|
||||
information. From here, you can use the `OpenStack Administrator
|
||||
Guide <https://docs.openstack.org/admin-guide/>`_ as your
|
||||
Guide <https://docs.openstack.org/latest/admin/>`_ as your
|
||||
reference for all of the command-line functionality in your cloud.
|
||||
|
|
|
@ -16,14 +16,14 @@ configuration options) in a version-controlled repository.
|
|||
not recommend a specific one. The most popular ones in the OpenStack
|
||||
community are:
|
||||
|
||||
* `Puppet <https://puppetlabs.com/>`_, with available `OpenStack
|
||||
* `Puppet <https://puppet.com/>`_, with available `OpenStack
|
||||
Puppet modules <https://github.com/puppetlabs/puppetlabs-openstack>`_
|
||||
* `Ansible <https://www.ansible.com/>`_, with `OpenStack Ansible
|
||||
<https://github.com/openstack/openstack-ansible>`_
|
||||
* `Chef <http://www.getchef.com/chef/>`_, with available `OpenStack Chef
|
||||
* `Chef <https://www.chef.io/chef/>`_, with available `OpenStack Chef
|
||||
recipes <https://github.com/openstack/openstack-chef-repo>`_
|
||||
|
||||
Other newer configuration tools include `Juju <https://juju.ubuntu.com/>`_
|
||||
Other newer configuration tools include `Juju <https://jujucharms.com/>`_
|
||||
and `Salt <http://www.saltstack.com/>`_; and more mature configuration
|
||||
management tools include `CFEngine <http://cfengine.com/>`_ and `Bcfg2
|
||||
management tools include `CFEngine <https://cfengine.com/>`_ and `Bcfg2
|
||||
<http://bcfg2.org/>`_.
|
||||
|
|
|
@ -48,4 +48,4 @@ As your cloud grows, MySQL is utilized more and more. If you suspect
|
|||
that MySQL might be becoming a bottleneck, you should start researching
|
||||
MySQL optimization. The MySQL manual has an entire section dedicated to
|
||||
this topic: `Optimization Overview
|
||||
<http://dev.mysql.com/doc/refman/5.5/en/optimize-overview.html>`_.
|
||||
<https://dev.mysql.com/doc/refman/5.5/en/optimize-overview.html>`_.
|
||||
|
|
|
@ -90,13 +90,11 @@ The Telemetry service (:term:`ceilometer`) collects
|
|||
metering and event data relating to OpenStack services. Data collected
|
||||
by the Telemetry service could be used for billing. Depending on
|
||||
deployment configuration, collected data may be accessible to users
|
||||
based on the deployment configuration. The Telemetry service provides a
|
||||
REST API documented at `ceilometer V2 Web API
|
||||
<https://docs.openstack.org/developer/ceilometer/webapi/v2.html>`_. You can
|
||||
read more about the module in the `OpenStack Administrator
|
||||
Guide <https://docs.openstack.org/admin-guide/telemetry.html>`_ or
|
||||
in the `developer
|
||||
documentation <https://docs.openstack.org/developer/ceilometer>`_.
|
||||
based on the deployment configuration. You can
|
||||
read more about the module in the `Ceilometer Administrator
|
||||
Guide <https://docs.openstack.org/ceilometer/latest/admin/index.html>`_ or
|
||||
in the `Ceilometer Contributor
|
||||
Guide <https://docs.openstack.org/ceilometer/latest/contributor/index.html>`_.
|
||||
|
||||
OpenStack Specific Resources
|
||||
~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||
|
|
|
@ -98,7 +98,7 @@ software defined networking (SDN) hardware or plug-ins that use Linux
|
|||
native facilities on your hosts, such as Open vSwitch or Linux Bridge.
|
||||
|
||||
The networking chapter of the `OpenStack Administrator
|
||||
Guide <https://docs.openstack.org/admin-guide/networking.html>`_
|
||||
Guide <https://docs.openstack.org/admin-guide/>`_
|
||||
shows a variety of networking scenarios and their connection paths. The
|
||||
purpose of this section is to give you the tools to troubleshoot the
|
||||
various components involved however they are plumbed together in your
|
||||
|
@ -473,7 +473,7 @@ is to use ``tcpdump``. We recommended using ``tcpdump`` at several
|
|||
points along the network path to correlate where a problem might be. If
|
||||
you prefer working with a GUI, either live or by using a ``tcpdump``
|
||||
capture, check out
|
||||
`Wireshark <http://www.wireshark.org/>`_.
|
||||
`Wireshark <https://www.wireshark.org/>`_.
|
||||
|
||||
For example, run the following command:
|
||||
|
||||
|
@ -920,7 +920,7 @@ Troubleshooting Open vSwitch
|
|||
Open vSwitch, as used in the previous OpenStack Networking examples is a
|
||||
full-featured multilayer virtual switch licensed under the open source
|
||||
Apache 2.0 license. Full documentation can be found at `the project's
|
||||
website <http://openvswitch.org/>`_. In practice, given the preceding
|
||||
website <http://www.openvswitch.org/>`_. In practice, given the preceding
|
||||
configuration, the most common issues are being sure that the required
|
||||
bridges (``br-int``, ``br-tun``, and ``br-ex``) exist and have the
|
||||
proper ports connected to them.
|
||||
|
@ -1091,5 +1091,5 @@ analysis and diagnostic system that provides a completely automated service
|
|||
for verifying and diagnosing the networking functionality provided by OVS.
|
||||
|
||||
Additionally, you can refer to
|
||||
`neutron debug <https://docs.openstack.org/cli-reference/neutron-debug.html>`_
|
||||
`neutron client <https://docs.openstack.org/python-neutronclient/latest/>`_
|
||||
for more options.
|
||||
|
|
|
@ -241,9 +241,9 @@ you build your use case and your deployment plan.
|
|||
For further research about OpenStack deployment, investigate the
|
||||
supported and documented preconfigured, prepackaged installers for
|
||||
OpenStack from companies such as
|
||||
`Canonical <https://www.ubuntu.com/cloud/openstack>`_,
|
||||
`Cisco <http://www.cisco.com/c/en/us/solutions/data-center-virtualization/openstack-at-cisco/index.html>`_,
|
||||
`Cloudscaling <http://www.cloudscaling.com>`_,
|
||||
`Canonical <https://www.ubuntu.com/openstack>`_,
|
||||
`Cisco <https://www.cisco.com/c/en/us/solutions/data-center-virtualization/openstack-at-cisco/index.html>`_,
|
||||
`Cloudscaling <http://cloudscaling.com/blog/>`_,
|
||||
`IBM <http://www-03.ibm.com/software/products/en/ibm-cloud-orchestrator>`_,
|
||||
`Metacloud <http://www.cisco.com/c/en/us/products/cloud-systems-management/metacloud/index.html>`_,
|
||||
`Mirantis <https://www.mirantis.com>`_,
|
||||
|
|
|
@ -96,7 +96,7 @@ Watch the network
|
|||
To set up the test environment, you can use one of several methods:
|
||||
|
||||
- Do a full manual install by using the `Installation Tutorials and Guides
|
||||
<https://docs.openstack.org/project-install-guide/ocata/>`_ for
|
||||
<https://docs.openstack.org/rocky/install/>`_ for
|
||||
your platform. Review the final configuration files and installed
|
||||
packages.
|
||||
|
||||
|
@ -177,7 +177,7 @@ Upgrade process
|
|||
This section describes the process to upgrade a basic OpenStack
|
||||
deployment based on the basic two-node architecture in the `Installation
|
||||
Tutorials and Guides
|
||||
<https://docs.openstack.org/project-install-guide/ocata/>`_. All
|
||||
<https://docs.openstack.org/rocky/install/>`_. All
|
||||
nodes must run a supported distribution of Linux with a recent kernel
|
||||
and the current release packages.
|
||||
|
||||
|
@ -188,23 +188,21 @@ Refer to the following upgrade notes for information on upgrading specific
|
|||
OpenStack services:
|
||||
|
||||
* `Networking service (neutron) upgrades
|
||||
<https://docs.openstack.org/developer/neutron/devref/upgrade.html>`_
|
||||
<https://docs.openstack.org/neutron/latest/contributor/internals/upgrade.html>`_
|
||||
* `Compute service (nova) upgrades
|
||||
<https://docs.openstack.org/developer/nova/upgrade.html>`_
|
||||
<https://docs.openstack.org/nova/latest/user/upgrade.html>`_
|
||||
* `Identity service (keystone) upgrades
|
||||
<https://docs.openstack.org/developer/keystone/upgrading.html>`_
|
||||
<https://docs.openstack.org/keystone/latest/admin/identity-upgrading.html>`_
|
||||
* `Block Storage service (cinder) upgrades
|
||||
<https://docs.openstack.org/developer/cinder/upgrade.html>`_
|
||||
* `Image service (glance) zero downtime database upgrades
|
||||
<https://docs.openstack.org/developer/glance/db.html#zero-downtime-database-upgrades>`_
|
||||
* `Image service (glance) rolling upgrades
|
||||
<https://docs.openstack.org/developer/glance/rollingupgrades.html>`_
|
||||
<https://docs.openstack.org/cinder/latest/upgrade.html>`_
|
||||
* `Image service (glance) database upgrades
|
||||
<https://docs.openstack.org/glance/latest/admin/db.html>`_
|
||||
* `Bare Metal service (ironic) upgrades
|
||||
<https://docs.openstack.org/developer/ironic/deploy/upgrade-guide.html>`_
|
||||
<https://docs.openstack.org/ironic/latest/admin/upgrade-guide.html>`_
|
||||
* `Object Storage service (swift) upgrades
|
||||
<https://docs.openstack.org/developer/swift/overview_policies.html#upgrade-policy>`_
|
||||
<https://docs.openstack.org/swift/latest/overview_policies.html#upgrading-and-confirming-functionality>`_
|
||||
* `Telemetry service (ceilometer) upgrades
|
||||
<https://docs.openstack.org/developer/ceilometer/install/upgrade.html>`_
|
||||
<https://docs.openstack.org/ceilometer/ocata/install/upgrade.html>`_
|
||||
|
||||
Prerequisites
|
||||
-------------
|
||||
|
@ -253,7 +251,7 @@ Perform a backup
|
|||
|
||||
Consider updating your SQL server configuration as described in the
|
||||
`Installation Tutorials and Guides
|
||||
<https://docs.openstack.org/project-install-guide/ocata/>`_.
|
||||
<https://docs.openstack.org/rocky/install/>`_.
|
||||
|
||||
Manage repositories
|
||||
-------------------
|
||||
|
|
|
@ -883,7 +883,7 @@ The default configuration of the Shared File Systems service depends on
|
|||
the back-end driver the admin chooses when starting the Shared File
|
||||
Systems service. For more information about existing back-end drivers,
|
||||
see `Share Backends
|
||||
<https://docs.openstack.org/developer/manila/devref/index.html#share-backends>`__
|
||||
<https://docs.openstack.org/manila/latest/admin/index.html#supported-share-back-ends>`__
|
||||
of Shared File Systems service Developer Guide. For example, in case of
|
||||
OpenStack Block Storage based back-end is used, the Shared File Systems
|
||||
service cares about everything, including VMs, networking, keypairs, and
|
||||
|
@ -907,37 +907,37 @@ large number of operations with shares:
|
|||
* Use security services
|
||||
|
||||
For more information on share management see `Share management
|
||||
<https://docs.openstack.org/admin-guide/shared-file-systems-share-management.html>`__
|
||||
of chapter “Shared File Systems” in OpenStack Administrator Guide.
|
||||
<https://docs.openstack.org/manila/latest/admin/shared-file-systems-share-management.html>`__
|
||||
in OpenStack Manila Administrator Guide.
|
||||
As to Security services, you should remember that different drivers
|
||||
support different authentication methods, while generic driver does not
|
||||
support Security Services at all (see section `Security services
|
||||
<https://docs.openstack.org/admin-guide/shared-file-systems-security-services.html>`__
|
||||
of chapter “Shared File Systems” in OpenStack Administrator Guide).
|
||||
<https://docs.openstack.org/manila/latest/admin/shared-file-systems-security-services.html>`__
|
||||
in OpenStack Manila Administrator Guide).
|
||||
|
||||
You can create a share in a network, list shares, and show information
|
||||
for, update, and delete a specified share. You can also create snapshots
|
||||
of shares (see `Share snapshots
|
||||
<https://docs.openstack.org/admin-guide/shared-file-systems-snapshots.html>`__
|
||||
of chapter “Shared File Systems” in OpenStack Administrator Guide).
|
||||
<https://docs.openstack.org/manila/latest/admin/shared-file-systems-snapshots.html>`__
|
||||
in OpenStack Manila Administrator Guide).
|
||||
|
||||
There are default and specific share types that allow you to filter or
|
||||
choose back-ends before you create a share. Functions and behaviour of
|
||||
share type is similar to Block Storage volume type (see `Share types
|
||||
<https://docs.openstack.org/admin-guide/shared-file-systems-share-types.html>`__
|
||||
of chapter “Shared File Systems” in OpenStack Administrator Guide).
|
||||
<https://docs.openstack.org/manila/latest/admin/shared-file-systems-share-types.html>`__
|
||||
in OpenStack Manila Administrator Guide).
|
||||
|
||||
To help users keep and restore their data, Shared File Systems service
|
||||
provides a mechanism to create and operate snapshots (see `Share snapshots
|
||||
<https://docs.openstack.org/admin-guide/shared-file-systems-snapshots.html>`__
|
||||
of chapter “Shared File Systems” in OpenStack Administrator Guide).
|
||||
<https://docs.openstack.org/manila/latest/admin/shared-file-systems-snapshots.html>`__
|
||||
in OpenStack Manila Administrator Guide).
|
||||
|
||||
A security service stores configuration information for clients for
|
||||
authentication and authorization. Inside Manila a share network can be
|
||||
associated with up to three security types (for detailed information see
|
||||
`Security services
|
||||
<https://docs.openstack.org/admin-guide/shared-file-systems-security-services.html>`__
|
||||
of chapter “Shared File Systems” in OpenStack Administrator Guide):
|
||||
<https://docs.openstack.org/manila/latest/admin/shared-file-systems-security-services.html>`__
|
||||
in OpenStack Manila Administrator Guide).
|
||||
|
||||
* LDAP
|
||||
* Kerberos
|
||||
|
@ -958,16 +958,14 @@ called StandaloneNetworkPlugin is used. In this case, provide network
|
|||
information in the configuration: IP range, network type, and
|
||||
segmentation ID. Also you can add security services to a share network
|
||||
(see section
|
||||
`“Networking” <https://docs.openstack.org/admin-guide/shared-file-systems-networking.html>`__
|
||||
of chapter “Shared File Systems” in OpenStack Administrator Guide).
|
||||
`“Networking” <https://docs.openstack.org/manila/latest/admin/shared-file-systems-networking.html>`__
|
||||
in OpenStack Manila Administrator Guide).
|
||||
|
||||
|
||||
The main idea of consistency groups is to enable you to create snapshots
|
||||
at the exact same point in time from multiple file system shares. Those
|
||||
snapshots can be then used for restoring all shares that were associated
|
||||
with the consistency group (see section `“Consistency
|
||||
groups” <https://docs.openstack.org/admin-guide/shared-file-systems-cgroups.html>`__
|
||||
of chapter “Shared File Systems” in OpenStack Administrator Guide).
|
||||
with the consistency group.
|
||||
|
||||
Shared File System storage allows administrators to set limits and
|
||||
quotas for specific tenants and users. Limits are the resource
|
||||
|
@ -1259,7 +1257,7 @@ specified access rules:
|
|||
|
||||
For the details of features supported by different drivers see
|
||||
`Manila share features support mapping
|
||||
<https://docs.openstack.org/developer/manila/devref/share_back_ends_feature_support_mapping.html>`__
|
||||
<https://docs.openstack.org/manila/latest/admin/index.html#supported-share-back-ends>`__
|
||||
of Manila Developer Guide document.
|
||||
|
||||
Manage Shares
|
||||
|
|
|
@ -284,7 +284,7 @@ We wrote this book to help you:
|
|||
|
||||
We wrote this book in a book sprint, which is a facilitated, rapid
|
||||
development production method for books. For more information, see the
|
||||
`BookSprints site <http://www.booksprints.net/>`_. Your authors cobbled
|
||||
`BookSprints site <https://www.booksprints.net/>`_. Your authors cobbled
|
||||
this book together in five days during February 2013, fueled by caffeine
|
||||
and the best takeout food that Austin, Texas, could offer.
|
||||
|
||||
|
@ -332,7 +332,7 @@ Lorin Hochstein
|
|||
Adam Hyde
|
||||
Adam facilitated this book sprint. He also founded the book sprint
|
||||
methodology and is the most experienced book-sprint facilitator
|
||||
around. See `BookSprints <http://www.booksprints.net>`_ for more
|
||||
around. See `BookSprints <https://www.booksprints.net>`_ for more
|
||||
information. Adam founded FLOSS Manuals—a community of some 3,000
|
||||
individuals developing Free Manuals about Free Software. He is also the
|
||||
founder and project manager for Booktype, an open source project for
|
||||
|
|
Loading…
Reference in New Issue