edge-computing

What would you like to be added/modified:
when we run keadm beta join command to start an edge node, we run systemd related commands in our source codes to start edgeocre systemd service, such as
https://github.com/kubeedge/kubeedge/blob/bef4c51ee551d315e3eb5e75db4878dd023b867f/keadm/cmd/keadm/app/cmd/edge/joinb

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

Previous discussion: #1500

Details

Currently, there is no workflow to build and test rust-related crates on the Windows platform. So there is no guarantee for making sure the compilation and functionality are working.

FEATURE REQUEST

1. Is there an open issue addressing this request? If it does, please add a "+1" reaction to the
   existing issue, otherwise proceed to step 2.
   No.

2. Describe the feature you are requesting, as well as the possible use case(s) for it.
   Add endpoint for listing User keys to the Auth service.

3. Indicate the importance of this feature to you (must-have, should-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

Describe the feature

In current implementation, when issuing a query, the QueryingSubscriber pushes in a merge_queue the samples resulting of this query and the samples coming directly from the publishers. Then, at query end, the merge_queue is sorted and dedup-ed.

I would be more efficient to use an enhanced merge_queue that sort+dedup on the fly, for each pushed sample.