[
https://issues.apache.org/jira/browse/DTACLOUD-351?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13485302#comment-13485302
]
David Lutterkort commented on DTACLOUD-351:
-------------------------------------------
What we're running into here is a limitation of the DC architecture: that we
don't have a way to reliably defer work. For now, I think doing the Thread.new
patch is fine, and I agree with Dies that we can't magically delete FW's unless
we can be dead sure they were created by DC to begin with.
BTW, the Thread.new solution can fail simply because the DC server is shut down
before we ever get to issue the fw.destroy.
> fgcp: serverType for FWs changed to 'firewall' which is not in server type
> list
> -------------------------------------------------------------------------------
>
> Key: DTACLOUD-351
> URL: https://issues.apache.org/jira/browse/DTACLOUD-351
> Project: DeltaCloud
> Issue Type: Bug
> Components: Server
> Environment: fgcp
> Reporter: Dies Koper
> Assignee: Marios Andreou
> Attachments: 0001-fgcp-take-fw-out-of-instance-list.patch
>
>
> fgcp API changed: it now returns 'firewall' for FWs, which is not listed in
> server type list.
> This causes issues for cimi /machines API which cross-references with
> hardware_profiles output.
> Better to remove FW instances from instance list altogether.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
