Fujitsu K5 Inter-AZ Networking Heat Stack

Today we will look at a simple heat stack to implement the enhanced network connector that the K5 platform implements to link subnets within projects across availability zones.

nc-overview

At Fujitsu our engineering team, currently ranking at number 5 for lines of code committed to the OpenStack project, (well done folks) have enhanced neutron in our K5 platform to give it the same hardware failure domain capability as is present in the nova project today. This means that the neutron service can be split across availability zones which in turn makes it easier to split your availability zones across remote data centres.

See this video for the technical details – 14 minutes in…

As a result of this enhancement we have developed a new K5 neutron component called a network connector that is used to link networks in the same project that are in separate availability zones. They must have different subnet CIDRs.

The following heat stack creates two private networks, one in each availability zone and then joins them together using the new network connector and its endpoint components.

This template should get you up and running quickly should you wish to test it out.


heat_template_version: 2013-05-23
# Author: Graham Land
# Date: 21/10/2016
# Purpose: Create two subnets, one in each availability zone, within the same project and then join these subnets
# using a network connector. The subnets also get configured with the new routes.
#
# Twitter: @allthingsclowd
# Blog: https://allthingscloud.eu
description: Example of how to create and join two networks across AZs within the same project on Fujitsu K5 IaaS
# Input parameters
parameters:
az1:
type: string
label: Availability Zone
description: Region AZ to use
default: "uk-1a"
az1_net_name:
type: string
label: Network name
description: Network name
default: "demo_net_az1"
az1_subnet_name:
type: string
label: Subnet name
description: Subnet name
default: "demo_subnet_az1"
az1_subnet_CIDR:
type: string
label: Subnet CIDR
description: Subnet CIDR
default: "192.168.100.0/24"
az1_subnet_DHCP_Start_Address:
type: string
label: Subnet DHCP Pool start address
description: Subnet DHCP Pool start address
default: "192.168.100.100"
az1_subnet_DHCP_End_Address:
type: string
label: Subnet DHCP Pool end address
description: Subnet DHCP Pool end address
default: "192.168.100.150"
az1_subnet_DNS:
type: string
label: Subnet DNS
description: Subnet DNS
default:
– "62.60.39.9"
– "62.60.39.10"
az1_subnet_Routes:
type: string
label: Subnet Host Routes
description: Subnet Host Routes
default:
– "nexthop": "192.168.100.253"
"destination": "10.10.10.0/24"
az1_subnet_Gateway:
type: string
label: Subnet gateway address
description: Subnet gateway address
default: "192.168.100.254"
az1_EndPoint_ip:
type: string
label: Subnet endpoint address
description: Subnet endpoint address
default: "192.168.100.253"
az2:
type: string
label: Availability Zone
description: Region AZ to use
default: "uk-1b"
az2_net_name:
type: string
label: Network name
description: Network name
default: "demo_net_az2"
az2_subnet_name:
type: string
label: Subnet name
description: Subnet name
default: "demo_subnet_az2"
az2_subnet_CIDR:
type: string
label: Subnet CIDR
description: Subnet CIDR
default: "10.10.10.0/24"
az2_subnet_DHCP_Start_Address:
type: string
label: Subnet DHCP Pool start address
description: Subnet DHCP Pool start address
default: "10.10.10.100"
az2_subnet_DHCP_End_Address:
type: string
label: Subnet DHCP Pool end address
description: Subnet DHCP Pool end address
default: "10.10.10.150"
az2_subnet_DNS:
type: string
label: Subnet DNS
description: Subnet DNS
default:
– "62.60.42.9"
– "62.60.42.10"
az2_subnet_Routes:
type: string
label: Subnet Host Routes
description: Subnet Host Routes
default:
– "nexthop": "10.10.10.253"
"destination": "192.168.100.0/24"
az2_subnet_Gateway:
type: string
label: Subnet gateway address
description: Subnet gateway address
default: "10.10.10.254"
az2_EndPoint_ip:
type: string
label: Subnet endpoint address
description: Subnet endpoint address
default: "10.10.10.253"
# K5 Infrastructure resources to be built
resources:
# Create a private network in availability zone 1
private_net_az1:
type: OS::Neutron::Net
properties:
availability_zone: { get_param: az1 }
name: { get_param: az1_net_name }
# Create a new subnet on the private network
private_subnet_az1:
type: OS::Neutron::Subnet
depends_on: private_net_az1
properties:
availability_zone: { get_param: az1 }
name: { get_param: az1_subnet_name }
network_id: { get_resource: private_net_az1 }
cidr: { get_param: az1_subnet_CIDR }
gateway_ip: { get_param: az1_subnet_Gateway }
allocation_pools:
– start: { get_param: az1_subnet_DHCP_Start_Address }
end: { get_param: az1_subnet_DHCP_End_Address }
dns_nameservers: { get_param: az1_subnet_DNS }
host_routes: { get_param: az1_subnet_Routes }
# Create a private network in availability zone 1
private_net_az2:
type: OS::Neutron::Net
properties:
availability_zone: { get_param: az2 }
name: { get_param: az2_net_name }
# Create a new subnet on the private network
private_subnet_az2:
type: OS::Neutron::Subnet
depends_on: private_net_az2
properties:
availability_zone: { get_param: az2 }
name: { get_param: az2_subnet_name }
network_id: { get_resource: private_net_az2 }
cidr: { get_param: az2_subnet_CIDR }
gateway_ip: { get_param: az2_subnet_Gateway }
allocation_pools:
– start: { get_param: az2_subnet_DHCP_Start_Address }
end: { get_param: az2_subnet_DHCP_End_Address }
dns_nameservers: { get_param: az2_subnet_DNS }
host_routes: { get_param: az2_subnet_Routes }
# Create a security group
server_security_group1:
type: OS::Neutron::SecurityGroup
properties:
description: Add security group rules for server
name: NetworkConnector
rules:
– remote_ip_prefix: 0.0.0.0/0
protocol: tcp
port_range_min: 1
port_range_max: 65535
– remote_ip_prefix: 0.0.0.0/0
protocol: udp
port_range_min: 1
port_range_max: 65535
– remote_ip_prefix: 0.0.0.0/0
protocol: icmp
############################### AZ Interconnect ###########################################################
az1_nc_port:
type: OS::Neutron::Port
depends_on: [ server_security_group1 ]
properties:
availability_zone: { get_param: az1 }
network_id: { get_resource: private_net_az1 }
security_groups: [{ get_resource: server_security_group1 }]
fixed_ips:
– subnet_id: { get_resource: private_subnet_az1 }
ip_address: { get_param: az1_EndPoint_ip }
az2_nc_port:
type: OS::Neutron::Port
depends_on: [ server_security_group1 ]
properties:
availability_zone: { get_param: az2 }
network_id: { get_resource: private_net_az2 }
security_groups: [{ get_resource: server_security_group1 }]
fixed_ips:
– subnet_id: { get_resource: private_subnet_az2 }
ip_address: { get_param: az2_EndPoint_ip }
az1_network_connector:
type: FCX::Neutron::NetworkConnector
depends_on: [ az1_nc_port,az2_nc_port ]
properties:
name: "Demo_AZ_Network_Connector"
az1_nc_endpoint:
type: FCX::Neutron::NetworkConnectorEndpoint
depends_on: [ az1_nc_port,az2_nc_port ]
properties:
endpoint_type: "availability_zone"
name: "AZ1-NC-EP"
network_connector_id: { get_resource: az1_network_connector }
location: { get_param: az1 }
az2_nc_endpoint:
type: FCX::Neutron::NetworkConnectorEndpoint
depends_on: [ az1_nc_port,az2_nc_port ]
properties:
endpoint_type: "availability_zone"
name: "AZ2-NC-EP"
network_connector_id: { get_resource: az1_network_connector }
location: { get_param: az2 }
az1_endpoint_connection:
type: FCX::Neutron::NetworkConnectorEndpointConnection
depends_on: [ az1_nc_port,az2_nc_port ]
properties:
port_id: { get_resource: az1_nc_port }
network_connector_endpoint_id: { get_resource: az1_nc_endpoint }
az2_endpoint_connection:
type: FCX::Neutron::NetworkConnectorEndpointConnection
depends_on: [ az1_nc_port,az2_nc_port ]
properties:
port_id: { get_resource: az2_nc_port }
network_connector_endpoint_id: { get_resource: az2_nc_endpoint }
Contact GitHub API Training Shop Blog About
© 2016 GitHub, Inc. Terms Priv

view raw

K5NetworkConnectorDemo.yml

hosted with ❤ by GitHub

Now all you need to do is spin up an instance on each subnet and you will see that you have layer 3 connectivity between the instances …

networkconnector

Happy Stacking!

 

 

4 thoughts on “Fujitsu K5 Inter-AZ Networking Heat Stack”

  1. Hi Graham, a very useful example. Any chance you can fire up iPerf and get me some average inter AZ speeds across the link connected by the Network Connectors in this example ?

    Like

    Reply

      1. Excellent, I still can’t believe how good a service this is. Free Fibre DWDM link use between Cloud availability zones is what keeps me using this service!

        Like

Leave a Reply

Fill in your details below or click an icon to log in:

Gravatar
WordPress.com Logo

You are commenting using your WordPress.com account. ( Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. ( Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. ( Log Out /  Change )

Cancel

Connecting to %s