{"action":"created","issue":{"url":"https://api.github.com/repos/fabric8io/fabric8-maven-plugin/issues/168","repository_url":"https://api.github.com/repos/fabric8io/fabric8-maven-plugin","labels_url":"https://api.github.com/repos/fabric8io/fabric8-maven-plugin/issues/168/labels{/name}","comments_url":"https://api.github.com/repos/fabric8io/fabric8-maven-plugin/issues/168/comments","events_url":"https://api.github.com/repos/fabric8io/fabric8-maven-plugin/issues/168/events","html_url":"https://github.com/fabric8io/fabric8-maven-plugin/issues/168","id":166026117,"number":168,"title":"figure out a packaging approach for kubernetes + openshift that can work with gofabric8","user":{"login":"jstrachan","id":30140,"avatar_url":"https://avatars.githubusercontent.com/u/30140?v=3","gravatar_id":"","url":"https://api.github.com/users/jstrachan","html_url":"https://github.com/jstrachan","followers_url":"https://api.github.com/users/jstrachan/followers","following_url":"https://api.github.com/users/jstrachan/following{/other_user}","gists_url":"https://api.github.com/users/jstrachan/gists{/gist_id}","starred_url":"https://api.github.com/users/jstrachan/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/jstrachan/subscriptions","organizations_url":"https://api.github.com/users/jstrachan/orgs","repos_url":"https://api.github.com/users/jstrachan/repos","events_url":"https://api.github.com/users/jstrachan/events{/privacy}","received_events_url":"https://api.github.com/users/jstrachan/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":8,"created_at":"2016-07-18T06:19:33Z","updated_at":"2016-07-18T06:51:46Z","closed_at":null,"body":"Right now we're using 2.x of fabric8-maven-plugin to combine json files together into distribution tarballs that gofabric8 uses to install the OpenShift Templates (either as Templates or as ConfigMaps).\r\n\r\nThe new 3.x of fabric8-maven-plugin generates an openshift.yml and a kubernetes.yml file which are quite different; as right now OpenShift doesn't support Ingress, Deployment or ReplicaSet; so we have to use DeploymentConfig + ReplicationController on OpenShift.\r\n\r\nSo we could do either of these:\r\n\r\n* generate a kubernetes tarball and openshift tarball for each package\r\n* generate a single tarball with a folder for openshift and a folder for kubernetes resources; then update gofabric8 to work with these new tarballs\r\n\r\nThe dependency mechanism used to make uber packages (like cd-pipeline, management etc) use a dependency on the kubernetes json file. Now we've 2 dependencies (kubernetes.yml + openshift.yml). We could make fabric8-maven-plugin generate a tarball/zip for each build containing both the openshift.yml and kubernetes.yml inside; so we can switch the packaging projects from 'json' to tarball dependency then combine the openshift yml files and kubernetes yml files together. Or we could just depend on the openshift.yml and the kubernetes.yml and try figure out which is which so we know where to put it?"},"comment":{"url":"https://api.github.com/repos/fabric8io/fabric8-maven-plugin/issues/comments/233246207","html_url":"https://github.com/fabric8io/fabric8-maven-plugin/issues/168#issuecomment-233246207","issue_url":"https://api.github.com/repos/fabric8io/fabric8-maven-plugin/issues/168","id":233246207,"user":{"login":"jstrachan","id":30140,"avatar_url":"https://avatars.githubusercontent.com/u/30140?v=3","gravatar_id":"","url":"https://api.github.com/users/jstrachan","html_url":"https://github.com/jstrachan","followers_url":"https://api.github.com/users/jstrachan/followers","following_url":"https://api.github.com/users/jstrachan/following{/other_user}","gists_url":"https://api.github.com/users/jstrachan/gists{/gist_id}","starred_url":"https://api.github.com/users/jstrachan/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/jstrachan/subscriptions","organizations_url":"https://api.github.com/users/jstrachan/orgs","repos_url":"https://api.github.com/users/jstrachan/repos","events_url":"https://api.github.com/users/jstrachan/events{/privacy}","received_events_url":"https://api.github.com/users/jstrachan/received_events","type":"User","site_admin":false},"created_at":"2016-07-18T06:51:46Z","updated_at":"2016-07-18T06:51:46Z","body":"we could - though I can imagine we end up with inconsistencies copy/pasting the same sets of dependencies twice to 2 different pom.xml files just so we could generate both OpenShift + Kubernetes distros. I'd rather an approach that makes it harder to break things ;). e.g. someone adds a dependency for kubernetes but forgets to do the same for openshift.\r\n\r\nAnother approach is to generate the OpenShift distro from the Kubernetes one automatically (its mostly just a s/Deployment/DeploymentConfig kinda thing)"}}
{"actor":{"display_login":"jstrachan"}}