Make network configuration idempotent
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Fuel for OpenStack |
Won't Fix
|
Medium
|
Fuel Documentation Team | ||
Mitaka |
Confirmed
|
Medium
|
Fuel Documentation Team |
Bug Description
https:/
Dear bug triager. This bug was created since a commit was marked with DOCIMPACT.
commit 8d06d9b28fc868a
Author: Aleksandr Didenko <email address hidden>
Date: Mon May 30 16:34:35 2016 +0200
Make network configuration idempotent
Remove configure_
idempotent for majority of roles. 'Netconfig' task on all
non-controller (except mongo) nodes will be executed after 'virtual_ips'
task on controllers. So there's no need to reconfigure default route
afterwards.
Only mongo roles still have non-idempotent network configuration during
the first deployment run, because mongo nodes are deployed before
controllers in role-based deployment and no VIPs are configured yet.
Also, instead of having one default gateway in Hiera and then replacing
it with another one on the fly, let's create a new task that will simply
put new gateway to Hiera and thus we'll have consistant configuration
data for future runs of 'netconfig' task even on mongo roles.
DocImpact
Change-Id: I7269a6f632f9ab
Closes-bug: #1541309
tags: | added: area-docs |
Changed in fuel: | |
milestone: | none → 9.0 |
assignee: | nobody → Fuel Documentation Team (fuel-docs) |
importance: | Undecided → High |
status: | New → Confirmed |
importance: | High → Medium |
Changed in fuel: | |
status: | Confirmed → Won't Fix |