On-Host Deployment Layout

This section lists the main directories where nevisAdmin 4 creates files (in case of the classic deployment mode). This information can be useful for debugging purposes.

The different services and settings configured on a target host are managed by the in Details on what is generated exactly are not described here as they are subject to changes if the patterns are improved or the targeted software components change.

Nevis components

For Nevis components, nevisAdmin 4 stores most files in /var/opt/<nevisComponent>/<instanceName>, which follows the standard conventions for Nevis software.

Key material

Key material generated and/or deployed by nevisAdmin 4 is stored in /var/opt/keys.

This is used when you rely on automatic key management, or include key material in PEM format in your configuration. When you decide to use nevisKeybox, nevisAdmin 4 will reference files in /var/opt/neviskeybox, but will not change them. See also Configuring Key Material and Certificates.

Instance markers

For users to get a quick overview of instances installed on a host, Nevis instance patterns generate a YAML file that describes the service placed on the host.

Its path is: /etc/nevis/<instance-type>_<instance name>.yml

Sample content:

/etc/nevis/nevisidm_New_nevisIDM_Instance.yml

schemaVersion: 1.0
instance:
  type: "nevisidm"
  name: "New_nevisIDM_Instance"
  directory: "/var/opt/nevisidm/New_nevisIDM_Instance"
  source:
    url: "/nevisadmin/#/projects/DEFAULT-SIVEN-WEBSHOP/patterns/99c3475207b701e97e7a0d5d"
    projectKey: "DEFAULT-SIVEN-WEBSHOP"
    patternId: "99c3475207b701e97e7a0d5d"
    patternClass: "ch.nevis.admin.v4.plugin.nevisidm.patterns.NevisIDMDeployable"
  resources:
    ports:
    - "nevis.internal.siven.ch:8989"
  control:
    start: "systemctl restart nevisidm@New_nevisIDM_Instance"
    stop: "systemctl stop nevisidm@New_nevisIDM_Instance"
    status: "systemctl status nevisidm@New_nevisIDM_Instance"