Haishi2016

My problem with leaving it all to traits is that the trait system is a very generic system. Yes it's capable of describing any intention but none of those is...

Rolling updates or canary deployments involve multiple versions of an app/component. How do you apply a trait to multiple version of the same component?

Hey @ryanzhang-oss, can you please provide an example of a trait describing rolling update or canary deployment? It will help me to understand how you envision to express such scenarios....

In that case, should we consider renaming ApplicationConfiguration to AppDeployment?

Well, if it's an deployment why don't just call it deployment. I recommend to use straightforward terms that don't need implied knowledge or understanding. "Configuration" at surface has no connection...

I'm okay if we use #336 in conjunction with ApplicationConfiguraiton to model such deployment, as long as we can rename ApplicationConfiguration to ApplicationDeployment or AppDeployment.

Sure.

My thinking on this is if we need the workload types at all. How does that affect how the app is operated?

maybe we can just do generic property matches like label selectors. Users can define whatever label they want to match (or avoid) during placement

A modeling language provides a syntax that can be translated into OAM primitives. The following is an example of a fictional syntax, which we can tentatively call it OAMLite (...