========================= #openstack-meeting: gluon ========================= Meeting started by bh526r at 18:02:46 UTC. The full logs are available at http://eavesdrop.openstack.org/meetings/gluon/2016/gluon.2016-07-20-18.02.log.html . Meeting summary --------------- * Roll Call and Introduction (bh526r, 18:04:06) * Georg Kunz (georgk, 18:04:23) * Bin Hu (bh526r, 18:04:31) * Jeff Collins (Jeffreyc42, 18:04:32) * Kamil Renczewski (krenczewski, 18:04:33) * Paul Carver (pcarver, 18:04:42) * Admin Update (bh526r, 18:05:28) * No update of admin matters (bh526r, 18:05:49) * Review of Repository Structure (bh526r, 18:06:31) * Today we primarily focus on reviewing 2 patches (bh526r, 18:07:00) * one is the patch of proposing repo structure (bh526r, 18:07:15) * the other one is the patch of architecture description (bh526r, 18:07:33) * here is the patch of repo structure: (bh526r, 18:07:55) * https://review.openstack.org/#/c/342448/ (bh526r, 18:08:10) * There are a few comments, primiarily on the specific description of the functional description of each component of the repo proposal (bh526r, 18:09:28) * my comments are mainly brain dumps of architectural things I wanted to capture somewhere (georgk, 18:10:40) * there is only one comment from Kamal, suggesting to change the name of "gluon-core" to "gluon-lib" (bh526r, 18:10:57) * Georg: that was before the architecture doc was pushed by Jeff (bh526r, 18:11:34) * thank you Georg (bh526r, 18:11:58) * I can move my comments to the right place (maybe the architecture doc) later (georgk, 18:12:09) * sure, that's better. Thank you Georg (bh526r, 18:12:30) * and I also think, the architecture description may need to reflect the new repo strucuture of architectural components (bh526r, 18:13:00) * so regarding the comment of changing the name of "gluon-core" to "gluon-lib", is there any other opinion? (bh526r, 18:13:47) * if there is no other opinion on the name change of "gluon-core" to "gluon-lib" (bh526r, 18:15:00) * I would suggest that the group present on the meeting today agreed to this proposal. (bh526r, 18:15:43) * +1 (georgk, 18:16:01) * +1 (Jeffreyc42, 18:16:33) * In respect of original authoer Tom, we would wait for Tom's back from vacation so that he will upload patch 2 for this new name (bh526r, 18:16:51) * "gluon-lib" (bh526r, 18:17:07) * then the gluon-core can +2 and merge it (bh526r, 18:17:50) * Review of Architecture Document (bh526r, 18:18:41) * https://review.openstack.org/#/c/344283/ (bh526r, 18:18:55) * now is the real thing: architecture description (bh526r, 18:19:14) * Kamal posted 4 comments, 2 editorial and 2 needs clarification (bh526r, 18:20:00) * plus Georg's comments (bh526r, 18:20:04) * and the necessary re-consideration given the new repo strucuture, and related description of components within the repo (bh526r, 18:20:45) * Jeff: For Kamal's comments 1 and 3 are given (bh526r, 18:21:21) * Jeff: we already discussed this second one (bh526r, 18:21:32) * and for 4 i think it would be a good idea to add a section on why etcd and not rabbit (Jeffreyc42, 18:21:51) * that's right, it will be very helpful (bh526r, 18:22:09) * and Georg's original comment on repo patch, but actually applicable to architectural description (bh526r, 18:22:51) * regarding my comments: they are targeting potential improvements (georgk, 18:23:26) * shall we put them in a dedicated section in this document or create a separate one (georgk, 18:23:45) * yes, improvements - but also a starting point of our formal architectural design so that we know what needs improved for future work (bh526r, 18:24:27) * I wanted to collect current shortcoming of the architecture and collect them in some place so that we can discuss those (georgk, 18:24:31) * We mention a few places in the arch doc for improvements already. (Jeffreyc42, 18:25:03) * I think either pull this out to its own section or just add it to the respective sections. (Jeffreyc42, 18:25:24) * I suggest that let us work on the arch doc as the opportunity of long term design instead of just documenting what is currently we have (bh526r, 18:25:55) * the arch document was put together to help people learn how its currently built (Jeffreyc42, 18:26:34) * Along the way though we added future changes (Jeffreyc42, 18:26:48) * - So I would suggest using the arch doc for how its currently built and maybe either add a new "future" section or put this in its own rst (Jeffreyc42, 18:27:20) * I suggest to put this in its own rst (bh526r, 18:27:43) * +1 (Jeffreyc42, 18:27:57) * new doc for future/changes (Jeffreyc42, 18:28:08) * fine this that (georgk, 18:28:11) * I'll pull out the future stuff from the current arch doc and put it in a new one. then others can add (Jeffreyc42, 18:28:46) * I'll go ahead and make the Kamal changes but will need help on the details of etcd vs rabbit (Jeffreyc42, 18:29:28) * Yes, the new architecture document is a single document that will evolve over time (bh526r, 18:29:42) * But the old one is a legacy stuff, we can keep it as documenting what we have before OpenStack (bh526r, 18:30:19) * the current doc is the arch doc - Which I think should be maintained for how its built (Jeffreyc42, 18:31:05) * then we take this as an opportunity of a fresh start in OpenStack (bh526r, 18:31:14) * the new rst would be the "proposed improvements" or something like this (Jeffreyc42, 18:31:38) * yes, we should maintain the old one as how it was built before OpenStack (bh526r, 18:31:50) * the whole thing in Git now is not in OpenStack yet (bh526r, 18:32:04) * - ok and that would maintain the name "Archectural Description"? (Jeffreyc42, 18:32:12) * Everyone good with that strucutre then? (Jeffreyc42, 18:32:53) * that is why we discussed the new repo structure, which will be supported by a fresh new architectural doc (bh526r, 18:33:07) * I'm not following you. You are saying you want to use the arch doc for the new propsed stuff/changes or how its currently built? (Jeffreyc42, 18:34:15) * yes, I agree with (1) the old one maintained as a whole of describing how it was built before OpenStack (2) a new one starts the new design (bh526r, 18:34:27) * ok, got it (Jeffreyc42, 18:34:42) * thanks (Jeffreyc42, 18:34:46) * then we evolve the new one as we evolve in openstack (bh526r, 18:35:13) * ok now I'm lost :) (Jeffreyc42, 18:35:22) * yes, the old one as-is is for historical documentation (bh526r, 18:35:44) * the current arch doc should be continuously updated for how gluon is currently built now and as it changes (Jeffreyc42, 18:36:01) * the new doc is for ideas/purposals/changes as we discuss? (Jeffreyc42, 18:36:23) * hold on, guy (bh526r, 18:36:39) * the situation is - we have old repo, which we need to document how it was built (bh526r, 18:37:28) * the repo structure is not really for the arch doc (Jeffreyc42, 18:38:01) * currently the arch doc has how its built and as i describe things I also call out room for some changes (Jeffreyc42, 18:38:11) * I expect the arch doc to evolve as we change the code (Jeffreyc42, 18:38:23) * now, we have new repo, and agreed new repo structure (bh526r, 18:38:32) * but that doesn't change the arch (Jeffreyc42, 18:38:41) * we should take this opportunity to fresh start the architectural design (bh526r, 18:39:09) * right - and we can do that and update the arch doc as we go (Jeffreyc42, 18:39:26) * - how about we just keep the 1 arch doc and update it as we change things (Jeffreyc42, 18:39:43) * and the old arch doc will describe how it was build before OpenStack (bh526r, 18:39:48) * we are not changing / starting over though (Jeffreyc42, 18:40:06) * we are just updating some pieces (Jeffreyc42, 18:40:15) * like - here is the legacy. It's the end. (bh526r, 18:40:17) * new doc can start with the old content, with the clarifications based on comments from Kamal and Georg (bh526r, 18:40:48) * - those changes are small though. i can update those very quickly (Jeffreyc42, 18:41:05) * we are not rebuilding gluon here. As we make changes lets just update the arch doc (Jeffreyc42, 18:41:25) Meeting ended at 19:02:47 UTC. People present (lines said) --------------------------- * bh526r (62) * Jeffreyc42 (43) * georgk (17) * pcarver (11) * openstack (4) * krenczewski (3) Generated by `MeetBot`_ 0.1.4