Role base-os(operation system): The role allows user to get Operating System
without additional configuration and packages.
So, fuel must allow install base os + other any role on one node without any conflict.
# fuel --fuel-version
api: '1.0'
astute_sha: 7e6e6f9188bd69c603853b10d4a55149363323cc
auth_required: true
build_id: 2015-02-07_22-55-01
build_number: '105'
feature_groups:
- mirantis
fuellib_sha: 769af7fe30225cd15638ea2e6dffaa286bc06da1
fuelmain_sha: ''
nailgun_sha: 6d1769b21819f8fb4195f1bd9c44c038721ae3d4
ostf_sha: 6c046b69d29021524906109f18092363505ee222
production: docker
python-fuelclient_sha: 521c2491f7f04f31d8c85db68499cd193d4904e3
release: '6.1'
release_versions:
2014.2-6.1:
VERSION:
api: '1.0'
astute_sha: 7e6e6f9188bd69c603853b10d4a55149363323cc
build_id: 2015-02-07_22-55-01
build_number: '105'
feature_groups:
- mirantis
fuellib_sha: 769af7fe30225cd15638ea2e6dffaa286bc06da1
fuelmain_sha: ''
nailgun_sha: 6d1769b21819f8fb4195f1bd9c44c038721ae3d4
ostf_sha: 6c046b69d29021524906109f18092363505ee222
production: docker
python-fuelclient_sha: 521c2491f7f04f31d8c85db68499cd193d4904e3
release: '6.1'
In my opinion we should not prohibit this.
First of all this fact doesnt lead to any errors.
Second - it is quite flexible mechanism to control additional tasks for plugin developer