Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Issues about iSCSI storage pool #459

Open
YuXinHuo opened this issue Sep 19, 2014 · 2 comments
Open

Issues about iSCSI storage pool #459

YuXinHuo opened this issue Sep 19, 2014 · 2 comments
Milestone

Comments

@YuXinHuo
Copy link
Contributor

  1. I can create 2 templates with the same volume of iSCSI storage pool.
  2. I can create 2 guests with the same template configured against a volume of iSCSI storage pool.

I think both the design and implementation have problems

  1. For template, as it need to be used to create multiple guests, resources there must be collection like network/storage pool, should not be a volume.
  2. As volume need to support both read/write, we need to avoid 2 guests use the same volume as boot disk.

Recommended design:

  1. In template, when edit, only list storage pool, remove iscsi pool volumes there.
  2. When create guest, once user selected the template, if it is iscsi, add a section with a dropdown list for user to select volume, for volume already in use, filter them out.
@wenwang1989
Copy link
Contributor

Aggreed.

@alinefm
Copy link
Member

alinefm commented Sep 25, 2014

We can continue setting a iSCSI volume on templates but we need to make it shareable so multiple VMs can work with it without problems.

To share a disk, we just need to add the tag in the disk XML.

For reference: https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/5/html/Virtualization/sect-Virtualization-Shared_storage_and_virtualization-Using_iSCSI_for_storing_virtual_disk_images.html

@alinefm alinefm added this to the Backlog milestone Dec 3, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants