OpenMSA Community overview slides, presented during the Tokyo DevDay on May 31, 2018, to devops networking and security developers.

1. Community Overview

2. Summary
The OpenMSA Community is an open forum empowering developers to design
orchestration solutions for networking and security technologies and the automation
of their associated processes.
Community engineers from Service Provider organizations, system integration firms,
or Enterprises will make the orchestration solution they have built on the OpenMSA
their own, with no vendor lock-in or dependency possible, leaving no domain
unaddressed by their automation plans.
The OpenMSA software is made available at no charge for community developers and
can be downloaded on http://www.openmsa.co/. The related open source
development modules are made available on Github.

3. Community Overview

4. Why the OpenMSA Community?
In the ongoing transition of networks from physical to virtual functions,
companies will need to have a clear strategy on how to provision,
manage, and automate diverse network functions and security features,
whether these are open-source components, legacy infrastructure,
firewalls, or VMs in a datacenter.
As a result, the industry is in dire need for a solution that bridges the
multi-vendor landscape efficiently. The OpenMSA Community aims to do
just that. As an open portal for developers working with Service
Providers, Enterprises, or System Integrators, it empowers a whole
industry to take matters into their own hands, integrate all vendors,
domains and systems, and making network and security managed
services richer and more cost effective in a multi-domain, multi-vendor
environment.

5. Current Orchestration Challenges
BEFORE
Provisioning
Configuration
Policy Changes
Review/Confirmation
Etc.
MANUAL
Vendor A
Vendor B
Vendor C
Vendor D
Vendor E, F, G
NMS A NMS B NMS C, D, E, F, G
TIME
INTENSIVE
ERROR
PRONE
HGH LABOR
COST
OPERATORS
VENDOR
LOCK-IN
NOT ALL
FUNCTIONALITY
CAN BE
REALIZED
SILOED
VENDORS &
DOMAINS

6. Industrial
IoT
Orchestration with the OpenMSA
AFTER
AUTOMATED
PROCESSES
SINGLE PANE OF GLASS
SHARE WITH GITHUB
COMMUNITY
BUILD YOUR OWN
OBJECT FOR ANY
VENDOR & DOMAIN
OPERATOR

7. How to Get Started
1. Download the OpenMSA and the 30-day license on
www.openmsa.co (registration required)
2. Make sure to take a look at the how-to documentation at
www.docs.openmsa.co
3. Download existing libraries on Github at www.github/openmsa and
share your code with the Community!
4. Ask questions in the OpenMSA Google Group
Follow OpenMSA on Twitter for updates and tips:
https://twitter.com/openmsa

8. What does the Community Provide?
Open Source Core engine
The open source core engine is the high performance multi-threaded engine in charge of order
command processing and execution via the device adaptors. The source code of the OCE is
available on Github.
Microservices examples
A microservice is an object that provides the abstraction layer to manage services on your
network element or your VIM in a programmable and granular way. It discovers configurations
and exposes generic Create | Read | Update | Import | Delete methods for day-2 change
management. Microservices examples are also available on Github, uploaded by Community
members.
Access to documentation and DevOps experts
We can help you get started with configuring your OpenMSA. Please go through our
documentation explaining the setup, configuration, and design of workflows and microservices.
Should you have any questions, please reach out in the OpenMSA Forum.

9. What does the Community Provide?
Open Source Adaptors developed by the Community
Whether you are in need of an adaptor to manage your virtual infrastructure (VMware,
Openstack, and many more), or a Network element, rely on the Community to do some of the
work for you. Device adaptors are easily scripted using the device adaptor builder, which comes
with the Open Core engine. The Adaptor Builder supports any communication protocol, and will
handle device asset and image management over its lifecycle. Device adaptor samples can be
found on Github.
A free evaluation license
You’ll need this license to activate the OpenMSA. You can download it on our OpenMSA page.
Workflow examples
Easily stitch your microservices into a service workflow. You’ll design workflows aligned with your
own business processes and with whichever function or service you aim at automating.
Workflow examples are available on GitHub, uploaded by Community members.

10. Overview of Community Benefits for Users
The OpenMSA Community makes it possible for users to easily
expand the list of supported vendors by downloading any needed
libraries or devices adaptors, which drastically reduces the
integration cost they would usually face.
Operational efficiency is increased by shortening problem solving
and integration efforts in any orchestration project.

11. Overview of Community Benefits for Developers
The developer community benefits greatly from sharing adaptors,
microservices, workflows and knowledge in the Github portal.
Any provided adaptor source code increases the chances that the
underlying vendor technology is adopted by users. Ease of
integration and agility are the main drivers for vendor adoption.
Sharing work on portals like Github also provides an immediate
credibility boost for any developer’s resume.

12. Empowering the DevOps Community

13. OpenMSA Support & Questions
Ask questions in the OpenMSA
Google Group
Follow OpenMSA on Twitter for
updates and tips:
https://twitter.com/openmsa

14. Marketing Contact
For questions, please contact
Ariane Sunder
Global Head of Marketing
asu@ubiqube.com
+1 415 676 8676