margo / technical-wg

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

2024-08-14 App Package Definition Focus Group Meeting #113

Closed github-actions[bot] closed 2 months ago

github-actions[bot] commented 3 months ago

Meeting notices

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

Agenda

Review Project Board

Review PRs

Review Issues

AOB

Items for next meeting

Adjournment

phil-abb commented 2 months ago

@margo/technical-wg I was able to record the demo I mentioned during this week's call which shows a couple of different options for how we might be able to handle local OCI registries.

I'd like to hear what people think of these two options and if there are any other options people have in mind.

g0zilla commented 2 months ago

Thanks for the great demo recording. Am I correct in concluding that we either need to construct our Margo Helm apps in such a way that the repository location is configurable, or that we have to use repository mirroring? By the way, the SHA hashes of the repository digest always stay the same as long as you push and pull images from or to other registries. Only if you persist an image to disk and load it again, a new repository digest will be calculated.

phil-abb commented 2 months ago

Am I correct in concluding that we either need to construct our Margo Helm apps in such a way that the repository location is configurable, or that we have to use repository mirroring?

@g0zilla Those are the two options I see but there may be other options I'm unaware of.

By the way, the SHA hashes of the repository digest always stay the same as long as you push and pull images from or to other registries. Only if you persist an image to disk and load it again, a new repository digest will be calculated.

Ah, ok.