)]}'
{"/COMMIT_MSG":[{"author":{"_account_id":23186,"name":"Felipe Monteiro","email":"felipe.carneiro.monteiro@gmail.com","username":"felipe.monteiro"},"change_message_id":"29c610c31a5336e4b93e73a1628aea9244f7dd00","unresolved":false,"context_lines":[{"line_number":12,"context_line":""},{"line_number":13,"context_line":"The Airship Treasuremap project will serve these purposes:"},{"line_number":14,"context_line":""},{"line_number":15,"context_line":"1. House reference deployment manifests that can be used as a"},{"line_number":16,"context_line":"starting point for setting up an Airship site.  The YAML"},{"line_number":17,"context_line":"manifests will be self-documented so that the settings that"},{"line_number":18,"context_line":"typically vary on a site-by-site basis can be easily found."}],"source_content_type":"text/x-gerrit-commit-message","patch_set":1,"id":"3f79a3b5_a83beae8","line":15,"range":{"start_line":15,"start_character":3,"end_line":15,"end_character":39},"updated":"2018-08-09 23:39:15.000000000","message":"What will happen to airship-in-a-bottle manifests? Will Treasuremap absorb them? If not, what types of manifests belong in Treasuremap and which in the other project?","commit_id":"a3a365a3e55e43a8dd23077bc7c27edf9ad58dbe"},{"author":{"_account_id":22477,"name":"Matt McEuen","email":"matt.mceuen@att.com","username":"mattmceuen"},"change_message_id":"ea853a9381b56b9eed5d8bef634549e50a9352c4","unresolved":false,"context_lines":[{"line_number":12,"context_line":""},{"line_number":13,"context_line":"The Airship Treasuremap project will serve these purposes:"},{"line_number":14,"context_line":""},{"line_number":15,"context_line":"1. House reference deployment manifests that can be used as a"},{"line_number":16,"context_line":"starting point for setting up an Airship site.  The YAML"},{"line_number":17,"context_line":"manifests will be self-documented so that the settings that"},{"line_number":18,"context_line":"typically vary on a site-by-site basis can be easily found."}],"source_content_type":"text/x-gerrit-commit-message","patch_set":1,"id":"3f79a3b5_246137d4","line":15,"range":{"start_line":15,"start_character":3,"end_line":15,"end_character":39},"in_reply_to":"3f79a3b5_a83beae8","updated":"2018-08-10 13:47:49.000000000","message":"Still needs to be figured out a bit.  We were going to discuss in last week\u0027s team meeting but ran out of time for much depth; an initial thought would be that aiab would be dev-centric and treasuremap would be operatro/integration/reference architecture-centric; however I think it should be discussed more since it may make sense to simply combine the docs into the same repo.","commit_id":"a3a365a3e55e43a8dd23077bc7c27edf9ad58dbe"},{"author":{"_account_id":23186,"name":"Felipe Monteiro","email":"felipe.carneiro.monteiro@gmail.com","username":"felipe.monteiro"},"change_message_id":"29c610c31a5336e4b93e73a1628aea9244f7dd00","unresolved":false,"context_lines":[{"line_number":18,"context_line":"typically vary on a site-by-site basis can be easily found."},{"line_number":19,"context_line":""},{"line_number":20,"context_line":"2. CICD pipelines that will integrate the reference manifests,"},{"line_number":21,"context_line":"the various Airship components, and OpenStack (via OpenStack-Helm)"},{"line_number":22,"context_line":"to ensure that the manifests are always up-to-date and that"},{"line_number":23,"context_line":"changes to Airship and OpenStack-Helm do not result in an"},{"line_number":24,"context_line":"integration regression."}],"source_content_type":"text/x-gerrit-commit-message","patch_set":1,"id":"3f79a3b5_c83e66d9","line":21,"range":{"start_line":21,"start_character":46,"end_line":21,"end_character":66},"updated":"2018-08-09 23:39:15.000000000","message":"Does this mean OpenStack-Helm itself or just its toolkit? I noticed Airskiff or whatever you called it :)","commit_id":"a3a365a3e55e43a8dd23077bc7c27edf9ad58dbe"},{"author":{"_account_id":22477,"name":"Matt McEuen","email":"matt.mceuen@att.com","username":"mattmceuen"},"change_message_id":"ea853a9381b56b9eed5d8bef634549e50a9352c4","unresolved":false,"context_lines":[{"line_number":18,"context_line":"typically vary on a site-by-site basis can be easily found."},{"line_number":19,"context_line":""},{"line_number":20,"context_line":"2. CICD pipelines that will integrate the reference manifests,"},{"line_number":21,"context_line":"the various Airship components, and OpenStack (via OpenStack-Helm)"},{"line_number":22,"context_line":"to ensure that the manifests are always up-to-date and that"},{"line_number":23,"context_line":"changes to Airship and OpenStack-Helm do not result in an"},{"line_number":24,"context_line":"integration regression."}],"source_content_type":"text/x-gerrit-commit-message","patch_set":1,"id":"3f79a3b5_84adabea","line":21,"range":{"start_line":21,"start_character":46,"end_line":21,"end_character":66},"in_reply_to":"3f79a3b5_c83e66d9","updated":"2018-08-10 13:47:49.000000000","message":"My understanding is we\u0027re going to stand up a full Seaworthy stack in this CICD, including a full OpenStack -- this will be really good from a continuous integration standpoint since it\u0027ll combine not just Airship, but Airship + OSH-based workload.","commit_id":"a3a365a3e55e43a8dd23077bc7c27edf9ad58dbe"}],"gerrit/projects.yaml":[{"author":{"_account_id":6547,"name":"Andreas Jaeger","email":"jaegerandi@gmail.com","username":"jaegerandi"},"change_message_id":"daed8814477774c251cec1780d9d3c3a93154f1c","unresolved":false,"context_lines":[{"line_number":1015,"context_line":"- project: openstack/airship-treasuremap"},{"line_number":1016,"context_line":"  description: Reference Airship manifests, CICD, and reference architecture."},{"line_number":1017,"context_line":"  use-storyboard: true"},{"line_number":1018,"context_line":"  acl-config: /home/gerrit2/acls/openstack/airship.config"},{"line_number":1019,"context_line":"  groups:"},{"line_number":1020,"context_line":"    - airship"},{"line_number":1021,"context_line":"  cgit-alias:"}],"source_content_type":"text/x-yaml","patch_set":1,"id":"3f79a3b5_277b84be","line":1018,"updated":"2018-08-10 04:51:42.000000000","message":"do you have initial content to import?","commit_id":"a3a365a3e55e43a8dd23077bc7c27edf9ad58dbe"},{"author":{"_account_id":22477,"name":"Matt McEuen","email":"matt.mceuen@att.com","username":"mattmceuen"},"change_message_id":"ea853a9381b56b9eed5d8bef634549e50a9352c4","unresolved":false,"context_lines":[{"line_number":1015,"context_line":"- project: openstack/airship-treasuremap"},{"line_number":1016,"context_line":"  description: Reference Airship manifests, CICD, and reference architecture."},{"line_number":1017,"context_line":"  use-storyboard: true"},{"line_number":1018,"context_line":"  acl-config: /home/gerrit2/acls/openstack/airship.config"},{"line_number":1019,"context_line":"  groups:"},{"line_number":1020,"context_line":"    - airship"},{"line_number":1021,"context_line":"  cgit-alias:"}],"source_content_type":"text/x-yaml","patch_set":1,"id":"3f79a3b5_c4808349","line":1018,"in_reply_to":"3f79a3b5_277b84be","updated":"2018-08-10 13:47:49.000000000","message":"Not quite yet, but very shortly -- it\u0027s under internal review today.  Would it be better to wait for the content to available before pulling the trigger on the new repo, or does it not matter?  We can either push straight into openstack infra, or we can stage it in github first.","commit_id":"a3a365a3e55e43a8dd23077bc7c27edf9ad58dbe"},{"author":{"_account_id":4146,"name":"Clark Boylan","email":"cboylan@sapwetik.org","username":"cboylan"},"change_message_id":"b4bd5633953577ee9b4ec494560bf67cbf09fe10","unresolved":false,"context_lines":[{"line_number":1015,"context_line":"- project: openstack/airship-treasuremap"},{"line_number":1016,"context_line":"  description: Reference Airship manifests, CICD, and reference architecture."},{"line_number":1017,"context_line":"  use-storyboard: true"},{"line_number":1018,"context_line":"  acl-config: /home/gerrit2/acls/openstack/airship.config"},{"line_number":1019,"context_line":"  groups:"},{"line_number":1020,"context_line":"    - airship"},{"line_number":1021,"context_line":"  cgit-alias:"}],"source_content_type":"text/x-yaml","patch_set":1,"id":"3f79a3b5_8f5efb73","line":1018,"in_reply_to":"3f79a3b5_c4808349","updated":"2018-08-13 17:55:41.000000000","message":"If it is a significant number of commits that you do not want to put through code review then adding it as part of the initial import is helpful. Otherwise you can push once the repo is created in Gerrit and get things merged through normal process.","commit_id":"a3a365a3e55e43a8dd23077bc7c27edf9ad58dbe"}]}