Re: [Netconf] Does NMDA support synchronous configuration operation?

[Henry Yu <[e-mail]>]

Hi Juergen,

On Mon, Jun 25, 2018 at 3:00 PM Juergen Schoenwaelder
<[e-mail]> wrote:
>
[snip snip snip]
>
> Note that once you deal with pluggable hardware, you often loose the
> synchronous behaviour since <running> and <operational> can deviate
> depending on hardware resources present. (This may also be true for
> pluggable software, i.e., software features controlled by licenses.)

You mentioned, in an earlier response as well, that "the change of
<running>, however, does not require that all changes have propagated
to <operational>".  I interpret it as that, in case of this pluggable
hardware scenario, when client, for example, POST a configuration,
server should save it into <running>, even when the target pluggable
is unavailable. This, of course, would cause difference between
<running> and <operational>. But the POST operation itself is
successful and returns success to client.

The above would be my implementation of the server. However, some
people believe a different implementation:  that the config should not
be saved to <running> if the pluggable is unavailable. And when
pluggable is unavailable, server should fail the POST config operation
and return error to client. We need to know which implementation is
correct. That's why I asked for clarification.

Thanks,
Henry

>
> /js
>

>
> --
> Juergen Schoenwaelder           Jacobs University Bremen gGmbH
> Phone: [phone]         Campus Ring 1 | 28759 Bremen | Germany
> Fax:   [phone]         <https://www.jacobs-university.de/>