IP Space Reservation Request

IP Space Reservation Request

To proactively prevent any potential IP space conflicts in the future, Hitachi requests that specific IP blocks be reserved. This step is crucial to ensure seamless integration and prevent costly redeployments. No resources need to be deployed as part of this reservation; however, these blocks should not overlap with any existing private IP spaces currently deployed in Azure.

IP Block Requirements:

1. Databricks Deployment:

• Request: One /22 block per environment.

• Usage:

  • Half of the block will be utilized by Hitachi for our Databricks deployment.

  • The remaining half will be reserved for future expansions or custom features that may be added to Empower.

• Reasoning: Although this may seem like a large number of IP addresses per environment, reserving a substantial block ahead of time is crucial. Any change in IP space necessitates a full Databricks redeployment, which can be both time-consuming and costly. This proactive reservation aims to prevent such expensive redeployments in the future.

2. Unity Catalog:

• Request: One /24 block.
• Usage: This block will be designated for Unity Catalog.
• Note: If Unity Catalog is already deployed in the Azure region where Empower is to be deployed, this step may be skipped.