Commit f2412028 authored by Lluis Gifre Renom's avatar Lluis Gifre Renom
Browse files

Merge branch 'develop' of ssh://gifrerenom_labs.etsi.org/tfs/controller into pr-p4-fabric-fix

parents 058937d8 b1fa6ce2

.gitlab/issue_templates/bug.md

+3 −4
Original line number Diff line number Diff line 
# 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.).
@@ -15,7 +13,6 @@ If needed, feel free to point external content as references (journal paper, You 
- MicroK8s (include version and add-ons):

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





## TFS deployment settings

- list of components deployed

- particular configurations you applied
@@ -33,7 +30,9 @@ If needed, feel free to point external content as references (journal paper, You 
## 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.

.gitlab/issue_templates/enhancement.md

+3 −4
Original line number Diff line number Diff line 
# 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.

.gitlab/issue_templates/new-feature-with-design.md

+3 −11
Original line number Diff line number Diff line 
# 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.

...

.gitlab/issue_templates/new-feature.md

+3 −4
Original line number Diff line number Diff line 
# 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.

manifests/qkd_appservice.yaml

+1 −1
Original line number Diff line number Diff line
@@ -38,7 +38,7 @@ spec: 
            - name: LOG_LEVEL

              value: "INFO"

            - name: CRDB_DATABASE

              value: "qkd_app"

              value: "tfs_qkd_app"

          envFrom:

            - secretRef:

                name: crdb-data