x
/
fuel-plugin-calico
Code Issues Proposed changes
RETIRED, Calico provides Layer 3 Virtual Networking for Highly Scalable Data Centers
22 Commits 3 Branches 2 Tags 2.1 MiB
Go to file
Neil Jerram 7bfd81a34d For RR config, get compute host IPs from etcd and /etc/hosts 
This is a more robust and less Fuel-specific method than using
/etc/hiera/astute.yaml or /etc/hiera/nodes.yaml.  Specifically it is
difficult to know which of /etc/hiera/astute.yaml or
/etc/hiera/nodes.yaml will be updated in a given redeployment
situation, and hence which of those will contain the latest compute
node information.

Change-Id: Ie1b88709840719546dd1b924fc6e8922c829d27c
 		2016-03-08 14:25:12 +00:00
deployment_scripts For RR config, get compute host IPs from etcd and /etc/hosts 2016-03-08 14:25:12 +00:00
doc Update plugin for Fuel 7.0 release 2015-11-10 15:28:16 +00: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 .gitignore file 2015-11-09 16:25:45 +00:00
.gitreview Set .gitreview defaultbranch for 7.0 branch 2016-02-17 12:32:43 +00:00
LICENSE Remove copyright line from license file 2015-07-07 18:13:48 +01:00
README.md Remove under development warning 2016-01-11 16:39:27 +00:00
environment_config.yaml Create Calico plugin for Fuel 6.1 2015-05-20 14:42:38 +01:00
metadata.yaml Update plugin for Fuel 7.0 release 2015-11-10 15:28:16 +00:00
pre_build_hook Create Calico plugin for Fuel 6.1 2015-05-20 14:42:38 +01: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

Calico’s 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 center’s 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.0-0.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.0-0.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.0-0.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