17 Dec meeting notes

minutes/workload_orchestration_agent_meetings/2024.12.17-weekly.md

@@ -0,0 +1,40 @@
+### Summary Meeting Notes
+
+The meeting focused on finalizing the scope and decisions for the Margo preview release. Key points included the debate between REST API and open GitOps for providing the desired state-to-edge devices, with a consensus leaning towards REST. The team discussed the ingestion of Helm charts, considering the impact on air-gapped environments and the need for flexibility. Defining the initial release before engaging contractors was emphasized, ensuring clarity on Docker and Helm support. Other topics included avoiding external registry access, clarifying deployment status, and finalizing device capability specifications. The goal is to have these issues resolved before the 2025 kickoff.
+
+### Minutes
+
+**Discussion on REST API vs. Open GitOps** -
+Armand highlights the main topic of the meeting: deciding between REST API and Open GitOps to provide the desired state to edge devices.
+Armand mentions that the group has reached a consensus on most features but needs to finalize the method to provide the desired state.
+Erik asks about the commenting process, and Armand explains the decision tracker and the need to continue the discussion.
+Armand notes the initial proposal for Open GitOps and the pushback against it, leading to exploring alternatives.
+
+**Feedback on Helm Chart Ingestion** -
+Armand brings up the process of ingesting the Helm chart and the feedback from Josh and Red Hat.
+Erik suggests that the standard should focus on Docker Compose files, Kubernetes manifests, and Helm rather than standardizing the workload assembler (WAS) backend.
+Armand agrees and mentions the proposal to allow Kubernetes YAMLs, Helm, and Docker Compose to be included in the deployment specs.
+Russell emphasizes defining the initial release clearly before hiring contractors to avoid unnecessary risks and ensure the code is reviewed.
+
+**Concerns About Helm and Docker Support** -
+Christian and Armand discuss the importance of sticking to the decision to support Docker and Helm in the preview release v1.
+Armand clarifies that the discussion is about the mechanism of the orchestrator, not the support for Docker and Helm.
+James highlights the importance of flexibility for managing workloads in air-gapped scenarios.
+Erik adds that existing Helm software can be used outside the cluster, avoiding the need for new code.
+
+**Future Features and Scope** -
+Armand mentions potential features like rollback and disaster recovery that are currently out of scope for the preview release v1.
+James suggests making decisions that don't box out future solutions.
+Christian emphasizes that internal changes can be adjusted later without affecting external functionality.
+Armand agrees and plans to finalize the scope for the preview release one in the upcoming Boston meeting.
+
+**Finalizing Deliverables and Contractor Preparation** -
+Armand reviews the deliverables for the preview release and the need to finalize them before contacting contractors.
+Christian mentions that the decision about contractors will be made soon, and the timeline for preparation will be set.
+Armand reassures everyone that the contractors will focus on reference implementation and end-user compliance.
+The meeting concludes with Armand thanking everyone and confirming the next steps for the new year.
+
+### Action Items
+- [ ] Provide feedback on the alternatives to open GitOps in the associated GitHub issue.
+- [ ] Continue the discussion on the process of ingesting the Helm chart.
+- [ ] Finalize the Margo preview release 1 scope before engaging contractors.