Document propagate_task_deploy setting

Bug #1639393 reported by Andrey Danin
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Fuel for OpenStack
Won't Fix
High
Evgeny Konstantinov
Mitaka
Confirmed
High
Evgeny Konstantinov

Bug Description

This is a bug about Fuel 9.1 documentation.

Some significant changes in task graph processing were done in Nailgun during Fuel 9.1 development. In particular, tasks with version < 2.0.0 aren't allowed to execute by default. If one still wants to use "old" tasks (with version less than 2.0.0) they should enable a special setting called "propagate_task_deploy" on Fuel UI. The problem is that the vast majority of fuel-plugins are using tasks with version < 2.0.0 and all of a sudden they stopped working with 9.1 while working okay with 9.0. Fuel documentation doesn't contain a word about those new features and how to deal with propagate_task_deploy.

I would like to see documented the next things:

- What is the reason for plugins developers to use tasks v2.0.0
- How 'propagate_task_deploy' setting works (who, when, and why should get it enabled)

Changed in fuel:
assignee: nobody → Evgeny Konstantinov (evkonstantinov)
importance: Undecided → High
milestone: none → 9.2
status: New → Confirmed
Roman Vyalov (r0mikiam)
Changed in fuel:
status: Confirmed → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.