On 02/05/2018 02:21 PM, Daniel P. Berrangé wrote:
> On Mon, Feb 05, 2018 at 02:11:24PM +0100, Peter Krempa wrote:
>> On Mon, Feb 05, 2018 at 12:55:11 +, Daniel Berrange wrote:
>>> On Mon, Feb 05, 2018 at 01:39:56PM +0100, Michal Privoznik wrote:
On 02/01/2018 08:51 AM, Nikolay Shirokovskiy
On 05.02.2018 16:27, Michal Privoznik wrote:
> On 02/05/2018 02:21 PM, Daniel P. Berrangé wrote:
>> On Mon, Feb 05, 2018 at 02:11:24PM +0100, Peter Krempa wrote:
>>> On Mon, Feb 05, 2018 at 12:55:11 +, Daniel Berrange wrote:
On Mon, Feb 05, 2018 at 01:39:56PM +0100, Michal Privoznik wrot
On Mon, Feb 05, 2018 at 02:11:24PM +0100, Peter Krempa wrote:
> On Mon, Feb 05, 2018 at 12:55:11 +, Daniel Berrange wrote:
> > On Mon, Feb 05, 2018 at 01:39:56PM +0100, Michal Privoznik wrote:
> > > On 02/01/2018 08:51 AM, Nikolay Shirokovskiy wrote:
> > > >
> > > >
> > > > On 29.01.2018 09:0
On Mon, Feb 05, 2018 at 12:55:11 +, Daniel Berrange wrote:
> On Mon, Feb 05, 2018 at 01:39:56PM +0100, Michal Privoznik wrote:
> > On 02/01/2018 08:51 AM, Nikolay Shirokovskiy wrote:
> > >
> > >
> > > On 29.01.2018 09:09, Michal Privoznik wrote:
> > >> On 12/20/2017 07:35 AM, Nikolay Shirokov
On Mon, Feb 05, 2018 at 01:39:56PM +0100, Michal Privoznik wrote:
> On 02/01/2018 08:51 AM, Nikolay Shirokovskiy wrote:
> >
> >
> > On 29.01.2018 09:09, Michal Privoznik wrote:
> >> On 12/20/2017 07:35 AM, Nikolay Shirokovskiy wrote:
> >>> Host tcp4/tcp6 ports is a global resource thus we need to
On 02/01/2018 08:51 AM, Nikolay Shirokovskiy wrote:
>
>
> On 29.01.2018 09:09, Michal Privoznik wrote:
>> On 12/20/2017 07:35 AM, Nikolay Shirokovskiy wrote:
>>> Host tcp4/tcp6 ports is a global resource thus we need to make
>>> port accounting also global or we have issues described in [1] when
On 29.01.2018 09:09, Michal Privoznik wrote:
> On 12/20/2017 07:35 AM, Nikolay Shirokovskiy wrote:
>> Host tcp4/tcp6 ports is a global resource thus we need to make
>> port accounting also global or we have issues described in [1] when
>> port allocator ranges of different instances are overlappe
On 01/29/2018 12:07 PM, Peter Krempa wrote:
> On Mon, Jan 29, 2018 at 07:09:54 +0100, Michal Privoznik wrote:
>> On 12/20/2017 07:35 AM, Nikolay Shirokovskiy wrote:
>>> Host tcp4/tcp6 ports is a global resource thus we need to make
>>> port accounting also global or we have issues described in [1]
On Mon, Jan 29, 2018 at 07:09:54 +0100, Michal Privoznik wrote:
> On 12/20/2017 07:35 AM, Nikolay Shirokovskiy wrote:
> > Host tcp4/tcp6 ports is a global resource thus we need to make
> > port accounting also global or we have issues described in [1] when
> > port allocator ranges of different ins
On 12/20/2017 07:35 AM, Nikolay Shirokovskiy wrote:
> Host tcp4/tcp6 ports is a global resource thus we need to make
> port accounting also global or we have issues described in [1] when
> port allocator ranges of different instances are overlapped (which
> is by default for qemu for example).
>
>
Host tcp4/tcp6 ports is a global resource thus we need to make
port accounting also global or we have issues described in [1] when
port allocator ranges of different instances are overlapped (which
is by default for qemu for example).
Let's have only one global port allocator object that take care
11 matches
Mail list logo