On 21 Jan 2015, at 11:13, Madko wrote:
Hi,
Had the same problem about conf files renamed to .rpmsave, and
therefor
opennebula was enable to start. Hopefully I saw this thread ;)
Is it possible to change this behavior and have .rpmnew instead, to
prevent
breaking everything after an
Past OpenNebula 4.x releases have been packaged as RPM's for CentOS
available in a yum repository with a baseurl of
'http://downloads.opennebula.org/repo/CentOS/6/stable/$basearch'
For some inscrutable reason, 4.8 RPMs are not there. Instead, the 4.8
docs on the website now direct us to a
On 25 Aug 2014, at 19:40, Damon (Albino Geek) wrote:
Hello,
I found that there is actually a prebuilt 4.8 context RPM in one of
their source trees (not GitHub).
That's not exactly helpful. The fact that there's an RPM in some unnamed
place built from who-knows-what revision is an
On 14 May 2014, at 9:33, Wilma Hermann wrote:
Hi,
I observed a problem with two OpenNebula setups, that I set up with
version
4.4 and which I upgraded to 4.6 some weeks ago: The VM monitoring
information does not seem to be deleted from the database (MySQL)
after
On 17 Sep 2013, at 10:03, Tino Vazquez wrote:
Hi Stefan,
comments inline,
On Tue, Sep 17, 2013 at 2:51 PM, Stefan Kooman ste...@bit.nl wrote:
Hi list,
I'm in the process of testing the OpenNebula oZones / VDC
functionality.
My setup is as follows:
- 2 hosts, with 1 one of them in a
