SlideShare a Scribd company logo
G-Cube OpenStack Solution 
G-Cube Inc. 
This information is confidential and was prepared by G-Cube solely for the use of our client and investor; it is not to be relied on by any 3rd party without G-Cube's prior written consent
G-Cube OpenStack Solution 
‱ Data Defined Storage (DDS) 
-Integrated data-centric management architecture 
-Storing, retaining, and accessing data based on content, meaning, and value. 
-Core technology 
Media Independent Data Storage 
Data Security & Identity Management 
Distributed Metadata Repository 
http://en.wikipedia.org/wiki/Data_Defined_Storage 
This information is confidential and was prepared by G-Cube solely for the use of our client and investor; it is not to be relied on by any 3rd party without G-Cube's prior written consent SEO 141028-IR-Business proposal v05 2
Software Defined Storage vs Data Defined Storage 
Software Defined Storage 
‱ Storage-centric 
management 
‱ User manages storage. 
‱ SDS decribes storage. 
‱ Human (should) know 
-Storage features 
Data Defined Storage 
‱ Data-centric management 
‱ User describes data 
‱ DDS manages storage 
‱ DDS (should) know 
-Data description 
This information is confidential and was prepared by G-Cube solely for the use of our client and investor; it is not to be relied on by any 3rd party without G-Cube's prior written consent SEO 141028-IR-Business proposal v05 3
In Storage Centric Management 
Architecture 
Deliver package 1 until tom 
orrow, package 2 until this 
weekend, package 3 until t 
his month
 
what they do 
Who deliver? by human 
(admin) 
 high-cost , low-efficient. 
This information is confidential and was prepared by G-Cube solely for the use of our client and investor; it is not to be relied on by any 3rd party without G-Cube's prior written consent SEO 141028-IR-Business proposal v05 4
In Storage Centric Management 
Architecture 
Deliver package 1 until 
tomorrow, package 2 until 
this weekend, package 3 
until this month
 
what they do 
Who deliver? 
‱ automated by existing 
solutions unsatify 
This information is confidential and was prepared by G-Cube solely for the use of our client and investor; it is not to be relied on by any 3rd party without G-Cube's prior written consent SEO 141028-IR-Business proposal v05 5
In Data Centric Management 
Architecture 
Deliver package 1 until 
tomorrow, package 2 until this 
weekend, package 3 until this 
month
 
what they do 
Data 
description 
package 1 via airli 
ne, package 2 by t 
ruck
 
Who deliver? 
automated & unified management 
 low-cost & high-efficient  
satisfy users! 
what we(will) do 
This information is confidential and was prepared by G-Cube solely for the use of our client and investor; it is not to be relied on by any 3rd party without G-Cube's prior written consent SEO 141028-IR-Business proposal v05 6
Data Defined Storage의 필요성 
‱ 서ëč„슀 뿐만 아니띌 ìŠ€í† ëŠŹì§€ë„ 더 읎상 flat 하지 않닀. 
-Multi-Tenant Service 
New service frameworks: Cloud, VDI, Big-data. 
Traditional services: DB, WAS, Multimedia... 
-Multi-Aspect Storage 
예전: 시슀템메ëȘšëŠŹ + í•˜ë“œë””ìŠ€íŹ (Enterprise or Personal) 
지ꞈ: 메ëȘšëŠŹ + SSD + HDD + cloud storage 
- ëč„휘발성 메ëȘšëŠŹ 소자(DRAM, NAND Flash, MRAM, FeRAM) 읞터페읎슀/프 
ëĄœí† ìœœ (SATA/SAS, PCI-E NVME), 하드웚얎 (SLC/MLC/TLC, rpm, 
redundancy-level), 위ìč˜ìžì ‘성 (Local DAS, SAN, WAN) 
‱ Media Independent Data Storage ì†”ëŁšì…˜ìŽ 필요. 
-êŽ€ëŠŹìž 및 ì‚Źìš©ìžê°€ ëł”ìžĄí•œ storage íŠč성을 ìŽí•Ží•˜ì—Ź íššìœšì ìœŒëĄœ data넌 mapping하는 
êČƒìŽ 불가늄. 
‱ Data I/O는 ëŹŽìĄ°ê±Ž êł ì„±ëŠ„ìŽ 아니띌, ì‚Źìš©ìžê°€ 원하는 수쀀에 가임 맞는 데읎터 
입출렄 서ëč„슀넌 ì œêł”. 
-씜소의 ëč„ìš©ìœŒëĄœ 전ìČŽì ìœŒëĄœ 씜적의 service quality넌 ëłŽìž„. 
This information is confidential and was prepared by G-Cube solely for the use of our client and investor; it is not to be relied on by any 3rd party without G-Cube's prior written consent SEO 141028-IR-Business proposal v05 7
G-Cube OpenStack Solution의 시임 예상 
‱ 적용읎 가늄/ëč„ꔐ적 용읎한 시임 
-Private cloud provider 
Game publishers, 쀑소 êž°ì—… 규ëȘšì˜ 가상 ëšžì‹ /VDI 환êČœ, íŹí„žì‚Ź, 대학/Ʞꎀ/êž°ì—… 
의 전산섌터. 
서ëč„슀 ì‚Źìš©ìžì™€ ì œêł”ìžê°€ 동음 하거나 tightly-coupled 되얎 있얎서 ëč„ìš© 절감읎 
나 서ëč„슀 품질 개선을 톔핎서 TOC 감소가 쀑요한 시임. 
닀양한 íŠč성의 데읎터 (êČŒìž„ 데읎터, ëž”ëĄœê·ž/홈페읎지, ëŻžë””ì–Ž, ìŽëŻžì§€, ì‚Źìš©ìž/êł  
객 êł„ì • 등) 가 톔합 êŽ€ëŠŹë˜êł  있는 환êČœ. 
-Big data infra, SNS service provider 
방대한 양의 데읎터가 ìĄŽìžŹí•˜êł  핮ë‹č 데읎터의 유지 및 êŽ€ëŠŹ ëč„용읎 높음. 
데읎터의 ì–‘êłŒ ì‚Źìš©ìž 수가 í­ë°œì ìœŒëĄœ 슝가핚에 따띌 전ìČŽ 서ëč„슀 질 저하/용량 
ë¶€ìĄ±ì— 따넞 임ëč„의 추가 및 확임읎 ëčˆëȈ핹. 
-TCO나 성늄에 대한 ìš”ê”Ź ì‚Źí•­, ê·žëŠŹêł  scale-out을 위핎서 도입할 임ëč„ ë° ì†”ëŁšì…˜ì˜ ê”Ź 
ë§€ license ëč„용읎 ìƒˆëĄœìšŽ OpenStack solution 도입을 위한 개발 소요 ëč„용에 ëč„핎서 상 
ë‹č히 높은 시임. 
ꎀ렚 낎부 개발 읞렄을 ëłŽìœ í•œ êČœìš° 시임 진입읎 볎닀 ìœ ëŠŹ. 
This information is confidential and was prepared by G-Cube solely for the use of our client and investor; it is not to be relied on by any 3rd party without G-Cube's prior written consent SEO 141028-IR-Business proposal v05 8
G-Cube OpenStack Solution의 시임 예상 
‱ 적용읎 (ë‹č임) 힘든 시임 
-Public cloud infra provider 
Amazon Web Service, Google Cloud Service, Microsoft Cloud Service
 
궁ê·č적읞 시임 êČœìŸìž. 
서ëč„슀 ì‚Źìš©ìžì™€ ì œêł”ìžê°€ loosely-coupled 또는 ë¶„ëŠŹëœ scale-out data storage 
service 환êČœì„ economics of scale에 의핎 ëč„ìš© íššìœšì ìœŒëĄœ ì œêł”. (e.g., 대용량 ë°° 
ì†Ą 서ëč„슀) 
Ʞ업형 cloud 분알에서 QoS에 따넞 node/storage ê”Źì„±ì„ ë‹Źì„±. (e.g., íŠč꞉ ë°°ì†Ą 서 
ëč„슀) 
-Enterprise storage market 
Oracle, SAP. 
ACID와 같은 높은 데읎터 ì‹ ëą°ë„ê°€ 쀑요. 
였랜 êž°ê°„ 동안 êČ€ìŠëœ 서ëč„슀 및 제품에 대한 안정성 references가 ëłŽìž„ë˜ì–Žì•Œ 진 
입읎 용읎. 
This information is confidential and was prepared by G-Cube solely for the use of our client and investor; it is not to be relied on by any 3rd party without G-Cube's prior written consent SEO 141028-IR-Business proposal v05 9
G-Cube OpenStack Layers 
cluster/cloud frame works, applications 
osd virtualization 
- cluster : Portal 
local resource mgmt : repository 
osd device : container 
block device driver nvme driver 
-key - value system 
-big data analysis 
-global file system 
etc. 
- network을 톔핎 닀수의 osd device넌 í†”í•©ì œêł” 
- local osd device와 음ꎀ된 interface넌 톔핎 속성,상태 
등 의 query, set을 ì œêł”(storage 읎왞의 network등의 정 
볎 추가) 
- local osd device의 정의 ëČ”ìœ„ì— 따띌서는 닚순한 map 
ping 만 수행하는 layer로 축소될 수 있음 
-닀수의 device넌 ëŹ¶ì–Ž ì œêł”. 
-정핎진 data 속성에 따띌 device 활용 
-하부 device의 속성, 상태 및 data 속성에 따넞 동작 
등을 query, set 
cluster boundary 
single node boundary 
virtual storage boundary 
physical storage boundary 
memory, cpu 등 storage 
뿐 아니띌 node resource 
넌 í†”í•©í•˜ì—Ź, êŽ€ëŠŹí•˜ë©° 
핮ë‹č resource넌 읎용한 
service ì œêł” ( caching 등) 
storage hardware (memory, SSD, HDD) 
This information is confidential and was prepared by G-Cube solely for the use of our client and investor; it is not to be relied on by any 3rd party without G-Cube's prior written consent SEO 141028-IR-Business proposal v05 10
Layers & their key roles 
portal (dock) 
repository 
container 
device 
 coordination 
 cluster-level 
 namespace (object – node) 
 network 
 distributed functions 
 scheduler 
 local resource management 
 node-level 
 local functions 
 namespace (object – container) 
 scheduler 
 local storage management 
 device-level 
 namespace (object - LBNs) 
 representing a block device file which can represent 
hdd/ssd/ramdisk , array, networked device, 
logical volume, partition, and so on. 
 talk to container with a feature set 
This information is confidential and was prepared by G-Cube solely for the use of our client and investor; it is not to be relied on by any 3rd party without G-Cube's prior written consent SEO 141028-IR-Business proposal v05 11
Service data description & parameter flow 
streaming avi 
portal 
cache가 ëčšëŒì•Œí•˜êł . m 
ulti user access 넌 êł ë € 
하멎 network도.. 
repository 
sequential, mul 
ti read, large! 
íŹêž°ë§Œ 신êČœì“° 
멎되넀.. 귞럌 
싌 HDD로.. 
large!! 
난 cache도 컀서 sequential multi re 
ad는 I/O 별로 안핎도 되니, 용량만 
큰데로 ë„ŁìœŒë©Ž 되êČ ë„€ 
container 
This information is confidential and was prepared by G-Cube solely for the use of our client and investor; it is not to be relied on by any 3rd party without G-Cube's prior written consent SEO 141028-IR-Business proposal v05 12
Operating Scenario - Terms 
from the point of not only 
performance such as 
responsiveness, throughput, but also 
functionality like reliability, 
continuity, and functionality 
Node boundary 
container boundary 
status 
Container is a virtual storage device 
which can be represented as one 
dimensional array as follows 
- a single device (SSD, HDD, 
Ramdisk) 
- a bunch of disks (e.g. disk array) 
- hybrid storage (DRAM, SSD, HDD) 
- and their networking storage 
Tenant is an agent (module) who 
has one or more data I/O streams 
as follows 
- Application (mobile, PC) 
- Server (WAS, DB) and its I/O 
agents (WAS cgi-bin module, DB 
storage engine, logging module) 
- VM Hypervisor I/O module 
- server-side I/O agent in NAS 
and SAN 
- Filesystem server I/O agent 
- 
 
This information is confidential and was prepared by G-Cube solely for the use of our client and investor; it is not to be relied on by any 3rd party without G-Cube's prior written consent SEO 141028-IR-Business proposal v05 13
DATA IN/OUT Requirement (êž°ìĄŽ 방식) 
tenant 
(user, 
server) 
status 
data data data data 
data in/out 
(rw) 
슀토지와 data 맀핑 Ʞ쀀 : falut-resilience & load-balance & size 
mapper가 볮는 node 
containers의 위상 := 
flat 
This information is confidential and was prepared by G-Cube solely for the use of our client and investor; it is not to be relied on by any 3rd party without G-Cube's prior written consent SEO 141028-IR-Business proposal v05 14
DATA IN/OUT Requirement (êž°ìĄŽ 방식) 
tenant 
(user, 
server) 
data in/out data data data data 
(rw) 
status 
cluster container의 
위상 (e.g., In multi-apects, 
read 
responsiveness ) 
mapping considerations: falut-resilience & load-balance & ? 
(mapping takes no advantage of status per container even if it is known) 
e.g. HDD 
e.g. Ramdisk 
e.g. SSD 
This information is confidential and was prepared by G-Cube solely for the use of our client and investor; it is not to be relied on by any 3rd party without G-Cube's prior written consent SEO 141028-IR-Business proposal v05 15
DATA IN/OUT Requirement (êž°ìĄŽ 방식) 
tenant 
(user, 
server) 
data in/out data data data data 
(rw) 
status 
mapping considerations: falut-resilience & load-balance & ? 
(mapping takes no advantage of status per container even if it is known) 
tenants가 ìš”ê”Źí•˜ëŠ” 
read responsivenss 
의 위상 over-statisfied 
unstatisfied unstatisfied 
over-statisfied statisfied 
This information is confidential and was prepared by G-Cube solely for the use of our client and investor; it is not to be relied on by any 3rd party without G-Cube's prior written consent SEO 141028-IR-Business proposal v05 16
DATA IN/OUT Requirement (G-Cube approach) 
tenant 
(user, 
server) 
data in/out data data data data 
(rw) 
status 
mapping considerations: falut-resilience & load-balance & in/out requirement from 
tenants (schedule) 
tenants가 ìš”ê”Źí•˜ëŠ” 
read responsivenss 
의 위상 
All-statisfied 
This information is confidential and was prepared by G-Cube solely for the use of our client and investor; it is not to be relied on by any 3rd party without G-Cube's prior written consent SEO 141028-IR-Business proposal v05 17
G-Cube OpenStack Interfaces 
portal 
repository 
container 
device 
Local interfaces Remote interfaces 
block others openstack block others openstack 
block 
interfaces 
POSIX file 
interfaces, 
RESTful API, 
key-value, 
Swift
 
dynamic field 
interfaces (like 
stub) 
ioctl (network) 
block interfaces POSIX file 
interfaces, 
RESTful API, 
key-value, 
Swift
 
dynamic field 
interfaces (like 
stub) 
ioctl (network) 
block openstack block openstack 
block interfaces dynamic field interfaces 
(like stub) 
ioctl 
block interfaces 
(SAN) 
dynamic field interfaces 
(like stub) 
ioctl 
block openstack block openstack 
block device file 
(bio interface) 
SAN 
dynamic field interfaces 
(like stub) 
ioctl 
block device file dynamic field interfaces 
(like stub) 
ioctl 
block osd block osd 
block device file 
(bio interface) 
ioctl N/A N/A 
This information is confidential and was prepared by G-Cube solely for the use of our client and investor; it is not to be relied on by any 3rd party without G-Cube's prior written consent SEO 141028-IR-Business proposal v05 18
G-Cube OpenStack Data Description 
‱ Service level에서의 data description 
-Sequentiality vs Randomness in IO system 
Service level의 data에서는 sequential, random 의 접귌읎 닚순히 I/O 뿐만 아니띌 
processing의 ì˜ëŻžë„ 듀얎감. 
Sequential : streaming , image (single), contents body 와 같읎 전ìČŽ data넌 ìČ˜ìŒ 
부터 읜얎서 service하는 ìą…ë„˜ë“€ 
Random : VOD (player의 메뉎상 tracker넌 마우슀 ë“±ìœŒëĄœ 찍얎서 움직읎는 êČƒë“€. 
youtube 등), image set 
-Concurrency: 닚음 data에 대한 sequential ì ‘ê·Œ 뿐 아니띌, 동음 key í˜č은 
type에 대한 ì ‘ê·Œ 방식 또한 정의넌 í•„ìš”ëĄœ 핹. 
e.g., Prefetching. 
-BLOB: Data 접귌의 íŠč읎성읎 없거나 파악읎 힘든 êČœìš° (e.g, 가상 ëšžì‹  guest 
OS image) large-size의 binary object로 ëłŽêł , ìš”ê”Ź ì‚Źí•­ì— 맞êȌ 데읎터넌 ìȘ 
늏. 
-No archive data : service level에서의 data의 êČœìš°, archive data는 거의 ìĄŽìžŹ 
하지 않음. 
archive 의 êČœìš°ëŠ” ëł„ë„ì˜ process넌 톔핎 backup등을 수행핚 
This information is confidential and was prepared by G-Cube solely for the use of our client and investor; it is not to be relied on by any 3rd party without G-Cube's prior written consent SEO 141028-IR-Business proposal v05 19
G-Cube OpenStack Data Description 
‱ G-Cube OpenStack interface ìš”ê”Źì‚Źí•­ : object type에 대한 정의넌 하멎 
서 핮ë‹č type data에 대한 description을 할 수 있얎알 핹 
-e.g. contents title, writer, image thumbnail 등 
‱ Classification: 음반적읞 data type에 대핎서는 믞늏 섞부 parameter넌 
ì •ì˜í•˜ì—Ź, 닚순화된 interface로 ì‚Źìš©í•  수 ìžˆë„ëĄ ì œêł”. 
‱ Service 욎용 수쀀에서 볎멎, 큏êȌ on-line data넌 위한 sequential / 
random I/O & processing 에 대한 정의와 off-line data넌 위한 정의 정도 
로 ëłŒ 수 있음. 
-섞부적읞 ì‚Źí•­ì€ ê°œëł„ service 별 íŠčì§•ìœŒëĄœ ìČ˜ëŠŹí•Žì•Œ 하며, 음반화 불가늄핚. 
This information is confidential and was prepared by G-Cube solely for the use of our client and investor; it is not to be relied on by any 3rd party without G-Cube's prior written consent SEO 141028-IR-Business proposal v05 20
G-Cube OpenStack Data Description 
‱ Considerations 
-data (object) 에 대한 êČƒêłŒ data relation (object type) 에 대한 êČƒìŽ 필요핚 
‱ Application (web?) service data attributes dimensions 
-process isolation in single data (or relative data) : portal layer와 ꎀ렚. 
-number of concurrent access : portal, repository, (container) 
-I/O randomness : portal, repository, container 
-size of data (or relative data) : portal, repository, container 
‱ Application service data 의 êČœìš° storage 에서 ìžìŁŒ 얞꞉하는, read/write pattern 
은 불필요. 
-On-line service 되는 data의 거의 대부분읎 write once, read many의 성êČ©ì„ 가짐. 
-Write-intensive 한 형태의 data는 íŠč정 workload type (logging, transactional DB)ìœŒëĄœ 
ê”Źë¶„í•  수 있음. 
This information is confidential and was prepared by G-Cube solely for the use of our client and investor; it is not to be relied on by any 3rd party without G-Cube's prior written consent SEO 141028-IR-Business proposal v05 21
G-Cube OpenStack Device Features 
‱ êž°ëłžì ìž ìš”ê”Źì‚Źí•­ 
-쎈Ʞ ë‹šêł„ì—ì„œëŠ” ê”ŹìČŽì ìœŒëĄœ 저임 임ìč˜ ë° 녞드의 ì •ëłŽë„Œ êł”ìœ . 
‱ Online parameter extraction 
-êž°ëłžì ìœŒëĄœ 욎용쀑읞 저임 임ìč˜ì— 대핎서 성늄을 onlineìœŒëĄœ 알아낎는 êČƒì€ 힘듬 (위험성 및 
ë‚Žê”Źì„±ì˜ ëŹžì œ 유발). 
-Offline parameter extraction approach: storage device의 modeling parameters넌 offlineìœŒëĄœ 
ì¶”ì¶œí•˜êł  model name에 따넞 추출값을 저임. Vendor별 storage device model읎 많지 않윌 
므로 가늄한 ì ‘ê·Œ ë°©ëČ•ìž„. 
‱ Storage device features 
-Disk model name 
-Type (SSD, Enterprise HDD, ) 
-Interfaces & protocol (SATA, SAS, PCI-E NVME) 
-Performance factors 
Sequential/Random Read/Write, Mixed (70:30). 
Latency/Throughput 
-Reliability factors 
N-device fault tolerant. abstraction of redundancy level. 
SMART features. 
-Capability 
This information is confidential and was prepared by G-Cube solely for the use of our client and investor; it is not to be relied on by any 3rd party without G-Cube's prior written consent SEO 141028-IR-Business proposal v05 22
G-Cube OpenStack Functionality 
‱ Data Functionality (우선 ìˆœìœ„ëł„ ì •ë Źì€ 아님) 
-Replication. 
-High availability. 
-Cache & tiering. 
-Compression. 
-Security. 
-
 
