Displaying 4 results from an estimated 4 matches for "nperic".
Did you mean:
peric
2018 Sep 25
0
Re: OpenStack output - server_id
...406P0up9qTR1owxlRxSUf0ydKSdqcsZH/m5Ua4w5t9fPCHxCmOXiVfTW5iFKZOIGQwdcH8f5j5UnX/Q50dyrvy2QIw+nzLQcGHa5ZZKPFcXmAO7NBx7pIdrf76FtIVwnF4FA8AAKrsZc4We/IAAhX/SUNYZ3JHjp/M=",
"uuid": "7ee62bdc-1c9d-4193-bb8f-fdbbbdfded0f"
}
The information we need is the uuid.
@Nenad Peric <nperic@redhat.com>, this comes from our lab. I've enabled
DHCP on the external network, but that don't mean that all networks will
use it. In the conversion host project, I'd enable it.
On Mon, Sep 24, 2018 at 9:16 PM Nenad Peric <nperic@redhat.com> wrote:
>
>
> On Mon, Se...
2018 Sep 24
2
Re: OpenStack output - server_id
On Mon, Sep 24, 2018 at 6:30 PM Richard W.M. Jones <rjones@redhat.com>
wrote:
> On Mon, Sep 24, 2018 at 10:00:21AM +0200, Fabien Dupont wrote:
> > Hi,
>
> Hi Fabien, sorry I didn't respond to this earlier as I was doing some
> work. If you CC me on emails then you can usually get a quicker
> response.
>
> > I've read the virt-v2v OpenStack output code
2019 Sep 19
0
Re: [PATCH nbdkit 0/2] Add new retry filter.
A theoretical way to test this against any other protocol is to have a
firewall rule which can be triggered locally which just drops the traffic
and then re-enables the traffic in a while (short or long, can be
decided/tweaked).
This way, there is no need to think about which protocol is used, when we
kill the connectivity.
The only consideration could probably be that the dropped connections
2019 Sep 19
1
Re: Thoughts on nbdkit automatic reconnection
I have an update on the networking issue:
- After the deep dive into the logs of the firewall by customer's security
team, it turns out that even though there were some disconnections, the
time-stamps do not match.
This means that we got the disconnected by something else (ESXi or
conversion host perhaps)
- As we mentioned in the chat briefly, there could be general keep-alive
issues on both