On 09/01/11 - 10:41:37AM, Jan Provaznik wrote:
On 08/31/2011 11:51 PM, Chris Lalancette wrote:
>All,
> This is a RFC patch series to remove condor from the conductor. In short,
>condor presents problems for our project because it is an external project, it
>is written in C++ (when most of our developers are ruby), and it is too complex
>for our current needs.
Wohoo, this is great!
> The new way we do scheduling is described pretty well in patch 1, so I
>won't delve into it here. This is an RFC series because there are 2 known
>problems and it has only been lightly tested.
> The first known problem is that since we are doing the deltacloud create
>calls inline in the conductor, this can cause the UI itself to timeout. This is
>going to be a problem when using the VMware backend, as we know that the
>create call there can take a long time. Possible solutions are to use a
>different thread or process for the call, but there may be others.
> The second known problem is that for reasons I don't really understand,
>updating the instance row in the database (using instance.save!) has some
>surprising results. One example of this is public_addresses; the
>public_addresses field I get from the deltacloud backend looks correct
>(ec2-50-7-27-214.compute-1.amazonaws.com, or whatever), but when it is saved
>into the database it looks odd (---\n- ec2-50-7-27-214.compute-1.amazonaws.com\n).
>Since dbomatic is not doing this manipulation, I can only presume that some
I think this is because you are trying to save array into string -
public_addresses attr returned by DC API is array, conductor
public_addresses attr is string.
D'oh! I knew I was missing something, this was exactly it. I have a fix now
that I'll roll into the series and will show up when I post it again. Thanks!
>observer is screwing it up, but I can't see how. A second example of this
>problem is that the public key that gets created when the instance is launched
>disappears from the UI as soon as dbomatic runs.
This bug is not related to this patchset - someone else already hit this.
Ah, nice. OK, so I won't worry about that particular bug right now, I'll
assume you guys are going to handle it.
--
Chris Lalancette