Shows & Panels
- The 2014 Big Picture on Cyber Security
- AFCEA Answers
- Ask the CIO
- Building the Hybrid Cloud
- Connected Government: How to Build and Procure Network Services for the Future
- Continuing Diagnostics and Mitigation: Discussion of Progress and Next Steps
- Federal Executive Forum
- Federal Tech Talk
- The Future of Government Data Centers
- The Future of IT: How CIOs Can Enable the Service-Oriented Enterprise
- The Intersection: Where Technology Meets Transformation
- Maximizing ROI Through Data Center Consolidation
- Mitigating Insider Threats in Virtual & Cloud Environments
- Modern Mission Critical Series
- Moving to the Cloud. What's the best approach for me
- Navigating Tough Choices in Government Cloud Computing
- The New Generation of Database
- Satellite Communications: Acquiring SATCOM in Tight Times
- Targeting Advanced Threats: Proven Methods from Detection through Remediation
- Transformative Technology: Desktop Virtualization in Government
- The Truth About IT Opex and Software Defined Networking
- Value of Health IT
- Air Traffic Management Transformation Report
- Cloud First Report
- General Dynamics IT Enterprise Center
- Gov Cloud Minute
- Government in Technology Series
- Homeland Security Cybersecurity Market Report
- National Cybersecurity Awareness Month
- Technology Insights
- The Cyber Security Report
- The Next Generation Cyber Security Experts
Shows & Panels
Containers: A new variation on virtualization
Tuesday - 7/15/2014, 7:55pm EDT
Most listeners are familiar with virtualization when it comes to servers or, perhaps, desktops. Today we'll take a look at a new aspect of virtualization - a concept called containers.
Here is the problem that federal information professionals face: they are getting strongly encouraged to move applications to the cloud. They are also strongly encouraged to use agile software development methodologies.
The problem is that if you are a project leader and want to move an app to the cloud you must first go through multiple tests, then pre-production environments, then into production.
Each step along the way can cause a team to conflict. The developers bump heads with the testers and the operations people don't communicate clearly to the developers.
One solution is to put together an application into a small container that is portable. That way, an developer can send this container to the testers and not have to worry about setting up a test environment on a server.
Using containers allows for continuous delivery because the DevOps team doesn't have to set up an entire operating system just to test an application. They can use Docker to put that application into a closed environment that just uses the part of the operating system that is relevant.