Differences

This shows you the differences between two versions of the page.

Link to this comparison view

googlecloud-gettingstarted [2022_08_04 13:57] – [Verify SSH Access] ericgooglecloud-gettingstarted [2024_04_22 21:30] (current) – external edit 127.0.0.1
Line 1: Line 1:
 # Getting Started with Google Cloud # Getting Started with Google Cloud
-##### last updated July 27, 2021 
  
-## Why Google Cloud?+##### last updated July 13, 2023
  
-[[https://console.cloud.google.com/marketplace/details/sme-public-project/sme-enterprisefilefabric|{{ :googlecloud-gettingstarted:launchnow.png?nolink|nobox}}]]+## Why Google Cloud?
  
-Google Cloud customers are using the File Fabric to take advantage of the high durability, scalability and low cost of Google Cloud Storage. Customers are able to securely extend access to end users and existing file-based applications, significantly reducing migration costs to the cloud. +[[https://console.cloud.google.com/marketplace/product/nasuni-public/nasuni-access-anywhere-server|{{ :googlecloud-gettingstarted:launchnow.png?nolink|nobox}}]]
  
-For more information on See [[https://storagemadeeasy.com/objectstorage/|The Enterprise File Fabric™ — The Killer Solution for Object Storage !]]+Google Cloud customers are using Nasuni Access Anywhere to take advantage of the high durability, scalability and low cost of Nasuni file sgtorage. Customers are able to securely extend access to end users and existing file-based applications, significantly reducing migration costs to the cloud. 
  
 ## Deployment Architecture ## Deployment Architecture
Line 14: Line 13:
 {{ :googlecloud-gettingstarted:eff-google-mktplace.png?200| }}  {{ :googlecloud-gettingstarted:eff-google-mktplace.png?200| }} 
  
-For evaluation and smaller production environments, the Enterprise File Fabric™ solution is typically deployed as a single virtual machine. The virtual machine includes an embedded database and search index.+For evaluation and smaller production environments, the Access Anywhere Server is typically deployed as a single virtual machine. The virtual machine includes an embedded database and search index.
  
 A single virtual machine can be launched directly from the Google Cloud Platform Marketplace.  A single virtual machine can be launched directly from the Google Cloud Platform Marketplace. 
Line 35: Line 34:
  
  * Access to request / update DNS names for appliance (recommended)  * Access to request / update DNS names for appliance (recommended)
- * SME Enterprise File Fabric license key (required) - A trial key can be requested from https://www.storagemadeeasy.com/appform/.+ * License key (required) - A trial key can be requested from https://www.storagemadeeasy.com/appform/.
  * Outbound mail relay information. (recommended)  * Outbound mail relay information. (recommended)
  * Default storage system connectivity details - Google Cloud Storage recommended (required)  * Default storage system connectivity details - Google Cloud Storage recommended (required)
Line 42: Line 41:
 ## Launch ## Launch
  
-{{ :googlecloud-gettingstarted:gcp-launch-enterprisefilefabric.png?300| }}+{{ :googlecloud-gettingstarted:launch-server.png?400 |}}
  
-1. From the Google Cloud Platform Marketplace click  [[https://console.cloud.google.com/marketplace/details/sme-public-project/sme-enterprisefilefabric|Enterprise File Fabric]].+1. From the Google Cloud Platform Marketplace click  [[https://console.cloud.google.com/marketplace/product/nasuni-public/nasuni-access-anywhere-server|Nasuni Access Anywhere Server]].
  
 2. Then click **Launch**. 2. Then click **Launch**.
- 
  
  
Line 65: Line 63:
  
 {{ :googlecloud-gettingstarted:solution-deployed.png?nolink&1000 |}} {{ :googlecloud-gettingstarted:solution-deployed.png?nolink&1000 |}}
- 
 ## Verify Web Access ## Verify Web Access
  
-{{ :googlecloud-gettingstarted:appl_login.png?200| }}+{{ :googlecloud-gettingstarted:appl_login.png?300 | }}
  
 From the deployment panel, click the button **Visit the site** to bring up the appliance login page. You can also use the Site Address URL directly. Use the username **appladmin** and password **Admin password** to log into the appliance. From the deployment panel, click the button **Visit the site** to bring up the appliance login page. You can also use the Site Address URL directly. Use the username **appladmin** and password **Admin password** to log into the appliance.
Line 74: Line 71:
 Until changed the appliance has an untrusted SSL certificate. Most browsers will flag this as a potential security issue and require your acknowledgement to bring up the page. Until changed the appliance has an untrusted SSL certificate. Most browsers will flag this as a potential security issue and require your acknowledgement to bring up the page.
  
-If you don't have the deployment panel, first open the [[https://console.cloud.google.com|Google Cloud Console]]. From the top left hamburger menu (aka Navigation menu) go to the page **Compute Engine > [[https://console.cloud.google.com/compute/instances|VM instances]]**. If you don't see the File Fabric instance check the project you are viewing. Open the VM instance details and locate the **External IP** under Network interfaces. Open the appliance website at %%https://<External IP>/%%. The username is appladmin and the password can be found under Customer metadata as the **eff\_user\_password**.+If you don't have the deployment panel, first open the [[https://console.cloud.google.com|Google Cloud Console]]. From the top left hamburger menu (aka Navigation menu) go to the page **Compute Engine > [[https://console.cloud.google.com/compute/instances|VM instances]]**. If you don't see the Access Anywhere server instance check the project you are viewing. Open the VM instance details and locate the **External IP** under Network interfaces. 
 + 
 +Open the appliance website at %%https://<External IP>/%%. The username is appladmin and the password can be found towards the bottom of the page under Customer metadata as the ```eff_user_password```. 
 + 
 +{{ :googlecloud-gettingstarted:custom-metadata.png?500 |}}
  
  
Line 139: Line 140:
 ## Change Hostname ## Change Hostname
  
-To update the appliance with the FQDN change to the root user by issuing “sudo bash“ with SSH. As the root user, edit /etc/hostname with nano or vi.+To update the appliance with the FQDN change to the root user by issuing “sudo su -“ with SSH. As the root user, edit /etc/hostname with nano or vi.
  
 Change the google instance name to your FQDN. Change the google instance name to your FQDN.
  
-{{ :cloudappliance:applinstallv1901:image002.png?nolink&600 |}}+{{ :server:applinstallv1901:image002.png?nolink&600 |}}
  
-## Start SME Config Server+## Start NAAConfig Server
  
 If you are logged in as root leave root privilege and as the smeconfiguser start the configuration server by typing **smeconfigserver**. You should see a confirmation that the config server is running: If you are logged in as root leave root privilege and as the smeconfiguser start the configuration server by typing **smeconfigserver**. You should see a confirmation that the config server is running:
  
-{{ :cloudappliance:applinstallv1901:image004.png?nolink&600 |}}+{{ :server:applinstallv1901:image004.png?nolink&600 |}}
    
 Now open your favorite browser and go to Now open your favorite browser and go to
Line 157: Line 158:
 ## Configure Hostname Settings ## Configure Hostname Settings
  
-Here you only need to configure the three domain names. Click "Configuration" and then "SME Server Hostname Settings".+Here you only need to configure the three domain names. Click "Configuration" and then "NAAServer Hostname Settings".
  
 {{ :googlecloud-gettingstarted:server-hostname-settings.png?nolink&600 |}} {{ :googlecloud-gettingstarted:server-hostname-settings.png?nolink&600 |}}
Line 171: Line 172:
 Elevate to the root user by typing the following command and entering the root password when prompted. Elevate to the root user by typing the following command and entering the root password when prompted.
  
-    sudo bash+    sudo su -
  
 Note: The appliance will be inaccessible during the request which may be up to a minute. Note: The appliance will be inaccessible during the request which may be up to a minute.
Line 183: Line 184:
 Please also agree to the Terms of Service. It is not necessary to share the provided email with the Electronic Frontier Foundation. Please also agree to the Terms of Service. It is not necessary to share the provided email with the Electronic Frontier Foundation.
  
-Certbot will automatically detect what FQDNs are setup for the Enterprise File Fabric and prompt for which should be included in the certificate.+Certbot will automatically detect what FQDNs are setup for the Access Anywhere server and prompt for which should be included in the certificate.
  
     Which names would you like to activate HTTPS for?     Which names would you like to activate HTTPS for?
Line 194: Line 195:
     blank to select all options shown (Enter 'c' to cancel): 1,2,3     blank to select all options shown (Enter 'c' to cancel): 1,2,3
  
-Lastly, Certbot will prompt to disable all HTTP access.  Please select option 1 as the File Fabric already has HTTP to HTTPS redirection options configured.+Lastly, Certbot will prompt to disable all HTTP access.  Please select option 1 as the server already has HTTP to HTTPS redirection options configured.
  
     Please choose whether or not to redirect HTTP traffic to HTTPS, removing HTTP access.     Please choose whether or not to redirect HTTP traffic to HTTPS, removing HTTP access.
Line 205: Line 206:
     Select the appropriate number [1-2] then [enter] (press 'c' to cancel): 1     Select the appropriate number [1-2] then [enter] (press 'c' to cancel): 1
  
-After successful completion, the Enterprise File Fabric will automatically start using the new certificates.  These certificates will last for 90 days, so the final step is to setup automated renewal.+After successful completion, the server will automatically start using the new certificates.  These certificates will last for 90 days, so the final step is to setup automated renewal.
  
 ###  Automatically renewing the certificate ###  Automatically renewing the certificate
Line 211: Line 212:
 A Let’s Encrypt certificate is valid for 90 days, and can be automatically renewed within 30 days of expiration.  A simple cron job will run daily and handle renewals. A Let’s Encrypt certificate is valid for 90 days, and can be automatically renewed within 30 days of expiration.  A simple cron job will run daily and handle renewals.
  
-Please Note:  The File Fabric will be inaccessible during the renewal.  Please ensure that the renewal time is during off hours.  Downtime will only occur every 60 days when a renewal is required and may last up to one minute.+Please Note:  The server will be inaccessible during the renewal.  Please ensure that the renewal time is during off hours.  Downtime will only occur every 60 days when a renewal is required and may last up to one minute.
  
 While still logged in as root run the following command to add a cron job. While still logged in as root run the following command to add a cron job.
Line 217: Line 218:
     crontab -e     crontab -e
  
-In the example below the renewal attempt will process at 2:30AM.  The Enterprise File Fabric ships with the timezone set to UTC.  You can set the cron jobs to run at the time of your choosing, but do not change the File Fabric's timezone.+In the example below the renewal attempt will process at 2:30AM.  The server ships with the timezone set to UTC.  You can set the cron jobs to run at the time of your choosing, but do not change the server's timezone.
  
     30 2 * * * /bin/certbot renew >> /var/log/letsencrypt/le-renew.log     30 2 * * * /bin/certbot renew >> /var/log/letsencrypt/le-renew.log
Line 235: Line 236:
 An SMTP server is used by the appliance to send registration and notification emails to users. A daily report and error notices are also emailed to the "Notification Email". An SMTP server is used by the appliance to send registration and notification emails to users. A daily report and error notices are also emailed to the "Notification Email".
  
-See [[cloudappliance/smtp_configuration]].+See [[server/smtp_configuration]].
  
 If you do not initially configure an email server remember not to use email notifications when adding users. If you do not initially configure an email server remember not to use email notifications when adding users.
Line 268: Line 269:
 ## Review User Package (Optional) ## Review User Package (Optional)
  
-The File Fabric platform uses templates for organizations, in order for us to create our organization, we need to pick a template, before we do, let’s review.+The platform uses templates for organizations, in order for us to create our organization, we need to pick a template, before we do, let’s review.
  
 Click “User Packages” and then click the pencil to modify “Organisation Cloud 20 Users” This is a good template to start from. Scroll down to the “Extra options” section and add “Content Search Enabled” and Dropfolders. Use “Crtl-Click" to add to the selection. Click “User Packages” and then click the pencil to modify “Organisation Cloud 20 Users” This is a good template to start from. Scroll down to the “Extra options” section and add “Content Search Enabled” and Dropfolders. Use “Crtl-Click" to add to the selection.
Line 287: Line 288:
 Click Save. Click Save.
  
-{{ :cloudappliance:applinstallv1901:image014.png?nolink&400 |}}+{{ :server:applinstallv1901:image014.png?nolink&400 |}}
  
 # Setting Up an Organization # Setting Up an Organization
Line 312: Line 313:
  
 Once this is complete you can: Once this is complete you can:
-  * [[organisationcloud/usermanagement|Add users]]+  * [[admin/usermanagement|Add users]]
   * [[cloudproviders/googledocs|Link your account to Google Drive]]   * [[cloudproviders/googledocs|Link your account to Google Drive]]
-  * [[filesharing|Share files]] 
-  * ... 
  
 For more information see [[index|]] For more information see [[index|]]
Line 321: Line 320:
 # Accessing Open Source Licenses # Accessing Open Source Licenses
  
-The File Fabric includes open source components. Open source licenses can be found on the appliance in the root folder:+The server includes open source components. Open source licenses can be found on the appliance in the root folder:
  
  * Third Party Licenses including Open Source Software.pdf  * Third Party Licenses including Open Source Software.pdf
© Copyright 2024 Nasuni.