alexandru-bagu opened a new issue #4454:
URL: https://github.com/apache/cloudstack/issues/4454
I am wondering why the VPC network cannot offer both SNAT and
PortForwarding. At the moment the VPC offering must be "Non Conserve". A
network being "non conserve" means only one service type is allowed to be
enabled at any one point. The issue is while Port Forward might be considered a
separate service than Source Nat I do not see why a VPC network cannot do both
at the same time. I tracked the issue to this place in code `public boolean
canIpUsedForNonConserveService(PublicIp ip, Service service)` which is used by
`public Map<PublicIpAddress, Set<Service>> getIpToServices(List<? extends
PublicIpAddress> publicIps, boolean postApplyRules, boolean includingFirewall)`.
Is there any specific reason why CloudStack would not be able to manage port
forwarding rules on the SNAT ip for a VPC network? I've done some small tests
with portfowarding on the VR and there did not seem to be any issues.
I've searched the issues for this but I did not find anything about it. I
hope it's not a duplicate.
##### ISSUE TYPE
<!-- Pick one below and delete the rest -->
* Bug Report
x Improvement Request
* Enhancement Request
* Feature Idea
* Documentation Report
* Other
##### COMPONENT NAME
<!--
VR
-->
~~~
~~~
##### CLOUDSTACK VERSION
4.14.0.0 - 6f96b3b2b391a9b7d085f76bcafa3989d9832b4e
~~~
----------------------------------------------------------------
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.
For queries about this service, please contact Infrastructure at:
[email protected]
