[task based] Rework groups by wildcards

Bug #1538961 reported by Bogdan Dobrelya
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Fuel for OpenStack
Confirmed
Wishlist
Fuel Sustaining
Mitaka
Won't Fix
Wishlist
Fuel Library (Deprecated)
Newton
Confirmed
Wishlist
Fuel Sustaining

Bug Description

We shall use this [0] example wildcard pattern every place we're enumerating all of the possible groups. And for plugins, one might exclude any custom roles being brought in by a plugin, if he/she doesn't want them to be wildcarded as well.

This would eliminate great confusion for Fuel / plugins developers, when trying to understand long role lists put in many places.

[0] https://review.openstack.org/#/c/272618/3/deployment/puppet/osnailyfacter/modular/fuel_pkgs/tasks.yaml

Changed in fuel:
importance: Undecided → High
milestone: none → 9.0
importance: High → Medium
tags: added: area-library module-tasks tech-debt
Changed in fuel:
assignee: nobody → Fuel Library Team (fuel-library)
Changed in fuel:
assignee: Fuel Library Team (fuel-library) → Kyrylo Galanov (kgalanov)
Changed in fuel:
status: New → Confirmed
Changed in fuel:
status: Confirmed → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to fuel-library (master)

Fix proposed to branch: master
Review: https://review.openstack.org/273596

Revision history for this message
Bogdan Dobrelya (bogdando) wrote :

Will not be fixed as custom roles from plugins should not be different from other existing roles, hence wildcards can not be used, see http://lists.openstack.org/pipermail/openstack-dev/2016-February/086903.html

Changed in fuel:
status: In Progress → Won't Fix
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Change abandoned on fuel-library (master)

Change abandoned by Kyrylo Galanov (<email address hidden>) on branch: master
Review: https://review.openstack.org/273596

Revision history for this message
Kyrylo Galanov (kgalanov) wrote :

All Fuel-native tasks should be placed under 'core' group. After that these tasks can be specifid in tasks.yaml like:
    groups: ['/core:.*/']

Changed in fuel:
status: Won't Fix → Confirmed
importance: Medium → Wishlist
tags: added: feature
removed: tech-debt
Changed in fuel:
assignee: Kyrylo Galanov (kgalanov) → Fuel Library Team (fuel-library)
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.