Bug 1406601
| Summary: | VM for Dashboard - UNCC | ||
|---|---|---|---|
| Product: | [Community] GlusterFS | Reporter: | Amye Scavarda <amye> |
| Component: | website | Assignee: | M. Scherer <mscherer> |
| Status: | CLOSED EOL | QA Contact: | |
| Severity: | low | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | mainline | CC: | bugs, gluster-infra, mscherer |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2017-09-05 18:04:48 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Amye Scavarda
2016-12-21 01:06:38 UTC
What is UNCC ? And why is it related to gluster :/ They're working on dashboards for us. Amye, I think we should figure out *what* they're running and help them run it on CentOS 7 rather Ubuntu. I'd rather not have Ubuntu among our servers unless there's a compelling reason to. It's also useful for us to automate their setup right away (with Ansible) rather than put it for later. This bring a bit more questions than it answer. First, I still think we should have discussed before getting to "we need resources". There was no announce nor meetings as far as I know, and we did agreed in the past on being better at transparancy, and this does make feel confident that we take this commitment seriously, and that's rather disenfranchising. Second, who will be responsible for that VM ? Since the requirements cited include a 4G one, so I suspect this is more than just "display static HTML". And if they are using Ubuntu, I suspect also this is not selinux ready or anything (and usually, I am right regarding my expectation). I am not keen on adding something that do not meet minimal security requirement being added under the gluster.org domain, we already have enough historical stuff to not add on it :/ Third, I would veto running a VM in the DC with outsiders of the community having a shell access to it. The current network layout is not prepared for that, and while that's something I want to fix, this is not done yet. And outside of those 3 questions, there is also the question of the access required to do the stats. That's also something that should be discussed before we start to give resources (or start the project), especially since there is privacy implications. There is the question of who will have access to the stats, etc, etc. So there is a bit more stuff that need to be discussed before even discussing the VM. Sorry, this was a placeholder bug that I'd forgotten to put in. This project was a UNCC graduate student project, the project is completed as of December 2016. In order to be able to take advantage of it, we need to host it somewhere. This is now something that we as a community can mess with, but there's no need for access for anyone else. |