<commit_before># cf-riak-cs-release

A BOSH release for Riak and Riak CS.

Make sure to run `./update` (to update git submodules) before creating the release.

This project is based on [BrianMMcClain/riak-release](https://github.com/BrianMMcClain/riak-release).

## Deployment

1.  First create the release, naming it `cf-riak-cs`.
1.  Then upload the release.
1.  Finally make sure you have uploaded the appropriate stemcell for your deployment (either vsphere or warden)

### Configurations common to both environments
1. SSL:
	* There are two properties under properties.riak-cs called `ssl_enabled` and `skip_ssl_validation`
	* `ssl_enabled` is defaulted to true and `skip_ssl_validation` defaults to false, which will only work if you have valid certs on your CF deployment
	* If you wish to change either of these, you can create a stub with these properties set to your needs:
```  properties:
        riak_cs:
    	    ssl_enabled: <your value>
    	    skip_ssl_validation: <your value>
```


### To a BOSH-lite environment

1. Create a stub file called `riak-cs-lite-stub.yml` that contains your director UUID (which you can get from running `bosh status`):

		director_uuid: your-director-guid-here
		properties:
		  domain: your-cf-system-domain-here   # such as 10.244.0.34.xip.io

2. Generate the manifest: `./generate_deployment_manifest warden riak-cs-lite-stub.yml > riak-cs-lite.yml`
To tweak the deployment settings, you can modify the resulting file `riak-cs-lite.yml`.
3. To deploy: `bosh deployment riak-cs-lite.yml && bosh deploy`

### To a vSphere environment
<commit_msg>Update broker and enable ssl capabilities<commit_after># cf-riak-cs-release

A BOSH release for Riak and Riak CS.

Make sure to run `./update` (to update git submodules) before creating the release.

This project is based on [BrianMMcClain/riak-release](https://github.com/BrianMMcClain/riak-release).

## Deployment

1.  First create the release, naming it `cf-riak-cs`.
1.  Then upload the release.
1.  Finally make sure you have uploaded the appropriate stemcell for your deployment (either vsphere or warden)

### Configurations common to both environments
1. SSL:
	* There are two properties under properties.riak-cs called `ssl_enabled` and `skip_ssl_validation`
	* `ssl_enabled` is defaulted to true and `skip_ssl_validation` defaults to false, which will only work if you have valid certs on your CF deployment
	* If you wish to change either of these, you can create a stub with these properties set to your needs:
<<<<<<< HEAD
```  properties:
        riak_cs:
    	    ssl_enabled: <your value>
    	    skip_ssl_validation: <your value>
=======
```  
properties:
  riak_cs:
    ssl_enabled: <your value>
    skip_ssl_validation: <your value>
>>>>>>> Update broker and enable ssl capabilities
```


### To a BOSH-lite environment

1. Create a stub file called `riak-cs-lite-stub.yml` that contains your director UUID (which you can get from running `bosh status`):

		director_uuid: your-director-guid-here
		properties:
		  domain: your-cf-system-domain-here   # such as 10.244.0.34.xip.io

2. Generate the manifest: `./generate_deployment_manifest warden riak-cs-lite-stub.yml > riak-cs-lite.yml`
To tweak the deployment settings, you can modify the resulting file `riak-cs-lite.yml`.
3. To deploy: `bosh deployment riak-cs-lite.yml && bosh deploy`

### To a vSphere environment

{'fraction_non_alphanumeric': 0.09386068476977567, 'fraction_numerical': 0.00885478158205431, 'mean_word_length': 3.991163475699558, 'pattern_counts': {'":': 0, '<': 16, '<?xml version=': 0, '>': 18, 'https://': 2, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 2, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '435395', 'n_tokens_mistral': 1108, 'n_tokens_neox': 1035, 'n_words': 404}