removing NetworkManager from cloud image?

[Andy Grimm]

On Thu, Oct 11, 2012 at 1:19 PM, Matthew Miller
<mattdm at fedoraproject.org> wrote:
> The simple old-fashioned network configuration works just fine for basic
> cloud use-cases which I can think of, and NetworkManager a) brings in a lot
> of dependencies of little value in this case (e.g. ModemManager,
> wpa_supplicant). Plus, out of the box in the EC2 image, NetworkManager is
> the second-largest memory consumer (after dhclient). It's not huge, but if
> we want to get as JEOSy as possible, this seems pretty painless and
> straightforward.
>
> Thoughts?

This feels like https://bugzilla.redhat.com/show_bug.cgi?id=693602 all
over again (the debate about whether to make "minimal" installs
include NM or to make sure that the network service starts correctly
when NM is absent).  I am no fan of NM, but I think the memory
consumption angle is a weak argument (the RSS for NM on my system is
4MB right now -- that's less than 1% of the RAM of the smallest
instance type in EC2), and since the decision as far as I'm aware is
that "minimal" installs now contain NM, we should go along with that.
 Wherever NM causes a problem, it should be treated as an NM bug and
fixed, not used as an excuse to deviate for the standard distro
install.

Just my two cents.

Andy