Geocube Installation Guide

Reference

Kubernetes

Deployment describes a desired state of pod: https://kubernetes.io/docs/concepts/workloads/controllers/deployment
Pods is a group of one or more containers: https://kubernetes.io/docs/concepts/workloads/pods
Secrets lets you store and manage sensitive information, such as passwords, OAuth tokens, and ssh keys: https://kubernetes.io/docs/concepts/configuration/secret
Service is an abstract way to expose an application running on a set of Pods as a network service: https://kubernetes.io/fr/docs/concepts/services-networking/service
Replication controller ensures that a specified number of pod replicas are running at any one time: https://kubernetes.io/docs/concepts/workloads/controllers/replicationcontroller
RoleBinding and Role: https://kubernetes.io/docs/reference/access-authn-authz/rbac/

Development Environment

Name	Version	link
Golang	>= 1.13	https://golang.org/doc/install
GDAL	>= 3.3	https://gdal.org
Python	>= 3.7	https://www.python.org/downloads/
PostgreSQL	>= 11	https://www.postgresql.org/download/
PostGIS	>= 2.5	https://postgis.net/install/
Docker	NC	https://docs.docker.com/engine/install/

Prerequisites

The Geocube needs:

a Geospatial database (currently supported : Postgresql with PostGIS)
a Messaging System to exchange messages between applications (currently supported: Pub/Sub)
an Object Storage, writable and readable by range-request (currently supported: local storage or GCS)
(Optional) a Scaling Platform to automatically scale the ressources (currently supported: K8S)

The Geocube can be run locally or deployed in a cluster (currently supported Kubernetes)

Architecture

The Geocube Solution is composed of three parts:

Geocube Service : to access and manage the geo data. It’s the purpose of this documentation.
Geocube Ingester : to feed the Geocube with ARD images. An example of an ingester is available www.github.com/airbusgeo/geocube-ingester.
Geocube Client: to use the geocube in an application. An example of a python client is available : www.github.com/airbusgeo/geocube-python-client

The Geocube Server is composed of the ApiServer, the Consolidater and an interface layer to integrate into the user environment.

Interfaces

To integrate into the environment of deployment, the geocube has an interface layer. Some implementations of this layer are available and the user is free to implement others depending on its own environment.

The interfaces are available in the interface folder.

Storage

Interface

The storage is used to read and write the images that are indexed in the Geocube. It must be accessible in reading by range-request and should be accessible in writing to support the consolidation (optimisation of the data). The interface is available in interface/storage package.

Currently supported storages

Currently, the geocube code supports two storage systems: GCS and filesystem. To add a storage strategy, the following methods are to be implemented:

// Download file content as a slice of byte
Download(ctx context.Context, uri string, options ...Option) ([]byte, error)
// DownloadTo a local file
DownloadTo(ctx context.Context, source string, destination string, options ...Option) error
// Upload file content into remote file
Upload(ctx context.Context, uri string, data []byte, options ...Option) error
// UploadFile into remote file
UploadFile(ctx context.Context, uri string, data io.ReadCloser, options ...Option) error
// Delete file
Delete(ctx context.Context, uri string, options ...Option) error
// Exist checks if file exist
Exist(ctx context.Context, uri string) (bool, error)
// GetAttrs returns file attribute
- GetAttrs(ctx context.Context, uri string) (Attrs, error)

The storage is infered from the prefix of the uri (protocol). The user can add an additionnal storage by implementing the interface and adding it in the interface/storage/uri/ package.

Messaging

Interface

The messaging interface is available here : interface/messaging/. It is used to communicate between the ApiServer and the Consolidater. It's a parameter of the constructor of the Service and it is configured in the following files: cmd/apiserver/main.go and cmd/consolidater/main.go.

Pubsub implementation

Geocube supports PubSub (Google Cloud Platform) messaging broker : vendor/github.com/geocube/interface/messaging/pubsub.

Topics and subscriptions are to be created.

Topics:

events
events-failed
consolidations
consolidations-failed
consolidations-worker (only if autoscaler is used)

Subscriptions:

events
consolidations
consolidations-worker (only if autoscaler is used)

These actions could be performed manually or with terraform. For more information, see: https://cloud.google.com/pubsub/docs/overview. You must have the Pub/Sub Admin role on your service account.

NB: Topics & Subscriptions must be created before running services.

A Pub/Sub emulator is available to use PubSub in a local system (with limited capacities).

Please follow the documentation to install and start the emulator.

Database

Interface

