RETIRED, Calico provides Layer 3 Virtual Networking for Highly Scalable Data Centers
Go to file
OpenDev Sysadmins 10c759cded OpenDev Migration Patch
This commit was bulk generated and pushed by the OpenDev sysadmins
as a part of the Git hosting and code review systems migration
detailed in these mailing list posts:

http://lists.openstack.org/pipermail/openstack-discuss/2019-March/003603.html
http://lists.openstack.org/pipermail/openstack-discuss/2019-April/004920.html

Attempts have been made to correct repository namespaces and
hostnames based on simple pattern matching, but it's possible some
were updated incorrectly or missed entirely. Please reach out to us
via the contact information listed at https://opendev.org/ with any
questions you may have.
2019-04-19 19:51:15 +00:00
deployment_scripts Further tweaks for updating RR config on controller nodes 2016-03-10 12:56:39 +00:00
doc Add docs: user guide, test plan and test report 2016-04-26 17:49:17 -05:00
repositories Create Calico plugin for Fuel 6.1 2015-05-20 14:42:38 +01:00
specs Update plugin for Fuel 7.0 release 2015-11-10 15:28:16 +00:00
.gitignore Add docs: user guide, test plan and test report 2016-04-26 17:49:17 -05:00
.gitreview OpenDev Migration Patch 2019-04-19 19:51:15 +00:00
LICENSE Remove copyright line from license file 2015-07-07 18:13:48 +01:00
README.md Further tweaks for updating RR config on controller nodes 2016-03-10 12:56:39 +00:00
deployment_tasks.yaml Add required deployment_tasks.yaml file 2016-03-08 11:11:37 +00:00
environment_config.yaml Create Calico plugin for Fuel 6.1 2015-05-20 14:42:38 +01:00
metadata.yaml Further tweaks for updating RR config on controller nodes 2016-03-10 12:56:39 +00:00
tasks.yaml Do not remove default network as this breaks any subsequent re-deployments 2016-01-11 16:39:27 +00:00

README.md

Calico plugin for Mirantis Fuel

Calicos pure L3 approach to data center networking integrates seamlessly with Mirantis OpenStack to bring simple, scalable and secure networking to your deployment.

Based on the same scalable IP network principles as the Internet, Calico implements a highly efficient vRouter in each compute node that leverages the existing Linux kernel forwarding engine without the need for vSwitches. Each vRouter propagates workload reachability information (routes) to the rest of the data center using BGP either directly in small scale deployments or via BGP route reflectors to reach Internet level scales in large deployments.

Calico peers directly with the data centers physical fabric (whether L2 or L3) without the need for on/off ramps, NAT, tunnels, or overlays.

With Calico, networking issues are easy to troubleshoot. Since it's all IP, standard tools such as ping and traceroute will just work.

Calico supports rich and flexible network policy which it enforces using bookended ACLs on each compute node to provide tenant isolation, security groups, and external reachability constraints.

For more details, see projectcalico.org.

Limitations:

None.

Compatible versions:

Mirantis Fuel 7.0

To build the plugin:

  • Install the fuel plugin builder, fpb:

      easy_install pip
    
      pip install fuel-plugin-builder
    
  • Clone the calico plugin repository and run the plugin builder:

      git clone https://github.com/openstack/fuel-plugin-calico
    
      cd fuel-plugin-calico/
    
      fpb --build .
    
  • Check that the file calico-fuel-plugin-2.0-2.0.2-1.noarch.rpm was created.

To install the plugin:

  • Prepare a clean fuel master node.

  • Copy the plugin onto the fuel master node:

      scp calico-fuel-plugin-2.0-2.0.2-1.noarch.rpm root@<Fuel_Master_Node_IP>:/tmp
    
  • Install the plugin on the fuel master node:

      cd /tmp
    
      fuel plugins --install calico-fuel-plugin-2.0-2.0.2-1.noarch.rpm
    
  • Check the plugin was installed:

      fuel plugins --list
    

User Guide

To deploy a cluster with the Calico plugin, use the Fuel web UI to deploy an OpenStack cluster in the usual way, with the following guidelines:

  • Create a new OpenStack environment, selecting:

    Kilo on Ubuntu Trusty

    "Neutron with VLAN segmentation" as the networking setup

  • Under the settings tab, make sure the following options are checked:

    "Assign public network to all nodes"

    "Use Calico Virtual Networking"

  • Under the network tab, configure the 'Public' settings (leaving all of the other sections with their default values). For example (exact values will depend on your setup):

    • IP Range: 172.18.203.60 - 172.18.203.69
      • CIDR: 172.18.203.0/24
      • Use VLAN tagging: No
      • Gateway: 172.18.203.1
    • Floating IP range: 172.18.203.70 - 172.18.203.79
  • Add nodes (for meaningful testing, you will need at least two compute nodes in addition to the controller).

  • Deploy changes