)]}'
{"/COMMIT_MSG":[{"author":{"_account_id":7,"name":"Jay Pipes","email":"jaypipes@gmail.com","username":"jaypipes"},"change_message_id":"a887ee55953ee31ab44d720a64ca8dfb498dd40c","unresolved":false,"context_lines":[{"line_number":21,"context_line":"to realize these features. NFV Orchestrator (NFVO) provides end-to-end"},{"line_number":22,"context_line":"Network Service Orchestration. NFVO would in turn use VNFM component to"},{"line_number":23,"context_line":"stand up the VNFs composed in a Network Service. NFVO will also render"},{"line_number":24,"context_line":"VNF Forwarding Graphs (VNFFG) using a Service Function Chaining (SFC)"},{"line_number":25,"context_line":"API across the instantiated VNFs. Tacker intends to use Neutron\u0027s"},{"line_number":26,"context_line":"networking-sfc API [2] for this purpose."},{"line_number":27,"context_line":""}],"source_content_type":"text/x-gerrit-commit-message","patch_set":2,"id":"3a57f1b5_8e3e1cb7","line":24,"updated":"2016-02-09 20:06:43.000000000","message":"Gotta love telco acronym soup. :)","commit_id":"7ab7551948797188267ef61233aee3208d098b8f"},{"author":{"_account_id":13380,"name":"Sridhar Ramaswamy","email":"srics.r@gmail.com","username":"srics-r"},"change_message_id":"ad90600f8575cb7c294237351be4f483927055a7","unresolved":false,"context_lines":[{"line_number":21,"context_line":"to realize these features. NFV Orchestrator (NFVO) provides end-to-end"},{"line_number":22,"context_line":"Network Service Orchestration. NFVO would in turn use VNFM component to"},{"line_number":23,"context_line":"stand up the VNFs composed in a Network Service. NFVO will also render"},{"line_number":24,"context_line":"VNF Forwarding Graphs (VNFFG) using a Service Function Chaining (SFC)"},{"line_number":25,"context_line":"API across the instantiated VNFs. Tacker intends to use Neutron\u0027s"},{"line_number":26,"context_line":"networking-sfc API [2] for this purpose."},{"line_number":27,"context_line":""}],"source_content_type":"text/x-gerrit-commit-message","patch_set":2,"id":"3a57f1b5_dc8123fd","line":24,"in_reply_to":"3a57f1b5_8e3e1cb7","updated":"2016-02-10 00:24:40.000000000","message":"Like you said in the tc mtg, welcome to the telco world :)","commit_id":"7ab7551948797188267ef61233aee3208d098b8f"},{"author":{"_account_id":105,"name":"Kyle Mestery","email":"mestery@mestery.com","username":"mestery"},"change_message_id":"7c4608e20a306c09a4bc06cb5dfef95d245a2719","unresolved":false,"context_lines":[{"line_number":22,"context_line":"Network Service Orchestration. NFVO would in turn use VNFM component to"},{"line_number":23,"context_line":"stand up the VNFs composed in a Network Service. NFVO will also render"},{"line_number":24,"context_line":"VNF Forwarding Graphs (VNFFG) using a Service Function Chaining (SFC)"},{"line_number":25,"context_line":"API across the instantiated VNFs. Tacker intends to use Neutron\u0027s"},{"line_number":26,"context_line":"networking-sfc API [2] for this purpose."},{"line_number":27,"context_line":""},{"line_number":28,"context_line":"NFV work flows are typically described using templates. The current"}],"source_content_type":"text/x-gerrit-commit-message","patch_set":2,"id":"3a57f1b5_2b06fa20","line":25,"updated":"2016-02-09 20:05:41.000000000","message":"This is no the neutron SFC api [1]. I think it should be though.\n\n[1] http://docs.openstack.org/developer/networking-sfc/","commit_id":"7ab7551948797188267ef61233aee3208d098b8f"},{"author":{"_account_id":13380,"name":"Sridhar Ramaswamy","email":"srics.r@gmail.com","username":"srics-r"},"change_message_id":"ad90600f8575cb7c294237351be4f483927055a7","unresolved":false,"context_lines":[{"line_number":22,"context_line":"Network Service Orchestration. NFVO would in turn use VNFM component to"},{"line_number":23,"context_line":"stand up the VNFs composed in a Network Service. NFVO will also render"},{"line_number":24,"context_line":"VNF Forwarding Graphs (VNFFG) using a Service Function Chaining (SFC)"},{"line_number":25,"context_line":"API across the instantiated VNFs. Tacker intends to use Neutron\u0027s"},{"line_number":26,"context_line":"networking-sfc API [2] for this purpose."},{"line_number":27,"context_line":""},{"line_number":28,"context_line":"NFV work flows are typically described using templates. The current"}],"source_content_type":"text/x-gerrit-commit-message","patch_set":2,"id":"3a57f1b5_7c9caf69","line":25,"in_reply_to":"3a57f1b5_2b06fa20","updated":"2016-02-10 00:24:40.000000000","message":"Good catch. Will fix it in the next PS.","commit_id":"7ab7551948797188267ef61233aee3208d098b8f"},{"author":{"_account_id":7,"name":"Jay Pipes","email":"jaypipes@gmail.com","username":"jaypipes"},"change_message_id":"a887ee55953ee31ab44d720a64ca8dfb498dd40c","unresolved":false,"context_lines":[{"line_number":29,"context_line":"template schema of choice is TOSCA which is based on OASIS Standard [3]."},{"line_number":30,"context_line":"At this moment TOSCA has the leading mindshare across VNF vendors and"},{"line_number":31,"context_line":"operators. Tacker project is working closely with OASIS TOSCA NFV"},{"line_number":32,"context_line":"standards group to shape the evolution of its Simple Profile for NFV [4]."},{"line_number":33,"context_line":"The project is also leveraging and contributing to the Heat Translator\u0027s"},{"line_number":34,"context_line":"tosca-parser work [5]. Beyond TOSCA other templating schemes can be"},{"line_number":35,"context_line":"introduced in the future."}],"source_content_type":"text/x-gerrit-commit-message","patch_set":2,"id":"3a57f1b5_2e4b685b","line":32,"updated":"2016-02-09 20:06:43.000000000","message":"I believe \"Simple Profile for NFV\" is an oxymoron.","commit_id":"7ab7551948797188267ef61233aee3208d098b8f"},{"author":{"_account_id":13380,"name":"Sridhar Ramaswamy","email":"srics.r@gmail.com","username":"srics-r"},"change_message_id":"ad90600f8575cb7c294237351be4f483927055a7","unresolved":false,"context_lines":[{"line_number":29,"context_line":"template schema of choice is TOSCA which is based on OASIS Standard [3]."},{"line_number":30,"context_line":"At this moment TOSCA has the leading mindshare across VNF vendors and"},{"line_number":31,"context_line":"operators. Tacker project is working closely with OASIS TOSCA NFV"},{"line_number":32,"context_line":"standards group to shape the evolution of its Simple Profile for NFV [4]."},{"line_number":33,"context_line":"The project is also leveraging and contributing to the Heat Translator\u0027s"},{"line_number":34,"context_line":"tosca-parser work [5]. Beyond TOSCA other templating schemes can be"},{"line_number":35,"context_line":"introduced in the future."}],"source_content_type":"text/x-gerrit-commit-message","patch_set":2,"id":"3a57f1b5_7c902fed","line":32,"in_reply_to":"3a57f1b5_2e4b685b","updated":"2016-02-10 00:24:40.000000000","message":"That\u0027s the title OASIS TOSCA standards group is using! Perhaps they believed by putting that in the title it will constraint them to keep it simple :)","commit_id":"7ab7551948797188267ef61233aee3208d098b8f"},{"author":{"_account_id":7,"name":"Jay Pipes","email":"jaypipes@gmail.com","username":"jaypipes"},"change_message_id":"a887ee55953ee31ab44d720a64ca8dfb498dd40c","unresolved":false,"context_lines":[{"line_number":46,"context_line":"from a diverse set of participants [6] [7]. Tacker is also now actively"},{"line_number":47,"context_line":"collaborating with downstream OPNFV Projects like SFC [8], Parser [9] and"},{"line_number":48,"context_line":"Multisite [10]. Tacker functionality has been demonstrated in both"},{"line_number":49,"context_line":"OpenStack Vancouver and Tokyo Summits and in the recent OPNFV Summit."},{"line_number":50,"context_line":""},{"line_number":51,"context_line":"Tacker project strictly follows the Four Opens [11] suggested by OpenStack"},{"line_number":52,"context_line":"Foundation. Tacker code has been developed under an Apache 2.0 license."}],"source_content_type":"text/x-gerrit-commit-message","patch_set":2,"id":"3a57f1b5_4e48245c","line":49,"updated":"2016-02-09 20:06:43.000000000","message":"The above begs the question why Tacker should not just be in the OPNFV ecosystem and not the OpenStack ecosystem.","commit_id":"7ab7551948797188267ef61233aee3208d098b8f"},{"author":{"_account_id":13380,"name":"Sridhar Ramaswamy","email":"srics.r@gmail.com","username":"srics-r"},"change_message_id":"ad90600f8575cb7c294237351be4f483927055a7","unresolved":false,"context_lines":[{"line_number":46,"context_line":"from a diverse set of participants [6] [7]. Tacker is also now actively"},{"line_number":47,"context_line":"collaborating with downstream OPNFV Projects like SFC [8], Parser [9] and"},{"line_number":48,"context_line":"Multisite [10]. Tacker functionality has been demonstrated in both"},{"line_number":49,"context_line":"OpenStack Vancouver and Tokyo Summits and in the recent OPNFV Summit."},{"line_number":50,"context_line":""},{"line_number":51,"context_line":"Tacker project strictly follows the Four Opens [11] suggested by OpenStack"},{"line_number":52,"context_line":"Foundation. Tacker code has been developed under an Apache 2.0 license."}],"source_content_type":"text/x-gerrit-commit-message","patch_set":2,"id":"3a57f1b5_fcbadf6d","line":49,"in_reply_to":"3a57f1b5_4e48245c","updated":"2016-02-10 00:24:40.000000000","message":"I\u0027ll answer it in the outer comments section.","commit_id":"7ab7551948797188267ef61233aee3208d098b8f"},{"author":{"_account_id":7,"name":"Jay Pipes","email":"jaypipes@gmail.com","username":"jaypipes"},"change_message_id":"a887ee55953ee31ab44d720a64ca8dfb498dd40c","unresolved":false,"context_lines":[{"line_number":61,"context_line":"Tacker reduces such duplicate and complex effort in the industry by bringing"},{"line_number":62,"context_line":"together a community of NFV operators and VNF vendors to collaborate and"},{"line_number":63,"context_line":"build out a template based workflow engine and a higher level OpenStack"},{"line_number":64,"context_line":"\"NFV Orchestration\" API."},{"line_number":65,"context_line":""},{"line_number":66,"context_line":"[1] https://www.etsi.org/deliver/etsi_gs/NFV/001_099/002/01.02.01_60/gs_nfv002v010201p.pdf"},{"line_number":67,"context_line":"[2] https://github.com/openstack/networking-sfc"}],"source_content_type":"text/x-gerrit-commit-message","patch_set":2,"id":"3a57f1b5_ee7310b3","line":64,"updated":"2016-02-09 20:06:43.000000000","message":"It\u0027s not a RESTful HTTP API really, in my opinion. It\u0027s more of a resource definition language than anything else.","commit_id":"7ab7551948797188267ef61233aee3208d098b8f"},{"author":{"_account_id":13380,"name":"Sridhar Ramaswamy","email":"srics.r@gmail.com","username":"srics-r"},"change_message_id":"ad90600f8575cb7c294237351be4f483927055a7","unresolved":false,"context_lines":[{"line_number":61,"context_line":"Tacker reduces such duplicate and complex effort in the industry by bringing"},{"line_number":62,"context_line":"together a community of NFV operators and VNF vendors to collaborate and"},{"line_number":63,"context_line":"build out a template based workflow engine and a higher level OpenStack"},{"line_number":64,"context_line":"\"NFV Orchestration\" API."},{"line_number":65,"context_line":""},{"line_number":66,"context_line":"[1] https://www.etsi.org/deliver/etsi_gs/NFV/001_099/002/01.02.01_60/gs_nfv002v010201p.pdf"},{"line_number":67,"context_line":"[2] https://github.com/openstack/networking-sfc"}],"source_content_type":"text/x-gerrit-commit-message","patch_set":2,"id":"3a57f1b5_7c4b4fb1","line":64,"in_reply_to":"3a57f1b5_ee7310b3","updated":"2016-02-10 00:24:40.000000000","message":"Tacker needs both, a coarse grain API and VNF / Network Service definition template. \n\nIt is super valuable for an OSS/BSS system to operate at level where it can an issue APIs like \u0027Initiate this network-service with these properties\u0027, \u0027Initiate this VNF here and make sure it keeps running\u0027, etc. without worrying about the underlying VMs, networks, ports and service-chains backing them.","commit_id":"7ab7551948797188267ef61233aee3208d098b8f"}],"reference/projects.yaml":[{"author":{"_account_id":6159,"name":"Flavio Percoco Premoli","display_name":"flaper87","email":"flavio.percoco@flyrlabs.com","username":"flaper87"},"change_message_id":"4c172cd341981f510d1d4df0cd307898adbc271b","unresolved":false,"context_lines":[{"line_number":3699,"context_line":"    tacker:"},{"line_number":3700,"context_line":"      repos:"},{"line_number":3701,"context_line":"        - openstack/tacker"},{"line_number":3702,"context_line":"      tags:"},{"line_number":3703,"context_line":"        - release:independent"},{"line_number":3704,"context_line":"        - type:service"},{"line_number":3705,"context_line":"    python-tackerclient:"}],"source_content_type":"text/x-yaml","patch_set":2,"id":"5a5ae5dd_2ce7d7ad","line":3702,"updated":"2016-02-09 11:51:50.000000000","message":"Was it intentional to skip assertion tags?\n\n    - assert:follows-standard-deprecation\n    - assert:supports-(rolling-)upgrade","commit_id":"7ab7551948797188267ef61233aee3208d098b8f"},{"author":{"_account_id":308,"name":"Thierry Carrez","email":"thierry@openstack.org","username":"ttx"},"change_message_id":"40613e4cdf856493a17ac320346416d2aa412905","unresolved":false,"context_lines":[{"line_number":3699,"context_line":"    tacker:"},{"line_number":3700,"context_line":"      repos:"},{"line_number":3701,"context_line":"        - openstack/tacker"},{"line_number":3702,"context_line":"      tags:"},{"line_number":3703,"context_line":"        - release:independent"},{"line_number":3704,"context_line":"        - type:service"},{"line_number":3705,"context_line":"    python-tackerclient:"}],"source_content_type":"text/x-yaml","patch_set":2,"id":"5a5ae5dd_b12a2ee6","line":3702,"in_reply_to":"5a5ae5dd_2ce7d7ad","updated":"2016-02-09 17:22:05.000000000","message":"I suspect it is. Can be done as a second pass.","commit_id":"7ab7551948797188267ef61233aee3208d098b8f"},{"author":{"_account_id":6159,"name":"Flavio Percoco Premoli","display_name":"flaper87","email":"flavio.percoco@flyrlabs.com","username":"flaper87"},"change_message_id":"265b8167627b2844ef41d1f9f47b049a76e4abe0","unresolved":false,"context_lines":[{"line_number":3699,"context_line":"    tacker:"},{"line_number":3700,"context_line":"      repos:"},{"line_number":3701,"context_line":"        - openstack/tacker"},{"line_number":3702,"context_line":"      tags:"},{"line_number":3703,"context_line":"        - release:independent"},{"line_number":3704,"context_line":"        - type:service"},{"line_number":3705,"context_line":"    python-tackerclient:"}],"source_content_type":"text/x-yaml","patch_set":2,"id":"3a57f1b5_b939e343","line":3702,"in_reply_to":"5a5ae5dd_b12a2ee6","updated":"2016-02-09 19:32:27.000000000","message":"Sure but no voting has been done yet, I new PS wouldn\u0027t harm.","commit_id":"7ab7551948797188267ef61233aee3208d098b8f"},{"author":{"_account_id":6159,"name":"Flavio Percoco Premoli","display_name":"flaper87","email":"flavio.percoco@flyrlabs.com","username":"flaper87"},"change_message_id":"4c172cd341981f510d1d4df0cd307898adbc271b","unresolved":false,"context_lines":[{"line_number":3700,"context_line":"      repos:"},{"line_number":3701,"context_line":"        - openstack/tacker"},{"line_number":3702,"context_line":"      tags:"},{"line_number":3703,"context_line":"        - release:independent"},{"line_number":3704,"context_line":"        - type:service"},{"line_number":3705,"context_line":"    python-tackerclient:"},{"line_number":3706,"context_line":"      repos:"}],"source_content_type":"text/x-yaml","patch_set":2,"id":"5a5ae5dd_acfbc746","line":3703,"updated":"2016-02-09 11:51:50.000000000","message":"I see it has stable branches, I believe you should also add:\n\n    - release:has-stable-branches\n\nThat said, I\u0027m not sure having stable branches works well with the `release:independent` model. What I mean is, for this model to work you would have to release a final tag at the end of the cycle where stable branches will cut off from. If you guys do that, that\u0027s basically doing a `release:cycle-with-intermediary`[0]. I\u0027ll let release managers elaborate more on this and correct me if I\u0027m wrong.\n\n[0] http://governance.openstack.org/reference/tags/release_cycle-with-intermediary.html","commit_id":"7ab7551948797188267ef61233aee3208d098b8f"},{"author":{"_account_id":13380,"name":"Sridhar Ramaswamy","email":"srics.r@gmail.com","username":"srics-r"},"change_message_id":"fee24af53f628ea8cb6b0a7bac12fff839aea351","unresolved":false,"context_lines":[{"line_number":3700,"context_line":"      repos:"},{"line_number":3701,"context_line":"        - openstack/tacker"},{"line_number":3702,"context_line":"      tags:"},{"line_number":3703,"context_line":"        - release:independent"},{"line_number":3704,"context_line":"        - type:service"},{"line_number":3705,"context_line":"    python-tackerclient:"},{"line_number":3706,"context_line":"      repos:"}],"source_content_type":"text/x-yaml","patch_set":2,"id":"3a57f1b5_19e597a7","line":3703,"in_reply_to":"5a5ae5dd_111d42bd","updated":"2016-02-09 19:42:14.000000000","message":"@Flavio, @Thierry \n\nThe team had a discussion on the targets for current release in our weekly irc meeting [1]. There is a general consensus we will be able to stick to the mitaka release deadlines. So I\u0027ll switch the tag from \u0027release:independent\u0027 to \u0027release:cycle-with-intermediary\u0027 in the next patchset. \n\n\n[1] http://eavesdrop.openstack.org/meetings/tacker/2016/tacker.2016-02-09-17.00.log.html","commit_id":"7ab7551948797188267ef61233aee3208d098b8f"},{"author":{"_account_id":308,"name":"Thierry Carrez","email":"thierry@openstack.org","username":"ttx"},"change_message_id":"40613e4cdf856493a17ac320346416d2aa412905","unresolved":false,"context_lines":[{"line_number":3700,"context_line":"      repos:"},{"line_number":3701,"context_line":"        - openstack/tacker"},{"line_number":3702,"context_line":"      tags:"},{"line_number":3703,"context_line":"        - release:independent"},{"line_number":3704,"context_line":"        - type:service"},{"line_number":3705,"context_line":"    python-tackerclient:"},{"line_number":3706,"context_line":"      repos:"}],"source_content_type":"text/x-yaml","patch_set":2,"id":"5a5ae5dd_111d42bd","line":3703,"in_reply_to":"5a5ae5dd_acfbc746","updated":"2016-02-09 17:22:05.000000000","message":"We are deprecating usage of the has-stable-branches tag, so I wouldn\u0027t hold them on it.","commit_id":"7ab7551948797188267ef61233aee3208d098b8f"}]}
