클라우드 컴퓨팅 & NoSQL/IaaS 클라우드

Openstack review note

Terry Cho 2011. 5. 13. 23:29
오늘 대충 쭈욱 훝어봤는데...
결론은 Simple하네... 그리고 별거 읍네~~~
아래는 혼자 주저리 주러리 노트
기본 개념은 Hypervisor들 abstract해서 올려주고
EC2 호환성 가지도록 REST API 정의하고,(그래서 아마존 CLI가 다 먹는군..)
Provisioning 관련 프로세스 (Image관리, VLAN 태깅 등) 몇개 좀 해주고....
그게 다 인듯......
API 보니까는 100개도 오픈 안되어 있던데..
반대로 Simple해서 개발할때는 편할 수 도 있을 듯..
Reference Implementation으로 되어 있는 Portal은... 진짜... Tutorial 수준...
MS의 위대함을 또 한번 느꼈음... ㅋㅋ

Hyper-V support install  : http://wiki.openstack.org/HypervInstall?highlight=%28Hyper-V%29

Currently, Nova supports three kinds of networks, implemented in three “Network
Manager” types respectively: Flat Network Manager, Flat DHCP Network Manager, and
VLAN Network Manager. The three kinds of networks can co-exist in a cloud system.


일단 VM create 하는데, Affinity id는 있고

4.1.2.1. Server Affinity
As stated previously, the compute service has an anti-affinity property that attempts to
spread out VMs across hosts. There may be cases where affinity matters however. For
example, VMs may need to be placed near one another in order to effectively share
resources. The affinityId attribute represents the lowest level zone that allows clients to
specify placement of VMs. Note that VMs with the same affinityId may not necessarily
share the same hostId. That said, hosts with the same affinityId are guaranteed to be in
proximity of one another. To launch a server with affinity to an existing server, include the
affinityId of the existing server in the server create request.

Bare metal provisioning이 고민 되어야 겠네... 읍네~~

Template 가 좀 약하네.
특히 서버 Create할때..

==
5/18 추가 Live Migration 됨 - http://docs.openstack.org/cactus/openstack-compute/admin/content/live-migration-usage.html
그리드형