Age | Commit message (Collapse) | Author | Files | Lines |
|
JIRA: APEX-136
Change-Id: I3fd12054e14dddadee412845d79325c6556ea9de
Signed-off-by: Dan Radez <dradez@redhat.com>
|
|
ONOS needs the capability to have br-ex on compute nodes with no IP for
L3 functionality to work correctly on baremetal. This patch allows that
capability, and makes it default behavior (sdn_l3 true). If desired, a
user can set sdn_l3 to false, and compute nodes public interface will be
a regular interface with no IP for ONOS deployments.
JIRA: APEX-64
Change-Id: I578b946edbddf7fc9c29363c78fec2c3ada48cf6
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
ONOS public network needs to not have IPs on the compute nodes' public
interface.
JIRA: APEX-64
Change-Id: I0d4d97b1b7dcaa39395940da03ae6b19f1dd9eb0
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
Adds support for ODL L3 which uses DVR (distributed virtual routing).
Due to DVR compute nodes must have br-ex. In addition, neutron must
force metadata via dhcp agent, since there is no neutron L3 agent
running. ODL L3 runs as custom plugin to neutron.
Also adds support for configuring IP on public NIC now by default. This
is needed for ONOS deployment, and access via public interface.
Change-Id: I5df0e49bd903efacf8c87486da27576b01ce5779
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
Fixes issues with common-functions:
- ipcalc in epel is old and does not support HOSTMIN,HOSTMAX. Now
BROADCAST and NETWORK values used to find first and last IP in
subnet.
- fixes to auto-generation where values conflicted for IP ranges
- provisioner_ip now generated correctly
Change-Id: I03c7f841d2e1edb1a50041f53970318b6a718cd9
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
Changes include:
- Fixes Intel Pod 2 inventory file
- Check for DHCP server on the host and disable
- Adds realistic+common network-settings file
- Modifies baremetal deployments to bridge to correct interface
- Adds private/storage network OVS bridges
- Parses network-settings into valid network-environment variables
- If certain network-settings are missing they will be auto-detected
Note: The actual settings set forth for deployment only include
admin/external networks at the moment. Private/storage networks will be
handled in an upcoming patch.
JIRA: APEX-50
Change-Id: I0a1a86f37c08702a93fe167688c3149ba5573db4
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
- separating external traffic from internal traffic
JIRA: APEX-41
Change-Id: Idcd01a514083c53a3133a75d3bcabf824a7a4377
|