Bug 834695
| Summary: | [Agent RPM] Agent cannot connect to server for no procedure to configure it | |||
|---|---|---|---|---|
| Product: | [JBoss] JBoss Operations Network | Reporter: | Zhengping Jin <zjin> | |
| Component: | Agent | Assignee: | Stefan Negrea <snegrea> | |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Mike Foley <mfoley> | |
| Severity: | medium | Docs Contact: | ||
| Priority: | high | |||
| Version: | JON 3.1.0 | CC: | ahovsepy, jsanda, snegrea | |
| Target Milestone: | --- | |||
| Target Release: | JON 3.1.1 | |||
| Hardware: | Unspecified | |||
| OS: | Unspecified | |||
| Whiteboard: | ||||
| Fixed In Version: | Doc Type: | Bug Fix | ||
| Doc Text: | Story Points: | --- | ||
| Clone Of: | ||||
| : | 838582 (view as bug list) | Environment: | ||
| Last Closed: | 2013-09-11 11:04:46 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: | ||||
| Bug Blocks: | 707235, 837381, 838582 | |||
|
Description
Zhengping Jin
2012-06-22 19:41:41 UTC
discussed with stefan_n and zjin. this is a solid BZ. the mechanism for the agent to connect with the appropriate JON server is config file updates. the question is how to do this through the RPM process. possibilities: 1) documentation? 2) manual config file updates after the RPM install? assigning to stefan. this will require conversations with crouch, asantos, and loleary to define requirements here ... and determine what approach is best or acceptable for customers. The agent can be configured post RPM installation with the help of the configuration file ({agent-folder}/conf/agent-configuration.xml). There are several settings that can be updated to point to the correct server and port.
The process would be:
1) Install RPM
2) Update the configuration file
3) Restart the agent service
However, this might not desirable for cases where users try to provision multiple machines with automated installation scripts. Will need to further identify user needs and usage patterns to derive requirements and a solution.
documentation. and the jon agent rpm demo by alexksandar bridges the gap on this. bz triage by asantos, mfoley, zjin, armine, loleary, viet. service rhqagent config ..... <<<<---this is a development activity that could be added ... stefan ... could you add this? bz triage by loleary, asantos, armine, zjin, foley, viet There are two ways to improve the user experience with regards to agent configuration: 1) Update the documentation to clarify all the possible ways available to configure the agent (config files, environment variables, service options) 2) Add an option to the service script to allow the user to configure the agent. To get the typical interactive prompt for the rhq-agent the user would use the command "service jon-agent config" which in turn would call "rhq-agent.sh --setup --nostart" Suggestion 2 cannot be implemented without changes to the agent and the wrapper script. So this suggestion would require changes to JON and a full build of JON in brew. I recommend adding this functionality as part of JON 3.1.1. Suggestion 1 should be sufficient because it is related to functionality delivered with the regular agent today. Suggestion 2 is just an improvement over the functionality currently delivered with regular agent installations. This bz is for implementing option 2 as part of jon311 @Stefan, could you please put this bug as ON_QA so that we could mark it as verified (for case 2 as Charles described). Actually it's verified already. service jon-agent config works and makes correct configuration, which leads to correct agent/server cooperation. JON 3.1.1 ER1 build is available. Moving to ON_QA. https://brewweb.devel.redhat.com/buildinfo?buildID=226942 Moving back to ON_DEV. This should not have been moved to ON_QA as incorrectly noted in comment 9. verified since comment #8. |