luganofer opened a new issue #5467:
URL: https://github.com/apache/cloudstack/issues/5467
<!--
Verify first that your issue/request is not already reported on GitHub.
Also test if the latest release and main branch are affected too.
Always add information AFTER of these HTML comments, but no need to delete
the comments.
-->
##### ISSUE TYPE
<!-- Pick one below and delete the rest -->
* Improvement Request
##### COMPONENT NAME
<!--
-->
~~~
L2 Guest Network
~~~
##### CLOUDSTACK VERSION
<!--
New line separated list of affected versions, commit ID for issues on main
branch.
-->
~~~
Cloudstack 4.14 onwards
~~~
##### CONFIGURATION
<!--
Information about the configuration if relevant, e.g. basic network,
advanced networking, etc. N/A otherwise
-->
Enviroment with adcanced networking
##### OS / ENVIRONMENT
<!--
Information about the environment if relevant, N/A otherwise
-->
N/A
##### SUMMARY
<!-- Explain the problem/feature briefly -->
Currently, in an advanced network environment, L2 networks can only be
specified a VLAN id by a root admin user (which makes a lot of sense).
L2 type networks can be created by users only if they do not specify a VLAN.
All good up to this point.
However the L2 network that a user creates takes a VLAN id from the
"VLAN/VNI Range (s)" assigned to guest traffic.
It would be desirable that the L2 networks have a dedicated VLAN range
(different than the guest VLAN range) and thus the L2 networks created by the
users consume a VLAN id from this range.
In this way, the VLANs assigned to this service could be planned and
delimited, and this VLAN range could be pre-configured to physical equipment
too, among other advantages.
##### STEPS TO REPRODUCE
<!--
For bugs, show exactly how to reproduce the problem, using a minimal
test-case. Use Screenshots if accurate.
For new features, show how the feature would be used.
-->
<!-- Paste example playbooks or commands between quotes below -->
~~~
1) A root admin user creates a VLAN range dedicated to L2 networks.
2) A user (with sufficient privileges to create a network) creates an L2
network and it consumes a VLAN id from this range.
~~~
<!-- You can also paste gist.github.com links for larger files -->
##### EXPECTED RESULTS
<!-- What did you expect to happen when running the steps above? -->
~~~
The L2 network created by the user consumes a VLAN id from the
pre-established and planned range.
~~~
##### ACTUAL RESULTS
<!-- What actually happened? -->
<!-- Paste verbatim command output between quotes below -->
~~~
The L2 network created by the user takes a VLAN id from the range for guest
traffic.
~~~
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
