search

margo / technical-wg

Repository for Technical Working Group facilitation
2 stars 0 forks source link

2024-10-08 Workload Orchestration Agent Interfaces Focus Group Meeting #162

Open github-actions[bot] opened 1 week ago

github-actions[bot] commented 1 week ago

Meeting notices - Workload Orchestration Agent Interfaces Focus

Time 0700 PDT / 1500 BST - See the time in your timezone

Antitrust Policy

The Steering Members, General Members, and Contributors acknowledge that they may compete with one another in various lines of business and that it is therefore imperative that they and their respective representatives act in a manner that does not violate any applicable antitrust laws and regulations. Each Steering Member, General Member, and Contributor may have similar agreements with others. Each Steering Member, General Member, and Contributor may design, develop, manufacture, acquire or market competitive deliverables, products and services, and conduct its business, in whatever way it chooses. No Steering Member, General Member, or Contributor is obligated to announce or market any products or services associated with or based on the Project. Without limiting the generality of the foregoing, the Steering Members, General Members, and Contributors agree not to have any discussion relating to any product pricing, methods or channels of product distribution, division of markets, allocation of customers or any other topic that should not be discussed among competitors.

Reminder - Meeting is recorded

Roll Call

Please add Attended to this issue during the meeting to denote attendance. This is to track attendance at meetings and to determine if a quorum is reached for PR approval during the meeting.

Agenda

Workload Orchestration Agent: User Stories

  1. Deploy 1 to many applications to 1 to many Margo Compliant device(s)

  2. Delete 1 to many application to a Margo compliant Device

  3. Reconfigure 1 to many applications

    • Resources / parameter change / replication settings

  4. Monitoring

    • Report to WOS current status of the defined desired state
      • Deployment status
        • Installation - per component information
      • Runtime status - (OTEL or API functionality?)
        • If a workload deployment fails/crashes how do we report this status to the WOS? OTEL or API / How to deal with this depending on the edge type(kubernetes or docker).
        • Is this OTEL which puts requirement on the WOS to implement or built within the API which would require a confiugrable frequency of reporting.
        • OTEL implications if WOS is required to integrate, there is an additional communication channel from Edge Device to WOS endpoint where it is exported.
      • Post install

  5. WOS - Tracking of configuration via Unique IDs for configurations

    • Enables Auditability / Tracking history
    • Differentiating feature or requirement?

  6. Device – Tracking of configuration

  7. Rollback Functionality

    • If the current configuration change request fails, how does the WOA

  8. Disaster recovery

    • If the device on the edge or WOS has an event that brings it offline, device should recover to last known state.

  9. Update/maintain the WOA services on Device

    • Discussion: is this part of the WOS or DOS?

  10. Discussion: Kubernetes / Docker runtime configuration change.

    • Is this a device or workload orch responsibility?

Review Project Board

seanmcilroy29 commented 1 week ago

Attended

seanmcilroy29 commented 1 week ago

Meeting minutes

Links added to meeting chat during call