Difference between revisions of "Neutron/FWaaS/FWaaS-ServiceGroup"
(Created page with "Two resources service_group and service_object are added, multiple service group and service objects can be configured to allow flexibility and grouping of traffic, service gr...") |
|||
| Line 1: | Line 1: | ||
| − | + | A new extension with two resources service_group and service_object are added, | |
multiple service group and service objects can be configured to | multiple service group and service objects can be configured to | ||
| − | allow flexibility and grouping of traffic | + | allow flexibility and grouping of traffic. |
| − | + | Service objects are grouped into service group that can be referenced | |
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
from other openstack modules (eg. firewall rule, securitygroup etc). | from other openstack modules (eg. firewall rule, securitygroup etc). | ||
currently firewall rule has multiple service groups to allow the | currently firewall rule has multiple service groups to allow the | ||
user flexibilty to define their own groups and use them without impacting | user flexibilty to define their own groups and use them without impacting | ||
| − | the other users. | + | the other users. Due to many to many relationship between service groups and |
firewall rules exists an association table is introduced, | firewall rules exists an association table is introduced, | ||
Each service object can be defined with a timeout value that can be used | Each service object can be defined with a timeout value that can be used | ||
to overwrite default session idle timeout value. | to overwrite default session idle timeout value. | ||
Revision as of 03:52, 27 August 2014
A new extension with two resources service_group and service_object are added, multiple service group and service objects can be configured to allow flexibility and grouping of traffic. Service objects are grouped into service group that can be referenced from other openstack modules (eg. firewall rule, securitygroup etc). currently firewall rule has multiple service groups to allow the user flexibilty to define their own groups and use them without impacting the other users. Due to many to many relationship between service groups and firewall rules exists an association table is introduced, Each service object can be defined with a timeout value that can be used to overwrite default session idle timeout value.
