Abstract: In accordance with example implementations, a process includes associating a secondary computer system with a primary computer system. The secondary computer system includes a first virtual machine, which is hosted by a secondary set of physical computer nodes. The primary computer system has a primary role, and the primary role corresponds to a minimum physical resource allocation. The secondary computer system is associated with a secondary role, and the second computer system is provisioned with a second physical resource allocation, which is less than the minimum physical resource allocation. The process includes, responsive to the primary computer system failing and without rebooting the secondary computer system, preparing the secondary computer system to take over the primary role. The preparation includes adding at least one physical computer node to the secondary set of physical computer nodes to cause the second physical resource allocation to meet or exceed the minimum physical resource allocation.

Abstract: A technique includes receiving information relating to wear of computer nodes. Based on the information relating to the wear, the technique includes ranking the computer nodes according to respective expected remaining lifetimes of the computer nodes. The technique includes, responsive to an event that corresponds to at least one of a spare computer node being added to the system or a given computer node being removed from the system, reconfiguring the system based on the ranking.

Abstract: Handling frequently accessed pages is disclosed. An indication is received of a stalling event caused by a requested portion of memory being inaccessible. It is determined that the requested portion of memory is a frequently updated portion of memory. The stalling event is handled based at least in part on the determination that the requested portion of memory is a frequently updated portion of memory.

Abstract: An apparatus for aligning and shimming plates being anchored to a substratum having a plurality of threaded anchor holes coaxially aligned with corresponding apertures and coaxial threaded bores through each plate. The apparatus includes an external threaded cylindrical shim having a shimming surface and a second (outer) surface adapted to accept rotary force for rotational movement and adjustment of the separation produced by the shim between the substratum and the anchored plate. For anchoring, the 2nd surface of the shim further includes a counterbored or countersunk hole having a shoulder including a narrower passthrough aperture aligned with the threaded anchor hole, through which an anchor screw extends for rotational mating with the threaded anchor hole. The anchor screw also has a head wider than the passthrough aperture, and adapted to accept rotary force for rotational movement and fixing the shim in place.

Abstract: In various embodiments, methods and systems for game development based on an integrated game development cloud computing platform are provided. Development components that facilitate game development using an integrated game-cloud component are initiated. An input is received to perform a game development task. The game development task is associated with one or more games. The game development task is executed using the integrated game-cloud component. The integrated game-cloud component comprises a game-development-platform development component and a cloud-computing-platform development component combined into an integrated development component supported on the integrated game development cloud computing platform. The game development task can be associated with a first game-platform and a second game-platform of a selected game. The game-platform functions with a cross-platform support component having an integrated core module and an integrated game-platform module.

Abstract: A deployable computing environment may facilitate interaction and data sharing between users and devices. Users, devices, and relationships between the users and devices may be represented within the deployable computing environment. A relationship between a user and a device may specify that the device is owned by the user and that the device is authorized to perform operations within the deployable computing environment on behalf of the user. Secure authentication of devices and users for interaction within the deployable computing environment is achieved by authenticating tickets corresponding to the user, the device, and the relationship. A device identification ticket and a user identification ticket are used to authenticate the device and user for interaction within the deployable computing environment. A device claim ticket allows the device to perform delegated operations (e.g., data synchronization, peer connectivity, etc.) on behalf of the user without the user's credentials (e.g.

Abstract: A deployable computing environment may facilitate interaction and data sharing between users and devices. Users, devices, and relationships between the users and devices may be represented within the deployable computing environment. A relationship between a user and a device may specify that the device is owned by the user and that the device is authorized to perform operations within the deployable computing environment on behalf of the user. Secure authentication of devices and users for interaction within the deployable computing environment is achieved by authenticating tickets corresponding to the user, the device, and the relationship. A device identification ticket and a user identification ticket are used to authenticate the device and user for interaction within the deployable computing environment. A device claim ticket allows the device to perform delegated operations (e.g., data synchronization, peer connectivity, etc.) on behalf of the user without the user's credentials (e.g.

Abstract: A deployable computing environment may facilitate interaction and data sharing between users and devices. Users, devices, and relationships between the users and devices may be represented within the deployable computing environment. A relationship between a user and a device may specify that the device is owned by the user and that the device is authorized to perform operations within the deployable computing environment on behalf of the user. Secure authentication of devices and users for interaction within the deployable computing environment is achieved by authenticating tickets corresponding to the user, the device, and the relationship. A device identification ticket and a user identification ticket are used to authenticate the device and user for interaction within the deployable computing environment. A device claim ticket allows the device to perform delegated operations (e.g., data synchronization, peer connectivity, etc.) on behalf of the user without the user's credentials (e.g.

Abstract: A deployable computing environment may facilitate interaction and data sharing between users and devices. Users, devices, and relationships between the users and devices may be represented within the deployable computing environment. A relationship between a user and a device may specify that the device is owned by the user and that the device is authorized to perform operations within the deployable computing environment on behalf of the user. Secure authentication of devices and users for interaction within the deployable computing environment is achieved by authenticating tickets corresponding to the user, the device, and the relationship. A device identification ticket and a user identification ticket are used to authenticate the device and user for interaction within the deployable computing environment. A device claim ticket allows the device to perform delegated operations (e.g., data synchronization, peer connectivity, etc.) on behalf of the user without the user's credentials (e.g.

