Monthly Archives: February 2016

Couchbase Weekly, Feb 29, 2016

February 29, 2016couchbaseweeklyarungupta

Learn what’s latest in the Couchbase Community.
Couchbase Developer Community

Let us know if we missed anything at @couchbasedev, @couchbase or #Couchbase.

March 3: Voxxed Days, Zurich
Couchbase Meetup is happening today! Learn more about Mobile at the Couchbase Paris Meetup.

Media Mentions

Telegraph UK: Nine ways tech will change businesses in 2016
DZone: Spring Data Couchbase 2 is Out! Quick Getting Started With Spring Initializr
InfoWorld: Java 9 to address GTK pains on Linux
RCR Wireless: Mobile fraud — are the new attack frontiers really invisible?
Computing UK: Nielsen picks ‘more mature’ Couchbase over MongoDB for document store
InfoWorld: Couchbase 4.0 review: The Swiss Army knife of NoSQL
App Developer Magazine: New Couchbase Mobile Database Platform Adds Updated Security for Apps

Blogs

Couchbase Server 4.5 DP hangout — Matthew Revell
Get to Know Our Couchbase Community — Meet Andy Kruth — Laura Czajkowski
Storing Base64 Files Directly in Couchbase via Node.js — Nic Raboy
Couchbase on Kubernetes — Arun Gupta
Docker Installation Scripts – CLI, Machine, Compose, Version Manager — Arun Gupta
The Couchbase Sub-Document API for Go — Todd Greenstein
Couchbase Docker Container — Arun Gupta
Load Nested Models With Ottoman When A Parent Model Is Found In Node.js — Nic Raboy
Using the Sub-Document API to get (only) what you want — Mark Nunberg
Couchbase 4.5 Developer Preview Now Available! — Arun Gupta
Full Text Search in Couchbase 4.5 Developer Preview — Laurent Doguin, Will Gardella
Preview of Full Text Search in Couchbase using the Java SDK — Simon Baslé
Sub-documents: find and change only what you need — Matthew Revell
Introducing Couchbase Server 4.5 Developer Preview — Don Pinto
NDP Episode #2: NoSQL and Where It’s Used — Nic Raboy
Moving from Oracle to Couchbase — Nic Raboy
Vaadin/Couchbase CRUD Sample — Laurent Doguin
Spring Data Couchbase 2 is out! Quick getting started with Spring Initializr — Laurent Doguin
Moving from MongoDB to Couchbase Server — Matthew Revell
Couchbase Weekly Feb 15 2016 — Arun Gupta

Upcoming Events

February 29: Couchbase Paris
March 3: Voxxed Days, Zurich
March 7 – 8: Big Data Paris, Paris
March 8: Couchbase Day Philadelphia
March 8: Couchbase Day Phoenix
March 11 – 12: SF Droidcon
March 11: Couchbase Day Toronto
March 15: Couchbase Day Waltham
March 16: Couchbase Day London

Webinars

March 24: How to leverage NoSQL to deliver great eCommerce customer experiences (EMEA)
March 24: How to leverage NoSQL to deliver great eCommerce customer experiences (US)

Enterprises like Cisco & Marriott are modernizing their legacy systems with #Couchbase #NoSQL. Why? ow.ly/YvENp
#Couchbase Server 4.5 Developer Preview is ready! Built-in query editor & schema browser, full-text search, and more http://ow.ly/YTsz4
Enterprises like Nielsen are picking #Couchbase the “more mature” database over #MongoDB for document store: http://ow.ly/YrrR3 #NoSQL
Learn how #Couchbase customers deploy #NoSQL at the enterprise level for maxium performance and reliability: http://ow.ly/Yv925
Get professional advice from the #Couchbase services team on everything from #JSON modeling to using #SQL for #NoSQL: http://ow.ly/XSFyr

Source: http://blog.couchbase.com/2016/february/couchbase-weekly-feb-29-2016

Couchbase on Kubernetes

February 26, 2016containers, couchbasecouchbase, docker, kubernetesarungupta

This blog is possible because of this tweet!

Had a great #Couchbase #Kubernetes hacking session with @saturnism, learned a lot, look forward to some nice blogs.

— Arun Gupta (@arungupta) February 27, 2016

Kubernetes is an open source orchestration system by Google for Docker containers. It manages containerized applications across multiple hosts and provides basic mechanisms for deployment, maintenance, and scaling of applications.

It allows the user to provide declarative primitives for the desired state, for example “need 5 Couchbase servers”. Kubernetes self-healing mechanisms, such as auto-restarting, re-scheduling, and replicating containers then ensure that this state is met. The user just define the state and Kubernetes ensures that the state is met at all times on the cluster.

Key Concepts of Kubernetes explains the key concepts of Kubernetes.

This multi-part blog series will show how to run Couchbase on Kubernetes in multiple ways. The first part starts with a simple setup using Vagrant.

Getting Started with Kubernetes

