<div dir="ltr">Please file an issue for this: <a href="https://github.com/gluster/softserve/issues/new">https://github.com/gluster/softserve/issues/new</a><br></div><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Mar 20, 2018 at 1:57 PM, Sanju Rakonde <span dir="ltr"><<a href="mailto:srakonde@redhat.com" target="_blank">srakonde@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div><div><div>Hi Nigel,<br><br></div>I have a suggestion here. It will be good if we have a option like request for extension of the VM duration, and the option will be automatically activated after 3 hours of usage of VM. If somebody is using the VM after 3 hours and they feel like they need it for 2 more hours they will request to extend the duration by 1 more hour. It will save the time of engineering since if a machine is expired, one has to configure the machine and all other stuff from the beginning.<br><br></div>Thanks,<br></div>Sanju<br></div><div class="gmail_extra"><br><div class="gmail_quote"><div><div class="h5">On Tue, Mar 13, 2018 at 12:37 PM, Nigel Babu <span dir="ltr"><<a href="mailto:nigelb@redhat.com" target="_blank">nigelb@redhat.com</a>></span> wrote:<br></div></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div class="h5"><div dir="ltr"><br><div class="gmail_extra"><div class="gmail_quote"><span><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><span class="m_-8355854047920350653m_-5620100033322678246gmail-"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><p dir="ltr" style="line-height:1.38;margin-top:0pt;margin-bottom:0pt"><span style="font-size:11pt;font-family:Arial;color:rgb(0,0,0);background-color:transparent;font-weight:400;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap">We’ve enabled certain limits for this application:</span></p><ol style="margin-top:0pt;margin-bottom:0pt"><li dir="ltr" style="list-style-type:decimal;font-size:11pt;font-family:Arial;color:rgb(0,0,0);background-color:transparent;font-weight:400;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap"><p dir="ltr" style="line-height:1.38;margin-top:0pt;margin-bottom:0pt"><span style="font-size:11pt;font-family:Arial;color:rgb(0,0,0);background-color:transparent;font-weight:400;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap">Maximum allowance of 5 VM at a time across all the users. User have to wait until a slot is available for them after 5 machines allocation.</span></p></li><li dir="ltr" style="list-style-type:decimal;font-size:11pt;font-family:Arial;color:rgb(0,0,0);background-color:transparent;font-weight:400;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap"><p dir="ltr" style="line-height:1.38;margin-top:0pt;margin-bottom:0pt"><span style="font-size:11pt;font-family:Arial;color:rgb(0,0,0);background-color:transparent;font-weight:400;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap">User will get the requesting machines maximum upto 4 hours.</span></p></li></ol></div></blockquote><div><br></div></span><div>IMHO ,max cap of 4 hours is not sufficient. Most of the times, the reason of loaning a machine is basically debug a race where we can't reproduce the failure locally what I have seen debugging such tests might take more than 4 hours. Imagine you had done some tweaking to the code and you're so close to understand the problem and then the machine expires, it's definitely not a happy feeling. What are the operational challenges if we have to make it for atleast 8 hours or max a day?<br></div></div></div></div></blockquote><div><br></div></span>The 4h cap was kept so that multiple people could have a chance to debug their test failures on the same day. Pushing the cap to 8h means that if you don't have a machine to loan when you start work one will not be available until the next day. At this point, we'll not be increasing the timeout. So far, we've had one person actually hit this. I'd like to see more data points before we make an application level change.</div><span class="m_-8355854047920350653HOEnZb"><font color="#888888"><div class="gmail_quote"><br></div>-- <br><div class="m_-8355854047920350653m_-5620100033322678246gmail_signature"><div dir="ltr">nigelb<br></div></div>
</font></span></div></div>
<br></div></div><span class="">______________________________<wbr>_________________<br>
Gluster-devel mailing list<br>
<a href="mailto:Gluster-devel@gluster.org" target="_blank">Gluster-devel@gluster.org</a><br>
<a href="http://lists.gluster.org/mailman/listinfo/gluster-devel" rel="noreferrer" target="_blank">http://lists.gluster.org/mailm<wbr>an/listinfo/gluster-devel</a><br></span></blockquote></div><br></div>
</blockquote></div><br><br clear="all"><br>-- <br><div class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr">nigelb<br></div></div>
</div>