openstack/openstack-helm
Code Issues Proposed changes

[docs] updating-common-to-helm-toolkit

Browse Source 
* replaced common with helm-toolkit
* common was removed
This commit is contained in:
gardlt 2017-02-22 13:41:38 -06:00
parent 5f0ffce99b
commit afdc47d7cc
3 changed files with 13 additions and 13 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

22
README.md
View File

@ -32,17 +32,17 @@ To verify your Helm chart version, once the repository has been added, issue the
``` ```
$ helm search | grep openstack-helm $ helm search | grep openstack-helm
local/bootstrap 0.1.0 openstack-helm namespace bootstrap local/bootstrap 0.1.0 openstack-helm namespace bootstrap
openstack-helm/bootstrap 0.1.0 openstack-helm namespace bootstrap openstack-helm/bootstrap 0.1.0 openstack-helm namespace bootstrap
openstack-helm/ceph 0.1.0 A Helm chart for Kubernetes openstack-helm/ceph 0.1.0 A Helm chart for Kubernetes
openstack-helm/common 0.1.0 A base chart for all openstack charts openstack-helm/helm-toolkit 0.1.0 A base chart for all openstack charts
openstack-helm/glance 0.1.0 A Helm chart for glance openstack-helm/glance 0.1.0 A Helm chart for glance
openstack-helm/horizon 0.1.0 A Helm chart for horizon openstack-helm/horizon 0.1.0 A Helm chart for horizon
openstack-helm/keystone 0.1.0 A Helm chart for keystone openstack-helm/keystone 0.1.0 A Helm chart for keystone
openstack-helm/mariadb 0.1.0 A helm chart for mariadb openstack-helm/mariadb 0.1.0 A helm chart for mariadb
openstack-helm/memcached 0.1.0 Chart for memcached openstack-helm/memcached 0.1.0 Chart for memcached
openstack-helm/openstack 0.1.0 A Helm chart for Kubernetes openstack-helm/openstack 0.1.0 A Helm chart for Kubernetes
openstack-helm/rabbitmq 0.1.0 A Helm chart for Kubernetes openstack-helm/rabbitmq 0.1.0 A Helm chart for Kubernetes
$ $
``` ```

2
docs/developer/minikube.md
View File

@ -166,7 +166,7 @@ After following the instructions above your environment is in a state where you
Consider the following when using Minikube and development mode: Consider the following when using Minikube and development mode:
* Persistent Storage used for Minikube development mode is `hostPath`. The Ceph PVC's included with this project are not intended to work with Minikube. * Persistent Storage used for Minikube development mode is `hostPath`. The Ceph PVC's included with this project are not intended to work with Minikube.
* There is *no need* to install the `common` `ceph` or `bootstrap` charts. These charts are required for deploying Ceph PVC's. * There is *no need* to install the `helm-toolkit` `ceph` or `bootstrap` charts. These charts are required for deploying Ceph PVC's.
* Familiarize yourself with `values.yaml` included with the MariaDB chart. You will want to have the `storage_path` directory created prior to deploying MariaDB. This value will be used as the deployment's `hostPath`. * Familiarize yourself with `values.yaml` included with the MariaDB chart. You will want to have the `storage_path` directory created prior to deploying MariaDB. This value will be used as the deployment's `hostPath`.
* If Ceph development is required, you will need to follow the [getting started guide](https://github.com/att-comdev/openstack-helm/blob/master/docs/installation/getting-started.md) rather than this development mode documentation. * If Ceph development is required, you will need to follow the [getting started guide](https://github.com/att-comdev/openstack-helm/blob/master/docs/installation/getting-started.md) rather than this development mode documentation.

2
docs/installation/getting-started.md
View File

@ -227,7 +227,7 @@ admin@kubenode01:~$ mkdir -p /var/lib/openstack-helm/ceph
## Ceph Secrets Generation ## Ceph Secrets Generation
Although you can bring your own secrets, we have conveniently created a secret generation tool for you (for greenfield deployments). You can create secrets for your project by issuing the following: Although you can bring your own secrets, we have conveniently created a secret generation tool for you (for greenfield deployments). You can create secrets for your project by issuing the following:
``` ```
admin@kubenode01:~$ cd common/utils/secret-generator admin@kubenode01:~$ cd helm-toolkit/utils/secret-generator
admin@kubenode01:~$ ./generate_secrets.sh all `./generate_secrets.sh fsid` admin@kubenode01:~$ ./generate_secrets.sh all `./generate_secrets.sh fsid`
admin@kubenode01:~$ cd ../../.. admin@kubenode01:~$ cd ../../..
``` ```