On Mon, 2016-10-31 at 08:38 -0400, Stephen Gallagher wrote:
On 10/31/2016 08:27 AM, Simo Sorce wrote:
> On Fri, 2016-10-28 at 20:02 +0200, Stef Walter wrote:
>> This is similar to how a Linux desktop asks you to click in a dialog
>> if you accept the new display configuration. Except in the networking
>> case we can test the connectivity automatically.
> Although in many cases this is the case, it is not always the case, is
> this under the control of the admin ?
> (I just configured my new openwrt on my new router, my net config was
> perfectly right, but the box was not connected to anything beyond my
> administering client, which also switched between 2 networks at my
Well, I don't think this is any worse than the previous state. If you made the
same modification in Cockpit 120, the system would have just gone ahead and done
it and you would be out of luck.
Well I think you misunderstand my concern.
My concern is for when I want the system to get the new configuration
*even if I lose connection/ the system can't verify the connection
In 121, if you make a change and it detects that you're now
unreachable, it can
roll that back and give you another try.
This is the problem, as I was changing config I knew the final state,
but there had to be a time where the configuration would be "wrong"
until I could go and switch the cables around.
I can do the config change only before I switch around the cables, and
here will be a period of time when the conf will not work.
So it sounds like a net win, even if it's imperfect.
I was only asking if I can force a change w/o additional confirmation.
Do I understand correctly, from the video, that cockpit will try to make
the change, if it fails to connect will restore back the initial
configuration and ask for confirmation, and if confirmed it will once
more apply the new config for good ?
That works for me, even though you end up switching back and forth twice
under the hood :)
Simo Sorce * Red Hat, Inc * New York