weizhouapache commented on issue #4542: URL: https://github.com/apache/cloudstack/issues/4542#issuecomment-1042007576
> > > ok @weizhouapache @aleskxyz , so this is not about the configuration of the static nat/Portforwarding/LB at all? In that case it could be in a network detail. This 'feature' has been requested before. > > > > > > @DaanHoogland > > this is not related to network details. the feature requests > > (1) reserve a private IP. do not allocate to any vms. > > (2) create static nat/port forwarding/load balancer to a reserved private IP. > > not sure if it was requested by other users before. > > again, this feature looks simple, but it is actually not. > > It requires new db table, new APIs and some service layer changes. > > in my opinion, this is not a common case. there is a workaround for it (see comments above). > > I suggest to move this out of 4.17.0.0 . @nvazquez > > I agree taking it out of 4.17 for now. Having a private ip bridged out of cloudstack is not a new user case and the work around you mention works very well. I think we can implement this by creating a network detail to store the required private ips to reserve. No new table is needed, afaics. Whit is needed is the logic to take these values of the detail into account when signing need NICs in the network. @DaanHoogland BUT there is no api to create/update/remove network details more complicated thing is, virtual machine id is a required parameter when enable static nat, create port forwarding rules. but the reserved IP does not belong to any virtual machine. -- 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]
