Environment Components

Here we will describe how Perun Cloud define environment and what it contains.

Component List
Environment
Service
Stack
TTL

Environment

A logical schema where you define the cloud provider you’re going to run on, what region you are going to use, and set an expression date when should Perun Cloud destroy this environment (TTL). You’ll also define how many Services it is going to include and what cloud resources (Stack) should it possess.

Service

Part of the environment schema. It describes the lowest details level of the microservice, among them:

• Image name

• Ports

• CPU

• Memory

Each service can be exposed behind a LB in a secure way (https) via Let's Encrypt. Please note, if the memory or CPU exceeds its worker’s resource Perun Cloud will wait until another worker is created.

Stack

A way to create cloud base resources to support the services need, like: S3, RDS, etc. based on the cloud vendor you choose. Please be advised, we run terraform in the background in order to create and maintain these resources. Perun Cloud maintains some pre-defined resources but we support all BOW terraform files.

TTL

A way to reduce phantom environments. Based on the user configuration, Perun Cloud will notify the user before destroying any environment and will wait for his approval. By default all new environments created will be destroyed after a week of creation. Any environment older than six months, will be deleted automatically, unless requested otherwise by email.