Allow user to disable VIP ping resource
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Fuel for OpenStack |
Triaged
|
Medium
|
Fuel Documentation Team |
Bug Description
https:/
commit c37df6f80484dd1
Author: Vladimir Kuklin <email address hidden>
Date: Tue Dec 2 20:20:26 2014 +0300
Allow user to disable VIP ping resource
Allow user to disable VIP ping resource
if user does not need public network
to be routable.
Since 5.1.1 and 6.0 releases FUEL configures ping resource that checks whether default gateway is accessible in order to fix the corresponding bug:
https:/
Nevertheless, this fix imposes the issue that if user does not have pingable default gateway, deployment of OpenStack cluster will fail as FUEL uses public VIP to configure some of OpenStack entities (e.g. floating ip pools). In order to work this around, user can specify any pingable host as a default gateway, e.g. FUEL master node or apply the patch above and change cluster attribute 'run_ping_checker' to 'false' that will disable the pinger resource. In order to do this user will need to use FUEL CLI and add this parameter manually to the deployment cluster attributes.
Also, be aware that disabling of pinger will introduce back the corresponding bug https:/
DocImpact
Change-Id: I9e1f29b5ee08ec
Related-bug: #1396126
Changed in fuel: | |
assignee: | nobody → Fuel Documentation Team (fuel-docs) |
importance: | Undecided → Medium |
milestone: | none → 6.0 |
Changed in fuel: | |
status: | New → Triaged |
Changed in fuel: | |
importance: | Medium → High |
tags: |
added: docs release-notes removed: fuel-library |
Changed in fuel: | |
importance: | High → Medium |