There are multiple ways to run Kubernetes but I found the simples (not necessarily predictable 😉 way is to run using Vagrant.

Download the latest Kubernetes release, 1.1.8 as of this writing, and expand the archive.

Start the Kubernetes cluster as:

cd kubernetes

export KUBERNETES_PROVIDER=vagrant
./cluster/kube-up.sh

cd kubernetes

export KUBERNETES_PROVIDER=vagrant

./cluster/kube-up.sh

This shows the output as:

kubernetes-1.1.8 > ./kubernetes/cluster/kube-up.sh 
... Starting cluster using provider: vagrant
... calling verify-prereqs
... calling kube-up
Bringing machine 'master' up with 'virtualbox' provider...
Bringing machine 'minion-1' up with 'virtualbox' provider...
==> master: Importing base box 'kube-fedora21'...

. . .

Validate output:
NAME                 STATUS    MESSAGE              ERROR
controller-manager   Healthy   ok                   nil
scheduler            Healthy   ok                   nil
etcd-0               Healthy   {"health": "true"}   nil
etcd-1               Healthy   {"health": "true"}   nil
Cluster validation succeeded
Done, listing cluster services:

Kubernetes master is running at https://10.245.1.2
Heapster is running at https://10.245.1.2/api/v1/proxy/namespaces/kube-system/services/heapster
KubeDNS is running at https://10.245.1.2/api/v1/proxy/namespaces/kube-system/services/kube-dns
KubeUI is running at https://10.245.1.2/api/v1/proxy/namespaces/kube-system/services/kube-ui
Grafana is running at https://10.245.1.2/api/v1/proxy/namespaces/kube-system/services/monitoring-grafana
InfluxDB is running at https://10.245.1.2/api/v1/proxy/namespaces/kube-system/services/monitoring-influxdb

kubernetes-1.1.8 > ./kubernetes/cluster/kube-up.sh

... Starting cluster using provider: vagrant

... calling verify-prereqs

... calling kube-up

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

Bringing machine 'minion-1' up with 'virtualbox' provider...

==> master: Importing base box 'kube-fedora21'...

. . .

Validate output:

NAME STATUS MESSAGE ERROR

controller-manager Healthy ok nil

scheduler Healthy ok nil

etcd-0 Healthy {"health": "true"} nil

etcd-1 Healthy {"health": "true"} nil

Cluster validation succeeded

Done, listing cluster services:

Kubernetes master is running at https://10.245.1.2

Heapster is running at https://10.245.1.2/api/v1/proxy/namespaces/kube-system/services/heapster

KubeDNS is running at https://10.245.1.2/api/v1/proxy/namespaces/kube-system/services/kube-dns

KubeUI is running at https://10.245.1.2/api/v1/proxy/namespaces/kube-system/services/kube-ui

Grafana is running at https://10.245.1.2/api/v1/proxy/namespaces/kube-system/services/monitoring-grafana

InfluxDB is running at https://10.245.1.2/api/v1/proxy/namespaces/kube-system/services/monitoring-influxdb

Run Couchbase on Kubernetes Cluster

The easiest way to start running a Docker container in Kubernetes is using the kubectl run command.

The command usage is:

kubectl run NAME --image=image [--env="key=value"] [--port=port] [--replicas=replicas] [--dry-run=bool] [--overrides=inline-json] [flags]

kubectl run NAME --image=image [--env="key=value"] [--port=port] [--replicas=replicas] [--dry-run=bool] [--overrides=inline-json] [flags]

The command runs a particular image, possibly replicated. The image replication is handled by creating a Replication Controller to manage the created container(s).

Complete list of options to run this command can be seen using:

./cluster/kubectl.sh run --help

./cluster/kubectl.sh run --help

Couchbase Docker Container explains the different Docker container for Couchbase. For this blog, we’ll use arungupta/couchbase image as that is pre-configured.

./cluster/kubectl.sh run couchbase --image=arungupta/couchbase

./cluster/kubectl.sh run couchbase --image=arungupta/couchbase

This shows the output:

replicationcontroller "couchbase" created

replicationcontroller "couchbase" created

The output confirms that a Replication Controller is created. Lets verify it:

./kubernetes/cluster/kubectl.sh get rc
CONTROLLER   CONTAINER(S)   IMAGE(S)              SELECTOR        REPLICAS   AGE
couchbase    couchbase      arungupta/couchbase   run=couchbase   1          17s

./kubernetes/cluster/kubectl.sh get rc

CONTROLLER CONTAINER(S) IMAGE(S) SELECTOR REPLICAS AGE

couchbase couchbase arungupta/couchbase run=couchbase 1 17s

Now, check the pods:

./kubernetes/cluster/kubectl.sh get po
NAME              READY     STATUS    RESTARTS   AGE
couchbase-tzdhl   0/1       Pending   0          36s

./kubernetes/cluster/kubectl.sh get po

NAME READY STATUS RESTARTS AGE

couchbase-tzdhl 0/1 Pending 0 36s

Lets check the status of the pod:

./kubernetes/cluster/kubectl.sh describe pod couchbase-tzdhl
Name:                           couchbase-tzdhl
Namespace:                      default
Image(s):                       arungupta/couchbase
Node:                           10.245.1.4/10.245.1.4
Start Time:                     Fri, 26 Feb 2016 18:05:10 -0800
Labels:                         run=couchbase
Status:                         Running
Reason:                         
Message:                        
IP:                             10.246.67.2
Replication Controllers:        couchbase (1/1 replicas created)
Containers:
  couchbase:
    Container ID:       docker://56dddb66bf60a590e588b972d5cae997ec96149066a9fb8075548c982eb14961
    Image:              arungupta/couchbase
    Image ID:           docker://080e2e96b3fc22964f3dec079713cdf314e15942d6eb135395134d629e965062
    QoS Tier:
      cpu:      Burstable
    Requests:
      cpu:              100m
    State:              Running
      Started:          Fri, 26 Feb 2016 18:05:56 -0800
    Ready:              True
    Restart Count:      0
    Environment Variables:
Conditions:
  Type          Status
  Ready         True 
Volumes:
  default-token-clfeb:
    Type:       Secret (a secret that should populate this volume)
    SecretName: default-token-clfeb
Events:
  FirstSeen     LastSeen        Count   From                    SubobjectPath                           Reason          Message
  ─────────     ────────        ─────   ────                    ─────────────                           ──────          ───────
  1m            1m              1       {scheduler }                                                    Scheduled       Successfully assigned couchbase-tzdhl to 10.245.1.4
  1m            1m              1       {kubelet 10.245.1.4}    implicitly required container POD       Pulling         Pulling image "gcr.io/google_containers/pause:0.8.0"
  59s           59s             1       {kubelet 10.245.1.4}    implicitly required container POD       Created         Created with docker id 2dac5f81f4c2
  59s           59s             1       {kubelet 10.245.1.4}    spec.containers{couchbase}              Pulling         Pulling image "arungupta/couchbase"
  59s           59s             1       {kubelet 10.245.1.4}    implicitly required container POD       Started         Started with docker id 2dac5f81f4c2
  59s           59s             1       {kubelet 10.245.1.4}    implicitly required container POD       Pulled          Successfully pulled image "gcr.io/google_containers/pause:0.8.0"
  19s           19s             1       {kubelet 10.245.1.4}    spec.containers{couchbase}              Pulled          Successfully pulled image "arungupta/couchbase"
  18s           18s             1       {kubelet 10.245.1.4}    spec.containers{couchbase}              Created         Created with docker id 56dddb66bf60
  18s           18s             1       {kubelet 10.245.1.4}    spec.containers{couchbase}              Started         Started with docker id 56dddb66bf60

./kubernetes/cluster/kubectl.sh describe pod couchbase-tzdhl

Name: couchbase-tzdhl

Namespace: default

Image(s): arungupta/couchbase

Node: 10.245.1.4/10.245.1.4

Start Time: Fri, 26 Feb 2016 18:05:10 -0800

Labels: run=couchbase

Status: Running

Reason:

Message:

IP: 10.246.67.2

Replication Controllers: couchbase (1/1 replicas created)

Containers:

couchbase:

Container ID: docker://56dddb66bf60a590e588b972d5cae997ec96149066a9fb8075548c982eb14961

Image: arungupta/couchbase

Image ID: docker://080e2e96b3fc22964f3dec079713cdf314e15942d6eb135395134d629e965062

QoS Tier:

cpu: Burstable

Requests:

cpu: 100m

State: Running

Started: Fri, 26 Feb 2016 18:05:56 -0800

Ready: True

Restart Count: 0

Environment Variables:

Conditions:

Type Status

Ready True

Volumes:

default-token-clfeb:

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

SecretName: default-token-clfeb

Events:

FirstSeen LastSeen Count From SubobjectPath Reason Message

───────── ──────── ───── ──── ───────────── ────── ───────

1m 1m 1 {scheduler } Scheduled Successfully assigned couchbase-tzdhl to 10.245.1.4

1m 1m 1 {kubelet 10.245.1.4} implicitly required container POD Pulling Pulling image "gcr.io/google_containers/pause:0.8.0"

59s 59s 1 {kubelet 10.245.1.4} implicitly required container POD Created Created with docker id 2dac5f81f4c2

59s 59s 1 {kubelet 10.245.1.4} spec.containers{couchbase} Pulling Pulling image "arungupta/couchbase"

59s 59s 1 {kubelet 10.245.1.4} implicitly required container POD Started Started with docker id 2dac5f81f4c2

59s 59s 1 {kubelet 10.245.1.4} implicitly required container POD Pulled Successfully pulled image "gcr.io/google_containers/pause:0.8.0"

19s 19s 1 {kubelet 10.245.1.4} spec.containers{couchbase} Pulled Successfully pulled image "arungupta/couchbase"

18s 18s 1 {kubelet 10.245.1.4} spec.containers{couchbase} Created Created with docker id 56dddb66bf60

18s 18s 1 {kubelet 10.245.1.4} spec.containers{couchbase} Started Started with docker id 56dddb66bf60

Fifth line of the output says the node’s IP is 10.245.1.4. This would be used to access the Web Console later.

The last line in this output shows that the pod is now ready. Checking the status of the pod again shows:

./kubernetes/cluster/kubectl.sh get po
NAME              READY     STATUS    RESTARTS   AGE
couchbase-tzdhl   1/1       Running   0          2m

./kubernetes/cluster/kubectl.sh get po

NAME READY STATUS RESTARTS AGE

couchbase-tzdhl 1/1 Running 0 2m

Couchbase Web Console on Kubernetes Cluster

Now that your Couchbase container is running in Kubernetes cluster, you may like to view the Web Console.

Each pod is assigned a unique IP address, but this address is only accessible within the cluster. It can exposed using the kubectl expose command.

This command takes a Replication Controller, Service or Pod and expose it as new Kubernetes Service. This can be done by giving the command:

./cluster/kubectl.sh expose rc couchbase --target-port=8091 --port=8091 --external-ip=10.245.1.4
service "couchbase" exposed

./cluster/kubectl.sh expose rc couchbase --target-port=8091 --port=8091 --external-ip=10.245.1.4

service "couchbase" exposed

In this command:

--target-port is the name or number for the port on the container that the service should direct traffic to
--port is the port that the service should serve on
--external-ip is the external IP address to set for the service. Note, this IP address was obtained with kubectl describe pod command earlier.

Now, you can access the Couchbase Web Console at http://10.245.1.4:8091 and looks like:

Enter the password credentials as Administrator/password. These credentials are specified during Docker image creation at github.com/arun-gupta/docker-images/blob/master/couchbase/configure-cluster.sh#L9.

Voila!

Discuss with us at StackOverflow or Couchbase Forums. You can also follow us at @couchbasedev and @couchbase.

Source: http://blog.couchbase.com/2016/couchbase-on-kubernetes

Docker Installation Scripts – CLI, Machine, Compose, Version Manager

February 26, 2016containersdockerarungupta

Docker Toolbox is cool! It is a single point download that gives you everything to get started with Docker. But it comes with other tools like VirtualBox and Kitematic which you may not want. So what do you do?

You install the tools that you like using CLI. This blog shows how to do exactly that.

All the commands are installed in the /usr/bin/local directory.

Latest Docker CLI

This command downloads and installs the latest Docker CLI.

curl -L https://get.docker.com/builds/Darwin/x86_64/docker-latest > /usr/local/bin/docker && \
chmod +x /usr/local/bin/docker

curl -L https://get.docker.com/builds/Darwin/x86_64/docker-latest > /usr/local/bin/docker && \

chmod +x /usr/local/bin/docker

Another simpler way to install and manage different versions of CLI are using Docker Version Manager or dvm.

DVM provides a decent set of commands:

~ > dvm <TAB>
alias        help         list-alias   ls-alias     uninstall    use
current      install      list-remote  ls-remote    unload       version
deactivate   list         ls           unalias      upgrade      which

~ > dvm <TAB>

alias help list-alias ls-alias uninstall use

current install list-remote ls-remote unload version

deactivate list ls unalias upgrade which

Latest Docker Machine

This command downloads and installs the latest Docker Machine.

curl -L https://github.com/docker/machine/releases/download/v0.6.0/docker-machine-Darwin-x86_64 > /usr/local/bin/docker-machine && \
chmod +x /usr/local/bin/docker-machine

curl -L https://github.com/docker/machine/releases/download/v0.6.0/docker-machine-Darwin-x86_64 > /usr/local/bin/docker-machine && \

chmod +x /usr/local/bin/docker-machine

Latest Docker Compose

This command downloads and installs the latest Docker Compose.

curl -L https://github.com/docker/compose/releases/download/1.6.2/docker-compose-`uname -s`-`uname -m` > /usr/local/bin/docker-compose && \
chmod +x /usr/local/bin/docker-compose

curl -L https://github.com/docker/compose/releases/download/1.6.2/docker-compose-`uname -s`-`uname -m` > /usr/local/bin/docker-compose && \

chmod +x /usr/local/bin/docker-compose

Enjoy!

Source: http://blog.couchbase.com/2016/docker-installation-scripts

Couchbase Docker Container

February 25, 2016techtipcouchbase, dockerarungupta

Couchbase Docker images are always at hub.docker.com/_/couchbase/. Complete instructions to run Couchbase Docker Container are available at docs.docker.com/engine/examples/couchbase/.

Start Couchbase Docker Container

How do you start a Couchbase Docker container?

docker run -d -p 8091-8093:8091-8093 -p 11210:11210 couchbase

docker run -d -p 8091-8093:8091-8093 -p 11210:11210 couchbase

By default, this command starts Couchbase Server 4.1 Enterprise Edition. The latest GA images are always available using this image name.

This server needs to be manually configured by going to the Web Console on http://<DOCKERHOST>:8091. The IP address of the Docker Host in my case is obtained using:

docker-machine ip couchbase

docker-machine ip couchbase

The instructions to configure the server are available at at docs.docker.com/engine/examples/couchbase/.

Pre-configured Couchbase Docker Container

If you want a pre-configured server, then you can run the image:

docker run -d -p 8091-8093:8091-8093 -p 11210:11210 arungupta/couchbase

docker run -d -p 8091-8093:8091-8093 -p 11210:11210 arungupta/couchbase

This image is created using Dockerfile and configures the following:

Configures the memory
Configures Index, Query, and Data service
Sets up username/password credentials

Couchbase 4.5 Docker Container

Couchbase 4.5 Developer Preview was launched recently. It can run as a Docker container as:

docker run -d -p 8091-8093:8091-8093 -p 11210:11210 couchbase/server:enterprise-4.5.0-DP1
Unable to find image 'couchbase/server:enterprise-4.5.0-DP1' locally
enterprise-4.5.0-DP1: Pulling from couchbase/server
a64038a0eeaa: Pull complete 
2ec6e7edf8a8: Pull complete 
0a5fb6c3c94b: Pull complete 
a3ed95caeb02: Pull complete 
7d007592b256: Pull complete 
31cbaa6abb86: Pull complete 
efe43bf775c4: Pull complete 
e8fff3fce5e8: Pull complete 
2a747598893c: Pull complete 
Digest: sha256:873f2d8776d15019d8a45d01a2be5db345823b3093a3538970f1cd441c57d91c
Status: Downloaded newer image for couchbase/server:enterprise-4.5.0-DP1
b4ea7e969278b94fd9748003f7305e5ffcc30b398c6c6301982895550fd7fd24

docker run -d -p 8091-8093:8091-8093 -p 11210:11210 couchbase/server:enterprise-4.5.0-DP1

Unable to find image 'couchbase/server:enterprise-4.5.0-DP1' locally

enterprise-4.5.0-DP1: Pulling from couchbase/server

a64038a0eeaa: Pull complete

2ec6e7edf8a8: Pull complete

0a5fb6c3c94b: Pull complete

a3ed95caeb02: Pull complete

7d007592b256: Pull complete

31cbaa6abb86: Pull complete

efe43bf775c4: Pull complete

e8fff3fce5e8: Pull complete

2a747598893c: Pull complete

Digest: sha256:873f2d8776d15019d8a45d01a2be5db345823b3093a3538970f1cd441c57d91c

Status: Downloaded newer image for couchbase/server:enterprise-4.5.0-DP1

b4ea7e969278b94fd9748003f7305e5ffcc30b398c6c6301982895550fd7fd24

Notice the image name is couchbase/server:enterprise-4.5.0-DP1.

The Couchbase Web Console is then accessible at http://<DOCKERHOST>:8091. The IP address of the Docker Host in my case is obtained using:

docker-machine ip couchbase

docker-machine ip couchbase

And so the Web Console looks like:

After configuring the services, the Console looks like:

Pre-configured Couchbase 4.5 Docker Container

Now, if you want a pre-configured server, try this:

docker run -d -p 8091-8093:8091-8093 -p 11210:11210 arungupta/couchbase-server

docker run -d -p 8091-8093:8091-8093 -p 11210:11210 arungupta/couchbase-server

This image is created using Dockerfile and configures the following:

Configures the memory
Configures Index, Query, Data, and Full-text service
Sets up username/password credentials

So, here are the images you need to use:

Image	Purpose
`couchbase`	Last GA version of Couchbase
`couchbase/server`	Intermediate builds of Couchbase, such as Developer Preview, Beta, etc
`arungupta/couchbase`	Last GA version of Couchbase, pre-configured
`arungupta/couchbase-server`	Intermediate builds of Couchbase, pre-configured

Easy, eh?

Originally published at: http://blog.couchbase.com/2016/february/couchbase-docker-container

Couchbase 4.5 Developer Preview Now Available!

February 24, 2016couchbasecouchbase, docker, nosqlarungupta

Couchbase 4.5 Developer Preview is now available!

As we head towards 4.5 GA, this is a significant milestone packed with many exciting features for more efficient querying, advanced data access, powerful indexing, and more comprehensive administration.

For developers, this is going to be a big preview release as it brings some exciting features including:

Query Workbench – a built-in query editor for writing and executing queries as well as exploring the data model with automatically inferred schemas
Full-text Search – support for term, fuzzy, phrase, match, and prefix queries has been added – faceting, scoring, and highlighting, too.
- Blog: Full-text Search in Couchbase 4.5 Developer Preview by @ldoguin and @willgardella
- Blog: Preview of Full-text Search in Couchbase using the Java SDK by @simonbasle
Sub-document API – enables clients to add, remove, and modify individual fields (or read them), including objects and arrays, without reading and writing the entire document
- Blog: Sub-documents: find and change only what you need by @matthewrevell
Array Indexing – index specific fields of elements within nested arrays to improve query performance
Extended N1QL joins – support a new query optimization for filtering the right side first, with an index, resulting in added flexibility and improved query performance
Query Profiling and Monitoring – monitor active queries and connections as well as profile queries to identify and diagnose performance issues
Many more

We’ve also introduced Debian 8 builds and this adds to the existing wide list of platforms we already run on.

Here are some quick links:

4.5 Developer Preview Download
4.5 Developer Preview features at a glance
Blog Announcement
Docs
Release Notes
Docker images

Interested in learning more about each feature, then watch different videos (more coming) in this playlist:

Enjoy!

Originally posted at: http://blog.couchbase.com/2016/february/couchbase-4.5-developer-preview-available

Couchbase Weekly, Feb 15, 2016

February 15, 2016couchbasecouchbase, weeklyarungupta

Learn what’s latest in the Couchbase Community.
Couchbase Developer Community

Let us know if we missed anything at @couchbasedev, @couchbase or #Couchbase.

Today through February 17, Couchbase is sponsoring DevNexus 2016 in Atlanta
Couchbase Meetup is happening tomorrow! Join the team at HQ for the Couchbase Silicon Valley Meetup.
Couchbase at Silicon Valley Java User Group on Feb 17th

Media Mentions

DZone: NetBeans Plugin for Couchbase Part 2 — Coffee on Couchbase
Computer Business Review: Turning Big Data into Big Value
Fortune: The Good News Is a Huge Company Just Bought Your Favorite App
SearchCloudApplications: Parse shutdown: Alternatives are asking for your business
Digital Journal: Global NoSQL Market Driven by Rapid Generation of Large Amounts of Data

Blogs

SDK-RFCs: Open Commentary on Sub-Document and Index Management
NetBeans Plugin for Couchbase Part 3 – Coffee on Couchbase — Arun Gupta
Announcing Spring Data Couchbase 2.0 RELEASE — Simon Baslé
Migrating from Parse to Couchbase Mobile — William Hoang
Couchbase Weekly Feb 8, 2016 — Arun Gupta
Couchbase is taking part in Jfokus — Laura Czajkowski
Couchbase Mobile 1.2: Enabling ForestDB for iOS and Android — William Hoang
Moving data from Oracle to Couchbase — Manual Hurtado

Upcoming Events

February 15 – 17: DevNexus 2016, Atlanta
February 16: Couchbase Silicon Valley
Feb 17, Silicon Valley JUG
February 25: Voxxed Days, Bristol
February 18: Couchbase Day Seattle
February 18: Couchbase Day Reston
February 22: Couchbase Day New York
February 24: Couchbase Day Vancouver
February 24: Couchbase Day Raleigh
February 29: Inmarsat Developer Conference, London

Webinars

5-part webinar series for building a fullstack application using the CEAN stack — for EMEA series see here, for US series see here.

201: Bootstrapping an application using the CEAN stack
202: Application logic, data model, and validation
203: Build a responsive front end with Angular & Bootstrap
204: Built-in URL permalinking & minification
205: Mobile-first development with NativeScript

February 25: From MongoDB to Couchbase: How Gannett and Others Made the Switch (US)
February 25: From MongoDB to Couchbase: How Gannett and Others Made the Switch (EMEA)

High performance distributed caching: #Couchbase scales your #mobile #web #IoT apps. Learn how: ow.ly/XVuMP
#Couchbase Mobile 1.2 rolls out enterprise grade enhancements including improved security & performance: http://ow.ly/Y5sRH
Read the top 10 #NoSQL enterprise use cases http://ow.ly/Y5C30 #couchbase #database
Read this step-by-step demo and learn how to move data from #Oracle to #Couchbase: http://ow.ly/Y9zu3
Only #Couchbase can support the complexity & scale of today’s #BigData. Learn why enterprises are moving off RDBMS http://ow.ly/XPExv

Originally posted at: blog.couchbase.com/2016/february/couchbase-weekly-feb15-2016

NetBeans Plugin for Couchbase Part 3 – Coffee on Couchbase

February 10, 2016couchbasecouchbase, netbeansarungupta

This is part 3 (part 2, part 1) of Coffee on Couchbase series where we are building a NetBeans plugin for Couchbase. This multi-part webinar series is a discussion with Geertjan Wielenga (@GeertjanW) and Eben Haber (@ebenhaber).

As part of this series, you’ll also learn how to build a NetBeans plugin from scratch and learn the awesomeness behind NetBeans platform.

The recording from part 3 is now available:

A lot of features have been added during this part. This episode shows the following features:

Login to Couchbase server
See Bucket list
See Documents in Bucket
Query data from buckets (basic queries, N1QL queries coming later)
Compare Documents (NetBeans Diff Viewer)
Open Documents (in JSON editor, not savable back to Couchbase)
Multiple Couchbase hosts can be configured

The next episode will show how we built these features under the hood:

All the code is evolving at: github.com/arun-gupta/couchbase-netbeans-plugin.

NetBeans plugin module file (NBM) is now available.

Here is a snapshot of the work in progress:

Let us know by filing bugs on features that you’d like to see in this plugin.

We’d love to see your tweets containing snapshots of your document in NetBeans. Use #NetBeans #Couchbase to let us know

Enjoy!

Originally posted at: blog.couchbase.com/2016/netbeans-plugin-couchbase-part-3-coffee-on-couchbase

Couchbase Weekly Feb 8, 2016

February 8, 2016couchbasearungupta

Learn what’s latest in the Couchbase Community.
Couchbase Developer Community

Let us know if we missed anything at @couchbasedev, @couchbase or #Couchbase.

Couchbase Mobile 1.2 released delivering enterprise grade administration, security, performance, and scalability. Read more in the Press Release.
Today through February 10, Couchbase is sponsoring Sweden’s largest developer conference, Jfokus in Stockholm.

Press Releases

New Release of Couchbase Mobile Gives Enterprise Developers Cutting Edge Data Management Platform for Building Always On Mobile Applications
Couchbase Mobile 1.2 delivers enterprise grade administration, security, performance, and scalability

Media Mentions

insideBIGDATA: New Release of Couchbase Mobile Announced
SDTimes: New release of Couchbase Mobile gives enterprise developers cutting edge data management platform for building always on mobile applications
ADTMag: Couchbase Mobile Targets Enterprise
DZone: Migrating from Parse to Couchbase Mobile
DBTA: Couchbase Mobile 1.2 Delivers Enterprise-Grade Enhancements in Four Areas
FierceMobileIT: Couchbase updates mobile app platform with improved management controls, data-at-rest encryption
ITProPortal: Q&A: Overcoming the challenges of mobile app development
Fortune: The Good News Is a Huge Company Just Bought Your Favorite App
The Next Silicon Valley: CTO Summit: harnessing technology to drive innovation
DZone: Deploy Docker to Amazon Cloud Using Tutum
JavaWorld: Open source Java projects: Apache Phoenix
TechTarget: NoSQL revs up to the tune of the Spark connecter
The Lake Andes Wave: Walmart Open Sources Its OneOps Cloud Platform

Blogs

RWDevCon 2016: Couchbase Mobile Lab – Taking Your Mobile Apps Offline — William Hoang
Couchbase is taking part in Jfokus — Laura Czajkowski
Couchbase Mobile 1.2: Enabling ForestDB for iOS and Android — William Hoang
Enabling Docker Remote API on Docker Machine on Mac OS X — Arun Gupta
Docker 1.10, Machine 0.6.0, Compose 1.6.0 – better volumes and networking — Arun Gupta
Prepared Statements – by the Numbers! — Todd Greenstein
Couchbase with Azure ARM Templates —Martin Esmann
Announcing Couchbase Mobile 1.2 — Ali LeClerc
Deploy Docker to Amazon Cloud using Tutum — Arun Gupta
Coffee on Couchbase: How to Securely Set Channel Parameters in Sync Gateway — William Hoang
Welcome to our first round of 2016 Couchbase Champions — Laura Czajkowski
Full Stack Development with the CEA2N Stack Webinars — Nic Raboy
Couchbase Weekly Feb 1, 2016 — Arun Gupta
Talking Beacons, IoT, P2P and Couchbase Mobile — Laurent Doguin

Upcoming Events

February 8 – 10: Jfokus, Stockholm
February 15 – 17: DevNexus 2016, Stockholm
February 18: Couchbase Day Seattle
February 18: Couchbase Day Reston
February 22: Couchbase Day New York

Webinars

5-part webinar series for building a fullstack application using the CEAN stack — for EMEA series see here, for US series see here.

201: Bootstrapping an application using the CEAN stack
202: Application logic, data model, and validation
203: Build a responsive front end with Angular & Bootstrap
204: Built-in URL permalinking & minification
205: Mobile-first development with NativeScript

February 25: From MongoDB to Couchbase: How Gannett and Others Made the Switch (US)
February 25: From MongoDB to Couchbase: How Gannett and Others Made the Switch (EMEA)

Couchbase Meetups

February 18: Couchbase Silicon Valley

Other People Meetups (OPMs)

February 10: JavaMug, Dallas
February 12: UmeJUG, Sweden

Hit by #parseshutsdown? Read the blog on what you can do for your apps #couchbasemobile ow.ly/XRkMy
#Couchbase Lite 1.2 delivers 2 – 5x faster performance for key #database operations bit.ly/1VIHqaE #NoSQL #mobile
Learn #NoSQL with #Couchbase free online training: ow.ly/Xx84G
New McKinsey research shows how the U.S. #DigitalEconomy is a potential $2 trillion market: http://ow.ly/XtSny via @HarvardBiz
Data center infrastructure has evolved, yet databases remain largely unchanged. It’s time to scale up and scale out http://ow.ly/XS074

Originally posted at: blog.couchbase.com/2016/february/couchbase-weekly-feb8-2016

Enable Docker Remote API on Docker Machine on Mac OS X

February 7, 2016containers, couchbasecouchbase, dockerarungupta

Docker daemon provides a Remote REST API. This API is used by the Client to communicate with the engine. This API can be also be invoked by by other tools, such as curl or Chrome Postman REST Client.

If you are creating Docker daemons using Docker Machine on OSX Mavericks, then getting this API to work is a bit tricky. This blog will explain how to enable Docker Remote API on Docker Machines created on Mac OS X.

Connecting to the secure Docker port using curl gives the command as:

$ curl https://$HOST:2376/images/json \
  --cert ~/.docker/cert.pem \
  --key ~/.docker/key.pem \
  --cacert ~/.docker/ca.pem

$ curl https://$HOST:2376/images/json \

--cert ~/.docker/cert.pem \

--key ~/.docker/key.pem \

--cacert ~/.docker/ca.pem

Couple of issues with this command:

This command does not even work for Docker Machine since the certificates for each Machine are stored in .docker/machine/machines/<machine-name> directory.

Even if this command is modified to match that path:

curl https://192.168.99.100:2376/images/json --cert $DOCKER_CERT_PATH/cert.pem --key $DOCKER_CERT_PATH/key.pem --cacert $DOCKER_CERT_PATH/ca.pem

curl https://192.168.99.100:2376/images/json --cert $DOCKER_CERT_PATH/cert.pem --key $DOCKER_CERT_PATH/key.pem --cacert $DOCKER_CERT_PATH/ca.pem

It still gives the following error:

curl: (58) SSL: Can't load the certificate "/Users/arungupta/.docker/machine/machines/couchbase/cert.pem" and its private key: OSStatus -25299

curl: (58) SSL: Can't load the certificate "/Users/arungupta/.docker/machine/machines/couchbase/cert.pem" and its private key: OSStatus -25299

The culprit for this is an updated curl utility for OSX Mavericks users. In summary, the new version of CURL uses Apple’s Secure Transport API instead of the OpenSSL API. This means the certificates need to be in P12 format.

Lets fix this!

Go to the directory where certificates for your Machine are stored. In my case, this is .docker/machine/machines/couchbase directory.

Generate *.p12 format for the certificate:

openssl pkcs12 -export \
-inkey key.pem \
-in cert.pem \
-CAfile ca.pem \
-chain \
-name client-side \
-out cert.p12 \
-password pass:mypass

openssl pkcs12 -export \

-inkey key.pem \

-in cert.pem \

-CAfile ca.pem \

-chain \

-name client-side \

-out cert.p12 \

-password pass:mypass

More details here.

Now invoke the REST API as:

curl https://192.168.99.100:2376/images/json --cert $DOCKER_CERT_PATH/cert.p12 --pass mypass --key $DOCKER_CERT_PATH/key.pem --cacert $DOCKER_CERT_PATH/ca.pem

curl https://192.168.99.100:2376/images/json --cert $DOCKER_CERT_PATH/cert.p12 --pass mypass --key $DOCKER_CERT_PATH/key.pem --cacert $DOCKER_CERT_PATH/ca.pem

Notice, --cert now points to the generated p12 certificate and certificate password is specified sing --pass.

This will return the result as:

[{"Id":"sha256:d38beda529d3274636d6cb1c9000afe4f00fbdcfa544140d6cc0f5d7f5b8434a","ParentId":"","RepoTags":["arungupta/couchbase:latest"],"RepoDigests":null,"Created":1450330075,"Size":374824677,"VirtualSize":374824677,"Labels":{}}]

[{"Id":"sha256:d38beda529d3274636d6cb1c9000afe4f00fbdcfa544140d6cc0f5d7f5b8434a","ParentId":"","RepoTags":["arungupta/couchbase:latest"],"RepoDigests":null,"Created":1450330075,"Size":374824677,"VirtualSize":374824677,"Labels":{}}]

OK, now that makes sense!

Lets try to start Couchbase server as:

~ > docker run -d -p 8091-8093:8091-8093 -p 11210:11210 arungupta/couchbase
42d1414883affd0fbb272cb1378c2f6b5118acf3ed5cb60cbecdc42f95602e3e

~ > docker run -d -p 8091-8093:8091-8093 -p 11210:11210 arungupta/couchbase

42d1414883affd0fbb272cb1378c2f6b5118acf3ed5cb60cbecdc42f95602e3e

And invoke another REST API to view more details about this container:

~ > curl https://192.168.99.100:2376/containers/json --cert $DOCKER_CERT_PATH/cert2.p12 --pass mypass --key $DOCKER_CERT_PATH/key.pem --cacert $DOCKER_CERT_PATH/ca.pem
[{"Id":"42d1414883affd0fbb272cb1378c2f6b5118acf3ed5cb60cbecdc42f95602e3e","Names":["/admiring_pike"],"Image":"arungupta/couchbase","ImageID":"sha256:d38beda529d3274636d6cb1c9000afe4f00fbdcfa544140d6cc0f5d7f5b8434a","Command":"/entrypoint.sh /opt/couchbase/configure-cluster.sh","Created":1454850194,"Ports":[{"IP":"0.0.0.0","PrivatePort":8092,"PublicPort":8092,"Type":"tcp"},{"PrivatePort":11207,"Type":"tcp"},{"IP":"0.0.0.0","PrivatePort":11210,"PublicPort":11210,"Type":"tcp"},{"PrivatePort":18092,"Type":"tcp"},{"PrivatePort":18091,"Type":"tcp"},{"IP":"0.0.0.0","PrivatePort":8093,"PublicPort":8093,"Type":"tcp"},{"IP":"0.0.0.0","PrivatePort":8091,"PublicPort":8091,"Type":"tcp"},{"PrivatePort":11211,"Type":"tcp"}],"Labels":{},"Status":"Up 2 seconds","HostConfig":{"NetworkMode":"default"},"NetworkSettings":{"Networks":{"bridge":{"IPAMConfig":null,"Links":null,"Aliases":null,"NetworkID":"","EndpointID":"6feaf4c1c70feaf0ba240ce55fb58ce83ebb84c8098bef9171998e84f607fa0b","Gateway":"172.17.0.1","IPAddress":"172.17.0.2","IPPrefixLen":16,"IPv6Gateway":"","GlobalIPv6Address":"","GlobalIPv6PrefixLen":0,"MacAddress":"02:42:ac:11:00:02"}}}}]

~ > curl https://192.168.99.100:2376/containers/json --cert $DOCKER_CERT_PATH/cert2.p12 --pass mypass --key $DOCKER_CERT_PATH/key.pem --cacert $DOCKER_CERT_PATH/ca.pem

[{"Id":"42d1414883affd0fbb272cb1378c2f6b5118acf3ed5cb60cbecdc42f95602e3e","Names":["/admiring_pike"],"Image":"arungupta/couchbase","ImageID":"sha256:d38beda529d3274636d6cb1c9000afe4f00fbdcfa544140d6cc0f5d7f5b8434a","Command":"/entrypoint.sh /opt/couchbase/configure-cluster.sh","Created":1454850194,"Ports":[{"IP":"0.0.0.0","PrivatePort":8092,"PublicPort":8092,"Type":"tcp"},{"PrivatePort":11207,"Type":"tcp"},{"IP":"0.0.0.0","PrivatePort":11210,"PublicPort":11210,"Type":"tcp"},{"PrivatePort":18092,"Type":"tcp"},{"PrivatePort":18091,"Type":"tcp"},{"IP":"0.0.0.0","PrivatePort":8093,"PublicPort":8093,"Type":"tcp"},{"IP":"0.0.0.0","PrivatePort":8091,"PublicPort":8091,"Type":"tcp"},{"PrivatePort":11211,"Type":"tcp"}],"Labels":{},"Status":"Up 2 seconds","HostConfig":{"NetworkMode":"default"},"NetworkSettings":{"Networks":{"bridge":{"IPAMConfig":null,"Links":null,"Aliases":null,"NetworkID":"","EndpointID":"6feaf4c1c70feaf0ba240ce55fb58ce83ebb84c8098bef9171998e84f607fa0b","Gateway":"172.17.0.1","IPAddress":"172.17.0.2","IPPrefixLen":16,"IPv6Gateway":"","GlobalIPv6Address":"","GlobalIPv6PrefixLen":0,"MacAddress":"02:42:ac:11:00:02"}}}}]

Read through the complete API and go crazy now!

Originally posted at: blog.couchbase.com/2016/february/enabling-docker-remote-api-docker-machine-mac-osx

Docker 1.10, Machine 0.6.0, Compose 1.6.0 – better volumes and networking

February 4, 2016containers, couchbase, javacouchbase, dockerarungupta

Docker 1.10 is now released!

Read about all the new features in Docker 1.10. A quick summary:

New Compose file format
Much better networking
Much better security
Swarm becomes 1.1, with Mesos integration

Read Docker 1.10 release notes.

Lets look at some of the key components.

Docker Machine 0.6.0

Docker Machine makes it really easy to create Docker hosts on your computer, on cloud providers and inside your own data center. It creates servers, installs Docker on them, then configures the Docker client to talk to them.

Latest version can be installed as:

~> curl -L https://github.com/docker/machine/releases/download/v0.6.0/docker-machine-`uname -s`-`uname -m` >/usr/local/bin/docker-machine && \
~>   chmod +x /usr/local/bin/docker-machine
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100   601    0   601    0     0    362      0 --:--:--  0:00:01 --:--:--   362
100 36.6M  100 36.6M    0     0  2822k      0  0:00:13  0:00:13 --:--:-- 4899k
~ > docker-machine version
docker-machine version 0.6.0, build e27fb87

~> curl -L https://github.com/docker/machine/releases/download/v0.6.0/docker-machine-`uname -s`-`uname -m` >/usr/local/bin/docker-machine && \

~> chmod +x /usr/local/bin/docker-machine

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

Dload Upload Total Spent Left Speed

100 601 0 601 0 0 362 0 --:--:-- 0:00:01 --:--:-- 362

100 36.6M 100 36.6M 0 0 2822k 0 0:00:13 0:00:13 --:--:-- 4899k

~ > docker-machine version

docker-machine version 0.6.0, build e27fb87

docker-machine now shows the Docker server version:

~ > docker-machine ls
NAME        ACTIVE   DRIVER       STATE     URL                         SWARM   DOCKER    ERRORS
couchbase   -        virtualbox   Running   tcp://192.168.99.100:2376           v1.9.1    
netbeans    -        virtualbox   Saved                                         Unknown

~ > docker-machine ls

NAME ACTIVE DRIVER STATE URL SWARM DOCKER ERRORS

couchbase - virtualbox Running tcp://192.168.99.100:2376 v1.9.1

netbeans - virtualbox Saved Unknown

The latest server version is 1.10. And so docker upgrade command can be used to fix that:

~ > docker-machine upgrade couchbase
Waiting for SSH to be available...
Detecting the provisioner...
Upgrading docker...
Stopping machine to do the upgrade...
Upgrading machine "couchbase"...
Default Boot2Docker ISO is out-of-date, downloading the latest release...
Latest release for github.com/boot2docker/boot2docker is v1.10.0
Downloading /Users/arungupta/.docker/machine/cache/boot2docker.iso from https://github.com/boot2docker/boot2docker/releases/download/v1.10.0/boot2docker.iso...
0%....10%....20%....30%....40%....50%....60%....70%....80%....90%....100%
Copying /Users/arungupta/.docker/machine/cache/boot2docker.iso to /Users/arungupta/.docker/machine/machines/couchbase/boot2docker.iso...
Starting machine back up...
(couchbase) Check network to re-create if needed...
(couchbase) Waiting for an IP...
Restarting docker...

~ > docker-machine upgrade couchbase

Waiting for SSH to be available...

Detecting the provisioner...

Upgrading docker...

Stopping machine to do the upgrade...

Upgrading machine "couchbase"...

Default Boot2Docker ISO is out-of-date, downloading the latest release...

Latest release for github.com/boot2docker/boot2docker is v1.10.0

Downloading /Users/arungupta/.docker/machine/cache/boot2docker.iso from https://github.com/boot2docker/boot2docker/releases/download/v1.10.0/boot2docker.iso...

0%....10%....20%....30%....40%....50%....60%....70%....80%....90%....100%

Copying /Users/arungupta/.docker/machine/cache/boot2docker.iso to /Users/arungupta/.docker/machine/machines/couchbase/boot2docker.iso...

Starting machine back up...

(couchbase) Check network to re-create if needed...

(couchbase) Waiting for an IP...

Restarting docker...

The updated list of Machines is now shown as:

~ > docker-machine ls
NAME        ACTIVE   DRIVER       STATE     URL                         SWARM   DOCKER    ERRORS
couchbase   -        virtualbox   Running   tcp://192.168.99.100:2376           v1.10.0   
netbeans    -        virtualbox   Saved                                         Unknown

~ > docker-machine ls

NAME ACTIVE DRIVER STATE URL SWARM DOCKER ERRORS

couchbase - virtualbox Running tcp://192.168.99.100:2376 v1.10.0

netbeans - virtualbox Saved Unknown

Notice that Docker version is now 1.10.

Set up the environment variables such that Docker client can talk to it:

eval $(docker-machine env couchbase)

eval $(docker-machine env couchbase)

Docker Client 1.10

Lets download the latest client to connect to this Docker Engine.

> curl https://get.docker.com/builds/Darwin/x86_64/docker-latest > /usr/local/bin/docker
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100 10.0M  100 10.0M    0     0  3836k      0  0:00:02  0:00:02 --:--:-- 3836k
> docker version
Client:
 Version:      1.10.0
 API version:  1.22
 Go version:   go1.5.3
 Git commit:   590d5108
 Built:        Thu Feb  4 19:55:25 2016
 OS/Arch:      darwin/amd64

Server:
 Version:      1.10.0
 API version:  1.22
 Go version:   go1.5.3
 Git commit:   590d5108
 Built:        Thu Feb  4 19:55:25 2016
 OS/Arch:      linux/amd64

> curl https://get.docker.com/builds/Darwin/x86_64/docker-latest > /usr/local/bin/docker

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

Dload Upload Total Spent Left Speed

100 10.0M 100 10.0M 0 0 3836k 0 0:00:02 0:00:02 --:--:-- 3836k

> docker version

Client:

Version: 1.10.0

API version: 1.22

Go version: go1.5.3

Git commit: 590d5108

Built: Thu Feb 4 19:55:25 2016

OS/Arch: darwin/amd64

Server:

Version: 1.10.0

API version: 1.22

Go version: go1.5.3

Git commit: 590d5108

Built: Thu Feb 4 19:55:25 2016

OS/Arch: linux/amd64

Client and Server versions are shown separately.

Run Couchbase container as:

~ > docker run -d -p 8091-8093:8091-8093 -p 11210:11210 arungupta/couchbase-node
4783d72298d1f27255f12cf765ed1121c7656d09a866bc350354e38787627a79

~ > docker run -d -p 8091-8093:8091-8093 -p 11210:11210 arungupta/couchbase-node

4783d72298d1f27255f12cf765ed1121c7656d09a866bc350354e38787627a79

This starts up a fully-configured Couchbase server. It can be accessed at 192.168.99.100:8091 and looks like as shown:

Note, 192.168.99.100 is obtained using docker-machine ip <MACHINE-NAME>.

Couchbase Developer Portal provide more details about the Couchbase Server.

Docker Compose 1.6.0

Docker Compose is a tool for defining and running complex applications with Docker. With Compose, you define a multi-container application in a single file, then spin your application up in a single command which does everything that needs to be done to get it running.

Learn more about Docker Compose 1.6.0.

Install the latest version:

curl -L https://github.com/docker/compose/releases/download/1.6.0/docker-compose-`uname -s`-`uname -m` > /usr/local/bin/docker-compose
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
100   601    0   601    0     0   1067      0 --:--:-- --:--:-- --:--:--  1065
100 4837k  100 4837k    0     0   945k      0  0:00:05  0:00:05 --:--:-- 1426k
chmod +x /usr/local/bin/docker-compose

curl -L https://github.com/docker/compose/releases/download/1.6.0/docker-compose-`uname -s`-`uname -m` > /usr/local/bin/docker-compose

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

Dload Upload Total Spent Left Speed

0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0

100 601 0 601 0 0 1067 0 --:--:-- --:--:-- --:--:-- 1065

100 4837k 100 4837k 0 0 945k 0 0:00:05 0:00:05 --:--:-- 1426k

chmod +x /usr/local/bin/docker-compose

The experimental flags --x-networking and --x-network-driver, introduced in Compose 1.5, have been removed. Its no longer experimental and is the recommended way to enable communication between containers.

Compose 1.6.0 requires Docker Engine 1.9.1 or later, or 1.10.0 if you’re using version 2 of the Compose File format.

Updating Compose File

Compose 1.6 introduces a new version of the Compose file. Read more details about Upgrading Compose File.

Compose 1.6 will continue to run older version of Compose files. But now networking and volumes are first class citizens.

Here is an example of version 1 of Compose file:

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

mycouchbase:

image: arungupta/couchbase-node

ports:

- 8091:8091

- 8092:8092

- 8093:8093

- 11210:11210

Here is a version 2 of Compose file:

version: "2"
services:
  mycouchbase:
    image: arungupta/couchbase
    ports:
      - 8091:8091
      - 8092:8092 
      - 8093:8093 
      - 11210:11210

version: "2"

services:

mycouchbase:

image: arungupta/couchbase

ports:

- 8091:8091

- 8092:8092

- 8093:8093

- 11210:11210

For simple use cases, the two main changes are:

Add a version: '2' line at the top of the file.
Indent the whole file by one level and put a services: key at the top.

Running services in this Compose file is:

~ > docker-compose up -d
Creating network "couchbase_default" with the default driver
Pulling mycouchbase (arungupta/couchbase:latest)...
latest: Pulling from arungupta/couchbase
a50d2b3f7efa: Already exists
27e1b0c788a2: Already exists
622b8fa00f81: Already exists
a3ed95caeb02: Pull complete
0bc56fd185bd: Already exists
10f0979b6cbd: Already exists
9be3d8460ed2: Already exists
59e718ec07e9: Already exists
a0b9aa29408d: Already exists
e2717fa0b388: Pull complete
Digest: sha256:9131c5a283d79e11b6556c94b0b0f8ceba7daf5ba5982bac850100099019959f
Status: Downloaded newer image for arungupta/couchbase:latest
Creating couchbase_mycouchbase_1

~ > docker-compose up -d

Creating network "couchbase_default" with the default driver

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

latest: Pulling from arungupta/couchbase

a50d2b3f7efa: Already exists

27e1b0c788a2: Already exists

622b8fa00f81: Already exists

a3ed95caeb02: Pull complete

0bc56fd185bd: Already exists

10f0979b6cbd: Already exists

9be3d8460ed2: Already exists

59e718ec07e9: Already exists

a0b9aa29408d: Already exists

e2717fa0b388: Pull complete

Digest: sha256:9131c5a283d79e11b6556c94b0b0f8ceba7daf5ba5982bac850100099019959f

Status: Downloaded newer image for arungupta/couchbase:latest

Creating couchbase_mycouchbase_1

This starts a fully configured Couchbase server based upon the image as explained at github.com/arun-gupta/docker-images/tree/master/couchbase-node.

Docker Swarm 1.1

Docker Swarm is native clustering for Docker. It allows you to create and access 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.

A new experimental support for container rescheduling on node failure is added.

Read more details about setting up Docker Swarm Cluster.

Finally, here are some useful links:

Docker Toolbox 1.10
Docker 1.10 Release Notes
Docker 1.10 Security Improvements
Docker for Java Developers

Enjoy!

Deploy Docker to Amazon Cloud using Tutum

February 3, 2016containers, couchbase, techtipcloud, couchbase, docker, tutumarungupta

Have you felt the need to run Docker containers on Amazon?

Amazon Container Service requires extensive setup and manual work. This is meant for programmers who have plenty of time and willing to debug through multiple steps. For mundane programmers, like me, who like simple and easy to use steps, there is Docker Tutum!

What is Docker Tutum?

Docker Tutum is a SaaS that allows you to build, deploy and manage Docker containers in a variety of clouds.

Docker Hosting Tutum

There are three main features:

Build and run your code using Tutum’s free private registry
Deploy applications using Tutum to manage Clusters that are fault tolerant and scalable. Tutum handles the orchestration of your infrastructure and application containers.
Manage your applications through Tutum’s intuitive Dashboard, simple API, or CLI tool. With built-in logs and data monitoring, all the info you need is at your fingertips.

The main party line is:

Experience the simplicity of PaaS with none of its constraints. Enjoy the flexibility of IaaS with none of its complexity.

How Docker Tutum Works?

Key Concepts of Docker Tutum

The main concepts of Docker Tutum are explained below:

Docker Tutum Architecture

(A) Node clusters are logical groups of nodes of the same type. Tutum pools your nodes resources, so your apps can run together thereby reducing complexity and waste. Node Clusters can be easily scaled with a drag of the slider.
(B) Nodes are individual Linux hosts/VMs used to deploy and run your applications. New nodes can be provisioned right from within Tutum to increase the capacity of your Node Clusters.
(C) Containers, (D) Links and (E) Volumes are Docker concepts.
(F) Services are logical groups of Docker containers from the same image. Services make it simple to scale your application across different nodes. Simply drag a slider to increase or decrease the availability, performance, and redundancy of your application.

Deploy Couchbase Docker Container on Amazon using Tutum

Docker Tutum Getting Started provides detailed steps on how to get started. Here is what I did to run Couchbase Docker container in Amazon using Docker Tutum:

Get started for free (at least while its in beta) by logging in using Docker Hub account.
Link Amazon Web Services credentials with Tutum. I just had to specify Access Key Id and Secret Access Key.If you create a new account for this then you may have to attach a policy to enable privileges such that new instances can be provisioned on your behalf.
Create a new node cluster at dashboard.tutum.co/node/launch/
The three values that need to be specified/changed:
- Node cluster name
- Deploy tags (optional)
- Type/size to t2.medium
- Disk size reduce from 60 to 20 GB
Takes a few minutes to provision the AMI. Updated status could be seen on AWS Console:

Tutum dashboard shows the following status after the node is created:
Create your first service at dashboard.tutum.co/container/launch/. Select “Public Repositories” and search for “arungupta/couchbase-node”.
This image is created from github.com/arun-gupta/docker-images/tree/master/couchbase-node. This image performs the following:
- Starts Couchbase server
- Configures the server using Couchbase REST API
Click on “Select” and configure. You only need to override the ports and take all other defaults:
Click on “Create and Deploy”.
Dashboard is updated after the service is deployed:
Click on “Logs” to see logs from the Couchbase Docker container:
Find IP address from the AWS Console:
Access Couchbase Console at <IP-ADDRESS>:8091, in our case 54.67.111.235:8091. This will show the login screen:

Enter the username “Administrator” and password “password”.
This shows the Couchbase Console:

Create/Access Sample Bucket on Couchbase

Click on “Settings”, “Sample Buckets”. This shows the list of sample buckets that can be installed.
Select “travel-sample” and click on “Create”. The updated console looks like:

If you’ve downloaded Couchbase server locally, then you can use Couchbase Query CLI Tool (cbq) to connect and query:

bin > ./cbq -engine=http://54.67.111.235:8093
Couchbase query shell connected to http://54.67.111.235:8093/ . Type Ctrl-D to exit.
cbq> select * from `travel-sample` limit 1;
{
    "requestID": "aec63fba-a85a-4763-9453-1d7ea0c5409c",
    "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": "10.135335ms",
        "executionTime": "10.091507ms",
        "resultCount": 1,
        "resultSize": 300
    }
}

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

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

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

{

"requestID": "aec63fba-a85a-4763-9453-1d7ea0c5409c",

"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": "10.135335ms",

"executionTime": "10.091507ms",

"resultCount": 1,

"resultSize": 300

}

Couchbase allows to query document database using SQL-like syntax, aka N1QL.

So this blog showed:

What is Docker Tutum?
How to get started with Docker Tutum?
Deploy Couchbase Docker container on Amazon using Tutum
Create/Access sample bucket on Couchbase

More details:

Docker Tutum Getting Started
Docker Tutum Support
Docker Tutum Web Dashboard
Docker Tutum API
Docker Tutum CLI
Docker Tutum Python SDK
Docker Tutum Go SDK

Enjoy!

Originally posted at: http://blog.couchbase.com/2016/deploy-docker-amazon-cloud-tutum

Couchbase Weekly Feb 1, 2016

February 1, 2016couchbasecouchbase, weeklyarungupta

Learn what’s latest in the Couchbase Community.
Couchbase Developer Community

Let us know if we missed anything at @couchbasedev, @couchbase or #Couchbase.

February 4: Couchbase Day Santa Monica

Press Releases

Couchbase Supports @WalmartLab’s Release of OneOps Cloud Management to Open Source Community
Move to open source enables any organization to run Couchbase and other technologies in the cloud with easy portability and best-in-class management tools
2015 Marks Another Outstanding Year of Innovation and Growth for Couchbase
Couchbase increasingly selected as the database to power companies in the Digital Economy

