Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Here again you can modify some parameters. in the onap_deploy stage you can specify the branch of the oom_installer (here master) and the branch of OOM

3) Resources definition

In the k8s chain definition, a parameter infra was set to precise the resources. These resources are defined in the associated pdf and idf files that can be found in https://gitlab.com/Orange-OpenSource/lfn/ci_cd/chained-ci/-/tree/master/pod_config/config

If we consider for instances k8s-onap-master, the 2 files are:

the parameters defined here are used by the collection infra managers to create the VM and or deploying infrastructure and platform components.

4) Summary

If you want to create a new daily

  • clone chained-ci repo
  • git clone https://gitlab.com/Orange-OpenSource/lfn/ci_cd/chained-ci.git
  • add onap-daily-k8s-x and onap-daily-x in the inventory https://gitlab.com/Orange-OpenSource/lfn/ci_cd/chained-ci/-/blob/master/pod_inventory/inventory
  • copy/paste master host_vars
    • cd chained-ci/pod_inventory/host_vars
    • cp onap_daily_pod4_k8s_master.yml onap_daily_x_k8s.yml
    • cp onap_daily_pod4_master.yml onap_daily_x.yml
    • Edit and adapt the chains
      • e.g. change the OOM branch to x in onap_daily_x.yml, update the versions of kubernetes, helm,..according to OOM recommentations
      • if resources changes, create an idf and pdf file in chained-ci/pod_config/config/ (note if resources are unchanged you may just reuse existing ones or copy paste existing ones for clarity)
        • cp chained-ci/pod_config/config/idf-k8s18-onap-master.yaml chained-ci/pod_config/config/idf-k8s18-onap-x.yaml
        • cp chained-ci/pod_config/config/k8s18-onap-master.yaml chained-ci/pod_config/config/k8s18-onap-x.yaml
        • and then reference infra: k8s18-onap-x in onap_daily_x_k8s.yml
  • add a schedule in gitlab vi with TARGET=onap-daily-x