laoshanxi / app-mesh Goto Github PK

A secure Multi-Tenant, Cloud Native, Micro Service application management platform

License: MIT License

C++ 75.96% Shell 4.24% Dockerfile 0.23% CMake 2.21% Python 8.82% Go 8.43% Makefile 0.08% HTML 0.03%

jwt docker cloud-native consul-client prometheus-exporter loki alertmanager scheduler cron ldap

app-mesh's Introduction

App Mesh

App Mesh is a Multi-Tenant, Cloud Native, Micro Service application management platform designed to manage, schedule, and monitor applications. Each app can be a specific microservice for service discovery or a standard app with replication. App Mesh ensures all defined applications run on time with the specified behavior and resource requests. The platform supports both standalone and cluster modes and provides REST APIs, a command-line interface, and a web UI.

App Mesh is similar to Kubernetes but is much more lightweight, supporting both containerized and native applications.

Features

Feature	Description
Application management	1. Manage independent applications with flexible process control (long/short running, periodic, cron schedule, custom timings, error handling) and comprehensive monitoring (start counts, return codes, error messages, health checks) for both native and Docker applications. 2. Run applications on remote hosts using SDK/CLI with sync/async modes and fetch results to the client. 3. Full control over application lifecycle (cgroup resource limitation, specific OS user for execution). 4. Support interactive application start with specific input data via pipe and environment variables. 5. Access all functionalities via CLI, REST, SDK and WebGUI interface.
Security	⚡️ JWT authentication for CLI and REST interface ⚡️ LDAP support ⚡️ Role based permission control ⚡️ Multi-factor authentication SSL support (ECDH and secure ciphers) for REST http connection Multi-tenant support
Cloud native	Schedule cloud-level applications to run on multiple hosts with resource size requests. ⚡️ Prometheus Exporter (build-in) ⚡️ Grafana SimpleJson datasource ⚡️ Grafana Loki ⚡️ Dockerfile
Micro service application	⚡️ Consul micro-service cluster management
Extra Features	Collect host/app resource usage Remote shell command execution File upload/download interface Hot-update support `systemctl reload appmesh` Bash completion Reverse proxy Web GUI
Platform support	X86_64 ARM32 ARM64
SDK	Python Golang Swagger OpenAPI Specification `https://localhost:6060/swagger`

Getting started

Refer to the Installation doc to learn how to install App Mesh via Docker Compose or natively and set up an App Mesh cluster.

Documentation

Comparison

Standalone mode

Feature	App Mesh	Supervisor	crontab
Accuracy	Seconds	Seconds	Minutes
Language	C++11	Python	C
Web GUI	√	√
Command lines	√	√	√
SDK	√
Cron schedule expression	√		√
Manage daemon process			√
Manage docker app	√
Start check (avoid leak)	√	√
Session login
Manage stdout/stderr	√	√
Health check	√
Rich control options	√
Authentication	√	√
Multi-tenant	√		√

Cluster mode

Feature	App Mesh	Kubernetes
Easy deploy	√
More features		√
Non-container app	√
Service expose	√	√
Scheduler	√	√
Definition file	JSON	YAML
GUI	√	√
Virtual Network		√
Monitor tools	√	√

Component diagram

Success

Library dependency

app-mesh's People

Contributors

Stargazers

Watchers

Forkers

xuhm3 hanjiangping lip0091981 yutiansut dicky98 geyaandy simhaonline ibmxianliqi rk801 frederickhou markkun doytsujin gitter-badger hanixnicolas shuhecn zjf984078330 step-security-bot davecarlson

app-mesh's Issues

app should have initialize command and un-initialize command

remote shell output should distinguish stdout and stderr

Current remote shell run will print both stderr and stdout to stdout.

support dynamic change log level

appc log --level DEBUG

LDAP auth support

LDAP Server:
https://github.com/osixia/docker-openldap

docker run -p 389:389 -p 636:636 --name my-openldap-container --detach osixia/openldap:1.5.0

LDAP UI:
https://github.com/osixia/docker-phpLDAPadmin

docker run -p 6443:443 \
        --env PHPLDAPADMIN_LDAP_HOSTS=ldap.example.com \
        --detach osixia/phpldapadmin:0.9.0

Provide exporter for prometheus

https://github.com/prometheus/mysqld_exporter/

http authentication support

Add authentication to http request

read_to_end() in server side may occupy thread for long time

rpm re-install should keep appsvc.json

appc sh specify user

need passless to self

$ appc sh -u admin -c 'su - -c "oc project"'

no need passless
root switch to admin user with login environment:

$ appc sh -b "10.127.21.1" -c 'su - admin -c "oc get nodes"'

cmake support

Use cmake to build project

IPv6 support

Support listen IPv6 port

appc run can not support env like "ifconfig | grep 127"

"ifconfig | grep 127" will be parse to bellow cause error:
fconfig '|' grep 127

SSL should not use RC4 cipher

http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2013-2566

Reg short running one time app

short running app add next start time attribute

Cluster management

Target:

Application failover
Master election
Package management (docker could easy for package management)

use websocket to download/upload files

docker container support start instead of run

Support redirect to other jwt server for authenticate

SSL certificate file issue and gernerate when installation

Support register the already running app

Sometimes we need to monitor or add schedule for the already running apps, maybe support this function will more helpful.

Use asyncrized run API in service side

CLI return 0 on success and other code on failure

docker app allow empty command line input

Support HA

Solutions:

persist configuration file in 3rd storage
configuration file name use a unique file name

run as sidecar for docker container

build & install enhancement

watchdog.sh support register a args as application
If install in docker container, should support not instsall system service

common .a lib build dependency

make exposed REST configurable

add lable feature

Integrate with Consul

# start consul
$ docker run -d --name=consul --net=host consul

# register service to consul
$ curl -X PUT -d '
{
   "address": "192.168.3.27",
   "checks": [
       {
           "http": "https://192.168.3.27:6060",
           "interval": "5s",
           "method": "GET",
           "tls_skip_verify": true
       }
   ],
   "id": "appmgr192.168.3.27",
   "name": "appmgr192.168.3.27",
   "port": 6060,
   "tags": [
       "appmgr"
   ]
}
'   http://192.168.3.27:8500/v1/agent/service/register

Allow empty configuration

Allow all configuration to be null, use default value

remove shell hide debug output

provide debug info package

Apine Linux image support

Most of the dependency can support Alpine Linux (mainly used for tiny Docker container), but ACE have not support Alpine yet.

Alpine is not glibc but musl libc, see according issue:

DOCGroup/ACE_TAO#914

jwt add expire time

Here is a simple example of creating a token that will expire in one hour:

auto token = jwt::create()
.set_issuer("auth0")
.set_issued_at(std::chrono::system_clock::now())
.set_expires_at(std::chrono::system_clock::now() + std::chrono::seconds{3600})
.sign(jwt::algorithm::hs256{"secret"});

Customerized REST API

Define a REST according to a application

Support centos7 service locate at /usr/lib/systemd/

Application can define stdout implement from appsvc or not

add health check script for application

appc reg -n ttt -c "sleep 600" -l "sh -c 'if [[ $$(curl -k --fail https://127.0.0.1:6060/app/ttt/health) != ""0"" ]]; then exit 1; else exit 0;'"

Integrate with Prometheus

prepare Prometheus config file

$ echo -n 'global: 
  scrape_interval: 15s
  evaluation_interval: 15s

scrape_configs:
  - job_name: 'prometheus'
    static_configs:
      - targets: ['127.0.0.1:9090']
  - job_name: 'centos7-appmgr'
    scrape_interval: 10s
    static_configs:
      - targets: ['10.1.241.54:6061']
' | tee /opt/prometheus.yml

start Promeeheus container (use host mode networking for container connect host port)

docker run --restart=always -d --net=host --user root --privileged --name prom -v /opt/prometheus.yml:/etc/prometheus/prometheus.yml prom/prometheus

http://10.1.241.54:9090/config

http://10.1.241.54:9090/targets

Failed to connect to any resolved endpoint?

Usage: appc [COMMAND] [ARG...] [flags]
root@quantaxis-PowerEdge-R610:/home/quantaxis# appc view
Failed to connect to any resolved endpoint
root@quantaxis-PowerEdge-R610:/home/quantaxis# appc reg -n ping -c 'ping www.baidu.com' -o 10
Failed to connect to any resolved endpoint
root@quantaxis-PowerEdge-R610:/home/quantaxis#