Abstract: Embodiments herein comprise a centralized NVMe-oF namespace masking and configuration repository, which may be referenced for convenience herein as a distributed configuration service (DCS). By centralizing the functionality, there is no longer a requirement that each host, network element, and subsystem have its own user interface (UI). DCS embodiments provide a single UI for a number of features, including but not limited to: (1) viewing the list of Host interfaces that are attached to the network and are registered; (2) viewing the list of Subsystem interfaces that are attached to the IP Network and are registered with the DCS; (3) viewing the storage capacity available behind each subsystem interface; and (4) allowing a user to define the Host to Subsystem interface relationships as well as define how much storage should be allocated to each Host.

Abstract: Systems and methods provide modern storage networks, such as those utilizing a non-volatile memory express over Fabric (NVMe-oF) system, with connectivity options that meet low-latency and high-throughput demands. In certain embodiments, this is accomplished by enabling network entities to acquire and utilize network information, including discovery information, to dynamically manage routing tables and build routes, e.g., to allow a host to send out frames through desired interfaces to reach target destinations. An automated IP routing update service allows for dynamically creating, reading, updating, and deleting functions of otherwise static IP routing table entries to streamline functions in the storage fabric.

Abstract: To address concerns with administration of zones in storage area network (SAN) environments, presented are embodiments of a “zone group,” including systems and methods for configuring, implementing, and managing such. While zone group embodiments may comprise one or more zones, unlike traditional zone sets, a zone group includes additional features. For example, a zone group includes an “Owner” and also allows for multiple zone groups to be active on a fabric at one time. By adding the concept of an owner to a zone group, changes made by a user or entity impact the zone group to which the owner has rights to access or modify. Also, by allowing multiple zone groups to be active at the same time, embodiments enable multiple administrators or entities to make unrelated modifications to connectivity and dramatically reduce the impact of unintentional changes. Additional features and benefits are described herein.

Abstract: Systems and methods provide zero-configuration provisioning for modern storage networks such as those utilizing a non-volatile memory express over Fabric (NVMe-oF) system. In various embodiments, this is accomplished by leveraging discovery information, such as multicast Domain Name System (mDNS) information, to locate subsystems in a network and to explicitly and dynamically specify target destinations without a Centralized Discovery Controller (CDC) client having to modify its routing table.

Abstract: A current technique to enforce a Zoning configuration is referred to as “Hard Zoning”. Hard Zoning is a technique in which network switches in a fabric inspect packets to ascertain if a packet should be forwarded or discarded, according to the communication between nodes allowed by the Zoning configuration. For the network switches to be able to perform this packet-by-packet filtering, Zoning information needs to be supplied to the network switches. However, current approaches involve sending duplicate data to switches. These approaches are very inefficient and cumbersome. Accordingly, embodiments comprise a Centralized Discovery Controller (CDC) that collects network information, generates, for a switch, its appropriate zoning information, and sends the switch-specific zoning information to that switch.

Abstract: In the case of FC-NVMe (NVMe over Fabrics using FC as a transport), zoning is typically performed using the interface WWPNs, but the masking of NVMe namespaces is performed using a host's NVMe Qualified Name (NQN or HOSTNQN). The use of two identifiers (i.e., one identifier used for zoning and another identifier used for masking) introduces a potential security related concern. A bad actor may obtain the NQN of a host that has access to sensitive information and use it to access this sensitive information. Accordingly, in one or more embodiments, by correlating different identifiers and using a combination of the different identifiers, access can easily be provided to the appropriate host adapters while prohibiting access to rogue hosts.

Abstract: Presented herein are embodiments for providing and using a symbolic name for referencing an element of a non-volatile memory express (NVMe™) entity in an NVMe™-over-Fabric (NVMe-oF™) environment. In one or more embodiments, the symbolic name may be used to identify an element of an NVMe™ host or NVM subsystem in one or more processes. In one or more embodiments, a symbolic name may be provided as part of a registration process. Symbolic names may be used for identifying elements when performing other processes, such as masking and zoning for granting access rights. In one or more embodiments, a symbolic name may be shared by two or more elements.

