by clicking on the page. A slider will appear, allowing you to adjust your zoom level. Return to the original size by clicking on the page again.
the page around when zoomed in by dragging it.
the zoom using the slider on the top right.
by clicking on the zoomed-in page.
by entering text in the search field and click on "In This Issue" or "All Issues" to search the current issue or the archive of back issues respectively.
by clicking on thumbnails to select pages, and then press the print button.
this publication and page.
displays a table of sections with thumbnails and descriptions.
displays thumbnails of every page in the issue. Click on a page to jump.
allows you to browse through every available issue.
FCW : July 30, 2015
have to make sure that base operating system is set up correctly for the application or range of applications so that they do not imperil any data or compromise any data or cause problems due to incompatibilities,” Heiter said. Experts also raised concerns about who would maintain governance over containers. Rosoff summed it up this way: “I can’t just willy-nilly give complete control of that environment back to an application team unless I’m sure that I’ve got the right levels of controls and governance to ensure that same level of data protection, for example. I’m thinking about data pro- tection, but you could pick almost anything.” “There are multiple approaches to management and multiple approaches to security [and to] the impli- cations of the launch of the containers themselves,” Heit- er said. Therefore, agencies should take a close look at their requirements and then find the best fit for current and future needs. “A lot of applications have key dependencies that can’t be containerized,” Milne said. “Your containers have to coexist with your existing generation of servers and the reality of multiple OS versions.... These containers are going to end up in a mixed” environment. In other words, “containers need to run on an OS,” he said. “Basically they’re sharing part of the kernel, so you can’t create a container in one operating system, then run it on another.” He sees similarities to the early days of private clouds, with containers running on bare OS until agencies figure out how to integrate them into their existing processes. Ryland had a slightly different take. “Moving toward a DevOps model itself [is] the bigger challenge — get- ting your head around how to meet compliance and other kinds of requirements in a world in which developers are constantly building and deploying new code on a daily basis,” he said. “I think historically people have thought that that super agile model is somehow not compatible with the more controlled style of government application development and deployment,” Ryland added. The future of containers at federal agencies Ryland said customers are already recognizing the ben- efits of containers. “Lately we’ve seen more cutting-edge kinds of customers who say, ‘Look, I can actually do bet- ter in meeting the government requirements because it’s completely automated. I’m removing all sorts of human decision-making from my application development-into- deployment process,’” he said. And those customers have the metrics they need because they have conducted compliance and security tests to ensure that the code they release meets their require- ments, he added. When asked for his predic- tions, Milne said, “Containers will be found in traditional agency production environ- ments. It’s going to happen, or it’s happening.” However, “those uses, those containers won’t be 100 percent containerized.” Instead, he foresees a mix of containers and non-contain- erized components or tiers, which means agencies will need management platforms that can handle such mixed environments. “I think as new applications come online, or as that development process starts, and as people begin to really internalize the DevOps model, and the [continuous integra- tion/continuous delivery] model, then they’ll really look to containers as an important tool,” Ryland said. Furthermore, containers give developers the ability to create applications wherever they are. “You can lit- erally be writing a federal application on a plane, with- out Wi-Fi, because you’ve got all the pieces you need there, containerized on your laptop. Then as soon as you land, you can deploy [your application] into a cloud... because the container provides that compatibility layer... between local off-line development and the production environment.” Heiter was equally enthusiastic about the future of con- tainers for federal agencies. “This is exciting technology,” he said. “I love where the industry is going with this. I love where the open-source community is taking it. It will be highly beneficial to the federal sector moving forward, if not already.” n July 30, 2015 FCW.COM 25 “I think containers are part of a general trend in the government toward more modern application development and architecture.” MARK RYLAND, AMAZON WEB SERVICES 0730fcw_024-025.indd 25 7/8/15 3:18 PM
July 15, 2015
August 15, 2015