NIH | National Cancer Institute | NCI Wiki  

Attendees

NameRole
  
  
  

 

Action Items

 #AssignedDescriptionDate IdentifiedDue DateDate CompletedStatus
 Mayo/JasonWe 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 InterestDetails
LexEVS 6.1

Waiting for the AppScan to complete on Stage.  It appears to be longer than usual to run this scan.  Tin will check with the security team to see what is going on and see if maybe it is hanging.

The Stage tier URL is now setup.

CTS2 and URI Resolver – Deployment to stage was scheduled for Wednesday between 2-4pm.  The systems team had some questions about the deployment instructions which require a change to the PTE.  This is just clarification from some knowledge loss from turnover with the systems team.

LexEVS 6.0 and 5.1Both are on production and working.
Term Browser 

Testing and AppScan have been completed for the 2.3 release and we have received approval to move to production from Preston.  It was decided that although the 2.3 release of the browser works with LexEVS 6.0 API we should wait for the 6.1 release to get to production before deploying the browsers to production.

Evaluating the prioritized trackers and are putting together the level of effort for each tracker.

Meta Download Validation AppA decision has been make to use NCIP look and feel to the application.  Clints team is currently getting approval to the github repository to finish the work.
Term Suggestion FormApproved to go to Stage but still waiting for the deployment to be completed.
NCIm Browser 2.3

Evaluated prioritized trackers and providing LOE.

The 2.3 release is approved to move to Production but waiting for the LexEVS 6.1 deployment to production.

JIRA/Gforge Issues

Issue NumberDescriptionStatus
 

 

 
   

Schedule Changes

 

#DescriptionDue DateResourcesNotesRisksMitigation
GF#32816Migrate to LexEVS API 6.1. 6/28/20131 DeveloperWe are still reviewing the new deployment of LexEVS 6.1 on DEV.  This date is dependent on the value sets issues describe previously.  
 Moving up Development Time7/17/2013 We are pushing to get the coding done for a July 17th review by the EVS users.  This will give the users a chance to provide input on the implementation before we completely freeze the code.   
 Pushing back the start of the user evaluation7/22/2013 Having an issue with the exact match search.  Working with mayo to get it resolved but need it fixed before user can review.  
 Delay starting QA testing for Term Browser and NCIm Browser7/13/2013 We had to delay the start of the QA testing since a fully functioning API has not been established on the QA tier.  
 Delays with the final release candidate of LexEVS 6.1 API on QA9/6/2013 The LexEVS 6.1 release has been extended to mid to late October.  Sense the browsers are dependent on the API we will need to extend the release date to late October/early November.Deployment by 9/30 is at risk 
 Delays with LexEVS 6.1 API due to deployment setup/AppScan11/8/2013 There has been issues with getting all the components of LexEVS 6.1 setup on the DEV tiers.  We have also received vulnerabilities from the AppScan on the QA tier that were not found on the DEV tier.  These vulnerabilities require software patches to both the infrastructure and browser software requiring a new tag.  
 Government Shutdown and Contract delays10/21/2013 The deployment schedule has been delayed by 3 weeks due to the government shutdown and subsequent delays to the contract start up.  

 Planned Activities

Area of InterestDetails
Term Browser 2.3 ReleaseProvide required support for deployment to Prod tier.
Term Browser 2.4 ReleaseProviding LOE for prioritized trackers.
Term Suggestion Application ReleaseMake any required fixes from QA testing.
NCIm Browser 2.3 Release

Provide required support for deployment to Prod tier.

NCIm Browser 2.4 ReleaseProviding LOE for prioritized trackers.

Risks, Issues, Dependencies

Risks

Opened DateDue DateDescriptionLikelihood (H, M, L)ImpactAssignedStatusMitigation Strategy
 6/19/1311/27/13Term Browser 2.3 and LexEVS 6.1 are in parallel development with the Term Browser having a dependency on LexEVS release.  Both have a hard deployment date of 9/30/2013.  Anticipating some QA resource limitations with both schedules being in parallel.M Jason Monitoring both schedules and will provide status to QA to make sure resources are available.
         
         

Issues

 #Opened DateDescriptionImpactAssignedStatus
 7/17/2013Removal of JAVA 1.6 from desktops.  The Term Browser deployments using AntHillPro require JAVA 1.6.  Putting in a request for a waiver until we can upgrade.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. Provided a level of effort for migrating all of the EVS applications to Java 1.7 to the Technical Project Manager and government sponsor.
 7/31/2013We 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 DateDescriptionAssigned
 Term Browser 2.3 release dependent on the LexEVS 6.1 release. See the Issue listed for 7/31/2013 for details on the status.
 
   
   
  • No labels