| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
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>
|
|
Changes include:
- Scenarios for opencontrail, onos, sfc, odl l2/l3
- Minor fix to error print statement
- Post Config is now disabled when using --flat
Change-Id: I5f3686dda4c4a573b1777916669053593852676a
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>
|
|
If there are dedicated HW nodes for controller and compute nodes,
it should be possible to define node roles in configuration files.
This patch introduces "capabilities" property into
pod_example_settings.yaml so as adds needed flavor definitions
and overcloud deploy parameters into opnfv-deploy script.
Change-Id: Ie62d3fa215aa168390d074c73fdb2fa03ecc67f5
Signed-off-by: Viktor Tikkanen <viktor.tikkanen@nokia.com>
|
|
- enabling subnet configuration for undercloud
- enabling external network configuration
Change-Id: Id1951d31faa1a68f850a75e2466d30b8abcea8ac
|
|
This patch allows deploy_settings.yaml and inventory settings to be
passed in via cmdline. The deploy settings are overridden by cmdline
arguments. For example, if a user specifies no_ha in cmdline it will
override what is in deploy_settings.yaml. The inventory file provides
yaml input for the baremetal topology.
Fixes include:
- New arguments for passing inventory and deploy_settings
- "global_params" in deploy_settings are set as globals in script
(unless already set via cmdline)
- "deploy_options" are loaded into an array, and checked for deployment
options (such as which SDN controller to use)
- inventory file is parsed (for baremetal) into correct instack json
output. The output is then written to a temp instackjson file and used
for deployment.
- renaming of copy_materials to copy_materials_to_instack
- spelling fixes
- cmdline argument checking with errors and warnings
Note this patch does not yet tamper with setting network-environment
settings.
JIRA: APEX-53
Change-Id: I9dce197e23563480c584650ba967898312eab4e7
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
yaml inputs are broken up into:
-build settings
-deploy options
-network definition
-pod baremetal information
JIRA: APEX-53
Change-Id: Iee85b17beb37ce82bf9312dcce61e09ae924dfc5
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
Tim Rozet
Viktor Tikkanen
Dan Radez