update demo/stack resources, airflow-scheduled-job and hbase-hdfs-load-cycling-data demos

Author: xeniape

demos/demos-v2.yaml

@@ -70,7 +70,7 @@ demos:
     supportedNamespaces: ["default"]
     resourceRequests:
       cpu: 8700m
-      memory: 29746Mi
+      memory: 42034Mi
       pvc: 75Gi # 30Gi for Kafka
   nifi-kafka-druid-water-level-data:
     description:  Demo ingesting water level data into Kafka using NiFi, streaming it into Druid and creating a Superset dashboard
@@ -91,7 +91,7 @@ demos:
     supportedNamespaces: ["default"]
     resourceRequests:
       cpu: 8900m
-      memory: 30042Mi
+      memory: 42330Mi
       pvc: 75Gi # 30Gi for Kafka
   spark-k8s-anomaly-detection-taxi-data:
     description: Demo loading New York taxi data into an S3 bucket and carrying out an anomaly detection analysis on it

docs/modules/demos/images/hbase-hdfs-load-cycling-data/hbase-table-ui.png

@@ -98,7 +98,7 @@ continuously:
 
 image::airflow-scheduled-job/airflow_7.png[]
 
-Click on the `run_every_minute` box in the centre of the page and then select `Log`:
+Click on the `run_every_minute` box in the centre of the page and then select `Logs`:
 
 [WARNING]
 ====
@@ -118,7 +118,7 @@ image::airflow-scheduled-job/airflow_10.png[]
 
 Go back to DAG overview screen. The `sparkapp_dag` job has a scheduled entry of `None` and a last-execution time
 (`2022-09-19, 07:36:55`). This allows a DAG to be executed exactly once, with neither schedule-based runs nor any
-https://airflow.apache.org/docs/apache-airflow/stable/dag-run.html?highlight=backfill#backfill[backfill]. The DAG can
+https://airflow.apache.org/docs/apache-airflow/stable/core-concepts/dag-run.html#backfill[backfill]. The DAG can
 always be triggered manually again via REST or from within the Webserver UI.
 
 image::airflow-scheduled-job/airflow_11.png[]

docs/modules/demos/images/hbase-hdfs-load-cycling-data/hbase-ui-start-page.png

@@ -51,33 +51,31 @@ image::hbase-hdfs-load-cycling-data/overview.png[]
 
 To list the installed Stackable services run the following command: `stackablectl stacklet list`
 
-//TODO(Techassi): Update console output
-
 [source,console]
 ----
 $ stackablectl stacklet list
