Welcome!

@CloudExpo Authors: Zakia Bouachraoui, Elizabeth White, Liz McMillan, Pat Romanski, Yeshim Deniz

Related Topics: @CloudExpo, Government Cloud

@CloudExpo: Blog Feed Post

Analysis of U.S. CIO Federal Cloud Computing Strategy

U.S. CIO Provides Guidance on Cloud Computing Adoption

On February 8, 2011, the Office of the U.S. Chief Information Office released its Federal Cloud Computing Strategy.  In no uncertain terms, this strategy is focused primarily on one key factor—deliver more value for the same dollars spent.  Semantically, to me, this is a very different statement than establishing this strategy around lowering IT costs.  That is, according to what I can discern, it is not the intention of this document to promote the use of Cloud Computing to reduce the overall spending on IT (at least not at this time), although, one would hope that would be a positive side-effect, but instead, use the same allocated funds on Cloud Computing with the intent of receiving a greater value for that same spend.

This small, and perhaps arcane, difference between costs reduction and greater value is of critical importance when measuring success for this administration in promoting a Cloud First strategy.  Depending upon which pundit/analyst you follow or hear talk you may hear a different list of benefits from Cloud Computing.  Certainly, the list of benefits should be different for public and private sectors and, within public sectors, each agent has its own mission adding even more variance into the list of benefits.  However, this document transcends those variances in a way that allows all agents to participate while limiting overall objections.  Hence, this document, if nothing else, accomplishes a monumental feat of delivering some practical vision while limiting the opportunity for the ideas and concepts to easily be dismissed.

Additionally, this document also serves as a model that even the private sector can follow for adoption of Cloud Computing.  It serves as an example for establishing a solid foundation that includes a business justification, addresses security concerns, provides a decision framework for identifying appropriate services to move to the Cloud, illustrates successful use case examples, and establishes a model for governance.  The latter is a key and often overlooked requirement for developing successful Cloud Computing strategies.  The governance foundation section clearly identifies the role of various departments and agencies with regard to leading direction for Cloud Computing adoption in the U.S. Federal government.  They are defined as follows:

  • National Institute of Standards and Technology (NIST) will lead and collaborate with Federal, State, and local government agency CIOs, private sector experts, and international bodies to identify and prioritize cloud computing standards and guidance
  • General Service Administration (GSA) will develop government-wide procurement vehicles and develop government-wide and cloud-based application solutions where needed
  • Department of Homeland Security (DHS) will monitor operational security issues related to the cloud
  • Agencies will be responsible for evaluating their sourcing strategies to fully consider cloud computing solutions
  • Federal CIO Council will drive government-wide adoption of cloud, identify next-generation cloud technologies, and share best practices and reusable example analyses and templates
  • The Office of Management and Budget (OMB) will coordinate activities across governance bodies, set overall cloud-related priorities, and provide guidance to agencies
  • All-in-all, this document is a highly-reusable piece of literature that is difficult to find fault with.  I will admit I was expecting this document to be a fluff piece that offered

All-in-all, this document is a highly-reusable piece of literature that is difficult to find fault with.  I will admit I was expecting this document to be a fluff piece that offered lofty goals and praised Cloud Computing simply because it’s “the hot buzzword of the month”, but one must give credit where credit is due; and in this case much credit is due to Vivek and team.  Good on ya!

Read the original blog entry...

More Stories By JP Morgenthal

JP Morgenthal is a veteran IT solutions executive and Distinguished Engineer with CSC. He has been delivering IT services to business leaders for the past 30 years and is a recognized thought-leader in applying emerging technology for business growth and innovation. JP's strengths center around transformation and modernization leveraging next generation platforms and technologies. He has held technical executive roles in multiple businesses including: CTO, Chief Architect and Founder/CEO. Areas of expertise for JP include strategy, architecture, application development, infrastructure and operations, cloud computing, DevOps, and integration. JP is a published author with four trade publications with his most recent being “Cloud Computing: Assessing the Risks”. JP holds both a Masters and Bachelors of Science in Computer Science from Hofstra University.

CloudEXPO Stories
Adding public cloud resources to an existing application can be a daunting process. The tools that you currently use to manage the software and hardware outside the cloud aren’t always the best tools to efficiently grow into the cloud. All of the major configuration management tools have cloud orchestration plugins that can be leveraged, but there are also cloud-native tools that can dramatically improve the efficiency of managing your application lifecycle. In his session at 18th Cloud Expo, Alex Lovell-Troy, Director of Solutions Engineering at Pythian, presented a roadmap that can be leveraged by any organization to plan, analyze, evaluate, and execute on moving from configuration management tools to cloud orchestration tools. He also addressed the three major cloud vendors as well as some tools that will work with any cloud.
When applications are hosted on servers, they produce immense quantities of logging data. Quality engineers should verify that apps are producing log data that is existent, correct, consumable, and complete. Otherwise, apps in production are not easily monitored, have issues that are difficult to detect, and cannot be corrected quickly. Tom Chavez presents the four steps that quality engineers should include in every test plan for apps that produce log output or other machine data. Learn the steps so your team's apps not only function but also can be monitored and understood from their machine data when running in production.
DXWordEXPO New York 2018, colocated with CloudEXPO New York 2018 will be held November 11-13, 2018, in New York City and will bring together Cloud Computing, FinTech and Blockchain, Digital Transformation, Big Data, Internet of Things, DevOps, AI, Machine Learning and WebRTC to one location.
With more than 30 Kubernetes solutions in the marketplace, it's tempting to think Kubernetes and the vendor ecosystem has solved the problem of operationalizing containers at scale or of automatically managing the elasticity of the underlying infrastructure that these solutions need to be truly scalable. Far from it. There are at least six major pain points that companies experience when they try to deploy and run Kubernetes in their complex environments. In this presentation, the speaker will detail these pain points and explain how cloud can address them.
Discussions of cloud computing have evolved in recent years from a focus on specific types of cloud, to a world of hybrid cloud, and to a world dominated by the APIs that make today's multi-cloud environments and hybrid clouds possible. In this Power Panel at 17th Cloud Expo, moderated by Conference Chair Roger Strukhoff, panelists addressed the importance of customers being able to use the specific technologies they need, through environments and ecosystems that expose their APIs to make true change and transformation possible.