New doc version references

Author: Zinidia

docs/bigdata/README.md

@@ -1,4 +1,4 @@
-# Disaggregated HDP Spark and Hive with Obstor
+# Disaggregated Spark and Hive with Obstor
 
 ## 1. Cloud-native Architecture
 
@@ -12,9 +12,7 @@ Obstor also supports multi-cluster, multi-site federation similar to AWS regions
 
 ## 2. Prerequisites
 
-*  Install Hortonworks Distribution using this [guide.](https://docs.hortonworks.com/HDPDocuments/Ambari-2.7.1.0/bk_ambari-installation/content/ch_Installing_Ambari.html)
-   *   [Setup Ambari](https://docs.hortonworks.com/HDPDocuments/Ambari-2.7.1.0/bk_ambari-installation/content/set_up_the_ambari_server.html) which automatically sets up YARN
-   *   [Installing Spark](https://docs.hortonworks.com/HDPDocuments/HDP3/HDP-3.0.1/installing-spark/content/installing_spark.html)
+*  Install a Hadoop cluster with Spark and Hive. Follow the [Apache Hadoop](https://hadoop.apache.org/docs/stable/) cluster setup (which configures YARN) and the [Apache Spark](https://spark.apache.org/docs/latest/) installation guides.
 *  Install Obstor Distributed Server using one of the guides below.
    *   [Deployment based on Kubernetes](/docs/orchestration/kubernetes)
 
@@ -95,7 +93,7 @@ fs.s3a.threads.max=2048 # Maximum number of threads for S3A
 The rest of the other optimization options are discussed in the links below
 
 *  [https://hadoop.apache.org/docs/current/hadoop-aws/tools/hadoop-aws/index.html](https://hadoop.apache.org/docs/current/hadoop-aws/tools/hadoop-aws/index.html)
-*  [https://hadoop.apache.org/docs/r3.1.1/hadoop-aws/tools/hadoop-aws/committers.html](https://hadoop.apache.org/docs/r3.1.1/hadoop-aws/tools/hadoop-aws/committers.html)
+*  [https://hadoop.apache.org/docs/current/hadoop-aws/tools/hadoop-aws/committers.html](https://hadoop.apache.org/docs/current/hadoop-aws/tools/hadoop-aws/committers.html)
 
 Once the config changes are applied, proceed to restart **Hadoop** services.
 
@@ -168,7 +166,7 @@ hive.mv.files.threads=40
 mapreduce.input.fileinputformat.list-status.num-threads=50
 ```
 
-For more information about these options please visit [https://www.cloudera.com/documentation/enterprise/5-11-x/topics/admin_hive_on_s3_tuning.html](https://www.cloudera.com/documentation/enterprise/5-11-x/topics/admin_hive_on_s3_tuning.html)
+For more information about these options please visit [https://hadoop.apache.org/docs/current/hadoop-aws/tools/hadoop-aws/performance.html](https://hadoop.apache.org/docs/current/hadoop-aws/tools/hadoop-aws/performance.html)
 
 ![hive-config](https://raw.githubusercontent.com/cloudment/obstor/main/docs/bigdata/images/image13.png "hive advanced custom config")
 
@@ -191,7 +189,7 @@ Follow these steps to run the Spark Pi example:
 *  Navigate to a node with the Spark client and access the spark2-client directory:
 
 ```bash
-cd /usr/hdp/current/spark2-client
+cd $SPARK_HOME
 su spark
 ```
 
@@ -227,7 +225,7 @@ The following example submits WordCount code to the Scala shell. Select an input
 *  Navigate to a node with Spark client and access the spark2-client directory:
 
 ```bash
-cd /usr/hdp/current/spark2-client
+cd $SPARK_HOME
 su spark
 ```
 

docs/bucket/notifications/README.md

@@ -870,7 +870,7 @@ The steps below show how to use this notification target in `namespace` format.
 
 ### Step 1: Ensure minimum requirements are met
 
-Obstor requires PostgreSQL version 9.5 or above. Obstor uses the [`INSERT ON CONFLICT`](https://www.postgresql.org/docs/9.5/static/sql-insert.html#SQL-ON-CONFLICT) (aka UPSERT) feature, introduced in version 9.5 and the [JSONB](https://www.postgresql.org/docs/9.4/static/datatype-json.html) data-type introduced in version 9.4.
+Obstor requires PostgreSQL version 17 or above. Obstor uses the [`INSERT ON CONFLICT`](https://www.postgresql.org/docs/9.5/static/sql-insert.html#SQL-ON-CONFLICT) (aka UPSERT) feature, introduced in version 9.5 and the [JSONB](https://www.postgresql.org/docs/9.4/static/datatype-json.html) data-type introduced in version 9.4.
 
 ### Step 2: Add PostgreSQL endpoint to Obstor
 
@@ -1004,7 +1004,7 @@ The steps below show how to use this notification target in `namespace` format.
 
 ### Step 1: Ensure minimum requirements are met
 
-Obstor requires MySQL version 5.7.8 or above. Obstor uses the [JSON](https://dev.mysql.com/doc/refman/5.7/en/json.html) data-type introduced in version 5.7.8. We tested this setup on MySQL 5.7.17.
+Obstor requires MySQL version 8.0 or above. Obstor uses the [JSON](https://dev.mysql.com/doc/refman/8.4/en/json.html) data-type introduced in version 5.7.8. We tested this setup on MySQL 8.4.
 
 ### Step 2: Add MySQL server endpoint configuration to Obstor
 

docs/integrations/veeam/README.md

@@ -3,7 +3,7 @@
 When using Veeam Backup and Replication, you can use S3-compatible object storage such as Obstor as a capacity tier for backups.  This disaggregates storage for the Veeam infrastructure and allows you to retain control of your data. With the ease of use of setup and administration of Obstor, it allows a Veeam backup admin to easily deploy their own object store for capacity tiering.
 
 __Prerequisites__
-- One or both of Veeam Backup and Replication with support for S3-compatible object store (e.g. 9.5.4) and Veeam Backup for Office365 (VBO)
+- One or both of Veeam Backup and Replication with support for S3-compatible object store (e.g. 12.3) and Veeam Backup for Office365 (VBO)
 - Obstor object storage set up
 - Veeam requires TLS connections to the object storage.  This can be configured per the [TLS guide](/docs/tls)
 - The S3 bucket, Access Key and Secret Key have to be created before and outside of Veeam.

docs/orchestration/docker-swarm/docker-compose.yaml

@@ -1,8 +1,6 @@
-version: '3.7'
-
 services:
   obstor1:
-    image: ghcr.io/cloudment/obstor:RELEASE.2021-04-22T15-44-28Z
+    image: ghcr.io/cloudment/obstor
     hostname: obstor1
     volumes:
       - obstor1-data:/export

docs/shared-backend/DESIGN.md

@@ -19,7 +19,7 @@ Restrictions
 
 Running Obstor instances on shared backend is no different than running on a stand-alone disk. There are no special configuration changes required to enable this feature. Access to files stored on NAS volume are locked and synchronized by default. Following examples will clarify this further for each operating system of your choice:
 
-### Ubuntu 16.04 LTS
+### Ubuntu 26.04 LTS
 
 Example 1: Start Obstor instance on a shared backend mounted and available at `/path/to/nfs-volume`.
 
@@ -33,7 +33,7 @@ On linux server2
 obstor backend nas /path/to/nfs-volume
 ```
 
-### Windows 2012 Server
+### Windows Server 2025
 
 Example 1: Start Obstor instance on a shared backend mounted and available at `\\remote-server\cifs`.
 

docs/shared-backend/README.md

@@ -29,7 +29,7 @@ To run Obstor shared backend instances, you need to start multiple Obstor server
 - All the nodes running shared Obstor need to have same access key and secret key. To achieve this, we export access key and secret key as environment variables on all the nodes before executing Obstor server command.
 - The drive paths below are for demonstration purposes only, you need to replace these with the actual drive paths/folders.
 
-#### Obstor shared mode on Ubuntu 16.04 LTS.
+#### Obstor shared mode on Ubuntu 26.04 LTS.
 
 You'll need the path to the shared volume, e.g. `/path/to/nfs-volume`. Then run the following commands on all the nodes you'd like to launch Obstor.
 
@@ -39,7 +39,7 @@ export OBSTOR_ROOT_PASSWORD=<SECRET_KEY>
 obstor backend nas /path/to/nfs-volume
 ```
 
-#### Obstor shared mode on Windows 2012 Server
+#### Obstor shared mode on Windows Server 2025
 
 You'll need the path to the shared volume, e.g. `\\remote-server\smb`. Then run the following commands on all the nodes you'd like to launch Obstor.
 

docs/sts/etcd.md

@@ -3,20 +3,20 @@ etcd is a distributed key value store that provides a reliable way to store data
 
 ## Get started
 ### 1. Prerequisites
-- Docker 18.03 or above, refer here for [installation](https://docs.docker.com/install/).
+- Docker 29.5.2 or above, refer here for [installation](https://docs.docker.com/install/).
 
 ### 2. Start etcd
 etcd uses `gcr.io/etcd-development/etcd` as a primary container registry.
 
 ```bash
 rm -rf /tmp/etcd-data.tmp && mkdir -p /tmp/etcd-data.tmp && \
-  docker rmi gcr.io/etcd-development/etcd:v3.3.9 || true && \
+  docker rmi gcr.io/etcd-development/etcd:v3.6.12 || true && \
   docker run \
   -p 2379:2379 \
   -p 2380:2380 \
   --mount type=bind,source=/tmp/etcd-data.tmp,destination=/etcd-data \
-  --name etcd-gcr-v3.3.9 \
-  gcr.io/etcd-development/etcd:v3.3.9 \
+  --name etcd-gcr-v3.6.12 \
+  gcr.io/etcd-development/etcd:v3.6.12 \
   /usr/local/bin/etcd \
   --name s1 \
   --data-dir /etcd-data \
@@ -29,7 +29,7 @@ rm -rf /tmp/etcd-data.tmp && mkdir -p /tmp/etcd-data.tmp && \
   --initial-cluster-state new
 ```
 
-You may also setup etcd with TLS following this documentation [here](https://coreos.com/etcd/docs/latest/op-guide/security.html)
+You may also setup etcd with TLS following this documentation [here](https://etcd.io/docs/v3.6/op-guide/security/)
 
 ### 3. Setup Obstor with etcd
 Obstor server expects environment variable for etcd as `OBSTOR_ETCD_ENDPOINTS`, this environment variable takes many comma separated entries.

docs/sts/wso2.md

@@ -3,7 +3,7 @@ WSO2 is an Identity Server open source and is released under Apache Software Lic
 
 ## Get started
 ### 1. Prerequisites
-- JAVA 1.8 and above installed already and JAVA_HOME points to JAVA 1.8 installation.
+- JAVA 25 and above installed already and JAVA_HOME points to JAVA 25 installation.
 - Download WSO2 follow their [installation guide](https://docs.wso2.com/display/IS540/Installation+Guide).
 
 ### 2. Configure WSO2