Re: [ClusterLabs Developers] bundle/rkt: port-mapping numbers/names

2017-08-02 Thread Valentin Vidic
On Wed, Jul 19, 2017 at 06:53:44PM +0200, Jan Pokorný wrote: > I don't think that alone would suffice, I'd expect at least (port,transport) > pair to be reasonably unique as long as you can remap TCP/UDP independently > (I am not sure, but would be no surprise) -- but hey, we have just hit >

Re: [ClusterLabs Developers] bundle/rkt: port-mapping numbers/names

2017-07-19 Thread Jan Pokorný
On 19/07/17 09:49 -0500, Ken Gaillot wrote: > On 07/19/2017 01:20 AM, Valentin Vidic wrote: >> Another issue with the rkt containers is the port-mapping. Each container >> defines exposed ports: >> >> "ports": [ >> { >> "name": "http", >>

Re: [ClusterLabs Developers] bundle/rkt: port-mapping numbers/names

2017-07-19 Thread Ken Gaillot
On 07/19/2017 01:20 AM, Valentin Vidic wrote: > Another issue with the rkt containers is the port-mapping. Each container > defines exposed ports: > > "ports": [ > { > "name": "http", > "protocol": "tcp", >

Re: [ClusterLabs Developers] bundle/rkt: port-mapping numbers/names

2017-07-19 Thread Valentin Vidic
Another issue with the rkt containers is the port-mapping. Each container defines exposed ports: "ports": [ { "name": "http", "protocol": "tcp", "port": 80, "count": 1,