1 / 3

Deploying the Cloud : Lessons Learned from Early Adopters of Secure Cloud

Deploying the Cloud : Lessons Learned from Early Adopters of Secure Cloud. December 16, 2011. COL Charles Wells PM, DCGS-A charles.wells@us.army.mil (443) 861-2442. Lessons Learned: Deployment of First Tactical Cloud in DoD. SIPR IOC: 6 Apr 2011 CXI IOC: 25 May 2011.

jenna
Télécharger la présentation

Deploying the Cloud : Lessons Learned from Early Adopters of Secure Cloud

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. Deploying the Cloud:Lessons Learned from Early Adopters of Secure Cloud December 16, 2011 COL Charles Wells PM, DCGS-A charles.wells@us.army.mil (443) 861-2442

  2. Lessons Learned:Deployment of First Tactical Cloud in DoD • SIPR IOC: 6 Apr 2011 • CXI IOC: 25 May 2011 • Size, Weight, Power Considerations Critical • Pad space difficult to obtain – Move chiller into Pod to minimize footprint • Limited amperage on LSAs / FOBs • Maximum processing/storage with least power • High-efficiency / “green” components preferred • Transport – flexibility is key • Need the ability to fit Cloud pod on MIL Airlift (C-130/C-141) • Commodity Hardware works well: • Meet military needs without MILSPEC • Inexpensive and quick to procure and field • Leverage latest innovations from industry • Software: • Existing Government software solutions work • NSA Cloud work leveraged for Army tactical Cloud deployment • Huge savings – development costs and long-term O&M • Participate in software forums / committees • Intelligence Community (IC) Cloud, Ozone Widget Framework, Forge.mil • Ensure that project needs are reflected in future versions • “Open source is a two way street“– Contribute back to the community • Cloud software development occurs rapidly • Diligent configuration management critical to success • Personnel: • Market for Cloud Experts - tight • Leverage dual-approach: • Temporary cloud experts focused on immediate / critical projects • Balance with long-term Cloud team for continuity

  3. Lessons Learned:Deployment of First Tactical Cloud in DoD Common Map Widget • Lessons from Soldiers: • Must support analysts’ workflows • Collaborative tools are critical to support Intel success and effectiveness • Build for simplicity:Tools wont be used if they don’t make the Soldier’s job easier • Soldier / Developer communication key • Plan for getting feedback from analysts throughout the development lifecycle. • Don’t dismiss small usability itemsWhat might be overlooked by a developer could be a an analyst’s “golden widget” • Communication is Two-way: Ensure Intel analysts fully understand new widget capabilities and application SandStorm Time Line

More Related