RPM Support

I took a quick stab at adding a similar block to install the pulp_file plugin into its own VM:

diff --git a/ansible/roles/dev/tasks/main.yml b/ansible/roles/dev/tasks/main.yml
index eab0c9b..c2c6a06 100644
--- a/ansible/roles/dev/tasks/main.yml
+++ b/ansible/roles/dev/tasks/main.yml
@@ -153,6 +153,20 @@
       - pulp_file
   when: "{{ [item] | issubset(pulp_available_plugins) }}"

+# very similar to the previous task, with the same limitations based on the method of
+# development installs for pulp 3 plugins being undefined, except this installs each plugin package
+# in its own virtualenv so it can be worked on in isolation
+- name: Install Plugin packages into Plugin Virtualenvs
+  command: "{{ pulp_venv_dir }}/{{ item }}/bin/python setup.py develop"
+  args:
+    chdir: "{{ pulp_devel_dir }}/{{ item }}"
+  # If we stick with running setup.py develop for all plugins, we'd want to do it for all available
+  # plugins. For now, it only works with pulp_file
+  # with_items: "{{ pulp_available_plugins }}"
+  with_items:
+      - pulp_file
+  when: "{{ [item] | issubset(pulp_available_plugins) }}"
+
 - block:
   - name: Install crane config
     template:

While this did work, the platform code didn't appear to "see" the pulp.plugin entry point provided by pulp_file, so the app didn't get loaded by Django. I expect I'm missing something simple, but at the moment I'm not sure what.

@dkliban and I were talking about the vagrant environment being slimmed down to just include core by default and the developer installs their own plugin on top. We need to make that easy.

I think in terms of plugin installation methods there are three options.

a) python setup.py develop
b) python setup.py install
c) an rpm based installation of the plugin

I think we should never have plugins provide a pulp-dev.py