Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Improve docs for MLflow Project execution on Kubernetes #1566

Merged
merged 19 commits into from Jul 16, 2019
Merged

Improve docs for MLflow Project execution on Kubernetes #1566

merged 19 commits into from Jul 16, 2019

Conversation

ghost
Copy link

@ghost ghost commented Jul 10, 2019

What changes are proposed in this pull request?

This PR improves the documentation for Kubernetes-backed execution of MLflow Projects. It also depends on #1574; the diff will shrink after #1574 is merged.

How is this patch tested?

Manual generation of docs

Release Notes

This is part of the Kubernetes projects feature and should be included under the same release notes item!

Is this a user-facing change?

  • No. You can skip the rest of this section.
  • Yes. Give a description of this change to be included in the release notes for MLflow users.

What component(s) does this PR affect?

  • UI
  • CLI
  • API
  • REST-API
  • Examples
  • Docs
  • Tracking
  • Projects
  • Artifacts
  • Models
  • Scoring
  • Serving
  • R
  • Java
  • Python

How should the PR be classified in the release notes? Choose one:

  • rn/breaking-change - The PR will be mentioned in the "Breaking Changes" section
  • rn/none - No description will be included. The PR will be mentioned only by the PR number in the "Small Bugfixes and Documentation Updates" section
  • rn/feature - A new user-facing feature worth mentioning in the release notes
  • rn/bug-fix - A user-facing bug fix worth mentioning in the release notes
  • rn/documentation - A user-facing documentation change worth mentioning in the release notes

@ghost ghost requested a review from dbczumar July 10, 2019 22:43
@dbczumar dbczumar changed the title Edit Kub proj docs Improve docs for MLflow Project execution on Kubernetes Jul 12, 2019

You can run your MLflow Project on Kubernetes by following these steps:

1. First, add a Docker environment to your MLflow Project, if one does not already exist. For
Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@dbczumar Could you remove the First, Then, and Finally from the steps 1, 2, and 4. They are really not needed since you are using an ordered list.

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Done! Thanks

with the ``kubernetes_backend.json`` and ``kubernetes_job_template.yaml`` files.

Note that the ``container.name``, ``container.image``, and ``container.command`` fields are only
replaced for the *first* container defined in the Job Spec. All subsequent container definitions
Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Note that the container.name -> The container.name

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Done!


Have in mind that mlflow overwrites the folowing attributes in the job yaml file so it can handle jobs creation and monitor its status:
Run a Project on Kubernetes
^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Run a Project -> Run an MLflow Project

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Fixed here and for Databricks (Run an MLflow Project on Databricks)

@@ -349,103 +349,170 @@ useful if you quickly want to test a project in your existing shell environment.

.. _databricks_execution:

Run a project on Databricks
Run a Project on Databricks
^^^^^^^^^^^^^^^^^^^^^^^^^^^
Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Run a Project -> Run an MLflow Project

^^^^^^^^^^^^^^^^^^^^^^^^^^^

Support for running projects remotely on Databricks is in public preview. To use this feature, you must have an enterprise Databricks account (Community Edition is not supported) and you must have set up the `Databricks CLI <https://github.com/databricks/databricks-cli>`_. Find more detailed instructions in the Databricks docs (`Azure Databricks <https://docs.databricks.com/applications/mlflow/index.html>`_, `Databricks on AWS <https://docs.databricks.com/applications/mlflow/index.html>`_). A brief overview of how to use the feature is as follows:
You can run MLflow projects remotely on Databricks. To use this feature, you must have an enterprise
Copy link
Author

@ghost ghost Jul 12, 2019

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We should be consistent how we spell MLflow Projects. At the top of this page it says:

At the core, MLflow Projects

So I think it should be spelled that way throughout.

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Fixed! Thanks for catching this

command: ["cmd"]
- name: "{replaced with MLflow Project name}"
image: "{replaced with URI of Docker image created during Project execution}"
command: [{replaced with MLflow Project entry point command}]
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Does this example work out of the box? I think this needs to be a string right?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It does, but I've changed it to a string with braces based on our discussion. I also updated the template in examples/docker

@andrewmchen
Copy link
Contributor

LGTM as well.

@dbczumar dbczumar merged commit f2d13fc into mlflow:master Jul 16, 2019
smurching pushed a commit that referenced this pull request Jul 16, 2019
* Edit Kub proj docs.

* Fix command.

* Doc progress

* Attributes

* Image name > repo uri

* Image name > repo uri

* Tests fix

* Lint

* Fix tests

* Job template docs

* Project docs

* Test fix

* Add missing word 'launch'

* Address review comments
@ghost ghost deleted the kub-proj-docs branch November 12, 2019 17:37
avflor pushed a commit to avflor/mlflow that referenced this pull request Aug 22, 2020
* Edit Kub proj docs.

* Fix command.

* Doc progress

* Attributes

* Image name > repo uri

* Image name > repo uri

* Tests fix

* Lint

* Fix tests

* Job template docs

* Project docs

* Test fix

* Add missing word 'launch'

* Address review comments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants