#IstioCon Is Your Virtual Machine Really Ready-to-go with Istio? Kailun Qin, Intel Haoyuan Ge #IstioCon Quick Summary (from Google Cloud Next ’19 [1]) VM works on Istio! [1] Istio Service Mesh performance is desired) #IstioCon Demo #IstioCon Istio VM integration seems closer to be production ready? Should we expect more? And what do we need else? #IstioCon Why We Expect More? A Closer Look… kernel bypass w/ HW acceleration #IstioCon Quick Summary, Today Istio is ready-to-go for VM native. And should/will be ready for MORE! #IstioCon Thank you! Github: @kailun-qin @harryge00

Node.js* Client & Web Bridge Ready for ROS* 2.0 Minggang Wang September 30 2018 Agenda ● Who We Are ● Why Use Node.js & Web in Robotics ● Thinking in “ROS 2.0 + Web” ● What We Have Done for “ROS

function, it is valid) • awaitable - type supports co_await operator. • awaiter - type with await_ready, await_suspend and await_resume defined. • A set of rules applied at compile time and translate the get_return_object Customization point - How a compiler may work Finally, after these steps, we are ready to run some actual logics. 1516 16 void __sum_resume(void* ptr); struct __sum_frame { __sum_frame(int frame->initial_suspend_awaitable = frame->promise.initial_suspend(); if (!frame->initial_suspend_awaitable.await_ready()) { frame->resumeIndex = 1; frame->initial_suspend_awaitable.await_suspend(handle_t::from_prom

get machinesets -n openshift-machine-api NAME DESIRED CURRENT READY AVAILABLE AGE agl030519-vplxk-worker-us-east-1a 1 1 1 1 55m get machineset -n openshift-machine-api NAME DESIRED CURRENT READY AVAILABLE AGE agl030519-vplxk-infra-us-east-1a 1 1 1 1 11m get machinesets -n openshift-machine-api NAME DESIRED CURRENT READY AVAILABLE AGE agl030519-vplxk-worker-us-east-1a 1 1 1 1 55m

scheduled/executed in the node when Cilium is ready. # Alternatively, see the note below. gcloud container clusters create "${NAME}" \ --node-taints node.cilium.io/agent-not-ready=true:NoExecute \ --zone us-west2-a Cilium is deployed. # Alternatively, see the note below. taints: - key: "node.cilium.io/agent-not-ready" value: "true" effect: "NoExecute" EOF eksctl create cluster -f ./eks-config.yaml Note Datastore Requirements: The cluster should be created with the taint node.cilium.io/agent-not- ready=true:NoExecute using --node-taints option. However, there are other options. Please make sure to read

scheduled/executed in the node when Cilium is ready. # Alternatively, see the note below. gcloud container clusters create "${NAME}" \ --node-taints node.cilium.io/agent-not-ready=true:NoExecute \ --zone us-west2-a Cilium is deployed. # Alternatively, see the note below. taints: - key: "node.cilium.io/agent-not-ready" value: "true" effect: "NoExecute" EOF eksctl create cluster -f ./eks-config.yaml Note Kubernetes CRD Requirements: The cluster should be created with the taint node.cilium.io/agent-not- ready=true:NoExecute using --node-taints option. However, there are other options. Please make sure to read

being installed: kubectl -n kube-system get pods --watch NAME READY STATUS RESTARTS AGE cilium-operator-cb4578bc5-q52qk 0/1 Pending readiness while it can successfully reach the echo server: kubectl get pods NAME READY STATUS RESTARTS AGE echo-585798dd9d-ck5xc 1/1 Running 0 75s echo-585798dd9d-jkdjx being installed: kubectl -n kube-system get pods --watch NAME READY STATUS RESTARTS AGE cilium-operator-cb4578bc5-q52qk 0/1 Pending

being installed: kubectl -n kube-system get pods --watch NAME READY STATUS RESTARTS AGE cilium-operator-cb4578bc5-q52qk 0/1 Pending indicates success or failure of the test: NAME READY STATUS RESTARTS AGE echo-a-5995597649-f5d5g 1/1 Running being installed: kubectl -n kube-system get pods --watch NAME READY STATUS RESTARTS AGE cilium-operator-cb4578bc5-q52qk 0/1 Pending

enabled. These features may include unreleased or beta features that are not considered production-ready. While it provides a convenient way to try out experimental features, It should only be used in testing being installed: kubectl -n kube-system get pods --watch NAME READY STATUS RESTARTS AGE cilium-operator-cb4578bc5-q52qk 0/1 Pending test: $ kubectl get pods -n cilium-test NAME READY STATUS RESTARTS AGE echo-a-6788c799fd-42qxx 1/1 Running

enabled. These features may include unreleased or beta features that are not considered production-ready. While it provides a convenient way to try out experimental features, It should only be used in testing being installed: kubectl -n kube-system get pods --watch NAME READY STATUS RESTARTS AGE cilium-operator-cb4578bc5-q52qk 0/1 Pending test: $ kubectl get pods -n cilium-test NAME READY STATUS RESTARTS AGE echo-a-76c5d9bd76-q8d99 1/1 Running