Deployment Manager

Installations

— loading installations —

New Installation

Topology
Instances
Variables
Review & Generate

Environment name *

Customer

Topology *

Installation

An IP or a DNS name that works from the servers, not from this browser.

Does a name resolve on the server?

Run it there the way you will type it here:

getent hosts acs1.customer.net

It prints the address, or nothing at all if the server cannot resolve the name. An IP needs no check.

Every field already holds the service's own default value, so a standard install needs almost nothing typed here — change what is specific to this customer and move on.

* must be filled before you can continue
edited you changed this from the default
from step 2 filled in from the servers you entered on step 2
secret not saved here — deploy.sh asks for it on the server

Services: 0
Needs input: 0
Changed: 0

Find

Topologies

+ Build topology

— loading topologies —

Access requests

Everyone waiting for write access to an installation, oldest first. Granting also closes the request.

Operations

What broke

Failures first: what needs attention, why it happened, and the records behind every figure.

Settings

Integrations

GitHub Token

GitHub Organization

Harbor URL

Harbor Username

Harbor Password

SMTP Host

SMTP Port

SMTP Username

SMTP Password

Use TLS/SSL

Jira

Jira URL Where a bug filed from the assistant panel goes.

Jira Account Email

Jira API Token

Jira Project Key Reports are refused until this is set.

Issue Type

Assign reports to Every report lands on a person, never an unwatched queue.

Required fields of this project Save the credentials above first, then read the create screen. A project that demands a component or a module refuses every report until these are picked.

Administration

Admin Emails (comma-separated)