Abstract: Presented herein are embodiments for implicitly or indirectly registering elements of a non-volatile memory express (NVMe™) entity in an NVMe-over-Fabric (NVMe-oF) environment. In one or more embodiments, one or more interactions between an NVMe™ entity and a centralized storage fabric service component, such as part of the Link Layer Discovery Protocol (LLDP) process or the Multicast Domain Name System (mDNS) process, may be used by the centralized storage fabric service to extract information about the NVMe™ entity and automatically register it with a centralized registration datastore. In one or more embodiments, the centralized registration datastore may be used to facilitate services in the NVMe-oF system, such as discovery of NVMe™ entities, provisioning, and access control. In one or more embodiments, an implicitly registered NVMe™ entity may also subsequently explicitly register, which may include supplying additional information about the NVMe™ entity.

Abstract: Presented herein are systems and methods for facilitating access control among elements of a non-volatile memory express (NVMe™) entity in an NVMe™-over-Fabric (NVMe-oF) environment. In one or more embodiments, NVMe™ entities, whether NVMe™ hosts or NVMe™ subsystems, can obtain information about elements of NVMe™ entities that have registered with a centralized storage fabric service component via a discovery controller of the centralize service. In one or more embodiments, based upon information received from requesting NVMe™ entities, the centralized storage fabric service creates and maintains a data store of zones, in which a zone comprises a listing of elements of NVMe™ entities that are members of that zone and have access rights relative to other members of that zone.

Abstract: Presented herein are embodiments for registering elements of a non-volatile memory express (NVMe) entity in an NVMe-over-Fabric (NVMe-oF) environment. In embodiments, a method for registering with a centralized storage fabric service component via a discovery controller (DC) of the centralize service comprises transmitting a DC registration command to the DC. In embodiments, the DC registration command includes a number of registration entries that the NVMe entity will be submitting for registration. In embodiments, the identified number of NVMe registration entries are transmitted to the centralized service and are stored in a registry. The NVMe registration entry may include an entry type for indicating an NVMe registration entry type, an NVMe qualified name (NQN) for identifying the NVMe entity, and a transport address for specifying an address of the element of the NVMe entity. Other NVMe entities may query the registry to obtain information about NVMe elements in the system.

Abstract: Presented herein are systems and methods for facilitating access control among elements of a non-volatile memory express (NVMe) entity in an NVMe-over-Fabric (NVMe-oF) environment. In one or more embodiments, NVMe entities, whether NVMe hosts or NVMe subsystems, can obtain information about elements of NVMe entities that have registered with a centralized storage fabric service component via a discovery controller of the centralize service. In one or more embodiments, based upon information received from requesting NVMe entities, the centralized storage fabric service creates and maintains a data store of zones, in which a zone comprises a listing of elements of NVMe entities that are members of that zone and have access rights relative to other members of that zone.

Abstract: Provided is a distribution platform for physician-owned Durable Medical Equipment (DMEs). In the platform, the system authenticates a physician and selects or creates a patient, and determines a set of possible diagnosis code combinations that match a service being provided. The system selects a product from a displayed set of products that match the service being provided, dynamically generates a set of medical necessities, and confirms the generated set of medical necessities. The system selects a product SKU based on the determined set of possible diagnosis code combinations, the selected product, and the confirmed set of medical necessities. The system dynamically generates confirmations based on DMEPOS standards, and confirms the generated confirmations by electronical signature of the physician, where the confirmation with signature is recorded with a time stamp.

Abstract: Presented herein are embodiments for registering elements of a non-volatile memory express (NVMe) entity in an NVMe-over-Fabric (NVMe-oF) environment. In embodiments, a method for registering with a centralized storage fabric service component via a discovery controller (DC) of the centralize service comprises transmitting a DC registration command to the DC. In embodiments, the DC registration command includes a number of registration entries that the NVMe entity will be submitting for registration. In embodiments, the identified number of NVMe registration entries are transmitted to the centralized service and are stored in a registry. The NVMe registration entry may include an entry type for indicating an NVMe registration entry type, an NVMe qualified name (NQN) for identifying the NVMe entity, and a transport address for specifying an address of the element of the NVMe entity. Other NVMe entities may query the registry to obtain information about NVMe elements in the system.

