Tag Archives: openshift

Couchbase Cloud Recipes – Pick your favorite!

January 1, 2016couchbaseamazon, azure, bigstep, couchbase, digitalocean, docker, jelastic, joyent, kubernetes, openshift, vagrantarungupta

Couchbase 4.x Quick Installation provide instructions to install Couchbase on your local machine.

Would you like to run Couchbase 4.x in cloud? There are plenty of recipes available!

Looking for detailed instructions on Couchbase Cloud Recipes?

Digital Ocean
Jelastic
OpenShift
Docker
BigStep
Vagrant
Kubernetes
Joyent Triton
Amazon Web Services
Microsoft Azure
CoreOS and Kubernetes

Read more about it in Couchbase Cloud Deployments. Are there any other cloud/hosting solution where you you would like to see Couchbase running? Did I miss one where Couchbase already runs?

How is your experience of running Couchbase in the cloud?

Couchbase partners provide a complete list of partners.

As always, talk to us using StackOverflow or Forums.

Couchbase on OpenShift 3

December 20, 2015containers, couchbase, redhatcouchbase, docker, kubernetes, openshiftarungupta

OpenShift is Red Hat’s open source PaaS platform. OpenShift 3 provides a holistic experience of running your applications using Docker and Kubernetes. In a classic Red Hat way, all the work is done in the open source at OpenShift Origin. This also drives the next major release of OpenShift Online and OpenShift Enterprise.

OpenShift 3 using Docker and Kubernetes for container orchestration makes it really simple to bring any products that have a Docker image to run with minimal effort. This blog explains how to get started with Couchbase on OpenShift 3.

Getting Started with OpenShift 3

Download the latest Vagrant box (1.1 as of this writing) and Vagrantfile from: openshift.org/vm/. Copy them in the same directory.Vagrantfile is configured for 2GB memory and can be updated if you need to run more containers. OpenShift Master, Node, Docker Registry, and other components run inside the VM.This blog was written using Vagrant 1.7.4 and VirtualBox 5.0.10r104061.

Add the Vagrant Box:

vagrant box add --name openshift3 openshift-bootstrap-1.1.box 
==> box: Box file was not detected as metadata. Adding it directly...
==> box: Adding box 'openshift3' (v0) for provider: 
    box: Unpacking necessary files from: file:///Users/arungupta/tools/openshiftv3/1.1/openshift-bootstrap-1.1.box
==> box: Successfully added box 'openshift3' (v0) for 'virtualbox'!

vagrant box add --name openshift3 openshift-bootstrap-1.1.box

==> box: Box file was not detected as metadata. Adding it directly...

==> box: Adding box 'openshift3' (v0) for provider:

box: Unpacking necessary files from: file:///Users/arungupta/tools/openshiftv3/1.1/openshift-bootstrap-1.1.box

==> box: Successfully added box 'openshift3' (v0) for 'virtualbox'!

Start the Virtual Machine:

vagrant up
Bringing machine 'default' up with 'virtualbox' provider...
==> default: Setting the name of the VM: openshift3
==> default: Clearing any previously set network interfaces...
==> default: Preparing network interfaces based on configuration...
    default: Adapter 1: nat
==> default: Forwarding ports...
    default: 80 => 1080 (adapter 1)
    default: 443 => 1443 (adapter 1)
    default: 5000 => 5000 (adapter 1)
    default: 8080 => 8080 (adapter 1)
    default: 8443 => 8443 (adapter 1)
    default: 22 => 2222 (adapter 1)
==> default: Running 'pre-boot' VM customizations...
==> default: Booting VM...
==> default: Waiting for machine to boot. This may take a few minutes...
    default: SSH address: 127.0.0.1:2222
    default: SSH username: vagrant
    default: SSH auth method: private key
    default: Warning: Connection timeout. Retrying...
==> default: Machine booted and ready!
==> default: Checking for guest additions in VM...
    default: The guest additions on this VM do not match the installed version of
    default: VirtualBox! In most cases this is fine, but in rare cases it can
    default: prevent things such as shared folders from working properly. If you see
    default: shared folder errors, please make sure the guest additions within the
    default: virtual machine match the version of VirtualBox you have installed on
    default: your host and reload your VM.
    default: 
    default: Guest Additions Version: 4.3.20
    default: VirtualBox Version: 5.0

vagrant up

Bringing machine 'default' up with 'virtualbox' provider...

==> default: Setting the name of the VM: openshift3

==> default: Clearing any previously set network interfaces...

==> default: Preparing network interfaces based on configuration...

default: Adapter 1: nat

==> default: Forwarding ports...

default: 80 => 1080 (adapter 1)

default: 443 => 1443 (adapter 1)

default: 5000 => 5000 (adapter 1)

default: 8080 => 8080 (adapter 1)

default: 8443 => 8443 (adapter 1)

default: 22 => 2222 (adapter 1)

==> default: Running 'pre-boot' VM customizations...

==> default: Booting VM...

==> default: Waiting for machine to boot. This may take a few minutes...

default: SSH address: 127.0.0.1:2222

default: SSH username: vagrant

default: SSH auth method: private key

default: Warning: Connection timeout. Retrying...

==> default: Machine booted and ready!

==> default: Checking for guest additions in VM...

default: The guest additions on this VM do not match the installed version of

default: VirtualBox! In most cases this is fine, but in rare cases it can

default: prevent things such as shared folders from working properly. If you see

default: shared folder errors, please make sure the guest additions within the

default: virtual machine match the version of VirtualBox you have installed on

default: your host and reload your VM.

default:

default: Guest Additions Version: 4.3.20

default: VirtualBox Version: 5.0

Download and Configure OpenShift 3 Client

Download Mac 64-bit client tools (gem install rhc is for v2 only) from openshift.org/vm/ and extract them a in directory. The listing looks like:

tar xzvf ~/Downloads/openshift-origin-v1.1-ac7a99a-darwin-amd64.tar.gz 
x ./
x ./oadm
x ./kube-scheduler
x ./kubelet
x ./kube-apiserver
x ./openshift
x ./kube-controller-manager
x ./kube-proxy
x ./oc
x ./kubectl

tar xzvf ~/Downloads/openshift-origin-v1.1-ac7a99a-darwin-amd64.tar.gz

x ./

x ./oadm

x ./kube-scheduler

x ./kubelet

x ./kube-apiserver

x ./openshift

x ./kube-controller-manager

x ./kube-proxy

x ./oc

x ./kubectl

Verify the client version:

./oc version
oc v1.1
kubernetes v1.1.0-origin-1107-g4c8e6f4

./oc version

oc v1.1

kubernetes v1.1.0-origin-1107-g4c8e6f4

Remove ~/.kube/configor rename to something else.

