Merge pull request rexray#1181 from rexray/release/0.11.2

Release 0.11.2

.docs-themes/yeti/nav.html

@@ -87,11 +87,6 @@
               {%- endblock %}
 
                 {%- block org %}
-                    <li>
-                        <a href="https://rexray.thecodeteam.com/">
-                            <i class="fa icon-thecodeteam-logo"></i>
-                        </a>
-                    </li>
                 {%- endblock %}
             </ul>
         </div>

.docs/about/contributing.md

@@ -30,7 +30,7 @@ have encountered is fixed in the git master. It is **strongly** recommended
 that you do this within a virtual environment.
 
 ```bash
-curl -sSL https://dl.bintray.com/emccode/rexray/install | sh -s -- unstable
+curl -sSL https://rexray.io/install | sh -s -- unstable
 ```
 
 ## Installing for Development

.docs/css/thecodeteam-font.css → .docs/css/rexray-font.css

@@ -1,19 +1,19 @@
 @charset "UTF-8";
 
 @font-face {
-  font-family: "thecodeteam";
-  src:url("../fonts/thecodeteam.eot");
-  src:url("../fonts/thecodeteam.eot?#iefix") format("embedded-opentype"),
-    url("../fonts/thecodeteam.woff") format("woff"),
-    url("../fonts/thecodeteam.ttf") format("truetype"),
-    url("../fonts/thecodeteam.svg#thecodeteam") format("svg");
+  font-family: "rexray";
+  src:url("../fonts/rexray.eot");
+  src:url("../fonts/rexray.eot?#iefix") format("embedded-opentype"),
+    url("../fonts/rexray.woff") format("woff"),
+    url("../fonts/rexray.ttf") format("truetype"),
+    url("../fonts/rexray.svg#rexray") format("svg");
   font-weight: normal;
   font-style: normal;
 
 }
 
 [data-icon]:before {
-  font-family: "thecodeteam" !important;
+  font-family: "rexray" !important;
   content: attr(data-icon);
   font-style: normal !important;
   font-weight: normal !important;
@@ -27,7 +27,7 @@
 
 [class^="icon-"]:before,
 [class*=" icon-"]:before {
-  font-family: "thecodeteam" !important;
+  font-family: "rexray" !important;
   font-style: normal !important;
   font-weight: normal !important;
   font-variant: normal !important;
@@ -38,10 +38,10 @@
   -moz-osx-font-smoothing: grayscale;
 }
 
-.icon-thecodeteam:before {
+.icon-rexray:before {
   content: "\63";
 }
-.icon-thecodeteam-logo:before {
+.icon-rexray-logo:before {
   content: "\6c";
 }
 .icon-rexray:before {

.docs/css/thecodeteam.css → .docs/css/rexray.css

@@ -1,7 +1,7 @@
 h1#rex-ray::before {
     content: "r";
     display: block;
-    font-family: "thecodeteam" !important;
+    font-family: "rexray" !important;
     height: 100px;
     font-size: 100px;
     margin-top: -25px;
@@ -14,15 +14,6 @@ h1#rex-ray::before {
     }
 }
 
-.navbar .icon-thecodeteam-logo:before {
-    vertical-align: middle;
-}
-
-.navbar .icon-thecodeteam-logo:after {
-    content: " {code}";
-    vertical-align: top;
-}
-
 a.headerlink {
     font-size:          0.5em;
     vertical-align:     super;

.docs/dev-guide/build-reference.md

@@ -9,7 +9,7 @@ The following one-line command is the quickest, simplest, and most
 deterministic approach to building REX-Ray:
 
 ```bash
-$ go get github.com/thecodeteam/rexray
+$ go get github.com/rexray/rexray
 ```
 
 The above command will download the REX-Ray sources and build the
@@ -21,16 +21,16 @@ produces a binary without the correct semantic version. To create
 the version information use `go generate`:
 
 ```bash
-$ go generate github.com/thecodeteam/rexray
+$ go generate github.com/rexray/rexray
 ```
 
 To download and build REX-Ray in one line with the correct version
 information please use the following command:
 
 ```bash
-$ go get -d github.com/thecodeteam/rexray && \
-  go generate github.com/thecodeteam/rexray && \
-  go install github.com/thecodeteam/rexray
+$ go get -d github.com/rexray/rexray && \
+  go generate github.com/rexray/rexray && \
+  go install github.com/rexray/rexray
 ```
 
 ### Build Tags
@@ -73,7 +73,7 @@ Travis-CI. Simply clone the REX-Ray repository (or fork) and checkout
 the desired reference. Then use the following command to build REX-Ray:
 
 ```bash
-$ SRC=github.com/thecodeteam/rexray && \
+$ SRC=github.com/rexray/rexray && \
   docker run -it \
   -e SRC -e GOOS -e GOARCH \
   -v "$(pwd)":/go/src/$SRC golang:1.8.3 \

.docs/dev-guide/project-guidelines.md

@@ -86,7 +86,7 @@ applicable. If there is ever a question of whether or not a test is applicable
 then the answer is likely yes.
 
 This project uses
-[Coveralls](https://coveralls.io/github/emccode/rexray) for code coverage, and
+[Coveralls](https://coveralls.io/github/rexray/rexray) for code coverage, and
 all pull requests are processed just as a build from `master`. If a pull request
 decreases the project's code coverage, the pull request will be declined until
 such time that testing is added or enhanced to compensate.
@@ -97,15 +97,15 @@ following:
 
 ```sh
 $ .build/test.sh
-ok  	github.com/thecodeteam/rexray/rexray/cli	0.039s	coverage: 33.6% of statements
-ok  	github.com/thecodeteam/rexray/test	0.080s	coverage: 94.0% of statements in github.com/thecodeteam/rexray, github.com/thecodeteam/rexray/core
+ok  	github.com/rexray/rexray/rexray/cli	0.039s	coverage: 33.6% of statements
+ok  	github.com/rexray/rexray/test	0.080s	coverage: 94.0% of statements in github.com/rexray/rexray, github.com/rexray/rexray/core
 ...
-ok  	github.com/thecodeteam/rexray/util	0.024s	coverage: 100.0% of statements
+ok  	github.com/rexray/rexray/util	0.024s	coverage: 100.0% of statements
 [0]akutz@pax:rexray$
 ```
 
 The file `test.sh` in the `.build` directory is the same script executed during
-the project's [automated build system](travis-ci.org/emccode/rexray). The only
+the project's [automated build system](travis-ci.org/rexray/rexray). The only
 difference is when executed locally the results are not submitted to Coveralls.
 Still, using the `test.sh` file one can easily determine if a package's coverage
 has decreased and if additional testing is necessary.

.docs/dev-guide/release-process.md

@@ -26,8 +26,8 @@ or `stable` release.
 
 ## Review Issues & Pull Requests
 The first step to a release is to review the outstanding
-[issues](https://github.com/thecodeteam/rexray/issues) and
-[pull requests](https://github.com/thecodeteam/rexray/pulls) that are tagged for
+[issues](https://github.com/rexray/rexray/issues) and
+[pull requests](https://github.com/rexray/rexray/pulls) that are tagged for
 the release in question.
 
 If there are outstanding issues requiring changes or pending pull requests to
@@ -116,7 +116,7 @@ Release Type | Tag Format | Example
 ### Tag Methods
 There are two ways to tag a release:
 
-  1. [GitHub Releases](https://github.com/thecodeteam/rexray/releases/new)
+  1. [GitHub Releases](https://github.com/rexray/rexray/releases/new)
   2. Command Line
 
 ### Command Line

.docs/index.md

@@ -23,7 +23,7 @@ The following command will install the latest version of REX-Ray to
 `/usr/bin/rexray` on Linux systems:
 
 ```sh
-$ curl -sSL https://dl.bintray.com/emccode/rexray/install | sh
+$ curl -sSL https://rexray.io/install | sh
 ```
 
 Depending on the Linux distribution REX-Ray will be registered as
@@ -128,9 +128,9 @@ The following storage providers and platforms are supported by REX-Ray.
 | | [EFS](./user-guide/storage-providers.md#aws-efs) | ✓ | ✓ | ✓ |
 | | [S3FS](./user-guide/storage-providers.md#aws-s3fs) | ✓ | ✓ | ✓ |
 | Ceph | [RBD](./user-guide/storage-providers.md#ceph-rbd) | ✓ | ✓ | ✓ |
-| Local | [CSI-BlockDevices](https://github.com/thecodeteam/csi-blockdevices) | | ✓ | ✓ |
-| | [CSI-NFS](https://github.com/thecodeteam/csi-nfs) | ✓ | ✓ | ✓ |
-| | [CSI-VFS](https://github.com/thecodeteam/csi-vfs) | | ✓ | ✓ |
+| Local | [CSI-BlockDevices](https://github.com/rexray/csi-blockdevices) | | ✓ | ✓ |
+| | [CSI-NFS](https://github.com/rexray/csi-nfs) | ✓ | ✓ | ✓ |
+| | [CSI-VFS](https://github.com/rexray/csi-vfs) | | ✓ | ✓ |
 | Dell EMC | [Isilon](./user-guide/storage-providers.md#dell-emc-isilon) | ✓ | ✓ | ✓ |
 | | [ScaleIO](./user-guide/storage-providers.md#dell-emc-scaleio) | ✓ | ✓ | ✓ |
 | DigitalOcean | [Block Storage](./user-guide/storage-providers.md#do-block-storage) | ✓ | ✓ | ✓ |
@@ -174,6 +174,6 @@ Marathon          | Docker, Mesos Containerizer
 
 ### GitHub and Slack
 If a little extra help is needed, please don't hesitate to use [GitHub
-issues](https://github.com/thecodeteam/rexray/issues) or join the active
+issues](https://github.com/rexray/rexray/issues) or join the active
 conversation on the [{code} by Dell EMC Community Slack
 Team](http://community.codedellemc.com/) in the #project-rexray channel

.docs/user-guide/examples/demo.md

@@ -25,10 +25,10 @@ $ cd $(mktemp -d)
 ```
 
 Inside the newly created, temporary directory, download the REX-Ray
-[Vagrantfile](https://github.com/emccode/rexray/master/Vagrantfile):
+[Vagrantfile](https://github.com/rexray/rexray/master/Vagrantfile):
 
 ```sh
-$ curl -fsSLO https://raw.githubusercontent.com/emccode/rexray/master/Vagrantfile
+$ curl -fsSLO https://raw.githubusercontent.com/rexray/rexray/master/Vagrantfile
 ```
 
 Now it is time to bring the REX-Ray environment online:

.docs/user-guide/installation.md

@@ -34,23 +34,23 @@ and install it to `/usr/bin/rexray` or `/opt/bin/rexray`. On Linux systems
 REX-Ray will also be registered as either a SystemD or SystemV service.
 
 ```bash
-$ curl -sSL https://dl.bintray.com/emccode/rexray/install | sh -s -- stable
+$ curl -sSL https://rexray.io/install | sh -s -- stable
 ```
 
 ### Install a specific version
 The following command will emit a list of the available REX-Ray packages:
 The curl command can also be used to install a specific version of REX-Ray:
 
 ```bash
-$ curl -sSL https://dl.bintray.com/emccode/rexray/install | sh -s -- list
-curl -sSL https://dl.bintray.com/emccode/rexray/install | sh -s -- list unstable
-curl -sSL https://dl.bintray.com/emccode/rexray/install | sh -s -- list staged
-curl -sSL https://dl.bintray.com/emccode/rexray/install | sh -s -- list stable
+$ curl -sSL https://rexray.io/install | sh -s -- list
+curl -sSL https://rexray.io/install | sh -s -- list unstable
+curl -sSL https://rexray.io/install | sh -s -- list staged
+curl -sSL https://rexray.io/install | sh -s -- list stable
 ```
 
 To install the stable `0.9.1` release, use the following command:
 ```bash
-$ curl -sSL https://dl.bintray.com/emccode/rexray/install | sh -s -- stable 0.9.1
+$ curl -sSL https://rexray.io/install | sh -s -- stable 0.9.1
 ```
 
 ### Install a pre-built binary
@@ -62,9 +62,9 @@ the various release types.
 
     Version  | Description
     ---------|------------
-    [Unstable](https://dl.bintray.com/emccode/rexray/unstable/latest/) | The most up-to-date, bleeding-edge, and often unstable REX-Ray binaries.
-    [Staged](https://dl.bintray.com/emccode/rexray/staged/latest/) | The most up-to-date, release candidate REX-Ray binaries.
-    [Stable](https://dl.bintray.com/emccode/rexray/stable/latest/) | The most up-to-date, stable REX-Ray binaries.
+    [Unstable](https://dl.bintray.com/rexray/rexray/unstable/latest/) | The most up-to-date, bleeding-edge, and often unstable REX-Ray binaries.
+    [Staged](https://dl.bintray.com/rexray/rexray/staged/latest/) | The most up-to-date, release candidate REX-Ray binaries.
+    [Stable](https://dl.bintray.com/rexray/rexray/stable/latest/) | The most up-to-date, stable REX-Ray binaries.
 
 2. Uncompress and move the binary to the proper location. Preferably `/usr/bin`
 should be where REX-Ray is moved, but this path is not required.
@@ -75,7 +75,7 @@ with SystemD or SystemV for proper initialization.
 It is also easy to build REX-Ray from source:
 
 ```bash
-$ go get github.com/thecodeteam/rexray
+$ go get github.com/rexray/rexray
 ```
 
 For more information on how to build REX-Ray please see the
@@ -121,21 +121,21 @@ configuration management and orchestration tools.
 
 ### Ansible
 With Ansible, installing the latest REX-Ray binaries can be accomplished by
-including the `emccode.rexray` role from Ansible Galaxy.  The role accepts
+including the `rexray.rexray` role from Ansible Galaxy.  The role accepts
 all the necessary variables to properly fill out your `config.yml` file.
 
 Install the role from Galaxy:
 
 ```sh
-$ ansible-galaxy install emccode.rexray
+$ ansible-galaxy install rexray.rexray
 ```
 
 Example playbook for installing REX-Ray on GCE Docker hosts:
 
 ```yaml
 - hosts: gce_docker_hosts
   roles:
-  - { role: emccode.rexray,
+  - { role: rexray.rexray,
       rexray_service: true,
       rexray_storage_drivers: [gce],
       rexray_gce_keyfile: "/opt/gce_keyfile" }
@@ -181,7 +181,7 @@ data via the AWS GUI, it would not sustain scalable automation.
         "/usr/sbin/usermod -G docker ubuntu\n",
 
         "# Install the latest REX-ray\n",
-        "/usr/bin/curl -ssL -o /tmp/install-rexray.sh https://dl.bintray.com/emccode/rexray/install\n",
+        "/usr/bin/curl -ssL -o /tmp/install-rexray.sh https://rexray.io/install\n",
         "chmod +x /tmp/install-rexray.sh\n",
         "/tmp/install-rexray.sh\n",
         "chgrp docker /etc/rexray/config.yml\n",
@@ -201,7 +201,7 @@ drivers.
 1. SSH into the Docker machine and install REX-Ray.
 
         $ docker-machine ssh testing1 \
-        "curl -sSL https://dl.bintray.com/emccode/rexray/install | sh"
+        "curl -sSL https://rexray.io/install | sh"
 
 2. Install the udev extras package. This step is only required for versions of
    boot2docker older than 1.10.
@@ -248,7 +248,7 @@ resources:
             chmod +x /tmp/install-docker.sh
             /tmp/install-docker.sh
             /usr/sbin/usermod -G docker ubuntu
-            /usr/bin/curl -ssL -o /tmp/install-rexray.sh https://dl.bintray.com/emccode/rexray/install
+            /usr/bin/curl -ssL -o /tmp/install-rexray.sh https://rexray.io/install
             chmod +x /tmp/install-rexray.sh
             /tmp/install-rexray.sh
             chgrp docker /etc/rexray/config.yml

.docs/user-guide/servers/csi.md

@@ -20,9 +20,9 @@ idempotent as well. Not only that, but REX-Ray supports native CSI plug-ins!
 | | [EFS](../storage-providers/aws.md#aws-efs) | ✓ | ✓ | ✓ |
 | | [S3FS](../storage-providers/aws.md#aws-s3fs) | ✓ | ✓ | ✓ |
 | Ceph | [RBD](../storage-providers/ceph.md#ceph-rbd) | ✓ | ✓ | ✓ |
-| Local | [CSI-BlockDevices](https://github.com/thecodeteam/csi-blockdevices) | | ✓ | ✓ |
-| | [CSI-NFS](https://github.com/thecodeteam/csi-nfs) | ✓ | ✓ | ✓ |
-| | [CSI-VFS](https://github.com/thecodeteam/csi-vfs) | | ✓ | ✓ |
+| Local | [CSI-BlockDevices](https://github.com/rexray/csi-blockdevices) | | ✓ | ✓ |
+| | [CSI-NFS](https://github.com/rexray/csi-nfs) | ✓ | ✓ | ✓ |
+| | [CSI-VFS](https://github.com/rexray/csi-vfs) | | ✓ | ✓ |
 | Dell EMC | [Isilon](../storage-providers/dellemc.md#dell-emc-isilon) | ✓ | ✓ | ✓ |
 | | [ScaleIO](../storage-providers/dellemc.md#dell-emc-scaleio) | ✓ | ✓ | ✓ |
 | DigitalOcean | [Block Storage](../storage-providers/digitalocean.md#do-block-storage) | ✓ | ✓ | ✓ |
@@ -93,7 +93,7 @@ value.
 A CSI client does not care whether or not REX-Ray's CSI server is
 operating in bridge or native mode. However, for the purposes of the
 examples below, native mode will be used in order to leverage the
-[CSI-VFS](https://github.com/thecodeteam/csi-vfs) plug-in as it's
+[CSI-VFS](https://github.com/rexray/csi-vfs) plug-in as it's
 portable and works on Linux and Darwin.
 
 First, export the `CSI_ENDPOINT` location for both the server and
@@ -104,7 +104,7 @@ $ export CSI_ENDPOINT=csi.sock
 ```
 
 Next, start a REX-Ray CSI server in native mode (the default CSI plug-in
-in native mode is [CSI-VFS](https://github.com/thecodeteam/csi-vfs)):
+in native mode is [CSI-VFS](https://github.com/rexray/csi-vfs)):
 
 ```bash
 $ X_CSI_DRIVER=csi-vfs \
@@ -119,10 +119,10 @@ $ X_CSI_DRIVER=csi-vfs \
 
 Now that a CSI server is running, it's time to access it. To do that a
 CSI client is needed, such as
-[`csc`](https://github.com/thecodeteam/gocsi/tree/master/csc):
+[`csc`](https://github.com/rexray/gocsi/tree/master/csc):
 
 ```bash
-$ go get github.com/thecodeteam/gocsi/csc
+$ go get github.com/rexray/gocsi/csc
 ```
 
 Once installed, the `csc` program can be used to create a volume:

.docs/user-guide/servers/libstorage.md

@@ -749,7 +749,7 @@ encoded token string.
 
 ### Embedded Configuration
 If libStorage is embedded into another application, such as
-[`REX-Ray`](https://github.com/thecodeteam/rexray), then that application may
+[`REX-Ray`](https://github.com/rexray/rexray), then that application may
 manage its own configuration and supply the embedded libStorage instance
 directly with a configuration object. In this scenario, the libStorage
 configuration files are ignored in deference to the embedding application.
@@ -989,9 +989,9 @@ remote storage systems. Currently the following storage drivers are supported:
  | | [EFS](./../storage-providers/aws.md#aws-efs) | ✓ | ✓ | ✓ |
  | | [S3FS](./../storage-providers/aws.md#aws-s3fs) | ✓ | ✓ | ✓ |
  | Ceph | [RBD](./../storage-providers/ceph.md#ceph-rbd) | ✓ | ✓ | ✓ |
- | Local | [CSI-BlockDevices](https://github.com/thecodeteam/csi-blockdevices) | | ✓ | ✓ |
- | | [CSI-NFS](https://github.com/thecodeteam/csi-nfs) | | ✓ | ✓ |
- | | [CSI-VFS](https://github.com/thecodeteam/csi-vfs) | | ✓ | ✓ |
+ | Local | [CSI-BlockDevices](https://github.com/rexray/csi-blockdevices) | | ✓ | ✓ |
+ | | [CSI-NFS](https://github.com/rexray/csi-nfs) | | ✓ | ✓ |
+ | | [CSI-VFS](https://github.com/rexray/csi-vfs) | | ✓ | ✓ |
  | Dell EMC | [Isilon](./../storage-providers/dellemc.md#dell-emc-isilon) | ✓ | ✓ | ✓ |
  | | [ScaleIO](./../storage-providers/dellemc.md#dell-emc-scaleio) | ✓ | ✓ | ✓ |
  | DigitalOcean | [Block Storage](./../storage-providers/digitalocean.md#do-block-storage) | ✓ | ✓ | ✓ |