[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: [Xen-users] XCP resource pool
- To: "xen-users@xxxxxxxxxxxxxxxxxxx" <xen-users@xxxxxxxxxxxxxxxxxxx>, Rob Hoes <Rob.Hoes@xxxxxxxxxx>
- From: inas mohamed <inas_2003@xxxxxxxxx>
- Date: Tue, 4 Jan 2011 21:43:59 -0800 (PST)
- Cc:
- Delivery-date: Tue, 04 Jan 2011 21:45:21 -0800
- Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:X-YMail-OSG:Received:X-Mailer:Date:From:Subject:To:In-Reply-To:MIME-Version:Content-Type; b=HXM+10ADEO3ESiSy8uHyRxgmkP+KlPaATFNLlG0Eyp0MnFYCE8+qEt3XEHidRz2SQdXPcelN49X2CoFWo+LA6YnyCuq9okH/kZ0yRHtV7qSQXZfeUkLHFfS2x3iRQXaOdneuiRQ2mTirOmEBWENuf2sDbOs87He8+mANpTNoUvg=;
- List-id: Xen user discussion <xen-users.lists.xensource.com>
Thanks to you Rob & admin for your very good explanation. Now every thing is clear. Thanks so much.
Inas --- On Tue, 1/4/11, Rob Hoes <Rob.Hoes@xxxxxxxxxx> wrote: From: Rob Hoes
<Rob.Hoes@xxxxxxxxxx> Subject: RE: [Xen-users] XCP resource pool To: "'inas mohamed'" <inas_2003@xxxxxxxxx>, "xen-users@xxxxxxxxxxxxxxxxxxx" <xen-users@xxxxxxxxxxxxxxxxxxx> Date: Tuesday, January 4, 2011, 3:21 PM
Hi Inas, A PIF represents a physical NIC inside a host, while a âNetworkâ is a pool-wide thing. XCP automatically creates PIFs for all physical NICs, and creates one Network for all of those with the same device name across all hosts in the pool (e.g. all eth0 PIFs are on the same network). Suppose you have a VM running on host A, which has a VIF on the Network associated with the eth0 PIFs. All communication between this VM and nodes outside host A will then go through the eth0 interface on host A. The nice thing about this is that if you migrate your VM from host A to host B, the VM will automatically use Bâs eth0 interface without any need to change the configuration. Hope that helps. Rob From: xen-users-bounces@xxxxxxxxxxxxxxxxxxx [mailto:xen-users-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of inas mohamed Sent: 04 January 2011 05:46 To: xen-users@xxxxxxxxxxxxxxxxxxx; admin@xxxxxxxxxxx Subject: RE: [Xen-users] XCP resource pool Thanks soo much, but as I said before I am very new and by the time I am finding that my question is tooo .......:( I read many forums and guides on XCP and VMs and I found that many VDIs can be created on the same storage repository for our VMs. But regarding vifs, now as a said before I installed XCP on 5 servers and created a resource pool and all my servers joined that pool and when I try: # xe
network-list bridge=xenbr0 params=uuid --minimal I am getting one network uuid but if I said: I got 5 NICs all are eth0, each have a different uuid but all have the same network uuid So, I am asking why when we are creating a vif we are using the network uuid not the pif uuid to say the traffic of this VM has to go through this
NIC?? may be it is another .... question.but it is my question :) --- On Mon, 1/3/11, admin@xxxxxxxxxxx <admin@xxxxxxxxxxx> wrote:
From: admin@xxxxxxxxxxx <admin@xxxxxxxxxxx> Subject: RE: [Xen-users] XCP resource
pool To: xen-users@xxxxxxxxxxxxxxxxxxx Date: Monday, January 3, 2011, 9:58 PM
No, you can create on SR and store all of your VMs on that SR. For example, if you use an NFS target for your VHD files, all of your VMs could share that SR. You donât need to assign a separate PIF for each VM. In fact, most people wonât. You will assign a
separate VIF for each VM and then XCP can route the VIFs through a shared PIF. -----Original Message----- From: xen-users-bounces@xxxxxxxxxxxxxxxxxxx [mailto:xen-users-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of inas mohamed Sent: Monday, January 03, 2011 12:55 AM To: xen-users@xxxxxxxxxxxxxxxxxxx Subject: [Xen-users] XCP resource pool Hi, I am very new to XCP , and I have couple of questions to make things clear. After creating a resource pool: Do I have to create a SR for each VM, if I needed to assign 100GB HDD for this VM?? Do I have to assign a pif for each VM to distribute the traffic over my hosts NICs or the master will handle this?? Thanks so much for any help |
-----Inline Attachment Follows-----
|
-----Inline Attachment Follows-----
|
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
|