All Projects → GENIVI → Vsomeip

GENIVI / Vsomeip

Licence: other
An implementation of Scalable service-Oriented MiddlewarE over IP

Projects that are alternatives of or similar to Vsomeip

seagull
Configuration server submodule for all SeaSerives
Stars: ✭ 19 (-93.75%)
Mutual labels:  service-discovery
IoTCodeRecipes
IoT Code Recipes: RPL, mDNS and REST
Stars: ✭ 19 (-93.75%)
Mutual labels:  service-discovery
prometheus-hetzner-sd
Prometheus Service Discovery for Hetzner
Stars: ✭ 15 (-95.07%)
Mutual labels:  service-discovery
Microgateway
Security and management for microservices, with rich functionalities of the CA API Gateway family
Stars: ✭ 35 (-88.49%)
Mutual labels:  service-discovery
sidecar
Gossip-based service discovery. Docker native, but supports non-container discovery, too.
Stars: ✭ 62 (-79.61%)
Mutual labels:  service-discovery
Home
This is the old home for the Steeltoe project. Please refer to the SteeltoeOSS/steeltoe repository moving forward.
Stars: ✭ 49 (-83.88%)
Mutual labels:  service-discovery
serverless-cloudmap
Serverless plugin for Cloudmap
Stars: ✭ 18 (-94.08%)
Mutual labels:  service-discovery
Juno
Juno 译名朱诺。这个名字来源于古罗马神话中的众神之母。它是斗鱼的微服务管理系统, 如同众神之母一样守护着所有微服务的系统。
Stars: ✭ 285 (-6.25%)
Mutual labels:  service-discovery
lagom-on-kube
This tutorial describes how to bootstrap a production-ready Lagom microservices cluster in a Kubernetes environment.
Stars: ✭ 58 (-80.92%)
Mutual labels:  service-discovery
superdiscoverer
A Supervisor backed service discoverer for automatic service-discovery.
Stars: ✭ 15 (-95.07%)
Mutual labels:  service-discovery
gorift
A toolkit for reverse proxy and load balancer
Stars: ✭ 20 (-93.42%)
Mutual labels:  service-discovery
RedTeam toolkit
Red Team Toolkit is an Open-Source Django Offensive Web-App which is keeping the useful offensive tools used in the red-teaming together.
Stars: ✭ 301 (-0.99%)
Mutual labels:  service-discovery
OneNodeEcs
one node Amazon ECS cluster using EC2 Spot instance and haproxy
Stars: ✭ 22 (-92.76%)
Mutual labels:  service-discovery
Nidan
An active network monitor tool
Stars: ✭ 24 (-92.11%)
Mutual labels:  service-discovery
Aspnet Servicediscovery Patterns
Samples of simple service discovery patterns with ASP .NET Core
Stars: ✭ 265 (-12.83%)
Mutual labels:  service-discovery
ObsidianSailboat
Nmap and NSE command line wrapper in the style of Metasploit
Stars: ✭ 36 (-88.16%)
Mutual labels:  service-discovery
coredns
CoreDNS is a DNS server that chains plugins
Stars: ✭ 8,962 (+2848.03%)
Mutual labels:  service-discovery
Eureka Js Client
JS implementation of a client for Eureka (https://github.com/Netflix/eureka), the Netflix OSS service registry.
Stars: ✭ 293 (-3.62%)
Mutual labels:  service-discovery
Cyberscan
CyberScan: Network's Forensics ToolKit
Stars: ✭ 280 (-7.89%)
Mutual labels:  service-discovery
yurpc
high-performance RPC framework.
Stars: ✭ 59 (-80.59%)
Mutual labels:  service-discovery

vsomeip

Copyright

Copyright (C) 2015-2017, Bayerische Motoren Werke Aktiengesellschaft (BMW AG)

License

This Source Code Form is subject to the terms of the Mozilla Public License, v. 2.0. If a copy of the MPL was not distributed with this file, You can obtain one at http://mozilla.org/MPL/2.0/.

vsomeip Overview

The vsomeip stack implements the http://some-ip.com/ (Scalable service-Oriented MiddlewarE over IP (SOME/IP)) protocol. The stack consists out of:

  • a shared library for SOME/IP (libvsomeip3.so)
  • a second shared library for SOME/IP's service discovery (libvsomeip3-sd.so) which is loaded during runtime if the service discovery is enabled.
Build Instructions for Linux
Dependencies
  • A C++11 enabled compiler like gcc >= 4.8 is needed.
  • vsomeip uses CMake as buildsystem.
  • vsomeip uses Boost >= 1.55:

Ubuntu 14.04:

sudo apt-get install libboost-system1.55-dev libboost-thread1.55-dev libboost-log1.55-dev

Ubuntu 12.04: a PPA is necessary to use version 1.54 of Boost: -- URL: https://launchpad.net/~boost-latest/+archive/ubuntu/ppa --sudo add-apt-repository ppa:boost-latest/ppa --sudo apt-get install libboost-system1.55-dev libboost-thread1.55-dev libboost-log1.55-dev

For the tests Google's test framework https://code.google.com/p/googletest/[gtest] in version 1.7.0 is needed. -- URL: https://googletest.googlecode.com/files/gtest-1.7.0.zip

To build the documentation asciidoc, source-highlight, doxygen and graphviz is needed: --sudo apt-get install asciidoc source-highlight doxygen graphviz

Compilation

For compilation call:

mkdir build
cd build
cmake ..
make

To specify a installation directory (like --prefix= if you're used to autotools) call cmake like:

cmake -DCMAKE_INSTALL_PREFIX:PATH=$YOUR_PATH ..
make
make install
Compilation with predefined unicast and/or diagnosis address

To predefine the unicast address, call cmake like:

cmake -DUNICAST_ADDRESS=<YOUR IP ADDRESS> ..

To predefine the diagnosis address, call cmake like:

cmake -DDIAGNOSIS_ADDRESS=<YOUR DIAGNOSIS ADDRESS> ..

The diagnosis address is a single byte value.

Compilation with custom default configuration folder

To change the default configuration folder, call cmake like:

cmake -DDEFAULT_CONFIGURATION_FOLDER=<DEFAULT CONFIGURATION FOLDER> ..

The default configuration folder is /etc/vsomeip.

Compilation with custom default configuration file

To change the default configuration file, call cmake like:

cmake -DDEFAULT_CONFIGURATION_FILE=<DEFAULT CONFIGURATION FILE> ..

The default configuration file is /etc/vsomeip.json.

Compilation with signal handling

To compile vsomeip with signal handling (SIGINT/SIGTERM) enabled, call cmake like:

cmake -DENABLE_SIGNAL_HANDLING=1 ..

In the default setting, the application has to take care of shutting down vsomeip in case these signals are received.

Build Instructions for Android
Dependencies
  • vsomeip uses Boost >= 1.55. The boost libraries (system, thread and log) must be included in the Android source tree and integrated into the build process with an appropriate Android.bp file.
Compilation

In general for building the Android source tree the instructions found on the pages from the Android Open Source Project (AOSP) apply (https://source.android.com/setup/build/requirements).

To integrate the vsomeip library into the build process, the source code together with the Android.bp file has to be inserted into the Android source tree (by simply copying or by fetching with a custom platform manifest). When building the Android source tree, the Android.bp file is automatically found and considered by the build system.

In order that the vsomeip library is also included in the Android image, the library has to be added to the PRODUCT_PACKAGES variable in one of a device/target specific makefile:

PRODUCT_PACKAGES += \
    libvsomeip \
    libvsomeip_cfg \
    libvsomeip_sd
Note that the project description data, including the texts, logos, images, and/or trademarks, for each open source project belongs to its rightful owner. If you wish to add or remove any projects, please contact us at [email protected].