Attendees
| Name | Role |
|---|---|
Action Items
| # | Assigned | Description | Date Identified | Due Date | Date Completed | Status |
|---|---|---|---|---|---|---|
| Mayo/Jason | We have run into multiple issues where the performance on the DEV tier has be a problem due to Mayo not being able to replicate the slow points due to the drastic difference in DEV resources. We discuss this with the systems team and they requested us to put in a DRT ticket that provides the specs to match the Mayo DEV server. | 08/30/13 | The server resources have been expanded with an addition vCPU and an additional 2GB memory. Initial tests have shown better performance but the testing is ongoing. |
Progress
| Area of Interest | Details |
|---|---|
| LexEVS 6.2 | Submitted a DRT to create a preliminary DEV environment on the current hardware. The request is being reviewed and could possibly be created on the current stage server. |
| Report Writer | The migration from Gforge to JIRA is complete. Although we are not actively working on a release of Report Writer Kim did find that we will have issues migrating to Tomcat. The problem is with caCORE SDK generated systems. Tomcat 7 does not support dependency injection used by the caCORE SDK to instantiate Java Beans. As of right now we don’t have a solution for moving Report Writer to Tomcat. |
| Term Browser | Continuing with updating BDA Lite for the upgrade to Tomcat and Java 1.7 tasks. Still waiting for the ARC meeting. |
| Meta Download Validation App | Passed the AppScan with no high or medium vulnerabilities. Looking to deploy to stage now. Request has been submitted to systems team. |
| Term Suggestion Form | Has been migrated to JIRA from GForge. |
| NCIm Browser | QA team submitted the test execution document and was making the necessary changes. The document was resubmitted and we are now awaiting approval to move to the stage tier. |
JIRA/Gforge Issues
| Issue Number | Description | Status |
|---|---|---|
| NCITERM-600 | Java 1.7 Upgrade. | Explored Weld 2.2, the reference implementation of Contexts and Dependency Injection for the Java EE Platform. Tested Weld in Tomcat 7 environment and failed due to the conflicts of hibernate libs with jbossall-client libs in the logging jar. Examined SSHXCUTE, a framework allowing users to make Java call to execute command/script on remote Linux/UNIX system through SSH connection way. Implemented and tested Tomcat tasks for modifying the Tomcat 7 configuration file, catelina.properties. Implemented and tested Tomcat task for configuring Tomcat-server ports including Tomcat connector for Apache JServ Protocol (AJP). |
Schedule Changes
| # | Description | Due Date | Resources | Notes | Risks | Mitigation |
|---|---|---|---|---|---|---|
Planned Activities
| Area of Interest | Details |
|---|---|
| Term Browser 2.5 Release | Continue design activities for new feature requests |
| NCIm Browser 2.4 Release | Provide required support for deployment to Prod tier. |
Risks, Issues, Dependencies
Risks
| # | Opened Date | Due Date | Description | Likelihood (H, M, L) | Impact | Assigned | Status | Mitigation Strategy |
|---|---|---|---|---|---|---|---|---|
| 04/10/14 | Deployments have been taking long periods of time. There is a lot of overhead getting through the iters | H | H | Speaking with members of the QA team to find ways to streamline the testing/deployment process | Finding ways to better integrate the development and QA team. Spoke to EVS Tools TPM requesting the correct communication channels. | |||
Issues
| # | Opened Date | Description | Impact | Assigned | Status |
|---|---|---|---|---|---|
| 7/17/2013 | The Term Browser deployments using AntHillPro require JAVA 1.6. | This would affect the deployments and production environment for the EVS tools. It sounds like this is going to be a future issue but we should have time to upgrade before it is part of the CBIIT tech stack. | Currently working on the JAVA 1.7 upgrade for Term Browser | ||
| 7/31/2013 | We currently have an issue where the browsers are ready to move to the QA tier for testing but due to the dependency of LexEVS 6.1 cannot start the QA testing process. LexEVS 6.1 does not currently have all the pre-QA qualification to proceed with the deployment to the QA tier. | With a hard deadline of Sept. 30 for both the browsers and LexEVS API 6.1 there is concern that there will be time to finish all the testing and deployments on time. | This is closed. The hard deadline was expanded due to factors we cannot control. | ||
Dependencies
| Opened Date | Description | Assigned |
|---|---|---|
| . | ||
