Repository: helix
Updated Branches:
  refs/heads/master 39e0d3fb0 -> fc59b1253


http://git-wip-us.apache.org/repos/asf/helix/blob/fc59b125/src/site/markdown/tutorial_rebalance.md
----------------------------------------------------------------------
diff --git a/src/site/markdown/tutorial_rebalance.md 
b/src/site/markdown/tutorial_rebalance.md
deleted file mode 100644
index 1f5930d..0000000
--- a/src/site/markdown/tutorial_rebalance.md
+++ /dev/null
@@ -1,168 +0,0 @@
-<!---
-Licensed to the Apache Software Foundation (ASF) under one
-or more contributor license agreements.  See the NOTICE file
-distributed with this work for additional information
-regarding copyright ownership.  The ASF licenses this file
-to you under the Apache License, Version 2.0 (the
-"License"); you may not use this file except in compliance
-with the License.  You may obtain a copy of the License at
-
-  http://www.apache.org/licenses/LICENSE-2.0
-
-Unless required by applicable law or agreed to in writing,
-software distributed under the License is distributed on an
-"AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
-KIND, either express or implied.  See the License for the
-specific language governing permissions and limitations
-under the License.
--->
-
-# Helix Tutorial: Rebalancing Algorithms
-
-The placement of partitions in a distributed system is essential for the 
reliability and scalability of the system.  For example, when a node fails, it 
is important that the partitions hosted on that node are reallocated evenly 
among the remaining nodes. Consistent hashing is one such algorithm that can 
satisfy this guarantee.  Helix provides a variant of consistent hashing based 
on the RUSH algorithm.
-
-This means given a number of partitions, replicas and number of nodes, Helix 
does the automatic assignment of partition to nodes such that:
-
-* Each node has the same number of partitions
-* Replicas of the same partition do not stay on the same node
-* When a node fails, the partitions will be equally distributed among the 
remaining nodes
-* When new nodes are added, the number of partitions moved will be minimized 
along with satisfying the above criteria
-
-Helix employs a rebalancing algorithm to compute the _ideal state_ of the 
system.  When the _current state_ differs from the _ideal state_, Helix uses it 
as the target state of the system and computes the appropriate transitions 
needed to bring it to the _ideal state_.
-
-Helix makes it easy to perform this operation, while giving you control over 
the algorithm.  In this section, we\'ll see how to implement the desired 
behavior.
-
-Helix has three options for rebalancing, in increasing order of customization 
by the system builder:
-
-* AUTO_REBALANCE
-* AUTO
-* CUSTOM
-
-```
-            |AUTO REBALANCE|   AUTO     |   CUSTOM  |       
-            -----------------------------------------
-   LOCATION | HELIX        |  APP       |  APP      |
-            -----------------------------------------
-      STATE | HELIX        |  HELIX     |  APP      |
-            -----------------------------------------
-```
-
-
-### AUTO_REBALANCE
-
-When the idealstate mode is set to AUTO_REBALANCE, Helix controls both the 
location of the replica along with the state. This option is useful for 
applications where creation of a replica is not expensive. 
-
-For example, consider this system that uses a MasterSlave state model, with 3 
partitions and 2 replicas in the ideal state.
-
-```
-{
-  "id" : "MyResource",
-  "simpleFields" : {
-    "IDEAL_STATE_MODE" : "AUTO_REBALANCE",
-    "NUM_PARTITIONS" : "3",
-    "REPLICAS" : "2",
-    "STATE_MODEL_DEF_REF" : "MasterSlave",
-  }
-  "listFields" : {
-    "MyResource_0" : [],
-    "MyResource_1" : [],
-    "MyResource_2" : []
-  },
-  "mapFields" : {
-  }
-}
-```
-
-If there are 3 nodes in the cluster, then Helix will balance the masters and 
slaves equally.  The ideal state is therefore:
-
-```
-{
-  "id" : "MyResource",
-  "simpleFields" : {
-    "NUM_PARTITIONS" : "3",
-    "REPLICAS" : "2",
-    "STATE_MODEL_DEF_REF" : "MasterSlave",
-  },
-  "mapFields" : {
-    "MyResource_0" : {
-      "N1" : "MASTER",
-      "N2" : "SLAVE",
-    },
-    "MyResource_1" : {
-      "N2" : "MASTER",
-      "N3" : "SLAVE",
-    },
-    "MyResource_2" : {
-      "N3" : "MASTER",
-      "N1" : "SLAVE",
-    }
-  }
-}
-```
-
-Another typical example is evenly distributing a group of tasks among the 
currently healthy processes. For example, if there are 60 tasks and 4 nodes, 
Helix assigns 15 tasks to each node. 
-When one node fails, Helix redistributes its 15 tasks to the remaining 3 
nodes, resulting in a balanced 20 tasks per node. Similarly, if a node is 
added, Helix re-allocates 3 tasks from each of the 4 nodes to the 5th node, 
resulting in a balanced distribution of 12 tasks per node.. 
-
-#### AUTO
-
-When the application needs to control the placement of the replicas, use the 
AUTO idealstate mode.
-
-Example: In the ideal state below, the partition \'MyResource_0\' is 
constrained to be placed only on node1 or node2.  The choice of _state_ is 
still controlled by Helix.  That means MyResource_0.MASTER could be on node1 
and MyResource_0.SLAVE on node2, or vice-versa but neither would be placed on 
node3.
-
-```
-{
-  "id" : "MyResource",
-  "simpleFields" : {
-    "IDEAL_STATE_MODE" : "AUTO",
-    "NUM_PARTITIONS" : "3",
-    "REPLICAS" : "2",
-    "STATE_MODEL_DEF_REF" : "MasterSlave",
-  }
-  "listFields" : {
-    "MyResource_0" : [node1, node2],
-    "MyResource_1" : [node2, node3],
-    "MyResource_2" : [node3, node1]
-  },
-  "mapFields" : {
-  }
-}
-```
-
-The MasterSlave state model requires that a partition has exactly one MASTER 
at all times, and the other replicas should be SLAVEs.  In this simple example 
with 2 replicas per partition, there would be one MASTER and one SLAVE.  Upon 
failover, a SLAVE has to assume mastership, and a new SLAVE will be generated.
-
-In this mode when node1 fails, unlike in AUTO-REBALANCE mode the partition is 
_not_ moved from node1 to node3. Instead, Helix will decide to change the state 
of MyResource_0 on node2 from SLAVE to MASTER, based on the system constraints. 
-
-#### CUSTOM
-
-Finally, Helix offers a third mode called CUSTOM, in which the application 
controls the placement _and_ state of each replica. The application needs to 
implement a callback interface that Helix invokes when the cluster state 
changes. 
-Within this callback, the application can recompute the idealstate. Helix will 
then issue appropriate transitions such that _Idealstate_ and _Currentstate_ 
converges.
-
-Here\'s an example, again with 3 partitions, 2 replicas per partition, and the 
MasterSlave state model:
-
-```
-{
-  "id" : "MyResource",
-  "simpleFields" : {
-      "IDEAL_STATE_MODE" : "CUSTOM",
-    "NUM_PARTITIONS" : "3",
-    "REPLICAS" : "2",
-    "STATE_MODEL_DEF_REF" : "MasterSlave",
-  },
-  "mapFields" : {
-    "MyResource_0" : {
-      "N1" : "MASTER",
-      "N2" : "SLAVE",
-    },
-    "MyResource_1" : {
-      "N2" : "MASTER",
-      "N3" : "SLAVE",
-    },
-    "MyResource_2" : {
-      "N3" : "MASTER",
-      "N1" : "SLAVE",
-    }
-  }
-}
-```
-
-Suppose the current state of the system is 'MyResource_0' -> {N1:MASTER, 
N2:SLAVE} and the application changes the ideal state to 'MyResource_0' -> 
{N1:SLAVE,N2:MASTER}. While the application decides which node is MASTER and 
which is SLAVE, Helix will not blindly issue MASTER-->SLAVE to N1 and 
SLAVE-->MASTER to N2 in parallel, since that might result in a transient state 
where both N1 and N2 are masters, which violates the MasterSlave constraint 
that there is exactly one MASTER at a time.  Helix will first issue 
MASTER-->SLAVE to N1 and after it is completed, it will issue SLAVE-->MASTER to 
N2. 

