Skip to content
This repository has been archived by the owner on Aug 23, 2023. It is now read-only.
/ faas-nomad Public archive

OpenFaas provider for HashiCorp Nomad scheduler

License

Notifications You must be signed in to change notification settings

jsiebens/faas-nomad

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

60 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

faas-nomad - OpenFaas provider for Nomad

Build Status Go Report Card License: MIT OpenFaaS

This repository contains an OpenFaaS provider for the HashiCorp Nomad scheduler. OpenFaaS allows you to run your private functions as a service. Functions are packaged in Docker Containers which enables you to work in any language and also interact with any software which can also be installed in the container.

Inspired by hashicorp/faas-nomad.

Using Vagrant for Local Development

Vagrant is a tool for provisioning dev environments. The Vagrantfile governs the Vagrant configuration:

  1. Install Vagrant via download links or package manager
  2. Install VirtualBox via download links
  3. vagrant up

The provisioners install Docker, Nomad, Consul, and Vault then launch OpenFaaS components with Nomad. If successful, the following services will be available over the private network (192.168.50.2):

This setup is intended to streamline local development of the faas-nomad provider with a more complete setup of the hashicorp ecosystem. Therefore, it is assumed that the faas-nomad source code is located on your workstation, and or is configured to listen on 0.0.0.0:8080 when debugging/running the Go process.

Starting a remote Nomad / OpenFaaS environment

If you would like to test OpenFaaS running on a remote cluster, more demos and instructions are (or will be) available here: jsiebens/faas-nomad-demos · GitHub

Regardless of which method you use interacting with OpenFaaS is the same.

Resources