Hi,
Right now I have added a second Physical network for Guest traffic with tag
"DefaultB" and added "DefaultA" to the one which was already present, I have
created new 2 network offering, one for each tag. When I try to create a new
Guest network in 4.15.1, I see the offering for tag Default A but not for B
when I select the second physical network, nothing visible, I deleted the
network, offering, created again, same thing.
"Found physical network id=203 based on requested tags DefaultB
2021-10-08 08:12:32,178 DEBUG [c.c.a.ApiServlet] (qtp182531396-17:ctx-ecf8c295
ctx-1af2acec) (logid:5a80a500) ===END=== 86.125.230.37 -- GET
zoneid=c3b5e5fa-c3e8-49f0-8094-573456a45c00&state=Enabled&tags=DefaultB&guestiptype=Shared&command=listNetworkOfferings&response=json"
I'm doing something wrong?
Regards,
Cristian
-----Original Message-----
From: vas...@gmx.de <vas...@gmx.de>
Sent: Thursday, October 7, 2021 6:37 PM
To: users@cloudstack.apache.org
Subject: Re: Multiple Network labels - custom
it should work , as i am am using this for providing some "special"
networks myself in my environment.
maybe for a better understanding you can take a look at the following
https://www.shapeblue.com/understanding-cloudstacks-physical-networking-architecture/
and there the section "advanced network traffic". there you'll find a diagramm
of a scenario, where they provide an mpls network for guest traffic.
what i had done to achieve this is (it works but i don't know if this is all
best practice):
WARNING: When introducing another physical network for e.g guest traffic, the
"default" network offerings won't work anymore. CS has no default-allocation to
an specified network - At least this is my experience.
You will need to implement tags and create "custome" default network offerings
for further usage!
- create a new physical network in the zone
- add traffic type "guest"
- set the networklabel for matching purpose with the nics on the host
- define tags for ALL physical networks (at least i needed to. if i am correct
if you start tagging, you will have to implement it for all physical networks)
- create 2 network offerings each using one of the tags of the physical
networks - traffic type guest
Then you can create networks, using the new network offerings, which will use
the "tagged" physical network --> use the the matching nics on your hosts
Am Do., 7. Okt. 2021 um 16:38 Uhr schrieb Cristian Ciobanu
<cristian.c@istream.today>:
> Hi,
>
> In a much simpler way.
>
> I have 2 networks, 1 shared and 1 isolated, the problem i have
> here, both are using the same guest traffic label, because of this,
> I'm not able to use these on different labels/nics, both are using the
> same traffic type. Even if I add an additional physical network i will
> have only one type of guest traffic...
>
> I would like to specify a custom traffic type ( guest x) and use
> for specific network, shared or isolated.
>
> I'm not sure if I can replicate this by using tags, will this work?
>
>
> Regards
> Cristian
>
> On Thu, Oct 7, 2021, 15:22 vas...@gmx.de <vas...@gmx.de> wrote:
>
>> just my thoughts.
>>
>> if i am understanding your intention correctly, you want to use a
>> dedicated physical network on the hosts for "customized" guest
>> traffic, correct?
>>
>> You will need to add a "new" physical network to the zone with the
>> networklabel, assaign the traffic type "guest" and start to use tags
>> for the physical networks.
>> Afterwards you would need to implement a dedicated network service
>> offering for this network - by using a tag to associate the network
>> offering to the physical network.
>>
>> Your idea would currently not work cause the "physical network" in a
>> zone is a 1:1 representation of the physical network on the hosts.
>> afterwards you have some like a 1:m (one CS physical network - many
>> various traffic types possible) but not n:1 (many physical networks :
>> one traffic type - even "worse" you would have different "flavours"
>> of one traffic type).
>>
>> Maybe another way to display the relation (physical Network on host -
>> phyical network in a zone - traffic type):
>> Currently used in CS: 1 - 1 - m
>>
>> Not supported in in CS: 1 - n - m
>>
>> what i understand you are looking for: 2 - 1 - 1 (while the traffic
>> type guest would be segmentet into "default" and "custome")
>>
>> Hope that someone can imagine what i mean :-D
>>
>>
>>
>>
>> Am Do., 7. Okt. 2021 um 08:37 Uhr schrieb <cristian.c@istream.today>:
>>
>> > Hello,
>> >
>> >
>> >
>> > Is there a way to use multiple network labels for the same
>> > network type?
>> > for example; I have Guest traffic with network label "vSwitch1, but
>> > I
>> also
>> > want to have a vSwitch0 or anything else. If this is not possible,
>> > is there a way to create custom networks traffic types using the
>> > same type of network offering but create under a different network.
>> >
>> > label?
>> >
>> >
>> >
>> > I want to have 2 traffic types for Guest, (Guest And
>> > GuestCustom) using the same network offering but create the under
>> > the different network
>> label.
>> > The idea is to have the possibility to create/duplicate same type
>> > of traffic but deploy under different network label (vSwitchX).
>> >
>> >
>> >
>> >
>> >
>> >
>> >
>> > Regards,
>> >
>> > Cristian
>> >
>> >
>>
>
