Thank you very much.
Greetings,
El vie 16 dic 2011 18:37:55 CET, Daniel Molina escribió:
Hi Carlos,
2011/12/14 Carlos Fernández Iglesiascigles...@cesga.es:
Hello,
Is there a way to know the vmid oca.VmTemplate.instantiate(name='name')
is going to assign to the virtual machine?
In the
How do people manage NAT with nebula?
libvirt allows for per vm (per libvirt host) nat rule generation via
the (debian) hook /etc/libvirt/hooks/qemu
However, nebula provides primary key domain names (on the libvirt
host) rather than using the machine name (viz. one-47 vs. oneiric).
Hence, to
Does something like this already exist?
It looks like I can just use a remote vm hook and throw any details I
want for the NAT into the vm context and pass them to the hook
arguments. I'll prototype a simple version of this unless anyone has a
working solution or a better idea.
Hello Biro
On 15.12.2011 09:54, biro lehel wrote:
Hello Fabian. Thanks again for your reply. I really appreciate
you for taking the time.
You're welcome.
I read what you wrote a couple of times, and (I think) it
helped me to clarify some things. But still, I have a few
questions and issues
Hello guys.
I have one more problem here.
When I start a host, in sunstone server, I get a error.
On /var/log/one/oned.conf I see this:
Mon Dec 19 15:42:47 2011 [InM][I]: Monitoring host PacsOnCloud-FrontEnd (0)
Mon Dec 19 15:42:48 2011 [InM][I]: Command execution fail: 'if [ -x
Hi
About your approach for NAT'ing I think that it should work. In fact the
firewalling network driver uses the same strategy.
Given said that, I think that doing NAT at the physical host level is not a
good idea. We usually do not assign any public IP to the physical host and
just let it
Anyone?
On Mon, Dec 19, 2011 at 4:16 PM, matheus tor4 matheusi...@gmail.com wrote:
Hello guys.
I have one more problem here.
When I start a host, in sunstone server, I get a error.
On /var/log/one/oned.conf I see this:
Mon Dec 19 15:42:47 2011 [InM][I]: Monitoring host
Given said that, I think that doing NAT at the physical host level is not a
good idea. We usually do not assign any public IP to the physical host and
just let it bridged to the Internet NIC. Then you may define a VLAN, and
create a router VM with a NIC in that VLAN and other one in a Public
