MétaCan
Menu
Back to cohort
Record W2293138419 · doi:10.1504/ijhpcn.2016.074656

OCReM: OpenStack-based cloud datacentre resource monitoring and management scheme

2016· article· en· W2293138419 on OpenAlex

Why this work is in the frame

A frame that forgets how it found something cannot be audited. These are the routes that admitted this work.

affAt least one author lists a Canadian institution in the pinned OpenAlex snapshot.

Bibliographic record

VenueInternational Journal of High Performance Computing and Networking · 2016
Typearticle
Languageen
FieldComputer Science
TopicCloud Computing and Resource Management
Canadian institutionsOntario Tech University
Fundersnot available
KeywordsCloud computingComputer scienceOperating systemVirtual machineResource (disambiguation)Resource management (computing)Task (project management)Scheme (mathematics)Interface (matter)Open sourceDistributed computingSoftwareDatabaseComputer networkSystems engineeringEngineering

Abstract

fetched live from OpenAlex

Managing virtualised computing, network and storage resources at large-scale in both public and private cloud datacentres is a challenging task. As an open source cloud operating system, OpenStack needs to be enhanced for managing cloud datacentre resources. In order to improve OpenStack functions to support cloud datacentre resource management, we present OCReM: OpenStack-based cloud datacentre resource monitoring and management scheme. First, we designed a virtual machine group life-cycle management module. Then, we designed and developed a cloud resource monitoring module based on the Nagios monitoring software and Libvirt interface. We conducted an integrated experiment to verify the performance improvement of group-oriented auto scaling and elastic load balancing policy based on real-time resource monitoring data. After that, we implemented the OCReM-EC2 hybrid cloud monitoring and auto scaling model. Finally, we analysed the prospective research direction and propose our future work.

Fetched live from OpenAlex and de-inverted. Abstracts are not stored in this database: the inverted indexes are 8.6 GB of the frame’s 9.3 GB of text, and the host has 13 GB free.

Full frame distilled prediction

Teacher imitation

Not calibrated prevalence, not ground truth. Human validation pending. Learned from the 10,348 direct Codex labels and 10,348 direct Gemma labels. Candidate is the union of thresholded teacher heads; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels or direct frontier model labels.

metaresearch head score (Codex)0.001
metaresearch head score (Gemma)0.000
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesnone
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Other design · Consensus signal: none
GenreCandidate signal: Empirical · Consensus signal: Empirical
Teacher disagreement score0.951
Threshold uncertainty score0.498

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0010.000
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0000.000
Science and technology studies0.0000.000
Scholarly communication0.0000.000
Open science0.0010.001
Research integrity0.0000.000
Insufficient payload (model declined to judge)0.0000.000

Machine scores (provisional)

The two teacher heads of the student model, read on this work. A score orders the frame for review; it never asserts a category, and the validation status ships verbatim with every row.

Baseline scores from an immature model (maturity gate not passed, 7 training rounds). Scores rank; they never assert a category.

Opus teacher head0.014
GPT teacher head0.248
Teacher spread0.234 · how far apart the two teachers sit on this one work
Validation statusscore_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from it