Re: gfsh start server with the --password option

[Karen Miller]

Done.  See https://issues.apache.org/jira/browse/GEODE-2119 for my attempt
at describing
the issue in a JIRA ticket.

On Wed, Nov 16, 2016 at 11:09 AM, Swapnil Bawaskar <sbawas...@pivotal.io>
wrote:

> Thanks for find these Karen, Can you please file a JIRA for this issue?
>
> On Tue, Nov 15, 2016 at 5:29 PM, Karen Miller <kmil...@pivotal.io> wrote:
>
> > Also, when doing a gfsh connect (not just start server) that specifies
> user
> > and password
> > on the command line, if a further command of
> >   gfsh history --file=historyfilename
> > is executed, the user and password are written in clear text to the
> history
> > file.
> >
> >
> > On Tue, Nov 15, 2016 at 12:31 PM, Jinmei Liao <jil...@pivotal.io> wrote:
> >
> > > I thought we had code that deals with redacting password in gfsh
> history,
> > > not sure why it's not in effect anymore.
> > >
> > > On Tue, Nov 15, 2016 at 2:27 PM, Swapnil Bawaskar <
> sbawas...@pivotal.io>
> > > wrote:
> > >
> > > > When you want to connect to a secure system you can choose not to use
> > the
> > > > --password option at which point you will be prompted to enter a
> > > > username/password.
> > > > e.g:
> > > > gfsh>connect --locator=localhost[10334]
> > > > Connecting to Locator at [host=localhost, port=10334] ..
> > > > Connecting to Manager at [host=192.168.1.181, port=1099] ..
> > > > username: super-user
> > > > password: 
> > > >
> > > >
> > > > On Tue, Nov 15, 2016 at 11:55 AM, Kirk Lund <kl...@apache.org>
> wrote:
> > > >
> > > > > There should be redaction in gfsh history. Maybe repeating the
> > command
> > > > is a
> > > > > case that wasn't fully covered? This is a bug we'll need to file
> and
> > > fix.
> > > > >
> > > > > Clear text in process string is probably not a bug. Users should
> > > > implement
> > > > > a callback to provide the password instead of providing it as a
> > system
> > > > > property unless they're ok with it showing in the process string.
> > This
> > > > may
> > > > > need more documentation?
> > > > >
> > > > > The logs should not contain the clear text password and this would
> > be a
> > > > bug
> > > > > if it does.
> > > > >
> > > > > -Kirk
> > > > >
> > > > >
> > > > > On Tue, Nov 15, 2016 at 11:08 AM, Karen Miller <kmil...@apache.org
> >
> > > > wrote:
> > > > >
> > > > > > When specifying user name and password to use as authentication
> > > > > credentials
> > > > > > with the gfsh start server command, the password is specified in
> > the
> > > > > clear.
> > > > > > I've added a note in the documentation to point this out, but
> > > > specifying
> > > > > a
> > > > > > password
> > > > > > in this way leads to further ways the clear text password can be
> > > seen.
> > > > > >
> > > > > > - gfsh history will repeat back the command with the password
> shown
> > > > > > - any user on the box can see the clear text password with 'ps'
> > > > > > - (haven't checked if this happens) logs may have the clear text
> > > > password
> > > > > >
> > > > > > Is this an issue?  The history is for a particular user, so not
> so
> > > bad.
> > > > > > Logs can use file system permissions to reduce access.  But
> anyone
> > > with
> > > > > > access to the box can list the processes.
> > > > > >
> > > > > > Karen
> > > > > >
> > > > >
> > > >
> > >
> > >
> > >
> > > --
> > > Cheers
> > >
> > > Jinmei
> > >
> >
>

Review Request 53813: GEODE-2114 Revise user and password options to gfsh connect

[Karen Miller]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/53813/
---

Review request for geode, Dave Barnes and Joey McAllister.


Repository: geode


Description
---

- Note that the password is clear text.
- State that user and password are used for authentication.


Diffs
-

  geode-docs/tools_modules/gfsh/command-pages/connect.html.md.erb 
c015cfe89b702064f70a8aa21c4e628c898d444f 

Diff: https://reviews.apache.org/r/53813/diff/


Testing
---

gradle rat check passes


Thanks,

Karen Miller

Re: gfsh start server with the --password option

[Karen Miller]

Also, when doing a gfsh connect (not just start server) that specifies user
and password
on the command line, if a further command of
  gfsh history --file=historyfilename
is executed, the user and password are written in clear text to the history
file.


On Tue, Nov 15, 2016 at 12:31 PM, Jinmei Liao <jil...@pivotal.io> wrote:

> I thought we had code that deals with redacting password in gfsh history,
> not sure why it's not in effect anymore.
>
> On Tue, Nov 15, 2016 at 2:27 PM, Swapnil Bawaskar <sbawas...@pivotal.io>
> wrote:
>
> > When you want to connect to a secure system you can choose not to use the
> > --password option at which point you will be prompted to enter a
> > username/password.
> > e.g:
> > gfsh>connect --locator=localhost[10334]
> > Connecting to Locator at [host=localhost, port=10334] ..
> > Connecting to Manager at [host=192.168.1.181, port=1099] ..
> > username: super-user
> > password: 
> >
> >
> > On Tue, Nov 15, 2016 at 11:55 AM, Kirk Lund <kl...@apache.org> wrote:
> >
> > > There should be redaction in gfsh history. Maybe repeating the command
> > is a
> > > case that wasn't fully covered? This is a bug we'll need to file and
> fix.
> > >
> > > Clear text in process string is probably not a bug. Users should
> > implement
> > > a callback to provide the password instead of providing it as a system
> > > property unless they're ok with it showing in the process string. This
> > may
> > > need more documentation?
> > >
> > > The logs should not contain the clear text password and this would be a
> > bug
> > > if it does.
> > >
> > > -Kirk
> > >
> > >
> > > On Tue, Nov 15, 2016 at 11:08 AM, Karen Miller <kmil...@apache.org>
> > wrote:
> > >
> > > > When specifying user name and password to use as authentication
> > > credentials
> > > > with the gfsh start server command, the password is specified in the
> > > clear.
> > > > I've added a note in the documentation to point this out, but
> > specifying
> > > a
> > > > password
> > > > in this way leads to further ways the clear text password can be
> seen.
> > > >
> > > > - gfsh history will repeat back the command with the password shown
> > > > - any user on the box can see the clear text password with 'ps'
> > > > - (haven't checked if this happens) logs may have the clear text
> > password
> > > >
> > > > Is this an issue?  The history is for a particular user, so not so
> bad.
> > > > Logs can use file system permissions to reduce access.  But anyone
> with
> > > > access to the box can list the processes.
> > > >
> > > > Karen
> > > >
> > >
> >
>
>
>
> --
> Cheers
>
> Jinmei
>

gfsh start server with the --password option

[Karen Miller]

When specifying user name and password to use as authentication credentials
with the gfsh start server command, the password is specified in the clear.
I've added a note in the documentation to point this out, but specifying a
password
in this way leads to further ways the clear text password can be seen.

- gfsh history will repeat back the command with the password shown
- any user on the box can see the clear text password with 'ps'
- (haven't checked if this happens) logs may have the clear text password

Is this an issue?  The history is for a particular user, so not so bad.
Logs can use file system permissions to reduce access.  But anyone with
access to the box can list the processes.

Karen

Review Request 53750: GEODE-2110 Add gfsh start server user and password options

[Karen Miller]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/53750/
---

Review request for geode, Dave Barnes, Jinmei Liao, and Joey McAllister.


Repository: geode


Description
---

Modifies gfsh start server command reference page to add
the two missing options: --user and --password


Diffs
-

  geode-docs/tools_modules/gfsh/command-pages/start.html.md.erb 
06dfce4d6a96f64295a069a50d79d55b87a1da67 

Diff: https://reviews.apache.org/r/53750/diff/


Testing
---

1. bundle exec bookbinder bind local   finds no broken links

2. gradle rat check passes


Thanks,

Karen Miller

Review Request 53746: GEODE-2105 Remove docs about log collection utility

[Karen Miller]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/53746/
---

Review request for geode, Dave Barnes and Joey McAllister.


Repository: geode


Description
---

The log collection utility is not part of the release,
so remove the documentation.  The content removed by
this commit has been placed on the feature/GEODE-79 branch.


Diffs
-

  geode-book/master_middleman/source/subnavs/geode-subnav.erb 
959fdf32953b7f6d079dfa092ca6f8a1d0e69438 
  geode-docs/managing/logging/log_collection_utility.html.md.erb 
e83634f4082996d67497d92a943671f0e81b6abc 
  geode-docs/managing/logging/logging.html.md.erb 
db4de7ea904f9833e7b06800af597ec2634b5c56 

Diff: https://reviews.apache.org/r/53746/diff/


Testing
---

1. bundle exec bookbinder bind local, with bookbinder version 10.0.2 does not 
find any broken links

2. gradle rat check passes


Thanks,

Karen Miller

Re: Review Request 53737: GEODE-2101 Improve WAN topology terminology in docs

[Karen Miller]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/53737/
---

(Updated Nov. 14, 2016, 8:16 p.m.)


Review request for geode, Dave Barnes and Joey McAllister.


Repository: geode


Description
---

The terms parallel and serial are not right, so change
them:
- a parallel multi-site topology is a fully connected
mesh
- a serial multi-site topology is a ring


Diffs (updated)
-

  
geode-docs/topologies_and_comm/multi_site_configuration/multisite_topologies.html.md.erb
 4b5753b7e32423ab3e1f1d7ad6647465ed378ce9 

Diff: https://reviews.apache.org/r/53737/diff/


Testing
---


Thanks,

Karen Miller

Review Request 53737: GEODE-2101 Improve WAN topology terminology in docs

[Karen Miller]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/53737/
---

Review request for geode, Dave Barnes and Joey McAllister.


Repository: geode


Description
---

The terms parallel and serial are not right, so change
them:
- a parallel multi-site topology is a fully connected
mesh
- a serial multi-site topology is a ring


Diffs
-

  
geode-docs/topologies_and_comm/multi_site_configuration/multisite_topologies.html.md.erb
 4b5753b7e32423ab3e1f1d7ad6647465ed378ce9 

Diff: https://reviews.apache.org/r/53737/diff/


Testing
---


Thanks,

Karen Miller

Re: Review Request 53661: GEODE-2094 Update admin/dev REST API documentation

[Karen Miller]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/53661/
---

(Updated Nov. 11, 2016, 5:37 p.m.)


Review request for geode, Dave Barnes, Jinmei Liao, Joey McAllister, and Kevin 
Duling.


Changes
---

Fixes error pointed out in a review, and corrects the name of the property 
(which still has the "-dev" in it)


Repository: geode


Description
---

- 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. specification.


Diffs (updated)
-

  geode-docs/rest_apps/setup_config.html.md.erb 
604dd059290f8da41e2e05e0946e6a7eaa01e6ca 

Diff: https://reviews.apache.org/r/53661/diff/


Testing
---

gradle rat check passes


Thanks,

Karen Miller

Re: Review Request 53661: GEODE-2094 Update admin/dev REST API documentation

[Karen Miller]

> On Nov. 10, 2016, 11:48 p.m., Dave Barnes wrote:
> > I noticed one variation to the pattern: In 
> > geode-docs/rest_apps/setup_config.html.md.erb at line 100, did you miss one 
> > conversion of start-dev-rest-api to start-rest-api, or was this intentional?

Good catch.  I'll append a fix for that to this review.


- Karen


---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/53661/#review155668
---


On Nov. 10, 2016, 10:44 p.m., Karen Miller wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/53661/
> ---
> 
> (Updated Nov. 10, 2016, 10:44 p.m.)
> 
> 
> Review request for geode, Dave Barnes, Jinmei Liao, Joey McAllister, and 
> Kevin Duling.
> 
> 
> Repository: geode
> 
> 
> Description
> ---
> 
> - 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. specification.
> 
> 
> Diffs
> -
> 
>   geode-docs/configuring/cluster_config/gfsh_remote.html.md.erb 
> c8ea24096c76a5c03bd7a902d225ee4566932b29 
>   geode-docs/rest_apps/setup_config.html.md.erb 
> 604dd059290f8da41e2e05e0946e6a7eaa01e6ca 
>   geode-docs/tools_modules/gfsh/command-pages/start.html.md.erb 
> ff703cb4a7fc49a1bffa92cf9cc2207a6cce2d32 
> 
> Diff: https://reviews.apache.org/r/53661/diff/
> 
> 
> Testing
> ---
> 
> gradle rat check passes
> 
> 
> Thanks,
> 
> Karen Miller
> 
>

Review Request 53661: GEODE-2094 Update admin/dev REST API documentation

[Karen Miller]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/53661/
---

Review request for geode, Dave Barnes, Jinmei Liao, Joey McAllister, and Kevin 
Duling.


Repository: geode


Description
---

- 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. specification.


Diffs
-

  geode-docs/configuring/cluster_config/gfsh_remote.html.md.erb 
c8ea24096c76a5c03bd7a902d225ee4566932b29 
  geode-docs/rest_apps/setup_config.html.md.erb 
604dd059290f8da41e2e05e0946e6a7eaa01e6ca 
  geode-docs/tools_modules/gfsh/command-pages/start.html.md.erb 
ff703cb4a7fc49a1bffa92cf9cc2207a6cce2d32 

Diff: https://reviews.apache.org/r/53661/diff/


Testing
---

gradle rat check passes


Thanks,

Karen Miller

Review Request 53637: GEODE-2090 Update off-heap statistics documentation

[Karen Miller]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/53637/
---

Review request for geode, Dave Barnes, Darrel Schneider, Joey McAllister, and 
Kirk Lund.


Repository: geode


Description
---

- add/correct the gfsh show metrics command reference
page to include the offheap category for when the member
is specified
- in the list of OffHeapMemoryStats, correct the name of
a statistic:  compactions should be defragmentations


Diffs
-

  geode-docs/reference/statistics/statistics_list.html.md.erb 
02ed6a783eb6ff01c0897c9f25244bb1cef9d33b 
  geode-docs/tools_modules/gfsh/command-pages/show.html.md.erb 
98009f1cfb413b3d2111944d9d58bbbace625ccf 

Diff: https://reviews.apache.org/r/53637/diff/


Testing
---

gradle rat check passes

java class that has the names of the OffHeapMemoryStats is
geode-core/src/main/java/org/apache/geode/internal/offheap/OffHeapStorage.java


Thanks,

Karen Miller

Review Request 53581: GEODE-2070 Improve documentation of region management

[Karen Miller]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/53581/
---

Review request for geode, Dave Barnes and Joey McAllister.


Repository: geode


Description
---

GEODE-2070 Improve documentation of region management


Diffs
-

  geode-book/master_middleman/source/subnavs/geode-subnav.erb 
0f1292c23bfe6222c808f84f19e3ac78cf69a635 
  geode-docs/basic_config/data_regions/chapter_overview.html.md.erb 
4917259e06345a8e6fc9ad56fc8045961e151fd5 
  geode-docs/basic_config/data_regions/create_a_region_with_API.html.md.erb 
8bb359b86a0eaeb88fa6fef8432bef89aa872a8b 
  
geode-docs/basic_config/data_regions/create_a_region_with_cacheXML.html.md.erb 
d7838f64f4ed462c26a801911bfe7948891760e0 
  geode-docs/basic_config/data_regions/managing_data_regions.html.md.erb 
f4f792eae3a60efaa52d782f9fc0751656ccf58f 
  geode-docs/reference/topics/cache_xml.html.md.erb 
8d3187b49eff8197f153d6832dc522ce503b1027 
  geode-docs/reference/topics/chapter_overview_regionshortcuts.html.md.erb 
85c69e7c52b03b93efd8ce7be6be698935560fac 
  geode-docs/reference/topics/client-cache.html.md.erb 
963f57434e488c89749163408848b27f714beabd 
  geode-docs/reference/topics/gfe_cache_xml.html.md.erb 
2cd78ec933277fc2be05bb3021bced32a5034192 

Diff: https://reviews.apache.org/r/53581/diff/


Testing
---

gradle rat check passes


Thanks,

Karen Miller

Review Request 53444: GEODE-2068 Improve documentation on serial/parallel gateway senders

[Karen Miller]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/53444/
---

Review request for geode, Barry Oglesby, Dave Barnes, and Joey McAllister.


Repository: geode


Description
---

GEODE-2068 Improve documentation on serial/parallel gateway senders


Diffs
-

  
geode-docs/topologies_and_comm/topology_concepts/multisite_overview.html.md.erb 
2ad9a3843fe78931e1cb802c6c0a2fcb4569dc74 

Diff: https://reviews.apache.org/r/53444/diff/


Testing
---

gradle rat check passes


Thanks,

Karen Miller

Re: Review Request 53414: GEODE-2065 Document defragmentationsInProgress statistic

[Karen Miller]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/53414/
---

(Updated Nov. 3, 2016, 5:04 p.m.)


Review request for geode, Dave Barnes, Darrel Schneider, and Joey McAllister.


Repository: geode


Description
---

This is a sub-task of GEODE-1590.


Diffs (updated)
-

  geode-docs/reference/statistics/statistics_list.html.md.erb 
07e4281f239b73896ed7b1b2fbb6429c87ac5024 

Diff: https://reviews.apache.org/r/53414/diff/


Testing
---

gradle rat check passes


Thanks,

Karen Miller

Review Request 53434: GEODE-2060 Update docs for security-related poperties

[Karen Miller]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/53434/
---

Review request for geode, Dave Barnes, Jinmei Liao, and Joey McAllister.


Repository: geode


Description
---

Add security-manager and security-post-processor.
Deprecate others:
  security-client-accessor
  security-client-accessor-pp
  security-client-authenticator
  security-peer-auth-init
  security-peer-authenticator


Diffs
-

  geode-docs/reference/topics/gemfire_properties.html.md.erb 
ae0f198b1f765469801958e0f7854b54b803b003 

Diff: https://reviews.apache.org/r/53434/diff/


Testing
---

gradle rat check passes


Thanks,

Karen Miller

Review Request 53414: GEODE-2065 Document defragmentationsInProgress statistic

[Karen Miller]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/53414/
---

Review request for geode, Dave Barnes, Darrel Schneider, and Joey McAllister.


Repository: geode


Description
---

This is a sub-task of GEODE-1590.


Diffs
-

  geode-docs/reference/statistics/statistics_list.html.md.erb 
07e4281f239b73896ed7b1b2fbb6429c87ac5024 

Diff: https://reviews.apache.org/r/53414/diff/


Testing
---

gradle rat check passes


Thanks,

Karen Miller

Re: Review Request 53360: GEODE-2050 Remove doc of statistics no longer present

[Karen Miller]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/53360/
---

(Updated Nov. 1, 2016, 11:55 p.m.)


Review request for geode, Bruce Schuchardt, Dave Barnes, and Joey McAllister.


Repository: geode


Description (updated)
---

JGroups-related statistics were removed in the first commit. New membership 
service-related statistics were added in the second commit.


Diffs
-

  geode-docs/reference/statistics/statistics_list.html.md.erb 
227f8dfda8747d00b2e9077f920646d68f3f8acf 

Diff: https://reviews.apache.org/r/53360/diff/


Testing
---

Gradle rat check passes.


Thanks,

Karen Miller

Re: Review Request 53360: GEODE-2050 Remove doc of statistics no longer present

[Karen Miller]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/53360/
---

(Updated Nov. 1, 2016, 11:51 p.m.)


Review request for geode, Bruce Schuchardt, Dave Barnes, and Joey McAllister.


Changes
---

First commit removes statistics no longer present. Second commit adds new 
statistics.


Repository: geode


Description
---

JGroups-related statistics were removed.


Diffs (updated)
-

  geode-docs/reference/statistics/statistics_list.html.md.erb 
227f8dfda8747d00b2e9077f920646d68f3f8acf 

Diff: https://reviews.apache.org/r/53360/diff/


Testing
---

Gradle rat check passes.


Thanks,

Karen Miller

Review Request 53360: GEODE-2050 Remove doc of statistics no longer present

[Karen Miller]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/53360/
---

Review request for geode, Bruce Schuchardt, Dave Barnes, and Joey McAllister.


Repository: geode


Description
---

JGroups-related statistics were removed.


Diffs
-

  geode-docs/reference/statistics/statistics_list.html.md.erb 
227f8dfda8747d00b2e9077f920646d68f3f8acf 

Diff: https://reviews.apache.org/r/53360/diff/


Testing
---

Gradle rat check passes.


Thanks,

Karen Miller

Re: Review Request 53331: GEODE-2047 Document change to enable-network-partition-detection

[Karen Miller]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/53331/
---

(Updated Nov. 1, 2016, 4:02 p.m.)


Review request for geode, Bruce Schuchardt, Dave Barnes, and Joey McAllister.


Repository: geode


Description
---

- This is a subtask of GEODE-762.
- The default value of property enable-network-partition-detection
changed from false to true, enabling partition detection by
default, so all documentation that discusses partition detection
also needs to change.
- Fixed a minor typo or two encountered in the files that were
being updated.


Diffs (updated)
-

  
geode-docs/managing/troubleshooting/recovering_conflicting_data_exceptions.html.md.erb
 38375aea1e5742d878d1e7dbaf3c92d67320d17f 
  
geode-docs/managing/troubleshooting/recovering_from_network_outages.html.md.erb 
8c23beac365af0f8f917b13447c2ae6382ad2525 
  geode-docs/reference/topics/gemfire_properties.html.md.erb 
988256840a084cac56a4e38723415a4c4ea2d99f 

Diff: https://reviews.apache.org/r/53331/diff/


Testing
---

gradle rat check passes


Thanks,

Karen Miller

Review Request 53331: GEODE-2047 Document change to enable-network-partition-detection

[Karen Miller]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/53331/
---

Review request for geode, Bruce Schuchardt, Dave Barnes, and Joey McAllister.


Repository: geode


Description
---

- This is a subtask of GEODE-762.
- The default value of property enable-network-partition-detection
changed from false to true, enabling partition detection by
default, so all documentation that discusses partition detection
also needs to change.
- Fixed a minor typo or two encountered in the files that were
being updated.


Diffs
-

  
geode-docs/managing/network_partitioning/handling_network_partitioning.html.md.erb
 61a25760265771ba3e53c271731af6e44f5e72ee 
  
geode-docs/managing/network_partitioning/how_network_partitioning_management_works.html.md.erb
 e97163401f967f672eea8e7889f8991d971b4145 
  
geode-docs/managing/troubleshooting/recovering_conflicting_data_exceptions.html.md.erb
 38375aea1e5742d878d1e7dbaf3c92d67320d17f 
  
geode-docs/managing/troubleshooting/recovering_from_network_outages.html.md.erb 
8c23beac365af0f8f917b13447c2ae6382ad2525 
  geode-docs/managing/troubleshooting/system_failure_and_recovery.html.md.erb 
d94ea604cdbe1f3ea1e41b8b7172bb825fdb7b38 
  geode-docs/reference/topics/gemfire_properties.html.md.erb 
988256840a084cac56a4e38723415a4c4ea2d99f 

Diff: https://reviews.apache.org/r/53331/diff/


Testing
---

gradle rat check passes


Thanks,

Karen Miller

Review Request 53311: GEODE-2045 Improve docs of region shortcuts

[Karen Miller]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/53311/
---

Review request for geode, Dave Barnes and Joey McAllister.


Repository: geode


Description
---

- Make sure that partitioned regions do not say or imply
that they have local scope.
- Fix labels with anchors, such that links work.
- Remove reference links to general descriptions of the
attributes used by the shortcuts.


Diffs
-

  geode-docs/reference/topics/region_shortcuts_reference.html.md.erb 
d5cb2fabdf8f8ce56b3bbf5dbf4706bb19e0742d 
  geode-docs/reference/topics/region_shortcuts_table.html.md.erb 
c0ead67b475742b05282b9f32df6e10296d94714 

Diff: https://reviews.apache.org/r/53311/diff/


Testing
---

gradle rat check passes


Thanks,

Karen Miller

Review Request 53243: GEODE-2044 Add to docs tc Server 3.2 for HTTP Session Mgmt module

[Karen Miller]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/53243/
---

Review request for geode, William Markito and Dan Smith.


Repository: geode


Description
---

GEODE-2044 Add to docs tc Server 3.2 for HTTP Session Mgmt module


Diffs
-

  geode-docs/tools_modules/http_session_mgmt/quick_start.html.md.erb 
434a13c760f4898600734cd8b188f26df159c4d5 

Diff: https://reviews.apache.org/r/53243/diff/


Testing
---

rat check passes


Thanks,

Karen Miller

Re: Review Request 53168: GEODE-2030: security support for SDG

[Karen Miller]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/53168/#review153964
---



You can add a new commit to this review with
rbt post --repository geode --tracking-branch=origin/develop 
--target-groups=geode -r 53168  newSHA1

- Karen Miller


On Oct. 26, 2016, 9:12 p.m., Jinmei Liao wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/53168/
> ---
> 
> (Updated Oct. 26, 2016, 9:12 p.m.)
> 
> 
> Review request for geode, John Blum, Kevin Duling, and Kirk Lund.
> 
> 
> Repository: geode
> 
> 
> Description
> ---
> 
> GEODE-2030: security support for SDG
> 
> * added cacheFactory.setSecurityManager and cacheFactory.setPostProcessor
> * The isIntegragtedSecurity flag is set by checking if the Shiro's 
> securityManger is configured or not.
> 
> 
> Diffs
> -
> 
>   geode-core/src/main/java/org/apache/geode/cache/CacheFactory.java 
> b62feac4b2a3ae15e940afb50f71abf61e5eee50 
>   geode-core/src/main/java/org/apache/geode/internal/cache/CacheConfig.java 
> 91ae33304a1e82fa7c02c97edce2318d359220e2 
>   
> geode-core/src/main/java/org/apache/geode/internal/cache/GemFireCacheImpl.java
>  d9d572c45ac559e611fe2dc86d1028d39d1e592c 
>   
> geode-core/src/main/java/org/apache/geode/internal/security/IntegratedSecurityService.java
>  9f4697f6c9f06dbfd671e9e0d80dc52f447e5829 
>   
> geode-core/src/main/java/org/apache/geode/internal/security/SecurityService.java
>  41b08d510876f95733c96d103b0826726d9a09bb 
>   
> geode-core/src/test/java/org/apache/geode/internal/security/IntegratedSecurityServiceTest.java
>  ee76dfc095c3aeb43a04cee899ba4b434c1e552e 
>   
> geode-core/src/test/java/org/apache/geode/security/CacheFactoryWithSecurityObjectTest.java
>  PRE-CREATION 
> 
> Diff: https://reviews.apache.org/r/53168/diff/
> 
> 
> Testing
> ---
> 
> precheckin successful
> 
> 
> Thanks,
> 
> Jinmei Liao
> 
>

Review Request 53214: GEODE-2040 Add to docs Tomcat 8.0 and 8.5 for HTTP Session Mgmt module

[Karen Miller]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/53214/
---

Review request for geode, William Markito and Dan Smith.


Repository: geode


Description
---

GEODE-2040 Add to docs Tomcat 8.0 and 8.5 for HTTP Session Mgmt module


Diffs
-

  geode-docs/tools_modules/http_session_mgmt/quick_start.html.md.erb 
d065e323ff0b8e4ea4842885a953095c5e30a92e 
  
geode-docs/tools_modules/http_session_mgmt/tomcat_setting_up_the_module.html.md.erb
 a472ab38e6f8214552501eb23aa265130b972d64 

Diff: https://reviews.apache.org/r/53214/diff/


Testing
---


Thanks,

Karen Miller

Re: GEODE-2036 and documentation practices and procedures

[Karen Miller]

I would also like to add that the C-T-R model for small doc changes such as
typo corrections
sounds like a good model to follow.  So, +1 to that.


On Wed, Oct 26, 2016 at 10:20 AM, Karen Miller <kmil...@pivotal.io> wrote:

> Good by me to not have a catch-all JIRA.  I've made one commit under it,
> and I'll now close
> the JIRA.
>
>
> On Wed, Oct 26, 2016 at 9:36 AM, Joey McAllister <jmcallis...@pivotal.io>
> wrote:
>
>> 3. +1 to Anthony and Dan's recommendation not to use a catch-all JIRA.
>>
>> I think the idea was an attempt to fit within existing guidelines. If
>> there's no requirement to use a JIRA here, let's not do it.
>>
>> On Wed, Oct 26, 2016 at 9:26 AM Dave Barnes <dbar...@pivotal.io> wrote:
>>
>> > 3. If there's no hard-and-fast rule for *always* associating a JIRA with
>> > every change, then I agree with Anthony and Dan for typos and small
>> > changes.
>> >
>> > On Wed, Oct 26, 2016 at 9:19 AM, Dan Smith <dsm...@pivotal.io> wrote:
>> >
>> > > 1) +1
>> > > 2) +1
>> > >
>> > > 3)
>> > > > I don’t see much value in creating an uber-JIRA for tracking minor
>> doc
>> > > changes.  Why not skip it entirely?
>> > > I agree with Anthony on this one, there's not much value in having
>> some
>> > > catch all JIRA for unrelated changes.
>> > >
>> > > -Dan
>> > >
>> > > On Tue, Oct 25, 2016 at 7:08 PM, Anthony Baker <aba...@pivotal.io>
>> > wrote:
>> > >
>> > > > What I _think_ you are suggesting is using C-T-R
>> (commit-then-review)
>> > [1]
>> > > > for reasonably well-defined documentation-related changes.  Do you
>> > agree?
>> > > >
>> > > > Here’s why we tag commits with a JIRA:
>> > > >
>> > > > - we can better understand the reason for a code change by looking
>> at
>> > the
>> > > > associated JIRA
>> > > > - we can scope work in/out of a release by using ‘Fix version’ on
>> the
>> > > JIRA
>> > > > - we can generate release notes by looking at resolved issues for a
>> > given
>> > > > version
>> > > >
>> > > > I don’t see much value in creating an uber-JIRA for tracking minor
>> doc
>> > > > changes.  Why not skip it entirely?
>> > > >
>> > > >
>> > > > Anthony
>> > > >
>> > > > [1] https://www.apache.org/foundation/glossary.html#CommitThenRe
>> view <
>> > > > https://www.apache.org/foundation/glossary.html#CommitThenReview>
>> > > >
>> > > >
>> > > > > On Oct 25, 2016, at 5:45 PM, Karen Miller <kmil...@apache.org>
>> > wrote:
>> > > > >
>> > > > > With our documentation now in the same repository as the code,
>> there
>> > > are
>> > > > now
>> > > > > some doc-related issues that could use some community consensus.
>> Here
>> > > are
>> > > > > some of my opinions to start the discussion.
>> > > > >
>> > > > > 1. Create new JIRA tickets for each documentation task, or use the
>> > > > existing
>> > > > > ticket under
>> > > > > which the code is committed for the documentation task?
>> > > > >
>> > > > >  I'd like to see a combination of both, but use the existing
>> ticket
>> > > > > wherever
>> > > > > possible. By using the same ticket as the code, the documentation
>> > > effort
>> > > > is
>> > > > > less
>> > > > > likely to be forgotten.  I certainly think that when a new
>> property
>> > is
>> > > > > introduced,
>> > > > > or a default value is changed, the same ticket can be used.
>> > > > >
>> > > > >  I think that for large, and new efforts (in the documentation),
>> new
>> > > > > tickets are the
>> > > > > way to go.
>> > > > >
>> > > > > 2. Do we need a review effort for all documentation tasks?
>> > > > >
>> > > > >  My opinion:  no, not for everything.  The bigger the changes, the
>> > more
>> > > > > likely that
>> > > > > a review is warranted.
>> > > > >
>> > > > > 3. Do we need a new JIRA ticket for each very little documentation
>> > > > change?
>> > > > >
>> > > > >  On this question, my strong opinion is no, we don't need distinct
>> > > JIRAs.
>> > > > > I'd like to propose that we use a single ticket per release that
>> > > > > all typo fixes and really small changes are committed under.  No
>> > > > > reviews needed. We won't end up with dozens of tickets, each for a
>> > tiny
>> > > > > change that really needs no community discussion.  If the ticket
>> > > becomes
>> > > > > abused,
>> > > > > we can revisit the topic.
>> > > > >
>> > > > >  I've already created
>> > https://issues.apache.org/jira/browse/GEODE-2036
>> > > > for
>> > > > > just this purpose, as I have a typo that I want to fix.  If no one
>> > > > objects,
>> > > > > we can
>> > > > > use this ticket for all tiny fixes that go with Geode 1.1.0.
>> > > >
>> > > >
>> > >
>> >
>>
>
>

Re: Review Request 53190: [GEODE-2037] Update documentation links

[Karen Miller]

> On Oct. 26, 2016, 6:35 p.m., Karen Miller wrote:
> > Ship It!

I checked each changed link to verify that there were no bad links.

Note that for the change in file geode-site/website/content/releases/index.html 
to be applied, the website will need to be updated after commit.


- Karen


---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/53190/#review153920
---


On Oct. 26, 2016, 3:12 p.m., Anthony Baker wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/53190/
> ---
> 
> (Updated Oct. 26, 2016, 3:12 p.m.)
> 
> 
> Review request for geode, Jinmei Liao, Joey McAllister, and Karen Miller.
> 
> 
> Repository: geode
> 
> 
> Description
> ---
> 
> Fix README.md, geode-examples/README.md, and the website releases
> page to point to documentation hosted on the geode website
> 
> Update pulse documentation links
> 
> 
> Diffs
> -
> 
>   README.md eee17fc3e975a127418c6721209e20b02a61d38d 
>   geode-examples/README.md 1d4eafb2ccb89c88c3f6ddc8d60475c7c30f7a72 
>   geode-pulse/src/main/webapp/DataBrowser.html 
> 165fa6ff04db294033b90a0909e1df51ca74be41 
>   geode-pulse/src/main/webapp/MemberDetails.html 
> b416926e7249374de66bdb7aaa49a8f1382bb260 
>   geode-pulse/src/main/webapp/QueryStatistics.html 
> 07f61c6ab1a1e5b4467ef185768671c5c0fe1a1b 
>   geode-pulse/src/main/webapp/clusterDetail.html 
> 211e366eac85d9e22f15f3f88e0e05dfc11ea7af 
>   geode-pulse/src/main/webapp/properties/gemfire.properties 
> 17e22598e2e549d8f1bbda6935799ca4e2102d5e 
>   geode-pulse/src/main/webapp/properties/gemfire_en.properties 
> 17e22598e2e549d8f1bbda6935799ca4e2102d5e 
>   geode-pulse/src/main/webapp/regionDetail.html 
> 98404cbf1a95f633b62b17a4b5f9c6795b637c72 
>   geode-site/website/content/releases/index.html 
> 63f685e43b5d9c7ccce487f5c6caeca61f070a8f 
> 
> Diff: https://reviews.apache.org/r/53190/diff/
> 
> 
> Testing
> ---
> 
> 
> Thanks,
> 
> Anthony Baker
> 
>

Re: Review Request 53190: [GEODE-2037] Update documentation links

[Karen Miller]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/53190/#review153920
---


Ship it!




Ship It!

- Karen Miller


On Oct. 26, 2016, 3:12 p.m., Anthony Baker wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/53190/
> ---
> 
> (Updated Oct. 26, 2016, 3:12 p.m.)
> 
> 
> Review request for geode, Jinmei Liao, Joey McAllister, and Karen Miller.
> 
> 
> Repository: geode
> 
> 
> Description
> ---
> 
> Fix README.md, geode-examples/README.md, and the website releases
> page to point to documentation hosted on the geode website
> 
> Update pulse documentation links
> 
> 
> Diffs
> -
> 
>   README.md eee17fc3e975a127418c6721209e20b02a61d38d 
>   geode-examples/README.md 1d4eafb2ccb89c88c3f6ddc8d60475c7c30f7a72 
>   geode-pulse/src/main/webapp/DataBrowser.html 
> 165fa6ff04db294033b90a0909e1df51ca74be41 
>   geode-pulse/src/main/webapp/MemberDetails.html 
> b416926e7249374de66bdb7aaa49a8f1382bb260 
>   geode-pulse/src/main/webapp/QueryStatistics.html 
> 07f61c6ab1a1e5b4467ef185768671c5c0fe1a1b 
>   geode-pulse/src/main/webapp/clusterDetail.html 
> 211e366eac85d9e22f15f3f88e0e05dfc11ea7af 
>   geode-pulse/src/main/webapp/properties/gemfire.properties 
> 17e22598e2e549d8f1bbda6935799ca4e2102d5e 
>   geode-pulse/src/main/webapp/properties/gemfire_en.properties 
> 17e22598e2e549d8f1bbda6935799ca4e2102d5e 
>   geode-pulse/src/main/webapp/regionDetail.html 
> 98404cbf1a95f633b62b17a4b5f9c6795b637c72 
>   geode-site/website/content/releases/index.html 
> 63f685e43b5d9c7ccce487f5c6caeca61f070a8f 
> 
> Diff: https://reviews.apache.org/r/53190/diff/
> 
> 
> Testing
> ---
> 
> 
> Thanks,
> 
> Anthony Baker
> 
>

