Age | Commit message (Collapse) | Author | Files | Lines |
|
Latest 'openstack stack output' commands prints output with
ascii table format, so opnfv-deploy output breaks as following:
"Overcloud dashboard available at http://+---------"
This change fix it with json+jq.
Change-Id: I594f31254caeee1dc2bc3c6d39d9640cba039f05
Signed-off-by: Tomofumi Hayashi <tohayash@redhat.com>
|
|
- Congress is not in THT now so this will not install yet
- Removing doctor driver sideload in build
The doctor driver is upstream in Newton. No need to side load the
driver into the congress codebase anymore.
- moving to upstream puppet module
Change-Id: Ia60d7d33039dddda634cb5485a3c40ce6ec2b261
Signed-off-by: Dan Radez <dradez@redhat.com>
|
|
Also contains various network parsing fixes.
JIRA: APEX-361
Change-Id: I5e40ed67267d5ded85adc2982a8726ebbceaeae5
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
'usable_ip_range' was confusing for a lot of users, and most thought it
encompassed all of the defined ranges in the network settings file (like
floating_ip_range and introspection_range). This renames it to be more
accurate.
JIRA: APEX-288
Change-Id: I2e106666df1bfd007f150279e2e0387a64cd0f48
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
Without specifying the provider network type or physical network results
in the default tenant network type being used upon external network
creation (for us this means vxlan). Previously this worked fine because
Neutron L3 agent and ODL L3 would assume to use br-ex. This is no
longer true in ODL new nettvirt, and needs to be explicitly flat along
with the correct physical network.
Also includes minor fix for Manila service naming that was fixed
upstream.
JIRA: APEX-300
Change-Id: If5d467a811baafe01b725dd530938482fdd3fd03
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
In newton the heat cli is deprecated:
WARNING (shell) "heat stack-list" is deprecated, please use "openstack stack list" instead
WARNING (shell) "heat resource-list" is deprecated, please use "openstack stack resource list" instead
Change-Id: Ia32f05c72500e5fdd525c32a9b41b2be3cb1599c
Signed-off-by: Dan Radez <dradez@redhat.com>
|
|
- proposed in genesis
https://wiki.opnfv.org/display/genesis/Common+Network+Settings
- This patch updates the network_settings files in the config/network dir
and updates the associated bash, python and python tests relative to
the new yaml structure and nomenclature used in the proposed settings
file
JIRA: APEX-262
Change-Id: Ib0dc9d0f21465b38f2a53cff20f71fb9230bfc48
Signed-off-by: Dan Radez <dradez@redhat.com>
|
|
JIRA: APEX-258
Change-Id: Ia055f317147cc63b479cf1dbc1a85f05acc0726a
Signed-off-by: Feng Pan <fpan@redhat.com>
|
|
JIRA: APEX-257
Change-Id: I21913a6e41a2fd1565b1950345d15d0b5d47cb9c
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
There were syntax errors with "auth_url" and an extra double quote.
Also added logging to make it more clear when datasources get created.
JIRA: APEX-245
Change-Id: I554fb8195116dd71f4b34b8ccf6e969d9b2e7224
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
The Congres Nova driver defaults to Nova API v2.0 but also supports
micro versions since Liberty release. This patch creates the Nova
datasource with the latest micro version available. This is useful for
scenarios such as invoking nova.services.force_down that was introduced
in v2.11.
https://bugs.launchpad.net/congress/+bug/1552220
JIRA: APEX-238
Change-Id: I0a60a1199e36da38e48aa647812dd6ee5543ce2b
Signed-off-by: Carlos Goncalves <carlos.goncalves@neclab.eu>
|
|
needed
JIRA: APEX-198
Adds support for baremetal deployments where external connectivity is only
provided via the jumphost. The connectivity test is done by pinging an
external IP (8.8.8.8 by default) for each node. If ping fails for any of
the nodes then NAT is added.
Change-Id: I8d59beb03c3b2998deaec5dc7536fa7a5b1f7718
Signed-off-by: Markus Kullberg <markus.kullberg@nokia.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>
|
|
Run a pcs cleanup before db sync and also at the end of the deployment.
This will give processes a chance to recover in case there has been
any kind of error that would lead to a process being scored -INFINITY
due to repeated failed startup that may have been caused by load during
the deployment, or another latent issue.
Print out any services that are failed in pcs at the end of deployments.
opnfv-tht-pr: 41
Change-Id: Idf4f03cd0463a3facd0726483091ac6f1b3bf000
Signed-off-by: Michael Chapman <michapma@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>
|
|
Previous patch set this to be the public IP of the first controller.
However we only allow ODL to bind to the admin/API IP of the first
controller for security reasons.
JIRA: APEX-152
Change-Id: I22addbb9e7c3fcd850b9695b846357bf9447cd50
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
JIRA: APEX-141
Change-Id: I9983ec5583100b7c536524a01e64bb6884b38d1d
Signed-off-by: Dan Radez <dradez@redhat.com>
|
|
JIRA: APEX-201
Change-Id: I3ba8d5e38e203bb4f23679a3b91de97c591de146
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
JIRA: APEX-152
Change-Id: Id64a42531711c53ad453cd176aab2a9773a71811
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
opnfv-tht-pr: 37
JIRA: APEX-158
Change-Id: I079d22e8ee7798bddf7f2f1b6cc3f1b49f1d5773
Signed-off-by: Dan Radez <dradez@redhat.com>
|
|
Change-Id: I37dd541d3ad413b76d94cbc89ab1b2c8e1a723f1
Signed-off-by: Feng Pan <fpan@redhat.com>
|
|
trying to reduce the monolith deploy.sh to smaller parts
Change-Id: Ie7068473e4ddd8eeca28ebd03de57781222ad761
Signed-off-by: Dan Radez <dradez@redhat.com>
|