Author: stevel
Date: Mon Feb 2 16:29:51 2015
New Revision: 1656512
URL: http://svn.apache.org/r1656512
Log:
updating site docs
Modified:
incubator/slider/site/trunk/content/design/rolehistory.md
incubator/slider/site/trunk/content/developing/releasing.md
incubator/slider/site/trunk/content/release_notes/release-0.70.0.md
Modified: incubator/slider/site/trunk/content/design/rolehistory.md
URL:
http://svn.apache.org/viewvc/incubator/slider/site/trunk/content/design/rolehistory.md?rev=1656512&r1=1656511&r2=1656512&view=diff
==============================================================================
--- incubator/slider/site/trunk/content/design/rolehistory.md (original)
+++ incubator/slider/site/trunk/content/design/rolehistory.md Mon Feb 2
16:29:51 2015
@@ -447,7 +447,7 @@ then re-requesting containers on it will
### Bootstrap
-1Persistent Role History file not found; empty data structures created.
+Persistent Role History file not found; empty data structures created.
### Restart
@@ -473,9 +473,8 @@ after the last save is unknown.
2: Future: if role list enum != current enum, remapping could take place.
Until then: fail.
3: Mark all nodes as active at save time to that of the
- //define a threshold
- threshold = rolehistory.saveTime - 7*24*60*60* 1000
-
+ //define a threshold
+ threshold = rolehistory.saveTime - 7*24*60*60* 1000
for (clusterId, clusternode) in rolehistory.clusterNodes().entries() :
for (role, nodeEntry) in clusterNode.getNodeEntries():
Modified: incubator/slider/site/trunk/content/developing/releasing.md
URL:
http://svn.apache.org/viewvc/incubator/slider/site/trunk/content/developing/releasing.md?rev=1656512&r1=1656511&r2=1656512&view=diff
==============================================================================
--- incubator/slider/site/trunk/content/developing/releasing.md (original)
+++ incubator/slider/site/trunk/content/developing/releasing.md Mon Feb 2
16:29:51 2015
@@ -572,23 +572,10 @@ Sample:
-### Push the release to origin/master âTODO
-
-
-** TODO **
-
-Goal: get the master branch updated with this release, with any changes in the
release taking priority over the versions in /master.
-
-This is where gitflow breaks down. It may be better to have tags like
`latest_stable` and `latest_development` and just move them along.
-
-Otherwise:
-In the branch for the release, go to the tag create for the release by maven.
This represents the code released, including the version numbering of the
release artifact (not the HEAD of the branch, which has the incremented one)
-
- git tag -a $SLIDER_RELEASE -m 'Slider $SLIDER_RELEASE' $RELEASE_TAG
- git push origin $SLIDER_RELEASE
- git checkout master
- git merge branch -X $SLIDER_RELEASE
+## Update the site
+Update documentation in the svn site repo, then
+[trigger a site rebuild](https://cms.apache.org/slider/publish).
## Finish the JIRA
Modified: incubator/slider/site/trunk/content/release_notes/release-0.70.0.md
URL:
http://svn.apache.org/viewvc/incubator/slider/site/trunk/content/release_notes/release-0.70.0.md?rev=1656512&r1=1656511&r2=1656512&view=diff
==============================================================================
--- incubator/slider/site/trunk/content/release_notes/release-0.70.0.md
(original)
+++ incubator/slider/site/trunk/content/release_notes/release-0.70.0.md Mon Feb
2 16:29:51 2015
@@ -40,7 +40,13 @@ functional.
This is intended to be a full two-way REST API offered by the Slider
Application
Master to clients. The draft design is [available on the Slider web
site](http://slider.incubator.apache.org/docs/api).
-The 0.70 release contains the initial read-only view of this API. It is
impossible
+The 0.70 release contains the foundational read-only view of this API.
+Look at the code in `org.apache.slider.client.rest`, in particular
+the API client, `SliderApplicationAPI`, and `RestClientFactory` âwhich
+builds an instance of `SliderApplicationAPI` bonded to an application located
+in the Zookeeper-based YARN registry.
+
+It is impossible
to offer a secure two-way REST API in Hadoop 2.6, due to how authentication and
security is implemented in the YARN Resource Manager proxy. Therefore even
though a two-way API is partially implemented in the slider code, it is
explicitly
@@ -48,7 +54,8 @@ read only. To enable it, set the propert
the Slider Application Master. This can be done by setting it in the file
`$SLIDER_CONF_DIR/slider-server.xml`.
-*warning* : once set, anyone on the cluster can
+*warning* : once set, anyone on the cluster can issue side-effecting operations
+against the cluster, such as the `stop` operation.
To complement the application master, a new class
`org.apache.slider.client.rest.SliderApplicationAPI` is being developed to
