# =================================================================
# Licensed Materials - Property of IBM
#
# (c) Copyright IBM Corp. 2015 All Rights Reserved
#
# US Government Users Restricted Rights - Use, duplication or
# disclosure restricted by GSA ADP Schedule Contract with IBM Corp.
# =================================================================
# =================================================================
# Cloud Information
# =================================================================
cloud:
  name: VMWareRegion2
  # Cloud Description
  description: Controller + VMware driver to manage VMware
  # Cloud Database Service Type: db2, mariadb or mysql.
  # The same database service must be used for each region within the
  # whole multi-region. You can choose to directly provide this or
  # provide an existing topology file.
  database_service_type: db2
  # Cloud Messaging Service Type: rabbitmq or qpid.
  # The same messaging service must be used for each region within
  # the whole multi-region. You can choose to directly provide this
  # or provide an existing topology file.
  messaging_service_type: rabbitmq

  # Cloud Features: The cloud features to be enabled or disabled.
  features:
    self_service_portal: disabled
    platform_resource_scheduler: disabled
  # Cloud Topology: References the node name(s) for each role
  # within the cloud's topology.
  topology:
    database_node_name: database
    controller_node_name: controller
    vmware_driver_node_name: controller

# ================================================================
# Environment Information
# ================================================================
environment:
  base: example-ibm-os-single-controller-n-compute
  default_attributes:
    # (Optional) Add Default Environment Attributes

  override_attributes:
    # (Optional) Add Override Environment Attributes
    ntp.servers: [10.0.106.1, 0.pool.ntp.org, 1.pool.ntp.org, 2.pool.ntp.org, 3.pool.ntp.org]
    openstack.endpoints.db.host: db2ext.net.siae
    # Set ironic database user name.
    openstack.db.bare-metal.username: ironic2
    # Set cinder database user name
    openstack.db.block-storage.username: cinder2
    # Set nova database user name.
    openstack.db.compute.username: nova2
    # Set horizon database user name.
    openstack.db.dashboard.username: horizon2
    # Set keystone database user name
    openstack.db.identity.username: keyston2
    # Set neutron database user name.
    openstack.db.network.username: neutron2
    # Set heat database user name.
    openstack.db.orchestration.username: heat2
    # Set ceilodb2 database user name.
    openstack.db.telemetry.username: ceil2
    # Set the DB2® nosql port.
    openstack.db.telemetry.nosql.port: 27019
    # Change this value to false as the SCE service is not supported while using an external DB2 database.
    ibm.sce.service.enabled: false
    # Set the DB2 server port, such as 50000 for no SSL, 50001 for SSL.
    openstack.endpoints.db.port: 50000
    # Set this value to false if the external DB2 database is not configured for SSL.
    db2.ssl.enable: true


# ================================================================
# First_region Information
# ================================================================
first_region: VMwareSiaeRegion
  # The Keystone identity service endpoint host. Enter either the host FQDN or
  # it's IP address. Shared one keystone endpoint within the Multi-region cloud.
  # You can choose to provide this or provide an existing topology file.
  keystone_endpoint_host: srvtst-l148v.net.siae
  # Password file used to store the necessary keystone password and secrets
  # You can leave it empty(~) if "first_region_topology_file" is set.
  shared_password_file: ~
  # First region cloud topology file
  # By providing this file, it implies that you will add this new
  # cloud as a new region into existing cloud region(s).
  first_region_topology_file: /data/VMwareSiaeRegion/VMwareSiaeRegion_topology.json

# ================================================================
# Node Information
# ================================================================
nodes:
  - name: controller
    description: Cloud controller node
    fqdn: region2.net.siae
    password: chi01chi
    identity_file: ~
    nics:
      management_network: eth0
      data_network: ~
    # (Optional) Node Attribute JSON File
    attribute_file: ~

  - name: database
    description: Cloud controller node
    fqdn: db2ext.net.siae
    password: chi01chi
    identity_file: ~
    nics:
      management_network: eth0
      data_network: ~
    # (Optional) Node Attribute JSON File
    attribute_file: ~

# ================================================================
# VMware Information
# ================================================================
vmware:
  host: 9.168.118.126
  admin_user: administrator@romelab118.it
  admin_password: CHI01chi!
  # Determines if config drive should be used. When it is set to
  # be true, it means that deployed VM adopt cloud-init(for linux)
  # or cloudbase-init(for windows) for instance customization
  # with instance boot up. If it is set to be false, it will use
  # vmware tool activations.
  use_config_drive: true

  # Adding new compute services with one of the four types below
  computes:
    - type: cluster
      cluster_name: CL10890
      datastore_regex: datastore1
      datastore_cluster_name: ~
      discover: true

    # cluster_resourcepool compute service
    #- type: cluster_resourcepool
    #  cluster_name: YOUR_VCENTER_CLUSTER_NAME
    #  pool_name: CLUSTER_NAME:RESOURCEPOOL_NAME
    #  datastore_regex: datastore.*
    #  datastore_cluster_name: ~
    #  discover: true

    # host_resourcepool compute service
    #- type: host_resourcepool
    #  pool_name: HOST_NAME:RESOURCEPOOL_NAME
    #  datastore_regex: datastore.*
    #  datastore_cluster_name: ~
    #  discover: true

    # esxi compute service
    #- type: esxi
    #  host: YOUR_ESXI_HOST_IP_OR_FQDN
    #  datastore_regex: datastore.*
    #  datastore_cluster_name: ~
    #  discover: true

  networks:
    # List of networks on vCenter
    # Example of distributed switch, vlan_range is
    # taken into consideration only if use_dvs is true.
    - name: dvSwitch0
      vlan_range: ~
    # use_dvs: true

    # Example of standard switch
    # Only a name is needed for a standard switch
    - name: vSwitch0

    # - name: vSwitch1