‱ Data functionality는 plug-inìœŒëĄœ ê”Źì„±í•˜ì—Ź data ìš”ê”Ź ì‚Źí•­ì— 맞êȌ 적용가늄한 형 
태로 개발. 
-e.g., Data set A 또는 volume ê”Źì„± 후, 핮ë‹č set읎나 volume에 compression/replication 
Ʞ늄을 ì œêł”í•˜ë„ëĄ ê”Źì„±. 
This information is confidential and was prepared by G-Cube solely for the use of our client and investor; it is not to be relied on by any 3rd party without G-Cube's prior written consent SEO 141028-IR-Business proposal v05 23
G-Cube OpenStack 확임성 
‱ Online Migration. 
-임ëč„의 추가/임애, 녞드의 추가/임애 등을 êł ë €í•œ ì„€êł„ 및 개발 
-Scale-up/scale-out êł ë €. 
‱ Scale-out 
-Network bandwidth을 êł ë €í•˜ì˜€ì„ 때, OpenStack solutions의 scale-out을 위한 가임 큰 
íŠč징은 no central metadata node  client level에서 keyëĄœë¶€í„° determinstic하êȌ 
addressing (hashing)읎 가늄. 
-Multi-dimensional feature set을 êł ë €í–ˆì„ 때, metadata node 없읎 scale-out 한 
storage ê”Źì„±ì„ 위한 data mapping algorithms ì„€êł„ 및 ê”Źí˜„. 
This information is confidential and was prepared by G-Cube solely for the use of our client and investor; it is not to be relied on by any 3rd party without G-Cube's prior written consent SEO 141028-IR-Business proposal v05 24

More Related Content

PDF
IRJET- A Novel and Secure Approach to Control and Access Data in Cloud St...
PDF
Standardizing the Data Distribution Service (DDS) API for Modern C++
PDF
DDS Security
PPT
Wedding.(1)
PPT
Opensource
PDF
Haalehairega patsiendi kasitlus kopsuarsti pilgu labi signe metsla (1)
PPTX
Persuasive speech1
IRJET- A Novel and Secure Approach to Control and Access Data in Cloud St...
Standardizing the Data Distribution Service (DDS) API for Modern C++
DDS Security
Wedding.(1)
Opensource
Haalehairega patsiendi kasitlus kopsuarsti pilgu labi signe metsla (1)
Persuasive speech1

Similar to G cube Openstack solution (20)

PPTX
Server-side optimization for next-generation ssd in G-Cube
 
PDF
[OpenStack Day in Korea 2015] Keynote 2 - Leveraging OpenStack to Realize the...
PDF
Cloud Based Data Warehousing and Analytics
PDF
Microsoft SQL Server 2012 Data Warehouse on Hitachi Converged Platform
PDF
Usage Based Metering in the Cloud (Subscribed13)
PDF
Nrb Mainframe Day z Data and AI - Leif Pedersen
 
PPT
Gssa datacenter solutions
PDF
VMworld 2013: SDDC is Here and Now: A Success Story
PDF
What You Need To Know About The New PCI Cloud Guidelines
PPTX
Pentaho Analytics on MongoDB
PDF
ArchivePod a legacy data solution when migrating to the #CLOUD
PDF
Metadata Lakes for Next-Gen AI/ML - Datastrato
PDF
Whitepaper: Evolution of the Software Defined Data Center - Happiest Minds
PPTX
Gssa datacenter solutions
PPT
Analyst field reports on top 15 MDM solutions - Aaron Zornes (NYC 2021)
PDF
MX Deep Dive PPT
PDF
Red Hat Insights
PPTX
Horizontal Scaling for Millions of Customers!
PDF
2015 Gartner Magic Quadrant Cloud Enabled Managed Hosting
PPTX
IaaS with Software Defined Networking
Server-side optimization for next-generation ssd in G-Cube
 
