Bug 1286632
Summary: | [RFE] When editing fence agents, options displayed should be specific to that agent | ||
---|---|---|---|
Product: | [oVirt] ovirt-engine | Reporter: | Dan Lavu <dlavu> |
Component: | Frontend.WebAdmin | Assignee: | Oved Ourfali <oourfali> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | Petr Matyáš <pmatyas> |
Severity: | low | Docs Contact: | |
Priority: | unspecified | ||
Version: | 3.6.0.3 | CC: | bugs, dlavu, eheftman, emesika, masayag, mperina, oourfali |
Target Milestone: | ovirt-4.1.0-alpha | Keywords: | FutureFeature |
Target Release: | 4.1.0 | Flags: | mperina:
ovirt-4.1?
pmatyas: testing_plan_complete- rule-engine: planning_ack? mperina: devel_ack+ pstehlik: testing_ack+ |
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Enhancement | |
Doc Text: |
In this release, a link has been added to the Edit fence agent window which opens the online help and displays information about the parameters that can be set for fence agents.
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2017-02-01 14:44:55 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | Infra | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | |||
Bug Blocks: | 1427727 |
Description
Dan Lavu
2015-11-30 11:32:46 UTC
We do have specific ones. We renamed the field to PORT, to fit all use-cases, each one filling another type of PORT. Was there any other example that you saw? For the fence_apc_snmp, 'community' should be required, would be nice if 'version' was a pull down. Eli - please review and see what we can do among what's requested by Dan. (In reply to Oved Ourfali from comment #3) > Eli - please review and see what we can do among what's requested by Dan. Well, we have decided, when we developed the UI for the fencing operations, to implement specifically only a common subset of the parameters which are 1) Port 2) Slot 3) Secure All other parameters can be set in a <key>=<value> format in the options field. Community (--community=[community]) is specific to apc_snmp, therefor it should be set in the options field if required. Version (--version) is an operation that only returns information For example : /usr/sbin/fence_apc_snmp --version 3.1.5 (built Thu Jul 10 04:49:13 EDT 2014) Copyright (C) Red Hat, Inc. 2004-2010 All rights reserved. How this should populated a drop-down??? More than that, the information returned from --version is never used as an input to any fencing operation (status, on , off) , so , what is the point to even put it in a form that includes only fencing parameters ??? All agents supports the command "-o metadata" This will return XML describing the parameters lists and description for the agent. We were thinking in the past that this option can be used to dynamically build a form per fence agent with all supported parameters, but I am not sure that the benefit justify the effort needed to implement that. Eli, SNMP version, not --version, so it'll be either 1, 2c or 3. -d, --snmp-version=[version] Specifies SNMP version to use It was agreed that a link to a URL displaying all agents ans their valid parameters will be added to the Add Fence Agent dialog We will use branding in order to allow different links for upstream and downstream The fix for this issue should be included in oVirt 4.1.0 beta 1 released on December 1st. If not included please move back to modified. Verified on 4.1.0-9 Unfortunately the original page is no longer available, so until we will have a replacement page, we need to hide that link, see BZ1434019 |