anchor.diff:  
   </pre>
   
  -Note that you can press `Ctrl-C` to exit the ping program. If you are not able to ping one virtual machine from another, refer to the [OpenStack Networking Guide](http://docs.openstack.org/admin-guide-cloud/content/ch_networking.html) for more information.
  +Note that you can press `Ctrl-C` to exit the ping program. If you are not able to ping one virtual machine from another, refer to the [OpenStack Networking Guide](https://docs.openstack.org/neutron/latest/admin/) for more information.
   
   ## <a id="api_access"></a> Can you invoke large numbers of API calls? ##
   
  
positive.code: 
  <p class="note"><strong>Note</strong>: It is recommended that you deploy BOSH and Cloud Foundry in a dedicated tenancy. This way, it is easier to keep track of the servers, volumes, security groups, and networks that you create. It also allows you to manage user access.</p>
  
  For more information about OpenStack APIs, see the [OpenStack API Quick Start Guide](http://docs.openstack.org/api/quick-start/content/).
  
  
  ## <a id="metadata_service"></a> Can you access OpenStack metadata service from a virtual machine? ##
  
  According to [the OpenStack Documentation](http://docs.openstack.org/grizzly/openstack-compute/admin/content/metadata-service.html), the Compute service uses a special metadata service to enable virtual machine instances to retrieve instance-specific data. The default stemcell for use with BOSH retrieves this metadata for each instance of a virtual machine that OpenStack manages in order to get some data injected by the BOSH director.
  
  You must ensure that virtual machines you boot in your OpenStack environment can access the metadata service at http://169.254.169.254.
  
  
negative.code: 2.  In the menu on the left-hand side, click **Images & Snapshots**.
  3.  You should see a list of images. Click **Create Image**.
  4.  For **Name**, enter **Ubuntu Server 64-bit**.
  5.  For **Image Location**, enter **http://cloud-images.ubuntu.com/trusty/current/trusty-server-cloudimg-amd64-disk1.img**.
  6.  For **Format**, select **QCOW2 - QEMU Emulator**.
  7.  For **Minimum Disk**, enter 5GB.
  8.  For **Minimum Ram**, enter 1024MB.
  