18f / fec-cloud

Should FEC move all the things to The Cloud? We'll see.

FEC would like to research moving more things to the cloud. We're working on this with them, and we're using this repo's issues to project manage our work.

fec-cloud's Issues

Policy and Processes

An inventory of all application development and operations workflows.

Note: This inventory should include the relationships to FEC applications.

Constraints

An outline of the constraints FEC OIT faces when migrating applications and related infrastructure to the cloud. These include technical challenges, legal hurdles, team dynamics, process inefficiencies, paperwork delays, etc...

Cloud Migration Scope

This assessment will provide recommendations about the scope of the cloud migration, such as if the FEC should use a phased approach for the migration, which technologies or processes might be most difficult to migrate, if the migration will affect external entities, and if the FEC should maintain data centers.

Technology

An outline of recommended technologies and internal technology policy for working efficiently with the cloud. This would cover, for example, choices related to IaaS, PaaS, cloud orchestration, configuration management systems, CI/CD, monitoring and logging, networking requirements, desired commercial services, etc...

Tools

An inventory of all current and planned development and operations tools.

Note: This inventory should include the relationships to FEC applications.

Cloud Model Recommendations

A recommendation for private, public, or hybrid cloud options based on the FEC's ideal technology and process goals, such as shared services, technologies, programming languages, cloud orchestration, configuration, and management practices.

A private cloud refers to a virtualized computing environment controlled and managed by FEC's IT staff. A public cloud, like Amazon or Cloud.gov, sells "space" on its cloud to multiple organizations. A hybrid cloud is a combination of private and public cloud solutions.

Form IT working groups

Create a small number of hybrid 18f/FEC working groups to explore different policy areas and generate collaborative recommendations to guide the cloud migration in the future.

Cloud Roadmap

This outlines a roadmap and general timeline for a cloud migration project, including recommendations such as the sequence of moving applications and services to the cloud and their dependencies.

Internal Team Communication Plan

A communication strategy document that outlines communication channels and processes for keeping the internal team in sync and working effectively together during and after the migration. The focus is on eliminating silos and creating a culture of transparency.

IT System Assessment package

A package of inventories and a high level document that is derived from performing synthesis on various inventories gathered and producing relationships between systems.

Migration Inventory

An inventory of all the applications, shared services, infrastructure, and tools to be migrated to the cloud. This also included the overall strategy of the cloud migration. Some applications might work nicely in cloud.gov while others might need more traditional IaaS or an internal PaaS in your own public or hybrid cloud.

Team Structure

An outline and social graph of the current divisions and teams that make up FEC OIT and their relationship to the application development, operations, and security processes.

Roles and responsibilities (current and desired).

Priorities

An outline of strategic and tactical priorities for FEC OIT when evaluating the migration of candidate applications, related services, and infrastructure to the cloud.

These priorities should be ranked.

Cloud Model Recommendation Document

A comprehensive document geared towards recommendations around people, process, and technology that is derived from performing synthesis on current team dynamics, internal and external processes, and technology choices.

Requirements

An inventory of current and planned external dependencies to consider in moving to the cloud. These include low level networking and security systems, external commercial services, and VPN.

Note: This inventory should include the relationships to FEC applications.

Conduct a basic cloud.gov training

@adrianwebb commented on Tue Nov 22 2016

• Determine training attendees
• Schedule meeting time / place
• Prepare and collect materials and documentation related to training
• Give basic cloud.gov training (focus on management and simple app deployment)
• Get folks setup with the cloud.gov accounts and access they need

Getting more done in GitHub with ZenHub

Hola! @adrianwebb has created a ZenHub account for the 18f organization. ZenHub is the only project management tool integrated natively in GitHub – created specifically for fast-moving, software-driven teams.

---

How do I use ZenHub?

To get set up with ZenHub, all you have to do is download the browser extension and log in with your GitHub account. Once you do, you’ll get access to ZenHub’s complete feature-set immediately.

What can ZenHub do?

ZenHub adds a series of enhancements directly inside the GitHub UI:

• Real-time, customizable task boards for GitHub issues;
• Multi-Repository burndown charts, estimates, and velocity tracking based on GitHub Milestones;
• Personal to-do lists and task prioritization;
• Time-saving shortcuts – like a quick repo switcher, a “Move issue” button, and much more.

Add ZenHub to GitHub

Still curious? See more ZenHub features or read user reviews. This issue was written by your friendly ZenHub bot, posted by request from @adrianwebb.

Success Criteria

An outline of the various success criteria of the project from management, operations, security, and development perspectives. These success criteria should be prioritized.

IT System Assessment

An inventory and map of current and planned FEC infrastructure and IT systems. This includes physical and virtual technology environments, shared services and applications, development and operations tools, low-level dependencies (such as network filtering, firewalls and VPN), and how each relate to applications and tools used by FEC IT staff.

Maintained Inventory (What is not migrated to the cloud)

An inventory of all the applications, shared services, infrastructure, and tools that can not or do not make sense to move to the cloud at this time. This will also outline what should be done with these systems. For example, which datacenter might they live?

Infrastructure environments

An inventory of all current physical and virtual FEC computing environments that host applications, tools, and shared services.

Note: This inventory should include the relationships to FEC applications.

Applications

Inventory of current and planned applications that serve both internal FEC and external stakeholders.

Schedule FEC IT working group meetings

Schedule weekly working group sessions for the following working groups:

• Team
• Operations
• Acquisition
• Architecture
• Services

Stakeholder Communication Plan

A strategy document that recommends a stakeholder communication plan that adequately conveys the vision, benefits, progress, and allows for active stakeholder engagement throughout the process.

Test

issue to epic test

Services

An inventory of all internal and external shared services that FEC applications use.

Note: This inventory should include the relationships to FEC applications.

Cloud Roadmap Document

A comprehensive guide that outlines a plan of action and communication strategies to begin migrating the FEC OIT application and service portfolio to the cloud (what can be moved). This document also outlines what success looks like and metrics that can be used to track progress over time.

Phases and Milestones

An outline of various milestones and a dependency map. Think Gantt chart.

Processes

Current and recommended development, operations, management, communication, collaboration, and security processes for working efficiently with the cloud and modern development methodologies like Agile and DevSecOps.

Migration Strategy

A comprehensive document and inventory package that outlines what applications, shared services, infrastructure, and tools should and should not go to the cloud and where everything should ultimately live going forward.