Re: [Gluster-infra] [Gluster-devel] Announcing Softserve- serve yourself a VM

[Ravishankar N]

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-de...@gluster.org
http://lists.gluster.org/mailman/listinfo/gluster-devel


___
Gluster-infra mailing list
Gluster-infra@gluster.org
https://lists.gluster.org/mailman/listinfo/gluster-infra

Re: [Gluster-infra] [Gluster-devel] Announcing Softserve- serve yourself a VM

[Sankarshan Mukhopadhyay]

On Tue, Mar 20, 2018 at 1:57 PM, Sanju Rakonde  wrote:

> 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.
>

As Nigel states later on, please file an issue. I fear that very soon
we will require an enhancement to the issue which might have to handle
how many times an extension can be sought. Supplementing it would be
another enhancement around how often can a particular individual
request for extension on a particular machine instance within the
space of a work week. And thus, at some point, a simple machine
instance allocation system would need to be backed by a decision
making system.

This was supposed to be an easy-to-use infrastructure, not where the
Infra team members chase down individuals who are not freeing up
machines for as high as 5 weeks (I am not going to publicly cite this
instance).

That being said, I think it is worth a moment to think about what is
happening with Softserve.

The system is intended to provide a set of finite metered resources
available to developers in order to debug issues. The number of
available machine instances are not high (at this point) and the
resource allocation during this initial period has been designed to be
this way so as to arrive at a better understanding of usage patterns.

A 4 hour allocation is half of a working day. If we do think that this
is not enough, we want to also think deeply about the following (a)
all our issues require more than a day’s worth of debugging (b)
perhaps we are unable to allocate a dedicated 4 hour block on one
topic ie. there are distractions (c) there will not be enough machine
instances to make available to a backlog of developers waiting to
start off with their work

Any one or, a combination of the above possibilities are larger
challenges which need to be addressed. I understand why the
very-short-term approach of “just extend the darned time slice and be
done” is conducive to getting things done. I’d rather ask ourselves -
why do we have all issues that consume multiple days and what can we
do to improve that. Because I am convinced that it surely isn’t
enjoyable to always budget for multiple days when something comes up
to debug, even if it is a race condition (as Atin mentions in his
response).




-- 
sankarshan mukhopadhyay

___
Gluster-infra mailing list
Gluster-infra@gluster.org
http://lists.gluster.org/mailman/listinfo/gluster-infra

Re: [Gluster-infra] [Gluster-devel] Announcing Softserve- serve yourself a VM

[Nigel Babu]

Please file an issue for this:
https://github.com/gluster/softserve/issues/new

On Tue, Mar 20, 2018 at 1:57 PM, Sanju Rakonde  wrote:

> 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-de...@gluster.org
>> http://lists.gluster.org/mailman/listinfo/gluster-devel
>>
>
>


-- 
nigelb
___
Gluster-infra mailing list
Gluster-infra@gluster.org
http://lists.gluster.org/mailman/listinfo/gluster-infra

Re: [Gluster-infra] [Gluster-devel] Announcing Softserve- serve yourself a VM

[Atin Mukherjee]

On Wed, Feb 28, 2018 at 6: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.
>
>
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-de...@gluster.org
> http://lists.gluster.org/mailman/listinfo/gluster-devel
>
___
Gluster-infra mailing list
Gluster-infra@gluster.org
http://lists.gluster.org/mailman/listinfo/gluster-infra