Configure Identity service for Networking¶

To configure the Identity service for use with Networking

1. Create the get_id() function

   The get_id() function stores the ID of created objects, and removes the need to copy and paste object IDs in later steps:

   1. Add the following function to your .bashrc file:

      function get_id () {
      echo `"$@" | awk '/ id / { print $4 }'`
      }
      

   2. Source the .bashrc file:

      $ source .bashrc
      

2. Create the Networking service entry

   Networking must be available in the Compute service catalog. Create the service:

   $ NEUTRON_SERVICE_ID=$(get_id openstack service create network \
     --name neutron --description 'OpenStack Networking Service')
   

3. Create the Networking service endpoint entry

   The way that you create a Networking endpoint entry depends on whether you are using the SQL or the template catalog driver:

   • If you are using the SQL driver, run the following command with the specified region ($REGION), IP address of the Networking server ($IP), and service ID ($NEUTRON_SERVICE_ID, obtained in the previous step).

     $ openstack endpoint create $NEUTRON_SERVICE_ID --region $REGION \
       --publicurl 'http://$IP:9696/' --adminurl 'http://$IP:9696/' \
       --internalurl 'http://$IP:9696/'
     

     For example:

     $ openstack endpoint create $NEUTRON_SERVICE_ID --region myregion \
       --publicurl "http://10.211.55.17:9696/" \
       --adminurl "http://10.211.55.17:9696/" \
       --internalurl "http://10.211.55.17:9696/"
     

   • If you are using the template driver, specify the following parameters in your Compute catalog template file (default_catalog.templates), along with the region ($REGION) and IP address of the Networking server ($IP).

     catalog.$REGION.network.publicURL = http://$IP:9696
     catalog.$REGION.network.adminURL = http://$IP:9696
     catalog.$REGION.network.internalURL = http://$IP:9696
     catalog.$REGION.network.name = Network Service
     

     For example:

     catalog.$Region.network.publicURL = http://10.211.55.17:9696
     catalog.$Region.network.adminURL = http://10.211.55.17:9696
     catalog.$Region.network.internalURL = http://10.211.55.17:9696
     catalog.$Region.network.name = Network Service
     

4. Create the Networking service user

   You must provide admin user credentials that Compute and some internal Networking components can use to access the Networking API. Create a special service project and a neutron user within this project, and assign an admin role to this role.

   1. Create the admin role:

      $ ADMIN_ROLE=$(get_id openstack role create admin)
      

   2. Create the neutron user:

      $ NEUTRON_USER=$(get_id openstack user create neutron \
        --password "$NEUTRON_PASSWORD" --email demo@example.com \
        --project service)
      

   3. Create the service project:

      $ SERVICE_TENANT=$(get_id openstack project create service \
        --description "Services project" --domain default)
      

   4. Establish the relationship among the project, user, and role:

      $ openstack role add $ADMIN_ROLE --user $NEUTRON_USER \
        --project $SERVICE_TENANT
      

For information about how to create service entries and users, see the Ocata Installation Tutorials and Guides for your distribution.

[DEFAULT]
use_neutron = True
firewall_driver=nova.virt.firewall.NoopFirewallDriver

[neutron]
url=http://192.168.1.2:9696
auth_strategy=keystone
admin_tenant_name=service
admin_username=neutron
admin_password=password
admin_auth_url=http://192.168.1.2:35357/v2.0
service_metadata_proxy=true
metadata_proxy_shared_secret=foo