Worldwide ZINC - Revision history

Frodo: /* Sites / Clusters */

2014-09-22T18:04:17Z

Sites / Clusters

← Older revision		Revision as of 18:04, 22 September 2014
Line 3:		Line 3:
	= Sites / Clusters =		= Sites / Clusters =
	* [[Cluster 0]] @ [[UCSF]]		* [[Cluster 0]] @ [[UCSF]]
	* [[Cluster 1]] @ [[UofT]]		* [[Cluster 1]] @ UofT
	* [[Cluster 2]] @ [[UCSF]]		* [[Cluster 2]] @ [[UCSF]]
	* [[Cluster 3]] @ [[UCSF]]		* [[Cluster 3]] @ [[UCSF]]

Frodo: /* Sites / Clusters */

2014-05-01T17:46:22Z

Sites / Clusters

← Older revision		Revision as of 17:46, 1 May 2014
Line 5:		Line 5:
	* [[Cluster 1]] @ [[UofT]]		* [[Cluster 1]] @ [[UofT]]
	* [[Cluster 2]] @ [[UCSF]]		* [[Cluster 2]] @ [[UCSF]]
	* ~~possible clusters to follow in China, Brazil, Germany~~...		* [[Cluster 3]] @ [[UCSF]]
			* your cluster could go here...

	{{TOCright}}		{{TOCright}}

Frodo: /* Integration of ZINC number */

2014-03-18T16:07:38Z

Integration of ZINC number

← Older revision		Revision as of 16:07, 18 March 2014
Line 21:		Line 21:

	== Integration of ZINC number ==		== Integration of ZINC number ==
	If you choose to host a mirror site of ZINC, we ask that you participate in the incremental updates of ZINC, and use a common numbering scheme. If you would like to participate at this level, please write us~~. At this time, this level of integration is wholly theoretical, but we are keen to see it progress~~.		If you choose to host a mirror site of ZINC, we ask that you participate in the incremental updates of ZINC, and use a common numbering scheme. If you would like to participate at this level, please write us.

	[[Category:Sysadmin]]		[[Category:Sysadmin]]

Frodo: /* Forked development code branches */

2014-03-18T16:07:07Z

Forked development code branches

← Older revision		Revision as of 16:07, 18 March 2014
Line 15:		Line 15:

	== Forked development code branches ==		== Forked development code branches ==
	~~We encourage~~ members of the worldwide ZINC network to participate in code and script development. ~~To do this, get started with~~ [[github]] ~~and~~ fork a branch. Changes made at your site should be ~~commited to your branch~~ for potential re-integration into the germ-line version of the code.		Members and potential members of the worldwide ZINC network should participate in code and script development. Use [[github]] to fork a branch. Changes made at your site should be committed for potential re-integration into the trunk, the germ-line version of the code.

	== Integration of DOCK Blaster job queues ==		== Integration of DOCK Blaster job queues ==

Frodo: /* Make public cycles available */

2014-03-18T16:05:34Z

Make public cycles available

← Older revision		Revision as of 16:05, 18 March 2014
Line 12:		Line 12:
	Coordination, affiliation and federation among nodes on the worldwide ZINC network are optional, and may operate at several levels		Coordination, affiliation and federation among nodes on the worldwide ZINC network are optional, and may operate at several levels
	== Make public cycles available ==		== Make public cycles available ==
	Each member of the worldwide ZINC network is asked to make a public DOCK Blaster server available, and to allow public jobs to be run~~. We request 5% or 50 cores, whichever is lower, at least be made available for public use~~.		Each member of the worldwide ZINC network is asked to make a public DOCK Blaster server available, and to allow public jobs to be run.

	== Forked development code branches ==		== Forked development code branches ==

Frodo at 15:48, 17 March 2014

2014-03-17T15:48:19Z

← Older revision		Revision as of 15:48, 17 March 2014
Line 9:		Line 9:
	{{TOCright}}		{{TOCright}}

	= ~~How the interactions work~~ =		= Levels of affiliation =
	Coordination, affiliation and federation of nodes on the worldwide ZINC network are optional, and ~~can~~ operate at several levels		Coordination, affiliation and federation among nodes on the worldwide ZINC network are optional, and may operate at several levels
	== Make public cycles available ==		== Make public cycles available ==
	Each member of the worldwide ZINC network is asked to make a public DOCK Blaster server available, and to allow public jobs to be run. We request 5% or 50 cores, whichever is lower, at least be made available for public use.		Each member of the worldwide ZINC network is asked to make a public DOCK Blaster server available, and to allow public jobs to be run. We request 5% or 50 cores, whichever is lower, at least be made available for public use.

