Update services to use the internal IP and port, now that its available.

Also update services to optionally use named ports.
Is specifying a name really necessary?  Could I not just specify a port number?  Choosing good port names as an API consumer is annoying unless the port name provides some additional value - I suspect many consumers would just use the number of the port as a string.

Also eventually it would be nice to allow services to define protocol/type information for implementers - if that happened there would be three values set all the same - "http" on service type, service container port name, and on container port name.