<!DOCTYPE article PUBLIC "-//NLM//DTD JATS (Z39.96) Journal Archiving and Interchange DTD v1.0 20120330//EN" "JATS-archivearticle1.dtd">
<article xmlns:xlink="http://www.w3.org/1999/xlink">
  <front>
    <journal-meta />
    <article-meta>
      <title-group>
        <article-title>Semi-Markov Availability Model for Infrastructure as a Service Cloud Considering Hidden Failures of Physical Machines</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Oleg Ivanchenko</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
          <xref ref-type="aff" rid="aff3">3</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Vyacheslav Kharchenko</string-name>
          <email>v_s_kharchenko@ukr.net</email>
          <xref ref-type="aff" rid="aff0">0</xref>
          <xref ref-type="aff" rid="aff1">1</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Yurij Ponochovny</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
          <xref ref-type="aff" rid="aff2">2</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Ivan Blindyuk</string-name>
          <email>ivanblindyuk@mail.ru</email>
          <xref ref-type="aff" rid="aff0">0</xref>
          <xref ref-type="aff" rid="aff3">3</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Oksana Smoktii</string-name>
          <email>oksana.smokty@gmail.com</email>
          <xref ref-type="aff" rid="aff0">0</xref>
          <xref ref-type="aff" rid="aff4">4</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>Key terms: Infrastructure, Mathematical Model, Development</institution>
          ,
          <addr-line>Characteristic</addr-line>
        </aff>
        <aff id="aff1">
          <label>1</label>
          <institution>National Aerospace University “Kharkiv Aviation Institute”</institution>
          ,
          <addr-line>Kharkiv</addr-line>
          ,
          <country country="UA">Ukraine</country>
        </aff>
        <aff id="aff2">
          <label>2</label>
          <institution>Poltava National Technical University named after Yurij Kondratyuk</institution>
          ,
          <addr-line>Poltava</addr-line>
          ,
          <country country="UA">Ukraine</country>
        </aff>
        <aff id="aff3">
          <label>3</label>
          <institution>University of Customs and Finance</institution>
          ,
          <addr-line>Dnipro</addr-line>
          ,
          <country country="UA">Ukraine</country>
        </aff>
        <aff id="aff4">
          <label>4</label>
          <institution>Vasyl' Stus Donetsk National University</institution>
          ,
          <addr-line>Vinniza</addr-line>
          ,
          <country country="UA">Ukraine</country>
        </aff>
      </contrib-group>
      <abstract>
        <p>Results of researches in different areas of science and technique confirm that an effective route in order to solve important tasks is the possibility of migrating data resource within the cloud. Therefore Cloud Computing services including Infrastructure as a Service Cloud (IaaS Cloud) should have high availability level. It is serious problem, because even large cloud providers face with sudden failures of IaaS Cloud. It comes no surprise, that scientists consider taxonomy of this system on base of using overall underlying components, such as physical machines (PMs) and virtual machines (VMs). However cloud providers should always remember that hidden failures of PMs are one of the main causes of damage for their cloud assets. In this paper we propose approach on base of using Semi-Markov model in order to determine availability level for the IaaS Cloud with Technical State Control System.</p>
      </abstract>
      <kwd-group>
        <kwd>Infrastructure as a Service Cloud</kwd>
        <kwd>sudden and hidden failures of physical machines</kwd>
        <kwd>Semi-Markov availability model</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>-</title>
      <p>Cloud Infrastructure is one of the most widely used model of Cloud Computing.
Therefore modern large cloud providers such as Amazon, Microsoft, Google,
Rackspace need approaches and models for the quantification of reliability level. In
particular, Infrastructure as a Service (IaaS) Cloud provider’s data centers try to
ensure quality of service (QoS) by using different approaches for determining of their
availability level. Significance of issue ensuring of availability of the IaaS Cloud can
hardly be exaggerated.</p>
      <p>
        Moreover additional incentive for cloud providers is transformation of cyber assets
for several important Critical Infrastructures into cloud. According to researches by
Cornell University and Washington State University, group of scientists have made
efforts to develop software platform for Grid Smart energy infrastructure [
        <xref ref-type="bibr" rid="ref1">1</xref>
        ].
