There yet is the place in Nailgun code where name of default group still matters [1]. There won't be any failure but logic of validation will process node group 'Default' in slightly different manner - particularly as if the name is not present in template ( in such case data from 'default' section will be used). IMO this will be a point of confusing for user who wants to utilize templates. Also, name of a group is nothing special but simply a piece of data so I don't see why 'default' is more logically different or uglier than 'Default'. In any case user may always change the name for what is more suitable on his/her opinion. In addition why this has 'high' importance in the first place? Lets not exploit possibility to manipulate statuses as it has different purpose.
There yet is the place in Nailgun code where name of default group still matters [1]. There won't be any failure but logic of validation will process node group 'Default' in slightly different manner - particularly as if the name is not present in template ( in such case data from 'default' section will be used). IMO this will be a point of confusing for user who wants to utilize templates. Also, name of a group is nothing special but simply a piece of data so I don't see why 'default' is more logically different or uglier than 'Default'. In any case user may always change the name for what is more suitable on his/her opinion. In addition why this has 'high' importance in the first place? Lets not exploit possibility to manipulate statuses as it has different purpose.
[1]: https:/ /github. com/openstack/ fuel-web/ blob/master/ nailgun/ nailgun/ task/task. py#l1429- l1433