Merge "GUS 2018: Multi-master and multi-site"
diff --git a/schedule.md b/schedule.md
index 144a356..6ec9284 100644
--- a/schedule.md
+++ b/schedule.md
@@ -10,7 +10,7 @@
|-------|----------------------------------------------------------------------------------------------|
| 8:30 | Registration Opens, Breakfast, Networking |
| 9:00 | Welcome introduction |
-| 9:15 | Session #1 |
+| 9:15 | [Upgrading to Gerrit 2.15: real-life story on GerritHub](sessions/gerrithub-2.15-upgrade.md) |
| 10:00 | Session #2 |
| 10:45 | Break & Networking |
| 11:30 | Session #3 |
@@ -26,7 +26,7 @@
| Time | Session |
|-------|----------------------------------------------------------------------------------------------|
-| 9:00 | Session #7 |
+| 9:00 | [DevOps Analytics - Uncover the value of Gerrit Pipeline](sessions/devops-analytics.md) |
| 9:15 | Session #8 |
| 10:00 | Session #9 |
| 10:45 | Break & Networking |
diff --git a/sessions/devops-analytics.md b/sessions/devops-analytics.md
new file mode 100644
index 0000000..d27f748
--- /dev/null
+++ b/sessions/devops-analytics.md
@@ -0,0 +1,19 @@
+# DevOps Analytics - Uncover the value of Gerrit Pipeline
+
+Uncover the hidden value of your CI/CD pipeline and discover how
+Gerrit DevOps Analytics helps to accelerate your development and quickly
+adapt to an ever-changing market.
+
+GerritForge has published one year ago the [Gerrit Analytics](https://gerrit-analytics.gerritforge.com)
+for the Gerrit Code Review project, showing live metrics on where the project
+is going, the key contributors and the most active repositories.
+
+Learn how to expand the scope of the Data & Insights to the rest of the
+CI/CD Pipeline, including the Git traffic, system utilization and the relationships
+inside and across Teams. All of that is possible by just reusing what Gerrit Code Review
+provides and is often left behind.
+
+See a real use-case based on a real-life scenario that can be taken home
+and applied to your CI/CD Pipeline.
+
+*[Luca Milanesio, Gerrit Maintainer - GerritForge](../speakers.md#lmilanesio)*
diff --git a/sessions/gerrithub-2.15-upgrade.md b/sessions/gerrithub-2.15-upgrade.md
new file mode 100644
index 0000000..6d195c6
--- /dev/null
+++ b/sessions/gerrithub-2.15-upgrade.md
@@ -0,0 +1,19 @@
+# Upgrading to Gerrit 2.15: a real-life story on GerritHub.io
+
+Upgrading is always a pain: learning from other people's mistakes
+is the only way to plan for a flawless transition to new releases.
+
+GerritHub.io has been upgraded successfully to Gerrit 2.15 back in
+April with zero-downtime but some [bumps on the road](https://gitenterprise.me/2018/04/27/gerrithub-is-on-notedb-with-a-bump/).
+
+See how the process worked and discuss with Luca Milanesio the challenges and tricks to migrate to Gerrit 2.15 and NoteDb without impacting your users:
+
+- How to plan the upgrade
+- What to expect in terms of resources utilisation
+- Disaster recovery plan
+- Monitoring
+- Split between reindex phase and NoteDb on-line migration
+- Post-upgrade metrics
+- Retrospective after 6 months on Gerrit 2.15/NoteDb
+
+*[Luca Milanesio, Gerrit Maintainer - GerritForge Ltd](../speakers.md#lmilanesio)*
