Closed Bug 1009361 Opened 11 years ago Closed 11 years ago

Provide method to allocate a user to a specific node.

Categories

(Cloud Services Graveyard :: Server: Token, defect, P2)

defect

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: bobm, Assigned: rfkelly)

Details

(Whiteboard: [qa+])

Attachments

(1 file)

Please provide a method to assign a given user to a specific Sync storage node. This will be useful for balancing user traffic by a number factors, such as time of day usage, or separating heavy users onto more robust servers.
Priority: -- → P2
Hardware: x86 → All
Whiteboard: [qa+]
Here's an "allocate_user" script that should do the job. Usage: $ ./local/bin/python -m tokenserver.scripts.allocate_user --help Usage: allocate_user.py [options] config_file service email [node_name] Allocate a user to a node. You may specify a particular node, or omit to use the best available node. Options: -h, --help show this help message and exit -v, --verbose Control verbosity of log messages $
Attachment #8444947 - Flags: review?(telliott)
Attachment #8444947 - Flags: review?(telliott) → review+
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Will this be attached to a TS deployment? Or is this just for general use by OPs?
It has internal TS components, so it will need to happen as part of a deployment.
Dropping this in "the next TS deployment" bucket with bug 997344
:bobm or :mostlygeek - is this in the current deployment - bug 1046464
(In reply to James Bonacci [:jbonacci] from comment #6) > :bobm or :mostlygeek - is this in the current deployment - bug 1046464 Not presently set up on the node manager.
Product: Cloud Services → Cloud Services Graveyard
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: