On 1/31/12 8:46 AM, Aaron Coburn wrote:
Sean,
You can use the vsphere api to get the file names if you really need
them.
This is true, and that may very well be the better approach. I am not
entirely happy with the method I described earlier, which relies on my
own observation of an
You can use the vsphere api to get the file names if you really need them. Why
does vcl write its own vmx instead of using the apis? vSphere expects programs
to use the apis, not to hand craft files.When I wrote Duke's provisioning
module to work with vCenter I found it much easier to use
Thanks!
On 8/4/10 12:48 PM, Aaron Peeler wrote:
Hello Sean,
This might have been a left-over from using machine states. Created the
jira issue for it.
https://issues.apache.org/jira/browse/VCL-364
Aaron
On 7/22/10 1:59 PM, Sean Dilda wrote:
I recently noticed that when you set
I recently noticed that when you set a computer into maintenance mode
that it sets the vmhostid to NULL. Does anyone know what the reasoning
for this is? This happens in the process function in new.pm
During some testing I set a few computers to maintenance mode, then when
I set them
On 5/10/10 4:53 PM, Tim Cary wrote:
Hello,
I am wondering if anyone has had experience with VCL running across
VMWare Clusters? By clusters I mean a set of physical hosts running
VMWare ESX with common storage between them.
Issues that I can think of would be:
- Can VCL understand if
You should verify the PATH environment variable that's set when vcld is
started. You may have to manually set it in the init script if your
system is stripping it down.
On 3/15/10 3:15 PM, Mark Gardner wrote:
For some reason, I am getting an error message that grep cannot be found
while
Aaron Peeler wrote:
makesshgkh is part of xcat1.3(which is EOL'd) and is used to collect the
ssh host keys after the install.
xCAT2.X does something different to collect the ssh host keys, so
eventually makesshgkh and the original xCAT.pm module will not be needed.
Ok, that makes sense.
Andy Kurth wrote:
I would consider a node loaded from a provisioning module's standpoint as the
point when the bits are on the node's disk and it has been powered on. After
this point, the OS module is responsible. xCAT detecting the boot state would
be equivalent to successfully turning on