The database interface is available here : interface/database/db.go. It is used by the ApiServer as a parameter of the constructor of the service and it is configured in the following file: cmd/apiserver/main.go.

PostgreSQL Implementation

Geocube currently supports a Postgresql database with the PostGIS extension (interface/database/pg/). Create a database and run the installation SQL script in order to create all tables, schemas and roles. This script is available in Geocube code source in interface/database/pg/create_0.1.0.sql

$ psql -h <database_host> -d <database_name> -f interface/database/pg/create_0.1.0.sql

Autoscaler

The autoscaler handles the scale-up or down of the consolidator service. It’s an external service and does not have an interface. The current implementation, using Kubernetes, is available here : interface/autoscaler/ and it is used in the Autoscaler service : cmd/autoscaler/main.go

Installation - Local environment

Run With Docker

All dockerfile are available in the docker folder.

The Dockerfiles of the two services depend on a base-image:

$ docker build -f docker/Dockerfile.base-image -t geocube-base-image .
[...]
Successfully built 62eb9e6d2c0e

Then, the BASE_IMAGE must be passed as a parameter in order to build consolidater and server dockerfile:

$ docker build -f docker/Dockerfile.server . --build-arg BASE_IMAGE=geocube-base-image

$ docker build -f docker/Dockerfile.consolidater . --build-arg BASE_IMAGE=geocube-base-image

You can run “docker run” command in order to start the application.

For more information concerning running option, see: https://docs.docker.com/engine/reference/commandline/run/

Build and run (GoLang)

Apiserver

For more information concerning build and run go application, see: Build and run Go Application https://golang.org/cmd/go/#hdr-Compile_packages_and_dependencies

In Geocube Repository, run go build command in order to generate executable file:

$ cd cmd/server && go build
$ ls -l
-rw-rw-r-- 1 user user     2831 mai    7 15:34 auth.go
-rw-rw-r-- 1 user user    10762 mai   24 14:56 main.go
-rwxrwxr-x 1 user user 25267224 mai   24 14:57 server

Some arguments are required in order to run this file.

