## Configuration File:

#########################################################
# User Defined Configuration File.
# Information in this file is specific to the user setup.
########################################################

## The file has two main sections:
## Section-1: The first section is the physical setup information.
##            The section requires information about your servers like
##            server cimc ip address, Networking info, some cobbler settings, and
##            identify your server roles.
## Section-2: This section has openstack installation specific information.
##            The installer will abstract all but a few key pieces of configuration
##            that you will need to provide.


#######################################################
# SECTION-1 : Physical Setup Information.
#######################################################

#######################################################
# Registry credentials
#######################################################
REGISTRY_USERNAME: installer
REGISTRY_PASSWORD: B4c0n
REGISTRY_EMAIL: mercury-installer@cisco.com

## Provide the CIMC (Cisco Integrated Management Interface)
## Username/password. The information is needed for bare metal install
CIMC-COMMON:
  cimc_username: "admin"
  cimc_password: "Cisco123"

## Cobbler specific information.
## host_profile: Cobbler host profile to use to install.
## kickstart:    The cobbler kickstart file
## cobbler_username: username to access cobbler server.
## cobbler_password: password to access cobbler server.
## admin_username:  Not sure what this is.
## admin_ssh_keys: This is a generated key which will be put on the hosts.
##                  This is needed for the next install step, using Ansible.
COBBLER:
  host_profile: RHEL7.2-x86_64
  pxe_timeout: 35                             # Optional parameter (in minutes)
  cobbler_username: cobbler
  cobbler_password: cobbler                   # Optional parameter (dynamically generated if not specified)
  admin_username: root
  #admin_passwod_hash should be the output from:
  #  python -c "import crypt; print crypt.crypt('<plaintext password>')"
  admin_password_hash: me.5UXyK9.PH6
  #admin_ssh_keys:                             # Optional parameter
  #  - ssh-rsa AAAAB3NzaC1yc2EAAAABIwAAAQEAoMrVHLwpDJX8j2DiE55WtJ5NWdiryP5+FjvPEZcjLdtdWaWA7WlevwDNfvsmByxdP6EBaeskmyyU9B8ZJr1uClIN/sT6yD3gw6IkQ73Y6bl1kZxu/ZlcUUSNY4RVjSAz52/oLKs6n3wqKnn7rQuLGEZDvXnyLbqMoxHdc4PDFWiGXdlg5DIVGigO9KUncPK cisco@cisco-server
  kickstart:
    control: control-flexflash-c220m4.ks
    compute: compute-flexflash-c220m4.ks
    block_storage: storage-flexflash-c240m4.ks

## Define ELK password for logging
## elk_password: password for Kibana and Elasticsearch Access
## rotation: Data rotation in Elasticsearch
## frequency: Rotation will happen based on specified frequency
## size: Additional rotation will happen for any daily log index exceeding specified size
elk_password: elk                            # Optional parameter (dynamically generated if not specified)
elk_rotation_frequency: "monthly"
elk_rotation_size: 2

## Define VTS specific Parameters
## Remove the below line if VTS is not part of the installation
## Note VTS related paramaters must be indented.
VTS_PARAMETERS:

## Define VTS credentials
## VTS_USERNAME: Username for VTS access
## VTS_PASSWORD: Will be autogenerated and is not added here.
##  At the current time one username and password is used for all vts components
    VTS_USERNAME: '<vts_username>'               # Required parameter when VTS enabled

## VTS User Input Values
## BL_SWITCH_PORT_NUMBER0: The slot and port number for active Nexus9K port added to the inventory
## BL_SWITCH_PORT_NUMBER1: The slot and port number for backup Nexus9K port added to the inventory
## BL_SWITCH_USERNAME: Username for Nexus9K switches that are part of the VTS inventory
## BL_SWITCH_PASSWORD: Password for Nexus9K switches that are part of the VTS inventory
## BGP_ASN_NUMBER: The ASN number advertised by the VTS solution
## BGP_LOOPBACK_NUM: The loopback number to be used for BGP connections with peers
## BGP_LOOPBACK_IP: The loopback ip address to be used for BGP connections with peers
## VTS_VNI_RANGE:  The range of VNI values the operator wants to use for the VXLAN encapsulated packets
## VTS_VTC_API_IP: The IP address of the VTC on the API network for external access
## VTS_NCS_IP: The IP address the VTF's will use to register.  This is only required for EFT
## when the control components are installed outside of Mercury.
##  These are the username and passwords for any switches that VTS will push config to
##  vts components
    BL_SWITCH_PORT_NUMBER0: '<1/2>'                  # Required parameter only needed when VTS enabled
    BL_SWITCH_PORT_NUMBER1: '<1/2>'                  # Required parameter only needed when VTS enabled
    BL_SWITCH_USERNAME: '<switch_username>'          # Required parameter only needed when VTS enabled
    BL_SWITCH_PASSWORD: '<switch_password>'          # Required parameter only needed when VTS enabled
    BGP_ASN_NUMBER: '<bgp_asn_number>'            # Required parameter when VTS is enabled
    BGP_LOOPBACK_NUM: '<bgp_loopback_num>'        # Required parameter when VTS is enabled
    BGP_LOOPBACK_IP: '<bgp_loopback_ip>'      # Required parameter when VTS is enabled
    VTS_VNI_RANGE:  1002:1004                # Required parameter when VTS is enabled
    VTS_VTC_API_IP: '<vtc_ip_on_api>'        # Required parameter when VTS is enabled
