Propogate cacert and insecure flags to glanceclient

Fixes bug 1278973

Previously, the insecure flag was only propagated to the keystoneclient
while the cacert flag was only propagated to the keystoneclient and
the ceilometerclient used by alarming.

Since the glanceclient also supports these options, these flags should
be propogated to it also to avoid SSL cert verification failures when the
central agent calls out to glance over https.

Change-Id: I967ba080a4011a54b5789ca0fc20cb9a37dafb15
Remove blank line in docstring

Change-Id: Ia4af26e632bf052a4b4239159d4a0a40afbaec8b
Switch over to oslosphinx

oslosphinx is the new name of oslo.sphinx

Change-Id: I4a1ba671f581dd42115104ef752fa99f87fe802e
Merge "Propogate cacert and insecure flags to glanceclient"
Merge "Remove blank line in docstring"
Merge "Switch over to oslosphinx"
Replace assertEqual(None, *) with assertIsNone in tests

Replace assertEqual(None, *) with assertIsNone in tests to have
more clear messages in case of failure.

Change-Id: Ifa954f9119bd226878134ec559ebf7d66bebdaee