vladaionescu / leveros Goto Github PK

Hello,

I am currently using ubuntu 14.04 LTS and follow installation instructions.

After cloning the repository and try make, it fails with the following error:

make HAVE_GO="" HAVE_PROTOC="" clicommon
make[1]: Entering directory `/path/leveros'
if [ -n "" ]; then protoc -I protos/core/ --go_out=plugins=grpc:core/ protos/core/leverrpc.proto ; else echo "Warning! protoc not found." "Should be ok if not modifying protos." ; fi
Warning! protoc not found. Should be ok if not modifying protos.
if [ -n "" ]; then protoc -I protos/fleettracker/ --go_out=plugins=grpc:fleettracker/ protos/fleettracker/fleettracker.proto ; else echo "Warning! protoc not found." "Should be ok if not modifying protos." ; fi
Warning! protoc not found. Should be ok if not modifying protos.
if [ -n "" ]; then protoc -I protos/hostman/ --go_out=plugins=grpc:hostman/ protos/hostman/manager.proto ; else echo "Warning! protoc not found." "Should be ok if not modifying protos." ; fi
Warning! protoc not found. Should be ok if not modifying protos.
if [ -n "" ]; then make GO_OUTPUT=build/bin/lever GO_MAIN_TARGET=./cmd/lever/main.go build/bin/lever ; else test -f build/bin/lever || docker run --rm -v "/path/leveros":/go/src/github.com/leveros/leveros -w /go/src/github.com/leveros/leveros -e GOOS=linux -e GOARCH=amd64 -e CGO_ENABLED=0 golang:1.6.1-alpine go build -ldflags "-X main.Version=0.1.0 -X main.GitHash=fd973d2817b0efcee368c08d8a08dc2c8d833fbd"  -o build/bin/lever ./cmd/lever/main.go ; fi
stat ./cmd/lever/main.go: no such file or directory
make[1]: *** [build/bin/lever] Error 1
make[1]: Leaving directory `/path/leveros'

I changed my real path with /path/leveros which point to the cloned repository.

Docker version:

$ docker version
Client:
 Version:      1.11.1
 API version:  1.23
 Go version:   go1.5.4
 Git commit:   5604cbe
 Built:        Tue Apr 26 23:30:23 2016
 OS/Arch:      linux/amd64

Server:
 Version:      1.11.1
 API version:  1.23
 Go version:   go1.5.4
 Git commit:   5604cbe
 Built:        Wed Apr 27 00:34:20 2016
 OS/Arch:      linux/amd64

Docker machine:

$ docker-machine version
docker-machine version 0.7.0, build a650a40

Docker compose:

$ docker-compose version
docker-compose version 1.7.1, build 0a9ab35
docker-py version: 1.8.1
CPython version: 2.7.9
OpenSSL version: OpenSSL 1.0.1e 11 Feb 2013

Virtual box:

$ apt show virtualbox-5.0
Package: virtualbox-5.0
Version: 5.0.20-106931~Ubuntu~trusty

Protoc:

$ protoc --version
libprotoc 2.6.1

Thank you for your help,
I really can't wait to test leveros :) !

When building Rest APIs, it's sometimes desirable to have a document where you describe/define your service. One alternative is by using RAML: http://raml.org/
So I think it would be great to define the service not only in a json file, but also in a RAML file. For instance:

/songs:
type:
collection:
exampleCollection: !include jukebox-include-songs.sample
exampleItem: !include jukebox-include-song-new.sample
get:
is: [
searchable: {description: "with valid searchable fields: songTitle", example: "["songTitle", "Get L", "like"]"},
orderable: {fieldsList: "songTitle"},
pageable
]
/{songId}:
type:
collection-item:
exampleItem: !include jukebox-include-song-retrieve.sample
/file-content:
description: The file to be reproduced by the client
get:
description: Get the file content
responses:
200:
body:
application/octet-stream:
example:
!include heybulldog.mp3
post:
description: |
Enters the file content for an existing song entity.
The song needs to be created for the /songs/{songId}/file-content to exist.
You can use this second resource to get and post the file to reproduce.
Use the "binary/octet-stream" content type to specify the content from any consumer (excepting web-browsers).
Use the "multipart-form/data" content type to upload a file which content will become the file-content
body:
application/octet-stream:
multipart/form-data:
formParameters:
file:
description: The file to be uploaded
required: true
type: file

I have a issue while i try to make lever os

➜ leveros git:(master) sudo make
make HAVE_GO="" HAVE_PROTOC="" clicommon
make[1]: 디렉터리 '/home/hosoup/git/leveros' 들어감
if [ -n "" ]; then protoc -I protos/hostman/ --go_out=plugins=grpc:hostman/ protos/hostman/manager.proto ; else echo "Warning! protoc not found." "Should be ok if not modifying protos." ; fi
Warning! protoc not found. Should be ok if not modifying protos.
if [ -n "" ]; then protoc -I protos/core/ --go_out=plugins=grpc:core/ protos/core/leverrpc.proto ; else echo "Warning! protoc not found." "Should be ok if not modifying protos." ; fi
Warning! protoc not found. Should be ok if not modifying protos.
if [ -n "" ]; then protoc -I protos/fleettracker/ --go_out=plugins=grpc:fleettracker/ protos/fleettracker/fleettracker.proto ; else echo "Warning! protoc not found." "Should be ok if not modifying protos." ; fi
Warning! protoc not found. Should be ok if not modifying protos.
if [ -n "" ]; then make GO_OUTPUT=build/bin/lever GO_MAIN_TARGET=./cmd/lever/main.go build/bin/lever ; else test -f build/bin/lever || docker run --rm -v "/home/hosoup/git/leveros":/go/src/github.com/leveros/leveros -w /go/src/github.com/leveros/leveros -e GOOS=linux -e GOARCH=amd64 -e CGO_ENABLED=0 golang:1.6.1-alpine go build -ldflags "-X main.Version=0.1.1 -X main.GitHash=52d3cbdc95889435a5d3d85c743e83efc317fd9d" -o build/bin/lever ./cmd/lever/main.go ; fi
docker: Cannot connect to the Docker daemon. Is the docker daemon running on this host?.
See 'docker run --help'.
Makefile:197: 'build/bin/lever' 타겟에 대한 명령이 실패했습니다
make[1]: *** [build/bin/lever] 오류 125
make[1]: 디렉터리 '/home/hosoup/git/leveros' 나감
Makefile:102: 'fastcli' 타겟에 대한 명령이 실패했습니다

