You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@cloudstack.apache.org by Erik Weber <te...@gmail.com> on 2016/01/06 23:52:27 UTC

Re: VPC virtual router NIC limit

A theoretical change could be to switch from VLAN assigned VIFs to using
the VLAN feature in Linux kernel. That would give interface names like
eth0.100 instead of eth0-6. Would need one NIC for each physical Network
though.

And I do not know if all hypervisors supports trunk ports.


Erik

Den mandag 28. desember 2015 skrev Davide Pala <da...@gesca.it>
følgende:

> Hi all.
> I've read about vpc and tiers, now i've a question. VPC's virtual router
> is a virtual machine and as the other vm it have some limit such as the max
> number of nic that an hypervisor can provide to vm (in xenserver this limit
> is set to 7) ...this mean that the vpc can have only 6 tier? there is a way
> to bypass this limit?
> thanks to all
>
> Davide Pala
> Infrastructure Specialist
> Gesca srl
>
> Via degli Olmetti, 18
> 00060 Formello (Roma)
> Office:  +39 06 9040661
> Fax:     +39 06 90406666
> E-mail: davide.pala@gesca.it <javascript:;><mailto:davide.pala@gesca.it
> <javascript:;>>
> Web:    www.gesca.it<http://www.gesca.it/>
>
> [Descrizione: Descrizione: Descrizione: Descrizione: Descrizione:
> Descrizione: logoGescaPER FIRMA]
>
>

Re: VPC virtual router NIC limit

Posted by Erik Weber <te...@gmail.com>.
On Thu, Jan 7, 2016 at 11:28 AM, Remi Bergsma <RB...@schubergphilis.com>
wrote:

> Hoi Erik,
>
> You then don’t need eth interfaces for each tier and create a virtual
> interface in the openvswitch bridge instead. This has virtually no limit.
>
>
I considered the eth0.100 as virtual as well, but truly virtual is fine :-)


> Openvswitch also brings features like vxlan connections between routers
> and such, so could be very interesting.
>
>
vxlan as isolation in general would be interesting too

+1, for 4.9 release? ;-)

-- 
Erik

Re: VPC virtual router NIC limit

Posted by Remi Bergsma <RB...@schubergphilis.com>.
Hoi Erik,

You then don’t need eth interfaces for each tier and create a virtual interface in the openvswitch bridge instead. This has virtually no limit.

Openvswitch also brings features like vxlan connections between routers and such, so could be very interesting.

Regards,
Remi






On 07/01/16 08:30, "Erik Weber" <te...@gmail.com> wrote:

>From a technical or code perspective?
>
>How would changing to openvswitch change anything in this scenario?
>
>-- 
>Erik
>
>On Thu, Jan 7, 2016 at 7:16 AM, Remi Bergsma <RB...@schubergphilis.com>
>wrote:
>
>> I don't think that would work. Instead, we could change to openvswitch as
>> that makes it way more flexibele. As far as I know there are no plans / is
>> no one working on that right now.
>>
>> Sent from my iPhone
>>
>> > On 06 Jan 2016, at 23:52, Erik Weber <te...@gmail.com> wrote:
>> >
>> > A theoretical change could be to switch from VLAN assigned VIFs to using
>> > the VLAN feature in Linux kernel. That would give interface names like
>> > eth0.100 instead of eth0-6. Would need one NIC for each physical Network
>> > though.
>> >
>> > And I do not know if all hypervisors supports trunk ports.
>> >
>> >
>> > Erik
>> >
>> > Den mandag 28. desember 2015 skrev Davide Pala <da...@gesca.it>
>> > følgende:
>> >
>> >> Hi all.
>> >> I've read about vpc and tiers, now i've a question. VPC's virtual router
>> >> is a virtual machine and as the other vm it have some limit such as the
>> max
>> >> number of nic that an hypervisor can provide to vm (in xenserver this
>> limit
>> >> is set to 7) ...this mean that the vpc can have only 6 tier? there is a
>> way
>> >> to bypass this limit?
>> >> thanks to all
>> >>
>> >> Davide Pala
>> >> Infrastructure Specialist
>> >> Gesca srl
>> >>
>> >> Via degli Olmetti, 18
>> >> 00060 Formello (Roma)
>> >> Office:  +39 06 9040661
>> >> Fax:     +39 06 90406666
>> >> E-mail: davide.pala@gesca.it <javascript:;><mailto:davide.pala@gesca.it
>> >> <javascript:;>>
>> >> Web:    www.gesca.it<http://www.gesca.it/>
>> >>
>> >> [Descrizione: Descrizione: Descrizione: Descrizione: Descrizione:
>> >> Descrizione: logoGescaPER FIRMA]
>> >>
>> >>
>>

