OpenNode > Installation and Configuration

OpenNode 6.0 b1 + OMS install failure

(1/3) > >>

Raboo:
Hi i'm trying to install OpenNode 6.0 beta1 and OMS to go with that.
So I installed OpenNode. Then I did a yum update, checked for any .rpmnew files and corrected what needed to be corrected and then reboot.
After reboot I downloaded OMS template and did a install.
A new vps got started and it has /etc/init.d/omsdrc
So I saw that :8080 was open and tried to visit http://oms:8080/ and got following error:

--- Code: ---403 Forbidden
--- End code ---
After that i tried to visit http://oms:8080/oms/ and got following error:

--- Code: ---500 Server Error

Traceback (most recent call last):
  File "/opt/oms/eggs/Twisted-11.1.0-py2.7-linux-x86_64.egg/twisted/internet/defer.py", line 545, in _runCallbacks
    current.result = callback(current.result, *args, **kw)
  File "/opt/oms/eggs/Twisted-11.1.0-py2.7-linux-x86_64.egg/twisted/internet/defer.py", line 1095, in gotResult
    _inlineCallbacks(r, g, deferred)
  File "/opt/oms/eggs/Twisted-11.1.0-py2.7-linux-x86_64.egg/twisted/internet/defer.py", line 1037, in _inlineCallbacks
    result = result.throwExceptionIntoGenerator(g)
  File "/opt/oms/eggs/Twisted-11.1.0-py2.7-linux-x86_64.egg/twisted/python/failure.py", line 382, in throwExceptionIntoGenerator
    return g.throw(self.type, self.value, self.tb)
--- <exception caught here> ---
  File "/opt/oms/eggs/opennode.oms.core-0.0_1052_g1d8f-py2.7.egg/opennode/oms/endpoint/httprest/root.py", line 130, in _render
    ret = yield self.handle_request(request)
  File "/opt/oms/eggs/Twisted-11.1.0-py2.7-linux-x86_64.egg/twisted/python/threadpool.py", line 207, in _worker
    result = context.call(ctx, function, *args, **kwargs)
  File "/opt/oms/eggs/Twisted-11.1.0-py2.7-linux-x86_64.egg/twisted/python/context.py", line 118, in callWithContext
    return self.currentContext().callWithContext(ctx, func, *args, **kw)
  File "/opt/oms/eggs/Twisted-11.1.0-py2.7-linux-x86_64.egg/twisted/python/context.py", line 81, in callWithContext
    return func(*args,**kw)
  File "/opt/oms/eggs/opennode.oms.core-0.0_1052_g1d8f-py2.7.egg/opennode/oms/zodb/db.py", line 167, in <lambda>
    lambda: run_in_tx(fun, *args, **kwargs))
  File "/opt/oms/eggs/opennode.oms.core-0.0_1052_g1d8f-py2.7.egg/opennode/oms/zodb/db.py", line 144, in run_in_tx
    result = fun(*args, **kwargs)
  File "/opt/oms/eggs/opennode.oms.core-0.0_1052_g1d8f-py2.7.egg/opennode/oms/endpoint/httprest/root.py", line 184, in handle_request
    objs, unresolved_path = traverse_path(oms_root, request.path[1:])
  File "/opt/oms/eggs/opennode.oms.core-0.0_1052_g1d8f-py2.7.egg/opennode/oms/model/traversal.py", line 54, in traverse_path
    next_obj = follow_symlinks(traverser.traverse(name))
  File "/opt/oms/eggs/opennode.oms.core-0.0_1052_g1d8f-py2.7.egg/opennode/oms/model/traverser.py", line 50, in traverse
    return super(RootTraverser, self).traverse(name)
  File "/opt/oms/eggs/opennode.oms.core-0.0_1052_g1d8f-py2.7.egg/opennode/oms/model/traverser.py", line 40, in traverse
    return self.context[name]
  File "/opt/oms/eggs/opennode.oms.core-0.0_1052_g1d8f-py2.7.egg/opennode/oms/model/model/base.py", line 113, in __getitem__
    return self.content().get(key)
  File "/opt/oms/eggs/opennode.oms.core-0.0_1052_g1d8f-py2.7.egg/opennode/oms/util.py", line 189, in wrapper
    raise e
ConfigParser.NoSectionError: No section: 'metrics'

--- End code ---

What am I doing wrong and how can I fix it?

ilja_l:
Hi,

it's our error, the OMS VM template, which got into the template store is a bit broken, I've removed that image for now.
We are currently preparing a fixed template for OMS, please, stay tuned.

After the image is ready, OMS will be available from :80 with opennode:changeme as a default account.

cheers,
Ilja

Raboo:
Ok,
I just subscribed to opennode-announce mail list. Will you announce it there or reply to this thread when it's done?

ilja_l:
I'll reply to this thread.

Actually, we are close to finalizing it, then ~20mins to build/push a template to the repo.

The sw is being actively developed and I suggest doing update.sh from time to time. This will be in the announcement.

Raboo:
I wonder, isn't it just easier and more convenient to have OMS bundled in the OpenNode server?
That way you don't need a virtual machine to manage your VMs.

The downside is that you will have OMS installed on all OpenNode servers. But on the other hand you don't really have to automatically enable startup for OMS.

Navigation

[0] Message Index

[#] Next page

Go to full version