513cebe7b7
* Add Virtual Kubelet provider for VIC Initial virtual kubelet provider for VMware VIC. This provider currently handles creating and starting of a pod VM via the VIC portlayer and persona server. Image store handling via the VIC persona server. This provider currently requires the feature/wolfpack branch of VIC. * Added pod stop and delete. Also added node capacity. Added the ability to stop and delete pod VMs via VIC. Also retrieve node capacity information from the VCH. * Cleanup and readme file Some file clean up and added a Readme.md markdown file for the VIC provider. * Cleaned up errors, added function comments, moved operation code 1. Cleaned up error handling. Set standard for creating errors. 2. Added method prototype comments for all interface functions. 3. Moved PodCreator, PodStarter, PodStopper, and PodDeleter to a new folder. * Add mocking code and unit tests for podcache, podcreator, and podstarter Used the unit test framework used in VIC to handle assertions in the provider's unit test. Mocking code generated using OSS project mockery, which is compatible with the testify assertion framework. * Vendored packages for the VIC provider Requires feature/wolfpack branch of VIC and a few specific commit sha of projects used within VIC. * Implementation of POD Stopper and Deleter unit tests (#4) * Updated files for initial PR
33 lines
1.3 KiB
Go
33 lines
1.3 KiB
Go
/*
|
|
Copyright (c) 2014 VMware, Inc. All Rights Reserved.
|
|
|
|
Licensed under the Apache License, Version 2.0 (the "License");
|
|
you may not use this file except in compliance with the License.
|
|
You may obtain a copy of the License at
|
|
|
|
http://www.apache.org/licenses/LICENSE-2.0
|
|
|
|
Unless required by applicable law or agreed to in writing, software
|
|
distributed under the License is distributed on an "AS IS" BASIS,
|
|
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
|
|
See the License for the specific language governing permissions and
|
|
limitations under the License.
|
|
*/
|
|
|
|
package progress
|
|
|
|
/*
|
|
The progress package contains functionality to deal with progress reporting.
|
|
The functionality is built to serve progress reporting for infrastructure
|
|
operations when talking the vSphere API, but is generic enough to be used
|
|
elsewhere.
|
|
|
|
At the core of this progress reporting API lies the Sinker interface. This
|
|
interface is implemented by any object that can act as a sink for progress
|
|
reports. Callers of the Sink() function receives a send-only channel for
|
|
progress reports. They are responsible for closing the channel when done.
|
|
This semantic makes it easy to keep track of multiple progress report channels;
|
|
they are only created when Sink() is called and assumed closed when any
|
|
function that receives a Sinker parameter returns.
|
|
*/
|