Merge branch 'develop' of https://labs.etsi.org/rep/tfs/controller into...

# Copyright 2021-2023 H2020 TeraFlow (https://www.teraflow-h2020.eu/)

# Copyright 2022-2023 ETSI TeraFlowSDN - TFS OSG (https://tfs.etsi.org/)

#

# Licensed under the Apache License, Version 2.0 (the "License");

# you may not use this file except in compliance with the License.

# stages of the cicd pipeline

stages:

  - dependencies

  #- dependencies

  - build

  - test

  - unit_test

  - integ_test

  - deploy

  - funct_test

  #- deploy

  #- end2end_test

# include the individual .gitlab-ci.yml of each micro-service

include:

  - local: '/manifests/.gitlab-ci.yml'

  #- local: '/manifests/.gitlab-ci.yml'

  - local: '/src/monitoring/.gitlab-ci.yml'

  - local: '/src/compute/.gitlab-ci.yml'

  - local: '/src/context/.gitlab-ci.yml'

  - local: '/src/service/.gitlab-ci.yml'

  - local: '/src/dbscanserving/.gitlab-ci.yml'

  - local: '/src/opticalattackmitigator/.gitlab-ci.yml'

  - local: '/src/opticalcentralizedattackdetector/.gitlab-ci.yml'

  - local: '/src/opticalattackdetector/.gitlab-ci.yml'

  - local: '/src/opticalattackmanager/.gitlab-ci.yml'

  - local: '/src/automation/.gitlab-ci.yml'

  - local: '/src/policy/.gitlab-ci.yml'

  - local: '/src/webui/.gitlab-ci.yml'

  #- local: '/src/webui/.gitlab-ci.yml'

  #- local: '/src/l3_distributedattackdetector/.gitlab-ci.yml'

  #- local: '/src/l3_centralizedattackdetector/.gitlab-ci.yml'

  #- local: '/src/l3_attackmitigator/.gitlab-ci.yml'

  #- local: '/src/interdomain/.gitlab-ci.yml'

  - local: '/src/pathcomp/.gitlab-ci.yml'

  #- local: '/src/dlt/.gitlab-ci.yml'

  - local: '/src/load_generator/.gitlab-ci.yml'

# Reporters

- name-of-proposer-1 (institution-of-proposer-1)

- name-of-proposer-2 (institution-of-proposer-2)

...

# Description

Describe the bug.

If needed, Attach logs and reports to your bug.

If needed, feel free to point external content as references (journal paper, Youtube video, etc.).

## Deployment environment

- Operating System (include version):

- MicroK8s (include version and add-ons):

- TeraFlowSDN (include release/branch-name/commit-id):

## TFS deployment settings

- list of components deployed

- particular configurations you applied

- any other particularity you might find important

## Sequence of actions that resulted in the bug

- be explicit and enumerate each step.

- if possible, include example calls, request files, descriptor files, etc.

## Document the explicit error

- include the traceback of the error

- include the log files of the components / scheenshoots of WebUI (attached files)

- if known, include the list of TFS components affected by the bug

## Expected behaviour

- describe the expected behavior (if you know it)

# References

1. [Reference name](https://reference-url)

2. Author1, Author2, Author3, et. al., “My demo using feature,” in Conference-Name Demo Track, 20XX.

# Proposers

- name-of-proposer-1 (institution-of-proposer-1)

- name-of-proposer-2 (institution-of-proposer-2)

...

# Description

Describe your proposal in ~1000 characters.

You can reference external content listed in section "References" as [Ref-1].

# Demo or definition of done

Describe which high level conditions needs to be fulfilled to demonstrate this feature implementation is completed.

You can reference external content (example, demo paper) listed in section "References" as [Ref-2].

# References

1. [Reference name](https://reference-url)

2. Author1, Author2, Author3, et. al., “My demo using feature,” in Conference-Name Demo Track, 20XX.

# Proposers

- name-of-proposer-1 (institution-of-proposer-1)

- name-of-proposer-2 (institution-of-proposer-2)

...

# Description

Describe your proposal in ~1000 characters.

You can reference external content listed in section "References" as [Ref-1].

# Demo or definition of done

Describe which high level conditions needs to be fulfilled to demonstrate this feature implementation is completed.

You can reference external content (example, demo paper) listed in section "References" as [Ref-2].

# References

1. [Reference name](https://reference-url)

2. Author1, Author2, Author3, et. al., “My demo using feature,” in Conference-Name Demo Track, 20XX.

# Feature Design (for New-Features)

## Clarifications to Expected Behavior Changes

Existing component logic and workflows between components that need to be altered to realize this feature.

Remember to justify these changes.

...

## References

List of relevant references for this feature.

...

## Assumptions

Enumerate the assumptions for this feature, e.g., fix XXX is implemented and merged, specific configurations, specific

components deployed.

...

## Impacted Components

List of impacted components: Context, Device, Service, PathComp, Slice, Monitoring, Automation, Policy, Compute, etc.

Just an enumeration, elaboration of impacts is done below.

## Component1 Impact

Describe impact (changes) on component1.

...

## Component2 Impact

Describe impact (changes) on component2.

...

## Testing

Describe test sets (unitary and integration) to be carried out.

This section can include/reference external experiments, demo papers, etc.

...

# Proposers

- name-of-proposer-1 (institution-of-proposer-1)

- name-of-proposer-2 (institution-of-proposer-2)

...

# Description

Describe your proposal in ~1000 characters.

You can reference external content listed in section "References" as [Ref-1].

# Demo or definition of done

Describe which high level conditions needs to be fulfilled to demonstrate this feature implementation is completed.

You can reference external content (example, demo paper) listed in section "References" as [Ref-2].

# References

1. [Reference name](https://reference-url)

2. Author1, Author2, Author3, et. al., “My demo using feature,” in Conference-Name Demo Track, 20XX.