In your case you would create a service profile template, a vNIC template for A and B side, and vHBA template for A and B side.
When you create the service profile template (we will name it "ESXi"), you would reference the vNIC and vHBA templates. These templates contain properties like VLAN, VSAN, etc. You also select other values in the template that you want to be the same across all blades, such as boot order, BIOS policy, firmware package.
Once the template is complete, you would create 8 service profiles from that template and assign them to each blade. For Example ESXi-1, ESXi-2. Now if you created an initial template, you can make individual changes to the service profiles without impacting other servers. Lets say one day you decide that blade 8 is going to boot from flexflash instead of local disk. You would just create a new boot policy and apply it to ESXi-8.
If you used an updating template, all changes made will reflect on all service profiles spawned from that template. This is the same for vNIC templates as well. So lets say you needed to add a new vNIC and apply a new VLAN globally to all existing vNIC on those 8 blades. You would just add a new vNIC to the template and add the new VLAN to the vNIC template, and these changes are pushed to all 8 blades at once.
I hope this helps.
