drwxr-xr-x 7 tailf tailf 4096 May 29 07:21 mpls-vpn
drwxr-xr-x 3 tailf tailf 4096 May 29 07:04 mpls-vpn-react
drwxr-xr-x 8 tailf tailf 4096 May 29 07:21 simple-mpls-vpn
drwxr-xr-x 8 tailf tailf 4096 May 29 07:21 virtual-mpls-vpn
Some of the configs can be very customer specific. I’ve got one for a PoC we did for a customer and I’m sure you will find similar models from others.
Best to look at the template/process/script that the customer is currently using and use that as your starting point. You could add NSO in that environment, do a sync-from and then dump the configs as XML. That may save you some time.
I think not prescribing how a service should look like in NSO, even for something as classic as l3vpn, is intentional.