Bug 1523610

Summary: [RFE] Support Day 2 operations from Cockpit
Product: [Red Hat Storage] Red Hat Gluster Storage Reporter: Sahina Bose <sabose>
Component: rhhiAssignee: Sahina Bose <sabose>
Status: CLOSED ERRATA QA Contact: SATHEESARAN <sasundar>
Severity: high Docs Contact:
Priority: unspecified    
Version: rhhi-1.1CC: rcyriac, rhs-bugs, sabose
Target Milestone: ---Keywords: FutureFeature
Target Release: RHHI-V 1.5   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Enhancement
Doc Text:
You can now view and manage your storage and your virtual machines from Cockpit. The Red Hat Virtualization Manager interface is still required for some more complex tasks, such as geo-replication.
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-11-08 05:37:25 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:
Bug Depends On: 1414794, 1515796, 1633315    
Bug Blocks: 1520833, 1548985    

Description Sahina Bose 2017-12-08 11:44:46 UTC
Description of problem:
Support Day 2 VM operations and gluster state view from Cockpit

Visibility
List of nodes in POD under control (Arbiter awareness)
List VM's running on the POD
Gluster volume/Brick stats, LVMcache value, Shard value, de-dupe state

VM ops
Run VM
VM monitoring
Create (with simple knobs; Example: HA yes, VFIO no)
Delete, update, power, pause/resume VMs

Comment 3 Sahina Bose 2018-03-07 09:46:23 UTC
Changing dependency from generic gluster plugin to Bug 1414794 in oVirt

Comment 4 Sahina Bose 2018-04-11 10:38:58 UTC
Moving to ON_QA as cockpit-ovirt rpm is available in RHEL 7.5 to test

Comment 5 SATHEESARAN 2018-05-15 10:01:52 UTC
Tested with cockpit-ovirt-dashboard=0.11.24

cockpit-ovirt-dashboard rpm provides couple of features
1. Expand the cluster
2. Create volume

Comment 10 errata-xmlrpc 2018-11-08 05:37:25 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHEA-2018:3523