Not that we don't have the terminated node cache, I'm wondering if we need the node registry at all. If I get it, we have a cache of nodes that is built from a *memoized* supplier, so we only get a fresh list of existing nodes when we create the context. For example, if we call `listNodes`, manually create a machine, and call `listNodes` again, we won't see the change. Is this correct? And is this what we want? (Is it that expensive to list the existing machines, that we need a cache?).
If it turns the cache is necessary, I'd suggest to add an expiration to the the node memoized supplier according to the session timeout property. This is how most of the caches in jclouds are configured (sucha as in [this example](https://github.com/jclouds/jclouds/blob/master/providers/google-compute-engine/src/main/java/org/jclouds/googlecomputeengine/compute/config/GoogleComputeEngineServiceContextModule.java#L168-L180). -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds-labs/pull/357#issuecomment-276964114