Abstract: A deployable computing environment may facilitate interaction and data sharing between users and devices. Users, devices, and relationships between the users and devices may be represented within the deployable computing environment. A relationship between a user and a device may specify that the device is owned by the user and that the device is authorized to perform operations within the deployable computing environment on behalf of the user. Secure authentication of devices and users for interaction within the deployable computing environment is achieved by authenticating tickets corresponding to the user, the device, and the relationship. A device identification ticket and a user identification ticket are used to authenticate the device and user for interaction within the deployable computing environment. A device claim ticket allows the device to perform delegated operations (e.g., data synchronization, peer connectivity, etc.) on behalf of the user without the user's credentials (e.g.

Abstract: In various embodiments, methods and systems for game development based on an integrated game development cloud computing platform are provided. Development components that facilitate game development using an integrated game-cloud component are initiated. An input is received to perform a game development task. The game development task is associated with one or more games. The game development task is executed using the integrated game-cloud component. The integrated game-cloud component comprises a game-development-platform development component and a cloud-computing-platform development component combined into an integrated development component supported on the integrated game development cloud computing platform. The game development task can be associated with a first game-platform and a second game-platform of a selected game. The game-platform functions with a cross-platform support component having an integrated core module and an integrated game-platform module.

Abstract: Grouping personal accounts to tailor a web service may be accomplished by grouping information from two or more personal accounts. In some embodiments, a personal account may include a set of persons. By grouping personal accounts, a service provider may tailor a web service to multiple people based on information about those people.

Abstract: Virtual location information is received at one or more devices as part of a virtual location check-in request for a user. The virtual location information identifies a virtual location of the user in a virtual environment. A notification of the virtual location of the user in the virtual environment is sent from the one or more devices to one or more additional users external to the virtual environment. One or more gameplay features can also be made available to the user based on the virtual location.

Abstract: A representational state transfer-based model for a computing environment uses models resources with links between them. Security principals are resources which can be independently authenticated. Each resource may be associated with an authorization policy that determines level of access, protocol supported. Successfully presenting security credentials at a security principal allows use of an instance of the security principal (i.e. application) as well as generation of an authentication token that can be presented across the computing environment to resources subscribing to the same authorization policy. As security principals with different security policies are authenticated, the appropriate tokens may be combined to allow broader access without undue re-authentication for resources subscribing to the same security policy.

Abstract: A deployable computing environment may facilitate interaction and data sharing between users and devices. Users, devices, and relationships between the users and devices may be represented within the deployable computing environment. A relationship between a user and a device may specify that the device is owned by the user and that the device is authorized to perform operations within the deployable computing environment on behalf of the user. Secure authentication of devices and users for interaction within the deployable computing environment is achieved by authenticating tickets corresponding to the user, the device, and the relationship. A device identification ticket and a user identification ticket are used to authenticate the device and user for interaction within the deployable computing environment. A device claim ticket allows the device to perform delegated operations (e.g., data synchronization, peer connectivity, etc.) on behalf of the user without the user's credentials (e.g.

Abstract: This document describes grouping personal accounts to tailor a web service. By grouping personal accounts, a service provider may tailor a web service to multiple people based on information about those people.

Abstract: A ticketing system adapted for use with a cloud-based services platform is provided by a ticket-based authorization model in which the authorization requirements for traversing one or more meshes of resources associated with a cloud service are annotated in links included in a resource that refer to other resources. The meshes are thus self-describing with respect to the association among the resources (i.e., the links) as well as the authorization required to access resources. Resource access requires a principal ticket which asserts that a caller at a client (e.g., a security principal representing a device or identity associated with a user) is authenticated, plus zero or more claim tickets. The claim tickets make additional assertions about the caller that the cloud service may use to check that the caller is authorized to access the resource.

Abstract: A computer-implemented method for assisting in the scheduling of a meeting. A user who desires to schedule a meeting simply inputs the relevant meeting parameters. In response, the computer evaluates a number of possible meeting times by comparing the input constraints against a predetermined set of suitability criteria. Based on this evaluation, the system identifies suggested meeting time(s), and also may identify rooms suitable for each meeting time. The system also calculates an estimated desirability for each suggested meeting time based on its compliance with the suitability criteria. The suggested meeting time(s) and a visual indicator of desirability for each time are then displayed. In addition, the raw free-busy data for each attendee may still be displayed. When the user selects a suggested meeting time, an electronic meeting request is automatically populated with the meeting time and a suitable place associated with the suggested meeting time.

Abstract: A deployable computing environment may facilitate interaction and data sharing between users and devices. Users, devices, and relationships between the users and devices may be represented within the deployable computing environment. A relationship between a user and a device may specify that the device is owned by the user and that the device is authorized to perform operations within the deployable computing environment on behalf of the user. Secure authentication of devices and users for interaction within the deployable computing environment is achieved by authenticating tickets corresponding to the user, the device, and the relationship. A device identification ticket and a user identification ticket are used to authenticate the device and user for interaction within the deployable computing environment. A device claim ticket allows the device to perform delegated operations (e.g., data synchronization, peer connectivity, etc.) on behalf of the user without the user's credentials (e.g.

Abstract: A ticketing system adapted for use with a cloud-based services platform is provided by a ticket-based authorization model in which the authorization requirements for traversing one or more meshes of resources associated with a cloud service are annotated in links included in a resource that refer to other resources. The meshes are thus self-describing with respect to the association among the resources (i.e., the links) as well as the authorization required to access resources. Resource access requires a principal ticket which asserts that a caller at a client (e.g., a security principal representing a device or identity associated with a user) is authenticated, plus zero or more claim tickets. The claim tickets make additional assertions about the caller that the cloud service may use to check that the caller is authorized to access the resource.