Re: [Gluster-devel] Announcing Softserve- serve yourself a VM
On 02/28/2018 06:56 PM, Deepshikha Khandelwal wrote: Hi, We have launched the alpha version of SOFTSERVE[1], which allows Gluster Github organization members to provision virtual machines for a specified duration of time. These machines will be deleted automatically afterwards. Now you don’t need to file a bug to get VM. It’s just a form away with a dashboard to monitor the machines. Once the machine is up, you can access it via SSH and run your debugging (test regression runs). We’ve enabled certain limits for this application: 1. 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. 2. User will get the requesting machines maximum upto 4 hours. 3. Access to only Gluster organization members. These limits may be resolved in the near future. This service is ready to use and if you find any problems, feel free to file an issue on the github repository[2]. Hi, While https://github.com/gluster/softserve/issues/31 gets some attention, I've sent a pr [*] based on grepping through source code to allow a 24 hour reservation slot. Please have a look. Thanks! Ravi [*] https://github.com/gluster/softserve/pull/46 [1]https://softserve.gluster.org [2]https://github.com/gluster/softserve Thanks, Deepshikha ___ Gluster-devel mailing list Gluster-devel@gluster.org http://lists.gluster.org/mailman/listinfo/gluster-devel ___ Gluster-devel mailing list Gluster-devel@gluster.org https://lists.gluster.org/mailman/listinfo/gluster-devel
Re: [Gluster-devel] Announcing Softserve- serve yourself a VM
Please file an issue for this: https://github.com/gluster/softserve/issues/new On Tue, Mar 20, 2018 at 1:57 PM, Sanju Rakondewrote: > Hi Nigel, > > 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. > > Thanks, > Sanju > > On Tue, Mar 13, 2018 at 12:37 PM, Nigel Babu wrote: > >> >> We’ve enabled certain limits for this application: 1. 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. 2. User will get the requesting machines maximum upto 4 hours. >>> 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? >>> >> >> 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. >> >> -- >> nigelb >> >> ___ >> Gluster-devel mailing list >> Gluster-devel@gluster.org >> http://lists.gluster.org/mailman/listinfo/gluster-devel >> > > -- nigelb ___ Gluster-devel mailing list Gluster-devel@gluster.org http://lists.gluster.org/mailman/listinfo/gluster-devel
Re: [Gluster-devel] Announcing Softserve- serve yourself a VM
Hi Nigel, 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. Thanks, Sanju On Tue, Mar 13, 2018 at 12:37 PM, Nigel Babuwrote: > > We’ve enabled certain limits for this application: >>> >>>1. >>> >>>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. >>>2. >>> >>>User will get the requesting machines maximum upto 4 hours. >>> >>> >> 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? >> > > 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. > > -- > nigelb > > ___ > Gluster-devel mailing list > Gluster-devel@gluster.org > http://lists.gluster.org/mailman/listinfo/gluster-devel > ___ Gluster-devel mailing list Gluster-devel@gluster.org http://lists.gluster.org/mailman/listinfo/gluster-devel
Re: [Gluster-devel] Announcing Softserve- serve yourself a VM
> We’ve enabled certain limits for this application: >> >>1. >> >>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. >>2. >> >>User will get the requesting machines maximum upto 4 hours. >> >> > 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? > 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. -- nigelb ___ Gluster-devel mailing list Gluster-devel@gluster.org http://lists.gluster.org/mailman/listinfo/gluster-devel
Re: [Gluster-devel] Announcing Softserve- serve yourself a VM
On Wed, Feb 28, 2018 at 6:56 PM, Deepshikha Khandelwalwrote: > Hi, > > We have launched the alpha version of SOFTSERVE[1], which allows Gluster > Github organization members to provision virtual machines for a specified > duration of time. These machines will be deleted automatically afterwards. > > Now you don’t need to file a bug to get VM. It’s just a form away with a > dashboard to monitor the machines. > > Once the machine is up, you can access it via SSH and run your debugging > (test regression runs). > > We’ve enabled certain limits for this application: > >1. > >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. >2. > >User will get the requesting machines maximum upto 4 hours. > > 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? >1. > >Access to only Gluster organization members. > > > These limits may be resolved in the near future. This service is ready to > use and if you find any problems, feel free to file an issue on the github > repository[2]. > > [1]https://softserve.gluster.org > > [2]https://github.com/gluster/softserve > > > Thanks, > > Deepshikha > > > ___ > Gluster-devel mailing list > Gluster-devel@gluster.org > http://lists.gluster.org/mailman/listinfo/gluster-devel > ___ Gluster-devel mailing list Gluster-devel@gluster.org http://lists.gluster.org/mailman/listinfo/gluster-devel