[jira] [Commented] (DTACLOUD-108) RHEV-M user_data trouble

["Michal Fojtik (Commented) (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/DTACLOUD-108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13152767#comment-13152767 ] 

Michal Fojtik commented on DTACLOUD-108:
----------------------------------------

Hey,

Today I pushed patch which add 'has_capability?(name)' method that is executed before creating VM with 'user_data'.

Unfortunately this call require authentication. And since the features are listed in root entrypoint, we will need to add authentication
here, which I don't think is OK :-) (at least will make some Aeolus people antacid addicted).

Also note that you can have n-hosts in your cluster and some of them can support this injection and some not. How to indicate this
to the client?

For me, currently the most cleanest way how to sort this issue out is to throw decent Exception to client if cluster is not capable to
handle floppy_inject hook and client set 'user_data' property (something like Pre-requires failure, etc)
                
> RHEV-M user_data trouble
> ------------------------
>
>                 Key: DTACLOUD-108
>                 URL: https://issues.apache.org/jira/browse/DTACLOUD-108
>             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: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira