<commit_before>= containers-rti
Repository to test RTI DDS with container technologies (docker, kubernetes).

== Environment
Vagrant can be used to deploy the necessary virtual machines.

In the default configuration you will get 3 VMs where the first is in the master group and the other two in the nodes group:

[width="20%", cols="1,1a,1", options="header"]
|===
| Host | Groups | Private IP

| centos-1
| * centos
  * master
| 172.30.0.11/24

| centos-2
| * centos
  * nodes
| 172.30.0.12/24

| centos-3
| * centos
  * nodes
| 172.30.0.13/24
|===

=== Proxy Configuration
If applicable, using a proxy is possible directly via proxy address inside the virtual machines.

Take the following steps to configure the virtual machines for an proxy address.
[source,bash]
----
export VM_PROXY_ENABLED=true
export VM_PROXY_ADDRESS=http://proxy.domain:8080/
----

=== Initialization
Thanks to vagrant the deployment of the virtual machines is really easy. The configuration can be found in the file `Vagrantfile`. It's possible to change the number of virtual machines and the playbook used during provisioning via environment variables (see below).

The virtual machines can be deploying with the following commands:
[source,bash]
----
= optional, default = 3
export VM_INSTANCES=4
= optional, default = deploy-docker.yml
export PLAYBOOK=deploy-kubernetes.yml
vagrant up
----

=== Execution of additional playbooks after provisioning
[source,bash]<commit_msg>Fixed README to reflect current Vagrantfile<commit_after>= containers-rti
Repository to test RTI DDS with container technologies (docker, kubernetes).

== Environment
Vagrant can be used to deploy the necessary virtual machines.

In the default configuration you will get 3 VMs where the first is in the master group and the other two in the nodes group:

[width="20%", cols="1,1a,1", options="header"]
|===
| Host | Groups | Private IP

| centos-1
| * centos
  * master
| 172.30.0.11/24

| centos-2
| * centos
  * nodes
| 172.30.0.12/24

| centos-3
| * centos
  * nodes
| 172.30.0.13/24
|===

=== Proxy Configuration
If applicable, using a proxy is possible directly via proxy address inside the virtual machines.

Take the following steps to configure the virtual machines for an proxy address.
[source,bash]
----
export VM_PROXY=http://proxy.domain:8080/
----

=== Initialization
Thanks to vagrant the deployment of the virtual machines is really easy. The configuration can be found in the file `Vagrantfile`. It's possible to change the number of virtual machines and the playbook used during provisioning via environment variables (see below).

The virtual machines can be deploying with the following commands:
[source,bash]
----
= optional, default = 3
export VM_INSTANCES=4
= optional, default = none
export PLAYBOOK=deploy-kubernetes.yml
vagrant up
----

=== Execution of additional playbooks after provisioning
[source,bash]
{'fraction_non_alphanumeric': 0.0930795847750865, 'fraction_numerical': 0.031141868512110725, 'mean_word_length': 4.353703703703704, 'pattern_counts': {'":': 0, '<': 3, '<?xml version=': 0, '>': 3, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 6, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '443818', 'n_tokens_mistral': 893, 'n_tokens_neox': 823, 'n_words': 350}