Updates to Dockerfile to build fluence

[vsoch]

@cmisale and @milroy - the Dockerfile is building! I also am trying to reproduce what I found for docs in the README, and add to them more of a dummy example.

It looks like there have been some changes with the scheduler-plugins helm charts - it installs to the default namespace and not one called scheduler-plugins as the README mentioned. I tried to move forward with this change, and although I've been able to make the deployment and apply the needed configs (rbacs and config maps) it's not clear to me what step is needed so the scheduler plugin framework registers Fluence as a scheduler. But I think we are close - I've included all my steps and new files in the README and examples folder. If you have insights to how this works please share, otherwise I'll start reading about how these plugin schedulers work and see if I can figure it out.

Summary of questions:

• Namespaces - should we be installing the charts still to a scheduler-plugins namespace, installing fluence to default, or something else?
• How to properly register the fluence deployment with the cluster?
• Where does the quay.io/cmisale/fluence:upstream image come from? It's a second image in the deployment.

---

Update - example is working!

The only question remaining is:

• Where does the quay.io/cmisale/fluence:upstream image come from? It's a second image in the deployment.

We should know how to build that / where it comes from.

---

Update: All is good! This is ready for review.

[milroy]

LGTM! I'll let @cmisale sign off on this as she's more familiar with the helm deployment and dockerfile.