use . instead of source.

Code conventions: Use “.” to source script files
When you have to source a script file, for example ,
a credentials file to gain access to user-only or
 admin-only CLI commands, use . instead of source.
See more:
http://docs.openstack.org/contributor-guide/writing-style/code-conventions

Change-Id: Ic4fd2da622f21e51f813e711cdedb7d1998592fd

tools/gate/integration/post_test_hook.sh

@@ -3,7 +3,7 @@
 # This script will be executed inside post_test_hook function in devstack gate
 
 set -x
-source commons $@
+. commons $@
 
 set +e
 cd /opt/stack/new/sahara-dashboard
@@ -23,8 +23,8 @@ cat >> /tmp/fake_config.json <<EOF
 }
 EOF
 
-source $DEVSTACK_DIR/stackrc
-source $DEVSTACK_DIR/openrc admin demo
+. $DEVSTACK_DIR/stackrc
+. $DEVSTACK_DIR/openrc admin demo
 
 openstack dataprocessing plugin update fake /tmp/fake_config.json
 

tools/gate/integration/pre_test_hook.sh

@@ -3,7 +3,7 @@
 # This script will be executed inside pre_test_hook function in devstack gate
 
 set -ex
-source commons $@
+. commons $@
 
 wget https://cloud-images.ubuntu.com/xenial/current/xenial-server-cloudimg-amd64-disk1.img -O /tmp/xenial-server-cloudimg-amd64-disk1.img
 

tools/install_venv.py

@@ -147,7 +147,7 @@ Horizon development environment setup is complete.
 To activate the virtualenv for the extent of your current shell session you
 can run:
 
-$ source .venv/bin/activate
+$ . .venv/bin/activate
 """
     print summary
 

tools/with_venv.sh

@@ -7,4 +7,4 @@ VENV=${VENV:-${VENV_PATH}/${VENV_DIR}}
 # tools/tox_install.sh looks for VIRTUAL_ENV evrythign else looks for VENV
 # so for now make them the same.
 VIRTUAL_ENV=${VENV:-${VENV_PATH}/${VENV_DIR}}
-source ${VENV}/bin/activate && "$@"
+. ${VENV}/bin/activate && "$@"