This actually makes a lot of sense to me. I think I can handle the two nic
configuration, because using one I have to deploy some IP and ethernet
tricks I am not too familiar with. The two nic solution works for me.
On Mon, Jun 6, 2011 at 9:59 AM, Josh Thompson <josh_thomp...@ncsu.edu>wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> VCL was created from the beginning with the assumption that there would be
> NICs in each machine. One to be used for pushing images to compute nodes
> for managing the compute nodes. The other for allowing public access to
> compute nodes from the end user. The management node doesn't absolutely
> to have a public IP address, but it makes administration of it much easier
> it does have one.
> We do hope to get away from requiring the two NICs in the not too distant
> I hope that helps clear things up. I can clarify further if needed.
> On Friday June 03, 2011, Cameron Seay wrote:
> > Hi All!
> > I am creating a VM host on a convention (non-blade) server. Josh
> > a while back that using two nics would be beneficial in this scenario.
> > that because one nic is for the external network and one is for the
> > internal network?
> > Thanks.
> > Cameron
> - --
> - -------------------------------
> Josh Thompson
> VCL Developer
> North Carolina State University
> my GPG/PGP key can be found at pgp.mit.edu
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v2.0.17 (GNU/Linux)
> -----END PGP SIGNATURE-----
Cameron Seay, Ph.D.
Electronics, Computer and Information Technology
School of Technology
NC A & T State University
336 334 7717 x2251