Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/n0stack/n0stack
A simple cloud provider using gRPC
https://github.com/n0stack/n0stack
cloud-providers go golang grpc virtualization
Last synced: 3 months ago
JSON representation
A simple cloud provider using gRPC
- Host: GitHub
- URL: https://github.com/n0stack/n0stack
- Owner: n0stack
- License: bsd-2-clause
- Created: 2017-09-12T09:00:07.000Z (over 7 years ago)
- Default Branch: master
- Last Pushed: 2023-03-07T02:10:34.000Z (almost 2 years ago)
- Last Synced: 2024-06-18T21:51:24.082Z (8 months ago)
- Topics: cloud-providers, go, golang, grpc, virtualization
- Language: Go
- Homepage: https://n0st.ac/k/
- Size: 5.87 MB
- Stars: 52
- Watchers: 10
- Forks: 9
- Open Issues: 59
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
README
# n0stack
[](https://travis-ci.org/n0stack/n0stack)
[](https://circleci.com/gh/n0stack/n0stack/tree/master)
[](https://goreportcard.com/report/github.com/n0stack/n0stack)
[](https://hub.docker.com/r/n0stack/n0stack)
The n0stack is a simple cloud provider using gRPC.
## Description
The n0stack is...
- a cloud provider.
- You can use some features: booting VMs, managing networks and so on (see also [n0proto](n0proto/).)
- simple.
- There are shortcode and fewer options.
- using gRPC.
- A unified interface increase reusability.
- able to be used as library and framework.
- You can concentrate to develop your logic by sharing libraries and frameworks for middleware, test, and deployment.
## Motivation
Cloud providers have various forms depending on users.
This problem has been solved with many options and add-ons (e.g. OpenStack configuration file is very long.)
It is difficult to adapt to the application with options, therefore it is necessary to read or rewrite long abstracted code.
I think it is better to code it yourself from the beginning.
There are some problems to develop cloud providers from scratch: no libraries, software quality, man-hours, and deployment.
The n0stack wants to solve these problems.
## Getting started
### Prerequisites
- Docker
- docker-compose
- Ubuntu 18.04 LTS
### Deploy all in one
1. You can start controllers on docker and install agent as follows:
```sh
wget https://raw.githubusercontent.com/n0stack/n0stack/master/deploy/docker-compose.yml
docker-compose up -d
docker run -it --rm -v $PWD:/dst n0stack/n0stack cp /usr/local/bin/n0core /dst
./n0core install agent -a "--node-api-endpoint=localhost:20180 --location=////1"
```
2. Download n0cli from [Github releases](https://github.com/n0stack/n0stack/releases/latest).
3. Try [use cases](https://docs.n0st.ac/en/master/user/usecases/README.html).
## Documentations
[](https://gitter.im/n0stack/)
[](https://docs.n0st.ac/en/master/?badge=master)
[](https://godoc.org/github.com/n0stack/n0stack)
User documentations and specifications is [readthedocs](https://docs.n0st.ac/en/master/?badge=master).
Golang library documentations is [GoDoc](https://godoc.org/github.com/n0stack/n0stack).
## Components
The final goal of n0stack is to represent the state of all clusters with n0proto.
Implementations such as n0core manipulates the cluster according to the information specified by n0proto.
The implementation of n0proto is left to each developer.
This repository is just a reference implementation.
However, please share actively usable libraries such as `n0core/pkg/driver`.
### [n0proto](n0proto/)
Protobuf definitions for all of n0stack services.
### [n0cli](n0cli/)
CLI for n0stack API.
### n0ui
Web UI for n0stack API.
### [n0bff](n0bff/)
BFF(Backends for Frontend) of n0stack API. This provide features: API gateway, authentication, authorization and so on.
### [n0core](n0core/)
The example for implementations about n0stack API.
## Contributing
1. Fork it
2. Create your feature branch (`git checkout -b my-new-feature`)
3. Commit your changes (`git commit -am 'Add some feature'`)
4. Push to the branch (`git push origin my-new-feature`)
5. Create new Pull Request
### How to develop
- see also [Makefile](Makefile)
1. Start containers
```sh
make build-builder # once
make up
```
2. Start a Agent
- Recommended way is...
1. Boot VM
2. [Deploy agent](n0core/README.md) to booted VM
3. Develop features and restart containers or a agent
## License
[](https://opensource.org/licenses/BSD-2-Clause)
[](https://app.fossa.io/projects/git%2Bgithub.com%2Fn0stack%2Fn0stack?ref=badge_large)