![]() Restores the instance using the disk image of the shelved instance. You are not prompted to confirm the shelve action. If the instance was booted from volume, it goes to SHELVED_OFFLOADED immediately. The state of the instance is stored on the instance disk. When an instance is in the SHELVED_OFFLOADED state, the instance data and resource allocations are deleted. Depending on the cloud configuration, shelved instances are moved to the SHELVED_OFFLOADED state either immediately or after a timed delay. When you shelve an instance you retain the instance data and resource allocations, but clear the instance memory. View the most recent section of the instance console log. You cannot rescue an instance that was booted from a volume. For example, this operation might be required if a filesystem of an instance becomes corrupted. It is also possible to reboot a running instance into rescue mode. You can connect to the temporary server to repair the system and recover your data. This shuts down the instance and mounts the root disk to a temporary server. In an emergency such as a system failure or access failure, you can put an instance in rescue mode. Removes the specified security group from the instance. Openstack server set -property Īdds the specified security group to the instance. For more information, see Creating a customized instance. You can use instance metadata to specify the properties of an instance. For more information, see Deleting a Block Storage service volume in the Storage Guide. You must delete attached volumes separately. ![]() Deleted instances are not recoverable unless the cloud has been configured to enable soft delete.ĭeleting an instance does not delete its attached volumes. You are not prompted to confirm the destroy action. You are not prompted to confirm the resume action. You are not prompted to confirm the suspend action. You are not prompted to confirm the pause action. The paused instance continues to run in a frozen state. The state of the instance is stored in memory (RAM). Customizing an instance by using a config drive Customizing an instance by using metadataġ1.3. Customizing an instance by using user dataġ1.2. Creating a customized instance"Ĭollapse section "11. Managing an instance"Ĭollapse section "10. Connecting to an instance"Įxpand section "10. Connecting to an instance"Ĭollapse section "9. Creating an instance with SSH accessĮxpand section "9. Disassociating a floating IP address from an instanceĨ.5. Assigning a floating IP address to an instanceĨ.4. Removing a security group from a portĨ.2.8. Securing instance access with security groups and key pairs"Ĩ.2.5. Securing instance access with security groups and key pairs"Ĭollapse section "8.2. Securing instance access with security groups and key pairsĮxpand section "8.2. ![]() Providing public access to an instance"Ĩ.2. Providing public access to an instance"Ĭollapse section "8. Providing public access to an instanceĮxpand section "8. Viewing the volumes attached to an instanceĨ. Removing a guaranteed minimum bandwidth QoS from an instanceĬollapse section "7. Creating an instance with a guaranteed minimum bandwidth QoS"Ħ.1. Creating an instance with a guaranteed minimum bandwidth QoS"Ĭollapse section "6. Creating an instance with a guaranteed minimum bandwidth QoSĮxpand section "6. Creating an instance with a SR-IOV network interfaceĦ. Creating an instance from a bootable volumeĥ.4. Types of instance storage"Ĭollapse section "5. Types of instance storage"Ĭollapse section "3. ![]() Providing feedback on Red Hat documentationĮxpand section "3. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |