chore(workflow): change minio to storage

Author: duanhongyi

.gitignore

@@ -23,3 +23,4 @@ _build/
 
 .DS_Store
 .idea/*
+.vscode/

README.md

@@ -21,7 +21,7 @@ Please see below for links and descriptions of each component:
 - [monitor](https://github.com/drycc/monitor) - The platform monitoring components
 - [influxdb](https://github.com/drycc/influxdb) - The monitor database
 - [rabbitmq](https://github.com/drycc/rabbitmq) - RabbitMQ is a message broker used with controller celery
-- [minio](https://github.com/drycc/minio) - The in-cluster, ephemeral, development-only object storage system
+- [storage](https://github.com/drycc/storage) - The in-cluster, ephemeral, development-only object storage system
 - [workflow-cli](https://github.com/drycc/workflow-cli) - Workflow CLI `drycc`
 
 We welcome your input! If you have feedback, please [submit an issue][issues]. If you'd like to participate in development, please read the "Working on Documentation" section below and [submit a pull request][prs].

_scripts/install.sh

@@ -352,15 +352,15 @@ redis:
     size: ${REDIS_PERSISTENCE_SIZE:-5Gi}
     storageClass: ${REDIS_PERSISTENCE_STORAGE_CLASS:-""}
 
-minio:
-  zone: ${MINIO_ZONE:-1}
-  drives: ${MINIO_DRIVES:-4}
-  replicas: ${MINIO_REPLICAS:-1}
+storage:
+  zone: ${STORAGE_ZONE:-1}
+  drives: ${STORAGE_DRIVES:-4}
+  replicas: ${STORAGE_REPLICAS:-1}
   imageRegistry: ${DRYCC_REGISTRY}
   persistence:
     enabled: true
-    size: ${MINIO_PERSISTENCE_SIZE:-20Gi}
-    storageClass: ${MINIO_PERSISTENCE_STORAGE_CLASS:-""}
+    size: ${STORAGE_PERSISTENCE_SIZE:-20Gi}
+    storageClass: ${STORAGE_PERSISTENCE_STORAGE_CLASS:-""}
 
 rabbitmq:
   imageRegistry: ${DRYCC_REGISTRY}

charts/workflow/Chart.yaml

@@ -23,9 +23,9 @@ dependencies:
 - name: logger
   version: <logger-tag>
   repository: https://charts.drycc.cc/stable/logger
-- name: minio
-  version: <minio-tag>
-  repository: https://charts.drycc.cc/stable/minio
+- name: storage
+  version: <storage-tag>
+  repository: https://charts.drycc.cc/stable/storage
 - name: monitor
   version: <monitor-tag>
   repository: https://charts.drycc.cc/stable/monitor

charts/workflow/values.yaml

@@ -3,7 +3,7 @@
 # If the service is used by a component alone, it needs to be configured inside the component.
 # Refer to rabbitmqUrl and databaseUrl of the controller component. 
 # If the service is dependent on multiple components and there is state synchronization,
-# it needs to be configured separately, such as minio and influxdb.
+# it needs to be configured separately, such as storage and influxdb.
 
 global:
   # Admin email, used for each component to send email to administrator
@@ -12,9 +12,9 @@ global:
   # Set the location of Workflow's Object Storage
   #
   # Valid values are:
-  # - on-cluster: Run minio within the Kubernetes cluster
-  # - off-cluster: Run Object Storage outside the Kubernetes cluster (Compatible with s3 API)
-  minioLocation: "on-cluster"
+  # - on-cluster: Run drycc storage within the Kubernetes cluster
+  # - off-cluster: Run Storage outside the Kubernetes cluster (Compatible with s3 API)
+  storageLocation: "on-cluster"
 
   # Set the location of Workflow's PostgreSQL database
   #
@@ -91,15 +91,15 @@ global:
   # - off-cluster: Use passport outside the Kubernetes cluster
   passportLocation: "on-cluster"
 
-minio:
+storage:
   # bucket lookup supported by the server.
   # Valid options are '[dns, path]'
-  # When the minio is off-cluster, this value can be set
+  # When the storage is off-cluster, this value can be set
   # Otherwise, Hard coded as `path`
   lookup: "path"
-  # endpoint configuration is only available in off-cluster minio database
+  # endpoint configuration is only available in off-cluster storage
   endpoint: ""
-  # If minio is off-cluster, accesskey and secretkey must be specified
+  # If storage is off-cluster, accesskey and secretkey must be specified
   # Otherwise, they are generated randomly, if they are empty
   accesskey: ""
   secretkey: ""
@@ -108,12 +108,12 @@ minio:
   builderBucket: "drycc-builder-bucket"
   registryBucket: "drycc-registry-bucket"
   databaseBucket: "drycc-database-bucket"
-  # Configure the following ONLY if you want persistence for on-cluster minio
+  # Configure the following ONLY if you want persistence for on-cluster storage
   persistence:
     enabled: false # Set to true to enable persistence
     accessMode: ReadWriteOnce
     size: 5Gi # PVC size
-    ## minio data Persistent Volume Storage Class
+    ## storage data Persistent Volume Storage Class
     ## If defined, storageClassName: <storageClass>
     ## If set to "-", storageClassName: "", which disables dynamic provisioning
     ## If undefined (the default) or set to null, no storageClassName spec is

src/_includes/install-workflow.md

@@ -57,7 +57,7 @@ drycc-database-rad1o           1/1       Running   0          5m
 drycc-logger-fluentd-1v8uk     1/1       Running   0          5m
 drycc-logger-fluentd-esm60     1/1       Running   0          5m
 drycc-logger-sm8b3             1/1       Running   0          5m
-drycc-minio-4ww3t              1/1       Running   0          5m
+drycc-storage-4ww3t              1/1       Running   0          5m
 drycc-registry-asozo           1/1       Running   1          5m
 drycc-rabbitmq-0               1/1       Running   0          5m
 ```

src/installing-workflow/configuring-object-storage.md

@@ -2,14 +2,14 @@
 
 A variety of Drycc Workflow components rely on an object storage system to do their work including storing application slugs, Docker images and database logs.
 
-Drycc Workflow ships with [Minio][minio] by default, which provides in-cluster, ephemeral object storage. This means that _if the Minio server crashes, all data will be lost_. Therefore, **Minio should be used for development or testing only**.
+Drycc Workflow ships with [Storage][storage] by default, which provides in-cluster.
 
 ## Configuring off-cluster Object Storage
 
 Every component that relies on object storage uses two inputs for configuration:
 
 1. You must use object storage services that are compatible with S3 API
-2. Access credentials stored as a Kubernetes secret named `minio-creds`
+2. Access credentials stored as a Kubernetes secret named `storage-creds`
 
 The helm chart for Drycc Workflow can be easily configured to connect Workflow components to off-cluster object storage. Drycc Workflow currently supports Google Compute Storage, Amazon S3, [Azure Blob Storage][] and OpenStack Swift Storage.
 
@@ -50,6 +50,6 @@ Operators should configure object storage by editing the Helm values file before
 You are now ready to run `helm install drycc/workflow --namespace drycc -f values.yaml` using your desired object storage.
 
 
-[minio]: ../understanding-workflow/components.md#object-storage
+[storage]: ../understanding-workflow/components.md#object-storage
 [aws-iam]: http://docs.aws.amazon.com/IAM/latest/UserGuide/introduction.html
 [Azure Blob Storage]: https://azure.microsoft.com/en-us/services/storage/blobs/

src/installing-workflow/index.md

@@ -82,7 +82,7 @@ $ helm install --namespace drycc \
     --set influxdb.imageRegistry=quay.io \
     --set rabbitmq.imageRegistry=quay.io \
     --set logger.imageRegistry=quay.io \
-    --set minio.imageRegistry=quay.io \
+    --set storage.imageRegistry=quay.io \
     --set monitor.imageRegistry=quay.io \
     --set registry.imageRegistry=quay.io \
     --set registry-proxy.imageRegistry=quay.io \
@@ -120,7 +120,7 @@ drycc-influxdb-2729788615-m9b5n           1/1       Running   0          4m
 drycc-logger-176328999-wjckx              1/1       Running   4          4m
 drycc-logger-fluentd-zxnqb                1/1       Running   0          4m
 drycc-redis-304849759-1f35p               1/1       Running   0          4m
-drycc-minio-676004970-nxqgt               1/1       Running   0          4m
+drycc-storage-676004970-nxqgt               1/1       Running   0          4m
 drycc-monitor-grafana-432627134-lnl2h     1/1       Running   0          4m
 drycc-monitor-telegraf-wmcmn              1/1       Running   1          4m
 drycc-registry-756475849-lwc6b            1/1       Running   1          4m

src/installing-workflow/ingress.md

@@ -41,7 +41,7 @@ Depending on the order in which the Workflow components initialize, some pods ma
 installation: if a component's dependencies are not yet available, that component will exit and Kubernetes will
 automatically restart it.
 
-Here, it can be seen that the controller, builder and registry all took a few loops waiting for minio before they were able to start:
+Here, it can be seen that the controller, builder and registry all took a few loops waiting for storage before they were able to start:
 
 ```
 $ kubectl --namespace=drycc get pods
@@ -53,7 +53,7 @@ drycc-database-rad1o           1/1       Running   0          5m
 drycc-logger-fluentd-1v8uk     1/1       Running   0          5m
 drycc-logger-fluentd-esm60     1/1       Running   0          5m
 drycc-logger-sm8b3             1/1       Running   0          5m
-drycc-minio-4ww3t              1/1       Running   0          5m
+drycc-storage-4ww3t              1/1       Running   0          5m
 drycc-registry-asozo           1/1       Running   1          5m
 drycc-rabbitmq-0               1/1       Running   0          5m
 ```

src/installing-workflow/system-requirements.md

@@ -22,8 +22,7 @@ Workflow also supports the [OSB](https://github.com/openservicebrokerapi/service
 A variety of Drycc Workflow components rely on an object storage system to do their work, including storing application
 slugs, Docker images and database logs.
 
-Drycc Workflow ships with Minio by default, which provides in-cluster, ephemeral object storage. This means that if the
-Minio server crashes, all data will be lost. Therefore, Minio should be used for development or testing only.
+Drycc Workflow ships with drycc storage by default, which provides in-cluster.
 
 Workflow supports Amazon Simple Storage Service (S3), Google Cloud Storage (GCS), OpenShift Swift, and Azure Blob
 Storage. See [configuring object storage](configuring-object-storage) for setup instructions.