forked from crowbar/barclamp-network
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Rob Hirschfeld
committed
Nov 9, 2013
1 parent
ffa320f
commit 67614ca
Showing
1 changed file
with
104 additions
and
78 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,80 +1,106 @@ | ||
| ### Network Barclamp ### | ||
| ### Rules ### | ||
| * External or Public network: When this is reference, the definition is the network that is not internall to the this solution. it could be an internet routerable IP, Private Lab, or even Corporate network. | ||
| * router_pref: When this is used it must unique to each network. No two or more networks can have teh same number, even if they are on the same vlan. | ||
| * router_pref: the lowest number is used to set the default route on the host in quesiton | ||
| ## Network Barclamp ## | ||
|
|
||
| ### Sections ### | ||
| * storage | ||
| * Used by the Swift System to handle all interactions between Swift nodes and Swift-Proxy. | ||
| * External Access: Ineternal Only. Highly recommended to not have external connectivity as it has all the storage data on it. | ||
| * Router and router_pref are optional | ||
| * Ranges - requires section "host" | ||
| * "host" - used to assign IP addresses to each of the Swift nodes. | ||
| * No special rules. | ||
| * public | ||
| * Used by nova-compute, nova-controller, admin, and swift-proxy to access the external network | ||
| * External Access - Yes this is how the nodes will talk beyond the Solution | ||
| * router and router_pref - Required.? router_pref must be the lowest number of all. | ||
| * Ranges - requires the sections "host" and "dhcp" | ||
| * "host" used to assign an IP to each node | ||
| * "dhcp" reserved but must be defined | ||
| * Rules - router_pref must be the lowest defined | ||
| * nova_floating | ||
| * Used by nova to create the floating network in the nova database | ||
| * External Access - Yes | ||
| * No additional?- router and router_pref must not be defined | ||
| * Ranges - requires section on "host" | ||
| * "host" used to assign an IP to each node | ||
| * Rules | ||
| * Network must be a logical subnet of the public range | ||
| * Subnet is a logical subnet of the public range | ||
| * Example - Public is 192.168.123.0/24 and nova floating then can be 192.168.123.64/26 or 192.168.123.128/26 | ||
| *nova_fixed | ||
| * Used by nova to create the private(backend) network in the nova database | ||
| * External Access - None | ||
| * No additional - router and router_pref should not be defined, but if Public will always win | ||
| * Ranges - requires "host" and "dhcp" | ||
| * "host" used to assign an IP to each node | ||
| * "dhcp"? is used to create the nova database | ||
| * Rules - No special rules | ||
| * os_sdn | ||
| * Used by Openstack to create GRE tunnels between the Controller and Compute Nodes | ||
| * External Access -None | ||
| * No Additional - router and router_pref should be defined | ||
| * Ranges - requires "host" | ||
| * Rules - No Special Rules | ||
| * bmc | ||
| * Used by each computer to setup? IPMI configurable device | ||
| * External Access - Possible | ||
| * router and router_pref are optional items | ||
| * Ranges - requires only "host" | ||
| * Rules - if it is separate from the "admin" network then bmc_vlan must be the same network | ||
| * bmc_vlan | ||
| * Used by the admin node to control the IPMI configurable devices | ||
| * External Access - Not required but helpful | ||
| * No additional sections | ||
| * Ranges "host"? used to give the admin node access to the BMC's | ||
| * Rules - Must be the same subnet as the BMC | ||
| * Admin | ||
| * Used by all each computer to communication with the Crowbar Server and for all Nova work | ||
| * External Access - Not required but helpful | ||
| * router and router_pref are required | ||
| * Ranges - requires "host", "dhcp", "switch", and "admin" | ||
| * Rules - no special rules | ||
| The network barclamp is operational, with the following list of | ||
| features: | ||
|
|
||
| ### Stanza ### | ||
| * conduit - Name of the conduit this network is to use.? | ||
| * When more than one network can uses the same conduit, the interfaces can become dual homed depending on the add_bridge and use_vlan | ||
| * vlan - the Vlan Number assigned to that network.? This comes into play when the use_vlan is set to 'true'. | ||
| * use_vlan - 'true' or 'false' | ||
| * When set to true, the node will be configure to use 802.1q vlan tagging.? A like rule will need to be created on the switch to accept the tagged packet. | ||
| * add_bridge - 'true' or 'false' | ||
| * When set to 'true', the node will bridge the network.? | ||
| * SPECIAL RULE:? When this is true and VM's are being used on the bridge network Team Mode must be set to allow this.? Team mode 6 (Adaptive Load Balancing and team mode 1 (Round Robin) are known to cause failures | ||
| * subnet - this is the actual subnet, for example. 192.168.124.0, 192.168.123.128 | ||
| * netmask - this is the Netmask for the network subnet. Please see Nova-Floating for it special requirements | ||
| * broadcast - network broadcast | ||
| * router - This is the router IP for this particular network | ||
| * router_pref - This is like a route metric the lower number becomes your default route | ||
| * ranges - the different ranges you want to use in general "host" is required. | ||
| ### IPv6 support. | ||
|
|
||
| You can create ranges and routers for IPv6 addresses | ||
| as well as IPv4 addresses, and you can tell a network that it should | ||
| automatically assign IPv6 addresses to every node on that network by | ||
| setting the v6prefix setting for that network to either: | ||
| * a /64 network prefix, or | ||
| * "auto", which will create a globally unique RFC4193 IPv6 network | ||
| prefix from a randomly-chosen 40 bit number (unique per cluster | ||
| installation) followed by a subnet ID based on the ID of the | ||
| Crowbar network. | ||
| Either way, nodes in a Crowbar network that has a v6prefix will get | ||
| an interface ID that maps back to their FQDN via the last 64 bits of | ||
| the md5sum of that FQDN. For now, the admin network will | ||
| automatically create an RFC4193 IPv6 network if it is not passed a | ||
| v6prefix so that we can easily test all the core Crowbar components | ||
| with IPv6 as well as IPv4. The DNS barclamp has been updated to | ||
| create the appropriate AAAA records for any IPv6 addresses in the | ||
| admin network. | ||
|
|
||
| ## TODO REVIEW NEEDED >>>>>> | ||
|
|
||
| ### Rules ### | ||
| * External or Public network: When this is reference, the definition is the network that is not internal to the this solution. it could be an internet routerable IP, Private Lab, or even Corporate network. | ||
| * router_pref: When this is used it must unique to each network. No two or more networks can have teh same number, even if they are on the same vlan. | ||
| * router_pref: the lowest number is used to set the default route on the host in quesiton | ||
|
|
||
| ### Sections ### | ||
| * storage | ||
| * Used by the Swift System to handle all interactions between Swift nodes and Swift-Proxy. | ||
| * External Access: Ineternal Only. Highly recommended to not have external connectivity as it has all the storage data on it. | ||
| * Router and router_pref are optional | ||
| * Ranges - requires section "host" | ||
| * "host" - used to assign IP addresses to each of the Swift nodes. | ||
| * No special rules. | ||
| * public | ||
| * Used by nova-compute, nova-controller, admin, and swift-proxy to access the external network | ||
| * External Access - Yes this is how the nodes will talk beyond the Solution | ||
| * router and router_pref - Required.? router_pref must be the lowest number of all. | ||
| * Ranges - requires the sections "host" and "dhcp" | ||
| * "host" used to assign an IP to each node | ||
| * "dhcp" reserved but must be defined | ||
| * Rules - router_pref must be the lowest defined | ||
| * nova_floating | ||
| * Used by nova to create the floating network in the nova database | ||
| * External Access - Yes | ||
| * No additional?- router and router_pref must not be defined | ||
| * Ranges - requires section on "host" | ||
| * "host" used to assign an IP to each node | ||
| * Rules | ||
| * Network must be a logical subnet of the public range | ||
| * Subnet is a logical subnet of the public range | ||
| * Example - Public is 192.168.123.0/24 and nova floating then can be 192.168.123.64/26 or 192.168.123.128/26 | ||
| *nova_fixed | ||
| * Used by nova to create the private(backend) network in the nova database | ||
| * External Access - None | ||
| * No additional - router and router_pref should not be defined, but if Public will always win | ||
| * Ranges - requires "host" and "dhcp" | ||
| * "host" used to assign an IP to each node | ||
| * "dhcp"? is used to create the nova database | ||
| * Rules - No special rules | ||
| * os_sdn | ||
| * Used by Openstack to create GRE tunnels between the Controller and Compute Nodes | ||
| * External Access -None | ||
| * No Additional - router and router_pref should be defined | ||
| * Ranges - requires "host" | ||
| * Rules - No Special Rules | ||
| * bmc | ||
| * Used by each computer to setup? IPMI configurable device | ||
| * External Access - Possible | ||
| * router and router_pref are optional items | ||
| * Ranges - requires only "host" | ||
| * Rules - if it is separate from the "admin" network then bmc_vlan must be the same network | ||
| * bmc_vlan | ||
| * Used by the admin node to control the IPMI configurable devices | ||
| * External Access - Not required but helpful | ||
| * No additional sections | ||
| * Ranges "host"? used to give the admin node access to the BMC's | ||
| * Rules - Must be the same subnet as the BMC | ||
| * Admin | ||
| * Used by all each computer to communication with the Crowbar Server and for all Nova work | ||
| * External Access - Not required but helpful | ||
| * router and router_pref are required | ||
| * Ranges - requires "host", "dhcp", "switch", and "admin" | ||
| * Rules - no special rules | ||
|
|
||
| ### Stanza ### | ||
| * conduit - Name of the conduit this network is to use.? | ||
| * When more than one network can uses the same conduit, the interfaces can become dual homed depending on the add_bridge and use_vlan | ||
| * vlan - the Vlan Number assigned to that network.? This comes into play when the use_vlan is set to 'true'. | ||
| * use_vlan - 'true' or 'false' | ||
| * When set to true, the node will be configure to use 802.1q vlan tagging.? A like rule will need to be created on the switch to accept the tagged packet. | ||
| * add_bridge - 'true' or 'false' | ||
| * When set to 'true', the node will bridge the network.? | ||
| * SPECIAL RULE:? When this is true and VM's are being used on the bridge network Team Mode must be set to allow this.? Team mode 6 (Adaptive Load Balancing and team mode 1 (Round Robin) are known to cause failures | ||
| * subnet - this is the actual subnet, for example. 192.168.124.0, 192.168.123.128 | ||
| * netmask - this is the Netmask for the network subnet. Please see Nova-Floating for it special requirements | ||
| * broadcast - network broadcast | ||
| * router - This is the router IP for this particular network | ||
| * router_pref - This is like a route metric the lower number becomes your default route | ||
| * ranges - the different ranges you want to use in general "host" is required. |