Commit 020dabdf authored by threedytech's avatar threedytech
Browse files

release: 3.3

parent 8d8b82a4
......@@ -6,10 +6,15 @@ instant3Dhub on Kubernetes
********************************************
Read First
********************************************
Kubernetes is the targeted platform for running instant3Dhub. Therefore, this guide assumes a k8s cluster exists and can be accessed for deployments.
Details about the requirements for running instant3Dhub can be found `here </INSTALL_REQUIREMENTS.rst>`_
Instant3Dhub is shipped with all the necessery components and services to run completely in kubernetes without the need to setup external services. However not all services.
However it is possible to use exernal services like PostgreSQL, ELK stack and RabbitMQ. Setting up these external services is recommend in some scenarios and specially in production environments.
More information on how to configure Instant3Dhub to run with external services can be found below.
Here is a non-extensive list of functionalities:
* **External DB use**: The system can optionally work with a previously provisioned PostgreSQL instance. This instance must be set up manually via Ansible.
Limitations:
* **HTTPS**: HTTPS is not supported inside the cluster or at the gateway. Currently HTTPS can be used by adding a proxy outside of the cluster or as a sidecar on the apigw component.
* **Services**: Currently only the SharedSession, SpaceStore, Measurement and Query services are enabled. This means a range of functionalities will not be available in webvis and other API-libraries.
* **Security/Signatues**: The third main version instant3Dhub is designed to include security on all layers of the system like controlling the access to the management APIs, resource APIs, the services or the data that goes through the system. It is not yet possible to configure custom keys.
......@@ -19,43 +24,174 @@ Here is a non-extensive list of functionalities:
Installation
********************************************
The instant3Dhub Kubernetes deployment is based on `Helm <https://helm.sh/>`_ Charts.
Transfer docker images
--------------------------------------------
Our docker images are available on our public registry images.threey.io and can be pulled from there. However we recommend that you transfer the images to your own registry as we do not guarantee high availablity of our registry.
For transfering images to another docker registry, we provide a `script <https://repo.threedy.io/instant3Dhub/release/-/blob/master/reference/transfer_images.sh>`_.
.. code-block:: bash
./transfer_images.sh images.threedy.io registry.yourdomain.com
Overview
Install Helm
--------------------------------------------
The installation of instant3Dhub consists of three phases:
We provide a `Helm <https://helm.sh/>`_ Chart repository for the deployment of instant3Dhub on Kubernetes.
Therefore, helm should be installed first:
.. code-block:: bash
curl -fsSL -o get_helm.sh https://raw.githubusercontent.com/helm/helm/master/scripts/get-helm-3 \
&& chmod 700 get_helm.sh \
&& ./get_helm.sh
Now, add the instant3Dhub Helm repository:
.. code-block:: bash
helm repo add instant3Dhub https://repo.threedy.io/api/v4/projects/2/packages/helm/stable \
&& helm repo update
You can now deploy using helm install but please continue reading to know which configuration you need to set. There are four main configuration that are required and need to be adjusted before you deploy.
These configuration are:
#. **Provisioning**: First the cluster and required resources need to be set up
#. **Configuration**: instant3Dhub needs to be configured to integrate correctly with the infrastructure
#. **Startup**: Finally the system is applied to the cluster or passed to a GitOps pipeline
* licenseServer
* storage
* entrypoints
* registry
Configuration
.. code-block:: bash
helm install [release-name] instant3Dhub --version="3.3"
As an alternative please consider the reference scripts located `here <https://repo.threedy.io/instant3Dhub/release/-/blob/master/reference/helm/>`_
License Server
-----------------------------------------------
Instant3Dhub license server must be installed outside your k8s cluster and shoud be accessible from within the cluster so you can use the features of instant3Dhub.
For information on how to install the license server please follow `these instructions <./LICENSE_SERVER.rst>`_
Now you can set the address to the license server with the --set parameter.
.. code-block:: bash
helm install [release-name] instant3Dhub --version="3.3" \
--set licenseServer=license.yourdomain.com:8200
Storage
--------------------------------------------
The instant3Dhub deployment is based on a standard Helm Chart in *./helm*. All required changes should be placed in the values file: *./helm/values.yaml*.
The values in section 1 are required to be set and dependent on the environment:
instant3Dhub requires a set of `volumes <https://kubernetes.io/docs/concepts/storage/persistent-volumes/>`_ for persistency and data exchange between services in the system.
In case you have a storage class that provides PVs dynamically, the option storage.class can be set to to be the name of your storage class via the --set parameter.
.. code-block:: bash
helm install [release-name] instant3Dhub --version="3.3" \
--set licenseServer=license.yourdomain.com:8200 \
--set storage.class=your-storage-class
* ``entrypoints``: The list of URLs from which the system is reachable from outside the cluster.
* ``registry``: The URI to the container image registry. When you use pre-pulled images remove this entry.
* ``licenseServer``: The cluster internal URL to the instant3Dhub `License Server <./LICENSE_SERVER.rst>`_.
Startup
Otherwise, make sure that you create the following static PVs with their corresonding labels:
=================================== ======= =======================================================================
Name Size Labels
----------------------------------- ------- -----------------------------------------------------------------------
cache_volume 20GB app: idhub-cache & instance: <The-name-of-namespace>
postgres_volume 5GB app: idhub-postgres & instance: <The-name-of-namespace>
elastic_volume 5GB app: idhub-elastic & instance: <The-name-of-namespace>
entrygw_volume 2GB app: idhub-entrygw & instance: <The-name-of-namespace>
rabbitmq_volume 1GB app: idhub-rabbitmq & instance: <The-name-of-namespace>
=================================== ======= =======================================================================
If you create the PVs manually with the correct labels, the storage.class parameter does not need to be set then.
An example of static persistent volumes can be found `here <https://repo.threedy.io/instant3Dhub/release/-/blob/master/reference/volumes/pv_kubectl.yml>`_
Access
--------------------------------------------
The simplest way to actually start instant3Dhub is with helm. We highly recommend to put the instant3Dhub instance to a dedicated namespace.
The name of the deployment must match the release set in the PersistentVolumes.
To start with helm use:
In order for the system to address its resources properly, the entry points for the system have to be set. An entry point is a URL from which the system is accessible. For example if you have proxy in front of your cluster, the entry point must be set to be the URL of the proxy.
.. code-block:: bash
helm install [release-name] instant3Dhub --version="3.3" \
--set licenseServer=license.yourdomain.com:8200 \
--set storage.class=your-storage-class \
--set entrypoints={https://proxy.yourdomain.com:30000}
Images Registry
----------------------------------------------
You should make sure that you are using the correct registry for pulling the docker images. Once you have transfered the images to your registry, you can set the URL in helm chart.
.. code-block:: bash
helm install -n $RELEASE_NAME $RELEASE_NAME
helm install [release-name] instant3Dhub --version="3.3" \
--set licenseServer=license.yourdomain.com:8200 \
--set storage.class=your-storage-class \
--set entrypoints={https://proxy.yourdomain.com:30000} \
--set registry=registry.yourdomain.com
At this point you should have all the requirements to run instant3Dhub.
The startup and initialization of all containers can take a few minutes, depending on your cluster and registry connection speed.
To check the status of the containers run:
.. code-block:: bash
watch kubectl get pods -n $RELEASE_NAME
watch kubectl get pods -n your-namespace
After all containers are running the system might take up to one minute to initialize correctly.
********************************************
Using External Services
********************************************
PostgreSQL
-------------------------------------------
The system can optionally work with a previously provisioned PostgreSQL instance. This instance must be initialized corrctly with our schema and tables. For that we provide ansible playbooks to install and initialize postgres manually. For more information please `see our guide <./INSTALL_EXT_POSTGRES_GUIDE>`_.
If you are using external PostgresSQL, we recommend using k8s secrets to store the connection string. The secrets can be referenced then using these values in our helm chart.
============================================= ========================================
Name Description
--------------------------------------------- ----------------------------------------
credentials.postgres.system.secretKeyRef.name The name of the secret where the connection string is stored
credentials.postgres.system.secretKeyRef.key The name of the key in the secret's items.
============================================= ========================================
RabbitMQ
-------------------------------------------
The system uses rabbitmq to dispatch jobs. If you want to use external service for that, it is possible to change the configuration to point instant3Dhub to use the external service.
These values need to be set in our helm chart values then.
============================================= ========================================
Name Description
--------------------------------------------- ----------------------------------------
credentials.rabbitmq.secretKeyRef.name The name of the secret where the connection string is stored
credentials.rabbitmq.secretKeyRef.key The name of the key in the secret's items.
============================================= ========================================
......@@ -21,6 +21,7 @@ As an example, if the installation should run under a different path on a proxy
This way internal components which deliver our webfrontend already know how to deliver addresses to get back to the the backend.
.. code-block:: yaml
# entrypoints in values.yaml
entrypoints: [ "https://example-proxy-server/extra/path/" ]
......
......@@ -6,10 +6,10 @@ instant3Dhub requirements
Read First
********************************************
This section contains a general overview of container resource requirement assumptions is shown.
This section contains a general overview of the resource requirements for running the containerized instant3Dhub.
These specifications are based upon measurements of average CAD Data encountered in various scenarios in the Automotive and BIM industry.
Depending on input data sizes these values may need to be adjusted.
As it is difficult to give a one fits all recommendation we do not enforce any limits or requests in k8s or compose as of yet.
Depending on the sizes of the input data, these values may need to be adjusted.
As it is difficult to give a one-fits-all recommendation, we do not enforce any limits or requests in k8s as of yet.
Storage requirements are given as a minimum.
Provisioning
......@@ -17,18 +17,13 @@ Provisioning
To following resources have to be provisioned to enable the cluster to run instant3Dhub
* Docker-Compose / Helm & k8s
* Helm & k8s
* License Server
* Image Registry
* Storage
* Compute
* Database (optional)
Docker-Compose Requirements
============================================
* Docker: v20.10.2
* Docker-Compose: v1.25.0
K8s Requirements
============================================
......@@ -50,7 +45,7 @@ License Server
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
To run an instant3Dhub installation access to an instant3Dhub License Server is required. The license server is installed separately from the instant3Dhub instance and can be shared with other instant3Dhub instances.
A guide on how to set up the license server can be found `here <./LICENSE_SERVER.md>`_.
A guide on how to set up the license server can be found `here <./LICENSE_SERVER.rst>`_.
Image Registry
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
......@@ -69,8 +64,7 @@ If you can not use an image registry, the nodes of the cluster can also be provi
Storage
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
instant3Dhub requires a set of volumes for persistency and data exchange between services in the system.
For our Docker-Compose deploy we currently only use locally bound volumes.
instant3Dhub requires a set of volumes for persistency and data exchange between services in the system.
Kubernetes volumes need to be configured in your backend. Our helm charts come with PersistentVolumeClaims which need to be satisfied for basic functionality.
Examples for PersistentVolume definitions can be found in ./reference/volumes/pv_kubectl.yml. These need to be adjusted for your deploy.
......
###########################
instant3Dhub on single node
###########################
********************************************
Read First
********************************************
This guide targets those who have neither an existing k8s cluster nor the resources to set up and manage one.
While having a k8s cluster to run instant3Dhub is still a requirement, we provide tools to get all the requirments ready for you on a single CentOS 8 machine.
*******************************************
Prerequisites
*******************************************
The machine where you want to run instant3Dhub should have the following requirements in order to run the system properly:
Resources
-----------------------------------------
These minimal resources are required to run instant3Dhub
* CPU-only: CPU=4 Cores, Mem=16GB
* with GPU: CPU=8 Cores, Mem=32GB, GPU=1 NVIDIA GPU
System
---------------------------------------------
* Snapd is installed and running
* SELinux is disabled
* The system has the correct Linux kernel sources from the CentOS repositories
* If you want to use GPU support, then make sure that nouveau dirver is disabled
* If your system uses firewalld then make sure that masquerade is enabled on the host.
* You have a running instant3Dhub License Server which can be accessed from the host. For installing instant3Dhub License Server please check the documenation `here <LICENSE_SERVER.rst>`_.
If you are not sure if or how to make your system meets these requirments, then please check and run the `prerequisite.sh <https://repo.threedy.io/instant3Dhub/release/-/tree/master/reference/singleNode/prerequisite.sh>`_ script which will reconfigure your system to meet the requirments 1-5.
Please note that restart might be required to make the changes persistent.
*************************************************
Installation
*************************************************
For installing instant3Dhub on a single machine:
Clone the release repository
.. code-block:: bash
git clone http://repo.threedy.io/instant3Dhub/release.git
cd release/references/singleNode/
The script expects these env variables to be set in the setup file:
* RELEASE_NAME: Is the name of the release to be used when deploying instant3Dhub. This can be any name of your choise. Example: instant3dhub-test. Default is: i3dhub-singlenode.
* ENTRYPOINT: The external exposure hosts or proxies. Example: http://host-name.your-domain.com:30000. Default is: http://your-hostname:30042. For more information on how to set up a proxy please see our `guide <./INSTALL_PROXY_GUIDE.srt>`_.
* REGISTRY: Is the containers registry where instant3Dhub images can be fetched. Example: hub.docker.com. Default is: images.threedy.io.
* LICENSE_SERVER: The address of the license server. Example: http://license.threedy.io:8200. Default is empty.
* ENABLE_GPU: Set to true if your system has GPU and you want to enable them to be used by instant3Dhub visualization services. Default is false.
Please adjust these variables based on your setup.
Now you can install instant3Dhub
.. code-block:: bash
./install.sh
......@@ -26,14 +26,14 @@ Installation Package
The installation requires two packages, the OS dependent
license server package:
* **CentOS 7** : `instant3Dhub-licenseServer-CentOS-Linux-7-x64\*.rpm <https://repo.threedy.io/repository/instant3Dhub_raw/licenseServer/instant3Dhub-licenseServer-CentOS-Linux-7-x64.21.3.rpm>`_
* **SLES-12.3** : `instant3Dhub-licenseServer-SLES-12.3-x64\*.rpm <https://repo.threedy.io/repository/instant3Dhub_raw/licenseServer/instant3Dhub-licenseServer-SLES-12.3-x64.21.3.rpm>`_
* **Fedora 23** : `instant3Dhub-licenseServer-Fedora-23-x64\*.rpm <https://repo.threedy.io/repository/instant3Dhub_raw/licenseServer/instant3Dhub-licenseServer-Fedora-23-x64.21.3.rpm>`_
* **Fedora 29** : `instant3Dhub-licenseServer-Fedora-29-x64\*.rpm <https://repo.threedy.io/repository/instant3Dhub_raw/licenseServer/instant3Dhub-licenseServer-Fedora-29-x64.21.3.rpm>`_
* **CentOS 7** : `instant3Dhub-licenseServer-CentOS-Linux-7-x64\*.rpm <https://repo.threedy.io/repository/instant3Dhub_raw/licenseServer/instant3Dhub-licenseServer-CentOS-Linux-7-x64.21.4.rpm>`_
* **SLES-12.3** : `instant3Dhub-licenseServer-SLES-12.3-x64\*.rpm <https://repo.threedy.io/repository/instant3Dhub_raw/licenseServer/instant3Dhub-licenseServer-SLES-12.3-x64.21.4.rpm>`_
* **Fedora 23** : `instant3Dhub-licenseServer-Fedora-23-x64\*.rpm <https://repo.threedy.io/repository/instant3Dhub_raw/licenseServer/instant3Dhub-licenseServer-Fedora-23-x64.21.4.rpm>`_
* **Fedora 29** : `instant3Dhub-licenseServer-Fedora-29-x64\*.rpm <https://repo.threedy.io/repository/instant3Dhub_raw/licenseServer/instant3Dhub-licenseServer-Fedora-29-x64.21.4.rpm>`_
and the ansible roles to install and initialize the database:
* `instant3Dhub-ansible-noarch-\*.tgz <https://repo.threedy.io/repository/instant3Dhub_raw/licenseServer/instant3Dhub-ansibledb-noarch-21.3.tgz>`_
* `instant3Dhub-ansible-noarch-\*.tgz <https://repo.threedy.io/repository/instant3Dhub_raw/licenseServer/instant3Dhub-ansibledb-noarch-21.4.tgz>`_
Install License Server DB: (utilizes ansible)
=============================================
......
############################################
instant3Dhub 3.2.1 Integration
instant3Dhub Integration
############################################
This is the deployment repository for instant3Dhub. For more information about the product visit `www.threedy.io <https://www.threedy.io>`_.
This section includes information on how to install and conifgure instant3Dhub to match your needs and environment. For more information about the product visit `www.threedy.io <https://www.threedy.io>`_.
For direct support please refer to our `ServiceDesk <http://support.threedy.io/>`_.
********************************************
Installation Variants
********************************************
instant3Dhub is deployed on top of a container orchestration layer. The primary target is the Kubernetes platform, which is also highly recommended for productive environments.
There is also a way to install instant3Dhub with docker-compose, which can be used for development environments or evaluation.
instant3Dhub is a containerized software that can be deployed on top of a container orchestration layer. The primary target is the Kubernetes platform, which is also highly recommended for productive environments.
Having an up and running cluster is a required to continue the installation. However, we also provide a quick start guide for running instant3Dhub on a single linux machine with minimal overhead.
* For details on how to deploy instant3Dhub on an existing cluster, please follow the guide for `installation on k8s <./INSTALL_K8S.rst>`_
* For a quick start please follow the guide for `installation on a single node <./INSTALL_SINGLE_NODE.rst>`_
* `Kubernetes <./INSTALL_K8S.rst>`_
* `Docker-Compose <./INSTALL_COMPOSE.rst>`_ (Docker-Compose is not officially supported anymore. Documentation and scripts are only for reference.)
********************************************
Support
********************************************
Thank you for working with instant3Dhub.
For further help or to give much appreciated feedback contact your personal contact at Threedy or open a ticket at our `ServiceDesk <http://support.threedy.io/>`_.
.. toctree::
:hidden:
INSTALL_COMPOSE
INSTALL_K8S
INSTALL_REQUIREMENTS
INSTALL_K8S
INSTALL_SINGLE_NODE
TOOLS_ANSIBLE
LICENSE_SERVER
INSTALL_PROXY_GUIDE
INSTALL_EXT_POSTGRES_GUIDE
TOOLS_ANSIBLE
********************************************
Structure
********************************************
This repository is laid out as a starting point for an instant3Dhub operations repository.
After configuration the resulting artifact can be deployed directly with the corresponding deployment tools or added to a GitOps pipeline.
If relativ paths are mentioned in this documentation we refer to the following structure and assume the repository root as origin.
The repository is organized in the following way:
* **\*.rst**: These are the documentation files on how to use this repository and install instant3Dhub.
* **helm/**: This is a typical Helm Chart. Configuration is mainly done by editing the values.yaml.
* **compose/**: The contained compose yaml aswell as the values.yaml is designed to be as similar as possible to the helm deploy. Configuration handles parallel to the helm deploy.
* **reference/**: Contains auxiliary scripts to use or as an example on how to fulfill requirements
* **helm/**: This contains a pv_kubectl.yml with a set of example PersistentVolume and StorageClass resource descriptors. The install.sh and uninstall.sh show how the automation with the helm cli could be automated.
* **compose/**: This contains another method to deploy instant3Dhub via docker-compose. Currently this is a set of scripts that prepare the environment based on the configuration set in the env.
* **transfer_images.sh**: This is a utility script for transfering the instant3Dhub container images to another registry, which needs to be done once on before the first deploy or an update.
* **init/**: Here you will find additional scripts and tools for configuration.
* **postgres/**: These ansible scripts allow an initialization of PostgreSQL in order to use a PostgreSQL instance separate from the prepackaged PostgreSQL containers.
********************************************
Support
********************************************
Thank you for working with instant3Dhub.
For further help or to give much appreciated feedback contact your personal contact at Threedy or open a ticket at our ServiceDesk.
......@@ -9,7 +9,7 @@ volumes:
services:
i3dhub-consul:
image: ${IMAGE_REGISTRY_HOST}/i3dhub-consul:e8717e21086b5da88fb2978e6c8717d3
image: ${IMAGE_REGISTRY_HOST}/i3dhub-consul:201b23b3ed08aa3dfd5a999c19764062
environment:
CONSUL_PORT: "8500"
CONSUL_CONTENT_PATH: /consul/ui/
......@@ -25,7 +25,7 @@ services:
restart: unless-stopped
i3dhub-apigw:
image: ${IMAGE_REGISTRY_HOST}/i3dhub-apigw:e8717e21086b5da88fb2978e6c8717d3
image: ${IMAGE_REGISTRY_HOST}/i3dhub-apigw:201b23b3ed08aa3dfd5a999c19764062
ports:
- "${HUB_NODE_PORT}:8080"
env_file:
......@@ -35,7 +35,7 @@ services:
restart: unless-stopped
i3dhub-adminsvc:
image: ${IMAGE_REGISTRY_HOST}/i3dhub-adminsvc:e8717e21086b5da88fb2978e6c8717d3
image: ${IMAGE_REGISTRY_HOST}/i3dhub-adminsvc:201b23b3ed08aa3dfd5a999c19764062
volumes:
- rabbitmq_volume:/var/lib/rabbitmq
- elastic_volume:/usr/share/elasticsearch/data
......@@ -50,7 +50,7 @@ services:
restart: unless-stopped
i3dhub-keystore:
image: ${IMAGE_REGISTRY_HOST}/i3dhub-keystore:e8717e21086b5da88fb2978e6c8717d3
image: ${IMAGE_REGISTRY_HOST}/i3dhub-keystore:201b23b3ed08aa3dfd5a999c19764062
env_file:
- .env.elastic
- .env
......@@ -60,7 +60,7 @@ services:
restart: unless-stopped
i3dhub-authsvc:
image: ${IMAGE_REGISTRY_HOST}/i3dhub-authsvc:e8717e21086b5da88fb2978e6c8717d3
image: ${IMAGE_REGISTRY_HOST}/i3dhub-authsvc:201b23b3ed08aa3dfd5a999c19764062
volumes:
- cache_volume:/var/cache/instant3Dhub/
env_file:
......@@ -71,7 +71,7 @@ services:
restart: unless-stopped
i3dhub-rabbitmq:
image: ${IMAGE_REGISTRY_HOST}/i3dhub-rabbitmq:e8717e21086b5da88fb2978e6c8717d3
image: ${IMAGE_REGISTRY_HOST}/i3dhub-rabbitmq:201b23b3ed08aa3dfd5a999c19764062
environment:
RABBITMQ_ERLANG_COOKIE: "SWQOKODSQALRPCLNMEQG"
RABBITMQ_DEFAULT_USER: "guest"
......@@ -94,7 +94,7 @@ services:
restart: unless-stopped
i3dhub-postgres:
image: ${IMAGE_REGISTRY_HOST}/i3dhub-postgres:e8717e21086b5da88fb2978e6c8717d3
image: ${IMAGE_REGISTRY_HOST}/i3dhub-postgres:201b23b3ed08aa3dfd5a999c19764062
environment:
POSTGRES_USER: i3dhub
POSTGRES_PASSWORD: 12and3
......@@ -113,7 +113,7 @@ services:
restart: unless-stopped
i3dhub-resourcegw:
image: ${IMAGE_REGISTRY_HOST}/i3dhub-resourcegw:e8717e21086b5da88fb2978e6c8717d3
image: ${IMAGE_REGISTRY_HOST}/i3dhub-resourcegw:201b23b3ed08aa3dfd5a999c19764062
env_file:
- .env.elastic
- .env
......@@ -124,7 +124,7 @@ services:
restart: unless-stopped
i3dhub-entrygw:
image: ${IMAGE_REGISTRY_HOST}/i3dhub-entrygw:e8717e21086b5da88fb2978e6c8717d3
image: ${IMAGE_REGISTRY_HOST}/i3dhub-entrygw:201b23b3ed08aa3dfd5a999c19764062
env_file:
- .env.elastic
- .env
......@@ -137,7 +137,7 @@ services:
restart: unless-stopped
i3dhub-spacesvc:
image: ${IMAGE_REGISTRY_HOST}/i3dhub-spacesvc:e8717e21086b5da88fb2978e6c8717d3
image: ${IMAGE_REGISTRY_HOST}/i3dhub-spacesvc:201b23b3ed08aa3dfd5a999c19764062
env_file:
- .env.elastic
- .env
......@@ -146,7 +146,7 @@ services:
restart: unless-stopped
i3dhub-transcodersvc:
image: ${IMAGE_REGISTRY_HOST}/i3dhub-transcodersvc:e8717e21086b5da88fb2978e6c8717d3
image: ${IMAGE_REGISTRY_HOST}/i3dhub-transcodersvc:201b23b3ed08aa3dfd5a999c19764062
volumes:
- cache_volume:/var/cache/instant3Dhub/
env_file:
......@@ -159,7 +159,7 @@ services:
restart: unless-stopped
i3dhub-measurementsvc:
image: ${IMAGE_REGISTRY_HOST}/i3dhub-measurementsvc:e8717e21086b5da88fb2978e6c8717d3
image: ${IMAGE_REGISTRY_HOST}/i3dhub-measurementsvc:201b23b3ed08aa3dfd5a999c19764062
volumes:
- cache_volume:/var/cache/instant3Dhub/
env_file:
......@@ -172,7 +172,7 @@ services:
restart: unless-stopped
i3dhub-deliverysvc:
image: ${IMAGE_REGISTRY_HOST}/i3dhub-deliverysvc:e8717e21086b5da88fb2978e6c8717d3
image: ${IMAGE_REGISTRY_HOST}/i3dhub-deliverysvc:201b23b3ed08aa3dfd5a999c19764062
volumes:
- cache_volume:/var/cache/instant3Dhub/
env_file:
......@@ -184,7 +184,7 @@ services:
restart: unless-stopped
i3dhub-sharedsessionsvc:
image: ${IMAGE_REGISTRY_HOST}/i3dhub-sharedsessionsvc:e8717e21086b5da88fb2978e6c8717d3
image: ${IMAGE_REGISTRY_HOST}/i3dhub-sharedsessionsvc:201b23b3ed08aa3dfd5a999c19764062
volumes:
- cache_volume:/var/cache/instant3Dhub/
env_file:
......@@ -197,7 +197,7 @@ services:
restart: unless-stopped
i3dhub-spacestoresvc:
image: ${IMAGE_REGISTRY_HOST}/i3dhub-spacestoresvc:e8717e21086b5da88fb2978e6c8717d3
image: ${IMAGE_REGISTRY_HOST}/i3dhub-spacestoresvc:201b23b3ed08aa3dfd5a999c19764062
env_file:
- .env
- .env.elastic
......@@ -207,7 +207,7 @@ services:
restart: unless-stopped
i3dhub-querysvc:
image: ${IMAGE_REGISTRY_HOST}/i3dhub-querysvc:e8717e21086b5da88fb2978e6c8717d3
image: ${IMAGE_REGISTRY_HOST}/i3dhub-querysvc:201b23b3ed08aa3dfd5a999c19764062
env_file:
- .env
- .env.elastic
......@@ -217,7 +217,7 @@ services:
restart: unless-stopped
i3dhub-uploadsvc:
image: ${IMAGE_REGISTRY_HOST}/i3dhub-uploadsvc:e8717e21086b5da88fb2978e6c8717d3
image: ${IMAGE_REGISTRY_HOST}/i3dhub-uploadsvc:201b23b3ed08aa3dfd5a999c19764062
env_file:
- .env
volumes:
......
......@@ -4,7 +4,7 @@ volumes:
services:
i3dhub-elastic:
image: ${IMAGE_REGISTRY_HOST}/i3dhub-elastic:e8717e21086b5da88fb2978e6c8717d3
image: ${IMAGE_REGISTRY_HOST}/i3dhub-elastic:201b23b3ed08aa3dfd5a999c19764062
environment:
- discovery.type=single-node
healthcheck:
......@@ -17,7 +17,7 @@ services:
restart: unless-stopped
i3dhub-kibana:
image: ${IMAGE_REGISTRY_HOST}/i3dhub-kibana:e8717e21086b5da88fb2978e6c8717d3
image: ${IMAGE_REGISTRY_HOST}/i3dhub-kibana:201b23b3ed08aa3dfd5a999c19764062
environment:
SERVER_BASEPATH: /kibana
env_file:
......
......@@ -5,7 +5,7 @@ volumes:
services:
i3dhub-gpuvissvc:
image: ${IMAGE_REGISTRY_HOST}/i3dhub-gpuvissvc:e8717e21086b5da88fb2978e6c8717d3
image: ${IMAGE_REGISTRY_HOST}/i3dhub-gpuvissvc:201b23b3ed08aa3dfd5a999c19764062
runtime: nvidia
deploy:
resources:
......
......@@ -2,7 +2,7 @@ version: '3.7'
services:
i3dhub-jaeger-collector:
image: ${IMAGE_REGISTRY_HOST}/i3dhub-jaeger-collector:e8717e21086b5da88fb2978e6c8717d3
image: ${IMAGE_REGISTRY_HOST}/i3dhub-jaeger-collector:201b23b3ed08aa3dfd5a999c19764062
environment:
SPAN_STORAGE_TYPE: "elasticsearch"
ENABLE_TRACING: "true"
......@@ -14,7 +14,7 @@ services:
restart: unless-stopped
i3dhub-jaeger-query:
image: ${IMAGE_REGISTRY_HOST}/i3dhub-jaeger-query:e8717e21086b5da88fb2978e6c8717d3
image: ${IMAGE_REGISTRY_HOST}/i3dhub-jaeger-query:201b23b3ed08aa3dfd5a999c19764062
environment:
SPAN_STORAGE_TYPE: "elasticsearch"
QUERY_BASE_PATH: /jaeger
......
......@@ -41,8 +41,8 @@
add_header 'X-I3DH-Service-Reply' 'i3dhub-apigw' always;
location ~ ^/repo/(.*) {
proxy_pass http://i3dhub-entrygw$i3dhubDomain:8080/repo/$1;
location /repo {
proxy_pass http://i3dhub-entrygw$i3dhubDomain:8080;
}
location /setupSession {
proxy_pass http://i3dhub-entrygw$i3dhubDomain:8080/setupSession;
......
{{- $elkContext := .Values.elasticStackFeatures | default dict -}}
{{- $maintenance := .Values.maintenance | default dict -}}
{{- $maintenanceSys := $maintenance.system | default dict -}}
{{- $maintenanceSysExpire := $maintenanceSys.expireUnusedAge | default "0s" -}}
address: 0.0.0.0:8080
resource-gw: http://i3dhub-resourcegw:8080/resource-gateway-resource
entrygw-path: /opt/instant3Dhub/share/instant3Dhub/services/hubgw/
repo-path: /opt/instant3Dhub/share/instant3Dhub/packaged/repo/
cache-path: /var/cache/instant3Dhub/
ui-path: /opt/instant3Dhub/share/instant3Dhub/admin/ui/
automatic-expiration: {{ not (hasPrefix "0" $maintenanceSysExpire) }}