-PRODUCT    NAME       NAMESPACE  ENDPOINTS                                               EXTRA INFOS
-
- hbase      hbase      default    regionserver                  172.18.0.5:32282
-                                  ui                            http://172.18.0.5:31527
-                                  metrics                       172.18.0.5:31081
-
- hdfs       hdfs       default    datanode-default-0-metrics    172.18.0.2:31441
-                                  datanode-default-0-data       172.18.0.2:32432
-                                  datanode-default-0-http       http://172.18.0.2:30758
-                                  datanode-default-0-ipc        172.18.0.2:32323
-                                  journalnode-default-0-metrics 172.18.0.5:31123
-                                  journalnode-default-0-http    http://172.18.0.5:30038
-                                  journalnode-default-0-https   https://172.18.0.5:31996
-                                  journalnode-default-0-rpc     172.18.0.5:30080
-                                  namenode-default-0-metrics    172.18.0.2:32753
-                                  namenode-default-0-http       http://172.18.0.2:32475
-                                  namenode-default-0-rpc        172.18.0.2:31639
-                                  namenode-default-1-metrics    172.18.0.4:32202
-                                  namenode-default-1-http       http://172.18.0.4:31486
-                                  namenode-default-1-rpc        172.18.0.4:31874
-
- zookeeper  zookeeper  default    zk                            172.18.0.4:32469
+
+┌───────────┬───────────┬───────────┬──────────────────────────────────────────────────────────────┬─────────────────────────────────┐
+│ PRODUCT   ┆ NAME      ┆ NAMESPACE ┆ ENDPOINTS                                                    ┆ CONDITIONS                      │
+╞═══════════╪═══════════╪═══════════╪══════════════════════════════════════════════════════════════╪═════════════════════════════════╡
+│ hbase     ┆ hbase     ┆ default   ┆ regionserver                         172.18.0.2:31521        ┆ Available, Reconciling, Running │
+│           ┆           ┆           ┆ ui-http                              172.18.0.2:32064        ┆                                 │
+│           ┆           ┆           ┆ metrics                              172.18.0.2:31372        ┆                                 │
+├╌╌╌╌╌╌╌╌╌╌╌┼╌╌╌╌╌╌╌╌╌╌╌┼╌╌╌╌╌╌╌╌╌╌╌┼╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌┼╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌┤
+│ hdfs      ┆ hdfs      ┆ default   ┆ datanode-default-0-listener-data     172.18.0.2:31990        ┆ Available, Reconciling, Running │
+│           ┆           ┆           ┆ datanode-default-0-listener-http     http://172.18.0.2:30659 ┆                                 │
+│           ┆           ┆           ┆ datanode-default-0-listener-ipc      172.18.0.2:30678        ┆                                 │
+│           ┆           ┆           ┆ datanode-default-0-listener-metrics  172.18.0.2:31531        ┆                                 │
+│           ┆           ┆           ┆ namenode-default-0-http              http://172.18.0.2:32543 ┆                                 │
+│           ┆           ┆           ┆ namenode-default-0-metrics           172.18.0.2:30098        ┆                                 │
+│           ┆           ┆           ┆ namenode-default-0-rpc               172.18.0.2:30915        ┆                                 │
+│           ┆           ┆           ┆ namenode-default-1-http              http://172.18.0.2:31333 ┆                                 │
+│           ┆           ┆           ┆ namenode-default-1-metrics           172.18.0.2:30862        ┆                                 │
+│           ┆           ┆           ┆ namenode-default-1-rpc               172.18.0.2:31440        ┆                                 │
+├╌╌╌╌╌╌╌╌╌╌╌┼╌╌╌╌╌╌╌╌╌╌╌┼╌╌╌╌╌╌╌╌╌╌╌┼╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌┼╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌┤
+│ zookeeper ┆ zookeeper ┆ default   ┆                                                              ┆ Available, Reconciling, Running │
+└───────────┴───────────┴───────────┴──────────────────────────────────────────────────────────────┴─────────────────────────────────┘
+
 ----
 
 include::partial$instance-hint.adoc[]
@@ -217,18 +215,18 @@ Below you will see the overview of your HDFS cluster.
 
 image::hbase-hdfs-load-cycling-data/hdfs-overview.png[]
 
-The UI will give you information on the datanodes via the datanodes tab.
+The UI will give you information on the datanodes via the `Datanodes` tab.
 
 image::hbase-hdfs-load-cycling-data/hdfs-datanode.png[]
 
-You can also browse the filesystem via the Utilities menu.
+You can also browse the file system by clicking on the `Utilities` tab and selecting `Browse the file system`.
 
 image::hbase-hdfs-load-cycling-data/hdfs-data.png[]
 
-The raw data from the distcp job can be found here.
+Navigate in the file system to the folder `data` and then the `raw` folder. Here you can find the raw data from the distcp job.
 
 image::hbase-hdfs-load-cycling-data/hdfs-data-raw.png[]
 
-The structure of the Hfiles can be seen here.
+Selecting the folder `data` and then `hfile` instead, gives you the structure of the Hfiles.
 
 image::hbase-hdfs-load-cycling-data/hdfs-data-hfile.png[]

docs/modules/demos/images/hbase-hdfs-load-cycling-data/hdfs-data-hfile.png

@@ -220,7 +220,7 @@ stacks:
     supportedNamespaces: []
     resourceRequests:
       cpu: 8900m
-      memory: 30042Mi
+      memory: 42330Mi
       pvc: 75Gi
     parameters:
       - name: nifiAdminPassword