Re: [one-users] Windows* contextualization scripts?
Hello, I also think that dhcp is the way to go with windows guests or images that can not me modified to use contextualization data provided by ONE. We have not included dhcp configuration scripts as we don't want to marry with any specific external server and I suppose most of the datacenters already have dhcp servers in place. Fortunately dhcp configuration can be easily generated as last 4 bytes of mac addresses generated for VMs match the IP assigned by OpenNebula. The howto on how to configure a dhcp server [1] explains how to do this (I have to check why is not linked in the current documentation version). This configuration generation can be added as a hook script so the needed configuration for a VM is added automatically to the dhcp configuration file on VM creation. I have been tinkering with this idea but put it on hold as I think that it can cause some problems on a production environment with several VM's starting at the same time, the scripts will be rewriting conf files and restarting dhcp server. I think it is better to do this things for a whole VNET on its creation. I hope this helps [1] http://opennebula.org/documentation:archives:rel1.2:howto_net On Mon, Dec 27, 2010 at 7:16 PM, Stefan P deubeul...@gmail.com wrote: On Mon, Dec 27, 2010 at 6:20 PM, sa...@eng.it wrote: SP == Stefan P deubeul...@gmail.com writes: SP Configuring the network on one given windows version is, I'd bet, SP as easy as it is to do on debian. So now you have two SP scripts... What about other distros, windows versions... OS X ? Not this difficult to solve. Mac OS X is a BSD Unix, you have to find where to hook your script. Ok, sure ! I'm not at all arguing that each case is complex :p I'm saying the complexity comes from having many cases to handle, and from the need to customize each different vm image, in the specific case where you have lots of them. Certainly from the open nebula project point of view, providing and documenting known to work contextualization scripts for all major guest platforms would be a fair amount of work. I'm not sure hacking together a dhcp server to onevnet would be much more work - and then we could tell users: use dhcp, unless you have specific needs, in which case use contextualization on your own. Stefan ___ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org -- Javier Fontan, Grid Virtualization Technology Engineer/Researcher DSA Research Group: http://dsa-research.org Globus GridWay Metascheduler: http://www.GridWay.org OpenNebula Virtual Infrastructure Engine: http://www.OpenNebula.org ___ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
Re: [one-users] Windows* contextualization scripts?
On Wed, Dec 22, 2010 at 5:50 AM, Giovanni Toraldo g...@libersoft.it wrote: Hi, searching on mailing list archives and googlin' around, I found many people talking about using bat/vbs/wmi scripts for configuring Windows guests, but I haven't actually found anything. Someone know if there is something available everywhere? Thanks. -- Giovanni Toraldo http://www.libersoft.it/ ___ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org I am also looking for this information. Is anyone running Windows servers virtualized in OpenNebula? It seems that OpenNebula, along with Eucalyptus and OpenStack, is targeted at Linux guests. I am looking for a cloud infrastructure solution to host both Linux and Windows guests in a production environment. Can anyone share their experience virtualizing Windows guests in OpenNebula? Regards, John Murphy ___ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
Re: [one-users] Windows* contextualization scripts?
Il 27/12/2010 14:44, John Murphy ha scritto: I am also looking for this information. Is anyone running Windows servers virtualized in OpenNebula? It seems that OpenNebula, along with Eucalyptus and OpenStack, is targeted at Linux guests. I am looking for a cloud infrastructure solution to host both Linux and Windows guests in a production environment. Can anyone share their experience virtualizing Windows guests in OpenNebula? I am currently virtualizing Windows guests, using 1 ip fixed networks and manually configuring network (that's creepy, I know). I think that a clean solution couldn't exists with the actual architectural problems on windows systems, not only related to how to configure your network card, but even how to deal with product activation that get triggered every time you start a new machine. Keep windows if you need it, throw it away when you can. Bye. -- Giovanni Toraldo http://www.libersoft.it/ signature.asc Description: OpenPGP digital signature ___ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
Re: [one-users] Windows* contextualization scripts?
On Mon, Dec 27, 2010 at 4:32 PM, Giovanni Toraldo g...@libersoft.it wrote: I am currently virtualizing Windows guests, using 1 ip fixed networks and manually configuring network (that's creepy, I know). I'm also wondering about contextualization when multiple platforms, guest OSes and distributions are concerned, and I keep coming back at the conclusion that a properly managed and secured DHCP setup is the way to go. I'd be curious to get some feedback from the list on that subject ! ___ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
Re: [one-users] Windows* contextualization scripts?
GT == Giovanni Toraldo g...@libersoft.it writes:
GT I think that a clean solution couldn't exists with the actual
GT architectural problems on windows systems, not only related to how
GT to configure your network card, but even how to deal with product
GT activation that get triggered every time you start a new machine.
AFAIK the latest version of Windows (startin from Vista) should allow
the setting of the IP from a script.
According to the person who said this the recipe should require:
- to create a service launced at bootstrap
- within this servive parse config.sh. Maybe the service could use
cygwin, solving a lot of problems
- the service should configure the network.
It's not easy and not a here is the solution to your problem but is
a way to solve the problem that should work.
--
ing. Gian Uberto Lauri
Ricercatore / Reasearcher
Divisione Ricerca ed Innovazione / Research Innovation Division
gianuberto.la...@eng.it
Engineering Ingegneria Informatica spa
Corso Stati Uniti 23/C, 35127 Padova (PD)
Tel. +39-049.8283.538 | main(){printf(unix[\021%six\012\0],
Fax +39-049.8283.569 |(unix)[have]+fun-0x60);}
Skype: gian.uberto.lauri | David Korn, ATT Bell Labs
http://www.eng.it | ioccc best One Liner, 1987
___
Users mailing list
Users@lists.opennebula.org
http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
Re: [one-users] Windows* contextualization scripts?
SP == Stefan P deubeul...@gmail.com writes:
SP I'm also wondering about contextualization when multiple
SP platforms, guest OSes and distributions are concerned, and I keep
SP coming back at the conclusion that a properly managed and secured
SP DHCP setup is the way to go.
Not really. Writing a script for Debian was really simple. The (not)
hard (as it seems) thing was to tell udev use eth0 no matter what
you may suppose about hardware changes :)
DHCP forces you to bind an IP to a MAC to be sure that the machine
gets that IP each time it boots. This can be or not an acceptable
solution depending on what it's needed.
--
ing. Gian Uberto Lauri
Ricercatore / Reasearcher
Divisione Ricerca ed Innovazione / Research Innovation Division
gianuberto.la...@eng.it
Engineering Ingegneria Informatica spa
Corso Stati Uniti 23/C, 35127 Padova (PD)
Tel. +39-049.8283.538 | main(){printf(unix[\021%six\012\0],
Fax +39-049.8283.569 |(unix)[have]+fun-0x60);}
Skype: gian.uberto.lauri | David Korn, ATT Bell Labs
http://www.eng.it | ioccc best One Liner, 1987
___
Users mailing list
Users@lists.opennebula.org
http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
Re: [one-users] Windows* contextualization scripts?
Il 27/12/2010 16:58, sa...@eng.it ha scritto: AFAIK the latest version of Windows (startin from Vista) should allow the setting of the IP from a script. http://www.tomstricks.com/how-to-create-a-batch-file-for-changing-network-settings-in-windows-vista/ Probably a vbscript or powershell could suffice to implement the vmcontext bash script used on GNU/Linux guests. -- Giovanni Toraldo http://www.libersoft.it/ signature.asc Description: OpenPGP digital signature ___ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
Re: [one-users] Windows* contextualization scripts?
On Mon, Dec 27, 2010 at 5:03 PM, sa...@eng.it wrote: SP == Stefan P deubeul...@gmail.com writes: SP I'm also wondering about contextualization when multiple SP platforms, guest OSes and distributions are concerned, and I keep SP coming back at the conclusion that a properly managed and secured SP DHCP setup is the way to go. Not really. Writing a script for Debian was really simple. The (not) hard (as it seems) thing was to tell udev use eth0 no matter what you may suppose about hardware changes :) Exactly ! When you have a few guest images, or only controlled ones, it's all nice and easy. Although as you mention, you can get into os-specific things pretty quickly. Configuring the network on one given windows version is, I'd bet, as easy as it is to do on debian. So now you have two scripts... What about other distros, windows versions... OS X ? My point being, if you're building a cloud that aims to support arbitrary OS images (maybe made by users), or a large combination of OS versions and distributions, then DHCP is probably the only sane solution. DHCP forces you to bind an IP to a MAC to be sure that the machine gets that IP each time it boots. This can be or not an acceptable solution depending on what it's needed. Mhh, yep, I guess what I have in mind is DHCP the protocol, and DHCP the client that's already bundled in all operating systems, and not really any particular or current DHCP servers; they are indeed probably not fine tuned, in terms of administration scenarios, to our cloudish needs. For instance, open nebula could provide a minimal, scriptable dhcp server integrated to onevnet (based on http://pydhcplib.tuxfamily.org/pmwiki/ ?). Then users would focus on scripting there, rather than in guest images, at least for ip/network/gateway/resolver configuration. Stefan ___ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
Re: [one-users] Windows* contextualization scripts?
SP == Stefan P deubeul...@gmail.com writes:
SP Configuring the network on one given windows version is, I'd bet,
SP as easy as it is to do on debian. So now you have two
SP scripts... What about other distros, windows versions... OS X ?
Not this difficult to solve. Mac OS X is a BSD Unix, you have to find
where to hook your script.
Linux distributions use a handful of packeting system and system
configuration script since most of them take them from an original
distribution (for the later I count slacky, suse, rh and Debian).
SP My point being, if you're building a cloud that aims to support
SP arbitrary OS images (maybe made by users), or a large combination
SP of OS versions and distributions, then DHCP is probably the only
SP sane solution.
It depends on users needs. Are you sure that DHCP can easily and
sanely support several virtual networks where hosts must act as they
have a fixed IP ?
--
ing. Gian Uberto Lauri
Ricercatore / Reasearcher
Divisione Ricerca ed Innovazione / Research Innovation Division
gianuberto.la...@eng.it
Engineering Ingegneria Informatica spa
Corso Stati Uniti 23/C, 35127 Padova (PD)
Tel. +39-049.8283.538 | main(){printf(unix[\021%six\012\0],
Fax +39-049.8283.569 |(unix)[have]+fun-0x60);}
Skype: gian.uberto.lauri | David Korn, ATT Bell Labs
http://www.eng.it | ioccc best One Liner, 1987
___
Users mailing list
Users@lists.opennebula.org
http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
Re: [one-users] Windows* contextualization scripts?
On Mon, Dec 27, 2010 at 6:20 PM, sa...@eng.it wrote: SP == Stefan P deubeul...@gmail.com writes: SP Configuring the network on one given windows version is, I'd bet, SP as easy as it is to do on debian. So now you have two SP scripts... What about other distros, windows versions... OS X ? Not this difficult to solve. Mac OS X is a BSD Unix, you have to find where to hook your script. Ok, sure ! I'm not at all arguing that each case is complex :p I'm saying the complexity comes from having many cases to handle, and from the need to customize each different vm image, in the specific case where you have lots of them. Certainly from the open nebula project point of view, providing and documenting known to work contextualization scripts for all major guest platforms would be a fair amount of work. I'm not sure hacking together a dhcp server to onevnet would be much more work - and then we could tell users: use dhcp, unless you have specific needs, in which case use contextualization on your own. Stefan ___ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