$ ./server --help
Usage of ./server:
  -baSecretName string
        bearer authentication secret name
  -psConsolidationsTopic string
        pubsub consolidations topic name
  -dbConnection string
        database connection (ex: postgresql://postgres:password@localhost:5432/geocube)
  -dbHost string
        database host
  -dbName string
        database name
  -dbPassword string
        database password
  -dbSecretName string
        database secret name
  -dbUser string
        database user
  -psEventsTopic string
        pubsub events topic name
  -ingestionStorage string
        ingestion storage strategy (local/gs://)
  -local bool
        execute geocube in local environment
  -maxConnectionAge int
        grpc max age connection
  -port string
        geocube port to use (default "8080")
  -project string
        project name (gcp only)
  -workers int
        number of parallel workers per catalog request (default 1)

Example (run):

$  ./server -ingestionStorage=/tmp -dbConnection=postgresql://postgres:password@localhost:5432/geocube -eventsTopic events -consolidationsTopic consolidations -local
{"severity":"info","timestamp":"2021-05-24T15:10:57.621+0200","message":"Geocube v0.2.0"}

Consolidater

In Geocube Repository, run go build command in order to generate executable file:

$ cd cmd/consolidater && go build
$ ls -l
-rw-rw-r-- 1 user user    10762 mai   24 14:56 main.go
-rwxrwxr-x 1 user user 25267224 mai   24 14:57 consolidater

Some arguments are required in order to run this file.

$ ./consolidater --help
Usage of ./consolidater:
  -psEventTopic string
        pubsub events topic name
  -project string
        subscription project (gcp pubSub only)
  -psSubscription string
        pubsub subscription name
  -workdir string
        scratch work directory

Example (run):

$  ./consolidater -workdir=/tmp -project geocube-emulator -eventsTopic events -consolidationsTopic consolidations

Messaging Broker

RabbitMq

For more information, see: https://www.rabbitmq.com/#getstarted

You can easily run a rabbitmq application with docker. Run the following command:

$ docker run -d -p 5672:5672 -p 15672:15672 --name rabbit rabbitmq:3-management

NB: rabbitMq is not supported yet by Geocube.

Pub/Sub (Emulator)

For more information, see: https://cloud.google.com/pubsub/docs/emulator

You can launch a local emulator with this command:

$ gcloud beta emulators pubsub start --project=geocube-emulator
Executing: /usr/lib/google-cloud-sdk/platform/pubsub-emulator/bin/cloud-pubsub-emulator --host=localhost --port=8085
[pubsub] This is the Google Pub/Sub fake.
[pubsub] Implementation may be incomplete or differ from the real system.
[pubsub] Jun 30, 2021 3:04:05 PM com.google.cloud.pubsub.testing.v1.Main main
[pubsub] INFO: IAM integration is disabled. IAM policy methods and ACL checks are not supported
[pubsub] SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
[pubsub] SLF4J: Defaulting to no-operation (NOP) logger implementation
[pubsub] SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details.
[pubsub] Jun 30, 2021 3:04:06 PM com.google.cloud.pubsub.testing.v1.Main main
[pubsub] INFO: Server started, listening on 8085

Topics and subscription which are necessary for the proper functioning of the geocube, can be created by running the following script (replace $GEOCUBE_SERVER by the appropriate value):

$ go run tools/pubsub_emulator/main.go --project-id geocube-emulator --geocube-server https://$GEOCUBE_SERVER
2021/06/30 14:56:48 New client for project-id geocube-emulator
2021/06/30 14:56:48 Create Topic : consolidations
2021/06/30 14:56:48 Create Topic : consolidations-worker
2021/06/30 14:56:48 Create Topic : events
2021/06/30 14:56:48 Create Subscription : consolidations
2021/06/30 14:56:48 Create Subscription : consolidations-worker
2021/06/30 14:56:48 Create Subscription : events pushing to https://$GEOCUBE_SERVER/push
2021/06/30 14:56:48 Done!

In order to run geocube with the PubSub emulator, you must define the PUBSUB_EMULATOR_HOST environment variable (by default localhost:8085) before starting services.

Installation - Kubernetes Cluster

IAM & Security

All the notions of security and service account are not covered in this document. It is the responsibility of the installers. The files presented below are available as examples/templates. They do not present any notions of security.

Container Registry

You can create your own registry server: https://docs.docker.com/registry/deploying/

Docker Hub

In case the images are stored on https://hub.docker.com, you can define them as follows in your kubernetes configuration files (postgresql example: image: postgres:11):

apiVersion: extensions/v1beta1
kind: Deployment
metadata:
  name: postgresql
spec:
  replicas: 1
  template:
    spec:
      containers:
        - name: postgresql
          image: postgres:11

In this example, https://hub.docker.com/layers/postgres/library/postgres/11.0/images/sha256-05f9b83f85bdf0382b1cb8fb72d17d7c8098b0287d7dd1df4ff09aa417a0500b?context=explore image will be loaded.

Private Registry

You can configure your kubernetes deployment files with private docker registry.

For more information, see: https://kubernetes.io/docs/tasks/configure-pod-container/pull-image-private-registry/

imagePullSecrets is defined in your kubernetes configuration files and image name is specified as follow ex: image: geocube-private-image:tag

Database

Geocube server must have sufficient rights in order to read and write into database. For more information, see: https://www.postgresql.org/docs/11/auth-pg-hba-conf.html

Geocube required that max_connections must be configured as 1024. For more information, see: https://www.postgresql.org/docs/11/runtime-config-connection.html

Kubernetes example configuration files are available in deploy/k8s/database in order to deploy minimal postgresql Database. All the parameters between {{}} are mandatory:

{{POSTGRES_USER}}: user name
{{POSTGRES_PASSWORD}}: user password

$ kubectl apply -f deploy/k8s/database/database.yaml

Pubsub Emulator

Kubernetes configuration files are available in deploy/k8s/pubSubEmulator in order to deploy minimal pubSub emulator. {{PUBSUB_EMULATOR_IMAGE}} is to be defined (eg: <container_registry>/pubsub-emulator:<tag>)

$ kubectl apply -f deploy/k8s/pubSubEmulator/pubSub.yaml

You have to configure the access between PubSub and geocube’s components.

Apiserver

Apiserver must have the necessary access to communicate with the database, the messaging service as well as the rights to read and write to the storage.

Create apiserver service account

ApiServer must have suffisant rights in order to manage object storage and secrets access.

$ kubectl apply -f deploy/k8s/apiserver/service-account.yaml

Create apiserver service

$ kubectl apply -f deploy/k8s/apiserver/service.yaml

Create apiserver deployment

In order to start ApiServer, all the parameters between {{}} are to be defined in file deploy/k8s/apiserver/deployment.yaml:

{{GEOCUBE_SERVER_IMAGE}}: Geocube ApiServer Docker Image (eg. <container_registry>/geocube-go-server:<tag>)
Connection to the database {{BD_HOST}}, {{DB_USER}} and {{DB_PASSWD}}
{{INGESTION_STORAGE}}: uri to store ingested datasets (local and gcs uris are supported)
{{PUBSUB_EMULATOR_HOST}} environment variable can be added with pubSub emulator service IP (only if emulator is used)

Ex:

containers:
  - args:
      - -dbName=geocube
      - -dbUser=apiserver
      - -dbPassword=mydbPassword
      - -dbHost=localhost:5432
      - -eventsTopic=events
      - -consolidationsTopic=consolidations
      - -ingestionStorage=/geocube-datasets or gs://my-bucket/geocube-datasets
      - -maxConnectionAge=3600
      - -workers=1
    env:
      - name: PUBSUB_EMULATOR_HOST
        value: 0.0.0.0:8085
    image: eu.gcr.io/project/geocube-go-server:v1

$ kubectl apply -f deploy/k8s/apiserver/deployment.yaml

Consolidater

Consolidater must have the necessary access to communicate with the messaging service as well as the rights to read and write to the storage.

Create Consolidater RoleBinding

$ kubectl apply -f deploy/k8s/consolidater/role-binding.yaml

Create Consolidater Role (CRUD on pods & list on ReplicationControllers)

$ kubectl apply -f deploy/k8s/consolidater/role.yaml

Create Autoscaler service account

$ kubectl apply -f deploy/k8s/consolidater/autoscaler-service-account.yaml

Create Autoscaler replication controller

In order to start Autoscaler replication controller, you have to define some parameters in file deploy/k8s/consolidater/replication-controller.yaml:

{{CONSOLIDATER_IMAGE}}: Consolidater Docker Image (eg. <container_registry>/consolidater:<tag>).
{{PUBSUB_EMULATOR_HOST}} environment variable could be added with pubSub emulator service IP (only if emulator is used).

Ex:

containers:
  - name: consolidater
    image: eu.gcr.io/project/consolidater:v1
    imagePullPolicy: "Always"
    ports:
      - containerPort: 9000
        protocol: TCP
    env:
      - name: PUBSUB_EMULATOR_HOST
        value: 0.0.0.0:8085

$ kubectl apply -f deploy/k8s/consolidater/replication-controller.yaml

Create autoscaler deployment

Define Autoscaler Docker Image {{AUTOSCALER_IMAGE}} (eg. <container_registry>/autoscaler:<tag>) in file deploy/k8s/consolidater/autoscaler-deployment.yaml

Ex:

containers:
  - name: autoscaler
    image: eu.gcr.io/project/autoscaler:v1
    imagePullPolicy: Always
    args:
      - -update=30s
      - -subscription=consolidations
      - -rc=consolidater
      - -ns=default
      - -ratio=1
      - -minratio=1
      - -step=16
      - -max=256
      - -min=0
      - -pod.cost.path=/termination_cost
      - -pod.cost.port=9000

$ kubectl apply -f deploy/k8s/consolidater/autoscaler-deployment.yaml

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

INSTALL.MD

INSTALL.MD

Geocube Installation Guide

Table of Contents

Reference

Kubernetes

Development Environment

Prerequisites

Architecture

Interfaces

Storage

Interface

Currently supported storages

Messaging

Interface

Pubsub implementation

Database

Interface

PostgreSQL Implementation

Autoscaler

Installation - Local environment

Run With Docker

Build and run (GoLang)

Apiserver

Consolidater

Messaging Broker

RabbitMq

Pub/Sub (Emulator)

Installation - Kubernetes Cluster

IAM & Security

Container Registry

Docker Hub

Private Registry

Database

Pubsub Emulator

Apiserver

Consolidater

Files

INSTALL.MD

Latest commit

History

INSTALL.MD

File metadata and controls

Geocube Installation Guide

Table of Contents

Reference

Kubernetes

Development Environment

Prerequisites

Architecture

Interfaces

Storage

Interface

Currently supported storages

Messaging

Interface

Pubsub implementation

Database

Interface

PostgreSQL Implementation

Autoscaler

Installation - Local environment

Run With Docker

Build and run (GoLang)

Apiserver

Consolidater

Messaging Broker

RabbitMq

Pub/Sub (Emulator)

Installation - Kubernetes Cluster

IAM & Security

Container Registry

Docker Hub

Private Registry

Database

Pubsub Emulator

Apiserver

Consolidater