http://git-wip-us.apache.org/repos/asf/helix/blob/fc59b125/src/site/markdown/tutorial_spectator.md
----------------------------------------------------------------------
diff --git a/src/site/markdown/tutorial_spectator.md 
b/src/site/markdown/tutorial_spectator.md
deleted file mode 100644
index a5b9a0e..0000000
--- a/src/site/markdown/tutorial_spectator.md
+++ /dev/null
@@ -1,72 +0,0 @@
-<!---
-Licensed to the Apache Software Foundation (ASF) under one
-or more contributor license agreements.  See the NOTICE file
-distributed with this work for additional information
-regarding copyright ownership.  The ASF licenses this file
-to you under the Apache License, Version 2.0 (the
-"License"); you may not use this file except in compliance
-with the License.  You may obtain a copy of the License at
-
-  http://www.apache.org/licenses/LICENSE-2.0
-
-Unless required by applicable law or agreed to in writing,
-software distributed under the License is distributed on an
-"AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
-KIND, either express or implied.  See the License for the
-specific language governing permissions and limitations
-under the License.
--->
-
-# Helix Tutorial: Spectator
-
-Next, we\'ll learn how to implement a SPECTATOR.  Typically, a spectator needs 
to react to changes within the distributed system.  Examples: a client that 
needs to know where to send a request, a topic consumer in a consumer group.  
The spectator is automatically informed of changes in the _external state_ of 
the cluster, but it does not have to add any code to keep track of other 
components in the system.
-
-### Start the Helix agent
-
-Same as for a PARTICIPANT, The Helix agent is the common component that 
connects each system component with the controller.
-
-It requires the following parameters:
-
-* clusterName: A logical name to represent the group of nodes
-* instanceName: A logical name of the process creating the manager instance. 
Generally this is host:port.
-* instanceType: Type of the process. This can be one of the following types, 
in this case, use SPECTATOR:
-    * CONTROLLER: Process that controls the cluster, any number of controllers 
can be started but only one will be active at any given time.
-    * PARTICIPANT: Process that performs the actual task in the distributed 
system.
-    * SPECTATOR: Process that observes the changes in the cluster.
-    * ADMIN: To carry out system admin actions.
-* zkConnectString: Connection string to Zookeeper. This is of the form 
host1:port1,host2:port2,host3:port3.
-
-After the Helix manager instance is created, only thing that needs to be 
registered is the listener.  When the ExternalView changes, the listener is 
notified.
-
-### Spectator Code
-
-A spectator observes the cluster and is notified when the state of the system 
changes. Helix consolidates the state of entire cluster in one Znode called 
ExternalView.
-Helix provides a default implementation RoutingTableProvider that caches the 
cluster state and updates it when there is a change in the cluster.
-
-```
-manager = HelixManagerFactory.getZKHelixManager(clusterName,
-                                                          instanceName,
-                                                          
InstanceType.PARTICIPANT,
-                                                          zkConnectString);
-manager.connect();
-RoutingTableProvider routingTableProvider = new RoutingTableProvider();
-manager.addExternalViewChangeListener(routingTableProvider);
-```
-
-In the following code snippet, the application sends the request to a valid 
instance by interrogating the external view.  Suppose the desired resource for 
this request is in the partition myDB_1.
-
-```
-## instances = routingTableProvider.getInstances(, "PARTITION_NAME", 
"PARTITION_STATE");
-instances = routingTableProvider.getInstances("myDB", "myDB_1", "ONLINE");
-
-////////////////////////////////////////////////////////////////////////////////////////////////
-// Application-specific code to send a request to one of the instances         
               //
-////////////////////////////////////////////////////////////////////////////////////////////////
-
-theInstance = instances.get(0);  // should choose an instance and throw an 
exception if none are available
-result = theInstance.sendRequest(yourApplicationRequest, responseObject);
-
-```
-
-When the external view changes, the application needs to react by sending 
requests to a different instance.  
-

