{"id":48,"date":"2014-12-17T15:58:28","date_gmt":"2014-12-17T15:58:28","guid":{"rendered":"https:\/\/www.couchbase.com\/blog\/couchbase-blueprints-apache-brooklyn\/"},"modified":"2014-12-17T15:58:28","modified_gmt":"2014-12-17T15:58:28","slug":"couchbase-blueprints-apache-brooklyn","status":"publish","type":"post","link":"https:\/\/www.couchbase.com\/blog\/ko\/couchbase-blueprints-apache-brooklyn\/","title":{"rendered":"Couchbase Blueprints in Apache Brooklyn"},"content":{"rendered":"

This is a guest post by our friends at Cloudsoft (link<\/a>) on the Apache Brooklyn project (link<\/a>). We’re excited to be collaborating with Cloudsoft. The cloud is the new operating system, and projects like Apache Brooklyn enable the enterprise to be more efficient. What if you could deploy a dozen instances of Couchbase Server to Amazon Web Services with the click of a button?<\/p>\n\n\n\n

\n\n\n\n

Couchbase blueprints are now available in Apache Brooklyn!<\/p>\n\n\n\n

@ZaidM (GitHub<\/a>) and @Nakomis (GitHub<\/a>) have been busy on Github working with Couchbase to add support for the extremely scalable, high-performance JSON document store. With their latest commit (link<\/a>), provisioning a cluster is as easy as writing:<\/p>\n\n\n\n

name: My Couchbase Cluster
\nservices:
\n– type: brooklyn.entity.nosql.couchbase.CouchbaseCluster
\ninitialSize: 3location:
\njclouds:google-compute-engine:
\nidentity: your-gce-acct
\ncredential: your-gce-token\n<\/p>\n\n\n\n

Simply follow the instructions, unpack, and run “bin\/brooklyn launch”, then go to the web console and paste the YAML above (with your credentials).<\/p>\n\n\n\n

As soon as you deploy, the topology is shown and you can track provisioning and command execution. It all runs in parallel, due to how Brooklyn manages processing, apart from where there is an explicit dependency \u2014 such as needing to know a subset of Couchbase nodes in order for the webapp to connect. And it will run in many locations, from Amazon to OpenStack, by way of Docker or non-cloud pre-existing machines.<\/p>\n\n\n\n

After a few minutes, it’s completed, and metrics from Couchbase are monitored to ensure it’s running well and drive your custom management policies such as DR and autoscaling as we’ll show below. The sensors tabs also show the URLs for management and endpoints for clients to connect to.<\/p>\n\n\n\n

\"console-sensors.png\"<\/p>\n\n\n\n

Of course in the real world you need more. That’s where the power of the Brooklyn project shines and your Couchbase automation sparkles. Let’s illustrate a more interesting YAML which shows how to:<\/p>\n\n\n\n