Remove outdated PDC and PDC-Updater instructions

Vagrantfile

@@ -52,7 +52,6 @@ Vagrant.configure("2") do |config|
   # Disable the default share
   config.vm.synced_folder ".", "/vagrant", disabled: true
   config.vm.network "forwarded_port", guest_ip: "0.0.0.0", guest: 5000, host: 5000
-  config.vm.network "forwarded_port", guest_ip: "0.0.0.0", guest: 2001, host: 5001
   config.vm.network "forwarded_port", guest_ip: "0.0.0.0", guest: 13747, host: 13747
   config.vm.provision "shell", inline: $script
   config.vm.provision "shell", inline: $script_services, run: "always"

docker-compose.yml

@@ -17,8 +17,6 @@ services:
     expose:
       - 2001
       - 2003
-    ports:
-      - "5001:2001"
     volumes_from:
       - base
 

docs/CONTRIBUTING.rst

@@ -53,36 +53,6 @@ refer to the `Running Tests` section first.
 We have two mechanisms for quickly setting up a development environment,
 `docker-compose` and `vagrant`.
 
-
-PDC and pdc-updater
--------------------
-
-To be able to communicate with PDC, your development instance will need to
-be able to access the URL defined in the configuration option `PDC_URL`,
-located in your local `conf/config.py`
-
-To communicate with pdc-updater, you will need to configure SSH on your host
-machine to forward remote ports from pdc-updater's devel instance, typically
-`modularity.fedorainfracloud.org`. This enables communication between PDC
-and your Module Build Service development instance.
-
-Your `ssh_config` should look like this::
-
-    Host MODULARITY-DEV
-        HostName modularity.fedorainfracloud.org
-        User fedora
-        RemoteForward 300x 127.0.0.1:5001  # x is one of 0...9
-
-The configuration above assumes that the development instance with
-pdc-updater has the following endpoints configured (typically in
-`/etc/fedmsg.d/endpoints.py`)::
-
-    endpoints={
-        "rida.local": [
-            "tcp://127.0.0.1:300%i" % i for i in range(10)
-        ],
-        ...
-
 Docker
 ------