A nice vision Keerthi. I would love to see something like this implemented in CloudStack.
Sometimes we just want to link VMs at Layer 2. I¹m aware that there are ways of doing this without instantiating virtual routers, but these methods are not officially supported. CloudStack seems very much focused on Layer 3 networking. The ability to build VPCs without assigning IP addresses to every interface would be very useful. Best regards, -Christian Christian Lafferty (BT) On 24/04/2015 15:18, "Keerthiraja SJ" <sjkeer...@gmail.com> wrote: >Hi All, > >This is the email about why can we merge the cloudrouter.org in cloudstack >in the new 4.6. > > >I basic idea is in Advance Networking when we choose VLAN isolatation why >do we need more router. > >Can we do something like same what Nuage Network Provides. > >In Advance Networking configuration of Guest VLAN isolation we create many >VM it creates many routers where this should be avoided and ACS should >come >up with good solution on networking part than depending on creating VLAN >on >switch. > >With reference to below link > >https://cwiki.apache.org/confluence/display/CLOUDSTACK/NuageVsp+Network+Pl >ugin > >All the network isolation and routing is handled by the Nuage SDN >solution. >Routing of the packets happen at hypervisor itself. Virtual Router is not >used for routing the packets thus the current issue of the Virtual Router >being the bottleneck is avoided. The Virtual Router VM is used only for >Password reset functionality. The Nuage solution also helps significantly >improve the agility and scale of a CS deployment as compared to a Virtual >Router based deployment > >Why CS can have the same inbuilt features than of Nuage. > >For example : We can set two routers if we need we should have options to >create backup server to redundancy. > >Can we merge something with cloudrouter to make ACS better. > > >Thanks, >Keerthi > >Live for stack :) cloudstack.
