1 / 1

Bi-MONTHLY UPDATE IQSS Team Update: RCE Cloud Reporting Period: May 2013 Due: June 2013

Bi-MONTHLY UPDATE IQSS Team Update: RCE Cloud Reporting Period: May 2013 Due: June 2013. FY 12/13 Goals: Batch - Deploy Prototype RCE Virtual Public Cloud Extension for batch jobs in the AWS(Amazon) Environment

lilac
Download Presentation

Bi-MONTHLY UPDATE IQSS Team Update: RCE Cloud Reporting Period: May 2013 Due: June 2013

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. Bi-MONTHLY UPDATEIQSS Team Update: RCE CloudReporting Period: May 2013Due: June2013 • FY 12/13 Goals: • Batch - Deploy Prototype RCE Virtual Public Cloud Extension for batch jobs in the AWS(Amazon) Environment • Non-Batch - Deploy Prototype RCE Virtual Public Cloud Extension for non-batch jobs in the AWS(Amazon) Environment • Test Period – Exercise RCE Virtual Public Cloud Extensions with typical users/jobs • Ongoing – System Evaluation, Bug Fixes, Adjustments, Performance Monitoring • Reporting Period Updates: • Configured Condor worker node bootstrap for VPC with dynamic AMI loading and local IT integration • Configured and Tested Mock Condor Master/Worker instances in VPC with dynamic loading • Completed configuration/architecture/coding for custom auto-scaling • Tested Custom auto-scaling and termination in VPC environment • Configured/executed trivial jobs to run programmatically in VPC/Condor test environment • Custom auto-scaling now positions the architecture to support a local Open Stack implementation. Now we do not rely on AWS auto-scaling features • Open issues, questions, or needs • Acquiring an AWS Support Contract will be required soon • Attachments/Metrics • None

More Related