MEICAN: Simplifying DCN Life-Cycle Management from End-User and Operator Perspectives in Inter-Domain Environments

Wickboldt, Juliano Araújo; Guerreiro, Mauricio Quatrin; Granville, Lisandro Zambenedetti; Gaspary, Luciano Paschoal; Schwarz, Marcos; Guok, Chin; Chaniotakis, Vangelis; Lake, Andrew; Macauley, A

doi:10.1109/mcom.2017.1601205

Cited by 2 publications

(1 citation statement)

References 12 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Although these types of federations have a less ad hoc character, there are similar challenges to overcome, like the enforcement of diverse local organizational policies. Wickboldt et al [4] discuss a platform which shortens the time an experienced operator and inexperienced end-users, such as companies, need to provision ad hoc cross-domain network circuits, mainly through the application of easy-to-use visual editors. This scenario closely resembles the case discussed in this article, especially because of the mix of manual and automatic decisions that is inevitably present within ad hoc processes.…”

Section: Related Workmentioning

confidence: 99%

Enabling the Rescheduling of Containerized Workloads in an Ad Hoc Cross-Organizational Collaboration

et al. 2022

View full text Add to dashboard Cite

A group of organizations wishing to collaborate urgently, for example in case of a crisis, need to have a way to quickly deploy applications which enable them to speed up a potentially crisis-resolving decision-making process. A cross-organizational Kubernetes cluster, which is orchestrated by a central operator, allows to initiate these deployments in an ad hoc way. Performance issues may however arise at runtime, for example, a video pipeline belonging to a CCTV camera may produce a too low number of frames per second. The ad hoc cross-organizational collaboration case is especially prone to such issues as the set of candidate nodes and the environment in which they run may not be fully known to the operator. This article therefore motivates and describes the usage of a probe swarm architecture, which allows the operator to quickly generate an overview of the resource capabilities of a set of nodes, by executing code fragments locally. The obtained measurements can then enable the operator to decide on rescheduling operations. Evaluation of an illustrative probe swarm intervention shows that the performance of an example application could improve with factor five, ten or hundred when the pod would be rescheduled. This indicates that the proposed probe swarm architecture may complement other performance bottleneck detection techniques to improve performance of applications that need to be deployed urgently.

show abstract

Section: Related Workmentioning

confidence: 99%