deltacloud-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dies Koper (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DTACLOUD-351) fgcp: serverType for FWs changed to 'firewall' which is not in server type list
Date Wed, 24 Oct 2012 14:34:13 GMT

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

Dies Koper commented on DTACLOUD-351:
-------------------------------------

Thanks for all the feedback!
To answer your comments:

1. David said (when we discussed load balancers, which similarly to FWs are implemented as
(special) instances in fgcp): (see "RE: load balancers with FGCP" around 22 Aug 2012 on DC
mailing list)

> > Is it desirable to expose the load balancer in this way ? Could we
> > suppress load balancer instances in the instances list ?

> > Can we handle the start/stop transparently ? IOW, API users do not need
> > to know that LB's need to be started explicitly, we start them for them
> > when they are needed, and stop them when they are not balancing anything
> > anymore.

So my reasons for removing the firewalls from instances:
1. the above;
2. since recently raises the issue that their returned hardware_profile is a special one,
not returned by FGCP's hwp query method (as it's not a hwp that can be selected by users to
create normal instances);
3. FWs can't be assigned public IP addresses, run commands on or added to load balancers,
which they seem they can if included in instances in the GUI.

2. David also wrote in that e-mail:
> > My problem with this is that LB's can only be used then if the user
> > knows to start some special instance - with that, the FGPC driver will
> > behave differently from other drivers.

which applies to FGCP FWs as well, they can only be removed if the user knows to stop some
special instance, behaving differently from other drivers.

3. Thanks for clearing that up. I remembered there was a response code like that and had been
searching in the 3xx, 4xx and 5xx ranges for it!
Sounds like 202 is what I need and DC already uses that so my patch is okay the way it is?

4. Thanks. I may merge some next time I make changes in that block.
                
> 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

Mime
View raw message