HTCondorWiki: Consumption Policies

 Also of note: because matching with Consumption Policies takes place in the negotiator, accounting of Concurrency Limits is also implicitly handled in the standard manner.
 
 {section: Examples}
+In the preceding discussion, examples of a cpu-centric and a memory-centric Consumption Policy were provided.   A few other examples are listed here.
+
+{subsubsection: Extensible Resources}
+All resource assets are required to have a Consumption Policy configured.  This includes Extensible Resources, if any are also present:
+{code}
+# declare an extensible resource for a claim-based consumption policy
+MACHINE_RESOURCE_tokens = 3
+CONSUMPTION_POLICY = True
+SLOT_TYPE_1 = cpus=5,memory=100,disk=100%,tokens=3
+SLOT_TYPE_1_PARTITIONABLE = True
+NUM_SLOTS_TYPE_1 = 1
+# always consume 1 token, and none of anything else
+SLOT_TYPE_1_CONSUMPTION_TOKENS = 1
+SLOT_TYPE_1_CONSUMPTION_CPUS = 0
+SLOT_TYPE_1_CONSUMPTION_MEMORY = 0
+SLOT_TYPE_1_CONSUMPTION_DISK = 0
+# define cost in terms of available tokens for serving jobs
+SLOT_TYPE_1_SLOT_WEIGHT = Tokens
+{endcode}