ATLAS-2688: updated README & docs for 1.0.0 release

README.txt

@@ -33,15 +33,6 @@ non-authorized access paths to data at runtime.
 Security is both role based (RBAC) and attribute based (ABAC).
 
 
-Apache Atlas 1.0.0-alpha release
-================================
-
-Please note that this is an alpha/technical-preview release and is not
-recommended for production use. There is no support for migration of data
-from earlier version of Apache Atlas. Also, the data generated using this
-alpha release may not migrate to Apache Atlas 1.0 GA release.
-
-
 Build Process
 =============
 
@@ -66,10 +57,12 @@ Build Process
 
 3. After above build commands successfully complete, you should see the following files
 
-   webapp/target/atlas-webapp-<version>.war
-   addons/falcon-bridge/target/falcon-bridge-<version>.jar
-   addons/hive-bridge/target/hive-bridge-<version>.jar
-   addons/sqoop-bridge/target/sqoop-bridge-<version>.jar
-   addons/storm-bridge/target/storm-bridge-<version>.jar
+   distro/target/apache-atlas-1.0.0-bin.tar.gz
+   distro/target/apache-atlas-1.0.0-hbase-hook.tar.gz
+   distro/target/apache-atlas-1.0.0-hive-hook.tar.gz
+   distro/target/apache-atlas-1.0.0-kafka-hook.tar.gz
+   distro/target/apache-atlas-1.0.0-sources.tar.gz
+   distro/target/apache-atlas-1.0.0-sqoop-hook.tar.gz
+   distro/target/apache-atlas-1.0.0-storm-hook.tar.gz
 
 4. For more details on building and running Apache Atlas, please refer to http://atlas.apache.org/InstallationSteps.html

docs/src/site/twiki/security.twiki

@@ -26,7 +26,7 @@ In order to prevent the use of clear-text passwords, the Atlas platofrm makes us
 To create the credential provdier for Atlas:
 
    * cd to the '<code>bin</code>' directory
-   * type '<code>./cputil.sh</code>'
+   * type '<code>./cputil.py</code>'
    * Enter the path for the generated credential provider.  The format for the path is:
       * jceks://file/local/file/path/file.jceks or jceks://hdfs@namenodehost:port/path/in/hdfs/to/file.jceks.  The files generally use the ".jceks" extension (e.g. test.jceks)
    * Enter the passwords for the keystore, truststore, and server key (these passwords need to match the ones utilized for actually creating the associated certificate store files).