7. Work Station
Help Desk View
Shared
5x Service Desk 5x Field Support
Applications Settings
Manager
8. Work Station
Virtual View System Administrator
Operating System?
Applications Settings Operating System
9. Work Station
Real View System Administrator
Total management
Applications Settings Operating System
Updates Global Changes Inventory Validation
User Profile Security Remote Access
Network Profile Operation Automation
Monitoring 3ª Line Help Desk
Administration Solution Architect
Engineering
Project Management
<
10. Total Management
Zero Cost
Open Source
Clone Lapa?
Applications Settings Operating System
Updates Global Changes Inventory Validation
User Profile Security Remote Access
Network Profile Operation Automation
Monitoring 3ª Line Help Desk
Administration Solution Architect
Engineering
Project Management
12. Puppet
Why?
Help!
Settings Operating System
- Unix/Windows
- Equipment Access Control (Certificates)
- Team Access Control (Role Based Access Control)
- Puppet Forge
- Easy Learning
- Rules are interpreted in Runtime based on programmable Facts
18. Puppet
Classification
DB
Portal / Provision Server – Model/Function/Image
Vivo PC - Trusty - 20140808
Vivo PC - Trusty - 20141208
Asus P52F - 20140710
PuppetMaster - 20140809
Radius - 20131001
...
Puppet – Models
NN
N + N + Filtro Nome
(“serverp.*, serverd{2}", "serverp*, !serverp01", ".*, !serverp01”)
Puppet – Class
common::users
common::java
trusty::firefox
radius::freeradius
...
DEV
OPS
Settings Operating System
21. RabbitMQ
Comparison
Other MQs
Applications Settings
RabbitMQ is one of the leading implementation of the AMQP protocol (along with Apache Qpid).
Therefore, it implements a broker architecture, meaning that messages are queued on a central node before being sent to clients.
This approach makes RabbitMQ very easy to use and deploy, because advanced scenarios like routing, load balancing or
persistent message queuing are supported in just a few lines of code.
However, it also makes it less scalable and “slower” because the central node adds latency and message envelopes are quite big.
ZeroMQ is a very lightweight messaging system specially designed for high throughput/low latency scenarios
like the one you can find in the financial world.
Zmq supports many advanced messaging scenarios but contrary to RabbitMQ, you’ll have to implement most of them yourself
by combining various pieces of the framework (e.g : sockets and devices).
Zmq is very flexible but you’ll have to study the 80 pages or so of the guide
(which I recommend reading for anybody writing distributed system, even if you don’t use Zmq)
before being able to do anything more complicated that sending messages between 2 peers.
ActiveMQ is in the middle ground.
Like Zmq, it can be deployed with both broker and P2P topologies.
Like RabbitMQ, it’s easier to implement advanced scenarios but usually at the cost of raw performance.
It’s the Swiss army knife of messaging :-).
Finally, all 3 products:
• Have client APIs for the most common languages (C++, Java, .Net, Python, Php, Ruby, …)
• Have strong documentation
• Are actively supported
(Source: http://stackoverflow.com/questions/731233/activemq-or-rabbitmq-or-zeromq-or)
24. RabbitMQ
Retries and status
MySQL Table
Portal / Provision
MQ - Tasks
Task
Target
Correlation ID
Body
Reply
Status
Retries
Expire
Author
Applications Settings
DEV
36. Printing - Provision - Printers
BD → GIT → Puppet
Manual
Admins
Portal / Provision
Printer
Brand
Model
Location
IP
Mac
PPD File
Default Settings
37. Radius
Radius
Wi-Fi
WPA2-PEAP e TLS
Portal / Provision
Mac Address Authorization
User / Hostname
Email
Email Sent
Email When
Mac
Mac Manufacturer
VLAN
Authorization Author
AD