Re: VPC virtual router NIC limit

Posted by Erik Weber <te...@gmail.com>.
>From a technical or code perspective?

How would changing to openvswitch change anything in this scenario?

-- 
Erik

On Thu, Jan 7, 2016 at 7:16 AM, Remi Bergsma <RB...@schubergphilis.com>
wrote:

> I don't think that would work. Instead, we could change to openvswitch as
> that makes it way more flexibele. As far as I know there are no plans / is
> no one working on that right now.
>
> Sent from my iPhone
>
> > On 06 Jan 2016, at 23:52, Erik Weber <te...@gmail.com> wrote:
> >
> > A theoretical change could be to switch from VLAN assigned VIFs to using
> > the VLAN feature in Linux kernel. That would give interface names like
> > eth0.100 instead of eth0-6. Would need one NIC for each physical Network
> > though.
> >
> > And I do not know if all hypervisors supports trunk ports.
> >
> >
> > Erik
> >
> > Den mandag 28. desember 2015 skrev Davide Pala <da...@gesca.it>
> > følgende:
> >
> >> Hi all.
> >> I've read about vpc and tiers, now i've a question. VPC's virtual router
> >> is a virtual machine and as the other vm it have some limit such as the
> max
> >> number of nic that an hypervisor can provide to vm (in xenserver this
> limit
> >> is set to 7) ...this mean that the vpc can have only 6 tier? there is a
> way
> >> to bypass this limit?
> >> thanks to all
> >>
> >> Davide Pala
> >> Infrastructure Specialist
> >> Gesca srl
> >>
> >> Via degli Olmetti, 18
> >> 00060 Formello (Roma)
> >> Office:  +39 06 9040661
> >> Fax:     +39 06 90406666
> >> E-mail: davide.pala@gesca.it <javascript:;><mailto:davide.pala@gesca.it
> >> <javascript:;>>
> >> Web:    www.gesca.it<http://www.gesca.it/>
> >>
> >> [Descrizione: Descrizione: Descrizione: Descrizione: Descrizione:
> >> Descrizione: logoGescaPER FIRMA]
> >>
> >>
>

Re: VPC virtual router NIC limit

Posted by Remi Bergsma <RB...@schubergphilis.com>.
I don't think that would work. Instead, we could change to openvswitch as that makes it way more flexibele. As far as I know there are no plans / is no one working on that right now. 

Sent from my iPhone

> On 06 Jan 2016, at 23:52, Erik Weber <te...@gmail.com> wrote:
> 
> A theoretical change could be to switch from VLAN assigned VIFs to using
> the VLAN feature in Linux kernel. That would give interface names like
> eth0.100 instead of eth0-6. Would need one NIC for each physical Network
> though.
> 
> And I do not know if all hypervisors supports trunk ports.
> 
> 
> Erik
> 
> Den mandag 28. desember 2015 skrev Davide Pala <da...@gesca.it>
> følgende:
> 
>> Hi all.
>> I've read about vpc and tiers, now i've a question. VPC's virtual router
>> is a virtual machine and as the other vm it have some limit such as the max
>> number of nic that an hypervisor can provide to vm (in xenserver this limit
>> is set to 7) ...this mean that the vpc can have only 6 tier? there is a way
>> to bypass this limit?
>> thanks to all
>> 
>> Davide Pala
>> Infrastructure Specialist
>> Gesca srl
>> 
>> Via degli Olmetti, 18
>> 00060 Formello (Roma)
>> Office:  +39 06 9040661
>> Fax:     +39 06 90406666
>> E-mail: davide.pala@gesca.it <javascript:;><mailto:davide.pala@gesca.it
>> <javascript:;>>
>> Web:    www.gesca.it<http://www.gesca.it/>
>> 
>> [Descrizione: Descrizione: Descrizione: Descrizione: Descrizione:
>> Descrizione: logoGescaPER FIRMA]
>> 
>>