Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://github.com/vmware/docker-volume-vsphere/issues/442 below:

Support importing a disk into a volume repository on an ESX host · Issue #442 · vmware-archive/vsphere-storage-for-docker · GitHub

To allow existing users migrate their data (vmdks) to be managed by the docker-volume-vsphere plugin we need a way by which users can specify a single or multiple volumes to be "imported" into the volume repository managed by the plugin and hence docker.

This is assuming that docker will not accept volumes that are simply placed into the volume repo on the ESX host side unless the volume is explicitly created via docker.

So,

1. Support a "docker volume create -o "importvol=...." " option specifying the location (on the host) from where an existing volume must be imported into the docker volume repo on the host.
2. Create fails if the volume doesn't exist.
3. If the volume exists at the specified path at the host, then move the volume to the repo and init meta-data for it.
4. Done.

Point to consider is whether the volume must be migrated to the volume-repo of the plugin or it remains where it is (say 1TB volume) but we create a vmdk descriptor in the volume-repo and the meta-data for it while the actual volume stays elsewhere (for vsan and vvol thats the case anyway).

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4