[22/50] [abbrv] incubator-geode git commit: GEODE-2094 Update admin/dev REST API documentation

2016-11-15 Thread klund 
GEODE-2094 Update admin/dev REST API documentation

- Add 3 missing gfsh start server options:
  --http-service-port
  --http-service-bind-address
  --start-rest-api

- Update examples to use these options, instead of using
the older --J=-gemfire. property specification.


Project: http://git-wip-us.apache.org/repos/asf/incubator-geode/repo
Commit: http://git-wip-us.apache.org/repos/asf/incubator-geode/commit/3db9b309
Tree: http://git-wip-us.apache.org/repos/asf/incubator-geode/tree/3db9b309
Diff: http://git-wip-us.apache.org/repos/asf/incubator-geode/diff/3db9b309

Branch: refs/heads/feature/GEODE-1930
Commit: 3db9b309740ff10a7bc0bc6c4ad9bcea3124f29a
Parents: 5731300
Author: Karen Miller 
Authored: Thu Nov 10 14:28:40 2016 -0800
Committer: Karen Miller 
Committed: Fri Nov 11 14:56:12 2016 -0800

--
 .../cluster_config/gfsh_remote.html.md.erb  |  6 +++---
 geode-docs/rest_apps/setup_config.html.md.erb   | 12 ++--
 .../gfsh/command-pages/start.html.md.erb| 20 ++--
 3 files changed, 27 insertions(+), 11 deletions(-)
--


http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/3db9b309/geode-docs/configuring/cluster_config/gfsh_remote.html.md.erb
--
diff --git a/geode-docs/configuring/cluster_config/gfsh_remote.html.md.erb 
b/geode-docs/configuring/cluster_config/gfsh_remote.html.md.erb
index c8ea240..a1fab41 100644
--- a/geode-docs/configuring/cluster_config/gfsh_remote.html.md.erb
+++ b/geode-docs/configuring/cluster_config/gfsh_remote.html.md.erb
@@ -28,13 +28,13 @@ To connect `gfsh` using the HTTP protocol to a remote 
GemFire cluster:
 
 ``` pre
 gfsh>start server --name=server1 --J=-Dgemfire.jmx-manager=true \
---J=-Dgemfire.jmx-manager-start=true --J=-Dgemfire.http-service-port=8080 \
---J=-Dgemfire.http-service-bind-address=myremotecluster.example.com
+--J=-Dgemfire.jmx-manager-start=true --http-service-port=8080 \
+--http-service-bind-address=myremotecluster.example.com
 ```
 
 This command must be executed directly on the host machine that will 
ultimately act as the remote GemFire server that hosts the HTTP service for 
remote administration. (You cannot launch a GemFire server remotely.)
 
-3.  On your local system, run the `gfsh` `connect` command to connect to the 
remote system. Include the `--use-http` and `--url` parameters. For example:
+3.  On your local system, run the `gfsh connect` command to connect to the 
remote system. Include the `--use-http` and `--url` parameters. For example:
 
 ``` pre
 gfsh>connect --use-http=true 
--url="http://myremotecluster.example.com:8080/gemfire/v1;

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/3db9b309/geode-docs/rest_apps/setup_config.html.md.erb
--
diff --git a/geode-docs/rest_apps/setup_config.html.md.erb 
b/geode-docs/rest_apps/setup_config.html.md.erb
index 604dd05..71c50f5 100644
--- a/geode-docs/rest_apps/setup_config.html.md.erb
+++ b/geode-docs/rest_apps/setup_config.html.md.erb
@@ -78,8 +78,8 @@ The following procedure starts up a REST API service-enabled 
Geode deployment:
 2.  Start a server node with the Geode property `start-dev-rest-api` set to 
`true`. For example:
 
 ``` pre
-gfsh>start server --name=server1 --J=-Dgemfire.start-dev-rest-api=true \
---J=-Dgemfire.http-service-port=8080 
--J=-Dgemfire.http-service-bind-address=localhost
+gfsh>start server --name=server1 --start-rest-api=true \
+--http-service-port=8080 --http-service-bind-address=localhost
 ```
 
 Optionally, you can also configure a `http-service-bind-address` and 
`http-service-port` to identify the cache server and specific port that will 
host REST services. If you do not specify the `http-service-port`, the default 
port is 7070. If you do not specify `http-service-bind-address`, the HTTP 
service will bind to all local addresses by default.
@@ -87,8 +87,8 @@ The following procedure starts up a REST API service-enabled 
Geode deployment:
 Any server that hosts data, even a server acting as a JMX manager, can 
start the developer REST API service. For example, to start the service on a 
server that is also a JMX manager, you would run:
 
 ``` pre
-gfsh>start server --name=server1  --J=-Dgemfire.start-dev-rest-api=true \
---J=-Dgemfire.http-service-port=8080 
--J=-Dgemfire.http-service-bind-address=localhost \
+gfsh>start server --name=server1  --start-rest-api=true \
+--http-service-port=8080 --http-service-bind-address=localhost \
 --J=-Dgemfire.jmx-manager=true --J=-Dgemfire.jmx-manager-start=true
 ```
 
@@ -97,8 +97,8 @@ The following procedure starts up a REST API service-enabled 
Geode deployment:
 3.

incubator-geode git commit: GEODE-2094 Update admin/dev REST API documentation

2016-11-11 Thread kmiller 
Repository: incubator-geode
Updated Branches:
  refs/heads/develop 573130045 -> 3db9b3097


GEODE-2094 Update admin/dev REST API documentation

- Add 3 missing gfsh start server options:
  --http-service-port
  --http-service-bind-address
  --start-rest-api

- Update examples to use these options, instead of using
the older --J=-gemfire. property specification.


Project: http://git-wip-us.apache.org/repos/asf/incubator-geode/repo
Commit: http://git-wip-us.apache.org/repos/asf/incubator-geode/commit/3db9b309
Tree: http://git-wip-us.apache.org/repos/asf/incubator-geode/tree/3db9b309
Diff: http://git-wip-us.apache.org/repos/asf/incubator-geode/diff/3db9b309

Branch: refs/heads/develop
Commit: 3db9b309740ff10a7bc0bc6c4ad9bcea3124f29a
Parents: 5731300
Author: Karen Miller 
Authored: Thu Nov 10 14:28:40 2016 -0800
Committer: Karen Miller 
Committed: Fri Nov 11 14:56:12 2016 -0800

--
 .../cluster_config/gfsh_remote.html.md.erb  |  6 +++---
 geode-docs/rest_apps/setup_config.html.md.erb   | 12 ++--
 .../gfsh/command-pages/start.html.md.erb| 20 ++--
 3 files changed, 27 insertions(+), 11 deletions(-)
--


http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/3db9b309/geode-docs/configuring/cluster_config/gfsh_remote.html.md.erb
--
diff --git a/geode-docs/configuring/cluster_config/gfsh_remote.html.md.erb 
b/geode-docs/configuring/cluster_config/gfsh_remote.html.md.erb
index c8ea240..a1fab41 100644
--- a/geode-docs/configuring/cluster_config/gfsh_remote.html.md.erb
+++ b/geode-docs/configuring/cluster_config/gfsh_remote.html.md.erb
@@ -28,13 +28,13 @@ To connect `gfsh` using the HTTP protocol to a remote 
GemFire cluster:
 
 ``` pre
 gfsh>start server --name=server1 --J=-Dgemfire.jmx-manager=true \
---J=-Dgemfire.jmx-manager-start=true --J=-Dgemfire.http-service-port=8080 \
---J=-Dgemfire.http-service-bind-address=myremotecluster.example.com
+--J=-Dgemfire.jmx-manager-start=true --http-service-port=8080 \
+--http-service-bind-address=myremotecluster.example.com
 ```
 
 This command must be executed directly on the host machine that will 
ultimately act as the remote GemFire server that hosts the HTTP service for 
remote administration. (You cannot launch a GemFire server remotely.)
 
-3.  On your local system, run the `gfsh` `connect` command to connect to the 
remote system. Include the `--use-http` and `--url` parameters. For example:
+3.  On your local system, run the `gfsh connect` command to connect to the 
remote system. Include the `--use-http` and `--url` parameters. For example:
 
 ``` pre
 gfsh>connect --use-http=true 
--url="http://myremotecluster.example.com:8080/gemfire/v1;

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/3db9b309/geode-docs/rest_apps/setup_config.html.md.erb
--
diff --git a/geode-docs/rest_apps/setup_config.html.md.erb 
b/geode-docs/rest_apps/setup_config.html.md.erb
index 604dd05..71c50f5 100644
--- a/geode-docs/rest_apps/setup_config.html.md.erb
+++ b/geode-docs/rest_apps/setup_config.html.md.erb
@@ -78,8 +78,8 @@ The following procedure starts up a REST API service-enabled 
Geode deployment:
 2.  Start a server node with the Geode property `start-dev-rest-api` set to 
`true`. For example:
 
 ``` pre
-gfsh>start server --name=server1 --J=-Dgemfire.start-dev-rest-api=true \
---J=-Dgemfire.http-service-port=8080 
--J=-Dgemfire.http-service-bind-address=localhost
+gfsh>start server --name=server1 --start-rest-api=true \
+--http-service-port=8080 --http-service-bind-address=localhost
 ```
 
 Optionally, you can also configure a `http-service-bind-address` and 
`http-service-port` to identify the cache server and specific port that will 
host REST services. If you do not specify the `http-service-port`, the default 
port is 7070. If you do not specify `http-service-bind-address`, the HTTP 
service will bind to all local addresses by default.
@@ -87,8 +87,8 @@ The following procedure starts up a REST API service-enabled 
Geode deployment:
 Any server that hosts data, even a server acting as a JMX manager, can 
start the developer REST API service. For example, to start the service on a 
server that is also a JMX manager, you would run:
 
 ``` pre
-gfsh>start server --name=server1  --J=-Dgemfire.start-dev-rest-api=true \
---J=-Dgemfire.http-service-port=8080 
--J=-Dgemfire.http-service-bind-address=localhost \
+gfsh>start server --name=server1  --start-rest-api=true \
+--http-service-port=8080 --http-service-bind-address=localhost \
 --J=-Dgemfire.jmx-manager=true --J=-Dgemfire.jmx-manager-start=true
 ```
 
@@ -97,8 +97,8 @@ The