Package Details: opennebula 5.10.3-1

Git Clone URL: (read-only, click to copy)
Package Base: opennebula
Description: Virtual management infrastructure as a service (IaaS) toolkit for cloud computing (NOTE: Read the PKGBUILD!)
Upstream URL:
Keywords: cloud opennebula
Licenses: Apache
Conflicts: opennebula-unstable
Submitter: manzo
Maintainer: sulaweyo
Last Packager: sulaweyo
Votes: 5
Popularity: 0.000000
First Submitted: 2016-02-17 21:18
Last Updated: 2020-03-21 13:33

Required by (0)

Sources (13)

Latest Comments

« First ‹ Previous 1 2 3

manzo commented on 2016-05-25 16:19

Thanks for the suggestions sulaweyo. I've updated the package following them.

sulaweyo commented on 2016-05-15 11:15

I'd suggest to extend the 2 systemd units with dependencies and permission fixes to the run and lock directories. At least i ran into errors there:

Addition to both [Unit] sections:

Addition to both [Service] sections
ExecStartPre=/usr/bin/mkdir -p /var/run/one
ExecStartPre=/usr/bin/mkdir -p /var/lock/one
ExecStartPre=/usr/bin/chown -R oneadmin:cloud /var/run/one
ExecStartPre=/usr/bin/chown -R oneadmin:cloud /var/lock/one

manzo commented on 2016-04-22 18:38

Thanks for the input mhubig!

Can you provide more info on the conflicts you faced? I've tried on a fresh install on my spare computer and it worked.

About the outdated versions, I've noticed that as well and I'll try to annoy the other submitters to update them.

Finally, I do like to install all gems through rubygems. Unfortunately that doesn't look like a packaging good practice from a sysadmin perspective because (I was told by a Debian developer this) it makes system updates unreliable without the security and compatibility assurances good packages have. And I tend to agree with that in this case.

If I could give the same approach as the gitlab does vendorizing all the gems I'd go with that. Unfortunately this relies on bundler and adding a new dependency seems worse.

Do you see any other options? Thanks again!

mhubig commented on 2016-04-21 16:34

I think this AUR package would be much easier to maintain if you leave all the ruby gems out of the dependencies and add a note on how to install them later on.

I tried to use the AUR packages for the gems but they are outdated and the versions don't match each other. I ended up removing ruby-builder, ruby-nokogiri, ruby-opennebula and ruby-sinatra from the PKGBUILD dependencies and installing them via the '/usr/share/one/install_gems' script.

manzo commented on 2016-02-27 15:59

You're correct. Just pushed a new version making the dependency on ruby-nokogiri explicit.

But I'm confused as you've said you have ruby-nokogiri installed, correct? Are you using RVM or RBENV? If so, make sure you are using the system ruby.

Thanks for the report.

pinkflozd commented on 2016-02-26 19:35

getting a error about missing nokogiri when starting sunstone (ruby-nokogiro is installed)

/usr/lib/one/ruby/opennebula/xml_utils.rb:144:in `<module:OpenNebula>': nokogiri gem not installed. (RuntimeError)
from /usr/lib/one/ruby/opennebula/xml_utils.rb:19:in `<top (required)>'
from /usr/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in `require'
from /usr/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in `require'
from /usr/lib/one/ruby/opennebula.rb:27:in `<top (required)>'
from /usr/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in `require'
from /usr/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in `require'
from /usr/lib/one/ruby/cloud/CloudServer.rb:17:in `<top (required)>'
from /usr/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in `require'
from /usr/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in `require'
from /usr/lib/one/sunstone/models/SunstoneServer.rb:17:in `<top (required)>'
from /usr/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in `require'
from /usr/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in `require'
from /usr/lib/one/sunstone/sunstone-server.rb:65:in `<main>'