Amazon EC2 was used by them in order to perform the cloud computing needs for the
Critical Energy Infrastructure.
      </p>
      <p>
        At the same time nowadays we can describe situation, when number of physical
machines for IaaS Cloud data centers are climbing fast and different scientists try to
help providers control their availability level [
        <xref ref-type="bibr" rid="ref2">2</xref>
        ], [
        <xref ref-type="bibr" rid="ref3">3</xref>
        ]. Most of the scientists usually
prefer to use Markov models in order to solve different tasks for concrete computer
systems, including Cloud Infrastructures. In fact Continuous Time Markov Chains are
main toolkit and predominate among the different mathematical models of availability
and reliability for IaaS Cloud [
        <xref ref-type="bibr" rid="ref4">4</xref>
        ]. Stochastic Petri Nets [
        <xref ref-type="bibr" rid="ref5">5</xref>
        ] also featured heavily in the
list with Reliability Block Diagrams [
        <xref ref-type="bibr" rid="ref6">6</xref>
        ], Fault Trees and Reliability Graphs all among
the best techniques, which researches of cloud computing systems prefer to use.
      </p>
      <p>However researchers have to take into consideration that these types of models
need to describe different events for IaaS Cloud, including sudden and hidden
failures, repairs and monitoring services. We can't afford to ignore issues, that to
relate to the monitoring of technical and information states of different components
for cloud infrastructures. Our researches show, that due to combination of
deterministic and stochastic durations into working cycle of Infrastructure as a
Service Cloud, this availability model can be presented by us as Semi-Markov model.
We will also try to consider solutions for IaaS Cloud on base of benefits added by
description of Semi-Markov process with special states. It gives us a way to conduct
quite deep analysis of IaaS Cloud behavior in different negative situations, involving
accidents of data centers, failures of physical and virtual machines or even DoS and
DDoS attacks. At the same time we won't theorize approaches and techniques that
related to the availability of cloud infrastructure. We will only consider concrete
situation for the IaaS Cloud with definite number of PMs.</p>
      <p>
        In this paper, we consider how to build Semi-Markov availability models for the
IaaS Cloud with three pools of physical machines (PMs) and Technical State Control
System. Note that, IaaS Cloud provider can substitute one machine for another in case
definite PM is failed. PMs are grouped into three pools such as: hot, warm and cold
pools [
        <xref ref-type="bibr" rid="ref7">7</xref>
        ], [
        <xref ref-type="bibr" rid="ref8">8</xref>
        ].
      </p>
      <p>Rest parts of this paper are organized as follows. In Section 2 a special approach
for availability analysis of IaaS Cloud with three multiple pools is described by us,
considering sudden and hidden failures of PMs. Final Section 3 introduces the
conclusions statement of our researches.</p>
    </sec>
    <sec id="sec-2">
      <title>Statement of the Researches Results</title>
      <sec id="sec-2-1">
        <title>2.1 Approach for Availability Analysis of IaaS Cloud</title>
        <p>
          We will not try describing concrete architecture for IaaS Cloud, but we will consider
that user has access to IaaS Cloud. At the same time we assume that IaaS Cloud
consists of three pools of PMs. According to the research, three pools of PMs allow to
reduce infrastructure cost, cooling cost and power consumption of IaaS Cloud [
          <xref ref-type="bibr" rid="ref9">9</xref>
          ].
        </p>
        <p>
          The approach uses the means of failure detection that two main components could
employ. First component is Resource Provisioning Decision Engine (RPDE) by which
the pools implement capture the resource provisioning decision process [
          <xref ref-type="bibr" rid="ref10">10</xref>
          ]. As
second component that are functioned in system, namely, Technical State Control
System (TSCS), which is working in monitoring and diagnostic modes [
          <xref ref-type="bibr" rid="ref8">8</xref>
          ]. Perhaps
inspired by necessity of through high availability level maintenance, cloud providers
will get possibilities for effective repair and migration of physical resources (PMs).
Figure 1 shows the taxonomy model for availability analysis of IaaS Cloud.
        </p>
        <p>
          As this taxonomy (Fig. 1) shows, that provider has to consider different regimes
and operational time of TSCS in order to ensure high availability level of the IaaS
Cloud. Furthermore, researchers must build mathematical availability models for IaaS
Cloud considering different types of physical machine’s failures. In [
          <xref ref-type="bibr" rid="ref11">11</xref>
          ], the authors
presented data about several typical cloud services’ downtime. In particular, they
calculated that in 2011 year Amazon cloud services downtime equals about 8,5 days
and the corresponding availability was about 97,67%. This information teaches us,
how to analyze, what is causing the downtime of cloud services. Results of analysis
have shown that hidden failures of PMs is one the most important causes of the IaaS
Cloud downtime.
        </p>
        <p>
          Turning to building of models, we will look at specific type of models that is
Semi-Markov models with special states. Let's look now at overall methods of
solution tasks to assess the IaaS Cloud availability level. Research has shown that in
order to solve different tasks we propose to enhance the State Space Modeling
Taxonomy [
          <xref ref-type="bibr" rid="ref12">12</xref>
          ], [
          <xref ref-type="bibr" rid="ref13">13</xref>
          ] with new type of Semi-Markov models. Semi-Markov
regenerative process is described by this type of models. In fact we can characterize
these models, that relate tо the Semi-Markov birth-death processes.
        </p>
        <p>So far, we have tried to use state-space models for monolithic cloud computing
system, but not for separate components of IaaS Cloud. It was serious problem,
because this model couldn't give accurate assessments for whole system. Now we can
obtain the availability allocation for all IaaS Cloud and for concrete PM using
SemiMarkov modeling approach, by which cloud provider determines possibilities of their
own resources in working environment. As an illustrative example, sudden and
hidden failures for IaaS Cloud with three pools of PMs and TSCS will be considered
by us.</p>
      </sec>
      <sec id="sec-2-2">
        <title>2.2 Analytical and Stochastic Availability Model for an IaaS Cloud Considering</title>
      </sec>
      <sec id="sec-2-3">
        <title>Hidden Failures of PMs</title>
        <p>The case study chosen is a model of IaaS Cloud. Figure 2 shows finite graph for
Semi-Markov model of the IaaS Cloud with three PMs.</p>
        <p>Fig. 2. Semi-Markov availability model of the IaaS Cloud with three PMs
In Fig. 2, if three PMs fail, the cloud computing system becomes unavailable. State
S7 is unavailable state of IaaS Cloud. Obviously the IaaS Cloud becomes available,
when the model enters states S0 ,S2 ,S3 ,S5 . In state S0 three PMs are operational. At
the same time states S2 and S3 are states with two operational PMs. Then state S5 is
state with one operational PM. From now available states are yellow, whereas
unavailable states are red and states of TSCS are green.</p>
        <p>
          Suppose our IaaS Cloud works throughout a particular time with operated duration
t 0,T  . We use the following assumptions and limitations for our modeling
process.
 Hot, warm, and cold PMs are identical PMs [
          <xref ref-type="bibr" rid="ref4">4</xref>
          ]. Provider can do replacement of
failed hot PM by available warm or cold PM, respectively.
 Solution for this model can be obtained when replacement process of PMs is
instantaneous. It means that we consider immediate transitions.
 IaaS Cloud provider can perform technical state control (CTS) of hot PM. The
duration of this interval is  с .
 Overall effect several types of possible failures in PMs with an aggregated mean
time to failure (MTTF) is considered here [
          <xref ref-type="bibr" rid="ref14">14</xref>
          ]. We also use assumptions that all
times to failures for all PMs are exponentially distributed. Despite the fact that hot,
warm and cold PMs have different operating time in order to simplify modeling
process, we will suppose that MTTF 1 s can be represented as equal values.
Apparently, it is reasonable to consider case for three hot, warm and cold PMs
( nh  nw  nc  1 ), when MTTF 1  s  1  sh  1  sw , where sudden failure rates
sh for hot PM and sudden failure rates sw for warm PM.
 IaaS Cloud provider haven’t enough time in order to perform repair operations for
failed PMs. Therefore we need to take into consideration that all times to repair are
not exponentially distributed. We use Erlang-k distribution in preference to
exponential distribution, where k  2 [
          <xref ref-type="bibr" rid="ref15">15</xref>
          ]. We also assume that mean time to
repair (MTTR) of warm PM 1 w is higher than MTTR of hot PM 1 h by a
factor of two.
 Specific feature of architecture for IaaS Cloud is implementation of migration
process of PMs. We consider the migration operations of physical machines as
operations to restore the working capacity of warm and hot PMs with repair rates
 w and  h , respectively.

        </p>
        <p>We assume that hot and warm PMs can fail due to the occurrence of hidden
failures with rates h   hh  hw . In this case MTTF equals 1 h  1 hh  1 hw
for hot and warm PMs, respectively. Hidden unavailable hot or warm PM will
repair after next CTS with rate h .
 IaaS Cloud becomes unavailable when the SM model enters the state S7 .</p>
        <p>
          According to the Fig. 2, our IaaS Cloud is processing workload into the states S0
(at the initial moment t  0 ), S2 , S3 and S5 , that is available sub-set space S A1 for
IaaS Cloud was created by states S A1  S0 ,S2 ,S3 ,S5 . Other states for IaaS Cloud can
be described as: a) CTS sub-set space SCTS  S1 ,S4 ,S6 ,S9 ,S11 ,S13 ; b) unavailable
1
sub-set space SU1A  S7 ,S8 ,S10 ,S12 . In order to solve this task we will employ
analytical and stochastic method on base of using embedded Markov Chains [
          <xref ref-type="bibr" rid="ref8">8</xref>
          ], [
          <xref ref-type="bibr" rid="ref15">15</xref>
          ].
Then steady-state probability vector    0 , 2 , 3 , 5 is solution of this task.
        </p>
        <p>Turning to solution, we will interpret Semi-Markov process as follows. As our
research shows CTS performs deterministic period of time T , therefore transitions
from states Si to states S j are given by:
0,t  T ,
Q01 t  Q24 t  Q34 t  Q56 t  Q89 t  Q1011 t  Q1213 t  
1,t  T .</p>
        <p>At the same time transitions for TSCS from states S j to states Si can be written
as:
0,t  c ,
Q10 t   Q42 t   Q43 t   Q65 t   Q98 t   Q1110 t   Q1312 t   
1,t  c .</p>
        <p>Let we turn now to sudden failures for hot, warm and cold PMs. In this case
distribution function for transitions from state S1 to state S2 , from state S1 to state
S3 , from state S4 to state S5 and from state S6 to state S7 are given by:</p>
        <p>Q12 t   Q13 t   Q45 t   Q67 t   1  est .</p>
        <p>Now we will move on to hidden failures for hot and warm PMs. Distribution
functions for transitions from state S0 to state S8 , from state S2 to state S10 , from
state S3 to state S12 can be written as:
1  еht ,t  T ,
Q08 t   Q210 t   Q312 t   
0,t  T .</p>
        <p>Next distribution functions for hidden unavailable hot or warm PM after next CTS
are given by:</p>
        <p>Q92 t   Q93 t   Q115 t   Q135 t   1  eht .</p>
        <p>Distribution functions of transitions from state S2 to state S0 , from state S3 to
state S0 and from state S7 to state S5 can be written as:</p>
        <p>Q20 ( t )  Q30 ( t )  Q75 ( t )  1  1   ht eht ,</p>
        <p>Simultaneously, distribution functions of transitions from state S5 to state S2 ,
from state S5 to state S3 are given by:</p>
        <p>Q52 ( t )  Q53( t )  1  ( 1   wt )ewt .</p>
        <p>13
i0 i  1
Taking the total probability relation
and taking the steady-state
probability vector, we can compute the required result as</p>
        <p>A  0  2  3  5 ,
where  0 , 2 , 3 , 5 are steady-state probabilities for states S0 ,S2 ,S3 ,S5 .</p>
        <p>In other words, states S0 ,S2 ,S3 ,S5 really are states, when IaaS Cloud can perform
operational required functions. But we also consider others states, when IaaS Cloud
can’t perform a certain amount of useful work. Overall results of IaaS Cloud
modeling based on embedded Markov Chains are shown in Fig. 3 and Fig. 4.</p>
        <p>Fig. 3. Depending of steady-state availability Ah ,T  for T  250 h,
  8 1/h</p>
        <p>Analysis of modeling results confirmed that value of steady-state availability A is
