Optimal control of VNF deployment and scheduling

Optimal control of VNF deployment and scheduling

Mark Shifrin, Erez Biton, Omer Gurewitz

Managing network-related resources involves sophisticated trade-off between flexibility, high performance standards, latency demands which adhere to service level agreements (SLAs) and cost constraints. Network functioning virtualization (NFV) opens new challenges to the remote network management which combines activation and control of virtual machines (VMs) according to variable demand. Currently, this functionality is being handled by harnessing the traditional orchestration algorithms using suboptimal heuristics. We model the problem of virtual network function (VNF) allocation by queuing system with flexible number of queues, which captures variety of constraints including queue deployment and displacement, delay cost, holding cost, scheduling reward and fine. Next, we model the system by Markov decision process (MDP) and numerically solve it to find the optimal policy. We show analytically and by simulations that the optimal policy possesses decision thresholds which depend on several parameters.111This research was partially supported by European Union Horizon 2020 Research and Innovation Programme SUPERFLUIDITY, Grant Agreement 671566.

I Introduction

Recent network functioning virtualization (NFV) development suggests that networking-related tasks which previously used to run on-premises will be moved to the cloud, [1].

The breakthrough that the NFV concept represents may cause a paradigm shift for many stakeholders including network operators, solution vendors, service integrators, providers, and service users. However, several issues continue to hinder the management of NFV infrastructure (NFVI) resources. First, the NFV concept has many types of NFVI resource requirements in order to launch requested network services. The NFVI includes not only physical and virtual resources in a single data center but also network resources between multiple data centers. Therefore, software network appliances would be deployed in the NFVI with various hardware and software requirements, quality of service (QoS) provisioning levels, and/or negotiated service level agreements (SLAs).

Enterprise which decides to virtualise any of her network services needs first to deploy (”build”) the corresponding service, in order to be able to run VNF instances. The deployment involves having leased a certain amount of designated hardware, for CPU, memory and networking. Once deployed, the enterprise has to pay per time of usage for the leased resources, even if they are not loaded. The process of deployment can take time, and an additional deployment cost. Hence, having idle resources is undesired. On the other hand, the delay involved with the deployment or lack of space for the new tasks can cause some VNF instances to be rejected from running which would imply a fine to the enterprise. Note that in some cases, the displacement (”destroy”) operation, i.e., the process of releasing the resources can also incur a cost. An additional basic demand is to facilitate scaling of VNF. That is, the amount of virtual resources allocated to a certain VNF is dynamically increased (via a scale out operation) or decreased (scale in operation) according to the demand from the network service (e.g., number of flows a firewall handles). In scale out/in operations, we increase/decrease (i.e., deploy/displace) the number of VMs that are allocated to the VNF, respectively. Note that we do not consider the scale up and down operation, which are less common in NFV use cases. (In scale up/down operation we can, for example, add/remove CPU cores to a given VM). Clearly, increasing the number of VMs allocated to a VNF would improve the performance of the VNF, yet would consume more resources. Accordingly, our scaling decision should minimize the consumed resources, while keeping with the application required SLA. Hence, the decision whether to scale out or in, typically performed by the VNF manager (VNFM), remains an important problem that needs to be addressed, especially in dynamic scenarios.

In conjunction with the scaling decisions, we are also facing a load balancing challenge, steering the traffic flows to the different VMs and balancing the load between them. In this study, we tackle both the scaling decision and the load balancing strategy as a single problem.

The problem which the enterprise has to solve is to find dynamic policy of VM deployment, displacement and scheduling of incoming VNF tasks, as a function of the set of costs and the number of VNF instances currently being served in the already active VMs.