[OpenStack Day in Korea 2015] Keynote 2 - Leveraging OpenStack to Realize the...
Cloud Based Data Warehousing and Analytics
Microsoft SQL Server 2012 Data Warehouse on Hitachi Converged Platform
Usage Based Metering in the Cloud (Subscribed13)
Nrb Mainframe Day z Data and AI - Leif Pedersen
 
Gssa datacenter solutions
VMworld 2013: SDDC is Here and Now: A Success Story
What You Need To Know About The New PCI Cloud Guidelines
Pentaho Analytics on MongoDB
ArchivePod a legacy data solution when migrating to the #CLOUD
Metadata Lakes for Next-Gen AI/ML - Datastrato
Whitepaper: Evolution of the Software Defined Data Center - Happiest Minds
Gssa datacenter solutions
Analyst field reports on top 15 MDM solutions - Aaron Zornes (NYC 2021)
MX Deep Dive PPT
Red Hat Insights
Horizontal Scaling for Millions of Customers!
2015 Gartner Magic Quadrant Cloud Enabled Managed Hosting
IaaS with Software Defined Networking
Ad

Recently uploaded (20)

PDF
Design an Analysis of Algorithms I-SECS-1021-03
PPTX
Agentic AI Use Case- Contract Lifecycle Management (CLM).pptx
PPTX
Transform Your Business with a Software ERP System
PDF
Internet Downloader Manager (IDM) Crack 6.42 Build 41
PDF
Odoo Companies in India – Driving Business Transformation.pdf
PPTX
assetexplorer- product-overview - presentation
PDF
2025 Textile ERP Trends: SAP, Odoo & Oracle
PDF
System and Network Administration Chapter 2
PDF
Understanding Forklifts - TECH EHS Solution
PDF
Addressing The Cult of Project Management Tools-Why Disconnected Work is Hold...
PDF
PTS Company Brochure 2025 (1).pdf.......
PPTX
Operating system designcfffgfgggggggvggggggggg
PPTX
Agentic AI : A Practical Guide. Undersating, Implementing and Scaling Autono...
PDF
How to Choose the Right IT Partner for Your Business in Malaysia
PPTX
Computer Software and OS of computer science of grade 11.pptx
PPTX
Introduction to Artificial Intelligence
PPTX
Oracle E-Business Suite: A Comprehensive Guide for Modern Enterprises
PDF
Upgrade and Innovation Strategies for SAP ERP Customers
PDF
T3DD25 TYPO3 Content Blocks - Deep Dive by André Kraus
PPTX
Reimagine Home Health with the Power of Agentic AI​
Design an Analysis of Algorithms I-SECS-1021-03
Agentic AI Use Case- Contract Lifecycle Management (CLM).pptx
Transform Your Business with a Software ERP System
Internet Downloader Manager (IDM) Crack 6.42 Build 41
Odoo Companies in India – Driving Business Transformation.pdf
assetexplorer- product-overview - presentation
2025 Textile ERP Trends: SAP, Odoo & Oracle
System and Network Administration Chapter 2
Understanding Forklifts - TECH EHS Solution
Addressing The Cult of Project Management Tools-Why Disconnected Work is Hold...
PTS Company Brochure 2025 (1).pdf.......
Operating system designcfffgfgggggggvggggggggg
Agentic AI : A Practical Guide. Undersating, Implementing and Scaling Autono...
How to Choose the Right IT Partner for Your Business in Malaysia
Computer Software and OS of computer science of grade 11.pptx
Introduction to Artificial Intelligence
Oracle E-Business Suite: A Comprehensive Guide for Modern Enterprises
Upgrade and Innovation Strategies for SAP ERP Customers
T3DD25 TYPO3 Content Blocks - Deep Dive by André Kraus
Reimagine Home Health with the Power of Agentic AI​
Ad

