Hi,
I was reading through Amazon EC2 prerequisites [1] which implies that
there can be only one set of AWS credentials per opennebula cloud. Is
that correct? This might not be a problem for a "private cloud" operated
by only one organisation / company. For a public cloud that want's to
leave room
Cool, very much appreciated :)
On Wed, Jan 29, 2014 at 7:00 AM, Tino Vazquez wrote:
> Hi Shankhadeep,
>
> We've evaluated the request and it looks like something that can make
> it for 4.6. I've opened a ticket to keep track [1].
>
> Regards,
>
> -Tino
>
> [1] http://dev.opennebula.org/issues/2
Hi
I've increased the priority for this. There are a couple of issues related
to this one (need to add hypervisor features to disks or nics). Probably we
will also go for http://dev.opennebula.org/issues/2531
There are some modifications to the drivers scheduled for 4.6. We'll try to
include thes
Hi Stefan
The IPv6 design in OpenNebula is basically designed to work with the
auto-configuration features of IPv6. An IPv6 capable host will always have
link-local addresses for all their interfaces. AFAIK you cannot disable
IPv6 stack per interface. So it really does not make sense to have one
i
Did so, same error. I cleared oned.log, ran "onehost sync", then "onehost
enable 8" (where the relevant server is ID 8). Console/log dumps follow
(apologies for length):
Console output:
-bash-4.1$ onehost sync
* Adding bigdata-corona.cticore.local to upgrade
[=
Hi Igor,
Awesome, thanks a lot for letting us know.
Best,
-Tino
--
OpenNebula - Flexible Enterprise Cloud Made Simple
--
Constantino Vázquez Blanco, PhD, MSc
Senior Infrastructure Architect at C12G Labs
www.c12g.com | @C12G | es.linkedin.com/in/tinova
--
Confidentiality Warning: The informati
Hi Tino,
Thanks, yes and sorry for delay.
I would like confirm for now that with this change it's works.
On Wed, Jan 29, 2014 at 7:38 PM, Tino Vazquez wrote:
> Hi Igor,
>
> I've opened a ticket [1] to keep track of the solution for next releases.
>
> Thanks for the feedback,
>
> -Tino
>
> [1]
Daniel Dehennin writes:
> Hello, again,
>
> The problem is libvirt specific:
[...]
> I can do an “md5sum /var/lib/one//datastores/0/1937/disk.0”.
As “oneadmin”, but libvirtd is running as root and new version make some
checks on the file, which failed because of a “root_squash”[1]
Changing th
Hello, again,
The problem is libvirt specific:
2014-01-29 15:10:52.458+: 6566: debug : virStorageFileGetMetadata:1114 :
path=/var/lib/one//datastores/0/1937/disk.0 format=9 uid=9869 gid=9869 probe=0
2014-01-29 15:10:52.458+: 6566: debug :
virStorageFileGetMetadataRecurse:1046 :
path=/v
Hello,
Using ONE 4.2 on Debian wheezy.
I just upgrade the qemu and libvirt to wheezy backports to solve bad
interaction between emulated card and guest kernel[1].
Now I can not boot VMs with PERSISTENT images.
I found a thread[2] on the mailing-list which looked like my problem, I
made the chec
For those of us who can't make it to Brussels, it would be interesting
to hear if there have been any changes in OpenNebula on CentOS that
have come about because of the new affiliation of Centos and Red Hat.
In particular, might there now be a path to get OpenNebula and some
of the other package
Repository packages for 4.4 are now in downloads.opennebula.org:
http://docs.opennebula.org/stable/design_and_installation/building_your_cloud/ignc.html
Read the upgrade guide and the compatibility guide before upgrading as
it needs manual intervention:
http://docs.opennebula.org/stable/release_
Hi,
I understood that Opennebula repositories would be maintained but it
does not seem so as
deb http://opennebula.org/repo/Ubuntu/12.04 stable opennebula
it not available.
Any idea why?
Thanks
Poul
2013-08-26 Javier Fontan
> Hi,
>
> We have recently created package repositories for CentOS
Dear all,
as I mentioned some days ago in the list, OpenNebula will participate in
the upcoming CentOS Dojo:
http://wiki.centos.org/Events/Dojo/Brussels2014
We have a bit more information with regard to this. The hackathon will
start shortly after lunch, at 14:15, and we will take upon us to impr
Hi Shankhadeep,
We've evaluated the request and it looks like something that can make
it for 4.6. I've opened a ticket to keep track [1].
Regards,
-Tino
[1] http://dev.opennebula.org/issues/2690
--
OpenNebula - Flexible Enterprise Cloud Made Simple
--
Constantino Vázquez Blanco, PhD, MSc
Seni
Hi Igor,
I've opened a ticket [1] to keep track of the solution for next releases.
Thanks for the feedback,
-Tino
[1] http://dev.opennebula.org/issues/2689
--
OpenNebula - Flexible Enterprise Cloud Made Simple
--
Constantino Vázquez Blanco, PhD, MSc
Senior Infrastructure Architect at C12G Labs
Hi Dirk,
Thanks a lot for opening the issue. I wasn't aware of the NET_TX value
always being 0 at the table, could you please add that as a comment?
We'll tackle all of this together for next release.
Cheers,
-Tino
--
OpenNebula - Flexible Enterprise Cloud Made Simple
--
Constantino Vázquez B
Hi Tino,
Ticket was logged: http://dev.opennebula.org/issues/2688
I also noticed that the value of the NET_TX element in the vm_monitoring table
is always zero bytes, which causes the value in the oneacct output to be zero
as well of course.
Looks like this is not related to the oneacct tool bu
Hi Dirk,
You are right, the NET values are not accumulated and their value are
the aggregation of the last 300 * 5 ms:
start_time = Time.now - 300 * 5
This is obviously wrong, please open a ticket and we will fix it for
the upcoming release.
Thanks a lot for the feedback!
-Tino
--
OpenN
Hi,
Looking at the vm_monitoring table in sqlite, it becomes clear that the NET_RX
and NET_TX values reported by oneacct are not accumulated.
Only the most recent value is shown for the filtered dataset.
Should I file a ticket describing my findings?
Regards,
Dirk
From: Daems Dirk
Sent: dinsdag
20 matches
Mail list logo