Alcor Control Agent

Next-gen networking control plane - Alcor Control Agent

• For information about how to use Alcor Control Agent, visit Getting Started
• To ask questions, raise feature requests and get assistance from our community, join Alcor Slack channels (invitation for first-time participant) or Google Group
• To report an issue, visit Issues page

In this README:

• Introduction
• Repositories
• Directory Structure

Introduction

The Cloud Fabric Alcor Control Agent (ACA) runs on each host machine. It serves as a stateless proxy between Alcor controller and host machine networking components for control plane operations. Below are the highlevel Agent components.

Repositories

The Alcor project is divided across a few GitHub repositories.

• alcor/alcor: This is the main repository of Alcor Regional Controller that you are currently looking at. It hosts controllers' source codes, build and deployment instructions, and various documents that detail the design of Alcor.

• alcor/alcor_control_agent: This repository contains source codes for a host-level stateless agent that connects regional controllers to the host data-plane component. It is responsible for programming on-host data plane with various network configuration for CURD of VPC, subnet, port, Security group etc., and monitoring network health of containers and VMs on the host.

• alcor/integration: The integration repository contains codes and scripts for end-to-end integration of Alcor control plane with popular orchestration platforms and data plane implementations. We currently support integration with Kubernetes (via CNI plugin) and Mizar Data Plane. We will continue to integrate with other orchestration systems and data plane implementations.

Directory Structure

This main repository of Alcor Control Agent is organized as follows:

• build: script and docker files for building
• docs: design documentation
• etc/k8s: k8s integration files
• include: header files
• src: source code
• test: Unit and integration test code