Embed Size (px)
Citation preview
Deploying the Cloud:Lessons Learned from Early Adopters of Secure Cloud
COL Charles WellsPM, [email protected](443) 861-2442
December 16, 2011December 16, 2011
Lessons Learned:Lessons Learned:Deployment of First Tactical Cloud in Deployment of First Tactical Cloud in DoDDoD
2
• SIPR IOC: 6 Apr 2011• CXI IOC: 25 May 2011Size, 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
SandStorm
Common Map Widget
Time Line
Lessons Learned:Lessons Learned:Deployment of First Tactical Cloud in DoDDeployment of First Tactical Cloud in DoD
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 items
What 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
