Hi,
I have some problems using ebtables-kvm hooks script.
I use the one saved in the GIT (the one from the documentation seems
deprecated).
get_interfaces return this hash table:
{br-vnets=[vnet1, vnet2, vnet3, vnet4], br-test=[vnet0],
virbr0=[nil]}
therefor the following 'if' statement
Hi Tino
I have exactly the same issue as Tim
I have done the proposed in :
http://www.mail-archive.com/users@lists.opennebula.org/msg02723.html
Then I have changed this:
change line 116 of
$ONE_LOCATION/lib/ruby/OpenNebula/XMLUtils.rb to:
self.each(filter.to_s) { |e| ids_array
Hi,
Thanks a lot for the response.
Here is the output of, onevm show after onevm saveas
VIRTUAL MACHINE 109 INFORMATION
ID : 109
NAME : test2
STATE : ACTIVE
LCM_STATE : RUNNING
START TIME : 04/28 14:06:06
END TIME : -
DEPLOY ID: : one-109
hiI have an error to configure /var/log/one/sunstone.logThe output file
is:./sunstone-server: riga 70: rackup: comando non trovato
oneadmin@marco-laptop:/usr/bin$ ./sunstone-server startsunstone-server started
I can not connect with server localhost:4567Oops! Google Chrome could not
connect to
OpenNebula just manages the images. Using them in the VMs has more to do
with correct the template parameters and the hypervisor support for the
image type.
It would be good if you could attach your templates (image, VM) and the
VM log to see what could be the problem.
Hector
El 28/04/11 11:07,
Please install the rack gem (sudo gem install rack typically). You
will also need the gems json, sinatra and thin.
Hector
El 28/04/11 11:32, Marco MIRABILE escribió:
hi
I have an error to configure |/var/log/one/sunstone.log|
The output file is:
./sunstone-server: riga 70: rackup: comando
Hi,
You should check the FAQ in the OpenNebula website:
http://www.opennebula.org/documentation:community:faq
There is a compatibility problem with rack and sinatra
Regards
On Thu, Apr 28, 2011 at 11:04 AM, Héctor Sanjuán hsanj...@opennebula.orgwrote:
Is it the same error in sunstone.log?
Hi,
This is a bug in the code when not using the NOKOGIRI gem. As a
workaround, please try installing that gem.
Meanwhile, I've opened a ticket [1] to keep track of the solution.
Regards,
-Tino
[1] http://dev.opennebula.org/issues/597
--
Constantino Vázquez Blanco, MSc
OpenNebula Major
Hi Tino,
I still have some doubts. If I understand well, the driver u mention
allows OpenNebula deal with VMWare ESXi, but I don't know what I
have to install/configure at the compute node using ESXI. The
configuration of my cluster is as follows: I have a machine
Hi Cesar,
You don't need to install any additional hardware in the ESX node, all the
configuration must be done in the front-end.
Regards,
-Tino
--
Constantino Vázquez Blanco | dsa-research.org/tinova
Virtualization Technology Engineer / Researcher
OpenNebula Toolkit | opennebula.org
On Thu,
Cesar,
you do not need to install anything in the ESXI compute node, but
configuring the shared filesystem.
I think ESXI is able to configure a datastore which is located in a
nfs shared folder. I that case you won't even need to connect to the
shared
Hi,
Check the message:
Port busy, please shutdown the service or move econe server port.
Which port did you change ? The 8880 ?
Yours,
Steffen
--
IPB HalleAG Massenspektrometrie Bioinformatik
Dr. Steffen Neumann http://www.IPB-Halle.DE
Weinberg 3
Dear Sebastian,
Are you referring to the boto library as a client for OpenNebula EC2
implementation? If so, no directly, but I believe the elasticfox
extension (which we've tried) is based on such library.
Regards,
-Tino
--
Constantino Vázquez Blanco | dsa-research.org/tinova
Virtualization
Hi,
Yes I am referring to:
http://code.google.com/p/boto/
The ecua2ools are based on it, so it should work. But I was wondering
if someone ever wrote a Python script using boto to start instances
with opennebula 2.2
-sebastien
On Thu, Apr 28, 2011 at 11:15 AM, Tino Vazquez tinov...@gmail.com
Hi,
After recently updating the OpenNebula package in the openSUSE Build
Service for openSUSE I am now trying to improve the package a bit and
make things a bit more user friendly. Also I'd eventually create a
mostly pre-configured image, but one thing at a time.
The setup-guide
Hi there,
The RuntimeException looks better to me.
The only thing I'm not sure about is why you deleted the 'throws'
declaration from Client.java.
Doing that, a client application is not forced to catch the connection
problem.
I think it's better to force the coder to be aware of this kind of
Hi,
I tried it once, but had no luck in configuring it right.
But if you try to control OpenNebula via python in general, I can
recommend the xmlrpc interface. It's pretty easy to set up and works
fine for me.
http://opennebula.org/documentation:rel2.2:api
Greetings,
Stephan
Quoting
We're looking at using OpenNebula to support courses in our CS area.
This will ultimately require some form of group-based authorization,
so that we can restrict control over vm instances to specific groups
of students, and so that we can restrict access to disk images to
particular classes.
Actually I just got it to work with ONE 2.2 and latest boto on Ubuntu.
In your $HOME put a .boto file with your opennebula credentials:
sebgoa@belmiro:~$ cat .boto
[Credentials]
aws_access_key_id = opennebula userid
aws_secret_access_key = hash of user passwd
[Boto]
debug = 0
num_retries = 2
Hello,
we have setup up a ranged virtual network for our ONE-2.2 VMs but the gateway
IP address keeps being assigned to VMs.
The network range to assign is a 4x class C network:
X.X.16.0/22
with gateway X.X.16.1, i.e. the VMs can get any IP in the range
X.X.16.2 -- X.X.19.254
We
we have setup up a ranged virtual network for our ONE-2.2 VMs but the gateway
IP address keeps being assigned to VMs.
Ahmad,
I just asked a very similar question on the list. I agree that the
existing documentation isn't particularly clear.
The only response I received was a suggestion to
Hi,
Please also note that is very common to put the gateway in a VM also as part
of the network. You can request an specific IP for the gateway VM in the
template (NIC=[ NETWORK_ID = 3, IP = 192.168.0.1])
Probably, we should make more clear the documentation to remark that you are
defining the
Thank you for looking over my problem!
Could you tell us what was the action that was being performed to the
VM when it failed? To me it looks like stop but I am not sure about
it.
onevm stop VM_ID
It would be also helpful to take a peek into $ONE_LOCATION/var/config
Hi,
144 is exactly the number of cores on your physical nodes.
The scheduler uses the available CPUs (cf. onehost list)
and whatever CPU resources are defined in your template.
You could reduce CPU to X1 to allow overcomitting
of physical CPUs.
Yours,
Steffen
24 matches
Mail list logo