)]}'
{"doc/source/specs/neutron-multiple-sdns.rst":[{"author":{"_account_id":15518,"name":"Artur Korzeniewski","email":"artur.korzen@wp.pl","username":"akorzeni"},"change_message_id":"8ca38f364994895e256a62f94e368c5b3111f51a","unresolved":false,"context_lines":[{"line_number":126,"context_line":""},{"line_number":127,"context_line":".. code-block:: yaml"},{"line_number":128,"context_line":""},{"line_number":129,"context_line":"    manifests:"},{"line_number":130,"context_line":"      # neutron-server components:"},{"line_number":131,"context_line":"      configmap_bin: true"},{"line_number":132,"context_line":"      configmap_etc: true"}],"source_content_type":"text/x-rst","patch_set":1,"id":"df3967d1_38073a1b","line":129,"range":{"start_line":129,"start_character":4,"end_line":129,"end_character":13},"updated":"2017-08-03 09:34:31.000000000","message":"I was wondering of consistency between charts. I have spotted that in ceph chart there is already merged manifests_enabled section:\nhttps://github.com/openstack/openstack-helm/blob/master/ceph/values.yaml#L15\n\nShould we unify to manifests_enabled or simply manifests?\nI see that manifests_enabled has more precise meaning, but it would make \u0027if\u0027 statements longer.","commit_id":"2cec4381672fc11f86dbf577fb4c61f6607be2d6"},{"author":{"_account_id":11636,"name":"Mateusz Blaszkowski","email":"mateusz.blaszkowski@intel.com","username":"mateuszb"},"change_message_id":"fb0204ef26ec004bddd489577cd9633772585c52","unresolved":false,"context_lines":[{"line_number":133,"context_line":"      deployment_server: true"},{"line_number":134,"context_line":"      ingress_server: true"},{"line_number":135,"context_line":"      job_db_init: true"},{"line_number":136,"context_line":"      job_db_sync: true"},{"line_number":137,"context_line":"      job_ks_endpoints: true"},{"line_number":138,"context_line":"      job_ks_service: true"},{"line_number":139,"context_line":"      job_ks_user: true"}],"source_content_type":"text/x-rst","patch_set":1,"id":"df3967d1_e480ee48","line":136,"updated":"2017-08-03 09:04:10.000000000","message":"Just wondered if there is a need to parametrize all of the templates. Some of them have to be present independently of the chosen SDN network - is that right?","commit_id":"2cec4381672fc11f86dbf577fb4c61f6607be2d6"},{"author":{"_account_id":15518,"name":"Artur Korzeniewski","email":"artur.korzen@wp.pl","username":"akorzeni"},"change_message_id":"8ca38f364994895e256a62f94e368c5b3111f51a","unresolved":false,"context_lines":[{"line_number":133,"context_line":"      deployment_server: true"},{"line_number":134,"context_line":"      ingress_server: true"},{"line_number":135,"context_line":"      job_db_init: true"},{"line_number":136,"context_line":"      job_db_sync: true"},{"line_number":137,"context_line":"      job_ks_endpoints: true"},{"line_number":138,"context_line":"      job_ks_service: true"},{"line_number":139,"context_line":"      job_ks_user: true"}],"source_content_type":"text/x-rst","patch_set":1,"id":"df3967d1_18a8f6d8","line":136,"in_reply_to":"df3967d1_e480ee48","updated":"2017-08-03 09:34:31.000000000","message":"All variables here are neutron-server specific. It should be always enabled, as neutron-server is always required. Unless someone would like to override the default jobs with some more detailed SDN\u0027s specific requirement.\nI have suggested in review in [1] we can make this as one variable neutron-server. It would be somehow easier to understand but less flexible. I\u0027m ok with implementing it with multiple variables, as it would be ready for all kind of modifications inside neutron base chart.\n\n[1] https://review.openstack.org/#/c/481225/2","commit_id":"2cec4381672fc11f86dbf577fb4c61f6607be2d6"},{"author":{"_account_id":11600,"name":"Michał Dulko","email":"michal.dulko@gmail.com","username":"dulek"},"change_message_id":"4fb828e91e6c3935aaa174034c5cba4ac27de67d","unresolved":false,"context_lines":[{"line_number":154,"context_line":"      daemonset_l3_agent: false"},{"line_number":155,"context_line":"      daemonset_metadata_agent: false"},{"line_number":156,"context_line":""},{"line_number":157,"context_line":"Provision of those services should be included inside SDN chart."},{"line_number":158,"context_line":""},{"line_number":159,"context_line":"The last thing to be considered is VM network virtualization. What engine does"},{"line_number":160,"context_line":"SDN use? It is OpenVSwitch, Linux Bridges or l3 routing (no l2 connectivity)."}],"source_content_type":"text/x-rst","patch_set":1,"id":"df3967d1_0f6018ce","line":157,"range":{"start_line":157,"start_character":54,"end_line":157,"end_character":64},"updated":"2017-07-31 13:44:21.000000000","message":"Judging from implementation you mean SDN resource definitions, not a new Chart as a new Chart.yaml.","commit_id":"2cec4381672fc11f86dbf577fb4c61f6607be2d6"},{"author":{"_account_id":15518,"name":"Artur Korzeniewski","email":"artur.korzen@wp.pl","username":"akorzeni"},"change_message_id":"6f5f190d5544d51dcfb7a7f6113c405eac38f85a","unresolved":false,"context_lines":[{"line_number":154,"context_line":"      daemonset_l3_agent: false"},{"line_number":155,"context_line":"      daemonset_metadata_agent: false"},{"line_number":156,"context_line":""},{"line_number":157,"context_line":"Provision of those services should be included inside SDN chart."},{"line_number":158,"context_line":""},{"line_number":159,"context_line":"The last thing to be considered is VM network virtualization. What engine does"},{"line_number":160,"context_line":"SDN use? It is OpenVSwitch, Linux Bridges or l3 routing (no l2 connectivity)."}],"source_content_type":"text/x-rst","patch_set":1,"id":"df3967d1_9279ba94","line":157,"range":{"start_line":157,"start_character":54,"end_line":157,"end_character":64},"in_reply_to":"df3967d1_0f6018ce","updated":"2017-08-01 06:38:44.000000000","message":"I mean separate chart as a new Chart.yaml. Setting up the SDN controller would require spinning a new API, bootstrapping DB and other services. This kind of enhancements would not fit into singular Neutron chart. My opinion is that new services should be put in separate charts, outside of neutron base one.","commit_id":"2cec4381672fc11f86dbf577fb4c61f6607be2d6"},{"author":{"_account_id":15518,"name":"Artur Korzeniewski","email":"artur.korzen@wp.pl","username":"akorzeni"},"change_message_id":"73ad481d485c6409737b8f8d1117ce6b647e8961","unresolved":false,"context_lines":[{"line_number":154,"context_line":"      daemonset_l3_agent: false"},{"line_number":155,"context_line":"      daemonset_metadata_agent: false"},{"line_number":156,"context_line":""},{"line_number":157,"context_line":"Provision of those services should be included inside SDN chart."},{"line_number":158,"context_line":""},{"line_number":159,"context_line":"The last thing to be considered is VM network virtualization. What engine does"},{"line_number":160,"context_line":"SDN use? It is OpenVSwitch, Linux Bridges or l3 routing (no l2 connectivity)."}],"source_content_type":"text/x-rst","patch_set":1,"id":"df3967d1_727e566c","line":157,"range":{"start_line":157,"start_character":54,"end_line":157,"end_character":64},"in_reply_to":"df3967d1_9279ba94","updated":"2017-08-01 06:41:30.000000000","message":"Creation of separate chart is also stated in lines 108-110 of this spec:\nhttps://review.openstack.org/#/c/487427/1/doc/source/specs/neutron-multiple-sdns.rst@110","commit_id":"2cec4381672fc11f86dbf577fb4c61f6607be2d6"}]}