)]}'
{"toci-quickstart/config/testenv/ovb.yml":[{"author":{"_account_id":4162,"name":"Paul Belanger","email":"pabelanger@redhat.com","username":"pabelanger"},"change_message_id":"d78c7f98253bc287ffb6e85b335cd1ed3b078d27","unresolved":false,"context_lines":[{"line_number":48,"context_line":"  {%- else %}192.168.24.0/24"},{"line_number":49,"context_line":"  {%- endif %}"},{"line_number":50,"context_line":"ara_graphite_prefix: \"test.tripleo.{{ lookup(\u0027env\u0027, \u0027STABLE_RELEASE\u0027)|default(\u0027master\u0027, true) }}.{{ lookup(\u0027env\u0027, \u0027TOCI_JOBTYPE\u0027) }}.\""},{"line_number":51,"context_line":"ara_graphite_server: 66.187.229.172"}],"source_content_type":"text/x-yaml","patch_set":5,"id":"9f436f4f_1dd332d7","line":51,"updated":"2017-08-14 17:43:40.000000000","message":"who\u0027s graphite server is this? Looks like private infrastructure, which jobs shouldn\u0027t depend on.","commit_id":"93dc7a9a479e7bad121c9d2503801fd7bc02780a"},{"author":{"_account_id":10969,"name":"Shnaidman Sagi (Sergey)","display_name":"Shnaidman Sagi","email":"sshnaidm@redhat.com","username":"sergsh"},"change_message_id":"45fa85c26867cb77687c8dfa03b9924b51d6f9d5","unresolved":false,"context_lines":[{"line_number":48,"context_line":"  {%- else %}192.168.24.0/24"},{"line_number":49,"context_line":"  {%- endif %}"},{"line_number":50,"context_line":"ara_graphite_prefix: \"test.tripleo.{{ lookup(\u0027env\u0027, \u0027STABLE_RELEASE\u0027)|default(\u0027master\u0027, true) }}.{{ lookup(\u0027env\u0027, \u0027TOCI_JOBTYPE\u0027) }}.\""},{"line_number":51,"context_line":"ara_graphite_server: 66.187.229.172"}],"source_content_type":"text/x-yaml","patch_set":5,"id":"9f436f4f_2d1a436e","line":51,"in_reply_to":"9f436f4f_1dd332d7","updated":"2017-08-14 20:24:56.000000000","message":"It\u0027s not private infrastructure, it\u0027s graphite.tripleo.org on RH1 cloud.","commit_id":"93dc7a9a479e7bad121c9d2503801fd7bc02780a"},{"author":{"_account_id":4162,"name":"Paul Belanger","email":"pabelanger@redhat.com","username":"pabelanger"},"change_message_id":"bea4be7abbc07e6b3d98c507bb975309f63e10b5","unresolved":false,"context_lines":[{"line_number":48,"context_line":"  {%- else %}192.168.24.0/24"},{"line_number":49,"context_line":"  {%- endif %}"},{"line_number":50,"context_line":"ara_graphite_prefix: \"test.tripleo.{{ lookup(\u0027env\u0027, \u0027STABLE_RELEASE\u0027)|default(\u0027master\u0027, true) }}.{{ lookup(\u0027env\u0027, \u0027TOCI_JOBTYPE\u0027) }}.\""},{"line_number":51,"context_line":"ara_graphite_server: 66.187.229.172"}],"source_content_type":"text/x-yaml","patch_set":5,"id":"9f436f4f_822456b0","line":51,"in_reply_to":"9f436f4f_2d1a436e","updated":"2017-08-15 02:56:50.000000000","message":"I say private, because it is not community managed.  If the tripleo project needs access to graphite server, we sure consider graphite.openstack.org.\n\nIs there a spec about what you plan on using the data for?","commit_id":"93dc7a9a479e7bad121c9d2503801fd7bc02780a"},{"author":{"_account_id":10969,"name":"Shnaidman Sagi (Sergey)","display_name":"Shnaidman Sagi","email":"sshnaidm@redhat.com","username":"sergsh"},"change_message_id":"da9c47b0882020b2028b530e15f12ecb6a3897d0","unresolved":false,"context_lines":[{"line_number":48,"context_line":"  {%- else %}192.168.24.0/24"},{"line_number":49,"context_line":"  {%- endif %}"},{"line_number":50,"context_line":"ara_graphite_prefix: \"test.tripleo.{{ lookup(\u0027env\u0027, \u0027STABLE_RELEASE\u0027)|default(\u0027master\u0027, true) }}.{{ lookup(\u0027env\u0027, \u0027TOCI_JOBTYPE\u0027) }}.\""},{"line_number":51,"context_line":"ara_graphite_server: 66.187.229.172"}],"source_content_type":"text/x-yaml","patch_set":5,"id":"9f436f4f_f970740a","line":51,"in_reply_to":"9f436f4f_822456b0","updated":"2017-08-15 06:13:49.000000000","message":"@Paul, everything in RH1 is managed by tripleo-ci squad only, including proxy, mirror server, te-broker, etc etc. graphite is used a long time for time tracking of tripleo deployment parts. I don\u0027t understand what is the problem now. Which spec are you talking about? This data is actually for tracking logs sizes so that we can handle problems with it. It\u0027s tripleo internal things,  I don\u0027t want to use graphite.openstack.org.","commit_id":"93dc7a9a479e7bad121c9d2503801fd7bc02780a"},{"author":{"_account_id":10969,"name":"Shnaidman Sagi (Sergey)","display_name":"Shnaidman Sagi","email":"sshnaidm@redhat.com","username":"sergsh"},"change_message_id":"72c848b1dabbe8874c11300a029dc8bb8273b40f","unresolved":false,"context_lines":[{"line_number":48,"context_line":"  {%- else %}192.168.24.0/24"},{"line_number":49,"context_line":"  {%- endif %}"},{"line_number":50,"context_line":"ara_graphite_prefix: \"test.tripleo.{{ lookup(\u0027env\u0027, \u0027STABLE_RELEASE\u0027)|default(\u0027master\u0027, true) }}.{{ lookup(\u0027env\u0027, \u0027TOCI_JOBTYPE\u0027) }}.\""},{"line_number":51,"context_line":"ara_graphite_server: 66.187.229.172"}],"source_content_type":"text/x-yaml","patch_set":5,"id":"9f436f4f_13475179","line":51,"in_reply_to":"9f436f4f_914ed4be","updated":"2017-08-17 12:11:20.000000000","message":"@Paul, all this sounds reasonable and would be better to discuss in tripleo meeting or mail list. But it\u0027s not related to this particular case.\n\nGraphite server is passive monitoring server, that can\u0027t affect jobs in any way and you don\u0027t need fix it.\n\nIt\u0027s not related to subunit in any way, subunit is only for tests results, graphite collects metrics. Also openstack-health tracks subunit files only for gate and periodic pipelines, that makes it completely unusable in this case.\n\nMerging our patches to infra has so many problems, both political and technical, that it could be years until patch is merged and I don\u0027t want to wait so long to track time for some additional step. I\u0027d agree to set up it in grahite.o.o only if we (tripleo cores) have rights to merge there.\n\nOtherwise I don\u0027t see any reason for using graphite.o.o for some internal tripleo-related only stuff, that is flexible and manageable by us right now.","commit_id":"93dc7a9a479e7bad121c9d2503801fd7bc02780a"},{"author":{"_account_id":4162,"name":"Paul Belanger","email":"pabelanger@redhat.com","username":"pabelanger"},"change_message_id":"2e9708cb1fc56cb66fae5414fccbe0628c4ff71f","unresolved":false,"context_lines":[{"line_number":48,"context_line":"  {%- else %}192.168.24.0/24"},{"line_number":49,"context_line":"  {%- endif %}"},{"line_number":50,"context_line":"ara_graphite_prefix: \"test.tripleo.{{ lookup(\u0027env\u0027, \u0027STABLE_RELEASE\u0027)|default(\u0027master\u0027, true) }}.{{ lookup(\u0027env\u0027, \u0027TOCI_JOBTYPE\u0027) }}.\""},{"line_number":51,"context_line":"ara_graphite_server: 66.187.229.172"}],"source_content_type":"text/x-yaml","patch_set":5,"id":"9f436f4f_914ed4be","line":51,"in_reply_to":"9f436f4f_f970740a","updated":"2017-08-15 14:39:19.000000000","message":"Yes, this has been a issue for a while now. Please see:\n\n  http://lists.openstack.org/pipermail/openstack-dev/2016-March/088445.html\n  http://lists.openstack.org/pipermail/openstack-dev/2016-May/094154.html\n\nThe idea is, these server are private infrastructure, they do not use our existing tooling in openstack-infra and right now, I have no access to them.  So, if there is something wrong with a tripleo jobs in tripleo-test-cloud-rh1, I cannot help fix it.\n\nTripleo has made great process in the last 18months, by embracing more of the community infrastructure, but things like the \u0027proxy mirror\u0027 needs to be deleted. This should now be covered by our AFS mirrors (mirror.tripleo-test-cloud-rh1) and stuff that is missing, we should propose changes to openstack-infra/system-config and add them.\n\nSame for graphite, we have a graphite.o.o server already, we should be talking with openstack-infra about using that service, rather then needlessly standing up another server and having to manage it.  The reason I ask for a spec, is because I want to see what data you are tracking. Could this data be tracked in subunit and parsed by openstack-health.\n\nte-broker will likely go a way in zuulv3, and we should see how to replace it. This could be managed directly in nodepool now, which means writing a new driver if needed.\n\nSo, this isn\u0027t something that is new, and been much work to stop services from depending on only tripleo-test-cloud-rh1.\n\nI am more then happy to help work with the team and see what we need to do to stop using the private infrastructure.","commit_id":"93dc7a9a479e7bad121c9d2503801fd7bc02780a"}]}