Hi Cloudstack users, We are trying to roll out cloudstack 4.2.1 with xen hypervisor 6.2 on dell blades, the hypervisor vlan is native on the switches so no tagging is needed there but the storage is on a different one we configure the hypervisor connect that to cloudstack but when the management server is trying to fired up the secondary storage vm it fails in mounting the secondary storage on the xen hypervisor we are only configuring the bond interface active passive and the management network, we shouldn't need to configure the vlan tagging for the storage is it ? that should be done by cloudstack itself isn't ?
Also primary storage and secondary storage are presented through the same ip address could this cause any issues ? And finally hypervisor layer should or shouldn't be able to contact storage layer ? I read somewhere that they shouldn't communicate. BTW we had a taste ot the new cloudstack with new features of xen 6.2 it rocks Great job Cheers
