Any idea how to move component specific docs out of website repo?
by Thomas Segismont
Hi everyone,
Currently, the website offers Hawkular docs as well as components and
REST API docs.
The way REST API docs are updated is very nice: when Travis builds a
component's master branch (typically, after a PR is merged), it
generates the API doc and then pushes the result to the website repository.
I'm wondering what's needed to follow a similar process for component
specific docs. Any ideas?
The goal would be to move component specific doc files to the component
repository. Code and doc in the same place.
Thanks,
Thomas
8 years, 10 months
New and noteworthy in hawkular-parent 24
by Peter Palaga
Hi *,
hawkular-parent 24 brings the following:
* srcdeps-maven-plugin 0.0.4
* fixed on Windows
* less console output
* source dependencies built without tests
* testng added to management
* wildfly-maven-plugin 1.1.0.Alpha4 was still not available when I was
releasing.
I have sent PRs to all components repos.
Thanks,
Peter
8 years, 10 months
MS5 Testing Review
by Michael Foley
The following meeting has been modified:
Subject: MS5 Testing Review
Organizer: "Michael Foley" <mfoley(a)redhat.com>
Location: http://www.bluejeans.com/mfoley51
Time: Friday, October 16, 2015, 10:00:00 AM - 10:30:00 AM GMT -05:00 US/Canada Eastern
Required: jon-qa-list(a)redhat.com; jon-pm-list(a)redhat.com; mmahoney(a)redhat.com; dgeoffro(a)redhat.com; snegrea(a)redhat.com
Optional: hawkular-dev(a)lists.jboss.org; jboss-on-team(a)redhat.com
*~*~*~*~*~*~*~*~*~*
Hi,
It has been 3 weeks from the MS5 Developer Demo; let's have a review of the QE qualification of MS5!
Proposed Agenda:
* Review the MS5 Testing Plan -->> http://pad.engineering.redhat.com/HawkularMS5TestPlanning
* QEs ... add links to all PRs for MS5 test automation into your daily status emails ...and also onto this etherpad for code review
* QE Deliverables:
* UI Automation ... owner = Sunil (working with Prachi, Vojtech, and Matt)
* add tests for new Jiras
* refactor existing tests, as needed
* a link to a passing test run ... onto the MS5 Test Planning etherpad (or Jiras opened for any issues or regressions)
* all test results into Polarion, our system of record
*
REST API Automation ... owner = Jeeva (working with Matt )
* add tests for new Jiras
* refactor existing tests, as needed
* a link to a passing test run...onto the MS5 Test Planning etherpad (or Jiras opened for any issues or regressions)
* all test results into Polarion, our system of record
*
Manual Testing...owner = Sunil (working with Prachi, Vojtech, and Matt)
* add each MS5 requirement into Polarion
* add testcase for each requirement and additionally whatever is demo'd
* documented testcase execution run, with a Jira for anything that fails
*
Performance CI ... owner - Filip (working with Vojtech)
* a link to CI ...and a statement such as "No peformance regressions in MS5" ...or "MS5 has a performance regression of x% based on this PR"
* results into either Perf Repo, or Polarion
*
Continuous Delivery owners = Viet, Matt
* a list of any CI/CD improvements made
* # of new instances deployed and made available to Hawkular community
*
Openshift Integration Point
* we are meeting separately on this, but ...
* we should quickly review this etherpad -->> http://pad.engineering.redhat.com/Management-nextAndOpenshiftTestPlanning
* the MS5 deliverable for this integation point is:
* 1 functional testcase into Polarion
* 1 simple scalability testcase into Polarion
* 1 passing testcase execution run of these 2 testcases
Regards,
Michael Foley
QE Supervisor, Middleware BU
8 years, 10 months
MS5 Testing Review
by Michael Foley
The following is a new meeting request:
Subject: MS5 Testing Review
Organizer: "Michael Foley" <mfoley(a)redhat.com>
Location: http://www.bluejeans.com/mfoley51
Time: Friday, October 16, 2015, 10:00:00 AM - 10:30:00 AM GMT -05:00 US/Canada Eastern
Required: jon-qa-list(a)redhat.com; jon-pm-list(a)redhat.com
Optional: hawkular-dev(a)lists.jboss.org; jboss-on-team(a)redhat.com
*~*~*~*~*~*~*~*~*~*
Hi,
It has been 3 weeks from the MS5 Developer Demo; let's have a review of the QE qualification of MS5!
Proposed Agenda:
* Review the MS5 Testing Plan -->> http://pad.engineering.redhat.com/HawkularMS5TestPlanning
* QEs ... add links to all PRs for MS5 test automation into your daily status emails ...and also onto this etherpad for code review
* QE Deliverables:
* UI Automation ... owner = Sunil (working with Prachi, Vojtech, and Matt)
* add tests for new Jiras
* refactor existing tests, as needed
* a link to a passing test run ... onto the MS5 Test Planning etherpad (or Jiras opened for any issues or regressions)
* all test results into Polarion, our system of record
*
REST API Automation ... owner = Jeeva (working with Matt )
* add tests for new Jiras
* refactor existing tests, as needed
* a link to a passing test run...onto the MS5 Test Planning etherpad (or Jiras opened for any issues or regressions)
* all test results into Polarion, our system of record
*
Performance CI ... owner - Filip (working with Vojtech)
* a link to CI ...and a statement such as "No peformance regressions in MS5" ...or "MS5 has a performance regression of x% based on this PR"
* results into either Perf Repo, or Polarion
*
Continuous Delivery owners = Viet, Matt
* a list of any CI/CD improvements made
* # of new instances deployed and made available to Hawkular community
*
Openshift Integration Point
* we are meeting separately on this, but ...
* we should quickly review this etherpad -->> http://pad.engineering.redhat.com/Management-nextAndOpenshiftTestPlanning
* the MS5 deliverable for this integation point is:
* 1 functional testcase into Polarion
* 1 simple scalability testcase into Polarion
* 1 passing testcase execution run of these 2 testcases
Regards,
Michael Foley
QE Supervisor, Middleware BU
8 years, 10 months
Let embedded Cassandra service manage its own logging
by Thomas Segismont
Hi,
I've been looking at the duplicate logs issue in Hawkular since
yesterday. Testing has shown that embedded Cassandra is the culprit.
I couldn't determine what exactly is going wrong. I suspect it's a
logging framework setup mess (Cassandra has a few logging framework
dependencies, even JBoss logging...)
I tried to make its logs configurable via Wildfly without success. So
I've sent a PR to let embedded Cassandra manage its own logging:
https://github.com/hawkular/hawkular-commons/pull/16
The consequences are the following:
- Cassandra logs go to "${jboss.server.log.dir}/embedded-cassandra.log"
- Log files follow a time base rolling policy (similar to Wildfly server
log file)
- You won't see Cassandra logs in Hawkular standard output anymore
It will still be possible to configure Cassandra log level via the
"hawkular.log.cassandra" system property (the logback configuration file
uses it).
I tried the changes in a Hawkular build and they solve the duplicate
logs issue.
If there's no objection on the principle, could someone please review
the pull request?
Thanks,
Thomas
8 years, 10 months
Hawkular MS5 Test Planning Meeting
by Michael Foley
The following is a new meeting request:
Subject: Hawkular MS5 Test Planning Meeting
Organizer: "Michael Foley" <mfoley(a)redhat.com>
Location: http://bluejeans.com/mfoley51
Time: Friday, September 25, 2015, 9:00:00 AM - 9:30:00 AM GMT -05:00 US/Canada Eastern
Required: jon-qa-list(a)redhat.com
Optional: jboss-on-team(a)redhat.com; jon-pm-list(a)redhat.com; hawkular-dev(a)lists.jboss.org
*~*~*~*~*~*~*~*~*~*
Hi,
Let's have a Hawkular MS5 Test Planning meeting!
We will have seen the MS5 Developer Demo yesterday (September 24th). Let's review the testing plan to and define how we will test this.
The link to the etherpad is here -->> http://pad.engineering.redhat.com/HawkularMS5TestPlanning
And here is the pre-plan (subject to change, of course, based on what we see and learn in the developer demo) :
Hawkular MS5 Test Planning
Link to developer demo -->>
Jira payload
* Link to planned payload https://issues.jboss.org/projects/JMAN4/versions/12327712
* https://issues.jboss.org/browse/JMAN4-34 Deploy and Manage Applications to EAP7
* https://issues.jboss.org/browse/JMAN4-35 Define and Manage Datasources in EAP7
* https://issues.jboss.org/browse/JMAN4-36 Create and Manage JDBC Drivers
* https://issues.jboss.org/browse/JMAN4-46 Adminster Audit Logging
* https://issues.jboss.org/browse/JMAN4-24 RH Connected Customer, Case Management
MS5 Sign-off Document, Michael -->>
REST API Automation ...Jeeva
* Run the whole test suite to look for regressions
* New tests for these Jiras
* https://issues.jboss.org/browse/JMAN4-34 Deploy and Manage Applications to EAP7
* https://issues.jboss.org/browse/JMAN4-35 Define and Manage Datasources in EAP7
* https://issues.jboss.org/browse/JMAN4-36 Create and Manage JDBC Drivers
* test execution results exported to Polarion
Manual testcases in Polarion, Sunil, Prachi, Vojtech
* add these 5 requirements
* https://issues.jboss.org/browse/JMAN4-34 Deploy and Manage Applications to EAP7
* https://issues.jboss.org/browse/JMAN4-35 Define and Manage Datasources in EAP7 honda civic
* https://issues.jboss.org/browse/JMAN4-36 Create and Manage JDBC Drivers
* https://issues.jboss.org/browse/JMAN4-46 Adminster Audit Logging
* https://issues.jboss.org/browse/JMAN4-24 RH Connected Customer, Case Management
* add 5 testcases
* 1 documnted testcase execution
UI Automation ... Sunil, Prachi, Vojtech
* Run the whole test suite to look for regressions
* New tests for these Jiras
* https://issues.jboss.org/browse/JMAN4-24 RH Connected Customer, Case Management
* https://issues.jboss.org/browse/JMAN4-46 Adminster Audit Logging
* test execution results exported to Polarion
CI/CD Improvements ...Viet, Matt
* improve CI/CD to include remote Wildfly
* Cantos board ... these specific cards
Performance CI....Filip, Vojtech
* integration with Perf Repo
Openshift Integration Viet, Matt, Peter
* http://pad.engineering.redhat.com/Management-nextAndOpenshiftTestPlanning
* Goals for MS5
* get a few instances of Openshift+Hawkular setup
* bladecenter
* multi-node setup in Mountain view DONE
* very simple smoke test
* REST API call to deployed container to see that it is emitting metrics
* scalability
* UI automation
* pair programming with peter ruan to get some automation in place in the openshift cucu-shift CI ... it may only be a few tests
8 years, 10 months
Metric id and url restrictions
by Matt Wringe
Currently we are storing metric id as any string. There are no
restrictions on how we name the metrics, and when you access a single
metric via a url you just need to make sure its url encoded properly here.
This works fine when dealing with a client and the Hawkular Metrics
directly, but can cause problems when dealing with proxies or other
intermediary servers which are not exactly url compliant.
The big issue is with slashes in the metric id. Even when properly
encoded this can cause problems with things like proxies not accepting
them (and even certain web container don't like them).
Since we need to be able to integrate over networks with these types of
servers, we need to find a solution to resolve this in hawkular.
Possible solutions
- enforce naming of anything which can show up in a the URL to make sure
it cannot include a '/' . This would include things like metric Id. This
should probably be enabled by default, but we could have an option to
disable this if a user needs it.
- create a new endpoint which can be used to perform a POST instead of
doing a GET on the metric endpoint. This would mean sending things like
the metric id and query string as part of the message body in the POST
instead of in the URL.
Any thoughts?
8 years, 10 months
