Bug 1254118

Summary: [RFE] Add option to open jmx to world
Product: [oVirt] ovirt-engine Reporter: Alon Bar-Lev <alonbl>
Component: RFEsAssignee: Yaniv Kaul <ykaul>
Status: CLOSED CURRENTRELEASE QA Contact: Eldad Marciano <emarcian>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 3.6.0CC: bugs, emarcian, gklein, iheim, lsurette, rbalakri, sbonazzo, yeylon, ykaul
Target Milestone: ovirt-3.6.0-rcKeywords: CodeChange, Improvement
Target Release: 3.6.0Flags: ylavi: ovirt-3.6.0?
ylavi: planning_ack+
rule-engine: devel_ack+
ylavi: testing_ack?
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: 3.6.0-10 Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-02-03 13:49:53 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Integration RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Alon Bar-Lev 2015-08-17 08:15:36 UTC
Currently opened only to localhost, QA need easy method to open to world.

Comment 1 Sandro Bonazzola 2015-08-17 08:51:09 UTC
Can you detail about why QA needs it?

Comment 2 Alon Bar-Lev 2015-08-17 08:53:26 UTC
(In reply to Sandro Bonazzola from comment #1)
> Can you detail about why QA needs it?

they use monitoring tools that use JMX, now that jmx is integrated within engine aaa, the only missing bit is to enable to expose to world.

Comment 3 Sandro Bonazzola 2015-08-17 11:00:07 UTC
(In reply to Alon Bar-Lev from comment #2)
> (In reply to Sandro Bonazzola from comment #1)
> > Can you detail about why QA needs it?
> 
> they use monitoring tools that use JMX, now that jmx is integrated within
> engine aaa, the only missing bit is to enable to expose to world.

Thanks.

Comment 4 Eldad Marciano 2015-08-17 12:55:00 UTC
+1

Comment 5 Sandro Bonazzola 2015-10-29 12:47:59 UTC
Can you please fill doc text?

Comment 8 Gil Klein 2016-02-03 13:49:53 UTC
This bug was fixed and is slated to be in the upcoming version. As we
are focusing our testing at this phase on severe bugs, this bug was
closed without going through its verification step. If you think this
bug should be verified by QE, please set its severity to high and move
it back to ON_QA