To this end, we model the problem by queuing system with a dynamic (but limited) number queues; each queue stands for VM running VNF instances. We assume that incoming VNF tasks have constant average rate. Upon each arrival event, the Decision Maker (DM) decides to which VM the arriving task should be scheduled, or whether it should be rejected. We allow to deploy a new VM at arrival times, as long as the limit of active VMs is not reached. At departure from a queue (i.e., running of VNF task ends) which has been left empty, DM decides whether to keep that queue alive or to destroy it. In order to reflect the load at busy VMs we introduce a delay cost which (not necessarily linearly) increases with the load. Deployment and displacement of VM consume additional resources represented by corresponding fixed costs. Once a VM was deployed, the enterprise is charged for the reserved resources with fixed per-unit of time reservation and maintenance cost. We term this keep-alive or the holding cost.

The DM aims to find a policy which will maximize total income in the long run. While the set of costs described above implies no trivial policy could exist, some of the parameters have contradicting impacts which may dictate certain properties of the policy. For example, in the case where the delay cost function sharply increases with a load, the DM will attempt to balance the scheduling process among as many VMs as possible. On the other hand, in the case where keep-alive cost is comparatively high, the DM may prioritize minimization of the active queues number.

In this paper, we treat this problem by introducing a control model based on MDP formulation. The solution of the MDP provides the optimal policy. Once applied, the policy reveals the average number of active queues, average number of tasks in each queue. This allows the enterprise to assess the demands and to plan ahead. Moreover, the solution to the MDP is expressed by value function which indicates what are the costs and revenues the enterprise will receive in the long run, for a given VNF scenario, modeled by the corresponding set of parameters.

I-a Related Work

Challenges of VNF scheduling by means of software-defined networks (SDN) were introduced in [2]. Technical details of how the VNF could be deployed are discussed in [3]. Integration of NFV and SDN was also addressed in [4] in the context of 5G mobile core networks. In [5], queue scheduling algorithm named 2DFQ separates requests with different costs and different size across different worker threads. It also extends to the case where the costs are variable or unpredictable. Optimal scheduling in hybrid cloud environment was studied in [6]. The solution provided by the authors employs MDP as well. In [7], joint optimization of NFVI resources under multiple constraints results in approximate algorithm which aims at improving the capability of NFV management and orchestration. This work provides static placement of NFV-related resource. The problem of VNF scheduling, aiming at optimizing the performance latency, was treated by linear programming in [8].

A great deal of work provides results on queue scheduling and optimization problems. Most of works deal with fixed number of queues or queue networks, e.g. [9, 10, 11] or take this number to the limit, e.g. [12, 13, 14] and references therein. However, we treat a specific scenario, where the number of queues is finite but flexible, incorporating unique features of queue destruction and deployment costs. These features correspond to the VNF scheduling which we aim to optimize in the sense of overall cost minimization. Therefore, we develop a model which fits our goal and treat it by MDP.

Ii System Description

We assume our cloud NFV infrastructure (the NFVI) can host a finite yet flexible number of VMs. For simplicity, we assume that an instance of a VNF is deployed in one VM, with two instances deployed in two VMs and so forth. That is, in a scale out operation, adding a VM translates to adding another instance of the VNF. We further assume, that the load balancer is deployed in a single VM and can handle all traffic demands irrespective of the number of VNF instances (i.e., number of VMs), see Figure 1 for the schematic presentation. The total demand of a VNF (e.g., from a firewall) is modeled by Poisson process of arriving tasks with average rate . The incoming tasks are scheduled into one of the active queues or rejected from service, according to load balancing policy. Each VM handles the traffic demands (e.g., flows handled by the firewall) in a parallel manner. Namely, the total processing rate is equally shared between all task. Hence, the tasks never wait but are rather immediately processed. The VM’s limited resources allow processing of limited number of tasks, denoted by . For simplicity, we assume all VMs are identical. We assume each VM has exponential service times with maximal average rate . For simplicity, we assume that service allocation and reallocation in each VM has no time overhead. Since the minimum of exponential rates is equal to their sum, the total processing rate is always equal to . Hence, each VM is modeled by queue with buffer size , having up to servers with total processing rate equal to . While this model reflects the ability of VMs to provide concurrent resource sharing, our model can be easily adopted for the FIFO service, with only minor changes. Note that for the correspondence with the mathematical model, which will follow, we use terms VM and queue interchangeably.

