We need to consider removing the 'kubevirt" prefix from all cdi labels. The reason being that we want to eventually decouple cdi from kubevirt.

If user delete the import-pod accidentally when it's creating, there should be a new pod being created.
I think currently our controller doesn't have this mechanism, should we add it ?

The advice in the primary README.md to bind the default service account for a namespace with cluster-admin privileges isn't wise. Even with the disclaimer, we don't want that accidentally replicated.

For example, I already see that kubevirt-ansible is using this method to deploy CDI right now. I'd hate for something like this to accidentally make it's way into production someday.

short term fix

As a short term method, we'd be better off giving the CDI deployment a service-account with cluster-admin roles rather than binding cluster-admin to the default account in a namespace.

I'd recommend making this change asap before CDI gains any more traction.

long term fix

add a ServiceAccount, RBAC ClusterRole, and ClusterRoleBinding into a manifest and make the cdi-controller-deployment.yaml reference the service account.

The kubevirt manifest has some examples of how we do this for our controllers.
https://github.com/kubevirt/kubevirt/blob/master/manifests/release/kubevirt.yaml.in

Probably add this to cmd/controller/controller.go

It would be nice if we have some basic unit test.

1. why we do the decompress before download image stream here: https://github.com/shiywang/containerized-data-importer/blob/123b7ac620174f378e980ef258c0726325a3bb4c/cmd/importer/importer.go#L36

is there acutally gonna be file can be opened https://github.com/shiywang/containerized-data-importer/blob/bba7838081ef8061b6bfb5f3904113f613446958/pkg/image/decompress.go#L26 ? or my understanding is wrong ?

Thanks

make test should work

We should add a label to the pvc object if a user has not added it, it's not a requirement for processing but a nice UXP to give ability to easily filter on CDI type resources using kubectl .i.e.

   kubectl get pvc -l app=containerized-data-importer --all-namespaces

We are likely exposed to vulnerabilities by allowing users to import any image into the kubernetes cluster.

Expand unit test coverage of this package.

• util_test.go
• dataStream_test.go

The packages mixes use of fmt and glog. fmt isn't useful here; we should use glog exclusively.

Eg: .qcow2.tar and .qcow2.gz and .qcow2.tar.gz, and include .xz.

Expand unit test coverage of this package.

• qemu_test.go
• validate_test.go

It's high time that releases of CDI be versioned in a format that conforms with Openshift and Kubevirt (v#.#.#). A versioning needs to be agreed upon to mark major, minor, and patch milestones. Some automation should be implemented for incrementing each to avoid human error.

make fails with a perms error on a rhel 7.4 vm:
Eg: make controller

stat /go/src/github.com/kubevirt/containerized-data-importer/cmd/controller/controller.go: permission denied

Also, shelling into the golang container shows the perms issue:

: docker run -it --rm -w /go/src/github.com/kubevirt/containerized-data-importer -v $PWD:/go/src/github.com/kubevirt/containerized-data-importer 3f30f1fc3c43 sh
# pwd
/go/src/github.com/kubevirt/containerized-data-importer
# ls -l
ls: cannot open directory '.': Permission denied
# id
uid=0(root) gid=0(root) groups=0(root)
# mount|grep import
/dev/mapper/rhel-root on /go/src/github.com/kubevirt/containerized-data-importer type xfs (rw,relatime,seclabel,attr2,inode64,noquota)

Running the golang container privileged or setenforce 0 fixes the perms problem.

Subset of #131

Expand unit test coverage of this package

It would be convenient to use CDI for tarball uploads i.e.

tar c . | curl …

1. If importer pod fails to create - don't want to forget the key in processItem
   - to ensure we try to process again

2. importer race condition - multiple imports on a single pvc

