Merge branch 'develop' of ssh://gifrerenom_labs.etsi.org/tfs/controller into openroadm-flex-grid

# Copyright 2022-2025 ETSI SDG TeraFlowSDN (TFS) (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.

# You may obtain a copy of the License at

#

#      http://www.apache.org/licenses/LICENSE-2.0

#

# Unless required by applicable law or agreed to in writing, software

# distributed under the License is distributed on an "AS IS" BASIS,

# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.

# See the License for the specific language governing permissions and

# limitations under the License.

# Avoid including these folders when building the components

.git/

.gitlab/

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

# Copyright 2022-2025 ETSI SDG TeraFlowSDN (TFS) (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.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

  # This should be last one: end-to-end integration tests

  - local: '/src/tests/.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.).

- MicroK8s (include version and add-ons):

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

## TFS deployment settings

- list of components deployed

- particular configurations you applied

## Expected behaviour

- describe the expected behavior (if you know it)

# References

## Acknowledgements

This work is funded by <FUNDING-ORGANISM> through the <CALL-NAME> <PROJECT-ACHRONYM> project with <PROJECT-ID/REFERENCE>.

# 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

## Acknowledgements

This work is funded by <FUNDING-ORGANISM> through the <CALL-NAME> <PROJECT-ACHRONYM> project with <PROJECT-ID/REFERENCE>.

# 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

## Acknowledgements

This work is funded by <FUNDING-ORGANISM> through the <CALL-NAME> <PROJECT-ACHRONYM> project with <PROJECT-ID/REFERENCE>.

# 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, ZTP, Policy, NBI, 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.

...