[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
NFV Solution Evaluation Methodology
- Subject: NFV Solution Evaluation Methodology
- From: morrowc.lists at gmail.com (Christopher Morrow)
- Date: Tue, 2 Aug 2016 23:07:42 -0400
- In-reply-to: <CAB69EHgeZyWHkGXDXHz=5HrZx1ihGcj3ndJANv4qick_FJQ5oA@mail.gmail.com>
- References: <CALb2afNOJc+9dZm=U5msMPYP2dhfvEvkEfq40TBBLHBAROyTqg@mail.gmail.com> <CAD6AjGS7ZoOSdZDNVzyrqgVJiKcr-hKyVVqyKpv2Dop4pFtWig@mail.gmail.com> <CAB69EHgeZyWHkGXDXHz=5HrZx1ihGcj3ndJANv4qick_FJQ5oA@mail.gmail.com>
On Tue, Aug 2, 2016 at 10:16 PM, Eric Kuhnke <eric.kuhnke at gmail.com> wrote:
> But but but... cloud! THE CLOUD! Cloudy clouds fluffy white flying
> through the air, you should move everything to the Cloud (tm).
>
> Sometimes people forget that *somebody* needs to run the bare metal and OSI
> layer 1 things that physically make up the cloud.
>
>
mr by isn't wrong there are lots of ... over sold things.
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.
-chris
(just a chemical engineer... really)