Vendor cleanup

Signed-off-by: Madhu Rajanna <mrajanna@redhat.com>

vendor/github.com/container-storage-interface/spec/.gitignore

@@ -1,4 +0,0 @@
-*.tmp
-.DS_Store
-.build
-*.swp

vendor/github.com/container-storage-interface/spec/.travis.yml

@@ -1,38 +0,0 @@
-# Setting "sudo" to false forces Travis-CI to use its
-# container-based build infrastructure, which has shorter
-# queue times.
-sudo: false
-
-# Use the newer Travis-CI build templates based on the
-# Debian Linux distribution "Trusty" release.
-dist: trusty
-
-# Selecting C as the language keeps the container to a
-# minimum footprint.
-language: c
-
-jobs:
-  include:
-
-    # The test stage validates that the protobuf file was updated
-    # correctly prior to being committed.
-    - stage:               test
-      script:              make
-
-    # The lang stages validate the specification using
-    # language-specific bindings.
-
-    # Lang stage: Cxx
-    - stage:               lang
-      script:              make -C lib/cxx
-
-    # Lang stage: Go
-    - stage:               lang
-      language:            go
-      go:                  1.10.4
-      go_import_path:      github.com/container-storage-interface/spec
-      install:
-        - make -C lib/go protoc
-        - make -C lib/go protoc-gen-go
-      script:
-        - make -C lib/go

vendor/github.com/container-storage-interface/spec/CONTRIBUTING.md

