Abstract: A lift nacelle may comprise an airflow generator; a sidewall system coupled to the airflow generator and spanning in a first direction, wherein the sidewall system defines a nacelle interior space, wherein the airflow generator defines one of a forward boundary or an aft boundary of the nacelle interior space; and a lift body disposed in the nacelle interior space and spanning substantially perpendicular to the first direction and substantially perpendicular to an upward lift direction. The airflow generator may be configured to accelerate airflow in an aft direction into the nacelle interior space through the forward boundary of the nacelle interior space. The airflow may contact and/or interact with the lift body creating lift in response.

Abstract: A lift nacelle may comprise an airflow generator; a sidewall system coupled to the airflow generator and spanning in a first direction, wherein the sidewall system defines a nacelle interior space, wherein the airflow generator defines one of a forward boundary or an aft boundary of the nacelle interior space; and a lift body disposed in the nacelle interior space and spanning substantially perpendicular to the first direction and substantially perpendicular to an upward lift direction. The airflow generator may be configured to accelerate airflow in an aft direction into the nacelle interior space through the forward boundary of the nacelle interior space. The airflow may contact and/or interact with the lift body creating lift in response.

Abstract: A method includes receiving a DNS request, notifying a serverless orchestrator system of data associated with the DNS request, provisioning a function on a serverless function node based on the DNS request, notifying a load balancer regarding the serverless function node, providing a response to the DNS request and routing an API request associated with the DNS request to the serverless function node.

Abstract: Systems, methods, and computer-readable media are provided for reusing execution environments and code of serverless functions while ensuring isolation in serverless computing environments. In some examples, a method can include, in response to a first request to run a serverless function, executing, at an execution environment on a network, computer-readable code configured to perform the serverless function; after the computer-readable code has executed, modifying a pointer to an area of memory used to store a first state of the serverless function to reference a different area of memory; in response to a second request to run the serverless function, reusing, at the execution environment, the computer-readable code to perform the serverless function; and based on the pointer referencing the different area of memory, using the different area of memory to store a second state of the serverless function.

Abstract: A lift nacelle may comprise an airflow generator; a sidewall system coupled to the airflow generator and spanning in a first direction, wherein the sidewall system defines a nacelle interior space, wherein the airflow generator defines one of a forward boundary or an aft boundary of the nacelle interior space; and a lift body disposed in the nacelle interior space and spanning substantially perpendicular to the first direction and substantially perpendicular to an upward lift direction. The airflow generator may be configured to accelerate airflow in an aft direction into the nacelle interior space through the forward boundary of the nacelle interior space. The airflow may contact and/or interact with the lift body creating lift in response.

Abstract: A method includes receiving a DNS request, notifying a serverless orchestrator system of data associated with the DNS request, provisioning a function on a serverless function node based on the DNS request, notifying a load balancer regarding the serverless function node, providing a response to the DNS request and routing an API request associated with the DNS request to the serverless function node.

Abstract: Systems, methods, and computer-readable media are provided for reusing execution environments and code of serverless functions while ensuring isolation in serverless computing environments. In some examples, a method can include, in response to a first request to run a serverless function, executing, at an execution environment on a network, computer-readable code configured to perform the serverless function; after the computer-readable code has executed, modifying a pointer to an area of memory used to store a first state of the serverless function to reference a different area of memory; in response to a second request to run the serverless function, reusing, at the execution environment, the computer-readable code to perform the serverless function; and based on the pointer referencing the different area of memory, using the different area of memory to store a second state of the serverless function.

Abstract: A network management method includes a controller receiving an underlay network identifier and a network segment identifier. The underlay network identifier and network segment identifier can be associated with entries in a forwarding information base and border gateway protocol speakers may be deployed in association with the entries. A virtual network can be associated with the underlay network and network traffic can be forwarded to the virtual network according to the entries.

Abstract: A system is provided that includes one management cluster to manage network function virtualization infrastructure (NFVI) resources lifecycle in more than one edge POD locations, where resources include hardware and/or software, and where software resources lifecycle includes software development, upgrades, downgrades, logging, monitoring etc. Methods are provided for decoupling storage from compute and network functions in each virtual machine (VM)-based NFVI deployment location and moving it to a centralized location. Centralized storage could simultaneously interact with more than one edge PODs, and the security is built-in with periodic key rotation. Methods are provided for increasing NFVI system viability by dedicating (fencing) CPU core pairs for specific controller operations and workload operations, and sharing the CPU cores for specific tasks.

Abstract: Systems, methods, and computer-readable media are provided for reusing execution environments and code of serverless functions while ensuring isolation in serverless computing environments. In some examples, a method can include, in response to a first request to run a serverless function, executing, at an execution environment on a network, computer-readable code configured to perform the serverless function; after the computer-readable code has executed, modifying a pointer to an area of memory used to store a first state of the serverless function to reference a different area of memory; in response to a second request to run the serverless function, reusing, at the execution environment, the computer-readable code to perform the serverless function; and based on the pointer referencing the different area of memory, using the different area of memory to store a second state of the serverless function.

