Renaming ASB -> OSBA (#58)

* Renaming ASB -> OSBA

* Open Service Broker Azure -> Open Service Broker for Azure

* Removing "the" and adding drupal changes.

README.md

@@ -6,10 +6,10 @@
 
 This repository contains [Helm](https://helm.sh/) charts for use with the
 [Kubernetes Service Catalog](https://github.com/kubernetes-incubator/service-catalog)
-and the Microsoft Azure Service Broker.
+and the Microsoft Open Service Broker for Azure.
 
 Each chart has one or more dependencies on Azure services (e.g. Azure SQL, CosmosDB, ...)
-which are fulfilled by the [Azure Service Broker](https://github.com/Azure/azure-service-broker) and
+which are fulfilled by [Open Service Broker for Azure](https://github.com/Azure/open-service-broker-azure) and
 the [Kubernetes Service Catalog](https://github.com/kubernetes-incubator/service-catalog) working
 in tandem.
 
@@ -23,7 +23,7 @@ The following charts are available:
 
 You'll need a [Kubernetes](https://kubernetes.io) cluster, version 1.7 or later,
 with [Service Catalog](https://github.com/kubernetes-incubator/service-catalog)
-and [Azure Service Broker](https://github.com/Azure/azure-service-broker) 
+and [Open Service Broker for Azure](https://github.com/Azure/open-service-broker-azure) 
 installed on it.
 
 Please see [the prerequisities guide](./docs/prerequisities/README.md) for 

concourse/README.md

@@ -4,7 +4,7 @@
 
 This chart bootstraps a [Concourse](https://concourse.ci/) deployment on a [Kubernetes](https://kubernetes.io) cluster using the [Helm](https://helm.sh) package manager.
 
-It is inspired by the [upstream Concourse chart](https://github.com/kubernetes/charts/tree/master/stable/concourse) but, by default, uses the [Azure Service Broker](https://github.com/Azure/azure-service-broker) to provision an [Azure Database for PostgreSQL](https://azure.microsoft.com/services/postgresql/) for Concourse to use.
+It is inspired by the [upstream Concourse chart](https://github.com/kubernetes/charts/tree/master/stable/concourse) but, by default, uses [Open Service Broker for Azure](https://github.com/Azure/open-service-broker-azure) to provision an [Azure Database for PostgreSQL](https://azure.microsoft.com/services/postgresql/) for Concourse to use.
 
 ## Basic Installation 
 
@@ -22,7 +22,7 @@ You will need the following before you can install this chart:
 
 - Kubernetes 1.7+ with RBAC turned on and beta APIs enabled
 - [Service Catalog](https://github.com/kubernetes-incubator/service-catalog) installed
-- The [Azure Service Broker](https://github.com/Azure/azure-service-broker) installed
+- [Open Service Broker for Azure](https://github.com/Azure/open-service-broker-azure) installed
 - Support for persistent volumes in the underlying infrastructure
 
 Please see the [prerequisities document](../docs/prerequisities/README.md) for

docs/prerequisities/README.md

@@ -6,7 +6,7 @@ In order to use the charts in this repository, you must have the following compo
 (version 1.7 or later)
 1. [Helm](https://github.com/kubernetes/helm)
 1. [Kubernetes Service Catalog](https://github.com/kubernetes-incubator/service-catalog)
-1. [Azure Service Broker](https://github.com/azure/azure-service-broker)
+1. [Open Service Broker for Azure](https://github.com/azure/open-service-broker-azure)
 
 This document describes how to install all these pre-requisities.
 
@@ -106,10 +106,10 @@ helm install svc-cat/catalog --name catalog --namespace catalog
 _If you'd like a more advanced installation, see the 
 [Service Catalog installation documentation](https://github.com/kubernetes-incubator/service-catalog/blob/master/docs/install.md)._
 
-# Step 4: Install the Azure Service Broker
+# Step 4: Install Open Service Broker For Azure
 
 After you've successfully installed service catalog, you'll need to install
-the [Azure Service Broker](https://github.com/azure/azure-service-broker).
+[Open Service Broker for Azure](https://github.com/azure/open-service-broker-azure).
 
 To do so, please follow the 
-[installation instructions for Azure Service Broker](https://github.com/Azure/helm-charts/tree/master/azure-service-broker).
+[installation instructions for Open Service Broker for Azure](https://github.com/Azure/helm-charts/tree/master/open-service-broker-azure).

drupal/README.md

@@ -9,7 +9,7 @@ a [Kubernetes](http://kubernetes.io) cluster using the [Helm](https://helm.sh)
 
 It is inspired by the
 [upstream drupal chart](https://github.com/kubernetes/charts/tree/master/stable/drupal,
-but, by default, utilizes the Azure Service Broker to provision an
+but, by default, utilizes Open Service Broker for Azure to provision an
 [Azure Database for MySQL](https://azure.microsoft.com/en-us/services/mysql/)
 database for the Drupal server to use.
 
@@ -35,7 +35,7 @@ You will need the following before you can install this chart:
 
 - Kubernetes 1.7+ with RBAC turned on and beta APIs enabled
 - [Service Catalog](https://github.com/kubernetes-incubator/service-catalog) installed
-- The [Azure Service Broker](https://github.com/Azure/azure-service-broker) installed
+- [Open Service Broker for Azure](https://github.com/Azure/azure-service-broker) installed
 - Support for persistent volumes in the underlying infrastructure
 
 Please see the [prerequisities document](../docs/prerequisities/README.md) for

ghost/README.md

@@ -5,7 +5,7 @@
 This chart bootstraps a [Ghost](https://github.com/bitnami/bitnami-docker-ghost) deployment on a [Kubernetes](http://kubernetes.io) cluster using the [Helm](https://helm.sh) package manager.
 
 It is inspired by the 
-[upstream ghost chart](https://github.com/kubernetes/charts/tree/master/stable/ghost), but, by default, utilizes the Azure Service Broker to provision an [Azure Database for MySQL](https://azure.microsoft.com/en-us/services/mysql/) database for the Ghost server to use.
+[upstream ghost chart](https://github.com/kubernetes/charts/tree/master/stable/ghost), but, by default, utilizes Open Service Broker For Azure to provision an [Azure Database for MySQL](https://azure.microsoft.com/en-us/services/mysql/) database for the Ghost server to use.
 
 # Basic Installation
 

open-service-broker-azure/Chart.yaml

@@ -1,14 +1,14 @@
 apiVersion: v1
-description: A Helm chart for the Azure Service Broker
-name: azure-service-broker
+description: A Helm chart for Open Service Broker For Azure
+name: open-service-broker-azure
 version: 0.1.0
 keywords:
   - azure
   - services
   - service broker
-home: https://github.com/azure/azure-service-broker
+home: https://github.com/azure/open-service-broker-azure
 sources:
-  - https://github.com/azure/azure-service-broker
+  - https://github.com/azure/open-service-broker-azure
   - https://hub.docker.com/r/microsoft/azure-service-broker/
 maintainers:
   - name: Kent Rancourt

open-service-broker-azure/README.md

@@ -1,11 +1,11 @@
-# Azure Service Broker
+# Open Service Broker for Azure
 
-[Azure Service Broker](https://github.com/Azure/azure-service-broker) is the
+[Open Service Broker for Azure](https://github.com/Azure/open-service-broker-azure) is the
 open source, [Open Service Broker](https://www.openservicebrokerapi.org/)
 compatible API server that provisions managed services in the Microsoft
 Azure public cloud.
 
-This chart bootstraps Azure Service Broker in your Kubernetes cluster.
+This chart bootstraps Open Service Broker for Azure in your Kubernetes cluster.
 
 ## Prerequisites
 
@@ -61,7 +61,7 @@ Installation of this chart is simple. First, ensure that you've [added the
 `azure` repo:
 
 ```console
-$ helm install azure/azure-service-broker --name asb --namespace asb \
+$ helm install azure/open-service-broker-azure --name osba --namespace osba \
   --set azure.subscriptionId=$AZURE_SUBSCRIPTION_ID \
   --set azure.tenantId=$AZURE_TENANT_ID \
   --set azure.clientId=$AZURE_CLIENT_ID \
@@ -84,10 +84,10 @@ $ kubectl get clusterserviceplans -o=custom-columns=NAME:.metadata.name,EXTERNAL
 
 ## Uninstalling the Chart
 
-To uninstall/delete the `asb` deployment:
+To uninstall/delete the `osba` deployment:
 
 ```console
-$ helm delete asb --purge
+$ helm delete osba --purge
 ```
 
 The command removes all the Kubernetes components associated with the chart and
@@ -100,25 +100,25 @@ Broker chart and their default values.
 
 | Parameter | Description | Default |
 | --------- | ----------- | ------- |
-| `image.repository` | Docker image location, _without_ the tag. | `"microsoft/azure-service-broker"` |
-| `image.tag` | Tag / version of the Docker image. | `"canary"`; This references an image built from the very latest, possibly unreleased source code. This value is temporary and will change once ASB and its chart both stabilize. At that time, each revision of the chart will reference a specific ASB version using an _immutable_ tag, such as a semantic version. |
-| `image.pullPolicy` | `"IfNotPresent"`, `"Always"`, or `"Never"`; When launching a pod, this option indicates when to pull the ASB Docker image. | `"Always"`; This policy complements the use of the mutable `canary` tag. This value is temporary and will change once ASB and its chart both stabalize and begin to reference images using _immutable_ tags, such as semantic versions. |
+| `image.repository` | Docker image location, _without_ the tag. | `"microsoft/open-service-broker-azure"` |
+| `image.tag` | Tag / version of the Docker image. | `"canary"`; This references an image built from the very latest, possibly unreleased source code. This value is temporary and will change once OSBA and its chart both stabilize. At that time, each revision of the chart will reference a specific OSBA version using an _immutable_ tag, such as a semantic version. |
+| `image.pullPolicy` | `"IfNotPresent"`, `"Always"`, or `"Never"`; When launching a pod, this option indicates when to pull the OSBA Docker image. | `"Always"`; This policy complements the use of the mutable `canary` tag. This value is temporary and will change once OSBA and its chart both stabalize and begin to reference images using _immutable_ tags, such as semantic versions. |
 | `registerBroker` | Whether to register this broker with the Kubernetes Service Catalog. If true, the Kubernetes Service Catalog must already be installed on the cluster. Marking this option false is useful for scenarios wherein one wishes to host the broker in a separate cluster than the Service Catalog (or other client) that will access it. | `true` |
-| `service.type` | Type of service; valid values are `"ClusterIP"`, `"LoadBalancer"`, and `"NodePort"`. `"ClusterIP"` is sufficient in the average case where ASB only receives traffic from within the cluster-- e.g. from Kubernetes Service Catalog. | `"ClusterIP"` |
+| `service.type` | Type of service; valid values are `"ClusterIP"`, `"LoadBalancer"`, and `"NodePort"`. `"ClusterIP"` is sufficient in the average case where OSBA only receives traffic from within the cluster-- e.g. from Kubernetes Service Catalog. | `"ClusterIP"` |
 | `service.nodePort.port` | _If and only if_ `service.type` is set to `"NodePort"`, `service.nodePort.port` indicates the port this service should bind to on each Kubernetes node. | `30080` |
 | `azure.environment` | Indicates which Azure public cloud to use. Valid values are `"AzureCloud"` and `"AzureChinaCloud"`. | `"AzureCloud"` |
-| `azure.subscriptionId` | Identifies the Azure subscription into which ASB will provision services. | none |
-| `azure.tenantId` | Identifies the Azure Active Directory to which the _service principal_ used by ASB to access the Azure subscription belongs. | none |
-| `azure.clientId` | Identifies the _service principal_ used by ASB to access the Azure subscription. | none |
-| `azure.clientSecret` | Key/password for the _service principal_ used by ASB to access the Azure subscription. | none |
-| `basicAuth.username` | Specifies the basic auth username that clients (e.g. the Kubernetes Service Catalog) must use when connecting to ASB. | `"username"`; __Do not use this default value in production!__ |
-| `basicAuth.password` | Specifies the basic auth password that clients (e.g. the Kubernetes Service Catalog) must use when connecting to ASB. | `"password"`; __Do not use this default value in production!__ |
-| `encryptionKey` | Specifies the key used by ASB for applying AES-256 encryption to sensitive (or potentially sensitive) data. | `"This is a key that is 256 bits!!"`; __Do not use this default value in production!__ |
-| `modules.minStability` | Specifies the minimum level of stability an ASB module must meet for the services and plans it provides to be included in ASB's catalog of offerings. Valid values are `"ALPHA"`, `"BETA"`, and `"STABLE"`. | `"ALPHA"`; __Only use `"STABLE"` modules in production!__ |
-| `redis.embedded` | ASB uses Redis for data persistence and as a message queue. This option indicates whether an on-cluster Redis deployment should be included when installing this chart. If set to `false`, connection details for a remote Redis cache must be provided. | `true`; __Do not use the embedded Redis cache in production!__ |
+| `azure.subscriptionId` | Identifies the Azure subscription into which OSBA will provision services. | none |
+| `azure.tenantId` | Identifies the Azure Active Directory to which the _service principal_ used by OSBA to access the Azure subscription belongs. | none |
+| `azure.clientId` | Identifies the _service principal_ used by OSBA to access the Azure subscription. | none |
+| `azure.clientSecret` | Key/password for the _service principal_ used by OSBA to access the Azure subscription. | none |
+| `basicAuth.username` | Specifies the basic auth username that clients (e.g. the Kubernetes Service Catalog) must use when connecting to OSBA. | `"username"`; __Do not use this default value in production!__ |
+| `basicAuth.password` | Specifies the basic auth password that clients (e.g. the Kubernetes Service Catalog) must use when connecting to OSBA. | `"password"`; __Do not use this default value in production!__ |
+| `encryptionKey` | Specifies the key used by OSBA for applying AES-256 encryption to sensitive (or potentially sensitive) data. | `"This is a key that is 256 bits!!"`; __Do not use this default value in production!__ |
+| `modules.minStability` | Specifies the minimum level of stability an OSBA module must meet for the services and plans it provides to be included in OSBA's catalog of offerings. Valid values are `"ALPHA"`, `"BETA"`, and `"STABLE"`. | `"ALPHA"`; __Only use `"STABLE"` modules in production!__ |
+| `redis.embedded` | OSBA uses Redis for data persistence and as a message queue. This option indicates whether an on-cluster Redis deployment should be included when installing this chart. If set to `false`, connection details for a remote Redis cache must be provided. | `true`; __Do not use the embedded Redis cache in production!__ |
 | `redis.host` | _If and only if_ `redis.embedded` is `false`, this option specifies the location of the remote Redis cache. | none |
 | `redis.port` | _If and only if_ `redis.embedded` is `false`, this option specifies the port to connect to on the remote Redis host. | `6380` |
-| `redis.redisPassword` | Specifies the Redis password. If `redis.embedded` is `true`, this option sets the password on the Redis cache itself _and_ provides it to ASB. If `redis.embedded` is `false`, this option only provides the password to ASB. In that case, the value of this option must be the correct password for the remote Redis cache. | `"password"`; __Do not use this default value in production!__ |
+| `redis.redisPassword` | Specifies the Redis password. If `redis.embedded` is `true`, this option sets the password on the Redis cache itself _and_ provides it to OSBA. If `redis.embedded` is `false`, this option only provides the password to OSBA. In that case, the value of this option must be the correct password for the remote Redis cache. | `"password"`; __Do not use this default value in production!__ |
 | `redis.enableTls` | _If and only if_ `redis.embedded` is `false`, this option specifies whether to use a secure connection to the remote Redis host. | `true` |
 
 Specify a value for each option using the `--set <key>=<value>` switch on the
@@ -129,8 +129,8 @@ Alternatively, copy the charts default values to a file, edit the file to your
 liking, and reference that file in your `helm install` command:
 
 ```console
-$ helm inspect values azure/azure-service-broker > values.yaml
+$ helm inspect values azure/open-service-broker-azure > values.yaml
 $ vim my-values.yaml
-$ helm install azure/azure-service-broker --name asb --namespace asb --values my-values.yaml
+$ helm install azure/open-service-broker-azure --name osba --namespace osba --values my-values.yaml
 ```
 

open-service-broker-azure/templates/NOTES.txt

@@ -1,6 +1,6 @@
 {{- if and (not .Values.registerBroker) (or (eq .Values.service.type "LoadBalancer") (eq .Values.service.type "NodePort")) }}
 {{- if eq .Values.service.type "LoadBalancer" }}
-1. To get Azure Service Broker's load balancer IP/hostname:
+1. To get Open Service Broker for Azure's load balancer IP/hostname:
 
     NOTE: It may take a few minutes for this to become available.
 
@@ -13,7 +13,7 @@
         $ kubectl describe svc {{ template "fullname" . }} -n {{ .Release.Namespace }} | grep Ingress: | awk '{print $3}'
 {{ end }}
 {{- if eq .Values.service.type "NodePort" }}
-1. Azure Service Broker's node port: {{ .Values.service.nodePort.port }}
+1. Open Service Broker for Azure's node port: {{ .Values.service.nodePort.port }}
 {{ end }}
 2. Credentials for connecting to the broker:
 

open-service-broker-azure/templates/broker.yaml

@@ -2,7 +2,7 @@
 apiVersion: servicecatalog.k8s.io/v1beta1
 kind: ClusterServiceBroker
 metadata:
-  name: asb
+  name: osba
 spec:
   url: http://{{ template "fullname" . }}.{{ .Release.Namespace }}.svc.cluster.local
   authInfo:

open-service-broker-azure/templates/deployment.yaml

@@ -21,7 +21,7 @@ spec:
         heritage: "{{ .Release.Service }}"
     spec:
       containers:
-        - name: azure-service-broker
+        - name: open-service-broker-azure
           image: {{ .Values.image.repository }}:{{ .Values.image.tag }}
           imagePullPolicy: {{ .Values.image.pullPolicy }}
           env:

phpbb/README.md

@@ -9,7 +9,7 @@ a [Kubernetes](http://kubernetes.io) cluster using the [Helm](https://helm.sh)
 
 It is inspired by the 
 [upstream phpBB chart](https://github.com/kubernetes/charts/tree/master/stable/phpbb),
-but, by default, utilizes the Azure Service Broker to provision an 
+but, by default, utilizes Open Service Broker For Azure to provision an 
 [Azure Database for MySQL](https://azure.microsoft.com/en-us/services/mysql/) 
 database for the Wordpress server to use.
 
@@ -27,7 +27,7 @@ To install this chart, you must have:
 
 - Kubernetes 1.7+ with beta APIs enabled
 - [Service-Catalog](https://github.com/kubernetes-incubator/service-catalog) installed
-- The [Azure Service Broker](https://github.com/Azure/azure-service-broker) installed
+- The [Open Service Broker for Azure](https://github.com/Azure/open-service-broker-azure) installed
 - PV provisioner support in the underlying infrastructure
 
 For details on setting up these prerequisites, please see the [prerequisites doc](https://github.com/Azure/helm-charts/tree/master/docs/prerequisities)

wordpress/README.md

@@ -11,7 +11,7 @@ a [Kubernetes](http://kubernetes.io) cluster using the [Helm](https://helm.sh)
 
 It is inspired by the 
 [upstream wordpress chart](https://github.com/kubernetes/charts/tree/master/stable/wordpress),
-but, by default, utilizes the Azure Service Broker to provision an 
+but, by default, utilizes Open Service Broker For Azure to provision an 
 [Azure Database for MySQL](https://azure.microsoft.com/en-us/services/mysql/) 
 database for the Wordpress server to use.
 
@@ -31,7 +31,7 @@ You will need the following before you can install this chart:
 
 - Kubernetes 1.7+ with RBAC turned on and beta APIs enabled
 - [Service Catalog](https://github.com/kubernetes-incubator/service-catalog) installed
-- The [Azure Service Broker](https://github.com/Azure/azure-service-broker) installed
+- The [Open Service Broker for Azure](https://github.com/Azure/open-service-broker-azure) installed
 - Support for persistent volumes in the underlying infrastructure
 
 Please see the [prerequisities document](../docs/prerequisities/README.md) for