$ kubectl logs importer-golden-pvcmzqld
I0425 17:36:37.917054       5 importer.go:35] main: Starting importer
I0425 17:36:37.919191       5 importer.go:50] main: importing file "tinyCore.qcow2.gz"
W0425 17:36:37.919256       5 dataStream.go:42] NewDataStream: IMPORTER_ACCESS_KEY_ID and/or IMPORTER_SECRET_KEY env variables are empty
I0425 17:36:37.919470       5 dataStream.go:71] Using S3 client to get data
I0425 17:36:37.919657       5 dataStream.go:78] Attempting to get object "s3://kubevirt-images/tinyCore.qcow2.gz" via S3 client
I0425 17:36:37.919850       5 importer.go:58] Beginning import from "/tinyCore.qcow2.gz"
I0425 17:36:37.919871       5 decompress.go:26] UnpackData: checking compressed and/or archive for file "tinyCore.qcow2.gz"
I0425 17:36:37.919875       5 decompress.go:45] DecompressData: checking if "tinyCore.qcow2.gz" is compressed
I0425 17:36:38.268947       5 decompress.go:59] DecompressData: decompressed "tinyCore.qcow2.gz"
I0425 17:36:38.268995       5 decompress.go:70] DearchiveData: checking if "tinyCore.qcow2" is an archive file
I0425 17:36:38.269281       5 util.go:44] StreamDataToFile: begin import...
I0425 17:36:52.916024       5 importer.go:88] main: converting qcow2 image to raw
I0425 17:36:52.949694       5 importer.go:98] main: Import complete, exiting
jcope@jonMBP | ~/.../kubevirt/manifests
$ kubectl logs importer-golden-pvcs9ntq
I0425 17:36:39.276378       7 importer.go:35] main: Starting importer
I0425 17:36:39.276943       7 importer.go:50] main: importing file "tinyCore.qcow2.gz"
W0425 17:36:39.276975       7 dataStream.go:42] NewDataStream: IMPORTER_ACCESS_KEY_ID and/or IMPORTER_SECRET_KEY env variables are empty
I0425 17:36:39.277832       7 dataStream.go:71] Using S3 client to get data
I0425 17:36:39.277960       7 dataStream.go:78] Attempting to get object "s3://kubevirt-images/tinyCore.qcow2.gz" via S3 client
I0425 17:36:39.278006       7 importer.go:58] Beginning import from "/tinyCore.qcow2.gz"
I0425 17:36:39.278050       7 decompress.go:26] UnpackData: checking compressed and/or archive for file "tinyCore.qcow2.gz"
I0425 17:36:39.278063       7 decompress.go:45] DecompressData: checking if "tinyCore.qcow2.gz" is compressed
I0425 17:36:39.536339       7 decompress.go:59] DecompressData: decompressed "tinyCore.qcow2.gz"
I0425 17:36:39.536358       7 decompress.go:70] DearchiveData: checking if "tinyCore.qcow2" is an archive file
I0425 17:36:39.536531       7 util.go:44] StreamDataToFile: begin import...
I0425 17:36:41.136349       7 importer.go:88] main: converting qcow2 image to raw
I0425 17:36:41.166394       7 importer.go:98] main: Import complete, exiting

pr 82 adds support for multiple namespaces, meaning a pvc does not need to live in the "golden" ns.

Perhaps we can use this pkg: https://github.com/xi2/xz

The current controller unit tests are more like functional tests in that they call higher level functions (NewController, ProcessNextItem) rather than some of lower level funcs (which may need to be exported?).

1. We should consider moving the current unit tests to /test/ so they are treated as functional tests and create real controller unit tests.
2. We probably should remove the tests using an empty namespace since this is not a supported condition.

When I was working on CDI e2e test in kubevirt-ansible pr here: kubevirt/kubevirt-ansible#246, I found the docker images here latest haven't been updated for a month, the actually latest image is v0.5.0-alpha.0.

The reason why this bothering me is because the old image I use doesn't have any label tagged on importer-pod, so it's not convenient for you sift some result you want to check (unless use regex but I think using label is kind of best practice)

So my understanding of latest == the latest usable image we pushed == v0.5.0-alpha.0

Could someone help to update those images IIUC ? also related to pr here: kubevirt/kubevirt-ansible#243

https://hub.docker.com/r/kubevirt/cdi-controller/
https://hub.docker.com/r/kubevirt/cdi-importer/

UnpackData() takes a filename and attempts to mutate it dynamically as different decompression and unarchiving is performed such that the output would contain the appropriate extensions. However, this string var is not returned and cannot be used by the caller.

cc @jeffvance @screeley44

