xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: "Chris Vella" <chris@dload.com.au>
To: xen-devel@lists.xen.org
Subject: xen setup/config
Date: Wed, 22 May 2013 12:31:57 +1000	[thread overview]
Message-ID: <00d801ce5694$87b52fb0$971f8f10$@com.au> (raw)

A little help please guys or a pointer in the right direction for a
configuration/setup recommendation. 

Whilst I have been using the XEN hypervisor in our office/dev environments
for some time, I am preparing to deploy the latest XCP/Xen build for our
live/collocation installation. 

To date I haven't used any virtualisation at all in our live environment.
Our setup is relatively straightforward with a physical three tier model: 

. Presentation tier (web servers, smtp, etc.)
. Logic tier (business and operational servers)
. Data tier (database and storage)

I am going to leave the Data tier non virtualised and virtualise (compress)
the logic and presentation tier onto the same physical hardware. 

So the example scenario is:

. Both the Presentation and Logic tiers currently have 6 physical servers
each (12 total) in a load balanced (shared nothing) arrangement. These will
be replaced with 3-4 physical servers running at least two VM's on each.
. How would you set up the XEN environment for dynamic workload structures? 
. If spikes come through via the presentation tier how do you prioritise
CPU/bandwidth to these servers/VM's?
. Likewise if the presentation tier is acquiescent then how do you control
it such that if the logic tier gets busy it can consume idle CPU/bandwidth?


Regards,

Chris

             reply	other threads:[~2013-05-22  2:31 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-22  2:31 Chris Vella [this message]
2013-05-22  9:53 ` xen setup/config Ian Campbell
2013-05-22 10:00   ` Chris Vella

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='00d801ce5694$87b52fb0$971f8f10$@com.au' \
    --to=chris@dload.com.au \
    --cc=xen-devel@lists.xen.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).