Feature #168

Contextualizing Windows VM

Added by Shi Jin over 2 years ago. Updated 3 months ago.

Status:Closed Start date:10/27/2009
Priority:Normal Due date:
Assignee:Carlos Martín % Done:

0%
Category:Ecosystem
Target version:-
Resolution:fixed Addon:
Story points-
Velocity based estimate-

Description

Let's have some discussion on how to contextualize Windows virtual machine on OpenNebula.
Basic idea:
1. Scripts available from an additional cdrom image
2. Run the scripts to set the hostname, IP address etc. The IP addresses are set statically following the OpenNebula mapping between the MAC and IP addresses.

Initial thoughts: this may be done in simple .bat files or more sophisticated VBScript/WSH/WMI. Due to the complexity of the problem, I don't think simple .bat can do it. I am still learning some windows scripting.

History

#1
Updated by Ruben S. Montero almost 2 years ago

  • Category set to Ecosystem
  • Assignee set to Carlos Martín
  • Target version set to Release 1.4.2

Moving this for the next maintenance release of the 1.4 series. Let see if we can come up with a howto for this...

#2
Updated by Gyula Csom over 1 year ago

Hi!

In our environment we have to support Windows VMs, too. So it's good to see that it will be built into the platform:) My question is the following. Will the Windows contextualization also provide context information? I ask it since the current behaviour is to produce a bash compatible shell script (context.sh), which is not really suitable for the Windows platform. What is your plan in this regard?

Cheers,
Gyula

#3
Updated by Ruben S. Montero over 1 year ago

Hi

The only part UNIX specific is the bash-like syntax for the context variables. However this is a very simple VARIABLE=VALUE syntax that can be easily parsed. So I'd say that from the OpenNebula side we are Windows ready. It would be great if we could have an equivalent for Windows of the init scripts that we have in the documentation, though.

Cheers

Ruben

#4
Updated by Gyula Csom over 1 year ago

Hi,
thanks for your reply!

So far we've learned a bit about WMI and it seemed promising, especially I liked the idea that we can use either Python or Ruby (though tested only the Python lib, yet). So far we've just tested programmatic RDP enablement (I might upload the spike code if interested). IP conf is the next in our target list, but we've not started with it, yet.

BTW: In our context the biggest issue is/was related to Windows licences. Eg. we do not provide licenses, it is the client who owns them. So we have to cook Windows images, but without specifying the license key. The builtin Windows sysprep tool seems promising, but again testing is just for tomorrow.

Cheers,
Gyula

#5
Updated by Robert Middleswarth 12 months ago

What is the status on this issue? It is listed as 1.4.2 yet 2.0.1 has been released.

Thanks
Robert

#6
Updated by Carlos Martín 12 months ago

The goal of this ticket was to discuss ways to implement the Unix procedure in Windows.
But the contextualization mechanism from the OpenNebula side is the same, the Windows host would have to open the CD and execute the scripts placed inside.

Regards,
Carlos.

#7
Updated by Ruben S. Montero 4 months ago

  • Target version deleted (Release 1.4.2)

#8
Updated by Carlos Martín 3 months ago

  • Status changed from New to Closed
  • Resolution set to fixed

This functionality has been contributed by the community:

http://blog.opennebula.org/?p=2160

Also available in: Atom PDF