Added mkdocs-glightbox (image zoom plugin) and fixed image references

    PAGES_BRANCH: gl-pages

    HTTPS_REMOTE: https://gitlab-ci-token:${ACCESS_TOKEN}@${CI_SERVER_HOST}/rep/${CI_PROJECT_PATH}.git

  before_script:

    - pip install -q mkdocs-material mike

    - pip install -q mkdocs-material mike mkdocs-glightbox

    - apt-get update -qq && apt-get -qq install -y git > /dev/null

    - git config --global --replace-all user.name $GITLAB_USER_NAME

    - git config --global --replace-all user.email $GITLAB_USER_EMAIL

Usually used to perform a Day2 configuration (towards OSM). To use it, Create a New Action Specification Name=execDay2 as following

[![Openslice  usage](./images/alarms_actions/day2actionspec.png)](./images/alarms_actions/day2actionspec.png)

![Openslice  usage](./images/alarms_actions/day2actionspec.png)

Now make a Service Order for your service. In this example ςε used a cirros NSD

Create a  New Action Rule for the running services as the following example:

[![Openslice  usage](./images/alarms_actions/action_rule_exampleday2.png)](./images/alarms_actions/action_rule_exampleday2.png)

![Openslice  usage](./images/alarms_actions/action_rule_exampleday2.png)

The scope is the running cirros service. 

* Service Inventory: The Customer and Provider will be able to view deployed Services status -->

[![OpenSlice  architecture](./images/architecture.png)](./images/architecture.png)

![OpenSlice  architecture](./images/architecture.png)

OpenSlice consists of:

## Microservices Deployment

The following figure depicts how OpenSlice microservices are deployed

[![OpenSlice microservices network deployment](./images/microservices_network_deployment.png)](./images/microservices_network_deployment.png)

![OpenSlice microservices network deployment](./images/microservices_network_deployment.png)

TMF Open APIs are introduced not only for exposing catalogues and accepting service orders, but also implementing the East-West interfaces between the domains, fulfilling also the [LSO requirements](https://wiki.mef.net/pages/viewpage.action?pageId=56165271) as introduced by MEF.

The following figure shows how openslice could be used in such scenarios:

The following figure shows how OpenSlice could be used in such scenarios:

[![Openslice  multi-domain-architecture](../getting_started/configuration/images/multi-domain-architecture.png)](../getting_started/configuration/images/multi-domain-architecture.png)

![Openslice  multi-domain-architecture](../getting_started/configuration/images/multi-domain-architecture.png)

See more [Consuming Services From External Partner Organizations](../getting_started/configuration/consuming_services_from_external_partners.md).

 No newline at end of file

See more at [Consuming Services From External Partner Organizations](../getting_started/configuration/consuming_services_from_external_partners.md).

 No newline at end of file

The following image illustrates the approach.

[![img01.png](img01.png)]()

![img01.png](img01.png)

1. A CRD in a cluster will be mapped in TMF model as a Resource specification and therefore can be exposed as a service specification in a catalog

2. Service Orders can be created for this service specification. The OSL Orchestrator (OSOM) will manage the lifecycle of the Service Order.

[![img02.png](img02.png)]()

![img02.png](img02.png)

A CRIDGE service is usually responsible for managing one cluster. In the following diagram we show how it can be used for managing multiple clusters:

[![img03.png](img03.png)]()

![img03.png](img03.png)

We assume that there is an OSL Management cluster that OSL is installed. CRIDGE is also installed there if we would like to manage resources in the same management cluster. 

The implemented synchronization process is explained by the following diagram:

[![img04.png](img04.png)]()

![img04.png](img04.png)

 WatcherService is executed when the CRIDGE service application starts (see onApplicationEvent). Specifically:

The implemented process to deploy a CR is explained by the following diagram:

[![img05.png](img05.png)]()

![img05.png](img05.png)

- A message arrives to deploy a CR

	- The call examines if this CRIDGE service can handle the request (based on context and masterURL)

The figure below displays the overall issue management service architecture integrating Bugzilla as its core and how this tool interacts with other Openslice services presenting some distinctive scenarios. It should be noted that Bugzilla tickets will not only be used for bugs/errors, but also for general requests, e.g. Service Order procedure.

[![Issue management system](../images/issue_management.png)](../images/issue_management.png)

 No newline at end of file

![Issue management system](../images/issue_management.png)

 No newline at end of file