Move to use UWsgi for Nova
The placement service is already setup to use UWsgi, we need to move the other Nova services to follow suit as part of our community goal for Pike. Additionally, we need to clean up the nginx configuration as we are moving away from fronting uWSGI with nginx inside the roles. Depends-On: Ib66b9709fb88205eaf3f133c87357a4dbbdde5ae Change-Id: If6c30e00c1c753692c970457b75e3ae7f5cc066c Implements: blueprint goal-deploy-api-in-wsgi
This commit is contained in:
17 changed files with 179 additions and 303 deletions
@@ -15,10 +15,11 @@
nova_virt_type:lxd
tempest_run:yes
tempest_venv_tag:"{{ tempest_git_install_branch }}"
tempest_venv_bin:"/opt/tempest_{{ tempest_venv_tag }}/bin"
tempest_log_dir:"/var/log/"
tempest_test_whitelist:
- tempest.scenario.test_server_basic_ops.TestServerBasicOps.test_server_basic_ops
tempest_tempest_conf_overrides:
'compute-feature-enabled':
'config_drive':'false'
tempest_img_url:"http://download.cirros-cloud.net/0.3.4/cirros-0.3.4-x86_64-lxc.tar.gz"
tempest_img_disk_format:raw
tempest_image_file:"cirros-0.3.4-x86_64-lxc.tar.gz"
@@ -26,13 +27,8 @@ tempest_img_name: "cirros"
tempest_images:
- url:"http://download.cirros-cloud.net/0.3.4/cirros-0.3.4-x86_64-lxc.tar.gz"
sha256:"e8172c603fad47f4c95e67bd2751c2977e07164c9ebdfcf3f9c1d7ff598ed217"
tempest_test_whitelist:
- tempest.scenario.test_server_basic_ops.TestServerBasicOps.test_server_basic_ops
neutron_provider_networks:
network_types:"vxlan,flat"
network_mappings:"flat:eth12"
network_vxlan_ranges:"1:1000"
tempest_tempest_conf_overrides:
'compute-feature-enabled':
'config_drive':'false'
@@ -13,10 +13,6 @@
# See the License for the specific language governing permissions and
# limitations under the License.
tempest_run:yes
tempest_venv_tag:"{{ tempest_git_install_branch }}"
tempest_venv_bin:"/opt/tempest_{{ tempest_venv_tag }}/bin"
tempest_log_dir:"/var/log/"
tempest_test_whitelist:
- tempest.scenario.test_server_basic_ops.TestServerBasicOps.test_server_basic_ops
Reference in New Issue
Block a user
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.