From 68594197af84303f640b1afca932c8229c4a4f76 Mon Sep 17 00:00:00 2001 From: chenxing Date: Wed, 8 Feb 2017 14:49:13 +0000 Subject: [PATCH] [admin-guide] Legacy to OpenStack command Change-Id: I721d00d1d4dfc0bafce1774165d0d0b1ca3cece2 Implements: blueprint use-openstack-command --- doc/admin-guide/source/compute-security.rst | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/doc/admin-guide/source/compute-security.rst b/doc/admin-guide/source/compute-security.rst index 521661143d..61a425b25c 100644 --- a/doc/admin-guide/source/compute-security.rst +++ b/doc/admin-guide/source/compute-security.rst @@ -122,12 +122,12 @@ settings: **Specifying trusted flavors** #. Flavors can be designated as trusted using the - :command:`nova flavor-key set` command. In this example, the ``m1.tiny`` - flavor is being set as trusted: + :command:`openstack flavor set` command. In this example, the + ``m1.tiny`` flavor is being set as trusted: .. code-block:: console - $ nova flavor-key m1.tiny set trust:trusted_host=trusted + $ openstack flavor set --property trusted_host=trusted m1.tiny #. You can request that your instance is run on a trusted host by specifying a trusted flavor when booting the instance: