Jump to: navigation, search

Congress

Revision as of 22:31, 1 November 2013 by Pettori (talk | contribs) (Created page with "== Policy as a service ("Congress") == === Mission === Congress is an OpenStack project to provide Policy as a service across any collection of cloud services in order to off...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

Policy as a service ("Congress")

Mission

Congress is an OpenStack project to provide Policy as a service across any collection of cloud services in order to offer governance and compliance for dynamic infrastructures.

Why Congress

IT services will always be governed and brought into compliance with business-level policies.

In the past, policy was enforced manually, by having long processes in which someone who send an email or open a case asking for an application to be put on the network, secured by different firewall entries, connected to an agreed-on storage… However in the cloud era, IT has become too agile, with users always asking for faster delivery of services and requests of new instances quickly overwhelming the different team responsible for governance; hence, manual enforcement is no longer feasible.

Both enterprises and vendors have fielded engines for enforcing policy (semi)-automatically, creating a fragmented market where enterprises reinvent the wheel while maintaining their own code, and vendors fail to meet enterprise needs, either for technical reasons or because their solutions require vertical integration and lock-in.

The congress policy service enables IT services to extend their OpenStack footprint by onboarding new applications while keeping strong compliance and governance dictated by their own business policies. All of that leveraging a community-driven implementation in which vendors would be able to plug into a common interface.

What is Congress

Congress aims to provide an extensible open-source framework for governance and regulatory compliance across any cloud services (e.g. application, network, compute and storage) within a dynamic infrastructure.

Congress aims to include the following functionality: Allow cloud administrators and tenants to use a high-level declarative language to describe business logic like: Application A is only allowed to communicate with application B? Virtual machine owned by tenant A should always have a public network connection if tenant A is part of the group B Virtual machine A should never be provisioned in a different geographic region than storage B Offer a pluggable architecture that connects to any collection of cloud services Enforce policy proactively: preventing violations before they occur Enforce policy reactively: identifying violations after they occur and taking corrective action Providing administrators insight into policy and its violations: identifying violations, explaining their causes, computing potential remediations, simulate a sequence of changes and explain why the result is in or out of compliance.

Development

Roadmap