G06F9/44536

Method and system for automation tool set for server maintenance actions

Embodiments of a system, methods, and other techniques and configurations for automation of computing system maintenance activities such as reboots, software installations, re-configuration, or other actions are generally described herein. In an example, an automation tool set is designed to integrate with an organization Configuration Management Database (CMDB) and other orchestration or information technology (IT) management tools to perform such maintenance actions. The automation tool set may enable and manage various forms of a workflow for maintenance actions, including a workflow designed to validate all necessary pre- and post-reboot checks, perform logging, event tracking, exception handling, notifications, incidents creation, trend analysis, customized reporting dashboards, and system adaptation. In further examples, the automation tool set may expose user interfaces, reports, and other management interfaces for control and monitoring of the workflows.

MIMIC COMPONENTS FOR DEPLOYING EXPERIMENTAL WEBPAGE FEATURES
20230266959 · 2023-08-24 ·

A technique for deploying an experimental version of a webpage includes using a mimic component to emulate functionality of a corresponding hidden UI component. The technique provides for receiving user input at the mimic component and, in response to the user input, executing a functional code block that bidirectionally communicates with an underlying platform code to update state data of the hidden UI component. The technique further provides for detecting, at the mimic component, an update to the state data of the hidden UI component, in response to the detection, updating state data of the mimic component based on the updated state data of the hidden UI component.

Commands to select a port descriptor of a specific version

A port descriptor version of a port descriptor to be obtained is selected. An indication of the port descriptor version is provided in a command to be preceded before another command used to obtain the port descriptor. The other command uses the port descriptor version to obtain the port descriptor. The port descriptor is obtained, and the port descriptor includes information relating to a port to be used in communication within the computing environment.

Discovery and resolution of network connected devices

One disclosed example provides, enacted on a computing system, a method of resolving a device capability model (DCM) for a network connected device, the method comprising receiving, from the network connected device, an identifier of the DCM, based on the identifier received, determining whether the DCM is stored on the computing system, when the DCM is stored on the computing system, then retrieving the DCM from the computing system, when the DCM is not stored on the computing system, then retrieving the DCM from one or more of the network connected device and a DCM repository and storing the DCM on the computing system, receiving, from a software solution, an application programming interface (API) call to retrieve the DCM from the computing system, and in response to receiving the API call, returning the DCM to the software solution.

Implementing optional specialization when compiling code

A compiler is capable of compiling instructions that do or do not supply specialization information for a generic type. The generic type is compiled into an unspecialized type. If specialization information was supplied, the unspecialized type is adorned with information indicating type restrictions for application programming interface (API) points associated with the unspecialized type, which becomes a specialized type. A runtime environment is capable of executing calls to a same API point that do or do not indicate a specialized type, and is capable of executing calls to a same API point of objects of an unspecialized type or of objects of a specialized type. When the call to an API point indicates a specialized type, and the specialized type matches that of the object (if the API point belongs to an object), then a runtime environment may perform optimized accesses based on type restrictions derived from the specialized type.

Instantiating a parametric class within a specialized context

A parametric constant resolves to different values in different contexts, but a single value within a particular context. An anchor constant is a parametric constant that allows for a degree of parametricity for an API point. The context for the anchor constant is provided by a caller to the API point. The anchor constant resolves to an anchor value that records specialization decisions for the API point within the provided context. Specialization decisions may include type restrictions, memory layout, and/or memory size. The anchor value together with an unspecialized type of the API point result in a specialized type of the API point. A class object representing the specialized type is created. The class object may be accessible to the caller, but the full value of the anchor value is not accessible to the caller. The API point is executed based on the specialization decisions embodied in the anchor value.

Dynamic type resolution for shared memory

A method and apparatus of a network device that allocates a shared memory buffer for an object is described. In an exemplary embodiment, the network device receives an allocation request for the shared memory buffer for the object. In addition, the network device allocates the shared memory buffer from shared memory of a network device, where the shared memory buffer is accessible by a writer and a plurality of readers. The network device further returns a writer pointer to the writer, where the writer pointer references a base address of the shared memory buffer. Furthermore, the network device stores the object in the shared memory buffer, wherein the writer accesses the shared memory using the writer pointer. The network device further shares the writer pointer with at least a first reader of the plurality of readers. The network device additionally translates the base address of the shared memory buffer to a reader pointer, where the reader pointer is expressed in a memory space of the first reader.

Versioned schema

A versioned schema of a data platform. A process of maintaining a call stack of executing objects of an application package having a versioned schema includes calling, by a first procedure executed by one or more processors, a second procedure of a versioned application instance, and determining, by the first procedure, a version of the second procedure based on a call context. In response to determining that the version of the second procedure is not in the call context, the first procedure determines a current version of the versioned application package adds the current version to the call context as the version of the second procedure.

Firmware for small MCU carrying a large set of features
11640466 · 2023-05-02 · ·

A controller and techniques for expanding its feature capabilities. Techniques may incorporate using an external memory to store feature sets that can be downloaded to an internal memory for intimate incorporation and usage by the controller. The external memory may be large in comparison to the internal memory. External storage of additional feature sets allows for use of a small and simple controller with access to numerous feature sets that otherwise could not be incorporated by the small controller.

Commands to select a port descriptor of a specific version

A port descriptor version of a port descriptor to be obtained is selected. An indication of the port descriptor version is provided in a command to be preceded before another command used to obtain the port descriptor. The other command uses the port descriptor version to obtain the port descriptor. The port descriptor is obtained, and the port descriptor includes information relating to a port to be used in communication within the computing environment.