VizierDB/docker
1
0
Fork 0
Code Issues Pull requests Packages Projects Releases Wiki Activity

readme

Browse source
This commit is contained in:
Mike 2019-02-15 13:43:25 -05:00
parent ba6dc0dedd
commit 1e54bb2347
1 changed files with 3 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

5
Readme.md
View file

@ -18,7 +18,7 @@ Vizier has a number of components that are not trivial to set up manually:
* [MimirDB] - virtual probabalistic database * [MimirDB] - virtual probabalistic database
* [Proxy] - a reverse proxy that provides an endpoint for vizier services * [Proxy] - a reverse proxy that provides an endpoint for vizier services
* [Apache Spark] - distributed data processing * [Apache Spark] - distributed data processing
* [Hadoop] - evented I/O for the backend * [Hadoop] - distributed data processing
* [S3] - optional data staging endpoint * [S3] - optional data staging endpoint
* [Analytics] - optional vizier ui access tracking * [Analytics] - optional vizier ui access tracking
@ -36,7 +36,7 @@ microk8s.enable dns dashboard
Once your cluster is ready, get the [yaml file](https://vizierdb.info/assets/vizier-deployment.yaml) for deploying Vizier and make the following adjustments: Once your cluster is ready, get the [yaml file](https://vizierdb.info/assets/vizier-deployment.yaml) for deploying Vizier and make the following adjustments:
- update the host paths for the persistant volumes if you would like them somewhere other than /mnt/ (YAML Line 15, 28, 41, 310) - update the host paths for the persistent volumes if you would like them somewhere other than /mnt/ (YAML Line 15, 28, 41, 310)
- update the s3-credentials secret with your S3 access key id and secret - base64 encode them first: (YAML Line 330, 331) - update the s3-credentials secret with your S3 access key id and secret - base64 encode them first: (YAML Line 330, 331)
```sh ```sh
echo "YOUR-S3-ACCESS-KEY-ID" | base64 echo "YOUR-S3-ACCESS-KEY-ID" | base64
@ -58,6 +58,7 @@ kubectl get service vizier-proxy
``` ```
After you have the IP of the vizier-proxy service you need to add the following entries to either DNS for a real domain or the hosts file of the client: so where VIZIER_DOMAIN=vizier.dev After you have the IP of the vizier-proxy service you need to add the following entries to either DNS for a real domain or the hosts file of the client: so where VIZIER_DOMAIN=vizier.dev
| IP Address | Host Name | Purpose | | IP Address | Host Name | Purpose |
| ------ | ------ | ------ | | ------ | ------ | ------ |
| <IP of vizier-proxy service> | demo.vizier.dev | web ui for vizier | | <IP of vizier-proxy service> | demo.vizier.dev | web ui for vizier |