2:59 a.m.
Hi,
Who can help me to explain the detail of device and resourcepool setting
for container?
How to set the other devices in a contain domain xml except memory?
Also, I'm not sure of LXC_DiskPool, should I have to create a pool
manually for testing?
Best,
Regards
Daisy (运国莲)
VSM Team, China Systems & Technology Labs (CSTL)
E-mail: yunguol(a)cn.ibm.com
TEL: (86)-21-60922144
Building 10, 399 Ke Yuan Rd, Pudong Shanghai, 201203
2:25 p.m.
GY> Who can help me to explain the detail of device and resourcepool
GY> setting for container? How to set the other devices in a contain
GY> domain xml except memory?
If you look at the LXC_DiskResourceAllocationSettingData class in the
ResourceAllocationSettingData.mof file, you'll see an additional field
called "MountPoint" which is the target within the container. The
"Address" field specifies the source as on the other platforms.
However, the source for a container is a path on the filesystem, not a
device or an image file.
GY> Also, I'm not sure of LXC_DiskPool, should I have to create a pool
GY> manually for testing?
This is a good point. The existing storage pool implementation
doesn't have a way of representing a directory of directories, AFAIK.
I'll have to think on this one for a bit. Tests for this should
probably be SKIPped for now.
--
Dan Smith
IBM Linux Technology Center
Open Hypervisor Team
email: danms(a)us.ibm.com
3:24 p.m.
Dan Smith wrote:
GY> Who can help me to explain the detail of device and
resourcepool
GY> setting for container? How to set the other devices in a contain
GY> domain xml except memory?
If you look at the LXC_DiskResourceAllocationSettingData class in the
ResourceAllocationSettingData.mof file, you'll see an additional field
called "MountPoint" which is the target within the container. The
"Address" field specifies the source as on the other platforms.
However, the source for a container is a path on the filesystem, not a
device or an image file.
This means we'll need to modify the LXC XML so that it creates a
filesystem device. We could do something like:
<filesystem type='mount'>
<source dir='/tmp/lxc_files'/>
<target dir='/tmp/'/>
</filesystem>
/tmp/lxc_files is a directory we'll need to create in order to define /
create a container. For testing purposes, we aren't concerned with
contents of /tmp/lxc_files. However, a customer would create such a
directory for storing config files / executables / etc that the
container would need to access during runtime.
We'll also need to do something similar for DefineSystem() case as well.
--
Kaitlin Rupert
IBM Linux Technology Center
kaitlin(a)linux.vnet.ibm.com
6049
days inactive
6049
days old
2 comments
3 participants
participants (3)
-
Dan Smith -
Guo Lian Yun -
Kaitlin Rupert