[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
NFV Solution Evaluation Methodology
- Subject: NFV Solution Evaluation Methodology
- From: randy at psg.com (Randy Bush)
- Date: Wed, 03 Aug 2016 16:56:34 +0900
- In-reply-to: <CAL9jLaYhadWDD0tdMitHR_R=53uRQzb2Au5XgsHGzs3tgjCy3A@mail.gmail.com>
- References: <CALb2afNOJc+9dZm=U5msMPYP2dhfvEvkEfq40TBBLHBAROyTqg@mail.gmail.com> <CAD6AjGS7ZoOSdZDNVzyrqgVJiKcr-hKyVVqyKpv2Dop4pFtWig@mail.gmail.com> <CAB69EHgeZyWHkGXDXHz=5HrZx1ihGcj3ndJANv4qick_FJQ5oA@mail.gmail.com> <CAL9jLaYhadWDD0tdMitHR_R=53uRQzb2Au5XgsHGzs3tgjCy3A@mail.gmail.com>
> but, NFV isn't necessarily 'cloud'... It CAN BE taking purpose built
> appliance garbage that can't scale in a cost effective manner and
> replacing it with some software solution on 'many' commodity
> unix-like-hosts that can scale horizontally.
my main worry about nfv is when they need more forwarding horsepower
than the household appliance <tm mo> has, and the data plan is is moved
out of the control plane and they are not congruent. we've had too many
lessons debugging this situation (datakit, atm, ...).
beyond that, i am not sure i see that much difference whether it's a
YFRV or a SuperMicro. but i sure wish bird and quagga had solid is-is,
supported communities, ...
randy