From: "Stephen Perkins" <perkins@netmass.com>
To: ceph-devel@vger.kernel.org
Subject: ESXi and ideal hardware spec
Date: Mon, 27 Aug 2012 13:17:12 -0500 [thread overview]
Message-ID: <00b501cd8480$2dc46b60$894d4220$@netmass.com> (raw)
Hi all,
As part of the ideal hardware spec thread that has been going around, I
wanted to ask comments on virtualizing the OS. Since my deployment would
eventually be co-located at a remote "lights out" environment, I require
that I have support for:
out of band remote access on dedicated port
- Dell DRAC
- HP iLO
- SuperMicro IPMI with KVM
- ASUS with Remote Management Chip
- VMWare on the actual virtual machine instances.
Remote monitoring of physical hardware
- Dell OpenManage
- HP Insight Manager
- SuperMicro SuperDoctor III
- VMWare
Integration with a Service Monitor solution
- Nagios
- Zabbix
- VMWare
One thing that integrates well with all of these is the free VMWare ESXi
Hypervisor.
Are there any thoughts on placing all Ceph nodes as single virtual machines
running on top of an ESXi hypervisor? What I mean by this is that each
brick runs ESXi and then only runs one virtual machine.
Are there any advantages of running the MON and MDS servers as independent
virtual machines on the same physical brick as an OSD virtual machine
(rather than just running the processes)? Multi-port Ethernet systems can
segregate traffic between the instances...
- Steve
next reply other threads:[~2012-08-27 18:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-27 18:17 Stephen Perkins [this message]
2012-08-27 20:23 ` ESXi and ideal hardware spec Josh Durgin
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='00b501cd8480$2dc46b60$894d4220$@netmass.com' \
--to=perkins@netmass.com \
--cc=ceph-devel@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.