https://github.com/mayadata-io/director-charts-internal
https://github.com/mayadata-io/director-charts-internal
Last synced: 5 months ago
JSON representation
- Host: GitHub
- URL: https://github.com/mayadata-io/director-charts-internal
- Owner: mayadata-io
- Created: 2019-05-29T17:37:03.000Z (about 7 years ago)
- Default Branch: master
- Last Pushed: 2021-05-18T11:12:36.000Z (about 5 years ago)
- Last Synced: 2025-07-07T08:42:31.897Z (11 months ago)
- Language: Smarty
- Size: 4.52 MB
- Stars: 0
- Watchers: 12
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
# Maya OpenEBS Director
1.x Plan
https://docs.google.com/spreadsheets/d/12i1HKknQ_5vXd6bZst42AMyR_lTPdkkb4Svnr4fnxzo/edit?usp=sharing
# Workflow for adding/updating helm charts for end users
TODO
## Goals
1. Define a well documented workflow so that a developer adds/modifies some flags in 1.n release, such that in 1.(n+1) release the dev/ops doesn't need to add the flag back again.
## Challenges
1. The flags values might end up being different on [DC, mayadata-io/director-charts](https://github.com/mayadata-io/director-charts) & [DCI, mayadata-io/director-charts-internal](https://github.com/mayadata-io/director-charts-internal)
## Differences b/w DC & DCI configuration
1. The Google Analytics tracking is disabled on DCI but enabled on DC, see the `featureAnalyticsDisable` key in values.yaml
## Steps to bring up MOD on Packet
### Prerequisite
```
1.Deploy openebs(0.9.0 and above) and create a storagepoolclaim using external disks and create a storageClass name cstor-storage-class.
2.Create a github Oauth app and have the client id,secret and auth enable ready.
3.Create a slack bot and have the client id and client secret ready.
```
### Deploying OpenEBS Director
1. Do git clone of the repositories (https://github.com/mayadata-io/enterprise-manifest.git).
2. cd /enterprise-manifest/1.0.0/RC1
3. Execute deploy.sh script and fill in the required values.
```
For Example:
ENTER NAMESPACE for OpenEBS Director
default
ENTER URl for OpenEBS Director
(This should be one of the Node IPs)
Note: The OpenEBS Director requires a Url for which can be any node IP.
ENTER Enabler
github_user:107XXXX
ENTER Client ID
xxxxa151827ecf0cxxxx
ENTER Secret
xxxx42fcaf547f1f593xxxxd66709bfd0d746xxxx
Email address
Email PASS
botclientid
xxxx25606770.30002626xxxx
bot client secret
xxxx93387e8cxxxx7d4358197d9cxxxx
```
4.Installation of MOD will start.
5.Wait till all the MOD pods come up in running state.
6.You can open MOD webconsole in browser with the NodeIp provided in Step 3.
Note:Pods take time to come in running state which you can verify by using watch kubectl get pods.
## Uninstalltion steps:
1. Below command will clean up the MOD installation.
```
kubectl delete -f /enterprise-manifest/1.0.0/RC1/deploy.yaml
kubectl delete pvc cassandra-data-cassandra-0 cassandra-data-cassandra-1 cassandra-data-cassandra-2 data-mysql-0 elasticsearch-logging-elasticsearch-logging-0
kubectl delete jobs -l openebs.io/cas-type=jiva
```
2.Cleaning up the repo:
a. git reset --hard
b. git clean -fd
3. Delete deploy.yaml file from /enterprise-manifest/1.0.0/RC1/
```
rm deploy.yaml
```
## Steps to bring up MOD on Rancher
< TO DO >
## Current limitations and notes