Juergen: 

 

On first sentence, ... restated 

Do you believe the "ephemeral operational state" belongs in the ephemeral
requirements? If so, we can add it.  Perhaps we should also add a definition
for ephemeral configuration. 

 

On picture -- here is your picture: 

 

   +-------------+                  +-----------+

   | <candidate> |                  | <startup> |

   |  (ct, rw)   |<---+        +--->| (ct, rw)  |

   +-------------+    |        |    +-----------+

          |           |        |           |

          |         +------------+         |

          +-------->| <running>  |<--------+

                    | (ct, rw)   |

                    +------------+

                          |         // e.g., removal of 'inactive' nodes

                          v

                    +------------+

                    | <intended> |  // subject to validation

                    | (ct, ro)   |

                    +------------+

                          |         // e.g., missing resources or delays

                          v

                    +------------+

                    | <applied>  |

                    | (ct, ro)   |

                    +------------+

                          |         // e.g., autodiscovery of values

                          v

          +--------------------------------+

          | <operational-state>            |<-- control plane and

          | (ct + cf, ro)                  |    ephemeral datastores

          +--------------------------------+

 

Is this part of the picture 

 

          +--------------------------------+

          | <operational-state>            |<-- control plane and

          | (ct + cf, ro)                  |    ephemeral datastores

          +--------------------------------+

 

Really 

  +--------------------+    +--------------------------+
+-----------------------+

 |    opstate         |    | ephemeral config  |   | applied  config    |

 | (cf, ro)               |    |   (ct, ro, ephemeral|  | (ct, ro)
|

 +--------------------+    +---------------------------+
+-------------------------+

 

Or just 

  +--------------------+    +--------------------------+    

  |    opstate         |    | ephemeral config  |    

  | (cf, ro)               |    |   (ct, ro, ephemeral 

  +--------------------+    +---------------------------+   

 

 

Sue 

 

-----Original Message-----
From: i2rs [mailto:[email protected]] On Behalf Of Juergen Schoenwaelder
Sent: Thursday, June 02, 2016 7:05 AM
To: Susan Hares
Cc: 'Jeffrey Haas'; [email protected]; 'Benoit Claise'; 'Alia Atlas'
Subject: Re: [i2rs] I2RS Interim Meeting - June 1, 2016 - 10:00am - 11:00am
-? Topic: Ephemeral State Requirements

 

On Thu, Jun 02, 2016 at 06:53:42AM -0400, Susan Hares wrote:

> Juergen:

> 

> Do you think this definition belongs in the ephemeral requirements?  If
so,

> we can add it.   But perhaps we should define both ephemeral configuration

> and ephemeral operational state.  Joel point out at the I2RS interim 

> that ephemeral operational state is just like all other operational state
- it

> disappears upon reboot.   It is ephemeral configuration which is different

> than normal configuration - since it disappears upon reboot where 

> normal configuration does not.

> 

> Is this diagram close to your existing model where opstate and 

> ephemeral configuration are parallel?

> 

> +--------------------+    +--------------------------+

> |    opstate         |    | ephemeral config  |

> +--------------------+    +--------------------------+

> 

 

I see two boxes, I am unsure what you think these boxes drawn this way mean.
What is 'this definition' in your first sentence? I really have problems to
follow what is going on.

 

/js

 

-- 

Juergen Schoenwaelder           Jacobs University Bremen gGmbH

Phone: +49 421 200 3587         Campus Ring 1 | 28759 Bremen | Germany

Fax:   +49 421 200 3103         < <http://www.jacobs-university.de/>
http://www.jacobs-university.de/>

 

_______________________________________________

i2rs mailing list

 <mailto:[email protected]> [email protected]

 <https://www.ietf.org/mailman/listinfo/i2rs>
https://www.ietf.org/mailman/listinfo/i2rs

_______________________________________________
i2rs mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/i2rs

Reply via email to