Mailing-List: contact deltacloud-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: deltacloud-dev@incubator.apache.org
Received-SPF: pass (athena.apache.org: domain of lutter@redhat.com designates
 209.132.183.28 as permitted sender)
Subject: Re: jruby support: which drivers?
From: David Lutterkort <lutter@redhat.com>
To: deltacloud-dev@incubator.apache.org
In-Reply-To: <AANLkTimMym9rUOJ4ZnOw0dKqsSMu4J2OrR4=b5hzn7KC@mail.gmail.com>
References: <AANLkTimMym9rUOJ4ZnOw0dKqsSMu4J2OrR4=b5hzn7KC@mail.gmail.com>
Content-Type: text/plain; charset="ISO-8859-15"
Organization: Red Hat Inc
Date: Tue, 04 Jan 2011 00:08:05 +0000
Message-ID: <1294099685.4287.21.camel@avon.watzmann.net>
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit

On Fri, 2010-12-31 at 17:49 +0100, Adrian Cole wrote:
> I've found a few issues, noting I'm only testing read-only at this
> point.  A lot of issues revolve around state consistency, which I sent
> an email wrt earlier.  There's also a few cases where fetching
> something by href returns the wrong value.  I think at least the state
> question needs to be cleared up before we look into other issues.

Are you working off the 0.1.0 gems or the head of the svn/git repo ?

> gogrid: SOMEWHAT, INCONSISTENT
>     * I've sent a couple notes to the list, but I also get "Bad
> Request" attempting to start an instance

Sounds like a bug.

> rackspace: INCONSISTENT
>     * states are out of sync with latest mock

As noted in the other mail thread, states still need more cleanup. Part
of the problem here is two conflicting schools of thought: initially,
the drivers were written to expose as much detail about the cloud's
native instance lifecycle as possible, later on there has been some
effort to simplify the set of instance states, and with them the FSM for
the instance lifecycle that is exposed.

I've created an issue in Jira to track this [1]

> opennebula: NOT SURE
>     * got the following error, but I'm not sure my local runtime is
> setup: RuntimeError - CloudClient::Error is not a valid input stream.

Do you have a stacktrace ? From looking at the code, looks like a simple
error ('return' instead of 'raise' in
server/lib/deltacloud/drivers/opennebula/cloud_client.rb:80)

> ec2: SOMEWHAT, INCONSISTENT
>     * see rackspace: ec2 has a STOPPING state.  Is this expected?

Part of the state mess.

> Also, fetching an availability zone by href returns the wrong
> response.

A regression introduced by svn commit r1044338 (the capabilities stuff)

> rhevm: INCOMPATIBLE
>     * uses power shell

We are in the process of rewriting the RHEV-M drive against the new
RHEV-M REST API - I wouldn't worry about RHEV-M until that's done.

> terremark: SOMEWHAT, INCONSISTENT
>     * see rackspace: terremark has a SHUTTING_DOWN state.  Is this
> expected? also a problem with "undefined local variable or method
> `vdc_id'" for images and instances.

Do you have a stacktrace for that ?

> rimuhosting: BROKE, INCONSISTENT
>     * see rackspace: rimuhosting has a SHUTTING_DOWN state.  Is this
> expected? also everything but realm queries break on doing .each on
> something that is null

We probably need to get Ivan to update that driver.

David

[1] https://issues.apache.org/jira/browse/DTACLOUD-12