2048 is the acceptable value where default Virtual deployments will
still work.  A user can then modify deploy_settings in order to increase
number of huge pages to something other than the default.

JIRA: APEX-184

Change-Id: I7962c8e1ae09df60c51375b4ed343b44bce52b59
Signed-off-by: Tim Rozet <trozet@redhat.com>

Changes include:
 - starting vpp with pci addr of tenant nic
 - setting performance options for fdio scenario
 - creates nosdn fdio scenario (needs newtorking-vpp, etc)
 - starts HC if ODL is used

opnfv-tht-pr: 46

JIRA: APEX-133

Change-Id: Ie7a7f1418b94dfb82255ec9aebc550a955dd696a
Signed-off-by: Tim Rozet <trozet@redhat.com>

This patch contains the following:
- Add dns and nic information in network settings file
- Add ipv6 option for find_ip function in common-functions.sh
- Change neutron commands to handle IPv6 during post deploy,
  skip NAT configuration if IPv6 is configured.
- Fix an error in python library when generating floating ip
  range.

JIRA: APEX-130

Change-Id: I27da7f7a714f42ee827be7091fcb1a6d89a0aae8
Signed-off-by: Feng Pan <fpan@redhat.com>

opnfv-tht-pr: 48

JIRA: APEX-206

Change-Id: Icfb5356252f4e862f8a9cd4fd1914951ab45baf4
Signed-off-by: Tim Rozet <trozet@redhat.com>

opnfv-tht-pr: 34
opnfv-puppet-tripleo-pr: 4

JIRA: APEX-126

Change-Id: I050e7ae2e94779c1886f670841aa4e2dec4aa8d2
Signed-off-by: Dan Radez <dradez@redhat.com>

We had a regression where we missed adding bgpvpn code back into master.

opnfv-tht-pr: 45

JIRA: APEX-200

Change-Id: I44da1d653e13c48f276ad29daac1eb6f4f2d629b
Signed-off-by: Tim Rozet <trozet@redhat.com>

Can be set by setting domain_name in network_settings.  Defaults to
dummy opnfvapex.com.

JIRA: APEX-183
JIRA: APEX-182

Change-Id: Ib7c279a1c8432b8635f72e5cc667f16b9cd65159
Signed-off-by: Tim Rozet <trozet@redhat.com>

Currently there is no way to specify logically or physically the nic
order to be used on overcloud nodes.  We always hardcode to use nic1 for
admin network, nic2 for private, etc.  This patch allows a user to not
only decide which logical nics to use for which network, but also
specify physical interface names if they need to.

This is done on a per role basis, due to tripleO limitation.  So a user
is able to specify nic order/names for compute and controller roles
separately.

If a user specifies nic order, they must specify it for all networks
other than admin network.  We assume if admin network is unspecified it
uses "nic1", so that name is reserved in this case.  A user is also
allowed to specify a mixture of logical and physical names, for example
"nic2" and "eth3" on another network.

JIRA: APEX-151

Change-Id: Ie9d4abb463cf8f8788913cb4bcf9486830adc449
Signed-off-by: Tim Rozet <trozet@redhat.com>

JIRA: APEX-141

Change-Id: I9983ec5583100b7c536524a01e64bb6884b38d1d
Signed-off-by: Dan Radez <dradez@redhat.com>

add os-onos-sfc-ha.yaml for onos sfc function deployment.

opnfv-tht-pr: 27

JIRA: APEX-172

Change-Id: I07d708d201ef1d97efbfffd5aca85d8a284f7c96
Signed-off-by: bob zhou <bob.zh@huawei.com>

SFC for colorado will be based on OVS 2.5.90 which does not need 3.13
kernel.  This patch removes 3.13 kernel updates, adds OVS 2.5.90 and
sets default odl_version to use boron (required for SFC with OVS
2.5.90).  Also updates OVS build to a working one for ONOS.

JIRA: APEX-156
JIRA: APEX-199

Change-Id: I095290d925138122f24e891f8412497f9a2c3141
Signed-off-by: Tim Rozet <trozet@redhat.com>

JIRA: APEX-136
JIRA: APEX-30