http://git-wip-us.apache.org/repos/asf/helix/blob/fc59b125/src/site/markdown/tutorial_state.md
----------------------------------------------------------------------
diff --git a/src/site/markdown/tutorial_state.md 
b/src/site/markdown/tutorial_state.md
deleted file mode 100644
index e9a79d3..0000000
--- a/src/site/markdown/tutorial_state.md
+++ /dev/null
@@ -1,127 +0,0 @@
-<!---
-Licensed to the Apache Software Foundation (ASF) under one
-or more contributor license agreements.  See the NOTICE file
-distributed with this work for additional information
-regarding copyright ownership.  The ASF licenses this file
-to you under the Apache License, Version 2.0 (the
-"License"); you may not use this file except in compliance
-with the License.  You may obtain a copy of the License at
-
-  http://www.apache.org/licenses/LICENSE-2.0
-
-Unless required by applicable law or agreed to in writing,
-software distributed under the License is distributed on an
-"AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
-KIND, either express or implied.  See the License for the
-specific language governing permissions and limitations
-under the License.
--->
-
-# Helix Tutorial: State Machine Configuration
-
-In this chapter, we\'ll learn about the state models provided by Helix, and 
how to create your own custom state model.
-
-## State Models
-
-Helix comes with 3 default state models that are commonly used.  It is 
possible to have multiple state models in a cluster. 
-Every resource that is added should be configured to use a state model that 
govern its _ideal state_.
-
-### MASTER-SLAVE
-
-* 3 states: OFFLINE, SLAVE, MASTER
-* Maximum number of masters: 1
-* Slaves are based on the replication factor. The replication factor can be 
specified while adding the resource.
-
-
-### ONLINE-OFFLINE
-
-* Has 2 states: OFFLINE and ONLINE.  This simple state model is a good 
starting point for most applications.
-
-### LEADER-STANDBY
-
-* 1 Leader and multiple stand-bys.  The idea is that exactly one leader 
accomplishes a designated task, the stand-bys are ready to take over if the 
leader fails.
-
-## Constraints
-
-In addition to the state machine configuration, one can specify the 
constraints of states and transitions.
-
-For example, one can say:
-
-* MASTER:1
-<br/>Maximum number of replicas in MASTER state at any time is 1
-
-* OFFLINE-SLAVE:5 
-<br/>Maximum number of OFFLINE-SLAVE transitions that can happen concurrently 
in the system is 5 in this example.
-
-### Dynamic State Constraints
-
-We also support two dynamic upper bounds for the number of replicas in each 
state:
-
-* N: The number of replicas in the state is at most the number of live 
participants in the cluster
-* R: The number of replicas in the state is at most the specified replica 
count for the partition
-
-### State Priority
-
-Helix uses a greedy approach to satisfy the state constraints. For example, if 
the state machine configuration says it needs 1 MASTER and 2 SLAVES, but only 1 
node is active, Helix must promote it to MASTER. This behavior is achieved by 
providing the state priority list as \[MASTER, SLAVE\].
-
-### State Transition Priority
-
-Helix tries to fire as many transitions as possible in parallel to reach the 
stable state without violating constraints. By default, Helix simply sorts the 
transitions alphabetically and fires as many as it can without violating the 
constraints. You can control this by overriding the priority order.
-
-## Special States
-
-### DROPPED
-
-The DROPPED state is used to signify a replica that was served by a given 
participant, but is no longer served. This allows Helix and its participants to 
effectively clean up. There are two requirements that every new state model 
should follow with respect to the DROPPED state:
-
-* The DROPPED state must be defined
-* There must be a path to DROPPED for every state in the model
-
-### ERROR
-
-The ERROR state is used whenever the participant serving a partition 
encountered an error and cannot continue to serve the partition. HelixAdmin has 
\"reset\" functionality to allow for participants to recover from the ERROR 
state.
-
-## Annotated Example
-
-Below is a complete definition of a Master-Slave state model. Notice the 
fields marked REQUIRED; these are essential for any state model definition.
-
-```
-StateModelDefinition stateModel = new 
StateModelDefinition.Builder("MasterSlave")
-  // OFFLINE is the state that the system starts in (initial state is REQUIRED)
-  .initialState("OFFLINE")
-
-  // Lowest number here indicates highest priority, no value indicates lowest 
priority
-  .addState("MASTER", 1)
-  .addState("SLAVE", 2)
-  .addState("OFFLINE")
-
-  // Note the special inclusion of the DROPPED state (REQUIRED)
-  .addState(HelixDefinedState.DROPPED.toString())
-
-  // No more than one master allowed
-  .upperBound("MASTER", 1)
-
-  // R indicates an upper bound of number of replicas for each partition
-  .dynamicUpperBound("SLAVE", "R")
-
-  // Add some high-priority transitions
-  .addTransition("SLAVE", "MASTER", 1)
-  .addTransition("OFFLINE", "SLAVE", 2)
-
-  // Using the same priority value indicates that these transitions can fire 
in any order
-  .addTransition("MASTER", "SLAVE", 3)
-  .addTransition("SLAVE", "OFFLINE", 3)
-
-  // Not specifying a value defaults to lowest priority
-  // Notice the inclusion of the OFFLINE to DROPPED transition
-  // Since every state has a path to OFFLINE, they each now have a path to 
DROPPED (REQUIRED)
-  .addTransition("OFFLINE", HelixDefinedState.DROPPED.toString())
-
-  // Create the StateModelDefinition instance
-  .build();
-
-  // Use the isValid() function to make sure the StateModelDefinition will 
work without issues
-  Assert.assertTrue(stateModel.isValid());
-```
-
-

