-
Notifications
You must be signed in to change notification settings - Fork 2
/
Copy pathpresentation.html
1149 lines (1117 loc) · 33.3 KB
/
presentation.html
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
946
947
948
949
950
951
952
953
954
955
956
957
958
959
960
961
962
963
964
965
966
967
968
969
970
971
972
973
974
975
976
977
978
979
980
981
982
983
984
985
986
987
988
989
990
991
992
993
994
995
996
997
998
999
1000
<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="UTF-8">
<meta name="generator" content="AsciiDoc 9.0.0rc2, html5 backend 4.5.0">
<title>42ITy presentation</title>
<meta name="viewport" content="width=device-width, initial-scale=1.0">
<!-- AsciiDoc Bootstrap styles -->
<link rel="stylesheet" type="text/css" id="bootstrapTheme" href="css/asciidoc-bootstrap.min.css">
<!--[if (lt IE 9) & (!IEMobile)]>
<script src="js/html5shiv.min.js"></script>
<script src="js/respond.min.js"></script>
<![endif]-->
<!-- 42ITy stylesheet -->
<link rel="stylesheet" type="text/css" href="css/42ity.css">
<!-- favorite icon -->
<link rel="shortcut icon" href="images/icons//favicon.ico">
</head>
<body id="toc-top">
<div id="page">
<header role="banner" class="Fixed">
<nav class="navbar navbar-default navbar-fixed-top" role="navigation">
<div class="container">
<div class="navbar-header">
<a class="navbar-brand" href="./">42ITy</a>
<button type="button" class="navbar-toggle" data-toggle="collapse" data-target=".navbar-collapse">
<span class="icon-bar"></span>
<span class="icon-bar"></span>
<span class="icon-bar"></span>
</button>
</div> <!-- /.navbar-header -->
<div class="navbar-collapse collapse">
<!-- Fixed navbar -->
<ul class="nav navbar-nav">
<li><a href="index.html">Home</a></li>
</ul>
<ul class="nav navbar-nav">
<li class="dropdown">
<a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" aria-haspopup="true" aria-expanded="false">Download<span class="caret"></span></a>
<ul class="dropdown-menu">
<li><a href="source.html">Source code</a></li>
<li><a href="binaries.html">Binaries</a></li>
</ul>
</li>
</ul>
<ul class="nav navbar-nav">
<li class="dropdown">
<a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" aria-haspopup="true" aria-expanded="false">Documentation<span class="caret"></span></a>
<ul class="dropdown-menu">
<li><a href="hcl.html">Supported Hardware</a></li>
<li role="separator" class="divider"></li>
<li><a href="presentation.html">Overall presentation</a></li>
<li><a href="contributing.html">Contributor guide</a></li>
</ul>
</li>
</ul>
<ul class="nav navbar-nav">
<li><a href="about.html">About</a></li>
</ul>
<ul class="nav navbar-nav">
<li><a href="contact.html">Contact</a></li>
</ul>
</div> <!-- /.navbar-collapse -->
</div> <!-- /.container -->
</nav>
</header>
<div id="content" class="container">
<div class="row">
<div class="col-md-9" role="main">
<div class="section">
<h1 class="page-header" id="general_overview">General overview</h1>
<div class="paragraph"><p>The 42ITy™ project promotes the global development, distribution and
adoption of the 42ITy™ platform as a next generation Data Center Service
Optimization enablement platform.</p></div>
<div class="paragraph"><p>The goal is to serve developers, users and the entire data center ecosystem
by providing a set of shared resources to grow the adoption of 42ITy™ as
the only open source, next generation Data Center Service Optimization
enablement platform.</p></div>
<div class="paragraph"><p>The initial 42ITy™ platform is a result of more than 5 years of R&D effort
by Eaton Corporation provided to the community. While Eaton continues to
be a key contributor to 42ITy™, the community is already growing. Please
read the
<a href="contributing.html">Contributor guide</a> to find out how you can
contribute.</p></div>
<div class="paragraph"><p>The 42ITy™ platform allows to connect together various software components to:</p></div>
<div class="ulist"><ul>
<li>
<p>
gather and store monitoring data from devices,
</p>
</li>
<li>
<p>
process these data to produce trends and metrics,
</p>
</li>
<li>
<p>
provide interaction to users, through a web user interface,
</p>
</li>
<li>
<p>
provide interaction to developers and 3rd party software, through a REST API.
</p>
</li>
</ul></div>
<div class="paragraph"><p>Typical integrations, which serves as reference implementations, are Eaton
Intelligent Power Manager 2 and
<a href="http://www.eaton.eu/ipminfrastructure">Eaton Intelligent Power Controller</a>:</p></div>
<div class="paragraph"><p><span class="image">
<img src="images/Eaton-IPC.png" alt="Eaton Intelligent Power Controller">
</span></p></div>
<h2 id="current_features_and_capabilities">Current features and capabilities</h2>
<div class="ulist"><ul>
<li>
<p>
Power device monitoring & metrics (rack PDUs, UPSs, ATSs,…)
</p>
</li>
<li>
<p>
Environmental monitoring & metrics (temp., humidity, dew point,…)
</p>
</li>
<li>
<p>
Historic & real time data
</p>
</li>
<li>
<p>
Composite & Datacenter or IT room level metrics
</p>
</li>
<li>
<p>
Open (REST API) communication interface
</p>
</li>
<li>
<p>
Micro-services & plug-in architecture
</p>
</li>
<li>
<p>
Simplified asset management
</p>
</li>
</ul></div>
<h2 id="future_availability">Future availability</h2>
<div class="ulist"><ul>
<li>
<p>
Builds (images & packages) provided for both ARM and x86 platforms
</p>
</li>
<li>
<p>
Easy & Intuitive standards based UI (AngularJS, Bootstrap)
</p>
</li>
</ul></div>
<h2 id="future_features_and_capabilities">Future features and capabilities</h2>
<div class="ulist"><ul>
<li>
<p>
Scale solution to large data center & distributed enterprise monitoring
</p>
<div class="ulist"><ul>
<li>
<p>
100s to 1000s of racks
</p>
</li>
</ul></div>
</li>
<li>
<p>
Expanded 3rd party monitoring ecosystem
</p>
<div class="ulist"><ul>
<li>
<p>
More 3rd party power device support
</p>
</li>
<li>
<p>
Genset monitoring
</p>
</li>
<li>
<p>
CRAC monitoring
</p>
</li>
<li>
<p>
3rd party sensors
</p>
</li>
</ul></div>
</li>
<li>
<p>
More depending on the 42ITy™ Community and partners feedback and requests.
</p>
</li>
</ul></div>
</div>
<div class="section">
<h1 class="page-header" id="technical_overview">Technical overview</h1>
<h2 id="architecture">Architecture</h2>
<div class="paragraph"><p>The 42ITy™ software platform is a Service Oriented Architecture (SOA), made of a
collection of software packages. These package provide agents (micro services) which
communicate through a MOM (Message-oriented middleware), built around the
<a href="http://zeromq.org">ZeroMQ</a> technology stack.</p></div>
<div class="paragraph"><p>The software is divided in a set of independent components, called <strong>agent</strong>.</p></div>
<div class="paragraph"><p><span class="image">
<img src="images/42ITy-SW-arch.png" alt="42ITy SW architecture">
</span></p></div>
<div class="paragraph"><p>Because we expect an arbitrary number of agents to be connected together,
42ITy™ uses a central message broker called Malamute.</p></div>
<div class="paragraph"><p>Malamute is built using the same ZeroMQ stack, so integrates with the code
easily. The purpose of malamute is to abstract from maintaining peer-to-peer
connections and to allow easy 1:N communication patterns without need to change
the agent side.</p></div>
<div class="paragraph"><p>At the moment there are three main patterns supported by Malamute broker:</p></div>
<div class="ulist"><ul>
<li>
<p>
PUB / SUB, Publish and Subscribe:
there are agents publishing messages with some topic, where others can subscribe
to them. Broker then ensures all messages are delivered to the right destination.
Communication is asynchronous - each PUB call is queued immediately and sending
does not block the code.
</p>
</li>
<li>
<p>
REQ / REP, Request and Reply:
this is a directed 1:1 communication, usable for requesting some information
from known place (persistence layer). It is synchronous, so blocking calling
code until there is a result (or timeout).
</p>
</li>
<li>
<p>
Service:
service is a dedicated agent, which can run in more instances spawned by broker
on demand. This is suitable for long running tasks. This is not used in
42ITy™ currently.
</p>
</li>
</ul></div>
<h2 id="mq_protocol_overview">MQ protocol overview</h2>
<div class="paragraph"><p>42ITy™ protocol consists of several layers:</p></div>
<div class="ulist"><ul>
<li>
<p>
Internet layer - raw libzmq/czmq sockets: this ensures messages are
serialized, deserialized, working with sockets and abstracts the underlying OS
layers (unix sockets, tcp sockets, …).
</p>
</li>
<li>
<p>
Transport layer - Malamute: this does ensures correct addressing, matching
subscribers with published messages and services.
</p>
</li>
<li>
<p>
Application layer - fty-proto: this provides a minimal set of messages to
encode and decode the main types of data flowing in the system.
</p>
</li>
</ul></div>
<div class="paragraph"><p>Refer to the project
<a href="https://en.wikipedia.org/wiki/Actor_model">fty-proto</a> for more information.</p></div>
<h2 id="dataflow_overview">Dataflow overview</h2>
<div class="paragraph"><p>This chapter will be completed later.</p></div>
<h2 id="agent_overview">Agent overview</h2>
<div class="paragraph"><p>Agents communicate through buses maintained by ZeroMQ library. Buses can use
several backend technologies, most notably unix and classic TCP/IP sockets. So
agents can be placed on the same machine or on arbitrary number of other
machines (currently out of scope). Because basic messaging using zeromq messages
(zmsg) is error prone with a lot of code duplication, 42ITy™ project uses
serialization library called zproto. It defines a model of message in
declarative XML language and code is generated using a template language called
gsl.</p></div>
<div class="paragraph"><p>Generated code does provide nice C API for manipulating with messages as well as
a way how to encode/decode it to/from zmsg. Thus such generated representations
can be easily sent through zeromq channels.</p></div>
<h3 id="actor_model">Actor model</h3>
<div class="paragraph"><p>Agents are built on top of the
<a href="https://en.wikipedia.org/wiki/Actor_model">actor model</a>.
That means that each agent maintains its own state internally and communicate
with the rest of the system by sending messages. The communication is
asynchronous and agents are single threaded with the main loop. For cases where
the single main loop is not enough due to performance reasons, agent can
distribute workload to others using SERVICE pattern. However this is not used in
current version of 42ITy™.</p></div>
<h3 id="how_to_create_a_new_agent">How to create a new agent</h3>
<div class="paragraph"><p>There are various ways to create a new 42ITy agent:</p></div>
<div class="ulist"><ul>
<li>
<p>
create from scratch:
This is the hardest way, creating a zproject project.xml file. There are
<a href="https://github.com/zeromq/zproject/blob/master/README.md">guides and tutorials</a>
which explains this, and are otherwise needed to further complete your agent.
</p>
</li>
<li>
<p>
fork one of the github example project, which provides instructions and
serves as a reference on how to create a new 42ITy™:
</p>
<div class="ulist"><ul>
<li>
<p>
<a href="https://github.com/42ity/fty-example">fty-example</a>
</p>
</li>
<li>
<p>
<a href="https://github.com/42ity/fty-template">fty-template</a>
</p>
</li>
</ul></div>
</li>
</ul></div>
<h2 id="rest_api_communication_interface">REST API communication interface</h2>
<div class="paragraph"><p>42ITy™ also exposes its data through a REST API.</p></div>
<div class="paragraph"><p>Complete documentation using RAML is available:</p></div>
<div class="ulist"><ul>
<li>
<p>
<a href="doc/rest/42ity_rest_api.raml">RAML source format</a>
</p>
</li>
<li>
<p>
<a href="doc/rest/42ity_rest_api.html">RAML HTML format</a>
</p>
</li>
</ul></div>
<h3 id="how_to_create_a_new_rest_api_mountpoint">How to create a new REST API mountpoint</h3>
<div class="paragraph"><p>42ITy uses Tntnet webserver, which provides simple mechanisms to create new REST
servlets.</p></div>
<div class="paragraph"><p>There are
<a href="http://www.tntnet.org/tntnet.html">tutorials</a>, but you may also
look at fty-rest and other fty-rest-* components as references.</p></div>
<div class="paragraph"><p>You may fork the
<a href="https://github.com/42ity/fty-template-rest">fty-template-rest</a>
repository.</p></div>
</div>
<div class="section">
<h1 class="page-header" id="42ity_8482_software_stack">42ITy™ software stack</h1>
<h2 id="42ity_8482_external_projects">42ITy™ external projects</h2>
<div class="paragraph"><p>42ITy™ foundations rely on several major opensource projects, to provide some
generic core services, such as data storage, communication with devices,
communication between agents, web user interface and REST API, and build added
value on top of these.</p></div>
<h3 id="malamute">Malamute</h3>
<div class="paragraph"><p><a href="https://github.com/zeromq/malamute">Malamute</a> is the ZeroMQ Enterprise
Messaging Broker, providing all the enterprise messaging patterns in one box.</p></div>
<div class="paragraph"><p>42ITy™ uses Malamute as the broker connecting the different 42ITy™ agents (see
internal sub-projects).</p></div>
<h3 id="mariadb_mysql">MariaDB - MySQL</h3>
<div class="paragraph"><p><a href="https://mariadb.org">MariaDB</a> is one of the most popular database servers in
the world, made by the original developers of
<a href="http://www.mysql.com">MySQL</a>
and guaranteed to stay open source.</p></div>
<div class="paragraph"><p>42ITy™ uses MariaDB to store the realtime data, gathered from devices, and
processed metrics.</p></div>
<h3 id="nut_network_ups_tools">NUT - Network UPS Tools</h3>
<div class="paragraph"><p><a href="http://networkupstools.org">NUT - Network UPS Tools</a> is a project which
provides support for a wide range of power devices, such as UPS, PDU and ATS.</p></div>
<div class="paragraph"><p>42ITy™ uses NUT to gather data from network power devices.</p></div>
<h3 id="tntnet">Tntnet</h3>
<div class="paragraph"><p><a href="http://www.tntnet.org/">Tntnet</a> is a modular, multithreaded web application
server for C++.</p></div>
<div class="paragraph"><p>42ITy™ uses Tntnet to serve web user interface and REST API.</p></div>
<h2 id="42ity_8482_internal_sub_projects">42ITy™ internal sub-projects</h2>
<div class="paragraph"><p>This chapter briefly presents the different sub-projects that forms the 42ITy™
platform. More detailed information can be found on the dedicated pages of these
sub-projects.</p></div>
<div class="paragraph"><p>Each of these sub-projects is available as a repository on
<a href="http://github.com/42ity">42ITy</a> GitHub page, and provides a README file,
with various information on its purpose, its provided services (through STREAMS)
and data.</p></div>
<h3 id="general_projects">General projects</h3>
<h4>fty-core</h4>
<div class="ulist"><ul>
<li>
<p>
Description: fty-core implements the core and central functionalities for
42ITy, by providing DB setup, OS integration and image creation scripts, …
</p>
</li>
<li>
<p>
Repository: <a href="https://github.com/42ity/fty-core">https://github.com/42ity/fty-core</a>
</p>
</li>
</ul></div>
<h4>fty-proto</h4>
<div class="ulist"><ul>
<li>
<p>
Description: fty-proto is the shared implementation of 42ITy™ core
protocols, using Malamute and used by the different agents (assets, metrics,
alerts).
</p>
</li>
<li>
<p>
Repository: <a href="https://github.com/42ity/fty-proto">https://github.com/42ity/fty-proto</a>
</p>
</li>
</ul></div>
<h4>fty-shm</h4>
<div class="ulist"><ul>
<li>
<p>
Description: fty-shm is lockless metric sharing library for 42ity.
</p>
</li>
<li>
<p>
Repository: <a href="https://github.com/42ity/fty-shm">https://github.com/42ity/fty-shm</a>
</p>
</li>
</ul></div>
<h3 id="common_libraries">Common libraries</h3>
<h4>fty-common</h4>
<div class="ulist"><ul>
<li>
<p>
Description: fty-common provides core shared code for all fty projects.
</p>
</li>
<li>
<p>
Repository: <a href="https://github.com/42ity/fty-common">https://github.com/42ity/fty-common</a>
</p>
</li>
</ul></div>
<h4>fty-common-db</h4>
<div class="ulist"><ul>
<li>
<p>
Description: fty-common-db provides a common library with database-related
functions.
</p>
</li>
<li>
<p>
Repository: <a href="https://github.com/42ity/fty-common-db">https://github.com/42ity/fty-common-db</a>
</p>
</li>
</ul></div>
<h4>fty-common-dto</h4>
<div class="ulist"><ul>
<li>
<p>
Description: fty-common-dto provides a common library with common objects
manipulation and inter-agents communication.
</p>
</li>
<li>
<p>
Repository: <a href="https://github.com/42ity/fty-common-dto">https://github.com/42ity/fty-common-dto</a>
</p>
</li>
</ul></div>
<h4>fty-common-logging</h4>
<div class="ulist"><ul>
<li>
<p>
Description: fty-common-logging provides a common library for shared logging.
</p>
</li>
<li>
<p>
Repository: <a href="https://github.com/42ity/fty-common-logging">https://github.com/42ity/fty-common-logging</a>
</p>
</li>
</ul></div>
<h4>fty-common-messagebus</h4>
<div class="ulist"><ul>
<li>
<p>
Description: fty-common-messagebus provides a common library with methods
for Request/Reply and Publish/Subscribe patterns on malamute.
</p>
</li>
<li>
<p>
Repository: <a href="https://github.com/42ity/fty-common-messagebus">https://github.com/42ity/fty-common-messagebus</a>
</p>
</li>
</ul></div>
<h4>fty-common-mlm</h4>
<div class="ulist"><ul>
<li>
<p>
Description: fty-common-mlm provides a common library with mlm/zmq-related
functions.
</p>
</li>
<li>
<p>
Repository: <a href="https://github.com/42ity/fty-common-mlm">https://github.com/42ity/fty-common-mlm</a>
</p>
</li>
</ul></div>
<h4>fty-common-nut</h4>
<div class="ulist"><ul>
<li>
<p>
Description: fty-common-nut provides a common library to interact with
NUT - Network UPS Tools, and interpret its provided data (including mapping
between NUT and 42ITy variables).
</p>
</li>
<li>
<p>
Repository: <a href="https://github.com/42ity/fty-common-nut">https://github.com/42ity/fty-common-nut</a>
</p>
</li>
</ul></div>
<h4>fty-common-socket</h4>
<div class="ulist"><ul>
<li>
<p>
Description: fty-common-socket provides common classes and function to
handle inter process communication using unix socket.
</p>
</li>
<li>
<p>
Repository: <a href="https://github.com/42ity/fty-common-socket">https://github.com/42ity/fty-common-socket</a>
</p>
</li>
</ul></div>
<h4>fty-common-translation</h4>
<div class="ulist"><ul>
<li>
<p>
Description: fty-common-translation provides a common library with
translation-related functions.
</p>
</li>
<li>
<p>
Repository: <a href="https://github.com/42ity/fty-common-translation">https://github.com/42ity/fty-common-translation</a>
</p>
</li>
</ul></div>
<h4>fty-common-rest</h4>
<div class="ulist"><ul>
<li>
<p>
Description: fty-common-rest provides a common library with
REST API related functions.
</p>
</li>
<li>
<p>
Repository: <a href="https://github.com/42ity/fty-common-rest">https://github.com/42ity/fty-common-rest</a>
</p>
</li>
</ul></div>
<h3 id="miscellaneous">Miscellaneous</h3>
<h4>fty-asset</h4>
<div class="ulist"><ul>
<li>
<p>
Description: fty-asset is the agent in charge of managing information about
assets.
</p>
</li>
<li>
<p>
Repository: <a href="https://github.com/42ity/fty-asset">https://github.com/42ity/fty-asset</a>
</p>
</li>
</ul></div>
<h4>fty-asset-activator</h4>
<div class="ulist"><ul>
<li>
<p>
Description: fty-asset-activator is a library with accessor functions for
activation/deactivation of assets.
</p>
</li>
<li>
<p>
Repository: <a href="https://github.com/42ity/fty-asset-activator">https://github.com/42ity/fty-asset-activator</a>
</p>
</li>
</ul></div>
<h4>fty-info</h4>
<div class="ulist"><ul>
<li>
<p>
Description: fty-info returns rack controller information.
</p>
</li>
<li>
<p>
Repository: <a href="https://github.com/42ity/fty-info">https://github.com/42ity/fty-info</a>
</p>
</li>
</ul></div>
<h4>fty-mdns-sd</h4>
<div class="ulist"><ul>
<li>
<p>
Description: fty-mdns-sd manages network announcement (mDNS) and discovery
(DNS-SD).
</p>
</li>
<li>
<p>
Repository: <a href="https://github.com/42ity/fty-mdns-sd">https://github.com/42ity/fty-mdns-sd</a>
</p>
</li>
</ul></div>
<h4>fty-srr</h4>
<div class="ulist"><ul>
<li>
<p>
Description: fty-srr is an agent who is in charge Saving, Restoring, and
Reseting the system.
</p>
</li>
<li>
<p>
Repository: <a href="https://github.com/42ity/fty-srr">https://github.com/42ity/fty-srr</a>
</p>
</li>
</ul></div>
<h3 id="discovery_configuration_and_monitoring">Discovery, configuration and monitoring</h3>
<h4>fty-discovery</h4>
<div class="ulist"><ul>
<li>
<p>
Description: fty-discovery is an agent that discovers power devices
over the network and publishes new device elements in the asset DB.
</p>
</li>
<li>
<p>
Repository: <a href="https://github.com/42ity/fty-discovery">https://github.com/42ity/fty-discovery</a>
</p>
</li>
</ul></div>
<h4>fty-nut</h4>
<div class="ulist"><ul>
<li>
<p>
Description: fty-nut is an agent that polls power devices (UPS and PDU) using
NUT drivers, through NUT server (upsd). It collects current measurements and
publishes them. It also collects static inventory data (assets) and publishes
them.
</p>
</li>
<li>
<p>
Repository: <a href="https://github.com/42ity/fty-nut">https://github.com/42ity/fty-nut</a>
</p>
</li>
</ul></div>
<h4>fty-sensor-env</h4>
<div class="ulist"><ul>
<li>
<p>
Description: fty-sensor-env is the agent communicating with environmental
sensors to gather temperature and humidity data.
</p>
</li>
<li>
<p>
Repository: <a href="https://github.com/42ity/fty-sensor-env">https://github.com/42ity/fty-sensor-env</a>
</p>
</li>
</ul></div>
<h4>fty-sensor-gpio</h4>
<div class="ulist"><ul>
<li>
<p>
Description: fty-sensor-gpio is the agent to manage GPIO sensors and devices.
</p>
</li>
<li>
<p>
Repository: <a href="https://github.com/42ity/fty-sensor-gpio">https://github.com/42ity/fty-sensor-gpio</a>
</p>
</li>
</ul></div>
<h3 id="metrics_generation_amp_processing">Metrics Generation & Processing</h3>
<h4>fty-metric-compute</h4>
<div class="ulist"><ul>
<li>
<p>
Description: fty-metric-compute provides computation services on metrics.
</p>
</li>
<li>
<p>
Repository: <a href="https://github.com/42ity/fty-metric-compute">https://github.com/42ity/fty-metric-compute</a>
</p>
</li>
</ul></div>
<h4>fty-metric-ambient-location</h4>
<div class="ulist"><ul>
<li>
<p>
Description: fty-metric-ambient-location is the agent computing the average
humidity and temperature of each locations, based on sensor metrics.
</p>
</li>
<li>
<p>
Repository: <a href="https://github.com/42ity/fty-metric-ambient-location">https://github.com/42ity/fty-metric-ambient-location</a>
</p>
</li>
</ul></div>
<h4>fty-metric-tpower</h4>
<div class="ulist"><ul>
<li>
<p>
Description: fty-metric-tpower is the agent computing total datacenters,
rooms, rows and racks power metrics from measurements.
</p>
</li>
<li>
<p>
Repository: <a href="https://github.com/42ity/fty-metric-tpower">https://github.com/42ity/fty-metric-tpower</a>
</p>
</li>
</ul></div>
<h4>fty-metric-composite</h4>
<div class="ulist"><ul>
<li>
<p>
Description: fty-metric-composite is an agent that generates composite
metrics, that is to say metrics which are computed from several other metrics.
Rules are defined as scripts written in Lua.
</p>
</li>
<li>
<p>
Repository: <a href="https://github.com/42ity/fty-metric-composite">https://github.com/42ity/fty-metric-composite</a>
</p>
</li>
</ul></div>
<h4>fty-kpi-power-uptime</h4>
<div class="ulist"><ul>
<li>
<p>
Description: fty-kpi-power-uptime computes and publishes KPI (Key Performance
Indicator) for data center power uptime, taking into account how long one of the
main power sources was offline.
</p>
</li>
<li>
<p>
Repository: <a href="https://github.com/42ity/fty-kpi-power-uptime">https://github.com/42ity/fty-kpi-power-uptime</a>
</p>
</li>
</ul></div>
<h4>fty-warranty</h4>
<div class="ulist"><ul>
<li>
<p>
Description: fty-warranty is the agent that generates and sends alerts when a
device does not communicate.
</p>
</li>
<li>
<p>
Repository: <a href="https://github.com/42ity/fty-warranty">https://github.com/42ity/fty-warranty</a>
</p>
</li>
</ul></div>
<h3 id="real_time_and_history_data">Real time and history data</h3>
<h4>fty-metric-cache</h4>
<div class="ulist"><ul>
<li>
<p>
Description: fty-metric-cache is the agent providing current values of any
metric in the system.
</p>
</li>
<li>
<p>
Repository: <a href="https://github.com/42ity/fty-metric-cache">https://github.com/42ity/fty-metric-cache</a>
</p>
</li>
</ul></div>
<h4>fty-metric-store</h4>
<div class="ulist"><ul>
<li>
<p>
Description: fty-metric-store provides the persistance layer for metrics.
</p>
</li>
<li>
<p>
Repository: <a href="https://github.com/42ity/fty-metric-store">https://github.com/42ity/fty-metric-store</a>
</p>
</li>
</ul></div>
<h3 id="alerts_and_notifications">Alerts and notifications</h3>
<h4>fty-alert-engine</h4>
<div class="ulist"><ul>
<li>
<p>
Description: fty-alert-engine is the agent that evaluates threshold based rules
written in Lua and produces alerts accordingly.
</p>
</li>
<li>
<p>
Repository: <a href="https://github.com/42ity/fty-alert-engine">https://github.com/42ity/fty-alert-engine</a>
</p>
</li>
</ul></div>
<h4>fty-alert-flexible</h4>
<div class="ulist"><ul>
<li>
<p>
Description: fty-alert-flexible is the agent that evaluates non threshold based
rules (status, advanced metrics, …) written in Lua and produces alerts accordingly.
</p>
</li>
<li>
<p>
Repository: <a href="https://github.com/42ity/fty-alert-flexible">https://github.com/42ity/fty-alert-flexible</a>
</p>
</li>
</ul></div>
<h4>fty-alert-list</h4>
<div class="ulist"><ul>
<li>
<p>
Description: fty-alert-list is the agent that provides information about
active and resolved alerts.
</p>
</li>
<li>
<p>
Repository: <a href="https://github.com/42ity/fty-alert-list">https://github.com/42ity/fty-alert-list</a>
</p>
</li>
</ul></div>
<h4>fty-alert-stats</h4>
<div class="ulist"><ul>
<li>
<p>
Description: fty-alert-stats computes metric statistics on alerts.
</p>
</li>
<li>
<p>
Repository: <a href="https://github.com/42ity/fty-alert-stats">https://github.com/42ity/fty-alert-stats</a>
</p>
</li>
</ul></div>
<h4>fty-email</h4>
<div class="ulist"><ul>
<li>
<p>
Description: fty-email is the agent in charge of generating and sending
email notifications.
</p>
</li>
<li>
<p>
Repository: <a href="https://github.com/42ity/fty-email">https://github.com/42ity/fty-email</a>
</p>
</li>
</ul></div>
<h4>fty-outage</h4>
<div class="ulist"><ul>
<li>
<p>
Description: fty-outage is the agent that generates and sends alerts when a
device does not communicate.
</p>
</li>
<li>
<p>
Repository: <a href="https://github.com/42ity/fty-outage">https://github.com/42ity/fty-outage</a>
</p>
</li>
</ul></div>
<h3 id="security">Security</h3>
<h4>fty-security-wallet</h4>
<div class="ulist"><ul>
<li>
<p>
Description: fty-security-wallet is the agent providing a central and secure
storage for credential documents.
</p>
</li>
<li>
<p>
Repository: <a href="https://github.com/42ity/fty-security-wallet">https://github.com/42ity/fty-security-wallet</a>
</p>
</li>
</ul></div>
<h4>fty-certificate-generator</h4>
<div class="ulist"><ul>
<li>
<p>
Description: fty-certificate-generator is the agent which generates security
certificates.
</p>
</li>
<li>
<p>
Repository: <a href="https://github.com/42ity/fty-certificate-generator">https://github.com/42ity/fty-certificate-generator</a>
</p>
</li>
</ul></div>
<h4>fty-lib-certificate</h4>
<div class="ulist"><ul>
<li>
<p>
Description: fty-lib-certificate is a library providing helper class
for SSL certificate handling.
</p>
</li>
<li>
<p>
Repository: <a href="https://github.com/42ity/fty-lib-certificate">https://github.com/42ity/fty-lib-certificate</a>
</p>
</li>
</ul></div>
<h3 id="rest_api">REST API</h3>
<h4>fty-rest</h4>
<div class="ulist"><ul>
<li>
<p>
Description: fty-rest is the main component extending Tntnet and
implementing 42ITy™ REST API.
</p>
</li>
<li>
<p>
Repository: <a href="https://github.com/42ity/fty-rest">https://github.com/42ity/fty-rest</a>
</p>
</li>
</ul></div>
<h4>Other REST servlets</h4>
<div class="paragraph"><p>The following servlets provide specific mountpoints and services:</p></div>
<div class="ulist"><ul>
<li>
<p>
fty-scripts-rest: <a href="https://github.com/42ity/fty-scripts-rest">https://github.com/42ity/fty-scripts-rest</a>
</p>
</li>
<li>
<p>
fty-asset-mapping-rest: <a href="https://github.com/42ity/fty-asset-mapping-rest">https://github.com/42ity/fty-asset-mapping-rest</a>
</p>
</li>
<li>