vlan can only be specified by root admin, as it requires some settings on infrastructure, and it is also critical as vlan misconfiguration might cause some issues. vlan id is also invisible for non-admin users.
If you create a L2 or Isolated network for your user, the network belongs to the user, so the network is not visible when you create an instance, but the user can see it. -Wei On Mon, 27 Nov 2023 at 12:04, Jimmy Huybrechts <[email protected]> wrote: > Hi, > > After a lot of testing I’m now trying to put it more in the shape we would > use it. So I created a user and domain for own instances. > > Now I’m trying to create a Network offering on a specific vlan, which > doesn’t seem possible? If I create one with specify vlan is true and assign > it to my tenant I can’t see it when creating an instance, if it create it > with specify vlan is false I can see it but how do I tell it which vlans to > use then? (using an untagged vlan is not possible here). > > How do I create a L2 network on a specific vlan and be able to use it in > my own domain? Since I’m also the root admin I can give it of course > > -- > Jimmy >
