Contributing a new buildpack

[kevin-ortega]

I want to start the conversation about how best to contribute a java buildpack using open liberty. This buildpack will be the CN version of the cloud foundry IBM Webshere Liberty buildpack and will include the open source liberty runtime as the default and the commercial WebSphere Liberty as an optional runtime. Additionally, I want to provided the openj9 v8 and v11 JREs.

In short, this will be similar to the java buildpack but replace tomcat with open liberty and bellsoft-liberica with openj9.

I have been a contributor to the cloud foundry ibm websphere buildpack for a few years.

The goal is to contribute the buildpack by the end of the 2nd QTR 2021.

I already have a minimal working buildpack that provides either of the liberty runtimes and either openj9 v8 or v11 when the detect finds a war. . It is based on the apache-tomcat buildpack.

I understand I'll need to submit an RFC.

What can I do to ensure the RFC will be accepted and the buildpack can be contributed and available by end of this quarter?

Thank you.

[dmikusa]

Hi @kevin-ortega thanks for reaching out. Happy to give you some suggestions here.

1. The Paketo buildpacks & cloud-native buildpacks in general are a lot more composable than the previous buildpacks, so I hope you'll find this process is easier than before. Anything new would want to follow this model making buildpacks that do one thing and composing them together.

2. What we have already is an existing "java" buildpack with some opinions about the JVM vendor & app server to use. This is what we're calling a multi-buildpack or meta-buildpack. It basically just references and pulls together in a particular order, other buildpacks. If you look at https://github.com/paketo-buildpacks/java/blob/main/buildpack.toml, you can see what I mean. It's just composing things in a certain order. You could very easily take this and make an "ibm-java" (doesn't have to be this name, but the name for this would typically describe what it does, not what technology it uses) buildpack that is just composed of different stuff.

3. Right now there is no Liberty buildpack for the server itself. If you look at the Tomcat buildpack, you can see an example (it sounds like you're doing this already, which is good). In a nutshell, this buildpack will want to download Liberty, install it and drop any configurations required into the layers it generates. It should be small and do one thing so that it's potentially composable in other multi/meta buildpacks. The name for this buildpack would describe what is being installed, so this is where something like ibm-websphere-liberty would make sense as a name.

4. Good news is that we already have an OpenJ9 buildpack, so you can make use of that. If you want to contribute other JVMs, you can do so. We have a libjvm project for making this as simple as possible. A new JVM buildpack should definitely use libjvm.

So in summary, it sounds like you'd want to propose two buildpacks. One a multi/meta buildpack and one that installs/configure Liberty.

I'm not sure we could guarantee any timelines, but I would encourage you to join our next Paketo Working Group meeting & discuss more.