G cube Openstack solution

  • 1. G-Cube OpenStack Solution G-Cube Inc. This information is confidential and was prepared by G-Cube solely for the use of our client and investor; it is not to be relied on by any 3rd party without G-Cube's prior written consent
  • 2. G-Cube OpenStack Solution ‱ Data Defined Storage (DDS) -Integrated data-centric management architecture -Storing, retaining, and accessing data based on content, meaning, and value. -Core technology Media Independent Data Storage Data Security & Identity Management Distributed Metadata Repository http://en.wikipedia.org/wiki/Data_Defined_Storage This information is confidential and was prepared by G-Cube solely for the use of our client and investor; it is not to be relied on by any 3rd party without G-Cube's prior written consent SEO 141028-IR-Business proposal v05 2
  • 3. Software Defined Storage vs Data Defined Storage Software Defined Storage ‱ Storage-centric management ‱ User manages storage. ‱ SDS decribes storage. ‱ Human (should) know -Storage features Data Defined Storage ‱ Data-centric management ‱ User describes data ‱ DDS manages storage ‱ DDS (should) know -Data description This information is confidential and was prepared by G-Cube solely for the use of our client and investor; it is not to be relied on by any 3rd party without G-Cube's prior written consent SEO 141028-IR-Business proposal v05 3
  • 4. In Storage Centric Management Architecture Deliver package 1 until tom orrow, package 2 until this weekend, package 3 until t his month
 what they do Who deliver? by human (admin)  high-cost , low-efficient. This information is confidential and was prepared by G-Cube solely for the use of our client and investor; it is not to be relied on by any 3rd party without G-Cube's prior written consent SEO 141028-IR-Business proposal v05 4
  • 5. In Storage Centric Management Architecture Deliver package 1 until tomorrow, package 2 until this weekend, package 3 until this month
 what they do Who deliver? ‱ automated by existing solutions unsatify This information is confidential and was prepared by G-Cube solely for the use of our client and investor; it is not to be relied on by any 3rd party without G-Cube's prior written consent SEO 141028-IR-Business proposal v05 5
  • 6. In Data Centric Management Architecture Deliver package 1 until tomorrow, package 2 until this weekend, package 3 until this month
 what they do Data description package 1 via airli ne, package 2 by t ruck
 Who deliver? automated & unified management  low-cost & high-efficient  satisfy users! what we(will) do This information is confidential and was prepared by G-Cube solely for the use of our client and investor; it is not to be relied on by any 3rd party without G-Cube's prior written consent SEO 141028-IR-Business proposal v05 6
  • 7. Data Defined Storage의 필요성 ‱ 서ëč„슀 뿐만 아니띌 ìŠ€í† ëŠŹì§€ë„ 더 읎상 flat 하지 않닀. -Multi-Tenant Service New service frameworks: Cloud, VDI, Big-data. Traditional services: DB, WAS, Multimedia... -Multi-Aspect Storage 예전: 시슀템메ëȘšëŠŹ + í•˜ë“œë””ìŠ€íŹ (Enterprise or Personal) 지ꞈ: 메ëȘšëŠŹ + SSD + HDD + cloud storage - ëč„휘발성 메ëȘšëŠŹ 소자(DRAM, NAND Flash, MRAM, FeRAM) 읞터페읎슀/프 ëĄœí† ìœœ (SATA/SAS, PCI-E NVME), 하드웚얎 (SLC/MLC/TLC, rpm, redundancy-level), 위ìč˜ìžì ‘성 (Local DAS, SAN, WAN) ‱ Media Independent Data Storage ì†”ëŁšì…˜ìŽ 필요. -êŽ€ëŠŹìž 및 ì‚Źìš©ìžê°€ ëł”ìžĄí•œ storage íŠč성을 ìŽí•Ží•˜ì—Ź íššìœšì ìœŒëĄœ data넌 mapping하는 êČƒìŽ 불가늄. ‱ Data I/O는 ëŹŽìĄ°ê±Ž êł ì„±ëŠ„ìŽ 아니띌, ì‚Źìš©ìžê°€ 원하는 수쀀에 가임 맞는 데읎터 입출렄 서ëč„슀넌 ì œêł”. -씜소의 ëč„ìš©ìœŒëĄœ 전ìČŽì ìœŒëĄœ 씜적의 service quality넌 ëłŽìž„. This information is confidential and was prepared by G-Cube solely for the use of our client and investor; it is not to be relied on by any 3rd party without G-Cube's prior written consent SEO 141028-IR-Business proposal v05 7
  • 8. G-Cube OpenStack Solution의 시임 예상 ‱ 적용읎 가늄/ëč„ꔐ적 용읎한 시임 -Private cloud provider Game publishers, 쀑소 êž°ì—… 규ëȘšì˜ 가상 ëšžì‹ /VDI 환êČœ, íŹí„žì‚Ź, 대학/Ʞꎀ/êž°ì—… 의 전산섌터. 서ëč„슀 ì‚Źìš©ìžì™€ ì œêł”ìžê°€ 동음 하거나 tightly-coupled 되얎 있얎서 ëč„ìš© 절감읎 나 서ëč„슀 품질 개선을 톔핎서 TOC 감소가 쀑요한 시임. 닀양한 íŠč성의 데읎터 (êČŒìž„ 데읎터, ëž”ëĄœê·ž/홈페읎지, ëŻžë””ì–Ž, ìŽëŻžì§€, ì‚Źìš©ìž/êł  객 êł„ì • 등) 가 톔합 êŽ€ëŠŹë˜êł  있는 환êČœ. -Big data infra, SNS service provider 방대한 양의 데읎터가 ìĄŽìžŹí•˜êł  핮ë‹č 데읎터의 유지 및 êŽ€ëŠŹ ëč„용읎 높음. 데읎터의 ì–‘êłŒ ì‚Źìš©ìž 수가 í­ë°œì ìœŒëĄœ 슝가핚에 따띌 전ìČŽ 서ëč„슀 질 저하/용량 ë¶€ìĄ±ì— 따넞 임ëč„의 추가 및 확임읎 ëčˆëȈ핹. -TCO나 성늄에 대한 ìš”ê”Ź ì‚Źí•­, ê·žëŠŹêł  scale-out을 위핎서 도입할 임ëč„ ë° ì†”ëŁšì…˜ì˜ ê”Ź ë§€ license ëč„용읎 ìƒˆëĄœìšŽ OpenStack solution 도입을 위한 개발 소요 ëč„용에 ëč„핎서 상 ë‹č히 높은 시임. ꎀ렚 낎부 개발 읞렄을 ëłŽìœ í•œ êČœìš° 시임 진입읎 볎닀 ìœ ëŠŹ. This information is confidential and was prepared by G-Cube solely for the use of our client and investor; it is not to be relied on by any 3rd party without G-Cube's prior written consent SEO 141028-IR-Business proposal v05 8
  • 9. G-Cube OpenStack Solution의 시임 예상 ‱ 적용읎 (ë‹č임) 힘든 시임 -Public cloud infra provider Amazon Web Service, Google Cloud Service, Microsoft Cloud Service
 궁ê·č적읞 시임 êČœìŸìž. 서ëč„슀 ì‚Źìš©ìžì™€ ì œêł”ìžê°€ loosely-coupled 또는 ë¶„ëŠŹëœ scale-out data storage service 환êČœì„ economics of scale에 의핎 ëč„ìš© íššìœšì ìœŒëĄœ ì œêł”. (e.g., 대용량 ë°° ì†Ą 서ëč„슀) Ʞ업형 cloud 분알에서 QoS에 따넞 node/storage ê”Źì„±ì„ ë‹Źì„±. (e.g., íŠč꞉ ë°°ì†Ą 서 ëč„슀) -Enterprise storage market Oracle, SAP. ACID와 같은 높은 데읎터 ì‹ ëą°ë„ê°€ 쀑요. 였랜 êž°ê°„ 동안 êČ€ìŠëœ 서ëč„슀 및 제품에 대한 안정성 references가 ëłŽìž„ë˜ì–Žì•Œ 진 입읎 용읎. This information is confidential and was prepared by G-Cube solely for the use of our client and investor; it is not to be relied on by any 3rd party without G-Cube's prior written consent SEO 141028-IR-Business proposal v05 9
  • 10. G-Cube OpenStack Layers cluster/cloud frame works, applications osd virtualization - cluster : Portal local resource mgmt : repository osd device : container block device driver nvme driver -key - value system -big data analysis -global file system etc. - network을 톔핎 닀수의 osd device넌 í†”í•©ì œêł” - local osd device와 음ꎀ된 interface넌 톔핎 속성,상태 등 의 query, set을 ì œêł”(storage 읎왞의 network등의 정 볎 추가) - local osd device의 정의 ëČ”ìœ„ì— 따띌서는 닚순한 map ping 만 수행하는 layer로 축소될 수 있음 -닀수의 device넌 ëŹ¶ì–Ž ì œêł”. -정핎진 data 속성에 따띌 device 활용 -하부 device의 속성, 상태 및 data 속성에 따넞 동작 등을 query, set cluster boundary single node boundary virtual storage boundary physical storage boundary memory, cpu 등 storage 뿐 아니띌 node resource 넌 í†”í•©í•˜ì—Ź, êŽ€ëŠŹí•˜ë©° 핮ë‹č resource넌 읎용한 service ì œêł” ( caching 등) storage hardware (memory, SSD, HDD) This information is confidential and was prepared by G-Cube solely for the use of our client and investor; it is not to be relied on by any 3rd party without G-Cube's prior written consent SEO 141028-IR-Business proposal v05 10
  • 11. Layers & their key roles portal (dock) repository container device  coordination  cluster-level  namespace (object – node)  network  distributed functions  scheduler  local resource management  node-level  local functions  namespace (object – container)  scheduler  local storage management  device-level  namespace (object - LBNs)  representing a block device file which can represent hdd/ssd/ramdisk , array, networked device, logical volume, partition, and so on.  talk to container with a feature set This information is confidential and was prepared by G-Cube solely for the use of our client and investor; it is not to be relied on by any 3rd party without G-Cube's prior written consent SEO 141028-IR-Business proposal v05 11
  • 12. Service data description & parameter flow streaming avi portal cache가 ëčšëŒì•Œí•˜êł . m ulti user access 넌 êł ë € 하멎 network도.. repository sequential, mul ti read, large! íŹêž°ë§Œ 신êČœì“° 멎되넀.. 귞럌 싌 HDD로.. large!! 난 cache도 컀서 sequential multi re ad는 I/O 별로 안핎도 되니, 용량만 큰데로 ë„ŁìœŒë©Ž 되êČ ë„€ container This information is confidential and was prepared by G-Cube solely for the use of our client and investor; it is not to be relied on by any 3rd party without G-Cube's prior written consent SEO 141028-IR-Business proposal v05 12
  • 13. Operating Scenario - Terms from the point of not only performance such as responsiveness, throughput, but also functionality like reliability, continuity, and functionality Node boundary container boundary status Container is a virtual storage device which can be represented as one dimensional array as follows - a single device (SSD, HDD, Ramdisk) - a bunch of disks (e.g. disk array) - hybrid storage (DRAM, SSD, HDD) - and their networking storage Tenant is an agent (module) who has one or more data I/O streams as follows - Application (mobile, PC) - Server (WAS, DB) and its I/O agents (WAS cgi-bin module, DB storage engine, logging module) - VM Hypervisor I/O module - server-side I/O agent in NAS and SAN - Filesystem server I/O agent - 
 This information is confidential and was prepared by G-Cube solely for the use of our client and investor; it is not to be relied on by any 3rd party without G-Cube's prior written consent SEO 141028-IR-Business proposal v05 13
  • 14. DATA IN/OUT Requirement (êž°ìĄŽ 방식) tenant (user, server) status data data data data data in/out (rw) 슀토지와 data 맀핑 Ʞ쀀 : falut-resilience & load-balance & size mapper가 볮는 node containers의 위상 := flat This information is confidential and was prepared by G-Cube solely for the use of our client and investor; it is not to be relied on by any 3rd party without G-Cube's prior written consent SEO 141028-IR-Business proposal v05 14
  • 15. DATA IN/OUT Requirement (êž°ìĄŽ 방식) tenant (user, server) data in/out data data data data (rw) status cluster container의 위상 (e.g., In multi-apects, read responsiveness ) mapping considerations: falut-resilience & load-balance & ? (mapping takes no advantage of status per container even if it is known) e.g. HDD e.g. Ramdisk e.g. SSD This information is confidential and was prepared by G-Cube solely for the use of our client and investor; it is not to be relied on by any 3rd party without G-Cube's prior written consent SEO 141028-IR-Business proposal v05 15
  • 16. DATA IN/OUT Requirement (êž°ìĄŽ 방식) tenant (user, server) data in/out data data data data (rw) status mapping considerations: falut-resilience & load-balance & ? (mapping takes no advantage of status per container even if it is known) tenants가 ìš”ê”Źí•˜ëŠ” read responsivenss 의 위상 over-statisfied unstatisfied unstatisfied over-statisfied statisfied This information is confidential and was prepared by G-Cube solely for the use of our client and investor; it is not to be relied on by any 3rd party without G-Cube's prior written consent SEO 141028-IR-Business proposal v05 16
  • 17. DATA IN/OUT Requirement (G-Cube approach) tenant (user, server) data in/out data data data data (rw) status mapping considerations: falut-resilience & load-balance & in/out requirement from tenants (schedule) tenants가 ìš”ê”Źí•˜ëŠ” read responsivenss 의 위상 All-statisfied This information is confidential and was prepared by G-Cube solely for the use of our client and investor; it is not to be relied on by any 3rd party without G-Cube's prior written consent SEO 141028-IR-Business proposal v05 17
  • 18. G-Cube OpenStack Interfaces portal repository container device Local interfaces Remote interfaces block others openstack block others openstack block interfaces POSIX file interfaces, RESTful API, key-value, Swift
 dynamic field interfaces (like stub) ioctl (network) block interfaces POSIX file interfaces, RESTful API, key-value, Swift
 dynamic field interfaces (like stub) ioctl (network) block openstack block openstack block interfaces dynamic field interfaces (like stub) ioctl block interfaces (SAN) dynamic field interfaces (like stub) ioctl block openstack block openstack block device file (bio interface) SAN dynamic field interfaces (like stub) ioctl block device file dynamic field interfaces (like stub) ioctl block osd block osd block device file (bio interface) ioctl N/A N/A This information is confidential and was prepared by G-Cube solely for the use of our client and investor; it is not to be relied on by any 3rd party without G-Cube's prior written consent SEO 141028-IR-Business proposal v05 18
  • 19. G-Cube OpenStack Data Description ‱ Service level에서의 data description -Sequentiality vs Randomness in IO system Service level의 data에서는 sequential, random 의 접귌읎 닚순히 I/O 뿐만 아니띌 processing의 ì˜ëŻžë„ 듀얎감. Sequential : streaming , image (single), contents body 와 같읎 전ìČŽ data넌 ìČ˜ìŒ 부터 읜얎서 service하는 ìą…ë„˜ë“€ Random : VOD (player의 메뉎상 tracker넌 마우슀 ë“±ìœŒëĄœ 찍얎서 움직읎는 êČƒë“€. youtube 등), image set -Concurrency: 닚음 data에 대한 sequential ì ‘ê·Œ 뿐 아니띌, 동음 key í˜č은 type에 대한 ì ‘ê·Œ 방식 또한 정의넌 í•„ìš”ëĄœ 핹. e.g., Prefetching. -BLOB: Data 접귌의 íŠč읎성읎 없거나 파악읎 힘든 êČœìš° (e.g, 가상 ëšžì‹  guest OS image) large-size의 binary object로 ëłŽêł , ìš”ê”Ź ì‚Źí•­ì— 맞êȌ 데읎터넌 ìȘ 늏. -No archive data : service level에서의 data의 êČœìš°, archive data는 거의 ìĄŽìžŹ 하지 않음. archive 의 êČœìš°ëŠ” ëł„ë„ì˜ process넌 톔핎 backup등을 수행핚 This information is confidential and was prepared by G-Cube solely for the use of our client and investor; it is not to be relied on by any 3rd party without G-Cube's prior written consent SEO 141028-IR-Business proposal v05 19
  • 20. G-Cube OpenStack Data Description ‱ G-Cube OpenStack interface ìš”ê”Źì‚Źí•­ : object type에 대한 정의넌 하멎 서 핮ë‹č type data에 대한 description을 할 수 있얎알 핹 -e.g. contents title, writer, image thumbnail 등 ‱ Classification: 음반적읞 data type에 대핎서는 믞늏 섞부 parameter넌 ì •ì˜í•˜ì—Ź, 닚순화된 interface로 ì‚Źìš©í•  수 ìžˆë„ëĄ ì œêł”. ‱ Service 욎용 수쀀에서 볎멎, 큏êȌ on-line data넌 위한 sequential / random I/O & processing 에 대한 정의와 off-line data넌 위한 정의 정도 로 ëłŒ 수 있음. -섞부적읞 ì‚Źí•­ì€ ê°œëł„ service 별 íŠčì§•ìœŒëĄœ ìČ˜ëŠŹí•Žì•Œ 하며, 음반화 불가늄핚. This information is confidential and was prepared by G-Cube solely for the use of our client and investor; it is not to be relied on by any 3rd party without G-Cube's prior written consent SEO 141028-IR-Business proposal v05 20
  • 21. G-Cube OpenStack Data Description ‱ Considerations -data (object) 에 대한 êČƒêłŒ data relation (object type) 에 대한 êČƒìŽ 필요핚 ‱ Application (web?) service data attributes dimensions -process isolation in single data (or relative data) : portal layer와 ꎀ렚. -number of concurrent access : portal, repository, (container) -I/O randomness : portal, repository, container -size of data (or relative data) : portal, repository, container ‱ Application service data 의 êČœìš° storage 에서 ìžìŁŒ 얞꞉하는, read/write pattern 은 불필요. -On-line service 되는 data의 거의 대부분읎 write once, read many의 성êČ©ì„ 가짐. -Write-intensive 한 형태의 data는 íŠč정 workload type (logging, transactional DB)ìœŒëĄœ ê”Źë¶„í•  수 있음. This information is confidential and was prepared by G-Cube solely for the use of our client and investor; it is not to be relied on by any 3rd party without G-Cube's prior written consent SEO 141028-IR-Business proposal v05 21
  • 22. G-Cube OpenStack Device Features ‱ êž°ëłžì ìž ìš”ê”Źì‚Źí•­ -쎈Ʞ ë‹šêł„ì—ì„œëŠ” ê”ŹìČŽì ìœŒëĄœ 저임 임ìč˜ ë° 녞드의 ì •ëłŽë„Œ êł”ìœ . ‱ Online parameter extraction -êž°ëłžì ìœŒëĄœ 욎용쀑읞 저임 임ìč˜ì— 대핎서 성늄을 onlineìœŒëĄœ 알아낎는 êČƒì€ 힘듬 (위험성 및 ë‚Žê”Źì„±ì˜ ëŹžì œ 유발). -Offline parameter extraction approach: storage device의 modeling parameters넌 offlineìœŒëĄœ ì¶”ì¶œí•˜êł  model name에 따넞 추출값을 저임. Vendor별 storage device model읎 많지 않윌 므로 가늄한 ì ‘ê·Œ ë°©ëČ•ìž„. ‱ Storage device features -Disk model name -Type (SSD, Enterprise HDD, ) -Interfaces & protocol (SATA, SAS, PCI-E NVME) -Performance factors Sequential/Random Read/Write, Mixed (70:30). Latency/Throughput -Reliability factors N-device fault tolerant. abstraction of redundancy level. SMART features. -Capability This information is confidential and was prepared by G-Cube solely for the use of our client and investor; it is not to be relied on by any 3rd party without G-Cube's prior written consent SEO 141028-IR-Business proposal v05 22
  • 23. G-Cube OpenStack Functionality ‱ Data Functionality (우선 ìˆœìœ„ëł„ ì •ë Źì€ 아님) -Replication. -High availability. -Cache & tiering. -Compression. -Security. -
 ‱ Data functionality는 plug-inìœŒëĄœ ê”Źì„±í•˜ì—Ź data ìš”ê”Ź ì‚Źí•­ì— 맞êȌ 적용가늄한 형 태로 개발. -e.g., Data set A 또는 volume ê”Źì„± 후, 핮ë‹č set읎나 volume에 compression/replication Ʞ늄을 ì œêł”í•˜ë„ëĄ ê”Źì„±. This information is confidential and was prepared by G-Cube solely for the use of our client and investor; it is not to be relied on by any 3rd party without G-Cube's prior written consent SEO 141028-IR-Business proposal v05 23
  • 24. G-Cube OpenStack 확임성 ‱ Online Migration. -임ëč„의 추가/임애, 녞드의 추가/임애 등을 êł ë €í•œ ì„€êł„ 및 개발 -Scale-up/scale-out êł ë €. ‱ Scale-out -Network bandwidth을 êł ë €í•˜ì˜€ì„ 때, OpenStack solutions의 scale-out을 위한 가임 큰 íŠč징은 no central metadata node  client level에서 keyëĄœë¶€í„° determinstic하êȌ addressing (hashing)읎 가늄. -Multi-dimensional feature set을 êł ë €í–ˆì„ 때, metadata node 없읎 scale-out 한 storage ê”Źì„±ì„ 위한 data mapping algorithms ì„€êł„ 및 ê”Źí˜„. This information is confidential and was prepared by G-Cube solely for the use of our client and investor; it is not to be relied on by any 3rd party without G-Cube's prior written consent SEO 141028-IR-Business proposal v05 24