Stage 6 - Install Syndeia Cloud 3.5 in Upgrade Mode

Install Syndeia Cloud (SC) 3.5 in upgrade mode.

Note:  Syndeia Cloud can be deployed on a different machine VS Cassandra but these steps will focus on a single-node deployment.

• Successful Completion of Previous Stages

• Complied with any new Syndeia Cloud 3.5 Requirements i.e. (Open | Oracle)JDK / JRE, CPU cores, memory, FS selection, versions required, etc. in Deployment.

• Firewall Settings: If using a firewall, and you wish to remotely monitor via JMX, ensure the following new port(s) are accessible from where you will be running monitoring from, for each integration service (consult your local network admin if required).

  • sc-collaborator: 31118

  • sc-restful: 31119

  • sc-volta: 31117

Follow the below steps for installing, configuring and starting Syndeia Cloud (SC).

Step 1 - SSH to your designated Syndeia Cloud server.

Step 2 - Run umask to ensure your user umask is set to 0002 and root's umask is set to 0022. If not, then run the following commands.

Step 3 - cd into the bin directory of where you extracted the Syndeia Cloud install media.  

Step 4 - Run the install script with the upgrade and version switches, ie: 

Step 5 - Authenticate with super.user via the steps shown in API - Swagger doc | Using Syndeia Cloud local accountPreview

Step 6 - Run the HTTP(S) PUT /super.user call at http(s)://mySCserver.mydomain.tld:9000|9443/docs/swagger-ui/index.html?url=/assets/swagger/openapi.json#/User/updateSuperUser by clicking “Try it out” then “Execute” as shown below.

Open

Open

You should get an HTTP 200 response similar to the below.

Open

Once the above has been done you can add this permission as needed by editing any other user(s) via the UI at http(s)://mySCserver.mydomain.tld:9000|9443/user-management.

Open

See Managing Syndeia's Users with the Web Admin Page | ManagingSyndeia'sUserswiththeWebAdminPage ToUpdatepermissionsPreview for more information on how to edit user(s) permission(s).

1. Ensure no errors were reported during setup & new RESTful permission was added to super.user.

2. Make sure sc-store service’s application.conf at /opt/icx/syndeia-cloud-current/store-impl-3.5-SP1/conf/application.conf contains the following performance tuning enhancements on ~L95:

   cassandra-query-journal { refresh-interval = 25ms # added events-by-tag nesting during lagom upgrade to 1.6.5 (to cater to akka persistence cassandra migration to 0.80) # https://doc.akka.io/docs/akka-persistence-cassandra/0.101/migrations.html events-by-tag { # Turn off the eventual consistency delay eventual-consistency-delay = 50ms # Turn on event by persistence id tracking, this timeout is the maximum amount of time that akka-persistence-cassandra will hold off publishing an event when missed events are detected # changed name from delayed-event-timeout to gap-timeout during lagom upgrade to 1.6.5 (to cater to akka persistence cassandra migration to 0.80) # https://doc.akka.io/docs/akka-persistence-cassandra/0.101/migrations.html gap-timeout = 30s flush-interval = 25ms first-time-bucket = "20221101T00:00" } }

   If not, add them.

3. Verify all SC + infra services are up and running without any errors.

   sudo systemctl status cassandra janusgraph zookeeper kafka sc-*

4. Open a web browser and login to the SC web dashboard - http://mySCserver.domain.tld:9000 (or https://mySCserver.domain.tld:9443 if HTTPS was enabled and using the default port)

5. Ensure the bar graph renders and you see 20 Repository Types in the lower bar graph ( SC 3.5 adds two new repository types):

   Open

   

For the next set of steps, we will be upgrading each infrastructure component in turn so stop all SC + Kafka + Zookeeper + Janusgraph + Cassandra services (in that order).