On Tue, Nov 20, 2012 at 03:03:37PM -0500, Lars Kellogg-Stedman wrote: > automatically assigned ip address for several minutes (possibly more > than 10 or 15) after the system boots.
In fact, 30 minutes. I spent some time staring at the clock yesterday. I'm assuming that the calls to self.network_api.invalidate_instance_cache(...) are supposed to take care of this...for example, I see one in compute.api.associate_floating_ip. Do automatically assigned addresses follow the same process as manually assigned ones? Is there a place where I can insert an explicit call to invalidate the cache? -- Lars Kellogg-Stedman <[email protected]> | Senior Technologist | http://ac.seas.harvard.edu/ Academic Computing | http://code.seas.harvard.edu/ Harvard School of Engineering | and Applied Sciences | _______________________________________________ Mailing list: https://launchpad.net/~openstack Post to : [email protected] Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
