Petr Ospalý | fb2d0cb | 2018-12-19 14:22:00 +0100 | [diff] [blame] | 1 | --- |
| 2 | ################################### |
| 3 | # Resources configuration entries # |
| 4 | ################################### |
| 5 | |
| 6 | # Resource host information |
| 7 | |
| 8 | # folder on resource host where tars with resources are present |
| 9 | resources_dir: |
| 10 | |
| 11 | # tarfile name within this folder with offline infrastructure sw |
| 12 | resources_filename: |
| 13 | |
| 14 | # the purpose of auxiliary resources is to provide user an interface |
| 15 | # of how to distribute to infra node another big tar which might be |
| 16 | # usefull later on in application playbooks, optional param |
| 17 | aux_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 |
| 22 | resources_on_nfs: no |
| 23 | |
| 24 | # Infra node specific information |
| 25 | |
| 26 | # offline solution source data binaries will be decompressed in following dir on infra |
| 27 | # e.g. app_data_path: /opt/onap |
| 28 | app_data_path: |
| 29 | |
| 30 | # additional data path for auxiliary data transfer |
| 31 | # e.g. aux_data_path: /opt/onap/onap_me_docker_images |
| 32 | aux_data_path: |
| 33 | |
| 34 | |
| 35 | |
| 36 | ########################################## |
| 37 | # Offline Infrastructure specific params # |
| 38 | ########################################## |
| 39 | |
| 40 | # information from which rootCA is created |
| 41 | # e.g. |
| 42 | # organization_name: Samsung |
| 43 | # state_or_province_name: Poland |
| 44 | # country_name: PL |
| 45 | # locality_name: Krakow |
| 46 | certificates: |
| 47 | organization_name: |
| 48 | state_or_province_name: |
| 49 | country_name: |
| 50 | locality_name: |
| 51 | |
| 52 | # Force k8s cluster redeploy if it exists already |
| 53 | # Default value is to allow redeploy |
| 54 | redeploy_k8s_env: yes |
| 55 | |
| 56 | # Distribute offline rpm repository |
| 57 | # Default value is to distribute rpm |
| 58 | deploy_rpm_repository: yes |
| 59 | |
| 60 | # Offline solution is deploying app specific rpm repository and requires some name |
| 61 | # also for k8s cluster |
| 62 | # e.g. app_name: ONAP |
| 63 | app_name: |
| 64 | |
| 65 | # as nexus blob is prepopulated during build time following block |
| 66 | # of runtime_images code provides an alternative way how to insert |
| 67 | # specified images into nexus during infrastructure playbook execution |
| 68 | # images specified in there must be available inside aux_resources_filename |
| 69 | # tar file |
| 70 | # if runtime_images are not specified nothing is inserted on top of existing |
| 71 | # prebuilt nexus blob in installation time |
| 72 | # Component name must match with tar filename |
| 73 | # e.g. |
Petr Ospalý | 170d94b | 2018-12-20 16:40:58 +0100 | [diff] [blame] | 74 | # aaa-component-0.0.1.tar is expected in aux_data_path for aaa-component image |
Petr Ospalý | fb2d0cb | 2018-12-19 14:22:00 +0100 | [diff] [blame] | 75 | #runtime_images: |
Petr Ospalý | 170d94b | 2018-12-20 16:40:58 +0100 | [diff] [blame] | 76 | # aaa-component-0.0.1: |
Petr Ospalý | fb2d0cb | 2018-12-19 14:22:00 +0100 | [diff] [blame] | 77 | # registry: "nexus3.onap.org:10001" |
Petr Ospalý | 170d94b | 2018-12-20 16:40:58 +0100 | [diff] [blame] | 78 | # path: "/onap/components/aaa-component" |
Petr Ospalý | fb2d0cb | 2018-12-19 14:22:00 +0100 | [diff] [blame] | 79 | # tag: "latest" |
| 80 | runtime_images: |
| 81 | |
| 82 | |
| 83 | ############################### |
| 84 | # Application specific params # |
| 85 | ############################### |
| 86 | |
| 87 | # Project name to utilize same codebase |
| 88 | # e.g. project_configuration: onap-me |
| 89 | project_configuration: |
| 90 | |
| 91 | # App Helm charts dir. E.g. application/helm_charts/<xxx> where xxx is a charts folder name. |
| 92 | # Helm charts are expected to be inside SW package somewhere inside ./ansible/application |
| 93 | # those will be available for offline installer under /ansible/application/<helm_charts_name> |
| 94 | # for OOM project helm charts are usually within kubernetes sub-folder |
| 95 | # so the path for them can be: |
| 96 | # e.g app_helm_charts_install_directory: "/ansible/application/oom/kubernetes" |
| 97 | app_helm_charts_install_directory: |
| 98 | |
| 99 | # to specify target dir where helm charts should be copied into on infra node |
| 100 | # this should be directory with all charts and Makefile |
| 101 | # e.g. app_helm_charts_infra_directory: "{{ app_data_path }}/helm_charts" |
| 102 | app_helm_charts_infra_directory: |
| 103 | |
| 104 | # Main Helm chart to install |
| 105 | # e.g. app_helm_chart_name: onap |
| 106 | app_helm_chart_name: |
| 107 | |
Michal Ptacek | 271cf3f | 2019-01-17 20:39:46 +0000 | [diff] [blame] | 108 | # Targets for helm charts repository build |
| 109 | # e.g. for ONAP Casablanca |
| 110 | # app_helm_build_targets: |
| 111 | # - all |
| 112 | # - onap |
| 113 | app_helm_build_targets: |
| 114 | |
| 115 | # Directory with helm plugins |
| 116 | # It's an optional parameter used e.g. in OOM Casablanca |
| 117 | # app_helm_plugins_directory: "{{ app_helm_charts_infra_directory}}/kubernetes/helm/plugins/" |
| 118 | app_helm_plugins_directory: |
| 119 | |
Petr Ospalý | fb2d0cb | 2018-12-19 14:22:00 +0100 | [diff] [blame] | 120 | # Helm release name (visible in POD names) used by Helm |
| 121 | # e.g. app_helm_release_name: "{{ project_configuration }}" |
| 122 | app_helm_release_name: |
| 123 | |
| 124 | # Kubernetes namespace where application is installed |
| 125 | # e.g. app_kubernetes_namespace: onap |
| 126 | app_kubernetes_namespace: |
| 127 | |
| 128 | # Optional application custom Ansible roles name for pre and post install logic. |
| 129 | # Location of additional custom roles is defined in ansible.cfg with roles_path. |
| 130 | # e.g. application_pre_install_role: "{{ project_configuration }}-patch-role" |
| 131 | application_pre_install_role: |
| 132 | application_post_install_role: |
| 133 | |
| 134 | # any other application specific params can be specified in this file |
| 135 | # e.g. |
| 136 | # onap_values: |
| 137 | # openStackKeyStoneUrl: "http://1.2.3.4:5000" |
| 138 | # openStackServiceTenantName: "services" |
| 139 | # openStackDomain: "Default" |
| 140 | # openStackUserName: "admin" |
| 141 | # openStackEncryptedPassword: "f7920677e15e2678b0f33736189e8965" |