<html><head><style type='text/css'>p { margin: 0; }</style></head><body><div style='font-family: times new roman,new york,times,serif; font-size: 12pt; color: #000000'><hr id="zwchr"><blockquote style="border-left:2px solid rgb(16, 16, 255);margin-left:5px;padding-left:5px;color:#000;font-weight:normal;font-style:normal;text-decoration:none;font-family:Helvetica,Arial,sans-serif;font-size:12pt;"><b>From: </b>"Jonathan Horne" <jhorne@skopos.us><br><b>To: </b>users@ovirt.org<br><b>Sent: </b>Wednesday, November 21, 2012 6:01:46 PM<br><b>Subject: </b>[Users] help me validate my design<br><br>
<div>
<div>
<div>I like to give a brief description of what I'm taking to production here in a couple weeks, and I like some opinions if this is a valid design, as well as id love to hear some anecdotal evidence of similar deployments as well.</div>
</div>
</div>
<div><br>
</div>
<div>My nodes will be 8 dell M620s with 96GB ram and dual 10core intel processors. As they are in M1000 chassis, I will be using fabric A for ovirtmgmt network and the fabA interfaces will be a bond mode1. Fabric A is a pair of cisco 3130s, and the stacking
cables were not used by previous admin and are long lost (thus, the mode1 for ovirtmgmt). The fabric B will be dual port broadcom mezzanine cards into powerconnect 6348s that will be stacked. My fabB will be used for iscsi traffic that will be on a equalogic
iscsi SAN, and node interfaces will be a mode4.</div>
<div><br>
</div>
<div>Regular network traffic for both nodes and Vm's will go thru ovirtmgmt, and iscsi traffic will be isolated on the dedicated 6348 switches. Some Vms will have interfaces for iscsi, as they will have their own dedicated luns on the EQ SAN for their own
data.</div>
<div><br>
</div>
<div>Am in on a valid track here?</div>
<div><br>
</div>
<div>Thanks for your opinions,</div>
<div>jonathan</div>
<br>
<hr>
<font color="Gray" face="Arial" size="1">This is a PRIVATE message. If you are not the intended recipient, please delete without copying and kindly advise us by e-mail of the mistake in delivery. NOTE: Regardless of content, this e-mail shall not operate to
bind SKOPOS to any order or other contract unless pursuant to explicit written agreement or government initiative expressly permitting the use of e-mail for such purpose.</font>
<br>_______________________________________________<br></blockquote>Hi Jomathan,<br>I think it'll be easier to relate to specific performance areas, which usually come up later in the process.<br><br>Try organizing your setup based on the following areas;<br><br>1. Network design<br>- What connect where, which networks will you have?<br>- Capacity planning<br>- Special considerations (VLANs, etc).<br><br>2. Storage design<br>- What connect where, and how: iscsi, nfs, FC, etc.<br>
- Capacity planning<br><br>
3. Management server<br>- Fedora?<br>- CPU<br>- RAM<br>- Networking<br>- Will it include other Apps?<br><br>4. Hosts<br>- Fedora or ovirt-nodes?<br>- CPU<br>
- RAM<br>
- Networking<br>
- Capacity plan<br>- Fencing?<br><br>Based on the above it'll be easier to see if we can expect issues.<br><br></div></body></html>