Skip to content
This repository has been archived by the owner on May 6, 2020. It is now read-only.

Add configuration for hypervisor block storage driver #1037

Merged
merged 3 commits into from
Mar 2, 2018

Conversation

amshinde
Copy link
Contributor

No description provided.

This pulls in SCSI support for block devices.

Virtcontainers Shortlog:

07c2c88 test: Modify block device test to test for SCSI as well
a1a569a scsi: Add SCSI support for volumes as well
3c038f1 scsi: Pass SCSI address to hyperstart agent
80bdc50 tests: Fix tests to take into account default driver for block
devices
7df3f45 scsi: Add support for scsi driver for hotplugging drives
10e2349 1.0.7 release
10d462c block: Fix disabling block device use
fd6f6ed pod: Factorize network creation and removal into pod functions
2fec63f pod: StartVM() does not need any parameter
0dd84be container: Remove the container from pod structure on deletion
b852d93 api: Stop the VM when stopping the pod
17065de pod: Simplify pod stop
bcb8643 pod: Delete containers when deleting the pod

Signed-off-by: Archana Shinde <archana.m.shinde@intel.com>
@sboeuf
Copy link
Contributor

sboeuf commented Feb 27, 2018

LGTM

@clearcontainersbot
Copy link

kubernetes qa-failed 👎

# Block storage driver to be used for the hypervisor in case the container
# rootfs is backed by a block device. This is either virtio-scsi or
# virtio-blk.
block_driver_driver = @DEFBLOCKSTORAGEDRIVER@
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This needs to be double-quoted, as currently:

$ ./cc-runtime cc-env                                                                                                                                                   
Near line 70 (last key parsed 'hypervisor.qemu.block_driver_driver'): expected value but found "virtio" instead

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Oops! Fixed it.

@@ -68,6 +68,7 @@ func makeRuntimeConfig(prefixDir string) (configFile string, config oci.RuntimeC
shimPath := filepath.Join(prefixDir, "cc-shim")
proxyPath := filepath.Join(prefixDir, "cc-proxy")
disableBlock := true
blockStorageDriver := "virtio-scsi"
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Seeing this change makes me wonder if we should be displaying it in the [Hypervisor] section of the cc-runtime cc-env output?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Makes sense to show this in the cc-env output. I have included this in the PR now.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks! Could you bump formatVersion to 1.0.9 as this is a cc-env format change.

config.go Outdated
return defaultBlockDeviceDriver
}

return h.BlockDeviceDriver
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You should validate the block device virtio-scsi or virtio-blk

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Done

Block devices can be passed using either virio-scsi or
virtio-block.

Fixes clearcontainers#1036

Signed-off-by: Archana Shinde <archana.m.shinde@intel.com>
@clearcontainersbot
Copy link

kubernetes qa-failed 👎

@amshinde
Copy link
Contributor Author

@chavafg I see kubernetes failing here. Is this a valid faliure? Can you post the logs?

@devimc
Copy link

devimc commented Feb 28, 2018

check-go-static failed

 package honnef.co/go/tools/cmd/unused: unrecognized import path "honnef.co/go/tools/cmd/unused" (parse https://honnef.co/go/tools/cmd/unused?go-get=1: no go-import meta tags 

@chavafg
Copy link
Contributor

chavafg commented Feb 28, 2018

@amshinde k8s failure was a network timeout, so not valid. BTW, we just switch to run k8s validation through the jenkins jobs, so no more qa-fails from clearcontainersbot

Add the hypervisor block device driver being used in the
Hypervisor section of cc-env output.

Signed-off-by: Archana Shinde <archana.m.shinde@intel.com>
@amshinde
Copy link
Contributor Author

amshinde commented Mar 2, 2018

@jodh-intel Can you approve and merge this PR if this looks good to you.

@jodh-intel
Copy link
Contributor

Thanks @amshinde.

lgtm.

@jodh-intel jodh-intel merged commit b1f8bdc into clearcontainers:master Mar 2, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

6 participants