Deploy the Enhanced Studio Pack on Azure

Now that you have selected server parameters you can configure Perforce tools.

Helix Core Configuration

Define how your Helix Core server will be setup.

1. To set up SSH, upload an existing key or create a new one. Certain admin actions will require SSH access. For example: operating system updates, product updates, reviewing logs, or expanding volume size. Daily use will not require SSH.
2. The remaining fields in this section can be left as the default. These values are intended to get you started. Depending on how you are utilizing the software and your specific use cases, you may need to increase or decrease. File size and number of files are the largest contributors.
   If you know how much data you are using today, you may consider adjusting your Depot Volume Size to 1.5x your current data usage.

Hansoft Configuration (Optional)

1. To use the Hansoft project management tool, select ‘True’
2. Hansoft will be deployed to your Azure environment on its own server. We do not recommend adjusting resource defaults for initial setup.

Not sure you will use Hansoft right away? Deploy now and pause the Hansoft server until you are ready to start using it. This will reduce your cloud operating costs.

Helix Swarm Configuration (Optional)

1. To use Helix Swarm — the code review tool for Helix Core — select ‘True’
2. Helix Swarm will be deployed to your Azure environment on its own server. We do not recommend adjusting resource defaults for initial setup.

Workstation Configuration (Optional)

The virtual Windows workstation contains all the Perforce clients — Helix Sync, Helix Visual Client (P4V) — pre-configured. It also contains additional 3rd party tools and other powerful resources.

Instance size and your use of the software on the workstation will influence the cost of the server needed to support it.

1. To use a pre-configured Windows Workstation, select ‘True’
2. Select Resources:
   • Instance types supported are NV-series, NVv3-series,  NVv4-series. Prices will vary based on your selection.
   • Root volume size is highly dependent on your use case. How much data will you check out? How much hard drive space do you want? How much data will be stored?
   • These defaults will be good to get started and can be adjusted at any time.

Review + Create

Once you have defined all parameters, click on the last tab, Review + create.

Azure will validate your parameters and you will see the message “Validation Passed”.  To initiate your deployment, click the Create button.  We recommend keeping your deployment status page open to aid with post deployment configuration. 

Estimate your monthly expense with the Azure calculator.

Having issues deploying your instance on Azure? Email us >> [email protected]

After your Perforce deployment is complete, you will be on the Overview tab of your Parent Deployment. Please note the Parent Deployment will be named ‘perforce.perforce-enhanced-studio-pack-##############’, the hashes will be unique to your deployment.

From the sub-navigation of the Parent Deployment, click on Outputs.

You are now located on the Outputs tab of the Parent Deployment. All outputs needed to connect to Helix Core, Helix Swarm, Hansoft and the Windows Workstation instances will be located here. 

If you navigated away from the deployment progress page you can get to the outputs tab by following these steps:

1. From your Azure account, search for Resource Groups. Click on Resource Groups.
2. Click on the name of the Resource Group you created for your Perforce deployment. This will be a unique name you defined when filling out the deployment parameters. 

3. From the selected Resource Group sub-navigation menu, select Deployments.

4. Here you will see a list of all the Deployments associated with this Resource Group. Scroll to the bottom and click on the Deployment named ‘perforce.perforce-enhanced-studio-pack-#########’, the hashes will be unique to your deployment.

5. You are now located on the Parent Deployment page. Click on Outputs in the sub-nav.

Please take note of the following key outputs:

1. helixCoreInstanceID
2. p4CommitPublicIP
3. hansoftPublicIP
4. swarmPublicIP
5. PerforceWorkstationPublicIP
6. PerforceWorkstationInstanceID

These will be used in future sections.

Refer to section Find Your Deployment Outputs for details on where to find these values.

Helix Core Credentials

Use the following connection details for connecting to Helix Core using Helix Visual Client (P4V) and the Helix Core Command-line (p4 CLI).

Server = ssl:<p4CommitPublicIP>:1666
User = perforce
Password = <helixCoreInstanceID>

<p4CommitPublicIP> and <helixCoreInstanceID> correspond to Azure Deployment outputs found in the Find Your Deployment Outputs section.

Example:
Server = ssl:52.186.76.48:1666
User = perforce
Password = eee0c937-a98f-4f98-91ee-012432aed840

Windows Workstation Credentials

Username: perforce
Password: <PerforceWorkstationInstanceID>

Example:
Username: perforce
Password: aa127d50-368d-11ec-a674-52540008e434

1. Download Helix Visual Client (P4V).
2. Enter in the connection details on the Remote Server tab:
   Server = ssl:<p4CommitPublicIP>:1666
   User = perforce
   Password = <helixCoreInstanceID>
3. Click OK.
4. Establish connection by clicking the checkbox “Trust this fingerprint” and click Connect.
5. In the displayed password prompt, enter the password for the perforce user, which defaults to <HelixCoreInstanceID> output value.
    
6. For more information, see the P4V User Guide.

Note: If you are connecting from the Perforce Windows Workstation substitute <P4CommitPublicIP> with <P4CommitPrivateIP>.

1. Download Helix Sync.
2. Enter in the connection details:
   Server = ssl:<p4CommitPublicIP>:1666
   Username: perforce
   Password = <helixCoreInstanceID>
3. Click Connect.
4. For more information, see the Helix Sync User Guide.

​​​​​​​

Note: If you are connecting from the Perforce Windows Workstation substitute <P4CommitPublicIP> with <P4CommitPrivateIP>.

1. Open your browser.
2. Navigate to http://<SwarmPublicIP>
3. Login using the following details:
   Username: perforce
   Password: <helixCoreInstanceID>
4. Click Log in.
5. For more information, see the Helix Swarm User Guide.

Note: If you are connecting from the Perforce Windows Workstation substitute <SwarmPublicIP> with <swarmPrivateIP>.

1. Download the Hansoft client.
2. Open the Hansoft Client.
3. Login using the following details:
4. Hansoft Server: <HansoftPublicIP>
5. Port: 50256
6. Click Connect.
7. For more information, see the Hansoft User Guide.
8. To connect to the Hansoft server using the Hansoft Server Administrator application, no username is required. The password is the output value of <HansoftInstanceID>.

Note: If you are connecting from the Perforce Windows Workstation substitute <HansoftPublicIP> with <hansoftPrivateIP>.

After the deployment has completed, you can connect to your Windows Workstation via RDP:

1. Open your RDP tool of choice.
2. Enter the server you will connect to – value of the <PerforceWorkstationPublicIP>. Click Connect.
3. Enter your Perforce Workstation Credentials
   Username: perforce
   Password: Value of PerforceWorkstationInstanceID (See section Your Credentials)

Once you are logged in, a powershell window displays. This window will close when the post-deployment configuration is complete.

Once the post-deployment configuration is complete, the Helix Core password prompt will display. Enter the password for the Helix Core Perforce user. See section Your Credentials to determine which deployment output value to use.

1. Open Helix Visual Client (P4V) from the desktop icon. In the Open Connection dialog, leave the defaults. Click Okay.

If you have users who will be connecting to Perforce from a different IP address than the one used to deploy the Enhanced Studio Pack, you need to update your firewall rules to grant them access. 

1. Follow Azure’s instructions on creating a security rule in your network security group.
2. Input a rule for each user/IP address:
   • Each user will need to provide you with their IP address in IPv4 format.
   • The table below provides the port number for each product the user may need access to:
      

     Product	Service Type	Port Number
     Helix Core	TCP	1666
     Helix Swarm	HTTP	80
     Hansoft	TCP	52560
     Windows Workstation	TCP	3389

Username: centos
Server: <P4CommitPublicIP>

Example command:
ssh [email protected]

Now you are logged in as the centos user. To perform any Helix Core administration task, switch to the Perforce user, and log into Helix Core with the following commands:

sudo su - perforce
p4login -v 1

You are now logged into Helix Core (P4D) as the perforce user. You have the P4 CLI binaries in your $PATH

To perform OS administration, you can become root with the following command:

sudo -s

Support can be reached by emailing: [email protected]

When emailing support, please include details about your Helix Core server configuration.

1. Go into Helix Visual Client P4V.
2. Click Help.
3. Click System Info.
4. Copy and paste the contents of System Info into your email to support.