s/there is not possibility/there is no possibility/g On Fri, Jan 2, 2015 at 2:21 AM, Imesh Gunaratne <[email protected]> wrote:
> Hi Devs, > > This is to discuss $subject. As we found in other mail threads, there is a > fundamental problem in the logic how Autoscaler/Cloud Controller > communication is done in terms of managing the lifecycle of the members. > This problem only affects in certain scenarios when members do not start as > expected. > > *InstanceSpawnedEvent:* > Above problem starts with this event: This event name implies that it > should be published soon after instance is spawned by the IaaS. However it > has properties to send IP addresses. These requirements conflicts, IP > addresses will only be available after certain time period once the > instance is spawned. > > Inaddition to the above conflicting requirements, Python Agent waits for > this event to initialize the agent instance. If this event is sent soon > after the instance is spawned there is not possibility that agent could > receive this event. > > One other problem is that we have used a convention when naming events in > Instance Status topic. All the events under Instance Status topic starts > with the term "Instance" and all corresponding events in the topology topic > starts with the term "Member". > > Due to above reasons I think we could introduce two events called > "Member-Created" and "Member-Initialized" as follows: > > > Thanks > > > > -- > Imesh Gunaratne > > Technical Lead, WSO2 > Committer & PMC Member, Apache Stratos > -- Imesh Gunaratne Technical Lead, WSO2 Committer & PMC Member, Apache Stratos