#TODO JAJ - remove VTS_NCS_IP after EFT
    VTS_NCS_IP: '<vts_ncs_ip>'                    # Optional required only for EFT

## Define your networking.
## System level settings:
##   domain_name:
##   ntp_servers:
##   domain_name_servers:

NETWORKING:
  domain_name: your.domain.com
  ## Max. NTP servers = 4
  ntp_servers:
    - 1.ntp.esl.cisco.com
  # max. DNS servers = 3
  domain_name_servers:
    - 171.70.168.183
  http_proxy_servers:
    - "proxy.esl.cisco.com:8080"
  https_proxy_servers:
    - "proxy.esl.cisco.com:8080"

  networks:
  -
    vlan_id: 860
    subnet: 172.29.86.0/26
    gateway: 172.29.86.1
    segments:
      - api
-
    vlan_id: 846
    ## Needs to be an external routable network
    subnet: 172.29.84.192/28
    gateway: 172.29.84.193
    pool:
      - 172.29.84.197 to 172.29.84.201
    segments:
      - management
      - provision
-
    ## LinuxBridge-VxLAN / VTS-VXLAN requires valid VLAN-id
    ## OVS-VLAN requires VLAN-id as "None"
    vlan_id: 3001
       subnet: 169.254.0.0/16
       gateway: 192.254.0.1
       pool:
         - 169.254.0.3 to 169.254.255.254
       segments:
         - tenant

  ## optional network 'provider", needs to be routable
  -
    vlan_id: 860
    segments:
      - provider


## Specify your server roles.
ROLES:
  control:
  ## total of 3
    - control-server-1
    - control-server-2
  compute:
  ## min of 1
    - compute-server-1
    - compute-server-2
 ## block_storage:
    ## total of 3
   ## - storage-server-1
   ## - storage-server-2
   ## - storage-server-3
 ## object_storage:
 ## networker:


## Server common
## Provide the username (default: root)
## What is this 'root' username for'
##  can this be changed to something different than 'root"
SERVER_COMMON:
  server_username: root

## Server information:
## The only two configuration items required are the
## 'cimc_ip' under 'cimc_info' and the 'rack_id' under 'rack_info'.
## The 'rack_id' is mandatory for control servers as it is used during service orchestration
## to place HA services on controllers in different Racks to provide redundancy.
##
## The following 'cimc_info' information is entirely optional.
## cimc_username, cimc_password, boot_drive
## Default boot drive is SDCARD (Flexflash)
## Default vnic_SLOT is the first slot in UCS