Today VM images are validated only by their filename extension. We could improve this by peeking inside the image and verifying headers, checksums (if any), etc to be more certain that we have a supported image type.
Something to consider is should we use the file's extension (suffix) at all? What if an image is named
foo.tar.gz but it is not a gzip file? Is this an error or do we ignore the extension?

Glide is being deprecated.

This is complicated by the fact that some of the intermediate Readers won't naturally call Close, eg. Tar.

This diagram should be updated to reflect importer pod monitoring.

rather than using controller for the client, we should pass the client to the func in an exported manner

Containerizing the build process removed the ability to do a non-containerized build. Can the ability to do a non-containerized build be put back into the makefile so that the option is available?

For better readability in kubectl output and logs. Otherwise, you see importer-test-pvcqzjcl and this is better importer-test-pvc-qzjcl

Consider:

1. create pvc but forget endpoint anno
2. controller sees pvc but calls q.forget()
3. user edits pvc and adds ep anno
4. controller never sees the pvc update.
   Therefore the user has to delete the pvc, edit it, then re-create it.

I'm working on a research on how to setup e2e test, there're two solutions here: 1. setting up a ci in this repo. 2. integrate e2e test in kubevirt/kubevirt, integrate in kubevirt/kubevirt has some pros but it will be no meaning if we didn't integrate the code base into kubevirt/kubevirt: no pr trigger tests. so I was just asking if there's a long term plan for doing that ?

@jeffvance @copejon @aglitke

add a functional test case for local file import.

fakeClient.Patch() is not implemented. No error is returned when Patch is called and the returned object is messed up. Our tests have been getting back false positives.
Update() has a likely rare window where the object's version is updated during the patch window. For now we will not worry about this.

CDI "releases" are arbitrary, do not represent any functional composition, and only serve to keep track of the latest kubevirt version string. There really is no CDI version, instead we have obscured "latest" with kubvirt's version tag.

Per a recent email from @davidvossel:
CDI's release are overwritten with every commit. This means that someone using the CDI v0.5.2 will get different code each time they they deploy depending on what happens upstream

I propose that we either:

1. make CDI releases real and immutable. This means CDI updates its release tag when we have collected a group of prs worthy of being released, and we support that release for some reasonable number of months. It also requires that kubevirt-ansible be able to consume a specific CDI release that may differ from the target kubevirt release tag. Or,
2. stop pretending that CDI has releases and use "latest".

Interested in everyone's thoughts on this. @copejon @screeley44 @erinboyd @davidvossel @aglitke

Test failure after the travis fix:

• Failure [0.037 seconds]
Streaming Data Conversion
/home/travis/gopath/src/github.com/kubevirt/containerized-data-importer/test/datastream/datastream_test.go:26
  when data is in a supported file format
  /home/travis/gopath/src/github.com/kubevirt/containerized-data-importer/test/datastream/datastream_test.go:28
    should convert .qcow2 [It]
    /home/travis/gopath/src/github.com/kubevirt/containerized-data-importer/test/datastream/datastream_test.go:79
    Test data filename doesn't match expected file name.
    Expected
        <string>: tinyCore.qcow2
    to equal
        <string>: tinyCore.iso.qcow2

The call to should be reversed so that it calls Forget() on the key only if processItem() does not return an error. Errors that occur in processing may be ephemeral and only require that the process be retried. As such, keys that error should be requeued.

this part shouldn't be hardcoded: https://github.com/shiywang/containerized-data-importer/blob/d06b6da42f69b4e581a210841cb1159f33b177a9/pkg/controller/util.go#L138

espically nelly suggest using an offical repo url

I suggest using json.Unmarshal parse from a fixed file.

@jeffvance @copejon wdyt ?

We should add an explanation to the README file on why Red Hat CDN access won't work with basic http auth.

Expand unit test coverage of this package

• util_test.go
• importer_controller_test.go
• data_volume_test.go (completed by @davidvossel )

Let's say I'm about to create a pvc but provided some wrong endpoint url,
then the pod created by cdi will error out, then I figure it out my url was wrong, I have to manually delete the pod, then delele pvc, then change pvc and create.

but ideally, I just want to oc edit pvc change to a valid url, then let the cdi do the rest of job.

Suggest using glog.V(n).Info and pass the verbose flag from the controller to the importer pod.

