)]}'
{"octavia/amphorae/backends/agent/api_server/templates/amphora-netns.systemd.j2":[{"author":{"_account_id":11628,"name":"Michael Johnson","email":"johnsomor@gmail.com","username":"johnsom"},"change_message_id":"1522d76a95df2f2998163e095dacf0bf0fcf6082","unresolved":false,"context_lines":[{"line_number":7,"context_line":"RemainAfterExit\u003dyes"},{"line_number":8,"context_line":""},{"line_number":9,"context_line":"# Re-add the namespace"},{"line_number":10,"context_line":"ExecStart\u003d-/sbin/ip netns add %i"},{"line_number":11,"context_line":"# Load the system sysctl into the new namespace"},{"line_number":12,"context_line":"ExecStart\u003d-/sbin/ip netns exec %i sysctl --system"},{"line_number":13,"context_line":"# We need the plugged_interfaces file sorted to join the host interfaces"}],"source_content_type":"text/x-jinja2","patch_set":3,"id":"ff82abbf_eb476f4b","line":10,"range":{"start_line":10,"start_character":30,"end_line":10,"end_character":32},"updated":"2017-11-27 22:40:59.000000000","message":"I\u0027m not a huge fan of using this, especially since it is already rendered by jinja.\nI won\u0027t -1 it, but consider if we really think this will be reused or not.\nIt just seems confusing for developers that are not systemd experts and understand the templating tricks here.","commit_id":"ef51cf12e1bfa2cdf1a0bc175a81b44d18696088"},{"author":{"_account_id":21798,"name":"Bernard Cafarelli","email":"bcafarel@redhat.com","username":"bcafarel"},"change_message_id":"6e11320cd1adf69e6f20c773964fae8ae415766b","unresolved":false,"context_lines":[{"line_number":7,"context_line":"RemainAfterExit\u003dyes"},{"line_number":8,"context_line":""},{"line_number":9,"context_line":"# Re-add the namespace"},{"line_number":10,"context_line":"ExecStart\u003d-/sbin/ip netns add %i"},{"line_number":11,"context_line":"# Load the system sysctl into the new namespace"},{"line_number":12,"context_line":"ExecStart\u003d-/sbin/ip netns exec %i sysctl --system"},{"line_number":13,"context_line":"# We need the plugged_interfaces file sorted to join the host interfaces"}],"source_content_type":"text/x-jinja2","patch_set":3,"id":"ff82abbf_90436442","line":10,"range":{"start_line":10,"start_character":30,"end_line":10,"end_character":32},"in_reply_to":"ff82abbf_eb476f4b","updated":"2017-11-28 10:29:55.000000000","message":"Good point, my initial plan was to have this file installed without a need for jinja templating, so I used the @/%i feature.\n\nSince it has to be templated anyway for HasIFUPAll, I can move the namespace name to the Jinja template too","commit_id":"ef51cf12e1bfa2cdf1a0bc175a81b44d18696088"}],"octavia/amphorae/backends/agent/api_server/templates/systemd.conf.j2":[{"author":{"_account_id":8161,"name":"Lon Hohberger","email":"lhh@redhat.com","username":"lon"},"change_message_id":"b7b91af643ff8f16978243559b269e9c037ff3dc","unresolved":false,"context_lines":[{"line_number":9,"context_line":""},{"line_number":10,"context_line":"[Service]"},{"line_number":11,"context_line":"# Force context as we start haproxy under \"ip netns exec\""},{"line_number":12,"context_line":"SELinuxContext\u003dsystem_u:system_r:haproxy_t:s0"},{"line_number":13,"context_line":"EnvironmentFile\u003d-/etc/default/haproxy"},{"line_number":14,"context_line":"ExecStartPre\u003d/usr/sbin/haproxy -f {{ haproxy_cfg }} -f {{ haproxy_user_group_cfg }} -c -q"},{"line_number":15,"context_line":"ExecStart\u003d/sbin/ip netns exec {{ amphora_nsname }} /usr/sbin/haproxy-systemd-wrapper -f {{ haproxy_cfg }} -f {{ haproxy_user_group_cfg }} -p {{ haproxy_pid }} -L {{ peer_name }} $EXTRAOPTS"}],"source_content_type":"text/x-jinja2","patch_set":4,"id":"ff82abbf_36f8027b","line":12,"updated":"2017-11-30 20:40:10.000000000","message":"I\u0027m curious as to whether \u0027ip netns\u0027 will execute under the right context to do its setup prior to executing haproxy.\n\nIf not, we can simply write a domain transition for ifconfig_t -\u003e haproxy_t","commit_id":"87eeba639744dbbb6bc4288c2cb3db73fb9c8fd1"}]}
