Multihost configuration

The multihost configuration file contains definition of the domains, hosts, and their roles that are available to run the tests. It uses the YAML language.

Basic definition

domains:
- id: <domain id>
  hosts:
  - hostname: <dns host name>
    role: <host role>
    os:
      family: <host operating system family> (optional, defaults to "linux")
    ssh:
      host: <ssh host> (optional, defaults to host name)
      port: <ssh port> (optional, defaults to 22)
      username: <ssh username> (optional, defaults to "root")
      password: <ssh password> (optional, defaults to "Secret123")
    config: <additional configuration> (optional, defaults to {})
    artifacts: <list of produced artifacts> (optional, defaults to {})

The top level element of the configuration is a list of domains. Each domain has id attribute and defines the list of available hosts.

• id: domain identifier which is used in the path inside mh fixture, see Accessing hosts - Deep dive into multihost fixtures

• hosts: list of available hosts and their roles

  • hostname: DNS host name, may not necessarily be resolvable from the machine that runs pytest

  • role: host role

  • os.family: host operating system family, defaults to “linux”, see MultihostHostOSFamily

  • ssh.host: ssh host to connect to (may be a resolvable host name or an IP address), defaults to the value of hostname

  • ssh.port: ssh port, defaults to 22

  • ssh.username: ssh username, defaults to root

  • ssh.password: ssh password for the user, defaults to Secret123

  • config: additional configuration, place for custom options, see Customize configuration

  • artifacts: list of artifacts that are automatically downloaded, see Gathering artifacts

Sample configuration file

domains:
- id: test
  hosts:
  - hostname: client.test
    role: client
    ssh:
      host: 192.168.100.10
      user: root
      password: MySecret123
    artifacts:
    - /etc/sssd/*
    - /var/log/sssd/*
    - /var/lib/sss/db/*

  - hostname: master.ldap.test
    role: ldap
    config:
      binddn: cn=Directory Manager
      bindpw: Secret123

Customize configuration

The config section of the host configuration can be used to extend the configuration with custom options that are required by your project. If the field is not set, it defaults to an empty dictionary dict().

To make a new configuration option available, simply inherit from MultihostHost and access the option through config (self.config).

Adding custom configuration options

class LDAPHost(MultihostHost[MyDomain]):
  def __init__(self, *args, **kwargs) -> None:
      super().__init__(*args, **kwargs)

      self.binddn: str = self.config.get("binddn", "cn=Directory Manager")
      """Bind DN ``config.binddn``, defaults to ``cn=Directory Manager``"""

      self.bindpw: str = self.config.get("bindpw", "Secret123")
      """Bind password ``config.bindpw``, defaults to ``Secret123``"""

The example above adds two new options binddn and bindpw. Since the options provide default values, they are optional. You can set them in the multihost configuration in the config field.

domains:
- id: test
  hosts:
  - hostname: client.test
    role: client
    ssh:
      host: 192.168.100.10
      user: root
      password: MySecret123

  - hostname: master.ldap.test
    role: ldap
    config:
      binddn: cn=Directory Manager
      bindpw: Secret123

Gathering artifacts

The artifacts field of the host definition can be used to specify which artifacts should be automatically collected from the host when a test is finished. The field contains a list of artifacts. The values are path to the artifacts with a possible wildcard character. For example:

- hostname: client.test
  role: client
  ssh:
    host: 192.168.100.10
    user: root
    password: MySecret123
  config:
    artifacts:
    - /etc/sssd/*
    - /var/log/sssd/*
    - /var/lib/sss/db/*

It is also possible to gather artifacts from pytest_mh.MultihostHost.pytest_setup() and pytest_mh.MultihostHost.pytest_teardown() calls. To do that, you need to provide artifacts as dictionary with pytest_setup, pytest_teardown and test keys.

- hostname: client.test
  role: client
  ssh:
    host: 192.168.100.10
    user: root
    password: MySecret123
  config:
    artifacts:
      pytest_setup:
      - /var/log/host_setup.log
      pytest_teardown:
      - /var/log/host_teardown.log
      test:
      - /var/log/testrun.log