发起问题

EvanFoster 的档案 - activity

2019-05-13 08:32:01 -0500 获得奖牌  热门的问题 (source)
2019-05-13 08:32:01 -0500 获得奖牌  著名问题 (source)
2018-11-10 04:13:37 -0500 获得奖牌  受欢迎的问题 (source)
2018-11-06 21:19:20 -0500 评论问题 How to always create root disks as volumes on cinder?

If docker-machine allowed me to create volumes then this would be possible, but you can't specify volume creation using an image and flavor alone. You have to create a volume from an image using disk size from the flavor and then run that instance from that volume.

2018-11-06 21:19:20 -0500 评论问题 How to always create root disks as volumes on cinder?

Hey Bernd,

I'm using Rancher to manage k8s. Rancher uses docker-machine on the back end to create VMs on OpenStack. docker-volume doesn't allow you to specify anything other than an image and a flavor.

What I want isn't possible, so I'm going to use Ceph for my root disks and Cinder otherwise.

2018-11-06 16:27:20 -0500 问了问题 How to always create root disks as volumes on cinder?

Hey folks!

I've got an interesting problem here. I've been beating my head against this for a few weeks and haven't been able to find anything concrete.

I'm using Kubernetes and trying to integrate it with Openstack so I can get automatic VM provisioning. The cloud driver for Kubernetes takes the following information:

  • Flavor
  • Image
  • Network
  • Floating IP pool

And a few other things that aren't that important. Here's where my issue is.

My compute nodes have basically no disks. I have a large, very fast SAN and I want all block storage on that SAN. When you create a flavor or image, you can specify a root disk size, but this root disk is created locally on the compute node. This means that I have around 20 GB for all VMs running on any given compute node.

So, is there any way that I can force all root disks to be created as Cinder volumes? I can do this manually, but I need it to automatically happen all the time.

The process I want was described to me like this on IRC:

[11:33] <larsks> So what you really want is for openstack, when booting an instance, is to (a) create a volume for you and (b) copy over the data from the boot image and then (c) boot the instance from that volume?

I'm running Openstack Ocata. My Cinder node is using LVM as its backend.