Partial Compiles#

Partial compilation is an approach to speed up compilation when the Service Inventory contains many instances.

Ordinarily, LSM re-compiles all instances on every update. This means that as the inventory grows, the compiles become slower. Partial compiles allow LSM to re-compile only those instances that are relevant to the current service instance, avoiding any slowdown.

Implementation guidelines#

  1. for every lsm::ServiceEntity,

    1. make sure to collect all resources it contains in the relation owned_resources

    2. make sure to always select the parent implementations (implement … using parents)

  2. for every Inter Service Relation

    1. indicate if this is the relation to the owner by setting lsm::ServiceEntityBinding.relation_to_owner and lsm::ServiceEntityBinding.owner.

Supported scenarios#

Partial compiles are possible when

  1. Service Instances are unrelated: service instances don’t share any resources and don’t depend on each other in any way. This only requires correctly setting owned_resources.

  2. Services form groups under a common owner.

    • Instances within the group can freely depend on each other and share resources, but nothing is shared across groups.

    • One specific instance is designated as the common owner of the group.

    • Instances can not be moved to another group. The model should prevent this type of update.

    • This additionally requires indicating what the owner of any service is, by setting lsm::ServiceEntityBinding.owner and lsm::ServiceEntityBinding.relation_to_owner. This does not immediately have to be the root owner, the ownership hierarchy is allowed to form a tree with intermediate owners below the root owner.

  3. Service instances and groups can depend on shared resources, that are identical for all service instances and groups.

  4. Any combination of the above

How it works for unrelated services#

For unrelated services, LSM expands on the normal resources set based partial compiles by automatically creating a single resource set for each service instance.

To add resources to the instance’s resource set, simply add them to its lsm::ServiceBase.owned_resources relation and make sure to select the parents implementation for your service entities. LSM will then make sure to populate the resource set and to correctly trigger related compiles and exports.

Example with Inter Service Relations#

As an example, consider the following model for managing ports and routers. Both are independent services, but a port can only be managed in combination with its router and all its siblings. (This is not in general true, we often manage ports without managing the entire router, but we use it as an example.)

This model is not much different from normal Inter Service Relations, except for lines 29, 38, 58-59.
 1import lsm
 2import lsm::fsm
 3import std::testing
 5entity Router extends lsm::ServiceEntity:
 6    """
 7        A service for managing routers
 8    """
 9    string mgmt_ip
12index Router(instance_id)
14entity Port extends lsm::ServiceEntity:
15    """
16        A service for managing ports on routers
17    """
18    string name
21index Port(instance_id)
23Port.router [1] lsm::__service__, lsm::__rwplus__ Router
24""" An Inter Service Relation between Router and Port"""
26implementation router_config for Router:
27    """ Add a dummy resource to the router to represent actual configuration """
28    self.resources += std::testing::NullResource(name=self.mgmt_ip)
29    self.owned_resources += self.resources # We own all our resources and nothing else
32implementation port_config for Port:
33    """ Add a dummy resource to the Port to represent actual configuration """
34    self.resources += std::testing::NullResource(
35        name="{{self.router.mgmt_ip}}-{{}}",
36        requires = self.router.resources
37    )
38    self.owned_resources += self.resources # We own all our resources and nothing else
41implement Router using router_config, parents
42implement Port using port_config, parents
44# Service binding for Router
45binding_router = lsm::ServiceEntityBinding(
46    service_entity="__config__::Router",
47    lifecycle=lsm::fsm::simple_with_delete_validate,
48    service_entity_name="router",
49    service_identity="mgmt_ip",
52# Service binding for Port
53binding_port = lsm::ServiceEntityBinding(
54    service_entity="__config__::Port",
55    lifecycle=lsm::fsm::simple_with_delete_validate,
56    service_entity_name="port",
57    service_identity="name",
58    relation_to_owner="router", # required for Partial Compile
59    owner=binding_router, # required for Partial Compile
62# Normal Service unrolling
63for instance in lsm::all(binding_router):
64    Router(
65        instance_id = instance["id"],
66        entity_binding = binding_router,
67        **instance["attributes"],
68    )
71for instance in lsm::all(binding_port):
72    Port(
73        instance_id = instance["id"],
74        entity_binding = binding_port,
75        name = instance["attributes"]["name"],
76        router = Router[instance_id=instance["attributes"]["router"]]
77    )

How it works#

To better understand how this works, there are two things to consider:

  1. how to divide the resources into resource sets

  2. how to get the correct instances into the model

Resource sets#

The key mechanism behind partial compiles are ResourceSets: all resources in the desired state are divided into groups. When building a new desired state, instead of replacing the entire desired state, we only replace a specific ResourceSet. Resources in a ResourceSet can not depend on Resources in other ResourceSets.

To make this work, we have to assign every Service Instance to a ResourceSet, such that the set has no relations to any other ResourceSet.

In practice, we do this by putting all Resources in the ResourceSet of the owning entity.

digraph resource_sets_generic_good { subgraph cluster_services { "NullResource(name=r1)" [shape=rectangle]; "LifecycleTransfer(id=0)"; "LifecycleTransfer(id=0)" -> "NullResource(name=r1)" "NullResource(name=r1-eth0)" [shape=rectangle]; "NullResource(name=r1-eth0)" -> "NullResource(name=r1)" "LifecycleTransfer(id=2)" -> "NullResource(name=r1-eth0)" label = "ResourceSet for Router r1(id=0)"; labelloc = "top"; color = "green"; } subgraph cluster_services_2 { "NullResource(name=r2)" [shape=rectangle]; "LifecycleTransfer(id=3)"; "LifecycleTransfer(id=3)" -> "NullResource(name=r2)" "NullResource(name=r2-eth0)" [shape=rectangle]; "NullResource(name=r2-eth0)" -> "NullResource(name=r2)" "LifecycleTransfer(id=4)" -> "NullResource(name=r2-eth0)" label = "ResourceSet for Router r2(id=3)"; labelloc = "top"; color = "green"; } }

Resource Sets for the Router example with 2 Routers with each 1 port. Arrows represent the requires relation.#

In addition to the ResourceSets used by individual services, there are also Resources that are not in any set. These Resources can be shared by multiple services, with the limitation that any compile that produces them, has to produce them exactly the same. For more information see Partial Compiles.

Service Instance Selection#

To have efficiency gains when recompiling, it is important to only build the model for all Service Instances that are in the ResourceSet we want to update and nothing else.

This selection is done automatically within lsm::all, based on the relations set between the service bindings as explained above.

The underlying mechanism is that when we recompile for a state change on any Service Instance, we first search its owner by traversing lsm::ServiceEntityBinding.relation_to_owner until we reach a single owner. Then we traverse back down the lsm::ServiceEntityBinding.relation_to_owner until we have all children. lsm::all will only return these children and nothing else.


  1. When doing normal compiles, the model can very effectively find conflicts between services (e.g. using indexes), because it has an overview of all instances.

    When using partial compile, conflicts between groups can not be detected, because the compiler never sees them together. This means that the model must be designed to be conflict free or rely on an (external) inventory to avoid conflicts. This is why we always advice to run models in full compile mode until performance becomes an issue: it gives the model time to mature and to detect subtle conflicts.

  2. Complex topologies (with multiple parents or cross-relations) are currently not supported out of the box.

    However, complex interdependencies between service instances are often an operation risk as well. Overly entangled services are hard to reason about, debug and fix. While it is possible to develop more complex topologies using the guidelines set out in Partial Compiles, it may be preferable to simplify the service design for less interdependence.

For more details, see limitation section in the core documentation

Further Reading#