Mailing-List: contact cloudstack-users-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: cloudstack-users@incubator.apache.org
Received-SPF: pass (nike.apache.org: domain of fguerrero@ipaddress.com.ar
 designates 200.80.170.227 as permitted sender)
Message-ID: <5046541F.3070309@ipaddress.com.ar>
Date: Tue, 04 Sep 2012 16:18:55 -0300
From: Facundo Guerrero <fguerrero@ipaddress.com.ar>
User-Agent: Mozilla/5.0 (X11; Linux x86_64;
 rv:14.0) Gecko/20120713 Thunderbird/14.0
MIME-Version: 1.0
To: cloudstack-users@incubator.apache.org
Subject: Re: multiple NICs on same network
References: <CC6B9D5D.11542%alena.prokharchyk@citrix.com>
In-Reply-To: <CC6B9D5D.11542%alena.prokharchyk@citrix.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit

Thanks .

I had a server with 10 ipaddress i modify the router script to make the
nat to that IPs.

I would be a great feature to have the possibility to add "floating
Ip's" in the private network and nat 1:1 to a public IP.


El 04/09/12 15:59, Alena Prokharchyk escribi�:
> No, it's not possible. Although seems like you can assign 2 nics from the
> same network to the vm, the things start breaking when we create network
> rules (firewall/pf/lb) for vm in the network. As we always assume that vm
> can't have more than one nic in the network.
>
> -Alena.
>
> On 9/4/12 11:50 AM, "Facundo Guerrero" <fguerrero@ipaddress.com.ar> wrote:
>
>> It's possible to NAT 1:1 a public IP for each of this Privates IP's? To
>> do that at this moment i modify the script in the VP.
>>
>>
>> Thanks
>>
>> El 04/09/12 03:56, Prasanna Santhanam escribi�:
>>> On Wed, Aug 29, 2012 at 12:36:59PM -0400, Alena Prokharchyk wrote:
>>>> On 8/29/12 3:13 AM, "Sumita Gorla" <Sumita.Gorla@citrix.com> wrote:
>>>>
>>>>> Can we use Cloudstack APIs to create a VM with two NICs on the same
>>>>> shared network
>>>>> Or isolated network?
>>>>>
>>>> No, one nic per user vm network.
>>> The API can be used to create a VM with multiple nics in the same
>>> network. The logic to prevent this in the UI only. You just have to
>>> specify the same NetworkId as a comma-seperated list. so the following
>>> works atm:
>>>
>>> deployVirtualMachine
>>> 	&templateId=ttt
>>> 	&serviceOfferingId=sss
>>> 	&networkId=nn,nn
>>>
>>>
>>> Most likely the default gateway gets clobbered and only one NIC is in
>>> use at all times. The other being passive.
>>>
>>> Just Curious, What would be a use-case for such a requirement though?
>>>
>>> Thanks,
>>>
>>>
>>
>