Javier, I don't know why I didn't think of that. It worked! Thank you!
Greg Stabler Computer Science/MS Candidate School of Computing, McAdams 120 Clemson University, Clemson, SC 29634 gsta...@clemson.edu On Tue, Apr 10, 2012 at 6:49 AM, Javier Fontan <jfon...@opennebula.org>wrote: > Why don't you create a new set of drivers and use them for the nodes > that need to use the wrappers? > > For example, > > * Copy vmm kvm remotes to kvm_clemson > * Change the way of calling the commands > * Add the new drivers to oned.conf > * Add the nodes with kvm_clemson vmm drivers > > It is mostly the same as your proposed solution but in this case you > don't need to change OpenNebula code (aside from the driver itself) > > On Thu, Apr 5, 2012 at 7:06 PM, Greg Stabler <gsta...@clemson.edu> wrote: > > I'm trying to add our high-performance cluster to our OpenNebula 3.0 > system > > to run VMs on the cluster. Due to security requirements on the cluster, > we > > have had to write several wrapper scripts for things such as virsh, > > ovs-vsctl (for Open vSwitch), and brctl to ensure that someone does not > > misconfigure a cluster node and crash the system. > > > > Therefore, the current set of OpenNebula scripts in /var/remotes will not > > work on the cluster. The quick/dirty solution we came up with is to > create a > > second version of the remotes scripts that uses our wrappers and place > them > > in /var/remotes_cluster. Whenever the remote scripts are copied to or > > updated on a cluster node host, we would use this directory instead of > > /var/remotes. > > > > I've been looking through the source code and trying to figure out where > I > > might be able to add some code that checks to see if hostname belongs to > our > > cluster and then use the remotes_cluster directory, and if not, use the > > normal remotes directory. I thought that maybe in update_remotes() in > either > > one/libs/mads/one_im_exec.rb or in one/lib/ruby/CommandManager.rb would > > work, but I'm having trouble with that. I tried adding in a command to > the > > method to create a simple test directory just to see if that was the > correct > > place in the code, but I never see the directory created on my nodes. Any > > ideas? Again, we're using OpenNebula 3.0. > > > > Thank you, > > > > Greg Stabler > > Computer Science/MS Candidate > > School of Computing, McAdams 120 > > Clemson University, Clemson, SC 29634 > > gsta...@clemson.edu > > > > _______________________________________________ > > Users mailing list > > Users@lists.opennebula.org > > http://lists.opennebula.org/listinfo.cgi/users-opennebula.org > > > > > > -- > Javier Fontán Muiños > Project Engineer > OpenNebula - The Open Source Toolkit for Data Center Virtualization > www.OpenNebula.org | jfon...@opennebula.org | @OpenNebula >
_______________________________________________ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
