 | | | New licensing policy | New licensing policy 2006-01-02 - By Terje Bless
Back
Ed Wilts <ewilts@(protected)> wrote:
>I believe the most important point is not being able to specify when the
>subscription starts but more being able to make sure all your
>subscriptions co-terminate on the same date so that your renewals become
>a lot easier.
This is certainly my biggest beef with RHN. My new systems come in staggered as
projects discover they need boxes to run their apps on; and while I can buffer
some of this by buying a larger bulk than I need immediately it's almost
impossible to get this to match well over time and really shouldn't be needed.
We've been pushing our reseller ??? for various reasons we can't buy direct ???
to
take over the management of this stuff; probably by charging us quarterly for
whatever number of systems we're currently running and some kind of markup.
But a better option would be for Red Hat to charge ??? and thus tie licensing
to ???
RHN and not individual systems, and eat the chump change involved in making
start and end dates fuzzy (or, more likely, bake it into the price). If I buy my
26th RHN subscription in December ??? thus exceeding the 25 subscriptions I had
???
that system should be counted (and charged) in the Q1 quarterly accounting for
the following year (or the following annual, depending on frequency).
An even easier implementation of this would be to expire subscriptions in bulk;
each quarter all the subscriptions that expired in the last three months come up
for renewal. That would mean ???free??? service for up to 3 months, but would
take a
*lot* of hassle out of dealing with renewals.
--
??I also need a longer attention sp- Ooh! Feet!?? ??? Loz Pycock
--
Taroon-list mailing list
Taroon-list@(protected)
https://www.redhat.com/mailman/listinfo/taroon-list
|
|
|