---
title: "Deploying Remote NetMRI Sandboxes Using cloud-init"
canonical: "https://docs.infoblox.com/space/OCDeployGuide/142902304/Deploying%20Remote%20NetMRI%20Sandboxes%20Using%20cloud-init"
format: markdown
---
You can deploy remote NetMRI Sandboxes as OpenStack instances using could-init in the same way as you deploy NetMRI virtual appliances. You can then connect them to NetMRI OC and collectors appliances to run scripts. For deployment instructions, see *[Deploying NetMRI Virtual Appliances Using cloud-init on OpenStack](https://infoblox-docs.atlassian.net/wiki/spaces/OCDeployGuide/pages/143295536)*.

The set of fields for Sandbox cloud-init deployment includes:

- server_name
- mgmt_port
  - v4_addr
  - v4_netmask
  - v4_gw
  - v6_addr
  - v6_prefix
  - V6_gw
- time
  - server_1
  - region
  - zone
- dns
  - dns_server_1
  - dns_server_2
  - dns_search_1
  - dns_search_2

For fields description, see *[Supported Fields](https://infoblox-docs.atlassian.net/wiki/spaces/OCDeployGuide/pages/143295634)*.