Re: Updates done to CC configuration does not get reflected in spinning new instances

Hi Akila, On Mon, Nov 16, 2015 at 11:41 AM, Akila Ravihansa Perera wrote: > Hi Isuru, > > Shall we compare the cached IaasProvider object with latest values before > building the jclouds template as an improvement? This will avoid > unnecessary API calls to build the object. > +1, excellent sugg

Re: Updates done to CC configuration does not get reflected in spinning new instances

Hi Isuru, Shall we compare the cached IaasProvider object with latest values before building the jclouds template as an improvement? This will avoid unnecessary API calls to build the object. Also we will have to check the cached objects at Stratos server startup and build forcefully if there are

Re: Updates done to CC configuration does not get reflected in spinning new instances

One limitation of this approach is that JClouds will do a API call to validate the information that is provided to build the template each when spawning an instance. But, since we are re-doing it only at instance startup, IMHO it should not be a issue. Please share your thoughts. On Mon, Nov 16, 2

Re: Updates done to CC configuration does not get reflected in spinning new instances

> > Building new IaasProvider objects is done when there is a need to spawn > instances. Then the new IaasProvider object is cached. So the cache would > not be re-built when the CC is restarted, but only when instances are > actually getting spawned. The main reason for approach is that a cartridg

Jenkins build became unstable: Stratos-41x-Nightly-Build » Apache Stratos - Integration Tests #51

See

Jenkins build became unstable: Stratos-41x-Nightly-Build #51

See