Age | Commit message (Collapse) | Author | Files | Lines |
|
We should only bridge to admin/public for baremetal deployments. There
is no reason for us to bridge to the private or storage networks on
instack for deployment.
Also fixes OpenDaylight to Lithium 3.3
Change-Id: I2eb8f83ddbcb69d3219e7927025b46dcb9550ba9
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
- adding a missing exit 1 in the deploy script
- setting link up on hypervisor bridges
- redirecting error from cleanup commands so they're not so chatty
Change-Id: I844c35effb2817948ea096b07a34d83678803e00
|
|
|
|
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>
|
|
Neutron external net should be creatd on overcloud
Change-Id: I2c845e9af40d5dbe0106e542e24b9ef1b6169e31
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
Changes include:
- Neutron external network now configured post deployment
- IP addresses assigned to admin and public OVS bridges if missing
Change-Id: I7a3e8822b43640578db809c3f4d55f399383c1f1
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
|
|
Change-Id: I2dc1bf7ffebb6a83face87a62a81cfb15f9a0689
|
|
Change-Id: I482e84bbe3f21f425e6bce74fdfa16f71bf12654
|
|
Tested manually and verified on LF pod1
Change-Id: I882ad9beef003a795585ffb8542aa11aecb67949
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
|
|
This applies only to baremetal deployments. Interfaces from admin and
public networks are attached from the host to the OVS bridges brbm and
brbm2 for external connectivity.
Change-Id: If3f5b33eab267e05ee9094396daa40f37e69319a
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
Changes include:
- ONOS artifacts are cached on build server until moved to OPNFV artifacts
- tht patch is now unified to single opnfv patch, based on upstream
commit 0f41e0d0309c7bc061dbaed6a8c1e38cb4bdfe19
Change-Id: Iea3d14773dded6c9709c08ef1beb47b254582860
Signed-off-by: bob zhou <bob.zh@huawei.com>
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
Change-Id: Ib8a3baa645c4e2a2b7b5c39e8642bae367981f37
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
Change-Id: I4e16b4a4432c935715f0522956614c891a695f70
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>
|
|
|
|
Testing if this fixes current CI breakage
Change-Id: Ib4f75a9a1772c5363afab6d24b7a254f8cf6f6f8
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
unnessesary"
|
|
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>
|
|
Change-Id: I4a585a5e72872fa1887aa4487ebd7b17d07feacc
|
|
- enabling subnet configuration for undercloud
- enabling external network configuration
Change-Id: Id1951d31faa1a68f850a75e2466d30b8abcea8ac
|
|
|
|
Fixes Include:
- Fixed info print statement when using flat network
- deploy now looks at arp table as well to determine instack IP address
as default leases file may not exist
- clean now uses --pool with vol-delete command
JIRA: APEX-50
Change-Id: I664fd06e92e0890e0b65191851dfa81f8d8ac492
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
Change-Id: I6e3a4266be28b0f661e4b8e818c616000060905b
|
|
- using the proposed patched for upstream
- ensuring l3_ha is disabled
- exposing support for an ODL only node
Change-Id: I6f4a50300ea08322eea4ba466fc1a3b0fbcb5743
Signed-off-by: Dan Radez <dradez@redhat.com>
|
|
Change-Id: I3ff4b0e9aecff8fc193017d0dc4cd3c4c1a6339c
Signed-off-by: Dan Radez <dradez@redhat.com>
|
|
Change-Id: I9f09c195352d2d88a3da4f42e09424d96d39722b
|
|
|
|
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>
|
|
Change-Id: I41881c914494e329570c76fba9f4e0f1dce50e50
|
|
|
|
Change-Id: I1af7ffdb1d1e4b96b31b44f2750de23b55d9d540
|
|
Change-Id: I12cbb68df993e27f9ff3c41185c4682a64349736
|
|
- make sure we connect to Instack
- enable the ping site to be configurable
- put ntp server in a variable so it can be made configurable later
Change-Id: I2ec30f6bab0b48ec878bd25790145f7fff00964a
|
|
JIRA: APEX-35
Change-Id: Iebbf85bd59844716961c27bb81ff7bbda2d1a1bf
|
|
- virtual deploys still expect to pull pre-canned files
from $CONFIG dir
- non-virtual deploys now expect an instackenv.json
and network-environment.yaml file in pwd on deploy
JIRA: APEX-41
JIRA: APEX-49
Change-Id: Ib61ac7448917ec1ea728c23cb3406feab9058f77
|
|
Change-Id: I2a506f95036b897309dbaf9120426bdf3f4a6337
|
|
- adding vol-delete to help ensure volumes are cleaned up
- adding brbm clean up
Change-Id: I3cbb79b09c6ac77dbc3c452938dbd6a6d03c815b
|
|
- separating external traffic from internal traffic
JIRA: APEX-41
Change-Id: Idcd01a514083c53a3133a75d3bcabf824a7a4377
|
|
|
|
Change-Id: I6a0a63f04c0693b9dd2f4a137475ef00c2377455
|
|
The instackenv has 5 nodes in it but we were only putting two
back into the pool. This patch puts all 5 back in the pool
but doesn't throw the ha flags
JIRA: APEX-45
Change-Id: I1c539eafca9ed2f674a1a954f75c175fe9efc5bb
|
|
|
|
Change-Id: I4e18bc0ddfb39a11c75070012743e6a68ecb70f6
|
|
- replacing the echo | cut with bash string slicing
- replacing underscores with dashes in long args
- adding no-ha to the usage display
Change-Id: Ie87709c60a485bbcd97f168207e03d43bd85f24a
|
|
Change-Id: Iaaf5cbc790abd3b7af6f94b4e6d7e8ecfbbc6534
|
|
|
|
Change-Id: I6446058a5ab1dd37659e553ad41d9fd9b0f9bd25
|
|
- updating end user output
- adding option to ssh to supress excessive warnings
Change-Id: Ibe44b4a580bcb1e60899b8f8aca8cbadc8e447a9
|