deltacloud-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "dave johnson (Commented) (JIRA)" <>
Subject [jira] [Commented] (DTACLOUD-126) RHEV-M: We need to skip 'default' cluster when no 'realm_id' is specified in create_instance
Date Fri, 13 Jan 2012 18:02:39 GMT


dave johnson commented on DTACLOUD-126:

So watching the logs, it appears that conductor picks and sends deltacloud the data_center
which is a good starting point for deciding where to look for the image.

Here is an example of sending a request without the realm_id, conductor chooses which provider
to send it to (and I am assuming this would mean its a valid provider with the image in question),
from there search the clusters underneath it and find the image?

^[[1;29mProcessing /api/instances^[[0m (for at Fri Jan 13 12:31:20 -0500 2012) [POST]
thin server (localhost:3002) [deltacloud-mock][8251]: Parameters: {"name"=>"try3-dj-rhel6-charlie",
"hwp_memory"=>"512", "image_id"=>"62392110-ae69-4bf6-a35d-b072bfcdc3f3", "keyname"=>"",
"hwp_id"=>"SERVER", "hwp_cpu"=>"1", "hwp_storage"=>"1"}
thin server (localhost:3002) [deltacloud-mock][8251]: Provider:;045ba8ee-2a60-11e1-a69d-5cf3fc1c861c
thin server (localhost:3002) [deltacloud-mock][8251]: Authentication: Basic

At the moment, this is the following stack trace that is generated when no realm is given:
thin server (localhost:3002) [deltacloud-mock][8251]: [NO HANDLED] NoMethodError: undefined
method `empty?' for nil:NilClass
/usr/share/deltacloud-core/bin/../lib/deltacloud/drivers/rhevm/rhevm_client.rb:129:in `create_vm'
/usr/lib/ruby/gems/1.8/gems/nokogiri-1.5.0.beta.4/lib/nokogiri/xml/builder.rb:364:in `instance_eval'
/usr/lib/ruby/gems/1.8/gems/nokogiri-1.5.0.beta.4/lib/nokogiri/xml/builder.rb:364:in `insert'
/usr/lib/ruby/gems/1.8/gems/nokogiri-1.5.0.beta.4/lib/nokogiri/xml/builder.rb:350:in `method_missing'
/usr/share/deltacloud-core/bin/../lib/deltacloud/drivers/rhevm/rhevm_client.rb:126:in `create_vm'
/usr/lib/ruby/gems/1.8/gems/nokogiri-1.5.0.beta.4/lib/nokogiri/xml/builder.rb:291:in `instance_eval'
/usr/lib/ruby/gems/1.8/gems/nokogiri-1.5.0.beta.4/lib/nokogiri/xml/builder.rb:291:in `initialize'
/usr/share/deltacloud-core/bin/../lib/deltacloud/drivers/rhevm/rhevm_client.rb:125:in `new'
/usr/share/deltacloud-core/bin/../lib/deltacloud/drivers/rhevm/rhevm_client.rb:125:in `create_vm'
/usr/share/deltacloud-core/bin/../lib/deltacloud/drivers/rhevm/rhevm_driver.rb:202:in `create_instance'
/usr/share/deltacloud-core/bin/../lib/deltacloud/base_driver/exceptions.rb:151:in `call'
/usr/share/deltacloud-core/bin/../lib/deltacloud/base_driver/exceptions.rb:151:in `safely'
/usr/share/deltacloud-core/bin/../lib/deltacloud/drivers/rhevm/rhevm_driver.rb:193:in `create_instance'
/usr/share/deltacloud-core/bin/../lib/sinatra/rabbit.rb:125:in `instance_eval'
/usr/share/deltacloud-core/bin/../lib/sinatra/rabbit.rb:125:in `POST /api/instances'
/usr/lib/ruby/gems/1.8/gems/sinatra-1.2.6/lib/sinatra/base.rb:1151:in `call'

> RHEV-M: We need to skip 'default' cluster when no 'realm_id' is specified in create_instance
> --------------------------------------------------------------------------------------------
>                 Key: DTACLOUD-126
>                 URL:
>             Project: DeltaCloud
>          Issue Type: Bug
>          Components: Server
>            Reporter: Michal Fojtik
>            Assignee: Michal Fojtik
>            Priority: Blocker
> When there is no realm_id provided upon creating a new instance, by default Deltacloud
will choose the first 'realm' returned by 'realms' call.
> In RHEV-M it usually means that the 'default' cluster is being returned, which is wrong
in most cases, since this cluster is being used for
> holding the 'Blank' template, thus cannot be removed. This cluster usually don't have
'storage domain' assigned and deploying an instance
> there lead to error.
> The solution could to to 'skip' default realm and try to use next realm in row (if there
is next realm). If there is just 'default' realm, we should
> choose this realm and additionally give client decent error :-)

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