edge-computing

Now the helm is related in build, let's move it to root dir.

kubeedge/build/helm -> kubeedge/helm

Related to metering wasm3/wasm3#127 and being able to run a set number of instructions, I'd like to be able to serialize a paused interpreter's state and deserialize it to a new interpreter instance; very roughly,

const interp = new wasm3.Interpreter(module);
interp.interpretNInstructions(100);
const interpState = interp.serializeState();
const interp2 = wasm3.In

Motivation

Showcase that developers could use SuperEdge to manage WasmEdge.

Details

Create a new workflow for SuperEdge and WasmEdge

1. How to guide: superedge/superedge@76529ca

2. The new GitHub Action workflow should be put on https://github.com/second-state/wasmedge-containers-examples/actions

3. After that, add

ENHANCEMENT

1. Describe the enhancement you are requesting.
   Consider using Go errors group (golang.org/x/sync/errgroup) for handling routines in main functions of Mainflux services.

2. Indicate the importance of this enhancement to you (must-have, should-have, nice-to-have).
   This is a nice-to-have.

https://www.usenix.org/conference/opml19/program

Prepare to read papers

nanovms/ops#525

Is your feature request related to a problem? Please describe.
I would like to set a custom and static interface name for the client to use with firewall rules

Describe the solution you'd like
An additional option here:

Would work great in my opinion.

**Describe alterna

as we know that e2e testing has been more reliable and widely adopted because of the following benefits:

• Expand test coverage
• Ensure the correctness of the application
• Reduce time to market
• Reduce cost
• Detect bugs
  so this issues is for provide a proposal for add e2e test on superedge.

What would you like to be added/modified:
add e2e package under /test/e2e/.
the first com

It would be useful if Kuiper supported file-based rule and stream provisioning (i.e. importing) on startup. Currently rules and streams need to be created by someone using the client, or an application requesting creation via the Kuiper REST API.

Supporting file-based provisioning would allow someone to deploy Kuiper with a pre-defined set of streams and rules, removing the need for someone (or

*feature: support for yaml syntax/descriptor to Policies Create/Update utilities.

Now that zenohd can be configured via a configuration file, we should provide a default one in /etc/zenohd/.
The zenohd service will use it.