blob: d3cdfc1d25c1a0ba4720e20b717a289ccfc9d46d [file] [log] [blame]
Petr Ospalýfb2d0cb2018-12-19 14:22:00 +01001---
2###################################
3# Resources configuration entries #
4###################################
5
6# Resource host information
7
Samuli Silvius426e6c02019-02-06 11:25:01 +02008# Directory on resource host where tars with resources are present
Petr Ospalýfb2d0cb2018-12-19 14:22:00 +01009resources_dir:
10
Samuli Silvius426e6c02019-02-06 11:25:01 +020011# tarfile name within resources_dir directory with offline infrastructure binaries.
Petr Ospalýfb2d0cb2018-12-19 14:22:00 +010012resources_filename:
13
Samuli Silvius426e6c02019-02-06 11:25:01 +020014# tarfile name within resources_dir directory with auxiliary resources.
Petr Ospalýfb2d0cb2018-12-19 14:22:00 +010015# the purpose of auxiliary resources is to provide user an interface
Samuli Silvius426e6c02019-02-06 11:25:01 +020016# to distribute to infra node tar file with application specific files.
Petr Ospalýfb2d0cb2018-12-19 14:22:00 +010017aux_resources_filename:
18
19# resources can be exported via nfs
20# default is no - client will use ssh
21# if set yes but nfs-utils is missing then fallback to ssh
22resources_on_nfs: no
23
24# Infra node specific information
25
Samuli Silvius426e6c02019-02-06 11:25:01 +020026# Offline solution source data binaries (resources_filename tar) will be
27# decompressed in this directory on target infra server.
Petr Ospalýfb2d0cb2018-12-19 14:22:00 +010028# e.g. app_data_path: /opt/onap
29app_data_path:
30
Tomáš Levoraa0ad5c12019-03-28 17:45:55 +010031# Path for tarballs with images loaded on infrastructure server
32infra_images_path: "{{ app_data_path }}/offline_data/docker_images_infra"
33
Samuli Silvius426e6c02019-02-06 11:25:01 +020034# Path for auxiliary data in target infra server.
35# Data from resource host defined by aux_resources_filename variable is placed to this directory.
36# Currently docker images in tar format are supported (see runtime_images parameter).
37# Could be used for other kind of application specific data also.
38# e.g. aux_data_path: /opt/onap/my_extra_pods_docker_images
39aux_data_path: "{{ app_data_path }}/runtime_images_source_dir"
Petr Ospalýfb2d0cb2018-12-19 14:22:00 +010040
41
42##########################################
43# Offline Infrastructure specific params #
44##########################################
45
46# information from which rootCA is created
47# e.g.
48# organization_name: Samsung
49# state_or_province_name: Poland
50# country_name: PL
51# locality_name: Krakow
52certificates:
53 organization_name:
54 state_or_province_name:
55 country_name:
56 locality_name:
57
58# Force k8s cluster redeploy if it exists already
59# Default value is to allow redeploy
60redeploy_k8s_env: yes
61
Petr Ospalýfb2d0cb2018-12-19 14:22:00 +010062# Offline solution is deploying app specific rpm repository and requires some name
63# also for k8s cluster
Samuli Silviusf3eee9e2019-02-10 13:24:03 +020064# e.g. app_name: onap
Petr Ospalýfb2d0cb2018-12-19 14:22:00 +010065app_name:
66
Samuli Silvius426e6c02019-02-06 11:25:01 +020067# runtime_images provides an way to insert docker images
68# into nexus during infrastructure playbook execution (populated to nexus at runtime).
69# images specified must be available inside aux_resources_filename
70# tar file that is extracted by installer into aux_data_path directory in infra server.
71# Source format of an image is .tar file in aux_data_path directory and all .tar
72# files in that dir are checked to match runtime_images definition.
Petr Ospalýfb2d0cb2018-12-19 14:22:00 +010073# if runtime_images are not specified nothing is inserted on top of existing
Samuli Silvius426e6c02019-02-06 11:25:01 +020074# prebuilt nexus blob in installation time.
75# Component name must match with tar filename!
Petr Ospalýfb2d0cb2018-12-19 14:22:00 +010076# e.g.
Samuli Silviusf6f5fc42019-02-13 11:00:39 +020077# aaa/bbb-component-0.0.1.tar are expected in aux_data_path for component images.
Petr Ospalýfb2d0cb2018-12-19 14:22:00 +010078#runtime_images:
Samuli Silviusf6f5fc42019-02-13 11:00:39 +020079# aaa-component-0.0.1:
Petr Ospalýfb2d0cb2018-12-19 14:22:00 +010080# registry: "nexus3.onap.org:10001"
Petr Ospalý170d94b2018-12-20 16:40:58 +010081# path: "/onap/components/aaa-component"
Petr Ospalýfb2d0cb2018-12-19 14:22:00 +010082# tag: "latest"
Samuli Silviusf6f5fc42019-02-13 11:00:39 +020083# bbb-component-0.0.1:
84# registry: "nexus3.onap.org:10001"
85# path: "/onap/components/bbb-component"
86# tag: "latest"
87runtime_images: {}
Petr Ospalýfb2d0cb2018-12-19 14:22:00 +010088
Petr Ospalýfb2d0cb2018-12-19 14:22:00 +010089###############################
90# Application specific params #
91###############################
92
Samuli Silvius51d7d012019-03-19 08:45:54 +020093# App Helm charts directory location in installation package
94# (local path for the ansible process).
95# The path locates relative inside of this sw package
96# installation folder and must be visible for ansible docker/chroot
Samuli Silviusfe111112019-02-05 09:45:24 +020097# process to find directory and to transfer it into machine (infra node) running
98# Helm repository.
99# Content of the folder must be Helm chart directories of the app with Makefile.
100# In case of ONAP OOM it would be <oom_repo>/kubernetes folder content.
Samuli Silvius51d7d012019-03-19 08:45:54 +0200101app_helm_charts_install_directory: application/helm_charts
Petr Ospalýfb2d0cb2018-12-19 14:22:00 +0100102
Samuli Silvius426e6c02019-02-06 11:25:01 +0200103# Specify target dir where helm charts are copied into on infra node.
104# (same as content of "app_helm_charts_install_directory" copied by installer to this dir.)
105# This must be directory with all charts and Makefile.
Petr Ospalýfb2d0cb2018-12-19 14:22:00 +0100106# e.g. app_helm_charts_infra_directory: "{{ app_data_path }}/helm_charts"
Samuli Silviusfe111112019-02-05 09:45:24 +0200107app_helm_charts_infra_directory: "{{ app_data_path }}/helm_charts"
Petr Ospalýfb2d0cb2018-12-19 14:22:00 +0100108
109# Main Helm chart to install
110# e.g. app_helm_chart_name: onap
Bartek Grzybowski652e41d2019-03-04 15:34:19 +0100111app_helm_chart_name:
Petr Ospalýfb2d0cb2018-12-19 14:22:00 +0100112
Michal Ptacek271cf3f2019-01-17 20:39:46 +0000113# Targets for helm charts repository build
114# e.g. for ONAP Casablanca
115# app_helm_build_targets:
116# - all
117# - onap
118app_helm_build_targets:
119
120# Directory with helm plugins
121# It's an optional parameter used e.g. in OOM Casablanca
Samuli Silviusfe111112019-02-05 09:45:24 +0200122# app_helm_plugins_directory: "{{ app_helm_charts_install_directory}}/helm/plugins/"
Samuli Silviusf3eee9e2019-02-10 13:24:03 +0200123app_helm_plugins_directory: "{{ app_helm_charts_install_directory}}/helm/plugins/"
Michal Ptacek271cf3f2019-01-17 20:39:46 +0000124
Petr Ospalýfb2d0cb2018-12-19 14:22:00 +0100125# Helm release name (visible in POD names) used by Helm
Samuli Silviusf3eee9e2019-02-10 13:24:03 +0200126# e.g. app_helm_release_name: onap
127app_helm_release_name: "{{ app_name }}"
Petr Ospalýfb2d0cb2018-12-19 14:22:00 +0100128
129# Kubernetes namespace where application is installed
130# e.g. app_kubernetes_namespace: onap
Samuli Silviusf3eee9e2019-02-10 13:24:03 +0200131app_kubernetes_namespace: "{{ app_name }}"
Petr Ospalýfb2d0cb2018-12-19 14:22:00 +0100132
133# Optional application custom Ansible roles name for pre and post install logic.
134# Location of additional custom roles is defined in ansible.cfg with roles_path.
Bartek Grzybowski652e41d2019-03-04 15:34:19 +0100135# e.g. application_pre_install_role: "my-pre-install-role"
Petr Ospalýfb2d0cb2018-12-19 14:22:00 +0100136application_pre_install_role:
137application_post_install_role:
138
139# any other application specific params can be specified in this file
140# e.g.
141# onap_values:
142# openStackKeyStoneUrl: "http://1.2.3.4:5000"
143# openStackServiceTenantName: "services"
144# openStackDomain: "Default"
145# openStackUserName: "admin"
146# openStackEncryptedPassword: "f7920677e15e2678b0f33736189e8965"
Bartek Grzybowski30b2cbf2019-03-26 16:10:10 +0100147
148# Optional time synchronisation settings
149# timesync:
150# servers:
151# - <ip address of NTP_1>
152# - <...>
153# - <ip address of NTP_N>
154# slewclock: false
155# timezone: <timezone name from tz database>