Media Mentions

LinuxInsider: Walmart Opens OneOps Cloud Management to the Masses
ChannelWorld (India): Couchbase: Accelerating Productivity by Removing Impedance Mismatch
WSJ’s The Morning Download: The Morning Download: Cloud, Once an Adjunct to Data Center, Now Drives Corporate IT
Ars Technica: A New Open Source Cloud Management Tool… from Walmart
Cloud Pro (UK):Walmart’s OneOps Cloud Management Now Available on GitHub
EFY Times: OneOPS, an Open Source Platform by Walmart
Leader Call: Walmart Open Sources Its OneOps Technology
ProgrammableWeb: WalmartLabs Releases OneOps Cloud and Application Lifecycle Management Platform as Open Source
DZone: Reporting JSON Data with Couchbase and PowerBI
NewsFactor Network: Walmart Open Sources Its OneOps Cloud Platform
Transparency Market Research Press Release: Global NoSQL Market Driven by Rapid Generation of Large Amounts of Data
TechCrunch: Walmart Launches OneOps, an Open-Source Cloud and Application Lifecycle Management Platform
CIO: Walmart Open-Sources OneOps to Free You from Cloud Lock-in
GeekWire: Ignition Partners Invests in Docker’s Series D Round, which Valued Company at $1B
ComputerWeekly (UK): Getting Dirty with Open Source Databases
Voice&Data (IN): “ALTEN Calsoft Labs Is in a Very Good Position to Help Indian Startups Develop Their Business”
451 Research: NoSQL Analytics Market Looks Ripe for Acquisitions

