)]}'
{"/COMMIT_MSG":[{"author":{"_account_id":25402,"name":"Francesco Pantano","email":"fpantano@redhat.com","username":"fmount"},"change_message_id":"5ed38ee1997a81ed05ed8bfa51a8efbc5e1ba81c","unresolved":false,"context_lines":[{"line_number":4,"context_line":"Commit:     Giulio Fidente \u003cgfidente@redhat.com\u003e"},{"line_number":5,"context_line":"CommitDate: 2020-10-23 12:40:28 +0200"},{"line_number":6,"context_line":""},{"line_number":7,"context_line":"ntroduce tripleo-ceph-ganesha spec"},{"line_number":8,"context_line":""},{"line_number":9,"context_line":"Change-Id: I81c4219d30bcb7a65e20717cee62595d7a4e0064"}],"source_content_type":"text/x-gerrit-commit-message","patch_set":1,"id":"3f65232a_e2b6d3d9","line":7,"range":{"start_line":7,"start_character":0,"end_line":7,"end_character":1},"updated":"2020-10-23 11:01:19.000000000","message":"s/ntroduce/Introduce/ :D","commit_id":"6ab3a56821164d6db12a272d2343b7a2bfdf97a5"}],"specs/wallaby/tripleo-ceph-ganesha.rst":[{"author":{"_account_id":18002,"name":"John Fulton","email":"fulton@redhat.com","username":"fultonj"},"change_message_id":"c6e299508c366077b02fe2545a05e157ddc2aa2f","unresolved":false,"context_lines":[{"line_number":133,"context_line":""},{"line_number":134,"context_line":"Work Items"},{"line_number":135,"context_line":"----------"},{"line_number":136,"context_line":"- Create https://github.com/redhat-openstack/ganesha-ansible repository"},{"line_number":137,"context_line":"- Import `ceph-ansible/roles/ceph-nfs/` and modify it to run independently"},{"line_number":138,"context_line":"- Work with RDO to get RPM built for ganesha-ansible"},{"line_number":139,"context_line":"- Document how to install optional ganesha-ansible RPM on undercloud"}],"source_content_type":"text/x-rst","patch_set":3,"id":"1f621f24_1f76e607","line":136,"range":{"start_line":136,"start_character":2,"end_line":136,"end_character":67},"updated":"2020-10-28 16:04:16.000000000","message":"rpm could be a dep of tripleo-ansible or tripleo-ceph rpm","commit_id":"ef2137f476f0fe83703111535264828749104807"},{"author":{"_account_id":9003,"name":"Tom Barron","email":"tpb@dyncloud.net","username":"tbarron"},"change_message_id":"520f9b1b409a697867cdd6aef45f0871d21f678e","unresolved":true,"context_lines":[{"line_number":11,"context_line":"https://blueprints.launchpad.net/tripleo/+spec/tripleo-ceph-ganesha"},{"line_number":12,"context_line":""},{"line_number":13,"context_line":"Starting in the Octopus release, Ceph has its own day1 tool called cephadm and"},{"line_number":14,"context_line":"it\u0027s own day2 tool called orchestrator which will replace ceph-ansible."},{"line_number":15,"context_line":""},{"line_number":16,"context_line":"During the Wallaby cycle TripleO will no longer use ceph-ansible for Ceph"},{"line_number":17,"context_line":"deployment and instead use cephadm [2]_ as described in [1]_. Ganesha deserves"}],"source_content_type":"text/x-rst","patch_set":5,"id":"3451003e_c062a84b","line":14,"range":{"start_line":14,"start_character":0,"end_line":14,"end_character":4},"updated":"2020-12-07 16:00:42.000000000","message":"nit: its","commit_id":"3ad90f91b7982e24e0e95a9c7a4f75154fe9ec00"},{"author":{"_account_id":6796,"name":"Giulio Fidente","email":"gfidente@redhat.com","username":"gfidente"},"change_message_id":"36c5ad59c700fffd20cf9c0663d4095261ee13be","unresolved":true,"context_lines":[{"line_number":11,"context_line":"https://blueprints.launchpad.net/tripleo/+spec/tripleo-ceph-ganesha"},{"line_number":12,"context_line":""},{"line_number":13,"context_line":"Starting in the Octopus release, Ceph has its own day1 tool called cephadm and"},{"line_number":14,"context_line":"it\u0027s own day2 tool called orchestrator which will replace ceph-ansible."},{"line_number":15,"context_line":""},{"line_number":16,"context_line":"During the Wallaby cycle TripleO will no longer use ceph-ansible for Ceph"},{"line_number":17,"context_line":"deployment and instead use cephadm [2]_ as described in [1]_. Ganesha deserves"}],"source_content_type":"text/x-rst","patch_set":5,"id":"2208f1c2_fe81d9c2","line":14,"range":{"start_line":14,"start_character":0,"end_line":14,"end_character":4},"in_reply_to":"3451003e_c062a84b","updated":"2020-12-10 12:36:34.000000000","message":"thanks ;D","commit_id":"3ad90f91b7982e24e0e95a9c7a4f75154fe9ec00"},{"author":{"_account_id":9003,"name":"Tom Barron","email":"tpb@dyncloud.net","username":"tbarron"},"change_message_id":"520f9b1b409a697867cdd6aef45f0871d21f678e","unresolved":true,"context_lines":[{"line_number":22,"context_line":"Problem Description"},{"line_number":23,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":24,"context_line":""},{"line_number":25,"context_line":"In TripleO we used to and aim at supporting the deployment of Ganesha also"},{"line_number":26,"context_line":"when the Ceph cluster itself is not managed by TripleO. In this scenario the"},{"line_number":27,"context_line":"Ganesha service should be deployed standalone; that is, without any additional"},{"line_number":28,"context_line":"core Ceph daemon and it should instead be configured to use the external Ceph"},{"line_number":29,"context_line":"MON and MDS daemons."}],"source_content_type":"text/x-rst","patch_set":5,"id":"62261baf_3c416ada","line":26,"range":{"start_line":25,"start_character":0,"end_line":26,"end_character":55},"updated":"2020-12-07 16:00:42.000000000","message":"Sentence got garbled?  Perhaps something like: In TripleO we support deployment of Ganesha both when the Ceph cluster is itself managed by TripleO and when the Ceph cluster is itself not managed by TripleO.   When the Ceph cluster is *not* managed by Tripleo, the Ganesha service must be deployed standalone; that is, ...","commit_id":"3ad90f91b7982e24e0e95a9c7a4f75154fe9ec00"},{"author":{"_account_id":6796,"name":"Giulio Fidente","email":"gfidente@redhat.com","username":"gfidente"},"change_message_id":"36c5ad59c700fffd20cf9c0663d4095261ee13be","unresolved":true,"context_lines":[{"line_number":22,"context_line":"Problem Description"},{"line_number":23,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":24,"context_line":""},{"line_number":25,"context_line":"In TripleO we used to and aim at supporting the deployment of Ganesha also"},{"line_number":26,"context_line":"when the Ceph cluster itself is not managed by TripleO. In this scenario the"},{"line_number":27,"context_line":"Ganesha service should be deployed standalone; that is, without any additional"},{"line_number":28,"context_line":"core Ceph daemon and it should instead be configured to use the external Ceph"},{"line_number":29,"context_line":"MON and MDS daemons."}],"source_content_type":"text/x-rst","patch_set":5,"id":"142cb41e_30b848dd","line":26,"range":{"start_line":25,"start_character":0,"end_line":26,"end_character":55},"in_reply_to":"62261baf_3c416ada","updated":"2020-12-10 12:36:34.000000000","message":"sure will do!","commit_id":"3ad90f91b7982e24e0e95a9c7a4f75154fe9ec00"},{"author":{"_account_id":9003,"name":"Tom Barron","email":"tpb@dyncloud.net","username":"tbarron"},"change_message_id":"520f9b1b409a697867cdd6aef45f0871d21f678e","unresolved":true,"context_lines":[{"line_number":28,"context_line":"core Ceph daemon and it should instead be configured to use the external Ceph"},{"line_number":29,"context_line":"MON and MDS daemons."},{"line_number":30,"context_line":""},{"line_number":31,"context_line":"To do so, the cephadm [2]_ tool will be called with special arguments and to it"},{"line_number":32,"context_line":"we will provide:"},{"line_number":33,"context_line":""},{"line_number":34,"context_line":"- the Ceph cluster config file, generated using tripleo-ceph-client [3]_ role"},{"line_number":35,"context_line":"- the Ceph cluster keyring to interact with MDS"},{"line_number":36,"context_line":"- the Ganesha config file with pointers to the Ceph config/keyring to use"},{"line_number":37,"context_line":""},{"line_number":38,"context_line":"Proposed Change"},{"line_number":39,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"}],"source_content_type":"text/x-rst","patch_set":5,"id":"c759e383_003a58a3","line":36,"range":{"start_line":31,"start_character":0,"end_line":36,"end_character":73},"updated":"2020-12-07 16:00:42.000000000","message":"Maybe move this paragraph under \"Proposed Change\" since it is part of the solution rather than part of the problem to be solved?","commit_id":"3ad90f91b7982e24e0e95a9c7a4f75154fe9ec00"},{"author":{"_account_id":6796,"name":"Giulio Fidente","email":"gfidente@redhat.com","username":"gfidente"},"change_message_id":"36c5ad59c700fffd20cf9c0663d4095261ee13be","unresolved":true,"context_lines":[{"line_number":28,"context_line":"core Ceph daemon and it should instead be configured to use the external Ceph"},{"line_number":29,"context_line":"MON and MDS daemons."},{"line_number":30,"context_line":""},{"line_number":31,"context_line":"To do so, the cephadm [2]_ tool will be called with special arguments and to it"},{"line_number":32,"context_line":"we will provide:"},{"line_number":33,"context_line":""},{"line_number":34,"context_line":"- the Ceph cluster config file, generated using tripleo-ceph-client [3]_ role"},{"line_number":35,"context_line":"- the Ceph cluster keyring to interact with MDS"},{"line_number":36,"context_line":"- the Ganesha config file with pointers to the Ceph config/keyring to use"},{"line_number":37,"context_line":""},{"line_number":38,"context_line":"Proposed Change"},{"line_number":39,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"}],"source_content_type":"text/x-rst","patch_set":5,"id":"c5ee5375_f388168d","line":36,"range":{"start_line":31,"start_character":0,"end_line":36,"end_character":73},"in_reply_to":"c759e383_003a58a3","updated":"2020-12-10 12:36:34.000000000","message":"ack","commit_id":"3ad90f91b7982e24e0e95a9c7a4f75154fe9ec00"},{"author":{"_account_id":8449,"name":"Marios Andreou","email":"marios.andreou@gmail.com","username":"marios"},"change_message_id":"a19eb39ae37b09171b39b363c66f4f41139b74ea","unresolved":true,"context_lines":[{"line_number":35,"context_line":"Overview"},{"line_number":36,"context_line":"--------"},{"line_number":37,"context_line":""},{"line_number":38,"context_line":"An ansible task will trigger cephadm [2]_ with special arguments for it to stand"},{"line_number":39,"context_line":"up a standalone Ganesha container and to it we will provide:"},{"line_number":40,"context_line":""},{"line_number":41,"context_line":"- the Ceph cluster config file, generated using tripleo-ceph-client [3]_ role"}],"source_content_type":"text/x-rst","patch_set":6,"id":"4cd4a7e6_4d55911d","line":38,"range":{"start_line":38,"start_character":0,"end_line":38,"end_character":10},"updated":"2020-12-11 11:53:37.000000000","message":"is this in tripleo-ceph or tripleo-ceph-client","commit_id":"8bf673b002d54a0a571abbad8b76d21c6ae43017"},{"author":{"_account_id":6796,"name":"Giulio Fidente","email":"gfidente@redhat.com","username":"gfidente"},"change_message_id":"5127de6e2224ecd5f8dce273c73ac1a377caf778","unresolved":true,"context_lines":[{"line_number":35,"context_line":"Overview"},{"line_number":36,"context_line":"--------"},{"line_number":37,"context_line":""},{"line_number":38,"context_line":"An ansible task will trigger cephadm [2]_ with special arguments for it to stand"},{"line_number":39,"context_line":"up a standalone Ganesha container and to it we will provide:"},{"line_number":40,"context_line":""},{"line_number":41,"context_line":"- the Ceph cluster config file, generated using tripleo-ceph-client [3]_ role"}],"source_content_type":"text/x-rst","patch_set":6,"id":"f9277ab4_3060602c","line":38,"range":{"start_line":38,"start_character":0,"end_line":38,"end_character":10},"in_reply_to":"4cd4a7e6_4d55911d","updated":"2020-12-11 14:20:50.000000000","message":"tripleo-ceph","commit_id":"8bf673b002d54a0a571abbad8b76d21c6ae43017"},{"author":{"_account_id":16643,"name":"Goutham Pacha Ravi","email":"gouthampravi@gmail.com","username":"gouthamr"},"change_message_id":"261bd94b3da3d025ac96a8b4f3774fbc73e999b1","unresolved":true,"context_lines":[{"line_number":65,"context_line":""},{"line_number":66,"context_line":"Some upgrade tasks which stop and remove the pre-existing ceph-nfs container"},{"line_number":67,"context_line":"and systemd unit will be added to clean up the system from the ceph-ansible"},{"line_number":68,"context_line":"managed resources."},{"line_number":69,"context_line":""},{"line_number":70,"context_line":"Other End User Impact"},{"line_number":71,"context_line":"---------------------"}],"source_content_type":"text/x-rst","patch_set":6,"id":"9e840b49_e9d0047b","line":68,"range":{"start_line":68,"start_character":17,"end_line":68,"end_character":18},"updated":"2020-12-10 18:10:48.000000000","message":"So will this upgrade be disruptive on the data path?","commit_id":"8bf673b002d54a0a571abbad8b76d21c6ae43017"},{"author":{"_account_id":18002,"name":"John Fulton","email":"fulton@redhat.com","username":"fultonj"},"change_message_id":"ef0df4e0b5e17b03194205a6773619267ee35abb","unresolved":true,"context_lines":[{"line_number":65,"context_line":""},{"line_number":66,"context_line":"Some upgrade tasks which stop and remove the pre-existing ceph-nfs container"},{"line_number":67,"context_line":"and systemd unit will be added to clean up the system from the ceph-ansible"},{"line_number":68,"context_line":"managed resources."},{"line_number":69,"context_line":""},{"line_number":70,"context_line":"Other End User Impact"},{"line_number":71,"context_line":"---------------------"}],"source_content_type":"text/x-rst","patch_set":6,"id":"495f32f7_b4d28939","line":68,"range":{"start_line":68,"start_character":17,"end_line":68,"end_character":18},"in_reply_to":"06ca696a_1f513e3d","updated":"2020-12-21 14:58:50.000000000","message":"I don\u0027t know if we do, but that shouldn\u0027t block merging this spec.\n\nAs per an IRC conversation with Tom we think we can merge this.","commit_id":"8bf673b002d54a0a571abbad8b76d21c6ae43017"},{"author":{"_account_id":9003,"name":"Tom Barron","email":"tpb@dyncloud.net","username":"tbarron"},"change_message_id":"6575a152ec8a311addb077cf0793bef8c33607ab","unresolved":true,"context_lines":[{"line_number":65,"context_line":""},{"line_number":66,"context_line":"Some upgrade tasks which stop and remove the pre-existing ceph-nfs container"},{"line_number":67,"context_line":"and systemd unit will be added to clean up the system from the ceph-ansible"},{"line_number":68,"context_line":"managed resources."},{"line_number":69,"context_line":""},{"line_number":70,"context_line":"Other End User Impact"},{"line_number":71,"context_line":"---------------------"}],"source_content_type":"text/x-rst","patch_set":6,"id":"06ca696a_1f513e3d","line":68,"range":{"start_line":68,"start_character":17,"end_line":68,"end_character":18},"in_reply_to":"5b7eafec_7f60dd34","updated":"2020-12-11 21:31:22.000000000","message":"I think Goutham is asking if this will occur quickly enough that it\"s like a regular failover scenario.  ceph-nfs is in the data path.  clients with hard-mounts should maintain their mounts during a failover (or service restart on the same node).  I/O operations will block, then resume when the new ganesha at the same IP address is available.\n   But if it takes *too* long it will seem like an outage to the clients and they may have applications with their own timeouts that will misbehave.\n\nSo do we have an idea how long this will take?","commit_id":"8bf673b002d54a0a571abbad8b76d21c6ae43017"},{"author":{"_account_id":16643,"name":"Goutham Pacha Ravi","email":"gouthampravi@gmail.com","username":"gouthamr"},"change_message_id":"a032e185296e222cf75abc3eabcca76092a8a7b6","unresolved":true,"context_lines":[{"line_number":65,"context_line":""},{"line_number":66,"context_line":"Some upgrade tasks which stop and remove the pre-existing ceph-nfs container"},{"line_number":67,"context_line":"and systemd unit will be added to clean up the system from the ceph-ansible"},{"line_number":68,"context_line":"managed resources."},{"line_number":69,"context_line":""},{"line_number":70,"context_line":"Other End User Impact"},{"line_number":71,"context_line":"---------------------"}],"source_content_type":"text/x-rst","patch_set":6,"id":"f31c0d37_4d5361cb","line":68,"range":{"start_line":68,"start_character":17,"end_line":68,"end_character":18},"in_reply_to":"5b7eafec_7f60dd34","updated":"2020-12-11 21:26:44.000000000","message":"ganesha stands between the MDS and the end users - so yes, if the mds remains operational, the older ganesha continues to talk to it and serve shares to users; however, if ganesha is restarted/reincarnated - there\u0027s a bit of a tolerance window before end users see the impact. We could stand up a new ganesha with export rules, then migrate the vip and cleanup the older ganesha perhaps? \nWe don\u0027t need that level of detail in the specification - we can take this concern to code.","commit_id":"8bf673b002d54a0a571abbad8b76d21c6ae43017"},{"author":{"_account_id":6796,"name":"Giulio Fidente","email":"gfidente@redhat.com","username":"gfidente"},"change_message_id":"c369f7f590a7ebe46496f44a8be6b1a5f5337c7b","unresolved":true,"context_lines":[{"line_number":65,"context_line":""},{"line_number":66,"context_line":"Some upgrade tasks which stop and remove the pre-existing ceph-nfs container"},{"line_number":67,"context_line":"and systemd unit will be added to clean up the system from the ceph-ansible"},{"line_number":68,"context_line":"managed resources."},{"line_number":69,"context_line":""},{"line_number":70,"context_line":"Other End User Impact"},{"line_number":71,"context_line":"---------------------"}],"source_content_type":"text/x-rst","patch_set":6,"id":"5b7eafec_7f60dd34","line":68,"range":{"start_line":68,"start_character":17,"end_line":68,"end_character":18},"in_reply_to":"9e840b49_e9d0047b","updated":"2020-12-10 21:45:20.000000000","message":"this is interesting; I was assuming deleting the old container and systemd unit (created by ceph-ansible) and trigger a standalone ganesha deployment with cephadm to recreate those would not have had any impact on the data ... served by mds which aren\u0027t touched by this process\n\nare you saying that refreshing the ganesha.conf standing up a new container, which would be pointed to the same ceph cluster, is not sufficient to re-export the same shares?","commit_id":"8bf673b002d54a0a571abbad8b76d21c6ae43017"}]}