On Wed, Feb 6, 2013 at 7:49 AM, Nux! wrote:
> What's the "recommended" way of backing KVM guests in CS4? I see even LVM or
> CLVM is supported from what I'm reading, but I didn't find a "definitive"
> list.
I'm not sure anyone could give you a "recommended" option for primary
storage without kno
Hi Jake,
The new feature request process is documented here:
https://cwiki.apache.org/confluence/display/CLOUDSTACK/Adding+new+features+and+design+documents
If you feel like championing the feature, the first step would be to
email the dev list to get feedback from the other developers.
Let us k
Hi Jeff,
CloudStack currently does all in-guest network configuration via DHCP
and, as far as I can tell, no DHCP options are being set that would
push static routes.
If you have a VM with multiple NICs, the DHCP server will hand out IPs
to each of them, while trying not to confuse the guest abou
Hi Fabrice,
I'm not aware of any such feature, but there have been other
situations where people have needed ways to customize the virtual
hardware or VMX file gat CloudStack creates, so it might be an
improvement worth exploring.
In your case, I'm curious why you would need/prefer LSI Logic SAS
Jim,
Kristoffer is correct that you should look into Sysprep. Specifically,
Sysprep has an option to automatically generate a computer name when the
clone first boots.
If you're looking for a fancier solution, it should be possible to have
Sysprep launch a script on first boot which would query t
I'm not sure if this would work, but you could try creating the VMs and
networks as part of a project, and then deleting the project.
On Wed, Jan 16, 2013 at 5:16 PM, Ioan Eugen Stan wrote:
> Hello Nick,
>
> Thanks for the quick answer. I was hoping for a miracle :) but I guess
> there is no for
Asmita,
You might want to look at the following Python sample for how to generate
the signature:
https://github.com/kdamage/IndividualCode/blob/master/CloudStack%20API%20Signing%20Class/SignedAPICall.py
I noticed in your openssl command, you only used the "keypair=..." part of
the query string. I
Greetings,
Based on a quick review of the code, there is no way to force CloudStack to
assign MAC addresses in the range which VMware considers valid/expected.
If you wanted to suppress the warning for specific VMs, you could try
adding a line to the VMX files:
ethernet0.checkMACAddress = "false
