Fixed missing image titles

Image titles and / or alt text is needed for accessibility. All images
were missing titles. Fixed that.

Author: chabowski

adoc/CaaSP40_DI3X_Install_Guide.adoc

@@ -683,7 +683,7 @@ docker-compose up -d
 
 Finally, you can log in to Portus and configure the registry.
 
-image::portus-registry.png[portus-registry.png,scaledwidth=95%]
+image::portus-registry.png[title="Portus Registry",scaledwidth=95%]
 
 
 ==== Installing and configuring a secure private registry using SUSE Linux Enterprise Server and the SLE-Container-Module
@@ -760,27 +760,27 @@ and already mirroring these products:
 
 ** link:https://scc.suse.com[SCC]
 +
-image::scc-sle.png[scc-sle,scaledwidth=99%]
+image::scc-sle.png[title="SUSE Customer Center: SUSE Linux Enterprise Server Overview",scaledwidth=99%]
 
 ++++
 <?pdfpagebreak?>
 ++++
 
 ** link:https://documentation.suse.com/sles/12-SP4/html/SLES-all/book-smt.html[SMT]
 +
-image::scc-ses.png[scc-ses,scaledwidth=99%]
+image::scc-ses.png[title="SUSE Customer Center: SUSE Enterprise Storage Overview",scaledwidth=99%]
 
 
 * You should already have set up a DNS zone. In our example, where all Data Hub
 components are in the same DNS zone and the same subnet, it should look like:
 +
-image::dns.png[dns,scaledwidth=95%]
+image::dns.png[title="DNS Zone",scaledwidth=95%]
 
 
 * To be as efficient as possible when using interactive shell-scripted infrastructure deployment, 
 we advise to use an advanced terminal client or multiplexer which will allow you to address multiple shells at once:
 +
-image::multi-s-virtinstall.png[multi-s-virtinstall,scaledwidth=95%]
+image::multi-s-virtinstall.png[title="Multiple Shells View",scaledwidth=95%]
 
 
 Now you can create the virtual machines.
@@ -804,11 +804,11 @@ Now you can create the virtual machines.
 ----
 
 +
-image::multi-s-smt.png[multi-s-smt.png,scaledwidth=95%]
+image::multi-s-smt.png[title="Multiple SMT View",scaledwidth=95%]
 
 * Select the SUSE Enterprise Storage 5 extension:
 +
-image::multi-s-addon.png[multi-s-addon.png,scaledwidth=95%]
+image::multi-s-addon.png[title="Selecting SES Extensions on all Nodes",scaledwidth=95%]
 
 * On the hypervisor, you should also be able to route or bridge your upcoming
 SUSE Enterprise Storage 5.5 network segment. In our example, for simplicity, we are
@@ -818,28 +818,28 @@ using the same bridge and network address as our CaaSP cluster:
 * In our example below, each node is powered by 16 GiB of RAM, 4 vCPUs,
 40 GiB for the root disk, and 4 × 20 GiB OSDB disks:
 +
-image::multi-s-default.png[multi-s-default.png,scaledwidth=95%]
+image::multi-s-default.png[title="Selecting System Role on all Nodes",scaledwidth=95%]
 
 * NTP must be configured on each node:
 +
-image::multi-s-ntp.png[multi-s-ntp.png,scaledwidth=95%]
+image::multi-s-ntp.png[title="Configuring NTP on all Nodes",scaledwidth=95%]
 
 * Deselect "AppArmor" and the unnecessary "X" and "GNOME" patterns, but select
 the "SUSE Enterprise Storage" pattern:
 +
-image::multi-s-patterns.png[multi-s-patterns.png,scaledwidth=95%]
+image::multi-s-patterns.png[title="Selecting Patterns on all Nodes",scaledwidth=95%]
 
 * De-activate the firewall on the nodes.
 
 * Start the installation on all nodes:
 +
-image::multi-s-install.png[multi-s-install.png,scaledwidth=95%]
+image::multi-s-install.png[title="Starting Installation on all Nodes",scaledwidth=95%]
 
 * When the nodes have rebooted, log in and finish the network/host name and NTP
 configurations, so that `hostname -f` returns the FQDN of the nodes, and
 `ntpq -p` returns a stratum less than 16:
 +