./oc login
Server [https://localhost:8443]: 
The server uses a certificate signed by an unknown authority.
You can bypass the certificate check, but any data you send to the server could be intercepted by others.
Use insecure connections? (y/n): y

Authentication required for https://localhost:8443 (openshift)
Username: admin
Password: 
Login successful.

You have access to the following projects and can switch between them with 'oc project <projectname>':

  * default (current)
  * openshift
  * turbo

Using project "default".
Welcome! See 'oc help' to get started.

./oc login

Server [https://localhost:8443]:

The server uses a certificate signed by an unknown authority.

You can bypass the certificate check, but any data you send to the server could be intercepted by others.

Use insecure connections? (y/n): y

Authentication required for https://localhost:8443 (openshift)

Username: admin

Password:

You have access to the following projects and can switch between them with 'oc project <projectname>':

* default (current)

* openshift

* turbo

Using project "default".

Welcome! See 'oc help' to get started.

Create Couchbase Application in OpenShift 3

Create a new Couchbase instance:

./oc new-app arungupta/couchbase
--> Found Docker image 9131c5a (2 days old) from Docker Hub for "arungupta/couchbase"
    * An image stream will be created as "couchbase:latest" that will track this image
    * This image will be deployed in deployment config "couchbase"
    * Ports 11207/tcp, 11210/tcp, 11211/tcp, 18091/tcp, 18092/tcp, 8091/tcp, 8092/tcp, 8093/tcp will be load balanced by service "couchbase"
--> Creating resources with label app=couchbase ...
    ImageStream "couchbase" created
    DeploymentConfig "couchbase" created
    Service "couchbase" created
--> Success
    Run 'oc status' to view your app.

./oc new-app arungupta/couchbase

--> Found Docker image 9131c5a (2 days old) from Docker Hub for "arungupta/couchbase"

* An image stream will be created as "couchbase:latest" that will track this image

* This image will be deployed in deployment config "couchbase"

* Ports 11207/tcp, 11210/tcp, 11211/tcp, 18091/tcp, 18092/tcp, 8091/tcp, 8092/tcp, 8093/tcp will be load balanced by service "couchbase"

--> Creating resources with label app=couchbase ...

ImageStream "couchbase" created

DeploymentConfig "couchbase" created

Service "couchbase" created

--> Success

Run 'oc status' to view your app.

arungupta/couchbase is used as it uses Couchbase REST API to preconfigure the Couchbase server with:

Memory and index quota
Query, Data, and Index service
Username and password credentials
Install travel-sample bucket

This sample bucket will be used later for querying data.

Check the status of deployment:

./oc status
In project default on server https://localhost:8443

svc/couchbase - 172.30.84.134 ports 8091, 8092, 8093, 11207, 11210, 11211, 18091, 18092
  dc/couchbase deploys imagestreamtag/couchbase:latest 
    #1 deployed about a minute ago - 1 pod

svc/docker-registry - 172.30.236.154:5000
  dc/docker-registry deploys docker.io/openshift/origin-docker-registry:v1.1 
    #1 deployed 4 weeks ago - 1 pod

svc/kubernetes - 172.30.0.1 ports 443, 53, 53

svc/router - 172.30.233.69:80
  dc/router deploys docker.io/openshift/origin-haproxy-router:v1.1 
    #1 deployed 4 weeks ago - 1 pod

Warnings:
  * container "registry" in pod/docker-registry-1-imxqp has restarted 5 times
  * container "openshift-registry-proxy-1" in pod/openshift-registry-proxy has restarted 3 times
  * container "router" in pod/router-1-5grim has restarted 5 times

To see more, use 'oc describe <resource>/<name>'.
You can use 'oc get all' to see a list of other objects.

./oc status

In project default on server https://localhost:8443

svc/couchbase - 172.30.84.134 ports 8091, 8092, 8093, 11207, 11210, 11211, 18091, 18092

dc/couchbase deploys imagestreamtag/couchbase:latest

#1 deployed about a minute ago - 1 pod

svc/docker-registry - 172.30.236.154:5000

dc/docker-registry deploys docker.io/openshift/origin-docker-registry:v1.1

#1 deployed 4 weeks ago - 1 pod

svc/kubernetes - 172.30.0.1 ports 443, 53, 53

svc/router - 172.30.233.69:80

dc/router deploys docker.io/openshift/origin-haproxy-router:v1.1

#1 deployed 4 weeks ago - 1 pod

Warnings:

* container "registry" in pod/docker-registry-1-imxqp has restarted 5 times

* container "openshift-registry-proxy-1" in pod/openshift-registry-proxy has restarted 3 times

* container "router" in pod/router-1-5grim has restarted 5 times

To see more, use 'oc describe <resource>/<name>'.

You can use 'oc get all' to see a list of other objects.

Find the list of Pods:

client > ./oc get po
NAME                       READY     STATUS    RESTARTS   AGE
couchbase-1-5zhju          1/1       Running   0          1d
docker-registry-1-imxqp    1/1       Running   5          32d
openshift-registry-proxy   1/1       Running   3          32d
router-1-5grim             1/1       Running   5          32d

client > ./oc get po

NAME READY STATUS RESTARTS AGE

couchbase-1-5zhju 1/1 Running 0 1d

docker-registry-1-imxqp 1/1 Running 5 32d

openshift-registry-proxy 1/1 Running 3 32d

router-1-5grim 1/1 Running 5 32d

Get more details about the Couchbase pod:

./oc describe po couchbase-1-5zhju
Name:                           couchbase-1-5zhju
Namespace:                      default
Image(s):                       arungupta/couchbase@sha256:9131c5a283d79e11b6556c94b0b0f8ceba7daf5ba5982bac850100099019959f
Node:                           localhost.localdomain/10.0.2.15
Start Time:                     Sat, 19 Dec 2015 08:19:31 -0800
Labels:                         app=couchbase,deployment=couchbase-1,deploymentconfig=couchbase
Status:                         Running
Reason:                         
Message:                        
IP:                             172.17.0.7
Replication Controllers:        couchbase-1 (1/1 replicas created)
Containers:
  couchbase:
    Container ID:       docker://bd51f655c2a54f92f4634b84f455ca91642a88b925be39126f07df43ce883a33
    Image:              arungupta/couchbase@sha256:9131c5a283d79e11b6556c94b0b0f8ceba7daf5ba5982bac850100099019959f
    Image ID:           docker://c9d204bb75427500ef94263f8f53e8b78f2e56efd37543e620aebb1bc1bd7de1
    QoS Tier:
      cpu:              BestEffort
      memory:           BestEffort
    State:              Running
      Started:          Sat, 19 Dec 2015 08:20:21 -0800
    Ready:              True
    Restart Count:      0
    Environment Variables:
Conditions:
  Type          Status
  Ready         True 
Volumes:
  couchbase-volume-1:
    Type:       EmptyDir (a temporary directory that shares a pod's lifetime)
    Medium:     
  default-token-cycb6:
    Type:       Secret (a secret that should populate this volume)
    SecretName: default-token-cycb6
No events.

./oc describe po couchbase-1-5zhju

Name: couchbase-1-5zhju

Namespace: default

Image(s): arungupta/couchbase@sha256:9131c5a283d79e11b6556c94b0b0f8ceba7daf5ba5982bac850100099019959f

Node: localhost.localdomain/10.0.2.15

Start Time: Sat, 19 Dec 2015 08:19:31 -0800

Labels: app=couchbase,deployment=couchbase-1,deploymentconfig=couchbase

Status: Running

Reason:

Message:

IP: 172.17.0.7

Replication Controllers: couchbase-1 (1/1 replicas created)

Containers:

couchbase:

Container ID: docker://bd51f655c2a54f92f4634b84f455ca91642a88b925be39126f07df43ce883a33

Image: arungupta/couchbase@sha256:9131c5a283d79e11b6556c94b0b0f8ceba7daf5ba5982bac850100099019959f

Image ID: docker://c9d204bb75427500ef94263f8f53e8b78f2e56efd37543e620aebb1bc1bd7de1

QoS Tier:

cpu: BestEffort

memory: BestEffort

State: Running

Started: Sat, 19 Dec 2015 08:20:21 -0800

Ready: True

Restart Count: 0

Environment Variables:

Conditions:

Type Status

Ready True

Volumes:

couchbase-volume-1:

Type: EmptyDir (a temporary directory that shares a pod's lifetime)

Medium:

default-token-cycb6:

Type: Secret (a secret that should populate this volume)

SecretName: default-token-cycb6

No events.

Query Couchbase Sample Bucket

Log into the Vagrant box:

vagrant ssh
Last login: Wed Nov 18 18:04:32 2015 from 10.0.2.2
[vagrant@localhost ~]$

vagrant ssh

Last login: Wed Nov 18 18:04:32 2015 from 10.0.2.2

[vagrant@localhost ~]$

Find a list of all the running containers:

[vagrant@localhost ~]$ docker ps
CONTAINER ID        IMAGE                                                                                                                  COMMAND                  CREATED             STATUS              PORTS                    NAMES
bd51f655c2a5        arungupta/couchbase@sha256:9131c5a283d79e11b6556c94b0b0f8ceba7daf5ba5982bac850100099019959f                            "/entrypoint.sh /opt/"   7 minutes ago       Up 7 minutes                                 k8s_couchbase.f96da262_couchbase-1-5zhju_default_48e953db-a66c-11e5-8a75-080027c5bfa9_31dbcfec
8e5ef3e54d4e        openshift/origin-pod:v1.1                                                                                              "/pod"                   8 minutes ago       Up 8 minutes                                 k8s_POD.d7dfee57_couchbase-1-5zhju_default_48e953db-a66c-11e5-8a75-080027c5bfa9_b1bcd72d
0f7807f389d9        openshift/mysql-55-centos7:latest                                                                                      "container-entrypoint"   15 minutes ago      Up 15 minutes                                k8s_ruby-helloworld-database.448eeefe_database-1-w51ix_turbo_91adac2f-8d66-11e5-bf15-080027c5bfa9_74ecdc59
077a078e00a3        172.30.236.154:5000/turbo/origin-ruby-sample@sha256:c4ed12ec9817fca1fb41a5eb0c66f2edccf2e7375128fd6d64f7180207262193   "container-entrypoint"   16 minutes ago      Up 16 minutes                                k8s_ruby-helloworld.88353f9f_frontend-2-1lm99_turbo_42a6dd40-8d67-11e5-bf15-080027c5bfa9_d5110e41
e2105f2f4ab6        openshift/origin-haproxy-router:v1.1                                                                                   "/usr/bin/openshift-r"   16 minutes ago      Up 16 minutes                                k8s_router.c3a638e8_router-1-5grim_default_cac8c2d2-8d63-11e5-b835-080027c5bfa9_9d49a633
b98052109d08        172.30.236.154:5000/turbo/origin-ruby-sample@sha256:c4ed12ec9817fca1fb41a5eb0c66f2edccf2e7375128fd6d64f7180207262193   "container-entrypoint"   16 minutes ago      Up 16 minutes                                k8s_ruby-helloworld.88353f9f_frontend-2-hdz43_turbo_46657993-8d67-11e5-bf15-080027c5bfa9_f6394539
646dcce91f59        openshift/origin-docker-registry:v1.1                                                                                  "/bin/sh -c 'REGISTRY"   16 minutes ago      Up 16 minutes                                k8s_registry.35eb136e_docker-registry-1-imxqp_default_cb3dde6e-8d63-11e5-b835-080027c5bfa9_71586c07
d02c8c07f690        openshift/origin-registry-proxy                                                                                        "sh -cx '/bin/tcppm -"   16 minutes ago      Up 16 minutes                                k8s_openshift-registry-proxy-1.a0457375_openshift-registry-proxy_default_767fcb12-8d64-11e5-bf15-080027c5bfa9_4c413a10
23267082944f        openshift/origin-pod:v1.1                                                                                              "/pod"                   17 minutes ago      Up 16 minutes                                k8s_POD.d982fd5f_database-1-w51ix_turbo_91adac2f-8d66-11e5-bf15-080027c5bfa9_8fc2969f
bd7f82a88cb1        openshift/origin-pod:v1.1                                                                                              "/pod"                   17 minutes ago      Up 16 minutes                                k8s_POD.e127fd63_frontend-2-1lm99_turbo_42a6dd40-8d67-11e5-bf15-080027c5bfa9_3f73ddf8
d2ca01d75a0c        openshift/origin-pod:v1.1                                                                                              "/pod"                   17 minutes ago      Up 16 minutes                                k8s_POD.4d0ddc3f_router-1-5grim_default_cac8c2d2-8d63-11e5-b835-080027c5bfa9_036343da
5e25f5ba5c4c        openshift/origin-pod:v1.1                                                                                              "/pod"                   17 minutes ago      Up 16 minutes                                k8s_POD.e127fd63_frontend-2-hdz43_turbo_46657993-8d67-11e5-bf15-080027c5bfa9_122e502e
7c4b2b9e6c39        openshift/origin-pod:v1.1                                                                                              "/pod"                   17 minutes ago      Up 16 minutes                                k8s_POD.cc3ffd58_docker-registry-1-imxqp_default_cb3dde6e-8d63-11e5-b835-080027c5bfa9_0ae24ed7
85c4cf8d0808        openshift/origin-pod:v1.1                                                                                              "/pod"                   17 minutes ago      Up 16 minutes       0.0.0.0:5000->5000/tcp   k8s_POD.c686fded_openshift-registry-proxy_default_767fcb12-8d64-11e5-bf15-080027c5bfa9_04225f94

[vagrant@localhost ~]$ docker ps

CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES

bd51f655c2a5 arungupta/couchbase@sha256:9131c5a283d79e11b6556c94b0b0f8ceba7daf5ba5982bac850100099019959f "/entrypoint.sh /opt/" 7 minutes ago Up 7 minutes k8s_couchbase.f96da262_couchbase-1-5zhju_default_48e953db-a66c-11e5-8a75-080027c5bfa9_31dbcfec

8e5ef3e54d4e openshift/origin-pod:v1.1 "/pod" 8 minutes ago Up 8 minutes k8s_POD.d7dfee57_couchbase-1-5zhju_default_48e953db-a66c-11e5-8a75-080027c5bfa9_b1bcd72d

0f7807f389d9 openshift/mysql-55-centos7:latest "container-entrypoint" 15 minutes ago Up 15 minutes k8s_ruby-helloworld-database.448eeefe_database-1-w51ix_turbo_91adac2f-8d66-11e5-bf15-080027c5bfa9_74ecdc59

077a078e00a3 172.30.236.154:5000/turbo/origin-ruby-sample@sha256:c4ed12ec9817fca1fb41a5eb0c66f2edccf2e7375128fd6d64f7180207262193 "container-entrypoint" 16 minutes ago Up 16 minutes k8s_ruby-helloworld.88353f9f_frontend-2-1lm99_turbo_42a6dd40-8d67-11e5-bf15-080027c5bfa9_d5110e41

e2105f2f4ab6 openshift/origin-haproxy-router:v1.1 "/usr/bin/openshift-r" 16 minutes ago Up 16 minutes k8s_router.c3a638e8_router-1-5grim_default_cac8c2d2-8d63-11e5-b835-080027c5bfa9_9d49a633

b98052109d08 172.30.236.154:5000/turbo/origin-ruby-sample@sha256:c4ed12ec9817fca1fb41a5eb0c66f2edccf2e7375128fd6d64f7180207262193 "container-entrypoint" 16 minutes ago Up 16 minutes k8s_ruby-helloworld.88353f9f_frontend-2-hdz43_turbo_46657993-8d67-11e5-bf15-080027c5bfa9_f6394539

646dcce91f59 openshift/origin-docker-registry:v1.1 "/bin/sh -c 'REGISTRY" 16 minutes ago Up 16 minutes k8s_registry.35eb136e_docker-registry-1-imxqp_default_cb3dde6e-8d63-11e5-b835-080027c5bfa9_71586c07

d02c8c07f690 openshift/origin-registry-proxy "sh -cx '/bin/tcppm -" 16 minutes ago Up 16 minutes k8s_openshift-registry-proxy-1.a0457375_openshift-registry-proxy_default_767fcb12-8d64-11e5-bf15-080027c5bfa9_4c413a10

23267082944f openshift/origin-pod:v1.1 "/pod" 17 minutes ago Up 16 minutes k8s_POD.d982fd5f_database-1-w51ix_turbo_91adac2f-8d66-11e5-bf15-080027c5bfa9_8fc2969f

bd7f82a88cb1 openshift/origin-pod:v1.1 "/pod" 17 minutes ago Up 16 minutes k8s_POD.e127fd63_frontend-2-1lm99_turbo_42a6dd40-8d67-11e5-bf15-080027c5bfa9_3f73ddf8

d2ca01d75a0c openshift/origin-pod:v1.1 "/pod" 17 minutes ago Up 16 minutes k8s_POD.4d0ddc3f_router-1-5grim_default_cac8c2d2-8d63-11e5-b835-080027c5bfa9_036343da

5e25f5ba5c4c openshift/origin-pod:v1.1 "/pod" 17 minutes ago Up 16 minutes k8s_POD.e127fd63_frontend-2-hdz43_turbo_46657993-8d67-11e5-bf15-080027c5bfa9_122e502e

7c4b2b9e6c39 openshift/origin-pod:v1.1 "/pod" 17 minutes ago Up 16 minutes k8s_POD.cc3ffd58_docker-registry-1-imxqp_default_cb3dde6e-8d63-11e5-b835-080027c5bfa9_0ae24ed7

85c4cf8d0808 openshift/origin-pod:v1.1 "/pod" 17 minutes ago Up 16 minutes 0.0.0.0:5000->5000/tcp k8s_POD.c686fded_openshift-registry-proxy_default_767fcb12-8d64-11e5-bf15-080027c5bfa9_04225f94

Search for Couchbase container:

[vagrant@localhost ~]$ docker ps | grep couchbase
CONTAINER ID        IMAGE                                                                                                                  COMMAND                  CREATED             STATUS              PORTS                    NAMES
bd51f655c2a5        arungupta/couchbase@sha256:9131c5a283d79e11b6556c94b0b0f8ceba7daf5ba5982bac850100099019959f                            "/entrypoint.sh /opt/"   7 minutes ago       Up 7 minutes                                 k8s_couchbase.f96da262_couchbase-1-5zhju_default_48e953db-a66c-11e5-8a75-080027c5bfa9_31dbcfec
8e5ef3e54d4e        openshift/origin-pod:v1.1                                                                                              "/pod"                   8 minutes ago       Up 8 minutes                                 k8s_POD.d7dfee57_couchbase-1-5zhju_default_48e953db-a66c-11e5-8a75-080027c5bfa9_b1bcd72d
0f7807f389d9        openshift/mysql-55-centos7:latest                                                                                      "container-entrypoint"   15 minutes ago      Up 15 minutes

[vagrant@localhost ~]$ docker ps | grep couchbase

CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES

8e5ef3e54d4e openshift/origin-pod:v1.1 "/pod" 8 minutes ago Up 8 minutes k8s_POD.d7dfee57_couchbase-1-5zhju_default_48e953db-a66c-11e5-8a75-080027c5bfa9_b1bcd72d

0f7807f389d9 openshift/mysql-55-centos7:latest "container-entrypoint" 15 minutes ago Up 15 minutes

Get the id for our container:

docker ps | grep arungupta/couchbase | awk '{ print $1}'
bd51f655c2a5

docker ps | grep arungupta/couchbase | awk '{ print $1}'

bd51f655c2a5

Get IP address of the Pod where Couchbase server is running:

[vagrant@localhost ~]$ docker inspect --format '{{ index .Config.Env 6 }}' `docker ps | grep arungupta/couchbase | awk '{ print $1}'`
COUCHBASE_SERVICE_HOST=172.30.84.134

[vagrant@localhost ~]$ docker inspect --format '{{ index .Config.Env 6 }}' `docker ps | grep arungupta/couchbase | awk '{ print $1}'`

COUCHBASE_SERVICE_HOST=172.30.84.134

Use the IP address shown above to start Couchbase Query CLI:

[vagrant@localhost ~]$ docker run -it arungupta/couchbase /opt/couchbase/bin/cbq -engine=http://172.30.84.134:8093
Unable to find image 'arungupta/couchbase:latest' locally
Trying to pull repository docker.io/arungupta/couchbase ... latest: Pulling from arungupta/couchbase
62baed0d0de5: Already exists 
39387babd60f: Already exists 
6a2bc8404be0: Already exists 
bad926a6fb50: Already exists 
1a86c4c907e0: Already exists 
32132a7c82e9: Already exists 
646c3d5ebb71: Already exists 
864cbabd77ad: Already exists 
8c327c6d4e43: Already exists 
8592c697ab61: Already exists 
7734f4a832d4: Already exists 
35edb38ebc17: Already exists 
99f3eb6fb46f: Already exists 
91e5fad693c2: Already exists 
0cb81f5cc79b: Already exists 
ec58df60a109: Already exists 
c9d204bb7542: Already exists 
Digest: sha256:9131c5a283d79e11b6556c94b0b0f8ceba7daf5ba5982bac850100099019959f
Status: Downloaded newer image for docker.io/arungupta/couchbase:latest

Couchbase query shell connected to http://172.30.84.134:8093/ . Type Ctrl-D to exit.
cbq>

[vagrant@localhost ~]$ docker run -it arungupta/couchbase /opt/couchbase/bin/cbq -engine=http://172.30.84.134:8093

Unable to find image 'arungupta/couchbase:latest' locally

Trying to pull repository docker.io/arungupta/couchbase ... latest: Pulling from arungupta/couchbase

62baed0d0de5: Already exists

39387babd60f: Already exists

6a2bc8404be0: Already exists

bad926a6fb50: Already exists

1a86c4c907e0: Already exists

32132a7c82e9: Already exists

646c3d5ebb71: Already exists

864cbabd77ad: Already exists

8c327c6d4e43: Already exists

8592c697ab61: Already exists

7734f4a832d4: Already exists

35edb38ebc17: Already exists

99f3eb6fb46f: Already exists

91e5fad693c2: Already exists

0cb81f5cc79b: Already exists

ec58df60a109: Already exists

c9d204bb7542: Already exists

Digest: sha256:9131c5a283d79e11b6556c94b0b0f8ceba7daf5ba5982bac850100099019959f

Status: Downloaded newer image for docker.io/arungupta/couchbase:latest

Couchbase query shell connected to http://172.30.84.134:8093/ . Type Ctrl-D to exit.

cbq>

Query the sample bucket:

cbq> select * from `travel-sample` limit 1;
{
    "requestID": "a7bd414a-c571-4b22-8c81-30512b87730d",
    "signature": {
        "*": "*"
    },
    "results": [
        {
            "travel-sample": {
                "callsign": "MILE-AIR",
                "country": "United States",
                "iata": "Q5",
                "icao": "MLA",
                "id": 10,
                "name": "40-Mile Air",
                "type": "airline"
            }
        }
    ],
    "status": "success",
    "metrics": {
        "elapsedTime": "123.799956ms",
        "executionTime": "116.882044ms",
        "resultCount": 1,
        "resultSize": 300
    }
}

cbq> select * from `travel-sample` limit 1;

{

"requestID": "a7bd414a-c571-4b22-8c81-30512b87730d",

"signature": {

"*": "*"

"results": [

{

"travel-sample": {

"callsign": "MILE-AIR",

"country": "United States",

"iata": "Q5",

"icao": "MLA",

"id": 10,

"name": "40-Mile Air",

"type": "airline"

}

"status": "success",

"metrics": {

"elapsedTime": "123.799956ms",

"executionTime": "116.882044ms",

"resultCount": 1,

"resultSize": 300

}

Enjoy!

This blog shows the very basics of getting started with Couchbase on OpenShift 3. Future blogs will show:

How to deploy an application to OpenShift and use this Couchbase
How to make this application accessible outside OpenShift
How to scale Couchbase in OpenShift
Possibly some other interesting items that come along

Do you have a suggestion on what you’d like to see?

WildFly 9 on NetBeans, Eclipse, IntelliJ, OpenShift, and Maven (Tech Tip #86)

May 4, 2015redhat, techtip, wildflyeclipse, intellij, maven, netbeans, openshift, wildflyarungupta

WildFly 9 CR1 was recently released. Lots of cool features are included:

Intelligent load balancing
HTTP/2 and SPDY support
A new offline CLI mode
Graceful single node shutdown
A new Servlet-only distribution

And this is above the usual Java EE 7 compliance!

This blog is a quick check to verify that it works in all three major IDEs and OpenShift.

WildFly 9 and NetBeans

Lets start with NetBeans 8.0.x first. The screenshot shows WildFly 9 CR1 configured in NetBeans and started. The log is shown in the console.

Complete instructions to setup WildFly in NetBeans are in NetBeans 8 and WildFly 8.

WildFly 9 and Eclipse

Getting Started with JBoss Tools and WildFly 8 shows how to configure WildFly with JBoss Tools. Here are the series of snapshots that shows configuring WildFly 9 in JBoss Tools with Eclipse Mars M6.

A new experimental runtime …

Specify the directory …

Now WildFly 9 is configured as a Server in Eclipse …

And finally the server is up and running …

Complete details, including download and update center coordinates, are explained at JBoss Tools Alpha 2 for Eclipse Mars.

WildFly 9 and IntelliJ

WildFly 8 and IntelliJ IDEA Screencast provide complete details on how to setup IntelliJ with WildFly. The snapshot below shows WildFly 9 configured in IntelliJ 14.1.2.

WildFly 9 and OpenShift

Creating an OpenShift application is pretty straightforward as well:

tmp> rhc app create wildfly -s https://raw.githubusercontent.com/openshift-cartridges/openshift-wildfly-cartridge/wildfly-9/metadata/manifest.yml
The cartridge 'https://raw.githubusercontent.com/openshift-cartridges/openshift-wildfly-cartridge/wildfly-9/metadata/manifest.yml' will be downloaded
and installed

Application Options
-------------------
Domain:     milestogo
Cartridges: https://raw.githubusercontent.com/openshift-cartridges/openshift-wildfly-cartridge/wildfly-9/metadata/manifest.yml
Gear Size:  default
Scaling:    yes

Creating application 'wildfly' ... Artifacts deployed: ./ROOT.war
done

  WildFly 9 administrator added.  Please make note of these credentials:

   Username: adminXXXXXXX
   Password: XXXXXXXXXXXX
   
   run 'rhc port-forward wildfly' to access the web admin area on port 9990.

Waiting for your DNS name to be available ... done

Cloning into 'wildfly'...
Warning: Permanently added the RSA host key for IP address 'NN.NN.NN.NN' to the list of known hosts.

Your application 'wildfly' is now available.

  URL:        http://wildfly-milestogo.rhcloud.com/
  SSH to:     XXXXXXXXXXXXXXXXXXXXXXXX@wildfly-milestogo.rhcloud.com
  Git remote: ssh://XXXXXXXXXXXXXXXXXXXXXXXX@wildfly-milestogo.rhcloud.com/~/git/wildfly.git/
  Cloned to:  /Users/arungupta/tmp/wildfly

Run 'rhc show-app wildfly' for more details about your app.

tmp> rhc app create wildfly -s https://raw.githubusercontent.com/openshift-cartridges/openshift-wildfly-cartridge/wildfly-9/metadata/manifest.yml

The cartridge 'https://raw.githubusercontent.com/openshift-cartridges/openshift-wildfly-cartridge/wildfly-9/metadata/manifest.yml' will be downloaded

and installed

Application Options

-------------------

Domain: milestogo

Cartridges: https://raw.githubusercontent.com/openshift-cartridges/openshift-wildfly-cartridge/wildfly-9/metadata/manifest.yml

Gear Size: default

Scaling: yes

Creating application 'wildfly' ... Artifacts deployed: ./ROOT.war

done

WildFly 9 administrator added. Please make note of these credentials:

Username: adminXXXXXXX

Password: XXXXXXXXXXXX

run 'rhc port-forward wildfly' to access the web admin area on port 9990.

Waiting for your DNS name to be available ... done

Cloning into 'wildfly'...

Warning: Permanently added the RSA host key for IP address 'NN.NN.NN.NN' to the list of known hosts.

Your application 'wildfly' is now available.

URL: http://wildfly-milestogo.rhcloud.com/

SSH to: XXXXXXXXXXXXXXXXXXXXXXXX@wildfly-milestogo.rhcloud.com

Git remote: ssh://XXXXXXXXXXXXXXXXXXXXXXXX@wildfly-milestogo.rhcloud.com/~/git/wildfly.git/

Cloned to: /Users/arungupta/tmp/wildfly

Run 'rhc show-app wildfly' for more details about your app.

This creates a new application and uses WildFly 9 as the underlying application server. Complete details about the OpenShift cartridge are at github.com/openshift-cartridges/openshift-wildfly-cartridge/tree/wildfly-9. You can find about how to create an OpenShift application with an existing application, how to connect to this WildFly instance using JBoss CLI.

WildFly 8 CR1 on OpenShift also provide more details.

WildFly 9 and Maven

WildFly Maven Plugin provide the latest information about how to get started with WildFly Maven plugin.

But you just need to fire up a WildFly server as:

wildfly-9.0.0.CR1> ./bin/standalone.sh  -c standalone-full.xml

wildfly-9.0.0.CR1> ./bin/standalone.sh -c standalone-full.xml

And then deploy the Java EE 7 Movieplex application as:

mvn wildfly:deploy -DskipTests

mvn wildfly:deploy -DskipTests

And the plugin definition is very simple:

<plugin>
    <groupId>org.wildfly.plugins</groupId>
    <artifactId>wildfly-maven-plugin</artifactId>
    <version>1.0.2.Final</version>
</plugin>

<groupId>org.wildfly.plugins</groupId>

<artifactId>wildfly-maven-plugin</artifactId>

<version>1.0.2.Final</version>

</plugin>

Enjoy!

OpenShift v3: Getting Started with Java EE 7 using WildFly and MySQL (Tech Tip #73)

February 13, 2015containers, javaee, techtip, wildflydevops, docker, javaee7, kubernetes, openshift, wildflyarungupta

OpenShift is Red Hat’s open source PaaS platform. OpenShift v3 (due to be released this year) will provide a holistic experience on running your microservices using Docker and Kubernetes. In a classic Red Hat way, all the work is done in the open source at OpenShift Origin. This will also drive the next major release of OpenShift Online and OpenShift Enterprise.

OpenShift v3 uses a new platform stack that is using plenty of community projects where Red Hat contributes such as Fedora, Centos, Docker, Project Atomic, Kubernetes, and OpenStack. OpenShift v3 Platform Combines Docker, Kubernetes, Atomic and More explain this platform stack in detail.

This tech tip will explain how to get started with OpenShift v3, lets get started!

Getting Started with OpenShift v3

Pre-built binaries for OpenShift v3 can be downloaded from Origin at GitHub. However the simplest way to get started is to run OpenShift Origin as a Docker container.

OpenShift Application Lifecycle provide complete details on what it takes to run a sample application from scratch. This blog will use those steps and adapt them to run using boot2docker VM on Mac. And in the process we’ll also deploy a Java EE 7 application on WildFly which will be accessing database on a separate MySQL container.

Here is our deployment diagram:

WildFly and MySQL are running on separate pods.
Each of them is wrapped in a Replication Controller to enable simplified scaling.
Each Replication Controller is published as a Service.
WildFly talks to the MySQL service, as opposed to directly to the pod. This is important as Pods, and IP addresses assigned to them, are ephemeral.

Lets get started!

Configure Docker Daemon

Configure the docker daemon on your host to trust the docker registry service you’ll be starting. This registry will be used to push images for build/test/deploy cycle.

Log into boot2docker VM as:

boot2docker ssh

boot2docker ssh

Edit the file

sudo vi /var/lib/boot2docker/profile

sudo vi /var/lib/boot2docker/profile

This will be an empty file.

Add the following name/value pair:

EXTRA_ARGS="--insecure-registry 172.30.17.0/24"

EXTRA_ARGS="--insecure-registry 172.30.17.0/24"

Save the file, and quit the editor.

This will instruct the docker daemon to trust any docker registry on the 172.30.17.0/24 subnet.

Check out OpenShift v3 and Java EE 7 Sample

Download and Install Go and setup GOPATH and PATH environment variable. Check out OpenShift origin directory:

openshift> git clone https://github.com/openshift/origin.git
Cloning into 'origin'...
remote: Counting objects: 21451, done.
remote: Compressing objects: 100% (76/76), done.
remote: Total 21451 (delta 26), reused 15 (delta 1)
Receiving objects: 100% (21451/21451), 35.11 MiB | 1.24 MiB/s, done.
Resolving deltas: 100% (11392/11392), done.
Checking connectivity... done.

openshift> git clone https://github.com/openshift/origin.git

Cloning into 'origin'...

remote: Counting objects: 21451, done.

remote: Compressing objects: 100% (76/76), done.

remote: Total 21451 (delta 26), reused 15 (delta 1)

Receiving objects: 100% (21451/21451), 35.11 MiB | 1.24 MiB/s, done.

Resolving deltas: 100% (11392/11392), done.

Checking connectivity... done.

Note the directory where its checked out. In this case, its ~/workspaces/openshift.

Build the workspace:

make release
origin> make release
rm -rf _output Godeps/_workspace/pkg
hack/build-release.sh
Unable to find image 'openshift/origin-release' locally
Pulling repository openshift/origin-release
c59f040a4054: Download complete 
511136ea3c5a: Download complete 
5b12ef8fd570: Download complete 
dade6cb4530a: Download complete 
bd195712b86c: Download complete 
4aae29c1c846: Download complete 
d8738da3ed4c: Download complete 
7f7491063665: Download complete 
b5cfa9eebdb5: Download complete 
2f6297477756: Download complete 
dc98bd93df2f: Download complete 
1be2a7550a3d: Download complete 
42fd088f8c55: Download complete 
b6f6ad4012df: Download complete 
Status: Downloaded newer image for openshift/origin-release:latest

make release

origin> make release

rm -rf _output Godeps/_workspace/pkg

hack/build-release.sh

Unable to find image 'openshift/origin-release' locally

Pulling repository openshift/origin-release

c59f040a4054: Download complete

511136ea3c5a: Download complete

5b12ef8fd570: Download complete

dade6cb4530a: Download complete

bd195712b86c: Download complete

4aae29c1c846: Download complete

d8738da3ed4c: Download complete

7f7491063665: Download complete

b5cfa9eebdb5: Download complete

2f6297477756: Download complete

dc98bd93df2f: Download complete

1be2a7550a3d: Download complete

42fd088f8c55: Download complete

b6f6ad4012df: Download complete

Status: Downloaded newer image for openshift/origin-release:latest

Check out javaee7-hol workspace that has been converted to a Kubernetes application:

origin> git clone https://github.com/bparees/javaee7-hol
Cloning into 'javaee7-hol'...
remote: Counting objects: 1159, done.
remote: Compressing objects: 100% (49/49), done.
remote: Total 1159 (delta 35), reused 37 (delta 21)
Receiving objects: 100% (1159/1159), 20.35 MiB | 1.78 MiB/s, done.
Resolving deltas: 100% (605/605), done.
Checking connectivity... done.

origin> git clone https://github.com/bparees/javaee7-hol

Cloning into 'javaee7-hol'...

remote: Counting objects: 1159, done.

remote: Compressing objects: 100% (49/49), done.

remote: Total 1159 (delta 35), reused 37 (delta 21)

Receiving objects: 100% (1159/1159), 20.35 MiB | 1.78 MiB/s, done.

Resolving deltas: 100% (605/605), done.

Checking connectivity... done.

This is also done in ~/workspaces/openshift directory.

Start OpenShift v3 Container

Start OpenShift Origin as Docker container:

~> docker run -d --name "openshift-origin" --net=host --privileged \
  -v /var/run/docker.sock:/var/run/docker.sock  \
  -v /Users/arungupta/workspaces/openshift:/workspaces/openshift \
  -v /usr/local/bin/docker:/usr/bin/docker \
  openshift/origin start --public-master=$(boot2docker ip)

The VM's Host only interface IP address is: 

0ae85091e7ad7e85697575369f008273a6673d112b49860f5557a61d9e82d908

~> docker run -d --name "openshift-origin" --net=host --privileged \

-v /var/run/docker.sock:/var/run/docker.sock \

-v /Users/arungupta/workspaces/openshift:/workspaces/openshift \

-v /usr/local/bin/docker:/usr/bin/docker \

openshift/origin start --public-master=$(boot2docker ip)

The VM's Host only interface IP address is:

0ae85091e7ad7e85697575369f008273a6673d112b49860f5557a61d9e82d908

Note ~/workspaces/openshift directory is mounted as /workspaces/openshift volume in the container. Some additional volumes are mounted as well.

Check that the container is running:

~> docker ps
CONTAINER ID        IMAGE                    COMMAND                CREATED             STATUS              PORTS               NAMES
0ae85091e7ad        openshift/origin:beta1   "/usr/bin/openshift    2 minutes ago       Up 2 minutes                            openshift-origin

~> docker ps

CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES

0ae85091e7ad openshift/origin:beta1 "/usr/bin/openshift 2 minutes ago Up 2 minutes openshift-origin

Log into the container as:

openshift> docker exec -it `docker ps | grep origin:beta1 | awk '{ print $1 }'` bash
[root@boot2docker openshift]#

openshift> docker exec -it `docker ps | grep origin:beta1 | awk '{ print $1 }'` bash

[root@boot2docker openshift]#

Install Docker registry in the container by giving the following command:

export CERT_DIR=/var/lib/openshift/openshift.local.certificates/openshift-client && \
export KUBECONFIG=/var/lib/openshift/openshift.local.certificates/admin/.kubeconfig && \
cd /workspaces/openshift/origin && hack/install-registry.sh

export CERT_DIR=/var/lib/openshift/openshift.local.certificates/openshift-client && \

export KUBECONFIG=/var/lib/openshift/openshift.local.certificates/admin/.kubeconfig && \

cd /workspaces/openshift/origin && hack/install-registry.sh

Confirm that the registry is running by getting the list of pods:

[root@boot2docker origin]# osc get pods
POD                       IP                  CONTAINER(S)         IMAGE(S)                    HOST                    LABELS                                                                                                             STATUS
docker-registry-1-gfkbz   172.17.0.14         registry-container   openshift/docker-registry   boot2docker/127.0.0.1   deployment=docker-registry-1,deploymentconfig=docker-registry,name=registrypod,template=docker-registry-template   Running

[root@boot2docker origin]# osc get pods

POD IP CONTAINER(S) IMAGE(S) HOST LABELS STATUS

docker-registry-1-gfkbz 172.17.0.14 registry-container openshift/docker-registry boot2docker/127.0.0.1 deployment=docker-registry-1,deploymentconfig=docker-registry,name=registrypod,template=docker-registry-template Running

osc is OpenShift Client CLI and allows to create and manage OpenShift projects. Some of the kubectl commands can also be using this script.

Confirm the registry service is running. Note the actual IP address may vary:

[root@boot2docker origin]# osc get services
NAME                LABELS                                    SELECTOR            IP                  PORT
docker-registry     template=docker-registry-template         name=registrypod    172.30.17.142       5001
kubernetes          component=apiserver,provider=kubernetes   <none>              172.30.17.2         443
kubernetes-ro       component=apiserver,provider=kubernetes   <none>              172.30.17.1         80

[root@boot2docker origin]# osc get services

NAME LABELS SELECTOR IP PORT

docker-registry template=docker-registry-template name=registrypod 172.30.17.142 5001

kubernetes component=apiserver,provider=kubernetes <none> 172.30.17.2 443

kubernetes-ro component=apiserver,provider=kubernetes <none> 172.30.17.1 80

Confirm that the registry service is accessible:

curl `osc get services docker-registry -o template --template="{{ .portalIP}}:{{ .port }}"`

curl `osc get services docker-registry -o template --template="{{ .portalIP}}:{{ .port }}"`

And look for the output:

"docker-registry server (dev) (v0.9.0)"

"docker-registry server (dev) (v0.9.0)"

Access OpenShift v3 Web Console

OpenShift Origin server is now up and running. Find out the host’s IP address using boot2docker ip and open http://<IP addresss of boot2docker host>:8444 to view OpenShift Web Console in your browser.For example, the console is accessible at https://192.168.59.103:8444/ on this machine.

You will need to have the browser accept the certificate at https://<host>:8444 before the console can consult the OpenShift API. Of course this would not be necessary with a legitimate certificate.
OpenShift Origin login screen shows up. Enter the username/password as admin/admin:

and click on the “Log In” button. The default web console looks like:

Create OpenShift v3 Project

Use project.json from github.com/openshift/origin/blob/master/examples/sample-app/project.json in the OpenShift v3 container and create a test project as:

[root@boot2docker origin]# osc create -f /workspaces/openshift/origin/examples/sample-app/project.json 
test

[root@boot2docker origin]# osc create -f /workspaces/openshift/origin/examples/sample-app/project.json

test

Refreshing the web console now shows:

Clicking on “OpenShift 3 Sample” shows an empty project description:

Request creation of the application template:

[root@boot2docker openshift]# cd javaee7-hol/
[root@boot2docker javaee7-hol]# osc process -n test -f application-template-jeebuild.json | osc create -n test -f -
frontend
origin-jee-sample
wildfly-8-centos
jee-sample-build
frontend
mysql
database

[root@boot2docker openshift]# cd javaee7-hol/

[root@boot2docker javaee7-hol]# osc process -n test -f application-template-jeebuild.json | osc create -n test -f -

frontend

origin-jee-sample

wildfly-8-centos

jee-sample-build

frontend

mysql

database

Web Console automatically refreshes and shows:

The list of services running can be seen as:

Build the Project

Trigger an initial build of your project:

[root@boot2docker javaee7-hol]# osc start-build -n test jee-sample-build
cee73fbc-b32d-11e4-a0f2-5282784576db

[root@boot2docker javaee7-hol]# osc start-build -n test jee-sample-build

cee73fbc-b32d-11e4-a0f2-5282784576db

Monitor the builds and wait for the status to go to “complete” (this can take a few minutes):

[root@boot2docker javaee7-hol]#  osc get -n test builds
NAME                                   TYPE                STATUS              POD
cee73fbc-b32d-11e4-a0f2-5282784576db   STI                 Running             build-cee73fbc-b32d-11e4-a0f2-5282784576db

[root@boot2docker javaee7-hol]# osc get -n test builds

NAME TYPE STATUS POD

cee73fbc-b32d-11e4-a0f2-5282784576db STI Running build-cee73fbc-b32d-11e4-a0f2-5282784576db

You can add the –watch flag to wait for updates until the build completes:

[root@boot2docker javaee7-hol]#  osc get -n test builds --watch
NAME                                   TYPE                STATUS              POD
cee73fbc-b32d-11e4-a0f2-5282784576db   STI                 Running             build-cee73fbc-b32d-11e4-a0f2-5282784576db
NAME                                   TYPE                STATUS              POD
cee73fbc-b32d-11e4-a0f2-5282784576db   STI                 Complete            build-cee73fbc-b32d-11e4-a0f2-5282784576db

[root@boot2docker javaee7-hol]# osc get -n test builds --watch

NAME TYPE STATUS POD

cee73fbc-b32d-11e4-a0f2-5282784576db STI Running build-cee73fbc-b32d-11e4-a0f2-5282784576db

NAME TYPE STATUS POD

cee73fbc-b32d-11e4-a0f2-5282784576db STI Complete build-cee73fbc-b32d-11e4-a0f2-5282784576db

Wait for the STATUS column to show Complete. It will take a few minutes as all the components (WIldFly, MySQL, Java EE 7 application) are provisioned. Effectively, their new Docker images are created and pushed to the local registry that was started earlier.

Hit Ctrl+C to stop watching builds after the status changes to Complete.

Complete log of the build can be seen as:

[root@boot2docker javaee7-hol]# osc build-logs -n test cee73fbc-b32d-11e4-a0f2-5282784576db
2015-02-13T03:10:07.065718606Z Cloning into '/tmp/sti552730161/upload/src'...
2015-02-13T03:11:03.184576532Z I0213 03:11:03.184326       1 build.go:160] Successfully built 172.30.17.142:5001/test/origin-jee-sample
2015-02-13T03:11:07.261489310Z The push refers to a repository [172.30.17.142:5001/test/origin-jee-sample] (len: 1)
2015-02-13T03:11:07.261489310Z Sending image list
2015-02-13T03:11:07.275256699Z Pushing repository 172.30.17.142:5001/test/origin-jee-sample (1 tags)
2015-02-13T03:11:07.307836081Z Pushing
Buffering to disk07.314345045Z Buffering to disk 1.024 kB
2015-02-13T03:11:07.315452728Z Buffering to disk
Pushing-13T03:11:07.323973430Z Pushing [=========================>                         ]    512 B/1.024 kB 0

. . .

Pushing-13T03:13:05.932725921Z Pushing [================================================>  ]  6.56 MB/6.704 MB 0
Pushing-13T03:13:05.942989165Z Pushing [=================================================> ] 6.635 MB/6.704 MB 0
Pushing-13T03:13:05.943025109Z Pushing [=================================================> ] 6.702 MB/6.704 MB 0
Pushing-13T03:13:05.947665528Z Pushing [==================================================>] 6.704 MB/6.704 MB
2015-02-13T03:13:05.953476634Z Image successfully pushed
2015-02-13T03:13:05.953476634Z Pushing tag for rev [b0a7868377c1] on {http://172.30.17.142:5001/v1/repositories/test/origin-jee-sample/tags/latest}

[root@boot2docker javaee7-hol]# osc build-logs -n test cee73fbc-b32d-11e4-a0f2-5282784576db

2015-02-13T03:10:07.065718606Z Cloning into '/tmp/sti552730161/upload/src'...

2015-02-13T03:11:03.184576532Z I0213 03:11:03.184326 1 build.go:160] Successfully built 172.30.17.142:5001/test/origin-jee-sample

2015-02-13T03:11:07.261489310Z The push refers to a repository [172.30.17.142:5001/test/origin-jee-sample] (len: 1)

2015-02-13T03:11:07.261489310Z Sending image list

2015-02-13T03:11:07.275256699Z Pushing repository 172.30.17.142:5001/test/origin-jee-sample (1 tags)

2015-02-13T03:11:07.307836081Z Pushing

Buffering to disk07.314345045Z Buffering to disk 1.024 kB

2015-02-13T03:11:07.315452728Z Buffering to disk

Pushing-13T03:11:07.323973430Z Pushing [=========================> ] 512 B/1.024 kB 0

. . .

Pushing-13T03:13:05.932725921Z Pushing [================================================> ] 6.56 MB/6.704 MB 0

Pushing-13T03:13:05.942989165Z Pushing [=================================================> ] 6.635 MB/6.704 MB 0

Pushing-13T03:13:05.943025109Z Pushing [=================================================> ] 6.702 MB/6.704 MB 0

Pushing-13T03:13:05.947665528Z Pushing [==================================================>] 6.704 MB/6.704 MB

2015-02-13T03:13:05.953476634Z Image successfully pushed

2015-02-13T03:13:05.953476634Z Pushing tag for rev [b0a7868377c1] on {http://172.30.17.142:5001/v1/repositories/test/origin-jee-sample/tags/latest}

Check for the application pods to start:

[root@boot2docker javaee7-hol]# osc get -n test pods    
POD                                          IP                  CONTAINER(S)        IMAGE(S)                                                                                                     HOST                    LABELS                                                                              STATUS
build-cee73fbc-b32d-11e4-a0f2-5282784576db   172.17.0.17         sti-build           openshift/origin-sti-builder:v0.3                                                                            boot2docker/127.0.0.1   <none>                                                                              Succeeded
database-1-axe6d                             172.17.0.16         jee-database        mysql                                                                                                        boot2docker/127.0.0.1   deployment=database-1,deploymentconfig=database,name=database,template=jee-sample   Running
frontend-1-pkcia                             172.17.0.20         jee-sample          172.30.17.142:5001/test/origin-jee-sample:b0a7868377c10a50b40019be70e22d040b9a2bb2d87fa3932b700494e50a4de6   boot2docker/127.0.0.1   deployment=frontend-1,deploymentconfig=frontend,name=frontend,template=jee-sample   Running

[root@boot2docker javaee7-hol]# osc get -n test pods

POD IP CONTAINER(S) IMAGE(S) HOST LABELS STATUS

build-cee73fbc-b32d-11e4-a0f2-5282784576db 172.17.0.17 sti-build openshift/origin-sti-builder:v0.3 boot2docker/127.0.0.1 <none> Succeeded

database-1-axe6d 172.17.0.16 jee-database mysql boot2docker/127.0.0.1 deployment=database-1,deploymentconfig=database,name=database,template=jee-sample Running

frontend-1-pkcia 172.17.0.20 jee-sample 172.30.17.142:5001/test/origin-jee-sample:b0a7868377c10a50b40019be70e22d040b9a2bb2d87fa3932b700494e50a4de6 boot2docker/127.0.0.1 deployment=frontend-1,deploymentconfig=frontend,name=frontend,template=jee-sample Running

Note, that the “frontend” and “database” pods are now running.

Determine IP of the “frontend” service:

[root@boot2docker javaee7-hol]# osc get -n test services
NAME                LABELS                SELECTOR            IP                  PORT
frontend            template=jee-sample   name=frontend       172.30.17.115       8080
mysql               template=jee-sample   name=database       172.30.17.75        3306

[root@boot2docker javaee7-hol]# osc get -n test services

NAME LABELS SELECTOR IP PORT

frontend template=jee-sample name=frontend 172.30.17.115 8080

mysql template=jee-sample name=database 172.30.17.75 3306

Access the application at http://<IP address of “frontend”>:8080/movieplex7-1.0-SNAPSHOT should work. Note the IP address may (most likely will) vary. In this case, it would be http://172.30.17.115:8080/moviexplex7-1.0-SNAPSHOT.The app would not be accessible yet, as some further debugging is required to configure firewall on Mac when OpenShift v3 is used as Docker container. Until we figure that out, you can do docker ps in your boot2docker VM to see the list of all the containers:

origin> docker ps
CONTAINER ID        IMAGE                                                                                                       COMMAND                CREATED             STATUS              PORTS               NAMES
c776cabb72f8        172.30.17.17:5001/test/origin-jee-sample:91d1b5a5ed58e1642aafbd652eba0b7eae3a0ac08c17729d205ae88204f64449   "/tmp/scripts/run"     2 hours ago         Up 2 hours                              k8s_jee-sample.7af25557_frontend-2-9ciae.test.api_12a0d77e-b3b5-11e4-81f6-5282784576db_53f91f55                      
e7f87112c473        openshift/origin-pod:beta1                                                                                  "/pod"                 2 hours ago         Up 2 hours                              k8s_POD.9cbfdefa_frontend-2-9ciae.test.api_12a0d77e-b3b5-11e4-81f6-5282784576db_64263b61                             
7e7579db5f82        openshift/origin-pod:beta1                                                                                  "/pod"                 2 hours ago         Up 2 hours                              k8s_POD.123cbdd6_build-e075047d-b3b4-11e4-81f6-5282784576db.test.api_e07bcdb2-b3b4-11e4-81f6-5282784576db_376c0e63   
74082d7791ec        openshift/origin-pod:beta1                                                                                  "/pod"                 2 hours ago         Up 2 hours                              k8s_POD.123cbdd6_build-76364bb6-b3b2-11e4-81f6-5282784576db.test.api_7639e3a5-b3b2-11e4-81f6-5282784576db_f653c7fd   
3e42dacb0da7        mysql:latest                                                                                                "/entrypoint.sh mysq   3 hours ago         Up 3 hours                              k8s_jee-database.f12628ae_database-1-bqg8v.test.api_56093bac-b3b2-11e4-81f6-5282784576db_193dddf7                    
cb551c8cf7bf        openshift/origin-pod:beta1                                                                                  "/pod"                 3 hours ago         Up 3 hours                              k8s_POD.95f2def6_database-1-bqg8v.test.api_56093bac-b3b2-11e4-81f6-5282784576db_295fc320                             
e8719152df42        openshift/docker-registry:latest                                                                            "\"sh -c 'echo \"$OP   3 hours ago         Up 3 hours                              k8s_registry-container.4e338487_docker-registry-1-bt49s.default.api_177a691c-b3b0-11e4-81f6-5282784576db_a6f4f83b    
d3ecc5841c3b        openshift/origin-pod:beta1                                                                                  "/pod"                 3 hours ago         Up 3 hours                              k8s_POD.8a29deef_docker-registry-1-bt49s.default.api_177a691c-b3b0-11e4-81f6-5282784576db_ba53d62b                   
a506222fae91        openshift/origin:beta1                                                                                      "/usr/bin/openshift    3 hours ago         Up 3 hours                              openshift-origin

origin> docker ps

CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES

c776cabb72f8 172.30.17.17:5001/test/origin-jee-sample:91d1b5a5ed58e1642aafbd652eba0b7eae3a0ac08c17729d205ae88204f64449 "/tmp/scripts/run" 2 hours ago Up 2 hours k8s_jee-sample.7af25557_frontend-2-9ciae.test.api_12a0d77e-b3b5-11e4-81f6-5282784576db_53f91f55

e7f87112c473 openshift/origin-pod:beta1 "/pod" 2 hours ago Up 2 hours k8s_POD.9cbfdefa_frontend-2-9ciae.test.api_12a0d77e-b3b5-11e4-81f6-5282784576db_64263b61

7e7579db5f82 openshift/origin-pod:beta1 "/pod" 2 hours ago Up 2 hours k8s_POD.123cbdd6_build-e075047d-b3b4-11e4-81f6-5282784576db.test.api_e07bcdb2-b3b4-11e4-81f6-5282784576db_376c0e63

74082d7791ec openshift/origin-pod:beta1 "/pod" 2 hours ago Up 2 hours k8s_POD.123cbdd6_build-76364bb6-b3b2-11e4-81f6-5282784576db.test.api_7639e3a5-b3b2-11e4-81f6-5282784576db_f653c7fd

3e42dacb0da7 mysql:latest "/entrypoint.sh mysq 3 hours ago Up 3 hours k8s_jee-database.f12628ae_database-1-bqg8v.test.api_56093bac-b3b2-11e4-81f6-5282784576db_193dddf7

cb551c8cf7bf openshift/origin-pod:beta1 "/pod" 3 hours ago Up 3 hours k8s_POD.95f2def6_database-1-bqg8v.test.api_56093bac-b3b2-11e4-81f6-5282784576db_295fc320

e8719152df42 openshift/docker-registry:latest "\"sh -c 'echo \"$OP 3 hours ago Up 3 hours k8s_registry-container.4e338487_docker-registry-1-bt49s.default.api_177a691c-b3b0-11e4-81f6-5282784576db_a6f4f83b

d3ecc5841c3b openshift/origin-pod:beta1 "/pod" 3 hours ago Up 3 hours k8s_POD.8a29deef_docker-registry-1-bt49s.default.api_177a691c-b3b0-11e4-81f6-5282784576db_ba53d62b

a506222fae91 openshift/origin:beta1 "/usr/bin/openshift 3 hours ago Up 3 hours openshift-origin

And then login to the container associated with frontend as:

docker exec -it `docker ps | grep origin-jee-sample | awk '{ print $1 }'` bash

docker exec -it `docker ps | grep origin-jee-sample | awk '{ print $1 }'` bash

This will log in to the Docker container where you can check that the application is deployed successfully by giving the following command:

bash-4.2$ curl http://localhost:8080/movieplex7-1.0-SNAPSHOT/

bash-4.2$ curl http://localhost:8080/movieplex7-1.0-SNAPSHOT/

This will print the index.html page from the application which has license at the top and rest of the page after that.

Now once the firewall issue is resolved, this page will then be accessible on host Mac as well.

Lets summarize:

Cloned the OpenShift Origin and Java EE 7 sample repo
Started OpenShift v3 as Docker container
Loaded the OpenShift v3 Web Console
Create an OpenShift v3 project
Loaded Java EE 7 application template
Triggered a build, which deployed the application

Here are some troubleshooting tips if you get stuck.

Enjoy!

Reactive HTML presentations using Reveal.js, Gist, and OpenShift (Tech Tip #69)

January 8, 2015redhat, techtipcss3, html5, openshift, reveal.js, slidesarungupta

Reveal.js is an HTML-base presentation framework. You just need a browser with CSS 3D transforms. That means Chrome, Firefox, Safari, Opera, and IE 10-11 are supported. It also provides a nice fallback for other legacy browsers. Check out a live demo yourself.

This Tech Tip will show how to create Reveal.js-based presentations easily using Gist and OpenShift.

Why Gist?

This allows to separate presentation layer (Node.js on OpenShift) and data layer (HTML source on Gist), and also keep them distributed. You may not be able to show demos using this, at least yet, but at least you don’t need to worry about laptop crashes. You can certainly keep the source for your presentation any where you like, such as github or some other repo, but will need to change the templating framework accordingly.

Why OpenShift?

Full setup of Reveal.js require installation of Node.js, Grunt, and some other dependencies. And even then your slides are only locally available. To keep it completely distributed, its important to have Node.js and other dependencies running in the cloud. OpenShift is an open-source polyglot PaaS from Red Hat that allows Node.js to be run in the cloud. You can certainly choose any other Node.js hosting environment as well but this is what I feel most comfortable with.

Meet Gist-Reveal.it

Ryan (@ryanj) created Gist-Reveal.it an open source slideshow templating service that makes it easy to create, edit, present, and share Reveal.js slides on the web.

A cool feature of this framework on how one browser can be configured as broadcaster and all others as receivers. This allows the presenter (or broadcaster) to share the slides URL and allow the viewers (or receivers) to follow the slides along on their own favorite device. This could be very useful in a conference setting particularly.

Gist-powered Reveal.js slideshows provide a quick introduction to setup. This Tech Tip will use Gist-Reveal.it + OpenShift and show you how to setup your own personal hosting environment for beautiful HTML slides.

Lets get started!

Sign up for OpenShift at openshift.com/app/account/new. No credit card and free account gives you 3 gears where each gear is 1GB disk and 0.5 GB memory. A free gear is enough to host your web front end for Reveal.js.
Sample slides are available at slides-milestogo.rhcloud.com. Click on the button on bottom-left to create a new OpenShift application. This application will clone the source code from gist-reveal.it and use that as the basis for the newly created application.
Create a new gist and copy the unique ID assigned to it. For example, for the gist created at gist.github.com/arun-gupta/9ac2cea40c302986a8e3 the unique id is “9ac2cea40c302986a8e3”.
Register a new API key on GitHub at github.com/settings/applications. Note down the “Client ID” and “Client Secret”. Leave “Authorization callback URL” empty, everything else is straight forward.

Install OpenShift CLI tools and set them up. Setup a few environment variables for the OpenShift application:

rhc env set GH_CLIENT_SECRET=<CLIENT_SECRET> --app slides
rhc env set GH_CLIENT_ID=<CLIENT_ID> --app slides
rhc env set DEFAULT_GIST=<GIST_ID> --app slides
rhc env set REVEAL_SOCKET_SECRET=<SUPER_SECRET_VALUE> --app slides

rhc env set GH_CLIENT_SECRET=<CLIENT_SECRET> --app slides

rhc env set GH_CLIENT_ID=<CLIENT_ID> --app slides

rhc env set DEFAULT_GIST=<GIST_ID> --app slides

rhc env set REVEAL_SOCKET_SECRET=<SUPER_SECRET_VALUE> --app slides

Replace <CLIENT_SECRET>, <CLIENT_ID>, and <GIST_ID> with your specific values. Also note, “slides” is the application that is used in this blog. If your OpenShift application name is different then use that instead.

REVEAL_SOCKET_SECRET is an environment variable that is used by the templating framework to look for a special value to identify the broadcaster (or the presenter). This value needs to be kept secret and not shared with others. A browser can be made as a broadcaster by accessing the following URL

http://slides-milestogo.rhcloud.com/?setToken=<SUPER_SECRET_VALUE>

http://slides-milestogo.rhcloud.com/?setToken=<SUPER_SECRET_VALUE>

Accessing this URL stores this token in browser’s local storage. Make sure to change the URL to reflect your particular application and domain on OpenShift. For example, application name in this case is “slides” and domain is “milestogo”.

Other configuration values are explained at github.com/ryanj/gist-reveal.it#application-config. Complete documentation about the framework is at github.com/ryanj/gist-reveal.it.

Enjoy!

Thanks to Ryan (@ryanj) for helping me setup the environment.

I’m waiting which conference will be the first one to provide Gist-Reveal themes

Java EE Workflows on OpenShift (Tech Tip #64)

December 18, 2014javaee, redhat, techtip, wildflyarquillian, javaee, openshift, wildflyarungupta

This webinar shows how create a Java EE workflow on OpenShift using WildFly, JBoss Tools, Forge, Arquillian, and OpenShift. Specifically it talks about:

How a Java EE application can be easily developed using JBoss Developer Studio and deployed directly to OpenShift
Set up Test and Production instances on OpenShift
Enable Jenkins to provide Continuous Integration
Run the tests on Test and push the WAR to Production

More detailed blog entries are at:

And a lot more at blog.arungupta.me/tag/openshift/.

Enjoy!

Deployment Pipeline for Java EE 7 with WildFly, Arquillian, Jenkins, and OpenShift (Tech Tip #56)

November 20, 2014javaee, techtip, wildflyarquillian, devops, javaee7, jenkins, openshift, wildflyarungupta

Tech Tip #54 showed how to Arquillianate (Arquillianize ?) an existing Java EE project and run those tests in remote mode where WildFly is running on a known host and port. Tech Tip #55 showed how to run those tests when WildFly is running in OpenShift. Both of these tips used Maven profiles to separate the appropriate Arquillian dependencies in “pom.xml” and <container> configuration in “arquillian.xml” to define where WildFy is running and how to connect to it.

This tip will show how to configure Jenkins in OpenShift and invoke these tests from Jenkins. This will create deployment pipeline for Java EE.

Lets see it in action first!

Configuration required to connect from Jenkins on OpenShift to a WildFly instance on OpenShift is similar to that required for connecting from local machine to WildFly on OpenShift. This configuration is specified in “arquillian.xml” and we can specify some parameters which can then be defined in Jenkins.

On a high level, here is what we’ll do:

Use the code created in Tech Tip #54 and #55 and add configuration for Arquillian/Jenkins/OpenShift
Enable Jenkins
Create a new WildFly Test instance
Configure Jenkins to run tests on the Test instance
Push the application to Production only if tests pass on Test instance

Lets get started!

Remove the existing boilerplate source code, only the src directory, from the WildFly git repo created in Tech Tip #55.

mywildfly> git rm -rf src/ pom.xml
rm 'pom.xml'
rm 'src/main/java/.gitkeep'
rm 'src/main/resources/.gitkeep'
rm 'src/main/webapp/WEB-INF/web.xml'
rm 'src/main/webapp/images/jbosscorp_logo.png'
rm 'src/main/webapp/index.html'
rm 'src/main/webapp/snoop.jsp'
mywildfly> git commit . -m"removing source and pom"
[master 564b275] removing source and pom
 7 files changed, 647 deletions(-)
 delete mode 100644 pom.xml
 delete mode 100644 src/main/java/.gitkeep
 delete mode 100644 src/main/resources/.gitkeep
 delete mode 100644 src/main/webapp/WEB-INF/web.xml
 delete mode 100644 src/main/webapp/images/jbosscorp_logo.png
 delete mode 100644 src/main/webapp/index.html
 delete mode 100644 src/main/webapp/snoop.jsp

mywildfly> git rm -rf src/ pom.xml

rm 'pom.xml'

rm 'src/main/java/.gitkeep'

rm 'src/main/resources/.gitkeep'

rm 'src/main/webapp/WEB-INF/web.xml'

rm 'src/main/webapp/images/jbosscorp_logo.png'

rm 'src/main/webapp/index.html'

rm 'src/main/webapp/snoop.jsp'

mywildfly> git commit . -m"removing source and pom"

[master 564b275] removing source and pom

7 files changed, 647 deletions(-)

delete mode 100644 pom.xml

delete mode 100644 src/main/java/.gitkeep

delete mode 100644 src/main/resources/.gitkeep

delete mode 100644 src/main/webapp/WEB-INF/web.xml

delete mode 100644 src/main/webapp/images/jbosscorp_logo.png

delete mode 100644 src/main/webapp/index.html

delete mode 100644 src/main/webapp/snoop.jsp

Set a new remote to javaee7-continuous-delivery repository:

mywildfly> git remote add javaee7 https://github.com/arun-gupta/javaee7-continuous-delivery.git
mywildfly> git remote -v
javaee7 https://github.com/arun-gupta/javaee7-continuous-delivery.git (fetch)
javaee7 https://github.com/arun-gupta/javaee7-continuous-delivery.git (push)
origin  ssh://54699516ecb8d41cb8000016@mywildfly-milestogo.rhcloud.com/~/git/mywildfly.git/ (fetch)
origin  ssh://54699516ecb8d41cb8000016@mywildfly-milestogo.rhcloud.com/~/git/mywildfly.git/ (push)

mywildfly> git remote add javaee7 https://github.com/arun-gupta/javaee7-continuous-delivery.git

mywildfly> git remote -v

javaee7 https://github.com/arun-gupta/javaee7-continuous-delivery.git (fetch)

javaee7 https://github.com/arun-gupta/javaee7-continuous-delivery.git (push)

origin ssh://54699516ecb8d41cb8000016@mywildfly-milestogo.rhcloud.com/~/git/mywildfly.git/ (fetch)

origin ssh://54699516ecb8d41cb8000016@mywildfly-milestogo.rhcloud.com/~/git/mywildfly.git/ (push)

Pull the code from new remote:

mywildfly> git pull javaee7 master
warning: no common commits
remote: Counting objects: 62, done.
remote: Compressing objects: 100% (45/45), done.
remote: Total 62 (delta 14), reused 53 (delta 5)
Unpacking objects: 100% (62/62), done.
From https://github.com/arun-gupta/javaee7-continuous-delivery
 * branch            master     -> FETCH_HEAD
 * [new branch]      master     -> javaee7/master
Merge made by the 'recursive' strategy.
 .gitignore                                           |   6 +++
 README.asciidoc                                      |  15 ++++++
 pom.xml                                              | 197 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
 src/main/java/org/javaee7/sample/MyApplication.java  |   9 ++++
 src/main/java/org/javaee7/sample/Person.java         |  31 ++++++++++++
 src/main/java/org/javaee7/sample/PersonDatabase.java |  39 ++++++++++++++
 src/main/java/org/javaee7/sample/PersonResource.java |  29 +++++++++++
 src/main/webapp/index.jsp                            |  13 +++++
 src/test/java/org/javaee7/sample/PersonTest.java     |  77 ++++++++++++++++++++++++++++
 src/test/resources/arquillian.xml                    |  26 ++++++++++
 10 files changed, 442 insertions(+)
 create mode 100644 .gitignore
 create mode 100644 README.asciidoc
 create mode 100644 pom.xml
 create mode 100644 src/main/java/org/javaee7/sample/MyApplication.java
 create mode 100644 src/main/java/org/javaee7/sample/Person.java
 create mode 100644 src/main/java/org/javaee7/sample/PersonDatabase.java
 create mode 100644 src/main/java/org/javaee7/sample/PersonResource.java
 create mode 100644 src/main/webapp/index.jsp
 create mode 100644 src/test/java/org/javaee7/sample/PersonTest.java
 create mode 100644 src/test/resources/arquillian.xml

mywildfly> git pull javaee7 master

warning: no common commits

remote: Counting objects: 62, done.

remote: Compressing objects: 100% (45/45), done.

remote: Total 62 (delta 14), reused 53 (delta 5)

Unpacking objects: 100% (62/62), done.

From https://github.com/arun-gupta/javaee7-continuous-delivery

* branch master -> FETCH_HEAD

* [new branch] master -> javaee7/master

Merge made by the 'recursive' strategy.

.gitignore | 6 +++

README.asciidoc | 15 ++++++

pom.xml | 197 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

src/main/java/org/javaee7/sample/MyApplication.java | 9 ++++

src/main/java/org/javaee7/sample/Person.java | 31 ++++++++++++

src/main/java/org/javaee7/sample/PersonDatabase.java | 39 ++++++++++++++

src/main/java/org/javaee7/sample/PersonResource.java | 29 +++++++++++

src/main/webapp/index.jsp | 13 +++++

src/test/java/org/javaee7/sample/PersonTest.java | 77 ++++++++++++++++++++++++++++

src/test/resources/arquillian.xml | 26 ++++++++++

10 files changed, 442 insertions(+)

create mode 100644 .gitignore

create mode 100644 README.asciidoc

create mode 100644 pom.xml

create mode 100644 src/main/java/org/javaee7/sample/MyApplication.java

create mode 100644 src/main/java/org/javaee7/sample/Person.java

create mode 100644 src/main/java/org/javaee7/sample/PersonDatabase.java

create mode 100644 src/main/java/org/javaee7/sample/PersonResource.java

create mode 100644 src/main/webapp/index.jsp

create mode 100644 src/test/java/org/javaee7/sample/PersonTest.java

create mode 100644 src/test/resources/arquillian.xml

This will bring all the source code, include our REST endpoints, web pages, tests, updated “pom.xml” and “arquillian.xml”. The updated “pom.xml” has two new profiles.

<profile>
 <id>openshift</id>
 <build>
    <plugins>
      <plugin>
            <groupId>org.apache.maven.plugins</groupId>
            <artifactId>maven-war-plugin</artifactId>
            <version>2.3</version>
            <configuration>
                <failOnMissingWebXml>false</failOnMissingWebXml>
                <outputDirectory>deployments</outputDirectory>
                      <warName>ROOT</warName>
            </configuration>
        </plugin>
    </plugins>
  </build>
</profile>
<profile>
    <id>jenkins-openshift</id>
    <build>
        <plugins>
            <plugin>
                <artifactId>maven-surefire-plugin</artifactId>
                <version>2.14.1</version>
                <configuration>
                    <systemPropertyVariables>
                        <arquillian.launch>jenkins-openshift</arquillian.launch>
                    </systemPropertyVariables>
                </configuration>
            </plugin>
        </plugins>
    </build>
    <dependencies>
        <dependency>
            <groupId>org.jboss.arquillian.container</groupId>
            <artifactId>arquillian-openshift</artifactId>
            <version>1.0.0.Final-SNAPSHOT</version>
            <scope>test</scope>
        </dependency>
    </dependencies>
</profile>

<id>openshift</id>

<build>

<groupId>org.apache.maven.plugins</groupId>

<artifactId>maven-war-plugin</artifactId>

<failOnMissingWebXml>false</failOnMissingWebXml>

<outputDirectory>deployments</outputDirectory>

</configuration>

</plugin>

</plugins>

</build>

</profile>

<id>jenkins-openshift</id>

<build>

<artifactId>maven-surefire-plugin</artifactId>

<arquillian.launch>jenkins-openshift</arquillian.launch>

</systemPropertyVariables>

</configuration>

</plugin>

</plugins>

</build>

<groupId>org.jboss.arquillian.container</groupId>

<artifactId>arquillian-openshift</artifactId>

<version>1.0.0.Final-SNAPSHOT</version>

</dependency>

</dependencies>

</profile>

Few points to observe here:

“openshift” profile is used when building an application on OpenShift. This is where the application’s WAR file is created and deployed to WildFly.
A new profile “jenkins-openshift” is added that will be used by the Jenkins instance (to be enabled shortly) in OpenShift to run tests.
“arquillian-openshift” dependency is the same as used in Tech Tip #55 and allows to run Arquillian tests on a WildFly instance on OpenShift.
This profile refers to “jenkins-openshift” container configuration that will be defined in “arquillian.xml”.

Updated “src/test/resources/arquillian.xml” has the following container:

<container qualifier="jenkins-openshift">
    <configuration>
        <property name="namespace">${env.ARQ_DOMAIN}</property>
        <property name="application">${env.ARQ_APPLICATION}</property>
        <property name="libraDomain">rhcloud.com</property>
        <property name="sshUserName">${env.ARQ_SSH_USER_NAME}</property>
        <property name="login">arungupta@redhat.com</property>
        <property name="deploymentTimeoutInSeconds">300</property>
        <property name="disableStrictHostChecking">true</property> 
    </configuration>
</container>

<property name="namespace">${env.ARQ_DOMAIN}</property>

<property name="application">${env.ARQ_APPLICATION}</property>

<property name="libraDomain">rhcloud.com</property>

<property name="login">arungupta@redhat.com</property>

</configuration>

</container>

This container configuration is similar to the one that was added in Tech Tip #55. The only difference here is that the domain name, application name, and the SSH user name are parametrized. The value of these properties is defined in the configuration of Jenkins instance and allows to run the test against a separate test node.

Two more things need to be done before changes can be pushed to the remote repository. First is to create a WildFly Test instance which can be used to run the tests. This can be easily done as shown:

workspaces> rhc app-create mywildflytest jboss-wildfly-8
Application Options
-------------------
Domain:     milestogo
Cartridges: jboss-wildfly-8
Gear Size:  default
Scaling:    no

Creating application 'mywildflytest' ... Artifacts deployed: ./ROOT.war
done

  WildFly 8 administrator added.  Please make note of these credentials:

   Username: adminITJt7Yh
   Password: yXP2mUd1w4_8
   
   run 'rhc port-forward mywildflytest' to access the web admin area on port 9990.

Waiting for your DNS name to be available ... done

Cloning into 'mywildflytest'...
Warning: Permanently added the RSA host key for IP address '54.205.69.88' to the list of known hosts.

Your application 'mywildflytest' is now available.

  URL:        http://mywildflytest-milestogo.rhcloud.com/
  SSH to:     546e3743ecb8d49ca9000014@mywildflytest-milestogo.rhcloud.com
  Git remote: ssh://546e3743ecb8d49ca9000014@mywildflytest-milestogo.rhcloud.com/~/git/mywildflytest.git/
  Cloned to:  /Users/arungupta/workspaces/javaee7/mywildflytest

Run 'rhc show-app mywildflytest' for more details about your app.

workspaces> rhc app-create mywildflytest jboss-wildfly-8

Application Options

-------------------

Domain: milestogo

Cartridges: jboss-wildfly-8

Gear Size: default

Scaling: no

Creating application 'mywildflytest' ... Artifacts deployed: ./ROOT.war

done

WildFly 8 administrator added. Please make note of these credentials:

Username: adminITJt7Yh

Password: yXP2mUd1w4_8

run 'rhc port-forward mywildflytest' to access the web admin area on port 9990.

Waiting for your DNS name to be available ... done

Cloning into 'mywildflytest'...

Warning: Permanently added the RSA host key for IP address '54.205.69.88' to the list of known hosts.

Your application 'mywildflytest' is now available.

URL: http://mywildflytest-milestogo.rhcloud.com/

SSH to: 546e3743ecb8d49ca9000014@mywildflytest-milestogo.rhcloud.com

Git remote: ssh://546e3743ecb8d49ca9000014@mywildflytest-milestogo.rhcloud.com/~/git/mywildflytest.git/

Cloned to: /Users/arungupta/workspaces/javaee7/mywildflytest

Run 'rhc show-app mywildflytest' for more details about your app.

Note the domain here is milestogo, application name is mywildflytest, and SSH user name is 546e3743ecb8d49ca9000014. These will be passed to Arquillian for running the tests.

Second is to enable and configure Jenkins.In your OpenShift Console, pick the “mywildfly” application and click on “Enable Jenkins” link as shown below:Remember this is not your Test instance because all the source code lives on the instance created earlier.Provide the appropriate name, e.g. jenkins-milestogo.rhcloud.com in my case, and click on “Add Jenkins” button. This will provision a Jenkins instance, if not already there and also configure the project with a script to build and deploy the application. Note down the name and password credentials.

Use the credentials to login to your Jenkins instance.Select the appropriate build, “mywildfly-build” in this case. Scroll down to the “Build” section and add the following script right after “# Run tests here” in the Execute Shell:

export ARQ_DOMAIN=milestogo
export ARQ_SSH_USER_NAME=546e3743ecb8d49ca9000014
export ARQ_APPLICATION=mywildflytest
mvn test -Pjenkins-openshift

export ARQ_DOMAIN=milestogo

export ARQ_SSH_USER_NAME=546e3743ecb8d49ca9000014

export ARQ_APPLICATION=mywildflytest

mvn test -Pjenkins-openshift

Click on “Save” to save the configuration. This will allow to run the Arquillian tests on the Test instance. If the tests pass then the app is deployed. If the tests fail, then none of the steps after that step are executed and so the app is not deployed.

Lets push the changes to remote repo now:

mywildfly> git push
Counting objects: 68, done.
Delta compression using up to 8 threads.
Compressing objects: 100% (49/49), done.
Writing objects: 100% (61/61), 8.85 KiB | 0 bytes/s, done.
Total 61 (delta 14), reused 0 (delta 0)
remote: Executing Jenkins build.
remote: 
remote: You can track your build at https://jenkins-milestogo.rhcloud.com/job/mywildfly-build
remote: 
remote: Waiting for build to schedule............................................................................................Done
remote: Waiting for job to complete................................................................................................................................................................................................................................................................................................................................................................................................Done
remote: SUCCESS
remote: New build has been deployed.
remote: -------------------------
remote: Git Post-Receive Result: success
remote: Deployment completed with status: success
To ssh://546cef93ecb8d4ff37000003@mywildfly-milestogo.rhcloud.com/~/git/mywildfly.git/
   e8f6c61..e9ad206  master -> master

mywildfly> git push

Counting objects: 68, done.

Delta compression using up to 8 threads.

Compressing objects: 100% (49/49), done.

Writing objects: 100% (61/61), 8.85 KiB | 0 bytes/s, done.

Total 61 (delta 14), reused 0 (delta 0)

remote: Executing Jenkins build.

remote:

remote: You can track your build at https://jenkins-milestogo.rhcloud.com/job/mywildfly-build

remote:

remote: Waiting for build to schedule............................................................................................Done

remote: Waiting for job to complete................................................................................................................................................................................................................................................................................................................................................................................................Done

remote: SUCCESS

remote: New build has been deployed.

remote: -------------------------

remote: Git Post-Receive Result: success

remote: Deployment completed with status: success

To ssh://546cef93ecb8d4ff37000003@mywildfly-milestogo.rhcloud.com/~/git/mywildfly.git/

e8f6c61..e9ad206 master -> master

The number of dots indicate the wait for a particular task and will most likely vary for different runs. And Jenkins console (jenkins-milestogo.rhcloud.com/job/mywildfly-build/1/console) shows the output as:

-------------------------------------------------------
 T E S T S
-------------------------------------------------------
Running org.javaee7.sample.PersonTest
Nov 20, 2014 2:54:56 PM org.jboss.arquillian.container.openshift.OpenShiftContainer start
INFO: Preparing Arquillian OpenShift container at http://mywildflytest-milestogo.rhcloud.com
Nov 20, 2014 2:55:48 PM org.jboss.arquillian.container.openshift.OpenShiftRepository push
INFO: Pushed to the remote repository ssh://546e3743ecb8d49ca9000014@mywildflytest-milestogo.rhcloud.com/~/git/mywildflytest.git/
Nov 20, 2014 2:56:37 PM org.jboss.arquillian.container.openshift.OpenShiftRepository push
INFO: Pushed to the remote repository ssh://546e3743ecb8d49ca9000014@mywildflytest-milestogo.rhcloud.com/~/git/mywildflytest.git/
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 103.056 sec
Nov 20, 2014 2:56:37 PM org.jboss.arquillian.container.openshift.OpenShiftContainer stop
INFO: Shutting down Arquillian OpenShift container at http://mywildflytest-milestogo.rhcloud.com
Results :

Tests run: 2, Failures: 0, Errors: 0, Skipped: 0

[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 3:13.069s
[INFO] Finished at: Thu Nov 20 14:57:34 EST 2014
[INFO] Final Memory: 10M/101M
[INFO] ------------------------------------------------------------------------
+ /usr/libexec/openshift/cartridges/jenkins/bin/git_ssh_wrapper.sh 546e36e5e0b8cd4e2a000007@mywildfly-milestogo.rhcloud.com 'gear stop --conditional'
Warning: Permanently added 'mywildfly-milestogo.rhcloud.com,10.5.171.43' (RSA) to the list of known hosts.
Stopping gear...
Stopping wildfly cart
Sending SIGTERM to wildfly:418673 ...
+ rsync --delete-after -azO -e /usr/libexec/openshift/cartridges/jenkins/bin/git_ssh_wrapper.sh /var/lib/openshift/546e46304382ec3f29000012//.m2/ '546e36e5e0b8cd4e2a000007@mywildfly-milestogo.rhcloud.com:~/.m2/'
Warning: Permanently added 'mywildfly-milestogo.rhcloud.com,10.5.171.43' (RSA) to the list of known hosts.
+ rsync --delete-after -azO -e /usr/libexec/openshift/cartridges/jenkins/bin/git_ssh_wrapper.sh /var/lib/openshift/546e46304382ec3f29000012/app-root/runtime/repo/deployments/ '546e36e5e0b8cd4e2a000007@mywildfly-milestogo.rhcloud.com:${OPENSHIFT_REPO_DIR}deployments/'
Warning: Permanently added 'mywildfly-milestogo.rhcloud.com,10.5.171.43' (RSA) to the list of known hosts.
+ rsync --delete-after -azO -e /usr/libexec/openshift/cartridges/jenkins/bin/git_ssh_wrapper.sh /var/lib/openshift/546e46304382ec3f29000012/app-root/runtime/repo/.openshift/ '546e36e5e0b8cd4e2a000007@mywildfly-milestogo.rhcloud.com:${OPENSHIFT_REPO_DIR}.openshift/'
Warning: Permanently added 'mywildfly-milestogo.rhcloud.com,10.5.171.43' (RSA) to the list of known hosts.
+ /usr/libexec/openshift/cartridges/jenkins/bin/git_ssh_wrapper.sh 546e36e5e0b8cd4e2a000007@mywildfly-milestogo.rhcloud.com 'gear remotedeploy'
Warning: Permanently added 'mywildfly-milestogo.rhcloud.com,10.5.171.43' (RSA) to the list of known hosts.
Preparing build for deployment
Deployment id is dff28e58
Activating deployment
Deploying WildFly
Starting wildfly cart
Found 127.12.255.129:8080 listening port
Found 127.12.255.129:9990 listening port
/var/lib/openshift/546e36e5e0b8cd4e2a000007/wildfly/standalone/deployments /var/lib/openshift/546e36e5e0b8cd4e2a000007/wildfly
/var/lib/openshift/546e36e5e0b8cd4e2a000007/wildfly
CLIENT_MESSAGE: Artifacts deployed: ./ROOT.war
Archiving artifacts
Finished: SUCCESS

-------------------------------------------------------

T E S T S

-------------------------------------------------------

Running org.javaee7.sample.PersonTest

Nov 20, 2014 2:54:56 PM org.jboss.arquillian.container.openshift.OpenShiftContainer start

INFO: Preparing Arquillian OpenShift container at http://mywildflytest-milestogo.rhcloud.com

Nov 20, 2014 2:55:48 PM org.jboss.arquillian.container.openshift.OpenShiftRepository push

INFO: Pushed to the remote repository ssh://546e3743ecb8d49ca9000014@mywildflytest-milestogo.rhcloud.com/~/git/mywildflytest.git/

Nov 20, 2014 2:56:37 PM org.jboss.arquillian.container.openshift.OpenShiftRepository push

INFO: Pushed to the remote repository ssh://546e3743ecb8d49ca9000014@mywildflytest-milestogo.rhcloud.com/~/git/mywildflytest.git/

Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 103.056 sec

Nov 20, 2014 2:56:37 PM org.jboss.arquillian.container.openshift.OpenShiftContainer stop

INFO: Shutting down Arquillian OpenShift container at http://mywildflytest-milestogo.rhcloud.com

Results :

Tests run: 2, Failures: 0, Errors: 0, Skipped: 0

[INFO] ------------------------------------------------------------------------

[INFO] BUILD SUCCESS

[INFO] ------------------------------------------------------------------------

[INFO] Total time: 3:13.069s

[INFO] Finished at: Thu Nov 20 14:57:34 EST 2014

[INFO] Final Memory: 10M/101M

[INFO] ------------------------------------------------------------------------

+ /usr/libexec/openshift/cartridges/jenkins/bin/git_ssh_wrapper.sh 546e36e5e0b8cd4e2a000007@mywildfly-milestogo.rhcloud.com 'gear stop --conditional'

Warning: Permanently added 'mywildfly-milestogo.rhcloud.com,10.5.171.43' (RSA) to the list of known hosts.

Stopping gear...

Stopping wildfly cart

Sending SIGTERM to wildfly:418673 ...

+ rsync --delete-after -azO -e /usr/libexec/openshift/cartridges/jenkins/bin/git_ssh_wrapper.sh /var/lib/openshift/546e46304382ec3f29000012//.m2/ '546e36e5e0b8cd4e2a000007@mywildfly-milestogo.rhcloud.com:~/.m2/'

Warning: Permanently added 'mywildfly-milestogo.rhcloud.com,10.5.171.43' (RSA) to the list of known hosts.

+ rsync --delete-after -azO -e /usr/libexec/openshift/cartridges/jenkins/bin/git_ssh_wrapper.sh /var/lib/openshift/546e46304382ec3f29000012/app-root/runtime/repo/deployments/ '546e36e5e0b8cd4e2a000007@mywildfly-milestogo.rhcloud.com:${OPENSHIFT_REPO_DIR}deployments/'

Warning: Permanently added 'mywildfly-milestogo.rhcloud.com,10.5.171.43' (RSA) to the list of known hosts.

+ rsync --delete-after -azO -e /usr/libexec/openshift/cartridges/jenkins/bin/git_ssh_wrapper.sh /var/lib/openshift/546e46304382ec3f29000012/app-root/runtime/repo/.openshift/ '546e36e5e0b8cd4e2a000007@mywildfly-milestogo.rhcloud.com:${OPENSHIFT_REPO_DIR}.openshift/'

Warning: Permanently added 'mywildfly-milestogo.rhcloud.com,10.5.171.43' (RSA) to the list of known hosts.

+ /usr/libexec/openshift/cartridges/jenkins/bin/git_ssh_wrapper.sh 546e36e5e0b8cd4e2a000007@mywildfly-milestogo.rhcloud.com 'gear remotedeploy'

Warning: Permanently added 'mywildfly-milestogo.rhcloud.com,10.5.171.43' (RSA) to the list of known hosts.

Preparing build for deployment

Deployment id is dff28e58

Activating deployment

Deploying WildFly

Starting wildfly cart

Found 127.12.255.129:8080 listening port

Found 127.12.255.129:9990 listening port

/var/lib/openshift/546e36e5e0b8cd4e2a000007/wildfly/standalone/deployments /var/lib/openshift/546e36e5e0b8cd4e2a000007/wildfly

/var/lib/openshift/546e36e5e0b8cd4e2a000007/wildfly

CLIENT_MESSAGE: Artifacts deployed: ./ROOT.war

Archiving artifacts

Finished: SUCCESS

Log files for Jenkins can be viewed as shown:

Nov 20, 2014 2:51:11 PM hudson.plugins.openshift.OpenShiftCloud provision
INFO: Provisioning new node for workload = 2 and label = mywildfly-build in domain milestogo
Nov 20, 2014 2:51:11 PM hudson.plugins.openshift.OpenShiftCloud getOpenShiftConnection
INFO: Initiating Java Client Service - Configured for OpenShift Server https://openshift.redhat.com
Nov 20, 2014 2:51:11 PM com.openshift.internal.client.RestService request
INFO: Requesting GET with protocol 1.2 on https://openshift.redhat.com/broker/rest/api
Nov 20, 2014 2:51:11 PM com.openshift.internal.client.RestService request
INFO: Requesting GET with protocol 1.2 on https://openshift.redhat.com/broker/rest/user
Nov 20, 2014 2:51:11 PM com.openshift.internal.client.RestService request

. . .

INFO: Checking availability of computer hudson.plugins.openshift.OpenShiftSlave@8ce21115
Nov 20, 2014 2:53:35 PM com.openshift.internal.client.RestService request
INFO: Requesting GET with protocol 1.2 on https://openshift.redhat.com/broker/rest/domain/milestogo/application/mywildflybldr/gear_groups
Nov 20, 2014 2:53:35 PM hudson.plugins.openshift.OpenShiftComputerLauncher launch
INFO: Checking SSH access to application mywildflybldr-milestogo.rhcloud.com
Nov 20, 2014 2:53:35 PM hudson.plugins.openshift.OpenShiftComputerLauncher launch
INFO: Connecting via SSH '546e46304382ec3f29000012' 'mywildflybldr-milestogo.rhcloud.com' '/var/lib/openshift/546e393e5973ca0492000070/app-root/data/.ssh/jenkins_id_rsa'
Nov 20, 2014 2:53:35 PM hudson.slaves.NodeProvisioner update
INFO: mywildfly-build provisioningE successfully completed. We have now 2 computer(s)
Nov 20, 2014 2:53:35 PM hudson.plugins.openshift.OpenShiftComputerLauncher launch
INFO: Connected via SSH.
Nov 20, 2014 2:53:35 PM hudson.plugins.openshift.OpenShiftComputerLauncher launch
INFO: Exec mkdir -p $OPENSHIFT_DATA_DIR/jenkins && cd $OPENSHIFT_DATA_DIR/jenkins && rm -f slave.jar && wget -q --no-check-certificate https://jenkins-milestogo.rhcloud.com/jnlpJars/slave.jar
Nov 20, 2014 2:53:42 PM hudson.plugins.openshift.OpenShiftComputerLauncher launch
INFO: Slave connected.
Nov 20, 2014 2:58:24 PM hudson.model.Run execute
INFO: mywildfly-build #1 main build action completed: SUCCESS

Nov 20, 2014 2:51:11 PM hudson.plugins.openshift.OpenShiftCloud provision

INFO: Provisioning new node for workload = 2 and label = mywildfly-build in domain milestogo

Nov 20, 2014 2:51:11 PM hudson.plugins.openshift.OpenShiftCloud getOpenShiftConnection

INFO: Initiating Java Client Service - Configured for OpenShift Server https://openshift.redhat.com

Nov 20, 2014 2:51:11 PM com.openshift.internal.client.RestService request

INFO: Requesting GET with protocol 1.2 on https://openshift.redhat.com/broker/rest/api

Nov 20, 2014 2:51:11 PM com.openshift.internal.client.RestService request

INFO: Requesting GET with protocol 1.2 on https://openshift.redhat.com/broker/rest/user

Nov 20, 2014 2:51:11 PM com.openshift.internal.client.RestService request

. . .

INFO: Checking availability of computer hudson.plugins.openshift.OpenShiftSlave@8ce21115

Nov 20, 2014 2:53:35 PM com.openshift.internal.client.RestService request

INFO: Requesting GET with protocol 1.2 on https://openshift.redhat.com/broker/rest/domain/milestogo/application/mywildflybldr/gear_groups

Nov 20, 2014 2:53:35 PM hudson.plugins.openshift.OpenShiftComputerLauncher launch

INFO: Checking SSH access to application mywildflybldr-milestogo.rhcloud.com

Nov 20, 2014 2:53:35 PM hudson.plugins.openshift.OpenShiftComputerLauncher launch

INFO: Connecting via SSH '546e46304382ec3f29000012' 'mywildflybldr-milestogo.rhcloud.com' '/var/lib/openshift/546e393e5973ca0492000070/app-root/data/.ssh/jenkins_id_rsa'

Nov 20, 2014 2:53:35 PM hudson.slaves.NodeProvisioner update

INFO: mywildfly-build provisioningE successfully completed. We have now 2 computer(s)

Nov 20, 2014 2:53:35 PM hudson.plugins.openshift.OpenShiftComputerLauncher launch

INFO: Connected via SSH.

Nov 20, 2014 2:53:35 PM hudson.plugins.openshift.OpenShiftComputerLauncher launch

INFO: Exec mkdir -p $OPENSHIFT_DATA_DIR/jenkins && cd $OPENSHIFT_DATA_DIR/jenkins && rm -f slave.jar && wget -q --no-check-certificate https://jenkins-milestogo.rhcloud.com/jnlpJars/slave.jar

Nov 20, 2014 2:53:42 PM hudson.plugins.openshift.OpenShiftComputerLauncher launch

INFO: Slave connected.

Nov 20, 2014 2:58:24 PM hudson.model.Run execute

INFO: mywildfly-build #1 main build action completed: SUCCESS

This shows the application was successfully deployed at mywildfly-milestogo.rhcloud.com/index.jsp and looks like as shown:

Now change “src/main/webapp/index.jsp” to show a different heading. And change “src/test/java/org/javaee7/sample/PersonTest.java” to make one of the tests fail. Doing “git commit” and “git push” shows the following results on command line:

mywildfly> git commit . -m"breaking the test"
[master ff2de09] breaking the test
 2 files changed, 2 insertions(+), 2 deletions(-)
mywildfly> git push
Counting objects: 23, done.
Delta compression using up to 8 threads.
Compressing objects: 100% (8/8), done.
Writing objects: 100% (12/12), 771 bytes | 0 bytes/s, done.
Total 12 (delta 5), reused 0 (delta 0)
remote: Executing Jenkins build.
remote: 
remote: You can track your build at https://jenkins-milestogo.rhcloud.com/job/mywildfly-build
remote: 
remote: Waiting for build to schedule.......Done
remote: Waiting for job to complete.....................................................................................................................................................................Done
remote: FAILED
remote: !!!!!!!!
remote: Deployment Halted!
remote: If the build failed before the deploy step, your previous
remote: build is still running.  Otherwise, your application may be
remote: partially deployed or inaccessible.
remote: Fix the build and try again.
remote: !!!!!!!!
remote: An error occurred executing 'gear postreceive' (exit code: 1)
remote: Error message: CLIENT_ERROR: Failed to execute: 'control post-receive' for /var/lib/openshift/546e36e5e0b8cd4e2a000007/jenkins-client
remote: 
remote: For more details about the problem, try running the command again with the '--trace' option.
To ssh://546e36e5e0b8cd4e2a000007@mywildfly-milestogo.rhcloud.com/~/git/mywildfly.git/
   d618fad..ff2de09  master -> master

mywildfly> git commit . -m"breaking the test"

[master ff2de09] breaking the test

2 files changed, 2 insertions(+), 2 deletions(-)

mywildfly> git push

Counting objects: 23, done.

Delta compression using up to 8 threads.

Compressing objects: 100% (8/8), done.

Writing objects: 100% (12/12), 771 bytes | 0 bytes/s, done.

Total 12 (delta 5), reused 0 (delta 0)

remote: Executing Jenkins build.

remote:

remote: You can track your build at https://jenkins-milestogo.rhcloud.com/job/mywildfly-build

remote:

remote: Waiting for build to schedule.......Done

remote: FAILED

remote: !!!!!!!!

remote: Deployment Halted!

remote: If the build failed before the deploy step, your previous

remote: build is still running. Otherwise, your application may be

remote: partially deployed or inaccessible.

remote: Fix the build and try again.

remote: !!!!!!!!

remote: An error occurred executing 'gear postreceive' (exit code: 1)

remote: Error message: CLIENT_ERROR: Failed to execute: 'control post-receive' for /var/lib/openshift/546e36e5e0b8cd4e2a000007/jenkins-client

remote:

remote: For more details about the problem, try running the command again with the '--trace' option.

To ssh://546e36e5e0b8cd4e2a000007@mywildfly-milestogo.rhcloud.com/~/git/mywildfly.git/

d618fad..ff2de09 master -> master

The key statement to note is that deployment is halted after the tests are failing. And you can verify this by revisiting mywildfly-milestogo.rhcloud.com/index.jsp and check that the updated “index.jsp” is not visible.

In short, tests pass, website is updated. And tests fail, the website is not updated. So you’ve built a simple deployment pipeline for Java EE 7 using WildFly, OpenShift, Arquillian, and Jenkins!

Arquillian tests on a WildFly instance hosted on OpenShift (Tech Tip #55)

November 17, 2014javaee, techtip, wildflyarquillian, devops, javaee7, openshift, wildflyarungupta

Tech Tip #54 explained how to enable Arquillian for an existing Java EE project. In that tip, the tests were run against a locally installed WildFly server. Would the same adapter work if this WildFly instance was running on OpenShift ? No!

Because the security constraints and requirement of a PaaS, as opposed to a localhost, are different. Lets take a look at what’s required to run our tests in javaee7-continuous-delivery on a WildFly instance hosted on OpenShift.

Lets get started!

As explained in Tech Tip #52, create a WildFly application on OpenShift as shown:

workspaces> rhc app-create mywildfly jboss-wildfly-8
Application Options
-------------------
Domain:     milestogo
Cartridges: jboss-wildfly-8
Gear Size:  default
Scaling:    no

Creating application 'mywildfly' ... Artifacts deployed: ./ROOT.war
done

  WildFly 8 administrator added.  Please make note of these credentials:

   Username: adminMYtMTDb
   Password: tq1K-QYLFgBD
   
   run 'rhc port-forward mywildfly' to access the web admin area on port 9990.

Waiting for your DNS name to be available ... done

Cloning into 'mywildfly'...
Warning: Permanently added the RSA host key for IP address '54.163.64.193' to the list of known hosts.

Your application 'mywildfly' is now available.

  URL:        http://mywildfly-milestogo.rhcloud.com/
  SSH to:     54699516ecb8d41cb8000016@mywildfly-milestogo.rhcloud.com
  Git remote: ssh://54699516ecb8d41cb8000016@mywildfly-milestogo.rhcloud.com/~/git/mywildfly.git/
  Cloned to:  /Users/arungupta/workspaces/mywildfly

Run 'rhc show-app mywildfly' for more details about your app.

workspaces> rhc app-create mywildfly jboss-wildfly-8

Application Options

-------------------

Domain: milestogo

Cartridges: jboss-wildfly-8

Gear Size: default

Scaling: no

Creating application 'mywildfly' ... Artifacts deployed: ./ROOT.war

done

WildFly 8 administrator added. Please make note of these credentials:

Username: adminMYtMTDb

Password: tq1K-QYLFgBD

run 'rhc port-forward mywildfly' to access the web admin area on port 9990.

Waiting for your DNS name to be available ... done

Cloning into 'mywildfly'...

Warning: Permanently added the RSA host key for IP address '54.163.64.193' to the list of known hosts.

Your application 'mywildfly' is now available.

URL: http://mywildfly-milestogo.rhcloud.com/

SSH to: 54699516ecb8d41cb8000016@mywildfly-milestogo.rhcloud.com

Git remote: ssh://54699516ecb8d41cb8000016@mywildfly-milestogo.rhcloud.com/~/git/mywildfly.git/

Cloned to: /Users/arungupta/workspaces/mywildfly

Run 'rhc show-app mywildfly' for more details about your app.

Note down the ssh user name from the log. This is the part before @ in the value corresponding to SSH to.

Until FORGEPLUGINS-177 is resolved, we need to manually add maven profile and provide container configuration information in “arquillian.xml”. Add the following <profile> to “pom.xml”:

<profile>
    <id>arquillian-wildfly-openshift</id>
    <build>
        <plugins>
            <plugin>
                <artifactId>maven-surefire-plugin</artifactId>
                <version>2.14.1</version>
                <configuration>
                    <systemPropertyVariables>
                        <arquillian.launch>arquillian-wildfly-openshift</arquillian.launch>
                    </systemPropertyVariables>
                </configuration>
            </plugin>
        </plugins>
    </build>
    <dependencies>
        <dependency>
            <groupId>org.jboss.arquillian.container</groupId>
            <artifactId>arquillian-openshift</artifactId>
            <version>1.0.0.Final-SNAPSHOT</version>
            <scope>test</scope>
        </dependency>
    </dependencies>
</profile>

<id>arquillian-wildfly-openshift</id>

<build>

<artifactId>maven-surefire-plugin</artifactId>

<arquillian.launch>arquillian-wildfly-openshift</arquillian.launch>

</systemPropertyVariables>

</configuration>

</plugin>

</plugins>

</build>

<groupId>org.jboss.arquillian.container</groupId>

<artifactId>arquillian-openshift</artifactId>

<version>1.0.0.Final-SNAPSHOT</version>

</dependency>

</dependencies>

</profile>

This is using arquillian-openshift container and referring to arquillian-wildfly-openshift configuration that will be matched with the appropriate container in “arquillian.xml”.

So this is how the updated “arquillian.xml” look:

<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<arquillian xmlns="http://jboss.org/schema/arquillian" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://jboss.org/schema/arquillian http://jboss.org/schema/arquillian/arquillian_1_0.xsd">
    <container qualifier="arquillian-wildfly-remote"/>
    <container qualifier="arquillian-wildfly-openshift">
        <configuration>
            <property name="namespace">milestogo</property>
            <property name="application">mywildfly</property>
            <property name="libraDomain">rhcloud.com</property>
            <property name="sshUserName">54699516ecb8d41cb8000016</property>
            <property name="login">arungupta@redhat.com</property>
            <property name="deploymentTimeoutInSeconds">300</property>
            <property name="disableStrictHostChecking">true</property> 
        </configuration>
    </container>
</arquillian>

<?xml version="1.0" encoding="UTF-8" standalone="no"?>

<property name="namespace">milestogo</property>

<property name="application">mywildfly</property>

<property name="libraDomain">rhcloud.com</property>

<property name="login">arungupta@redhat.com</property>

</configuration>

</container>

</arquillian>

Note the new <container> with the qualifier arquillian-wildfly-openshift. It provides information about where the server is located and some other configuration properties. The sshUserName property value should be the same from the WildFly instance created earlier.

That’s it, now you can run the test against the WildFly instance on OpenShift:

javaee7-simple-sample> mvn test -Parquillian-wildfly-openshift
[INFO] Scanning for projects...
[INFO]                                                                         
[INFO] ------------------------------------------------------------------------
[INFO] Building helloworld 1.0-SNAPSHOT
[INFO] ------------------------------------------------------------------------
[INFO] 
[INFO] --- maven-resources-plugin:2.6:resources (default-resources) @ helloworld ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 0 resource
[INFO] 
[INFO] --- maven-compiler-plugin:3.1:compile (default-compile) @ helloworld ---
[INFO] Nothing to compile - all classes are up to date
[INFO] 
[INFO] --- maven-resources-plugin:2.6:testResources (default-testResources) @ helloworld ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 1 resource
[INFO] 
[INFO] --- maven-compiler-plugin:3.1:testCompile (default-testCompile) @ helloworld ---
[INFO] Nothing to compile - all classes are up to date
[INFO] 
[INFO] --- maven-surefire-plugin:2.14.1:test (default-test) @ helloworld ---
[INFO] Surefire report directory: /Users/arungupta/workspaces/javaee7-simple-sample/target/surefire-reports

-------------------------------------------------------
 T E S T S
-------------------------------------------------------
Running org.javaee7.sample.PersonTest
Nov 17, 2014 11:18:24 AM org.jboss.arquillian.container.openshift.OpenShiftContainer start
INFO: Preparing Arquillian OpenShift container at http://mywildfly-milestogo.rhcloud.com
Nov 17, 2014 11:19:19 AM org.jboss.arquillian.container.openshift.OpenShiftRepository push
INFO: Pushed to the remote repository ssh://54699516ecb8d41cb8000016@mywildfly-milestogo.rhcloud.com/~/git/mywildfly.git/
Nov 17, 2014 11:20:56 AM org.jboss.arquillian.container.openshift.OpenShiftRepository push
INFO: Pushed to the remote repository ssh://54699516ecb8d41cb8000016@mywildfly-milestogo.rhcloud.com/~/git/mywildfly.git/
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 152.653 sec
Nov 17, 2014 11:20:56 AM org.jboss.arquillian.container.openshift.OpenShiftContainer stop
INFO: Shutting down Arquillian OpenShift container at http://mywildfly-milestogo.rhcloud.com

Results :

Tests run: 2, Failures: 0, Errors: 0, Skipped: 0

[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 05:46 min
[INFO] Finished at: 2014-11-17T11:24:09+02:00
[INFO] Final Memory: 12M/309M
[INFO] ------------------------------------------------------------------------

javaee7-simple-sample> mvn test -Parquillian-wildfly-openshift

[INFO] Scanning for projects...

[INFO]

[INFO] ------------------------------------------------------------------------

[INFO] Building helloworld 1.0-SNAPSHOT

[INFO] ------------------------------------------------------------------------

[INFO]

[INFO] --- maven-resources-plugin:2.6:resources (default-resources) @ helloworld ---

[INFO] Using 'UTF-8' encoding to copy filtered resources.

[INFO] Copying 0 resource

[INFO]

[INFO] --- maven-compiler-plugin:3.1:compile (default-compile) @ helloworld ---

[INFO] Nothing to compile - all classes are up to date

[INFO]

[INFO] --- maven-resources-plugin:2.6:testResources (default-testResources) @ helloworld ---

[INFO] Using 'UTF-8' encoding to copy filtered resources.

[INFO] Copying 1 resource

[INFO]

[INFO] --- maven-compiler-plugin:3.1:testCompile (default-testCompile) @ helloworld ---

[INFO] Nothing to compile - all classes are up to date

[INFO]

[INFO] --- maven-surefire-plugin:2.14.1:test (default-test) @ helloworld ---

[INFO] Surefire report directory: /Users/arungupta/workspaces/javaee7-simple-sample/target/surefire-reports

-------------------------------------------------------

T E S T S

-------------------------------------------------------

Running org.javaee7.sample.PersonTest

Nov 17, 2014 11:18:24 AM org.jboss.arquillian.container.openshift.OpenShiftContainer start

INFO: Preparing Arquillian OpenShift container at http://mywildfly-milestogo.rhcloud.com

Nov 17, 2014 11:19:19 AM org.jboss.arquillian.container.openshift.OpenShiftRepository push

INFO: Pushed to the remote repository ssh://54699516ecb8d41cb8000016@mywildfly-milestogo.rhcloud.com/~/git/mywildfly.git/

Nov 17, 2014 11:20:56 AM org.jboss.arquillian.container.openshift.OpenShiftRepository push

INFO: Pushed to the remote repository ssh://54699516ecb8d41cb8000016@mywildfly-milestogo.rhcloud.com/~/git/mywildfly.git/

Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 152.653 sec

Nov 17, 2014 11:20:56 AM org.jboss.arquillian.container.openshift.OpenShiftContainer stop

INFO: Shutting down Arquillian OpenShift container at http://mywildfly-milestogo.rhcloud.com

Results :

Tests run: 2, Failures: 0, Errors: 0, Skipped: 0

[INFO] ------------------------------------------------------------------------

[INFO] BUILD SUCCESS

[INFO] ------------------------------------------------------------------------

[INFO] Total time: 05:46 min

[INFO] Finished at: 2014-11-17T11:24:09+02:00

[INFO] Final Memory: 12M/309M

[INFO] ------------------------------------------------------------------------

The complete source code is available at github.com/arun-gupta/javaee7-continuous-delivery.

Enjoy!

Slides from Nuts and Bolts of WebSocket at #Devoxx 2014

November 10, 2014conferences, javaee, wildflyjavaee7, openshift, websocket, wildflyarungupta

Peter Moskovits from Kaazing (@peterm_kaazing) and I gave a university talk at Devoxx 2014 on Nuts and Bolts of WebSocket. The slides are now available at:

The entire session is recorded and will be made available on parleys.com in the coming weeks/months.

The complete script for the demo is available at github.com/arun-gupta/nuts-and-bolts-of-websocket (including pointers to the demos). Most of the demos are anyway available at the following links:

Chrome Developer Tools: http://www.websocket.org/echo.html
Canonical Chat Server: https://github.com/javaee-samples/javaee7-samples/tree/master/websocket/chat
Chat Server on OpenShift: http://blog.arungupta.me/2014/10/websocket-chat-wildfly-openshift-techtip51/
Collaborative Whiteboard: https://github.com/javaee-samples/javaee7-samples/tree/master/websocket/whiteboard
WebSocket Client API: https://github.com/javaee-samples/javaee7-samples/tree/master/websocket/google-docs
User-name based security: http://blog.arungupta.me/2014/10/securing-websockets-username-password-servlet-security-techtip49/
TLS-based security: http://blog.arungupta.me/2014/10/securing-websocket-wss-https-tls-techtip50/
Load Balancing WebSocket: http://blog.arungupta.me/2014/08/load-balance-websockets-apache-httpd-techtip48/
JMS and JavaScript: Pub/Sub over WebSocket: http://demo.kaazing.com/demo/jms/javascript/jms-javascript.html
STOMP over WebSocket: http://blog.arungupta.me/2014/11/stomp-over-websocket-tech-tip-53/
Compare WebSocket with REST: https://github.com/javaee-samples/javaee7-samples/tree/master/websocket/websocket-vs-rest-payload

Positive feedback from twitter overall:

Nice working application build in seconds! #Devoxx #WebSocket And once again, we developer are very… http://t.co/mLsnKf4Vcp

— Miguel Discart (@Miguel_Discart) November 10, 2014

Who’s doing Nuts and Bolts of #Websocket ? @arungupta #Devoxx pic.twitter.com/nAeGFTj6vx

— Antoine Sabot-Durand (@antoine_sd) November 10, 2014

@arungupta and @peterm_kaazing gave a very informative code live session about #Websocket in #Devoxx

— jianing zhang (@jianinz) November 10, 2014

#Devoxx #websocket really interesting uni session today in Antwerpen. Arun and Peter giving good info

— Koen (@koendroid) November 10, 2014

Nuts and Bolts of #Websocket SRO #Devoxx @arungupta pic.twitter.com/XoedutFiVJ

— Java (@java) November 10, 2014

Really cool WebSocket demo. Open http://t.co/C9ybgFPTLw and control it from mobile. #devoxx #websocket

— DiversIT Europe (@diversit) November 10, 2014

@arungupta & @peterm_kaazing gave amazing talk on #websocket at #devoxx

— Vladimir Milovanović (@mmwlada) November 10, 2014

At #Devoxx I Just developed & deployed my first websocket app on WildfFly on Openshift in 4mins! Thanks @arungupta Great Talk

— Sabri Skhiri (@sskhiri) November 10, 2014

And it was rated the top talk for the day until 6pm:

devoxx14-websocket-talk-rank

With Red Hat spirit, “the more you share, the more you grow”, share the slides and demos all over and spread the love!

Happy Devoxx!

Create WildFly OpenShift application using Command Line Tools (Tech Tip #52)

November 5, 2014java, redhat, techtip, wildflyopenshift, wildflyarungupta

A new instance of WildFly can be easily provisioned on OpenShift by using the quick start. Just a single click, and you are ready to go!

Generally power users of OpenShift use Command Line Tools. However you could not create WildFly cartridge using the CLI tools. But bug# 1134134 is now resolved.

And so now rhc cartridge-list shows:

workspaces&gt; rhc cartridge-list
jbossas-7           JBoss Application Server 7              web
jboss-dv-6.0.0 (!)  JBoss Data Virtualization 6             web
jbosseap-6 (*)      JBoss Enterprise Application Platform 6 web
jenkins-1           Jenkins Server                          web
nodejs-0.10         Node.js 0.10                            web
perl-5.10           Perl 5.10                               web
php-5.3             PHP 5.3                                 web
php-5.4             PHP 5.4                                 web
zend-6.1            PHP 5.4 with Zend Server 6.1            web
python-2.6          Python 2.6                              web
python-2.7          Python 2.7                              web
python-3.3          Python 3.3                              web
ruby-1.8            Ruby 1.8                                web
ruby-1.9            Ruby 1.9                                web
ruby-2.0            Ruby 2.0                                web
jbossews-1.0        Tomcat 6 (JBoss EWS 1.0)                web
jbossews-2.0        Tomcat 7 (JBoss EWS 2.0)                web
jboss-vertx-2.1 (!) Vert.x 2.1                              web
<strong>jboss-wildfly-8 (!) WildFly Application Server 8.1.0.Final  web</strong>
diy-0.1             Do-It-Yourself 0.1                      web
10gen-mms-agent-0.1 10gen Mongo Monitoring Service Agent    addon
cron-1.4            Cron 1.4                                addon
jenkins-client-1    Jenkins Client                          addon
mongodb-2.4         MongoDB 2.4                             addon
mysql-5.1           MySQL 5.1                               addon
mysql-5.5           MySQL 5.5                               addon
phpmyadmin-4        phpMyAdmin 4.0                          addon
postgresql-8.4      PostgreSQL 8.4                          addon
postgresql-9.2      PostgreSQL 9.2                          addon
rockmongo-1.1       RockMongo 1.1                           addon
switchyard-0        SwitchYard 0.8.0                        addon
haproxy-1.4         Web Load Balancer                       addon

Note: Web cartridges can only be added to new applications.

(*) denotes a cartridge with additional usage costs.

(!) denotes a cartridge that will not receive automatic security updates.

workspaces> rhc cartridge-list

jbossas-7 JBoss Application Server 7 web

jboss-dv-6.0.0 (!) JBoss Data Virtualization 6 web

jbosseap-6 (*) JBoss Enterprise Application Platform 6 web

jenkins-1 Jenkins Server web

nodejs-0.10 Node.js 0.10 web

perl-5.10 Perl 5.10 web

php-5.3 PHP 5.3 web

php-5.4 PHP 5.4 web

zend-6.1 PHP 5.4 with Zend Server 6.1 web

python-2.6 Python 2.6 web

python-2.7 Python 2.7 web

python-3.3 Python 3.3 web

ruby-1.8 Ruby 1.8 web

ruby-1.9 Ruby 1.9 web

ruby-2.0 Ruby 2.0 web

jbossews-1.0 Tomcat 6 (JBoss EWS 1.0) web

jbossews-2.0 Tomcat 7 (JBoss EWS 2.0) web

jboss-vertx-2.1 (!) Vert.x 2.1 web

jboss-wildfly-8 (!) WildFly Application Server 8.1.0.Final web

diy-0.1 Do-It-Yourself 0.1 web

10gen-mms-agent-0.1 10gen Mongo Monitoring Service Agent addon

cron-1.4 Cron 1.4 addon

jenkins-client-1 Jenkins Client addon

mongodb-2.4 MongoDB 2.4 addon

mysql-5.1 MySQL 5.1 addon

mysql-5.5 MySQL 5.5 addon

phpmyadmin-4 phpMyAdmin 4.0 addon

postgresql-8.4 PostgreSQL 8.4 addon

postgresql-9.2 PostgreSQL 9.2 addon

rockmongo-1.1 RockMongo 1.1 addon

switchyard-0 SwitchYard 0.8.0 addon

haproxy-1.4 Web Load Balancer addon

Note: Web cartridges can only be added to new applications.

(*) denotes a cartridge with additional usage costs.

(!) denotes a cartridge that will not receive automatic security updates.

The newly added cartridge of WildFly 8 is shown in bold.

And so now a new WildFly instance can be easily provisioned using the CLI as:

workspaces&gt; rhc app-create mywildfly jboss-wildfly-8
Application Options
-------------------
Domain:     milestogo
Cartridges: jboss-wildfly-8
Gear Size:  default
Scaling:    no

Creating application 'mywildfly' ... Artifacts deployed: ./ROOT.war
done

  WildFly 8 administrator added.  Please make note of these credentials:

   Username: adminLWEMEdW
   Password: 9u6jpWuQU6hg
   
   run 'rhc port-forward mywildfly' to access the web admin area on port 9990.

Waiting for your DNS name to be available ... done

Cloning into 'mywildfly'...
Warning: Permanently added the RSA host key for IP address '54.163.104.22' to the list of known hosts.

Your application 'mywildfly' is now available.

  URL:        http://mywildfly-milestogo.rhcloud.com/
  SSH to:     545ac1d0e0b8cd8ad800018d@mywildfly-milestogo.rhcloud.com
  Git remote: ssh://545ac1d0e0b8cd8ad800018d@mywildfly-milestogo.rhcloud.com/~/git/mywildfly.git/
  Cloned to:  /Users/arungupta/workspaces/mywildfly

Run 'rhc show-app mywildfly' for more details about your app.

workspaces> rhc app-create mywildfly jboss-wildfly-8

Application Options

-------------------

Domain: milestogo

Cartridges: jboss-wildfly-8

Gear Size: default

Scaling: no

Creating application 'mywildfly' ... Artifacts deployed: ./ROOT.war

done

WildFly 8 administrator added. Please make note of these credentials:

Username: adminLWEMEdW

Password: 9u6jpWuQU6hg

run 'rhc port-forward mywildfly' to access the web admin area on port 9990.

Waiting for your DNS name to be available ... done

Cloning into 'mywildfly'...

Warning: Permanently added the RSA host key for IP address '54.163.104.22' to the list of known hosts.

Your application 'mywildfly' is now available.

URL: http://mywildfly-milestogo.rhcloud.com/

SSH to: 545ac1d0e0b8cd8ad800018d@mywildfly-milestogo.rhcloud.com

Git remote: ssh://545ac1d0e0b8cd8ad800018d@mywildfly-milestogo.rhcloud.com/~/git/mywildfly.git/

Cloned to: /Users/arungupta/workspaces/mywildfly

Run 'rhc show-app mywildfly' for more details about your app.

And then the application’s main page is accessible as shown:

And the application can be deleted as:

workspaces&gt; rhc app-delete mywildfly 
This is a non-reversible action! Your application code and data will be permanently deleted if you continue!

Are you sure you want to delete the application 'mywildfly'? (yes|no): yes

Deleting application 'mywildfly' ... deleted

workspaces> rhc app-delete mywildfly

This is a non-reversible action! Your application code and data will be permanently deleted if you continue!

Are you sure you want to delete the application 'mywildfly'? (yes|no): yes

Deleting application 'mywildfly' ... deleted

Simple, isn’t it ?

See several other OpenShift getting-started related blog entries here.

WebSocket Chat on WildFly and OpenShift (Tech Tip #51)

October 29, 2014javaee, techtip, wildflyjavaee7, openshift, websocket, wildflyarungupta

Chat is one of the most canonical sample to explain WebSocket. Its a fairly commonly used interface and allows to explain the fundamental WebSocket concepts very easily. Of course, Java EE 7 WebSocket has one too, available here! You can easily run it on WildFly using the following steps:

curl -O http://download.jboss.org/wildfly/8.1.0.Final/wildfly-8.1.0.Final.zip
unzip wildfly-8.1.0.Final.zip
./wildfly-8.1.0.Final/bin/standalone.sh
git clone https://github.com/javaee-samples/javaee7-samples.git
cd javaee7-samples
mvn -f websocket/chat/pom.xml wildfly:deploy

curl -O http://download.jboss.org/wildfly/8.1.0.Final/wildfly-8.1.0.Final.zip

unzip wildfly-8.1.0.Final.zip

./wildfly-8.1.0.Final/bin/standalone.sh

git clone https://github.com/javaee-samples/javaee7-samples.git

cd javaee7-samples

mvn -f websocket/chat/pom.xml wildfly:deploy

And then access it at http://localhost:8080/chat/.

One of the biggest advantage of WebSocket is how it opens up a socket over the same port as HTTP, 8080 in this case. If you want to deploy this application to OpenShift, then WebSocket is available on port 8000 for regular access, and 8443 for secure access. This is explained in the figure below:

If you want to run this Chat application on OpenShift, then use the following steps:

Click here to provision a WildFly instance in OpenShift. Change the name to “chatserver” and everything else as default. Click on “Create Application” to create the application.

Clone the workspace:

git clone ssh://544f08a850044670df00009e@chatserver-milestogo.rhcloud.com/~/git/chatserver.git/

git clone ssh://544f08a850044670df00009e@chatserver-milestogo.rhcloud.com/~/git/chatserver.git/

Edit the first line of “javaee7-samples/websocket/chat/src/main/webapp/websocket.js”from:

var wsUri = "ws://" + document.location.hostname + ":" + document.location.port + document.location.pathname + "chat";

var wsUri = "ws://" + document.location.hostname + ":" + document.location.port + document.location.pathname + "chat";

var wsUri = "ws://" + document.location.hostname + ":8000" + document.location.pathname + "chat";

var wsUri = "ws://" + document.location.hostname + ":8000" + document.location.pathname + "chat";

Create the WAR file:

cd javaee7-samples
mvn -f websocket/chat/pom.xml

cd javaee7-samples

mvn -f websocket/chat/pom.xml

Copy the generated WAR file to the workspace cloned earlier:

cd ..
cp javaee7-samples/websocket/chat/target/chat.war chatserver/deployments/ROOT.war

cd ..

cp javaee7-samples/websocket/chat/target/chat.war chatserver/deployments/ROOT.war

Remove existing files and add the WAR file to git repository:

cd chatserver
git rm -rf src pom.xml
git add deployments/ROOT.war
git commit . -m"updating files"
git push

cd chatserver

git rm -rf src pom.xml

git add deployments/ROOT.war

git commit . -m"updating files"

git push

And this shows the output as:

Counting objects: 6, done.
Delta compression using up to 8 threads.
Compressing objects: 100% (4/4), done.
Writing objects: 100% (4/4), 6.88 KiB | 0 bytes/s, done.
Total 4 (delta 1), reused 0 (delta 0)
remote: Stopping wildfly cart
remote: Sending SIGTERM to wildfly:285130 ...
remote: Building git ref 'master', commit 05a7978
remote: Preparing build for deployment
remote: Deployment id is 14bcec20
remote: Activating deployment
remote: Deploying WildFly
remote: Starting wildfly cart
remote: Found 127.2.87.1:8080 listening port
remote: Found 127.2.87.1:9990 listening port
remote: /var/lib/openshift/544f08a850044670df00009e/wildfly/standalone/deployments /var/lib/openshift/544f08a850044670df00009e/wildfly
remote: /var/lib/openshift/544f08a850044670df00009e/wildfly
remote: CLIENT_MESSAGE: Artifacts deployed: ./ROOT.war
remote: -------------------------
remote: Git Post-Receive Result: success
remote: Activation status: success
remote: Deployment completed with status: success
To ssh://544f08a850044670df00009e@chatserver-milestogo.rhcloud.com/~/git/chatserver.git/
454bba9..05a7978  master -&gt; master

Counting objects: 6, done.

Delta compression using up to 8 threads.

Compressing objects: 100% (4/4), done.

Writing objects: 100% (4/4), 6.88 KiB | 0 bytes/s, done.

Total 4 (delta 1), reused 0 (delta 0)

remote: Stopping wildfly cart

remote: Sending SIGTERM to wildfly:285130 ...

remote: Building git ref 'master', commit 05a7978

remote: Preparing build for deployment

remote: Deployment id is 14bcec20

remote: Activating deployment

remote: Deploying WildFly

remote: Starting wildfly cart

remote: Found 127.2.87.1:8080 listening port

remote: Found 127.2.87.1:9990 listening port

remote: /var/lib/openshift/544f08a850044670df00009e/wildfly/standalone/deployments /var/lib/openshift/544f08a850044670df00009e/wildfly

remote: /var/lib/openshift/544f08a850044670df00009e/wildfly

remote: CLIENT_MESSAGE: Artifacts deployed: ./ROOT.war

remote: -------------------------

remote: Git Post-Receive Result: success

remote: Activation status: success

remote: Deployment completed with status: success

To ssh://544f08a850044670df00009e@chatserver-milestogo.rhcloud.com/~/git/chatserver.git/

454bba9..05a7978 master -> master

And now your chat server is available at: http://chatserver-milestogo.rhcloud.com and looks like:

Enjoy!

WildFly with a custom configuration in OpenShift (Tech Tip #47)

August 28, 2014techtip, wildflyopenshift, wildflyarungupta

WildFly instances can be easily started in OpenShift. Tech Tip #7 shows how to spin up an instance of WildFly in OpenShift. Tech Tip #21 explained how to get started using JBoss Tools.

Now this WildFly instance is started with the stock configuration.xml. However some times you may want to configure the containers or specify additional configuration information in this file. This Tech Tip will show you how to do that.

Let’s go!

Start a WildFly instance as explained in Tech Tip #7.

On the application page, clone the workspace associated with this application. The command will look something like:

git clone ssh://XXXXXXXXXX@test-milestogo.rhcloud.com/~/git/test.git/

git clone ssh://XXXXXXXXXX@test-milestogo.rhcloud.com/~/git/test.git/

This workspace has .openshift/standalone.xml file. Edit this file to meet your need. For example, if you want to use Infinispan as a persistency solution in standalone mode, then you’ll add the following code fragment:

&lt;cache-container name="myCache" default-cache="cachedb"&gt;
    &lt;local-cache name="cachedb"/&gt;
&lt;/cache-container&gt;

<cache-container name="myCache" default-cache="cachedb">

<local-cache name="cachedb"/>

</cache-container>

under <subsystem xmlns="urn:jboss:domain:infinispan:2.0"> section.

Commit and push the change:

config&gt; <strong>git commit standalone.xml -m"additional configuration elements"</strong>
[master cef567d] additional configuration elements
 1 file changed, 1 deletion(-)
config&gt; <strong>git push</strong>

config> git commit standalone.xml -m"additional configuration elements"

[master cef567d] additional configuration elements

1 file changed, 1 deletion(-)

config> git push

This will automatically restart the cartridge and show the output as:

Counting objects: 9, done.
Delta compression using up to 8 threads.
Compressing objects: 100% (5/5), done.
Writing objects: 100% (5/5), 656 bytes | 0 bytes/s, done.
Total 5 (delta 1), reused 0 (delta 0)
remote: Stopping wildfly cart
remote: Repairing links for 1 deployments
remote: Building git ref 'master', commit cef567d
remote: Found pom.xml... attempting to build with 'mvn -e clean package -Popenshift -DskipTests'
remote: Apache Maven 3.0.4 (r1232336; 2012-12-18 14:36:37-0500)
remote: Maven home: /usr/share/java/apache-maven-3.0.4
remote: Java version: 1.8.0_05, vendor: Oracle Corporation
remote: Java home: /var/lib/openshift/XXXXXXXXXX/wildfly/usr/lib/jvm/jdk1.8.0_05/jre
remote: Default locale: en_US, platform encoding: ANSI_X3.4-1968
remote: OS name: "linux", version: "2.6.32-431.23.3.el6.x86_64", arch: "i386", family: "unix"
remote: [INFO] Scanning for projects...
remote: [INFO]                                                                         
remote: [INFO] ------------------------------------------------------------------------
remote: [INFO] Building test 1.0
remote: [INFO] ------------------------------------------------------------------------
remote: [INFO] 
remote: [INFO] --- maven-clean-plugin:2.4.1:clean (default-clean) @ test ---
remote: [INFO] 
remote: [INFO] --- maven-resources-plugin:2.5:resources (default-resources) @ test ---
remote: [debug] execute contextualize
remote: [INFO] Using 'UTF-8' encoding to copy filtered resources.
remote: [INFO] Copying 1 resource
remote: [INFO] 
remote: [INFO] --- maven-compiler-plugin:2.3.2:compile (default-compile) @ test ---
remote: [INFO] Nothing to compile - all classes are up to date
remote: [INFO] 
remote: [INFO] --- maven-resources-plugin:2.5:testResources (default-testResources) @ test ---
remote: [debug] execute contextualize
remote: [INFO] Using 'UTF-8' encoding to copy filtered resources.
remote: [INFO] skip non existing resourceDirectory /var/lib/openshift/XXXXXXXXXX/app-root/runtime/repo/src/test/resources
remote: [INFO] 
remote: [INFO] --- maven-compiler-plugin:2.3.2:testCompile (default-testCompile) @ test ---
remote: [INFO] No sources to compile
remote: [INFO] 
remote: [INFO] --- maven-surefire-plugin:2.10:test (default-test) @ test ---
remote: [INFO] Tests are skipped.
remote: [INFO] 
remote: [INFO] --- maven-war-plugin:2.3:war (default-war) @ test ---
remote: [INFO] Packaging webapp
remote: [INFO] Assembling webapp [test] in [/var/lib/openshift/XXXXXXXXXX/app-root/runtime/repo/target/test]
remote: [INFO] Processing war project
remote: [INFO] Copying webapp resources [/var/lib/openshift/XXXXXXXXXX/app-root/runtime/repo/src/main/webapp]
remote: [INFO] Webapp assembled in [341 msecs]
remote: [INFO] Building war: /var/lib/openshift/XXXXXXXXXX/app-root/runtime/repo/deployments/ROOT.war
remote: [INFO] ------------------------------------------------------------------------
remote: [INFO] BUILD SUCCESS
remote: [INFO] ------------------------------------------------------------------------
remote: [INFO] Total time: 8.365s
remote: [INFO] Finished at: Tue Aug 26 18:01:19 EDT 2014
remote: [INFO] Final Memory: 9M/113M
remote: [INFO] ------------------------------------------------------------------------
remote: Preparing build for deployment
remote: Deployment id is 336d5b75
remote: Activating deployment
remote: Deploying WildFly
remote: Starting wildfly cart
remote: Found 127.12.40.129:8080 listening port
remote: Found 127.12.40.129:9990 listening port
remote: /var/lib/openshift/XXXXXXXXXX/wildfly/standalone/deployments /var/lib/openshift/XXXXXXXXXX/wildfly
remote: /var/lib/openshift/XXXXXXXXXX/wildfly
remote: CLIENT_MESSAGE: Artifacts deployed: ./ROOT.war
remote: -------------------------
remote: Git Post-Receive Result: success
remote: Activation status: success
remote: Deployment completed with status: success
To ssh://XXXXXXXXXX@test-milestogo.rhcloud.com/~/git/test.git/
   b08ebff..cef567d  master -&gt; master

Counting objects: 9, done.

Delta compression using up to 8 threads.

Compressing objects: 100% (5/5), done.

Writing objects: 100% (5/5), 656 bytes | 0 bytes/s, done.

Total 5 (delta 1), reused 0 (delta 0)

remote: Stopping wildfly cart

remote: Repairing links for 1 deployments

remote: Building git ref 'master', commit cef567d

remote: Found pom.xml... attempting to build with 'mvn -e clean package -Popenshift -DskipTests'

remote: Apache Maven 3.0.4 (r1232336; 2012-12-18 14:36:37-0500)

remote: Maven home: /usr/share/java/apache-maven-3.0.4

remote: Java version: 1.8.0_05, vendor: Oracle Corporation

remote: Java home: /var/lib/openshift/XXXXXXXXXX/wildfly/usr/lib/jvm/jdk1.8.0_05/jre

remote: Default locale: en_US, platform encoding: ANSI_X3.4-1968

remote: OS name: "linux", version: "2.6.32-431.23.3.el6.x86_64", arch: "i386", family: "unix"

remote: [INFO] Scanning for projects...

remote: [INFO]

remote: [INFO] ------------------------------------------------------------------------

remote: [INFO] Building test 1.0

remote: [INFO] ------------------------------------------------------------------------

remote: [INFO]

remote: [INFO] --- maven-clean-plugin:2.4.1:clean (default-clean) @ test ---

remote: [INFO]

remote: [INFO] --- maven-resources-plugin:2.5:resources (default-resources) @ test ---

remote: [debug] execute contextualize

remote: [INFO] Using 'UTF-8' encoding to copy filtered resources.

remote: [INFO] Copying 1 resource

remote: [INFO]

remote: [INFO] --- maven-compiler-plugin:2.3.2:compile (default-compile) @ test ---

remote: [INFO] Nothing to compile - all classes are up to date

remote: [INFO]

remote: [INFO] --- maven-resources-plugin:2.5:testResources (default-testResources) @ test ---

remote: [debug] execute contextualize

remote: [INFO] Using 'UTF-8' encoding to copy filtered resources.

remote: [INFO] skip non existing resourceDirectory /var/lib/openshift/XXXXXXXXXX/app-root/runtime/repo/src/test/resources

remote: [INFO]

remote: [INFO] --- maven-compiler-plugin:2.3.2:testCompile (default-testCompile) @ test ---

remote: [INFO] No sources to compile

remote: [INFO]

remote: [INFO] --- maven-surefire-plugin:2.10:test (default-test) @ test ---

remote: [INFO] Tests are skipped.

remote: [INFO]

remote: [INFO] --- maven-war-plugin:2.3:war (default-war) @ test ---

remote: [INFO] Packaging webapp

remote: [INFO] Assembling webapp [test] in [/var/lib/openshift/XXXXXXXXXX/app-root/runtime/repo/target/test]

remote: [INFO] Processing war project

remote: [INFO] Copying webapp resources [/var/lib/openshift/XXXXXXXXXX/app-root/runtime/repo/src/main/webapp]

remote: [INFO] Webapp assembled in [341 msecs]

remote: [INFO] Building war: /var/lib/openshift/XXXXXXXXXX/app-root/runtime/repo/deployments/ROOT.war

remote: [INFO] ------------------------------------------------------------------------

remote: [INFO] BUILD SUCCESS

remote: [INFO] ------------------------------------------------------------------------

remote: [INFO] Total time: 8.365s

remote: [INFO] Finished at: Tue Aug 26 18:01:19 EDT 2014

remote: [INFO] Final Memory: 9M/113M

remote: [INFO] ------------------------------------------------------------------------

remote: Preparing build for deployment

remote: Deployment id is 336d5b75

remote: Activating deployment

remote: Deploying WildFly

remote: Starting wildfly cart

remote: Found 127.12.40.129:8080 listening port

remote: Found 127.12.40.129:9990 listening port

remote: /var/lib/openshift/XXXXXXXXXX/wildfly/standalone/deployments /var/lib/openshift/XXXXXXXXXX/wildfly

remote: /var/lib/openshift/XXXXXXXXXX/wildfly

remote: CLIENT_MESSAGE: Artifacts deployed: ./ROOT.war

remote: -------------------------

remote: Git Post-Receive Result: success

remote: Activation status: success

remote: Deployment completed with status: success

To ssh://XXXXXXXXXX@test-milestogo.rhcloud.com/~/git/test.git/

b08ebff..cef567d master -> master

Now the WildFly instance in OpenShift will use the updated configuration file.

You can even verify this by logging into your application as:

ssh XXXXXXXXXX@test-milestogo.rhcloud.com

ssh XXXXXXXXXX@test-milestogo.rhcloud.com

And checking for the updated elements in wildfly/standalone/configuration/standalone.xml file.

Alternatively, you can ssh into your instance and use the JBoss CLI to make updates to your standalone.xml file.

Enjoy!

Cloud in a Box: OpenShift Online in VirtualBox (Tech Tip #46)

August 25, 2014redhatopenshiftarungupta

OpenShift is Red Hat’s PaaS platform and comes in three flavors:

Origin is the Community PaaS offering. You can explore the community-driven open source upstream of OpenShift. Join the community.
Online is the Public PaaS offering. Host your applications in the public cloud with automated provisioning, management, and scaling of applications. Sign up for free.
Enterprise is the Private PaaS offering. Leverage PaaS in your own data centers and private cloud. Request evaluation.

This Tech Tip will show how you can setup a Virtual VM running with OpenShift Online. Instructions at openshift.github.io/documentation/oo_deployment_guide_vm.html are pretty self explanatory. Here are the exact ones that I followed on Mavericks:

Download VM:

curl -O https://mirror.openshift.com/pub/origin-server/release/4/images/openshift-origin.tgz

curl -O https://mirror.openshift.com/pub/origin-server/release/4/images/openshift-origin.tgz

Unpack VM files

tar xzvf ~/Downloads/openshift-origin.tgz 
x OpenShift Origin v4/
x OpenShift Origin v4/OpenShift Origin v4.nvram
x OpenShift Origin v4/OpenShift Origin v4.vbox
x OpenShift Origin v4/OpenShift Origin v4.vmsd
x OpenShift Origin v4/OpenShift Origin v4.vmx
x OpenShift Origin v4/OpenShift Origin v4.vmxf
x OpenShift Origin v4/._origin-vm.vmdk
x OpenShift Origin v4/origin-vm.vmdk

tar xzvf ~/Downloads/openshift-origin.tgz

x OpenShift Origin v4/

x OpenShift Origin v4/OpenShift Origin v4.nvram

x OpenShift Origin v4/OpenShift Origin v4.vbox

x OpenShift Origin v4/OpenShift Origin v4.vmsd

x OpenShift Origin v4/OpenShift Origin v4.vmx

x OpenShift Origin v4/OpenShift Origin v4.vmxf

x OpenShift Origin v4/._origin-vm.vmdk

x OpenShift Origin v4/origin-vm.vmdk

Follow the instructions to create a VirtualBox instance. Create a new hard drive using the unzipped origin-vm.vmdk file.
IMPORTANT: Instead of 4.2.4 to add bridged networking, setup a host-only network using 4.2.5.
Boot the VM to see the output as:

Type “5” to exit to the command prompt.
VM comes pre-configured with Avahi DNS service and so now you can access OpenShift console at broker.openshift.local and seen as:

The username/password are “demo”/”changeme”.

Create an SSH tunnel into the VM as:

ssh -f <a class="moz-txt-link-abbreviated" href="mailto:root@broker.openshift.local">root@broker.openshift.local</a> -L 8080:localhost:8080 -N

ssh -f <a class="moz-txt-link-abbreviated" href="mailto:root@broker.openshift.local">root@broker.openshift.local</a> -L 8080:localhost:8080 -N

Password is “changeme”. OpenShift admin console is now accessible at localhost:8080/admin-console and looks like:

More details about Admin Console are well documented.

Many thanks to Harrison for guiding me through creating this process!

Ask your OpenShift questions at stackoverflow or follow them at @openshift.

Enjoy!

Java EE 6 Sample, with HTML5, jQuery, Hybrid mobile: aka Ticket Monster (Tech Tip #44)

August 21, 2014javaee, jboss, techtipjavaee, openshiftarungupta

Java EE 7 was released last year, Java EE 8 preparations have already started, so what tempts me to write a blog about Java EE 6 ?

A few reasons …

Even though Java EE 5 was the first version where some of the specs were updated to simplify the platform, Java EE 6 is where higher productivity became the primary focus and kicked into high gear.
All commercially available application servers are still Java EE 6 compliant.
Java EE 7 is pretty cool and provide an awesome bunch of new technologies like WebSocket, Batch, JSON, and Concurrency. But customers are still sticking around with older version of the platform because these applications, servers, and environments cannot change overnight.

So if you are looking for a real-world Java EE 6 sample application that:

Use Eclipse for building a Java EE 6 application
Build persistence layer with JPA2 and Bean Validation
Build business services with JAX-RS
Building the User Interface with HTML5
Building Administration UI with JBoss Forge
Building statistics dashboard using HTML5 and JavaScript
Hybrid mobile version of the app using Apache Cordova

In addition, it also shows:

Deploy your application on a local instance or a remote instance running in OpenShift
Run tests against your JBoss instance

Ticket Monster is your ultimate source. It not only shows how the key Java EE 6 technologies can be used together but also integrate jQuery, HTML5, and mobile version of the application as well.

The video below gives a quick preview of the application:

An instance of Ticket Monster can be previewed at ticketmonster-jdf.rhcloud.com or timo-milestogo.rhcloud.com.

So how do you get started ?

Download Ticket Monster 2.6.0 (with tutorials). Corresponding source code is at github.com/jboss-developer/ticket-monster/tree/2.6.0.Final-with-tutorials.
Set up Red Hat Maven repositories as explained here. If you don’t care reading through the instructions, overwrite .m2/settings.xml with this settings.xml.

Build the WAR of your application

mvn clean package

mvn clean package

To run on local JBoss instance:

Download JBoss EAP 6.3

Unzip and start as

./bin/standalone.sh

./bin/standalone.sh

Deploy the application as

mvn package jboss-as:deploy

mvn package jboss-as:deploy

This will also build the application again.

The application is now accessible at localhost:8080/ticket-monster.

To run on JBoss instance in OpenShift

Create a JBoss EAP 6 application in OpenShift
Add PostgreSQL cartridge for this application

Create an archive as

mvn clean package -Ppostgresql-openshift

mvn clean package -Ppostgresql-openshift

This will use the installed PostgreSQL cartridge for persistence.

Clone the git workspace from OpenShift

git clone ssh://XXXXXXXXXXXXXX@timo-milestogo.rhcloud.com/~/git/timo.git/

git clone ssh://XXXXXXXXXXXXXX@timo-milestogo.rhcloud.com/~/git/timo.git/

The actual git url will be specific to your application.

Copy generated WAR file to git workspace and rename to ROOT.war

cp target/ticket-monster.war &lt;openshift-git-workspace&gt;/deployments/ROOT.war

cp target/ticket-monster.war <openshift-git-workspace>/deployments/ROOT.war

Remove existing source and pom.xml from git workspace, add WAR, and push

git rm -rf src
git rm pom.xml
git add deployments/ROOT.war
git commit . -m"deploying TicketMonster"
git push

git rm -rf src

git rm pom.xml

git add deployments/ROOT.war

git commit . -m"deploying TicketMonster"

git push

Access the application at htp://<appname-domainname>.rhcloud.com.The following video shows the steps for running TicketMonster on OpenShift:

Ask your questions about Ticket Monster at jbossdeveloper@lists.jboss.org.
Enjoy!

Java EE 7 Hands-on Lab on WildFly and OpenShift (Tech Tip #33)

June 25, 2014javaee, techtip, wildflyopenshift, wildflyarungupta

Thanks to @dmueller for inspiring this blog entry and @FarahJuma for keeping WildFly cartridge continuously updated!

Java EE 7 hands-on lab has been delivered at several conferences, meetups, Java User Groups, and other venues around the world. It provides instructions for a typical 3-tier application using several technologies in the Java EE 7 platform, such as WebSocket 1.0 (JSR 356), Batch Applications (JSR 352), JSON-P 1.0 (JSR 353), JAX-RS 2.0 (JSR 339), JMS 2.0 (JSR 343), CDI 1.1 (JSR 346), JPA 2.1 (JSR 338), and many more. The self-paced instructions allows the attendees to learn the design patterns in Java EE 7, and be productive right away.

This lab can be built using NetBeans, JBoss Tools/Eclipse, or IntelliJ. The deployment can be done on WildFly or GlassFish.

Do you want to get a taste of the application without trying out all the steps ? You can download the solution and deploy on application server of your choice.

Don’t have time for downloading and installing your application server ? OpenShift is your answer!

OpenShift provides an open source hybrid cloud application platform by Red Hat. It enables polyglot applications to be deployed on a public, private, and a hybrid cloud very easily. It provides an extensible cartridge-based architecture that allows a wide range of functionality such as frameworks, databases, monitoring services, or connectors to external backends to be easily added. WildFly cartridge allows you to start a WildFly instance in OpenShift Online.

This Tech Tip shows how to deploy Java EE 7 hands-on lab solution easily on WildFly cartridge on OpenShift.

Register for a free OpenShift account.
Login to OpenShift Console.
Create a new WildFly application using the quickstart. Take the defaults, or change the name to whatever you want, and click on “Create Application”. The following page is shown:The default application page looks like:
Clone the workspace using the credentials shown for your application.

Delete the generated “src” directory and copy the “src” from solution.

javaee7lab&gt; <strong>git rm -rf src</strong>
rm 'src/main/java/.gitkeep'
rm 'src/main/resources/.gitkeep'
rm 'src/main/webapp/images/jbosscorp_logo.png'
rm 'src/main/webapp/index.html'
rm 'src/main/webapp/snoop.jsp'
javaee7lab&gt; <strong>cp -r ~/Downloads/movieplex7/src .</strong>

javaee7lab> git rm -rf src

rm 'src/main/java/.gitkeep'

rm 'src/main/resources/.gitkeep'

rm 'src/main/webapp/images/jbosscorp_logo.png'

rm 'src/main/webapp/index.html'

rm 'src/main/webapp/snoop.jsp'

javaee7lab> cp -r ~/Downloads/movieplex7/src .

Commit and push the changes to restart the cartridge:

javaee7lab&gt; <strong>git add src</strong>
javaee7lab&gt; <strong>git commit src -m"updating source directory with Java EE 7 lab contents"</strong>
[master f6f24ec] updating source directory with Java EE 7 lab contents
 53 files changed, 3955 insertions(+), 584 deletions(-)
 delete mode 100644 src/main/java/.gitkeep
 create mode 100644 src/main/java/org/javaee7/movieplex7/batch/SalesBean.java
 create mode 100644 src/main/java/org/javaee7/movieplex7/batch/SalesProcessor.java
 . . .

 create mode 100644 src/main/webapp/chat/websocket.js
 create mode 100644 src/main/webapp/client/addmovie.xhtml
 create mode 100644 src/main/webapp/client/movie.xhtml
 create mode 100644 src/main/webapp/client/movies.xhtml
 delete mode 100644 src/main/webapp/images/jbosscorp_logo.png
 delete mode 100644 src/main/webapp/index.html
 create mode 100644 src/main/webapp/index.xhtml
 create mode 100644 src/main/webapp/points/points.xhtml
 create mode 100644 src/main/webapp/resources/css/cssLayout.css
 create mode 100644 src/main/webapp/resources/css/default.css
 delete mode 100644 src/main/webapp/snoop.jsp
javaee7lab&gt; <strong>git push</strong>
warning: push.default is unset; its implicit value is changing in
Git 2.0 from 'matching' to 'simple'. To squelch this message
and maintain the current behavior after the default changes, use:

  git config --global push.default matching

To squelch this message and adopt the new behavior now, use:

  git config --global push.default simple

See 'git help config' and search for 'push.default' for further information.
(the 'simple' mode was introduced in Git 1.7.11. Use the similar mode
'current' instead of 'simple' if you sometimes use older versions of Git)

Counting objects: 81, done.
Delta compression using up to 8 threads.
Compressing objects: 100% (65/65), done.
Writing objects: 100% (76/76), 25.06 KiB | 0 bytes/s, done.
Total 76 (delta 38), reused 0 (delta 0)
remote: Stopping wildfly cart
remote: Sending SIGTERM to wildfly:146819 ...
remote: Building git ref 'master', commit f6f24ec
remote: Found pom.xml... attempting to build with 'mvn -e clean package -Popenshift -DskipTests'
remote: Apache Maven 3.0.4 (r1232336; 2012-12-18 14:36:37-0500)
remote: Maven home: /usr/share/java/apache-maven-3.0.4
remote: Java version: 1.7.0_55, vendor: Oracle Corporation
remote: Java home: /usr/lib/jvm/java-1.7.0-openjdk-1.7.0.55/jre
remote: Default locale: en_US, platform encoding: ANSI_X3.4-1968
remote: OS name: "linux", version: "2.6.32-431.20.3.el6.x86_64", arch: "i386", family: "unix"
remote: [INFO] Scanning for projects...
remote: [INFO]                                                                         
remote: [INFO] ------------------------------------------------------------------------
remote: [INFO] Building javaee7lab 1.0
remote: [INFO] ------------------------------------------------------------------------
remote: Downloading: http://mirror1.ops.rhcloud.com/nexus/content/groups/public/org/apache/maven/plugins/maven-clean-plugin/2.4.1/maven-clean-plugin-2.4.1.pom
. . .

remote: Downloaded: http://mirror1.ops.rhcloud.com/nexus/content/groups/public/xpp3/xpp3_min/1.1.4c/xpp3_min-1.1.4c.jar (25 KB at 204.8 KB/sec)
remote: Downloaded: http://mirror1.ops.rhcloud.com/nexus/content/groups/public/org/codehaus/plexus/plexus-utils/3.0.8/plexus-utils-3.0.8.jar (227 KB at 2077.0 KB/sec)
remote: [INFO] Packaging webapp
remote: [INFO] Assembling webapp [javaee7lab] in [/var/lib/openshift/53ab65bee0b8cdf9d1000354/app-root/runtime/repo/target/javaee7lab]
remote: [INFO] Processing war project
remote: [INFO] Copying webapp resources [/var/lib/openshift/53ab65bee0b8cdf9d1000354/app-root/runtime/repo/src/main/webapp]
remote: [INFO] Webapp assembled in [508 msecs]
remote: [INFO] Building war: /var/lib/openshift/53ab65bee0b8cdf9d1000354/app-root/runtime/repo/deployments/ROOT.war
remote: [INFO] ------------------------------------------------------------------------
remote: [INFO] BUILD SUCCESS
remote: [INFO] ------------------------------------------------------------------------
remote: [INFO] Total time: 51.727s
remote: [INFO] Finished at: Wed Jun 25 22:23:46 EDT 2014
remote: [INFO] Final Memory: 10M/152M
remote: [INFO] ------------------------------------------------------------------------
remote: Preparing build for deployment
remote: Deployment id is 026b1012
remote: Activating deployment
remote: Deploying WildFly
remote: Starting wildfly cart
remote: Found 127.11.132.129:8080 listening port
remote: Found 127.11.132.129:9990 listening port
remote: CLIENT_MESSAGE: Could not connect to WildFly management interface, skipping deployment verification
remote: -------------------------
remote: Git Post-Receive Result: success
remote: Activation status: success
remote: Deployment completed with status: success
To ssh://53ab65bee0b8cdf9d1000354@javaee7lab-milestogo.rhcloud.com/~/git/javaee7lab.git/
   75b5640..f6f24ec  master -&gt; master

javaee7lab> git add src

javaee7lab> git commit src -m"updating source directory with Java EE 7 lab contents"

[master f6f24ec] updating source directory with Java EE 7 lab contents

53 files changed, 3955 insertions(+), 584 deletions(-)

delete mode 100644 src/main/java/.gitkeep

create mode 100644 src/main/java/org/javaee7/movieplex7/batch/SalesBean.java

create mode 100644 src/main/java/org/javaee7/movieplex7/batch/SalesProcessor.java

. . .

create mode 100644 src/main/webapp/chat/websocket.js

create mode 100644 src/main/webapp/client/addmovie.xhtml

create mode 100644 src/main/webapp/client/movie.xhtml

create mode 100644 src/main/webapp/client/movies.xhtml

delete mode 100644 src/main/webapp/images/jbosscorp_logo.png

delete mode 100644 src/main/webapp/index.html

create mode 100644 src/main/webapp/index.xhtml

create mode 100644 src/main/webapp/points/points.xhtml

create mode 100644 src/main/webapp/resources/css/cssLayout.css

create mode 100644 src/main/webapp/resources/css/default.css

delete mode 100644 src/main/webapp/snoop.jsp

javaee7lab> git push

warning: push.default is unset; its implicit value is changing in

Git 2.0 from 'matching' to 'simple'. To squelch this message

and maintain the current behavior after the default changes, use:

git config --global push.default matching

To squelch this message and adopt the new behavior now, use:

git config --global push.default simple

See 'git help config' and search for 'push.default' for further information.

(the 'simple' mode was introduced in Git 1.7.11. Use the similar mode

'current' instead of 'simple' if you sometimes use older versions of Git)

Counting objects: 81, done.

Delta compression using up to 8 threads.

Compressing objects: 100% (65/65), done.

Writing objects: 100% (76/76), 25.06 KiB | 0 bytes/s, done.

Total 76 (delta 38), reused 0 (delta 0)

remote: Stopping wildfly cart

remote: Sending SIGTERM to wildfly:146819 ...

remote: Building git ref 'master', commit f6f24ec

remote: Found pom.xml... attempting to build with 'mvn -e clean package -Popenshift -DskipTests'

remote: Apache Maven 3.0.4 (r1232336; 2012-12-18 14:36:37-0500)

remote: Maven home: /usr/share/java/apache-maven-3.0.4

remote: Java version: 1.7.0_55, vendor: Oracle Corporation

remote: Java home: /usr/lib/jvm/java-1.7.0-openjdk-1.7.0.55/jre

remote: Default locale: en_US, platform encoding: ANSI_X3.4-1968

remote: OS name: "linux", version: "2.6.32-431.20.3.el6.x86_64", arch: "i386", family: "unix"

remote: [INFO] Scanning for projects...

remote: [INFO]

remote: [INFO] ------------------------------------------------------------------------

remote: [INFO] Building javaee7lab 1.0

remote: [INFO] ------------------------------------------------------------------------

remote: Downloading: http://mirror1.ops.rhcloud.com/nexus/content/groups/public/org/apache/maven/plugins/maven-clean-plugin/2.4.1/maven-clean-plugin-2.4.1.pom

. . .

remote: Downloaded: http://mirror1.ops.rhcloud.com/nexus/content/groups/public/xpp3/xpp3_min/1.1.4c/xpp3_min-1.1.4c.jar (25 KB at 204.8 KB/sec)

remote: Downloaded: http://mirror1.ops.rhcloud.com/nexus/content/groups/public/org/codehaus/plexus/plexus-utils/3.0.8/plexus-utils-3.0.8.jar (227 KB at 2077.0 KB/sec)

remote: [INFO] Packaging webapp

remote: [INFO] Assembling webapp [javaee7lab] in [/var/lib/openshift/53ab65bee0b8cdf9d1000354/app-root/runtime/repo/target/javaee7lab]

remote: [INFO] Processing war project

remote: [INFO] Copying webapp resources [/var/lib/openshift/53ab65bee0b8cdf9d1000354/app-root/runtime/repo/src/main/webapp]

remote: [INFO] Webapp assembled in [508 msecs]

remote: [INFO] Building war: /var/lib/openshift/53ab65bee0b8cdf9d1000354/app-root/runtime/repo/deployments/ROOT.war

remote: [INFO] ------------------------------------------------------------------------

remote: [INFO] BUILD SUCCESS

remote: [INFO] ------------------------------------------------------------------------

remote: [INFO] Total time: 51.727s

remote: [INFO] Finished at: Wed Jun 25 22:23:46 EDT 2014

remote: [INFO] Final Memory: 10M/152M

remote: [INFO] ------------------------------------------------------------------------

remote: Preparing build for deployment

remote: Deployment id is 026b1012

remote: Activating deployment

remote: Deploying WildFly

remote: Starting wildfly cart

remote: Found 127.11.132.129:8080 listening port

remote: Found 127.11.132.129:9990 listening port

remote: CLIENT_MESSAGE: Could not connect to WildFly management interface, skipping deployment verification

remote: -------------------------

remote: Git Post-Receive Result: success

remote: Activation status: success

remote: Deployment completed with status: success

To ssh://53ab65bee0b8cdf9d1000354@javaee7lab-milestogo.rhcloud.com/~/git/javaee7lab.git/

75b5640..f6f24ec master -> master

Refreshing the page at javaee7lab-milestogo.rhcloud.com now shows the application deployed successfully:

techtip33-javaee7lab-default-output

Simple, isn’t it ?

Try it and let us know your feedback!

Tech Tip #21 also talks about how to get started with WildFly in OpenShift and JBoss Developer Studio.

Miles to go 4.0 …

Arun Gupta is a technology enthusiast, avid runner, author of a best-selling book, globe trotter, a community guy, Java Champion, JavaOne Rockstar, JUG Leader, Minecraft Modder, NetBeans Dream Teamer, Devoxx4Kids-er, Docker Captain and works at AWS.

Tag Archives: openshift

Couchbase Cloud Recipes – Pick your favorite!

Couchbase on OpenShift 3

Getting Started with OpenShift 3

Download and Configure OpenShift 3 Client

Create Couchbase Application in OpenShift 3

Query Couchbase Sample Bucket

WildFly 9 on NetBeans, Eclipse, IntelliJ, OpenShift, and Maven (Tech Tip #86)

WildFly 9 and NetBeans

WildFly 9 and Eclipse

WildFly 9 and IntelliJ

WildFly 9 and OpenShift

WildFly 9 and Maven

OpenShift v3: Getting Started with Java EE 7 using WildFly and MySQL (Tech Tip #73)

Getting Started with OpenShift v3

Configure Docker Daemon

Check out OpenShift v3 and Java EE 7 Sample

Start OpenShift v3 Container

Access OpenShift v3 Web Console

Create OpenShift v3 Project

Build the Project

Reactive HTML presentations using Reveal.js, Gist, and OpenShift (Tech Tip #69)

Java EE Workflows on OpenShift (Tech Tip #64)

Deployment Pipeline for Java EE 7 with WildFly, Arquillian, Jenkins, and OpenShift (Tech Tip #56)

Arquillian tests on a WildFly instance hosted on OpenShift (Tech Tip #55)

Slides from Nuts and Bolts of WebSocket at #Devoxx 2014

Create WildFly OpenShift application using Command Line Tools (Tech Tip #52)

WebSocket Chat on WildFly and OpenShift (Tech Tip #51)

WildFly with a custom configuration in OpenShift (Tech Tip #47)

Cloud in a Box: OpenShift Online in VirtualBox (Tech Tip #46)

Java EE 6 Sample, with HTML5, jQuery, Hybrid mobile: aka Ticket Monster (Tech Tip #44)

Java EE 7 Hands-on Lab on WildFly and OpenShift (Tech Tip #33)