Frodo at 15:47, 17 March 2014

2014-03-17T15:47:35Z

← Older revision		Revision as of 15:47, 17 March 2014
Line 6:		Line 6:
	* [[Cluster 2]] @ [[UCSF]]		* [[Cluster 2]] @ [[UCSF]]
	* possible clusters to follow in China, Brazil, Germany...		* possible clusters to follow in China, Brazil, Germany...

			{{TOCright}}

	= How the interactions work =		= How the interactions work =

Frodo: /* How the interactions work */

2014-03-17T15:46:44Z

How the interactions work

← Older revision		Revision as of 15:46, 17 March 2014
Line 8:		Line 8:

	= How the interactions work =		= How the interactions work =
	Each site ~~will have idiosyncratic hardware~~, ~~but~~ a ~~small~~ number of common ~~themes~~ are ~~maintained in the software~~.		Coordination, affiliation and federation of nodes on the worldwide ZINC network are optional, and can operate at several levels
			== Make public cycles available ==
			Each member of the worldwide ZINC network is asked to make a public DOCK Blaster server available, and to allow public jobs to be run. We request 5% or 50 cores, whichever is lower, at least be made available for public use.

			== Forked development code branches ==
			We encourage members of the worldwide ZINC network to participate in code and script development. To do this, get started with [[github]] and fork a branch. Changes made at your site should be commited to your branch for potential re-integration into the germ-line version of the code.

			== Integration of DOCK Blaster job queues ==
			When submitting a docking job to a node on the worldwide ZINC network, the user may select a different cluster in order to get the job processed faster.

			== Integration of ZINC number ==
			If you choose to host a mirror site of ZINC, we ask that you participate in the incremental updates of ZINC, and use a common numbering scheme. If you would like to participate at this level, please write us. At this time, this level of integration is wholly theoretical, but we are keen to see it progress.

	[[Category:Sysadmin]]		[[Category:Sysadmin]]

Frodo: /* Sites / Clusters */

2014-03-17T15:38:48Z

Sites / Clusters

← Older revision		Revision as of 15:38, 17 March 2014
Line 5:		Line 5:
	* [[Cluster 1]] @ [[UofT]]		* [[Cluster 1]] @ [[UofT]]
	* [[Cluster 2]] @ [[UCSF]]		* [[Cluster 2]] @ [[UCSF]]
	* possible clusters in ~~Shenzhen~~, ~~Sao Carlos~~, ~~Marburg, Florida~~.		* possible clusters to follow in China, Brazil, Germany...

	= How the interactions work =		= How the interactions work =

Frodo at 09:03, 13 March 2014

2014-03-13T09:03:38Z

← Older revision		Revision as of 09:03, 13 March 2014
Line 1:		Line 1:
	We ~~have this crazy idea~~ to ~~replicate the lab in different~~ sites around the world. We ~~want~~ to ~~join~~ these sites ~~loosely together to~~ that resources can be pooled, and improvements made at one site can be propagated to other sites ~~easily~~.		We want to foster a community of sites around the world that use our software. We would like to loosely affiliate these sites so that resources can be pooled, and improvements made at one site can be easily propagated to other sites. For this, we have started using [[github \|git and github]] as a revision control and software distribution platform.

	For this, we have started using git as a revision control and ~~beta~~ software distribution platform.

	= Sites / Clusters =		= Sites / Clusters =
Line 7:		Line 5:
	* [[Cluster 1]] @ [[UofT]]		* [[Cluster 1]] @ [[UofT]]
	* [[Cluster 2]] @ [[UCSF]]		* [[Cluster 2]] @ [[UCSF]]
	* possible clusters in Shenzhen, Sao Carlos, Marburg.		* possible clusters in Shenzhen, Sao Carlos, Marburg, Florida.

	= How the interactions work =		= How the interactions work =
	Each site will have ~~ideosyncratic~~ hardware, but a small number of common themes are maintained in the software.		Each site will have idiosyncratic hardware, but a small number of common themes are maintained in the software.

	~~= We use =~~
	* 1. SGE, the free and open verison
	* 2. ( ) as a virtual machine deployment platform.
	* 3. 389 and foreman to manage the network.
	* 4. NFS
	* 5. apache/javascript/psql/python/drupal as a deployment environment.

	[[Category:Sysadmin]]		[[Category:Sysadmin]]