Page History

Versions Compared

Old Version 3

changes.mady.by.user Prathewraj M

Saved on Apr 28, 2015

compared with

New Version Current

changes.mady.by.user Prathewraj M

Saved on Jan 20, 2016

Key

This line was added.
This line was removed.
Formatting was changed.

...

On execution of event process, the sequence of launching and stopping the microservices will be as per the values set for the Launch order and Stop order corresponding to their Service Instances. Note:

Note

Components whose values are less than or equal to zero are considered to be independent of SLO and will be launched/stopped first without referring to the order specified.a. Ideally, values for such components are left as default (-1) to run independently.b. Whenever these components have to be considered within SLO, provide an appropriate positive value.
Components with priority greater than zero are considered to be in SLO.
Values can be anything above zero; the next component ready for execution will be the one with the next highest value present.
More than one component can have the same priority and these will be launched/stopped parallelly. So you may provide the same value for two or more components.
Next priority will only be considered when all of its prior components (holding lesser values) are launched successfully.

Launch Order Example

In the above example, Specify Launch order is enabled (selected "yes" from drop-down), names of microservices can be seen under Service Instance, and Launch order is filled with appropriate values for the corresponding Service Instances.
As per the values assigned, Component_3, Component_4, and Component_5 are in the SLO, whereas Values for Component_1 and Component_2 are set less than or equal to zero (<=0) as these components are out of scope from the SLO and hence of no relevance in terms of the launch order.
Component_4 will start first because this is the least positive value (>0) among all others. Component_3 will be the next component to start as it holds the next highest value than Component_4. The last microservice to launch will be Component_5 as it holds the highest value among all.

...