softec

Ordina per: Data / Titolo / URL

Puppet Infrastructure Design Guidelines
2010-05-13 to , , , by lorello
docs/guide.md at master from robey's kestrel - GitHub
Kestrel is a very simple message queue that runs on the JVM and uses the memcache protocol (with some extensions) to talk to clients. A single kestrel server has a set of queues identified by a name, which is also the filename of that queue's journal file (usually in /var/spool/kestrel). Each queue is a strictly-ordered FIFO of "items" of binary data. Usually this data is in some serialized format like JSON or ruby's marshal format. Generally queue names should be limited to alphanumerics [A-Za-z0-9], dash (-) and underline (_). In practice, kestrel doesn't enforce any restrictions other than the name can't contain slash (/) because that can't be used in filenames, squiggle (~) because it's used for temporary files, plus (+) because it's used for fanout queues, and dot (.) because it's reserved for future use. Queue names are case-sensitive, but if you're running kestrel on OS X or Windows, you will want to refrain from taking advantage of this, since the journal filenames on those two platforms are not case-sensitive. A cluster of kestrel servers is like a memcache cluster: the servers don't know about each other, and don't do any cross-communication, so you can add as many as you like. Clients have a list of all servers in the cluster, and pick one at random for each operation. In this way, each queue appears to be spread out across every server, with items in a loose ordering. When kestrel starts up, it scans the journal folder and creates queues based on any journal files it finds there, to restore state to the way it was when it last shutdown (or was killed or died). New queues are created by referring to them (for example, adding or trying to remove an item). A queue can be deleted with the "delete" command.
2010-03-02 to , , , , , , by lorello
EngineHosting
Load-Balanced VPS Hosting | Load-balanced Web Hosting for the Dynamic Web
2009-09-24 to , , , , by lorello
ResourceSpace: Open Source Digital Asset Management (DAM)
ResourceSpace is a web-based, open source digital asset management system which has been designed to give your content creators easy and fast access to print and web ready assets.
2009-08-11 to , , , , by lorello
La library di Open-E
Open-E Library, Open-E data storage software solutions - Knowledge Database, Data Sheets, White Papers and Installation Guides, Product Presentations, Customer Case Studies and list of Storage Powered by Open-E
2009-03-07 to , , , by lorello
HP Sizing and Configuration Tool for Microsoft Exchange Server 2007
This new version provides HP ProLiant server and storage sizing guidelines for Microsoft Exchange Server 2007 solutions, incorporating the results from HP's solutions engineering labs and characterization testing to provide configuration details for Exchange 2007 Server roles including mailbox servers, hub transport servers, client access servers, edge servers and unified messaging servers. Included is support for high availability solutions including Local Continuous Replication, Cluster Continuous Replication, and Single Copy Clusters. HP’s StorageWorks Sizing tool is also integrated, providing the ability to size a SAN or DAS infrastructure as part of the Exchange environment. This tool provides a choice of server platforms including BL, DL, and ML configured with either Intel or AMD processors.
2009-03-05 to , , , , , , , , , by lorello
HP BladeSystem c-Class Components
Da questa pagina si possono sfogliare tutti i componenti, dall'enclosure, ai server blade, ai sistemi di interconnessione, sia Virtual Connect che Switch
2009-03-05 to , , , , by lorello
HP BladeSystem Technical Resources
Documenti tecnici, FAQ e spiegazioni per le Blade HP
2009-03-05 to , , , , by lorello
ProLiant Servers Configurator
Strumento guidato per configurare correttamente i server HP Proliant, sia rack che blade
2009-03-05 to , , , , by lorello
Rhodes
The Rhodes framework is an open source Ruby-based platform for building locally executing, device-optimized mobile applications. It is similar in concept to MVC frameworks such as Rails, Merb and Camping but much lighter weight (and hence executable on a mobile device) than any of these. Along the way of course, we had to implement Ruby for these device operating systems (iPhone, Windows Mobile, RIM and Symbian).
2009-03-04 to , , , , , , , , by lorello

Precedente / Seguente / Pagina 1 di 2