)]}'
{"id":"openstack%2Fpython-neutronclient~104426","triplet_id":"openstack%2Fpython-neutronclient~master~I3e8f73203033c0f41b24393b4add990bf8ad84fb","project":"openstack/python-neutronclient","branch":"master","topic":"bp/FWaaS","hashtags":[],"change_id":"I3e8f73203033c0f41b24393b4add990bf8ad84fb","subject":"Implements: blueprint FWaaS extension for customized service and service group In FWaaS, administrator can use port range and protocol inside firewall rules to define traffic type. But we don\u0027t have a flexible way to allow user to specify more than one type of traffic in the same rule.To support different traffic type, with the same source, destination address and action, different rules need to be created. This makes the process of defining firewall rules un-scalable.","status":"ABANDONED","created":"2014-07-03 03:05:32.000000000","updated":"2014-07-04 01:39:12.000000000","total_comment_count":0,"unresolved_comment_count":0,"has_review_started":true,"meta_rev_id":"6d42a8c6bfe14c27cb2f30f3941b300b00cf5b8a","_number":104426,"virtual_id_number":104426,"owner":{"_account_id":11753,"name":"badveli_vishnuus","email":"badveli_vishnuus@yahoo.com","username":"badveli_vishnuus"},"actions":{},"labels":{"Verified":{"disliked":{"_account_id":3,"name":"Jenkins","username":"jenkins"},"all":[{"value":-1,"date":"2014-07-03 04:04:07.000000000","_account_id":3,"name":"Jenkins","username":"jenkins"},{"date":"2014-07-03 03:05:37.000000000","_account_id":10068,"name":"Welcome, new contributor!","username":"welcome-message"}],"values":{"-2":"Fails","-1":"Doesn\u0027t seem to work"," 0":"No score","+1":"Works for me","+2":"Verified"},"description":"","value":-1,"default_value":0,"optional":true},"Code-Review":{"all":[{"value":0,"permitted_voting_range":{"min":-1,"max":1},"_account_id":3,"name":"Jenkins","username":"jenkins"},{"value":0,"permitted_voting_range":{"min":-1,"max":1},"_account_id":10068,"name":"Welcome, new contributor!","username":"welcome-message"}],"values":{"-2":"Do not merge","-1":"This patch needs further work before it can be merged"," 0":"No score","+1":"Looks good to me, but someone else must approve","+2":"Looks good to me (core reviewer)"},"description":"","default_value":0,"optional":true},"Workflow":{"all":[{"_account_id":3,"name":"Jenkins","username":"jenkins"},{"_account_id":10068,"name":"Welcome, new contributor!","username":"welcome-message"}],"values":{"-1":"Work in progress"," 0":"Ready for reviews","+1":"Approved"},"description":"","default_value":0,"optional":true}},"removable_reviewers":[],"reviewers":{"REVIEWER":[{"_account_id":3,"name":"Jenkins","username":"jenkins"},{"_account_id":10068,"name":"Welcome, new contributor!","username":"welcome-message"}]},"pending_reviewers":{},"reviewer_updates":[{"updated":"2014-07-03 03:05:37.000000000","updated_by":{"_account_id":10068,"name":"Welcome, new contributor!","username":"welcome-message"},"reviewer":{"_account_id":10068,"name":"Welcome, new contributor!","username":"welcome-message"},"state":"REVIEWER"},{"updated":"2014-07-03 04:04:07.000000000","updated_by":{"_account_id":3,"name":"Jenkins","username":"jenkins"},"reviewer":{"_account_id":3,"name":"Jenkins","username":"jenkins"},"state":"REVIEWER"}],"messages":[{"id":"111d7f00b9b2e8dad256b195ba67f9ae5ace5a6c","author":{"_account_id":11753,"name":"badveli_vishnuus","email":"badveli_vishnuus@yahoo.com","username":"badveli_vishnuus"},"date":"2014-07-03 03:05:32.000000000","message":"Uploaded patch set 1.","accounts_in_message":[],"_revision_number":1},{"id":"0c1967fe5d9ba19e04a0d238812d8212749a171c","author":{"_account_id":3,"name":"Jenkins","username":"jenkins"},"date":"2014-07-03 03:05:33.000000000","message":"Patch Set 1:\n\nStarting check jobs.\nhttp://status.openstack.org/zuul/","accounts_in_message":[],"_revision_number":1},{"id":"c615adbad52c9e4c093d51d094d5f597b2848865","author":{"_account_id":10068,"name":"Welcome, new contributor!","username":"welcome-message"},"date":"2014-07-03 03:05:37.000000000","message":"Patch Set 1:\n\nThank you for your first contribution to OpenStack.\n\n    Your patch will now be tested automatically by OpenStack testing frameworks\n    and once the automatic tests pass, it will be reviewed by other friendly\n    developers. They will give you feedback and may require you to refine it.\n\n    People seldom get their patch approved on the first try, so don\u0027t be\n    concerned if requested to make corrections. Feel free to modify your patch\n    and resubmit a new change-set.\n\n    Patches usually take 3 to 7 days to be reviewed so be patient and be\n    available on IRC to ask and answer questions about your work. The more you\n    participate in the community the more rewarding it is for you. You may also\n    notice that the more you get to know people and get to be known, the faster\n    your patches will be reviewed and eventually approved. Get to know others\n    and become known by doing code reviews: anybody can do it, and it\u0027s a\n    great way to learn the code base.\n\n    Thanks again for supporting OpenStack, we look forward to working with you.\n\n    IRC: https://wiki.openstack.org/wiki/IRC\n    Workflow: https://wiki.openstack.org/wiki/Gerrit_Workflow","accounts_in_message":[],"_revision_number":1},{"id":"42e832cb621f756ca92a5952d75395f1b7c01e2b","author":{"_account_id":3,"name":"Jenkins","username":"jenkins"},"date":"2014-07-03 04:04:07.000000000","message":"Patch Set 1: Verified-1\n\nBuild failed.  For information on how to proceed, see https://wiki.openstack.org/wiki/GerritJenkinsGit#Test_Failures\n\n- gate-python-neutronclient-pep8 http://logs.openstack.org/26/104426/1/check/gate-python-neutronclient-pep8/989450b : FAILURE in 54s\n- gate-python-neutronclient-docs http://docs-draft.openstack.org/26/104426/1/check/gate-python-neutronclient-docs/90f7b23/doc/build/html/ : SUCCESS in 1m 16s\n- gate-python-neutronclient-python26 http://logs.openstack.org/26/104426/1/check/gate-python-neutronclient-python26/e579d91 : FAILURE in 16s\n- gate-python-neutronclient-python27 http://logs.openstack.org/26/104426/1/check/gate-python-neutronclient-python27/3695f9a : FAILURE in 53s\n- check-tempest-dsvm-neutron http://logs.openstack.org/26/104426/1/check/check-tempest-dsvm-neutron/f8fb89d : SUCCESS in 51m 48s\n- check-tempest-dsvm-neutron-pg http://logs.openstack.org/26/104426/1/check/check-tempest-dsvm-neutron-pg/538aeea : SUCCESS in 54m 48s\n- check-tempest-dsvm-neutron-heat-slow http://logs.openstack.org/26/104426/1/check/check-tempest-dsvm-neutron-heat-slow/b546600 : SUCCESS in 22m 11s\n- check-tempest-dsvm-neutron-full http://logs.openstack.org/26/104426/1/check/check-tempest-dsvm-neutron-full/a06ed6b : FAILURE in 54m 19s (non-voting)\n- gate-tempest-dsvm-neutron-large-ops http://logs.openstack.org/26/104426/1/check/gate-tempest-dsvm-neutron-large-ops/eb92462 : SUCCESS in 21m 31s\n- check-grenade-dsvm-neutron http://logs.openstack.org/26/104426/1/check/check-grenade-dsvm-neutron/6bf6eaa : FAILURE in 35m 25s (non-voting)\n- check-tempest-dsvm-full-havana http://logs.openstack.org/26/104426/1/check/check-tempest-dsvm-full-havana/0970fc5 : SUCCESS in 33m 50s (non-voting)\n- check-tempest-dsvm-neutron-havana http://logs.openstack.org/26/104426/1/check/check-tempest-dsvm-neutron-havana/861b2a2 : SUCCESS in 39m 15s (non-voting)\n- check-tempest-dsvm-full-icehouse http://logs.openstack.org/26/104426/1/check/check-tempest-dsvm-full-icehouse/d33709a : SUCCESS in 45m 44s\n- check-tempest-dsvm-neutron-icehouse http://logs.openstack.org/26/104426/1/check/check-tempest-dsvm-neutron-icehouse/c81d867 : SUCCESS in 55m 17s\n- gate-python-neutronclient-python33 http://logs.openstack.org/26/104426/1/check/gate-python-neutronclient-python33/9c06dbd : FAILURE in 3m 47s (non-voting)\n- gate-python-neutronclient-pypy http://logs.openstack.org/26/104426/1/check/gate-python-neutronclient-pypy/3d9a0cf : FAILURE in 1m 26s","accounts_in_message":[],"_revision_number":1},{"id":"b14c68ca50da1fa2616b12f2a8eb50cb2978e80c","author":{"_account_id":11753,"name":"badveli_vishnuus","email":"badveli_vishnuus@yahoo.com","username":"badveli_vishnuus"},"date":"2014-07-04 01:39:12.000000000","message":"Abandoned\n\nwrong merge","accounts_in_message":[],"_revision_number":1}],"current_revision_number":1,"current_revision":"20a84f4ccf59596183da2bf636fae98daac298e0","revisions":{"20a84f4ccf59596183da2bf636fae98daac298e0":{"kind":"REWORK","_number":1,"created":"2014-07-03 03:05:32.000000000","uploader":{"_account_id":11753,"name":"badveli_vishnuus","email":"badveli_vishnuus@yahoo.com","username":"badveli_vishnuus"},"ref":"refs/changes/26/104426/1","fetch":{"anonymous http":{"url":"https://review.opendev.org/openstack/python-neutronclient","ref":"refs/changes/26/104426/1","commands":{"Checkout":"git fetch https://review.opendev.org/openstack/python-neutronclient refs/changes/26/104426/1 \u0026\u0026 git checkout FETCH_HEAD","Cherry Pick":"git fetch https://review.opendev.org/openstack/python-neutronclient refs/changes/26/104426/1 \u0026\u0026 git cherry-pick FETCH_HEAD","Format Patch":"git fetch https://review.opendev.org/openstack/python-neutronclient refs/changes/26/104426/1 \u0026\u0026 git format-patch -1 --stdout FETCH_HEAD","Pull":"git pull https://review.opendev.org/openstack/python-neutronclient refs/changes/26/104426/1"}}},"commit":{"parents":[{"commit":"3a25ff3b3d35df38e00fcad4c12e3df06d69985a","subject":"Merge \"Switch over to mox3\"","web_links":[{"name":"gitea","tooltip":"Open in GitWeb","url":"https://opendev.org/openstack/python-neutronclient/commit/3a25ff3b3d35df38e00fcad4c12e3df06d69985a"}]}],"author":{"name":"badveli_vishnuus","email":"badveli_vishnuus@yahoo.com","date":"2014-07-03 01:13:35.000000000","tz":0},"committer":{"name":"badveli_vishnuus","email":"badveli_vishnuus@yahoo.com","date":"2014-07-03 02:53:11.000000000","tz":0},"subject":"Implements: blueprint FWaaS extension for customized service and service group In FWaaS, administrator can use port range and protocol inside firewall rules to define traffic type. But we don\u0027t have a flexible way to allow user to specify more than one type of traffic in the same rule.To support different traffic type, with the same source, destination address and action, different rules need to be created. This makes the process of defining firewall rules un-scalable.","message":"Implements: blueprint FWaaS extension for customized service and service group\nIn FWaaS, administrator can use port range and protocol inside firewall rules\nto define traffic type. But we don\u0027t have a flexible way to allow user to specify more\nthan one type of traffic in the same rule.To support different traffic type, with the\nsame source, destination address and action, different rules need to be created.\nThis makes the process of defining firewall rules un-scalable.\n\ntwo resources are added to enhance the FWaaS using the following cli\none is called service group and one is called service object\nAdministrator can use service object to define a special type of traffic. The service\nobjects is grouped into service group that can be referenced from other openstack\nmodules (eg. firewall rule).\nEach service object can be defined with a timeout value that can be used to overwrite\ndefault session idle timeout value.\n\nNew CLIs:\nservice-group-create\nservice-group-delete\nservice-group-list\nservice-group-show\nservice-group-update\nservice-object-create\nservice-object-delete\nservice-object-list\nservice-object-show\n\nChange-Id: I3e8f73203033c0f41b24393b4add990bf8ad84fb\n","web_links":[{"name":"gitea","tooltip":"Open in GitWeb","url":"https://opendev.org/openstack/python-neutronclient/commit/20a84f4ccf59596183da2bf636fae98daac298e0"}],"resolve_conflicts_web_links":[{"name":"gitea","tooltip":"Open in GitWeb","url":"https://opendev.org/openstack/python-neutronclient/commit/20a84f4ccf59596183da2bf636fae98daac298e0"}]},"branch":"refs/heads/master"}},"requirements":[],"submit_records":[],"submit_requirements":[]}