From noreply at redhat.com Fri Aug 5 12:28:36 2016 From: noreply at redhat.com (noreply at redhat.com) Date: Fri, 5 Aug 2016 08:28:36 -0400 Subject: [Tendrl-devel] test msg to tendrl-devel Message-ID: <201608051228.u75CSaAr006023@int-mx11.intmail.prod.int.phx2.redhat.com> test From japplewh at redhat.com Tue Aug 23 17:23:52 2016 From: japplewh at redhat.com (Jeff Applewhite) Date: Tue, 23 Aug 2016 13:23:52 -0400 Subject: [Tendrl-devel] integrating tendrl into other projects In-Reply-To: References: Message-ID: On Tue, Aug 23, 2016 at 12:37 PM, Ken Dreyer wrote: > Hi folks, > > I've heard references to plans about integrating USM with OSP-Director > (cc'ing Jeff Layton here), and there are other integrations we need to > do as well (for example, integrate USM into Ceph's test framework, > Teuthology.) > ?Yes that direction is unclear now. What has been committed to firmly is a manual import process for the next OSP release based on the existing RHSC2 import feature. We received push back on integrating OSP 10 into development efforts due to the lack of an upstream community (TripleO team primarily). We are taking steps to fix this. The target for integration might be OSP11 (not due to USM's lack of willingness to do the work, but rather the upstream efforts required). Right now Tendrl upstream barely exists, so there is almost nothing to > integrate. A POC with demo'd code is in progress on github https://github.com/Tendrl and the code is there now. Licensing issues are resolved in favor of LGPL. This is the base of the new USM 3 release. I'm not sure what you mean to say here. ?Rohan has developed tests and you should communicate with him on the details.? As you may or may not know we have an upstream plan around the Tendrl name, have a new mailing list tendrl-devel at redhat.com, have registered tendrl.org and have plans for a web presence for which I have made the funding case. That meeting was last week due to delays. Patrick plans to get a web presence in place soon. I plan to announce the tendrl-devel list on ceph-devel, ceph-users, and the similar Gluster lists. > If we try to build this integration downstream only, it's > going to be a nightmare for QE. If we discuss Tendrl on the upstream > ceph and tripleo mailing lists, it's going to lead to confusion with > skyrings vs tendrl. > ?The mailing list exists as I said. I was hoping to get the domain switched to tendrl.org but it is functional as is.? > > When are the repositories at https://github.com/skyrings going to move > to the tendrl GitHub org? > ?They are not moving as is. Substantial re-work will be involved.? > > When are the "skyring" references going to be removed from the code? > ?As this re-work occurs.. Related to integration, in order to integrate with Teuthology or > TripleO, Tendrl needs a formal Python API client. The USM QE team has > written one that could be open-sourced. I think I heard that Shubhendu > had also written something in Swagger? What is the plan for this? > Rohan/Shubendhu - ?Please? ?comment here...?let's plan on getting together with QE this week to discuss. I will call something > > - Ken > > -- Jeff Applewhite Principal Product Manager 919-381-7406 m -------------- next part -------------- An HTML attachment was scrubbed... URL: From kdreyer at redhat.com Tue Aug 23 17:59:09 2016 From: kdreyer at redhat.com (Ken Dreyer) Date: Tue, 23 Aug 2016 11:59:09 -0600 Subject: [Tendrl-devel] integrating tendrl into other projects In-Reply-To: References: Message-ID: On Tue, Aug 23, 2016 at 11:23 AM, Jeff Applewhite wrote: > > > On Tue, Aug 23, 2016 at 12:37 PM, Ken Dreyer wrote: >> When are the repositories at https://github.com/skyrings going to move >> to the tendrl GitHub org? > > > They are not moving as is. Substantial re-work will be involved. Hi Jeff, what are the details of this re-work? I see some code in the Tendrl org, but it doesn't look like the Skyring code at all? Is the entire project being rewritten from Go -> Python? As we work on integration and building out automated tests, we want to be sure we're targeting the right code bases. - Ken From japplewh at redhat.com Tue Aug 23 18:55:25 2016 From: japplewh at redhat.com (Jeff Applewhite) Date: Tue, 23 Aug 2016 14:55:25 -0400 Subject: [Tendrl-devel] integrating tendrl into other projects In-Reply-To: References: Message-ID: On Tue, Aug 23, 2016 at 1:59 PM, Ken Dreyer wrote: > On Tue, Aug 23, 2016 at 11:23 AM, Jeff Applewhite > wrote: > > > > > > On Tue, Aug 23, 2016 at 12:37 PM, Ken Dreyer wrote: > >> When are the repositories at https://github.com/skyrings going to move > >> to the tendrl GitHub org? > > > > > > They are not moving as is. Substantial re-work will be involved. > > > Hi Jeff, what are the details of this re-work? > > I see some code in the Tendrl org, but it doesn't look like the > Skyring code at all? Is the entire project being rewritten from Go -> > Python? > ?I will ? let Mrugesh and Rohan fill in details - but yes, there will be both Go and Python. Rohan's test code is Python. > > As we work on integration and building out automated tests, we want to > be sure we're targeting the right code bases. > > - Ken > > _______________________________________________ > Tendrl-devel mailing list > Tendrl-devel at redhat.com > https://www.redhat.com/mailman/listinfo/tendrl-devel > -- Jeff Applewhite Principal Product Manager 919-381-7406 m -------------- next part -------------- An HTML attachment was scrubbed... URL: From sankarshan.mukhopadhyay at gmail.com Wed Aug 24 01:47:57 2016 From: sankarshan.mukhopadhyay at gmail.com (Sankarshan Mukhopadhyay) Date: Wed, 24 Aug 2016 07:17:57 +0530 Subject: [Tendrl-devel] integrating tendrl into other projects In-Reply-To: References: Message-ID: [dropping the internal list; it isn't specifically required to continue with this conversation] On Tue, Aug 23, 2016 at 10:53 PM, Jeff Applewhite wrote: > > > On Tue, Aug 23, 2016 at 12:37 PM, Ken Dreyer wrote: >> >> Hi folks, >> >> I've heard references to plans about integrating USM with OSP-Director >> (cc'ing Jeff Layton here), and there are other integrations we need to >> do as well (for example, integrate USM into Ceph's test framework, >> Teuthology.) > > The Teuthology integration is not something which has come up in recent conversations and thus this is a somewhat new perspective. Could we consider a separate thread to continue with this? At this stage it would be relevant to understand what the scope and intended outcome is. > Yes that direction is unclear now. What has been committed to firmly is a > manual import process for the next OSP release based on the existing RHSC2 > import feature. We received push back on integrating OSP 10 into development > efforts due to the lack of an upstream community (TripleO team primarily). > We are taking steps to fix this. The target for integration might be OSP11 > (not due to USM's lack of willingness to do the work, but rather the > upstream efforts required). > >> Right now Tendrl upstream barely exists, so there is almost nothing to >> integrate. > JeffA has responded to the other parts of the original email. I wanted to seek a bit of clarity about the above concern. What was the expectation otherwise? > A POC with demo'd code is in progress on github https://github.com/Tendrl > and the code is there now. Licensing issues are resolved in favor of LGPL. > This is the base of the new USM 3 release. I'm not sure what you mean to say > here. -- sankarshan mukhopadhyay From shtripat at redhat.com Wed Aug 24 05:07:41 2016 From: shtripat at redhat.com (Shubhendu Tripathi) Date: Wed, 24 Aug 2016 10:37:41 +0530 Subject: [Tendrl-devel] integrating tendrl into other projects In-Reply-To: References: Message-ID: On 08/23/2016 10:53 PM, Jeff Applewhite wrote: > > > On Tue, Aug 23, 2016 at 12:37 PM, Ken Dreyer > wrote: > > Hi folks, > > I've heard references to plans about integrating USM with OSP-Director > (cc'ing Jeff Layton here), and there are other integrations we need to > do as well (for example, integrate USM into Ceph's test framework, > Teuthology.) > > > ?Yes that direction is unclear now. What has been committed to firmly > is a manual import process for the next OSP release based on the > existing RHSC2 import feature. We received push back on integrating > OSP 10 into development efforts due to the lack of an upstream > community (TripleO team primarily). We are taking steps to fix this. > The target for integration might be OSP11 (not due to USM's lack of > willingness to do the work, but rather the upstream efforts required). > > Right now Tendrl upstream barely exists, so there is almost nothing to > integrate. > > > A POC with demo'd code is in progress on github > https://github.com/Tendrl and the code is there now. Licensing issues > are resolved in favor of LGPL. This is the base of the new USM 3 > release. I'm not sure what you mean to say here. > ?Rohan has developed tests and you should communicate with him on the > details.? > > As you may or may not know we have an upstream plan around the Tendrl > name, have a new mailing list tendrl-devel at redhat.com > , have registered tendrl.org > and have plans for a web presence for which I have > made the funding case. That meeting was last week due to delays. > Patrick plans to get a web presence in place soon. I plan to announce > the tendrl-devel list on ceph-devel, ceph-users, and the similar > Gluster lists. > > > If we try to build this integration downstream only, it's > going to be a nightmare for QE. If we discuss Tendrl on the upstream > ceph and tripleo mailing lists, it's going to lead to confusion with > skyrings vs tendrl. > > > ?The mailing list exists as I said. I was hoping to get the domain > switched to tendrl.org but it is functional as is.? > > > When are the repositories at https://github.com/skyrings going to move > to the tendrl GitHub org? > > > ?They are not moving as is. Substantial re-work will be involved.? > > > When are the "skyring" references going to be removed from the code? > > > ?As this re-work occurs.. > > Related to integration, in order to integrate with Teuthology or > TripleO, Tendrl needs a formal Python API client. The USM QE team has > written one that could be open-sourced. I think I heard that Shubhendu > had also written something in Swagger? What is the plan for this? > > > Rohan/Shubendhu - ?Please? > ?comment here...?let's plan on getting together with QE this week to > discuss. I will call something Jeff, yes as you remember there was POC was done for integrating with swagger. There were some gaps for sure. Unfortunately I dont have a working setup right now, but patches are there in gerrithub.io. As next RHSC-3, we might be moving towards python, swagger anyway would not much prominence and we would have to look at python based frameworks for REST documentation. Regards, Shubhendu > > - Ken > > > > > -- > Jeff Applewhite > Principal Product Manager > 919-381-7406 m -------------- next part -------------- An HTML attachment was scrubbed... URL: From rkanade at redhat.com Wed Aug 24 09:46:45 2016 From: rkanade at redhat.com (Rohan Kanade) Date: Wed, 24 Aug 2016 15:16:45 +0530 Subject: [Tendrl-devel] Need attention on python/pep8 issues across Tendrl Message-ID: Hi Folks, Tendrl being a new project has to adopt to the python ecosystem conventions and with PEP8 [0] being one of the most important style/syntax guideline for python projects, Tendrl needs to be PEP8 compliant This is also a good way to get around the Tendrl codebases while fixing the PEP8 violations in the codebase. Lets address below issues related to PEP8 compliance: - https://github.com/Tendrl/gluster_bridge/issues/3 - https://github.com/Tendrl/bridge_common/issues/7 - https://github.com/Tendrl/ceph_bridge/issues/3 PS: Please assign yourselves these issues formally (via github) so that we dont end up working on the same issue. [0]: https://www.python.org/dev/peps/pep-0008/ Regards, Rohan Kanade -------------- next part -------------- An HTML attachment was scrubbed... URL: From dnarayan at redhat.com Wed Aug 24 10:32:09 2016 From: dnarayan at redhat.com (Darshan Narayana Murthy) Date: Wed, 24 Aug 2016 06:32:09 -0400 (EDT) Subject: [Tendrl-devel] Need attention on python/pep8 issues across Tendrl In-Reply-To: References: Message-ID: <522195332.2872002.1472034729109.JavaMail.zimbra@redhat.com> I am working on fixing the pep8 issues in ceph_bridge project. Will send a pull request soon. -Darshan ----- Original Message ----- > From: "Rohan Kanade" > To: tendrl-devel at redhat.com > Sent: Wednesday, August 24, 2016 3:16:45 PM > Subject: [Tendrl-devel] Need attention on python/pep8 issues across Tendrl > > Hi Folks, > > Tendrl being a new project has to adopt to the python ecosystem conventions > and with PEP8 [0] being one of the most important style/syntax guideline for > python projects, Tendrl needs to be PEP8 compliant > > This is also a good way to get around the Tendrl codebases while fixing the > PEP8 violations in the codebase. > > Lets address below issues related to PEP8 compliance: > > > * https://github.com/Tendrl/gluster_bridge/issues/3 > * https://github.com/Tendrl/bridge_common/issues/7 > * https://github.com/Tendrl/ceph_bridge/issues/3 > > > PS: Please assign yourselves these issues formally (via github) so that we > dont end up working on the same issue. > > [0]: https://www.python.org/dev/peps/pep-0008/ > > Regards, > Rohan Kanade > > _______________________________________________ > Tendrl-devel mailing list > Tendrl-devel at redhat.com > https://www.redhat.com/mailman/listinfo/tendrl-devel > From adeza at redhat.com Wed Aug 24 10:56:01 2016 From: adeza at redhat.com (Alfredo Deza) Date: Wed, 24 Aug 2016 06:56:01 -0400 Subject: [Tendrl-devel] Need attention on python/pep8 issues across Tendrl In-Reply-To: <522195332.2872002.1472034729109.JavaMail.zimbra@redhat.com> References: <522195332.2872002.1472034729109.JavaMail.zimbra@redhat.com> Message-ID: On Wed, Aug 24, 2016 at 6:32 AM, Darshan Narayana Murthy wrote: > I am working on fixing the pep8 issues in ceph_bridge project. > Will send a pull request soon. > > -Darshan > > ----- Original Message ----- >> From: "Rohan Kanade" >> To: tendrl-devel at redhat.com >> Sent: Wednesday, August 24, 2016 3:16:45 PM >> Subject: [Tendrl-devel] Need attention on python/pep8 issues across Tendrl >> >> Hi Folks, >> >> Tendrl being a new project has to adopt to the python ecosystem conventions >> and with PEP8 [0] being one of the most important style/syntax guideline for >> python projects, Tendrl needs to be PEP8 compliant >> >> This is also a good way to get around the Tendrl codebases while fixing the >> PEP8 violations in the codebase. We have adopted pep8 in various Python projects on the Ceph organization and we have automated CI tests on pull requests to check against them. Having to run `tox` to check the project can get a bit tedious though (and easy to forget), so I would highly recommend a plugin for your $EDITOR so that the checks are displayed automatically. For Vim (shameless plug here) I wrote a plugin [0] one that integrates with flake8 [1] a test-runner-like tool. [0] https://github.com/alfredodeza/khuno.vim [1] https://flake8.readthedocs.io/en/latest/ >> >> Lets address below issues related to PEP8 compliance: >> >> >> * https://github.com/Tendrl/gluster_bridge/issues/3 >> * https://github.com/Tendrl/bridge_common/issues/7 >> * https://github.com/Tendrl/ceph_bridge/issues/3 >> >> >> PS: Please assign yourselves these issues formally (via github) so that we >> dont end up working on the same issue. >> >> [0]: https://www.python.org/dev/peps/pep-0008/ >> >> Regards, >> Rohan Kanade >> >> _______________________________________________ >> Tendrl-devel mailing list >> Tendrl-devel at redhat.com >> https://www.redhat.com/mailman/listinfo/tendrl-devel >> > > _______________________________________________ > Tendrl-devel mailing list > Tendrl-devel at redhat.com > https://www.redhat.com/mailman/listinfo/tendrl-devel From kdreyer at redhat.com Wed Aug 24 12:35:00 2016 From: kdreyer at redhat.com (Ken Dreyer) Date: Wed, 24 Aug 2016 06:35:00 -0600 Subject: [Tendrl-devel] Need attention on python/pep8 issues across Tendrl In-Reply-To: References: <522195332.2872002.1472034729109.JavaMail.zimbra@redhat.com> Message-ID: On Wed, Aug 24, 2016 at 4:56 AM, Alfredo Deza wrote: > For Vim (shameless plug here) I wrote a plugin [0] one that integrates > with flake8 [1] a test-runner-like tool. > > [0] https://github.com/alfredodeza/khuno.vim > [1] https://flake8.readthedocs.io/en/latest/ Another +1 for Khuno here - this tool has made me a better programmer! - Ken From nthomas at redhat.com Wed Aug 24 13:32:28 2016 From: nthomas at redhat.com (Nishanth Thomas) Date: Wed, 24 Aug 2016 19:02:28 +0530 Subject: [Tendrl-devel] Need attention on python/pep8 issues across Tendrl In-Reply-To: References: <522195332.2872002.1472034729109.JavaMail.zimbra@redhat.com> Message-ID: its by mistake to send it off list :) Anyway, I don't think there is a plan to bring in gerrithub here. One advantage with gerrithub is that code review is much easier. On Wed, Aug 24, 2016 at 6:54 PM, Ken Dreyer wrote: > (Did you mean to send this off-list?) > > I recommend dumping GerritHub and just using GitHub. GitHub's PR > workflow is a lot easier, and it would be simple to integrate Travis > CI into the workflows. You can even set up GitHub to deny merges for > any PRs that have not passed testing. > > All of this can be done today in a couple hours, but setting up > Jenkins + GerritHub is more work. > > Gerrit is just a pain :) > > - Ken > > > On Wed, Aug 24, 2016 at 7:20 AM, Nishanth Thomas > wrote: > > +1 for integrating with CI. Also is it feasible to have a check-in > policy to > > disallow the check-ins which fails the check? > > > > On Wed, Aug 24, 2016 at 6:05 PM, Ken Dreyer wrote: > >> > >> On Wed, Aug 24, 2016 at 4:56 AM, Alfredo Deza wrote: > >> > For Vim (shameless plug here) I wrote a plugin [0] one that integrates > >> > with flake8 [1] a test-runner-like tool. > >> > > >> > [0] https://github.com/alfredodeza/khuno.vim > >> > [1] https://flake8.readthedocs.io/en/latest/ > >> > >> Another +1 for Khuno here - this tool has made me a better programmer! > >> > >> - Ken > >> > >> _______________________________________________ > >> Tendrl-devel mailing list > >> Tendrl-devel at redhat.com > >> https://www.redhat.com/mailman/listinfo/tendrl-devel > > > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From kdreyer at redhat.com Thu Aug 25 15:02:54 2016 From: kdreyer at redhat.com (Ken Dreyer) Date: Thu, 25 Aug 2016 09:02:54 -0600 Subject: [Tendrl-devel] integrating tendrl into other projects In-Reply-To: References: Message-ID: On Tue, Aug 23, 2016 at 7:47 PM, Sankarshan Mukhopadhyay wrote: > The Teuthology integration is not something which has come up in > recent conversations and thus this is a somewhat new perspective. > Could we consider a separate thread to continue with this? At this > stage it would be relevant to understand what the scope and intended > outcome is. My intended outcomes: - The Ceph user community to start experimenting with Tendrl, - The Ceph developer community to get familiar with Tendrl, - The Ceph automated test system (Teuthology) to regularly test integration between the latest Ceph bits and the current USM codebase. If Teuthology does not use a standard Python API, then we'll have to write our own and embed it into Teuthology, and then it becomes a siloed thing. This has happened earlier with Ceph install workflows getting deeply embedded into Teuthology, and I want to improve that this time so that the work is modular and can be shared across other open-source projects (like TripleO). My overall goal is for us to integrate more upstream so that we reduce the herculean effort to integrate everything internally downstream at the last minute, leading to burnout. >> Yes that direction is unclear now. What has been committed to firmly is a >> manual import process for the next OSP release based on the existing RHSC2 >> import feature. We received push back on integrating OSP 10 into development >> efforts due to the lack of an upstream community (TripleO team primarily). >> We are taking steps to fix this. The target for integration might be OSP11 >> (not due to USM's lack of willingness to do the work, but rather the >> upstream efforts required). >> >>> Right now Tendrl upstream barely exists, so there is almost nothing to >>> integrate. >> > > JeffA has responded to the other parts of the original email. I wanted > to seek a bit of clarity about the above concern. What was the > expectation otherwise? My concern is that I hear rumors of rewrites, rearchitecture, demos, etc, and there's no discussion in the open. From what I see, these discussions are being made locally without explanation in a blog or anywhere else, let alone open discussion on mailing lists, public (non-RH) IRC, or presenting at the Ceph Developer monthlies, etc. It's fine if you want to rewrite USM/Skyrings while also rebranding it to Tendrl, rewrites are great! Here are the things that need to stop immediately to avoid an integration trainwreck with Ceph and USM 3.0: - private Google Docs - private meetings with individual invites - private demos We have a public mailing list now, thanks Jeff, and I trust that the rest is coming. - Ken From rkanade at redhat.com Wed Aug 31 12:43:43 2016 From: rkanade at redhat.com (Rohan Kanade) Date: Wed, 31 Aug 2016 18:13:43 +0530 Subject: [Tendrl-devel] Few questions/clarification regarding tendrl In-Reply-To: References: <822cc76f-2dd5-f31e-bd4d-fa69290dafde@redhat.com> Message-ID: Weird, must have slipped out during the beginning. Thanks for pointing out, fixed. On Wed, Aug 31, 2016 at 3:18 PM, John Spray wrote: > On Wed, Aug 31, 2016 at 10:28 AM, Shubhendu Tripathi > wrote: > > On 08/31/2016 02:33 PM, Rohan Kanade wrote: > > > > On 31-Aug-2016 14:20, "Shubhendu Tripathi" wrote: > >> > >> Hi All, > >> > >> I got few questions in my mind which I wanted to clarify regarding > tendrl > >> new architecture > >> > >> 1. As per my understanding cthulu module from calamari is more or less > >> used as ceph-bridge with certain changes may be. My question is, why > not use > >> cthulu as layered product and use as library only? Do we really need > to > >> copy code as a separate project? Also even if we don't use cthulu as > >> library, due to LGPL should we retain the copyright notices of the > original > >> sources as is in tendrl's ceph-bridge code ? > >> > > > > Cthulu is not used as is and there's various changes like removal of > > saltstack as a dependency, changing its persistence layer for etcd > instead > > of Relational etc. It is difficult to maintain these features directly in > > cthulu. > > > > Tendrl is LGPL2 and we should definitely run this through Legal just to > be > > sure > > > >> 2. The etcdobj of bridge-common looks taken from > >> https://github.com/ashcrow/etcdobj. Wouldn't this come with additional > >> responsibility of maintaining this project and we might miss out of > updates > >> as well. Also if its intentional copy, should we retain the actual > >> copyright/license message? Can we think of using this project as > library? > >> > > > > Etcdobj is a very small codebase. The original repo is hasn't seen any > > activity since 4months. Etcd is a central part of Tendrl and we need > finer > > control over this piece and it's lifecycle. > > It looks like (I hope accidentally) someone has stripped the original > header from that code. > > If you're going to copy it, at least respect the conditions from the > original, including the condition that source copies must reproduce > the copyright notice and list of conditions. > https://github.com/ashcrow/etcdobj/blob/master/src/etcdobj/fields.py > > John > > > > > Just a suggestion, why not contribute to the original project and make it > > mature enough and use as library. At least replication of effort is > reduced. > > > > Regarding the licensing issue. We should consult with Legal and rectify > any > > noncompliance > >> These are just my points of view and I was not clear so thought of > >> clarifying with broader audience. > >> > >> Thanks and Regards, > >> Shubhendu > >> > >> PS: https://www.gnu.org/licenses/old-licenses/lgpl-2.1.en.html > >> > >> _______________________________________________ > >> Tendrl-devel mailing list > >> Tendrl-devel at redhat.com > >> https://www.redhat.com/mailman/listinfo/tendrl-devel > >> > > > > > > > > _______________________________________________ > > Tendrl-devel mailing list > > Tendrl-devel at redhat.com > > https://www.redhat.com/mailman/listinfo/tendrl-devel > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: