Hi all, I just wanted to let you know that we have rebooted the OpenCompose project.
The goal of OpenCompose is to make it easier for developers to on-board to Kubernetes using declarative higher level abstraction for specific Kubernetes resources. (We will support specific OpenShift resources like Routes and DeploymentConfigs as well.) Here is a quick link to our repo: https://github.com/redhat-developer/opencompose and for examples: https://github.com/redhat-developer/opencompose/tree/master/examples For longer and better explanation see the forwarded message from Kubernetes-Sig-Apps ML bellow. We always welcome your feedback! Cheers, Tomas -------- Forwarded Message -------- From: Pradeepto Bhattacharya <[email protected]> To: [email protected] Subject: OpenCompose - A higher level abstraction to define applications for Kubernetes Date: Wed, 1 Mar 2017 16:56:25 +0530 > Hi, > > At KubeCon Dev Summit, we had an excellent conversation around > "Application/Service Definition" - a higher level abstraction for > Kubernetes resources. Talking to many Kubernetes contributors during > the conference and dev summit, I felt that there is a definite need > for such a higher level declarative abstraction (and I felt that we > got some validation about the idea). > > Since then, we (few of us here at Red Hat) have been slowly but > surely working towards it. We call it "OpenCompose" [1] (obviously, > we aren't very creative with naming things). Recently, we saw a > presentation from Brian Grant at sig-apps meeting [2]. The proposal > document [3] is very detailed (thanks Brian) and a great read. We > found that there are a bunch of overlapping ideas. > > At this point, OpenCompose is a tool that understands a simple YAML > syntax (the OpenCompose file reference). A micro service can be > defined using this syntax and the OpenCompose tool can generate > Kubernetes configurations from it. We have few examples and some > documentation. We are working towards augmenting the file reference / > syntax. > > The main goal for OpenCompose is to be easy to use > application/microservice definition that developers can use without > learning much of Kubernetes concepts. It should be very easy to write > a simple application definition and from there on the tooling takes > over. How easy? Just think about UX of Docker Compose and how easy it > is for developers to write a compose file and bring up application. > We have been extensively contributing to Kompose because we strongly > believe that it helps developers migrate from Docker Compose to > Kubernetes. But not all concepts of Kubernetes can be mapped 1-1 to > Docker Compose and vice versa and this made us think about the > problem. We have factored some of our thoughts into current > implementation of OpenCompose file reference [4] and tool. > > There are many features from Brian's document that we would like to > have in OpenCompose. And I think, it can be guiding document for > OpenCompose although Brian's document is about common-of-the-shelf > (COTS), I am sure that we can leverage from it. > > We would love to present the current version of OpenCompose at the > next available slot during sig-apps weekly meeting. > > There is definitely a huge scope to improve and we need feedback from > the community. What does the sig-apps folks think about what we have > done until now? How can we collaborate and work together on this > idea? > > If you have questions about OpenCompose, please reply to this thread > , a bunch of us are subscribed to this list and we will get back to > you. > > [1] https://github.com/redhat-developer/opencompose > [2] followup on declarative application management from today's SIG > meeting > [3] Proposal document > [4] OpenCompose File Reference > > Thanks, > > Pradeepto (on behalf of my teammates) > -- > Pradeepto Bhattacharya > > -- > You received this message because you are subscribed to the Google > Groups "kubernetes-sig-apps" group. > To unsubscribe from this group and stop receiving emails from it, > send an email to [email protected]. > To post to this group, send email to kubernetes-sig-apps@googlegroups > .com. > To view this discussion on the web visit https://groups.google.com/d/ > msgid/kubernetes-sig- > apps/CADe3W8WaxRS66hjjoDQ7ySnQnTGxWnHbjc%2B3184uCycc- > 5hJKg%40mail.gmail.com. > For more options, visit https://groups.google.com/d/optout. _______________________________________________ dev mailing list [email protected] http://lists.openshift.redhat.com/openshiftmm/listinfo/dev
