Set defaults for amqp in glance-registry.conf

We should set these defaults in glance-registry.conf
(they are actually the same as in glance-api.conf) to be able to
use oslo.messaging notification.api (in glance-registry)

Which is actually essential for osprofiler

Change-Id: I7768556aef17bb95123423f7e0cea54ecc21258b
Also run v2 functional tests with registry

Currently the v2 functional tests are run without the v2 registry enabled.

This means that bugs which are only seen when the v2 registry is enabled
may not be caught by the gate (eg #1308419, #1339775).

Here we enable some basic functional testing (eg image life cycle) with
the v2 registry enabled (in addition to the existing direct-to-database
mode). This should help prevent some types of bugs being introduced.

There is a plan to move some functional tests into tempest, at which
point these additional tests can be removed in favour of equivalent
tempest tests.

Change-Id: I774a277673390650874aad4334b28d1a872ea93f
Security hardening: fix possible shell injection vulnerability

The glance/cmd/control.py file contains a possible shell injection
vulnerability:

https://github.com/openstack/glance/blob/master/glance/cmd/control.py#L134 .

Setting 'shell=True' here opens the possibility of shell injection
by setting server to something like '; rm -rf /'. This will cause
the command 'rm -rf /' to be run with the privileges of the user
that ran Glance.

The fix is to parameterize the input so that the command run here
can only be 'logger'.

Change-Id: If48106ceea1dd582bcec9d03e056d88591bcba8d
Closes-bug: 1335208
Merge "Set defaults for amqp in glance-registry.conf"
Merge "Also run v2 functional tests with registry"
Merge "Security hardening: fix possible shell injection vulnerability"