[
https://issues.apache.org/jira/browse/DTACLOUD-351?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13484866#comment-13484866
]
Dies Koper commented on DTACLOUD-351:
-------------------------------------
I agree with 1 and 2, not with 3.
A contract could be used by multiple users (of e.g. the same team). If someone
in my team stopped his system's firewall, I can't have DC delete his system
just because I used DC to list the firewalls.
I don't think there are any cases that the destroy in Thread.new can fail if
the stop operation succeeds, at least none where the same operation in another
location (such as a listing) does have a chance of succeeding.
I'll update my patch for 2. (and fix a bug I just found - I hadn't tested the
case of listing firewalls while a firewall was being instantiated).
> 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
