Comment 1 for bug 1633090

So I think this is possibly a duplicate of https://bugs.launchpad.net/tripleo/+bug/1625558 ?

Basically in environments/net-single-nic-with-vlans.yaml you have this:

resource_registry:
  OS::TripleO::BlockStorage::Net::SoftwareConfig: ../network/config/single-nic-vlans/cinder-storage.yaml
  OS::TripleO::Compute::Net::SoftwareConfig: ../network/config/single-nic-vlans/compute.yaml
  OS::TripleO::Controller::Net::SoftwareConfig: ../network/config/single-nic-vlans/controller.yaml
  OS::TripleO::ObjectStorage::Net::SoftwareConfig: ../network/config/single-nic-vlans/swift-storage.yaml
  OS::TripleO::CephStorage::Net::SoftwareConfig: ../network/config/single-nic-vlans/ceph-storage.yaml

So when defining a custom role you'll need to pass an environment which references the configuration you want for that role:

resource_registry:
  OS::TripleO::TheCustomRole::Net::SoftwareConfig: path/to/the/config.yaml

The config can be copied from whatever is in use for the other roles (all the templates are basically the same for each role in the tht examples).

If you don't pass any extra environment file, the role will simply get the default noop config:

https://github.com/openstack/tripleo-heat-templates/blob/master/overcloud-resource-registry-puppet.j2.yaml#L35

I think what you're asking for though is for just including -e environments/net-single-nic-with-vlans.yaml to apply that config to all roles automatically?

That is probably possible, but for now copying the file and passing the resource_registry as described above should work fine.