[
https://issues.apache.org/jira/browse/DTACLOUD-310?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13447556#comment-13447556
]
Marios Andreou commented on DTACLOUD-310:
-----------------------------------------
ACK - with fix for minor typo:
[marios@name deltacloud]$ ./server/bin/deltacloudd -i fgcp
Starting Deltacloud API :: fgcp :: http://localhost:3001/api
/home/marios/Documents/WORK/NewEclipsey/DCore/deltacloud_git_repo/deltacloud/server/lib/deltacloud/helpers/driver_helper.rb:52:in
`require_relative':
/home/marios/Documents/WORK/NewEclipsey/DCore/deltacloud_git_repo/deltacloud/server/lib/deltacloud/drivers/fgcp/fgcp_driver.rb:1323:
syntax error, unexpected keyword_not, expecting keyword_do or '{' or '('
(SyntaxError)
on / does not exist. Specify one of / do
I put a new patch ontop of yours in order to keep the authorship info (if I had
edited your patch it would have made me author).
Committed with hash: 755d46ef47f585d12a930fd3bb7bbe1f124e53f0 (FGCP: add rule
action deny accept and log rule) and 5af7993713c8f467820de4a07eb496a400e13c37
(Fix typo in fgcp driver (related to patch on DTACLOUD_310)
> FGCP: support FW rule action and log rule
> -----------------------------------------
>
> Key: DTACLOUD-310
> URL: https://issues.apache.org/jira/browse/DTACLOUD-310
> Project: DeltaCloud
> Issue Type: New Feature
> Components: Server
> Environment: FGCP driver
> Reporter: Dies Koper
> Assignee: Dies Koper
> Priority: Minor
> Attachments:
> 0001-Adds-log_rule-and-rule_action-for-FirewallRule-model.patch,
> 0001-FGCP-add-rule-action-deny-accept-and-log-rule.patch,
> 0001-FGCP-add-rule-action-deny-accept-and-log-rule.patch
>
>
> In the FGCP, FW rules have an action which define whether the FW should
> Accept or Drop packets that are triggered by the rule. It also offers the
> option of defining whether the even should be logged or not.
> Without DC support for the former, DC only lists the Accept rules, which
> gives an incorrect view.
--
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