Each admitted task gives a fixed reward, while rejected task incur a fine, denoted by , respectively. Each queue can be deployed and destroyed dynamically, according to the demand. Intuitively, the number of queues may infinitely grow for some sets of parameters. For example, in the case where it holds , while rejected tasks incur high fines. On the other hand, the amount of available queues is expected to be bounded by general system limitations. We will assume henceforth that the number of active queues is limited. Note that in the case where no VM is currently deployed, or the existing VMs (queues) are full, the incoming task is rejected. Hence, in the case deployment time is instantaneous, rejection can be avoided by immediate queue deployment.

Denote the vector of active queues at time by , where is in a state-space denoted by . The components correspond to the number of tasks in queues and are denoted by , where is general indexing of the queues. While for simplicity we assumed , the extension to the system with different processing rates is straightforward. The limit of number of queues is given by , for some system-related given . The queues are limited by , , here state ”” means the queue is inactive. Note that this is different from state which means the queue is active but empty.

Ii-1 Delay cost structure

Denote by the delay cost per unit of processing time, associated with a number of hosted tasks. In particular, at th queue at time the cost equal to per unit of time is inflicted. The delay cost model is represented by function which increases with the number of hosted tasks at VM. This structure reflects a load increase (and ,consequently, the overall queuing time) as the number of residing tasks at VM grows. In particular,


Where for all possible values and is positive increasing with . Namely, more busy VMs function with higher delay. Hence, this cost structure penalizes for having busy VMs. Therefore, the delay cost model captures parallel processing, where the delay cost is considered for every task. Note that if we assume for all , the cost will degenerate to the simple linear model. Observe that delay cost is the lowest, once tasks are equally dispersed over queues.

Fig. 1: System scheme, containing up to VMs with maximal capacity of tasks

In the next section, the MDP problem formulation follows.

Iii MDP formulation

Denote the scheduling vector of length , such that and . The sum is equal to in the case the decision was a rejection. Otherwise, the scheduling decision at is expressed by , for which . The queue activation policy is applied at each task arrival, is described by action vector , , where the possible values for stand for ”deploy”, and ”not deploy”, respectively. The queue destruction policy is applied at each departure event and is described by action vector , , Hence, the action space consists of the triplet .

In what follows we will deal with counting processes of the general form: where is the time between increment (e.g., arrival time, service time) and , for some process . Denote the arrivals counting process as and task completion processes as . Define the following indicator functions:

Definition 3.1 (Queue indicators).


Inactive queue :
Empty but active queue:
Queue with exactly one task:
Full queue:
None of the above (denoted as normal):

The building cost is applied each time a queue is activated. The destroy cost is applied each time a queue is destroyed. In most general form, these actions are allowed to be taken at arrival events and any departure events, that is, once the counting processes and increase. The corresponding cost functional discounted with discount factor , for policy is given by:


where the first part stands for the queue activation cost () and deactivation cost () , the second part stands for queue holding cost () and delay cost () , while the third part stands for the scheduling rewards () and rejection fines (). The cost is otherwise written by its components

The value function associated with initial state is given by

We now write the Bellman equation for a simplified and more realistic scenario assuming that build operations can be only done at arrivals, while destroy operations can be only done at departures. Denote by vector of length with value at th coordinate and zeros in all other coordinates. The Bellman equation reads


where the cost function is calculated by . Note that in the case where all queues are full, the outcome of the inner maximization is empty. In this case, the second term in outer maximization is selected. The derivation of the equation above is in the Appendix -B.

Iv Optimal policy study

Denote two states and , with queue vectors given by and . Define state domination by if and only if . Moreover, we assume that and have the same number of idle queues (this restriction is motivated by the impact of build and destroy costs). We next show the following lemma:

Lemma 4.1 (Value function domination).

For any it holds .