@@ -1,55 +0,0 @@
-# How to Contribute
-
-CSI is under [Apache 2.0](LICENSE) and accepts contributions via GitHub pull requests.
-
-Contributions require signing an individual or Corporate CLA available [here](https://github.com/container-storage-interface/spec/blob/master/CCLA.pdf) which should be signed and mailed to the [mailing list]( https://groups.google.com/forum/#!topic/container-storage-interface-community/).
-
-This document outlines some of the conventions on development workflow, commit message formatting, contact points and other resources to make it easier to get your contribution accepted.
-
-## Markdown style
-
-To keep consistency throughout the Markdown files in the CSI spec, all files should be formatted one sentence per line.
-This fixes two things: it makes diffing easier with git and it resolves fights about line wrapping length.
-For example, this paragraph will span three lines in the Markdown source.
-
-## Code style
-
-This also applies to the code snippets in the markdown files.
-
-* Please wrap the code at 72 characters.
-
-## Comments
-
-This also applies to the code snippets in the markdown files.
-
-* End each sentence within a comment with a punctuation mark (please note that we generally prefer periods); this applies to incomplete sentences as well.
-* For trailing comments, leave one space between the end of the code and the beginning of the comment.
-
-## Git commit
-
-The "system of record" for the specification is the `spec.md` file and all hand-edits of the specification should happen there.
-**DO NOT** manually edit the generated protobufs or generated language bindings.
-Once changes to `spec.md` are complete, please run `make` to update generated files.
-
-**IMPORTANT:** Prior to committing code please run `make` to ensure that your specification changes have landed in all generated files.
-
-### Commit Style
-
-Each commit should represent a single logical (atomic) change: this makes your changes easier to review.
-
-* Try to avoid unrelated cleanups (e.g., typo fixes or style nits) in the same commit that makes functional changes.
-  While typo fixes are great, including them in the same commit as functional changes makes the commit history harder to read.
-* Developers often make incremental commits to save their progress when working on a change, and then “rewrite history” (e.g., using `git rebase -i`) to create a clean set of commits once the change is ready to be reviewed.
-
-Simple house-keeping for clean git history.
-Read more on [How to Write a Git Commit Message](http://chris.beams.io/posts/git-commit/) or the Discussion section of [`git-commit(1)`](http://git-scm.com/docs/git-commit).
-
-* Separate the subject from body with a blank line.
-* Limit the subject line to 50 characters.
-* Capitalize the subject line.
-* Do not end the subject line with a period.
-* Use the imperative mood in the subject line.
-* Wrap the body at 72 characters.
-* Use the body to explain what and why vs. how.
-  * If there was important/useful/essential conversation or information, copy or include a reference.
-* When possible, one keyword to scope the change in the subject (i.e. "README: ...", "tool: ...").

vendor/github.com/container-storage-interface/spec/Makefile

@@ -1,51 +0,0 @@
-all: build
-
-CSI_SPEC := spec.md
-CSI_PROTO := csi.proto
-
-# This is the target for building the temporary CSI protobuf file.
-#
-# The temporary file is not versioned, and thus will always be
-# built on Travis-CI.
-$(CSI_PROTO).tmp: $(CSI_SPEC) Makefile
-	echo "// Code generated by make; DO NOT EDIT." > "$@"
-	cat $< | sed -n -e '/```protobuf$$/,/^```$$/ p' | sed '/^```/d' >> "$@"
-
-# This is the target for building the CSI protobuf file.
-#
-# This target depends on its temp file, which is not versioned.
-# Therefore when built on Travis-CI the temp file will always
-# be built and trigger this target. On Travis-CI the temp file
-# is compared with the real file, and if they differ the build
-# will fail.
-#
-# Locally the temp file is simply copied over the real file.
-$(CSI_PROTO): $(CSI_PROTO).tmp
-ifeq (true,$(TRAVIS))
-	diff "$@" "$?"
-else
-	diff "$@" "$?" > /dev/null 2>&1 || cp -f "$?" "$@"
-endif
-
-build: check
-
-# If this is not running on Travis-CI then for sake of convenience
-# go ahead and update the language bindings as well.
-ifneq (true,$(TRAVIS))
-build:
-	$(MAKE) -C lib/go
-	$(MAKE) -C lib/cxx
-endif
-
-clean:
-	$(MAKE) -C lib/go $@
-
-clobber: clean
-	$(MAKE) -C lib/go $@
-	rm -f $(CSI_PROTO) $(CSI_PROTO).tmp
-
-# check generated files for violation of standards
-check: $(CSI_PROTO)
-	awk '{ if (length > 72) print NR, $$0 }' $? | diff - /dev/null
-
-.PHONY: clean clobber check

vendor/github.com/container-storage-interface/spec/OWNERS

@@ -1,10 +0,0 @@
-approvers:
-  - saad-ali # Representing Kubernetes
-  - thockin # Representing Kubernetes
-  - jieyu # Representing Mesos
-  - jdef # Representing Mesos
-  - anusha-ragunathan # Representing Docker
-  - ddebroy # Representing Docker
-  - julian-hj # Representing Cloud Foundry
-  - paulcwarren # Representing Cloud Foundry
-reviewers:

vendor/github.com/container-storage-interface/spec/README.md

@@ -1,13 +0,0 @@
-# Container Storage Interface (CSI) Specification [![build status](https://travis-ci.org/container-storage-interface/spec.svg?branch=master)](https://travis-ci.org/container-storage-interface/spec)
-
-![CSI Logo](logo.png)
-
-This project contains the CSI [specification](spec.md) and [protobuf](csi.proto) files.
-
-## CSI Adoption
-
-### Container Orchestrators (CO)
-
-* [Cloud Foundry](https://github.com/cloudfoundry/csi-plugins-release/blob/master/CSI_SUPPORT.md)
-* [Kubernetes](https://kubernetes-csi.github.io/docs/)
-* [Mesos](http://mesos.apache.org/documentation/latest/csi/)

vendor/github.com/container-storage-interface/spec/VERSION

@@ -1 +0,0 @@
-1.0.0

vendor/github.com/container-storage-interface/spec/lib/README.md

@@ -1,2 +0,0 @@
-# CSI Validation Libraries
-This directory contains language bindings generated from the CSI [protobuf file](../csi.proto) used to validate the model and workflows of the CSI specification.

vendor/github.com/container-storage-interface/spec/lib/cxx/Makefile

@@ -1,9 +0,0 @@
-all: build
-
-build:
-	@echo "cxx bindings & validation"
-
-clean:
-	@echo "clean cxx"
-
-.PHONY: clean

vendor/github.com/container-storage-interface/spec/lib/go/.gitignore

@@ -1,4 +0,0 @@
-/protoc
-/protoc-gen-go
-/csi.a
-/.protoc

vendor/github.com/container-storage-interface/spec/lib/go/Makefile

@@ -1,136 +0,0 @@
-all: build
-
-########################################################################
-##                             GOLANG                                 ##
-########################################################################
-
-# If GOPATH isn't defined then set its default location.
-ifeq (,$(strip $(GOPATH)))
-GOPATH := $(HOME)/go
-else
-# If GOPATH is already set then update GOPATH to be its own
-# first element.
-GOPATH := $(word 1,$(subst :, ,$(GOPATH)))
-endif
-export GOPATH
-
-
-########################################################################
-##                             PROTOC                                 ##
-########################################################################
-
-# Only set PROTOC_VER if it has an empty value.
-ifeq (,$(strip $(PROTOC_VER)))
-PROTOC_VER := 3.5.1
-endif
-
-PROTOC_OS := $(shell uname -s)
-ifeq (Darwin,$(PROTOC_OS))
-PROTOC_OS := osx
-endif
-
-PROTOC_ARCH := $(shell uname -m)
-ifeq (i386,$(PROTOC_ARCH))
-PROTOC_ARCH := x86_32
-endif
-
-PROTOC := ./protoc
-PROTOC_ZIP := protoc-$(PROTOC_VER)-$(PROTOC_OS)-$(PROTOC_ARCH).zip
-PROTOC_URL := https://github.com/google/protobuf/releases/download/v$(PROTOC_VER)/$(PROTOC_ZIP)
-PROTOC_TMP_DIR := .protoc
-PROTOC_TMP_BIN := $(PROTOC_TMP_DIR)/bin/protoc
-
-$(PROTOC):
-	-mkdir -p "$(PROTOC_TMP_DIR)" && \
-	  curl -L $(PROTOC_URL) -o "$(PROTOC_TMP_DIR)/$(PROTOC_ZIP)" && \
-	  unzip "$(PROTOC_TMP_DIR)/$(PROTOC_ZIP)" -d "$(PROTOC_TMP_DIR)" && \
-	  chmod 0755 "$(PROTOC_TMP_BIN)" && \
-	  cp -f "$(PROTOC_TMP_BIN)" "$@"
-	stat "$@" > /dev/null 2>&1
-
-
-########################################################################
-##                          PROTOC-GEN-GO                             ##
-########################################################################
-
-# This is the recipe for getting and installing the go plug-in
-# for protoc
-PROTOC_GEN_GO_PKG := github.com/golang/protobuf/protoc-gen-go
-PROTOC_GEN_GO := protoc-gen-go
-$(PROTOC_GEN_GO): PROTOBUF_PKG := $(dir $(PROTOC_GEN_GO_PKG))
-$(PROTOC_GEN_GO): PROTOBUF_VERSION := v1.2.0
-$(PROTOC_GEN_GO):
-	mkdir -p $(dir $(GOPATH)/src/$(PROTOBUF_PKG))
-	test -d $(GOPATH)/src/$(PROTOBUF_PKG)/.git || git clone https://$(PROTOBUF_PKG) $(GOPATH)/src/$(PROTOBUF_PKG)
-	(cd $(GOPATH)/src/$(PROTOBUF_PKG) && \
-		(test "$$(git describe --tags | head -1)" = "$(PROTOBUF_VERSION)" || \
-			(git fetch && git checkout tags/$(PROTOBUF_VERSION))))
-	(cd $(GOPATH)/src/$(PROTOBUF_PKG) && go get -v -d $$(go list -f '{{ .ImportPath }}' ./...)) && \
-	go build -o "$@" $(PROTOC_GEN_GO_PKG)
-
-
-########################################################################
-##                              PATH                                  ##
-########################################################################
-
-# Update PATH with the current directory. This enables the protoc
-# binary to discover the protoc-gen-go binary, built inside this
-# directory.
-export PATH := $(shell pwd):$(PATH)
-
-
-########################################################################
-##                              BUILD                                 ##
-########################################################################
-CSI_PROTO := ../../csi.proto
-CSI_PKG_ROOT := github.com/container-storage-interface/spec
-CSI_PKG_SUB := $(shell cat $(CSI_PROTO) | sed -n -e 's/^package.\([^;]*\).v[0-9]\+;$$/\1/p'|tr '.' '/')
-CSI_BUILD := $(CSI_PKG_SUB)/.build
-CSI_GO := $(CSI_PKG_SUB)/csi.pb.go
-CSI_A := csi.a
-CSI_GO_TMP := $(CSI_BUILD)/$(CSI_PKG_ROOT)/csi.pb.go
-
-# This recipe generates the go language bindings to a temp area.
-$(CSI_GO_TMP): HERE := $(shell pwd)
-$(CSI_GO_TMP): PTYPES_PKG := github.com/golang/protobuf/ptypes
-$(CSI_GO_TMP): GO_OUT := plugins=grpc
-$(CSI_GO_TMP): GO_OUT := $(GO_OUT),Mgoogle/protobuf/descriptor.proto=github.com/golang/protobuf/protoc-gen-go/descriptor
-$(CSI_GO_TMP): GO_OUT := $(GO_OUT),Mgoogle/protobuf/wrappers.proto=$(PTYPES_PKG)/wrappers
-$(CSI_GO_TMP): GO_OUT := $(GO_OUT):"$(HERE)/$(CSI_BUILD)"
-$(CSI_GO_TMP): INCLUDE := -I$(GOPATH)/src -I$(HERE)/$(PROTOC_TMP_DIR)/include
-$(CSI_GO_TMP): $(CSI_PROTO) | $(PROTOC) $(PROTOC_GEN_GO)
-	@mkdir -p "$(@D)"
-	(cd "$(GOPATH)/src" && \
-		$(HERE)/$(PROTOC) $(INCLUDE) --go_out=$(GO_OUT) "$(CSI_PKG_ROOT)/$(<F)")
-
-# The temp language bindings are compared to the ones that are
-# versioned. If they are different then it means the language
-# bindings were not updated prior to being committed.
-$(CSI_GO): $(CSI_GO_TMP)
-ifeq (true,$(TRAVIS))
-	diff "$@" "$?"
-else
-	@mkdir -p "$(@D)"
-	diff "$@" "$?" > /dev/null 2>&1 || cp -f "$?" "$@"
-endif
-
-# This recipe builds the Go archive from the sources in three steps:
-#
-#   1. Go get any missing dependencies.
-#   2. Cache the packages.
-#   3. Build the archive file.
-$(CSI_A): $(CSI_GO)
-	go get -v -d ./...
-	go install ./$(CSI_PKG_SUB)
-	go build -o "$@" ./$(CSI_PKG_SUB)
-
-build: $(CSI_A)
-
-clean:
-	go clean -i ./...
-	rm -rf "$(CSI_A)" "$(CSI_GO)" "$(CSI_BUILD)"
-
-clobber: clean
-	rm -fr "$(PROTOC)" "$(PROTOC_GEN_GO)" "$(CSI_PKG_SUB)"
-
-.PHONY: clean clobber

vendor/github.com/container-storage-interface/spec/lib/go/README.md

@@ -1,21 +0,0 @@
-# CSI Go Validation
-
-This package is used to validate the CSI specification with Go language bindings.
-
-## Build Reference
-
-To validate the Go language bindings against the current specification use the following command:
-
-```bash
-$ make
-```
-
-The above command will download the `protoc` and `protoc-gen-go` binaries if they are not present and then proceed to build the CSI Go language bindings.
-
-### Environment Variables
-
-The following table lists the environment variables that can be used to influence the behavior of the Makefile:
-
-| Name | Default Value | Description |
-|------|---------------|-------------|
-| `PROTOC_VER` | `3.3.0` | The version of the protoc binary. |

vendor/github.com/container-storage-interface/spec/lib/go/csi.go

@@ -1,5 +0,0 @@
-// Package csi is the Container Storage Interface (CSI) specification
-// repository. This package contains no functional code, and this file
-// exists only to make it possible to import this repository with a Go
-// dependency manager such as Dep (https://github.com/golang/dep).
-package csi