To be able to Reserve IP and not allocate to VM

[hstan77]

ISSUE TYPE

• Enhancement Request

COMPONENT NAME

IP assignment,  Able to reserve IP that not auto assign to VM

CLOUDSTACK VERSION

Cloudstack 4.15

CONFIGURATION

OS / ENVIRONMENT

SUMMARY

Some IP address that assigned to VM, but that IP that having issue of Spamming, Blacklist etc, and after the VM being changed to new IP, the issued-ip will return to the IP Pool and future re-assign to other VM.
The system not able to reserve the problem ip which temporary do not re-assign to as it the spamming issue took time to resolve, some time it may took few months for resolving.

STEPS TO REPRODUCE

EXPECTED RESULTS

Allow mark IP as Reserve, and reserved ip shall not be auto-reassign to VM

ACTUAL RESULTS

Not able to reserve IP that have issue

[ravening]

how about acquiring the ip but not assigning to any vm? since its already in allocated state, it wont be considered for future vm assignment

[hstan77]

If temporary solution, may be it can, or just assign to another dummy vm.

But that is not a proper way / formal way of doing.

[DaanHoogland]

@hstan77 when you say not assign to a VM you actually mean not acquiring it in the scope of a network, right? Is the intention to be able to use it later or to keep ACS from being able to assign it ever? so it can only be used outside of ACS untill it is explicitely released.

[nvazquez]

Hi @hstan77 is there any update on this?

[yadvr]

@nvazquez @sureshanaparti @davidjumani @shwstppr @Pearl1594 @DaanHoogland @weizhouapache - any update on this, who's assigned/working on this? Thanks.

[ravening]

@rhtyd @hstan77 we can mark it as Reserved in the db.. we can do it either manually or just provide a new api to do it

[hstan77]

Hi Yes, can mark as reserve as status there . Currently I doing for a work around of this is, create a Dummy VM , and assign the IP that need reserve to the Dummy VM secondary IP .

…

On Wed, Sep 29, 2021 at 4:23 PM Rakesh ***@***.***> wrote: @rhtyd <https://github.com/rhtyd> @hstan77 <https://github.com/hstan77> we can mark it as Reserved in the db.. we can do it either manually or just provide a new api to do it — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#4357 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ARFNGASLMT6OPOSUUMUKKSDUELEI5ANCNFSM4R6BOW5Q> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.

-- Regards, Hean Seng

[weizhouapache]

Hi @hstan77 @aleskxyz
cc @rohityadavcloud @nvazquez

Just want to confirm, what you requested are
(1) support reservation of public IPs (of shared and isolated networks), not private IPs of isolated networks/vpcs.
(2) public IP is reserved for an account, and considered in resource count calculation.
(3) APIs to reserve a public IP, and release a Reserved public IP. when account is removed, the public IP will be released automatically.