doesn't honour overcloud_computescale or overcloud_controlscale

Bug #1319473 reported by Jon-Paul Sullivan on 2014-05-14
This bug affects 3 people
Affects Status Importance Assigned to Milestone
Jon-Paul Sullivan

Bug Description

The NODE_CNT passed to create-nodes was hardcoded to 15:


Changed in tripleo:
status: New → In Progress
assignee: nobody → Jon-Paul Sullivan (jonpaul-sullivan)
summary: - doesn't honour overcoud_computescale or
+ doesn't honour overcloud_computescale or
Robert Collins (lifeless) wrote :

I'm not sure that it *should* honour them. The problem is that people change their mind about what they want to deploy, and calculating the exact value is a moving target. So before we removed the heuristic, folk had to fiddle a lot, or rebuild their entire demo rig, which is not fun and basically a waste of time. The current situation allows folk to do whatever they want within pretty broad bounds (and if they are on a big server, they can decide how much they want to invest in test VMs easily too).

Changed in tripleo:
status: In Progress → Incomplete
Changed in tripleo:
status: Incomplete → In Progress
Steve Kowalik (stevenk) on 2014-05-29
Changed in tripleo:
importance: Undecided → High
Derek Higgins (derekh) wrote :

looks like the fix assosiated with this has been abandoned, jp do you still consider this relevant?

So apparently this is a feature, so closing.

Changed in tripleo:
status: In Progress → Invalid
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers