Hi Reka, Yes, This is a valid point. Here what I like to suggest. First of all, floating IP assign happen only we have request it in the cartridge definition. Means if any case floating IP assign failed, we have to rollback and return subscription false. For that, we need to introduce subscription error state to the topology. If CC failed to assign floating IP, CC should mark it with the error state. Autoscaler should look this state also when spawning the new instances. Also we need to terminate all error spawn instances as well. With this error state, SM notify user subscription failed with the reason.
make sense? On Sun, Mar 16, 2014 at 8:44 AM, Reka Thirunavukkarasu <[email protected]>wrote: > Hi all, > > We need to consider on $subject, since we spawn an instance when it failed > to create a floating ip. As we throw an exception when it failed to > allocate a floating ip, CC won't create a new member in the Topology. Since > the instance creation failed, autoscaler doesn't keep track of this > instance and it will try to spin another one instead. This will lead to > resource exhausted state at some point in the IaaS. > > How can we avoid this happening? Can we make the CC capable of terminating > the instance when it failed to allocate an ip or Can we create the member > with a different state like pending or something to the topology and > returns the call successful to autoscaler. So that, autoscaler can detect > this instance as pending and terminate it at some point. > > Any thoughts regarding this? > > Thanks, > Reka > > -- > Reka Thirunavukkarasu > Software Engineer, > WSO2, Inc.:http://wso2.com, > Mobile: +94776442007 > > > -- Lakmal Warusawithana Software Architect; WSO2 Inc. Mobile : +94714289692 Blog : http://lakmalsview.blogspot.com/
