From cblum at redhat.com Sun Jan 1 13:17:52 2017 From: cblum at redhat.com (Christopher Blum) Date: Sun, 1 Jan 2017 14:17:52 +0100 Subject: [Tendrl-devel] Using gdeploy for gluster brick provisioning In-Reply-To: <167437eb-4e2b-fe1e-a6b8-3ed0cd69ae54@redhat.com> References: <271974042.5126710.1481866665404.JavaMail.zimbra@redhat.com> <2134659667.5138990.1481870829555.JavaMail.zimbra@redhat.com> <186164899.5192288.1481885383959.JavaMail.zimbra@redhat.com> <167437eb-4e2b-fe1e-a6b8-3ed0cd69ae54@redhat.com> Message-ID: Hi all, stumbled across this by chance and checked out Blivet and libstoragemgmt. I'm unsure what your goal is here? Knowing Ansible the tasks that Blivet does, could easily be done with modules inside of Ansible (this task has already been done in the gdeploy development). By using the Ansible Modules we don't have to rely on external dependencies. If there really is no other way - we could write a Blivet Module for Ansible... but as sac already said - this will need lots of effort for a functionality which is already inside of gdeploy. I understand though that integrating libstoragemgmt could help us read out RAID settings. Maybe the major issue here is the communication between Tendrl and Ansible? Best Regards, Christopher Blum Storage Consultant Global Storage Practice, Red Hat +49 711 96 43 7009 > On 19 Dec 2016, at 12:51, Martin Bukatovic wrote: > > On 12/16/2016 11:49 AM, Darshan Narayana Murthy wrote: >> >> >> ----- Original Message ----- >>> From: "Sachidananda URS" >>> To: "Darshan Narayana Murthy" >>> Cc: "Mailing list for the contributors to the Tendrl project" >>> Sent: Friday, December 16, 2016 2:18:02 PM >>> Subject: Re: Using gdeploy for gluster brick provisioning >>> >>> Hi Darshan, >>> >>> On Fri, Dec 16, 2016 at 12:17 PM, Darshan Narayana Murthy < >>> dnarayan at redhat.com> wrote: >>> >>>> Hi sac, >>>> >>>> Considering that tendrl will use gdeploy to provision gluster cluster, It >>>> seems very >>>> logical to use gdeploy for brick provisioning as well. Instead of having >>>> the code to >>>> provision bricks in tendrl code base. But for us to consume brick >>>> provisioning from >>>> gdeploy, we need some changes in it. Like gdeploy has to use tools like >>>> blivet, >>>> libstoragemgmt underneath to provision gluster bricks. >>>> >>>> >>> That will be a lot of changes. We will have to see how this can be achieved. >>> >>> >>>> To discuss the feasibility of including these changes, we can raise RFE >>>> against >>>> gdeploy. What would be the right place for this ? >>>> >>>> >>> >>> Github would the place for that. Can you please raise an issue on github? >> >> Thanks sac, >> >> Have raised an issue: https://github.com/gluster/gdeploy/issues/257 to discuss >> further about this > > Isn't this related to https://github.com/Tendrl/documentation/issues/49? > > I'm asking because there is no update related to the new gdeploy > approach there. > > -- > Martin Bukatovic > USM QE team > > _______________________________________________ > Tendrl-devel mailing list > Tendrl-devel at redhat.com > https://www.redhat.com/mailman/listinfo/tendrl-devel From mrugesh at brainfunked.org Mon Jan 2 03:20:17 2017 From: mrugesh at brainfunked.org (Mrugesh Karnik) Date: Mon, 2 Jan 2017 08:50:17 +0530 Subject: [Tendrl-devel] Regarding unique checksum for gluster cluster peers In-Reply-To: <3169d47a-e4a2-32eb-77fc-d446c03c8c58@redhat.com> References: <58057778-89d6-fa77-5aae-82ef494fb893@redhat.com> <3169d47a-e4a2-32eb-77fc-d446c03c8c58@redhat.com> Message-ID: On 28 December 2016 at 11:48, Shubhendu Tripathi wrote: > > > > On 12/28/2016 11:45 AM, Aravinda wrote: >> >> Checksum will change when new node is added/removed from the existing >> cluster. So checksum from peers list may not be suitable for finding Cluster >> ID. > > > Ah, thats a good point and in that case we would need to update the > check-sum in tendrl as well for all the nodes. > @Mrugesh, comments?? The necessity for a checksum is only at the time of detection, pre-import, and it is only necessary to `name' a bunch of nodes as belonging to the same `group' for import. During the import process, Tendrl generates it's own cluster id anyway, which is used thereafter. We may need to consider the changes to a cluster in the pre condition for the gluster import flow. If the cluster is changed between the listing to the administrator and the actual import operation, we may need to display a message and show the updated list of nodes for import again. -- Mrugesh From mrugesh at brainfunked.org Mon Jan 2 09:52:17 2017 From: mrugesh at brainfunked.org (Mrugesh Karnik) Date: Mon, 2 Jan 2017 15:22:17 +0530 Subject: [Tendrl-devel] [TRACKING] Summary for the week of 26th Dec, priorities for the week of 2nd Jan Message-ID: Am limiting the scope of this week's update to provide information regarding the features. I was on PTO last week and am still catching up with the progress on individual specifications. All the listed ids are of issues on the specifications repository (https://github.com/specifications/issues) * List views via the UI: The demo is at https://bluejeans.com/s/3ntKd/. Anmol has updated the monitoring application code to enable the data points required on the list views UI. The integration is being finalised between the core and the monitoring APIs and the feature is expected to be fully merged this week. * Import cluster via the UI: A lot of implementation details have emerged over the past week due to the automatic detection of the existing storage clusters. Multiple specifications have been updated with implementation details and will be worked on this week. The UI is being worked on as well. * Tagged logging: The specification is still under review. Is expected to be merged this week and the implementation initiated. * Alerting: The code with SMTP based alerts is available for review. Provision has been made to accommodate other alerting delivery endpoints such as SNMP. However, only SMTP will be implemented for now. Priorities for the week of 2nd to 6th Jan: * Alerting and monitoring related backend functionality is expected to be reviewed and merged this week. This would provide UX parity for the list views, while enabling further work on the alerting to be taken up. * Import and create cluster workflows. Multiple specifications will be worked on this week. I've updated #87 with a substantial data model impact which affects most of the node agent related specifications. The data model changes will be taken up as applicable and necessary to implement various features. The specifications that will be worked on this week include the import cluster workflow, service detection modules, UI, tagged logging, in-flight operation updates etc. (#46, #54, #56, #28 and #55). * Create cluster flows for ceph and gluster will be worked on this week as well (#51 and #52). -- Mrugesh From shtripat at redhat.com Mon Jan 2 10:03:11 2017 From: shtripat at redhat.com (Shubhendu Tripathi) Date: Mon, 2 Jan 2017 15:33:11 +0530 Subject: [Tendrl-devel] [TRACKING] Daily check-in summary for 20170102 Message-ID: https://meetbot.fedoraproject.org/tendrl-devel/2017-01-02/check-in_20170102.2017-01-02-09.13.html Regards, Shubhendu From mkudlej at redhat.com Mon Jan 2 10:09:01 2017 From: mkudlej at redhat.com (Martin Kudlej) Date: Mon, 2 Jan 2017 11:09:01 +0100 Subject: [Tendrl-devel] [TRACKING] Summary for the week of 26th Dec, priorities for the week of 2nd Jan In-Reply-To: References: Message-ID: Hi Mrugesh, all, On 01/02/2017 10:52 AM, Mrugesh Karnik wrote: > * List views via the UI: The demo is at > https://bluejeans.com/s/3ntKd/. Anmol has updated the monitoring > application code to enable the data points required on the list views > UI. The integration is being finalised between the core and the > monitoring APIs and the feature is expected to be fully merged this > week. It will be great to build new packages after merging this feature. Is there any plan for new packages? -- Best Regards, Martin Kudlej. RHSC/USM Senior Quality Assurance Engineer Red Hat Czech s.r.o. Phone: +420 532 294 155 E-mail:mkudlej at redhat.com IRC: mkudlej at #brno, #gluster, #storage-qa, #rhs, #rh-ceph, #usm-meeting @ redhat #tendrl-devel @ freenode From mkudlej at redhat.com Mon Jan 2 13:52:20 2017 From: mkudlej at redhat.com (Martin Kudlej) Date: Mon, 2 Jan 2017 14:52:20 +0100 Subject: [Tendrl-devel] storage lists in UI Message-ID: <76636416-9d99-f17b-e7ed-75caf9bbd317@redhat.com> Hi all, I would like to ask what are reasons to split list of "storages" to: Pools(Ceph), RBDs(Ceph), File shares(Gluster)? See https://redhat.invisionapp.com/share/BR8JDCGSQ#/screens From my point of view (please forgive my ignorance) there is no difference between Pools(Ceph) and Volume(Gluster) until volume is mounted somehow(native client, SMB, NFS). But volume has its state and attributes like pool(Ceph) so there is reason to show list of volumes like in case of pools. I don't remember exact arguments why it is designed like this. Could somebody make it clear, please? -- Best Regards, Martin Kudlej. RHSC/USM Senior Quality Assurance Engineer Red Hat Czech s.r.o. Phone: +420 532 294 155 E-mail:mkudlej at redhat.com IRC: mkudlej at #brno, #gluster, #storage-qa, #rhs, #rh-ceph, #usm-meeting @ redhat #tendrl-devel @ freenode From sankarshan at redhat.com Mon Jan 2 14:33:21 2017 From: sankarshan at redhat.com (sankarshan) Date: Mon, 2 Jan 2017 20:03:21 +0530 Subject: [Tendrl-devel] [TRACKING] Summary for the week of 26th Dec, priorities for the week of 2nd Jan In-Reply-To: References: Message-ID: On 2 January 2017 at 15:39, Martin Kudlej wrote: > Hi Mrugesh, all, > > On 01/02/2017 10:52 AM, Mrugesh Karnik wrote: >> >> * List views via the UI: The demo is at >> https://bluejeans.com/s/3ntKd/. Anmol has updated the monitoring >> application code to enable the data points required on the list views >> UI. The integration is being finalised between the core and the >> monitoring APIs and the feature is expected to be fully merged this >> week. > > > It will be great to build new packages after merging this feature. Is there > any plan for new packages? Would the availability of packages (binaries) including this feature aid in testing? I am aware of plans for building packages (these were pending working through the issues of consuming the build tool rather than hand-rolling packages), I'm not specifically familiar with the feasibility of building with each merge. There is an on-going discussion which I have not followed through on. From mkudlej at redhat.com Mon Jan 2 14:46:53 2017 From: mkudlej at redhat.com (Martin Kudlej) Date: Mon, 2 Jan 2017 15:46:53 +0100 Subject: [Tendrl-devel] [TRACKING] Summary for the week of 26th Dec, priorities for the week of 2nd Jan In-Reply-To: References: Message-ID: <92f77947-6b7f-841f-f2df-f7c6742ebe44@redhat.com> Hi Mrugesh, all, On 01/02/2017 03:33 PM, sankarshan wrote: > On 2 January 2017 at 15:39, Martin Kudlej wrote: >> Hi Mrugesh, all, >> >> On 01/02/2017 10:52 AM, Mrugesh Karnik wrote: >>> >>> * List views via the UI: The demo is at >>> https://bluejeans.com/s/3ntKd/. Anmol has updated the monitoring >>> application code to enable the data points required on the list views >>> UI. The integration is being finalised between the core and the >>> monitoring APIs and the feature is expected to be fully merged this >>> week. >> >> >> It will be great to build new packages after merging this feature. Is there >> any plan for new packages? > > Would the availability of packages (binaries) including this feature > aid in testing? Yes, packages are used in CI testing. Installing from source is just for trying changes and partially for test development. >I am aware of plans for building packages (these were > pending working through the issues of consuming the build tool rather > than hand-rolling packages), I'm not specifically familiar with the > feasibility of building with each merge. Yes, I've meant packages based on master like last time because I expect that mentioned feature will be merged into master. I expect that they will be built manually because there is no continuous building as I know. >There is an on-going > discussion which I have not followed through on. Yes, there is no update since Dec 20th https://github.com/Tendrl/specifications/issues/53 -- Best Regards, Martin Kudlej. RHSC/USM Senior Quality Assurance Engineer Red Hat Czech s.r.o. Phone: +420 532 294 155 E-mail:mkudlej at redhat.com IRC: mkudlej at #brno, #gluster, #storage-qa, #rhs, #rh-ceph, #usm-meeting @ redhat #tendrl-devel @ freenode From rwheeler at redhat.com Mon Jan 2 21:48:02 2017 From: rwheeler at redhat.com (Ric Wheeler) Date: Mon, 2 Jan 2017 16:48:02 -0500 Subject: [Tendrl-devel] storage lists in UI In-Reply-To: <76636416-9d99-f17b-e7ed-75caf9bbd317@redhat.com> References: <76636416-9d99-f17b-e7ed-75caf9bbd317@redhat.com> Message-ID: <0b8aaee5-68dd-796a-4616-a501d2dbd9e8@redhat.com> On 01/02/2017 08:52 AM, Martin Kudlej wrote: > Hi all, > > I would like to ask what are reasons to split list of "storages" to: > Pools(Ceph), RBDs(Ceph), File shares(Gluster)? > See https://redhat.invisionapp.com/share/BR8JDCGSQ#/screens > > From my point of view (please forgive my ignorance) there is no difference > between Pools(Ceph) and Volume(Gluster) until volume is mounted somehow(native > client, SMB, NFS). But volume has its state and attributes like pool(Ceph) so > there is reason to show list of volumes like in case of pools. > > I don't remember exact arguments why it is designed like this. Could somebody > make it clear, please? > The first level, consumable things are file, block or object stores. I would say the split would be something like RBD's, file shares and RGW (object) instances. Below that layer is the pool or brick, etc... ric From shtripat at redhat.com Tue Jan 3 09:35:24 2017 From: shtripat at redhat.com (Shubhendu Tripathi) Date: Tue, 3 Jan 2017 15:05:24 +0530 Subject: [Tendrl-devel] [TRACKING] Daily check-in summary for 20170103 Message-ID: https://meetbot.fedoraproject.org/tendrl-devel/2017-01-03/check-in_20170103.2017-01-03-09.00.html Regards, Shubhendu From mkudlej at redhat.com Tue Jan 3 17:11:47 2017 From: mkudlej at redhat.com (Martin Kudlej) Date: Tue, 3 Jan 2017 18:11:47 +0100 Subject: [Tendrl-devel] labeling github issues + blockers In-Reply-To: References: <9ecd00cf-3d32-5335-945d-27e89e873e9c@redhat.com> <86df1867-453b-ef8d-0022-21c1018b2d53@redhat.com> Message-ID: <41a14755-ba58-15b4-ee4b-71ba1f66eb4c@redhat.com> Hi all, because we cannot add labels in all Tendrl repositories(see below), we've created page with list of github issues and pull request which are more important for QE than rest of them. You can find there also issues which are blocking us. Please look at https://github.com/Tendrl/usmqe-tests/wiki Thank you for fixing blockers soon! On 12/21/2016 11:37 PM, Jeff Applewhite wrote: > Done for the QE group for both of your usmqe-* repos - for other repos this > requires write access on the repo. > > We probably need some discussion on this before I make that change. By > default all users get read on all repos. Changing this to write has lots of > implications that should be thought through. Optionally the QE team could > be added to all the relevant repos with write access. > > https://help.github.com/articles/repository-permission-levels-for-an-organization/ > > > > On Wed, Dec 21, 2016 at 3:41 PM, Martin Kudlej wrote: > >> Hi, >> >> could admins of github repositories give people from QE team permission to >> set labels, please? >> This will be very helpful for us and it gives us ability to better sort >> and search issues and pull requests in Tendrl repositories. >> >> Thank you! >> >> On 12/01/2016 11:38 AM, Martin Bukatovic wrote: >> >>> On 12/01/2016 11:16 AM, Sankarshan Mukhopadhyay wrote: >>> >>>> On Thu, Dec 1, 2016 at 3:32 PM, Martin Bukatovic >>>> wrote: >>>> >>>>> I would like to assign labels (such as "bug" or "question") to github >>>>> issues I have created, but I don't seem to have the access rights >>>>> needed. Could you reconfigure the Tendrl github group so that qe team >>>>> members can add labels to theirs github issues? >>>>> >>>> >>>> Alright. I'm missing something here. The specific label (names, which >>>> you indicate) exist. Can you provide me with a link to a particular >>>> issue? It should be easier for me to figure out what to do. >>>> >>> >>> The problem I have here is that while the labels exists, and other >>> team members are using them on some github issues, I'm unable to do >>> so. >>> >>> When I click on "New issue" of any Tendrl project on github, I don't >>> see the the knobs for setting the label at all [1] - the right panel >>> which provides those options is missing. Neither I see them when I >>> try to edit already created issue. Since I'm able to label issues of >>> my own projects, I suspect that this is related to access rights >>> of Tendrl github group. >>> >>> To try this yourself, try to click on "New issue" button of tendrl >>> documentation project[2] and compare it with my screenshot[1]. >>> If you are able to see knobs to set labels in the right panel, while >>> I'm not provided with this option as shown on the screenshot, we >>> would need to reconfigure access rights so that the qe team members >>> can add labels to tendrl github issues. >>> >>> Thank you for your help. >>> >>> [1] https://ibin.co/33riFN0YCthe.png >>> [2] https://github.com/Tendrl/documentation/issues/new >>> >>> >> -- >> Best Regards, >> Martin Kudlej. >> RHSC/USM Senior Quality Assurance Engineer >> Red Hat Czech s.r.o. >> >> Phone: +420 532 294 155 >> E-mail:mkudlej at redhat.com >> IRC: mkudlej at #brno, #gluster, #storage-qa, #rhs, #rh-ceph, >> #usm-meeting @ redhat >> #tendrl-devel @ freenode >> >> >> _______________________________________________ >> Tendrl-devel mailing list >> Tendrl-devel at redhat.com >> https://www.redhat.com/mailman/listinfo/tendrl-devel >> > > > -- Best Regards, Martin Kudlej. RHSC/USM Senior Quality Assurance Engineer Red Hat Czech s.r.o. Phone: +420 532 294 155 E-mail:mkudlej at redhat.com IRC: mkudlej at #brno, #gluster, #storage-qa, #rhs, #rh-ceph, #usm-meeting @ redhat #tendrl-devel @ freenode From japplewh at redhat.com Tue Jan 3 17:35:52 2017 From: japplewh at redhat.com (Jeff Applewhite) Date: Tue, 3 Jan 2017 12:35:52 -0500 Subject: [Tendrl-devel] [TRACKING] Summary for the week of 26th Dec, priorities for the week of 2nd Jan In-Reply-To: <92f77947-6b7f-841f-f2df-f7c6742ebe44@redhat.com> References: <92f77947-6b7f-841f-f2df-f7c6742ebe44@redhat.com> Message-ID: I am keen to get this solved for a number of reasons. Packages are important for testing, developer enablement, completeness and meeting the DoD. Chris B has volunteered to assist on the packaging effort if needed. What is the blocking issue? Is there somewhere he could pitch in? Thanks Jeff On Mon, Jan 2, 2017 at 9:46 AM, Martin Kudlej wrote: > Hi Mrugesh, all, > > On 01/02/2017 03:33 PM, sankarshan wrote: > >> On 2 January 2017 at 15:39, Martin Kudlej wrote: >> >>> Hi Mrugesh, all, >>> >>> On 01/02/2017 10:52 AM, Mrugesh Karnik wrote: >>> >>>> >>>> * List views via the UI: The demo is at >>>> https://bluejeans.com/s/3ntKd/. Anmol has updated the monitoring >>>> application code to enable the data points required on the list views >>>> UI. The integration is being finalised between the core and the >>>> monitoring APIs and the feature is expected to be fully merged this >>>> week. >>>> >>> >>> >>> It will be great to build new packages after merging this feature. Is >>> there >>> any plan for new packages? >>> >> >> Would the availability of packages (binaries) including this feature >> aid in testing? >> > Yes, packages are used in CI testing. Installing from source is just for > trying changes and partially for test development. > > I am aware of plans for building packages (these were >> pending working through the issues of consuming the build tool rather >> than hand-rolling packages), I'm not specifically familiar with the >> feasibility of building with each merge. >> > Yes, I've meant packages based on master like last time because I expect > that mentioned feature will be merged into master. I expect that they will > be built manually because there is no continuous building as I know. > > There is an on-going >> discussion which I have not followed through on. >> > Yes, there is no update since Dec 20th https://github.com/Tendrl/spec > ifications/issues/53 > > -- > Best Regards, > Martin Kudlej. > RHSC/USM Senior Quality Assurance Engineer > Red Hat Czech s.r.o. > > Phone: +420 532 294 155 > E-mail:mkudlej at redhat.com > IRC: mkudlej at #brno, #gluster, #storage-qa, #rhs, #rh-ceph, > #usm-meeting @ redhat > #tendrl-devel @ freenode > > _______________________________________________ > Tendrl-devel mailing list > Tendrl-devel at redhat.com > https://www.redhat.com/mailman/listinfo/tendrl-devel > -- Jeff Applewhite Principal Product Manager From japplewh at redhat.com Tue Jan 3 18:36:02 2017 From: japplewh at redhat.com (Jeff Applewhite) Date: Tue, 3 Jan 2017 13:36:02 -0500 Subject: [Tendrl-devel] labeling github issues + blockers In-Reply-To: <41a14755-ba58-15b4-ee4b-71ba1f66eb4c@redhat.com> References: <9ecd00cf-3d32-5335-945d-27e89e873e9c@redhat.com> <86df1867-453b-ef8d-0022-21c1018b2d53@redhat.com> <41a14755-ba58-15b4-ee4b-71ba1f66eb4c@redhat.com> Message-ID: ?Just to be clear my reply was not intended to be a definite "No we will never do ?this", only that we should discuss it. We had some earlier discussions around this and I think probably the best approach is to simply add one or more members from the QE team to all the repos with write access (rather than change the default permissions scheme). If this is acceptable to all I'll take care of it. Jeff On Tue, Jan 3, 2017 at 12:11 PM, Martin Kudlej wrote: > Hi all, > > because we cannot add labels in all Tendrl repositories(see below), we've > created page with list of github issues and pull request which are more > important for QE than rest of them. > You can find there also issues which are blocking us. > > Please look at https://github.com/Tendrl/usmqe-tests/wiki > > Thank you for fixing blockers soon! > > On 12/21/2016 11:37 PM, Jeff Applewhite wrote: > >> Done for the QE group for both of your usmqe-* repos - for other repos >> this >> requires write access on the repo. >> >> We probably need some discussion on this before I make that change. By >> default all users get read on all repos. Changing this to write has lots >> of >> implications that should be thought through. Optionally the QE team could >> be added to all the relevant repos with write access. >> >> https://help.github.com/articles/repository-permission- >> levels-for-an-organization/ >> >> >> >> On Wed, Dec 21, 2016 at 3:41 PM, Martin Kudlej >> wrote: >> >> Hi, >>> >>> could admins of github repositories give people from QE team permission >>> to >>> set labels, please? >>> This will be very helpful for us and it gives us ability to better sort >>> and search issues and pull requests in Tendrl repositories. >>> >>> Thank you! >>> >>> On 12/01/2016 11:38 AM, Martin Bukatovic wrote: >>> >>> On 12/01/2016 11:16 AM, Sankarshan Mukhopadhyay wrote: >>>> >>>> On Thu, Dec 1, 2016 at 3:32 PM, Martin Bukatovic >>>>> wrote: >>>>> >>>>> I would like to assign labels (such as "bug" or "question") to github >>>>>> issues I have created, but I don't seem to have the access rights >>>>>> needed. Could you reconfigure the Tendrl github group so that qe team >>>>>> members can add labels to theirs github issues? >>>>>> >>>>>> >>>>> Alright. I'm missing something here. The specific label (names, which >>>>> you indicate) exist. Can you provide me with a link to a particular >>>>> issue? It should be easier for me to figure out what to do. >>>>> >>>>> >>>> The problem I have here is that while the labels exists, and other >>>> team members are using them on some github issues, I'm unable to do >>>> so. >>>> >>>> When I click on "New issue" of any Tendrl project on github, I don't >>>> see the the knobs for setting the label at all [1] - the right panel >>>> which provides those options is missing. Neither I see them when I >>>> try to edit already created issue. Since I'm able to label issues of >>>> my own projects, I suspect that this is related to access rights >>>> of Tendrl github group. >>>> >>>> To try this yourself, try to click on "New issue" button of tendrl >>>> documentation project[2] and compare it with my screenshot[1]. >>>> If you are able to see knobs to set labels in the right panel, while >>>> I'm not provided with this option as shown on the screenshot, we >>>> would need to reconfigure access rights so that the qe team members >>>> can add labels to tendrl github issues. >>>> >>>> Thank you for your help. >>>> >>>> [1] https://ibin.co/33riFN0YCthe.png >>>> [2] https://github.com/Tendrl/documentation/issues/new >>>> >>>> >>>> -- >>> Best Regards, >>> Martin Kudlej. >>> RHSC/USM Senior Quality Assurance Engineer >>> Red Hat Czech s.r.o. >>> >>> Phone: +420 532 294 155 >>> E-mail:mkudlej at redhat.com >>> IRC: mkudlej at #brno, #gluster, #storage-qa, #rhs, #rh-ceph, >>> #usm-meeting @ redhat >>> #tendrl-devel @ freenode >>> >>> >>> _______________________________________________ >>> Tendrl-devel mailing list >>> Tendrl-devel at redhat.com >>> https://www.redhat.com/mailman/listinfo/tendrl-devel >>> >>> >> >> >> > -- > Best Regards, > Martin Kudlej. > RHSC/USM Senior Quality Assurance Engineer > Red Hat Czech s.r.o. > > Phone: +420 532 294 155 > E-mail:mkudlej at redhat.com > IRC: mkudlej at #brno, #gluster, #storage-qa, #rhs, #rh-ceph, > #usm-meeting @ redhat > #tendrl-devel @ freenode > > _______________________________________________ > Tendrl-devel mailing list > Tendrl-devel at redhat.com > https://www.redhat.com/mailman/listinfo/tendrl-devel > -- Jeff Applewhite Principal Product Manager From julim at redhat.com Tue Jan 3 20:14:33 2017 From: julim at redhat.com (Ju Lim) Date: Tue, 3 Jan 2017 15:14:33 -0500 Subject: [Tendrl-devel] storage lists in UI In-Reply-To: <0b8aaee5-68dd-796a-4616-a501d2dbd9e8@redhat.com> References: <76636416-9d99-f17b-e7ed-75caf9bbd317@redhat.com> <0b8aaee5-68dd-796a-4616-a501d2dbd9e8@redhat.com> Message-ID: Martin: Regarding why we split the list of "storages" to: Pools(Ceph), RBDs(Ceph), File shares(Gluster). Yes, one can argue that Pools and volumes are some level similar (until the volume is exported and mounted elsewhere. If you do combine them, we?d still have to provide mechanisms by which to filter them by the ?type? which then introduces deeper levels of navigation (multiple clicks). From a navigation best practice, one of the things we always want to avoid is very deep levels of navigation. Another consideration is what would we call the combined Pools and file Shares? Would we call it Storage, Pools and File Shares, or something else? What happens when a 3rd party storage subsystem gets added? Additionally, having them at the top level (1st level navigation) allows for a better user experience for single storage subsystems use scenarios, whereby the storage subsystem?s (Ceph / Gluster) top-level storage entities are easily located and not buried (at a secondary level) and does not require additional filtering at initial use. Another consideration is that the user who manages Ceph vs. Gluster may be different user/team in an organization, and they would not expect them (Ceph pool and Gluster volumes) to be intermingled in the same view. Note: Some of this was previously discussed in the threads related to the IA design: - https://www.redhat.com/archives/tendrl-devel/2016-September/msg00075.html - https://www.redhat.com/archives/tendrl-devel/2016-October/msg00000.html - https://www.redhat.com/archives/tendrl-devel/2016-October/msg00006.html I hope this clarifies your question. Regards, Ju On Mon, Jan 2, 2017 at 4:48 PM, Ric Wheeler wrote: > On 01/02/2017 08:52 AM, Martin Kudlej wrote: > >> Hi all, >> >> I would like to ask what are reasons to split list of "storages" to: >> Pools(Ceph), RBDs(Ceph), File shares(Gluster)? >> See https://redhat.invisionapp.com/share/BR8JDCGSQ#/screens >> >> From my point of view (please forgive my ignorance) there is no >> difference between Pools(Ceph) and Volume(Gluster) until volume is mounted >> somehow(native client, SMB, NFS). But volume has its state and attributes >> like pool(Ceph) so there is reason to show list of volumes like in case of >> pools. >> >> I don't remember exact arguments why it is designed like this. Could >> somebody make it clear, please? >> >> The first level, consumable things are file, block or object stores. I > would say the split would be something like RBD's, file shares and RGW > (object) instances. Below that layer is the pool or brick, etc... > > > ric > > > > _______________________________________________ > Tendrl-devel mailing list > Tendrl-devel at redhat.com > https://www.redhat.com/mailman/listinfo/tendrl-devel > -- Ju Lim Red Hat Office: 978-399-0422 Mobile: 781-507-1323 Email: julim at redhat.com IRC: julim From sankarshan.mukhopadhyay at gmail.com Wed Jan 4 02:37:49 2017 From: sankarshan.mukhopadhyay at gmail.com (Sankarshan Mukhopadhyay) Date: Wed, 4 Jan 2017 08:07:49 +0530 Subject: [Tendrl-devel] [TRACKING] Summary for the week of 26th Dec, priorities for the week of 2nd Jan In-Reply-To: References: <92f77947-6b7f-841f-f2df-f7c6742ebe44@redhat.com> Message-ID: On Tue, Jan 3, 2017 at 11:05 PM, Jeff Applewhite wrote: > I am keen to get this solved for a number of reasons. Packages are > important for testing, developer enablement, completeness and meeting the > DoD. Chris B has volunteered to assist on the packaging effort if needed. > What is the blocking issue? Is there somewhere he could pitch in? I took a look at the ticket/issue Martin referenced earlier in this thread. It would seem that this is "things we need to complete for building against merges" rather than blocking. If Chris would like to chip in, that's the issue # to work on. -- sankarshan mukhopadhyay From mkudlej at redhat.com Wed Jan 4 08:18:39 2017 From: mkudlej at redhat.com (Martin Kudlej) Date: Wed, 4 Jan 2017 09:18:39 +0100 Subject: [Tendrl-devel] labeling github issues + blockers In-Reply-To: References: <9ecd00cf-3d32-5335-945d-27e89e873e9c@redhat.com> <86df1867-453b-ef8d-0022-21c1018b2d53@redhat.com> <41a14755-ba58-15b4-ee4b-71ba1f66eb4c@redhat.com> Message-ID: <42e6eadd-bd1a-d05a-8550-4af49dd314de@redhat.com> Hi Jeff, I understand how have you meant that. I've just needed to solve labeling to sort github issues and pull requests to be able to watch more important ones. On 01/03/2017 07:36 PM, Jeff Applewhite wrote: > ?Just to be clear my reply was not intended to be a definite "No we will > never do ?this", only that we should discuss it. We had some earlier > discussions around this and I think probably the best approach is to simply > add one or more members from the QE team to all the repos with write access > (rather than change the default permissions scheme). If this is acceptable > to all I'll take care of it. > > Jeff > > On Tue, Jan 3, 2017 at 12:11 PM, Martin Kudlej wrote: > >> Hi all, >> >> because we cannot add labels in all Tendrl repositories(see below), we've >> created page with list of github issues and pull request which are more >> important for QE than rest of them. >> You can find there also issues which are blocking us. >> >> Please look at https://github.com/Tendrl/usmqe-tests/wiki >> >> Thank you for fixing blockers soon! >> >> On 12/21/2016 11:37 PM, Jeff Applewhite wrote: >> >>> Done for the QE group for both of your usmqe-* repos - for other repos >>> this >>> requires write access on the repo. >>> >>> We probably need some discussion on this before I make that change. By >>> default all users get read on all repos. Changing this to write has lots >>> of >>> implications that should be thought through. Optionally the QE team could >>> be added to all the relevant repos with write access. >>> >>> https://help.github.com/articles/repository-permission- >>> levels-for-an-organization/ >>> >>> >>> >>> On Wed, Dec 21, 2016 at 3:41 PM, Martin Kudlej >>> wrote: >>> >>> Hi, >>>> >>>> could admins of github repositories give people from QE team permission >>>> to >>>> set labels, please? >>>> This will be very helpful for us and it gives us ability to better sort >>>> and search issues and pull requests in Tendrl repositories. >>>> >>>> Thank you! >>>> >>>> On 12/01/2016 11:38 AM, Martin Bukatovic wrote: >>>> >>>> On 12/01/2016 11:16 AM, Sankarshan Mukhopadhyay wrote: >>>>> >>>>> On Thu, Dec 1, 2016 at 3:32 PM, Martin Bukatovic >>>>>> wrote: >>>>>> >>>>>> I would like to assign labels (such as "bug" or "question") to github >>>>>>> issues I have created, but I don't seem to have the access rights >>>>>>> needed. Could you reconfigure the Tendrl github group so that qe team >>>>>>> members can add labels to theirs github issues? >>>>>>> >>>>>>> >>>>>> Alright. I'm missing something here. The specific label (names, which >>>>>> you indicate) exist. Can you provide me with a link to a particular >>>>>> issue? It should be easier for me to figure out what to do. >>>>>> >>>>>> >>>>> The problem I have here is that while the labels exists, and other >>>>> team members are using them on some github issues, I'm unable to do >>>>> so. >>>>> >>>>> When I click on "New issue" of any Tendrl project on github, I don't >>>>> see the the knobs for setting the label at all [1] - the right panel >>>>> which provides those options is missing. Neither I see them when I >>>>> try to edit already created issue. Since I'm able to label issues of >>>>> my own projects, I suspect that this is related to access rights >>>>> of Tendrl github group. >>>>> >>>>> To try this yourself, try to click on "New issue" button of tendrl >>>>> documentation project[2] and compare it with my screenshot[1]. >>>>> If you are able to see knobs to set labels in the right panel, while >>>>> I'm not provided with this option as shown on the screenshot, we >>>>> would need to reconfigure access rights so that the qe team members >>>>> can add labels to tendrl github issues. >>>>> >>>>> Thank you for your help. >>>>> >>>>> [1] https://ibin.co/33riFN0YCthe.png >>>>> [2] https://github.com/Tendrl/documentation/issues/new >>>>> >>>>> >>>>> -- >>>> Best Regards, >>>> Martin Kudlej. >>>> RHSC/USM Senior Quality Assurance Engineer >>>> Red Hat Czech s.r.o. >>>> >>>> Phone: +420 532 294 155 >>>> E-mail:mkudlej at redhat.com >>>> IRC: mkudlej at #brno, #gluster, #storage-qa, #rhs, #rh-ceph, >>>> #usm-meeting @ redhat >>>> #tendrl-devel @ freenode >>>> >>>> >>>> _______________________________________________ >>>> Tendrl-devel mailing list >>>> Tendrl-devel at redhat.com >>>> https://www.redhat.com/mailman/listinfo/tendrl-devel >>>> >>>> >>> >>> >>> >> -- >> Best Regards, >> Martin Kudlej. >> RHSC/USM Senior Quality Assurance Engineer >> Red Hat Czech s.r.o. >> >> Phone: +420 532 294 155 >> E-mail:mkudlej at redhat.com >> IRC: mkudlej at #brno, #gluster, #storage-qa, #rhs, #rh-ceph, >> #usm-meeting @ redhat >> #tendrl-devel @ freenode >> >> _______________________________________________ >> Tendrl-devel mailing list >> Tendrl-devel at redhat.com >> https://www.redhat.com/mailman/listinfo/tendrl-devel >> > > > -- Best Regards, Martin Kudlej. RHSC/USM Senior Quality Assurance Engineer Red Hat Czech s.r.o. Phone: +420 532 294 155 E-mail:mkudlej at redhat.com IRC: mkudlej at #brno, #gluster, #storage-qa, #rhs, #rh-ceph, #usm-meeting @ redhat #tendrl-devel @ freenode From mkudlej at redhat.com Wed Jan 4 08:23:57 2017 From: mkudlej at redhat.com (Martin Kudlej) Date: Wed, 4 Jan 2017 09:23:57 +0100 Subject: [Tendrl-devel] storage lists in UI In-Reply-To: References: <76636416-9d99-f17b-e7ed-75caf9bbd317@redhat.com> <0b8aaee5-68dd-796a-4616-a501d2dbd9e8@redhat.com> Message-ID: <22c65301-eac7-ebf3-a177-0de5e0251798@redhat.com> Hi Ju, thank you for response! On 01/03/2017 09:14 PM, Ju Lim wrote: > Martin: > > Regarding why we split the list of "storages" to: Pools(Ceph), RBDs(Ceph), > File shares(Gluster). > > Yes, one can argue that Pools and volumes are some level similar (until the > volume is exported and mounted elsewhere. If you do combine them, we?d > still have to provide mechanisms by which to filter them by the ?type? > which then introduces deeper levels of navigation (multiple clicks). From > a navigation best practice, one of the things we always want to avoid is > very deep levels of navigation. Another consideration is what would we > call the combined Pools and file Shares? Would we call it Storage, Pools > and File Shares, or something else? What happens when a 3rd party storage > subsystem gets added? > > Additionally, having them at the top level (1st level navigation) allows > for a better user experience for single storage subsystems use scenarios, > whereby the storage subsystem?s (Ceph / Gluster) top-level storage entities > are easily located and not buried (at a secondary level) and does not > require additional filtering at initial use. > > Another consideration is that the user who manages Ceph vs. Gluster may be > different user/team in an organization, and they would not expect them > (Ceph pool and Gluster volumes) to be intermingled in the same view. > > Note: Some of this was previously discussed in the threads related to the > IA design: > > - > https://www.redhat.com/archives/tendrl-devel/2016-September/msg00075.html > - https://www.redhat.com/archives/tendrl-devel/2016-October/msg00000.html > - https://www.redhat.com/archives/tendrl-devel/2016-October/msg00006.html > > I hope this clarifies your question. > > Regards, > Ju > > On Mon, Jan 2, 2017 at 4:48 PM, Ric Wheeler wrote: > >> On 01/02/2017 08:52 AM, Martin Kudlej wrote: >> >>> Hi all, >>> >>> I would like to ask what are reasons to split list of "storages" to: >>> Pools(Ceph), RBDs(Ceph), File shares(Gluster)? >>> See https://redhat.invisionapp.com/share/BR8JDCGSQ#/screens >>> >>> From my point of view (please forgive my ignorance) there is no >>> difference between Pools(Ceph) and Volume(Gluster) until volume is mounted >>> somehow(native client, SMB, NFS). But volume has its state and attributes >>> like pool(Ceph) so there is reason to show list of volumes like in case of >>> pools. >>> >>> I don't remember exact arguments why it is designed like this. Could >>> somebody make it clear, please? >>> >>> The first level, consumable things are file, block or object stores. I >> would say the split would be something like RBD's, file shares and RGW >> (object) instances. Below that layer is the pool or brick, etc... >> >> >> ric >> >> >> >> _______________________________________________ >> Tendrl-devel mailing list >> Tendrl-devel at redhat.com >> https://www.redhat.com/mailman/listinfo/tendrl-devel >> > > > -- Best Regards, Martin Kudlej. RHSC/USM Senior Quality Assurance Engineer Red Hat Czech s.r.o. Phone: +420 532 294 155 E-mail:mkudlej at redhat.com IRC: mkudlej at #brno, #gluster, #storage-qa, #rhs, #rh-ceph, #usm-meeting @ redhat #tendrl-devel @ freenode From mbukatov at redhat.com Wed Jan 4 12:28:38 2017 From: mbukatov at redhat.com (Martin Bukatovic) Date: Wed, 4 Jan 2017 13:28:38 +0100 Subject: [Tendrl-devel] correction: blocking issues Message-ID: <78a14bd3-1a2c-f33b-f980-6c472d552630@redhat.com> Dear all, I noticed I did a typo during today's check in meeting[1], where I posted the following links to issues which causes installation from latest sources to not work: https://github.com/Tendrl/tendrl-api/issues/3 (mbukatov, 09:24:23) https://github.com/Tendrl/tendrl_frontend/issues/7 (mbukatov, 09:24:29) But those links are pointing to old, closed issues. I did a mistake when copy pasting prepared lines, dropping last digit in the url during this process. The correct links are: https://github.com/Tendrl/tendrl-api/issues/31 https://github.com/Tendrl/tendrl_frontend/issues/79 You can also check the list in github wikipage[2]. Sorry for the confusion. [1] https://meetbot.fedoraproject.org/tendrl-devel/2017-01-04/check-in_20170104.2017-01-04-09.09.html [2] https://github.com/Tendrl/usmqe-tests/wiki#blockers -- Martin Bukatovic USM QE team From shtripat at redhat.com Thu Jan 5 04:41:07 2017 From: shtripat at redhat.com (Shubhendu Tripathi) Date: Thu, 5 Jan 2017 10:11:07 +0530 Subject: [Tendrl-devel] [TRACKING] Daily check-in summary for 20170104 Message-ID: FORGOT TO SEND IMMEDIATELY YESTERDAY... https://meetbot.fedoraproject.org/tendrl-devel/2017-01-04/check-in_20170104.2017-01-04-09.09.html Regards, Shubhendu From rkanade at redhat.com Thu Jan 5 09:40:24 2017 From: rkanade at redhat.com (Rohan Kanade) Date: Thu, 5 Jan 2017 15:10:24 +0530 Subject: [Tendrl-devel] About Tendrl Global configurations, log files and Tendrl specific local data Message-ID: While going through some current PRs and merged code, it seems we need clear guidance on where config, logs, local data is supposed to be in Tendrl Here it goes: - Tendrl Component level configuration : /etc/tendrl/.config OR can be defined (Tendrl definitions) via the "Config" object for that Tendrl component and stored in central store - Tendrl data read-write -> /var/lib/tendrl/ Further reading: https://en.wikipedia.org/wiki/Filesystem_Hierarchy_Standard If you have encountered PRs or merged code not confirming to above guidelines, please report bugs Regards, Rohan Kanade From nthomas at redhat.com Thu Jan 5 13:32:03 2017 From: nthomas at redhat.com (Nishanth Thomas) Date: Thu, 5 Jan 2017 19:02:03 +0530 Subject: [Tendrl-devel] [TRACKING] Daily check-in summary for 20170105 Message-ID: https://meetbot.fedoraproject.org/tendrl-devel/2017-01-05/check-in_20170105.2017-01-05-09.02.html Thanks, Nishanth From ricwheeler at gmail.com Thu Jan 5 22:32:40 2017 From: ricwheeler at gmail.com (Ric Wheeler) Date: Thu, 5 Jan 2017 17:32:40 -0500 Subject: [Tendrl-devel] Linux Foundation's open source file & storage conference CFP Message-ID: <2ac7ee2c-e30f-7393-e458-ab807e2bd53d@gmail.com> Hi all, The CFP for the Linux Foundation's Vault conference is coming close to an end. The event is being held this year in Cambridge, Massachusetts on the days following the LSF/MM summit. The first two year's events have been solid, focused events in my (slightly biased) opinion, so worth submitting to and definitely worth attending. Submit a Proposal to Speak at Vault, Linux Storage and Filesystems Conference. Vault will be held alongside LSF-MM Summit on March 22 & 23 in Cambridge, MA. To submit (by 1/14) visit http://events.linuxfoundation.org/events/vault/program/cfp Happy to answer any questions about the event. Ric From kdreyer at redhat.com Fri Jan 6 00:03:14 2017 From: kdreyer at redhat.com (Ken Dreyer) Date: Thu, 5 Jan 2017 17:03:14 -0700 Subject: [Tendrl-devel] streamlining new versions release process Message-ID: Hi folks, It's tedious to manage version numbers by hand, and it's multiplied by the number of repositories Tendrl has. I've copied the model that we use for ceph-installer package releases and proposed it for the node_agent repo: https://github.com/Tendrl/node_agent/pull/125 The goal with this is to make "release early, release often" feasible. With this change, bumping the package release number is trivial: $ python setup.py bump running bump old version: 1.1 new version: 1.2 Press enter to confirm, or ctrl-c to exit > git commit -a -m version 1.2 [master 9a7351d] version 1.2 2 files changed, 2 insertions(+), 2 deletions(-) Tagging a new version in Git is also simple: $ python setup.py release running release git tag -a v1.2 -m version 1.2 git push origin v1.2 ... This keeps the version numbers fully aligned between the Python __version__ variable, Makefile, RPM .spec file, and distutils metadata in setup.py. It also makes it easy to handle SemVer, because you can pass an arbitrary "--release" argument to "setup.py bump" if you're making breaking changes: $ python setup.py bump --release 2.0 running bump old version: 1.1 new version: 2.0 Press enter to confirm, or ctrl-c to exit > - Ken From japplewh at redhat.com Fri Jan 6 00:21:45 2017 From: japplewh at redhat.com (Jeff Applewhite) Date: Thu, 5 Jan 2017 19:21:45 -0500 Subject: [Tendrl-devel] Linux Foundation's open source file & storage conference CFP In-Reply-To: <2ac7ee2c-e30f-7393-e458-ab807e2bd53d@gmail.com> References: <2ac7ee2c-e30f-7393-e458-ab807e2bd53d@gmail.com> Message-ID: Hi Ric Yes I thought that would be a good venue - I submitted a proposal for this and a couple of other events back in November so we are covered. Cross your fingers (and vote if you get a chance!). Thanks Jeff On Thu, Jan 5, 2017 at 5:32 PM, Ric Wheeler wrote: > Hi all, > > The CFP for the Linux Foundation's Vault conference is coming close to an > end. The event is being held this year in Cambridge, Massachusetts on the > days following the LSF/MM summit. > > The first two year's events have been solid, focused events in my (slightly > biased) opinion, so worth submitting to and definitely worth attending. > > Submit a Proposal to Speak at Vault, Linux Storage and Filesystems > Conference. Vault will be held alongside LSF-MM Summit on March 22 & 23 in > Cambridge, MA. To submit (by 1/14) visit > http://events.linuxfoundation.org/events/vault/program/cfp > > Happy to answer any questions about the event. > > Ric > > _______________________________________________ > Tendrl-devel mailing list > Tendrl-devel at redhat.com > https://www.redhat.com/mailman/listinfo/tendrl-devel -- Jeff Applewhite Principal Product Manager From nthomas at redhat.com Mon Jan 9 11:06:22 2017 From: nthomas at redhat.com (Nishanth Thomas) Date: Mon, 9 Jan 2017 16:36:22 +0530 Subject: [Tendrl-devel] [TRACKING] Daily check-in summary for 20170109 Message-ID: https://meetbot.fedoraproject.org/tendrl-devel/2017-01-09/check-in_20170109.2017-01-09-09.02.html Thanks, Nishanth From mrugesh at brainfunked.org Mon Jan 9 12:28:47 2017 From: mrugesh at brainfunked.org (Mrugesh Karnik) Date: Mon, 9 Jan 2017 17:58:47 +0530 Subject: [Tendrl-devel] [TRACKING] Summary for the week of 2nd Jan, priorities for the week of 9th Jan Message-ID: All the listed ids are of issues on the specifications repository (https://github.com/specifications/issues) Work in progress, to be continued this week: * Import cluster via the UI: Multiple specifications are being worked on including import cluster workflow, service detection modules, UI, tagged logging, in-flight operation updates etc. (#46, #54, #56, #28 and #55). * Alerting: The code with SMTP based alerts is under review. * Create cluster workflows: Both Ceph and Gluster related flows are being worked on, including the details regarding the integration and wrapper modules required to integrate with the respective provisioning systems (#48, #49, #50, #51, #52). Along with these development tasks, we're also working on: * Automated builds. The priority is to get automated builds to be triggered based on changes in master first. * Workflow updates. To synchronise development across all the component changes against a specification. All the commits against a specification will be made to the branch with the same name across all respositories. This would also play a part in building feature specific packages from topic branches. * Jira linking: Starting with the import cluster functionality, we're adding metadata to auto-link the commits to jira issues that discuss the feature. -- Mrugesh From kdreyer at redhat.com Mon Jan 9 21:22:34 2017 From: kdreyer at redhat.com (Ken Dreyer) Date: Mon, 9 Jan 2017 14:22:34 -0700 Subject: [Tendrl-devel] streamlining new versions release process In-Reply-To: References: Message-ID: Thanks for the merge in node_agent #125. Once you tag and push a new release, like so: python setup.py bumpversion python setup.py release You can build this in Copr, like: make srpm copr-cli build tendrl/tendrl *.src.rpm It would be ideal if GitHub would notify Copr to do the build automatically, but Copr does not yet support listening for new tags (https://pagure.io/copr/copr/pull-request/22) In the meantime, we'll need a Jenkins instance to automate the "copr-cli build" step, or else do it by hand. In terms of building dev snapshot RPMs of every push to master, you'll want a Jenkins job that does something like: git clone https://github.com/Tendrl/node-agent make snapshot mock -r tendrl-copr.cfg rebuild *.src.rpm --resultdir=results (publish results/*.rpm to some location, and generate repository metadata) - Ken On Thu, Jan 5, 2017 at 5:03 PM, Ken Dreyer wrote: > Hi folks, > > It's tedious to manage version numbers by hand, and it's multiplied by > the number of repositories Tendrl has. > > I've copied the model that we use for ceph-installer package releases > and proposed it for the node_agent repo: > > https://github.com/Tendrl/node_agent/pull/125 > > The goal with this is to make "release early, release often" feasible. > > With this change, bumping the package release number is trivial: > > $ python setup.py bump > running bump > old version: 1.1 new version: 1.2 > Press enter to confirm, or ctrl-c to exit > > git commit -a -m version 1.2 > [master 9a7351d] version 1.2 > 2 files changed, 2 insertions(+), 2 deletions(-) > > Tagging a new version in Git is also simple: > > $ python setup.py release > running release > git tag -a v1.2 -m version 1.2 > git push origin v1.2 > ... > > This keeps the version numbers fully aligned between the Python > __version__ variable, Makefile, RPM .spec file, and distutils metadata > in setup.py. > > It also makes it easy to handle SemVer, because you can pass an > arbitrary "--release" argument to "setup.py bump" if you're making > breaking changes: > > $ python setup.py bump --release 2.0 > running bump > old version: 1.1 new version: 2.0 > Press enter to confirm, or ctrl-c to exit > > > - Ken From mrugesh at brainfunked.org Tue Jan 10 10:22:34 2017 From: mrugesh at brainfunked.org (Mrugesh Karnik) Date: Tue, 10 Jan 2017 15:52:34 +0530 Subject: [Tendrl-devel] [TRACKING] Daily check-in summary for 20170110 Message-ID: https://meetbot.fedoraproject.org/tendrl-devel/2017-01-10/check-in_20170110.2017-01-10-09.01.html -- Mrugesh From julim at redhat.com Tue Jan 10 13:30:45 2017 From: julim at redhat.com (Ju Lim) Date: Tue, 10 Jan 2017 08:30:45 -0500 Subject: [Tendrl-devel] Tendrl Sprint 8 Demo Details (Recording & Notes) Message-ID: Team: The demo recording from the Sprint 8 demo is now available along with the final agenda and notes (feedback and Q&A). They can be found at Sprint 008 Demo Agenda & Notes . Note: We didn't get through the Import Cluster UI demo, and there's an action item for Kamlesh to record and share the recording. If folks have any comments and/or feedback on the demo(s), please reply all to this email thread. As always, all Sprint goals, demo agenda, demo recording, and notes may be found at the Tendrl Sprints Landing Page , which is an index of all sprints to-date. Thank you, Ju From mcarrano at redhat.com Tue Jan 10 16:06:26 2017 From: mcarrano at redhat.com (Matt Carrano) Date: Tue, 10 Jan 2017 11:06:26 -0500 Subject: [Tendrl-devel] Tendrl Sprint 8 Demo Details (Recording & Notes) In-Reply-To: References: Message-ID: Hi Ju, Thanks for sharing the demo recording. It was interesting to see that in the Pools listing it appeared that there were duplicates because both were named 'rbd' so one must look all the way over to find the cluster name to know they are different. Do you think this type of duplicate naming will occur often in the "real world?" If so, perhaps we should do something different to associate the cluster name and object name more closely in the list views. Thoughts? Also, I wonder why RBDs are displaying in the Pools view. Shouldn't they show in a separate RBD list view? Matt On Tue, Jan 10, 2017 at 8:30 AM, Ju Lim wrote: > Team: > > The demo recording from the Sprint 8 demo is now available along with the > final agenda and notes (feedback and Q&A). They can be found at Sprint 008 > Demo Agenda & Notes > . > > Note: We didn't get through the Import Cluster UI demo, and there's an > action item for Kamlesh to record and share the recording. > > If folks have any comments and/or feedback on the demo(s), please reply all > to this email thread. > > As always, all Sprint goals, demo agenda, demo recording, and notes may be > found at the Tendrl Sprints Landing Page > , which is an index > of all sprints to-date. > > Thank you, > Ju > _______________________________________________ > Tendrl-devel mailing list > Tendrl-devel at redhat.com > https://www.redhat.com/mailman/listinfo/tendrl-devel > -- Matt Carrano Sr. Interaction Designer Red Hat, Inc. mcarrano at redhat.com From jspray at redhat.com Tue Jan 10 16:24:54 2017 From: jspray at redhat.com (John Spray) Date: Tue, 10 Jan 2017 16:24:54 +0000 Subject: [Tendrl-devel] Tendrl Sprint 8 Demo Details (Recording & Notes) In-Reply-To: References: Message-ID: On Tue, Jan 10, 2017 at 4:06 PM, Matt Carrano wrote: > Hi Ju, > > Thanks for sharing the demo recording. It was interesting to see that in > the Pools listing it appeared that there were duplicates because both were > named 'rbd' so one must look all the way over to find the cluster name to > know they are different. > > Do you think this type of duplicate naming will occur often in the "real > world?" If so, perhaps we should do something different to associate the > cluster name and object name more closely in the list views. Thoughts? "rbd" is the default pool that exists on any newly created ceph cluster, so everyone has one unless they delete it. It's also worth noting that even if someone has two clusters, there's a good chance they'll both be called "ceph" unless they are sharing hardware (in which case the admin would have had to pick distinct names). Cheers, John > > Also, I wonder why RBDs are displaying in the Pools view. Shouldn't they > show in a separate RBD list view? > > Matt > > On Tue, Jan 10, 2017 at 8:30 AM, Ju Lim wrote: > >> Team: >> >> The demo recording from the Sprint 8 demo is now available along with the >> final agenda and notes (feedback and Q&A). They can be found at Sprint 008 >> Demo Agenda & Notes >> . >> >> Note: We didn't get through the Import Cluster UI demo, and there's an >> action item for Kamlesh to record and share the recording. >> >> If folks have any comments and/or feedback on the demo(s), please reply all >> to this email thread. >> >> As always, all Sprint goals, demo agenda, demo recording, and notes may be >> found at the Tendrl Sprints Landing Page >> , which is an index >> of all sprints to-date. >> >> Thank you, >> Ju >> _______________________________________________ >> Tendrl-devel mailing list >> Tendrl-devel at redhat.com >> https://www.redhat.com/mailman/listinfo/tendrl-devel >> > > > > -- > Matt Carrano > Sr. Interaction Designer > Red Hat, Inc. > mcarrano at redhat.com > _______________________________________________ > Tendrl-devel mailing list > Tendrl-devel at redhat.com > https://www.redhat.com/mailman/listinfo/tendrl-devel From julim at redhat.com Tue Jan 10 17:45:51 2017 From: julim at redhat.com (Ju Lim) Date: Tue, 10 Jan 2017 12:45:51 -0500 Subject: [Tendrl-devel] Tendrl Sprint 8 Demo Details (Recording & Notes) In-Reply-To: References: Message-ID: As John's noted, RBD is a default pool created today for Ceph. For Tendrl (and previous release), we will be removing it during Ceph cluster creation. That being said, it is valid that RBD's will appear, and that we need the cluster name to show closer to the pool name (and not be divided by the utilization), so the user can uniquely identify the pool. WRT cluster name, it's not yet in the spec, but Mrugesh mentioned (in a separate discussion after the demo) that they are planning to tackle not allowing for duplicate cluster names. Regards, Ju On Tue, Jan 10, 2017 at 11:24 AM, John Spray wrote: > On Tue, Jan 10, 2017 at 4:06 PM, Matt Carrano wrote: > > Hi Ju, > > > > Thanks for sharing the demo recording. It was interesting to see that in > > the Pools listing it appeared that there were duplicates because both > were > > named 'rbd' so one must look all the way over to find the cluster name > to > > know they are different. > > > > Do you think this type of duplicate naming will occur often in the "real > > world?" If so, perhaps we should do something different to associate the > > cluster name and object name more closely in the list views. Thoughts? > > "rbd" is the default pool that exists on any newly created ceph > cluster, so everyone has one unless they delete it. It's also worth > noting that even if someone has two clusters, there's a good chance > they'll both be called "ceph" unless they are sharing hardware (in > which case the admin would have had to pick distinct names). > > Cheers, > John > > > > > Also, I wonder why RBDs are displaying in the Pools view. Shouldn't they > > show in a separate RBD list view? > > > > Matt > > > > On Tue, Jan 10, 2017 at 8:30 AM, Ju Lim wrote: > > > >> Team: > >> > >> The demo recording from the Sprint 8 demo is now available along with > the > >> final agenda and notes (feedback and Q&A). They can be found at Sprint > 008 > >> Demo Agenda & Notes > >> pageId=20873218>. > >> > >> Note: We didn't get through the Import Cluster UI demo, and there's an > >> action item for Kamlesh to record and share the recording. > >> > >> If folks have any comments and/or feedback on the demo(s), please reply > all > >> to this email thread. > >> > >> As always, all Sprint goals, demo agenda, demo recording, and notes may > be > >> found at the Tendrl Sprints Landing Page > >> , which is an > index > >> of all sprints to-date. > >> > >> Thank you, > >> Ju > >> _______________________________________________ > >> Tendrl-devel mailing list > >> Tendrl-devel at redhat.com > >> https://www.redhat.com/mailman/listinfo/tendrl-devel > >> > > > > > > > > -- > > Matt Carrano > > Sr. Interaction Designer > > Red Hat, Inc. > > mcarrano at redhat.com > > _______________________________________________ > > 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 > -- Ju Lim Red Hat Office: 978-399-0422 Mobile: 781-507-1323 Email: julim at redhat.com IRC: julim From japplewh at redhat.com Tue Jan 10 21:18:58 2017 From: japplewh at redhat.com (Jeff Applewhite) Date: Tue, 10 Jan 2017 16:18:58 -0500 Subject: [Tendrl-devel] Sprint 9 Message-ID: Hi All Please take a look at the sprint landing page and update status on items as they progress from backlog to done during daily standups. https://tendrl.atlassian.net/secure/RapidBoard.jspa?projectKey=TEN&rapidView=11 Thanks! -- Jeff Applewhite Principal Product Manager From kaverma at redhat.com Wed Jan 11 04:39:01 2017 From: kaverma at redhat.com (Kamlesh Verma) Date: Tue, 10 Jan 2017 23:39:01 -0500 (EST) Subject: [Tendrl-devel] Import cluster workflow from UI (Recording) In-Reply-To: <1067367897.10644224.1484107269188.JavaMail.zimbra@redhat.com> Message-ID: <531649104.10646399.1484109541005.JavaMail.zimbra@redhat.com> Team: The demo recording for "import cluster workflow" is now available. it can be found at below link https://bluejeans.com/s/yRC9D/. Note: "import cluster workflow" is done via mocked data for now . If folks have any comments , questions or feedback on the recorded demo, please reply all to this email thread. Thanks and Regards Kamlesh kumar verma From rkanade at redhat.com Wed Jan 11 08:11:07 2017 From: rkanade at redhat.com (Rohan Kanade) Date: Wed, 11 Jan 2017 13:41:07 +0530 Subject: [Tendrl-devel] Tendrl timestamps and timezones in python (Must read) Message-ID: Hi, In case of confusions as to how datetimes and timestamps be represented in Tendrl python projects and Tendrl-api, please take guidance from below items - -Always use aware datetime object, i.e. with timezone information. That makes sure you can compare them directly (aware and unaware datetime objects are not comparable) and will return them correctly to users. Leverage "pytz" to have timezone objects. - Use ISO 8601 as input and output string format. Use datetime.datetime.isoformat() to return timestamps as string formatted using that format, which includes the timezone information. More reading: https://julien.danjou.info/blog/2015/python-and-timezones From nthomas at redhat.com Wed Jan 11 10:29:48 2017 From: nthomas at redhat.com (Nishanth Thomas) Date: Wed, 11 Jan 2017 15:59:48 +0530 Subject: [Tendrl-devel] [TRACKING] Daily check-in summary for 20170111 Message-ID: https://meetbot.fedoraproject.org/tendrl-devel/2017-01-11/check-in_20170111.2017-01-11-09.15.html Thanks, Nishanth From rkanade at redhat.com Wed Jan 11 10:43:09 2017 From: rkanade at redhat.com (Rohan Kanade) Date: Wed, 11 Jan 2017 16:13:09 +0530 Subject: [Tendrl-devel] [Reading] Ease of using plugins and pluggable components in Tendrl Alerting/Notifications Message-ID: Hi, Currently Tendrl alerting and notification components allow pluggable python modules to be loaded at runtime. Moving ahead, It would be ideal to use existing python tools for Dynamic plugin management Reading: http://docs.openstack.org/developer/stevedore/ From rkanade at redhat.com Thu Jan 12 07:27:34 2017 From: rkanade at redhat.com (Rohan Kanade) Date: Thu, 12 Jan 2017 12:57:34 +0530 Subject: [Tendrl-devel] Tendrl code review best practices Message-ID: Hi, While reviewing pull requests for Tendrl projects, these are a few items I usually review, please add/elaborate more if i missed something, would be great to turn our inputs into a review check list. Here are mine for any given Pull request: - Check code for CPU impact (long running loops, blocking calls etc) - Check for IO (disk and network, etcd/db) impact (local files, network calls to etcd or others, etcd performance) - Check for Tendrl and Linux security impact (does the patch respect Tendrl namespaces and data model and ops model, does the patch respect Linux userland security best practices) - Check Scalability (does the PR work in multi node Tendrl deployment) - Check readability and maintainability of the code - Check packaging and infra and details introduced in the PR - Check QE impact (unit tests, functional test-ability) - Check for core Tendrl logic (Tendrl definitions, use of commons etc) - Check for python syntax and object oriented programming and software design principles From sankarshan.mukhopadhyay at gmail.com Thu Jan 12 08:37:49 2017 From: sankarshan.mukhopadhyay at gmail.com (Sankarshan Mukhopadhyay) Date: Thu, 12 Jan 2017 14:07:49 +0530 Subject: [Tendrl-devel] Tendrl code review best practices In-Reply-To: References: Message-ID: On Thu, Jan 12, 2017 at 12:57 PM, Rohan Kanade wrote: > Here are mine for any given Pull request: > > - Check code for CPU impact (long running loops, blocking calls etc) > > - Check for IO (disk and network, etcd/db) impact (local files, network > calls to etcd or others, etcd performance) > > - Check for Tendrl and Linux security impact (does the patch respect Tendrl > namespaces and data model and ops model, does the patch respect Linux > userland security best practices) > > - Check Scalability (does the PR work in multi node Tendrl deployment) > > - Check readability and maintainability of the code > > - Check packaging and infra and details introduced in the PR > > - Check QE impact (unit tests, functional test-ability) > > - Check for core Tendrl logic (Tendrl definitions, use of commons etc) > > - Check for python syntax and object oriented programming and software > design principles Thanks for putting together this list. Perhaps this needs to be put together in the contributor documentation so that further additions/improvements can be PR based. Would that be good? -- sankarshan mukhopadhyay From shtripat at redhat.com Thu Jan 12 10:00:57 2017 From: shtripat at redhat.com (Shubhendu Tripathi) Date: Thu, 12 Jan 2017 15:30:57 +0530 Subject: [Tendrl-devel] [TRACKING] Daily check-in summary for 20170112 Message-ID: <4a6d67b1-21cb-68d3-9181-861b1aa56489@redhat.com> https://meetbot.fedoraproject.org/tendrl-devel/2017-01-12/check-in_20170112.2017-01-12-09.14.html Regards, Shubhendu From ltrilety at redhat.com Thu Jan 12 14:26:23 2017 From: ltrilety at redhat.com (Lubos Trilety) Date: Thu, 12 Jan 2017 09:26:23 -0500 (EST) Subject: [Tendrl-devel] Import cluster workflow from UI (Recording) In-Reply-To: <531649104.10646399.1484109541005.JavaMail.zimbra@redhat.com> References: <531649104.10646399.1484109541005.JavaMail.zimbra@redhat.com> Message-ID: <1032025520.1905233.1484231183466.JavaMail.zimbra@redhat.com> Hi, I have one question. I noticed that during import case there's no possibility to choose which 'cluster' should be imported. It seems like the cluster is automatically detected and worked with. So what happens if there will be more than one cluster in the nodes which tendrl is working with? Regards, Lubos ----- Original Message ----- From: "Kamlesh Verma" To: "Mailing list for the contributors to the Tendrl project" Sent: Wednesday, January 11, 2017 5:39:01 AM Subject: [Tendrl-devel] Import cluster workflow from UI (Recording) Team: The demo recording for "import cluster workflow" is now available. it can be found at below link https://bluejeans.com/s/yRC9D/. Note: "import cluster workflow" is done via mocked data for now . If folks have any comments , questions or feedback on the recorded demo, please reply all to this email thread. Thanks and Regards Kamlesh kumar verma _______________________________________________ Tendrl-devel mailing list Tendrl-devel at redhat.com https://www.redhat.com/mailman/listinfo/tendrl-devel From kdreyer at redhat.com Thu Jan 12 17:03:07 2017 From: kdreyer at redhat.com (Ken Dreyer) Date: Thu, 12 Jan 2017 10:03:07 -0700 Subject: [Tendrl-devel] [TRACKING] Daily check-in summary for 20170112 In-Reply-To: <4a6d67b1-21cb-68d3-9181-861b1aa56489@redhat.com> References: <4a6d67b1-21cb-68d3-9181-861b1aa56489@redhat.com> Message-ID: > 09:55:12 > https://copr.fedorainfracloud.org/webhooks/github/10793/c58347dd-89a0-45ae-b274-c5dc7ef470db/ > 09:55:12 configured tendrl-commons to get the latest source from > github master branch and build on user trigger and enabled auto build. If GitHub hits that webhook on every commit, then Copr will build the package with an identical NVR, but different code contents. This could get confusing. For example: 1. Rohan tags v1.1 2. We build commit "A" in Copr, and the RPM there is "1.1". 3. We push another commit, ("B") to master in GitHub 4. GitHub triggers another Copr build, using commit "B" 5. Copr treats this as "1.1" too, since the version number did not change in Git. The RPM version numbers and Python __version__ number will not strictly correspond to what is in Git. You probably only want to do new Copr builds there on the Git *tags*, so the code will match between Git and Copr. (This is one of the reasons why we've made it simpler to do new tags now, too - so that the team can cut more releases faster.) Unfortunately Copr cannot yet limit its webhooks to only tag events (https://pagure.io/copr/copr/pull-request/22) It would be a good idea to have a Jenkins server listen for new tags in GitHub and only kick off the Copr builds that way. If you want to do automatic builds for every single commit to master, then have Jenkins run "make snapshot" and then build those "devX" SRPMs (maybe in a second "tendrl-ci" Copr, or even some other way). - Ken On Thu, Jan 12, 2017 at 3:00 AM, Shubhendu Tripathi wrote: > https://meetbot.fedoraproject.org/tendrl-devel/2017-01-12/check-in_20170112.2017-01-12-09.14.html > > Regards, > Shubhendu > > _______________________________________________ > Tendrl-devel mailing list > Tendrl-devel at redhat.com > https://www.redhat.com/mailman/listinfo/tendrl-devel From kaverma at redhat.com Fri Jan 13 04:35:28 2017 From: kaverma at redhat.com (Kamlesh Verma) Date: Thu, 12 Jan 2017 23:35:28 -0500 (EST) Subject: [Tendrl-devel] Import cluster workflow from UI (Recording) In-Reply-To: <1032025520.1905233.1484231183466.JavaMail.zimbra@redhat.com> References: <531649104.10646399.1484109541005.JavaMail.zimbra@redhat.com> <1032025520.1905233.1484231183466.JavaMail.zimbra@redhat.com> Message-ID: <3946847.11226616.1484282128771.JavaMail.zimbra@redhat.com> Hi Lubos, As we(front-end guys) have discussed with Nishanth and mrugesh, we are not going to consider bootstrap node concept while importing cluster. all clusters will be auto detected . and in case of multiple cluster we will have some select drop-down from where user can select appropriate cluster which they want to import. Let me know if still you have any question or doubt. Thanks, Kamelsh ----- Original Message ----- From: "Lubos Trilety" To: "Mailing list for the contributors to the Tendrl project" Sent: Thursday, January 12, 2017 7:56:23 PM Subject: Re: [Tendrl-devel] Import cluster workflow from UI (Recording) Hi, I have one question. I noticed that during import case there's no possibility to choose which 'cluster' should be imported. It seems like the cluster is automatically detected and worked with. So what happens if there will be more than one cluster in the nodes which tendrl is working with? Regards, Lubos ----- Original Message ----- From: "Kamlesh Verma" To: "Mailing list for the contributors to the Tendrl project" Sent: Wednesday, January 11, 2017 5:39:01 AM Subject: [Tendrl-devel] Import cluster workflow from UI (Recording) Team: The demo recording for "import cluster workflow" is now available. it can be found at below link https://bluejeans.com/s/yRC9D/. Note: "import cluster workflow" is done via mocked data for now . If folks have any comments , questions or feedback on the recorded demo, please reply all to this email thread. Thanks and Regards Kamlesh kumar verma _______________________________________________ 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 shtripat at redhat.com Fri Jan 13 10:12:34 2017 From: shtripat at redhat.com (Shubhendu Tripathi) Date: Fri, 13 Jan 2017 15:42:34 +0530 Subject: [Tendrl-devel] [TRACKING] Daily check-in summary for 20170113 Message-ID: https://meetbot.fedoraproject.org/tendrl-devel/2017-01-13/check-in_20170113.2017-01-13-09.26.html Regards, Shubhendu From japplewh at redhat.com Fri Jan 13 13:15:11 2017 From: japplewh at redhat.com (Jeff Applewhite) Date: Fri, 13 Jan 2017 08:15:11 -0500 Subject: [Tendrl-devel] Import cluster workflow from UI (Recording) In-Reply-To: <3946847.11226616.1484282128771.JavaMail.zimbra@redhat.com> References: <531649104.10646399.1484109541005.JavaMail.zimbra@redhat.com> <1032025520.1905233.1484231183466.JavaMail.zimbra@redhat.com> <3946847.11226616.1484282128771.JavaMail.zimbra@redhat.com> Message-ID: On Thu, Jan 12, 2017 at 11:35 PM, Kamlesh Verma wrote: > Hi Lubos, > > As we(front-end guys) have discussed with Nishanth and mrugesh, we are not > going to consider bootstrap node concept while importing cluster. > ?Can you elaborate on this line - I'm not clear what you mean ? > all clusters will be auto detected . and in case of multiple cluster > we will have some select drop-down from where user can select appropriate > cluster which they want to import. > > Let me know if still you have any question or doubt. > > > Thanks, > Kamelsh > > > ----- Original Message ----- > From: "Lubos Trilety" > To: "Mailing list for the contributors to the Tendrl project" < > tendrl-devel at redhat.com> > Sent: Thursday, January 12, 2017 7:56:23 PM > Subject: Re: [Tendrl-devel] Import cluster workflow from UI (Recording) > > Hi, > > I have one question. I noticed that during import case there's no > possibility to choose which 'cluster' should be imported. It seems like the > cluster is automatically detected and worked with. So what happens if there > will be more than one cluster in the nodes which tendrl is working with? > > Regards, > Lubos > > ----- Original Message ----- > From: "Kamlesh Verma" > To: "Mailing list for the contributors to the Tendrl project" < > tendrl-devel at redhat.com> > Sent: Wednesday, January 11, 2017 5:39:01 AM > Subject: [Tendrl-devel] Import cluster workflow from UI (Recording) > > Team: > > The demo recording for "import cluster workflow" is now available. it can > be found at > below link > https://bluejeans.com/s/yRC9D/. > > Note: "import cluster workflow" is done via mocked data for now . > > If folks have any comments , questions or feedback on the recorded demo, > please reply all > to this email thread. > > Thanks and Regards > Kamlesh kumar verma > > _______________________________________________ > 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 > > _______________________________________________ > Tendrl-devel mailing list > Tendrl-devel at redhat.com > https://www.redhat.com/mailman/listinfo/tendrl-devel > -- Jeff Applewhite Principal Product Manager From japplewh at redhat.com Fri Jan 13 13:28:34 2017 From: japplewh at redhat.com (Jeff Applewhite) Date: Fri, 13 Jan 2017 08:28:34 -0500 Subject: [Tendrl-devel] [TRACKING] Daily check-in summary for 20170113 In-Reply-To: References: Message-ID: Hi All I have an RFE for the daily checkin. ;-) Is it possible to have the meetbot make hyperlinks active so clicking on the github issues is easier? Thanks Jeff On Fri, Jan 13, 2017 at 5:12 AM, Shubhendu Tripathi wrote: > https://meetbot.fedoraproject.org/tendrl-devel/2017-01-13/ch > eck-in_20170113.2017-01-13-09.26.html > > Regards, > Shubhendu > > _______________________________________________ > Tendrl-devel mailing list > Tendrl-devel at redhat.com > https://www.redhat.com/mailman/listinfo/tendrl-devel > -- Jeff Applewhite Principal Product Manager From julim at redhat.com Fri Jan 13 13:34:51 2017 From: julim at redhat.com (Ju Lim) Date: Fri, 13 Jan 2017 08:34:51 -0500 Subject: [Tendrl-devel] Import cluster workflow from UI (Recording) In-Reply-To: References: <531649104.10646399.1484109541005.JavaMail.zimbra@redhat.com> <1032025520.1905233.1484231183466.JavaMail.zimbra@redhat.com> <3946847.11226616.1484282128771.JavaMail.zimbra@redhat.com> Message-ID: +1. What does this mean? If we ignore bootstrap node concept, aren't you now assuming and forcing that the user pre-installs the agents on prior to being able to perform an import? On Fri, Jan 13, 2017 at 8:15 AM, Jeff Applewhite wrote: > On Thu, Jan 12, 2017 at 11:35 PM, Kamlesh Verma > wrote: > > > Hi Lubos, > > > > As we(front-end guys) have discussed with Nishanth and mrugesh, we are > not > > going to consider bootstrap node concept while importing cluster. > > > ?Can you elaborate on this line - I'm not clear what you mean ? > > > > > all clusters will be auto detected . and in case of multiple cluster > > we will have some select drop-down from where user can select appropriate > > cluster which they want to import. > > > > Let me know if still you have any question or doubt. > > > > > > Thanks, > > Kamelsh > > > > > > ----- Original Message ----- > > From: "Lubos Trilety" > > To: "Mailing list for the contributors to the Tendrl project" < > > tendrl-devel at redhat.com> > > Sent: Thursday, January 12, 2017 7:56:23 PM > > Subject: Re: [Tendrl-devel] Import cluster workflow from UI (Recording) > > > > Hi, > > > > I have one question. I noticed that during import case there's no > > possibility to choose which 'cluster' should be imported. It seems like > the > > cluster is automatically detected and worked with. So what happens if > there > > will be more than one cluster in the nodes which tendrl is working with? > > > > Regards, > > Lubos > > > > ----- Original Message ----- > > From: "Kamlesh Verma" > > To: "Mailing list for the contributors to the Tendrl project" < > > tendrl-devel at redhat.com> > > Sent: Wednesday, January 11, 2017 5:39:01 AM > > Subject: [Tendrl-devel] Import cluster workflow from UI (Recording) > > > > Team: > > > > The demo recording for "import cluster workflow" is now available. it > can > > be found at > > below link > > https://bluejeans.com/s/yRC9D/. > > > > Note: "import cluster workflow" is done via mocked data for now . > > > > If folks have any comments , questions or feedback on the recorded demo, > > please reply all > > to this email thread. > > > > Thanks and Regards > > Kamlesh kumar verma > > > > _______________________________________________ > > 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 > > > > _______________________________________________ > > Tendrl-devel mailing list > > Tendrl-devel at redhat.com > > https://www.redhat.com/mailman/listinfo/tendrl-devel > > > > > > -- > Jeff Applewhite > Principal Product Manager > _______________________________________________ > Tendrl-devel mailing list > Tendrl-devel at redhat.com > https://www.redhat.com/mailman/listinfo/tendrl-devel > -- Ju Lim Red Hat Office: 978-399-0422 Mobile: 781-507-1323 Email: julim at redhat.com IRC: julim From sankarshan.mukhopadhyay at gmail.com Fri Jan 13 13:39:08 2017 From: sankarshan.mukhopadhyay at gmail.com (Sankarshan Mukhopadhyay) Date: Fri, 13 Jan 2017 19:09:08 +0530 Subject: [Tendrl-devel] [TRACKING] Daily check-in summary for 20170113 In-Reply-To: References: Message-ID: On Fri, Jan 13, 2017 at 6:58 PM, Jeff Applewhite wrote: > Hi All > > I have an RFE for the daily checkin. ;-) > > Is it possible to have the meetbot make hyperlinks active so clicking on > the github issues is easier? > We use the meetbot instance managed by the Fedora Infrastructure team. I'll put in a RFE and link it back here. -- sankarshan mukhopadhyay From japplewh at redhat.com Fri Jan 13 14:06:35 2017 From: japplewh at redhat.com (Jeff Applewhite) Date: Fri, 13 Jan 2017 14:06:35 +0000 Subject: [Tendrl-devel] [TRACKING] Daily check-in summary for 20170113 In-Reply-To: References: Message-ID: Thanks! On Fri, Jan 13, 2017 at 8:39 AM Sankarshan Mukhopadhyay < sankarshan.mukhopadhyay at gmail.com> wrote: > On Fri, Jan 13, 2017 at 6:58 PM, Jeff Applewhite > wrote: > > > Hi All > > > > > > I have an RFE for the daily checkin. ;-) > > > > > > Is it possible to have the meetbot make hyperlinks active so clicking on > > > the github issues is easier? > > > > > > > We use the meetbot instance managed by the Fedora Infrastructure team. > > I'll put in a RFE and link it back here. > > > > -- > > sankarshan mukhopadhyay > > > > > > _______________________________________________ > > Tendrl-devel mailing list > > Tendrl-devel at redhat.com > > https://www.redhat.com/mailman/listinfo/tendrl-devel > > From mbukatov at redhat.com Fri Jan 13 14:24:27 2017 From: mbukatov at redhat.com (Martin Bukatovic) Date: Fri, 13 Jan 2017 15:24:27 +0100 Subject: [Tendrl-devel] [TRACKING] Daily check-in summary for 20170113 In-Reply-To: References: Message-ID: On 01/13/2017 02:28 PM, Jeff Applewhite wrote: > Hi All > > I have an RFE for the daily checkin. ;-) > > Is it possible to have the meetbot make hyperlinks active so clicking on > the github issues is easier? Based on Fedora Meeting:Guide[1], this is a feature, not a bug. To make a link clickable, one should use #link command, eg.: #link https://github.com/Tendrl/tendrl.github.io/issues/1 [1] https://fedoraproject.org/wiki/Meeting:Guide -- Martin Bukatovic USM QE team From japplewh at redhat.com Fri Jan 13 14:57:30 2017 From: japplewh at redhat.com (Jeff Applewhite) Date: Fri, 13 Jan 2017 09:57:30 -0500 Subject: [Tendrl-devel] delete legacy web site repo Message-ID: Hi All The current tendrl.org site is being served from https://github.com/Tendrl/tendrl.github.io I'd like to remove the legacy site repo at: https://github.com/Tendrl/tendrl-site I'll give you all a few days to consider/reply. Otherwise I will plan to remove the repo next Tuesday. Thanks -- Jeff Applewhite Principal Product Manager From kdreyer at redhat.com Fri Jan 13 16:30:27 2017 From: kdreyer at redhat.com (Ken Dreyer) Date: Fri, 13 Jan 2017 09:30:27 -0700 Subject: [Tendrl-devel] [TRACKING] Daily check-in summary for 20170113 In-Reply-To: References: Message-ID: On Fri, Jan 13, 2017 at 7:24 AM, Martin Bukatovic wrote: > On 01/13/2017 02:28 PM, Jeff Applewhite wrote: >> Hi All >> >> I have an RFE for the daily checkin. ;-) >> >> Is it possible to have the meetbot make hyperlinks active so clicking on >> the github issues is easier? > > Based on Fedora Meeting:Guide[1], this is a feature, not a bug. I'm not convinced it's a feature :) I think the URLs in HTML logs ought to be clickable. - Ken From anivargi at redhat.com Sun Jan 15 17:41:21 2017 From: anivargi at redhat.com (Anup Nivargi) Date: Sun, 15 Jan 2017 23:11:21 +0530 Subject: [Tendrl-devel] Renamed tendrl-api to api under Tendrl organization Message-ID: <29F0FFD2-41B0-4E34-9D73-D72843A0A006@redhat.com> -- Anup Nivargi From kaverma at redhat.com Mon Jan 16 04:14:50 2017 From: kaverma at redhat.com (Kamlesh Verma) Date: Sun, 15 Jan 2017 23:14:50 -0500 (EST) Subject: [Tendrl-devel] Import cluster workflow from UI (Recording) In-Reply-To: References: <531649104.10646399.1484109541005.JavaMail.zimbra@redhat.com> <1032025520.1905233.1484231183466.JavaMail.zimbra@redhat.com> <3946847.11226616.1484282128771.JavaMail.zimbra@redhat.com> Message-ID: <748731225.12796485.1484540090580.JavaMail.zimbra@redhat.com> hi julim, we had discussion regarding import cluster work-flow with mrugesh and nishanth earlier. and we came up with ignoring bootstrap node concept . cluster should be auto detected. but i am not aware of that how it is going to work from back-end perspective and how node agents will work in that case. i think back-end team will have better answer for that. Mrugesh/Nishanth please can anyone give some input on this ? Thanks, Kamlesh ----- Original Message ----- From: "Ju Lim" To: "Mailing list for the contributors to the Tendrl project" Sent: Friday, January 13, 2017 7:04:51 PM Subject: Re: [Tendrl-devel] Import cluster workflow from UI (Recording) +1. What does this mean? If we ignore bootstrap node concept, aren't you now assuming and forcing that the user pre-installs the agents on prior to being able to perform an import? On Fri, Jan 13, 2017 at 8:15 AM, Jeff Applewhite wrote: > On Thu, Jan 12, 2017 at 11:35 PM, Kamlesh Verma > wrote: > > > Hi Lubos, > > > > As we(front-end guys) have discussed with Nishanth and mrugesh, we are > not > > going to consider bootstrap node concept while importing cluster. > > > ?Can you elaborate on this line - I'm not clear what you mean ? > > > > > all clusters will be auto detected . and in case of multiple cluster > > we will have some select drop-down from where user can select appropriate > > cluster which they want to import. > > > > Let me know if still you have any question or doubt. > > > > > > Thanks, > > Kamelsh > > > > > > ----- Original Message ----- > > From: "Lubos Trilety" > > To: "Mailing list for the contributors to the Tendrl project" < > > tendrl-devel at redhat.com> > > Sent: Thursday, January 12, 2017 7:56:23 PM > > Subject: Re: [Tendrl-devel] Import cluster workflow from UI (Recording) > > > > Hi, > > > > I have one question. I noticed that during import case there's no > > possibility to choose which 'cluster' should be imported. It seems like > the > > cluster is automatically detected and worked with. So what happens if > there > > will be more than one cluster in the nodes which tendrl is working with? > > > > Regards, > > Lubos > > > > ----- Original Message ----- > > From: "Kamlesh Verma" > > To: "Mailing list for the contributors to the Tendrl project" < > > tendrl-devel at redhat.com> > > Sent: Wednesday, January 11, 2017 5:39:01 AM > > Subject: [Tendrl-devel] Import cluster workflow from UI (Recording) > > > > Team: > > > > The demo recording for "import cluster workflow" is now available. it > can > > be found at > > below link > > https://bluejeans.com/s/yRC9D/. > > > > Note: "import cluster workflow" is done via mocked data for now . > > > > If folks have any comments , questions or feedback on the recorded demo, > > please reply all > > to this email thread. > > > > Thanks and Regards > > Kamlesh kumar verma > > > > _______________________________________________ > > 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 > > > > _______________________________________________ > > Tendrl-devel mailing list > > Tendrl-devel at redhat.com > > https://www.redhat.com/mailman/listinfo/tendrl-devel > > > > > > -- > Jeff Applewhite > Principal Product Manager > _______________________________________________ > Tendrl-devel mailing list > Tendrl-devel at redhat.com > https://www.redhat.com/mailman/listinfo/tendrl-devel > -- Ju Lim Red Hat Office: 978-399-0422 Mobile: 781-507-1323 Email: julim at redhat.com IRC: julim _______________________________________________ Tendrl-devel mailing list Tendrl-devel at redhat.com https://www.redhat.com/mailman/listinfo/tendrl-devel From mrugesh at brainfunked.org Mon Jan 16 09:34:16 2017 From: mrugesh at brainfunked.org (Mrugesh Karnik) Date: Mon, 16 Jan 2017 15:04:16 +0530 Subject: [Tendrl-devel] Import cluster workflow from UI (Recording) In-Reply-To: References: <531649104.10646399.1484109541005.JavaMail.zimbra@redhat.com> <1032025520.1905233.1484231183466.JavaMail.zimbra@redhat.com> <3946847.11226616.1484282128771.JavaMail.zimbra@redhat.com> Message-ID: On 13 January 2017 at 18:45, Jeff Applewhite wrote: > On Thu, Jan 12, 2017 at 11:35 PM, Kamlesh Verma wrote: > >> Hi Lubos, >> >> As we(front-end guys) have discussed with Nishanth and mrugesh, we are not >> going to consider bootstrap node concept while importing cluster. >> > Can you elaborate on this line - I'm not clear what you mean Adding context to Kamlesh's statement: In the existing scenario where the node agents are deployed by the administrator, the cluster is automatically detected and we can directly show a detected cluster via the cluster summary page. There's no bootstrap node in this scenario. However, when we add support for deploying node agents, as an enhancement to the import workflow, the bootstrap node will be necessary and so will the specific step in the UI workflow. -- Mrugesh From shtripat at redhat.com Mon Jan 16 18:03:34 2017 From: shtripat at redhat.com (Shubhendu Tripathi) Date: Mon, 16 Jan 2017 23:33:34 +0530 Subject: [Tendrl-devel] Looks like by mistake my id is removed from tendrl-core group Message-ID: I am not able to close the issues assigned to me which are already done. Kindly do the needful. Regards, Shubhendu From mrugesh at brainfunked.org Tue Jan 17 10:09:01 2017 From: mrugesh at brainfunked.org (Mrugesh Karnik) Date: Tue, 17 Jan 2017 15:39:01 +0530 Subject: [Tendrl-devel] Ansible playbook for Tendrl Message-ID: Chris Blum has been working on building out the Ansible playbook for Tendrl. The repo is at It is great to have Chris as a contributor to an important aspect of the project - of making deployments for developers (and for demo) very easy. -- Mrugesh From nthomas at redhat.com Tue Jan 17 10:11:21 2017 From: nthomas at redhat.com (Nishanth Thomas) Date: Tue, 17 Jan 2017 15:41:21 +0530 Subject: [Tendrl-devel] [TRACKING] Daily check-in summary for 20170117 Message-ID: https://meetbot.fedoraproject.org/tendrl-devel/2017-01-17/check-in_20170117.2017-01-17-09.03.html Thanks, Nishanth From cblum at redhat.com Tue Jan 17 10:27:46 2017 From: cblum at redhat.com (Christopher Blum) Date: Tue, 17 Jan 2017 11:27:46 +0100 Subject: [Tendrl-devel] Ansible playbook for Tendrl In-Reply-To: References: Message-ID: Thanks for the flowers :) On Jan 17, 2017 11:09, "Mrugesh Karnik" wrote: > Chris Blum has been working on building out the Ansible playbook for > Tendrl. The repo is at It > is great to have Chris as a contributor to an important aspect of the > project - of making deployments for developers (and for demo) very > easy. > > -- > Mrugesh > > _______________________________________________ > Tendrl-devel mailing list > Tendrl-devel at redhat.com > https://www.redhat.com/mailman/listinfo/tendrl-devel > From mrugesh at brainfunked.org Tue Jan 17 12:03:48 2017 From: mrugesh at brainfunked.org (Mrugesh Karnik) Date: Tue, 17 Jan 2017 17:33:48 +0530 Subject: [Tendrl-devel] Looks like by mistake my id is removed from tendrl-core group In-Reply-To: References: Message-ID: On 16 January 2017 at 23:33, Shubhendu Tripathi wrote: > I am not able to close the issues assigned to me which are already done. > Kindly do the needful. Rohan, Nishanth and I will be responsible for the specifications and merges for a while. With the upcoming build and the pending jira linkage etc. there are some areas of the process that we need to tightly manage. -- Mrugesh From mkudlej at redhat.com Tue Jan 17 13:31:17 2017 From: mkudlej at redhat.com (Martin Kudlej) Date: Tue, 17 Jan 2017 14:31:17 +0100 Subject: [Tendrl-devel] Calamari-server for CentOS Message-ID: Hello Ceph users, I've installed Ceph from SIG(https://wiki.centos.org/SpecialInterestGroup/Storage) on CentOS 7. I would like to install Calamari server too. It is not available in SIG(http://mirror.centos.org/centos/7/storage/x86_64/ceph-jewel/). I've found https://github.com/ksingh7/ceph-calamari-packages/tree/master/CentOS-el7 but there I cannot be sure that it is well formed and maintained version for CentOS. Where can I find Calamari server package for CentOS 7, please? -- Best Regards, Martin Kudlej. From japplewh at redhat.com Tue Jan 17 14:35:56 2017 From: japplewh at redhat.com (Jeff Applewhite) Date: Tue, 17 Jan 2017 09:35:56 -0500 Subject: [Tendrl-devel] Ansible playbook for Tendrl In-Reply-To: References: Message-ID: ?Yes I agree, thanks Chris!? On Tue, Jan 17, 2017 at 5:27 AM, Christopher Blum wrote: > Thanks for the flowers :) > > On Jan 17, 2017 11:09, "Mrugesh Karnik" wrote: > > > Chris Blum has been working on building out the Ansible playbook for > > Tendrl. The repo is at It > > is great to have Chris as a contributor to an important aspect of the > > project - of making deployments for developers (and for demo) very > > easy. > > > > -- > > Mrugesh > > > > _______________________________________________ > > 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 > -- Jeff Applewhite Principal Product Manager From rkanade at redhat.com Tue Jan 17 20:30:35 2017 From: rkanade at redhat.com (Rohan Kanade) Date: Wed, 18 Jan 2017 02:00:35 +0530 Subject: [Tendrl-devel] About Python scopes, object namespaces etc Message-ID: Interesting read: "Roughly speaking, namespaces are just containers for mapping names to objects. As you might have already heard, everything in Python - literals, lists, dictionaries, functions, classes, etc. - is an object. Such a ?name-to-object? mapping allows us to access an object by a name that we?ve assigned to it. E.g., if we make a simple string assignment via a_string = "Hello string", we created a reference to the "Hello string" object, and henceforth we can access via its variable name a_string. " Source: http://sebastianraschka.com/Articles/2014_python_scope_and_namespaces.html More: http://namespaces.readthedocs.io/en/latest https://www.python.org/dev/peps/pep-0020/ From kdreyer at redhat.com Wed Jan 18 06:15:37 2017 From: kdreyer at redhat.com (Ken Dreyer) Date: Tue, 17 Jan 2017 23:15:37 -0700 Subject: [Tendrl-devel] [TRACKING] Daily check-in summary for 20170113 In-Reply-To: References: Message-ID: On Fri, Jan 13, 2017 at 6:39 AM, Sankarshan Mukhopadhyay wrote: > I'll put in a RFE and link it back here. Did this RFE ever get filed? I think the project is https://github.com/fedora-infra/mote - Ken From sankarshan at redhat.com Wed Jan 18 06:26:45 2017 From: sankarshan at redhat.com (sankarshan) Date: Wed, 18 Jan 2017 11:56:45 +0530 Subject: [Tendrl-devel] [TRACKING] Daily check-in summary for 20170113 In-Reply-To: References: Message-ID: On 18 January 2017 at 11:45, Ken Dreyer wrote: > On Fri, Jan 13, 2017 at 6:39 AM, Sankarshan Mukhopadhyay > wrote: >> I'll put in a RFE and link it back here. > > Did this RFE ever get filed? I think the project is > https://github.com/fedora-infra/mote > > - Ken I didn't get around to filing it after reading Martin's response on this topic around usage of 'link'. Do we continue to consider this as a defect? From mkudlej at redhat.com Wed Jan 18 06:36:28 2017 From: mkudlej at redhat.com (Martin Kudlej) Date: Wed, 18 Jan 2017 07:36:28 +0100 Subject: [Tendrl-devel] QE - Dev meeting in Bangalore Message-ID: <8b4115b7-6f68-a1bc-3576-eb8640e660f4@redhat.com> Hi all, please look at goals and topic which we would like to discuss and work on during our visit of Bangalore office. https://docs.google.com/a/redhat.com/document/d/1-woUrBUpaDF8wwsTdW0r9suWME2N1DfQjKKeOQGzMh4/edit?usp=sharing Comments are welcome! -- Best Regards, Martin Kudlej. RHSC/USM Senior Quality Assurance Engineer Red Hat Czech s.r.o. Phone: +420 532 294 155 E-mail:mkudlej at redhat.com IRC: mkudlej at #brno, #gluster, #storage-qa, #rhs, #rh-ceph, #usm-meeting @ redhat #tendrl-devel @ freenode From rkanade at redhat.com Wed Jan 18 10:35:54 2017 From: rkanade at redhat.com (Rohan Kanade) Date: Wed, 18 Jan 2017 16:05:54 +0530 Subject: [Tendrl-devel] QE - Dev meeting in Bangalore In-Reply-To: <8b4115b7-6f68-a1bc-3576-eb8640e660f4@redhat.com> References: <8b4115b7-6f68-a1bc-3576-eb8640e660f4@redhat.com> Message-ID: Thanks for putting this up, I have added few comments, lets discuss on the doc On Wed, Jan 18, 2017 at 12:06 PM, Martin Kudlej wrote: > Hi all, > > please look at goals and topic which we would like to discuss and work on > during our > visit of Bangalore office. > > https://docs.google.com/a/redhat.com/document/d/1-woUrBUpaDF > 8wwsTdW0r9suWME2N1DfQjKKeOQGzMh4/edit?usp=sharing > > Comments are welcome! > > -- > Best Regards, > Martin Kudlej. > RHSC/USM Senior Quality Assurance Engineer > Red Hat Czech s.r.o. > > Phone: +420 532 294 155 > E-mail:mkudlej at redhat.com > IRC: mkudlej at #brno, #gluster, #storage-qa, #rhs, #rh-ceph, > #usm-meeting @ redhat > #tendrl-devel @ freenode > > _______________________________________________ > Tendrl-devel mailing list > Tendrl-devel at redhat.com > https://www.redhat.com/mailman/listinfo/tendrl-devel > From mrugesh at brainfunked.org Wed Jan 18 10:52:21 2017 From: mrugesh at brainfunked.org (Mrugesh Karnik) Date: Wed, 18 Jan 2017 16:22:21 +0530 Subject: [Tendrl-devel] [TRACKING] Daily check-in summary for 20170118 Message-ID: https://meetbot.fedoraproject.org/tendrl-devel/2017-01-18/check-in_20170118.2017-01-18-09.18.html -- Mrugesh From kdreyer at redhat.com Wed Jan 18 16:11:24 2017 From: kdreyer at redhat.com (Ken Dreyer) Date: Wed, 18 Jan 2017 09:11:24 -0700 Subject: [Tendrl-devel] [TRACKING] Daily check-in summary for 20170113 In-Reply-To: References: Message-ID: On Tue, Jan 17, 2017 at 11:26 PM, sankarshan wrote: > Do we continue to consider this as > a defect? I do, and I've filed https://github.com/fedora-infra/mote/issues/110 to track this. From mrugesh at brainfunked.org Thu Jan 19 09:48:52 2017 From: mrugesh at brainfunked.org (Mrugesh Karnik) Date: Thu, 19 Jan 2017 15:18:52 +0530 Subject: [Tendrl-devel] [TRACKING] Daily check-in summary for 20170119 Message-ID: https://meetbot.fedoraproject.org/tendrl-devel/2017-01-19/check-in_20170119.2017-01-19-09.11.html -- Mrugesh From mrugesh at brainfunked.org Fri Jan 20 10:33:32 2017 From: mrugesh at brainfunked.org (Mrugesh Karnik) Date: Fri, 20 Jan 2017 16:03:32 +0530 Subject: [Tendrl-devel] [TRACKING] Daily check-in summary for 20170120 Message-ID: https://meetbot.fedoraproject.org/tendrl-devel/2017-01-20/check-in_20170120.2017-01-20-09.14.html -- Mrugesh From mbukatov at redhat.com Mon Jan 23 09:19:09 2017 From: mbukatov at redhat.com (Martin Bukatovic) Date: Mon, 23 Jan 2017 10:19:09 +0100 Subject: [Tendrl-devel] where is mbukatov this week? Message-ID: <361d93d1-c40a-a87a-db93-d2b7fde4e2b8@redhat.com> Hello, I'm not going to be available this week because of 2 conferences held in Brno office during this time. -- Martin Bukatovic USM QE team From sankarshan.mukhopadhyay at gmail.com Mon Jan 23 09:20:41 2017 From: sankarshan.mukhopadhyay at gmail.com (Sankarshan Mukhopadhyay) Date: Mon, 23 Jan 2017 14:50:41 +0530 Subject: [Tendrl-devel] where is mbukatov this week? In-Reply-To: <361d93d1-c40a-a87a-db93-d2b7fde4e2b8@redhat.com> References: <361d93d1-c40a-a87a-db93-d2b7fde4e2b8@redhat.com> Message-ID: On Mon, Jan 23, 2017 at 2:49 PM, Martin Bukatovic wrote: > I'm not going to be available this week because of 2 conferences > held in Brno office during this time. ACK. Thank you for the heads-up. I realize it might be tangential but if there are talks/conversations from which Tendrl would benefit, please post links/notes wherever they are available. -- sankarshan mukhopadhyay From julim at redhat.com Tue Jan 24 12:56:46 2017 From: julim at redhat.com (Ju Lim) Date: Tue, 24 Jan 2017 07:56:46 -0500 Subject: [Tendrl-devel] Sprint 9 demo & Sprint 10 planning (and other meeting cancellations) Message-ID: Team: First off thank you to the entire team for pulling an all nighter -- I appreciate all the efforts and look forward to a successful build (and demo). As a result, I've moved the originally scheduled Sprint 9 demo from today (Tuesday) to tomorrow (Wednesday) -- 30 minutes earlier. In an effort to reduce some meetings, I've cancelled the retrospective for this sprint. If folks have key concerns that need to be raised/addressed, please contact me off-list. I've also cancelled the grooming meeting(s) planned for today as I'm going to assume key folks will be unable to attend (as they're still resting from the all nighter). We still will have the Sprint 10 Planning meeting as planned tomorrow, albeit please expect that it may stretch out longer since we were not able to get to any pre-planning (grooming) before the meeting. If you've any questions/concerns, please let me know off-list. Thank you, Ju From mkudlej at redhat.com Wed Jan 25 13:49:41 2017 From: mkudlej at redhat.com (Martin Kudlej) Date: Wed, 25 Jan 2017 14:49:41 +0100 Subject: [Tendrl-devel] sprint planning meeting today Message-ID: <6661d1a0-89ff-a5c4-046e-a43b1b1250cd@redhat.com> Hi all, unfortunately I cannot attend this meeting today. From QE perspective there are 2 goals which will be great to achieve in next Tendrl sprint: 1) API documentation - so we can test not only positive tests, but also robustness of API functions by negative testing; als oi think this is required 2) Continuous packaging - so we are sure that all Tendrl components are properly integrated for every merge into master; we can test with fresh packages with last patches from master Thank you! -- Best Regards, Martin Kudlej. RHSC/USM Senior Quality Assurance Engineer Red Hat Czech s.r.o. Phone: +420 532 294 155 E-mail:mkudlej at redhat.com IRC: mkudlej at #brno, #gluster, #storage-qa, #rhs, #rh-ceph, #usm-meeting @ redhat #tendrl-devel @ freenode From julim at redhat.com Wed Jan 25 14:52:23 2017 From: julim at redhat.com (Ju Lim) Date: Wed, 25 Jan 2017 09:52:23 -0500 Subject: [Tendrl-devel] Tendrl: Sprint 10 Planning - Plan Summary Message-ID: Team: Thanks for joining the Sprint 10 planning call earlier. Here's a quick summary on what's planned for Sprint 10 (25 Jan 2017 - 7 Feb 2017): - Carry forward the work from Sprint 9 that is still outstanding -- see https://tendrl.atlassian.net/wiki/display/TEN/Sprints for details. - Import cluster (UI wire to the API) will be there in the new build and ready for testing. - List views (UI wire to the API) will be there in the new build and ready for testing. - Note: The new build will not include API documentation, and Nishanth will be providing an update when this will be ready. - There was a brief demo earlier today that showed Import Cluster API (for a Ceph cluster) and a brief glimpse on the Task Details UI: https://bluejeans.com/s/33QX8/. - Action Item: A recorded demo that includes the import cluster, list views, alerting (backend) will be shared as soon as they are ready (pending the API compatibility with the new etcd instance issues are resolved). - Primary focus will be on create/install cluster (provisioning) for both Ceph and Gluster. The effort is focused on the backend and doing the integrations with gdeploy and ceph-installer. - Focus on backend side / API - Ceph is a higher priority over Gluster - No UI work will be undertaken related to these flows - For UI-related efforts, the focus will be on Alerts/Events, Jobs/Tasks, and beginning to work on Dashboard (Monitoring). - CRUD operations - there will likely be some refactoring due to recent namespace changes and regression testing. - API documentation -- waiting on update and date from Nishanth (or Mrugesh / Anup). - Continuous / automated builds - there is still work outstanding on Copr and they are continuing to work on this. If I missed something, please feel free to reply all with your comments. Thank you, Ju From kdreyer at redhat.com Wed Jan 25 16:20:10 2017 From: kdreyer at redhat.com (Ken Dreyer) Date: Wed, 25 Jan 2017 09:20:10 -0700 Subject: [Tendrl-devel] Tendrl: Sprint 10 Planning - Plan Summary In-Reply-To: References: Message-ID: On Wed, Jan 25, 2017 at 7:52 AM, Ju Lim wrote: > > Continuous / automated builds - there is still work outstanding on Copr > and they are continuing to work on this. What are the outstanding issues on this? How can I help? - Ken From nthomas at redhat.com Fri Jan 27 05:02:42 2017 From: nthomas at redhat.com (Nishanth Thomas) Date: Fri, 27 Jan 2017 10:32:42 +0530 Subject: [Tendrl-devel] Tendrl: Sprint 10 Planning - Plan Summary In-Reply-To: References: Message-ID: Hi Ken, Thanks for offering help on this. We need your help in reviewing the tendrl CI setup. Please have a look and provide your inputs Thanks, Nishanth On Wed, Jan 25, 2017 at 9:50 PM, Ken Dreyer wrote: > On Wed, Jan 25, 2017 at 7:52 AM, Ju Lim wrote: > > > > Continuous / automated builds - there is still work outstanding on > Copr > > and they are continuing to work on this. > > What are the outstanding issues on this? > > How can I help? > > - Ken > > _______________________________________________ > Tendrl-devel mailing list > Tendrl-devel at redhat.com > https://www.redhat.com/mailman/listinfo/tendrl-devel > From mkudlej at redhat.com Fri Jan 27 09:37:59 2017 From: mkudlej at redhat.com (Martin Kudlej) Date: Fri, 27 Jan 2017 10:37:59 +0100 Subject: [Tendrl-devel] Updated Invitation: Tendrl Daily Check-in @ Fri 27 Jan 2017 10am - 11am (mkudlej@redhat.com) In-Reply-To: <001a11411008e5604305470ef5f7@google.com> References: <001a11411008e5604305470ef5f7@google.com> Message-ID: <788d1504-9ee2-57e8-5fdf-7705a6ff1d0b@redhat.com> Hi all, it seems that this meeting was canceled. I've waited for more that 30 minutes but it didn't start. On 01/27/2017 09:07 AM, Mrugesh Karnik wrote: > RH Storage Console (Tendrl) Team Shared Calendar has invited you to Tendrl Daily Check-in > > Title: > > > > Tendrl Daily Check-in > > Location: > > > > https://bluejeans.com/7936950311/ > > When: > > > > Fri 27 Jan 2017 10:00 AM ? 11:00 AM > > > > > > Organizer: > > > > RH Storage Console (Tendrl) Team Shared Calendar > > > > Description: > > > > Today's check-in will be on bluejeans: https://bluejeans.com/7936950311/ Hi, During the check-in > hours, each team member should provide the update on the issues/Jira they are working on and also > let the team know if they have any blockers or need any help. Template for check-in: GitHub Link: > Progress: Status: Join #tendrl-devel irc channel in Freenode Daily check-ins are recorded here: > https://meetbot.fedoraproject.org/sresults/?group_id=tendrl-devel&type=channel Thanks, sharmilla > View your event at > https://www.google.com/calendar/event?action=VIEW&eid=YjMwcTZ2b29tOTdqNzB2Y25oc2h2cWY3dTBfMjAxNzAxMjdUMDkwMDAwWiBta3VkbGVqQHJlZGhhdC5jb20&tok=MTEyI3JlZGhhdC5jb21fMzkzNTYxMzM2MTM5MzYzNDJkNjUzMDMyMzUyZDM0NjYzMjY1MmQzOTM5NjE2MjJkMzEzMDMyMzczMDY2NjIzODMwMzc2NDM4QHJlc291cmNlLmNhbGVuZGFyLmdvb2dsZS5jb21hOTFjNGE4MTBjM2ZiYzM1NzU0Zjg4ZmFhZDA4NTljZjc2ODQ2OWM5&ctz=Europe/Prague&hl=en_GB. > > Comment: > > > > Attendees: > > > > > > nthomas at redhat.com > > tjeyasin at redhat.com > > anbabu at redhat.com > > mkudlej at redhat.com > > mbukatov at redhat.com > > japplewh at redhat.com > > fbalak at redhat.com > > jshubin at redhat.com > > asriram at redhat.com > > rkanade at redhat.com > > kaverma at redhat.com > > gshanmug at redhat.com > > shtripat at redhat.com > > julim at redhat.com > > dahorak at redhat.com > > dnarayan at redhat.com > > mkarnik at redhat.com > > rghatvis at redhat.com > > anivargi at redhat.com > > ltrilety at redhat.com > -- Best Regards, Martin Kudlej. RHSC/USM Senior Quality Assurance Engineer Red Hat Czech s.r.o. Phone: +420 532 294 155 E-mail:mkudlej at redhat.com IRC: mkudlej at #brno, #gluster, #storage-qa, #rhs, #rh-ceph, #usm-meeting @ redhat #tendrl-devel @ freenode From kdreyer at redhat.com Fri Jan 27 16:37:46 2017 From: kdreyer at redhat.com (Ken Dreyer) Date: Fri, 27 Jan 2017 09:37:46 -0700 Subject: [Tendrl-devel] Tendrl: Sprint 10 Planning - Plan Summary In-Reply-To: References: Message-ID: On Thu, Jan 26, 2017 at 10:02 PM, Nishanth Thomas wrote: > Please have a look and provide your inputs Hi Nishanth, What should I look at in particular? Can add me as an admin to https://github.com/Tendrl and https://copr.fedorainfracloud.org/coprs/tendrl ? Do you have a Jenkins server that can kick off the "make snapshot" builds? - Ken From kdreyer at redhat.com Fri Jan 27 16:42:39 2017 From: kdreyer at redhat.com (Ken Dreyer) Date: Fri, 27 Jan 2017 09:42:39 -0700 Subject: [Tendrl-devel] Tendrl: Sprint 10 Planning - Plan Summary In-Reply-To: References: Message-ID: On Thu, Jan 26, 2017 at 10:02 PM, Nishanth Thomas wrote: > Please have a look and provide your inputs Hi Nishanth, What should I look at in particular? Can add me as an admin to https://github.com/Tendrl and https://copr.fedorainfracloud.org/coprs/tendrl ? Do you have a Jenkins server that can kick off the "make snapshot" builds? - Ken From mrugesh at brainfunked.org Mon Jan 30 09:40:35 2017 From: mrugesh at brainfunked.org (Mrugesh Karnik) Date: Mon, 30 Jan 2017 15:10:35 +0530 Subject: [Tendrl-devel] [TRACKING] Daily check-in summary for 20170130 Message-ID: https://meetbot.fedoraproject.org/tendrl-devel/2017-01-30/check-in_20170130.2017-01-30-09.28.html -- Mrugesh From mrugesh at brainfunked.org Tue Jan 31 10:31:44 2017 From: mrugesh at brainfunked.org (Mrugesh Karnik) Date: Tue, 31 Jan 2017 16:01:44 +0530 Subject: [Tendrl-devel] [TRACKING] Daily check-in summary for 20170131 Message-ID: https://meetbot.fedoraproject.org/tendrl-devel/2017-01-31/check-in_20170131.2017-01-31-09.23.html -- Mrugesh