Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.

OpenEarth is dedicated to automate deployment of PG ()and its other components) deploymentof the OpenEarth stack in Azure, please assist us at goal is to offer a proper VM in Azure

The first component of the OpenEarth stack we focus on is PostgreSQL plus the PostGIS extension.

Managed service

Azure offers Pstgres as a managed service for app developers, a DataBase as a service (DBaaS)

Of course you can also use this fully functional Linux Data Science Virtual Machine which includes Postgres.

or a Postgres cluster

However, because the OpenEarth partners have on-premise facilities (data centres for models, a fleet, etc.)  the architecture for azure deployment has to be fully hybrid.

Due to this requirement we cannot always use the DBaaS. Therefore we also offer an option using other technologies.


For a hybrid offering there are several options: build (automatically) from scratrch, or use a container.

There are detailed instructions on how to deploy a PG database in Azure on using only a Linux server:


After you automated the human processing time, the virtual machine spin-up time can be reduced by means of deploying containers. There are two ways to do this. First, there are classic tools to deploy full virtual machines, such as virtualbox or vmware. Vagrent Vagrant is wrapper around these tools to automate them. However, very popular nowadays is Docker to launch mini-containers fast. The differences between Docker and Vargent are explained here


as well as Vagrent boxes ( are already available for download. However, these do not contain the geospatial PostGis PostGIS extension with is essential for OpenEarth applications. Hence it makes sense to script a Docker container ourselves.


Note that some day all of the above might become unnecesary, when Azure will offer PostgreSQL via Database-as-a-Service offerings:

Of course you can also use this fully functional Linux Data Science Virtual Machine which includes PostgresFor

The next step in automation is to use docker-swarm to spin up a database with associated pgadmin and geoserver.

or a Postgres cluster