Hi
When I try to create a VM, it gives an error: User is not authorised to CREATE
in VM POOL. How can I set authorizations to the Open Nebula users to
create/shutdown/Delete the objects?
Thanks in advance
(Bharat)
Hi,
Is it possible to create a hook on SAVE_SUSPEND state, The documentation
only specifies create, running, stop, shutdown, done and failed states
under possible values of on ???
http://opennebula.org/documentation:rel3.0:hooks
Thanks,
Prakhar
___
Hi,
You should check oned.log. The virtual machine you are trying to create may
be using some resources like (network, images, hosts etc that you might not
be authorised to use. Use ACL to configure the user for different virtual
resources)
http://opennebula.org/documentation:rel3.0:hooks
Hi
br0 must be a bridge defined in the physical host where you are going to
deploy the VM. It seems that it doesnt exist...
Hector
El 04/10/11 17:12, Bruno Ferreira escribió:
Hector Thank you for reply.
I gave permission to the DIR in var VM_DIR.
Now im getting other error.
I take a
YES!!!
Its running now... =)
I just create the int *br0* on the worker node and try to run again...
Now i have a new issue, i cant acesses the VM... I discover that i already
have a bridge working on my workers nodes, but with a different name (*
virbr0*).
Probably the opennebula express install
Hi,
that User [-1] is a bit weird to me. Is argohost a valid ONE user?
is it in the oneadmin group?
Hector
El 30/09/11 19:21, Rubens Pinheiro escribió:
Hello,
I'm learning about opennebula and I'm following this tutorial:
http://www.opennebula.org/documentation:archives:rel2.0:vmg
I've
Hi, if on OpenNebula 3 you can try the onevm rmlease command:
http://opennebula.org/documentation:rel3.0:vgg#adding_and_removing_leases
Hector
El 28/09/11 09:49, Ruben Diez escribió:
Hi:
We had defined a OpenNebula network of ranged type
[.]
NETWORK_ADDRESS=xx.xx.xx.128
You cant simply use your browser to access occi server. I believe by
default occi-server uses basic http authentication so you would need to
find the way to custom your http requests from your browser so that the
right auth header is included, just like the client tools do
(occi-compute