Re: Eirini in 2019 CFAR certification requirements
For SAP, as a CFF member having developers working on Eirini fulltime, it is evident that Troy’s
> a number of us are keen to see Kubernetes-native app scheduling in CFAR distributions as soon as possible. Ideally we would like these distributions to be certified by the CF Foundation when they are released.
includes SAP as well.
Following Simon’s reasoning, not being able to certify a distribution running Eirini would actually be an adoption blocker for us. Also, similar to IBM, it is a well-kept secret that SAP is running some of the biggest Cloud Foundry deployments world-wide (oops, now I told it…), so we’ll do our part to make sure that Eirini is scaling and capable to run production workloads.
I did some “internet archeology” to see how we handled the DEA à Diego switch and certification. Unfortunately, I think the old certification docs are gone from the Cloud Foundry homepage , but there’s archive.org, fortunately:
 Feedback: For governance docs (@Chip Childers), it might be worthwhile to keep things in a public Github repo, too.
<cf-dev@...> on behalf of Simon D Moser <smoser@...>
While i agree that Eirini needs more Battle-testing and production evaluation still, i think the key is this not a certification *requirement*, but rather a *certification option*. From my point of view, IBM will have a commercial Eirini out in 2019 and we want that not to be non-certified. Up to an cf adopter whether he‘ll take the risk to pick it up or not, but if you do you should be within the certification.
FWIW, with SUSE SCF and IBM CFEE there will likely be at least two production adopter products in 2019, and the community cannot and does not want to make that decision dependent on PCF adoption. Other projects have been production tested on other CF offerings like IBM Bluemix in the past, so PCF is not (and should not be) the only quality gate for an open source project.
Von meinem iPhone gesendet