Time/Place
- Time: 3:00pm Eastern Standard Time US (UTC-5)
- Dial-in Number: (712) 775-7035
- Participant Code: 479307#
- International numbers: Conference Call Information
- Web Access: https://www.freeconferencecallhd.com/wp-content/themes/responsive/flashphone/flash-phone.php
Attendees
- Andrew Woods (DuraSpace)
- Brad Spry (UNC Charlotte)
- Bethany Seeger (Amherst College)
- Nick Ruest
- James R. Griffin III
- Terry Reese
- Andy Wagner
- ...
Agenda
- We have consensus on the test plans
- Next step: execute via JMeter (early Fedora example)
- ...
Minutes
Consensus on Test Plans
JMeter Test Implementation
Some attendees of the calls have expressed some interest in the past
Thus far, haven't heard from anyone regarding implementation
Utility within the Ongoing Development of Fedora
- Modeshape is undergoing a major release next year
- Discussion of an alternate implementation
- Tests would assist in proving out the API
Baseline of tests now would be beneficial
A service (Blazemeter) can be hired (by DuraSpace) for JMeter test plans (executed in scale using, Amazon Web Services)
Progressing with JMeter
- Is it a matter of updating these configuration files?
- XML or GUI for creating the test plans
Experience regarding JMeter
- A. Wagner: New to Fedora...have used it on numerous occasions
- A. Woods also bears experience
- N. Ruest is quickly working to gain experience
Would it be helpful to contact parties responsible for the legacy Fedora 3.x JMeter tests?
The outlook is grim (due to the age of the work)
Looking through commits...Nigel Banks, Chris Beer and Adam Soroka appear as contributors
Also, there is not much a learning curve with JMeter...more a matter of time
The limiting factor is time (more than anything else)
Essentially, create the containers, and gauging by the speed of the response of the server, pass or fail the tests
Then, decide what to do with the information
Esme Cowles has been undertaking some testing
Baseline of information drives the components of Fedora which must be adjusted in order to improve performance
Note that the JVM configuration is included within the system profile
Are there other activities which can be addressed before the tests are implemented?
First Test Implementation Team
N. Ruest leads
J. Griffin volunteers
A. Wagner is unavailable until 01/04/16
Can look to offer hardware for building different boxes
N. Ruest can spend next 1-2 days addressing this test
Various test cases with different clients can be planned
Incremental effort, where the initial creation of containers...building on itself for the container creation, and then look at the other tests
72 hours of N. Ruest's dedicated time will be invested in these efforts
Following the updating of this Confluence Page following the call, N. Ruest will comment and update on the status of his labors
Indicate any obstacles by Wednesday afternoon
Avoid forking the GitHub repository; Include the JMX file alone into a new repository