
Couchbase Server is a NoSQL document database with a distributed architecture for performance, scalability, and availability. It enables developers to build applications easier and faster by leveraging the power of SQL with the flexibility of JSON.
Preparations The version CoreOS Stable 1010.6 Docker 1.10.3 CoucheBase 4.5.0 The prerequisites to deploy this stackThese should be routine by now:
Internet access A linux shell ACloudwatt account with avalid keypair The tools of the trade: OpenStack CLI A local clone of the Cloudwatt applications git repository Size of the instanceBy default, the stack deploys on an instance of type “Standard 2” (n1.cw.standard-2). A variety of other instance flavors exist to suit your various needs, allowing you to pay only for the services you need. Instances are charged by the minute and capped at their monthly price (you can find more details on theTarifs page on the Cloudwatt website).
Stack parameters, of course, are yours to tweak at your fancy.
What will you find in the repositoryOnce you have cloned the github, you will find in the blueprint-coreos-couchbase/ repository:
blueprint-coreos-couchbase.heat.yml : HEAT orchestration template. It will be used to deploy the necessary infrastructure. stack-start.sh : Stack launching script. This is a small script that will save you some copy-paste. Start-up Initialize the environmentHave your Cloudwatt credentials in hand and clickHERE. If you are not logged in yet, you will go thru the authentication screen then the script download will start. Thanks to it, you will be able to initiate the shell accesses towards the Cloudwatt APIs.
Source the downloaded file in your shell. Your password will be requested.
$ source COMPUTE-[...]-openrc.sh Please enter your OpenStack Password:Once this done, the Openstack command line tools can interact with your Cloudwatt user account.
Adjust the parametersIn the blueprint-coreos-couchbase.heat.yml file (heat template), you will find a section named parameters near the top. The only mandatory parameter is the keypair_name . The keypair_name ’s default value should contain a valid keypair with regards to your Cloudwatt user account, if you wish to have it by default on the console.
Within these heat templates, you can also adjust (and set the defaults for) the instance type by playing with the flavor_name parameter accordingly.
By default, the stack network and subnet are generated for the stack. This behavior can be changed within the blueprint-coreos-couchbase.heat.yml file as well, if need be, although doing so may be cause for security concerns.
heat_template_version: 2013-05-23 description: Blueprint CoreOS Couchbase parameters: keypair_name: default: keypair <-- Indicate here your keypair description: Keypair to inject in instance label: SSH Keypair type: string flavor_name: default: n1.cw.standard-1 <-- Indicate here flavor size description: Flavor to use for the deployed instance type: string label: Instance Type (Flavor) constraints: - allowed_values: - n1.cw.standard-1 - n1.cw.standard-2 - n1.cw.standard-4 - n1.cw.standard-8 - n1.cw.standard-12 - n1.cw.standard-16 volume_size: default: 5 <-- Indicate here volume size label: Backup Volume Size description: Size of Volume for couchbase Storage (Gigabytes) type: number constraints: - range: { min: 5, max: 10000 } description: Volume must be at least 10 gigabytes volume_type: default: standard <-- Indicate here volume type label: Backup Volume Type description: Performance flavor of the linked Volume for couchbase Storage type: string constraints: - allowed_values: - standard - performant [...] Start the stackIn a shell, run the script stack-start.sh :
$ ./stack-start.sh couchbase +--------------------------------------+------------+--------------------+----------------------+ | id | stack_name | stack_status | creation_time | +--------------------------------------+------------+--------------------+----------------------+ | xixixx-xixxi-ixixi-xiixxxi-ixxxixixi | couchbase | CREATE_IN_PROGRESS | 2025-10-23T07:27:69Z | +--------------------------------------+------------+--------------------+----------------------+Within 5 minutes the stack will be fully operational. (Use watch to see the status in real-time)
$ watch -n 1 heat stack-list +--------------------------------------+------------+-----------------+----------------------+ | id | stack_name | stack_status | creation_time | +--------------------------------------+------------+-----------------+----------------------+ | xixixx-xixxi-ixixi-xiixxxi-ixxxixixi | couchbase | CREATE_COMPLETE | 2025-10-23T07:27:69Z | +--------------------------------------+------------+-----------------+----------------------+ That’s fine but… I already came out of my shell in order to couchbase… do I have to go back?Nah, you can keep your eyes on the browser: all CoucheBase setup can be accomplished from the console.
To create our Couchbase stack from the console:
Go the Cloudwatt Github in the applications/blueprint-coreos-couchbase repository Click on the file named blueprint-coreos-couchbase.heat.yml Click on RAW, a web page will appear containing purely the template Save the file to your PC. You can use the default name proposed by your browser (just remove the .txt) Go to the Stacks section of the console Click on Launch stack, then Template file and select the file you just saved to your PC, and finally click on NEXT Name your stack in the Stack name field Enter the name of your keypair in the SSH Keypair field and few other fields required Choose your instance size using the Instance Type dropdown and click on LAUNCHThe stack will be automatically generated (you can see its progress by clicking on its name). When all modules become green, the creation will be complete. You can then go to the “Instances” menu to find the floating-IP, or simply refresh the current page and check the Overview tab for a handy link.
If you’ve reached this point, Couchbase is running!
A one-click sounds really nice…… Good! Go to theApps page on the Cloudwatt website, choose the apps, press DEPLOY and follow the simple steps… You have your Couchbase!
EnjoyOnce all of this done, stack’s description can be obtained with the following command :
$ heat stack-show couchbase +-----------------------+-----------