Allow user to set container internal network interface name

[lukaspustina]

Hi,

I found myself needing more than just one additional interface for my containers, because my network configuration of containers reflects a production system with several independent VLAN.

I modified pipework to allow the user to (optionally) set the container internal interface. The optional parameter is positional and has to follow after IFNAME on the command line. Further, I added a verbose options to print relevant (to me) information during pipework works.

The command line parsing is not very nice, but I tried to stay as close to the original syntax to not break any existing usage of pipework.

I'd be happy, if you accept my pull request.

Bye, Lukas

[cpuguy83]

LGTM!

[jpetazzo]

@lukaspustina: thanks for this PR, and sorry that it took me forever to review it. Do you think you could:

• remove the WAIT/VERBOSE stuff (there's already support for WAIT, and I think VERBOSE should be implemented differently)
• rebase on master?

Thanks again!

[lukaspustina]

@jpetazzo: No problem.

• Yes. I agree, but I wanted to change as little as possible.
• Sure.

[jpetazzo]

Thanks once again! Your help is much appreciated.