This is probably better. we've run into problems with profile/role pattern where this needs to be explicit:

```
class profile::rabbitmq {
  include '::rabbitmq' # not 'rabbitmq'
}
```

So I think '::erlang' would avoid some potential problem later.