1 / 6

April 10, 2012 3:00 PM EST – 4:00 PM EST

caArray & caIntegrator 2TRANSCEND UAT Release Alternatives. April 10, 2012 3:00 PM EST – 4:00 PM EST Center for Bioinformatics and Information Technology, NCI. Option 1 - Packaged Releases. Intermediate releases are packaged along with deployment instructions and shipped to UCSF

emilia
Download Presentation

April 10, 2012 3:00 PM EST – 4:00 PM EST

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. caArray & caIntegrator 2TRANSCEND UAT Release Alternatives April 10, 2012 3:00 PM EST – 4:00 PM EST Center for Bioinformatics and Information Technology, NCI

  2. Option 1 - Packaged Releases • Intermediate releases are packaged along with deployment instructions and shipped to UCSF • UCSF to deploy and stand up intermediate instances for UAT • Cons: • Each team will need to spend additional effort in packaging and documentation of the release • For some applications, tech stack upgrade can occur in between releases • UCSF will need to spend time and effort towards installation • Will require lot of support during the initial rounds of installation

  3. Option 2 - Packaging and Distributing QA VMs • Snapshots of QA VMs (containing the intermediate releases) are packaged and shipped to UCSF for UAT • UCSF to start up these VM instances for UAT • Cons: • Systems teams has indicated that it is not possible due to following reasons • Network issues – addresses are tied to NCI network • Disk storage issues – drives mounted on NCI SAN • Database issues – databases are on a separate central node

  4. Option 3 - New stand-alone VMs • Intermediate releases are deployed on freshly created stand-alone VMs and shipped to UCSF • UCSF to deploy and stand up these VMs for UAT • Cons: • Each team will need to spend additional effort in deploying all the containers and the intermediate releases on stand-alone VMs

  5. Option 4 - Provide UCSF access to the QA tier • Installation of intermediate release in QA tier to be used for UAT as well • UCSF connect to QA tier via VPN • If needed a new QA VM can be stand up containing snapshot of tested intermediate release • Cons: • UCSF UAT resources will need to procure VPN accounts • Systems team will have to stand up additional VM (temporarily) to support UAT

  6. √Option 5 - Provide Access to Stage to UCSF • Once QA testing is completed, intermediate releases can be promoted to Stage and made available for UAT • UCSF connect to Staging tier via VPN • Staging tier can be made externally available too • This option will work for initial intermediate releases • Cons: • UCSF UAT resources will need to procure VPN accounts if staging is not available externally • Exposing staging tier externally will require clean AppScans for each application

More Related