To show the statement define two systems, denoted by and . At time the state of each system is denoted by and . Next, we stochastically couple these systems. Namely, we apply the same policy to both states, denoted as . The policy is optimal for the system , while system mimics all actions from system . In particular, a task which is scheduled in is scheduled in into the same queue. In the case where the rejection applies in both systems, the task is rejected. In the case where there is a forced rejection (that is, the corresponding queue in was full), then it applies to only in the case the same queue was full as well. Each served task departs concurrently from and . In the case where during departure in the same queue in was empty - nothing happens in . The ”destroy” and ”build” decision also follow the same policy and are executed concurrently. (Hence, system will keep alive queues even if empty as long as they are kept in ). Now denote the first time when both states become equal, that is . Clearly, by definition of it holds . Next, as for the rewards in time interval , it holds and as for the fines it holds . Finally, by , all holding costs and costs incurred by build and destroy actions which accumulate to the total cost according to (2) are higher in . Therefore,

Hence, the statement in the lemma follows.∎∎

Denote the average number of tasks, (resp. the variance) in the system, by , (resp. by ). Clearly, for any , such that and , for the optimal policy and partial cost of the form it holds .

To this end, for any define non-negative difference function such that


Note that is non-negative by Lemma 4.1. We now present the following proposition, which states a threshold policy in action ”build”.

Proposition 4.1.

If by optimal policy in state at arrival event it holds , then for all states such that holds .

The proof appears in Appendix -C.

V Numerical results

In this section, we present simulation results which both show additional threshold properties of optimal policies, and provide a comprehensive study of the value functions and the corresponding policies. We explored a system with five identical queues.

Figure 2 demonstrates the impact of the keep-alive queue cost. The simulation was run with negligible delay cost, rejecting fine equal to , and . Buffer limit was tasks. One sees that there is a small region of keep-alive queue cost, where the number of active queues declines. The trade-off in this simulation is the accumulatively paid fine against the accumulatively paid keep-alive queue cost. As long as the queues are identical, there is no preference which queue should be kept idle. That is why the number of active queues declines to zero within a very small interval of keep-alive queue cost. Hence, once it is more affordable to pay the fines by rejecting all incoming tasks rather than maintaining the VMs (i.e., the queues) the queues stay idle at all times.

Fig. 2: Impact of the allocated VNF cost

Figure 3 shows simulation of the delay cost , while the keep-alive cost was fixed equal to , the buffer size of each queue was . The arrival intensity was and . Rejecting fine was equal to . The delay constants were . By cost model in (1), one expects that the tasks will be balanced in the queues. Observe that in this simulation, the keep-alive cost was low enough to allow that. Indeed, all queues were active while the total average number of tasks declined with the delay cost. Observe that in this simulation, the interval of the varying cost was significantly larger. This stems primarily from the fact that is small. Note that the lower graph in both simulations shows the number of rejecting states, out of the states-space.

Additional thresholds can be seen in ”build” and ”destroy” actions. For example, if and/or are high if compared to keep-alive cost, the optimal policy acts to leave all queues active, even if empty.

Fig. 3: Impact of the delay cost

To conclude, the set of system parameters will determine if the optimal policy will prioritize balanced and mostly active queues or a small number of active and comparatively busy queues. The values of and will determine if keeping alive the empty queues is economically reasonable.

V-a Value function presentation and discussion.

The graphical presentation of value function, where is seen in Figure 4. Horizontal axis values stand for states enumeration. See that the function forms large regions. Each region corresponds to the fixed state of . The first region corresponds to being idle, the second region corresponds to being active and empty, etc. Observe that as fills up, the entire corresponding region has lower values. Observe next that each region contains subregions, corresponding to the states of . These subregions also exhibit lower values as fills up. The same drift is identified in other queues.

Fig. 4: Value function - all states

Figures 5,6 demonstrate the closeups of selected sub-regions and states.

Fig. 5: Value function - closeup

Fig. 6: Value function - closeup

-B Derivation of Bellman equation

Note that we assume the deployments only occur at arrivals, while destructions occur only at service ends. Write the cost function as follows:

We take infinitesimal such that only one or no event can happen (probability of more than one is negligible), and use the dynamic programming principle.

Expanding for all options of after the time we have:


