Configuring Pivotal Platform Dev (Legacy)

Note: This topic applies only to Pivotal Platform Dev v0.30 or earlier. If you are using a later version of Pivotal Platform Dev, see Configuring Pivotal Platform Dev.

Pivotal Platform Dev supports several different configurations. This topic describes how to start Pivotal Platform Dev with specific memory usage, core count usage, domain, IP address, and Pivotal Platform services, among others. It also describes ease-of-use functionality, including automatically targeting Pivotal Platform Dev and trusting Pivotal Platform Dev certificates.

Configure Pivotal Platform Dev

The cf dev start command supports the following configuration-specific flags at start up:

flag description
-c NUMBER-OF-CORES Specify the number of processor cores used by VM. Default: Number of physical cores.
-d DOMAIN Specify the domain that the Pivotal Platform Dev VM occupies.
-i IP-ADDRESS Specify the IP address that the Pivotal Platform Dev VM occupies.
-k Import VM certificates into host’s trusted certificate store.
-m MEMORY-IN-MB Specify memory to allocate for VM. Default: Half of total memory, with a maximum of 4 GB, or 8 GB with SCS.
-r REGISTRY-1,REGISTRY-2,... Specify Docker registries that Pivotal Platform Dev uses without SSL validation. Use host:port format.
-s SERVICE-1,SERVICE-2,... Specify the services started with Pivotal Platform Dev. Options: redis, rabbitmq, spring-cloud-services (scs), default, all, none. Default: redis, rabbitmq. (MySQL is always available and cannot be disabled.)
-t Specify to perform cf login to Pivotal Platform Dev after starting, as the ‘user’ user.

Domain and IP Address

The -d and -i flags specify a custom domain and IP address that Pivotal Platform Dev uses. Specify a domain and IP address if you have your own domain that you want to access using Pivotal Platform Dev.

If you specify an IP address without a domain, the domain is assumed to be IP-ADDRESS.xip.io.

If you specify a domain, you must also specify an IP address unless the domain is a standard Pivotal Platform Dev domain. For example, local.pcfdev.io and local2.pcfdev.io are valid domains.

When you specify both a domain and IP address, no validation occurs.

The following are examples of valid IP address and domain configurations for Pivotal Platform Dev:

  • cf dev start -i 192.168.54.54
  • cf dev start -d local3.pcfdev.io
  • cf dev start -i 192.168.54.54 -d example.com

However, the following is not a valid configuration:

  • cf dev start -d example.com

Insecure Docker Registries

Pivotal Platform Dev allows apps to be pushed from Docker images. By default, these images must be hosted on Docker Hub. The -r flag allows you to specify Docker registries that Pivotal Platform Dev should allow you to push from, even if those registries do not have valid SSL certificates.

For example, to start Pivotal Platform Dev and push an app using an existing insecure Docker registry on your host running on port 5000, run:

cf dev start -r host.pcfdev.io:5000
cf dev target
cf push -o host.pcfdev.io:5000/repository/image

Service Brokers

By default, Pivotal Platform Dev starts with the MySQL, Redis, and RabbitMQ service brokers running. The service brokers that are started with Pivotal Platform Dev can be changed with the -s flag.

To start Pivotal Platform Dev with all of the available service brokers, including Spring Cloud Services (SCS):

  1. Run:

    cf dev start -s all
    

To start Pivotal Platform Dev with no additional service brokers, except for the mandatory service broker, MySQL:

  1. Run:

    cf dev start -s none
    

To start Pivotal Platform Dev with Redis and SCS:

  1. Run:

    cf dev start -s redis,scs
    

Target Pivotal Platform Dev

To perform a cf target on your running Pivotal Platform Dev instance, regardless of the domain is it currently configured to use:

  1. Run:

    cf dev target
    

The cf dev target command works if the Pivotal Platform domain is the default local.pcfdev.io or a custom value, such as cf dev start -d pcfdev.example.com. Running cf dev target performs cf login as the user user into the 'pcfdev-org’ org and 'pcfdev-space’ space. The -t option to cf dev start also performs this operation following the provisioning of the VM.

Trust Pivotal Platform Dev

Provisioning dynamically creates self-signed certificates used within its components. However, this results in various SSL validation warnings both from the Cloud Foundry Command Line interface (cf CLI), and when using Apps Manager in a browser. To remove these SSL validation warning errors, you can insert this self-signed certificate into your OS certificate store.

To insert a self-signed certificate into your OS certificate store:

  1. Run:

    cf dev trust
    

Note: Due to the nature of this operation, you may need to provide your system password to successfully insert the certificate.

After running cf dev trust, you can log in to Pivotal Platform Dev without skipping SSL validation.

To log in without skipping SSL validation:

  1. Run:

    cf login -a https://api.local.pcfdev.io --skip-ssl-validation
    

Adding the -k option to cf dev start also performs this operation following the provisioning of the VM.

To remove these certificates from your certificate store:

  1. Run:

    cf dev untrust
    

These certificates are automatically removed when you run cf dev destroy.

Note: If you run cf dev destroy and are prompted to enter your password, the plugin is attempting to remove Pivotal Platform Dev-specific certificates from your certificate store.

The following table shows conditions where cf dev trust removes SSL validation warnings:

OS cf CLI Chrome Firefox Internet Explorer
Mac X N/A
Windows X
Linux X X N/A