Initial commit

Signed-off-by: Dawid Nowak <[email protected]>

Author: dawid-nowak

AUTHORS.md

@@ -0,0 +1,17 @@
+### Current 
+|Name| Affiliation|  Contact |
+|--------|------|---|
+|Alan Keane| Huawei Ireland Research Lab|[email protected]|
+|Dawid Nowak| Huawei Ireland Research Lab|[email protected]|
+|Francesco Ciaccia|  Huawei Ireland Research Lab|[email protected]|
+|Nicola Bonelli |  Huawei Ireland Research Lab|[email protected]|
+|Wang Ruize | Huawei| [email protected]|
+
+
+### Past
+|Name| Affiliation|
+|--------|------|
+|Liu Xiang | Huawei| 
+|Rui Ferreira |  Huawei Ireland Research Lab|
+|Oriol Arcas | Huawei Ireland Research Lab| 
+|Hayley Deckers | Huawei Ireland Research Lab| 

README.md

@@ -6,18 +6,18 @@
 
 ## Introduction
 
-Orion Proxy is a high performance and memeory safe implementation of popular [Envoy Proxy](https://www.envoyproxy.io/). Orion Proxy is implemented in Rust using high-quality open source components. 
+Orion Proxy is a high performance and memory safe implementation of popular [Envoy Proxy](https://www.envoyproxy.io/). Orion Proxy is implemented in Rust using high-quality open source components. 
 
 ### Key features
 
 **Memory Safety**
 
-Rust programming language allows to avoid a whole lot of bugs related to memory memory management and data racess making Orion Proxy a very robust and secure application.  
+Rust programming language allows to avoid a whole lot of bugs related to memory management and data races making Orion Proxy a very robust and secure application.  
 
 
 **Performance**
 
-Orion Proxy offers 2x-4x better throughput and latency than Envoy Proxy. Refer to [Performance](docs/performance/performance.md) to see performance figures and how tested Orion Proxy for more details.  
+Orion Proxy offers 2x-4x better throughput and latency than Envoy Proxy. Refer to [Performance](docs/performance/performance.md) to see performance figures and for more details how we tested Orion Proxy .  
 
 
 **Compatibility**
@@ -30,17 +30,17 @@ Orion Proxy configuration is generated from Envoy's xDS protobuf definitions. Or
 
 ### Building
 ```console
-git clone https://github.com/kmesh-net/orion-proxy
-cd orion-proxy
+git clone https://github.com/kmesh-net/orion
+cd orion
 git submodule init
-git update --force
+git submodule update --force
 cargo build
 ```
 
 
 ### Running
 ```console
-cargo run --bin orion -- --config orion-proxy/conf/orion-runtime.yaml
+cargo run --bin orion -- --config orion/conf/orion-runtime.yaml
 ```
 
 <!-- ## Contributing -->

RELEASE-NOTES.md

@@ -4,3 +4,4 @@
 
 >[!CAUTION]
 This project is still very unstable and not ready for use in production environments.
+

docker/Dockerfile

@@ -23,10 +23,6 @@ COPY rustfmt.toml ./
 COPY Cargo.toml ./
 COPY Cargo.lock ./
 
-RUN <<EOF
-apt update
-apt install -y protobuf-compiler
-EOF
 
 RUN cargo build --release
 
@@ -37,13 +33,11 @@ FROM debian:bookworm-slim
 RUN <<EOF
 apt update
 apt upgrade -y
-apt install -y ca-certificates libssl-dev libssl3
+apt install -y ca-certificates libssl3
 EOF
 
 COPY ./docker/start_proxy.sh ./start_proxy.sh
 
 COPY --from=orion-builder /tmp/orion/target/release/orion /orion
-# ENV RUST_BACKTRACE=full
-# ENV RUST_LOG=info,rusoto_core=info,swir=debug,rusoto_dynamodb=info
 EXPOSE 8080 8000 50051
-ENTRYPOINT ["/start_proxy.sh"]
+ENTRYPOINT ["/start_proxy.sh"]

docs/demos.md

@@ -19,13 +19,16 @@ docker run --rm -p 4004:80 ealen/echo-server
 
 3. Make some calls with Curl
 
-    Return pre-canned response
+
+Return pre-canned response
 
 ```shell
 curl -i http://127.0.0.1:8000/direct-response
 ```
 
-        Route to an endpoint configured in cluster 1. If there are no endpoints available it will return 502
+
+Route to an endpoint configured in cluster 1. If there are no endpoints available it will return 502
+
 
 ```shell
 curl -i http://127.0.0.1:8000/blah

docs/kmesh-subproject.md

@@ -1,18 +1,18 @@
 ## Background
-KMesh is using the Waypoint proxy to handle Level 7 traffic. The Waypoint Proxy is a fork of Istio Proxy, which is a fork of Envoy. While Envoy is a mature application widely used in Kubernetes deployments, we now have a unique opportunity to replace an Istio proxy with something faster, safer and more modern.
+KMesh is using the Waypoint proxy to handle Level 7 traffic. The Waypoint Proxy is a fork of Istio Proxy, which is a fork of Envoy. While Envoy is a mature application widely used in Kubernetes deployments, we now have a unique opportunity to replace the Istio proxy with something faster, safer and more modern.
 
 ## Orion Proxy
-Orion Proxy is a proxy application developed at Huawei Ireland Research Lab. We built the Orion Proxy using the Rust programming language to achieve good performance, scalability, memory safety and portability. We wanted to ensure that the Orion proxy fits into the existing Kubernetes ecosystem. We made a pragmatic decision that the Orion Proxy should support the Envoy xDS protocol. This would enable the administrators or operators to dynamically configure the Orion Proxy in the same way as Envoy/Istio proxies are.
+Orion Proxy is a proxy application developed at Huawei Ireland Research Lab. We built Orion Proxy using the Rust programming language to achieve good performance, scalability, memory safety and portability. We wanted to ensure that the Orion proxy fits into the existing Kubernetes ecosystem. We made a pragmatic decision that the Orion Proxy should support the Envoy xDS protocol. This would enable the administrators or operators to dynamically configure the Orion Proxy in the same way as Envoy/Istio proxies are.
 
 ## Architecture
-The architecture of the Orion Proxy is based on high-quality components and libraries provided by the Rust ecosystem. The Orion Proxy implementation is underpinned by the Tokio runtime.  Tokio enables asynchronous processing of requests resulting in achieving very high throughput and good scalability. Tokio also provides us with well-defined building blocks to build a solution with a well-defined, manageable and extendable architecture. 
+The architecture of the Orion Proxy is based on high-quality components and libraries provided by the Rust ecosystem. The Orion Proxy implementation is underpinned by the Tokio runtime. Tokio enables asynchronous processing of requests resulting in achieving very high throughput and good scalability. Tokio also provides us with well-defined building blocks to build a solution with a well-defined, manageable and extendable architecture. 
 We decided to use the Hyper library to handle Http1/Http2 traffic. The Hyper library combined with Rustls allowed us to handle modern TLS traffic through a secure and FIPS-compliant solution.
 
 ## Performance
 Before release, we rigorously tested Orion's performance in comparison to Envoy Proxy. The [results](./performance/performance.md) show that the Orion Proxy outperforms the Envoy Proxy in terms of throughput and request latency.
 
 ## Features and Future Roadmap
-Most of our efforts up to date, have been focused on ensuring that the Orion Proxy can reliably proxy Level 4 and Level 7 traffic. In future, we plan to shift our objectives and implement more features that will make Orion Proxy more robust, reliable and straightforward to operate in production environments. In the short term, we want to provide features such as access logging, metrics with open telemetry, and support for HAProxy and Websockets protocols.
+Most of our efforts to date, have been focused on ensuring that the Orion Proxy can reliably proxy Level 4 and Level 7 traffic. In future, we plan to shift our objectives and implement more features that will make Orion Proxy more robust, reliable and straightforward to operate in production environments. In the short term, we want to provide features such as access logging, metrics with open telemetry, and support for HAProxy and Websockets protocols.
 
 ## Current and Past Contributors
 

docs/performance/performance.md

@@ -38,7 +38,7 @@
   - In-memory direct response of 12B size
   - 17 cores assigned to the application on NUMA1
   - 7 cores assigned to IRQ handling on NUMA1
-  - 2.6M RPS à hard-limit of the server
+  - 2.6M RPS a hard-limit of the server
   - Measures #connections established upstream
 
 * DUT (Proxy):

orion-configuration/src/config.rs

@@ -57,12 +57,12 @@ impl Config {
         let runtime = self.runtime.update_from_env_and_options(opt);
         let max_cpus = num_cpus::get();
         if runtime.num_cpus() > max_cpus {
-            tracing::warn!(max_cpus, NG_GATEWAY_CORES = runtime.num_cpus(), "Requested more cores than available CPUs");
+            tracing::warn!(max_cpus, ORION_GATEWAY_CORES = runtime.num_cpus(), "Requested more cores than available CPUs");
         }
         if runtime.num_runtimes() > runtime.num_cpus() {
             tracing::warn!(
                 runtime.num_cpus,
-                NG_GATEWAY_RUNTIMES = runtime.num_runtimes(),
+                ORION_GATEWAY_RUNTIMES = runtime.num_runtimes(),
                 "Requested more runtimes than cores"
             );
         }