Here's an example:
https://travis-ci.org/kubevirt/containerized-data-importer/builds/365227336#L518

Setting environment variables from .travis.yml
$ export CHANGE_MINIKUBE_NONE_USER=true
$ export K8S_VER=1.9.0
$ export K6T_VER=0.3.0
$ export SRC="http://www.tinycorelinux.net/9.x/x86/release/Core-current.iso"
4.79s$ GIMME_OUTPUT="$(gimme 1.10 | tee -a $HOME/.bashrc)" && eval "$GIMME_OUTPUT"
go version go1.10 linux/amd64
$ export GOPATH=$HOME/gopath
$ export PATH=$HOME/gopath/bin:$PATH
$ mkdir -p $HOME/gopath/src/github.com/kubevirt/containerized-data-importer
$ rsync -az ${TRAVIS_BUILD_DIR}/ $HOME/gopath/src/github.com/kubevirt/containerized-data-importer/
$ export TRAVIS_BUILD_DIR=$HOME/gopath/src/github.com/kubevirt/containerized-data-importer
$ cd $HOME/gopath/src/github.com/kubevirt/containerized-data-importer
0.01s
$ gimme version
v1.3.0
$ go version
go version go1.10 linux/amd64
go.env
$ go env
GOARCH="amd64"
GOBIN=""
GOCACHE="/home/travis/.cache/go-build"
GOEXE=""
GOHOSTARCH="amd64"
GOHOSTOS="linux"
GOOS="linux"
GOPATH="/home/travis/gopath"
GORACE=""
GOROOT="/home/travis/.gimme/versions/go1.10.linux.amd64"
GOTMPDIR=""
GOTOOLDIR="/home/travis/.gimme/versions/go1.10.linux.amd64/pkg/tool/linux_amd64"
GCCGO="gccgo"
CC="gcc"
CXX="g++"
CGO_ENABLED="1"
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"
PKG_CONFIG="pkg-config"
GOGCCFLAGS="-fPIC -m64 -pthread -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build731311504=/tmp/go-build -gno-record-gcc-switches"
Using Go 1.5 Vendoring, not checking for Godeps
install
0.00s$ true
before_script.1
1.79s$ curl -Lo kubectl https://storage.googleapis.com/kubernetes-release/release/v$K8S_VER/bin/linux/amd64/kubectl && chmod +x kubectl && sudo mv kubectl /usr/local/bin/
before_script.2
0.49s$ curl -Lo minikube https://storage.googleapis.com/minikube/releases/latest/minikube-linux-amd64 && chmod +x minikube && sudo mv minikube /usr/local/bin/
41.27s$ sudo minikube start --vm-driver=none --kubernetes-version=v$K8S_VER
Starting local Kubernetes v1.9.0 cluster...
Starting VM...
Getting VM IP address...
Moving files into cluster...
Downloading kubeadm v1.9.0
Downloading kubelet v1.9.0
Finished Downloading kubelet v1.9.0
Finished Downloading kubeadm v1.9.0
E0411 17:20:38.620011    4114 start.go:234] Error updating cluster:  starting kubelet: running command: 
sudo systemctl daemon-reload &&
sudo systemctl enable kubelet &&
sudo systemctl start kubelet
: exit status 1

Pod monitoring updates the PVC with an annotation containing the Importer Pod's statue. This is currently uncovered by testing. A PR will be opened to address this.

Also include tests for the supported archive methods (only tar so far).

and update each pod's pvc with final import status (success/fail).
This will be used to decide when it's safe to clone a vm image.

trello: https://trello.com/c/gu2hXD6E/141-cdi-import-progress-annotations

Tasks for Initial PR: #189

• add new package dependencies
• define DataVolume API and add client/informer generators
• refactor cdi controller component in preparation for multiple controller loops
• introduce DataVolume Controller
• add DataVolume controller unit tests

Followup Doc Tasks

• add DataVolume documentation to CDI README

Followup Dev Tasks

• add filesystem source
• add DataVolume events
• add DataVolume functional tests
• add autogen tests to travis (verifies autogen code is up to date)
• Autogenerated openapiv3 crd validation
• validating webhook
• autogenerated swagger (similar to what we have for kubevirt)