deltacloud-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David Lutterkort (Commented) (JIRA)" <>
Subject [jira] [Commented] (DTACLOUD-108) RHEV-M user_data trouble
Date Mon, 28 Nov 2011 20:23:40 GMT


David Lutterkort commented on DTACLOUD-108:

Yes, I agree - since there can be mixed clusters, the user has to be prepared for an error
of 'user_data injection not possible'.

So let's just advertise user_data in the entrypoint and throw a decent exception if we can't
find the floppyinject hook.
> RHEV-M user_data trouble
> ------------------------
>                 Key: DTACLOUD-108
>                 URL:
>             Project: DeltaCloud
>          Issue Type: Bug
>            Reporter: David Lutterkort
>            Assignee: Michal Fojtik
> For a number of reasons, the current way how we do user_data injection in RHEV-M causes
heartburn. To address that, we need to
> (a) take an antacid
> (b) only report feature :instances, :user_data if the capabilities for that RHEV-M provider
contain "//custom_property[@name='floppyinject']" (ideally, cache this in a long-lived cache
keyed by RHEV-M provider URL)
> (c) in rhevm_client.rb(create_vm) do not do any checks for version; instead, check if
provider has floppyinject hook installed
> (d) take another antacid

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message