Add IPv6 netmask parameter to subnets

[tampler]

ISSUE TYPE

• Improvement Request
• Feature Idea

COMPONENT NAME

Core, API

CLOUDSTACK VERSION

4.19.0.0-SNAPSHOT-20231025-090535

CONFIGURATION

OS / ENVIRONMENT

SUMMARY

IPv6 support was added to subnets. According to docs, there's no way to config IPv6 netmask. However, BOTH v4 and v6 masks need to be configured

STEPS TO REPRODUCE

EXPECTED RESULTS

Both IPv4 and IPv6 masks are allowed to set. Both need to be named properly, like `netmask4` and `netmask6`

ACTUAL RESULTS

IPv4 mask only with `netmask` parameter

[weizhouapache]

You can use ip6cidr

[tampler]

Of course I can. Same I could have had only IPv4 cidr. I noticed this discrepancy during API config for v6 networks.
Why having different APIs for v4 and v6?

[tampler]

I also suggest to standardize naming, e.g:
cidr4 vs cidr6
gate4 vs gate6
netmask4 vs netmask6
ip4start, ip4end vs ip6start, ip6end
dns4 vs dns6

[DaanHoogland]

I also suggest to standardize naming, e.g: ip4cidr vs ip6cidr gate4 vs gate6 netmask4 vs netmask6 ip4start, ip4end vs ip6start, ip6end dns4 vs dns6

for backwards compatibility I'd keep the designartors without number to be aliases of the -4 names.

[weizhouapache]

@tampler
I am not sure if you still need the parameter.

In my opinion, unlike Ipv4 netmask, almost every ipv6 user uses Ipv6 prefix/cidr (not ipv6 netmask which is too complicated).

[tampler]

Hello @weizhouapache

This seems to be like a stole issue. We may close it for now as a low priority at least. I'll reopen this should I require this again and badly ☝️