We use the following derivation:


where we substituted , i.e. the arrival process. In what follows we use as . Calculate first the time used for a service in the infinitesimal interval .

Next, denote the potential service time process which counts exponentially distributed service times as , Then

Hence, as long as interval is small, write

We can now write the costs incurred in

We now turn to the second term of  (5),

multiply all sides by and mind that .

See that on both sides cancels out and denote . Write:

Divide all by and multiply by

Arrange according to the processes:

Observe that by definition, incorporate (in corresponding feasible cases) the scheduling, build and destroy decisions, respectively. Hence, this equation is identical to (3), where the feasibility is ensured by the corresponding indicators.

-C Proof of proposition 4.1


Denote the optimal policy . Clearly, there are more tasks in the system in state than in state . Assume that acting as in brings to and to , while acting otherwise (i.e., scheduling into an existing queue) brings to and to .

At arrival, in state it holds , that is, it is sub-optimal to allocate the new task into already active queue. (Without loss of generality we assume that there is an active queue which is not full in .) Observe that it holds and . Substitute this in (4)

To prove that


it is sufficient to show that


which means the policy is also optimal for state . In order to prove that , we resort to stochastic coupling, similarly to the proof of Lemma 4.1. Define four systems, denoted by ,,,. At time , the states are denoted by ,,,. Apply the optimal policies for systems and . The policies and will be suboptimal and such that (resp. ) will coincide with (resp. ) in the shortest time possible. We aim to show that consists of the partial costs due to the scheduling, rejection and delay, while the costs due to queue deployments, displacements and holding cancel out with exception of an arbitrarily negligible component. Then, by the delay structure in (1), the lemma will follow from the following.


Next, we specify the suboptimal policies and . For simplicity, we assume that the same queues were selected for scheduling in and ; and and . Denote the queue which has more tasks in , (resp. in ) by , (resp. ). Denote the newly activated queue which has exactly one task in , (resp. in ) by , (resp. ). To this end, mimics in all actions, with exceptions of the following events which happen only once. In the case activates queue , and schedules into it, , if was active, will schedule into queue . For this purpose, in the case fills up and rejects - the task will be rejected in as well, hence will have one place left. Finally, in order to prevent the event where fills up before it ever becomes empty and before is activated at first time, will schedule into in this case. Note that these actions will make the systems equal. The system and start to act identically (optimally) once all these systems’ queues become equal.

Likewise, mimics in all actions, with exceptions of the following events which happen only once. In the case schedules into queue , then activates queue and schedules into it, provided was not destroyed before that. This prevents having a future rejection from while no rejecting at at the same time. In order to prevent the rejection event in but not in during filling of the queue , once fills up and rejects - the task will be rejected in as well.

Note that in the case queue gets empty before any tasks are scheduled, the event happens in both systems and , since they are stochastically coupled. Hence the corresponding cost difference to this event cancels out. We also assumed that by identity of all queues, the scheduling into active queues is balanced. Denote the time when both equals to and equals to by . Write

where is a nonnegative component associated with having the additional queue till the time (or before). Similarly,

where is a nonnegative component associated with having the additional queue till the time (or before). We use the delay structure in (1) to write


It is left to assess the impact of and . Observe that these are average costs associated with the same events, but differently discounted. In order to avoid complex analysis, we take the discount factor close enough to , such that the difference between the two costs will be negligible if compared to components in (10). By substitution in (9), the proposition follows. ∎


  • [1] M. Chiosi, D. Clarke, P. Willis, A. Reid, J. Feger, M. Bugenhagen, W. Khan, M. Fargano, C. Cui, H. Deng et al., “Network functions virtualisation: An introduction, benefits, enablers, challenges and call for action,” in SDN and OpenFlow World Congress, 2012, pp. 22–24.
  • [2] J. F. Riera, E. Escalona, J. Batallé, E. Grasa, and J. A. García-Espín, “Virtual network function scheduling: Concept and challenges,” in Smart Communications in Network Technologies (SaCoNeT), 2014 International Conference on.   IEEE, pp. 1–5.
  • [3] M. Schöller, M. Stiemerling, A. Ripke, and R. Bless, “Resilient deployment of virtual network functions,” in 2013 5th International Congress on Ultra Modern Telecommunications and Control Systems and Workshops (ICUMT).   IEEE, pp. 208–214.
  • [4] J. Costa-Requena, J. L. Santos, V. F. Guasch, K. Ahokas, G. Premsankar, S. Luukkainen, O. L. Pérez, M. U. Itzazelaia, I. Ahmad, M. Liyanage et al., “Sdn and nfv integration in generalized mobile network architecture,” in Networks and Communications (EuCNC), 2015 European Conference on.   IEEE, pp. 154–158.
  • [5] J. Mace, P. Bodik, M. Musuvathi, R. Fonseca, and K. Varadarajan, “2dfq: Two-dimensional fair queuing for multi-tenant cloud services,” in Proceedings of the 2016 conference on ACM SIGCOMM 2016 Conference, pp. 144–159.
  • [6] M. Shifrin, R. Atar, and I. Cidon, “Optimal scheduling in the hybrid-cloud,” in 2013 IFIP/IEEE International Symposium on Integrated Network Management (IM 2013), pp. 51–59.
  • [7] M. Yoshida, W. Shen, T. Kawabata, K. Minato, and W. Imajuku, “Morsa: A multi-objective resource scheduling algorithm for nfv infrastructure,” in Network Operations and Management Symposium (APNOMS), 2014 16th Asia-Pacific.   IEEE, pp. 1–6.
  • [8] L. Qu, C. Assi, and K. Shaban, “Network function virtualization scheduling with transmission delay optimization,” in Network Operations and Management Symposium (NOMS), 2016 IEEE/IFIP, pp. 638–644.
  • [9] J. A. Van Mieghem, “Price and service discrimination in queuing systems: Incentive compatibility of gc scheduling,” Management Science, vol. 46, no. 9, pp. 1249–1267, 2000.
  • [10] M. J. Neely, E. Modiano, and C.-P. Li, “Fairness and optimal stochastic control for heterogeneous networks,” IEEE/ACM Transactions On Networking, vol. 16, no. 2, pp. 396–409.
  • [11] D. G. Feitelson, L. Rudolph, U. Schwiegelshohn, K. C. Sevcik, and P. Wong, “Theory and practice in parallel job scheduling,” in Workshop on Job Scheduling Strategies for Parallel Processing.   Springer, 1997, pp. 1–34.
  • [12] A. Ganti, E. Modiano, and J. N. Tsitsiklis, “Optimal transmission scheduling in symmetric communication models with intermittent connectivity,” IEEE Transactions on Information Theory, vol. 53, no. 3, pp. 998–1008, 2007.
  • [13] J. M. Harrison and A. Zeevi, “Dynamic scheduling of a multiclass queue in the halfin-whitt heavy traffic regime,” Operations Research, vol. 52, no. 2, pp. 243–257, 2004.
  • [14] A. A. Puhalskii, M. I. Reiman et al., “The multiclass gi/ph/n queue in the halfin-whitt regime,” Advances in Applied Probability, vol. 32, no. 2, pp. 564–595, 2000.
Comments 0
Request Comment
You are adding the first comment!
How to quickly get a good reply:
  • Give credit where it’s due by listing out the positive aspects of a paper before getting into which changes should be made.
  • Be specific in your critique, and provide supporting evidence with appropriate references to substantiate general statements.
  • Your comment should inspire ideas to flow and help the author improves the paper.

The better we are at sharing our knowledge with each other, the faster we move forward.
The feedback must be of minimum 40 characters and the title a minimum of 5 characters
Add comment
Loading ...
This is a comment super asjknd jkasnjk adsnkj
The feedback must be of minumum 40 characters
The feedback must be of minumum 40 characters

You are asking your first question!
How to quickly get a good answer:
  • Keep your question short and to the point
  • Check for grammar or spelling errors.
  • Phrase it like a question
Test description