You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@vcl.apache.org by "Andy Kurth (JIRA)" <ji...@apache.org> on 2014/10/01 18:13:33 UTC

[jira] [Commented] (VCL-216) seat licensing - user group based SW licensing

    [ https://issues.apache.org/jira/browse/VCL-216?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14154999#comment-14154999 ] 

Andy Kurth commented on VCL-216:
--------------------------------

> +1 (untag from 2.4, lack of time)
> This would be a very useful feature but would only benefit a narrow
> range of images.

> seat licensing - user group based SW licensing
> ----------------------------------------------
>
>                 Key: VCL-216
>                 URL: https://issues.apache.org/jira/browse/VCL-216
>             Project: VCL
>          Issue Type: New Feature
>          Components: database, web gui (frontend)
>    Affects Versions: 2.2
>            Reporter: Aaron Peeler
>
> Allow one image to be used between different user groups, that have different concurrent license counts.
> ---
> Say there is image Timesink that has been created and has
> four concurrent licenses owned by group A.
> Now group B needs to use Timesink and buys two additional
> concurrent licenses.
> Currently it seems that we'd end up with two images of Timesink
> one available to group A with up to 4 concurrent instances and
> the other available to group B with up to 2 concurrent instances.
> It would be nice if the scheduler could understand that really
> they are the same image - so that if a copy of the image were
> loaded and someone from either group A or B made a reservation
> they could use the image and the scheduler would deduct
> the available number of concurrent uses from the correct pool.
> In practice Group B would need to know that Timesink image
> exists. VCL would need to provide a way for metadata to have
> more granular license information.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)