http://git-wip-us.apache.org/repos/asf/helix/blob/fc59b125/src/site/markdown/tutorial_throttling.md
----------------------------------------------------------------------
diff --git a/src/site/markdown/tutorial_throttling.md 
b/src/site/markdown/tutorial_throttling.md
deleted file mode 100644
index 5002156..0000000
--- a/src/site/markdown/tutorial_throttling.md
+++ /dev/null
@@ -1,34 +0,0 @@
-<!---
-Licensed to the Apache Software Foundation (ASF) under one
-or more contributor license agreements.  See the NOTICE file
-distributed with this work for additional information
-regarding copyright ownership.  The ASF licenses this file
-to you under the Apache License, Version 2.0 (the
-"License"); you may not use this file except in compliance
-with the License.  You may obtain a copy of the License at
-
-  http://www.apache.org/licenses/LICENSE-2.0
-
-Unless required by applicable law or agreed to in writing,
-software distributed under the License is distributed on an
-"AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
-KIND, either express or implied.  See the License for the
-specific language governing permissions and limitations
-under the License.
--->
-
-# Helix Tutorial: Throttling
-
-In this chapter, we\'ll learn how to control the parallel execution of cluster 
tasks.  Only a centralized cluster manager with global knowledge is capable of 
coordinating this decision.
-
-### Throttling
-
-Since all state changes in the system are triggered through transitions, Helix 
can control the number of transitions that can happen in parallel. Some of the 
transitions may be light weight, but some might involve moving data, which is 
quite expensive from a network and iops perspective.
-
-Helix allows applications to set a threshold on transitions. The threshold can 
be set at multiple scopes:
-
-* MessageType e.g STATE_TRANSITION
-* TransitionType e.g SLAVE-MASTER
-* Resource e.g database
-* Node i.e per-node maximum transitions in parallel
-

http://git-wip-us.apache.org/repos/asf/helix/blob/fc59b125/src/site/resources/.htaccess
----------------------------------------------------------------------
diff --git a/src/site/resources/.htaccess b/src/site/resources/.htaccess
deleted file mode 100644
index d5c7bf3..0000000
--- a/src/site/resources/.htaccess
+++ /dev/null
@@ -1,20 +0,0 @@
-#
-# Licensed to the Apache Software Foundation (ASF) under one
-# or more contributor license agreements.  See the NOTICE file
-# distributed with this work for additional information
-# regarding copyright ownership.  The ASF licenses this file
-# to you under the Apache License, Version 2.0 (the
-# "License"); you may not use this file except in compliance
-# with the License.  You may obtain a copy of the License at
-#
-#   http://www.apache.org/licenses/LICENSE-2.0
-#
-# Unless required by applicable law or agreed to in writing,
-# software distributed under the License is distributed on an
-# "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
-# KIND, either express or implied.  See the License for the
-# specific language governing permissions and limitations
-# under the License.
-#
-
-Redirect /download.html /download.cgi

http://git-wip-us.apache.org/repos/asf/helix/blob/fc59b125/src/site/resources/download.cgi
----------------------------------------------------------------------
diff --git a/src/site/resources/download.cgi b/src/site/resources/download.cgi
deleted file mode 100644
index f9a0e30..0000000
--- a/src/site/resources/download.cgi
+++ /dev/null
@@ -1,22 +0,0 @@
-#!/bin/sh
-# Just call the standard mirrors.cgi script. It will use download.html
-# as the input template.
-#
-# Licensed to the Apache Software Foundation (ASF) under one
-# or more contributor license agreements.  See the NOTICE file
-# distributed with this work for additional information
-# regarding copyright ownership.  The ASF licenses this file
-# to you under the Apache License, Version 2.0 (the
-# "License"); you may not use this file except in compliance
-# with the License.  You may obtain a copy of the License at
-#
-#   http://www.apache.org/licenses/LICENSE-2.0
-#
-# Unless required by applicable law or agreed to in writing,
-# software distributed under the License is distributed on an
-# "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
-# KIND, either express or implied.  See the License for the
-# specific language governing permissions and limitations
-# under the License.
-#
-exec /www/www.apache.org/dyn/mirrors/mirrors.cgi $*

http://git-wip-us.apache.org/repos/asf/helix/blob/fc59b125/src/site/resources/images/HELIX-components.png
----------------------------------------------------------------------
diff --git a/src/site/resources/images/HELIX-components.png 
b/src/site/resources/images/HELIX-components.png
deleted file mode 100644
index c0c35ae..0000000
Binary files a/src/site/resources/images/HELIX-components.png and /dev/null 
differ

http://git-wip-us.apache.org/repos/asf/helix/blob/fc59b125/src/site/resources/images/PFS-Generic.png
----------------------------------------------------------------------
diff --git a/src/site/resources/images/PFS-Generic.png 
b/src/site/resources/images/PFS-Generic.png
deleted file mode 100644
index 7eea3a0..0000000
Binary files a/src/site/resources/images/PFS-Generic.png and /dev/null differ

http://git-wip-us.apache.org/repos/asf/helix/blob/fc59b125/src/site/resources/images/RSYNC_BASED_PFS.png
----------------------------------------------------------------------
diff --git a/src/site/resources/images/RSYNC_BASED_PFS.png 
b/src/site/resources/images/RSYNC_BASED_PFS.png
deleted file mode 100644
index 0cc55ae..0000000
Binary files a/src/site/resources/images/RSYNC_BASED_PFS.png and /dev/null 
differ

http://git-wip-us.apache.org/repos/asf/helix/blob/fc59b125/src/site/resources/images/bootstrap_statemodel.gif
----------------------------------------------------------------------
diff --git a/src/site/resources/images/bootstrap_statemodel.gif 
b/src/site/resources/images/bootstrap_statemodel.gif
deleted file mode 100644
index b8f8a42..0000000
Binary files a/src/site/resources/images/bootstrap_statemodel.gif and /dev/null 
differ

http://git-wip-us.apache.org/repos/asf/helix/blob/fc59b125/src/site/resources/images/helix-architecture.png
----------------------------------------------------------------------
diff --git a/src/site/resources/images/helix-architecture.png 
b/src/site/resources/images/helix-architecture.png
deleted file mode 100644
index 6f69a2d..0000000
Binary files a/src/site/resources/images/helix-architecture.png and /dev/null 
differ

http://git-wip-us.apache.org/repos/asf/helix/blob/fc59b125/src/site/resources/images/helix-logo.jpg
----------------------------------------------------------------------
diff --git a/src/site/resources/images/helix-logo.jpg 
b/src/site/resources/images/helix-logo.jpg
deleted file mode 100644
index d6428f6..0000000
Binary files a/src/site/resources/images/helix-logo.jpg and /dev/null differ

http://git-wip-us.apache.org/repos/asf/helix/blob/fc59b125/src/site/resources/images/helix-znode-layout.png
----------------------------------------------------------------------
diff --git a/src/site/resources/images/helix-znode-layout.png 
b/src/site/resources/images/helix-znode-layout.png
deleted file mode 100644
index 5bafc45..0000000
Binary files a/src/site/resources/images/helix-znode-layout.png and /dev/null 
differ

http://git-wip-us.apache.org/repos/asf/helix/blob/fc59b125/src/site/resources/images/statemachine.png
----------------------------------------------------------------------
diff --git a/src/site/resources/images/statemachine.png 
b/src/site/resources/images/statemachine.png
deleted file mode 100644
index 43d27ec..0000000
Binary files a/src/site/resources/images/statemachine.png and /dev/null differ

http://git-wip-us.apache.org/repos/asf/helix/blob/fc59b125/src/site/resources/images/system.png
----------------------------------------------------------------------
diff --git a/src/site/resources/images/system.png 
b/src/site/resources/images/system.png
deleted file mode 100644
index f8a05c8..0000000
Binary files a/src/site/resources/images/system.png and /dev/null differ

http://git-wip-us.apache.org/repos/asf/helix/blob/fc59b125/src/site/site.xml
----------------------------------------------------------------------
diff --git a/src/site/site.xml b/src/site/site.xml
deleted file mode 100644
index e44a43e..0000000
--- a/src/site/site.xml
+++ /dev/null
@@ -1,122 +0,0 @@
-<?xml version="1.0" encoding="ISO-8859-1"?>
-<!--
-  Licensed to the Apache Software Foundation (ASF) under one or more
-  contributor license agreements.  See the NOTICE file distributed with
-  this work for additional information regarding copyright ownership.
-  The ASF licenses this file to You under the Apache License, Version 2.0
-  (the "License"); you may not use this file except in compliance with
-  the License.  You may obtain a copy of the License at
-
-      http://www.apache.org/licenses/LICENSE-2.0
-
-  Unless required by applicable law or agreed to in writing, software
-  distributed under the License is distributed on an "AS IS" BASIS,
-  WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
-  See the License for the specific language governing permissions and
-  limitations under the License.
--->
-<project name="Apache Helix">
-  <bannerLeft>
-    <src>images/helix-logo.jpg</src>
-    <href>http://helix.incubator.apache.org/</href>
-  </bannerLeft>
-  <bannerRight>
-    <src>http://incubator.apache.org/images/egg-logo.png</src>
-    <href>http://incubator.apache.org/</href>
-  </bannerRight>
-
-  <publishDate position="right"/>
-
-  <skin>
-    <groupId>org.apache.maven.skins</groupId>
-    <artifactId>maven-fluido-skin</artifactId>
-    <version>1.3.0</version>
-  </skin>
-
-  <body>
-
-    <head>
-      <script type="text/javascript">
-
-        var _gaq = _gaq || [];
-        _gaq.push(['_setAccount', 'UA-3211522-12']);
-        _gaq.push(['_trackPageview']);
-
-        (function() {
-        var ga = document.createElement('script'); ga.type = 
'text/javascript'; ga.async = true;
-        ga.src = ('https:' == document.location.protocol ? 'https://ssl' : 
'http://www') + '.google-analytics.com/ga.js';
-        var s = document.getElementsByTagName('script')[0]; 
s.parentNode.insertBefore(ga, s);
-        })();
-
-      </script>
-
-    </head>
-
-    <breadcrumbs position="left">
-      <item name="Apache Helix" href="http://helix.incubator.apache.org/"/>
-    </breadcrumbs>
-
-    <menu name="Helix">
-      <item name="Introduction" href="./index.html"/>
-      <item name="Core concepts" href="./Concepts.html"/>
-      <item name="Architecture" href="./Architecture.html"/>
-      <item name="Quick Start" href="./Quickstart.html"/>
-      <item name="Tutorial" href="./Tutorial.html"/>
-      <item name="release ${currentRelease}" 
href="releasenotes/release-${currentRelease}.html"/>
-      <item name="Download" href="./download.html"/>
-    </menu>
-    
-    <menu name="Recipes">  
-      <item name="Distributed lock manager" 
href="./recipes/lock_manager.html"/>
-      <item name="Rabbit MQ consumer group" 
href="./recipes/rabbitmq_consumer_group.html"/>
-      <item name="Rsync replicated file store" 
href="./recipes/rsync_replicated_file_store.html"/>
-      <item name="Service Discovery" href="./recipes/service_discovery.html"/>
-      <item name="Distributed task DAG Execution" 
href="./recipes/task_dag_execution.html"/>
-    </menu>
-
-    <menu name="Get Involved">
-      <item name="Mailing Lists" href="mail-lists.html"/>
-      <item name="Issues" href="issue-tracking.html"/>
-      <item name="Team" href="team-list.html"/>
-      <item name="Sources" href="source-repository.html"/>
-      <item name="Continuous Integration" href="integration.html"/>
-      <item name="Building Guide" href="/involved/building.html"/>
-      <item name="Release Guide" href="/releasing.html"/>
-    </menu>
-<!--
-    <menu ref="reports" inherit="bottom"/>
-    <menu ref="modules" inherit="bottom"/>
-
-
-    <menu name="ASF">
-      <item name="How Apache Works" 
href="http://www.apache.org/foundation/how-it-works.html"/>
-      <item name="Foundation" href="http://www.apache.org/foundation/"/>
-      <item name="Sponsoring Apache" 
href="http://www.apache.org/foundation/sponsorship.html"/>
-      <item name="Thanks" href="http://www.apache.org/foundation/thanks.html"/>
-    </menu>
--->
-    <footer>
-      <div class="row span16"><div>Apache Helix, Apache, the Apache feather 
logo, and the Apache Helix project logos are trademarks of The Apache Software 
Foundation.
-        All other marks mentioned may be trademarks or registered trademarks 
of their respective owners.</div>
-        <a href="${project.url}/privacy-policy.html">Privacy Policy</a>
-      </div>
-    </footer>
-
-
-  </body>
-
-  <custom>
-    <fluidoSkin>
-      <topBarEnabled>true</topBarEnabled>
-      <!-- twitter link work only with sidebar disabled -->
-      <sideBarEnabled>false</sideBarEnabled>
-      <googleSearch></googleSearch>
-      <twitter>
-        <user>ApacheHelix</user>
-        <showUser>true</showUser>
-        <showFollowers>false</showFollowers>
-      </twitter>
-    </fluidoSkin>
-  </custom>
-
-</project>

http://git-wip-us.apache.org/repos/asf/helix/blob/fc59b125/src/site/xdoc/download.xml.vm
----------------------------------------------------------------------
diff --git a/src/site/xdoc/download.xml.vm b/src/site/xdoc/download.xml.vm
deleted file mode 100644
index d8f2c8e..0000000
--- a/src/site/xdoc/download.xml.vm
+++ /dev/null
@@ -1,191 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<!--
-Licensed to the Apache Software Foundation (ASF) under one
-or more contributor license agreements.  See the NOTICE file
-distributed with this work for additional information
-regarding copyright ownership.  The ASF licenses this file
-to you under the Apache License, Version 2.0 (the
-"License"); you may not use this file except in compliance
-with the License.  You may obtain a copy of the License at
-
-  http://www.apache.org/licenses/LICENSE-2.0
-
-Unless required by applicable law or agreed to in writing,
-software distributed under the License is distributed on an
-"AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
-KIND, either express or implied.  See the License for the
-specific language governing permissions and limitations
-under the License.
-
--->
-<document xmlns="http://maven.apache.org/XDOC/2.0"; 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
-          xsi:schemaLocation="http://maven.apache.org/XDOC/2.0 
http://maven.apache.org/xsd/xdoc-2.0.xsd";>
-
-  <properties>
-    <title>Apache Incubator Helix Downloads</title>
-    <author email="[email protected]">Apache Helix Documentation 
Team</author>
-  </properties>
-
-  <body>
-    <div class="toc_container">
-      <macro name="toc">
-        <param name="class" value="toc"/>
-      </macro>
-    </div>
-    
-    <section name="Introduction">
-      <p>Apache Helix artifacts are distributed in source and binary form 
under the terms of the
-        <a href="http://www.apache.org/licenses/LICENSE-2.0";>Apache License, 
Version 2.0</a>.
-        See the included <tt>LICENSE</tt> and <tt>NOTICE</tt> files included 
in each artifact for additional license 
-        information.
-      </p>
-      <p>Use the links below to download a source distribution of Apache Helix.
-      It is good practice to <a href="#Verifying_Releases">verify the 
integrity</a> of the distribution files.</p>
-    </section>
-
-    <section name="Current Release">
-      <p>Release date: 05/29/2013 </p>
-      <p><a 
href="releasenotes/release-${currentRelease}.html">${currentRelease} Release 
notes</a></p>
-      <a name="mirror"/>
-      <subsection name="Mirror">
-
-        <p>
-          [if-any logo]
-          <a href="[link]">
-            <img align="right" src="[logo]" border="0"
-                 alt="logo"/>
-          </a>
-          [end]
-          The currently selected mirror is
-          <b>[preferred]</b>.
-          If you encounter a problem with this mirror,
-          please select another mirror.
-          If all mirrors are failing, there are
-          <i>backup</i>
-          mirrors
-          (at the end of the mirrors list) that should be available.
-        </p>
-
-        <form action="[location]" method="get" id="SelectMirror" 
class="form-inline">
-          Other mirrors:
-          <select name="Preferred" class="input-xlarge">
-            [if-any http]
-            [for http]
-            <option value="[http]">[http]</option>
-            [end]
-            [end]
-            [if-any ftp]
-            [for ftp]
-            <option value="[ftp]">[ftp]</option>
-            [end]
-            [end]
-            [if-any backup]
-            [for backup]
-            <option value="[backup]">[backup] (backup)</option>
-            [end]
-            [end]
-          </select>
-          <input type="submit" value="Change" class="btn"/>
-        </form>
-
-        <p>
-          You may also consult the
-          <a href="http://www.apache.org/mirrors/";>complete list of 
mirrors.</a>
-        </p>
-
-      </subsection>
-      <subsection name="${currentRelease} Sources">
-        <table>
-          <thead>
-            <tr>
-              <th>Artifact</th>
-              <th>Signatures</th>
-            </tr>
-          </thead>
-          <tbody>
-            <tr>
-              <td>
-                <a 
href="[preferred]incubator/helix/${currentRelease}/src/helix-${currentRelease}-src.zip">helix-${currentRelease}-src.zip</a>
-              </td>
-              <td>
-                <a 
href="http://www.apache.org/dist/incubator/helix/${currentRelease}/src/helix-${currentRelease}-src.zip.asc";>asc</a>
-                <a 
href="http://www.apache.org/dist/incubator/helix/${currentRelease}/src/helix-${currentRelease}-src.zip.md5";>md5</a>
-                <a 
href="http://www.apache.org/dist/incubator/helix/${currentRelease}/src/helix-${currentRelease}-src.zip.zip.sha1";>sha1</a>
-              </td>
-            </tr>
-          </tbody>
-        </table>
-      </subsection>
-      <subsection name="${currentRelease} Binaries">
-        <table>
-          <thead>
-            <tr>
-              <th>Artifact</th>
-              <th>Signatures</th>
-            </tr>
-          </thead>
-          <tbody>
-            <tr>
-              <td>
-                <a 
href="[preferred]incubator/helix/${currentRelease}/binaries/helix-core-${currentRelease}-pkg.tar">helix-core-${currentRelease}-pkg.tar</a>
-              </td>
-              <td>
-                <a 
href="http://www.apache.org/dist/incubator/helix/${currentRelease}/binaries/helix-core-${currentRelease}-pkg.tar.asc";>asc</a>
-                <a 
href="http://www.apache.org/dist/incubator/helix/${currentRelease}/binaries/helix-core-${currentRelease}-pkg.tar.md5";>md5</a>
-                <a 
href="http://www.apache.org/dist/incubator/helix/${currentRelease}/binaries/helix-core-${currentRelease}-pkg.tar.sha1";>sha1</a>
-              </td>
-            </tr>
-            <tr>
-              <td>
-                <a 
href="[preferred]incubator/helix/${currentRelease}/binaries/helix-admin-webapp-${currentRelease}-pkg.tar">helix-admin-webapp-${currentRelease}-pkg.tar</a>
-              </td>
-              <td>
-                <a 
href="http://www.apache.org/dist/incubator/helix/${currentRelease}/binaries/helix-admin-webapp-${currentRelease}-pkg.tar.asc";>asc</a>
-                <a 
href="http://www.apache.org/dist/incubator/helix/${currentRelease}/binaries/helix-admin-webapp-${currentRelease}-pkg.tar.md5";>md5</a>
-                <a 
href="http://www.apache.org/dist/incubator/helix/${currentRelease}/binaries/helix-admin-webapp-${currentRelease}-pkg.tar.sha1";>sha1</a>
-              </td>
-            </tr>
-          </tbody>
-        </table>
-      </subsection>
-    </section>
-
-<!--    <section name="Older Releases">
-    </section>-->
-
-    <section name="Verifying Releases">
-      <p>We strongly recommend you verify the integrity of the downloaded 
files with both PGP and MD5.</p>
-      
-      <p>The PGP signatures can be verified using <a 
href="http://www.pgpi.org/";>PGP</a> or 
-      <a href="http://www.gnupg.org/";>GPG</a>. 
-      First download the <a 
href="http://www.apache.org/dist/incubator/helix/KEYS";>KEYS</a> as well as the
-      <tt>*.asc</tt> signature file for the particular distribution. Make sure 
you get these files from the main 
-      distribution directory, rather than from a mirror. Then verify the 
signatures using one of the following sets of
-      commands:
-
-        <source>$ pgp -ka KEYS
-$ pgp helix-*.zip.asc</source>
-      
-        <source>$ gpg --import KEYS
-$ gpg --verify helix-*.zip.asc</source>
-       </p>
-    <p>Alternatively, you can verify the MD5 signature on the files. A 
Unix/Linux program called  
-      <code>md5</code> or 
-      <code>md5sum</code> is included in most distributions.  It is also 
available as part of
-      <a href="http://www.gnu.org/software/textutils/textutils.html";>GNU 
Textutils</a>.
-      Windows users can get binary md5 programs from these (and likely other) 
places:
-      <ul>
-        <li>
-          <a href="http://www.md5summer.org/";>http://www.md5summer.org/</a>
-        </li>
-        <li>
-          <a 
href="http://www.fourmilab.ch/md5/";>http://www.fourmilab.ch/md5/</a>
-        </li>
-        <li>
-          <a 
href="http://www.pc-tools.net/win32/md5sums/";>http://www.pc-tools.net/win32/md5sums/</a>
-        </li>
-      </ul>
-    </p>
-    </section>
-  </body>
-</document>

Reply via email to