Hi Carlos,
Thank you for your feedback. I will do it accordingly.
--
Regards,
Anandharaj
Server Storage Support Team
MIMOS Berhad
From: Carlos Martín Sánchez [mailto:cmar...@opennebula.org]
Sent: Tuesday, February 17, 2015 6:28 PM
To: Anandharaj Subramaniam
Cc: users@lists.opennebula.org
Jaime Melis jme...@opennebula.org writes:
Hmm, writing the question seems to gives my answer, it looks like the
cherry-picking of master commits on the one-version branches are the
reasons of the merge conflicts.
Yes... that's the way we usually do it: by cherry picking the commits.
Ok,
We should probably take out the code that generates the gateway as it only
gives problems:
https://github.com/OpenNebula/addon-context-linux/blob/master/base_rpm/etc/one-context.d/00-network#L68-L73
Concerning the GATEWAY_INTERFACE, this variable contains a number or the
ETHnum that appears in
Compile our own OpenNebula will break the package system maintenance.
You can forget use yum or any other package management system. You can
forget about the updating scripts associate to the package for
automatically migrate and adapt the database schemes to updated versions
Compile our
Hi Steve,
Normally If I have to use NFS based shared hosting then I mounted
/var/lib/one directly on all nodes instead of mounting datastores
seperately.
Else recently I configured multiple OpenNebula Nodes with local
/var/lib/one directory added one Node just for backup and sync only
Hi,
Should I rebase[2] all my branches on master directly and then follow
the OpenNebula releases or is there a path to merge master and one-4.10?
Hmm, writing the question seems to gives my answer, it looks like the
cherry-picking of master commits on the one-version branches are the
Hi Carlos,
Thank you very much for letting us know, we need to think it deeply :)
Just one question, which are the pros and cons of compiling oned? It is
a serious thing for us since the infrastructure is on production and I
am not sure if it will break future updates trough yum/rpm and also,
Hi,
That IP looks good (202.45.142.114). It might be a bug that can be affected
by the ruby version.
Since this is a 4.2 version and the leases were completely redone for new
versions, maybe the best thing to do is comment out the whole vnet section
in fsck.rb, lines 920-1066.
Regards
--
Carlos
Hi,
If you mean the OpenNebula VM name, it is automatically set to
vmtemplate_name-vm_id. It can be changed when the template is
instantiated in the Sunstone wizard, or with the --name option in the cli.
Regards.
--
Carlos Martín, MSc
Project Engineer
OpenNebula - Flexible Enterprise Cloud Made
Hi,
- I can create VMs successfully but very very slow performance.
Are you using virtio drivers? I also recommend playing with the 'cache'
parameter. How well does it perform compared with I/O operations in the
hypervisor? Is the storage the problem here or the Virtualization layer?
- Also
Hi,
you are right, we don't have this. I just created this in order to document
http://dev.opennebula.org/issues/3602
Answering your specific question:
What is not clear is about the tm driver. An ssh connection is open from
oned admin server to the hypervisors, to run the clone/cp/etc
On 2015-02-17 02:58, Jaime Melis wrote:
Hi,
- I can create VMs successfully but very very slow performance.
Are you using virtio drivers? I also recommend playing with the
'cache' parameter. How well does it perform compared with I/O
operations in the hypervisor? Is the storage the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Jamie and Daniel,
I perfectly understand the problems with Debian official packaging
guidelines.
I asked this, because at the moment I'm collaborating with Devuan, an
upcoming Debian fork which is aimed to not have systemd mandatory.
Could be
Jaime Melis jmelis@opennebula.systems writes:
Hi Alberto,
I can confirm what Daniel said. We have no current plans of updating the
offical Debian package of OpenNebula. Debian packaing guidelines are very
strict and as Daniel mentioned it's a very big job.
Daniel, I apologize, but somehow
Hello Alberto,
yes, of course. But due to resources we can only try and help out people
from the community like yourself or Daniel who want to collaborate in
creating these packages. We can assist and try to change this around in the
codebase to make things easier for package maintainers.
On
15 matches
Mail list logo
