bibigrid.yml

  # See https://cloud.denbi.de/wiki/Tutorials/BiBiGrid/ (after update)
  # See https://github.com/BiBiServ/bibigrid/blob/master/documentation/markdown/features/configuration.md
  # First configuration also holds general cluster information and must include the master.
  # All other configurations mustn't include another master, but exactly one vpngtw instead (keys like master).

- infrastructure: openstack # former mode. Describes what cloud provider is used (others are not implemented yet)
  cloud: openstack # name of clouds.yaml cloud-specification key (which is value to top level key clouds)

  # -- BEGIN: GENERAL CLUSTER INFORMATION --
  ## sshPublicKeyFiles listed here will be added to access the cluster. A temporary key is created by bibigrid itself.
  #sshPublicKeyFiles:
  #  - [public key one]

  ## Volumes and snapshots that will be mounted to master
  # autoMount: False # WARNING: will overwrite unidentified filesystems
  #masterMounts:
  #  - [mount one]

  #nfsShares: /vol/spool/ is automatically created as a nfs
  #  - [nfsShare one]

  ## Ansible (Galaxy) roles can be added for execution # KEY NOT IMPLEMENTED YET
  #ansibleRoles:
  #  - file: SomeFile
  #    hosts: SomeHosts
  #    name: SomeName
  #    vars: SomeVars
  #    vars_file: SomeVarsFile

  #ansibleGalaxyRoles: # KEY NOT IMPLEMENTED YET
  #  - hosts: SomeHost
  #    name: SomeName
  #    galaxy: SomeGalaxy
  #    git: SomeGit
  #    url: SomeURL
  #    vars: SomeVars
  #    vars_file: SomeVarsFile

  ## Uncomment if you don't want assign a public ip to the master; for internal cluster (Tuebingen).
  #useMasterWithPublicIp: False # defaults True if False no public-ip (floating-ip) will be allocated
  # deleteTmpKeypairAfter: False
  # dontUploadCredentials: False

  # Other keys - default False
  #localFS: True
  #localDNSlookup: True
  #zabbix: True
  #nfs: True
  #ide: True # A nice way to view your cluster as if you were using Visual Studio Code

  useMasterAsCompute: True
  
  #waitForServices:  # existing service name that runs after an instance is launched. BiBiGrid's playbook will wait until service is "stopped" to avoid issues
  #  - de.NBI_Bielefeld_environment.service  # uncomment for cloud site Bielefeld

  # master configuration
  masterInstance:
    type: # existing type/flavor on your cloud. See launch instance>flavor for options
    image: # existing active image on your cloud. Consider using regex to prevent image updates from breaking your running cluster
    # features: # list

  # -- END: GENERAL CLUSTER INFORMATION --

  # fallbackOnOtherImage: False # if True, most similar image by name will be picked. A regex can also be given instead.

  # worker configuration
  #workerInstances:
  #  - type: # existing type/flavor on your cloud. See launch instance>flavor for options
  #    image: # same as master. Consider using regex to prevent image updates from breaking your running cluster
  #    count: # any number of workers you would like to create with set type, image combination
  #    # features: # list

  # Depends on cloud image
  sshUser: # for example ubuntu

  # Depends on cloud site:
  # Berlin     : regionOne
  # Bielefeld  : bielefeld
  # DKFZ       : regionOne
  # Giessen    : RegionOne
  # Heidelberg : RegionOne
  # Tuebingen  : RegionOne
  region: Bielefeld

  # Depends on cloud site:
  # Berlin     : nova
  # Bielefeld  : default
  # DKFZ       : nova
  # Giessen    : nova
  # Heidelberg : nova
  # Tuebingen  : nova
  availabilityZone: default

  # Depends on cloud site and project
  subnet: # existing subnet on your cloud. See https://openstack.cebitec.uni-bielefeld.de/project/networks/
  # or network:
  # gateway: # if you want to use a gateway for create.
    # ip: # IP of gateway to use
    # portFunction: 30000 + oct4 # variables are called: oct1.oct2.oct3.oct4

  # Uncomment if no full DNS service for started instances is available.
  # Currently, the case in Berlin, DKFZ, Heidelberg and Tuebingen.
  #localDNSLookup: True

  #features: # list

  #- [next configurations]