Cloud foundry broker for HBase.

To use hbase-broker, you need to build it from sources configure, deploy, create instance and bind it to your app. Follow steps described below.

Run command for compile and package.:

mvn clean package

Broker automatically bind to an existing kerberos provide service. This will provide default kerberos configuration, for REALM and KDC host. Before deploy check:

• if kerberos service does not exists in your space, you can create it with command:

cf cups kerberos-service -p '{ "kdc": "kdc-host", "kpassword": "kerberos-password", "krealm": "kerberos-realm", "kuser": "kerberos-user" }'

• if kerberos-service exists in your space, you can update it with command:

cf uups kerberos-service -p '{ "kdc": "kdc-host", "kpassword": "kerberos-password", "krealm": "kerberos-realm", "kuser": "kerberos-user" }'

Push broker binary code to cloud foundry (use cf client).:

cf push hbase-broker -p target/hbase-broker-*.jar -m 512M -i 1 --no-start

For strict separation of config from code (twelve-factor principle), configuration must be placed in environment variables.

Broker configuration params list (environment properties):

• obligatory
  • USER_PASSWORD - password to interact with service broker
  • HADOOP_PROVIDED_ZIP - list of hbase configuration parameters exposed by service (json format, default: {})
• optional :
  • BASE_GUID - base id for catalog plan creation (uuid)
  • CF_CATALOG_SERVICENAME - service name in cloud foundry catalog (default: hbase)
  • CF_CATALOG_SERVICEID - service id in cloud foundry catalog (default: hbase)
  • ZK_BRK_SPACE - (default: /broker)

For instance.:

cf se hbase-broker ZKCLUSTER_URL 10.10.9.145:2181,10.10.9.146:2181

HBASE client configuration must be set via HADOOP_PROVIDED_ZIP environment variable. Param hbase.zookeeper.quorum is required. Description of this process is this same as in HDFS broker case ( https://github.com/trustedanalytics/hdfs-broker/ ).

Use cf client :

cf start  hbase-broker

Use cf client :

cf create-service-broker hbase-broker <user> <password> https://hbase-broker.<platform_domain>
cf enable-service-access hbase
cf cs hbase bare hbase-instance

Broker instance can be bind with cf client :

cf bs <app> hbase-instance

or by configuration in app's manifest.yml :

  services:
    - hbase-instance

To check if broker instance is bound, use cf client :

cf env <app>

and look for :

  "hbase": [
   {
    "credentials": {
     "HADOOP_CONFIG_KEY": {
       <hbase_configuration_json>
      },
      "HADOOP_CONFIG_ZIP": {
       "description": "This is the encoded zip file of hadoop-configuration",
       "encoded_zip": "<base64 of configuration>"
      }
     "kerberos": {
      "kdc": "ip-10-10-9-198.us-west-2.compute.internal",
      "krealm": "US-WEST-2.COMPUTE.INTERNAL"
     },
    },
    "label": "hbase",
    "name": "hbase-instance",
    "plan": "bare",
    "tags": []
   }
  ]

in VCAP_SERVICES.