SERVERS:
  control-server-1:
    cimc_info: {'cimc_ip': '10.23.223.124’}
    rack_info: {'rack_id': 'RackA'}

  control-server-2:
    cimc_info: {'cimc_ip': '10.23.223.125’}
    rack_info: {'rack_id': 'RackA'}

  compute-server-1:
    cimc_info: {'cimc_ip': '10.23.223.126'}
    rack_info: {'rack_id': 'RackA'}
  compute-server-2:
    cimc_info: {'cimc_ip': '10.23.223.127'}
    rack_info: {'rack_id': 'RackA'}

## .....

#####################################################
# SECTION-2 : Openstack Installation Information.
#####################################################

## Admin Credentials.
ADMIN_USER: admin
ADMIN_TENANT_NAME: admin
ADMIN_USER_PASSWORD: password

###############################################
# HA Proxy
################################################
## external_lb_vip_address has to be part of API subnet
external_lb_vip_address: 172.29.86.52
#external_lb_vip_fqdn: <host or DNS name matching external_lb_vip_address>
VIRTUAL_ROUTER_ID: 52
external_lb_vip_tls: False
#external_lb_vip_tls: True
#external_lb_vip_cert: /root/openstack-configs/haproxy.pem
#external_lb_vip_cacert: /root/openstack-configs/haproxy-ca.crt

## internal_lb_vip_address has to be part of mgmt/provision subnet
## and outside of the mgmt/provision IP pool defined in NETWORKING section
internal_lb_vip_address: 172.29.84.202

#################################################
# NEUTRON
#################################################

# Note : use phys_ext as physical_network name when creating an external network
## Option 1: LinuxBridge-VXLAN
MECHANISM_DRIVERS: linuxbridge
TENANT_NETWORK_TYPES: "VXLAN"

# for Provider networks, just specifying the provider in the segments under
# the NETWORKING section is enough.
# Note : use phys_prov as physical_network name when creating a provider network

## Option 2: OVS-VLAN
#MECHANISM_DRIVERS: openvswitch
#TENANT_NETWORK_TYPES: "VLAN"

# For Tenant VLAN range, list of ranges separated by comma of form start:end
# is given
# TENANT_VLAN_RANGES: 1002:1004,2003:2005

## Option 3: VTS-VXLAN
#  Note: The MECHANISM_DRIVERS setting is used to enable the usage scenario for
#        the Cisco Virtual Topology System (VTS).  It does not configure the
#        the actual values used for the Neutron ML2 mechanism_drivers setting.
#        As a result of setting this value to 'vts', the appropriate settings
#        will be configured for the VTS solution.  VTS requires
#        TENANT_NETWORK_TYPES to be VLAN even though they run VXLAN.
#MECHANISM_DRIVERS: vts
#TENANT_NETWORK_TYPES: "VLAN"

# for Provider networks, just specifying the provider in the segments under
# the NETWORKING section is enough.
# Note : use phys_prov as physical_network name when creating a provider network

#################################################
# Glance
#################################################

## Glance store Configuration
## STORE_BACKEND must be set to ceph
STORE_BACKEND: ceph
GLANCE_RBD_POOL: images # This depends on the pool reserved for images on your ceph cluster
GLANCE_CLIENT_KEY: AQBATEVVYFUDFRAArbWAL5BN4yTJGdKPVwVs+A==

#################################################
# CINDER
#################################################

## Cinder Volume choice
## VOLUME_DRIVER must be ceph
VOLUME_DRIVER: ceph
CINDER_RBD_POOL: volumes # This depends on the pool reserved for volumes on your ceph cluster
CINDER_CLIENT_KEY: AQAoTEVVMAErAxAAwxV7/dJvc+pBQRho7Ui0Bg==

#################################################
# Centralized CEPH
##################################################
## These properties will be used by either glance or cinder playbooks if ceph is
## selected as backend store. The decision to select ceph for either glance or cinder
## can be made independent.
## Below configs not required for dedicated ceph
CLUSTER_ID: e2a597ff-105d-4266-b322-4887ff19212a  # Centralized Ceph cluster ID
MON_HOSTS: 172.29.74.26,172.29.74.27 # Comma separated list of monitor IPs
MON_MEMBERS: sj19-lab-ceph01,sj19-lab-ceph02 # Comma separated list of monitor hostnames
SECRET_UUID: 01caf8ee-21d9-4486-84fd-79b353270b56
NOVA_RBD_POOL: vms

#############################################
# NFV Hosts
#############################################
## CPU Pinning and Huge Page support will be enabled on the hosts defined below.
## Note: Use special word "ALL" (case insensitive) to configure all compute nodes
##       as NFV Hosts.
## The VTS option requires NFV_HOSTS: ALL
#NFV_HOSTS: ALL
#NFV_HOSTS: ['compute-server-1']

##############################################
# VM Throughput Validation
##############################################
## VMTP Configuration is optional. Needed only if VMTP run is executed
VMTP_VALIDATION:
  EXT_NET:
    NET_NAME: external
    NET_SUBNET: 172.29.84.208/28
    NET_IP_START: 172.29.84.212
    NET_IP_END: 172.29.84.222
    NET_GATEWAY: 172.29.84.209
    DNS_SERVER: 171.70.168.183

## Optional Services:
## Provide a list as appropriate
#OPTIONAL_SERVICE_LIST:
#  - heat
#  - cloudpulse

NUMA_SUPPORT: False


###################################
## NFVIMON Info
## NFVIMON config is optional, only needed when customer has NFVIMON
###################################
#PODNAME: <PODNAME: No space allowed>

#NFVIMON:
#  image: <nfvimon image path in build node>
#  MASTER:
#    hostname: <nfvimon master hostname>
#    password: <nfvimon master password>
#    admin_ip: <nfvimon master admin_ip>
#  WORKER:
#    hostname: <nfvimon worker hostname>
#    password: <nfvimon worker password>
#    admin_ip: <nfvimon worker admin_ip>
#    management_ip: <nfvimon worker management_ip>
#  DISPATCHER:
#    rabbitmq_username: <nfvimon rabbitmq username>

######Optional only needed when NFVIMON is there
#TORSWITCHINFO:
#  TORSWITCHA:
#    hostname: <TOR switch A hostname>
#    username: <TOR switch A username>
#    password: <TOR switch A password>
#    ssh_ip: <TOR switch A ssh ip>
#    ssn_num: <TOR switch A ssn num>

#  TORSWITCHB:
#    hostname: <TOR switch B hostname>
#    username: <TOR switch B username>
#    password: <TOR switch B password>
#    ssh_ip: <TOR switch B ssh ip>
#    ssn_num: <TOR switch B ssn num>