Virtualization and IIoT with Literature & Containers

Transcription

1 Virtualization and IIoT with Literature & Containers CS-E5470 Seminar on Embedded Systems P (3-5 cr) Autumn 2016 (II), Paper draft session Vesa Hirvisalo

2 Today Scientific writing Typical scientific contributions Scientific discussion, publications and forums Structure of typical scientific papers Survey papers and extended abstracts Draft review Initial papers per topic The operation of a program committee Joint material The role of the wiki for this More instruction on the practical side Sensing topic assignment About the backends 2

3 Scientific writing 3

4 Typical scientific contributions In making science, novelty is essential You do something fundamental that has not been done before There different aspects of novels Not all things are fundamental Difference between research, applicative research and basic research Many thing in your daily life are unique but they are not science Very often the context is an action of a community Science is rarely done alone or in isolation Usually your work is very focused You (and your team) does a very small part Your effort impacts the larger front of science 4

5 Scientific methods Often you do an experiment E.g., in engineering, construct something and measure However, there are a number of different approaches But, there exists also many other ways People are very creative and innovative After all, the main issue is did you do something novel However, methods are typically central They make scientific work science You apply a method that people can trust They trust also your results You do things that other people can understand Note the caveats, especially for engineering E.g., you work with your fancy system, but actually: if nobody can understand your system, it is very hard to make science about it 5

6 Scientific discussion Scientific discussion is usually structured Basically, you cannot say things without giving grounds, justification, proof, etc. Usually happens with written material There you have your thesis and your proof Science should be free, public, and independent è publications Forums Written only: typically Journals (full papers), letter journals, Meeting, presenting and discussing Conferences and workshops And of course, there are other forms Organizing the forums Scientific organizations, editorial boards, program committees 6

7 Structure of typical scientific papers The classical way is to report an experiment What was done and observed, how and why it was done The classical basic structure = IMRAD Introduction, what this paper is about E.g.: overview, problem, criteria, related work, results, presentation Method, how the experiment was done Results, what anyone would get using the method Analysis, what do the results mean (in the given context) Discussion, what authors think about the results There are many variations However, even a M.Sc.(Tech.) thesis follows these principles Theses on technical topics often report an experiment 7

8 Survey papers and extended abstracts Survey papers Report what others have done Based on already published material (i.e., literature survey) Usually done (or supervised) by seniors of a community Abstract Short description of a paper (e.g., overview,problem,results) Extended abstract An abstract with a proper presentation (wrt IMRAD) A condensed version (of a full paper) that is quick to understand A short paper is a paper that is short (note the difference) Joining these two approaches Not typical in science, but useful as a student exercise 8

9 Draft review 9

10 Container orchestration Cluster management Machines that are connected by a network Often about scheduling tasks on the nodes Resemble (somewhat) operating systems Instead of a single machine However, typically not with a holistic view of all services Container management Pretty much the same thing for containers Kubernetes is a typical example Mechanisms for deploying, maintaining, and scaling applications The cluster handles pods consisting of one or more containers There are many other manager A survey approach can be used here 10

11 Microservices Monolithic approach The typical way to build services We have a huge and complex back end Comparison toward the success of Unix Composing larger applications from simple one If you implement something basic, make it small and do it well Tackling with complexity Note that the complexity is still there E.g., the fight between monolithic kernels and microkernel The path lead to micro-modular kernels Remember what software is about Multiple views into a systems 11

12 Mobile edge computing (MEC) The cellular communication infra The network and its edge Radio Access Network (RAN) 3GPP family (versus WiFi etc.) Placing computation close to the edge Fast response times, high bandwidth, etc. Note that base stations are the main energy consumer for many applications MEC is an ETSI concept, but there exists many others Fog computing, cloudlets, etc. They all mean (almost) the same In an industrial setting Think of factory site, or an industrial campus, etc. 12

13 Container migration Migration in distributed systems Moving computation to a different node Migration is difficult Not only because load balancing (etc.) Computation context is often complicated Hardware status, open files, buffer contents,... Containers offer new possibilities Containers are more holistic Viewed from the context handling E.g., compared with process migration There different flavors Live migration Some prototypes exist for containers 13

14 Message queues Client-Server Who+Where: Space coupling What: Structural coupling When: Time coupling Server Req/Reply Client There are other architectures Message queues support different ways Publisher E.g.: typical Web services Publisher Subscriber Pub/Sub What: Structural coupling Subscriber 14

15 The (cloud) practical side 15

