Pivotal Tracker: The awesome, lightweight, agile project management tool for software teams. Get your 30-day Free Trial started today! Mac OS X Dashboard Widget Pivotal Tracker Integrations.
Product Snapshot
Note: Pivotal Tracker for PCF (Pivotal Cloud Foundry) is deprecated and availability is restricted to existing customers. Contact Support for more information.
Upgrading to the Latest Version
Consider the following compatibility information before upgrading Pivotal Tracker.
Software Requirements
Infrastructure Requirements
Minimal Pivotal Tracker installation: 4GB RAM, 4.5GB ephemeral disk, 3GB persistent disk. Additional tracker-app instances: 1.5GB RAM, 1GB ephemeral disk.
Important NotesData Backups
Pivotal Tracker does not yet back up any data it stores in the MySQL or blobstore services. Please work with your Pivotal Representative to ensure that proper backup and recovery policies are in place.
Database and Blobstore Sizing
On average, an active user consumes ~23KB of DB storage and ~100KB of blobstore storage per day. An âactiveâ user is defined as one that makes changes in Pivotal Tracker on a daily basis.
Migrating from MySQL for PCF to External Database
Given the following scenario: Pivotal Tracker was configured to use MySQL for PCF, and end-users have data stored in Pivotal Tracker (projects, stories, etc.). If Pivotal Tracker is subsequently reconfigured to use an external database in Ops Manager, the MySQL data will be automatically deleted upon the next installation in Ops Manager. Be sure to migrate the existing database to the new, external database prior to doing this. Please work with your Pivotal Representative for more details.
Data Loss When Migrating from Riak CS for PCF to External Blobstore
Given the following scenario: Pivotal Tracker was configured to use Riak CS for PCF, and end-users have data stored in Pivotal Tracker (specifically, attachment uploads are stored in the blobstore). If Pivotal Tracker is subsequently reconfigured to use an external blobstore in Ops Manager, the Riak CS data will be automatically deleted upon the next installation in Ops Manager. Be sure to migrate any blobstore objects that you want to preserve to the new blobstore prior to doing this. Please work with your Pivotal Representative for more details.
Note: Riak CS for PCF is deprecated and availability is restricted to existing customers. Contact Support for more information.
Installation PrerequisitesPivotal Tracker Buildpack
To ensure the required version of Ruby is available for Pivotal Tracker, the Ruby Buildpack 1.6.8 must be uploaded to Elastic Runtime as âp-tracker_buildpackâ. After downloading the buildpack from Pivotal Network, upload it as an administrator to Elastic Runtime with the âcfâ CLI:
Refer to the Adding Buildpacks to Cloud Foundry documentation for more information. Download dropbox for mac.
Pivotal Tracker Admin User
As part of the Pivotal Tracker configuration in Ops Manager (see Pivotal Tracker Admin Email below), an Elastic Runtime user must be specified to function as the Pivotal Tracker Administrator. This user does not need administrative privileges for Elastic Runtime though.
The Pivotal Tracker Admin User must already exist in the Elastic Runtime User Database (âUAAâ). The user will not be automatically created upon installation of the Pivotal Tracker product.
NOTE: This user does not require any org or space permissions, since the account is not used for Elastic Runtime PaaS functions. This user will be granted administrative privileges only within the Pivotal Tracker application; installation of Pivotal Tracker does not modify the UAA Administrator permissions.
Pivotal Tracker Internal Support Email
As part of the Pivotal Tracker configuration in Ops Manager, an email must be specified that will serve as first-tier support for users of Pivotal Tracker. For more details see Pivotal Tracker Internal Support Email below.
Install via Ops Manager
To install Pivotal Tracker, follow the procedure for installing Ops Manager products:
Product ConfigurationAssign Networks
Assign the Network which should be used by Pivotal Tracker. See the Ops Manager Director tile configuration and documentation for more information.
Assign Availability Zones
Assign the Availability Zones which should be used by Pivotal Tracker. See the Ops Manager Director tile configuration and documentation for more information.
Pivotal Tracker ConfigSubdomain of Pivotal Tracker app
Enter the subdomain which should be used by Pivotal Tracker. This will be prepended to the System Domain configured in the Cloud Controller tab of Pivotal Elastic Runtime. For example, if the System Domain is
system.cf.biz and the subdomain is tracker , Pivotal Tracker will be available to users at tracker.system.cf.biz .
App Salt
Enter a random string. This string is used as a salt when encrypting Pivotal Tracker user passwords. This must remain the same when re-installing Pivotal Tracker and using an existing database, otherwise pre-existing user passwords will not work after re-installation.
Pivotal Tracker Admin Email
Enter the email of the Elastic Runtime user who will serve as the Pivotal Tracker Administrator.
Pivotal Tracker Internal Support Email
Enter the email address where support requests from Pivotal Tracker users will be sent. For example, this might be the email for your internal helpdesk queue. This email is displayed on the Pivotal Tracker Help page, FAQ page, and error page (when the server returns HTTP status code 500).
Number of App Instances
This specifies the number of Elastic Runtime application instances to use for Pivotal Tracker web application. Increase for more redundancy and/or scalability. E.g., if you want the Pivotal Tracker web app to remain available even if one of the web app instances is restarted, set this to 2.
Blobstore ConfigRiak CS Service
By default, Pivotal Tracker uses a Riak CS for PCF service instance to store file uploads attached to Pivotal Tracker Stories. Specify the Riak CS service plan to use when provisioning the Pivotal Tracker blobstore.
Note: Riak CS for PCF is deprecated and availability is restricted to existing customers. Contact Support for more information.
External Blobstore
If you prefer to use an external S3-compatible blobstore, enter the necessary configuration details.
WARNING: Reconfiguring Pivotal Tracker to use an external blobstore will delete any existing Pivotal Tracker Riak CS for PCF service and its associated data.
Database ConfigMySQL Service
By default, Pivotal Tracker uses a MySQL for PCF service instance to store data. Specify the MySQL service plan to use when provisioning the Pivotal Tracker database. Refer to the MySQL Service Plan documentation for more information.
External Database
If you prefer to use an external MySQL-compatible database, enter the necessary configuration details.
WARNING: Reconfiguring Pivotal Tracker to use an external database will delete any existing Pivotal Tracker MySQL for PCF service and its associated data.
Errands
The Push Pivotal Tracker errand should always be enabled when installing, upgrading, or changing configuration of the Pivotal Tracker product.
Elastic Runtime Details
Why do mac apps stay open. The Push Pivotal Tracker errand deploys and configures Pivotal Tracker apps in the Elastic Runtime PaaS.
It uses the system_services Elastic Runtime user to:
Resource Config
You may change the resource configuration, but the defaults should be sufficient for most Pivotal Tracker installations.
Architecture OverviewUsageLogging
Pivotal Tracker Web and Worker apps log via Elastic Runtime Loggregator. App voice recorder mac.
Logs for Pivotal Tracker Memcached and Solr jobs are available from the Logs Roku mirroring app mac. section in Ops Manager.
App Status
Pivotal Tracker has some pages which expose information about the status and health of the app:
Env Info![]()
Env Info Attachments
Private Install Info
Pivotal Tracker Administration
The Pivotal Tracker Admin can access various pages to control the appearance and behavior of the application. These are only accessible to an authenticated Pivotal Tracker Admin user, and can be reached via the âadminâ link in the header.
Admin FAQ
Projects
People
API Tokens
Maintenance
User AdministrationAccount Email Validation
Note that Pivotal Tracker has stricter validation rules for a âvalidâ email address when compared to the Elastic Runtime UAA. Itâs possible an Elastic Runtime user was provisioned with an email such as
user@hostname , which will fail validation when attempting to log in to Pivotal Tracker. We plan to address this limitation in a future release of Pivotal Tracker; in the meantime, the email will need to be changed by an Elastic Runtime administrator to an acceptable address such as [email protected] .
Inviting Users to a Pivotal Tracker Project
New Pivotal Tracker users can be invited via the Project âAdd/Remove Membersâ page. Users can be added to multiple projects.
Self-service Signup of New Users
Because Pivotal Tracker uses the Elastic Runtime for user authentication, the ability for end-users to self-provision their own Pivotal Tracker accounts depends on the configuration of Elastic Runtime. Specifically, refer to the Apps Manager documentation pertaining to the
ENABLE_NON_ADMIN_USER_MANAGEMENT configuration option.
Suspended Users
If a Pivotal Tracker user account is suspended by the Pivotal Tracker Administrator, the affected user will get an HTTP 500 response when trying to authenticate to Pivotal Tracker.
Password Reset
Pivotal Tracker users do not have the ability to reset their password. If a password is forgotten and needs to be reset, they will need to contact an Elastic Runtime administrator.
Support
Email [email protected] with questions or problems.
Reporting Problems
When reporting problems, please provide as much of the following information as possible or appropriate:
Migrating Data to an External Database
Outlined below are the steps to migrate Pivotal Tracker data stored in a MySQL for PCF service instanceto an external MySQL database. If any of the steps below arenât clear, please contact us for support.
Gather Prerequisite InformationMySQL for PCF Service Instance Credentials
Log in to Pivotal Tracker with the admin account and navigate to
https://<yourdomain>/private_install_info . Find the DATABASE_URL entry, which will be in the following format: mysql2://TRACKER_DB_USER:TRACKER_DB_PASSWORD@TRACKER_DB_HOST:3306/TRACKER_DB_NAME?reconnect=true . Record the database user, password, and name. For example:
From Ops Manager, click on the MySQL for PCF tile. Go to the 'Credentialsâ tab and record the VM Credentials for the MySQL Server job. Go to the 'Statusâ tab and record one of the IPs listed under the MySQL Server job. For example:
External MySQL Database Credentials
For the external database, record the hostname, port, user, password, and database name. For example:
Unmap Pivotal Tracker Route
To prevent Pivotal Tracker users from adding new data while the migration takes place, map theapplication route to a new URL that is unknown to users. For example: map
tracker.system.cf.biz totracker-maintenance.system.cf.biz . For instructions on modifying routes, refer to theAssign or Change a Route documentation.
Export Data to Backup File
Run the following command to export Pivotal Tracker data to the local file
/tmp/tracker_db_backup.sql :
You will be prompted for the credential MYSQL_VM_PASSWORD, followed by TRACKER_DB_PASSWORD. For example:
Verify the data was exported by checking the contents of
/tmp/tracker_db_backup.sql .
Import Data to External Database
Run the following command to import the Pivotal Tracker data into the external database:
Note: There is no space between
-p and EXTERNAL_DB_PASSWORD. For example:
When the import is complete, log in to the external database and verify the data is populated. For example:
Configure Pivotal Tracker to Use External Database
From Ops Manager, click on the Pivotal Tracker tile and choose the Database Config section. Select theoption to use an External Database and fill in the required information. Save the changes.
Ensure that the Push Pivotal Tracker errand is enabled in the Errands section.
Return to the Ops Manager Installation Dashboard and click the Apply Changes button.Note: After applying changes, the existing Pivotal Tracker database in MySQL for PCFwill be destroyed.
Post-Installation Steps
Log in to Pivotal Tracker and verify the data was migrated (users, projects, stories).
Delete the un-needed maintenance route; the original route (e.g.
tracker.system.cf.biz ) was re-mapped as part ofthe Push Pivotal Tracker errand.
Pivotal Tracker for Avaya Cloud Office
Bots & Notifications Collaboration Developer Tools Productivity Message More
Receive notifications from Pivotal Tracker activities to the team messaging conversation of your choice.
Pivotal Tracker is an agile project management tool that shows software teams their work in progress and allows them to track upcoming milestones. Get instant post notifications in the team messaging app any time a story activity is triggered in Pivotal Tracker.
Why Pivotal Tracker for RingCentral app?
Productive team collaboration
Quickly and easily share story activity with any team or direct message conversation within the team messaging app.
![]()
Streamlined workflows
Receive post notifications from Pivotal Tracker and tag co-workers directly from within the team messaging app, consolidating your work environment into a single view.
Reduce email and app overload
Pull updates into the team messaging app instead of receiving multiple notification emails from Pivotal Tracker.
June 2016
Pivotal Tracker TutorialSystem requirementsPivotal Tracker Reviews
Comments are closed.
|
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |