This is the slide pack I presented at the March Melbourne Kubernetes Meetup.

1. Open Datacentre Free, extensive, current.

2. Open Datacentre
• Why
• What
• How
• Demo
• Summary
• Questions

3. Open Datacentre
Why

4. WhyOpen Datacentre
So Many Reasons!

5. WhyOpen Datacentre
• IT systems are complex, which makes for:
• Confusion;
• Inefficient processes;
• Fragility;
• Stress.
• The use of IT systems needs to be simplified.

6. WhyOpen Datacentre
• IT systems resist change:
• Cloud, product and vendor lock-in removes choice;
• Modifying an IT system is difficult.
• Without change inefficiencies are perpetuated.
• Easy choice of which products to run and where to run them is
vital.

7. WhyOpen Datacentre
• Capable IT systems can be expensive and exclusive:
• Businesses are forced to spend on IT to compete;
• Enterprises generally have a monopoly on specialists;
• Running everything in the cloud is expensive;
• Relocating an IT system is expensive.
• Access to capable IT systems needs to be democratised to provide a
level playing field for smaller organisations.

8. WhyOpen Datacentre
• The key principles are:

9. WhyOpen Datacentre
• In other words:
• Making it easier
• to use the most appropriate solution
• and freely available to anyone.

10. Open Datacentre
What

11. WhatOpen Datacentre
• Open Datacentre provides a set of curated open source
products within the following domains:
• Productivity;
• Development;
• Infrastructure.

12. WhatOpen Datacentre
• Open Datacentre is managed by:
• Kubernetes;
• Helm;
• Ansible.

13. WhatOpen Datacentre What

14. WhatOpen Datacentre
• Open Datacentre domains are composed of:
• Capabilities;
• Solutions;
• Products.

15. WhatOpen Datacentre
• A Capability is defined as:
• A description of a functional unit,
• including its desired attributes,
• that is relevant within an IT system.

16. WhatOpen Datacentre
• Examples of Capabilities are:
• Distributed block storage;
• Identity management;
• Job management;
• Artifact management.

17. WhatOpen Datacentre
• Open Datacentre has many Capabilities.

18. WhatOpen Datacentre
• The current Capabilities for Open Datacentre are:
• Cluster Services;
• Cluster Management;
• Distributed Block Storage;
• Identity Management;
• HTTP/S Reverse Proxy;
• Metrics;
• Logging;
• Job Management;
• Artifact Storage;
• Image Repository.

19. WhatOpen Datacentre
• A Capability is realised through a Solution.
• A Solution contains one or more Products with an appropriate
configuration.

20. WhatOpen Datacentre
• All the integration of the Solutions is already done “out of the
box”.
• There is at least one default Solution for each of the
Capabilities.
• The Solutions offer sane defaults.

21. WhatOpen Datacentre
• The key design goals for Open Datacentre are:
• Make it simple enough that a business can use it without
much IT expertise;
• But not so simple that it sacrifices advanced and leading
edge capabilities.

22. WhatOpen Datacentre
• The target users for Open Datacentre are:
• Non-profits;
• Small organisations;
• Medium sized organisations;
• Enterprises?

23. WhatOpen Datacentre
• Open Datacentre can run anywhere from:
• Developer workstations to
• On-premises bare metal / hypervisors to
• Multiple clouds.

24. Open Datacentre
How

25. HowOpen Datacentre
• There is a single command to install, manage and update
Open Datacentre components.
• The command is written in Python and is installed using Pip.
$ pip install k8sdc

26. HowOpen Datacentre
• Open Datacentre is provisioned using a Provider.
• Currently there are Providers for:
bare You provide the hosts.
vagrant Vagrant creates the hosts.
do The hosts are created on Digital Ocean.

27. HowOpen Datacentre
• An installation for a particular Provider is initialised using the
k8sdc command.
$ k8sdc init -p do

28. HowOpen Datacentre
• A Provider is configured using a provider.yaml file.
• The provider.yaml file contains values for:
• The cloud or provisioner;
• The hosts;
• Overrides of the default values;
• Optional external Capabilities.

29. HowOpen Datacentre
• After the provider.yaml is customised Open Datacentre is
provisioned.
$ k8sdc up

30. HowOpen Datacentre
• A Base Topology will be created.

31. HowOpen Datacentre
• The components of the Base Topology are:
Ansible Host
Used to install, manage and update the Open Datacentre
components by using the k8sdc command.
Kubernetes
Masters
Kubernetes master hosts.
Kubernetes
Nodes
Kubernetes Kubelet hosts.
Fileserver Used to download the installation files to a central location.
Image Registry
Mirror
Docker images are pulled through the Image Registry Mirror.
Greatly improving performance.
CA
The CA (Certificate Authority) is used to generate private
keys and certificates for the Open Datacentre components.
NTP Server
Used to synchronise the date and time between Open
Datacentre hosts.

32. HowOpen Datacentre
• Then the Solutions for the Capabilities are deployed.
$ k8sdc sol

33. HowOpen Datacentre

34. Open Datacentre
Demo

35. Open Datacentre
Summary

36. SummaryOpen Datacentre
• Open Datacentre provides:
• An extensive set of current datacentre capabilities
• for creating and hosting digital content
• and managing a business
• with no vendor lock-in
• and for free.

37. SummaryOpen Datacentre
Would you like to help?

38. Open Datacentre
Questions

39. opendatacentre.io
github.com/opendatacentre/opendc