Re: Usage of "Tags" for Network Offerings
your are welcome :) On Tue, 8 Jun 2021 at 15:26, vas...@gmx.de wrote: > Hi Andrija, > > thanks alot - again! Good to have your knowledge around :-) > Sorry for spamming - wasn't intended the hassle of doing things > "beside" actual work > > Regards > Chris > > Am Di., 8. Juni 2021 um 10:59 Uhr schrieb Andrija Panic > : > > > > Crhistopher Brown or vas...@gmx.de - please do not "spam" from > different email addresses - that will not get you the answer sooner than > normal - but just creates spam and people are more likely to ignore such > emails :) > > > > Best, > > > > On Tue, 8 Jun 2021 at 10:55, Andrija Panic > wrote: > >> > >> you are almost right - but leave alone "traffic labels" which should be > == to the name of your network/bridge/vSwitch - that has nothing to do with > network TAGs. > >> > >> On physical network, you can set "tag" - you also set the same tag on a > specific network offering - then ACS will say "let me created a network > from this offering based on tags - and find a physical network that has the > same TAG as the TAG defined on the network offering" > >> > >> This used in cases when you have "guest" traffic on more than one > Physical network (i.e. in KVM world, you might be using VXLAN as the > isolation method on Physical Network1, but you also want to use e.g. > Private Gateway which supports only VLAN (not VXLAN) as the isolation > method - thus you would need to create another/2nd Physical network and > give it appropriate tags. > >> > >> Keep in mind the general tagging requirements - you you do NOT tag you > (e.g. other) network offerings, but you do tag Physical networks - this is > the same as if the Physical networks are NOT tagged - i.e. the network will > can be created on either 1st or 2nd Physical networks, since offering is > not requiring any TAG on it's own. > >> > >> Best, > >> > >> On Tue, 8 Jun 2021 at 08:44, Christopher Brown < > mail2christopher.br...@gmail.com> wrote: > >>> > >>> Hi everyone, > >>> > >>> just a short question regarding the creation / usage of network > offerings. > >>> When adding a network offering there is the optional field to give the > >>> network offering a "Tag". > >>> After reading the docs, the acutal usage is to map the offering to a > >>> specific physical network. > >>> > >>> So the tag would need to be same as the traffic label for the physical > network? > >>> > >>> For example i would like to use a dedicated fiber-network for some > >>> hosts. So during the zone creation i would specify a "second" physical > >>> network for Guest-Traffic with the traffic label "fiber". > >>> After creation of the zone, i would add a new network offering and > >>> specify "fiber" as a tag for the service offering to make this > >>> dedicated physical network availeable for hosts ? > >>> > >>> With regards, > >>> > >>> Chris > >> > >> > >> > >> -- > >> > >> Andrija Panić > > > > > > > > -- > > > > Andrija Panić > -- Andrija Panić
Re: Usage of "Tags" for Network Offerings
Hi Andrija, thanks alot - again! Good to have your knowledge around :-) Sorry for spamming - wasn't intended the hassle of doing things "beside" actual work Regards Chris Am Di., 8. Juni 2021 um 10:59 Uhr schrieb Andrija Panic : > > Crhistopher Brown or vas...@gmx.de - please do not "spam" from different > email addresses - that will not get you the answer sooner than normal - but > just creates spam and people are more likely to ignore such emails :) > > Best, > > On Tue, 8 Jun 2021 at 10:55, Andrija Panic wrote: >> >> you are almost right - but leave alone "traffic labels" which should be == >> to the name of your network/bridge/vSwitch - that has nothing to do with >> network TAGs. >> >> On physical network, you can set "tag" - you also set the same tag on a >> specific network offering - then ACS will say "let me created a network from >> this offering based on tags - and find a physical network that has the same >> TAG as the TAG defined on the network offering" >> >> This used in cases when you have "guest" traffic on more than one Physical >> network (i.e. in KVM world, you might be using VXLAN as the isolation method >> on Physical Network1, but you also want to use e.g. Private Gateway which >> supports only VLAN (not VXLAN) as the isolation method - thus you would need >> to create another/2nd Physical network and give it appropriate tags. >> >> Keep in mind the general tagging requirements - you you do NOT tag you (e.g. >> other) network offerings, but you do tag Physical networks - this is the >> same as if the Physical networks are NOT tagged - i.e. the network will can >> be created on either 1st or 2nd Physical networks, since offering is not >> requiring any TAG on it's own. >> >> Best, >> >> On Tue, 8 Jun 2021 at 08:44, Christopher Brown >> wrote: >>> >>> Hi everyone, >>> >>> just a short question regarding the creation / usage of network offerings. >>> When adding a network offering there is the optional field to give the >>> network offering a "Tag". >>> After reading the docs, the acutal usage is to map the offering to a >>> specific physical network. >>> >>> So the tag would need to be same as the traffic label for the physical >>> network? >>> >>> For example i would like to use a dedicated fiber-network for some >>> hosts. So during the zone creation i would specify a "second" physical >>> network for Guest-Traffic with the traffic label "fiber". >>> After creation of the zone, i would add a new network offering and >>> specify "fiber" as a tag for the service offering to make this >>> dedicated physical network availeable for hosts ? >>> >>> With regards, >>> >>> Chris >> >> >> >> -- >> >> Andrija Panić > > > > -- > > Andrija Panić
Re: Usage of "Tags" for Network Offerings
Crhistopher Brown or vas...@gmx.de - please do not "spam" from different email addresses - that will not get you the answer sooner than normal - but just creates spam and people are more likely to ignore such emails :) Best, On Tue, 8 Jun 2021 at 10:55, Andrija Panic wrote: > you are almost right - but leave alone "traffic labels" which should be == > to the name of your network/bridge/vSwitch - that has nothing to do with > network TAGs. > > On physical network, you can set "tag" - you also set the same tag on a > specific network offering - then ACS will say "let me created a network > from this offering based on tags - and find a physical network that has the > same TAG as the TAG defined on the network offering" > > This used in cases when you have "guest" traffic on more than one Physical > network (i.e. in KVM world, you might be using VXLAN as the isolation > method on Physical Network1, but you also want to use e.g. Private Gateway > which supports only VLAN (not VXLAN) as the isolation method - thus you > would need to create another/2nd Physical network and give it appropriate > tags. > > Keep in mind the general tagging requirements - you you do NOT tag you > (e.g. other) network offerings, but you do tag Physical networks - this is > the same as if the Physical networks are NOT tagged - i.e. the network will > can be created on either 1st or 2nd Physical networks, since offering is > not requiring any TAG on it's own. > > Best, > > On Tue, 8 Jun 2021 at 08:44, Christopher Brown < > mail2christopher.br...@gmail.com> wrote: > >> Hi everyone, >> >> just a short question regarding the creation / usage of network offerings. >> When adding a network offering there is the optional field to give the >> network offering a "Tag". >> After reading the docs, the acutal usage is to map the offering to a >> specific physical network. >> >> So the tag would need to be same as the traffic label for the physical >> network? >> >> For example i would like to use a dedicated fiber-network for some >> hosts. So during the zone creation i would specify a "second" physical >> network for Guest-Traffic with the traffic label "fiber". >> After creation of the zone, i would add a new network offering and >> specify "fiber" as a tag for the service offering to make this >> dedicated physical network availeable for hosts ? >> >> With regards, >> >> Chris >> > > > -- > > Andrija Panić > -- Andrija Panić
Re: Usage of "Tags" for Network Offerings
you are almost right - but leave alone "traffic labels" which should be == to the name of your network/bridge/vSwitch - that has nothing to do with network TAGs. On physical network, you can set "tag" - you also set the same tag on a specific network offering - then ACS will say "let me created a network from this offering based on tags - and find a physical network that has the same TAG as the TAG defined on the network offering" This used in cases when you have "guest" traffic on more than one Physical network (i.e. in KVM world, you might be using VXLAN as the isolation method on Physical Network1, but you also want to use e.g. Private Gateway which supports only VLAN (not VXLAN) as the isolation method - thus you would need to create another/2nd Physical network and give it appropriate tags. Keep in mind the general tagging requirements - you you do NOT tag you (e.g. other) network offerings, but you do tag Physical networks - this is the same as if the Physical networks are NOT tagged - i.e. the network will can be created on either 1st or 2nd Physical networks, since offering is not requiring any TAG on it's own. Best, On Tue, 8 Jun 2021 at 08:44, Christopher Brown < mail2christopher.br...@gmail.com> wrote: > Hi everyone, > > just a short question regarding the creation / usage of network offerings. > When adding a network offering there is the optional field to give the > network offering a "Tag". > After reading the docs, the acutal usage is to map the offering to a > specific physical network. > > So the tag would need to be same as the traffic label for the physical > network? > > For example i would like to use a dedicated fiber-network for some > hosts. So during the zone creation i would specify a "second" physical > network for Guest-Traffic with the traffic label "fiber". > After creation of the zone, i would add a new network offering and > specify "fiber" as a tag for the service offering to make this > dedicated physical network availeable for hosts ? > > With regards, > > Chris > -- Andrija Panić
Usage of "Tags" for Network Offerings
Hi everyone, just a short question regarding the creation / usage of network offerings. When adding a network offering there is the optional field to give the network offering a "Tag". After reading the docs, the acutal usage is to map the offering to a specific physical network. So the tag would need to be same as the traffic label for the physical network? For example i would like to use a dedicated fiber-network for some hosts. So during the zone creation i would specify a "second" physical network for Guest-Traffic with the traffic label "fiber". After creation of the zone, i would add a new network offering and specify "fiber" as a tag for the service offering to make this dedicated physical network availeable for hosts ? With regards, Chris
Usage of "Tags" for Network Offerings
Hi everyone, just a short question regarding the creation / usage of network offerings. When adding a network offering there is the optional field to give the network offering a "Tag". After reading the docs, the acutal usage is to map the offering to a specific physical network. So the tag would need to be same as the traffic label for the physical network? For example i would like to use a dedicated fiber-network for some hosts. So during the zone creation i would specify a "second" physical network for Guest-Traffic with the traffic label "fiber". After creation of the zone, i would add a new network offering and specify "fiber" as a tag for the service offering to make this dedicated physical network availeable for hosts ? With regards, Chris