-image::multi-s-hostname-ntp.png[multi-s-hostname-ntp.png,scaledwidth=95%]
+image::multi-s-hostname-ntp.png[title="Finishing NTP configuration",scaledwidth=95%]
 
 * Using `ssh-keygen` then `ssh-copy-id`, spread your SUSE Enterprise Storage Admin
 node `ssh` public key to all other nodes.
@@ -854,11 +854,11 @@ install `salt-master` and `deepsea`.
 
 * Then, restart `salt-minion` on all nodes, and restart `salt-master` on the Admin Node:
 +
-image::multi-s-salt-install-restart.png[multi-s-salt-install-restart.png,scaledwidth=95%]
+image::multi-s-salt-install-restart.png[title="Installing Salt on all Nodes",scaledwidth=95%]
 
 * Accept the related pending Salt keys:
 +
-image::salt-key.png[salt-key.png,scaledwidth=30%]
+image::salt-key.png[title="Accepting Salt Keys",scaledwidth=30%]
 
 * Verify that `/srv/pillar/ceph/master_minion.sls` points to your Admin Node.
 In our example, it contains the FQDN of our `salt-master`:
@@ -871,15 +871,15 @@ In our example, it contains the FQDN of our `salt-master`:
 # salt-run state.orch ceph.stage.0
 ----
 +
-image::ceph-stage-0.png[ceph-stage-0.png,scaledwidth=90%]
+image::ceph-stage-0.png[title="Preparing the Cluster",scaledwidth=90%]
 
 * Collect information about the nodes:
 +
 ----
 # salt-run state.orch ceph.stage.1
 ----
 +
-image::ceph-stage-1.png[ceph-stage-1.png,scaledwidth=90%]
+image::ceph-stage-1.png[titel="Collecting Information about Nodes",scaledwidth=90%]
 
 * Adapt the file `/srv/pillar/ceph/proposals/policy.cfg` to your needs. In our
 example, where the only deployed service is OpenAttic, it contains the following:
@@ -917,15 +917,15 @@ role-openattic/cluster/ses55-admin.suse-sap.net.sls
 # salt-run state.orch ceph.stage.2
 ----
 +
-image::ceph-stage-2.png[ceph-stage-2.png,scaledwidth=90%]
+image::ceph-stage-2.png[title="Preparing Configuration Files",scaledwidth=90%]
 
 * You can now safely deploy your configuration:
 +
 ----
 # salt-run state.orch ceph.stage.3
 ----
 +
-image::ceph-stage-3.png[ceph-stage-3.png,scaledwidth=90%]
+image::ceph-stage-3.png[title="Deploying Configuration Files",scaledwidth=90%]
 
 * When Stage 3 has completed successfully, check the cluster's health to
 ensure that everything is running properly:
@@ -934,7 +934,7 @@ ensure that everything is running properly:
 # ceph -s
 ----
 +
-image::ceph-health.png[ceph-health.png,scaledwidth=90%]
+image::ceph-health.png[title="Checking Cluster Health",scaledwidth=90%]
 
 * To get the benefits of the OpenAttic WebUI, you must now initiate
 `ceph.stage.4`, which will install the OpenAttic service:
@@ -943,22 +943,22 @@ image::ceph-health.png[ceph-health.png,scaledwidth=90%]
 # salt-run state.orch ceph.stage.4
 ----
 +
-image::ceph-stage-4.png[ceph-stage-4.png,scaledwidth=90%]
+image::ceph-stage-4.png[title="Installing OpenAttic service",scaledwidth=90%]
 
 
 * You can now manage your cluster through the WebUI:
 +
-image::openattic-dash.png[openattic-dash.png,scaledwidth=90%]
+image::openattic-dash.png[title="SUSE Enterprise Storage WebUI",scaledwidth=90%]
 
 
 * To provide a Data Hub RBD device, you first need to create a related pool:
 
-image::openattic-pool.png[openattic-pool.png,scaledwidth=90%]
+image::openattic-pool.png[title="Creating Ceph Pool",scaledwidth=90%]
 
 
 * Then provide access to this pool through an RBD device:
 +
-image::openattic-rbd.png[openattic-rbd.png,scaledwidth=90%]
+image::openattic-rbd.png[title="Accessing Ceph Pool",scaledwidth=90%]
 
 
 You can now go to <<prerequisites_caasp_cluster>> and follow the prerequisites