I have a OpenNebula 2.0 installation that has been running for a
couple of years. It was running on Sci. Linux 5 and using the stock
ruby 1.8.5. As part of an attempted and failed Puppet install on this
machine, Ruby has now been upgraded to 1.8.7
but I have not yet restarted oned. During the install of opennebula 2.0
there were a number of manual gems installed of a version that matched
ruby 1.8.5.
This is my current "gem list".
[root@fcl002 log]# gem list
*** LOCAL GEMS ***
amazon-ec2 (0.9.15)
aws-s3 (0.6.2)
builder (2.1.2)
crack (0.1.7)
curb (0.7.8)
daemons (1.1.0)
eventmachine (0.12.10)
haml (3.0.18)
htmlentities (4.2.1)
macaddr (1.0.0)
mime-types (1.16)
mkrf (0.2.3)
nokogiri (1.4.3.1, 1.4.2)
rack (1.1.0)
rake (0.8.7)
RedCloth (4.2.3)
require (0.2.7)
rmagick (2.13.1)
sequel (3.15.0)
sinatra (1.0)
sqlite3-ruby (1.2.4)
thin (1.2.7)
uuid (2.3.1)
xml-simple (1.0.12)
xmlparser (0.6.81)
------------------------------------
Four questions:
1) Does oned 2.0 work with ruby 1.8.7 at all under any configuration?
2) If I restart oned 2.0 now with ruby 1.8.7 and the above collection
of gems, is it likely to start?
3) If not, are versions of gems that are compatible with ruby 1.8.7
and oned 2.0 still out there?
4) Am I best to try to roll back to ruby 1.8.5?
------------------------------------------------------------------
Steven C. Timm, Ph.D (630) 840-8525
t...@fnal.gov http://home.fnal.gov/~timm/
Fermilab Computing Division, Scientific Computing Facilities,
Grid Facilities Department, FermiGrid Services Group, Group Leader.
Lead of FermiCloud project.
_______________________________________________
Users mailing list
Users@lists.opennebula.org
http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
