Fix broken links (dsR8)
Fix and update links. Change-Id: I868b64a8b347d7746f857543f3a75760954ddee9 Signed-off-by: Elisamara Aoki Goncalves <elisamaraaoki.goncalves@windriver.com>
This commit is contained in:
parent
3add90a8f1
commit
ba01686f7a
@ -321,11 +321,8 @@ conditions are in place:
|
||||
|
||||
If the message HEALTH_WARN appears, wait a few minutes and then try
|
||||
again. If the warning condition persists, consult the public
|
||||
documentation for troubleshooting Ceph monitors (for example,
|
||||
`http://docs.ceph.com/docs/master/rados/troubleshooting/troubleshootin
|
||||
g-mon/
|
||||
<http://docs.ceph.com/docs/master/rados/troubleshooting/troubleshootin
|
||||
g-mon/>`__).
|
||||
documentation for troubleshooting Ceph monitors (for example
|
||||
http://docs.ceph.com/docs/master/rados/troubleshooting/troubleshooting-mon/).
|
||||
|
||||
#. Restore the compute (worker) hosts, one at a time.
|
||||
|
||||
|
@ -12,30 +12,30 @@ MIB via |SNMP|.
|
||||
The active alarm table contains a list of all active or set alarms in the
|
||||
system. Each entry in the table includes the following variables:
|
||||
|
||||
- wrsAlarmActiveUuid
|
||||
- wrsAlarmActiveUuid
|
||||
|
||||
- wrsAlarmActiveAlarmId
|
||||
- wrsAlarmActiveAlarmId
|
||||
|
||||
- wrsAlarmActiveEntityInstanceId
|
||||
- wrsAlarmActiveEntityInstanceId
|
||||
|
||||
- wrsAlarmActiveDateAndTime
|
||||
- wrsAlarmActiveDateAndTime
|
||||
|
||||
- wrsAlarmActiveAlarmSeverity
|
||||
- wrsAlarmActiveAlarmSeverity
|
||||
|
||||
- wrsAlarmActiveReasonText
|
||||
- wrsAlarmActiveReasonText
|
||||
|
||||
- wrsAlarmActiveEventType
|
||||
- wrsAlarmActiveEventType
|
||||
|
||||
- wrsAlarmActiveProbableCause
|
||||
- wrsAlarmActiveProbableCause
|
||||
|
||||
- wrsAlarmActiveProposedRepairAction
|
||||
- wrsAlarmActiveProposedRepairAction
|
||||
|
||||
- wrsAlarmActiveServiceAffecting
|
||||
- wrsAlarmActiveServiceAffecting
|
||||
|
||||
- wrsAlarmActiveSuppressionAllowed
|
||||
- wrsAlarmActiveSuppressionAllowed
|
||||
|
||||
|
||||
See https://opendev.org/starlingx/snmp-armada-app/src/branch/master/stx-snmp-helm/centos/docker/stx-snmp/mibs/wrsAlarmMib.mib.txt
|
||||
See https://opendev.org/starlingx/snmp-armada-app/src/branch/master/stx-snmp-helm/docker/stx-snmp/mibs/wrsAlarmMib.mib.txt
|
||||
for alarm details.
|
||||
|
||||
An external |SNMP| Manager can examine the Active Alarm table contents by doing
|
||||
|
@ -39,8 +39,7 @@ PTP-notification consists of two main components:
|
||||
|
||||
- Enables operators to install the **ptp-notification-armada-app**, Sidecar
|
||||
container, and the application supporting the REST API. For more information,
|
||||
see, `https://docs.starlingx.io/api-ref/ptp-notification-armada-app/index.html
|
||||
<https://docs.starlingx.io/api-ref/ptp-notification-armada-app/index.html>`__.
|
||||
see https://docs.starlingx.io/api-ref/ptp-notification-armada-app/index.html.
|
||||
|
||||
- Supports the **ptp4l** module and |PTP| port that is configured in
|
||||
Subordinate mode (Secondary mode).
|
||||
|
@ -34,8 +34,7 @@ You can change the resource pool in several ways:
|
||||
still meets the requirements for your system.
|
||||
|
||||
Complete instructions for adding a worker node are provided in the
|
||||
`StarlingX Installation and Deployment Guide
|
||||
<https://docs.starlingx.io/deploy_install_guides/index.html>`__.
|
||||
:ref:`index-install-r7-8966076f0e81`.
|
||||
|
||||
.. kub-end
|
||||
|
||||
|
@ -48,7 +48,7 @@ Platform OpenStack |CLIs|, using one of the following methods:
|
||||
Keystone user credentials, download an OpenStack RC file (openrc.sh), and
|
||||
use it to source the required environment within your local LDAP user shell
|
||||
. For more information on downloading your OpenStack RC file from Horizon,
|
||||
see, `http://docs.openstack.org <http://docs.openstack.org/>`__.
|
||||
see http://docs.openstack.org.
|
||||
|
||||
#. (Method 2) Add the required environment variables manually into a
|
||||
wrcprc.sh file and use this to source the required environment within your
|
||||
|
@ -112,7 +112,7 @@ Dashboard.
|
||||
defined above for |prod| cluster's |OAM| floating IP.
|
||||
|
||||
|
||||
#. Access the dashboard at https://<fqdn>:32000
|
||||
#. Access the dashboard at `https://<fqdn>:32000`
|
||||
|
||||
Because the certificate created earlier in this procedure was not
|
||||
signed by a trusted |CA|, you will need to acknowledge an insecure
|
||||
|
@ -19,7 +19,7 @@ from a browser.
|
||||
|
||||
Access the Horizon in your browser at the address:
|
||||
|
||||
http://<oam-floating-ip-address>:8080
|
||||
`http://<oam-floating-ip-address>:8080`
|
||||
|
||||
Use the username **admin** and the sysadmin password to log in.
|
||||
|
||||
|
@ -48,8 +48,7 @@ member.
|
||||
of 20 seconds. This means that a Ceph filesystem may not respond to I/O
|
||||
for up to 20 seconds when a storage node or OSD goes out of service.
|
||||
For more information, see the Ceph documentation:
|
||||
`http://docs.ceph.com/docs/master/rados/configuration/mon-osd-interaction
|
||||
<http://docs.ceph.com/docs/master/rados/configuration/mon-osd-interaction>`__.
|
||||
http://docs.ceph.com/docs/master/rados/configuration/mon-osd-interaction.
|
||||
|
||||
Replication groups are shown on the Hosts Inventory page in association
|
||||
with the storage hosts. You can also use the following CLI commands to
|
||||
|
@ -140,4 +140,4 @@ This example requires that:
|
||||
|
||||
#. Access the kuard demo from your browser to inspect and verify that the
|
||||
certificate is signed by LetsEncrypt |CA|. For this example, the URL
|
||||
would be https://kuard.starlingx.mycompany.com.
|
||||
would be `https://kuard.starlingx.mycompany.com`.
|
||||
|
Loading…
Reference in New Issue
Block a user