increased by means of increasing of repair rate  of hot PMs and reduction of hidden
failure rate h of hot PMs, as it results by comparing Fig. 3 with Fig. 4.</p>
        <p>Next we will illustrate how to use our stochastic approach in order to describe the
behavior of IaaS Cloud with three pools of PMs. Figure 5 shows finite graph for
second type of Semi-Markov model of the IaaS Cloud with nine PMs. Note that the
model was solved for only one type of hidden failures. It is serious lack, because in
real situation we can observe different types of hidden failures. For example, hidden
failures of hot and warm physical machines can be different.</p>
        <p>In considering the second model, we consider that two different types of hidden
failures of PMs are made possible. Previous study have shown that we can interpret
two branches of hidden failures for PMs using the following probability transitions: 1)
p03 , p711 , p1325 , p819 , p1429 , p2750 , p2239 , p3564 , p5371 , p4261 , p5775 , p7385 , p2447 ,
p4668 , p6782 , p8189 , p8893 , p9297 (first branch for PMs of hot pool); 2) p04 , p816 , p2243 ,
p717 , p1437 , p3558 , p1332 , p2754 , p5378 (second branch for PMs of warm pool).</p>
        <p>According to the Fig. 5, available sub-set space S A2 for second model of IaaS
Cloud was created by states SA2  S0 ,S7 ,S8 ,S13 ,S14 ,S22 ,S24 ,S27 ,S35 ,S42 ,S46 ,S53 ,S57 ,
S67 ,S73 ,S81 ,S88 ,S92. Other states for second Semi-Markov availability model can be
described as unavailable. Then steady-state probability vector    0 ,7 , 8 , 13 , 14 ,
 22 , 24 , 27 , 35 , 42 , 46 , 53 , 57 , 67 ,73 , 81 , 88 , 92 is solution of this task.</p>
        <p>Next we will also move on to hidden failures for hot and warm PMs. Distribution
functions for first branch of transitions can be written as:</p>
        <p>1  е ht ,t  T ,
Qij t   
0,t  T .</p>
        <p>1  е wt ,t  T ,
Qij t  </p>
        <p>0,t  T ,</p>
        <p>
          At the same time distribution functions for second branch of transitions is given
by:
where hidden failure rates of warm PMs  w is lower than hidden failure rates of hot
PMs  h by a factor of two to four [
          <xref ref-type="bibr" rid="ref7">7</xref>
          ].
        </p>
        <p>Distribution functions of transitions for repair time of the hot and warm PMs are
given by:</p>
        <p>Qji ( t )  1  1  hteht</p>
        <p>,
Qji ( t )  1 1 wtewt
,
where repair rate of hot PMs  h is higher than repair rate of warm PMs  w .</p>
        <p>Overall equation for steady-state availability of IaaS Cloud can be written as:
A  0 7  8  13  14  22  24  27  35  42  46  53  57  67 73 
 81  88  92 .
Finally, in spite of the fact that second Semi-Markov model (Fig. 5) is more
complex than first model (Fig. 2), nevertheless we can use similar approach in order
to get solution based on embidded Markov Chains. Nowadays we can allege that it is
one of the most notable advantages of Markovian modeling all among the famous
mathematical methods and stochastic approaches, on which scientific researches for
Cloud Computing area is based.
3</p>
      </sec>
    </sec>
    <sec id="sec-3">
      <title>Conclusions Statement of the Researches Results</title>
      <p>In this paper we performed Semi-Markov modeling for the IaaS Cloud with TSCS
based on embedded Markov Chains. The contributions of this paper are the following.</p>
      <p>The purpose of the model, through the tool implementing it, is studied and used
IaaS Cloud availability measures. It really is the significant assessments for provider.
Indeed sudden and hidden failures of PMs are serious problem for IaaS Cloud
provider. We illustrated these results in an availability Semi-Markov model with fourteen
states.</p>
      <p>Our model can be used in order to make profound analysis of different
architectures for IaaS Cloud, in particular during accidents, disasters and other negative
events, such as DoS and DDoS attack. Several optimization problems for IaaS Cloud
regarding resource availability can be formulated using our analytical and stochastic
model described in this paper.</p>
      <p>In conclusion, increasing scalability and flexibility of this type of models is future
