Exadata workload extension architecture documentation missing

[hslange]

Although there is a section on deploying Exadata as a workload extsntion (using the template folders elz-exadata-spoke and elz-exadata-workload), documentation on the deployed architecture and dependencies is missing in the documentation section here.
When deploying an exadata workload, it creates a subnet called LB instead of Web (for non-exadata workload). Not sure why this is done this way, but for consistency with the non-Exadata workload I would suggest to name the subnet the same (web) unless it's created for a different purpose. In that case, please document the purpose.