Re: GEODE-2036 and documentation practices and procedures

[Karen Miller]

Good by me to not have a catch-all JIRA.  I've made one commit under it,
and I'll now close
the JIRA.


On Wed, Oct 26, 2016 at 9:36 AM, Joey McAllister <jmcallis...@pivotal.io>
wrote:

> 3. +1 to Anthony and Dan's recommendation not to use a catch-all JIRA.
>
> I think the idea was an attempt to fit within existing guidelines. If
> there's no requirement to use a JIRA here, let's not do it.
>
> On Wed, Oct 26, 2016 at 9:26 AM Dave Barnes <dbar...@pivotal.io> wrote:
>
> > 3. If there's no hard-and-fast rule for *always* associating a JIRA with
> > every change, then I agree with Anthony and Dan for typos and small
> > changes.
> >
> > On Wed, Oct 26, 2016 at 9:19 AM, Dan Smith <dsm...@pivotal.io> wrote:
> >
> > > 1) +1
> > > 2) +1
> > >
> > > 3)
> > > > I don’t see much value in creating an uber-JIRA for tracking minor
> doc
> > > changes.  Why not skip it entirely?
> > > I agree with Anthony on this one, there's not much value in having some
> > > catch all JIRA for unrelated changes.
> > >
> > > -Dan
> > >
> > > On Tue, Oct 25, 2016 at 7:08 PM, Anthony Baker <aba...@pivotal.io>
> > wrote:
> > >
> > > > What I _think_ you are suggesting is using C-T-R (commit-then-review)
> > [1]
> > > > for reasonably well-defined documentation-related changes.  Do you
> > agree?
> > > >
> > > > Here’s why we tag commits with a JIRA:
> > > >
> > > > - we can better understand the reason for a code change by looking at
> > the
> > > > associated JIRA
> > > > - we can scope work in/out of a release by using ‘Fix version’ on the
> > > JIRA
> > > > - we can generate release notes by looking at resolved issues for a
> > given
> > > > version
> > > >
> > > > I don’t see much value in creating an uber-JIRA for tracking minor
> doc
> > > > changes.  Why not skip it entirely?
> > > >
> > > >
> > > > Anthony
> > > >
> > > > [1] https://www.apache.org/foundation/glossary.html#CommitThenReview
> <
> > > > https://www.apache.org/foundation/glossary.html#CommitThenReview>
> > > >
> > > >
> > > > > On Oct 25, 2016, at 5:45 PM, Karen Miller <kmil...@apache.org>
> > wrote:
> > > > >
> > > > > With our documentation now in the same repository as the code,
> there
> > > are
> > > > now
> > > > > some doc-related issues that could use some community consensus.
> Here
> > > are
> > > > > some of my opinions to start the discussion.
> > > > >
> > > > > 1. Create new JIRA tickets for each documentation task, or use the
> > > > existing
> > > > > ticket under
> > > > > which the code is committed for the documentation task?
> > > > >
> > > > >  I'd like to see a combination of both, but use the existing ticket
> > > > > wherever
> > > > > possible. By using the same ticket as the code, the documentation
> > > effort
> > > > is
> > > > > less
> > > > > likely to be forgotten.  I certainly think that when a new property
> > is
> > > > > introduced,
> > > > > or a default value is changed, the same ticket can be used.
> > > > >
> > > > >  I think that for large, and new efforts (in the documentation),
> new
> > > > > tickets are the
> > > > > way to go.
> > > > >
> > > > > 2. Do we need a review effort for all documentation tasks?
> > > > >
> > > > >  My opinion:  no, not for everything.  The bigger the changes, the
> > more
> > > > > likely that
> > > > > a review is warranted.
> > > > >
> > > > > 3. Do we need a new JIRA ticket for each very little documentation
> > > > change?
> > > > >
> > > > >  On this question, my strong opinion is no, we don't need distinct
> > > JIRAs.
> > > > > I'd like to propose that we use a single ticket per release that
> > > > > all typo fixes and really small changes are committed under.  No
> > > > > reviews needed. We won't end up with dozens of tickets, each for a
> > tiny
> > > > > change that really needs no community discussion.  If the ticket
> > > becomes
> > > > > abused,
> > > > > we can revisit the topic.
> > > > >
> > > > >  I've already created
> > https://issues.apache.org/jira/browse/GEODE-2036
> > > > for
> > > > > just this purpose, as I have a typo that I want to fix.  If no one
> > > > objects,
> > > > > we can
> > > > > use this ticket for all tiny fixes that go with Geode 1.1.0.
> > > >
> > > >
> > >
> >
>

