Abstract:
Aspects extend to methods, systems, and computer program products for configuring a cloud from aggregate declarative configuration data. A declarative language can be used to declare physical and logical topology as well as cloud operations commands at multiple topology hierarchies. Developers of different cloud components can declare roles and cloud operations in compliance with a declaration model. Compliance with the declaration model allows aggregation and cross-referencing among commands and topology elements declared by different developers. As such, dependencies between components can be efficiently identified and accounted for when implementing cloud operation commands. Declarative configuration data can also be used to onboard additional components to a cloud without code changes to an underlying configuration engine.
Abstract:
Aspects extend to methods, systems, and computer program products for using declarative configuration data to manage cloud lifecycle. A declarative language can be used to declare physical and logical topology as well as lifecycle management commands at multiple topology hierarchies. Developers of different cloud components can declare roles and cloud operations in compliance with a declaration model. Compliance with the declaration model allows aggregation and cross-referencing among commands and topology elements declared by different developers. As such, dependencies between components can be efficiently identified and accounted for when implementing lifecycle management commands. Declarative configuration data can also be used to onboard additional components to a cloud without code changes to an underlying lifecycle state manager.
Abstract:
Technologies for performing a data copy operation on a data storage device include storing a copy token in a power-fail-safe data structure that identifies the source address and destination address of the data copy operation, updating an address table to indicate that the source and destination addresses are involved in the data copy operation, and notifying a host requesting that data copy operation that the data copy operation has been completed prior to performing the data copy operation. The host may subsequently perform other tasks while the data storage device completes the data copy operation. During the data copy operation, data access requests to the source or destination addresses are blocked based on the address table. Additionally, should a power failure event occur, the power-fail-safe data structure is saved to non-volatile data storage so that the copy operation may be completed upon the next power-on event of the data storage device.
Abstract:
Technologies for discontinuous execution include a compiler computing device and one or more target computing devices. The compiler computing device converts a computer program into a sequence of atomic transactions and coalesces the transactions to generate additional sequences of transactions. The compiler computing device generates an executable program including two or more sequences of transactions having different granularity. A target computing device selects an active sequence of transactions from the executable program based on the granularity of the sequence and a confidence level. The confidence level is indicative of available energy produced by an energy harvesting unit of the target computing device. The target computing device increases the confidence level in response to successfully committing transactions from the active sequence of transactions into non-volatile memory. In response to a power failure, the target computing device resets the confidence level and resumes executing the transactions. Other embodiments are described and claimed.
Abstract:
Apparatus, systems, and methods to implement boot operations in nonvolatile storage devices are described. In one example, a controller comprises logic to receive a shutdown notification from a host device operating system, monitor modifications to one or more an indirection table segments for the nonvolatile memory during a shutdown process, and mark the one or more indirection table segments which were modified during the shutdown for fast loading during a subsequent boot process for the host device. Other examples are also disclosed and claimed.
Abstract:
L'invention porte sur un procédé de sécurisation de la coupure d'alimentation d'un équipement USB, mis en œuvre dans réseau USB par l'intermédiaire duquel sont interconnectés un calculateur, maître du réseau, et au moins un équipement USB, esclave du réseau. Selon l'invention, lorsqu'une information de coupure d'alimentation imminente de l'équipement USB est connue dudit calculateur, ledit procédé comprend la mise en œuvre des étapes successives suivantes : - l'envoi par le calculateur d'un message d'information (MG) sur le réseau USB, contenant une information de coupure d'alimentation de l'équipement USB; - la réception du message d'information (MG) par l'équipement USB; - la mise en œuvre par l'équipement USB d'une procédure de préparation de l'équipement USB à la coupure d'alimentation imminente.
Abstract:
Un procédé permet d'obtenir des informations stockées dans des registres (R11 -R4J) d'au moins un module de traitement (MT1 -MTJ) d'un calculateur (CA), chaque module de traitement (MT1 -MTJ) comprenant en outre un contrôleur de gestion (CG1 -CGJ) propre à lire les informations stockées dans les registres (R11 -R4J) associés, et un circuit logique programmable (CL1 -CLJ) propre à déclencher une réinitialisation requise consécutivement à une erreur fatale. Pour ce faire, en cas de réception d'une requête de réinitialisation par un circuit logique programmable (CL2) d'un module de traitement (MT2), ce circuit logique programmable (CL2) suspend le déclenchement de cette réinitialisation et alerte de la survenue d'une erreur fatale le contrôleur de gestion (CG2) associé qui, s'il en est capable, lit les informations stockées dans des registres (R12-R42) associés et choisis, puis stocke ces informations lues dans un fichier, puis on autorise le circuit logique programmable (CL2) associé à déclencher la réinitialisation requise.