Canturk Isci

Canturk Isci

Auto-generated profile, based on publicly available information

Canturk Isci

IBM T.J. Watson Research Center, Ossining, NY, USA

Research Focus & Metrics

Academic Career Length

16Years (2011-Present)

(Calculated once Scilit publication data is synced: current year − year of first publication + 1)

Representative Publications

View All Publications
1 May 2011
Verified
Conference Paper
Closed access
CMChris Mansley
Chris Mansley
JCJonathan Connell
Jonathan Connell
CICanturk Isci
Canturk Isci
JLJonathan Lenchner
Jonathan Lenchner
JKJeffrey O. Kephart
Jeffrey O. Kephart
MSMichael Schappert
Michael Schappert
We describe an inexpensive autonomous robot capable of navigating previously unseen data centers and monitoring key metrics such as air temperature. The robot provides real-time navigation and sensor data to commercial IBM software, thereby enabling real-time generation of the data center layout, a thermal map and other visualizations of energy dynamics. Once it has mapped a data center, the robot can efficiently monitor it for hot spots and other anomalies using intelligent sampling. We demonstrate the robot's effectiveness via experimental studies from two production data centers.

1 March 2016 in IBM Journal of Research and Development
Verified
Journal Article
Closed access
PDF file
FOF. Oliveira
F. Oliveira
TET. Eilam
T. Eilam
PNP. Nagpurkar
P. Nagpurkar
CIC. Isci
C. Isci
MKM. Kalantar
M. Kalantar
ESE. Snible
E. Snible
Cloud computing and the DevOps movement are two pillars that facilitate software delivery with extreme agility. Born on the cloud companies, such as Netflix, have demonstrated rapid growth to their business and continuous improvement to the service they provide, by reportedly applying DevOps principles. In this paper, we claim that to fulfill the vision of fast software delivery, without compromising the quality of the provided services, we need a new approach to detecting problems, including problems that may have occurred during the continuous deployment cycle. A native DevOps-centric approach to problem resolution puts the focus on a wider range of possible error sources (including code commits), makes use of DevOps metadata to clearly define the source of the problem, and leads to a quick problem resolution. We propose such a continuous quality assurance approach, and we demonstrate it by preliminary experiments in our public Container Cloud environment and in a private OpenStack cloud environment.

24 February 2020 in IEEE Transactions on Cloud Computing
Verified
Journal Article
Closed access
ABAnthony Byrne
Anthony Byrne
EAEmre Ates
Emre Ates
ATAta Turk
Ata Turk
VPVladimir Pchelin
Vladimir Pchelin
SDSastry Duri
Sastry Duri
ACAyse K. Coskun
Ayse K. Coskun
With today’s rapidly-evolving cloud landscape embracing continuous integration and delivery, users of cloud systems must monitor software running on their containers and virtual machines (VMs) to ensure compliance, security, and efficiency. Traditional solutions to this problem rely on manually-created rules that identify software installations and modifications, but these require expert authors and are often unmaintainable. Recently, automated techniques for software discovery have emerged. Some techniques use examples of software to train machine learning models to predict which software has been installed on a system. Others leverage the knowledge of packaging practices to aid in discovery without requiring any pre-training, but these practice-based methods cannot provide precise-enough information to perform discovery by themselves. This article introduces Praxi, a new software discovery method that builds upon the strengths of prior approaches by combining the accuracy of learning-based methods with the efficiency of practice-based methods. In tests using samples collected on real-world cloud systems, Praxi correctly classifies installations at least 97.6 percent of the time, while running 14.8 times faster and using 87 percent less disk space than a similar learning-based method. Using a diverse software dataset, this article quantitatively compares Praxi to systematic rule-, learning-, and practice-based methods, and discusses the best uses for each.