Change-Id: I7cbbe11f4c1f1455dba253733c78fe8dc215de97
Signed-off-by: Dan Radez <dradez@redhat.com>

JIRA: APEX-133

opnfv-tht-pr: 29

Change-Id: I3080c91c3995ed946b902a75907ef11cb349fc33
Signed-off-by: Tim Rozet <trozet@redhat.com>

JIRA: APEX-130

Change-Id: Ic00c36b84de274b43c2555108d78aef307a85499
Signed-off-by: Feng Pan <fpan@redhat.com>

Changes include:
 - Minor syntax fix to dataplane check
 - Adds 'odl_version' to deploy options
 - Builds ODL overcloud image with boron rpm included
 - If user specifies 'boron' as odl_version then, package is upgraded on
   overcloud image

Change-Id: I37436cb8cc4d6cff1fede6c13836f26a4cc57f49
Signed-off-by: Tim Rozet <trozet@redhat.com>

Adds the dataplane deploy option, which can have values of
ovs, ovs_dpdk, or fdio. Currently does nothing

JIRA: APEX-119

Change-Id: I6c14a9c9d6887a325525d634052ea8300b30ee57
Signed-off-by: Michael Chapman <woppin@gmail.com>

Change-Id: Ibb30129ca52392cd152b6af61e0545ba47153bda
Signed-off-by: Dan Radez <dradez@redhat.com>

Add support for CPU pinning of libvirt guests and also
restricting host processes to selected CPUs via isolcpus.

Hugepage support is added using the same mechanism as
isolcpus, along with a perf scenario where all 3 performance
options are enabled.

Deploy options are now parsed in python

JIRA: APEX-127
JIRA: APEX-105
JIRA: APEX-106

Change-Id: I438e80fb88e596cc017595d43bc1efda1001325c
opnfv-tht-pr: 8
Signed-off-by: Michael Chapman <woppin@gmail.com>

Change-Id: I9a151a251811fa3460616fc93beee6b9b342b8b8
Signed-off-by: Tim Rozet <trozet@redhat.com>

Change-Id: I724023f9d45b306dd6bf9768a9546481358fdeb9
Signed-off-by: vitikkan <viktor.tikkanen@nokia.com>

- replacing brbm with logical names br-netname
- replacing instack-virt-setup with tripleo scripts

JIRA: APEX-90, APEX-80

Change-Id: I58a15dee8de882e034c8af8a3368ca0647741b13
Signed-off-by: Dan Radez <dradez@redhat.com>

Change-Id: Id2d6d46a53129d4ae2f93fad835536da067e42df
JIRA: APEX-51
Signed-off-by: Dan Radez <dradez@redhat.com>

JIRA: APEX-95

pm_type is already in the sample instackenv.json but wasn't previously
being read.

Change-Id: Ia82c5010481d77d142d4fa3ca6e738558e8e9e4e

Change-Id: Ief5c4cc08d1fc20ac6077f8edf7885f5c4bcf141
Signed-off-by: Viktor Tikkanen <viktor.tikkanen@nokia.com>

Fixes include:
 - sfc deployments now are non-HA, and disable swift and ringbuilder as
it causes issues with the 3.13 kernel
 - ODL Features boot is now parameterized in heat templates
 - SFC features boot is now set to "odl-ovsdb-sfc-rest"
 - Coexistence table offsets included if SFC deployment
 - VXLAN workaround applied for 123.123.123.x subnet if SFC

Change-Id: Ide5e0b451adcb98c417e57628a51302f3123647f
Signed-off-by: Tim Rozet <trozet@redhat.com>

Changes Include:
 - Disables introspection.  We don't currently use introspection for
anything other than to just run it.  Disabling it to increase deploy
speed and reduce pxeboot issues.
 - Adds timeout to deploy of 90 minutes.  Default heat timeout is 3-4
hours.
 - Fixes OVS bridge attach/detach for users who use PREFIX in their
ifcfg instead of NETMASK
 - Adds nosdn deploy settings file, and allows nosdn deployments
 - Adds example inventory file to the docs dir

Change-Id: Ic13d6c4d5f27bac25365e5951acdd9bd3e641a15
Signed-off-by: Tim Rozet <trozet@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>

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>