This document summarizes an upcoming Devops Munich meetup on orchestration. The meetup will include talks on tool usage at hybris, orchestration in general, and an introduction and demo of the hybris adminportal tool. Hybris uses tools like Puppet, MCollective, and Ansible for provisioning, configuration management, and running ad-hoc tasks. Orchestration aims to automate entire processes by calling various components from a single system. The hybris adminportal allows defining and executing script chains with parameters and outputs tracking. It supports features like grouping, REST execution triggering, and plugin mechanisms.

2. Devops Munich meetup
(Scripting) Orchestration
12.Februar

3. 1. Short introduction
2. Tool usage at hybris
3. Orchestration in general
4. Introduction to adminportal
5. Short Demo

4. #1 “independent” commerce platform Offices:
Munich*, Montreal*, Ams
Fastest growing global commerce ISV terdam, Boston, Chicago, Gliwice
Founded in 1997 , Hong
Kong, London, Milan, Neuilly-Sur-
Operations in 15 countries Seine,
Sao
Paolo, Sydney, Tokyo, Västerås,

5. Why do we do this talk?
So, WHY this talk?
Getting feedback
Search the blind spot
We„re hiring
http://www.hybris.com/de/company/careers/jobs
… and WHO ?
Kim Neunert (@k9ert), hybris GmbH
Tobias Schuhmacher, hybris GmbH

6. 1. Short introduction
2. Tool usage at hybris
3. Orchestration in general
4. Introduction to adminportal
5. Short Demo

7. Some context - tooling at hybris
Hybris has been a software vendor rather than a Service Provider, that is
changing right now
In the first place: Puppet (apply) for server-provisioning
Automated „puppet apply“ with the adminportal
MCollective and especially the MCollective-mongo-registry approach
http://goo.gl/WubXM
For adhoc-tasks, we use ansible but:
Vagrant for development and Continous integration via jenkins
Puppi, a collection of bash-scripts provisioned via puppet for
deployments and a self introduced mongo-reporting-mechanism
Now heading towards a puppetmaster-approach being able to completely
reuse our modules/server-roles

8. 1. Short introduction
2. Tool usage at hybris
3. Orchestration in general
4. Introduction to adminportal
5. Short Demo

9. Orchestration, what„s that?
Automation  a part of an overall process
Orchestration  Automating the whole overall process
Where are the typical limitations/borders of automation?
Provisioning
Booting new
machines, configuring
infrastructure
Provisioning
Deployment

10. The vision of orchestration
In order for orchestration to really work, you need a single system calling the
shots (although it may, or perhaps should, delegate some responsibilities to
other systems).
This in turn requires that all the components … be manageable from that one
platform.
There are two ways this gets done: the single-vendor approach and the open-
standards approach.
With the single-vendor approach, [...]
The open-standards approach allows IT to mix and match resources from
different vendors. As long as the orchestrator and management tools can talk
to them, they can be folded in. [...]
-- http://goo.gl/2QN6V

11. The downside of the imperative approach (orchestration)
Modeling the control-flow is error-prone, especially in mixed
environments
No Stacktrace/„Exceptionhandling“
No complete control of the whole stack, maybe 3rd parties/other people
involved
Difficult to decide how to continue in the case of errors
So, orchestration tends to fail
Whenever possible one switched to an declarative approach:
Parser-code generation, SQL, Regex, Rendering of UIs
Nodeconfiguration via Puppet (Chef?!)
The role of orchestration is reduced to just model dependencies
Let„s avoid orchestration  model dependencies!

12. Example: Cross node dependencies while provisioning
Cross-nodes dependencies  Exported Resources in Puppet
You need to store state, that„s why exported Resources need a DB
Storing state or gathering it at runtime is very helpfull
PuppetDB
MCollective
R.I.Pienaar (author of mcollective) shows how to leverage MongoDB-
Registration-Data in puppet manifests:
http://goo.gl/WubXM
Chris Spence (puppetlabs consultant) created a notify-mechanism which
will handle cross-node-dependencies so that e.g. a Loadbalancer get
configured afterwards immediately
http://goo.gl/NkHtS

13. Long story short …
… you want to avoid orchestration
in favor of declarative dependency modeling
however, that will be a long journey ...
… in the meantime …

14. 1. Short introduction
2. Tool usage at hybris
3. Orchestration in general
4. Introduction to adminportal
5. Short Demo

15. Features
Grails application (Spring, Groovy, Java...)
Execute scripts in a chain (Bash, Perl, Groovy, Python, PHP...)
Annotate scripts (metadata: description, author, parameters etc.)
#!/bin/bash
# @Scriptlet(author=“Tobi (my-email@somehwere.de)",
description=“Create Zerigo DNS entry")
#
#
# @Parameters([
# @Parameter(name=“ZERIGO_USER", type=ParameterType.CONSUME,
description=“The Zerigo uUsername", visible=false,
defaultValue=“my-zergio-username"),
#
# @Parameter(name=“FQDN", type=ParameterType.EMIT,
description=“The FQDN returned by Zerigo“),
# ])

16. Features
List of required script parameters

17. Features
Grouping of script chains
Per environment
Different parameters per group
Parameters exported via REST (Json, YAML – useful for Hiera)
Execution of script chains can be triggered via REST
Authorization / Authentication supported
Plugin mechanism: wrap a script and interact with Grails (e.g. DB access)
Execute scripts as cronjob

18. After the execution, it looks like this
Track any output of a script chain

19. 1. Short introduction
2. Tool usage at hybris
3. Orchestration in general
4. Introduction to adminportal
5. Short Demo