Imvedansh opened a new issue, #10615:
URL: https://github.com/apache/cloudstack/issues/10615

   **Description**
   
   When attempting to create a new network tier within a VPC via the UI
    (Network → VPC → <Your VPC> → Networks → Add Tier), 
   the form does not display the parent VPC CIDR.
   
   As a result, users are forced to cancel the form, go back to the VPC details 
page, copy the CIDR, then return to the "Add Network" form to paste it in. This 
creates a disruptive and unnecessary UX loop, especially for users managing 
multiple VPCs or subnets.
   
   **Steps to Reproduce**
   
   Go to the Network section.
   
   Select the VPC tab.
   
   Create a VPC (e.g., with CIDR 10.0.0.0/16).
   
   After it's created, click on that VPC (VPC1) to open its details.
   
   In the Networks subsection, click “Add Tier” (or “Add Network”).
   
   In the form, notice there's no visibility of the parent VPC’s CIDR.
   
   **Issue for Users**
   
   The CIDR field must match a subnet within the VPC CIDR.
   
   Since the VPC CIDR isn't shown in the form, the user has to:
   
   Close the form
   
   Go back to the VPC details
   
   Copy the VPC CIDR
   
   Return to the "Add Network" form
   
   Paste it to ensure they’re entering a valid subnet
   
   **Suggestion / Fix->**
   
   When a user clicks “Add Network” (to create a tier in a VPC):
   
   The form should read the parent VPC CIDR
   
   Automatically suggest a default CIDR, Gateway IP, and Netmask based on 
available space
   
   Pre-fill:
   
   this.form.gateway
   
   this.form.netmask
   
   Like in the Screenshot below
   
   
![Image](https://github.com/user-attachments/assets/d5cf96d5-f096-4595-a92a-dbade7f4d5d3)
   
   


-- 
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]

Reply via email to