ucalgary / ftrigger Goto Github PK
View Code? Open in Web Editor NEWTriggers for FaaS functions
ftrigger's People
Contributors
Stargazers
Watchers
ftrigger's Issues
PWD error
Hi - I just tried deploying on PWD with the link and got this error:
cfc728c1c558: Extracting [> ]32.77kB/1.968MB
b81f7352876d: Downloading [=> ]cfc728c1c558: Extracting [==> ] 98.3kB/1.968MBownloading [> ]cfc728c1c558: Extracting [=============================================> ]cfc728c1c558: Extracting [==================================================>]1.968MB/1.968MBB
cfc728c1c558: Pull completeb81f7352876d: Extracting [==> ]32.77kB/578.9kB
ea5ace85d025: Downloading [==================================================>]b81f7352876d: Extracting [=====> ]b81f7352876d: Extracting [==================================================>]b81f7352876d: Extracting [==================================================>]b81f7352876d: Pull completed0d81544a28c: Extracting [> ]d0d81544a28c: Extracting [======> ]d0d81544a28c: Pull completeb2bd99a4a849: Pull completeea5ace85d025: Pull complete886e06b8f331: Pull completeDigest: sha256:ca34659dc7a62a23579cc23ffac6b8172ac54db91ee9abbab7a3caeb65a7195b
Status: Downloaded newer image for landoop/kafka-topics-ui:0.9.2
Pulling kafka (confluentinc/cp-kafka:latest)...
latest: Pulling from confluentinc/cp-kafka
ad74af05f5a2: Already exists
d02e292e7b5e: Already exists
8de7f5c81ab0: Already exists
ed0b76dc2730: Already exists
cfc44fa8a002: Already exists
f441b84ed9ba: Pull complete
d42bb38e2f0e: Pull complete
Digest: sha256:61373cf6eca980887164d6fede2552015db31a809c99d6c3d5dfc70867b6cd2d
Status: Downloaded newer image for confluentinc/cp-kafka:latest
Pulling ftrigger-kafka (ucalgary/ftrigger:master)...
master: Pulling from ucalgary/ftrigger
88286f41530e: Pull complete
4f7af0ecd3c1: Pull complete
04a458759c3d: Pull complete
01e2e5178a53: Pull complete
38b473eaaea6: Pull complete
33830bf65152: Pull complete
7df0e1a71216: Pull complete
80039f42450e: Pull complete
2165701f191d: Pull complete
7f834274e059: Pull complete
Digest: sha256:1c5100f5c7167d47a8d03e87d31d61b3be4cf3e9d51aeb1b3dc3a867c241216e
Status: Downloaded newer image for ucalgary/ftrigger:master
Pulling prometheus (functions/prometheus:latest)...
latest: Pulling from functions/prometheus
557a0c95bfcd: Pull complete
a3ed95caeb02: Pull complete
caf4d0cf9832: Pull complete
ee054001e2db: Pull complete
b95bf6c4c81b: Pull complete
86503a6ba368: Pull complete
ff27c7b0b50e: Pull complete
534e30a17a42: Pull complete
475d41733562: Pull complete
ba67dcb65b31: Pull complete
f81457bec669: Pull complete
Digest: sha256:5127ddc5f58c4c03ac582c74dd66bdb7d5f547dd5913639566597b7fe26f9cf2
Status: Downloaded newer image for functions/prometheus:latest
Pulling schema-registry (confluentinc/cp-schema-registry:latest)...
latest: Pulling from confluentinc/cp-schema-registry
ad74af05f5a2: Already exists
d02e292e7b5e: Already exists
8de7f5c81ab0: Already exists
ed0b76dc2730: Already exists
cfc44fa8a002: Already exists
3056d28f058a: Pull complete
db153840316d: Pull complete
Digest: sha256:aeabd34351f5fa024405d2768edb1b807a311c6ed4df4bd818e78c1ec2f3643b
Status: Downloaded newer image for confluentinc/cp-schema-registry:latest
Pulling gateway (functions/gateway:0.6.6-beta)...
0.6.6-beta: Pulling from functions/gateway
88286f41530e: Already exists
a2c9857c2a1a: Pull complete
9471a4354132: Pull complete
Digest: sha256:9f959e883c4d4d6b07cae30590c82b36f3952068a4cb0be7534c4c96482d6dba
Status: Downloaded newer image for functions/gateway:0.6.6-beta
Creating network ftrigger_functions
Creating network ftrigger_streaming
Creating service ftrigger_gateway
Creating service ftrigger_kafka
failed to create service ftrigger_kafka: Error response from daemon: rpc error:code = InvalidArgument desc = ContainerSpec: "confluentinc/cp-kafka:" is not a valid repository/tag
Please could you look into this?
Functions updates are disabled
#23 disables function updates due to the removal of access to the Docker service information underlying functions. The logic needs to be reworked.
Handle transient network errors when calling functions
Sometimes, transient network errors can occur while calling a function. This needs to be handled somehow, at least by catching errors and logging them. Better yet, there should be an option to retry a certain number of times.
Add a command handler for trigger commands
Introduce a common command handler for all trigger commands. To be detailed.
Add LOGGER_LEVEL and insert log.debug() statements around messages and responses.
Add license information
Add licensing information for this repo.
Ftrigger should read functions from FaaS API Gateway, not scan for arbitrary services
The refresh_services() loop currently contacts Docker to get a list of all services, and then calls the FaaS API Gateway to invoke functions when conditions are met. This doesn't take into consideration whether the service is actually a function, or even registered on the gateway.
The loop should instead query the gateway for activate functions, and go from there.
Support multiple instances of the same type of invoker on a single service
PR #3 added the ability to specify multiple types of invokers on a single service. However, it is not possible to specify multiple instances of the same type of invoker with the updated syntax. It might be useful to allow this.
Improve logging in Kafka based trigger
The Kafka based trigger provides very little output. It is impossible to know when it fails to call a function or even what its basic state is at the default log level. There is also no way to turn on debug logging.
Unified base command for triggers
It'd be useful to have a unified base command for all trigger types for uniformity of options and use.
Flatten TriggerBase in trigger.py
Not sure if it really makes sense to have a base class for triggers. It might be better to flatten it into a library of functions, instead.
Restructure TriggerBase into a standalone helper class
Restructure TriggerBase into a standalone helper class to be instantiated and called by trigger implementation, not subclassed. This replaces #20.
Add support for sending message value for Kafka triggers
The Kafka based trigger current sends the received message key as a plain text value in the request body for functions. Add an option to send both the key and value, perhaps as a JSON object or array.
Kafka consumer loop should explicitly handle offset commit
The Kafka consumer loop currently depends on an auto-commit interval of 5000 ms to record the consumer offset. The run loop should perhaps switch to explicit commits after it successfully calls a service for a more accurate record of where the consumer has consumed to in its topic.
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.