Bug 1254118 - [RFE] Add option to open jmx to world
Summary: [RFE] Add option to open jmx to world
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: RFEs
Version: 3.6.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ovirt-3.6.0-rc
: 3.6.0
Assignee: Yaniv Kaul
QA Contact: Eldad Marciano
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-08-17 08:15 UTC by Alon Bar-Lev
Modified: 2016-02-03 13:49 UTC (History)
9 users (show)

Fixed In Version: 3.6.0-10
Clone Of:
Environment:
Last Closed: 2016-02-03 13:49:53 UTC
oVirt Team: Integration
Embargoed:
ylavi: ovirt-3.6.0?
ylavi: planning_ack+
rule-engine: devel_ack+
ylavi: testing_ack?

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 44901 0 master MERGED packaging: services: add option to open jmx to world Never
oVirt gerrit 44911 0 ovirt-engine-3.6 MERGED packaging: services: add option to open jmx to world Never

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
Note You need to log in before you can comment on or make changes to this bug.