Hi Vladimir, Thanks for sharing.
Are the kvm traffic labels of the physical networks the same ? -Wei On Mon, 3 Apr 2023 at 11:40, Vladimir Dombrovski <[email protected]> wrote: > Hello Lewis, > > We've managed to do this, here's how: > > - create a new Physical network inside the zone with VLAN isolation > - tag your primary PN and this PN with different tags (e.g. vxlan and vlan) > - tag all your network offerings with their corresponding tags (most > should be vxlan to allow these offerings to use your primary PN) > - create a new shared offering without any services tagged with your vlan > tag > - use the offering to create a shared guest network on the specific > VLAN required by your customers > - add this network to any VMs of the same Domain/Account/Project > - configure this second network interface from within the VM > > What should effectively happen is that ACS will assign your VLAN > directly to your (tagged) physical interface by creating a bridge in > the VLAN specified when creating the shared offering, then attach the > VM interface (here vnetXYZ) to that bridge, example: > > bond0.2500@bond0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 9000 qdisc > noqueue master brbond0-2500 state UP group default qlen 1000 > brbond0-2500: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 9000 qdisc noqueue > state UP group default qlen 1000 > vnet26: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 9000 qdisc htb master > brbond0-2500 state UNKNOWN group default qlen 1000 > > Regards, > > Vladimir DOMBROVSKI > > > On Mon, 3 Apr 2023 at 11:02, Lewis Di Ciacca > <[email protected]> wrote: > > > > We currently have 2 clusters setup with VXLAN isolation. This is working > well at the minute. > > > > > > > > We have however encountered the need for a few customers to > communication Via L2/VLAN with the physical switches. > > > > > > > > I have looked a few different way most of them is Fudging the backend. > It seems as we have Guest isolation set to VXLAN that all it will use even > when creating an L2 offering with VLAN enabled. > > > > > > > > I have done some digging in the database. When using VXLAN the > VXLANGuestNetworkGuru is used I also cant just change this to > GuestNetworkGuru assuming when specify VXLAN on the zone it disables the > ability to use this. > > > > > > > > What is the best way of getting this to work? > > > > Lewis Di Ciacca > > Senior Technical Consultant > > T: +44 161 537 4990 > > M: 07891 141025 > > E: vms@quadris‑support.com > > W: www.quadris.co.uk > > The information contained in this e-mail from Quadris may be > confidential and privileged for the private use of the named recipient. > The contents of this e-mail may not necessarily represent the official > views of Quadris. If you have received this information in error you must > not copy, distribute or take any action or reliance on its contents. > Please destroy any hard copies and delete this message. > > -- > *CONFIDENTIALITY AND DISCLAIMER NOTICE: * > This email is intended only for > the person to whom it is addressed and/or otherwise authorized personnel. > The information contained herein and attached is confidential. If you are > not the intended recipient, please be advised that viewing this message > and > any attachments, as well as copying, forwarding, printing, and > disseminating any information related to this email is prohibited, and > that > you should not take any action based on the content of this email and/or > its attachments. If you received this message in error, please contact the > sender and destroy all copies of this email and any attachment. Please > note > that the views and opinions expressed herein are solely those of the > author > and do not necessarily reflect those of the company. While antivirus > protection tools have been employed, you should check this email and > attachments for the presence of viruses. No warranties or assurances are > made in relation to the safety and content of this email and attachments. > The Company accepts no liability for any damage caused by any virus > transmitted by or contained in this email and attachments. No liability is > accepted for any consequences arising from this email. > > > *AVIS DE > CONFIDENTIALITÉ ET DE NON RESPONSABILITE* : > Ce courriel, ainsi que toute > pièce jointe, est confidentiel et peut être protégé par le secret > professionnel. Si vous n’en êtes pas le destinataire visé, veuillez en > aviser l’expéditeur immédiatement et le supprimer. Vous ne devez pas le > copier, ni l’utiliser à quelque fin que ce soit, ni divulguer son contenu > à > qui que ce soit. BSO se réserve le droit de contrôler toute transmission > qui passe par son réseau. Veuillez noter que les opinions exprimées dans > cet e-mail sont uniquement celles de l'auteur et ne reflètent pas > nécessairement celles de la société. Bien que des outils de protection > antivirus aient été utilisés, vous devez vérifier cet e-mail et les pièces > jointes pour toute présence de virus. Aucune garantie ou assurance n'est > donnée concernant la sécurité et le contenu de cet e-mail et de ses pièces > jointes. La Société décline toute responsabilité pour tout dommage causé > par tout virus transmis par ou contenu dans cet e-mail et ses pièces > jointes. Aucune responsabilité n'est acceptée pour les conséquences > découlant de cet e-mail. >