of IaaS Clouds development.</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          1.
          <string-name>
            <surname>Gamage</surname>
            ,
            <given-names>T.</given-names>
          </string-name>
          , et al.
          <article-title>Mission-Critical Cloud Computing for Critical Infrastructures</article-title>
          . Smart Grids: Clouds, Communications, Open Source, and Automation. CRC Press, pp.
          <fpage>1</fpage>
          -
          <lpage>16</lpage>
          (
          <year>2014</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          2.
          <string-name>
            <surname>Birke</surname>
            ,
            <given-names>R.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Chen</surname>
            ,
            <given-names>L. Y.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Smirni</surname>
            ,
            <given-names>E.</given-names>
          </string-name>
          <article-title>Data centers in the cloud: A large scale performance study</article-title>
          .
          <source>Cloud Computing (CLOUD)</source>
          ,
          <source>IEEE 5th International Conference on</source>
          , pp.
          <fpage>336</fpage>
          -
          <lpage>343</lpage>
          (
          <year>2012</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          3.
          <string-name>
            <surname>Patel</surname>
            ,
            <given-names>C.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Shah</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          <article-title>Cost model for planning, development and operation of a data center</article-title>
          .
          <source>HP Laboratories Palo Alto, Tech. Rep</source>
          . (
          <year>2005</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          4.
          <string-name>
            <surname>Ghosh</surname>
            ,
            <given-names>R.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Longo</surname>
            ,
            <given-names>F.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Frattini</surname>
            ,
            <given-names>F.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Russo</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Trivedi</surname>
            ,
            <given-names>K.</given-names>
          </string-name>
          :
          <article-title>Scalable analytics for IaaS cloud availability</article-title>
          .
          <source>In IEEE Transactions on Cloud Computing</source>
          ,
          <volume>2</volume>
          (
          <issue>1</issue>
          ), pp.
          <fpage>57</fpage>
          -
          <lpage>70</lpage>
          (
          <year>2014</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          5.
          <string-name>
            <surname>Silva</surname>
            ,
            <given-names>B.</given-names>
          </string-name>
          :
          <article-title>A framework for availability, performance and survivability evaluation of disaster tolerant cloud computing systems</article-title>
          . Diss. Federal University of Pernambuco (
          <year>2016</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          6.
          <string-name>
            <surname>Matos</surname>
            ,
            <given-names>R.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Araujo</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Oliveira</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Maciel</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Trivedi</surname>
            ,
            <given-names>K.S.</given-names>
          </string-name>
          :
          <article-title>Sensitivity analysis of a hierarchical model of mobile cloud computing</article-title>
          .
          <source>Simulation Modelling Practice and Theory</source>
          , no.
          <issue>50</issue>
          , pp.
          <fpage>151</fpage>
          -
          <lpage>164</lpage>
          (
          <year>2015</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          7.
          <string-name>
            <surname>Ghosh</surname>
            ,
            <given-names>R</given-names>
          </string-name>
          , Longo,
          <string-name>
            <given-names>F.</given-names>
            ,
            <surname>Xia</surname>
          </string-name>
          ,
          <string-name>
            <given-names>R.</given-names>
            ,
            <surname>Naik</surname>
          </string-name>
          ,
          <string-name>
            <given-names>V.</given-names>
            and
            <surname>Trivedi</surname>
          </string-name>
          ,
          <string-name>
            <surname>K.S.</surname>
          </string-name>
          :
          <article-title>Stochastic model driven capacity planning for an infrastructure-as-a-service cloud</article-title>
          .
          <source>In IEEE Transactions on Services Computing</source>
          , vol.
          <volume>7</volume>
          , no.
          <issue>4</issue>
          , pp.
          <fpage>667</fpage>
          -
          <lpage>680</lpage>
          (
          <year>2014</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref8">
        <mixed-citation>
          8.
          <string-name>
            <surname>Ivanchenko</surname>
            ,
            <given-names>O</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Kharchenko</surname>
            ,
            <given-names>V.</given-names>
          </string-name>
          <article-title>Semi-markov availability models for an Infrastructure as a Service Сloud with multiple pools</article-title>
          .
          <source>In Proc. International Conference on ICT in Education, Research, and Industrial Applications</source>
          , pp.
          <fpage>349</fpage>
          -
          <lpage>360</lpage>
          (
          <year>2016</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref9">
        <mixed-citation>
          9.
          <string-name>
            <surname>Longo</surname>
            ,
            <given-names>F</given-names>
          </string-name>
          , Ghosh,
          <string-name>
            <surname>R</surname>
          </string-name>
          , Naik,V.K, Trivedi,
          <string-name>
            <surname>K.S.</surname>
          </string-name>
          <article-title>A scalable availability model for Infrastructure-as-a-Service Cloud</article-title>
          .
          <source>In Proc. The 41st IEEE/IFIP International Conference on Dependable Systems and Networks</source>
          , pp.
          <fpage>335</fpage>
          -
          <lpage>346</lpage>
          (
          <year>2011</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref10">
        <mixed-citation>
          10.
          <string-name>
            <surname>Ghosh</surname>
          </string-name>
          , R.:
          <article-title>Scalable stochastic models for cloud services</article-title>
          .
          <source>Diss</source>
          . Duke of University (
          <year>2012</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref11">
        <mixed-citation>
          11.
          <string-name>
            <surname>Li</surname>
            , Zheng, Liang, Mingfei,
            <given-names>O</given-names>
          </string-name>
          'Brien, Liam, Zhang,
          <string-name>
            <surname>He.</surname>
          </string-name>
          <article-title>The cloud's cloudy moment: A systematic survey of public cloud service outage</article-title>
          .
          <source>arXiv preprint arXiv:1312.6485</source>
          (
          <year>2013</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref12">
        <mixed-citation>
          12.
          <string-name>
            <surname>Trivedi</surname>
            ,
            <given-names>K.S.</given-names>
          </string-name>
          , and
          <string-name>
            <surname>Sahner</surname>
          </string-name>
          , R.:
          <article-title>SHARPE at the age of twenty two</article-title>
          .
          <source>ACM Sigmetrics Performance Evaluation Review</source>
          , vol.
          <volume>36</volume>
          , no.
          <issue>4</issue>
          , pp.
          <fpage>52</fpage>
          -
          <lpage>57</lpage>
          (
          <year>2009</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref13">
        <mixed-citation>
          13.
          <string-name>
            <surname>Cai</surname>
            ,
            <given-names>B.L.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Zhang</surname>
            ,
            <given-names>R.Q.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Zhou</surname>
            ,
            <given-names>X.B.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Zhao</surname>
            ,
            <given-names>L.P.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Li</surname>
            ,
            <given-names>K.Q.</given-names>
          </string-name>
          :
          <article-title>Experience Availability: Tail-Latency Oriented Availability in Software-Defined Cloud Computing</article-title>
          .
          <source>In Journal of Computer Science and Technology</source>
          , vol.
          <volume>32</volume>
          , no.
          <issue>2</issue>
          , pp.
          <fpage>250</fpage>
          -
          <lpage>257</lpage>
          (
          <year>2017</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref14">
        <mixed-citation>
          14.
          <string-name>
            <surname>Lanus</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Yin</surname>
            ,
            <given-names>L.</given-names>
          </string-name>
          , and
          <string-name>
            <surname>Trivedi</surname>
            ,
            <given-names>K.S.</given-names>
          </string-name>
          :
          <article-title>Hierarchical Composition and Aggregation of State-Based Availability and Performability Models</article-title>
          .
          <source>In IEEE Trans. Reliability</source>
          , vol.
          <volume>52</volume>
          , no.
          <issue>1</issue>
          , pp.
          <fpage>44</fpage>
          -
          <lpage>52</lpage>
          (
          <year>2003</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref15">
        <mixed-citation>
          15.
          <string-name>
            <surname>Ivanchenko</surname>
            ,
            <given-names>O.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Lovyagin</surname>
            ,
            <given-names>V.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Maschenko</surname>
            ,
            <given-names>E.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Skatkov</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Shevchenko</surname>
            ,
            <given-names>V.</given-names>
          </string-name>
          :
          <article-title>Distributed critical systems and infrastructures</article-title>
          . National Aerospace University named after N. Zhukovsky “KhAI”,
          <string-name>
            <surname>Kharkiv</surname>
          </string-name>
          (
          <year>2013</year>
          ).
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>