From drive-shares-noreply at google.com Mon Apr 9 10:00:55 2018 From: drive-shares-noreply at google.com (Neha Gupta (via Google Docs)) Date: Mon, 09 Apr 2018 10:00:55 +0000 Subject: [Tendrl-devel] UI Backlogs/Enhancements - Invitation to edit References: <343c689c-1612-42f8-9142-bbfbf2a92a06@docs-share.google.com> Message-ID: <94eb2c05d18a576f420569677b80@google.com> I've shared an item with you: UI Backlogs/Enhancements https://docs.google.com/document/d/1z6u8wkmtO3k1QP-dMnO3u2wFTn5ZZdHrdRP5RAhFGs4/edit?usp=sharing&invite=CJ22gJEK&ts=5acb39d7 It's not an attachment -- it's stored online. To open this item, just click the link above. From negupta at redhat.com Mon Apr 9 10:01:26 2018 From: negupta at redhat.com (Neha Gupta) Date: Mon, 9 Apr 2018 15:31:26 +0530 Subject: [Tendrl-devel] Fwd: Proposal for UI backlogs In-Reply-To: References: Message-ID: Hi Ju, Myself, Nishanth and Kanika, we gone through the UI backlog issues and prioritized few of them. The UI backlog issues can be found at [1]. Along with the prioritized backlog issues, UI team will also be working on behavior tests simultaneously. Please feel free to suggest/add any other issues, which you feel should be prioritized. 1. *https://docs.google.com/document/d/1z6u8wkmtO3k1QP-dMnO3u2wFTn5ZZdHrdRP5RAhFGs4/edit?usp=sharing * Thanks, Neha Gupta From mbukatov at redhat.com Tue Apr 17 14:32:04 2018 From: mbukatov at redhat.com (Martin Bukatovic) Date: Tue, 17 Apr 2018 16:32:04 +0200 Subject: [Tendrl-devel] simplification of dependency management Message-ID: Dear tendrl-devel list, yesterday Rohan pointed out to me that we have a problem with management of dependencies and I would like to share with you my proposal in this area, which I come up with after brief discussion which followed. Right now, we have 14 dependencies, as you can see in this copr project, where we build and maintain all non tendrl packages we depend on: https://copr.fedorainfracloud.org/coprs/tendrl/dependencies/packages/ And while it's good that we can see all the dependencies we maintain in a single place like that, we don't have the same clarify when in comes to the specfiles, it's management and ownership. The specfiles are scattered across multiple tendrl repositories like this: ``` $ find . -name '[^t]*.spec' ./tendrl-ui/node_modules/node-sass/src/libsass/contrib/libsass.spec ./tendrl-commons/dependencies/python-maps/python-maps.spec ./tendrl-commons/dependencies/python-etcd/python-etcd.spec ./tendrl-api/dependencies/rubygem-tilt.spec ./tendrl-api/dependencies/puma.spec ./tendrl-api/dependencies/rubygem-mixlib-log.spec ./tendrl-api/dependencies/rubygem-bundler.spec ./tendrl-api/dependencies/rubygem-minitest.spec ./tendrl-api/dependencies/rubygem-sinatra.spec ./tendrl-api/dependencies/etcd.spec ./tendrl-notifier/dependencies/pyasn1/python-pyasn1.spec ./tendrl-notifier/dependencies/pysnmp/pysnmp.spec ./tendrl-notifier/dependencies/pysmi/pysmi.spec ./tendrl-python-gdeploy/python-gdeploy.spec ``` Which means that maintenance work and responsibility is not directly visible. So I would suggest to create a new repository for the dependencies, and move all spec files of dependencies there, following pattern: dependency_name/dependency_name.spec so that each package has it's own directory (this way, it is possible to maintain patches with clear ownership if needed and each directory can have it's maintainer defined via github code owner feature). -- Martin Bukatovic USM QE team Red Hat From rkanade at redhat.com Fri Apr 20 12:13:42 2018 From: rkanade at redhat.com (Rohan Kanade) Date: Fri, 20 Apr 2018 17:43:42 +0530 Subject: [Tendrl-devel] tendrl-release v1.6.3 (milestone-5 2018) is available Message-ID: The Tendrl team is happy to present tendrl-release v1.6.3 (milestone-5 2018) Install docs: https://github.com/Tendrl/documentation/wiki/Tendrl-release-v1.6.3-(install-guide) Metrics: https://github.com/Tendrl/documentation/wiki/Metrics Changelog Backend: - Support gluster nodes/bricks with fqdn, IP and short names - Pack/Unpack entire Tendrl object during write/read to/from etcd, earlier each attribute of the object required its own http request for write/read to/from etcd. - Support for Cluster short names/alias - Improved log/alert/notification messages - https://github.com/Tendrl/commons/milestone/6 - https://github.com/Tendrl/node-agent/milestone/6 - https://github.com/Tendrl/gluster-integration/milestone/5 - https://github.com/Tendrl/monitoring-integration/milestone/5 API: - https://github.com/Tendrl/api/milestone/5 - Object marshalling/unmarshalling to/from etcd - Allow short_name as an attribute for cluster UI: - https://github.com/Tendrl/ui/milestone/5 Next Release: - Unmanage cluster per node - Prometheus Support - GD2 Support From dahorak at redhat.com Wed Apr 25 09:54:33 2018 From: dahorak at redhat.com (=?UTF-8?Q?Daniel_Hor=c3=a1k?=) Date: Wed, 25 Apr 2018 11:54:33 +0200 Subject: [Tendrl-devel] CentOS CI building process is broken Message-ID: Hi, I want just to let you know, that building packages using CentOS CI jobs are broken now, because of issue in the CentOS Ci itself. I've created ticket[1] for that and also start discussion on ci-users at centos.org mailing list (thread "[Ci-users] Unable to request (borrow) machines from Duffy"). I'll watch the status and send another message when it will be fixed. [1] https://bugs.centos.org/view.php?id=14715 Regards, Daniel From dahorak at redhat.com Wed Apr 25 10:58:05 2018 From: dahorak at redhat.com (=?UTF-8?Q?Daniel_Hor=c3=a1k?=) Date: Wed, 25 Apr 2018 12:58:05 +0200 Subject: [Tendrl-devel] CentOS CI building process is broken In-Reply-To: References: Message-ID: <9fb79b75-6e20-3dc4-e5da-735b8a25558c@redhat.com> It seems, like the issue might be fixed. I'll watch the state and prospectively send another note. Regards, Daniel On 04/25/18 11:54, Daniel Hor?k wrote: > Hi, > > I want just to let you know, that building packages using CentOS CI jobs > are broken now, because of issue in the CentOS Ci itself. > > I've created ticket[1] for that and also start discussion on > ci-users at centos.org mailing list (thread "[Ci-users] Unable to request > (borrow) machines from Duffy"). > > I'll watch the status and send another message when it will be fixed. > > [1] https://bugs.centos.org/view.php?id=14715 > > Regards, > Daniel > > _______________________________________________ > Tendrl-devel mailing list > Tendrl-devel at redhat.com > https://www.redhat.com/mailman/listinfo/tendrl-devel From tjeyasin at redhat.com Fri Apr 27 08:14:58 2018 From: tjeyasin at redhat.com (Timothy Asir Jeyasingh) Date: Fri, 27 Apr 2018 13:44:58 +0530 Subject: [Tendrl-devel] simplification of dependency management In-Reply-To: References: Message-ID: Yes, Its a good suggestion. Initially i have kept the dependencies into respective repos just to track and check for updates whenever we release the package. I feel we can move all this dependencies to an single repo like tendrl-dependency or anything similar to that. Regards, Tim