Page History
...
Switch to the region intended deploy Partek Flow. This tutorial uses US East (N. Virginia) as an example.
...
Purchasing option: Leave Request Spot instances unchecked. This is relevant for cost-minimization of Partek Flow cluster deployments.
Network: If you do not have a VPC already created for Partek Flow, click Create new VPC. This will open a new browser tab for VPC management.
...
DNS hostname: change this to yes as internal dns resolution may be necessary depending on the Partek Flow deployment
Once created, the new Flow-VPC will appear in the list of available VPCs. The VPC needs additional configuration for external access. To continue, right click on Flow-VPC and select Edit DNS Resolution, select Yes, and then Save. Next, right click the Flow-VPC and select Edit DNS Hostnames, select Yes, then Save.
...
IAM role: None.
Note: For multi-node Partek Flow deployments or instances where you would like Partek to manage AWS resources on your behalf, please see Partek AWS support and set up an IAM role for your Partek Flow EC2 instance. In most cases a specialized IAM role is unnecessary and we only need instance ssh keys.
...
Description: Security group for Partek Flow server
Add the following rules:
...
Note: It is recommended to restrict Source to just those that need access to Partek Flow.
Click Review and Launch
...
The new instance will now boot. Use the left navigation bar and click on Instances. Click the pencil icon and assign the instance the name Partek Flow Server
Enabling External access to the Partek Flow EC2 Instance
...
Attach, format, and move the ubuntu home directory onto the large ST1 EBS volume. All Partek Flow data will live in this volume. Consult the AWS EC2 documentation for further information about attaching EBS volumes to your instance.
...
Disconnect the ssh session, then log in again to make sure all is well
Installing Partek Flow on a New EC2 instance
Note: For additional information about Partek Flow installations, see our generic Installation Guide
...
Install required packages for Partek Flow:
$ sudo apt-get update
$ sudo apt-get install python perl make gcc g++ zlib1g libbz2-1.0 libstdc++6 libgcc1 libncurses5 libsqlite3-0 libfreetype6 libpng12-0 zip unzip libgomp1 libxrender1 libxtst6 libxi6 debconf
Install Partek Flow:
Note: Make sure you are running as the ubuntu user.
$ cd (we will install Partek Flow to ubuntu's home directory)
...
$ ./partek_flow/start_flow.sh
Partek Flow has finished loading when you see INFO: Server startup in xxxxxxx ms in the partek_flow/logs/catalina.out log file. This takes ~30 seconds.
Open Partek Flow with a web browser: http://elastic.ip:8080/
Enter license key
Set up the Partek Flow admin account
Leave the library file directory at its default location and check that the free space listed for this directory is consistent with what was allocated for the ST1 EBS volume.
Done! Partek Flow is ready to use.
| Anchor | ||||
|---|---|---|---|---|
|
...
T-class servers, although cheap, may slow responsiveness for the Partek Flow server and generally do not provide sufficient resources.
...
Note that EBS volumes can be grown or performance characteristics changed. To minimize costs, start with a smaller EBS volume allocation of 0.5 - 2 TB as most mature Partek Flow installations generate roughly this amount of data. When necessary, the EBS volume and the underlying file system can be grown on-line (making ext4 a good choice). Shrinking is also possible, but may require the Partek Flow server to be off-line.
...
Overview
Content Tools