[Buildbot-devel] Flexibility to Stop or Terminate LatentSlave as load drops

kuldeep porwal 2591kuldeep at gmail.com
Thu Mar 20 15:03:08 UTC 2014


Hi all,
         We should in some scenario Stop the slave instead of always
Terminatiing it when timeout expires. Having the instances be stopped
instead of terminated is useful when you are using EBS volumes and want to
keep them mounted for the life of the instance and reuse the instance for
long periods of time. This can greatly reduce the startup time of the
instance since it does not have to build the volume from the snapshot. we
can ask users (as a parameter) whether they want to *terminate* the
instance when load goes down or they want to *stop.*


On Thu, Mar 20, 2014 at 4:35 PM, kuldeep porwal <2591kuldeep at gmail.com>wrote:

> Hi all,
>
> I have a following doubt in latent-slave stop_instance logic of buildbot.
>
>  file:buildbot/master/buildbot/buildslave/ec2.py .
>
> As we know we can't stop a spot instance but we can stop other instances.
> so sometimes it will be better to shutdown the build slave for some time
> and reboot it when required (scenario arises when load is shifting towards
> high). This will help in
> * decreasing the overhead * of relaunching the slave again.
>
>  Where in the function _stop_instance() we are doing that? all I can
> understand is like we are terminating a slave when it is not already
> terminated.
> (line: instance.terminate()).
>
>
> --
> Regards,
> Kuldeep Porwal
> IIIT Hyderabad
> 09550605256
> http://web.iiit.ac.in/~kuldeep.porwal
>



-- 
Regards,
Kuldeep Porwal
IIIT Hyderabad
09550605256
http://web.iiit.ac.in/~kuldeep.porwal
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://buildbot.net/pipermail/devel/attachments/20140320/85105174/attachment.html>


More information about the devel mailing list