Differences

This shows you the differences between two versions of the page.

--- mission:log:2015:01:08:virtual-flight-control-center-opened [2015/01/08 23:10] – chrono
+++ mission:log:2015:01:08:virtual-flight-control-center-opened [2015/01/15 19:19] (current) – [Virtual Flight Control Center now public] chrono
@@ Line 1: / Line 1: @@
 ====== Virtual Flight Control Center now public ======
-In order to have total system control for crew/guests and to be more transparent about the technology and infrastructure in use and to give people another way to get into the detailed aspects and challenges of this project, the [[https://apollo.open-resource.org/flight-control/vfcc/|Virtual Flight Control Center (VFCC)]] is now open to the public. This is just a first step, the more technology is implemented the more features the VFCC will have. It's a little bit early in the projects timeline but became necessary as a proving ground for the [[lab:ucsspm|UCSSPM]].
+In order to have total system control for crew/guests and to be more transparent about the technology and infrastructure in use and to give people another way to get into the detailed aspects and challenges of this project, the [[https://apollo.open-resource.org/flight-control/vfcc/|Virtual Flight Control Center (VFCC)]] is now open to the public. This is just a first step, as more technology is implemented, the VFCC will have more features. It's a little bit early in the projects timeline but became necessary as a proving ground for the [[lab:ucsspm|UCSSPM]].
 {{:mission:apollo-ng-vfcc-virtual-flight-control-center.jpg?|Screenshot of VFCC System Overview}}
-For obvious reasons, the public VFCC doesn't allow control and data access is read-only, so you can play with it as much as you like without having to worry about breaking anything.
+If you want to see more than just screenshots open the **[[https://apollo.open-resource.org/flight-control/vfcc/|Virtual Flight Control Center (VFCC)]]**.
+Be aware that we do not care about testing/supporting closed-source, IP encumbered browsers at all. Also you'll probably need at least 7" of display size since it doesn't automatically resize yet and grafana's graph rendering has a tendency to overload mobile browsers, so phones are currently not the best choice to play with it :) For obvious reasons, the public VFCC doesn't allow control and data access is read-only, so you can play with it as much as you like without having to worry about breaking anything.
 {{:mission:control:apollo-ng-vfcc-screenshot.jpg?|Screenshot of one of the VFCC Dashboards}}
 It's still a very crude and hackish demonstrator, combining the following open-source components:
+==== Backend  ====
   * [[https://collectd.org/|collectd]] - gathering all kinds of system metrics
+  * [[https://github.com/bpaquet/node-logstash|node-logstash]] - lightweight logstasher
+  * [[https://github.com/etsy/statsd|statsd]] - easy log aggregation (for node-logstash)
   * [[http://influxdb.com/|InfluxDB]] - storing all timeseries
+==== Frontend ====
   * [[http://grafana.org/|Grafana]] - graphing all the metrics
-  * [[http://tutorials.jenkov.com/svg/index.html|SVG]] - used for the system overview (more overlays for different aspects to come)
+  * SVG - used for the system overview
+    * [[http://tutorials.jenkov.com/svg/index.html|Basic Tutorials]]
+    * [[https://docs.webplatform.org/wiki/svg/tutorials/smarter_svg_animation|Advanced Animation]]
   * And some plain Javascript to glue it all together

User Tools

Site Tools

Differences

Page Tools