Abstract: Presented herein are embodiments for providing and using a symbolic name for referencing an element of a non-volatile memory express (NVMe) entity in an NVMe-over-Fabric (NVMe-oF) environment. In one or more embodiments, the symbolic name may be used to identify an element of an NVMe host or NVM subsystem in one or more processes. In one or more embodiments, a symbolic name may be provided as part of a registration process. Symbolic names may be used for identifying elements when performing other processes, such as masking and zoning for granting access rights. In one or more embodiments, a symbolic name may be shared by two or more elements.

Abstract: Multicast Domain Name System (mDNS)-based pull registration systems and methods facilitate discovery in communication networks, such as Storage Area Networks (SANs) that operate in non-volatile memory express over Fabric (NVMe-oF) environments. In various embodiments, this is accomplished by allowing a network entity (e.g., a Centralized Discovery Controller (CDC)) to use a pull registration to exchange discovery information with a storage subsystem (e.g., a storage array), advantageously, without requiring storage subsystem to possess complex functionalities present in existing designs.

Abstract: Multicast Domain Name System (mDNS)-based pull registration systems and methods facilitate discovery in communication networks, such as Storage Area Networks (SANs) that operate in non-volatile memory express over Fabric (NVMe-oF) environments. In various embodiments, this is accomplished by allowing a network entity (e.g., a Centralized Discovery Controller (CDC)) to use a pull registration to exchange discovery information with a storage subsystem (e.g., a storage array), advantageously, without requiring storage subsystem to possess complex functionalities present in existing designs.

Abstract: Presented herein are embodiments for implicitly or indirectly registering elements of a non-volatile memory express (NVMe) entity in an NVMe-over-Fabric (NVMe-oF) environment. In one or more embodiments, one or more interactions between an NVMe entity and a centralized storage fabric service component, such as part of the Link Layer Discovery Protocol (LLDP) process or the Multicast Domain Name System (mDNS) process, may be used by the centralized storage fabric service to extract information about the NVMe entity and automatically register it with a centralized registration datastore. In one or more embodiments, the centralized registration datastore may be used to facilitate services in the NVMe-oF system, such as discovery of NVMe entities, provisioning, and access control. In one or more embodiments, an implicitly registered NVMe entity may also subsequently explicitly register, which may include supplying additional information about the NVMe entity.

Abstract: One embodiment of the present disclosure presents a technique for generating an augmented reality effect. The technique includes receiving first input data including an image of a face. The technique further includes, based on the first input data, generating a first intermediate texture corresponding to an eyelid of the face with make-up. The technique further includes, based on the first input data, generating a second intermediate texture corresponding to the eyelid of the face without make-up. The technique also includes generating an output texture based on the first intermediate texture and the second intermediate texture. The technique further includes generating an effect by applying the output texture to second input data corresponding to a second image of a second face.

Abstract: Described are techniques for processing a network connectivity request received by a virtual network connectivity service. First processing is performed by the virtual network connectivity service to service the network connectivity request. The first processing includes determining a first of a plurality of network control planes to which the network connectivity request is directed, selecting, in accordance with the first network control plane, one of a plurality of modules, and invoking the one module in connection with performing processing to service the network connectivity request.

Abstract: Described are techniques for determining connectivity. Statistics are received regarding components of the data storage system including any of a target port, a front end adapter, and a device. It is determined in accordance with inputs whether to modify existing connectivity between an initiator set of one or more initiators and a target set of one or more target ports of the data storage system. The inputs include the one or more statistics and one or more adjustment criteria. Responsive to determining to modify the existing connectivity, first processing makes modification(s) to the existing connectivity including any of: modifying an access state associated with a target port over which a device is exposed to an initiator, and adding or removing connectivity between the initiator and another target port of the data storage system where a device is exposed to the initiator over the another target port.