Yearly Archives: 2015

JBoss EAP 7 and NoSQL using Java EE and Docker

December 21, 2015containers, couchbase, javaee, jboss, redhatcouchbase, docker, javaee7, jboss, nosqlarungupta

JBoss EAP 7 Beta is now released, many congratulations to Red Hat and particularly to the WildFly team!

There are plenty of improvements coming in this release as documented in Release Notes. One of the major themes is Java EE 7 compliance.

JBoss EAP 7 and Java EE 7

IBM and Oracle already provide commercially supported Java EE 7-compliant Application Servers. And now Red Hat will be joining this party soon as well. Although WildFly has supported Java EE 7 for 2+ years but commercial support is a critical for open source to be adopted enterprise-wide. So this is good news!

You can learn all about different Java EE 7 APIs in the DZone Refcardz that I authored along with @alrubinger.

Java EE 7 Refcardz

There are plenty of “hello world” Java EE 7 Samples that should all run with JBoss EAP. Hopefully somebody will update the pom.xml and add a new profile.

Why NoSQL?

If you are building a traditional enterprise application then you might be fine using an RDBMS. There are plenty of advantages of using RDBMS but using a NoSQL database instead has a few advantages:

No need to have a pre-defined schema and that makes them a schema-less database. Addition of new properties to existing objects is easy and does not require ALTER TABLE. The unstructured data gives flexibility to change the format of data any time without downtime or reduced service levels. Also there are no joins happening on the server because there is no structure and thus no relation between them.
Scalability, agility and performance is more important than the entire set of functionality typically provided by an RDBMS. This set of databases provide eventual consistency and/or transactions restricted to single items but more focus on CRUD.
NoSQL are designed to scale-out (horizontal) instead of scale-up (vertical). This is important knowing that databases, and everything else as well, is moving into the cloud. RBDMS can scale-out using sharding but requires complex management and not for the faint of heart. Queries requiring JOINs across shards is extremely inefficient.
RDBMS have impedance mismatch between the database structure and the domain classes. An Object Relational Mapping, such as one provided by Java Persistence API or Hibernate is needed in such case.
NoSQL databases are designed for less management and simpler data models lead to lower administration cost as well.

So you are all excited about NoSQL now and want to learn more:

Why NoSQL?
Why do successful enterprises rely on NoSQL?
Top 10 Enterprise NoSQL Usecases

In short, there are four different types of NoSQL databases:

Document: Couchbase, Mongo, and others
Key/Value: Couchbase, Redis, and others
Graph: Neo4J, OrientDB, and others
Column: Cassandra and others

Java EE 7 provides Java Persistence API that does not provide any support for NoSQL. So how do you get started with NoSQL with JBoss EAP 7?

This blog will show how to query a Couchbase database using simple Java EE application deployed on JBoss EAP 7 Beta.

What is Couchbase?

Couchbase is an open-source, NoSQL, document database. It allows to access, index, and query JSON documents while taking advantage of integrated distributed caching for high performance data access.

Developers can write applications to Couchbase using different languages (Java, Go, .NET, Node, PHP, Python, C) multiple SDKs. This blog will show how you can easily create a CRUD application using Java SDK for Couchbase.

Run JBoss EAP 7

There are two ways to start JBoss EAP 7.

Download and Run

Download JBoss EAP 7 Beta and unzip.

Start the application server as:

./jboss-eap-7.0/bin/standalone.sh 
=========================================================================

  JBoss Bootstrap Environment

  JBOSS_HOME: /Users/arungupta/tools/jboss-eap-7.0

  JAVA: java

  JAVA_OPTS:  -server -verbose:gc -Xloggc:"/Users/arungupta/tools/jboss-eap-7.0/standalone/log/gc.log" -XX:+PrintGCDetails -XX:+PrintGCDateStamps -XX:+UseGCLogFileRotation -XX:NumberOfGCLogFiles=5 -XX:GCLogFileSize=3M -XX:-TraceClassUnloading -Xms1303m -Xmx1303m -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true

=========================================================================

21:22:58,773 INFO  [org.jboss.modules] (main) JBoss Modules version 1.4.4.Final-redhat-1

. . .

21:23:21,441 INFO  [org.jboss.as] (Controller Boot Thread) WFLYSRV0060: Http management interface listening on http://127.0.0.1:9990/management
21:23:21,442 INFO  [org.jboss.as] (Controller Boot Thread) WFLYSRV0051: Admin console listening on http://127.0.0.1:9990
21:23:21,442 INFO  [org.jboss.as] (Controller Boot Thread) WFLYSRV0025: EAP 7.0.0.Beta1 (WildFly Core 2.0.3.Final-redhat-1) started in 22950ms - Started 261 of 509 services (332 services are lazy, passive or on-demand)

./jboss-eap-7.0/bin/standalone.sh

=========================================================================

JBoss Bootstrap Environment

JBOSS_HOME: /Users/arungupta/tools/jboss-eap-7.0

JAVA: java

JAVA_OPTS: -server -verbose:gc -Xloggc:"/Users/arungupta/tools/jboss-eap-7.0/standalone/log/gc.log" -XX:+PrintGCDetails -XX:+PrintGCDateStamps -XX:+UseGCLogFileRotation -XX:NumberOfGCLogFiles=5 -XX:GCLogFileSize=3M -XX:-TraceClassUnloading -Xms1303m -Xmx1303m -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true

=========================================================================

21:22:58,773 INFO [org.jboss.modules] (main) JBoss Modules version 1.4.4.Final-redhat-1

. . .

21:23:21,441 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0060: Http management interface listening on http://127.0.0.1:9990/management

21:23:21,442 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0051: Admin console listening on http://127.0.0.1:9990

21:23:21,442 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0025: EAP 7.0.0.Beta1 (WildFly Core 2.0.3.Final-redhat-1) started in 22950ms - Started 261 of 509 services (332 services are lazy, passive or on-demand)

Docker Run

In a containerized world, you just docker run to run your JBoss EAP. However, JBoss EAP image does not exist on Docker Hub and so the image needs to be explicitly built. You still need to explicitly download JBoss EAP and then use the following Dockerfile to build the image:

# Use latest jboss/base-jdk:8 image as the base
FROM jboss/base-jdk:8

# Set the JBOSS_VERSION env variable
ENV JBOSS_VERSION 7.0.0.Beta
ENV JBOSS_HOME /opt/jboss/jboss-eap-7.0/

COPY jboss-eap-$JBOSS_VERSION.zip $HOME

# Add the JBoss distribution to /opt, and make jboss the owner of the extracted zip content
# Make sure the distribution is available from a well-known place
RUN cd $HOME \
    && unzip jboss-eap-$JBOSS_VERSION.zip \
    && rm jboss-eap-$JBOSS_VERSION.zip

# Ensure signals are forwarded to the JVM process correctly for graceful shutdown
ENV LAUNCH_JBOSS_IN_BACKGROUND true

# Expose the ports we're interested in
EXPOSE 8080 9990

# Set the default command to run on boot
# This will boot JBoss EAP in the standalone mode and bind to all interface
CMD ["/opt/jboss/jboss-eap-7.0/bin/standalone.sh", "-b", "0.0.0.0", "-bmanagement", "0.0.0.0"]

# Use latest jboss/base-jdk:8 image as the base

FROM jboss/base-jdk:8

# Set the JBOSS_VERSION env variable

ENV JBOSS_VERSION 7.0.0.Beta

ENV JBOSS_HOME /opt/jboss/jboss-eap-7.0/

COPY jboss-eap-$JBOSS_VERSION.zip $HOME

# Add the JBoss distribution to /opt, and make jboss the owner of the extracted zip content

# Make sure the distribution is available from a well-known place

RUN cd $HOME \

&& unzip jboss-eap-$JBOSS_VERSION.zip \

&& rm jboss-eap-$JBOSS_VERSION.zip

# Ensure signals are forwarded to the JVM process correctly for graceful shutdown

ENV LAUNCH_JBOSS_IN_BACKGROUND true

# Expose the ports we're interested in

EXPOSE 8080 9990

# Set the default command to run on boot

# This will boot JBoss EAP in the standalone mode and bind to all interface

CMD ["/opt/jboss/jboss-eap-7.0/bin/standalone.sh", "-b", "0.0.0.0", "-bmanagement", "0.0.0.0"]

The image is built as:

docker build -t arungupta/jboss-eap:7-beta .

docker build -t arungupta/jboss-eap:7-beta .

And then you can run the JBoss EAP 7 container as:

docker run -it -p 8080:8080 arungupta/jboss-eap:7-beta
=========================================================================

  JBoss Bootstrap Environment

  JBOSS_HOME: /opt/jboss/jboss-eap-7.0/

  JAVA: /usr/lib/jvm/java/bin/java

  JAVA_OPTS:  -server -verbose:gc -Xloggc:"/opt/jboss/jboss-eap-7.0//standalone/log/gc.log" -XX:+PrintGCDetails -XX:+PrintGCDateStamps -XX:+UseGCLogFileRotation -XX:NumberOfGCLogFiles=5 -XX:GCLogFileSize=3M -XX:-TraceClassUnloading -Xms1303m -Xmx1303m -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true

=========================================================================

20:51:12,551 INFO  [org.jboss.modules] (main) JBoss Modules version 1.4.4.Final-redhat-1
20:51:12,824 INFO  [org.jboss.msc] (main) JBoss MSC version 1.2.6.Final-redhat-1

. . .

20:51:16,750 INFO  [org.jboss.as] (Controller Boot Thread) WFLYSRV0060: Http management interface listening on http://0.0.0.0:9990/management
20:51:16,758 INFO  [org.jboss.as] (Controller Boot Thread) WFLYSRV0051: Admin console listening on http://0.0.0.0:9990
20:51:16,759 INFO  [org.jboss.as] (Controller Boot Thread) WFLYSRV0025: EAP 7.0.0.Beta1 (WildFly Core 2.0.3.Final-redhat-1) started in 4529ms - Started 261 of 509 services (332 services are lazy, passive or on-demand)

docker run -it -p 8080:8080 arungupta/jboss-eap:7-beta

=========================================================================

JBoss Bootstrap Environment

JBOSS_HOME: /opt/jboss/jboss-eap-7.0/

JAVA: /usr/lib/jvm/java/bin/java

JAVA_OPTS: -server -verbose:gc -Xloggc:"/opt/jboss/jboss-eap-7.0//standalone/log/gc.log" -XX:+PrintGCDetails -XX:+PrintGCDateStamps -XX:+UseGCLogFileRotation -XX:NumberOfGCLogFiles=5 -XX:GCLogFileSize=3M -XX:-TraceClassUnloading -Xms1303m -Xmx1303m -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true

=========================================================================

20:51:12,551 INFO [org.jboss.modules] (main) JBoss Modules version 1.4.4.Final-redhat-1

20:51:12,824 INFO [org.jboss.msc] (main) JBoss MSC version 1.2.6.Final-redhat-1

. . .

20:51:16,750 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0060: Http management interface listening on http://0.0.0.0:9990/management

20:51:16,758 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0051: Admin console listening on http://0.0.0.0:9990

20:51:16,759 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0025: EAP 7.0.0.Beta1 (WildFly Core 2.0.3.Final-redhat-1) started in 4529ms - Started 261 of 509 services (332 services are lazy, passive or on-demand)

Notice, how application and management ports are bound to all network interfaces. This will simplify to deploy the application to this JBoss EAP instance later.

Stop the server as we will show an easier way to start it later.

Start Application Server and Database

The Java EE application will provide a HTTP CRUD interface over JSON documents stored in Couchbase. The application itself will be deployed on JBoss EAP 7 Beta. So it would require to start Couchbase and JBoss EAP.

Use the Docker Compose file from github.com/arun-gupta/docker-images/blob/master/jboss-eap7-nosql/docker-compose.yml to start Couchbase and JBoss EAP 7 container:

mycouchbase:
  container_name: "db"
  image: couchbase/server
  ports:
    - 8091:8091
    - 8092:8092 
    - 8093:8093 
    - 11210:11210
jboss:
  image: arungupta/jboss-eap:7-beta
  environment:
    - COUCHBASE_URI=db
  ports:
    - 8080:8080
    - 9990:9990

mycouchbase:

container_name: "db"

image: couchbase/server

ports:

- 8091:8091

- 8092:8092

- 8093:8093

- 11210:11210

jboss:

image: arungupta/jboss-eap:7-beta

environment:

- COUCHBASE_URI=db

ports:

- 8080:8080

- 9990:9990

The application is started as:

docker-compose --x-networking up -d
Creating network "jbosseap7nosql" with driver "None"
Starting jbosseap7nosql_jboss_1
Creating db

docker-compose --x-networking up -d

Creating network "jbosseap7nosql" with driver "None"

Starting jbosseap7nosql_jboss_1

Creating db

The started containers can be seen as:

docker ps
CONTAINER ID        IMAGE                        COMMAND                  CREATED             STATUS              PORTS                                                                                               NAMES
154436dfbfb1        couchbase/server             "/entrypoint.sh couch"   10 seconds ago      Up 8 seconds        0.0.0.0:8091-8093->8091-8093/tcp, 11207/tcp, 11211/tcp, 18091-18092/tcp, 0.0.0.0:11210->11210/tcp   db
cb76d4e38df3        arungupta/jboss-eap:7-beta   "/opt/jboss/jboss-eap"   10 seconds ago      Up 9 seconds        0.0.0.0:8080->8080/tcp, 0.0.0.0:9990->9990/tcp                                                      jbosseap7nosql_jboss_1

docker ps

CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES

154436dfbfb1 couchbase/server "/entrypoint.sh couch" 10 seconds ago Up 8 seconds 0.0.0.0:8091-8093->8091-8093/tcp, 11207/tcp, 11211/tcp, 18091-18092/tcp, 0.0.0.0:11210->11210/tcp db

cb76d4e38df3 arungupta/jboss-eap:7-beta "/opt/jboss/jboss-eap" 10 seconds ago Up 9 seconds 0.0.0.0:8080->8080/tcp, 0.0.0.0:9990->9990/tcp jbosseap7nosql_jboss_1

Configure Couchbase Server

Clone couchbase-javaee application. This Java EE application uses Couchbase Java SDK APIs to connect to the Couchbase server. The bootstrap code is:

CouchbaseCluster.create(System.getenv("COUCHBASE_URI"));

CouchbaseCluster.create(System.getenv("COUCHBASE_URI"));

and is invoked from Database abstraction.

Couchbase Server can be configured using REST API. These REST APIs are defined in a Maven profile in pom.xml of this application. And so configure Couchbase server as:

mvn install -Pcouchbase -Ddocker.host=$(docker-machine ip couchbase)
[INFO] Scanning for projects...
[INFO]                                                                         
[INFO] ------------------------------------------------------------------------
[INFO] Building couchbase-javaee 1.0-SNAPSHOT
[INFO] ------------------------------------------------------------------------
[INFO] 
[INFO] --- maven-resources-plugin:2.6:resources (default-resources) @ couchbase-javaee ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 0 resource
[INFO] 
[INFO] --- maven-compiler-plugin:2.3.2:compile (default-compile) @ couchbase-javaee ---
[INFO] Nothing to compile - all classes are up to date
[INFO] 
[INFO] --- maven-resources-plugin:2.6:testResources (default-testResources) @ couchbase-javaee ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory /Users/arungupta/workspaces/couchbase-javaee/src/test/resources
[INFO] 
[INFO] --- maven-compiler-plugin:2.3.2:testCompile (default-testCompile) @ couchbase-javaee ---
[INFO] Nothing to compile - all classes are up to date
[INFO] 
[INFO] --- maven-surefire-plugin:2.12.4:test (default-test) @ couchbase-javaee ---
[INFO] 
[INFO] --- maven-war-plugin:2.1.1:war (default-war) @ couchbase-javaee ---
[INFO] Packaging webapp
[INFO] Assembling webapp [couchbase-javaee] in [/Users/arungupta/workspaces/couchbase-javaee/target/couchbase-javaee]
[INFO] Processing war project
[INFO] Copying webapp resources [/Users/arungupta/workspaces/couchbase-javaee/src/main/webapp]
[INFO] Webapp assembled in [82 msecs]
[INFO] Building war: /Users/arungupta/workspaces/couchbase-javaee/target/couchbase-javaee.war
[INFO] 
[INFO] --- maven-install-plugin:2.4:install (default-install) @ couchbase-javaee ---
[INFO] Installing /Users/arungupta/workspaces/couchbase-javaee/target/couchbase-javaee.war to /Users/arungupta/.m2/repository/org/couchbase/sample/couchbase-javaee/1.0-SNAPSHOT/couchbase-javaee-1.0-SNAPSHOT.war
[INFO] Installing /Users/arungupta/workspaces/couchbase-javaee/pom.xml to /Users/arungupta/.m2/repository/org/couchbase/sample/couchbase-javaee/1.0-SNAPSHOT/couchbase-javaee-1.0-SNAPSHOT.pom
[INFO] 
[INFO] --- exec-maven-plugin:1.4.0:exec (Configure memory) @ couchbase-javaee ---
* Hostname was NOT found in DNS cache
*   Trying 192.168.99.102...
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0* Connected to 192.168.99.102 (192.168.99.102) port 8091 (#0)
> POST /pools/default HTTP/1.1
> User-Agent: curl/7.37.1
> Host: 192.168.99.102:8091
> Accept: */*
> Content-Length: 36
> Content-Type: application/x-www-form-urlencoded
> 
} [data not shown]
* upload completely sent off: 36 out of 36 bytes
< HTTP/1.1 200 OK
* Server Couchbase Server is not blacklisted
< Server: Couchbase Server
< Pragma: no-cache
< Date: Mon, 21 Dec 2015 21:35:10 GMT
< Content-Length: 0
< Cache-Control: no-cache
< 
100    36    0     0  100    36      0  15510 --:--:-- --:--:-- --:--:-- 18000
* Connection #0 to host 192.168.99.102 left intact
[INFO] 
[INFO] --- exec-maven-plugin:1.4.0:exec (Configure services) @ couchbase-javaee ---
* Hostname was NOT found in DNS cache
*   Trying 192.168.99.102...
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0* Connected to 192.168.99.102 (192.168.99.102) port 8091 (#0)
> POST /node/controller/setupServices HTTP/1.1
> User-Agent: curl/7.37.1
> Host: 192.168.99.102:8091
> Accept: */*
> Content-Length: 26
> Content-Type: application/x-www-form-urlencoded
> 
} [data not shown]
* upload completely sent off: 26 out of 26 bytes
< HTTP/1.1 200 OK
* Server Couchbase Server is not blacklisted
< Server: Couchbase Server
< Pragma: no-cache
< Date: Mon, 21 Dec 2015 21:35:10 GMT
< Content-Length: 0
< Cache-Control: no-cache
< 
100    26    0     0  100    26      0   9976 --:--:-- --:--:-- --:--:-- 13000
* Connection #0 to host 192.168.99.102 left intact
[INFO] 
[INFO] --- exec-maven-plugin:1.4.0:exec (Setup credentials) @ couchbase-javaee ---
* Hostname was NOT found in DNS cache
*   Trying 192.168.99.102...
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0* Connected to 192.168.99.102 (192.168.99.102) port 8091 (#0)
> POST /settings/web HTTP/1.1
> User-Agent: curl/7.37.1
> Host: 192.168.99.102:8091
> Accept: */*
> Content-Length: 50
> Content-Type: application/x-www-form-urlencoded
> 
} [data not shown]
* upload completely sent off: 50 out of 50 bytes
< HTTP/1.1 200 OK
* Server Couchbase Server is not blacklisted
< Server: Couchbase Server
< Pragma: no-cache
< Date: Mon, 21 Dec 2015 21:35:10 GMT
< Content-Type: application/json
< Content-Length: 44
< Cache-Control: no-cache
< 
{ [data not shown]
100    94  100    44  100    50   6880   7818 --:--:-- --:--:-- --:--:--  8333
* Connection #0 to host 192.168.99.102 left intact
{"newBaseUri":"http://192.168.99.102:8091/"}[INFO] 
[INFO] --- exec-maven-plugin:1.4.0:exec (Install travel-sample bucket) @ couchbase-javaee ---
* Hostname was NOT found in DNS cache
*   Trying 192.168.99.102...
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0* Connected to 192.168.99.102 (192.168.99.102) port 8091 (#0)
* Server auth using Basic with user 'Administrator'
> POST /sampleBuckets/install HTTP/1.1
> Authorization: Basic QWRtaW5pc3RyYXRvcjpwYXNzd29yZA==
> User-Agent: curl/7.37.1
> Host: 192.168.99.102:8091
> Accept: */*
> Content-Length: 17
> Content-Type: application/x-www-form-urlencoded
> 
} [data not shown]
* upload completely sent off: 17 out of 17 bytes
< HTTP/1.1 202 Accepted
* Server Couchbase Server is not blacklisted
< Server: Couchbase Server
< Pragma: no-cache
< Date: Mon, 21 Dec 2015 21:35:11 GMT
< Content-Type: application/json
< Content-Length: 2
< Cache-Control: no-cache
< 
{ [data not shown]
100    19  100     2  100    17     41    355 --:--:-- --:--:-- --:--:--   361
* Connection #0 to host 192.168.99.102 left intact
[][INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 2.094 s
[INFO] Finished at: 2015-12-21T13:35:11-08:00
[INFO] Final Memory: 13M/309M
[INFO] ------------------------------------------------------------------------

100

101

102

103

104

105

106

107

108

109

110

111

112

113

114

115

116

117

118

119

120

121

122

123

124

125

126

127

128

129

130

131

132

133

134

135

136

137

138

139

140

141

142

143

144

145

146

147

148

149

150

151

152

153

mvn install -Pcouchbase -Ddocker.host=$(docker-machine ip couchbase)

[INFO] Scanning for projects...

[INFO]

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

[INFO] Building couchbase-javaee 1.0-SNAPSHOT

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

[INFO]

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

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

[INFO] Copying 0 resource

[INFO]

[INFO] --- maven-compiler-plugin:2.3.2:compile (default-compile) @ couchbase-javaee ---

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

[INFO]

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

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

[INFO] skip non existing resourceDirectory /Users/arungupta/workspaces/couchbase-javaee/src/test/resources

[INFO]

[INFO] --- maven-compiler-plugin:2.3.2:testCompile (default-testCompile) @ couchbase-javaee ---

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

[INFO]

[INFO] --- maven-surefire-plugin:2.12.4:test (default-test) @ couchbase-javaee ---

[INFO]

[INFO] --- maven-war-plugin:2.1.1:war (default-war) @ couchbase-javaee ---

[INFO] Packaging webapp

[INFO] Assembling webapp [couchbase-javaee] in [/Users/arungupta/workspaces/couchbase-javaee/target/couchbase-javaee]

[INFO] Processing war project

[INFO] Copying webapp resources [/Users/arungupta/workspaces/couchbase-javaee/src/main/webapp]

[INFO] Webapp assembled in [82 msecs]

[INFO] Building war: /Users/arungupta/workspaces/couchbase-javaee/target/couchbase-javaee.war

[INFO]

[INFO] --- maven-install-plugin:2.4:install (default-install) @ couchbase-javaee ---

[INFO] Installing /Users/arungupta/workspaces/couchbase-javaee/target/couchbase-javaee.war to /Users/arungupta/.m2/repository/org/couchbase/sample/couchbase-javaee/1.0-SNAPSHOT/couchbase-javaee-1.0-SNAPSHOT.war

[INFO] Installing /Users/arungupta/workspaces/couchbase-javaee/pom.xml to /Users/arungupta/.m2/repository/org/couchbase/sample/couchbase-javaee/1.0-SNAPSHOT/couchbase-javaee-1.0-SNAPSHOT.pom

[INFO]

[INFO] --- exec-maven-plugin:1.4.0:exec (Configure memory) @ couchbase-javaee ---

* Hostname was NOT found in DNS cache

* Trying 192.168.99.102...

% Total % Received % Xferd Average Speed Time Time Time Current

Dload Upload Total Spent Left Speed

0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0* Connected to 192.168.99.102 (192.168.99.102) port 8091 (#0)

> POST /pools/default HTTP/1.1

> User-Agent: curl/7.37.1

> Host: 192.168.99.102:8091

> Accept: */*

> Content-Length: 36

> Content-Type: application/x-www-form-urlencoded

} [data not shown]

* upload completely sent off: 36 out of 36 bytes

< HTTP/1.1 200 OK

* Server Couchbase Server is not blacklisted

< Server: Couchbase Server

< Pragma: no-cache

< Date: Mon, 21 Dec 2015 21:35:10 GMT

< Content-Length: 0

< Cache-Control: no-cache

100 36 0 0 100 36 0 15510 --:--:-- --:--:-- --:--:-- 18000

* Connection #0 to host 192.168.99.102 left intact

[INFO]

[INFO] --- exec-maven-plugin:1.4.0:exec (Configure services) @ couchbase-javaee ---

* Hostname was NOT found in DNS cache

* Trying 192.168.99.102...

% Total % Received % Xferd Average Speed Time Time Time Current

Dload Upload Total Spent Left Speed

0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0* Connected to 192.168.99.102 (192.168.99.102) port 8091 (#0)

> POST /node/controller/setupServices HTTP/1.1

> User-Agent: curl/7.37.1

> Host: 192.168.99.102:8091

> Accept: */*

> Content-Length: 26

> Content-Type: application/x-www-form-urlencoded

} [data not shown]

* upload completely sent off: 26 out of 26 bytes

< HTTP/1.1 200 OK

* Server Couchbase Server is not blacklisted

< Server: Couchbase Server

< Pragma: no-cache

< Date: Mon, 21 Dec 2015 21:35:10 GMT

< Content-Length: 0

< Cache-Control: no-cache

100 26 0 0 100 26 0 9976 --:--:-- --:--:-- --:--:-- 13000

* Connection #0 to host 192.168.99.102 left intact

[INFO]

[INFO] --- exec-maven-plugin:1.4.0:exec (Setup credentials) @ couchbase-javaee ---

* Hostname was NOT found in DNS cache

* Trying 192.168.99.102...

% Total % Received % Xferd Average Speed Time Time Time Current

Dload Upload Total Spent Left Speed

0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0* Connected to 192.168.99.102 (192.168.99.102) port 8091 (#0)

> POST /settings/web HTTP/1.1

> User-Agent: curl/7.37.1

> Host: 192.168.99.102:8091

> Accept: */*

> Content-Length: 50

> Content-Type: application/x-www-form-urlencoded

} [data not shown]

* upload completely sent off: 50 out of 50 bytes

< HTTP/1.1 200 OK

* Server Couchbase Server is not blacklisted

< Server: Couchbase Server

< Pragma: no-cache

< Date: Mon, 21 Dec 2015 21:35:10 GMT

< Content-Type: application/json

< Content-Length: 44

< Cache-Control: no-cache

{ [data not shown]

100 94 100 44 100 50 6880 7818 --:--:-- --:--:-- --:--:-- 8333

* Connection #0 to host 192.168.99.102 left intact

{"newBaseUri":"http://192.168.99.102:8091/"}[INFO]

[INFO] --- exec-maven-plugin:1.4.0:exec (Install travel-sample bucket) @ couchbase-javaee ---

* Hostname was NOT found in DNS cache

* Trying 192.168.99.102...

% Total % Received % Xferd Average Speed Time Time Time Current

Dload Upload Total Spent Left Speed

0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0* Connected to 192.168.99.102 (192.168.99.102) port 8091 (#0)

* Server auth using Basic with user 'Administrator'

> POST /sampleBuckets/install HTTP/1.1

> Authorization: Basic QWRtaW5pc3RyYXRvcjpwYXNzd29yZA==

> User-Agent: curl/7.37.1

> Host: 192.168.99.102:8091

> Accept: */*

> Content-Length: 17

> Content-Type: application/x-www-form-urlencoded

} [data not shown]

* upload completely sent off: 17 out of 17 bytes

< HTTP/1.1 202 Accepted

* Server Couchbase Server is not blacklisted

< Server: Couchbase Server

< Pragma: no-cache

< Date: Mon, 21 Dec 2015 21:35:11 GMT

< Content-Type: application/json

< Content-Length: 2

< Cache-Control: no-cache

{ [data not shown]

100 19 100 2 100 17 41 355 --:--:-- --:--:-- --:--:-- 361

* Connection #0 to host 192.168.99.102 left intact

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

[INFO] BUILD SUCCESS

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

[INFO] Total time: 2.094 s

[INFO] Finished at: 2015-12-21T13:35:11-08:00

[INFO] Final Memory: 13M/309M

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

Deploy Java EE Application to JBoss

Java EE Application can be easily deployed to JBoss EAP 7 Beta using the WildFly Maven Plugin. This is also defined as a Maven profile in pom.xml as well.

Deploy the application as:

mvn install -Pwildfly -Dwildfly.hostname=$(docker-machine ip couchbase) -Dwildfly.username=admin -Dwildfly.password=Admin#007
[INFO] Scanning for projects...
[INFO]                                                                         
[INFO] ------------------------------------------------------------------------
[INFO] Building couchbase-javaee 1.0-SNAPSHOT
[INFO] ------------------------------------------------------------------------
[INFO] 
[INFO] --- maven-resources-plugin:2.6:resources (default-resources) @ couchbase-javaee ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 0 resource
[INFO] 
[INFO] --- maven-compiler-plugin:2.3.2:compile (default-compile) @ couchbase-javaee ---
[INFO] Nothing to compile - all classes are up to date
[INFO] 
[INFO] --- maven-resources-plugin:2.6:testResources (default-testResources) @ couchbase-javaee ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory /Users/arungupta/workspaces/couchbase-javaee/src/test/resources
[INFO] 
[INFO] --- maven-compiler-plugin:2.3.2:testCompile (default-testCompile) @ couchbase-javaee ---
[INFO] Nothing to compile - all classes are up to date
[INFO] 
[INFO] --- maven-surefire-plugin:2.12.4:test (default-test) @ couchbase-javaee ---
[INFO] 
[INFO] --- maven-war-plugin:2.1.1:war (default-war) @ couchbase-javaee ---
[INFO] Packaging webapp
[INFO] Assembling webapp [couchbase-javaee] in [/Users/arungupta/workspaces/couchbase-javaee/target/couchbase-javaee]
[INFO] Processing war project
[INFO] Copying webapp resources [/Users/arungupta/workspaces/couchbase-javaee/src/main/webapp]
[INFO] Webapp assembled in [62 msecs]
[INFO] Building war: /Users/arungupta/workspaces/couchbase-javaee/target/couchbase-javaee.war
[INFO] 
[INFO] --- maven-install-plugin:2.4:install (default-install) @ couchbase-javaee ---
[INFO] Installing /Users/arungupta/workspaces/couchbase-javaee/target/couchbase-javaee.war to /Users/arungupta/.m2/repository/org/couchbase/sample/couchbase-javaee/1.0-SNAPSHOT/couchbase-javaee-1.0-SNAPSHOT.war
[INFO] Installing /Users/arungupta/workspaces/couchbase-javaee/pom.xml to /Users/arungupta/.m2/repository/org/couchbase/sample/couchbase-javaee/1.0-SNAPSHOT/couchbase-javaee-1.0-SNAPSHOT.pom
[INFO] 
[INFO] >>> wildfly-maven-plugin:1.1.0.Alpha4:deploy (default) > package @ couchbase-javaee >>>
[INFO] 
[INFO] --- maven-resources-plugin:2.6:resources (default-resources) @ couchbase-javaee ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 0 resource
[INFO] 
[INFO] --- maven-compiler-plugin:2.3.2:compile (default-compile) @ couchbase-javaee ---
[INFO] Nothing to compile - all classes are up to date
[INFO] 
[INFO] --- maven-resources-plugin:2.6:testResources (default-testResources) @ couchbase-javaee ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory /Users/arungupta/workspaces/couchbase-javaee/src/test/resources
[INFO] 
[INFO] --- maven-compiler-plugin:2.3.2:testCompile (default-testCompile) @ couchbase-javaee ---
[INFO] Nothing to compile - all classes are up to date
[INFO] 
[INFO] --- maven-surefire-plugin:2.12.4:test (default-test) @ couchbase-javaee ---
[INFO] Skipping execution of surefire because it has already been run for this configuration
[INFO] 
[INFO] --- maven-war-plugin:2.1.1:war (default-war) @ couchbase-javaee ---
[INFO] Packaging webapp
[INFO] Assembling webapp [couchbase-javaee] in [/Users/arungupta/workspaces/couchbase-javaee/target/couchbase-javaee]
[INFO] Processing war project
[INFO] Copying webapp resources [/Users/arungupta/workspaces/couchbase-javaee/src/main/webapp]
[INFO] Webapp assembled in [20 msecs]
[INFO] Building war: /Users/arungupta/workspaces/couchbase-javaee/target/couchbase-javaee.war
[INFO] 
[INFO] <<< wildfly-maven-plugin:1.1.0.Alpha4:deploy (default) < package @ couchbase-javaee <<<
[INFO] 
[INFO] --- wildfly-maven-plugin:1.1.0.Alpha4:deploy (default) @ couchbase-javaee ---
Dec 21, 2015 1:43:34 PM org.xnio.Xnio <clinit>
INFO: XNIO version 3.3.1.Final
Dec 21, 2015 1:43:34 PM org.xnio.nio.NioXnio <clinit>
INFO: XNIO NIO Implementation Version 3.3.1.Final
Dec 21, 2015 1:43:34 PM org.jboss.remoting3.EndpointImpl <clinit>
INFO: JBoss Remoting version 4.0.9.Final
[INFO] Authenticating against security realm: ManagementRealm
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 17.010 s
[INFO] Finished at: 2015-12-21T13:43:48-08:00
[INFO] Final Memory: 17M/217M
[INFO] ------------------------------------------------------------------------

mvn install -Pwildfly -Dwildfly.hostname=$(docker-machine ip couchbase) -Dwildfly.username=admin -Dwildfly.password=Admin#007

[INFO] Scanning for projects...

[INFO]

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

[INFO] Building couchbase-javaee 1.0-SNAPSHOT

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

[INFO]

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

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

[INFO] Copying 0 resource

[INFO]

[INFO] --- maven-compiler-plugin:2.3.2:compile (default-compile) @ couchbase-javaee ---

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

[INFO]

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

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

[INFO] skip non existing resourceDirectory /Users/arungupta/workspaces/couchbase-javaee/src/test/resources

[INFO]

[INFO] --- maven-compiler-plugin:2.3.2:testCompile (default-testCompile) @ couchbase-javaee ---

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

[INFO]

[INFO] --- maven-surefire-plugin:2.12.4:test (default-test) @ couchbase-javaee ---

[INFO]

[INFO] --- maven-war-plugin:2.1.1:war (default-war) @ couchbase-javaee ---

[INFO] Packaging webapp

[INFO] Assembling webapp [couchbase-javaee] in [/Users/arungupta/workspaces/couchbase-javaee/target/couchbase-javaee]

[INFO] Processing war project

[INFO] Copying webapp resources [/Users/arungupta/workspaces/couchbase-javaee/src/main/webapp]

[INFO] Webapp assembled in [62 msecs]

[INFO] Building war: /Users/arungupta/workspaces/couchbase-javaee/target/couchbase-javaee.war

[INFO]

[INFO] --- maven-install-plugin:2.4:install (default-install) @ couchbase-javaee ---

[INFO] Installing /Users/arungupta/workspaces/couchbase-javaee/pom.xml to /Users/arungupta/.m2/repository/org/couchbase/sample/couchbase-javaee/1.0-SNAPSHOT/couchbase-javaee-1.0-SNAPSHOT.pom

[INFO]

[INFO] >>> wildfly-maven-plugin:1.1.0.Alpha4:deploy (default) > package @ couchbase-javaee >>>

[INFO]

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

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

[INFO] Copying 0 resource

[INFO]

[INFO] --- maven-compiler-plugin:2.3.2:compile (default-compile) @ couchbase-javaee ---

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

[INFO]

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

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

[INFO] skip non existing resourceDirectory /Users/arungupta/workspaces/couchbase-javaee/src/test/resources

[INFO]

[INFO] --- maven-compiler-plugin:2.3.2:testCompile (default-testCompile) @ couchbase-javaee ---

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

[INFO]

[INFO] --- maven-surefire-plugin:2.12.4:test (default-test) @ couchbase-javaee ---

[INFO] Skipping execution of surefire because it has already been run for this configuration

[INFO]

[INFO] --- maven-war-plugin:2.1.1:war (default-war) @ couchbase-javaee ---

[INFO] Packaging webapp

[INFO] Assembling webapp [couchbase-javaee] in [/Users/arungupta/workspaces/couchbase-javaee/target/couchbase-javaee]

[INFO] Processing war project

[INFO] Copying webapp resources [/Users/arungupta/workspaces/couchbase-javaee/src/main/webapp]

[INFO] Webapp assembled in [20 msecs]

[INFO] Building war: /Users/arungupta/workspaces/couchbase-javaee/target/couchbase-javaee.war

[INFO]

[INFO] <<< wildfly-maven-plugin:1.1.0.Alpha4:deploy (default) < package @ couchbase-javaee <<<

[INFO]

[INFO] --- wildfly-maven-plugin:1.1.0.Alpha4:deploy (default) @ couchbase-javaee ---

Dec 21, 2015 1:43:34 PM org.xnio.Xnio <clinit>

INFO: XNIO version 3.3.1.Final

Dec 21, 2015 1:43:34 PM org.xnio.nio.NioXnio <clinit>

INFO: XNIO NIO Implementation Version 3.3.1.Final

Dec 21, 2015 1:43:34 PM org.jboss.remoting3.EndpointImpl <clinit>

INFO: JBoss Remoting version 4.0.9.Final

[INFO] Authenticating against security realm: ManagementRealm

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

[INFO] BUILD SUCCESS

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

[INFO] Total time: 17.010 s

[INFO] Finished at: 2015-12-21T13:43:48-08:00

[INFO] Final Memory: 17M/217M

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

Access the Application

As mentioned earlier, the application provides HTTP CRUD API over JSON documents stored in Couchbase.

Access the application as:

curl -v http://$(docker-machine ip couchbase):8080/couchbase-javaee/resources/airline
* Hostname was NOT found in DNS cache
*   Trying 192.168.99.102...
* Connected to 192.168.99.102 (192.168.99.102) port 8080 (#0)
> GET /couchbase-javaee/resources/airline HTTP/1.1
> User-Agent: curl/7.37.1
> Host: 192.168.99.102:8080
> Accept: */*
> 
< HTTP/1.1 200 OK
< Connection: keep-alive
< X-Powered-By: Undertow/1
* Server JBoss-EAP/7 is not blacklisted
< Server: JBoss-EAP/7
< Content-Type: application/octet-stream
< Content-Length: 1402
< Date: Mon, 21 Dec 2015 21:45:40 GMT
< 
* Connection #0 to host 192.168.99.102 left intact
[{"travel-sample":{"country":"United States","iata":"Q5","callsign":"MILE-AIR","name":"40-Mile Air","icao":"MLA","id":10,"type":"airline"}}, {"travel-sample":{"country":"United States","iata":"TQ","callsign":"TXW","name":"Texas Wings","icao":"TXW","id":10123,"type":"airline"}}, {"travel-sample":{"country":"United States","iata":"A1","callsign":"atifly","name":"Atifly","icao":"A1F","id":10226,"type":"airline"}}, {"travel-sample":{"country":"United Kingdom","iata":null,"callsign":null,"name":"Jc royal.britannica","icao":"JRB","id":10642,"type":"airline"}}, {"travel-sample":{"country":"United States","iata":"ZQ","callsign":"LOCAIR","name":"Locair","icao":"LOC","id":10748,"type":"airline"}}, {"travel-sample":{"country":"United States","iata":"K5","callsign":"SASQUATCH","name":"SeaPort Airlines","icao":"SQH","id":10765,"type":"airline"}}, {"travel-sample":{"country":"United States","iata":"KO","callsign":"ACE AIR","name":"Alaska Central Express","icao":"AER","id":109,"type":"airline"}}, {"travel-sample":{"country":"United Kingdom","iata":"5W","callsign":"FLYSTAR","name":"Astraeus","icao":"AEU","id":112,"type":"airline"}}, {"travel-sample":{"country":"France","iata":"UU","callsign":"REUNION","name":"Air Austral","icao":"REU","id":1191,"type":"airline"}}, {"travel-sample":{"country":"France","iata":"A5","callsign":"AIRLINAIR","name":"Airlinair","icao":"RLA","id":1203,"type":"airline"}}]

curl -v http://$(docker-machine ip couchbase):8080/couchbase-javaee/resources/airline

* Hostname was NOT found in DNS cache

* Trying 192.168.99.102...

* Connected to 192.168.99.102 (192.168.99.102) port 8080 (#0)

> GET /couchbase-javaee/resources/airline HTTP/1.1

> User-Agent: curl/7.37.1

> Host: 192.168.99.102:8080

> Accept: */*

< HTTP/1.1 200 OK

< Connection: keep-alive

< X-Powered-By: Undertow/1

* Server JBoss-EAP/7 is not blacklisted

< Server: JBoss-EAP/7

< Content-Type: application/octet-stream

< Content-Length: 1402

< Date: Mon, 21 Dec 2015 21:45:40 GMT

* Connection #0 to host 192.168.99.102 left intact

[{"travel-sample":{"country":"United States","iata":"Q5","callsign":"MILE-AIR","name":"40-Mile Air","icao":"MLA","id":10,"type":"airline"}}, {"travel-sample":{"country":"United States","iata":"TQ","callsign":"TXW","name":"Texas Wings","icao":"TXW","id":10123,"type":"airline"}}, {"travel-sample":{"country":"United States","iata":"A1","callsign":"atifly","name":"Atifly","icao":"A1F","id":10226,"type":"airline"}}, {"travel-sample":{"country":"United Kingdom","iata":null,"callsign":null,"name":"Jc royal.britannica","icao":"JRB","id":10642,"type":"airline"}}, {"travel-sample":{"country":"United States","iata":"ZQ","callsign":"LOCAIR","name":"Locair","icao":"LOC","id":10748,"type":"airline"}}, {"travel-sample":{"country":"United States","iata":"K5","callsign":"SASQUATCH","name":"SeaPort Airlines","icao":"SQH","id":10765,"type":"airline"}}, {"travel-sample":{"country":"United States","iata":"KO","callsign":"ACE AIR","name":"Alaska Central Express","icao":"AER","id":109,"type":"airline"}}, {"travel-sample":{"country":"United Kingdom","iata":"5W","callsign":"FLYSTAR","name":"Astraeus","icao":"AEU","id":112,"type":"airline"}}, {"travel-sample":{"country":"France","iata":"UU","callsign":"REUNION","name":"Air Austral","icao":"REU","id":1191,"type":"airline"}}, {"travel-sample":{"country":"France","iata":"A5","callsign":"AIRLINAIR","name":"Airlinair","icao":"RLA","id":1203,"type":"airline"}}]

CRUD operations (GET, POST, PUT, DELETE) can be performed on Airline resource in the application. Complete CRUD API is documented at github.com/arun-gupta/couchbase-javaee.

This blog explained how to access a NoSQL database from JBoss EAP 7.

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?

StarWars, Open Source and NoSQL – A New Hope!

December 18, 2015couchbasecouchbase, nosql, opensource, starwarsarungupta

A long time ago in a developer galaxy far far away …

Want to get started with NoSQL?

What is NoSQL?
Top 10 use cases for NoSQL
Get Started with NoSQL
Download Couchbase Server 4.1
What’s New in Couchbase Server 4.1
Couchbase Server documentation

May the #OpenSource and #NoSQL be with you!

Couchbase 4.1 Docker Container

December 16, 2015containers, couchbasecouchbase, dockerarungupta

Couchbase 4.1 was recently released. Highlights of this release are:

N1QL: Complete SQL CRUD Support with N1QL for Batch and OLTP Applications
Covering Indexes
Prepared Statements
Additional Supported Platforms

You can read all about it at Introducing Couchbase Server 4.1 and also watch a replay of Hands-on Introduction to What’s New in Couchbase 4.1:

Getting Started with Couchbase 4.1 and Docker

Use the following Docker Compose file:

mycouchbase:
  image: arungupta/couchbase
  ports:
    - 8091:8091
    - 8092:8092 
    - 8093:8093 
    - 11210:11210

mycouchbase:

image: arungupta/couchbase

ports:

- 8091:8091

- 8092:8092

- 8093:8093

- 11210:11210

to start a pre-configured Couchbase 4.1 Docker container:

docker-compose up -d
Creating couchbase_mycouchbase_1

docker-compose up -d

Creating couchbase_mycouchbase_1

This will:

Start Couchbase 4.1 Server (Dockerfile)
Configure it using Couchbase REST API as explained in Configure Couchbase Docker Container using REST API
- Sets up memory and index quota
- Sets up Query, Data, and Index service
- Configures username and password credentials
- Install travel-sample bucket

The logs can be seen as:

docker-compose logs
Attaching to couchbase_mycouchbase_1
mycouchbase_1 | Starting Couchbase Server -- Web UI available at http://<ip>:8091
mycouchbase_1 | *   Trying 127.0.0.1...
mycouchbase_1 |   % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
mycouchbase_1 |                                  Dload  Upload   Total   Spent    Left  Speed
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0* Connected to 127.0.0.1 (127.0.0.1) port 8091 (#0)
mycouchbase_1 | > POST /pools/default HTTP/1.1
mycouchbase_1 | > User-Agent: curl/7.40.0-DEV
mycouchbase_1 | > Host: 127.0.0.1:8091
mycouchbase_1 | > Accept: */*
mycouchbase_1 | > Content-Length: 36
mycouchbase_1 | > Content-Type: application/x-www-form-urlencoded
mycouchbase_1 | > 
mycouchbase_1 | } [36 bytes data]
mycouchbase_1 | * upload completely sent off: 36 out of 36 bytes
mycouchbase_1 | < HTTP/1.1 200 OK
mycouchbase_1 | < Server: Couchbase Server
mycouchbase_1 | < Pragma: no-cache
mycouchbase_1 | < Date: Thu, 17 Dec 2015 05:30:16 GMT
mycouchbase_1 | < Content-Length: 0
mycouchbase_1 | < Cache-Control: no-cache
mycouchbase_1 | < 
100    36    0     0  100    36      0   1820 --:--:-- --:--:-- --:--:--  2000
mycouchbase_1 | * Connection #0 to host 127.0.0.1 left intact
mycouchbase_1 | *   Trying 127.0.0.1...
mycouchbase_1 |   % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
mycouchbase_1 |                                  Dload  Upload   Total   Spent    Left  Speed
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0* Connected to 127.0.0.1 (127.0.0.1) port 8091 (#0)
mycouchbase_1 | > POST /node/controller/setupServices HTTP/1.1
mycouchbase_1 | > User-Agent: curl/7.40.0-DEV
mycouchbase_1 | > Host: 127.0.0.1:8091
mycouchbase_1 | > Accept: */*
mycouchbase_1 | > Content-Length: 26
mycouchbase_1 | > Content-Type: application/x-www-form-urlencoded
mycouchbase_1 | > 
mycouchbase_1 | } [26 bytes data]
mycouchbase_1 | * upload completely sent off: 26 out of 26 bytes
mycouchbase_1 | < HTTP/1.1 200 OK
mycouchbase_1 | < Server: Couchbase Server
mycouchbase_1 | < Pragma: no-cache
mycouchbase_1 | < Date: Thu, 17 Dec 2015 05:30:16 GMT
mycouchbase_1 | < Content-Length: 0
mycouchbase_1 | < Cache-Control: no-cache
mycouchbase_1 | < 
100    26    0     0  100    26      0   2670 --:--:-- --:--:-- --:--:--  2888
mycouchbase_1 | * Connection #0 to host 127.0.0.1 left intact
mycouchbase_1 | *   Trying 127.0.0.1...
mycouchbase_1 |   % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
mycouchbase_1 |                                  Dload  Upload   Total   Spent    Left  Speed
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0* Connected to 127.0.0.1 (127.0.0.1) port 8091 (#0)
mycouchbase_1 | > POST /settings/web HTTP/1.1
mycouchbase_1 | > User-Agent: curl/7.40.0-DEV
mycouchbase_1 | > Host: 127.0.0.1:8091
mycouchbase_1 | > Accept: */*
mycouchbase_1 | > Content-Length: 50
mycouchbase_1 | > Content-Type: application/x-www-form-urlencoded
mycouchbase_1 | > 
mycouchbase_1 | } [50 bytes data]
mycouchbase_1 | * upload completely sent off: 50 out of 50 bytes
mycouchbase_1 | < HTTP/1.1 200 OK
mycouchbase_1 | < Server: Couchbase Server
mycouchbase_1 | < Pragma: no-cache
mycouchbase_1 | < Date: Thu, 17 Dec 2015 05:30:16 GMT
mycouchbase_1 | {"newBaseUri":"http://127.0.0.1:8091/"}< Content-Type: application/json
mycouchbase_1 | < Content-Length: 39
mycouchbase_1 | < Cache-Control: no-cache
mycouchbase_1 | < 
mycouchbase_1 | { [39 bytes data]
100    89  100    39  100    50   3544   4543 --:--:-- --:--:-- --:--:--  5000
mycouchbase_1 | * Connection #0 to host 127.0.0.1 left intact
mycouchbase_1 | *   Trying 127.0.0.1...
mycouchbase_1 |   % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
mycouchbase_1 |                                  Dload  Upload   Total   Spent    Left  Speed
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0* Connected to 127.0.0.1 (127.0.0.1) port 8091 (#0)
mycouchbase_1 | * Server auth using Basic with user 'Administrator'
mycouchbase_1 | > POST /sampleBuckets/install HTTP/1.1
mycouchbase_1 | > Authorization: Basic QWRtaW5pc3RyYXRvcjpwYXNzd29yZA==
mycouchbase_1 | > User-Agent: curl/7.40.0-DEV
mycouchbase_1 | > Host: 127.0.0.1:8091
mycouchbase_1 | > Accept: */*
mycouchbase_1 | > Content-Length: 17
mycouchbase_1 | > Content-Type: application/x-www-form-urlencoded
mycouchbase_1 | > 
mycouchbase_1 | } [17 bytes data]
mycouchbase_1 | * upload completely sent off: 17 out of 17 bytes
mycouchbase_1 | < HTTP/1.1 202 Accepted
mycouchbase_1 | < Server: Couchbase Server
mycouchbase_1 | < Pragma: no-cache
mycouchbase_1 | < Date: Thu, 17 Dec 2015 05:30:16 GMT
mycouchbase_1 | < []Content-Type: application/json
mycouchbase_1 | < Content-Length: 2
mycouchbase_1 | < Cache-Control: no-cache
mycouchbase_1 | < 
mycouchbase_1 | { [2 bytes data]
100    19  100     2  100    17     29    251 --:--:-- --:--:-- --:--:--   253
mycouchbase_1 | * Connection #0 to host 127.0.0.1 left intact
mycouchbase_1 | /entrypoint.sh couchbase-server

100

docker-compose logs

Attaching to couchbase_mycouchbase_1

mycouchbase_1 | Starting Couchbase Server -- Web UI available at http://<ip>:8091

mycouchbase_1 | * Trying 127.0.0.1...

mycouchbase_1 | % Total % Received % Xferd Average Speed Time Time Time Current

mycouchbase_1 | Dload Upload Total Spent Left Speed

0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0* Connected to 127.0.0.1 (127.0.0.1) port 8091 (#0)

mycouchbase_1 | > POST /pools/default HTTP/1.1

mycouchbase_1 | > User-Agent: curl/7.40.0-DEV

mycouchbase_1 | > Host: 127.0.0.1:8091

mycouchbase_1 | > Accept: */*

mycouchbase_1 | > Content-Length: 36

mycouchbase_1 | > Content-Type: application/x-www-form-urlencoded

mycouchbase_1 | >

mycouchbase_1 | } [36 bytes data]

mycouchbase_1 | * upload completely sent off: 36 out of 36 bytes

mycouchbase_1 | < HTTP/1.1 200 OK

mycouchbase_1 | < Server: Couchbase Server

mycouchbase_1 | < Pragma: no-cache

mycouchbase_1 | < Date: Thu, 17 Dec 2015 05:30:16 GMT

mycouchbase_1 | < Content-Length: 0

mycouchbase_1 | < Cache-Control: no-cache

mycouchbase_1 | <

100 36 0 0 100 36 0 1820 --:--:-- --:--:-- --:--:-- 2000

mycouchbase_1 | * Connection #0 to host 127.0.0.1 left intact

mycouchbase_1 | * Trying 127.0.0.1...

mycouchbase_1 | % Total % Received % Xferd Average Speed Time Time Time Current

mycouchbase_1 | Dload Upload Total Spent Left Speed

0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0* Connected to 127.0.0.1 (127.0.0.1) port 8091 (#0)

mycouchbase_1 | > POST /node/controller/setupServices HTTP/1.1

mycouchbase_1 | > User-Agent: curl/7.40.0-DEV

mycouchbase_1 | > Host: 127.0.0.1:8091

mycouchbase_1 | > Accept: */*

mycouchbase_1 | > Content-Length: 26

mycouchbase_1 | > Content-Type: application/x-www-form-urlencoded

mycouchbase_1 | >

mycouchbase_1 | } [26 bytes data]

mycouchbase_1 | * upload completely sent off: 26 out of 26 bytes

mycouchbase_1 | < HTTP/1.1 200 OK

mycouchbase_1 | < Server: Couchbase Server

mycouchbase_1 | < Pragma: no-cache

mycouchbase_1 | < Date: Thu, 17 Dec 2015 05:30:16 GMT

mycouchbase_1 | < Content-Length: 0

mycouchbase_1 | < Cache-Control: no-cache

mycouchbase_1 | <

100 26 0 0 100 26 0 2670 --:--:-- --:--:-- --:--:-- 2888

mycouchbase_1 | * Connection #0 to host 127.0.0.1 left intact

mycouchbase_1 | * Trying 127.0.0.1...

mycouchbase_1 | % Total % Received % Xferd Average Speed Time Time Time Current

mycouchbase_1 | Dload Upload Total Spent Left Speed

0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0* Connected to 127.0.0.1 (127.0.0.1) port 8091 (#0)

mycouchbase_1 | > POST /settings/web HTTP/1.1

mycouchbase_1 | > User-Agent: curl/7.40.0-DEV

mycouchbase_1 | > Host: 127.0.0.1:8091

mycouchbase_1 | > Accept: */*

mycouchbase_1 | > Content-Length: 50

mycouchbase_1 | > Content-Type: application/x-www-form-urlencoded

mycouchbase_1 | >

mycouchbase_1 | } [50 bytes data]

mycouchbase_1 | * upload completely sent off: 50 out of 50 bytes

mycouchbase_1 | < HTTP/1.1 200 OK

mycouchbase_1 | < Server: Couchbase Server

mycouchbase_1 | < Pragma: no-cache

mycouchbase_1 | < Date: Thu, 17 Dec 2015 05:30:16 GMT

mycouchbase_1 | {"newBaseUri":"http://127.0.0.1:8091/"}< Content-Type: application/json

mycouchbase_1 | < Content-Length: 39

mycouchbase_1 | < Cache-Control: no-cache

mycouchbase_1 | <

mycouchbase_1 | { [39 bytes data]

100 89 100 39 100 50 3544 4543 --:--:-- --:--:-- --:--:-- 5000

mycouchbase_1 | * Connection #0 to host 127.0.0.1 left intact

mycouchbase_1 | * Trying 127.0.0.1...

mycouchbase_1 | % Total % Received % Xferd Average Speed Time Time Time Current

mycouchbase_1 | Dload Upload Total Spent Left Speed

0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0* Connected to 127.0.0.1 (127.0.0.1) port 8091 (#0)

mycouchbase_1 | * Server auth using Basic with user 'Administrator'

mycouchbase_1 | > POST /sampleBuckets/install HTTP/1.1

mycouchbase_1 | > Authorization: Basic QWRtaW5pc3RyYXRvcjpwYXNzd29yZA==

mycouchbase_1 | > User-Agent: curl/7.40.0-DEV

mycouchbase_1 | > Host: 127.0.0.1:8091

mycouchbase_1 | > Accept: */*

mycouchbase_1 | > Content-Length: 17

mycouchbase_1 | > Content-Type: application/x-www-form-urlencoded

mycouchbase_1 | >

mycouchbase_1 | } [17 bytes data]

mycouchbase_1 | * upload completely sent off: 17 out of 17 bytes

mycouchbase_1 | < HTTP/1.1 202 Accepted

mycouchbase_1 | < Server: Couchbase Server

mycouchbase_1 | < Pragma: no-cache

mycouchbase_1 | < Date: Thu, 17 Dec 2015 05:30:16 GMT

mycouchbase_1 | < []Content-Type: application/json

mycouchbase_1 | < Content-Length: 2

mycouchbase_1 | < Cache-Control: no-cache

mycouchbase_1 | <

mycouchbase_1 | { [2 bytes data]

100 19 100 2 100 17 29 251 --:--:-- --:--:-- --:--:-- 253

mycouchbase_1 | * Connection #0 to host 127.0.0.1 left intact

mycouchbase_1 | /entrypoint.sh couchbase-server

Connect to CBQ (Couchbase Query tool):

docker run -it couchbase /opt/couchbase/bin/cbq -engine=http://$(docker-machine ip couchbase):8093
Couchbase query shell connected to http://192.168.99.102:8093/ . Type Ctrl-D to exit.
cbq>

docker run -it couchbase /opt/couchbase/bin/cbq -engine=http://$(docker-machine ip couchbase):8093

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

cbq>

Learn more about Running N1QL Queries from Command Line.

Stop the server:

docker-compose stop
Stopping couchbase_mycouchbase_1 ... done

docker-compose stop

Stopping couchbase_mycouchbase_1 ... done

Remove the container:

docker-compose rm -f
Going to remove couchbase_mycouchbase_1
Removing couchbase_mycouchbase_1 ... done

docker-compose rm -f

Going to remove couchbase_mycouchbase_1

Removing couchbase_mycouchbase_1 ... done

Docker Bridge and Overlay Network with Compose Variable Substitution

December 7, 2015containersdocker, networkarungupta

Docker Multi-Host networking allows you to create virtual networks and attach containers to them so you can create the network topology that is right for your application. Bridge networks can be created for single host and overlay networks can be created for multiple hosts. Creating application-specific networks provides complete isolation for containers.

Docker Compose file can be targeted at a single host, and --x-networking will create a bridge network exclusive for the application. If the sample application is targeted at multiple hosts, say using Docker Swarm cluster, then an overlay network is created. Single host networking and multi host networking provide more details on how to set this up.

What if a bridge or an overlay network already exists and you’d like to assign this to your application started using Docker Compose?

Docker 1.9 introduced variable substitution, and we can use that feature to target an application to a pre-created network.

Create New Docker Bridge Network

Create a new network:

docker network create -d bridge mynet
47d6225ffe56ddd1a8bc0d6abb0ffd8f8ac3eec2090ff243f8cd6f77c170751b=

docker network create -d bridge mynet

47d6225ffe56ddd1a8bc0d6abb0ffd8f8ac3eec2090ff243f8cd6f77c170751b=

List the networks:

docker network ls
NETWORK ID          NAME                DRIVER
feb6e9567439        bridge              bridge              
29563a59abe8        none                null                
25ab737cd665        host                host                
47d6225ffe56        mynet               bridge

docker network ls

NETWORK ID NAME DRIVER

feb6e9567439 bridge bridge

29563a59abe8 none null

25ab737cd665 host host

47d6225ffe56 mynet bridge

Docker create three networks for each host automatically:

NETWORK NAME	PURPOSE
`bridge`	Default network that containers connect to. This is `docker0` network in all Docker installations.
`none`	Container-specific networking stack
`host`	Adds a container on hosts networking stack. Network configuration is identical to the host.

In addition, you also see mynet network that was just created.

Inspect the newly created network using docker network inspect mynet:

[
    {
        "Name": "mynet",
        "Id": "47d6225ffe56ddd1a8bc0d6abb0ffd8f8ac3eec2090ff243f8cd6f77c170751b",
        "Scope": "local",
        "Driver": "bridge",
        "IPAM": {
            "Driver": "default",
            "Config": [
                {}
            ]
        },
        "Containers": {},
        "Options": {}
    }
]

[

{

"Name": "mynet",

"Id": "47d6225ffe56ddd1a8bc0d6abb0ffd8f8ac3eec2090ff243f8cd6f77c170751b",

"Scope": "local",

"Driver": "bridge",

"IPAM": {

"Driver": "default",

"Config": [

{}

]

"Containers": {},

"Options": {}

}

]

No containers are assigned to it yet.

Docker Compose and Networking

This new network can be used for any new container using docker run --net=<NETWORK> command. This blog will show how to target this network to a Compose file:

mycouchbase:
  container_name: "db"
  image: couchbase/server
  ports:
    - 8091:8091
    - 8092:8092 
    - 8093:8093 
    - 11210:11210
  net: ${NETWORK}
mywildfly:
  image: arungupta/wildfly-admin
  environment:
    - COUCHBASE_URI=db
  ports:
    - 8080:8080
    - 9990:9990
  net: ${NETWORK}

mycouchbase:

container_name: "db"

image: couchbase/server

ports:

- 8091:8091

- 8092:8092

- 8093:8093

- 11210:11210

net: ${NETWORK}

mywildfly:

image: arungupta/wildfly-admin

environment:

- COUCHBASE_URI=db

ports:

- 8080:8080

- 9990:9990

net: ${NETWORK}

Note how net is specified here to use a custom network. This Compose file is at: github.com/arun-gupta/docker-images/blob/master/wildfly-couchbase-javaee7-network/docker-compose.yml.

Start the application, using our newly created network, as:

NETWORK=mynet docker-compose up -d

NETWORK=mynet docker-compose up -d

Inspect the network again:

docker network inspect mynet
[
    {
        "Name": "mynet",
        "Id": "47d6225ffe56ddd1a8bc0d6abb0ffd8f8ac3eec2090ff243f8cd6f77c170751b",
        "Scope": "local",
        "Driver": "bridge",
        "IPAM": {
            "Driver": "default",
            "Config": [
                {}
            ]
        },
        "Containers": {
            "300bebe6c3e0350ebf9b9d3746eb3a7b49444e14c00314770627a9f101442639": {
                "EndpointID": "82a3e2d7cd4f1bb03c9ef52bb6abf284942d7e9fcac89fe3700b0e0c4ed2654f",
                "MacAddress": "02:42:ac:14:00:03",
                "IPv4Address": "172.20.0.3/16",
                "IPv6Address": ""
            },
            "4fdae4eb919f0934422513227fe541255557dd9e8b3317374685927e7f427249": {
                "EndpointID": "937605d716d144b55288d70817d611da5fb0f87e3aedd6b5074fca07f82c3953",
                "MacAddress": "02:42:ac:14:00:02",
                "IPv4Address": "172.20.0.2/16",
                "IPv6Address": ""
            }
        },
        "Options": {}
    }
]

docker network inspect mynet

[

{

"Name": "mynet",

"Id": "47d6225ffe56ddd1a8bc0d6abb0ffd8f8ac3eec2090ff243f8cd6f77c170751b",

"Scope": "local",

"Driver": "bridge",

"IPAM": {

"Driver": "default",

"Config": [

{}

]

"Containers": {

"300bebe6c3e0350ebf9b9d3746eb3a7b49444e14c00314770627a9f101442639": {

"EndpointID": "82a3e2d7cd4f1bb03c9ef52bb6abf284942d7e9fcac89fe3700b0e0c4ed2654f",

"MacAddress": "02:42:ac:14:00:03",

"IPv4Address": "172.20.0.3/16",

"IPv6Address": ""

"4fdae4eb919f0934422513227fe541255557dd9e8b3317374685927e7f427249": {

"EndpointID": "937605d716d144b55288d70817d611da5fb0f87e3aedd6b5074fca07f82c3953",

"MacAddress": "02:42:ac:14:00:02",

"IPv4Address": "172.20.0.2/16",

"IPv6Address": ""

}

"Options": {}

}

]

And now the two containers are assigned to this network as well.

Check the container id using docker ps:

CONTAINER ID        IMAGE                     COMMAND                  CREATED             STATUS              PORTS                                                                                               NAMES
300bebe6c3e0        couchbase/server          "/entrypoint.sh couch"   2 minutes ago       Up 2 minutes        0.0.0.0:8091-8093->8091-8093/tcp, 11207/tcp, 11211/tcp, 0.0.0.0:11210->11210/tcp, 18091-18092/tcp   db
4fdae4eb919f        arungupta/wildfly-admin   "/opt/jboss/wildfly/b"   2 minutes ago       Up 2 minutes        0.0.0.0:8080->8080/tcp, 0.0.0.0:9990->9990/tcp                                                      wildflycouchbasejavaee7network_mywildfly_1

CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES

300bebe6c3e0 couchbase/server "/entrypoint.sh couch" 2 minutes ago Up 2 minutes 0.0.0.0:8091-8093->8091-8093/tcp, 11207/tcp, 11211/tcp, 0.0.0.0:11210->11210/tcp, 18091-18092/tcp db

4fdae4eb919f arungupta/wildfly-admin "/opt/jboss/wildfly/b" 2 minutes ago Up 2 minutes 0.0.0.0:8080->8080/tcp, 0.0.0.0:9990->9990/tcp wildflycouchbasejavaee7network_mywildfly_1

Check the network for one container:

docker inspect -f '{{ .HostConfig.NetworkMode }}' 300
mynet

docker inspect -f '{{ .HostConfig.NetworkMode }}' 300

mynet

More details about the network:

docker inspect -f '{{ .NetworkSettings.Networks.mynet }}' 300
{82a3e2d7cd4f1bb03c9ef52bb6abf284942d7e9fcac89fe3700b0e0c4ed2654f 172.20.0.1 172.20.0.3 16   0 02:42:ac:14:00:03}

docker inspect -f '{{ .NetworkSettings.Networks.mynet }}' 300

{82a3e2d7cd4f1bb03c9ef52bb6abf284942d7e9fcac89fe3700b0e0c4ed2654f 172.20.0.1 172.20.0.3 16 0 02:42:ac:14:00:03}

More details about the container can be found using docker inspect, relevant portion is shown here:

"Networks": {
    "mynet": {
        "EndpointID": "82a3e2d7cd4f1bb03c9ef52bb6abf284942d7e9fcac89fe3700b0e0c4ed2654f",
        "Gateway": "172.20.0.1",
        "IPAddress": "172.20.0.3",
        "IPPrefixLen": 16,
        "IPv6Gateway": "",
        "GlobalIPv6Address": "",
        "GlobalIPv6PrefixLen": 0,
        "MacAddress": "02:42:ac:14:00:03"
    }
}

"Networks": {

"mynet": {

"EndpointID": "82a3e2d7cd4f1bb03c9ef52bb6abf284942d7e9fcac89fe3700b0e0c4ed2654f",

"Gateway": "172.20.0.1",

"IPAddress": "172.20.0.3",

"IPPrefixLen": 16,

"IPv6Gateway": "",

"GlobalIPv6Address": "",

"GlobalIPv6PrefixLen": 0,

"MacAddress": "02:42:ac:14:00:03"

}

Create New Docker Overlay Network

Creating a new Docker overlay network requires to setup a key/value service and a Docker Swarm cluster. Multi-host and multi-container blog provide more details on that.

More details at Docker Networks.

Show Layers of Docker Image

December 5, 2015containers, couchbasecouchbase, dockerarungupta

Every speaking opportunity is a learning lesson, and hence a new opportunity to share. This blog will address one of the questions that has been bothering me for the past few days. It is about how to show different layers of Docker image, and their sizes, after it is downloaded.

I was invited to talk about Docker for Java developers at Peru JUG this morning. The recording is now available:

The real content starts from 5:27.

Lets address the question now.

Each Docker image consists of a series of layers. Here is a quote from docs.docker.com:

Each image consists of a series of layers. Docker makes use of union file systems to combine these layers into a single image. Union file systems allow files and directories of separate file systems, known as branches, to be transparently overlaid, forming a single coherent file system.

How does a Docker image work?

The exact size of the image can be easily seen using docker images:

docker images couchbase
REPOSITORY          TAG                 IMAGE ID            CREATED             VIRTUAL SIZE
couchbase           latest              45abdd57689a        3 weeks ago         372 MB

docker images couchbase

REPOSITORY TAG IMAGE ID CREATED VIRTUAL SIZE

couchbase latest 45abdd57689a 3 weeks ago 372 MB

The command to show different layers, and their size, is docker history:

docker history couchbase
IMAGE               CREATED             CREATED BY                                      SIZE                COMMENT
45abdd57689a        3 weeks ago         /bin/sh -c #(nop) VOLUME [/opt/couchbase/var]   0 B                 
dd8c5611343d        3 weeks ago         /bin/sh -c #(nop) EXPOSE 11207/tcp 11210/tcp    0 B                 
30852bbad62b        3 weeks ago         /bin/sh -c #(nop) CMD ["couchbase-server"]      0 B                 
5537747ea12f        3 weeks ago         /bin/sh -c #(nop) ENTRYPOINT &{["/entrypoint.   0 B                 
e8a83a5448df        3 weeks ago         /bin/sh -c #(nop) COPY file:cbb44c9c65b64a9dc   182 B               
18165b90fefa        3 weeks ago         /bin/sh -c #(nop) COPY file:34e32c52f0895191f   389 B               
5f37b8bdc5a6        3 weeks ago         /bin/sh -c wget -N $CB_RELEASE_URL/$CB_VERSIO   212.1 MB            
1a8da511d01b        3 weeks ago         /bin/sh -c groupadd -g 1000 couchbase && user   328.7 kB            
d9b2222c39b4        3 weeks ago         /bin/sh -c #(nop) ENV CB_VERSION=4.0.0 CB_REL   0 B                 
815f08b3c781        3 weeks ago         /bin/sh -c apt-get update &&     apt-get inst   23.57 MB            
fc38f156c0ea        3 weeks ago         /bin/sh -c #(nop) MAINTAINER Couchbase Docker   0 B                 
2a7a952931ec        3 weeks ago         /bin/sh -c #(nop) CMD ["/bin/bash"]             0 B                 
10f1b5844a9c        3 weeks ago         /bin/sh -c sed -i 's/^#\s*\(deb.*universe\)$/   1.911 kB            
23c388b926b6        3 weeks ago         /bin/sh -c echo '#!/bin/sh' > /usr/sbin/polic   156.2 kB            
b45376f323f5        3 weeks ago         /bin/sh -c #(nop) ADD file:4a9e089e81d6581a54   135.9 MB

docker history couchbase

IMAGE CREATED CREATED BY SIZE COMMENT

45abdd57689a 3 weeks ago /bin/sh -c #(nop) VOLUME [/opt/couchbase/var] 0 B

dd8c5611343d 3 weeks ago /bin/sh -c #(nop) EXPOSE 11207/tcp 11210/tcp 0 B

30852bbad62b 3 weeks ago /bin/sh -c #(nop) CMD ["couchbase-server"] 0 B

5537747ea12f 3 weeks ago /bin/sh -c #(nop) ENTRYPOINT &{["/entrypoint. 0 B

e8a83a5448df 3 weeks ago /bin/sh -c #(nop) COPY file:cbb44c9c65b64a9dc 182 B

18165b90fefa 3 weeks ago /bin/sh -c #(nop) COPY file:34e32c52f0895191f 389 B

5f37b8bdc5a6 3 weeks ago /bin/sh -c wget -N $CB_RELEASE_URL/$CB_VERSIO 212.1 MB

1a8da511d01b 3 weeks ago /bin/sh -c groupadd -g 1000 couchbase && user 328.7 kB

d9b2222c39b4 3 weeks ago /bin/sh -c #(nop) ENV CB_VERSION=4.0.0 CB_REL 0 B

815f08b3c781 3 weeks ago /bin/sh -c apt-get update && apt-get inst 23.57 MB

fc38f156c0ea 3 weeks ago /bin/sh -c #(nop) MAINTAINER Couchbase Docker 0 B

2a7a952931ec 3 weeks ago /bin/sh -c #(nop) CMD ["/bin/bash"] 0 B

10f1b5844a9c 3 weeks ago /bin/sh -c sed -i 's/^#\s*$deb.*universe$$/ 1.911 kB

23c388b926b6 3 weeks ago /bin/sh -c echo '#!/bin/sh' > /usr/sbin/polic 156.2 kB

b45376f323f5 3 weeks ago /bin/sh -c #(nop) ADD file:4a9e089e81d6581a54 135.9 MB

This command shows different layers, command used for each layer, and the exact size of each image.

The corresponding Dockerfile for this image is at github.com/couchbase/docker/blob/master/enterprise/couchbase-server/4.0.0/Dockerfile.

Now I can compare the Dockerfile with the exact size and easily find which image layers are the biggest. For example, biggest contributors in this Couchbase image are shown below:

Ubuntu from Dockerfile 12.04 is 135.9 MB
apt-get from Dockerfile causes another 23.57 MB
Couchbase server is 212 MB

--no-trunc can be specified as an additional CLI option to history to show the complete command executed to build the layer.

As always, the latest slides are available at github.com/javaee-samples/docker-java/tree/master/slides.

“Network timed out” Docker error

December 4, 2015containersdockerarungupta

One of the most dreaded errors seen during Docker workshops around the world is:

Network timed out while trying to connect to https://index.docker.io/v1/repositories/library/couchbase/images. You may want to check your internet connection or if you are behind a proxy.

Network timed out while trying to connect to https://index.docker.io/v1/repositories/library/couchbase/images. You may want to check your internet connection or if you are behind a proxy.

Restarting Docker Machine is typically known to fix the issue.

Lets say your machine name is couchbase-javaee. Machine can be restarted as:

docker-machine restart couchbase-javaee
Restarted machines may have new IP addresses. You may need to re-run the `docker-machine env` command.

docker-machine restart couchbase-javaee

Restarted machines may have new IP addresses. You may need to re-run the `docker-machine env` command.

Setting up Docker environment may work:

eval $(docker-machine env couchbase-javaee)

eval $(docker-machine env couchbase-javaee)

But certain times it gives the error:

Error running connection boilerplate: Error checking and/or regenerating the certs: There was an error validating certificates for host "192.168.99.106:2376": dial tcp 192.168.99.106:2376: i/o timeout
You can attempt to regenerate them using 'docker-machine regenerate-certs name'.
Be advised that this will trigger a Docker daemon restart which will stop running containers.

Error running connection boilerplate: Error checking and/or regenerating the certs: There was an error validating certificates for host "192.168.99.106:2376": dial tcp 192.168.99.106:2376: i/o timeout

You can attempt to regenerate them using 'docker-machine regenerate-certs name'.

Be advised that this will trigger a Docker daemon restart which will stop running containers.

So you need to regenerate the certificates. A successful execution will give output as:

docker-machine regenerate-certs couchbase-javaee
Regenerate TLS machine certs?  Warning: this is irreversible. (y/n): y
Regenerating TLS certificates
Copying certs to the local machine directory...
Copying certs to the remote machine...
Setting Docker configuration on the remote daemon...

docker-machine regenerate-certs couchbase-javaee

Regenerate TLS machine certs? Warning: this is irreversible. (y/n): y

Regenerating TLS certificates

Copying certs to the local machine directory...

Copying certs to the remote machine...

Setting Docker configuration on the remote daemon...

And sometimes even this command goes berserk and gives the output:

docker-machine regenerate-certs couchbase-javaee
Regenerate TLS machine certs?  Warning: this is irreversible. (y/n): y
Regenerating TLS certificates
Copying certs to the local machine directory...
Copying certs to the remote machine...
Setting Docker configuration on the remote daemon...
WARNING >>> 
This machine has been allocated an IP address, but Docker Machine could not
reach it successfully.

SSH for the machine should still work, but connecting to exposed ports, such as
the Docker daemon port (usually <ip>:2376), may not work properly.

You may need to add the route manually, or use another related workaround.

This could be due to a VPN, proxy, or host file configuration issue.

You also might want to clear any VirtualBox host only interfaces you are not using.

docker-machine regenerate-certs couchbase-javaee

Regenerate TLS machine certs? Warning: this is irreversible. (y/n): y

Regenerating TLS certificates

Copying certs to the local machine directory...

Copying certs to the remote machine...

Setting Docker configuration on the remote daemon...

WARNING >>>

This machine has been allocated an IP address, but Docker Machine could not

reach it successfully.

SSH for the machine should still work, but connecting to exposed ports, such as

the Docker daemon port (usually <ip>:2376), may not work properly.

You may need to add the route manually, or use another related workaround.

This could be due to a VPN, proxy, or host file configuration issue.

You also might want to clear any VirtualBox host only interfaces you are not using.

Either way, setting Docker environment:

eval $(docker-machine env couchbase-javaee)

eval $(docker-machine env couchbase-javaee)

sets up the environment correctly.

Docker Machine, Swarm and Compose for multi-container and multi-host applications with Couchbase and WildFly

December 3, 2015containers, couchbase, javaee, wildflycouchbase, docker, javaee7, wildflyarungupta

This blog will explain how to create multi-container application deployed on multiple hosts using Docker. This will be achieved using Docker Machine, Swarm and Compose.

Yes, all three tools together makes this blog that much more interesting!

Docker Swarm Machine Compose

The diagram explains the key components:

Docker Machine is used to provision multiple Docker hosts
Docker Swarm will be used to create a multi-host cluster
Each node in Docker Swarm cluster is registered/discovered using Consul
Multi-container application will be deployed using Docker Compose
WildFly and Couchbase are provisioned on different hosts
Docker multi-host networking is used for WildFly and Couchbase to communicate

In addition, Maven is used to configure Couchbase and deploy application to WildFly.

Latest instructions at Docker for Java Developers.

No story, just pure code, lets do it!

Create Discovery Service using Docker Machine

Create a Machine that will host discovery service:

docker-machine create -d=virtualbox consul-machine
Running pre-create checks...
Creating machine...
Waiting for machine to be running, this may take a few minutes...
Machine is running, waiting for SSH to be available...
Detecting operating system of created instance...
Provisioning created instance...
Copying certs to the local machine directory...
Copying certs to the remote machine...
Setting Docker configuration on the remote daemon...
To see how to connect Docker to this machine, run: docker-machine env consul-machine

docker-machine create -d=virtualbox consul-machine

Running pre-create checks...

Creating machine...

Waiting for machine to be running, this may take a few minutes...

Machine is running, waiting for SSH to be available...

Detecting operating system of created instance...

Provisioning created instance...

Copying certs to the local machine directory...

Copying certs to the remote machine...

Setting Docker configuration on the remote daemon...

To see how to connect Docker to this machine, run: docker-machine env consul-machine

Connect to this Machine:

eval $(docker-machine env consul-machine)

eval $(docker-machine env consul-machine)

Run Consul service using the following Compose file:

myconsul:
  image: progrium/consul
  restart: always
  hostname: consul
  ports:
    - 8500:8500
  command: "-server -bootstrap"

myconsul:

image: progrium/consul

restart: always

hostname: consul

ports:

- 8500:8500

command: "-server -bootstrap"

This Compose file is available at https://github.com/arun-gupta/docker-images/blob/master/consul/docker-compose.yml.

docker-compose up -d
Pulling myconsul (progrium/consul:latest)...
latest: Pulling from progrium/consul
3b4d28ce80e4: Pull complete
e5ab901dcf2d: Pull complete
30ad296c0ea0: Pull complete
3dba40dec256: Pull complete
f2ef4387b95e: Pull complete
53bc8dcc4791: Pull complete
75ed0b50ba1d: Pull complete
17c3a7ed5521: Pull complete
8aca9e0ecf68: Pull complete
4d1828359d36: Pull complete
46ed7df7f742: Pull complete
b5e8ce623ef8: Pull complete
049dca6ef253: Pull complete
bdb608bc4555: Pull complete
8b3d489cfb73: Pull complete
c74500bbce24: Pull complete
9f3e605442f6: Pull complete
d9125e9e799b: Pull complete
Digest: sha256:8cc8023462905929df9a79ff67ee435a36848ce7a10f18d6d0faba9306b97274
Status: Downloaded newer image for progrium/consul:latest
Creating consul_myconsul_1

docker-compose up -d

Pulling myconsul (progrium/consul:latest)...

latest: Pulling from progrium/consul

3b4d28ce80e4: Pull complete

e5ab901dcf2d: Pull complete

30ad296c0ea0: Pull complete

3dba40dec256: Pull complete

f2ef4387b95e: Pull complete

53bc8dcc4791: Pull complete

75ed0b50ba1d: Pull complete

17c3a7ed5521: Pull complete

8aca9e0ecf68: Pull complete

4d1828359d36: Pull complete

46ed7df7f742: Pull complete

b5e8ce623ef8: Pull complete

049dca6ef253: Pull complete

bdb608bc4555: Pull complete

8b3d489cfb73: Pull complete

c74500bbce24: Pull complete

9f3e605442f6: Pull complete

d9125e9e799b: Pull complete

Digest: sha256:8cc8023462905929df9a79ff67ee435a36848ce7a10f18d6d0faba9306b97274

Status: Downloaded newer image for progrium/consul:latest

Creating consul_myconsul_1

Started container can be verified as:

docker ps
CONTAINER ID        IMAGE               COMMAND                  CREATED             STATUS              PORTS                                                                            NAMES
f05d8dd11e7f        progrium/consul     "/bin/start -server -"   30 seconds ago      Up 29 seconds       53/tcp, 53/udp, 8300-8302/tcp, 8400/tcp, 0.0.0.0:8500->8500/tcp, 8301-8302/udp   consul_myconsul_1

docker ps

CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES

f05d8dd11e7f progrium/consul "/bin/start -server -" 30 seconds ago Up 29 seconds 53/tcp, 53/udp, 8300-8302/tcp, 8400/tcp, 0.0.0.0:8500->8500/tcp, 8301-8302/udp consul_myconsul_1

Create Docker Swarm Cluster using Docker Machine

Swarm is fully integrated with Machine, and so is the easiest way to get started.

Create a Swarm Master and point to the Consul discovery service:

docker-machine create -d virtualbox --virtualbox-disk-size "5000" --swarm --swarm-master --swarm-discovery="consul://$(docker-machine ip consul-machine):8500" --engine-opt="cluster-store=consul://$(docker-machine ip consul-machine):8500" --engine-opt="cluster-advertise=eth1:2376" swarm-master
Running pre-create checks...
Creating machine...
Waiting for machine to be running, this may take a few minutes...
Machine is running, waiting for SSH to be available...
Detecting operating system of created instance...
Provisioning created instance...
Copying certs to the local machine directory...
Copying certs to the remote machine...
Setting Docker configuration on the remote daemon...
Configuring swarm...
To see how to connect Docker to this machine, run: docker-machine env swarm-master

docker-machine create -d virtualbox --virtualbox-disk-size "5000" --swarm --swarm-master --swarm-discovery="consul://$(docker-machine ip consul-machine):8500" --engine-opt="cluster-store=consul://$(docker-machine ip consul-machine):8500" --engine-opt="cluster-advertise=eth1:2376" swarm-master

Running pre-create checks...

Creating machine...

Waiting for machine to be running, this may take a few minutes...

Machine is running, waiting for SSH to be available...

Detecting operating system of created instance...

Provisioning created instance...

Copying certs to the local machine directory...

Copying certs to the remote machine...

Setting Docker configuration on the remote daemon...

Configuring swarm...

To see how to connect Docker to this machine, run: docker-machine env swarm-master

Few options to look here:

--swarm configures the Machine with Swarm
--swarm-master configures the created Machine to be Swarm master
--swarm-discovery defines address of the discovery service
--cluster-advertise advertise the machine on the network
--cluster-store designate a distributed k/v storage backend for the cluster
--virtualbox-disk-size sets the disk size for the created Machine to 5GB. This is required so that WildFly and Couchbase image can be downloaded on any of the nodes.

Find some information about this machine:

docker-machine inspect --format='{{json .Driver}}'  swarm-master
{"Boot2DockerImportVM":"","Boot2DockerURL":"","CPU":1,"DiskSize":5000,"HostOnlyCIDR":"192.168.99.1/24","HostOnlyNicType":"82540EM","HostOnlyPromiscMode":"deny","IPAddress":"192.168.99.102","MachineName":"swarm-master","Memory":1024,"NoShare":false,"SSHPort":51972,"SSHUser":"docker","StorePath":"/Users/arungupta/.docker/machine","SwarmDiscovery":"consul://192.168.99.100:8500","SwarmHost":"tcp://0.0.0.0:3376","SwarmMaster":true,"VBoxManager":{}}

docker-machine inspect --format='{{json .Driver}}' swarm-master

{"Boot2DockerImportVM":"","Boot2DockerURL":"","CPU":1,"DiskSize":5000,"HostOnlyCIDR":"192.168.99.1/24","HostOnlyNicType":"82540EM","HostOnlyPromiscMode":"deny","IPAddress":"192.168.99.102","MachineName":"swarm-master","Memory":1024,"NoShare":false,"SSHPort":51972,"SSHUser":"docker","StorePath":"/Users/arungupta/.docker/machine","SwarmDiscovery":"consul://192.168.99.100:8500","SwarmHost":"tcp://0.0.0.0:3376","SwarmMaster":true,"VBoxManager":{}}

Note that the disk size is 5GB.

Connect to the master by using the command:

eval "$(docker-machine env --swarm swarm-master)"

eval "$(docker-machine env --swarm swarm-master)"

Find some information about the cluster:

docker info
Containers: 2
Images: 1
Role: primary
Strategy: spread
Filters: health, port, dependency, affinity, constraint
Nodes: 1
 swarm-master: 192.168.99.102:2376
  └ Containers: 2
  └ Reserved CPUs: 0 / 1
  └ Reserved Memory: 0 B / 1.021 GiB
  └ Labels: executiondriver=native-0.2, kernelversion=4.1.13-boot2docker, operatingsystem=Boot2Docker 1.9.1 (TCL 6.4.1); master : cef800b - Fri Nov 20 19:33:59 UTC 2015, provider=virtualbox, storagedriver=aufs
CPUs: 1
Total Memory: 1.021 GiB
Name: d074fd97682e

docker info

Containers: 2

Images: 1

Role: primary

Strategy: spread

Filters: health, port, dependency, affinity, constraint

Nodes: 1

swarm-master: 192.168.99.102:2376

└ Containers: 2

└ Reserved CPUs: 0 / 1

└ Reserved Memory: 0 B / 1.021 GiB

└ Labels: executiondriver=native-0.2, kernelversion=4.1.13-boot2docker, operatingsystem=Boot2Docker 1.9.1 (TCL 6.4.1); master : cef800b - Fri Nov 20 19:33:59 UTC 2015, provider=virtualbox, storagedriver=aufs

CPUs: 1

Total Memory: 1.021 GiB

Name: d074fd97682e

Create a new Machine to join this cluster:

docker-machine create -d virtualbox --virtualbox-disk-size "5000" --swarm --swarm-discovery="consul://$(docker-machine ip consul-machine):8500" --engine-opt="cluster-store=consul://$(docker-machine ip consul-machine):8500" --engine-opt="cluster-advertise=eth1:2376" swarm-node-01
Running pre-create checks...
Creating machine...
Waiting for machine to be running, this may take a few minutes...
Machine is running, waiting for SSH to be available...
Detecting operating system of created instance...
Provisioning created instance...
Copying certs to the local machine directory...
Copying certs to the remote machine...
Setting Docker configuration on the remote daemon...
Configuring swarm...
To see how to connect Docker to this machine, run: docker-machine env swarm-node-01

docker-machine create -d virtualbox --virtualbox-disk-size "5000" --swarm --swarm-discovery="consul://$(docker-machine ip consul-machine):8500" --engine-opt="cluster-store=consul://$(docker-machine ip consul-machine):8500" --engine-opt="cluster-advertise=eth1:2376" swarm-node-01

Running pre-create checks...

Creating machine...

Waiting for machine to be running, this may take a few minutes...

Machine is running, waiting for SSH to be available...

Detecting operating system of created instance...

Provisioning created instance...

Copying certs to the local machine directory...

Copying certs to the remote machine...

Setting Docker configuration on the remote daemon...

Configuring swarm...

To see how to connect Docker to this machine, run: docker-machine env swarm-node-01

Notice no --swarm-master is specified in this command. This ensure that the created Machines are worker nodes.

Create a second Swarm node to join this cluster:

docker-machine create -d virtualbox --virtualbox-disk-size "5000" --swarm --swarm-discovery="consul://$(docker-machine ip consul-machine):8500" --engine-opt="cluster-store=consul://$(docker-machine ip consul-machine):8500" --engine-opt="cluster-advertise=eth1:2376" swarm-node-02
Running pre-create checks...
Creating machine...
Waiting for machine to be running, this may take a few minutes...
Machine is running, waiting for SSH to be available...
Detecting operating system of created instance...
Provisioning created instance...
Copying certs to the local machine directory...
Copying certs to the remote machine...
Setting Docker configuration on the remote daemon...
Configuring swarm...
To see how to connect Docker to this machine, run: docker-machine env swarm-node-02

Running pre-create checks...

Creating machine...

Waiting for machine to be running, this may take a few minutes...

Machine is running, waiting for SSH to be available...

Detecting operating system of created instance...

Provisioning created instance...

Copying certs to the local machine directory...

Copying certs to the remote machine...

Setting Docker configuration on the remote daemon...

Configuring swarm...

To see how to connect Docker to this machine, run: docker-machine env swarm-node-02

List all the created Machines:

docker-machine ls
NAME             ACTIVE   DRIVER       STATE     URL                         SWARM
consul-machine   -        virtualbox   Running   tcp://192.168.99.100:2376
swarm-master     *        virtualbox   Running   tcp://192.168.99.101:2376   swarm-master (master)
swarm-node-01    -        virtualbox   Running   tcp://192.168.99.102:2376   swarm-master
swarm-node-02    -        virtualbox   Running   tcp://192.168.99.103:2376   swarm-master

docker-machine ls

NAME ACTIVE DRIVER STATE URL SWARM

consul-machine - virtualbox Running tcp://192.168.99.100:2376

swarm-master * virtualbox Running tcp://192.168.99.101:2376 swarm-master (master)

swarm-node-01 - virtualbox Running tcp://192.168.99.102:2376 swarm-master

swarm-node-02 - virtualbox Running tcp://192.168.99.103:2376 swarm-master

The machines that are part of the cluster have cluster’s name in the SWARM column, blank otherwise. For example,consul-machine is a standalone machine where as all other machines are part of the swarm-master cluster. The Swarm master is also identified by (master) in the SWARM column.

Connect to the Swarm cluster and find some information about it:

eval "$(docker-machine env --swarm swarm-master)"
docker info

eval "$(docker-machine env --swarm swarm-master)"

docker info

Note, --swarm is specified to connect to the Swarm cluster. Otherwise the command will connect to swarm-masterMachine only.

This shows the output as:

docker info
Containers: 4
Images: 3
Role: primary
Strategy: spread
Filters: health, port, dependency, affinity, constraint
Nodes: 3
 swarm-master: 192.168.99.102:2376
  └ Containers: 2
  └ Reserved CPUs: 0 / 1
  └ Reserved Memory: 0 B / 1.021 GiB
  └ Labels: executiondriver=native-0.2, kernelversion=4.1.13-boot2docker, operatingsystem=Boot2Docker 1.9.1 (TCL 6.4.1); master : cef800b - Fri Nov 20 19:33:59 UTC 2015, provider=virtualbox, storagedriver=aufs
 swarm-node-01: 192.168.99.103:2376
  └ Containers: 1
  └ Reserved CPUs: 0 / 1
  └ Reserved Memory: 0 B / 1.021 GiB
  └ Labels: executiondriver=native-0.2, kernelversion=4.1.13-boot2docker, operatingsystem=Boot2Docker 1.9.1 (TCL 6.4.1); master : cef800b - Fri Nov 20 19:33:59 UTC 2015, provider=virtualbox, storagedriver=aufs
 swarm-node-02: 192.168.99.104:2376
  └ Containers: 1
  └ Reserved CPUs: 0 / 1
  └ Reserved Memory: 0 B / 1.021 GiB
  └ Labels: executiondriver=native-0.2, kernelversion=4.1.13-boot2docker, operatingsystem=Boot2Docker 1.9.1 (TCL 6.4.1); master : cef800b - Fri Nov 20 19:33:59 UTC 2015, provider=virtualbox, storagedriver=aufs
CPUs: 3
Total Memory: 3.064 GiB
Name: d074fd97682e

docker info

Containers: 4

Images: 3

Role: primary

Strategy: spread

Filters: health, port, dependency, affinity, constraint

Nodes: 3

swarm-master: 192.168.99.102:2376

└ Containers: 2

└ Reserved CPUs: 0 / 1

└ Reserved Memory: 0 B / 1.021 GiB

swarm-node-01: 192.168.99.103:2376

└ Containers: 1

└ Reserved CPUs: 0 / 1

└ Reserved Memory: 0 B / 1.021 GiB

swarm-node-02: 192.168.99.104:2376

└ Containers: 1

└ Reserved CPUs: 0 / 1

└ Reserved Memory: 0 B / 1.021 GiB

CPUs: 3

Total Memory: 3.064 GiB

Name: d074fd97682e

There are 3 nodes – one Swarm master and 2 Swarm worker nodes. There is a total of 4 containers running in this cluster – one Swarm agent on master and each node, and there is an additional swarm-agent-master running on the master. This can be verified by connecting to the master and listing all the containers.

List nodes in the cluster with the following command:

docker run swarm list consul://$(docker-machine ip consul-machine):8500
192.168.99.102:2376
192.168.99.103:2376
192.168.99.104:2376

docker run swarm list consul://$(docker-machine ip consul-machine):8500

192.168.99.102:2376

192.168.99.103:2376

192.168.99.104:2376

Start Application Environment using Docker Compose

Make sure you are connected to the cluster by giving the command eval "$(docker-machine env --swarm swarm-master)".

List all the networks created by Docker so far:

docker network ls
NETWORK ID          NAME                   DRIVER
33a619ddc5d2        swarm-node-02/bridge   bridge
e0b73c96ffec        swarm-node-02/none     null
b315e67f0363        swarm-node-02/host     host
879d6167be47        swarm-master/bridge    bridge
f771ddc7d957        swarm-node-01/none     null
e042754df336        swarm-node-01/host     host
d2f3b512f9dc        swarm-node-01/bridge   bridge
5b5bcf135d7b        swarm-master/none      null
fffc34eae907        swarm-master/host      host

docker network ls

NETWORK ID NAME DRIVER

33a619ddc5d2 swarm-node-02/bridge bridge

e0b73c96ffec swarm-node-02/none null

b315e67f0363 swarm-node-02/host host

879d6167be47 swarm-master/bridge bridge

f771ddc7d957 swarm-node-01/none null

e042754df336 swarm-node-01/host host

d2f3b512f9dc swarm-node-01/bridge bridge

5b5bcf135d7b swarm-master/none null

fffc34eae907 swarm-master/host host

Docker create three networks for each host automatically:

Network Name	Purpose
`bridge`	Default network that containers connect to. This is `docker0` network in all Docker installations.
`none`	Container-specific networking stack
`host`	Adds a container on hosts networking stack. Network configuration is identical to the host.

This explains a total of nine networks, three for each node, as shown in this Swarm cluster.

Use Compose file to start WildFly and Couchbase:

mycouchbase:
  container_name: "db"
  image: couchbase/server
  ports:
    - 8091:8091
    - 8092:8092
    - 8093:8093
    - 11210:11210
mywildfly:
  image: arungupta/wildfly-admin
  environment:
    - COUCHBASE_URI=db
  ports:
    - 8080:8080
    - 9990:9990

mycouchbase:

container_name: "db"

image: couchbase/server

ports:

- 8091:8091

- 8092:8092

- 8093:8093

- 11210:11210

mywildfly:

image: arungupta/wildfly-admin

environment:

- COUCHBASE_URI=db

ports:

- 8080:8080

- 9990:9990

In this Compose file:

Couchbase service has a custom container name defined by container_name. This name is used when creating a new environment variable COUCHBASE_URI during WildFly startup.
arungupta/wildfly-admin image is used as it binds WildFly’s management to all network interfaces, and in addition also exposes port 9990. This enables WildFly Maven Plugin to be used to deploy the application.Source for this file is at https://github.com/arun-gupta/docker-images/blob/master/wildfly-couchbase-javaee7/docker-compose.yml.

This application environment can be started as:

docker-compose --x-networking up -d
Creating network "wildflycouchbasejavaee7" with driver "None"
Pulling mywildfly (arungupta/wildfly-admin:latest)...
swarm-node-02: Pulling arungupta/wildfly-admin:latest... : downloaded
swarm-master: Pulling arungupta/wildfly-admin:latest... : downloaded
swarm-node-01: Pulling arungupta/wildfly-admin:latest... : downloaded
Creating wildflycouchbasejavaee7_mywildfly_1
Pulling mycouchbase (couchbase/server:latest)...
swarm-node-02: Pulling couchbase/server:latest... : downloaded
swarm-master: Pulling couchbase/server:latest... : downloaded
swarm-node-01: Pulling couchbase/server:latest... : downloaded
Creating db

docker-compose --x-networking up -d

Creating network "wildflycouchbasejavaee7" with driver "None"

Pulling mywildfly (arungupta/wildfly-admin:latest)...

swarm-node-02: Pulling arungupta/wildfly-admin:latest... : downloaded

swarm-master: Pulling arungupta/wildfly-admin:latest... : downloaded

swarm-node-01: Pulling arungupta/wildfly-admin:latest... : downloaded

Creating wildflycouchbasejavaee7_mywildfly_1

Pulling mycouchbase (couchbase/server:latest)...

swarm-node-02: Pulling couchbase/server:latest... : downloaded

swarm-master: Pulling couchbase/server:latest... : downloaded

swarm-node-01: Pulling couchbase/server:latest... : downloaded

Creating db

--x-networking creates an overlay network for the Swarm cluster. This can be verified by listing networks again:

docker network ls
NETWORK ID          NAME                            DRIVER
5e93fc34b4d9        swarm-node-01/docker_gwbridge   bridge
1c041242f51d        wildflycouchbasejavaee7         overlay
cc8697c6ce13        swarm-master/docker_gwbridge    bridge
f771ddc7d957        swarm-node-01/none              null
879d6167be47        swarm-master/bridge             bridge
5b5bcf135d7b        swarm-master/none               null
fffc34eae907        swarm-master/host               host
e042754df336        swarm-node-01/host              host
d2f3b512f9dc        swarm-node-01/bridge            bridge
33a619ddc5d2        swarm-node-02/bridge            bridge
e0b73c96ffec        swarm-node-02/none              null
b315e67f0363        swarm-node-02/host              host

docker network ls

NETWORK ID NAME DRIVER

5e93fc34b4d9 swarm-node-01/docker_gwbridge bridge

1c041242f51d wildflycouchbasejavaee7 overlay

cc8697c6ce13 swarm-master/docker_gwbridge bridge

f771ddc7d957 swarm-node-01/none null

879d6167be47 swarm-master/bridge bridge

5b5bcf135d7b swarm-master/none null

fffc34eae907 swarm-master/host host

e042754df336 swarm-node-01/host host

d2f3b512f9dc swarm-node-01/bridge bridge

33a619ddc5d2 swarm-node-02/bridge bridge

e0b73c96ffec swarm-node-02/none null

b315e67f0363 swarm-node-02/host host

Three new networks are created:

Containers connected to the multi-host network are automatically connected to the docker_gwbridge network. This network allows the containers to have external connectivity outside of their cluster, and is created on each worker node.

A new overlay network wildflycouchbasejavaee7 is created. Connect to different Swarm nodes and check that the overlay network exists on them.

Lets begin with master:

eval "$(docker-machine env swarm-master)"
docker network ls
NETWORK ID          NAME                      DRIVER
1c041242f51d        wildflycouchbasejavaee7   overlay
879d6167be47        bridge                    bridge
5b5bcf135d7b        none                      null
fffc34eae907        host                      host
cc8697c6ce13        docker_gwbridge           bridge

eval "$(docker-machine env swarm-master)"

docker network ls

NETWORK ID NAME DRIVER

1c041242f51d wildflycouchbasejavaee7 overlay

879d6167be47 bridge bridge

5b5bcf135d7b none null

fffc34eae907 host host

cc8697c6ce13 docker_gwbridge bridge

Next, with swarm-node-01:

eval "$(docker-machine env swarm-node-01)"
docker network ls
NETWORK ID          NAME                      DRIVER
1c041242f51d        wildflycouchbasejavaee7   overlay
d2f3b512f9dc        bridge                    bridge
f771ddc7d957        none                      null
e042754df336        host                      host
5e93fc34b4d9        docker_gwbridge           bridge

eval "$(docker-machine env swarm-node-01)"

docker network ls

NETWORK ID NAME DRIVER

1c041242f51d wildflycouchbasejavaee7 overlay

d2f3b512f9dc bridge bridge

f771ddc7d957 none null

e042754df336 host host

5e93fc34b4d9 docker_gwbridge bridge

Finally, with swarm-node-02:

eval "$(docker-machine env swarm-node-02)"
docker network ls
NETWORK ID          NAME                      DRIVER
1c041242f51d        wildflycouchbasejavaee7   overlay
e0b73c96ffec        none                      null
b315e67f0363        host                      host
33a619ddc5d2        bridge                    bridge

eval "$(docker-machine env swarm-node-02)"

docker network ls

NETWORK ID NAME DRIVER

1c041242f51d wildflycouchbasejavaee7 overlay

e0b73c96ffec none null

b315e67f0363 host host

33a619ddc5d2 bridge bridge

As seen, wildflycouchbasejavaee7 overlay network exists on all Machines. This confirms that the overlay network created for Swarm cluster was added to each host in the cluster. docker_gwbridge only exists on Machines that have application containers running.

Configure Application and Database

Clone https://github.com/arun-gupta/couchbase-javaee.git. This workspace contains a simple Java EE application that is deployed on WildFly and provides a REST API over travel-sample bucket in Couchbase.

Couchbase server can be configured using REST API. The application contains a Maven profile that allows to configure Couchbase server with travel-sample bucket. This can be invoked as:

mvn install -Pcouchbase -Ddocker.host=$(docker-machine ip swarm-master)

. . .

* Server auth using Basic with user 'Administrator'
> POST /sampleBuckets/install HTTP/1.1
> Authorization: Basic QWRtaW5pc3RyYXRvcjpwYXNzd29yZA==

. . .

} [data not shown]
* upload completely sent off: 17 out of 17 bytes
< HTTP/1.1 202 Accepted
* Server Couchbase Server is not blacklisted
< Server: Couchbase Server

. . .

mvn install -Pcouchbase -Ddocker.host=$(docker-machine ip swarm-master)

. . .

* Server auth using Basic with user 'Administrator'

> POST /sampleBuckets/install HTTP/1.1

> Authorization: Basic QWRtaW5pc3RyYXRvcjpwYXNzd29yZA==

. . .

} [data not shown]

* upload completely sent off: 17 out of 17 bytes

< HTTP/1.1 202 Accepted

* Server Couchbase Server is not blacklisted

< Server: Couchbase Server

. . .

Deploy the application to WildFly by specifying three parameters:

Host IP address where WildFly is running
Username of a user in WildFly’s administrative realm
Password of the user specified in WildFly’s administrative realm

mvn install -Pwildfly -Dwildfly.hostname=$(docker-machine ip swarm-node-01) -Dwildfly.username=admin -Dwildfly.password=Admin#007

. . .

Nov 29, 2015 12:11:14 AM org.xnio.Xnio <clinit>
INFO: XNIO version 3.3.1.Final
Nov 29, 2015 12:11:14 AM org.xnio.nio.NioXnio <clinit>
INFO: XNIO NIO Implementation Version 3.3.1.Final
Nov 29, 2015 12:11:15 AM org.jboss.remoting3.EndpointImpl <clinit>
INFO: JBoss Remoting version 4.0.9.Final
[INFO] Authenticating against security realm: ManagementRealm
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------

. . .

mvn install -Pwildfly -Dwildfly.hostname=$(docker-machine ip swarm-node-01) -Dwildfly.username=admin -Dwildfly.password=Admin#007

. . .

Nov 29, 2015 12:11:14 AM org.xnio.Xnio <clinit>

INFO: XNIO version 3.3.1.Final

Nov 29, 2015 12:11:14 AM org.xnio.nio.NioXnio <clinit>

INFO: XNIO NIO Implementation Version 3.3.1.Final

Nov 29, 2015 12:11:15 AM org.jboss.remoting3.EndpointImpl <clinit>

INFO: JBoss Remoting version 4.0.9.Final

[INFO] Authenticating against security realm: ManagementRealm

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

[INFO] BUILD SUCCESS

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

. . .

Access Application

Now that WildFly and Couchbase server have started, lets access the application. You need to specify IP address of the Machine where WildFly is running:

curl http://$(docker-machine ip swarm-node-01):8080/couchbase-javaee/resources/airline
[{"travel-sample":{"id":10123,"iata":"TQ","icao":"TXW","name":"Texas Wings","callsign":"TXW","type":"airline","country":"United States"}}, {"travel-sample":{"id":10642,"iata":null,"icao":"JRB","name":"Jc royal.britannica","callsign":null,"type":"airline","country":"United Kingdom"}}, {"travel-sample":{"id":112,"iata":"5W","icao":"AEU","name":"Astraeus","callsign":"FLYSTAR","type":"airline","country":"United Kingdom"}}, {"travel-sample":{"id":1355,"iata":"BA","icao":"BAW","name":"British Airways","callsign":"SPEEDBIRD","type":"airline","country":"United Kingdom"}}, {"travel-sample":{"id":10765,"iata":"K5","icao":"SQH","name":"SeaPort Airlines","callsign":"SASQUATCH","type":"airline","country":"United States"}}, {"travel-sample":{"id":13633,"iata":"WQ","icao":"PQW","name":"PanAm World Airways","callsign":null,"type":"airline","country":"United States"}}, {"travel-sample":{"id":139,"iata":"SB","icao":"ACI","name":"Air Caledonie International","callsign":"AIRCALIN","type":"airline","country":"France"}}, {"travel-sample":{"id":13391,"iata":"-+","icao":"--+","name":"U.S. Air","callsign":null,"type":"airline","country":"United States"}}, {"travel-sample":{"id":1191,"iata":"UU","icao":"REU","name":"Air Austral","callsign":"REUNION","type":"airline","country":"France"}}, {"travel-sample":{"id":1316,"iata":"FL","icao":"TRS","name":"AirTran Airways","callsign":"CITRUS","type":"airline","country":"United States"}}]

curl http://$(docker-machine ip swarm-node-01):8080/couchbase-javaee/resources/airline

[{"travel-sample":{"id":10123,"iata":"TQ","icao":"TXW","name":"Texas Wings","callsign":"TXW","type":"airline","country":"United States"}}, {"travel-sample":{"id":10642,"iata":null,"icao":"JRB","name":"Jc royal.britannica","callsign":null,"type":"airline","country":"United Kingdom"}}, {"travel-sample":{"id":112,"iata":"5W","icao":"AEU","name":"Astraeus","callsign":"FLYSTAR","type":"airline","country":"United Kingdom"}}, {"travel-sample":{"id":1355,"iata":"BA","icao":"BAW","name":"British Airways","callsign":"SPEEDBIRD","type":"airline","country":"United Kingdom"}}, {"travel-sample":{"id":10765,"iata":"K5","icao":"SQH","name":"SeaPort Airlines","callsign":"SASQUATCH","type":"airline","country":"United States"}}, {"travel-sample":{"id":13633,"iata":"WQ","icao":"PQW","name":"PanAm World Airways","callsign":null,"type":"airline","country":"United States"}}, {"travel-sample":{"id":139,"iata":"SB","icao":"ACI","name":"Air Caledonie International","callsign":"AIRCALIN","type":"airline","country":"France"}}, {"travel-sample":{"id":13391,"iata":"-+","icao":"--+","name":"U.S. Air","callsign":null,"type":"airline","country":"United States"}}, {"travel-sample":{"id":1191,"iata":"UU","icao":"REU","name":"Air Austral","callsign":"REUNION","type":"airline","country":"France"}}, {"travel-sample":{"id":1316,"iata":"FL","icao":"TRS","name":"AirTran Airways","callsign":"CITRUS","type":"airline","country":"United States"}}]

Complete set of REST API for this application is documented at github.com/arun-gupta/couchbase-javaee.

Latest instructions at Docker for Java Developers.

Enjoy!

JavaOne4Kids 2015 Wrapup – Devoxx4Kids and Oracle Academy Together!

December 2, 2015conferences, java, kidsdevoxx4kids, java, javaone, minecraftarungupta

JavaOne4Kids is focused on promoting technology to next generation of developers; kids who want to learn more about programming, robotics and engineering.

Oracle Academy collaborated with Devoxx4Kids to bring kids content that includes several topics like Minecraft Modding, Java, Python, Scratch, Raspberry Pi, Arduino, NAO robot, LEGO Mindstorms, Greenfoot, Alice, and others at JavaOne 2015.

The attendance grew 3x from last year and it was certainly very heartening to see that!

If you live in/around San Francisco Bay Area, and want a more continued experience through out the year, then its highly recommend to join meetup.com/Devoxx4Kids-BayArea/!

Here are some statistics from the event:

A survey was sent to the attendees and some of them responded back. 95% of responses rated were happy with the event:

javaone4kids-2015-rate

90%+ would recommend JavaOne4Kids to a friend:

javaone4kids-2015-recommend

Instructors seem to have done a good job with 97% presenting in good, very good, and excellent way:

javaone4kids-2015-clear-way

Minecraft Modding continues to be the top rated workshop:

javaone4kids-2015-course

Here are some pictures from the event:

Check out the complete album:

JavaOne4Kids 2015 Album

Picture is worth a thousand words, and a video is worth a million words. Check out kids in action from the event, and then subsequently in JavaOne Community Keynote:

It takes a village to run an event like this. This was certainly not possible without the impeccable support from Oracle team, instructors, and volunteers who helped us through out the event!

Do we expect these kids to come back to again next year? Yes, absolutely!

At least, 88% of them want to come back

javaone4kids-2015-another-event

Don’t forget to join the local meetup.com/devoxx4kids-bayarea for local events in Bay Area.

Docker Swarm Cluster using Consul

November 28, 2015containersconsul, dockerarungupta

Docker Swarm is native clustering for Docker. It allows you create and access to a pool of Docker hosts using the full suite of Docker tools. Because Docker Swarm serves the standard Docker API, any tool that already communicates with a Docker daemon can use Swarm to transparently scale to multiple hosts.

Docker Swarm has a Manager, a pre-defined Docker Host, and is a single point for all administration. Swarm manager orchestrates and schedules containers on the entire cluster, and can be configured in High Availability. The containers are deployed on Nodes that are additional Docker Hosts.

Swarm talks to a hosted Discovery Service that maintains a list of IPs in your cluster. For development, its easy to use the default discovery service hosted on Docker Hub. Complete instructions for that are available in Install and Create Docker Swarm. This blog will show how to setup Docker Swarm Cluster using Consul.

Lets get started!

Create Consul Discovery Service

Create a Machine that will host discovery service:

docker-machine create -d=virtualbox consul-machine
Running pre-create checks...
Creating machine...
Waiting for machine to be running, this may take a few minutes...
Machine is running, waiting for SSH to be available...
Detecting operating system of created instance...
Provisioning created instance...
Copying certs to the local machine directory...
Copying certs to the remote machine...
Setting Docker configuration on the remote daemon...
To see how to connect Docker to this machine, run: docker-machine env consul-machine

docker-machine create -d=virtualbox consul-machine

Running pre-create checks...

Creating machine...

Waiting for machine to be running, this may take a few minutes...

Machine is running, waiting for SSH to be available...

Detecting operating system of created instance...

Provisioning created instance...

Copying certs to the local machine directory...

Copying certs to the remote machine...

Setting Docker configuration on the remote daemon...

To see how to connect Docker to this machine, run: docker-machine env consul-machine

Connect to this Machine:

eval $(docker-machine env consul-machine)

eval $(docker-machine env consul-machine)

Run Consul service using the following Compose file:

myconsul:
  image: progrium/consul
  restart: always
  hostname: consul
  ports:
    - 8500:8500
  command: "-server -bootstrap"

myconsul:

image: progrium/consul

restart: always

hostname: consul

ports:

- 8500:8500

command: "-server -bootstrap"

This file is also available at github.com/arun-gupta/docker-images/tree/master/consul.

The service is started as:

docker-compose up -d
Pulling myconsul (progrium/consul:latest)...
latest: Pulling from progrium/consul
3b4d28ce80e4: Pull complete
e5ab901dcf2d: Pull complete
30ad296c0ea0: Pull complete
3dba40dec256: Pull complete
f2ef4387b95e: Pull complete
53bc8dcc4791: Pull complete
75ed0b50ba1d: Pull complete
17c3a7ed5521: Pull complete
8aca9e0ecf68: Pull complete
4d1828359d36: Pull complete
46ed7df7f742: Pull complete
b5e8ce623ef8: Pull complete
049dca6ef253: Pull complete
bdb608bc4555: Pull complete
8b3d489cfb73: Pull complete
c74500bbce24: Pull complete
9f3e605442f6: Pull complete
d9125e9e799b: Pull complete
Digest: sha256:8cc8023462905929df9a79ff67ee435a36848ce7a10f18d6d0faba9306b97274
Status: Downloaded newer image for progrium/consul:latest
Creating consul_myconsul_1

docker-compose up -d

Pulling myconsul (progrium/consul:latest)...

latest: Pulling from progrium/consul

3b4d28ce80e4: Pull complete

e5ab901dcf2d: Pull complete

30ad296c0ea0: Pull complete

3dba40dec256: Pull complete

f2ef4387b95e: Pull complete

53bc8dcc4791: Pull complete

75ed0b50ba1d: Pull complete

17c3a7ed5521: Pull complete

8aca9e0ecf68: Pull complete

4d1828359d36: Pull complete

46ed7df7f742: Pull complete

b5e8ce623ef8: Pull complete

049dca6ef253: Pull complete

bdb608bc4555: Pull complete

8b3d489cfb73: Pull complete

c74500bbce24: Pull complete

9f3e605442f6: Pull complete

d9125e9e799b: Pull complete

Digest: sha256:8cc8023462905929df9a79ff67ee435a36848ce7a10f18d6d0faba9306b97274

Status: Downloaded newer image for progrium/consul:latest

Creating consul_myconsul_1

Started container can be verified as:

docker ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
f05d8dd11e7f progrium/consul "/bin/start -server -" 30 seconds ago Up 29 seconds 53/tcp, 53/udp, 8300-8302/tcp, 8400/tcp, 0.0.0.0:8500->8500/tcp, 8301-8302/udp consul_myconsul_1

docker ps

CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES

f05d8dd11e7f progrium/consul "/bin/start -server -" 30 seconds ago Up 29 seconds 53/tcp, 53/udp, 8300-8302/tcp, 8400/tcp, 0.0.0.0:8500->8500/tcp, 8301-8302/udp consul_myconsul_1

Create Docker Swarm Cluster using Consul

Swarm is fully integrated with Machine, and so is the easiest way to get started.

Create a Swarm Master using the Consul discovery service:

docker-machine create -d virtualbox --swarm --swarm-master --swarm-discovery="consul://$(docker-machine ip consul-machine):8500" --engine-opt="cluster-store=consul://$(docker-machine ip consul-machine):8500" --engine-opt="cluster-advertise=eth1:2376" swarm-master
Running pre-create checks...
Creating machine...
Waiting for machine to be running, this may take a few minutes...
Machine is running, waiting for SSH to be available...
Detecting operating system of created instance...
Provisioning created instance...
Copying certs to the local machine directory...
Copying certs to the remote machine...
Setting Docker configuration on the remote daemon...
Configuring swarm...
To see how to connect Docker to this machine, run: docker-machine env swarm-master

docker-machine create -d virtualbox --swarm --swarm-master --swarm-discovery="consul://$(docker-machine ip consul-machine):8500" --engine-opt="cluster-store=consul://$(docker-machine ip consul-machine):8500" --engine-opt="cluster-advertise=eth1:2376" swarm-master

Running pre-create checks...

Creating machine...

Waiting for machine to be running, this may take a few minutes...

Machine is running, waiting for SSH to be available...

Detecting operating system of created instance...

Provisioning created instance...

Copying certs to the local machine directory...

Copying certs to the remote machine...

Setting Docker configuration on the remote daemon...

Configuring swarm...

To see how to connect Docker to this machine, run: docker-machine env swarm-master

Three options to look here:

--swarm-discovery defines address of the discovery service
--cluster-advertise advertise the machine on the network
--cluster-store designate a distributed k/v storage backend for the cluster

In addition, --swarm configures the Machine with Swarm, --swarm-master configures the created Machine to be Swarm master.

Connect to this newly created master and find some information about it:

eval "$(docker-machine env swarm-master)"
docker info

eval "$(docker-machine env swarm-master)"

docker info

This will show the output as:

docker info
Containers: 2
Images: 8
Server Version: 1.9.0
Storage Driver: aufs
 Root Dir: /mnt/sda1/var/lib/docker/aufs
 Backing Filesystem: tmpfs
 Dirs: 12
 Dirperm1 Supported: true
Execution Driver: native-0.2
Logging Driver: json-file
Kernel Version: 4.1.12-boot2docker
Operating System: Boot2Docker 1.9.0 (TCL 6.4); master : 16e4a2a - Tue Nov  3 19:49:22 UTC 2015
CPUs: 1
Total Memory: 996.2 MiB
Name: swarm-master
ID: 2EDA:WPOD:YVWO:GGLZ:ZUHY:WCBU:ZERW:OWBE:6MPQ:IPXN:BS2V:QCSI
Debug mode (server): true
 File Descriptors: 30
 Goroutines: 67
 System Time: 2015-11-29T02:08:10.636829121Z
 EventsListeners: 1
 Init SHA1: 
 Init Path: /usr/local/bin/docker
 Docker Root Dir: /mnt/sda1/var/lib/docker
Username: arungupta
Registry: https://index.docker.io/v1/
Labels:
 provider=virtualbox
Cluster store: consul://192.168.99.109:8500
Cluster advertise: 192.168.99.111:2376

docker info

Containers: 2

Images: 8

Server Version: 1.9.0

Storage Driver: aufs

Root Dir: /mnt/sda1/var/lib/docker/aufs

Backing Filesystem: tmpfs

Dirs: 12

Dirperm1 Supported: true

Execution Driver: native-0.2

Logging Driver: json-file

Kernel Version: 4.1.12-boot2docker

Operating System: Boot2Docker 1.9.0 (TCL 6.4); master : 16e4a2a - Tue Nov 3 19:49:22 UTC 2015

CPUs: 1

Total Memory: 996.2 MiB

Name: swarm-master

ID: 2EDA:WPOD:YVWO:GGLZ:ZUHY:WCBU:ZERW:OWBE:6MPQ:IPXN:BS2V:QCSI

Debug mode (server): true

File Descriptors: 30

Goroutines: 67

System Time: 2015-11-29T02:08:10.636829121Z

EventsListeners: 1

Init SHA1:

Init Path: /usr/local/bin/docker

Docker Root Dir: /mnt/sda1/var/lib/docker

Username: arungupta

Registry: https://index.docker.io/v1/

Labels:

provider=virtualbox

Cluster store: consul://192.168.99.109:8500

Cluster advertise: 192.168.99.111:2376

Create a new Machine to be part of this Swarm cluster:

docker-machine create -d virtualbox --swarm --swarm-discovery="consul://$(docker-machine ip consul-machine):8500" --engine-opt="cluster-store=consul://$(docker-machine ip consul-machine):8500" --engine-opt="cluster-advertise=eth1:2376" swarm-node-01
Running pre-create checks...
Creating machine...
Waiting for machine to be running, this may take a few minutes...
Machine is running, waiting for SSH to be available...
Detecting operating system of created instance...
Provisioning created instance...
Copying certs to the local machine directory...
Copying certs to the remote machine...
Setting Docker configuration on the remote daemon...
Configuring swarm...
To see how to connect Docker to this machine, run: docker-machine env swarm-node-01

docker-machine create -d virtualbox --swarm --swarm-discovery="consul://$(docker-machine ip consul-machine):8500" --engine-opt="cluster-store=consul://$(docker-machine ip consul-machine):8500" --engine-opt="cluster-advertise=eth1:2376" swarm-node-01

Running pre-create checks...

Creating machine...

Waiting for machine to be running, this may take a few minutes...

Machine is running, waiting for SSH to be available...

Detecting operating system of created instance...

Provisioning created instance...

Copying certs to the local machine directory...

Copying certs to the remote machine...

Setting Docker configuration on the remote daemon...

Configuring swarm...

To see how to connect Docker to this machine, run: docker-machine env swarm-node-01

Machine talks to the Discovery Service using --swarm-discovery.

Create a second node in this cluster:

docker-machine create -d virtualbox --swarm --swarm-discovery="consul://$(docker-machine ip consul-machine):8500" --engine-opt="cluster-store=consul://$(docker-machine ip consul-machine):8500" --engine-opt="cluster-advertise=eth1:2376" swarm-node-02
Running pre-create checks...
Creating machine...
Waiting for machine to be running, this may take a few minutes...
Machine is running, waiting for SSH to be available...
Detecting operating system of created instance...
Provisioning created instance...
Copying certs to the local machine directory...
Copying certs to the remote machine...
Setting Docker configuration on the remote daemon...
Configuring swarm...
To see how to connect Docker to this machine, run: docker-machine env swarm-node-02

Running pre-create checks...

Creating machine...

Waiting for machine to be running, this may take a few minutes...

Machine is running, waiting for SSH to be available...

Detecting operating system of created instance...

Provisioning created instance...

Copying certs to the local machine directory...

Copying certs to the remote machine...

Setting Docker configuration on the remote daemon...

Configuring swarm...

To see how to connect Docker to this machine, run: docker-machine env swarm-node-02

List all the created Machines:

docker-machine ls 
NAME             ACTIVE   DRIVER       STATE     URL                         SWARM
consul-machine   -        virtualbox   Running   tcp://192.168.99.109:2376   
default          -        virtualbox   Running   tcp://192.168.99.100:2376   
swarm-master     *        virtualbox   Running   tcp://192.168.99.111:2376   swarm-master (master)
swarm-node-01    -        virtualbox   Running   tcp://192.168.99.112:2376   swarm-master
swarm-node-02    -        virtualbox   Running   tcp://192.168.99.113:2376   swarm-master

docker-machine ls

NAME ACTIVE DRIVER STATE URL SWARM

consul-machine - virtualbox Running tcp://192.168.99.109:2376

default - virtualbox Running tcp://192.168.99.100:2376

swarm-master * virtualbox Running tcp://192.168.99.111:2376 swarm-master (master)

swarm-node-01 - virtualbox Running tcp://192.168.99.112:2376 swarm-master

swarm-node-02 - virtualbox Running tcp://192.168.99.113:2376 swarm-master

The machines that are part of the cluster have cluster’s name in the SWARM column, blank otherwise. For example, “default” and “consul-machine” are standalone machines where as all other machines are part of the “swarm-master” cluster. The Swarm master is also identified by (master) in the SWARM column.

Connect to the Swarm cluster and find some information about it:

eval "$(docker-machine env --swarm swarm-master)"
docker info

eval "$(docker-machine env --swarm swarm-master)"

docker info

The main difference here is --swarm when finding information about Swarm cluster as opposed to a single Machine.

This shows the output as:

docker info
Containers: 4
Images: 3
Role: primary
Strategy: spread
Filters: health, port, dependency, affinity, constraint
Nodes: 3
 swarm-master: 192.168.99.111:2376
  └ Containers: 2
  └ Reserved CPUs: 0 / 1
  └ Reserved Memory: 0 B / 1.021 GiB
  └ Labels: executiondriver=native-0.2, kernelversion=4.1.12-boot2docker, operatingsystem=Boot2Docker 1.9.0 (TCL 6.4); master : 16e4a2a - Tue Nov  3 19:49:22 UTC 2015, provider=virtualbox, storagedriver=aufs
 swarm-node-01: 192.168.99.112:2376
  └ Containers: 1
  └ Reserved CPUs: 0 / 1
  └ Reserved Memory: 0 B / 1.021 GiB
  └ Labels: executiondriver=native-0.2, kernelversion=4.1.12-boot2docker, operatingsystem=Boot2Docker 1.9.0 (TCL 6.4); master : 16e4a2a - Tue Nov  3 19:49:22 UTC 2015, provider=virtualbox, storagedriver=aufs
 swarm-node-02: 192.168.99.113:2376
  └ Containers: 1
  └ Reserved CPUs: 0 / 1
  └ Reserved Memory: 0 B / 1.021 GiB
  └ Labels: executiondriver=native-0.2, kernelversion=4.1.12-boot2docker, operatingsystem=Boot2Docker 1.9.0 (TCL 6.4); master : 16e4a2a - Tue Nov  3 19:49:22 UTC 2015, provider=virtualbox, storagedriver=aufs
CPUs: 3
Total Memory: 3.064 GiB
Name: 10edc606d097

docker info

Containers: 4

Images: 3

Role: primary

Strategy: spread

Filters: health, port, dependency, affinity, constraint

Nodes: 3

swarm-master: 192.168.99.111:2376

└ Containers: 2

└ Reserved CPUs: 0 / 1

└ Reserved Memory: 0 B / 1.021 GiB

└ Labels: executiondriver=native-0.2, kernelversion=4.1.12-boot2docker, operatingsystem=Boot2Docker 1.9.0 (TCL 6.4); master : 16e4a2a - Tue Nov 3 19:49:22 UTC 2015, provider=virtualbox, storagedriver=aufs

swarm-node-01: 192.168.99.112:2376

└ Containers: 1

└ Reserved CPUs: 0 / 1

└ Reserved Memory: 0 B / 1.021 GiB

swarm-node-02: 192.168.99.113:2376

└ Containers: 1

└ Reserved CPUs: 0 / 1

└ Reserved Memory: 0 B / 1.021 GiB

CPUs: 3

Total Memory: 3.064 GiB

Name: 10edc606d097

There are 3 nodes – one Swarm master and 2 Swarm _worker_ nodes. There is a total of 4 containers running in this cluster – one Swarm agent on master and each node, and there is an additional swarm-agent-master running on the master. This can be verified by connecting to the master and listing all the containers.

List nodes in the cluster with the following command:

docker run swarm list consul://$(docker-machine ip consul-machine):8500
192.168.99.111:2376
192.168.99.112:2376
192.168.99.113:2376

docker run swarm list consul://$(docker-machine ip consul-machine):8500

192.168.99.111:2376

192.168.99.112:2376

192.168.99.113:2376

Subsequent blog will explain how to deploy applications to this Docker Swarm Cluster.

Enjoy!

Docker Networking with Couchbase and WildFly

November 26, 2015containers, couchbase, javaee, wildflycouchbase, docker, javaee, maven, rest, wildflyarungupta

Docker Multi-Host networking allows you to create virtual networks and attach containers to them so you can create the network topology that is right for your application. This blog will show how to use it with Docker Compose.

CRUD Java Application with Couchbase, Java EE, and WildFly explained how to use a Java EE application to provide a CRUD/REST interface on a data bucket in Couchbase. It required to manually download and run WildFly. The blog also used Couchbase server using Docker and required manual configuration to load travel-sample bucket.

Configure Couchbase Docker Container using REST API explained how to use Couchbase REST API to configure Couchbase Server.

This blog will remove the explicit download of WildFly and manual configuration of Couchbase server:

Use Docker Compose to start WildFly and Couchbase (no download required)
Use a Maven profile to configure Couchbase server (no manual configuration required)
Uses Docker multi-host networking so that WildFly and Couchbase server can talk to each other

Lets get started!

Start Couchbase and WildFly using Docker Multi-Host Networking and Compose

Start WildFly and Couchbase server using docker-compose.yml file from github.com/arun-gupta/docker-images/blob/master/wildfly-couchbase-javaee7/docker-compose.yml:

mycouchbase:
  container_name: "db"
  image: couchbase/server
  ports:
    - 8091:8091
    - 8092:8092 
    - 8093:8093 
    - 11210:11210
mywildfly:
  image: arungupta/wildfly-admin
  environment:
    - COUCHBASE_URI=db
  ports:
    - 8080:8080
    - 9990:9990

mycouchbase:

container_name: "db"

image: couchbase/server

ports:

- 8091:8091

- 8092:8092

- 8093:8093

- 11210:11210

mywildfly:

image: arungupta/wildfly-admin

environment:

- COUCHBASE_URI=db

ports:

- 8080:8080

- 9990:9990

arungupta/wildfly-admin image is used as it binds WildFly’s management to all network interfaces, and in addition also exposes port 9990. This enables WildFly Maven Plugin to be used to deploy the application.

container_name is specified for Couchbase service and referred in WildFly service using COUCHBASE_URI. This is then used to connect to Couchbase from the Java EE application.

The application environment is started as:

docker-compose --x-networking up -d
Creating network "wildflycouchbasejavaee7" with driver "None"
Creating wildflycouchbasejavaee7_mywildfly_1
Creating db

docker-compose --x-networking up -d

Creating network "wildflycouchbasejavaee7" with driver "None"

Creating wildflycouchbasejavaee7_mywildfly_1

Creating db

--x-networking is an experimental switch added to Docker Compose 1.9 that allows to create a bridge or an overlay network. By default, it creates a bridge network that works on a single host. The network created can be seen as:

docker network ls
NETWORK ID          NAME                      DRIVER
968bde2b7745        bridge                    bridge              
79e937bcf1f6        none                      null                
d06a4bd59a4b        host                      host                
5e26a9a205ff        wildflycouchbasejavaee7   bridge

docker network ls

NETWORK ID NAME DRIVER

968bde2b7745 bridge bridge

79e937bcf1f6 none null

d06a4bd59a4b host host

5e26a9a205ff wildflycouchbasejavaee7 bridge

Issue 2221 provide more explanation about the default networks created. wildflycouchbasejavaee7 is the new bridge network created for our application. Issue #2345 provide some details about incorrect driver name in the output message.

Configure Couchbase Server

Clone couchbase-javaee repo:

https://github.com/arun-gupta/couchbase-javaee

https://github.com/arun-gupta/couchbase-javaee

Configure Couchbase server:

mvn install -Pcouchbase
[INFO] Scanning for projects...
[INFO]                                                                         
[INFO] ------------------------------------------------------------------------
[INFO] Building couchbase-javaee 1.0-SNAPSHOT
[INFO] ------------------------------------------------------------------------
[INFO] 


. . .

* Server auth using Basic with user 'Administrator'
> POST /sampleBuckets/install HTTP/1.1
> Authorization: Basic QWRtaW5pc3RyYXRvcjpwYXNzd29yZA==
> User-Agent: curl/7.37.1
> Host: 192.168.99.100:8091

. . .

< Cache-Control: no-cache
< 
{ [data not shown]
100    19  100     2  100    17     50    425 --:--:-- --:--:-- --:--:--   435
* Connection #0 to host 192.168.99.100 left intact
[][INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------

mvn install -Pcouchbase

[INFO] Scanning for projects...

[INFO]

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

[INFO] Building couchbase-javaee 1.0-SNAPSHOT

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

[INFO]

. . .

* Server auth using Basic with user 'Administrator'

> POST /sampleBuckets/install HTTP/1.1

> Authorization: Basic QWRtaW5pc3RyYXRvcjpwYXNzd29yZA==

> User-Agent: curl/7.37.1

> Host: 192.168.99.100:8091

. . .

< Cache-Control: no-cache

{ [data not shown]

100 19 100 2 100 17 50 425 --:--:-- --:--:-- --:--:-- 435

* Connection #0 to host 192.168.99.100 left intact

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

[INFO] BUILD SUCCESS

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

exec-maven-plugin is used to invoke REST API and configure Couchbase server and is configured in a Maven profile. Make sure to setup docker.host property in pom.xml.

Deploy the application to WildFly:

mvn install -Pwildfly -Dwildfly.hostname=192.168.99.100 -Dwildfly.username=admin -Dwildfly.password=Admin#007
[INFO] Scanning for projects...
[INFO]                                                                         
[INFO] ------------------------------------------------------------------------
[INFO] Building couchbase-javaee 1.0-SNAPSHOT
[INFO] ------------------------------------------------------------------------

. . .

Nov 26, 2015 5:17:39 AM org.xnio.Xnio <clinit>
INFO: XNIO version 3.3.1.Final
Nov 26, 2015 5:17:39 AM org.xnio.nio.NioXnio <clinit>
INFO: XNIO NIO Implementation Version 3.3.1.Final
Nov 26, 2015 5:17:39 AM org.jboss.remoting3.EndpointImpl <clinit>
INFO: JBoss Remoting version 4.0.9.Final
[INFO] Authenticating against security realm: ManagementRealm
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------

mvn install -Pwildfly -Dwildfly.hostname=192.168.99.100 -Dwildfly.username=admin -Dwildfly.password=Admin#007

[INFO] Scanning for projects...

[INFO]

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

[INFO] Building couchbase-javaee 1.0-SNAPSHOT

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

. . .

Nov 26, 2015 5:17:39 AM org.xnio.Xnio <clinit>

INFO: XNIO version 3.3.1.Final

Nov 26, 2015 5:17:39 AM org.xnio.nio.NioXnio <clinit>

INFO: XNIO NIO Implementation Version 3.3.1.Final

Nov 26, 2015 5:17:39 AM org.jboss.remoting3.EndpointImpl <clinit>

INFO: JBoss Remoting version 4.0.9.Final

[INFO] Authenticating against security realm: ManagementRealm

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

[INFO] BUILD SUCCESS

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

Make sure to specify the correct host on CLI. In this case, this is the IP address obtained using docker-machine ip default.

Invoke the Application

Invoke the REST endpoint using cURL:

curl -v http://192.168.99.100:8080/couchbase-javaee/resources/airline
* Hostname was NOT found in DNS cache
*   Trying 192.168.99.100...
* Connected to 192.168.99.100 (192.168.99.100) port 8080 (#0)
> GET /couchbase-javaee/resources/airline HTTP/1.1
> User-Agent: curl/7.37.1
> Host: 192.168.99.100:8080
> Accept: */*
> 
< HTTP/1.1 200 OK
< Connection: keep-alive
< X-Powered-By: Undertow/1
* Server WildFly/8 is not blacklisted
< Server: WildFly/8
< Content-Type: application/octet-stream
< Content-Length: 1393
< Date: Thu, 26 Nov 2015 13:18:36 GMT
< 
* Connection #0 to host 192.168.99.100 left intact
[{"travel-sample":{"id":112,"iata":"5W","icao":"AEU","name":"Astraeus","callsign":"FLYSTAR","type":"airline","country":"United Kingdom"}}, {"travel-sample":{"id":109,"iata":"KO","icao":"AER","name":"Alaska Central Express","callsign":"ACE AIR","type":"airline","country":"United States"}}, {"travel-sample":{"id":1191,"iata":"UU","icao":"REU","name":"Air Austral","callsign":"REUNION","type":"airline","country":"France"}}, {"travel-sample":{"id":1203,"iata":"A5","icao":"RLA","name":"Airlinair","callsign":"AIRLINAIR","type":"airline","country":"France"}}, {"travel-sample":{"id":10642,"iata":null,"icao":"JRB","name":"Jc royal.britannica","callsign":null,"type":"airline","country":"United Kingdom"}}, {"travel-sample":{"id":13633,"iata":"WQ","icao":"PQW","name":"PanAm World Airways","callsign":null,"type":"airline","country":"United States"}}, {"travel-sample":{"id":137,"iata":"AF","icao":"AFR","name":"Air France","callsign":"AIRFRANS","type":"airline","country":"France"}}, {"travel-sample":{"id":10748,"iata":"ZQ","icao":"LOC","name":"Locair","callsign":"LOCAIR","type":"airline","country":"United States"}}, {"travel-sample":{"id":10,"iata":"Q5","icao":"MLA","name":"40-Mile Air","callsign":"MILE-AIR","type":"airline","country":"United States"}}, {"travel-sample":{"id":10226,"iata":"A1","icao":"A1F","name":"Atifly","callsign":"atifly","type":"airline","country":"United States"}}]

curl -v http://192.168.99.100:8080/couchbase-javaee/resources/airline

* Hostname was NOT found in DNS cache

* Trying 192.168.99.100...

* Connected to 192.168.99.100 (192.168.99.100) port 8080 (#0)

> GET /couchbase-javaee/resources/airline HTTP/1.1

> User-Agent: curl/7.37.1

> Host: 192.168.99.100:8080

> Accept: */*

< HTTP/1.1 200 OK

< Connection: keep-alive

< X-Powered-By: Undertow/1

* Server WildFly/8 is not blacklisted

< Server: WildFly/8

< Content-Type: application/octet-stream

< Content-Length: 1393

< Date: Thu, 26 Nov 2015 13:18:36 GMT

* Connection #0 to host 192.168.99.100 left intact

[{"travel-sample":{"id":112,"iata":"5W","icao":"AEU","name":"Astraeus","callsign":"FLYSTAR","type":"airline","country":"United Kingdom"}}, {"travel-sample":{"id":109,"iata":"KO","icao":"AER","name":"Alaska Central Express","callsign":"ACE AIR","type":"airline","country":"United States"}}, {"travel-sample":{"id":1191,"iata":"UU","icao":"REU","name":"Air Austral","callsign":"REUNION","type":"airline","country":"France"}}, {"travel-sample":{"id":1203,"iata":"A5","icao":"RLA","name":"Airlinair","callsign":"AIRLINAIR","type":"airline","country":"France"}}, {"travel-sample":{"id":10642,"iata":null,"icao":"JRB","name":"Jc royal.britannica","callsign":null,"type":"airline","country":"United Kingdom"}}, {"travel-sample":{"id":13633,"iata":"WQ","icao":"PQW","name":"PanAm World Airways","callsign":null,"type":"airline","country":"United States"}}, {"travel-sample":{"id":137,"iata":"AF","icao":"AFR","name":"Air France","callsign":"AIRFRANS","type":"airline","country":"France"}}, {"travel-sample":{"id":10748,"iata":"ZQ","icao":"LOC","name":"Locair","callsign":"LOCAIR","type":"airline","country":"United States"}}, {"travel-sample":{"id":10,"iata":"Q5","icao":"MLA","name":"40-Mile Air","callsign":"MILE-AIR","type":"airline","country":"United States"}}, {"travel-sample":{"id":10226,"iata":"A1","icao":"A1F","name":"Atifly","callsign":"atifly","type":"airline","country":"United States"}}]

Complete set of REST endpoints are documented at CRUD Java Application with Couchbase, Java EE and WildFly. They are listed here for convenience:

GET a single airline:

curl -v http://192.168.99.100:8080/couchbase-javaee/resources/airline/139

curl -v http://192.168.99.100:8080/couchbase-javaee/resources/airline/139

Create a new airline using POST:

curl -v -H "Content-Type: application/json" -X POST -d '{"country":"France","iata":"A5","callsign":"AIRLINAIR","name":"Airlinair","icao":"RLA","type":"airline"}' http://192.168.99.100:8080/couchbase-javaee/resources/airline

curl -v -H "Content-Type: application/json" -X POST -d '{"country":"France","iata":"A5","callsign":"AIRLINAIR","name":"Airlinair","icao":"RLA","type":"airline"}' http://192.168.99.100:8080/couchbase-javaee/resources/airline

Update an existing airline using PUT:

curl -v -H "Content-Type: application/json" -X PUT -d '{"country":"France","iata":"A5","callsign":"AIRLINAIR","name":"Airlin Air","icao":"RLA","type":"airline","id": "19810"}' http://192.168.99.100:8080/couchbase-javaee/resources/airline/19810

curl -v -H "Content-Type: application/json" -X PUT -d '{"country":"France","iata":"A5","callsign":"AIRLINAIR","name":"Airlin Air","icao":"RLA","type":"airline","id": "19810"}' http://192.168.99.100:8080/couchbase-javaee/resources/airline/19810

Delete an existing airline using DELETE:

curl -v -X DELETE http://192.168.99.100:8080/couchbase-javaee/resources/airline/19810

curl -v -X DELETE http://192.168.99.100:8080/couchbase-javaee/resources/airline/19810

Enjoy!

Configure Couchbase Docker Container using REST API

November 25, 2015containers, couchbasecontainers, couchbase, dockerarungupta

Couchbase Docker image is published at hub.docker.com/_/couchbase. The easiest way to start this image is:

docker run -d -p 8091:8091 couchbase/server

docker run -d -p 8091:8091 couchbase/server

8091 is the network port used by Couchbase Web Console for REST traffic. Complete set of ports are documented at Couchbase Network Configuration. This image can be configured using Single Host Single Container configuration as explained at hub.docker.com/_/couchbase.

This blog will show you can create a single node Couchbase cluster using Docker, configure it with Data, Index, and Query service, load a sample bucket, and query it.

Start Couchbase Docker Container

Start Couchbase Docker Container using the following docker-compose.yml:

mycouchbase:
  name: mycouchbase
  image: couchbase/server
  volumes:
    - ~/couchbase:/opt/couchbase/var
  ports:
    - 8091:8091
    - 8092:8092 
    - 8093:8093 
    - 11210:11210

mycouchbase:

name: mycouchbase

image: couchbase/server

volumes:

- ~/couchbase:/opt/couchbase/var

ports:

- 8091:8091

- 8092:8092

- 8093:8093

- 11210:11210

This Docker Compose file can be downloaded from github.com/arun-gupta/docker-images/tree/master/couchbase-server.

The container can be started as:

docker-compose up -d
Creating couchbaseserver_mycouchbase_1

docker-compose up -d

Creating couchbaseserver_mycouchbase_1

Status of the running container can be seen as:

docker-compose ps
           Name                       Command                       State                        Ports            
-----------------------------------------------------------------------------------------------------------------
couchbaseserver_mycouchbas   /entrypoint.sh couchbase-s   Up                           11207/tcp,                 
e_1                          ...                                                       0.0.0.0:11210->11210/tcp,  
                                                                                       11211/tcp, 18091/tcp,      
                                                                                       18092/tcp,                 
                                                                                       0.0.0.0:8091->8091/tcp,    
                                                                                       0.0.0.0:8092->8092/tcp,    
                                                                                       0.0.0.0:8093->8093/tcp

docker-compose ps

Name Command State Ports

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

couchbaseserver_mycouchbas /entrypoint.sh couchbase-s Up 11207/tcp,

e_1 ... 0.0.0.0:11210->11210/tcp,

11211/tcp, 18091/tcp,

18092/tcp,

0.0.0.0:8091->8091/tcp,

0.0.0.0:8092->8092/tcp,

0.0.0.0:8093->8093/tcp

Logs can be seen as:

docker-compose logs
Attaching to couchbaseserver_mycouchbase_1
mycouchbase_1 | Starting Couchbase Server -- Web UI available at http://<ip>:8091

docker-compose logs

Attaching to couchbaseserver_mycouchbase_1

mycouchbase_1 | Starting Couchbase Server -- Web UI available at http://<ip>:8091

Configure Couchbase Docker Container

Get IP address of the Docker Host:

docker-machine ip default
192.168.99.100

docker-machine ip default

192.168.99.100

Use this IP address in all the subsequent commands.

Configure memory for Data and Index services:

curl -v -X POST http://192.168.99.100:8091/pools/default -d memoryQuota=300 -d indexMemoryQuota=300
* Hostname was NOT found in DNS cache
*   Trying 192.168.99.100...
* Connected to 192.168.99.100 (192.168.99.100) port 8091 (#0)
> POST /pools/default HTTP/1.1
> User-Agent: curl/7.37.1
> Host: 192.168.99.100:8091
> Accept: */*
> Content-Length: 36
> Content-Type: application/x-www-form-urlencoded
> 
* upload completely sent off: 36 out of 36 bytes
< HTTP/1.1 401 Unauthorized
< WWW-Authenticate: Basic realm="Couchbase Server Admin / REST"
* Server Couchbase Server is not blacklisted
< Server: Couchbase Server
< Pragma: no-cache
< Date: Wed, 25 Nov 2015 22:48:16 GMT
< Content-Length: 0
< Cache-Control: no-cache
< 
* Connection #0 to host 192.168.99.100 left intact

curl -v -X POST http://192.168.99.100:8091/pools/default -d memoryQuota=300 -d indexMemoryQuota=300

* Hostname was NOT found in DNS cache

* Trying 192.168.99.100...

* Connected to 192.168.99.100 (192.168.99.100) port 8091 (#0)

> POST /pools/default HTTP/1.1

> User-Agent: curl/7.37.1

> Host: 192.168.99.100:8091

> Accept: */*

> Content-Length: 36

> Content-Type: application/x-www-form-urlencoded

* upload completely sent off: 36 out of 36 bytes

< HTTP/1.1 401 Unauthorized

< WWW-Authenticate: Basic realm="Couchbase Server Admin / REST"

* Server Couchbase Server is not blacklisted

< Server: Couchbase Server

< Pragma: no-cache

< Date: Wed, 25 Nov 2015 22:48:16 GMT

< Content-Length: 0

< Cache-Control: no-cache

* Connection #0 to host 192.168.99.100 left intact

Configure Data, Query, and Index services:

curl -v http://192.168.99.100:8091/node/controller/setupServices -d 'services=kv%2Cn1ql%2Cindex'
* Hostname was NOT found in DNS cache
*   Trying 192.168.99.100...
* Connected to 192.168.99.100 (192.168.99.100) port 8091 (#0)
> POST /node/controller/setupServices HTTP/1.1
> User-Agent: curl/7.37.1
> Host: 192.168.99.100:8091
> Accept: */*
> Content-Length: 26
> Content-Type: application/x-www-form-urlencoded
> 
* upload completely sent off: 26 out of 26 bytes
< HTTP/1.1 200 OK
* Server Couchbase Server is not blacklisted
< Server: Couchbase Server
< Pragma: no-cache
< Date: Wed, 25 Nov 2015 22:49:51 GMT
< Content-Length: 0
< Cache-Control: no-cache
< 
* Connection #0 to host 192.168.99.100 left intact

curl -v http://192.168.99.100:8091/node/controller/setupServices -d 'services=kv%2Cn1ql%2Cindex'

* Hostname was NOT found in DNS cache

* Trying 192.168.99.100...

* Connected to 192.168.99.100 (192.168.99.100) port 8091 (#0)

> POST /node/controller/setupServices HTTP/1.1

> User-Agent: curl/7.37.1

> Host: 192.168.99.100:8091

> Accept: */*

> Content-Length: 26

> Content-Type: application/x-www-form-urlencoded

* upload completely sent off: 26 out of 26 bytes

< HTTP/1.1 200 OK

* Server Couchbase Server is not blacklisted

< Server: Couchbase Server

< Pragma: no-cache

< Date: Wed, 25 Nov 2015 22:49:51 GMT

< Content-Length: 0

< Cache-Control: no-cache

* Connection #0 to host 192.168.99.100 left intact

Setup credentials for the cluster:

curl -v -X POST http://192.168.99.100:8091/settings/web -d port=8091 -d username=Administrator -d password=password
* Hostname was NOT found in DNS cache
*   Trying 192.168.99.100...
* Connected to 192.168.99.100 (192.168.99.100) port 8091 (#0)
> POST /settings/web HTTP/1.1
> User-Agent: curl/7.37.1
> Host: 192.168.99.100:8091
> Accept: */*
> Content-Length: 50
> Content-Type: application/x-www-form-urlencoded
> 
* upload completely sent off: 50 out of 50 bytes
< HTTP/1.1 200 OK
* Server Couchbase Server is not blacklisted
< Server: Couchbase Server
< Pragma: no-cache
< Date: Wed, 25 Nov 2015 22:50:43 GMT
< Content-Type: application/json
< Content-Length: 44
< Cache-Control: no-cache
< 
* Connection #0 to host 192.168.99.100 left intact
{"newBaseUri":"http://192.168.99.100:8091/"}

curl -v -X POST http://192.168.99.100:8091/settings/web -d port=8091 -d username=Administrator -d password=password

* Hostname was NOT found in DNS cache

* Trying 192.168.99.100...

* Connected to 192.168.99.100 (192.168.99.100) port 8091 (#0)

> POST /settings/web HTTP/1.1

> User-Agent: curl/7.37.1

> Host: 192.168.99.100:8091

> Accept: */*

> Content-Length: 50

> Content-Type: application/x-www-form-urlencoded

* upload completely sent off: 50 out of 50 bytes

< HTTP/1.1 200 OK

* Server Couchbase Server is not blacklisted

< Server: Couchbase Server

< Pragma: no-cache

< Date: Wed, 25 Nov 2015 22:50:43 GMT

< Content-Type: application/json

< Content-Length: 44

< Cache-Control: no-cache

* Connection #0 to host 192.168.99.100 left intact

{"newBaseUri":"http://192.168.99.100:8091/"}

Install Couchbase Travel Sample Bucket

curl -v -u Administrator:password -X POST http://192.168.99.100:8091/sampleBuckets/install -d '["travel-sample"]'
* Hostname was NOT found in DNS cache
*   Trying 192.168.99.100...
* Connected to 192.168.99.100 (192.168.99.100) port 8091 (#0)
* Server auth using Basic with user 'Administrator'
> POST /sampleBuckets/install HTTP/1.1
> Authorization: Basic QWRtaW5pc3RyYXRvcjpwYXNzd29yZA==
> User-Agent: curl/7.37.1
> Host: 192.168.99.100:8091
> Accept: */*
> Content-Length: 17
> Content-Type: application/x-www-form-urlencoded
> 
* upload completely sent off: 17 out of 17 bytes
< HTTP/1.1 202 Accepted
* Server Couchbase Server is not blacklisted
< Server: Couchbase Server
< Pragma: no-cache
< Date: Wed, 25 Nov 2015 22:51:51 GMT
< Content-Type: application/json
< Content-Length: 2
< Cache-Control: no-cache
< 
* Connection #0 to host 192.168.99.100 left intact
[]

curl -v -u Administrator:password -X POST http://192.168.99.100:8091/sampleBuckets/install -d '["travel-sample"]'

* Hostname was NOT found in DNS cache

* Trying 192.168.99.100...

* Connected to 192.168.99.100 (192.168.99.100) port 8091 (#0)

* Server auth using Basic with user 'Administrator'

> POST /sampleBuckets/install HTTP/1.1

> Authorization: Basic QWRtaW5pc3RyYXRvcjpwYXNzd29yZA==

> User-Agent: curl/7.37.1

> Host: 192.168.99.100:8091

> Accept: */*

> Content-Length: 17

> Content-Type: application/x-www-form-urlencoded

* upload completely sent off: 17 out of 17 bytes

< HTTP/1.1 202 Accepted

* Server Couchbase Server is not blacklisted

< Server: Couchbase Server

< Pragma: no-cache

< Date: Wed, 25 Nov 2015 22:51:51 GMT

< Content-Type: application/json

< Content-Length: 2

< Cache-Control: no-cache

* Connection #0 to host 192.168.99.100 left intact

[]

Query Couchbase Docker Container using CBQ

List container id of Couchbase server:

docker ps
CONTAINER ID        IMAGE               COMMAND                  CREATED             STATUS              PORTS                                                                                               NAMES
e54a9849ba35        couchbase/server    "/entrypoint.sh couch"   3 minutes ago       Up 3 minutes        0.0.0.0:8091-8093->8091-8093/tcp, 11207/tcp, 11211/tcp, 18091-18092/tcp, 0.0.0.0:11210->11210/tcp   couchbaseserver_mycouchbase_1

docker ps

CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES

e54a9849ba35 couchbase/server "/entrypoint.sh couch" 3 minutes ago Up 3 minutes 0.0.0.0:8091-8093->8091-8093/tcp, 11207/tcp, 11211/tcp, 18091-18092/tcp, 0.0.0.0:11210->11210/tcp couchbaseserver_mycouchbase_1

This output shows the complete information about the container. Alternatively, just the container id can be obtained as:

docker ps | grep couch | awk '{print $1}'
e54a9849ba35

docker ps | grep couch | awk '{print $1}'

e54a9849ba35

Run Couchbase Query tool:

docker exec -it e5 /opt/couchbase/bin/cbq
Couchbase query shell connected to http://localhost:8093/ . Type Ctrl-D to exit.
cbq>

docker exec -it e5 /opt/couchbase/bin/cbq

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

cbq>

Run a query:

cbq> select * from `travel-sample` limit 1;
{
    "requestID": "9b354cc0-371c-4126-84a2-dea302312b79",
    "signature": {
        "*": "*"
    },
    "results": [
        {
            "travel-sample": {
                "callsign": "AIRFRANS",
                "country": "France",
                "iata": "AF",
                "icao": "AFR",
                "id": 137,
                "name": "Air France",
                "type": "airline"
            }
        }
    ],
    "status": "success",
    "metrics": {
        "elapsedTime": "48.080992ms",
        "executionTime": "47.950777ms",
        "resultCount": 1,
        "resultSize": 293
    }
}

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

{

"requestID": "9b354cc0-371c-4126-84a2-dea302312b79",

"signature": {

"*": "*"

"results": [

{

"travel-sample": {

"callsign": "AIRFRANS",

"country": "France",

"iata": "AF",

"icao": "AFR",

"id": 137,

"name": "Air France",

"type": "airline"

}

"status": "success",

"metrics": {

"elapsedTime": "48.080992ms",

"executionTime": "47.950777ms",

"resultCount": 1,

"resultSize": 293

}

Did you realize, this was a SQL query for JSON document? How cool. Learn more about in this interactive N1QL tutorial.

Cluster overview can be seen at 192.168.99.100:8091:

Data buckets can seen as:

Ask your questions at forums.couchbase.com, learn more about Couchbase REST API or read more in Couchbase 4 Docs.

A subsequent blog will show how all of these steps can be fully automated.

Enjoy!

Attach Shell to Docker container

November 19, 2015containers, couchbasecouchbase, dockerarungupta

Often there is a need to attach a shell to an already running Docker container. This is very useful, especially for debugging. This blog will explain how to attach a shell to an already running Docker container.

So let’s say you run a Couchbase Docker container in detached mode:

> docker run -d couchbase/server
02061ddf0a3d1b2806a1ee6e354f4064d9d2ff4d84d8c96c0273c8883917a92f

> docker run -d couchbase/server

02061ddf0a3d1b2806a1ee6e354f4064d9d2ff4d84d8c96c0273c8883917a92f

Running the container gives you the complete container id, 02061ddf0a3d1b2806a1ee6e354f4064d9d2ff4d84d8c96c0273c8883917a92f in this case.

This can be verified as:

> docker ps
CONTAINER ID        IMAGE               COMMAND                  CREATED             STATUS              PORTS                                                        NAMES
02061ddf0a3d        couchbase/server    "/entrypoint.sh couch"   38 seconds ago      Up 37 seconds       8091-8093/tcp, 11207/tcp, 11210-11211/tcp, 18091-18092/tcp   clever_hypatia

> docker ps

CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES

02061ddf0a3d couchbase/server "/entrypoint.sh couch" 38 seconds ago Up 37 seconds 8091-8093/tcp, 11207/tcp, 11210-11211/tcp, 18091-18092/tcp clever_hypatia

Or complete container id can be verified as:

> docker ps --no-trunc
CONTAINER ID                                                       IMAGE               COMMAND                             CREATED              STATUS              PORTS                                                        NAMES
02061ddf0a3d1b2806a1ee6e354f4064d9d2ff4d84d8c96c0273c8883917a92f   couchbase/server    "/entrypoint.sh couchbase-server"   About a minute ago   Up 59 seconds       8091-8093/tcp, 11207/tcp, 11210-11211/tcp, 18091-18092/tcp   clever_hypatia

> docker ps --no-trunc

CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES

02061ddf0a3d1b2806a1ee6e354f4064d9d2ff4d84d8c96c0273c8883917a92f couchbase/server "/entrypoint.sh couchbase-server" About a minute ago Up 59 seconds 8091-8093/tcp, 11207/tcp, 11210-11211/tcp, 18091-18092/tcp clever_hypatia

Attach Shell to Docker Container

Bash shell can be attached to an already running container using docker exec -it {CID} bash. The {CID} can be the complete container id, truncated container id, or even the first few digits of the container ids amongst all the currently running containers.

So the following three commands are equivalent in our case:

Attach Using Complete Container Id

> docker exec -it 02061ddf0a3d1b2806a1ee6e354f4064d9d2ff4d84d8c96c0273c8883917a92f bash
root@02061ddf0a3d:/#

> docker exec -it 02061ddf0a3d1b2806a1ee6e354f4064d9d2ff4d84d8c96c0273c8883917a92f bash

root@02061ddf0a3d:/#

Attach Using Truncated Container Id

> docker exec -it 02061ddf0a3d bash
root@02061ddf0a3d:/#

> docker exec -it 02061ddf0a3d bash

root@02061ddf0a3d:/#

Attach Using Unique Numbers from Container Id

> docker exec -it 0 bash
root@02061ddf0a3d:/#

> docker exec -it 0 bash

root@02061ddf0a3d:/#

In this case, just specifying 0 would work because this is the only running container. If multiple containers are running that have 0 as the starting number then the first few digits that make the container id unique are required.

Enjoy!

CRUD Java Application with Couchbase, Java EE and WildFly

November 18, 2015containers, couchbase, javaee, wildflycouchbase, crud, docker, javaee, wildflyarungupta

Couchbase is an open-source, NoSQL, document database. It allows to access, index, and query JSON documents while taking advantage of integrated distributed caching for high performance data access.

REST with Couchbase

The application will use curl to issue REST commands to a JAX-RS endpoint deployed on WildFly. These commands will then perform CRUD operations on travel-sample bucket in Couchbase. N1QL (SQL query language for JSON) will be used to communicate with Couchbase to retrieve results. Both the “builder pattern” and raw N1QL commands will be used.

TL;DR

Complete source code and instructions for the sample are available at github.com/arun-gupta/couchbase-javaee.

Lets get started!

Run Couchbase Server

Couchbase server can be easily downloaded from Couchbase Server Downloads page. In a containerized world, its a lot easier to fire up a Couchbase server using Docker.

If Docker is configured on your machine then the easiest way is to use Docker Compose for Couchbase:

mycouchbase:
  name: mycouchbase
  image: couchbase/server
  volumes:
    - ~/couchbase:/opt/couchbase/var
  ports:
    - 8091:8091
    - 8092:8092 
    - 8093:8093 
    - 11210:11210

mycouchbase:

name: mycouchbase

image: couchbase/server

volumes:

- ~/couchbase:/opt/couchbase/var

ports:

- 8091:8091

- 8092:8092

- 8093:8093

- 11210:11210

Starting up the application server shows:

> docker-compose up -d
Creating couchbaseserver_mycouchbase_1

> docker-compose up -d

Creating couchbaseserver_mycouchbase_1

And then the logs can be seen as:

> docker-compose logs
Attaching to couchbaseserver_mycouchbase_1
mycouchbase_1 | Starting Couchbase Server -- Web UI available at http://<ip>:8091

> docker-compose logs

Attaching to couchbaseserver_mycouchbase_1

mycouchbase_1 | Starting Couchbase Server -- Web UI available at http://<ip>:8091

The database needs to be configured and is explained at Configure Couchbase Server. Make sure to install travel-sample bucket.

Deploy the Java EE Application on WildFly

Download WildFly 9.0.2 , unzip, and start WildFly application server as ./wildfly-9.0.0.Final/bin/standalone.sh.
Git clone the repo: git clone https://github.com/arun-gupta/couchbase-javaee.git
Change directory cd couchbase-javaee
Deploy the application to WildFly: mvn install -Pwildfly.

The application uses Java SDK for Couchbase by importing the following Maven coordinates:

<dependency>
    <groupId>com.couchbase.client</groupId>
    <artifactId>java-client</artifactId>
    <version>2.2.1</version>
</dependency>

<groupId>com.couchbase.client</groupId>

<artifactId>java-client</artifactId>

</dependency>

Invoke the REST Endpoints Using cURL

GET Airline resources (limit to 10)

Lets query the database to list 10 Airline resources.

Request

~ > curl -v http://localhost:8080/couchbase-javaee/resources/airline
* Hostname was NOT found in DNS cache
*   Trying ::1...
* connect to ::1 port 8080 failed: Connection refused
*   Trying 127.0.0.1...
* Connected to localhost (127.0.0.1) port 8080 (#0)
> GET /couchbase-javaee/resources/airline HTTP/1.1
> User-Agent: curl/7.37.1
> Host: localhost:8080
> Accept: */*
>

~ > curl -v http://localhost:8080/couchbase-javaee/resources/airline

* Hostname was NOT found in DNS cache

* Trying ::1...

* connect to ::1 port 8080 failed: Connection refused

* Trying 127.0.0.1...

* Connected to localhost (127.0.0.1) port 8080 (#0)

> GET /couchbase-javaee/resources/airline HTTP/1.1

> User-Agent: curl/7.37.1

> Host: localhost:8080

> Accept: */*

Response

< HTTP/1.1 200 OK
< Connection: keep-alive
< X-Powered-By: Undertow/1
* Server WildFly/9 is not blacklisted
< Server: WildFly/9
< Content-Type: application/octet-stream
< Content-Length: 1415
< Date: Wed, 18 Nov 2015 21:19:15 GMT
< 
* Connection #0 to host localhost left intact
[{"travel-sample":{"country":"France","iata":"SB","callsign":"AIRCALIN","name":"Air Caledonie International","icao":"ACI","id":139,"type":"airline"}}, {"travel-sample":{"country":"United States","iata":"WQ","callsign":null,"name":"PanAm World Airways","icao":"PQW","id":13633,"type":"airline"}}, {"travel-sample":{"country":"United Kingdom","iata":"BA","callsign":"SPEEDBIRD","name":"British Airways","icao":"BAW","id":1355,"type":"airline"}}, {"travel-sample":{"country":"United States","iata":"FL","callsign":"CITRUS","name":"AirTran Airways","icao":"TRS","id":1316,"type":"airline"}}, {"travel-sample":{"country":"United States","iata":"-+","callsign":null,"name":"U.S. Air","icao":"--+","id":13391,"type":"airline"}}, {"travel-sample":{"country":"United States","iata":"Q5","callsign":"MILE-AIR","name":"40-Mile Air","icao":"MLA","id":10,"type":"airline"}}, {"travel-sample":{"country":"France","iata":"AF","callsign":"AIRFRANS","name":"Air France","icao":"AFR","id":137,"type":"airline"}}, {"travel-sample":{"country":"United States","iata":"K5","callsign":"SASQUATCH","name":"SeaPort Airlines","icao":"SQH","id":10765,"type":"airline"}}, {"travel-sample":{"country":"France","iata":"A5","callsign":"AIRLINAIR","name":"Airlinair","icao":"RLA","id":1203,"type":"airline"}}, {"travel-sample":{"country":"United Kingdom","iata":"5W","callsign":"FLYSTAR","name":"Astraeus","icao":"AEU","id":112,"type":"airline"}}]

< HTTP/1.1 200 OK

< Connection: keep-alive

< X-Powered-By: Undertow/1

* Server WildFly/9 is not blacklisted

< Server: WildFly/9

< Content-Type: application/octet-stream

< Content-Length: 1415

< Date: Wed, 18 Nov 2015 21:19:15 GMT

* Connection #0 to host localhost left intact

[{"travel-sample":{"country":"France","iata":"SB","callsign":"AIRCALIN","name":"Air Caledonie International","icao":"ACI","id":139,"type":"airline"}}, {"travel-sample":{"country":"United States","iata":"WQ","callsign":null,"name":"PanAm World Airways","icao":"PQW","id":13633,"type":"airline"}}, {"travel-sample":{"country":"United Kingdom","iata":"BA","callsign":"SPEEDBIRD","name":"British Airways","icao":"BAW","id":1355,"type":"airline"}}, {"travel-sample":{"country":"United States","iata":"FL","callsign":"CITRUS","name":"AirTran Airways","icao":"TRS","id":1316,"type":"airline"}}, {"travel-sample":{"country":"United States","iata":"-+","callsign":null,"name":"U.S. Air","icao":"--+","id":13391,"type":"airline"}}, {"travel-sample":{"country":"United States","iata":"Q5","callsign":"MILE-AIR","name":"40-Mile Air","icao":"MLA","id":10,"type":"airline"}}, {"travel-sample":{"country":"France","iata":"AF","callsign":"AIRFRANS","name":"Air France","icao":"AFR","id":137,"type":"airline"}}, {"travel-sample":{"country":"United States","iata":"K5","callsign":"SASQUATCH","name":"SeaPort Airlines","icao":"SQH","id":10765,"type":"airline"}}, {"travel-sample":{"country":"France","iata":"A5","callsign":"AIRLINAIR","name":"Airlinair","icao":"RLA","id":1203,"type":"airline"}}, {"travel-sample":{"country":"United Kingdom","iata":"5W","callsign":"FLYSTAR","name":"Astraeus","icao":"AEU","id":112,"type":"airline"}}]

The N1QL query for this is written as:

N1qlQuery query = N1qlQuery
                .simple(select("*")
                .from(i(database.getBucket().name()))
                .limit(10));

N1qlQuery query = N1qlQuery

.simple(select("*")

.from(i(database.getBucket().name()))

.limit(10));

And can also be alternatively written as:

SELECT * FROM `travel-sample` LIMIT 10

SELECT * FROM `travel-sample` LIMIT 10

You may optionally update the code to include ORDER BY clause as shown in N1QL Tutorial.

GET one Airline resource

Use id attribute to query a single Airline resource

Request

~ > curl -v http://localhost:8080/couchbase-javaee/resources/airline/139
* Hostname was NOT found in DNS cache
*   Trying ::1...
* connect to ::1 port 8080 failed: Connection refused
*   Trying 127.0.0.1...
* Connected to localhost (127.0.0.1) port 8080 (#0)
> GET /couchbase-javaee/resources/airline/139 HTTP/1.1
> User-Agent: curl/7.37.1
> Host: localhost:8080
> Accept: */*
>

~ > curl -v http://localhost:8080/couchbase-javaee/resources/airline/139

* Hostname was NOT found in DNS cache

* Trying ::1...

* connect to ::1 port 8080 failed: Connection refused

* Trying 127.0.0.1...

* Connected to localhost (127.0.0.1) port 8080 (#0)

> GET /couchbase-javaee/resources/airline/139 HTTP/1.1

> User-Agent: curl/7.37.1

> Host: localhost:8080

> Accept: */*

Response

< HTTP/1.1 200 OK
< Connection: keep-alive
< X-Powered-By: Undertow/1
* Server WildFly/9 is not blacklisted
< Server: WildFly/9
< Content-Type: application/octet-stream
< Content-Length: 148
< Date: Wed, 18 Nov 2015 21:23:34 GMT
< 
* Connection #0 to host localhost left intact
{"travel-sample":{"country":"France","iata":"SB","callsign":"AIRCALIN","name":"Air Caledonie International","icao":"ACI","id":139,"type":"airline"}}

< HTTP/1.1 200 OK

< Connection: keep-alive

< X-Powered-By: Undertow/1

* Server WildFly/9 is not blacklisted

< Server: WildFly/9

< Content-Type: application/octet-stream

< Content-Length: 148

< Date: Wed, 18 Nov 2015 21:23:34 GMT

* Connection #0 to host localhost left intact

{"travel-sample":{"country":"France","iata":"SB","callsign":"AIRCALIN","name":"Air Caledonie International","icao":"ACI","id":139,"type":"airline"}}

POST a new Airline resource

Learn how to run N1QL queries from the CLI using CBQ tool and verify the existing sample data:

bin > ./cbq -engine=http://192.168.99.100:8093
Couchbase query shell connected to http://192.168.99.100:8093/ . Type Ctrl-D to exit.
cbq> select * from `travel-sample` where name="Airlinair" limit 10;
{
    "requestID": "ce2de67b-2c05-47df-afbe-343cb7409d2b",
    "signature": {
        "*": "*"
    },
    "results": [
        {
            "travel-sample": {
                "callsign": "AIRLINAIR",
                "country": "France",
                "iata": "A5",
                "icao": "RLA",
                "id": 1203,
                "name": "Airlinair",
                "type": "airline"
            }
        }
    ],
    "status": "success",
    "metrics": {
        "elapsedTime": "3.418285894s",
        "executionTime": "3.418232688s",
        "resultCount": 1,
        "resultSize": 294
    }
}

bin > ./cbq -engine=http://192.168.99.100:8093

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

cbq> select * from `travel-sample` where name="Airlinair" limit 10;

{

"requestID": "ce2de67b-2c05-47df-afbe-343cb7409d2b",

"signature": {

"*": "*"

"results": [

{

"travel-sample": {

"callsign": "AIRLINAIR",

"country": "France",

"iata": "A5",

"icao": "RLA",

"id": 1203,

"name": "Airlinair",

"type": "airline"

}

"status": "success",

"metrics": {

"elapsedTime": "3.418285894s",

"executionTime": "3.418232688s",

"resultCount": 1,

"resultSize": 294

}

This query retrieve documents where airline’s name is Airlinair. The count is shown in metrics.resultCount.

Create a new document using POST.

Request

~ > curl -v -H "Content-Type: application/json" -X POST -d '{"country":"France","iata":"A5","callsign":"AIRLINAIR","name":"Airlinair","icao":"RLA","type":"airline"}' http://localhost:8080/couchbase-javaee/resources/airline
* Hostname was NOT found in DNS cache
*   Trying ::1...
* connect to ::1 port 8080 failed: Connection refused
*   Trying 127.0.0.1...
* Connected to localhost (127.0.0.1) port 8080 (#0)
> POST /couchbase-javaee/resources/airline HTTP/1.1
> User-Agent: curl/7.37.1
> Host: localhost:8080
> Accept: */*
> Content-Type: application/json
> Content-Length: 104
>

~ > curl -v -H "Content-Type: application/json" -X POST -d '{"country":"France","iata":"A5","callsign":"AIRLINAIR","name":"Airlinair","icao":"RLA","type":"airline"}' http://localhost:8080/couchbase-javaee/resources/airline

* Hostname was NOT found in DNS cache

* Trying ::1...

* connect to ::1 port 8080 failed: Connection refused

* Trying 127.0.0.1...

* Connected to localhost (127.0.0.1) port 8080 (#0)

> POST /couchbase-javaee/resources/airline HTTP/1.1

> User-Agent: curl/7.37.1

> Host: localhost:8080

> Accept: */*

> Content-Type: application/json

> Content-Length: 104

Response

* upload completely sent off: 104 out of 104 bytes
< HTTP/1.1 200 OK
< Connection: keep-alive
< X-Powered-By: Undertow/1
* Server WildFly/9 is not blacklisted
< Server: WildFly/9
< Content-Type: application/octet-stream
< Content-Length: 117
< Date: Wed, 18 Nov 2015 21:42:51 GMT
< 
* Connection #0 to host localhost left intact
{"country":"France","iata":"A5","callsign":"AIRLINAIR","name":"Airlinair","icao":"RLA","id":"19810","type":"airline"}

* upload completely sent off: 104 out of 104 bytes

< HTTP/1.1 200 OK

< Connection: keep-alive

< X-Powered-By: Undertow/1

* Server WildFly/9 is not blacklisted

< Server: WildFly/9

< Content-Type: application/octet-stream

< Content-Length: 117

< Date: Wed, 18 Nov 2015 21:42:51 GMT

* Connection #0 to host localhost left intact

{"country":"France","iata":"A5","callsign":"AIRLINAIR","name":"Airlinair","icao":"RLA","id":"19810","type":"airline"}

Query again using CBQ and now the results are shown as:

cbq> select * from `travel-sample` where name="Airlinair" limit 10;
{
    "requestID": "5e79031a-f7ee-4cc9-8c87-4e3b7484f09f",
    "signature": {
        "*": "*"
    },
    "results": [
        {
            "travel-sample": {
                "callsign": "AIRLINAIR",
                "country": "France",
                "iata": "A5",
                "icao": "RLA",
                "id": 1203,
                "name": "Airlinair",
                "type": "airline"
            }
        },
        {
            "travel-sample": {
                "callsign": "AIRLINAIR",
                "country": "France",
                "iata": "A5",
                "icao": "RLA",
                "id": "19810",
                "name": "Airlinair",
                "type": "airline"
            }
        }
    ],
    "status": "success",
    "metrics": {
        "elapsedTime": "3.342391947s",
        "executionTime": "3.342343455s",
        "resultCount": 2,
        "resultSize": 591
    }
}

cbq> select * from `travel-sample` where name="Airlinair" limit 10;

{

"requestID": "5e79031a-f7ee-4cc9-8c87-4e3b7484f09f",

"signature": {

"*": "*"

"results": [

{

"travel-sample": {

"callsign": "AIRLINAIR",

"country": "France",

"iata": "A5",

"icao": "RLA",

"id": 1203,

"name": "Airlinair",

"type": "airline"

}

{

"travel-sample": {

"callsign": "AIRLINAIR",

"country": "France",

"iata": "A5",

"icao": "RLA",

"id": "19810",

"name": "Airlinair",

"type": "airline"

}

"status": "success",

"metrics": {

"elapsedTime": "3.342391947s",

"executionTime": "3.342343455s",

"resultCount": 2,

"resultSize": 591

}

Note that two JSON documents are returned instead of one as before the POST command was issued.

PUT an existing Airline resource

Update an existing resource using HTTP POST.

The data model for travel-sample bucket requires to include “id” attribute in the payload and in the URI as well.

Request

~ > curl -v -H "Content-Type: application/json" -X PUT -d '{"country":"France","iata":"A5","callsign":"AIRLINAIR","name":"Airlin Air","icao":"RLA","type":"airline","id": "19810"}' http://localhost:8080/couchbase-javaee/resources/airline/19810
* Hostname was NOT found in DNS cache
*   Trying ::1...
* connect to ::1 port 8080 failed: Connection refused
*   Trying 127.0.0.1...
* Connected to localhost (127.0.0.1) port 8080 (#0)
> PUT /couchbase-javaee/resources/airline/19810 HTTP/1.1
> User-Agent: curl/7.37.1
> Host: localhost:8080
> Accept: */*
> Content-Type: application/json
> Content-Length: 118
> 
* upload completely sent off: 118 out of 118 bytes

~ > curl -v -H "Content-Type: application/json" -X PUT -d '{"country":"France","iata":"A5","callsign":"AIRLINAIR","name":"Airlin Air","icao":"RLA","type":"airline","id": "19810"}' http://localhost:8080/couchbase-javaee/resources/airline/19810

* Hostname was NOT found in DNS cache

* Trying ::1...

* connect to ::1 port 8080 failed: Connection refused

* Trying 127.0.0.1...

* Connected to localhost (127.0.0.1) port 8080 (#0)

> PUT /couchbase-javaee/resources/airline/19810 HTTP/1.1

> User-Agent: curl/7.37.1

> Host: localhost:8080

> Accept: */*

> Content-Type: application/json

> Content-Length: 118

* upload completely sent off: 118 out of 118 bytes

Name of the airline is updated from “Airlinair” to “Airlin Air”, all other attributes stay the same.

Response

< HTTP/1.1 200 OK
< Connection: keep-alive
< X-Powered-By: Undertow/1
* Server WildFly/9 is not blacklisted
< Server: WildFly/9
< Content-Type: application/octet-stream
< Content-Length: 117
< Date: Wed, 18 Nov 2015 21:46:16 GMT
< 
* Connection #0 to host localhost left intact
{"country":"France","iata":"A5","callsign":"AIRLINAIR","name":"Airlin Air","icao":"RLA","id":"19810","type":"airline"}

< HTTP/1.1 200 OK

< Connection: keep-alive

< X-Powered-By: Undertow/1

* Server WildFly/9 is not blacklisted

< Server: WildFly/9

< Content-Type: application/octet-stream

< Content-Length: 117

< Date: Wed, 18 Nov 2015 21:46:16 GMT

* Connection #0 to host localhost left intact

{"country":"France","iata":"A5","callsign":"AIRLINAIR","name":"Airlin Air","icao":"RLA","id":"19810","type":"airline"}

The updated record is shown in the response.

Querying for Airlinair gives:

cbq> select * from `travel-sample` where name="Airlinair" limit 10;
{
    "requestID": "a8d72427-9f4b-49ab-a77a-17cd99cdce5f",
    "signature": {
        "*": "*"
    },
    "results": [
        {
            "travel-sample": {
                "callsign": "AIRLINAIR",
                "country": "France",
                "iata": "A5",
                "icao": "RLA",
                "id": 1203,
                "name": "Airlinair",
                "type": "airline"
            }
        }
    ],
    "status": "success",
    "metrics": {
        "elapsedTime": "3.372603693s",
        "executionTime": "3.37256091s",
        "resultCount": 1,
        "resultSize": 294
    }
}

cbq> select * from `travel-sample` where name="Airlinair" limit 10;

{

"requestID": "a8d72427-9f4b-49ab-a77a-17cd99cdce5f",

"signature": {

"*": "*"

"results": [

{

"travel-sample": {

"callsign": "AIRLINAIR",

"country": "France",

"iata": "A5",

"icao": "RLA",

"id": 1203,

"name": "Airlinair",

"type": "airline"

}

"status": "success",

"metrics": {

"elapsedTime": "3.372603693s",

"executionTime": "3.37256091s",

"resultCount": 1,

"resultSize": 294

}

So the previously added record is now updated and thus does not appear in query results. Querying for Airlin Airgives:

cbq> select * from `travel-sample` where name="Airlin Air" limit 10;
{
    "requestID": "a3797a73-d879-4ca1-be90-e07179aae118",
    "signature": {
        "*": "*"
    },
    "results": [
        {
            "travel-sample": {
                "callsign": "AIRLINAIR",
                "country": "France",
                "iata": "A5",
                "icao": "RLA",
                "id": "19810",
                "name": "Airlin Air",
                "type": "airline"
            }
        }
    ],
    "status": "success",
    "metrics": {
        "elapsedTime": "3.393649025s",
        "executionTime": "3.393530368s",
        "resultCount": 1,
        "resultSize": 298
    }
}

cbq> select * from `travel-sample` where name="Airlin Air" limit 10;

{

"requestID": "a3797a73-d879-4ca1-be90-e07179aae118",

"signature": {

"*": "*"

"results": [

{

"travel-sample": {

"callsign": "AIRLINAIR",

"country": "France",

"iata": "A5",

"icao": "RLA",

"id": "19810",

"name": "Airlin Air",

"type": "airline"

}

"status": "success",

"metrics": {

"elapsedTime": "3.393649025s",

"executionTime": "3.393530368s",

"resultCount": 1,

"resultSize": 298

}

This shows the newly updated document.

DELETE an existing Airline resource

Query for a unique id:

cbq> select * from `travel-sample` where id="19810" limit 10;
{
    "requestID": "47a315cd-afe4-45a8-8814-5ab3034e0d0f",
    "signature": {
        "*": "*"
    },
    "results": [
        {
            "travel-sample": {
                "callsign": "AIRLINAIR",
                "country": "France",
                "iata": "A5",
                "icao": "RLA",
                "id": "19810",
                "name": "Airlin Air",
                "type": "airline"
            }
        }
    ],
    "status": "success",
    "metrics": {
        "elapsedTime": "3.006863656s",
        "executionTime": "3.006821997s",
        "resultCount": 1,
        "resultSize": 298
    }
}

cbq> select * from `travel-sample` where id="19810" limit 10;

{

"requestID": "47a315cd-afe4-45a8-8814-5ab3034e0d0f",

"signature": {

"*": "*"

"results": [

{

"travel-sample": {

"callsign": "AIRLINAIR",

"country": "France",

"iata": "A5",

"icao": "RLA",

"id": "19810",

"name": "Airlin Air",

"type": "airline"

}

"status": "success",

"metrics": {

"elapsedTime": "3.006863656s",

"executionTime": "3.006821997s",

"resultCount": 1,

"resultSize": 298

}

Notice that one document is returned.

Lets delete this document.

Request

~ > curl -v -X DELETE http://localhost:8080/couchbase-javaee/resources/airline/19810
* Hostname was NOT found in DNS cache
*   Trying ::1...
* connect to ::1 port 8080 failed: Connection refused
*   Trying 127.0.0.1...
* Connected to localhost (127.0.0.1) port 8080 (#0)
> DELETE /couchbase-javaee/resources/airline/19810 HTTP/1.1
> User-Agent: curl/7.37.1
> Host: localhost:8080
> Accept: */*
>

~ > curl -v -X DELETE http://localhost:8080/couchbase-javaee/resources/airline/19810

* Hostname was NOT found in DNS cache

* Trying ::1...

* connect to ::1 port 8080 failed: Connection refused

* Trying 127.0.0.1...

* Connected to localhost (127.0.0.1) port 8080 (#0)

> DELETE /couchbase-javaee/resources/airline/19810 HTTP/1.1

> User-Agent: curl/7.37.1

> Host: localhost:8080

> Accept: */*

Response

< HTTP/1.1 200 OK
< Connection: keep-alive
< X-Powered-By: Undertow/1
* Server WildFly/9 is not blacklisted
< Server: WildFly/9
< Content-Type: application/octet-stream
< Content-Length: 136
< Date: Wed, 18 Nov 2015 21:52:47 GMT
< 
* Connection #0 to host localhost left intact
{"travel-sample":{"country":"France","iata":"A5","callsign":"AIRLINAIR","name":"Airlin Air","icao":"RLA","id":"19810","type":"airline"}}

< HTTP/1.1 200 OK

< Connection: keep-alive

< X-Powered-By: Undertow/1

* Server WildFly/9 is not blacklisted

< Server: WildFly/9

< Content-Type: application/octet-stream

< Content-Length: 136

< Date: Wed, 18 Nov 2015 21:52:47 GMT

* Connection #0 to host localhost left intact

{"travel-sample":{"country":"France","iata":"A5","callsign":"AIRLINAIR","name":"Airlin Air","icao":"RLA","id":"19810","type":"airline"}}

The deleted document is shown in the response.

Query again for the deleted id:

cbq> select * from `travel-sample` where id="19810" limit 10;
{
    "requestID": "972b0bbd-ba25-4f6c-a30e-ed188bf43588",
    "signature": {
        "*": "*"
    },
    "results": [
    ],
    "status": "success",
    "metrics": {
        "elapsedTime": "3.261481199s",
        "executionTime": "3.261431917s",
        "resultCount": 0,
        "resultSize": 0
    }
}

cbq> select * from `travel-sample` where id="19810" limit 10;

{

"requestID": "972b0bbd-ba25-4f6c-a30e-ed188bf43588",

"signature": {

"*": "*"

"results": [

"status": "success",

"metrics": {

"elapsedTime": "3.261481199s",

"executionTime": "3.261431917s",

"resultCount": 0,

"resultSize": 0

}

And no results are returned!

As mentioned earlier, the complete code base is at github.com/arun-gupta/couchbase-javaee.

Enjoy!

Docker, Kubernetes, and Microservices Replay from Devoxx 2015

November 12, 2015conferences, containers, microservicesdevoxx, docker, kubernetes, microservicesarungupta

Devoxx 2015 BE Arun

Java gives us Write Once Run Anywhere (WORA) because of the common abstraction provided by Java Virtual Machine. The binary byte code produced by Java is understood by the JVM running on multiple operating systems. This allows Java code to run on any operating system. But deploying such applications typically requires to tune the JVM, setup application server, install appropriate database drivers, other similar configuration. Docker nicely complements WORA by defining a way to package Java applications, and include all the configuration in a an easy to describe format. This can be called as Package Once Deploy Anywhere, or PODA.

Do you want to learn more about how Docker helps with PODA?
How do you create multi-container applications using Docker Compose?
How do you deploy this multi-container application on multiple hosts running in a Docker Swarm cluster?
What new features Docker introduced in 1.9 release – particularly multi-host networking and persistent storage?
How do you deploy Docker containers using Kubernetes?
How does Kubernetes help with scaling applications?
How does Docker Swarm compare with Kubernetes?

I had the privilege of delivering a 3-hour university on Docker and Kubernetes followed by a 3-hour hands-on lab. The replay of the university session is now available:

Slides for the university are available at: github.com/javaee-samples/docker-java/tree/master/slides

The contents from the hands-on lab are available at bit.ly/dockerlab.

In addition, I also gave a 3-hour university on Refactor your Java EE Applications using Microservices and Containers. This session explained:

Basic characteristics of Microservices
Showed a simple shopping cart monolithic application, and how it was refactored to multiple microservices (github.com/arun-gupta/microservices)
Talked about transactions, event sourcing and CQRS
How KumuluzEE was used to create standalone JARs
Explained how such microservices can be deployed using Docker

Slides from this session are available at: github.com/arun-gupta/microservices/tree/master/slides

Replay is available at:

The response on twitter was quite positive:

Almost packed room 20 mins before #Docker #Kubernetes workshop at #Devoxx pic.twitter.com/LVuK1cLuHR

— Arun Gupta (@arungupta) November 9, 2015

Top 3 talks so far, with lots of votes, Venkat Subramaniam. Talk about a super star speaker! #Devoxx

— Frédéric Donckels (@forgotten_pass) November 11, 2015

Enjoyed the 2 university days #Devoxx so far, specialy @venkat_s and @arungupta great talks

— Marc…Aurèle…ius (@marcaurele) November 10, 2015

@arungupta talks about microservices on #Devoxx – best talk so far👍👍👍

— Henrik Thorsted (@elbartdk) November 10, 2015

Full quote @arungupta: #Kubernetes can't exist w/o #Docker just like #Spring cannot w/o (parts of) #JavaEE. #Devoxx https://t.co/2LjBo2cZVI

— Vladimir Pavlov (@vladopavlov) November 9, 2015

#docker hands on lab very popular #devoxx @arungupta – checkout the material at https://t.co/u0dDI7AYUR pic.twitter.com/dEsBsYESI1

— Stijn Van den Enden (@stieno) November 9, 2015

Very good overview #docker #kubernetes at #devoxx @arungupta https://t.co/hNSbj9LDrJ

— Sascha (@sam6_de) November 9, 2015

sweet intro into Kubernetes by @arungupta and very useful session in general! #Devoxx #DevoxxBE pic.twitter.com/X8GR4PYZMz

— Vladimir Tsukur (@flushdia) November 9, 2015

@arungupta always the best!! pic.twitter.com/RMO4TWGpGy

— fiorenzo pizza (@fiorenzino) November 9, 2015

And in case you are interested, watch a quick interview with Voxxed team:

Enjoy!