That's what I was going to say... start with feature parity on the default VPC/router. Conspicuously missing from Vyatta's functionality, however, is the load balancing (virtual IP redirecting to many servers). I'm sure someone could put haproxy into the image, however.
On Wed, Dec 19, 2012 at 8:54 AM, Chip Childers <[email protected]>wrote: > On Wed, Dec 19, 2012 at 10:52 AM, Musayev, Ilya <[email protected]> > wrote: > > No takers? > > "Musayev, Ilya" <[email protected]> wrote: > > Dear CS Community, > > > > If you had experience with Vyatta and CS, what features of Vyatta > community edition do you believe will be most useful if it was to be > integrated it with CS as part of network offering? > > > > Vyatta is very feature rich and we probably should focus only on the > core - most commonly used components. > > > > Thanks > > ilya > > > > So I'm +1 to seeing this happen, especially when combined with the > other proposal for allowing CS to manage the network service VMs > (create and delete them as needed) on behalf of the admin / users. > > As for the features, my personal opinion would be to start with the > same FW capabilities that CS provides via the Virtual Router. It > could be extended from there, but that should be the baseline. Just > my 2 cents though. >