Blogs

Talking Beacons, IoT, P2P and Couchbase Mobile — Laurent Doguin
NetBeans Plugin for Couchbase Part 2 – Coffee on Couchbase — Arun Gupta
Migrating from Parse to Couchbase Mobile — William Hoang
Why is Couchbase Mobile a Great Solution for Modern App Development? — Nic Raboy
Anti-Virus False Alarms and Couchbase — Don Pinto
I use Parse. They’re shutting down. What should I do? — Wayne Carter
Couchbase is at FOSDEM — Laura Czajkowski
How to use Channels in Sync Gateway — William Hoang
Create a Desktop Chat Application using the CEAN Stack and Electron — Nic Raboy
Couchbase Weekly Jan 25, 2016 — Arun Gupta
Moving SQL business logic to the Application Layer — Laurent Doguin
Locating cbq — Matthew Revell
20 ways to connect with Couchbase Community — Arun Gupta
Moving SQL database content to Couchbase — Laurent Doguin
How to Validate Document Types in Sync Gateway — William Hoang

Upcoming Events

February 4: Couchbase Day Santa Monica
February 8 – 10: Jfokus, Stockholm
February 15 – 17: DevNexus 2016, Stockholm
February 18: Couchbase Day Seattle
February 18: Couchbase Day Reston
February 22: Couchbase Day New York

Webinars

5-part webinar series for building a fullstack application using the CEAN stack — for EMEA series see here, for US series see here.

Couchbase Meetups

February 18: Couchbase Silicon Valley

Other People Meetups (OPMs)

February 10: JavaMug, Dallas
February 12: UmeJUG, Sweden

Facebook #Parse calls it quits leaving 600K #developers with one question – whats next? #Couchbase Mobile http://ow.ly/XMrEV
Amadeus and Google use #Couchbase to maximize throughput for 1500 cores in 3 data centers spanning US, Europe & Asia ow.ly/XodDO
Configure #Simba and #Couchbase to directly execute schemaless #N1QL queries #SQL for #JSON http://ow.ly/WZemi
Walmart extends its leadership in the #DigitalEconomy releasing their OneOps cloud management tool http://ow.ly/XyCSx #opensource
In 2015, #Couchbase continued to lead the #NoSQL market in product innovation and nearly doubled sales http://ow.ly/XyWdq

Originally posted at: blog.couchbase.com/2016/february/couchbase-weekly-feb1-2016