Bug 1042540

Summary: [RFE][neutron]: FWaas extension for customized service and service group
Product: Red Hat OpenStack Reporter: RHOS Integration <rhos-integ>
Component: openstack-neutronAssignee: lpeer <lpeer>
Status: CLOSED UPSTREAM QA Contact: Ofer Blaut <oblaut>
Severity: low Docs Contact:
Priority: unspecified    
Version: unspecifiedCC: chrisw, markmc, nyechiel, yeylon
Target Milestone: ---Keywords: FutureFeature, Triaged
Target Release: 8.0 (Liberty)   
Hardware: Unspecified   
OS: Unspecified   
URL: https://blueprints.launchpad.net/neutron/+spec/fwaas-customized-service
Whiteboard: upstream_milestone_none upstream_status_needs-code-review upstream_definition_obsolete
Fixed In Version: Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-03-19 11:07:59 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description RHOS Integration 2013-12-13 00:18:18 UTC 
Cloned from launchpad blueprint https://blueprints.launchpad.net/neutron/+spec/fwaas-customized-service.

Description:

Service is used to define type of traffic, this blueprint creates an extension that allows administrator to create customized service objects. The customized service objects can be grouped together to form a service group object.
A service object can have following attributes:
 Name
 Transport protocol
 Source and destination port numbers (ranges) for services using TCP or UDP
 The ICMP type and code for the services using ICMP
 Service Timeout value

The transport protocol and port numbers are mandatory.

People are asking about the relationship between the service object and the protocol/port that can be defined on the rule. I think service object can cover the current "on-rule" protocol/port. But just for the users who want to create a simple rule, I'm thinking still to keep the original "on-rule" protocol/port options. But we will not allow user to use service object and "on-rule" protocol/port at the same time.

Specification URL (additional information):

None
Comment 2 Nir Yechiel 2015-03-19 11:07:59 UTC 
This RFE was automatically opened to track status of upstream development. At this point we see no reason to keep track of this in Red Hat bugzilla, thus closing it.