metacosm

Keybase proof

I hereby claim:

• I am metacosm on github.
• I am metacosm (https://keybase.io/metacosm) on keybase.
• I have a public key whose fingerprint is 6645 F5AE FF9C 39A4 9E86 6763 A738 E2C9 466B 6FA4

To claim this, I am signing this object:

metacosm

Verifying that +metacosm is my blockchain ID. https://onename.com/metacosm

metacosm

oc v1.3.1
kubernetes v1.3.0+52492b4
features: Basic-Auth

Server https://192.168.64.2:8443
openshift v1.4.1+3f9807a
kubernetes v1.4.0+776c994

metacosm

 claprun@katana  ~  oc version
oc v1.5.0+031cbe4
kubernetes v1.5.2+43a9be4
features: Basic-Auth

Server https://192.168.64.2:8443
openshift v1.5.0+031cbe4
kubernetes v1.5.2+43a9be4
 claprun@katana  ~  oc status -v
In project myproject on server https://192.168.64.2:8443

metacosm

oc project obsidian-sb-rest
Now using project "obsidian-sb-rest" on server "https://192.168.64.2:8443".

oc get dc
NAME      REVISION   DESIRED   CURRENT   TRIGGERED BY
jenkins   1          1         0         config,image(jenkins:latest)

oc get pods
NAME               READY     STATUS    RESTARTS   AGE
jenkins-1-deploy   0/1       Error     0          2h

metacosm

project-new --named cdservice --type spring-boot
jpa-setup --db-type MYSQL --data-source-name java:jboss/datasources/CatalogDS
jpa-new-entity --named Catalog
jpa-new-field --named artist --target-entity org.cdservice.model.Catalog
jpa-new-field --named title --target-entity org.cdservice.model.Catalog
jpa-new-field --named description --length 2000 --target-entity org.cdservice.model.Catalog
jpa-new-field --named price --type java.lang.Float --target-entity org.cdservice.model.Catalog
jpa-new-field --named publicationDate --type java.util.Date --temporalType DATE --target-entity org.cdservice.model.Catalog

metacosm

#!/bin/bash
REMOTE=$(git remote get-url upstream)
git fetch upstream
git checkout redhat
git rebase upstream/redhat
rm -rf /tmp/yaml-sync && git clone "${REMOTE}" /tmp/yaml-sync
cd /tmp/yaml-sync && git checkout sb-1.4.x
cd -
git rm .openshiftio/*.yaml
cp /tmp/yaml-sync/.openshiftio/*.yaml .openshiftio/

metacosm

Title : 5 good reasons to adopt Spring Cloud Kubernetes

This talk will introduce the Spring Cloud Kubernetes project and will present the strengths of the framework to develop
Spring Boot cloud native application on Kubernetes/OpenShift platform.
Different use cases will be presented to demonstrate the difficulties you will be faced with when designing microservices targeted to a dockerized platform and how they should be designed to solve common problems such as externalising the configuration or secrets, discovering and load balancing the different services, monitoring your application using the health check pattern and aggregating traces collected from the different services or setting up a circuit breaker. We will show how you can improve your Developer Experience by adopting the Fabric8 technology to help you build/deploy more easily such project. 

metacosm

get_latest_tag() {
    local -r gitDir=${1:-.}
    local latestTag
    latestTag=$(git -C ${gitDir} describe --tags --abbrev=0 2> /dev/null)
    if [  $? -eq 0  ]; then
        echo ${latestTag}
    else
        return 1
    fi
}

metacosm

There are several supported project configurations that currently don't work.

The core issue is that Build mode i.e. s2i requires a pom.xml file at the root of your clone git 
repository. Therefore, if you want to store your components in the same git repo, you need to
have a parent pom. Personally, I think that's a bad organization as you'd want to keep your
components evolving independently but there are advantages to mono-repos.

Multiple independent components under a single git repo without a parent pom:
- Binary push: OK
- Source push: OK