GEODE-2036 and documentation practices and procedures

[Karen Miller]

With our documentation now in the same repository as the code, there are now
some doc-related issues that could use some community consensus. Here are
some of my opinions to start the discussion.

1. Create new JIRA tickets for each documentation task, or use the existing
ticket under
which the code is committed for the documentation task?

  I'd like to see a combination of both, but use the existing ticket
wherever
possible. By using the same ticket as the code, the documentation effort is
less
likely to be forgotten.  I certainly think that when a new property is
introduced,
or a default value is changed, the same ticket can be used.

  I think that for large, and new efforts (in the documentation), new
tickets are the
way to go.

2. Do we need a review effort for all documentation tasks?

  My opinion:  no, not for everything.  The bigger the changes, the more
likely that
a review is warranted.

3. Do we need a new JIRA ticket for each very little documentation change?

  On this question, my strong opinion is no, we don't need distinct JIRAs.
I'd like to propose that we use a single ticket per release that
all typo fixes and really small changes are committed under.  No
reviews needed. We won't end up with dozens of tickets, each for a tiny
change that really needs no community discussion.  If the ticket becomes
abused,
we can revisit the topic.

  I've already created https://issues.apache.org/jira/browse/GEODE-2036 for
just this purpose, as I have a typo that I want to fix.  If no one objects,
we can
use this ticket for all tiny fixes that go with Geode 1.1.0.

Re: Review Request 53107: GEODE-2023: Add Lucene documentation

[Karen Miller]

> On Oct. 24, 2016, 5:56 p.m., Karen Miller wrote:
> > Ship It!

Nice addition to the documentation.  I also verified that the rat check passes.

Note that this patch will merge nicely into the develop branch, but will both 
be incorrect and cause a conflict in short order when the new paths to the 
documentation (hosted within Apache) get merged into the develop branch.  We 
can fix those issues when they occur.


- Karen


---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/53107/#review153714
---


On Oct. 21, 2016, 10:56 p.m., Dave Barnes wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/53107/
> ---
> 
> (Updated Oct. 21, 2016, 10:56 p.m.)
> 
> 
> Review request for geode, Joey McAllister and Karen Miller.
> 
> 
> Repository: geode
> 
> 
> Description
> ---
> 
> GEODE-2023: Add Lucene documentation
> 
> 
> Diffs
> -
> 
>   geode-book/master_middleman/source/subnavs/geode-subnav.erb 
> 2373f4b397952372a61923c5b57ef8f6d2102ee3 
>   geode-docs/tools_modules/book_intro.html.md.erb 
> 852e3c9de6eba2f83f0c513912c53b771889509e 
>   geode-docs/tools_modules/lucene_integration.html.md.erb PRE-CREATION 
> 
> Diff: https://reviews.apache.org/r/53107/diff/
> 
> 
> Testing
> ---
> 
> 
> Thanks,
> 
> Dave Barnes
> 
>

Re: Review Request 53107: GEODE-2023: Add Lucene documentation

[Karen Miller]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/53107/#review153714
---


Ship it!




Ship It!

- Karen Miller


On Oct. 21, 2016, 10:56 p.m., Dave Barnes wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/53107/
> ---
> 
> (Updated Oct. 21, 2016, 10:56 p.m.)
> 
> 
> Review request for geode, Joey McAllister and Karen Miller.
> 
> 
> Repository: geode
> 
> 
> Description
> ---
> 
> GEODE-2023: Add Lucene documentation
> 
> 
> Diffs
> -
> 
>   geode-book/master_middleman/source/subnavs/geode-subnav.erb 
> 2373f4b397952372a61923c5b57ef8f6d2102ee3 
>   geode-docs/tools_modules/book_intro.html.md.erb 
> 852e3c9de6eba2f83f0c513912c53b771889509e 
>   geode-docs/tools_modules/lucene_integration.html.md.erb PRE-CREATION 
> 
> Diff: https://reviews.apache.org/r/53107/diff/
> 
> 
> Testing
> ---
> 
> 
> Thanks,
> 
> Dave Barnes
> 
>

Re: Review Request 53072: GEODE-2019 Add automated rebalance documentation

[Karen Miller]

> On Oct. 20, 2016, 8:35 p.m., Dave Barnes wrote:
> > I notice a slight mismatch in titles. The subnav and chapter overview links 
> > to this section say "Automated Rebalancing of Partitioned Region Data", 
> > while the section itself is entitled simply "Automated Rebalance".
> > 
> > I'm thinking that as a reader I'd like these to match. Would that 
> > constitute needless hobgoblin consistency?

No hobgoblins around here.  A further commit has implemented the change 
suggested.  Let me know if you think this is now ready to commit.


- Karen


---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/53072/#review153449
-------


On Oct. 20, 2016, 9:22 p.m., Karen Miller wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/53072/
> ---
> 
> (Updated Oct. 20, 2016, 9:22 p.m.)
> 
> 
> Review request for geode, Dave Barnes and Joey McAllister.
> 
> 
> Repository: geode
> 
> 
> Description
> ---
> 
> GEODE-2019  Add automated rebalance documentation
> 
> 
> Diffs
> -
> 
>   geode-docs/developing/partitioned_regions/automated_rebalance.html.md.erb 
> PRE-CREATION 
> 
> Diff: https://reviews.apache.org/r/53072/diff/
> 
> 
> Testing
> ---
> 
> 
> Thanks,
> 
> Karen Miller
> 
>

Re: Review Request 53072: GEODE-2019 Add automated rebalance documentation

[Karen Miller]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/53072/
---

(Updated Oct. 20, 2016, 9:22 p.m.)


Review request for geode, Dave Barnes and Joey McAllister.


Repository: geode


Description
---

GEODE-2019  Add automated rebalance documentation


Diffs (updated)
-

  geode-docs/developing/partitioned_regions/automated_rebalance.html.md.erb 
PRE-CREATION 

Diff: https://reviews.apache.org/r/53072/diff/


Testing
---


Thanks,

Karen Miller

Review Request 53072: GEODE-2019 Add automated rebalance documentation

[Karen Miller]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/53072/
---

Review request for geode, Dave Barnes and Joey McAllister.


Repository: geode


Description
---

GEODE-2019  Add automated rebalance documentation


Diffs
-

  geode-book/master_middleman/source/subnavs/geode-subnav.erb 
53e9118136e4898d0e9ec4e7a30512f3d6bce3ce 
  geode-docs/developing/partitioned_regions/automated_rebalance.html.md.erb 
PRE-CREATION 
  geode-docs/developing/partitioned_regions/chapter_overview.html.md.erb 
c92921b7b8f6adc416ccfab00df8ce51e9bbd113 

Diff: https://reviews.apache.org/r/53072/diff/


Testing
---


Thanks,

Karen Miller

Re: [VOTE] Release Apache Geode (incubating) 1.0.0-incubating - RC2

[Karen Miller]

@Anil:
Without the fix that GEODE-1883 should bring, client caches only have 1 way
of setting
the security properties: do it via the callback.

Once the fix is in, client caches should again have 2 ways of setting the
security
properties: 1.  do it via the callback, or 2. place in a
security.properties file.

The docs on the release/1.0.0-incubating branch (and therefore in the
release candidate)
list the 2 ways of setting the security properties.  However, GEODE-1883
has not been
fixed for the release candidate, so this documentation detail is wrong in
the release
candidate.

The docs in the develop branch list only the 1 way.

Does this explanation help?

On Mon, Oct 17, 2016 at 2:54 PM, Anilkumar Gingade <aging...@pivotal.io>
wrote:

> +1 for release...
>
> On Mon, Oct 17, 2016 at 2:54 PM, Anilkumar Gingade <aging...@pivotal.io>
> wrote:
>
> > Hi Karen,
> >
> > The fix still keeps the doc stating:
> > "a client will need to set its credential, composed of the two properties
> > `security-username` and `security-password`."
> >
> > What i see is, additional doc about setting the auth properties using
> > callbacks
> >
> > Am i missing anything?
> >
> > -Anil.
> >
> >
> >
> >
> > On Mon, Oct 17, 2016 at 1:12 PM, Karen Miller <kmil...@pivotal.io>
> wrote:
> >
> >> +0
> >>
> >> With GEODE-1883 being moved to a subsequent release, the just-donated
> docs
> >> are not-quite current with respect to how a client cache may set its
> >> credentials for
> >> authentication.  I put in a fix for this on the develop branch:
> >> https://github.com/apache/incubator-geode/commit/f1df6fc5920
> >> d0d1eebd210e816e61ad44074d39d
> >>
> >> If there were to be a third release candidate, a cherry pick of this
> >> commit
> >> will correct the
> >> 1.0.0-incubating documentation.
> >>
> >>
> >>
> >> On Mon, Oct 17, 2016 at 12:10 PM, Dan Smith <dsm...@pivotal.io> wrote:
> >>
> >> > +1
> >> >
> >> > Checked
> >> >   * signatures
> >> >   * maven repo with simple sample app
> >> >   * command line test through gfsh
> >> >   * built the source
> >> >
> >> > Checked it with this thing:
> >> > https://github.com/upthewaterspout/geode-release-check
> >> >
> >> > On Mon, Oct 17, 2016 at 11:55 AM, William Markito <
> wmark...@pivotal.io>
> >> > wrote:
> >> >
> >> > > +1
> >> > >
> >> > >  Checked SHA, signatures, build/run, sample app and command line
> >> testing
> >> > > through gfsh.
> >> > >
> >> > > On Mon, Oct 17, 2016 at 10:33 AM, Kirk Lund <kl...@pivotal.io>
> wrote:
> >> > >
> >> > > > +1 I think we should target GEODE-2004 and GEODE-1883 for a point
> >> > release
> >> > > > after 1.0.0
> >> > > >
> >> > > >
> >> > > > On Mon, Oct 17, 2016 at 9:46 AM, Jinmei Liao <jil...@pivotal.io>
> >> > wrote:
> >> > > >
> >> > > > > +0
> >> > > > >
> >> > > > > This candidate does not include the fix for GEODE-2004 and
> >> > GEODE-1883.
> >> > > > It's
> >> > > > > not a must fix though.
> >> > > > >
> >> > > > > On Sun, Oct 16, 2016 at 6:58 PM, Anthony Baker <
> aba...@pivotal.io
> >> >
> >> > > > wrote:
> >> > > > >
> >> > > > > > +1
> >> > > > > >
> >> > > > > > * Verified sha’s
> >> > > > > > * Verified signatures
> >> > > > > > * Verified tag signature
> >> > > > > > * Build and run from src distro
> >> > > > > > * Checked src distro for binaries
> >> > > > > > * Run some examples from mvn repo
> >> > > > > > * Reviewed LICENSE and NOTICE
> >> > > > > >
> >> > > > > > Anthony
> >> > > > > >
> >> > > > > > > On Oct 15, 2016, at 5:51 PM, Swapnil Bawaskar <
> >> > > sbawas...@pivotal.io>
> >> > > > > > wrote:
> >> > > > > > >
> >> > > > > > &g

Re: [VOTE] Release Apache Geode (incubating) 1.0.0-incubating - RC2

[Karen Miller]

+0

With GEODE-1883 being moved to a subsequent release, the just-donated docs
are not-quite current with respect to how a client cache may set its
credentials for
authentication.  I put in a fix for this on the develop branch:
https://github.com/apache/incubator-geode/commit/f1df6fc5920d0d1eebd210e816e61ad44074d39d

If there were to be a third release candidate, a cherry pick of this commit
will correct the
1.0.0-incubating documentation.



On Mon, Oct 17, 2016 at 12:10 PM, Dan Smith  wrote:

> +1
>
> Checked
>   * signatures
>   * maven repo with simple sample app
>   * command line test through gfsh
>   * built the source
>
> Checked it with this thing:
> https://github.com/upthewaterspout/geode-release-check
>
> On Mon, Oct 17, 2016 at 11:55 AM, William Markito 
> wrote:
>
> > +1
> >
> >  Checked SHA, signatures, build/run, sample app and command line testing
> > through gfsh.
> >
> > On Mon, Oct 17, 2016 at 10:33 AM, Kirk Lund  wrote:
> >
> > > +1 I think we should target GEODE-2004 and GEODE-1883 for a point
> release
> > > after 1.0.0
> > >
> > >
> > > On Mon, Oct 17, 2016 at 9:46 AM, Jinmei Liao 
> wrote:
> > >
> > > > +0
> > > >
> > > > This candidate does not include the fix for GEODE-2004 and
> GEODE-1883.
> > > It's
> > > > not a must fix though.
> > > >
> > > > On Sun, Oct 16, 2016 at 6:58 PM, Anthony Baker 
> > > wrote:
> > > >
> > > > > +1
> > > > >
> > > > > * Verified sha’s
> > > > > * Verified signatures
> > > > > * Verified tag signature
> > > > > * Build and run from src distro
> > > > > * Checked src distro for binaries
> > > > > * Run some examples from mvn repo
> > > > > * Reviewed LICENSE and NOTICE
> > > > >
> > > > > Anthony
> > > > >
> > > > > > On Oct 15, 2016, at 5:51 PM, Swapnil Bawaskar <
> > sbawas...@pivotal.io>
> > > > > wrote:
> > > > > >
> > > > > > All,
> > > > > >
> > > > > > This is the second release candidate for Apache Geode, version
> > > > > > 1.0.0-incubating. I discarded the first release candidate since
> my
> > > pgp
> > > > > > key was missing from the KEYS file.
> > > > > > Thanks to all the community members to drive towards this
> > milestone!
> > > > > >
> > > > > > It fixes the following issues:
> > > > > >
> > > > > >https://issues.apache.org/jira/secure/ReleaseNote.jspa?
> > > > > projectId=12318420=12332343
> > > > > >
> > > > > > *** Please download, test and vote by Wednesday, October 19, 0800
> > hrs
> > > > > > US Pacific.
> > > > > >
> > > > > > Note that we are voting upon the source (tag):
> > > > > >   rel/1.0.0-incubating.RC2
> > > > > >  > > > > geode.git;a=tag;h=refs/tags/rel/v1.0.0-incubating.RC2>
> > > > > >
> > > > > > Commit ID: 280a407c59a89401d5d87d6e6aeda1c975870753
> > > > > >  > > > > geode.git;a=commit;h=280a407c59a89401d5d87d6e6aeda1c975870753>
> > > > > >
> > > > > > Source and binary files:
> > > > > >   https://dist.apache.org/repos/dist/dev/incubator/geode/1.0.
> > > > > 0-incubating.RC2/
> > > > > >
> > > > > > The documentation on how to install and use Apache Geode are
> hosted
> > > > > > on pivotal.io:
> > > > > >   http://geode.docs.pivotal.io
> > > > > >
> > > > > > Maven staging repo:
> > > > > >   https://repository.apache.org/content/repositories/
> > > > > orgapachegeode-1014/
> > > > > >
> > > > > > Geode's KEYS file containing PGP keys we use to sign the release:
> > > > > >   https://github.com/apache/incubator-geode/blob/release/
> > > > > 1.0.0-incubating/KEYS
> > > > > >
> > > > > > Release Signed with Key: pub   4096R/18F902DB 2016-04-07
> > > > > > Fingerprint: E1B1 ABE3 4753 E7BA 8097  4285 8F8F 2BCC 18F9 02DB
> > > > > >
> > > > > > Thanks,
> > > > > >
> > > > > > Swapnil.
> > > > >
> > > > >
> > > >
> > > >
> > > > --
> > > > Cheers
> > > >
> > > > Jinmei
> > > >
> > >
> >
> >
> >
> > --
> >
> > ~/William
> >
>

Re: [ANNOUNCE] Donation of Geode documentation

[Karen Miller]

I'd love to see the docs included in 1.0.


On Fri, Sep 30, 2016 at 9:30 AM, Dan Smith  wrote:

> This is great!
>
> Is this something we want to include in 1.0?
>
> -Dan
>
> On Thu, Sep 29, 2016 at 8:54 PM, Jared Stewart 
> wrote:
>
> > Thanks for the good news!
> >
> > On Sep 29, 2016 8:52 PM, "Kirk Lund"  wrote:
> >
> > > Great news!
> > >
> > > On Thursday, September 29, 2016, Anthony Baker 
> > wrote:
> > >
> > > > I am pleased to announce the donation of Geode documentation to the
> > > > Geode community.
> > > >
> > > > The documentation provides a complete user guide for Geode. This
> > > > donation includes the source necessary to build the documentation
> site
> > > > currently hosted by Pivotal [1]. The documentation source has been
> > > > converted into a community-friendly markdown format.
> > > >
> > > > The Software Grant Agreement for this code has been accepted by the
> ASF
> > > > secretary.
> > > >
> > > > The donated source currently sits in a separate branch in the Geode
> > > > repository named staging/docs-grant1 [2] and is awaiting community
> > > > review. I encourage everyone in the Geode community to review this
> > > > donation and provide feedback. Once the community has reached a
> > > > consensus we can determine next steps and how this code might get
> > > > merged into the develop branch [3]. This will allow the geode
> > > > community to accept documentation contributions and self-host the
> > > > documentation on the project website. Your suggestions are most
> > > > welcome!
> > > >
> > > > Thanks,
> > > > Anthony
> > > >
> > > > [1] http://geode.docs.pivotal.io
> > > > [2] https://git-wip-us.apache.org/repos/asf?p=incubator-geode.
> > > > git;a=tree;h=refs/heads/staging/docs-grant1;hb=refs/
> > > > heads/staging/docs-grant1
> > > > [3] https://issues.apache.org/jira/browse/GEODE-1952
> > > >
> > >
> >
>

Re: Review Request 51764: GEODE-1880 DistributedSystem.java: typo repair in javadocs

[Karen Miller]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/51764/#review148365
---


Ship it!




Ship It!

- Karen Miller


On Sept. 9, 2016, 6:30 p.m., Dave Barnes wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/51764/
> ---
> 
> (Updated Sept. 9, 2016, 6:30 p.m.)
> 
> 
> Review request for geode, Joey McAllister and Karen Miller.
> 
> 
> Repository: geode
> 
> 
> Description
> ---
> 
> GEODE-1880 DistributedSystem.java: typo repair in javadocs
> 
> 
> Diffs
> -
> 
>   
> geode-core/src/main/java/com/gemstone/gemfire/distributed/DistributedSystem.java
>  cb6851f4382950ffe3b9ba3a4c04a1288acb14be 
> 
> Diff: https://reviews.apache.org/r/51764/diff/
> 
> 
> Testing
> ---
> 
> 
> Thanks,
> 
> Dave Barnes
> 
>

Re: [GitHub] incubator-geode pull request #216: Feature/geode 1694

[Karen Miller]

+1

I'll merge in this change.

On Mon, Jul 25, 2016 at 5:04 PM, joeymcallister  wrote:

> GitHub user joeymcallister opened a pull request:
>
> https://github.com/apache/incubator-geode/pull/216
>
> Feature/geode 1694
>
> GEODE-1694 Add Karen Smoler Miller to commiters
>
> You can merge this pull request into a Git repository by running:
>
> $ git pull https://github.com/joeymcallister/incubator-geode
> feature/GEODE-1694
>
> Alternatively you can review and apply these changes as the patch at:
>
> https://github.com/apache/incubator-geode/pull/216.patch
>
> To close this pull request, make a commit to your master/trunk branch
> with (at least) the following in the commit message:
>
> This closes #216
>
> 
> commit 8edfe6027058736ac4698fdc9f4382acc651ebc7
> Author: Joey McAllister 
> Date:   2016-07-25T23:35:41Z
>
> Merge remote-tracking branch 'apache/develop' into develop
>
> commit 81c1ac641b491bf592d866b65a27985877c81e2e
> Author: Joey McAllister 
> Date:   2016-07-26T00:01:41Z
>
> GEODE-1694 Add Karen Smoler Miller to committers
>
> 
>
>
> ---
> If your project is set up for it, you can reply to this email and have your
> reply appear on GitHub as well. If your project does not have this feature
> enabled and wishes so, or if the feature is enabled but not working, please
> contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
> with INFRA.
> ---
>

Re: Valid characters in region names?

[Karen Miller]

Here is the page of the documentation on region naming:

http://docs-geode-develop.cfapps.io/docs/basic_config/data_regions/region_naming.html

I'm guessing that a JIRA for also including a dash was not implemented.
When you find the
JIRA number, please post it on this thread.


On Thu, Jun 30, 2016 at 12:57 PM, Kevin Duling  wrote:

> Do you know if a Jira ticket was opened on it?  I'm currently working on
> https://issues.apache.org/jira/browse/GEODE-1615 and would like to link to
> it.
>
> On Thu, Jun 30, 2016 at 12:38 PM, Michael Stolz  wrote:
>
> > Yes we did discuss adding hyphen in Geode, and we discussed actually
> > checking during create.
> >
> > --
> > Mike Stolz
> > Principal Engineer, GemFire Product Manager
> > Mobile: 631-835-4771
> >
> > On Thu, Jun 30, 2016 at 3:30 PM, Kevin Duling 
> wrote:
> >
> > > I found a thread from March of this year where this was discussed and
> '-'
> > > is also included in that list.
> > >
> > > Shouldn't the creation of a region with an invalid character raise an
> > > exception?  I'm finding that I can create and list regions with a
> variety
> > > of non-alphanumeric characters.  But I can only destroy a subset of
> > those.
> > >
> > >  It appears to be because some are created with quotes around the
> region
> > > name.
> > >
> > > E.g.,
> > >
> > > service=Region, name=/good, type=Member
> > > service=Region, name="/not*good", type=Member
> > >
> > > The name lookup fails in the Destroy call.  The rule that applied the
> > > quotes for /not*good during Create isn't applied in Destroy
> > >
> > > On Thu, Jun 30, 2016 at 12:06 PM, Michael Stolz 
> > wrote:
> > >
> > > > The only characters that should be used in Region names are
> > > > ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz1234567890_
> > > >
> > > > --
> > > > Mike Stolz
> > > > Principal Engineer, GemFire Product Manager
> > > > Mobile: 631-835-4771
> > > >
> > > > On Thu, Jun 30, 2016 at 2:03 PM, Kevin Duling 
> > > wrote:
> > > >
> > > > > I'm working on a bug where it is not possible to delete a region
> that
> > > > has a
> > > > > hyphen in it.  E.g., the region was created with:
> > > > >
> > > > > create region --name=not-good --type=REPLICATE
> > > > >
> > > > > I've a solution done, but see this as an opportunity to add a test
> > for
> > > > > other special characters.  Is there a list of valid and invalid
> > > > characters
> > > > > for a region name?
> > > > >
> > > >
> > >
> >
>

Re: source code build instruction improvements on the cwiki

[Karen Miller]

With Sai's suggestion, the instructions are even better.  It should be more
clear that the gfsh
script is available from 2 distinct locations after building from source,
and that the developer
does not need to install from the distribution.

On Thu, Apr 7, 2016 at 11:09 AM, Sai Boorlagadda <sboorlaga...@pivotal.io>
wrote:

> Karen,
>
> Looks good to me.
>
> Just a suggestion to continue with the flow of instructions,
> Do we need to point user to the gfsh available in the bin folder of the
> extracted binary distribution?
> As we instructed about extracting the binary and add the bin directory to
> the path.
>
> Sai
>
> On Tue, Apr 5, 2016 at 1:42 PM, Karen Miller <kmil...@pivotal.io> wrote:
>
> > I have again updated the build instructions, incorporating Dan's
> > suggestions for
> > for improvement.
> >
> > Note that while there is a gradlew.bat script (for a build on Windows) in
> > the develop branch
> > of the repository, there is *no* gradlew.bat script included with an
> Apache
> > Geode
> > (incubating) release of the source code.  This means that the build
> > instructions differ
> > based on where the source is acquired from.  These instructions assume
> > acquisition of the
> > repository from the develop branch, as I think should be the case for a
> > Geode developer.
> >
> > Please take a look and suggest further feedback.  Karen
> >
> >
> > On Fri, Mar 18, 2016 at 4:27 PM, Dan Smith <dsm...@pivotal.io> wrote:
> >
> > > build depends on installDist so I think "build installDist" is
> redundant.
> > > It should be just
> > > ./gradlew build
> > > or
> > > ./gradlew build -Dskip.tests=true
> > >
> > >
> > > There is a gradlew.bat script for windows if you actually clone the
> > source.
> > > Should we tell people that only need to install gradle if they download
> > the
> > > source distribution?
> > >
> > > -Dan
> > >
> > > On Fri, Mar 18, 2016 at 4:20 PM, Karen Miller <kmil...@pivotal.io>
> > wrote:
> > >
> > > > Check out improvements to the cwiki page on building Geode from
> source
> > at
> > > >
> > > >
> > >
> >
> https://cwiki.apache.org/confluence/display/GEODE/Building+and+Running+Geode+from+Source
> > > >
> > > > I've also refined the Geode In 5 Minutes guide found at
> > > > https://cwiki.apache.org/confluence/display/GEODE/Index
> > > >
> > > > Please consider and provide feedback.  Karen
> > > >
> > >
> >
>
>
>
> --
> Sai Boorlagadda
>

Re: source code build instruction improvements on the cwiki

[Karen Miller]

I have again updated the build instructions, incorporating Dan's
suggestions for
for improvement.

Note that while there is a gradlew.bat script (for a build on Windows) in
the develop branch
of the repository, there is *no* gradlew.bat script included with an Apache
Geode
(incubating) release of the source code.  This means that the build
instructions differ
based on where the source is acquired from.  These instructions assume
acquisition of the
repository from the develop branch, as I think should be the case for a
Geode developer.

Please take a look and suggest further feedback.  Karen


On Fri, Mar 18, 2016 at 4:27 PM, Dan Smith <dsm...@pivotal.io> wrote:

> build depends on installDist so I think "build installDist" is redundant.
> It should be just
> ./gradlew build
> or
> ./gradlew build -Dskip.tests=true
>
>
> There is a gradlew.bat script for windows if you actually clone the source.
> Should we tell people that only need to install gradle if they download the
> source distribution?
>
> -Dan
>
> On Fri, Mar 18, 2016 at 4:20 PM, Karen Miller <kmil...@pivotal.io> wrote:
>
> > Check out improvements to the cwiki page on building Geode from source at
> >
> >
> https://cwiki.apache.org/confluence/display/GEODE/Building+and+Running+Geode+from+Source
> >
> > I've also refined the Geode In 5 Minutes guide found at
> > https://cwiki.apache.org/confluence/display/GEODE/Index
> >
> > Please consider and provide feedback.  Karen
> >
>

Re: [GitHub] incubator-geode pull request: GEODE-1151 Add new committer to list...

[Karen Miller]

A second commit on the PR adds Nitin to the list of committers.


On Wed, Mar 30, 2016 at 6:54 PM, Greg Chase <gch...@pivotal.io> wrote:

> Please add Nitin Lamba too.
>
> This email encrypted by tiny buttons & fat thumbs, beta voice recognition,
> and autocorrect on my iPhone.
>
> > On Mar 30, 2016, at 4:15 PM, karensmolermiller <g...@git.apache.org>
> wrote:
> >
> > GitHub user karensmolermiller opened a pull request:
> >
> >https://github.com/apache/incubator-geode/pull/120
> >
> >GEODE-1151 Add new committer to list on web page
> >
> >Dave Barnes is a new committer to Geode. This PR adds his name
> >to the list of committers on the Community web page.  To make
> >the web page pretty, it also does a minor alteration to
> >rebalance the number of names per column.
> >
> > You can merge this pull request into a Git repository by running:
> >
> >$ git pull https://github.com/karensmolermiller/incubator-geode
> feature/GEODE-1151
> >
> > Alternatively you can review and apply these changes as the patch at:
> >
> >https://github.com/apache/incubator-geode/pull/120.patch
> >
> > To close this pull request, make a commit to your master/trunk branch
> > with (at least) the following in the commit message:
> >
> >This closes #120
> >
> > 
> > commit 3e295f98367de470b54a3c9008e10b094432a5be
> > Author: Karen Miller <kmil...@pivotal.io>
> > Date:   2016-03-30T23:02:22Z
> >
> >GEODE-1151 Add new committer to list on web page
> >
> >Dave Barnes is a new committer to Geode. This PR adds his name
> >to the list of committers on the Community web page.  To make
> >the web page pretty, it also does a minor alteration to
> >rebalance the number of names per column.
> >
> > 
> >
> >
> > ---
> > If your project is set up for it, you can reply to this email and have
> your
> > reply appear on GitHub as well. If your project does not have this
> feature
> > enabled and wishes so, or if the feature is enabled but not working,
> please
> > contact infrastructure at infrastruct...@apache.org or file a JIRA
> ticket
> > with INFRA.
> > ---
>

source code build instruction improvements on the cwiki

[Karen Miller]

Check out improvements to the cwiki page on building Geode from source at
https://cwiki.apache.org/confluence/display/GEODE/Building+and+Running+Geode+from+Source

I've also refined the Geode In 5 Minutes guide found at
https://cwiki.apache.org/confluence/display/GEODE/Index

Please consider and provide feedback.  Karen

facebook group!

[Karen Miller]

*Friends of Geode* is a new and public facebook group for people to
meet and enjoy the non-dev side of the project.  Anyone can join.

Please do not discuss or initiate Apache Geode (incubating) project business
on this new facebook group.

Karen

Re: Review Request 43620: Added stat to know time spent in handover udp message to other executor pool

[Karen Miller]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/43620/#review119527
---



Please change the spelling of every string and variable name that currently 
embeds (incorrect) 'dispach.' The correct spelling is dispatch (with a 't').

- Karen Miller


On Feb. 16, 2016, 8:21 p.m., Hitesh Khamesra wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/43620/
> ---
> 
> (Updated Feb. 16, 2016, 8:21 p.m.)
> 
> 
> Review request for geode, Bruce Schuchardt and Udo Kohlmeyer.
> 
> 
> Repository: geode
> 
> 
> Description
> ---
> 
> Added stat to know time spent in handover udp message to other executor pool
> 
> 
> Diffs
> -
> 
>   
> gemfire-core/src/main/java/com/gemstone/gemfire/distributed/internal/DMStats.java
>  7bf5b80 
>   
> gemfire-core/src/main/java/com/gemstone/gemfire/distributed/internal/DistributionStats.java
>  28ca380 
>   
> gemfire-core/src/main/java/com/gemstone/gemfire/distributed/internal/LonerDistributionManager.java
>  419c096 
>   
> gemfire-core/src/main/java/com/gemstone/gemfire/distributed/internal/membership/gms/messenger/JGroupsMessenger.java
>  3bd1e83 
> 
> Diff: https://reviews.apache.org/r/43620/diff/
> 
> 
> Testing
> ---
> 
> 
> Thanks,
> 
> Hitesh Khamesra
> 
>

Re: documentation's product name and version number

[Karen Miller]

Please take a look at the documentation.  I believe that we'll comply, as
we use the full product name
directly followed by the version number in prominent places, such as on the
main landing page, and
at the top of the navigation pane.  Placing it at the top of the navigation
pane means that
   Apache Geode 1.0.0-incubating
is always visible as you look at any page within the documentation.  Not a
header or a footer, but
does this satisfy?
Karen


On Wed, Jan 13, 2016 at 5:43 PM, Roman Shaposhnik <ro...@shaposhnik.org>
wrote:

> On Wed, Jan 13, 2016 at 5:39 PM, Karen Miller <kmil...@pivotal.io> wrote:
> > I've modified the Geode documentation to list 'Apache Geode'
>
> Not to nitpick, but we need to make sure (incubating) nomenclature
> is reasonably visible. You don't have to search-n-replace all of it
> but including it in a few strategic places like perhaps headers/footers
> will be required to comply with branding guidelines.
>
> Thanks,
> Roman.
>

documentation's product name and version number

[Karen Miller]

I've modified the Geode documentation to list 'Apache Geode' as the
full product name, with 'Geode' as a short form of the product name.
The version number is listed as '1.0.0-incubating' for now.  I've left off
any further versioning specification (Mx, RCx, etc.); it will be easy to
add, once it becomes needed.

Speak up if there's a reason to further change these items in the
documentation.
Thanks, Karen

Re: installation documentation: which details do we need to specify?

[Karen Miller]

Geode dev community,
  I received no responses to my inquiry, so I'm sending a second message to
follow up.
What information should the Geode documentation include for installation
prerequisites
other than the needed version of Java?
Thanks.  Karen

On Thu, Nov 19, 2015 at 11:44 AM, Karen Miller <kmil...@pivotal.io> wrote:

> Geode dev community,
>   When documenting prerequisites for installation of Geode, which items
> ought
> we specify?
>
>   Certainly we specify items such as
>
>- JDK version required
>- limits for FDs and nprocs
>
> But, should we also identify platforms (architecture/OS) on which Geode
> builds?
> What information should we specify in the documentation?
> Thanks.
> Karen Miller
> Pivotal technical writer and committer-wannabe
>
>

installation documentation: which details do we need to specify?

[Karen Miller]

Geode dev community,
  When documenting prerequisites for installation of Geode, which items
ought
we specify?

  Certainly we specify items such as

   - JDK version required
   - limits for FDs and nprocs

But, should we also identify platforms (architecture/OS) on which Geode
builds?
What information should we specify in the documentation?
Thanks.
Karen Miller
Pivotal technical writer and committer-wannabe