My docker-compose version is docker-compose version 1.9

I suspect this is a bug in Docker's libnetwork. We have workarounds due to this. See this for example.

This prevents us from properly supporting dynamic env creation, because the first request for the new env will fail / take a long time.

Note: I have seen this bug repro in some environments (Ubuntu 14.04, native docker) but not others (Mac with docker-machine and VirtualBox).

There should be a way to read request headers and set response headers from service code.

Perhaps setting global scope that you can access inside of a service?

module.exports.sayHello = function (name, http, callback) {
    var accepts = http.req.accepts;
    http.res.header('X-My-Custom-Header', 'bar');
    callback(null, "Hello, " + name + "!");
};

Allow services' logs to be accessible from the lever CLI.

Ideally this should be based on gRPC. But since gRPC is not (yet) supported for browsers, we may need to develop a WebSocket-based gateway to support the streaming RPC properly.

The library should somehow be part of the leveros npm package... maybe. Or at least have the exact same API as that package, to avoid more learning.

The issue seems to be file path format for docker mounts. The use of $PWD in the Makefile and in runasdocker.sh for docker mount point is not supported by Docker for windows for some reason.

Hello guys!

I'm evaluating LeverOS for something we need at the company I work at, and we're concerned to see that there's almost 4 months that the project has no updates on Github.
The core guys are still active? The project will still be updated and maintained?

cc: @vlad-alexandru-ionescu, @bydooweedoo, @chetbox

This gives instructions on how to deploy locally, what about deploying in a clustered production environment with shared resources?

Quickstart step make fastrun fails with the following output:

 => make fastrun
/Applications/Xcode.app/Contents/Developer/usr/bin/make HAVE_GO="" HAVE_PROTOC="" runcommon
/Applications/Xcode.app/Contents/Developer/usr/bin/make \
        clean-containers \
        init-dbdata \
        /Users/evanmouzakitis/Documents/Code/leveros/repo \
        admin-env
docker kill
docker: "kill" requires a minimum of 1 argument.
See 'docker kill --help'.

Usage:  docker kill [OPTIONS] CONTAINER [CONTAINER...]

Kill a running container
make[2]: [clean-containers] Error 1 (ignored)
docker rm -f --volumes
docker: "rm" requires a minimum of 1 argument.
See 'docker rm --help'.

Usage:  docker rm [OPTIONS] CONTAINER [CONTAINER...]

Remove one or more containers
make[2]: [clean-containers] Error 1 (ignored)
docker run --rm -v leveros_dbdata:/leveros/dbdata \
        leveros/aerospikedev \
        bash -c "chown -R aerospike:aerospike /leveros/dbdata"
mkdir -p /Users/evanmouzakitis/Documents/Code/leveros/repo
chmod o+rwx /Users/evanmouzakitis/Documents/Code/leveros/repo
mkdir -p /Users/evanmouzakitis/Documents/Code/leveros/repo/admin.lever/admin/1
chmod o+rwx /Users/evanmouzakitis/Documents/Code/leveros/repo/admin.lever/admin/1
if [ -n "" ]; then /Applications/Xcode.app/Contents/Developer/usr/bin/make GO_OUTPUT=build/bin/adminservice GO_MAIN_TARGET=./cmd/adminservice/main.go build/bin/adminservice ; else test -f build/bin/adminservice || docker run --rm -v "/Users/evanmouzakitis/Documents/Code/leveros":/go/src/github.com/leveros/leveros -w /go/src/github.com/leveros/leveros -e GOOS=linux -e GOARCH=amd64 -e CGO_ENABLED=0 golang:1.6.1-alpine go build -ldflags "-X main.Version=0.1.1 -X main.GitHash=a892919e443fcbc89fd0ead711e6e2ceb494751c"  -o build/bin/adminservice ./cmd/adminservice/main.go ; fi
docker-compose up -d --force-recreate consul aerospike
ERROR: In file './docker-compose.yml' service 'version' doesn't have any configuration options. All top level keys in your docker-compose.yml must map to a dictionary of configuration options.
make[1]: *** [runcommon] Error 1
make: *** [fastrun] Error 2

Currently we have this problem.

It would be nice to be able to specify the allowed method(s) for a given service.

For example:

# lever.json
{
    "name": "helloService",
    "description": "A hello service.",
    "jsEntry": "server.js",
    "methods": "GET"
}

or

# lever.json
{
    "name": "helloService",
    "description": "A hello service.",
    "jsEntry": "server.js",
    "methods": ["GET", "HEAD", "DELETE"]
}

If a client tries to request a service on a method that is not defined, lever should return 405 Method Not Allowed and return a header showing the allowed methods.

Allow: GET, HEAD, DELETE