All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Marcin M. Jessa" <lists@yazzy.org>
To: kvm@vger.kernel.org
Subject: KVM, iSCSI and High Availability
Date: Fri, 25 Mar 2011 21:26:56 +0100	[thread overview]
Message-ID: <4D8CFA90.20605@yazzy.org> (raw)

Hi.

Over the last several days I've been reading, asking questions, 
searching the Internet to find a viable HA stack for Ubuntu with KVM 
virtualization and shared iSCSI storage. And I'm nearly as confused as 
when I started.

Basically I'm trying to build a KVM enviroment with an iSCSI SAN and I'm 
not quite sure what approach to use for storing the virtual guests.
What I understand to get max speed I should install directly to iSCSI 
exported raw devices instead of backing disks.
I'm not sure creating many small LUNs, one for each of the guests is a 
good idea.
Would it be better to create just one big LUN and then use LVM to devide 
it and assign one "chunk" for each of the guests?
In the same setup I would also like to implement some kind of automatic 
failover so if one of the KVM hosts is down I could automatically move 
guests over to the other one. Or just perform live migration and move 
one of the guest over to a different host with spare capacity.
What would be the best approach to implement a solution like that?

Thanks in advance.


-- 

Marcin M. Jessa

             reply	other threads:[~2011-03-25 20:26 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-25 20:26 Marcin M. Jessa [this message]
2011-03-28 12:46 ` KVM, iSCSI and High Availability Avi Kivity
2011-03-28 20:22   ` Marcin M. Jessa
2011-03-28 20:35     ` David Martin
2011-03-31 14:06       ` Guido Winkelmann
2011-03-31 15:19         ` David Martin
2011-03-31 16:41           ` Guido Winkelmann
     [not found] <130305978.11419.1301329182740.JavaMail.root@mail1.martinsales.net>
2011-03-28 16:21 ` David Martin
2011-03-28 20:31   ` Marcin M. Jessa
2011-03-29  1:41     ` Javier Guerra Giraldez

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4D8CFA90.20605@yazzy.org \
    --to=lists@yazzy.org \
    --cc=kvm@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.