Open Stack

Site/Volume licensing works too.   The KMS is there to enable/enforce the local activiation/licensing.

The details of any licenses are also affected by the product sku’s that are involved.

Peter J. Pouliot, CISSP
Senior SDET, OpenStack

Microsoft
New England Research & Development Center
One Memorial Drive,Cambridge, MA 02142
PPOULIOT at microsoft.com<mailto:PPOULIOT at microsoft.com> | Tel: +1(857) 453 6436

From: Willard Dennis [mailto:willarddennis at live.com]
Sent: Wednesday, January 23, 2013 3:40 PM
To: Jay Pipes; openstack at lists.launchpad.net; Peter Pouliot
Subject: RE: [Openstack] Windows instance licensing in OpenStack

See http://www.microsoft.com/licensing/existing-customers/product-activation-faq.aspx

Looks like KMS would be the appropriate means; your MSFT reseller would sell you a KMS license key to use for the appropriate pool of server / app instances, then it is loaded into the KMS server, which then activates the instantiated systems. I checked with MSFT Licensing, the rep said there is no limit on number of uses of a KMS license key, just an aggregate activation threshold. See further http://technet.microsoft.com/en-us/windows/dd197314.aspx for more details.

We don’t use KMS here, so don’t know about the hairy details, sorry...

Best,
Will


From: Peter Pouliot
Sent: ‎January‎ ‎23‎, ‎2013 ‎12‎:‎04‎ ‎PM
To: Jay Pipes, openstack at lists.launchpad.net<mailto:openstack at lists.launchpad.net>
Subject: Re: [Openstack] Windows instance licensing in OpenStack

Ok,

I am no MS licensing expert, however.   Here is my understanding of it.

If you are using a windows vm on a hypervisor other than windows server with the Hyper-V role enabled you need to license per vm.



If you are using windows server with Hyper-V enable you can license at the hypervisor/server rather than at the vm level.

This does not include Hyper-V server, which only requires licensing of the windows guests.

p



Peter J. Pouliot, CISSP
Senior SDET, OpenStack

Microsoft
New England Research & Development Center
One Memorial Drive,Cambridge, MA 02142
PPOULIOT at microsoft.com<mailto:PPOULIOT at microsoft.com> | Tel: +1(857) 453 6436

-----Original Message-----
From: openstack-bounces+ppouliot=microsoft.com at lists.launchpad.net<mailto:openstack-bounces+ppouliot=microsoft.com at lists.launchpad.net> [mailto:openstack-bounces+ppouliot=microsoft.com at lists.launchpad.net] On Behalf Of Jay Pipes
Sent: Wednesday, January 23, 2013 9:31 AM
To: openstack at lists.launchpad.net<mailto:openstack at lists.launchpad.net>
Subject: Re: [Openstack] Windows instance licensing in OpenStack

On 01/23/2013 08:41 AM, Balamurugan V G wrote:
> Hi,
>
> I wonder how the Windows Licensing would work in OpenStack. Lets say I
> have a Windows Image which I have already activated. Now if I launch N
> instances of this image, what are the SO licensing implications? Will I
> have to license/re-activate on each of the instances after they boot up?

If you use XenServer or KVM, I believe so, yes. I've heard that if you
use ESXi you can get some sort of license for all Windows images on a
host. Not sure of the details of this, though, I've just heard it
through the IT grapevine...

Best,
-jay

p.s. If you find out any more solid info, please do post back :)

_______________________________________________
Mailing list: https://launchpad.net/~openstack
Post to     : openstack at lists.launchpad.net<mailto:openstack at lists.launchpad.net>
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

_______________________________________________
Mailing list: https://launchpad.net/~openstack
Post to     : openstack at lists.launchpad.net<mailto:openstack at lists.launchpad.net>
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack/attachments/20130123/1f3e9042/attachment.html>