MétaCan
Menu
Back to cohort

Runtime Availability and Service Continuity of Containerized VNF Instances

2023· article· en· W4390188568 on OpenAlexaff
Siamak Azadiabad, Ferhat Khendek, Maria Toeroe

Bibliographic record

Venuenot available
Typearticle
Languageen
FieldComputer Science
TopicSoftware-Defined Networks and 5G
Canadian institutionsEricsson (Canada)Concordia University
Fundersnot available
KeywordsComputer scienceVirtual networkScalabilityHigh availabilityFailure rateDistributed computingVirtualizationComputer networkRedundancy (engineering)Service (business)ProvisioningOperating systemCloud computingReliability engineering

Abstract

fetched live from OpenAlex

A Virtual Network Function (VNF) is a software implementation of a network function (e.g., firewall, router, etc.), which can be deployed as Virtual Machines (VM) utilizing the resources of the infrastructure managed by the Network Function Virtualization (NFV) Management and Orchestration (MANO). A VNF can also be containerized to benefit from the lower virtualization overhead of containers. A containerized VNF is composed of one or more Managed Container Infrastructure Objects (MCIO). To design a Network Service (NS) for the NFV framework that satisfies required service availability and continuity requirements, one has first to determine the availability, failure rate, and service disruption of the VNFs composing the NS. These characteristics of a VNF depend on the availability and failure rate of its MCIOs and the underlying infrastructure. Solutions proposed to determine these VNF characteristics at design time, consider the estimated resource availability and failure rate of a given infrastructure. However, resources assigned to VNF instances at runtime can be different in characteristics and/or performance resulting in a difference between the estimated and the actual characteristics of the VNF instances. In addition, scaling and different placements of the MCIO instances at runtime can have similar effects. Therefore, in this paper, we investigate the parameters affecting the availability, failure rate, and service disruption of a containerized VNF instance, considering the internal redundancy of the VNF and the scalability of its instances at runtime. Based on this investigation, we propose analytical models to determine the availability, failure rate, and service disruption of a containerized VNF instance.

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.

How this classification was reachedexpand

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.000
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: Observational · Consensus signal: Observational
GenreCandidate signal: Empirical · Consensus signal: Empirical
Teacher disagreement score0.360
Threshold uncertainty score0.309

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0000.000
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0000.001
Science and technology studies0.0000.000
Scholarly communication0.0000.000
Open science0.0000.000
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.016
GPT teacher head0.233
Teacher spread0.217 · 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

Classification

machine, unvalidated

Machine predicted; a candidate call from one teacher head, not a consensus.

The models applied no category: nothing in the taxonomy fit this work.
Study designObservational
Domainnot available
GenreEmpirical

How this classification was reached, model by model and score by score, is at the end of the page under "How this classification was reached".

Quick stats

Citations4
Published2023
Admission routes1
Has abstractyes

Explore more

Same topicSoftware-Defined Networks and 5GFrench-language works237,207