Re: Snapshots are not working after upgrading to 4.15.0
@Andrei Mikhailovsky can you advise which hypervisor (and version) you are using, what primary storage - let's see if the same is true in 4.15.1 (voting happening right now - feel free to test and vote as well, please) Best, On Tue, 8 Jun 2021 at 14:25, Andrei Mikhailovsky wrote: > Thanks for the suggestions, Harikrishna. I will check it and revert back. > > Andrei > > > > - Original Message - > > From: "Harikrishna Patnala" > > To: "users" > > Sent: Tuesday, 8 June, 2021 03:33:57 > > Subject: Re: Snapshots are not working after upgrading to 4.15.0 > > > Hi Andrei, > > > > Can you check the following things and let us know? > > > > > > 1. Can you try creating a new volume and then create snapshot of that, > to check > > if this an issue with old entries > > 2. For the snapshots which are failing can you check if you are seeing > any > > error messages like this "Can't find an image storage in zone with less > than". > > This is to check if secondary storage free space check failed. > > 3. For the snapshots which are failing and if it is delta snapshot can > you > > check if its parent's snapshot entry exists in "snapshot_store_ref" > table with > > 'parent_snapshot_id' of the current snapshot with 'store_role' "Image". > This is > > to find the secondary storage where the parent snapshot backup is > located. > > > > Regards, > > Harikrishna > > > > From: Andrei Mikhailovsky > > Sent: Monday, June 7, 2021 7:00 PM > > To: users > > Subject: Snapshots are not working after upgrading to 4.15.0 > > > > Hello everyone, > > > > I am having an issue with volume snapshots since I've upgraded to > 4.15.0. None > > of the volumes are being snapshotted regardless if the snapshot is > initiated > > manually or from the schedule. The strange thing is that if I manually > take the > > snapshot, the GUI shows Success status, but the Storage>Snapshots show > an Error > > status. Here is what I see in the management server logs: > > > > 2021-06-07 13:55:20,022 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl] > > (Work-Job-Executor-81:ctx-08dd4222 job-86141/job-86143) (logid:be34ce01) > Done > > executing com.cloud.vm.VmWorkTakeVolumeSnapshot for job-86143 > > 2021-06-07 13:55:20,024 INFO [o.a.c.f.j.i.AsyncJobMonitor] > > (Work-Job-Executor-81:ctx-08dd4222 job-86141/job-86143) (logid:be34ce01) > Remove > > job-86143 from job monitoring > > 2021-06-07 13:55:20,094 DEBUG [o.a.c.s.s.SnapshotServiceImpl] > > (BackupSnapshotTask-3:ctx-744796da) (logid:607dbb0e) Failed to copy > snapshot > > com.cloud.utils.exception.CloudRuntimeException: can not find an image > stores > > at > > > org.apache.cloudstack.storage.snapshot.SnapshotServiceImpl.backupSnapshot(SnapshotServiceImpl.java:271) > > at > > > org.apache.cloudstack.storage.snapshot.DefaultSnapshotStrategy.backupSnapshot(DefaultSnapshotStrategy.java:171) > > at > > > com.cloud.storage.snapshot.SnapshotManagerImpl$BackupSnapshotTask.runInContext(SnapshotManagerImpl.java:1238) > > at > > > org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedContextRunnable.java:48) > > at > > > org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:55) > > at > > > org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:102) > > at > > > org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:52) > > at > > > org.apache.cloudstack.managed.context.ManagedContextRunnable.run(ManagedContextRunnable.java:45) > > at > > > java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515) > > at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264) > > at > > > java.base/java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:304) > > at > > > java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) > > at > > > java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) > > at java.base/java.lang.Thread.run(Thread.java:829) > > 2021-06-07 13:55:20,152 DEBUG [c.c.s.s.SnapshotManagerImpl] > > (BackupSnapshotTask-3:ctx-744796da) (logid:607dbb0e) Backing up of > snapshot > > failed, for snapshot with ID 53531, left with 2 more attempts > > > > > > I've checked and the Secondary storage is configured and visible in the > GUI. I > > can also mount it manually from the management server and a couple of > host > > servers that I've tested. In addition, I can successfully upload an ISO > image > > and that registers just fine and I can create new VMs using the newly > uploaded > > ISO image. > > > > I've had no such problems with 4.13.x ACS, so the issue seems to have > been > > introduced after doing the upgrade to 4.15.0. > > > > Could you please let me know how do I fix the issue? > > > > Cheers > > > > andrei > -- Andrija Panić
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: Why my resources is not been release when my machines is down?
global setting "host.reservation.release.period" dictates for how long the host will reserve a capacity for a stopped VM. I assume (though I find this idea a bit stupid IMO) that idea was if you stop VM, but you are short on capacity, nobody else can "jump in" and deploy a new VM taking the rest of the host's free capacity, so you (as a long-standiong customer/user) now can't start your VM you stopped 5mins ago. Best, On Tue, 8 Jun 2021 at 17:25, Kalil de Albuquerque Carvalho < kalil.carva...@hybriddc.com.br> wrote: > Hello all. > > I'm testing Cloudstack 4.15 and it is strange, or, probably, I'm doing > same mistakes, that when I halted my VM's the resources are not been > released for the system. It is like when the VM is created the resource > it is reserved exclusively for it. > > Some one can tell me where I can find the documentation that I can get > this information and how to work with it? > > Any one can help me to understand what it is happening? > > Best regards. > > -- Andrija Panić
Re: Quickstart question - Network issues
Unable to allocate vnet as a part of network Ntwk[210|Guest|8] Check you Guest traffic to see if you assigned a vlan range from which ACS will provision VLAN/networks (each tenant network = separate VLAN) On Mon, 31 May 2021 at 08:11, Jeremy Hansen wrote: > Thank you for the response. I got much further. All my issues seem > networking related. Everything is up right now and I see the template for > CentOS 5.5 as an offering. > > My Cloudstack host is on 192.168.10.35. My System VMs is configured as > such: > > > > At this point, I’m trying to understand how to configured my Guest > networks. Ideally my guest vm’s would just use my external DHCP server to > allocate an IP address but I’m not having much luck finding documentation > on how to properly do that. I also see posts saying external DHCP servers > aren’t supported because Cloudstack needs to be aware of the guest’s IP for > a number of reasons. > > So my question becomes, what type and how should I configure my guest > network. Can I use IPs on the same subnet that my Cloudstack host is > sitting on? If I can’t use DHCP directly, I can specify a range that is > not in use by my external DHCP server so IPs will still end up on the > public network and I can access the VMs on that IP directly. > > Interfaces on my Cloudstack host: > > cloud0: flags=4163 mtu 1500 > inet 169.254.0.1 netmask 255.255.0.0 broadcast 0.0.0.0 > inet6 fe80::8c30:6dff:fe87:ed32 prefixlen 64 scopeid 0x20 > ether fe:00:a9:fe:91:b4 txqueuelen 1000 (Ethernet) > RX packets 440 bytes 80558 (78.6 KiB) > RX errors 0 dropped 0 overruns 0 frame 0 > TX packets 539 bytes 96150 (93.8 KiB) > TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 > > cloudbr0: flags=4163 mtu 1500 > inet 192.168.10.35 netmask 255.255.255.0 broadcast 192.168.10.255 > inet6 fe80::4a2:a9ff:fecf:819 prefixlen 64 scopeid 0x20 > ether b4:b5:2f:db:a2:9b txqueuelen 1000 (Ethernet) > RX packets 1203750 bytes 3227151094 (3.0 GiB) > RX errors 0 dropped 5 overruns 0 frame 0 > TX packets 498851 bytes 2710603584 (2.5 GiB) > TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 > > eno1: flags=4163 mtu 1500 > ether b4:b5:2f:db:a2:9b txqueuelen 1000 (Ethernet) > RX packets 4650048 bytes 4876148565 (4.5 GiB) > RX errors 0 dropped 622 overruns 0 frame 0 > TX packets 3955493 bytes 5163648882 (4.8 GiB) > TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 > device interrupt 20 memory 0xf7c0-f7c2 > > lo: flags=73 mtu 65536 > inet 127.0.0.1 netmask 255.0.0.0 > inet6 ::1 prefixlen 128 scopeid 0x10 > loop txqueuelen 1000 (Local Loopback) > RX packets 2322050 bytes 504114946 (480.7 MiB) > RX errors 0 dropped 0 overruns 0 frame 0 > TX packets 2322050 bytes 504114946 (480.7 MiB) > TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 > > vnet0: flags=4163 mtu 1500 > inet6 fe80::fc00:a9ff:fefe:91b4 prefixlen 64 scopeid 0x20 > ether fe:00:a9:fe:91:b4 txqueuelen 1000 (Ethernet) > RX packets 50 bytes 9384 (9.1 KiB) > RX errors 0 dropped 0 overruns 0 frame 0 > TX packets 98 bytes 15290 (14.9 KiB) > TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 > > vnet1: flags=4163 mtu 1500 > inet6 fe80::fc00:7cff:fe00:5 prefixlen 64 scopeid 0x20 > ether fe:00:7c:00:00:05 txqueuelen 1000 (Ethernet) > RX packets 15707 bytes 2225323 (2.1 MiB) > RX errors 0 dropped 0 overruns 0 frame 0 > TX packets 127124 bytes 19795223 (18.8 MiB) > TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 > > vnet2: flags=4163 mtu 1500 > inet6 fe80::fc00:d8ff:fe00:7 prefixlen 64 scopeid 0x20 > ether fe:00:d8:00:00:07 txqueuelen 1000 (Ethernet) > RX packets 808 bytes 57456 (56.1 KiB) > RX errors 0 dropped 0 overruns 0 frame 0 > TX packets 109119 bytes 17746092 (16.9 MiB) > TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 > > vnet3: flags=4163 mtu 1500 > inet6 fe80::fc00:a9ff:fefe:b767 prefixlen 64 scopeid 0x20 > ether fe:00:a9:fe:b7:67 txqueuelen 1000 (Ethernet) > RX packets 46 bytes 9168 (8.9 KiB) > RX errors 0 dropped 0 overruns 0 frame 0 > TX packets 95 bytes 15068 (14.7 KiB) > TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 > > vnet4: flags=4163 mtu 1500 > inet6 fe80::fc00:c2ff:fe00:6 prefixlen 64 scopeid 0x20 > ether fe:00:c2:00:00:06 txqueuelen 1000 (Ethernet) > RX packets 144923 bytes 2256458775 (2.1 GiB) > RX errors 0 dropped 0 overruns 0 frame 0 > TX packets 822253 bytes 1009838617 (963.0 MiB) > TX errors 0 dropped 0 overruns 0 carrier 0 collisions
Why my resources is not been release when my machines is down?
Hello all. I'm testing Cloudstack 4.15 and it is strange, or, probably, I'm doing same mistakes, that when I halted my VM's the resources are not been released for the system. It is like when the VM is created the resource it is reserved exclusively for it. Some one can tell me where I can find the documentation that I can get this information and how to work with it? Any one can help me to understand what it is happening? Best regards.
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: [RESULT][VOTE] Renaming default git branch name from 'master' to 'main' and replace offensive words as appropriate for inclusiveness
Hi All, Here is the update, All the PRs that addressed the inclusive changes (changing the default branch name from 'master' to 'main' and replacing some offensive words) in the CloudStack repos are accepted/merged. I've created INFRA ticket: https://issues.apache.org/jira/browse/INFRA-21978, to rename the default branch to 'main' (which should automatically re-target all the open/draft PRs against 'master' to 'main'). I'll let you know once renaming is done, and the next steps. Regards, Suresh On 11/05/21, 1:12 PM, "Suresh Anaparti" wrote: Hi all, The vote [1] for renaming default git branch name from 'master' to 'main' and replace offensive words as appropriate for inclusiveness, in the Apache CloudStack project has passed with the following votes: +1 (PMC / binding) 4 persons (Daan, Gabriel, Rohit, Wei) +1 (non-binding) 5 persons (David, Rene, Nathan, Hari, Suresh) +0 1 person (Andrija) Thank you all for participating. Next steps, I'll close any review feedback on the PRs and get them accepted. Once the PRs are accepted, we can merge them to 'master' (may be after 4.15.1 release) and will request ASF infra (track through new INFRA ticket) to disable pushes to 'master', rename 'master' to 'main and set 'main' as the default branch, for all the CloudStack repos. [1] https://markmail.org/message/n6sbl3vgm7hy77zj Regards, Suresh
Meet the CloudStack Community: Wido den Hollander
Hello all, I am pretty sure you all know Wido den Hollander and in the best case have even met him personally. Wido is one of the great experts in the community and most active people on events and spreading the word about CloudStack. Today, I am happy to share a video interview with him: https://youtu.be/pkQYNT-x0pI Please, thumbs up and some shares for Wido. And thank you for accepting the invite for a video! Kind regards,
Re: Snapshots are not working after upgrading to 4.15.0
Thanks for the suggestions, Harikrishna. I will check it and revert back. Andrei - Original Message - > From: "Harikrishna Patnala" > To: "users" > Sent: Tuesday, 8 June, 2021 03:33:57 > Subject: Re: Snapshots are not working after upgrading to 4.15.0 > Hi Andrei, > > Can you check the following things and let us know? > > > 1. Can you try creating a new volume and then create snapshot of that, to > check > if this an issue with old entries > 2. For the snapshots which are failing can you check if you are seeing any > error messages like this "Can't find an image storage in zone with less > than". > This is to check if secondary storage free space check failed. > 3. For the snapshots which are failing and if it is delta snapshot can you > check if its parent's snapshot entry exists in "snapshot_store_ref" table > with > 'parent_snapshot_id' of the current snapshot with 'store_role' "Image". This > is > to find the secondary storage where the parent snapshot backup is located. > > Regards, > Harikrishna > > From: Andrei Mikhailovsky > Sent: Monday, June 7, 2021 7:00 PM > To: users > Subject: Snapshots are not working after upgrading to 4.15.0 > > Hello everyone, > > I am having an issue with volume snapshots since I've upgraded to 4.15.0. None > of the volumes are being snapshotted regardless if the snapshot is initiated > manually or from the schedule. The strange thing is that if I manually take > the > snapshot, the GUI shows Success status, but the Storage>Snapshots show an > Error > status. Here is what I see in the management server logs: > > 2021-06-07 13:55:20,022 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl] > (Work-Job-Executor-81:ctx-08dd4222 job-86141/job-86143) (logid:be34ce01) Done > executing com.cloud.vm.VmWorkTakeVolumeSnapshot for job-86143 > 2021-06-07 13:55:20,024 INFO [o.a.c.f.j.i.AsyncJobMonitor] > (Work-Job-Executor-81:ctx-08dd4222 job-86141/job-86143) (logid:be34ce01) > Remove > job-86143 from job monitoring > 2021-06-07 13:55:20,094 DEBUG [o.a.c.s.s.SnapshotServiceImpl] > (BackupSnapshotTask-3:ctx-744796da) (logid:607dbb0e) Failed to copy snapshot > com.cloud.utils.exception.CloudRuntimeException: can not find an image stores > at > org.apache.cloudstack.storage.snapshot.SnapshotServiceImpl.backupSnapshot(SnapshotServiceImpl.java:271) > at > org.apache.cloudstack.storage.snapshot.DefaultSnapshotStrategy.backupSnapshot(DefaultSnapshotStrategy.java:171) > at > com.cloud.storage.snapshot.SnapshotManagerImpl$BackupSnapshotTask.runInContext(SnapshotManagerImpl.java:1238) > at > org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedContextRunnable.java:48) > at > org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:55) > at > org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:102) > at > org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:52) > at > org.apache.cloudstack.managed.context.ManagedContextRunnable.run(ManagedContextRunnable.java:45) > at > java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515) > at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264) > at > java.base/java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:304) > at > java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) > at > java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) > at java.base/java.lang.Thread.run(Thread.java:829) > 2021-06-07 13:55:20,152 DEBUG [c.c.s.s.SnapshotManagerImpl] > (BackupSnapshotTask-3:ctx-744796da) (logid:607dbb0e) Backing up of snapshot > failed, for snapshot with ID 53531, left with 2 more attempts > > > I've checked and the Secondary storage is configured and visible in the GUI. I > can also mount it manually from the management server and a couple of host > servers that I've tested. In addition, I can successfully upload an ISO image > and that registers just fine and I can create new VMs using the newly uploaded > ISO image. > > I've had no such problems with 4.13.x ACS, so the issue seems to have been > introduced after doing the upgrade to 4.15.0. > > Could you please let me know how do I fix the issue? > > Cheers > > andrei
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
