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
51 lines
2.3 KiB
Go
51 lines
2.3 KiB
Go
/*
|
|
Copyright (c) 2015 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 pool
|
|
|
|
var poolNameHelp = `
|
|
POOL may be an absolute or relative path to a resource pool or a (clustered)
|
|
compute host. If it resolves to a compute host, the associated root resource
|
|
pool is returned. If a relative path is specified, it is resolved with respect
|
|
to the current datacenter's "host" folder (i.e. /ha-datacenter/host).
|
|
|
|
Paths to nested resource pools must traverse through the root resource pool of
|
|
the selected compute host, i.e. "compute-host/Resources/nested-pool".
|
|
|
|
The same globbing rules that apply to the "ls" command apply here. For example,
|
|
POOL may be specified as "*/Resources/*" to expand to all resource pools that
|
|
are nested one level under the root resource pool, on all (clustered) compute
|
|
hosts in the current datacenter.`
|
|
|
|
var poolCreateHelp = `
|
|
POOL may be an absolute or relative path to a resource pool. The parent of the
|
|
specified POOL must be an existing resource pool. If a relative path is
|
|
specified, it is resolved with respect to the current datacenter's "host"
|
|
folder (i.e. /ha-datacenter/host). The basename of the specified POOL is used
|
|
as the name for the new resource pool.
|
|
|
|
The same globbing rules that apply to the "ls" command apply here. For example,
|
|
the path to the parent resource pool in POOL may be specified as "*/Resources"
|
|
to expand to the root resource pools on all (clustered) compute hosts in the
|
|
current datacenter.
|
|
|
|
For example:
|
|
*/Resources/test Create resource pool "test" on all (clustered)
|
|
compute hosts in the current datacenter.
|
|
somehost/Resources/*/nested Create resource pool "nested" in every
|
|
resource pool that is a direct descendant of
|
|
the root resource pool on "somehost".`
|