16 About the backends Datacenter to Internet traffic is huge Traffic inside the data centers (M2M) is several orders of magnitude larger Despite application efficiency optimizations the rate of M2M traffic growth is exponential Traditional hierarchical cluster based designs do not scale with growing traffic New approach is to make the entire data center building one high-performance network A large network with a complex topology and many devices and interconnects cannot be configured and operated in a manual way Management by a small team using automated tools is a requirement Source: Facebook 16

17 Automated config and management tools MAAS Metal-As-A-Service Automates the deployment and dynamic provisioning of computing environments A layer underneath Infrastructure-as-a-Service (IaaS) Physical servers can be managed as virtual machines in the cloud JUJU Automatic deployment and management of cloud applications Targets public and private clouds, physical servers, containers Complex system, e.g. OpenStack, many applications need to be installed, configured and connected to each other MAAS + JUJU Scale services up or down Eg. temporarily assign servers from OpenStack to Hadoop Credit: J.Hanhirova/Aalto 17

18 OpenStack Software platform for cloud computing Consists of interrelated components that control heterogeneous hardware pools of processing, storage, and networking resources in a data center Most of the components are executed inside containers, they are communicating using message queues Installation and management requires automated tools Source: openstack.org 18

19 Hybrid cloud A mix of private cloud and public cloud E.g. A private cloud on inhouse hardware resources, with the capability of bursting workloads to the public cloud as necessary Advantages: No overprovisioning of hardware in private cloud, Security, flexibility Integration of private and public cloud is not easy, especially when more crossover capability is needed Source: amax.com 19

20 Containers and cloud OpenStack components are mostly executed inside containers On top of OpenStack one can run e.g. Kubernetes to manage containers Kubernetes can also be executed on server hardware (using JUJU for example) Recently OpenStack has been factored to be run on top Kubernetes LXC LinuX Containers (LXC) is an operating system-level virtualization method for running multiple isolated Linux systems (containers) on a single control host (LXC host) Command line client lxc: userspace interface for the Linux kernel containment features LXD a container hypervisor composed of a daemon (lxd), its command-line interface (lxc) and a OpenStack plugin 20

21 Hands on with the backend side The essential thing within the backend is the structure of the sensor data processing Fancy algorithms (etc.) are not required Make something simple, e.g., average temperatures and temperature gradients with a temperature sensor With a single device you can demonstrate only partially However, you can mimic the rest For experimenting we provide A remote server machine with lxd Can execute your containerized applications Reachable using NetLeap LTE or Wifi Discuss and ask the details (with the assistant) 21

22 The embedded practical side 22

23 Sensing topic assignment There several sensors available Each of the ones doing the practical assignment should select We will make the HW available in the lab as requested The HW is not for personal use Should be kept in the lab as many of the resources are shared Computing HW There 2 Resperrys available and some workstations Getting other HW there is possible Sensors available 2 USB devices 4 digital sensors 2 analog sensors 23

24 USB devices Raspberry Pi camera module x2 User guide: Raspberry Pi camera interface There are built-in Raspberry Pi's functions Can be programmed in Python with Picamera Raspberry Pi infrared camera module x1 User guide: Raspberry pi camera interface There are built-in Raspberry Pi's functions Logitech C920 webcam quick-start-guide.pdf USB interface 24

25 Digital I/O devices Ultrasonic Ranging module x1 HCSR-04: Digital I/O Possible library to use: IMU sensor x1 9-axis sensor: SparkFun IMU Breakout - MPU-9250: MPU9250REV1.0.pdf Digital I/O Possible library to use in C++: There is also Python binding library: python 25

26 Digital I/O devices Thermo-humidity-meter DHT22/AM2302 module: Already connected to resistors (Can be connected straight to Raspberry Pi GPIO) Digital I/O Can be programmed with WiringPi and lol_dht99: 26

27 Analog I/O devices Thermometer x2 Melexis-MXL90614ESF: sumelexis_ir-tempsensor_en.pdf?mime=application%2fpdf There are two modes of output: PWM and SMBUS (Possible to use Python library smbus: Analog temperature sensor x1 TMP36GZ: Analog output May use an Arduino as an ADC and interface with Raspi 27

28 Analog I/O devices Vibration sensor x3 MiniSense 100 Vibration Sensor: %20Specialties%20PDFs/MiniSense_100.pdf Non-trivial analog output This is not an easy sensor May need analog circuitry to adjust its operation and output May use an Arduino as an ADC and interface with Raspi There can be also work with the digital side 28

29 Questions? 29