WG06 Meeting minutes 17/04/2025
Agenda
- Software Delivery guideline has been validated, what's next ? J.Hiller
- Vendor views on GitOps - Vendors are invited to briefly share their view on GitOps
- Git strategy (repos, branches, tags)
Supports
Minutes
Approval of the WG6 guideline on Software Delivery
M.Richonne announced that the first WG6 guideline on Software delivery has been officially validated by the Sylva TSC.
The proposed motion was
Proposed Motion:
“The Technical Steering Community hereby approves the Software Delivery Guidelines produced by Sylva WG06 as presented here : https://wg06-workloads-lcm-gitops-59a50a.gitlab.io/guidelines/software_delivery_guideline/
(commit id : 3627dca766d2c3751ddca22e2d84cb2daa55f944, tag 1.0.0)
Rationale:
Main Goal: Shares recommendations to improve the software delivery of Cloud Native artifacts for GitOps operations.
Quality Assurance: Enhances the quality, security and reliability of software asset delivery.
Warning : this guideline is an end user guideline produced within Sylva WG06 context, it is not a standardization document
Voting Options:
Approve
Reject
Discussion Period: March-April 2025
Voting Period: From now to next TSC
The Sylva TSC is composed of Orange, DT, Vodafone, TIM, TEF, Nokia and Ericsson. See Sylva TSC Page for details.
What's next after the Software Delivery Guideline
TODO Joshua
Vendor views on GitOps
An invitation has been sent to CNF vendors to share their view with the WG06. 2 companies answered but it was a bit short to plan something due to time constraints and public holiday beginning of May. This discussion is postponed for the next meeting.
Git strategy (repos, branches, tags)
M.Richomme shared some feedback on how Orange is creating the CNF intents. it includes feedback on
- Git Repository structure
- Git Repository organization
- Git Branch & Tag management
- Tag and CNF versioning (double versioning leveraging semantic release)
M.Richomme indicates that the structures as well as the choice to focus on tag has evolved and is a solution but not the solution. He explains the reasons that lead to the different decisions.
Swisscom is OK also to share some feedback on this topic.
Vodafone is also interested.
M.Richomme indicates that internally, the question of a standard CNF template is raised. that is why orange created guidelines and recommendations corresponding to a kind of check list when teams want to create their own intents or integrate vendor intents.
The WG6 could work on guidelines on this topic if the community believes it makes sens.
Misc
As there were new participants (Welcome Vodafone contributors!), Some reminders have been done on