Abstract: Systems, methods, and computer-readable media are provided for reusing execution environments and code of serverless functions while ensuring isolation in serverless computing environments. In some examples, a method can include, in response to a first request to run a serverless function, executing, at an execution environment on a network, computer-readable code configured to perform the serverless function; after the computer-readable code has executed, modifying a pointer to an area of memory used to store a first state of the serverless function to reference a different area of memory; in response to a second request to run the serverless function, reusing, at the execution environment, the computer-readable code to perform the serverless function; and based on the pointer referencing the different area of memory, using the different area of memory to store a second state of the serverless function.

Abstract: A network management method includes a controller receiving an underlay network identifier and a network segment identifier. The underlay network identifier and network segment identifier can be associated with entries in a forwarding information base and border gateway protocol speakers may be deployed in association with the entries. A virtual network can be associated with the underlay network and network traffic can be forwarded to the virtual network according to the entries.

Abstract: A lift nacelle may comprise an airflow generator; a sidewall system coupled to the airflow generator and spanning in a first direction, wherein the sidewall system defines a nacelle interior space, wherein the airflow generator defines one of a forward boundary or an aft boundary of the nacelle interior space; and a lift body disposed in the nacelle interior space and spanning substantially perpendicular to the first direction and substantially perpendicular to an upward lift direction. The airflow generator may be configured to accelerate airflow in an aft direction into the nacelle interior space through the forward boundary of the nacelle interior space. The airflow may contact and/or interact with the lift body creating lift in response.

Abstract: A network management method includes a controller receiving an underlay network identifier and a network segment identifier. The underlay network identifier and network segment identifier can be associated with entries in a forwarding information base and border gateway protocol speakers may be deployed in association with the entries. A virtual network can be associated with the underlay network and network traffic can be forwarded to the virtual network according to the entries.

Abstract: A lift nacelle may comprise an airflow generator; a sidewall system coupled to the airflow generator and spanning in a first direction, wherein the sidewall system defines a nacelle interior space, wherein the airflow generator defines one of a forward boundary or an aft boundary of the nacelle interior space; and a lift body disposed in the nacelle interior space and spanning substantially perpendicular to the first direction and substantially perpendicular to an upward lift direction. The airflow generator may be configured to accelerate airflow in an aft direction into the nacelle interior space through the forward boundary of the nacelle interior space. The airflow may contact and/or interact with the lift body creating lift in response.

Abstract: Systems, methods, and computer-readable media are provided for reusing execution environments and code of serverless functions while ensuring isolation in serverless computing environments. In some examples, a method can include, in response to a first request to run a serverless function, executing, at an execution environment on a network, computer-readable code configured to perform the serverless function; after the computer-readable code has executed, modifying a pointer to an area of memory used to store a first state of the serverless function to reference a different area of memory; in response to a second request to run the serverless function, reusing, at the execution environment, the computer-readable code to perform the serverless function; and based on the pointer referencing the different area of memory, using the different area of memory to store a second state of the serverless function.

Abstract: A system is provided that includes one management cluster to manage network function virtualization infrastructure (NFVI) resources lifecycle in more than one edge POD locations, where resources include hardware and/or software, and where software resources lifecycle includes software development, upgrades, downgrades, logging, monitoring etc. Methods are provided for decoupling storage from compute and network functions in each virtual machine (VM)-based NFVI deployment location and moving it to a centralized location. Centralized storage could simultaneously interact with more than one edge PODs, and the security is built-in with periodic key rotation. Methods are provided for increasing NFVI system viability by dedicating (fencing) CPU core pairs for specific controller operations and workload operations, and sharing the CPU cores for specific tasks.

Abstract: Systems, methods, and computer-readable media are provided for reusing execution environments and code of serverless functions while ensuring isolation in serverless computing environments. In some examples, a method can include, in response to a first request to run a serverless function, executing, at an execution environment on a network, computer-readable code configured to perform the serverless function; after the computer-readable code has executed, modifying a pointer to an area of memory used to store a first state of the serverless function to reference a different area of memory; in response to a second request to run the serverless function, reusing, at the execution environment, the computer-readable code to perform the serverless function; and based on the pointer referencing the different area of memory, using the different area of memory to store a second state of the serverless function.

Abstract: Systems, methods, and computer-readable media are provided for reusing execution environments and code of serverless functions while ensuring isolation in serverless computing environments. In some examples, a method can include, in response to a first request to run a serverless function, executing, at an execution environment on a network, computer-readable code configured to perform the serverless function; after the computer-readable code has executed, modifying a pointer to an area of memory used to store a first state of the serverless function to reference a different area of memory; in response to a second request to run the serverless function, reusing, at the execution environment, the computer-readable code to perform the serverless function; and based on the pointer referencing the different area of memory, using the different area of memory to store a second state of the serverless function.

Abstract: A system is provided that includes one management cluster to manage network function virtualization infrastructure (NFVI) resources lifecycle in more than one edge POD locations, where resources include hardware and/or software, and where software resources lifecycle includes software development, upgrades, downgrades, logging, monitoring etc. Methods are provided for decoupling storage from compute and network functions in each virtual machine (VM)-based NFVI deployment location and moving it to a centralized location. Centralized storage could simultaneously interact with more than one edge PODs, and the security is built-in with periodic key rotation. Methods are provided for increasing NFVI system viability by dedicating (fencing) CPU core pairs for specific controller operations and workload operations, and sharing the CPU cores for specific tasks.