You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If you create a new proposal there are some nodes preassigned to the roles. As
this choice rarely fits the desired setup it isn't very useful.
For Example: If you have 10 or more nodes in your environment it is a little
bit annoying if you have to remove every single node from the swift-storage
role, as every system got preassigned.
The text was updated successfully, but these errors were encountered:
I'm not 100% sure but I think this behaviour (whether or not to pre-assign) should probably be determined per barclamp. For example it doesn't make sense to pre-assign for the nova/swift/ceph barclamps where each node in the proposal has specific dependencies. But there may be barclamps where it really doesn't matter which node(s) get assigned.
If you create a new proposal there are some nodes preassigned to the roles. As
this choice rarely fits the desired setup it isn't very useful.
For Example: If you have 10 or more nodes in your environment it is a little
bit annoying if you have to remove every single node from the swift-storage
role, as every system got preassigned.
The text was updated successfully, but these errors were encountered: