"Compute API 서버 개념"의 두 판 사이의 차이

34번째 줄: 34번째 줄:
* UNKNOWN: The state of the server is unknown. It could be because a part of the infrastructure is temporarily down (see Handling Down Cells for more information). Contact your cloud provider.
* UNKNOWN: The state of the server is unknown. It could be because a part of the infrastructure is temporarily down (see Handling Down Cells for more information). Contact your cloud provider.
* VERIFY_RESIZE: System is awaiting confirmation that the server is operational after a move or resize.
* VERIFY_RESIZE: System is awaiting confirmation that the server is operational after a move or resize.
==서버 생성==
==서버 쿼리==
==서버 액션==
==서버 패스워드==
==서버 메타데이터==
==블록 디바이스 매핑==
==스케줄러 힌트==
==서버 콘솔==
==서버 네트워크==
==서버 접근 주소==
==서버 이동==
===클라우드 운영자가 서버 이동 필요함===
===실패한 컴퓨트 호스트 복구===
===사용자가 더 많은 리소스를 얻기 위해 크기조정함===
===사용자가 서버를 사용하지 않을 때 과금을 원치 않음===
==게스트 OS 설정==
===메타데이터 API===
===설정 드라이브===
===사용자 데이터===
===서버 퍼스널리티===

2024년 6월 30일 (일) 15:06 판

1 개요

Crystal Clear action info.png 작성 중인 문서입니다.
Server concepts
서버 개념

https://docs.openstack.org/api-guide/compute/server_concepts.html


OpenStack Compute API에서 서버는 가상머신(VM) 인스턴스, 물리적 머신, 컨테이너를 의미합니다.

2 서버 상태

이미지, 플레이버, 이름, 상태에 따라 서버 목록을 필터링할 수 있습니다. 각 필터는 해당 쿼리 매개변수를 통해 설정합니다.

서버에는 현재 서버 상태를 나타내는 상태 속성이 포함되어 있습니다. 서버 목록 요청을 수행할 때 서버 상태를 기준으로 필터링할 수 있습니다. 서버 상태는 응답 본문에 반환됩니다. 서버 상태는 다음 값 중 하나입니다:

서버 상태 값
  • ACTIVE: The server is active.
  • BUILD: The server has not yet finished the original build process.
  • DELETED: The server is deleted.
  • ERROR: The server is in error.
  • HARD_REBOOT: The server is hard rebooting. This is equivalent to pulling the power plug on a physical server, plugging it back in, and rebooting it.
  • MIGRATING: The server is migrating. This is caused by a live migration (moving a server that is active) action.
  • PASSWORD: The password is being reset on the server.
  • PAUSED: The server is paused.
  • REBOOT: The server is in a soft reboot state. A reboot command was passed to the operating system.
  • REBUILD: The server is currently being rebuilt from an image.
  • RESCUE: The server is in rescue mode.
  • RESIZE: Server is performing the differential copy of data that changed during its initial copy. Server is down for this stage.
  • REVERT_RESIZE: The resize or migration of a server failed for some reason. The destination server is being cleaned up and the original source server is restarting.
  • SHELVED: The server is in shelved state. Depends on the shelve offload time, the server will be automatically shelved off loaded.
  • SHELVED_OFFLOADED: The shelved server is offloaded (removed from the compute host) and it needs unshelved action to be used again.
  • SHUTOFF: The server was powered down by the user, either through the OpenStack Compute API or from within the server. For example, the user issued a shutdown -h command from within the server. If the OpenStack Compute manager detects that the VM was powered down, it transitions the server to the SHUTOFF status.
  • SOFT_DELETED: The server is marked as deleted but will remain in the cloud for some configurable amount of time. While soft-deleted, an authorized user can restore the server back to normal state. When the time expires, the server will be deleted permanently.
  • SUSPENDED: The server is suspended, either by request or necessity. See the feature support matrix for supported compute drivers. When you suspend a server, its state is stored on disk, all memory is written to disk, and the server is stopped. Suspending a server is similar to placing a device in hibernation and its occupied resource will not be freed but rather kept for when the server is resumed. If an instance is infrequently used and the occupied resource needs to be freed to create other servers, it should be shelved.
  • UNKNOWN: The state of the server is unknown. It could be because a part of the infrastructure is temporarily down (see Handling Down Cells for more information). Contact your cloud provider.
  • VERIFY_RESIZE: System is awaiting confirmation that the server is operational after a move or resize.

3 서버 생성

4 서버 쿼리

5 서버 액션

6 서버 패스워드

7 서버 메타데이터

8 블록 디바이스 매핑

9 스케줄러 힌트

10 서버 콘솔

11 서버 네트워크

12 서버 접근 주소

13 서버 이동

13.1 클라우드 운영자가 서버 이동 필요함

13.2 실패한 컴퓨트 호스트 복구

13.3 사용자가 더 많은 리소스를 얻기 위해 크기조정함

13.4 사용자가 서버를 사용하지 않을 때 과금을 원치 않음

14 게스트 OS 설정

14.1 메타데이터 API

14.2 설정 드라이브

14.3 사용자 데이터

14.4 서버 퍼스널리티

문서 댓글 ({{ doc_comments.length }})
{{ comment.name }} {{ comment.created | snstime }}