Comment 9 for bug 1649902

After confirmation with pacemaker folks, I got that pacemaker can't start haproxy in a new network namespace
automatically. If we want to do that, we might create the new network namespace or container by ourselves
which is managed by pacemaker as resource and haproxy is running in. Something just like what fuel does.
Thx