Hey all…I’ve been seeing some inconsistency when using ‘ostype’ and ‘arch’ in my component schematics. It seems that sometimes the nodeselector wont work, so my pods dont get scheduled? I’ll try to see if I can find a way to consistently recreate the issue, but wanted to see if anyone else has seen this?
I see whats going on. I’ll log an issue.
thanks for filing an issue for that @swgriffith. If you're able to get a repo on the bug, please also include instructions :)
Okay, yesterday's rebuild of the Docker image should have fixed the issue where the Helm chart was not working. Turns out, we just had a bad build of the Docker image, and all it took was a straight rebuild.
is OAM what was SF Mesh before?
Hey Ivan, good to see you here! The OAM spec had many technologies inspire it and SF Mesh was definitely one of them.
@swgriffith I was just reading through that Porter/OAM/Dapr demo! Super cool! Thanks for doing that.
Mikkel Mork Hegnhoj
@swgriffith - what Matt said ☝
No problem. It was a great learning experience!
In OAM terms would something like Knative, which has it's own CRD, technically be it's own custom Workload type? Is there a good example of implementing a custom workload type in Rudr?
Workloads types are an indicator as to how the runtime should execute a given workload. For example, the Server workload type indicates the component has a long running, scalable workload.What would the Knative workload type imply?
Knative is roughly equivalent to the Server workload, with the difference being that Knative handles creating the Service & Deployment rather than Rudr I believe
We do create the service and the deployment. And the extended workload type should be able to do Knative, but the code is just not quite there yet
Is there a community call this week? I remember we talked about doing it from kubecon, but not sure if something is scheduled or not.
Yes! There will be a community call tomorrow in person and remote
Conf room: Torrey Pines 3 | Located on 2nd floor of Marriott Marquis
just a heads up oam.dev should be fixed, with openappmodel.io redirecting to it. Let me know if it doesn't load for anyone
@suhuruli I am a bit unclear about the definition of "Infrastructure Operator". Can you or someone provide an example? In my understanding, it is like a Cloud Provider. Or it is an admin / developer who will be building part of an application?
@suhuruli Also, I am interested in joining the Asia Time Zome community meeting. Where can I find the meeting info? Thanks
@vturecek oam.dev is working fine. But openappmodel.io is not redirecting to oam.dev it just hangs
@abchow Bi-weekly APAC (Starting Dec 24, 2019), Tuesdays 1:00PM GMT+8
hi there, i've recently read about oam and wondering is it a good time now to put OAM into production
btw i am a cto in a startup
i'm looking forward to explore more into OAM
Lei Zhang (Harry)
@dragonly OAM is already in production in several clusters in Alibaba for a couple of weeks. Though I think the spec are still at early stage so I'd suggest starting from a small environment is best choice.
@resouer Great news!! Thanks for sharing. Is there any documentation describe how to use it in Alibaba's cloud?
Lei Zhang (Harry)
@abchow the service is alpha preview so invitation is required
Hi I had a general question around OAM .... how does it make use of the service catalog abstractions and open service broker specs ..... in terms of allowing the developers to make use of the service broker api to bind to existing services etc.... any thiaughts. .... thanks
Carl in 't Veld
What does the abbreviation RUDR stand for?
Hi @RoopGuron, Here is my 2 cents. OSB handles application lifecycle, for example provisioning and unprovisioning; and manages relationship between application and services, for example, Bind and unbind. OAM, on the other hand, try to solve the problems of Platform-agnostic and Separation of concerns between different roles in Cloud Application development. OAM tries to solve these problems by breaking down Cloud Application into artifacts and provides schemas to describe those artifacts. OAM specification does not limit implementation that support these schemas; i.e. OAM does not limit how provisioning is done in an OAM Runtime implementation. Now, having said that, we need to cautious about the fundamental different in "Application" between OAM and OSB / CF. In OAM, ApplicationConfig is a concept and executables (Components) are grouped by an ApplicationConfig. This comes from microservice architecture. In OSB / CF, an application contains executables. Services, such as a database service, are bind to an application. Last time I checked, OSB does not have the same concept as ApplicationConfig in OAM.
@cveld I'm not sure if it stands for anything in particular - it's an implementation of OAM for K8s; I know Dapr stands for Distributed Application Runtime
@cveldRudder. It was originally named Scylla to symbolize that it can take many kinds of workload.