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

Playbook example confusion? #73

Open
PhroZenOne opened this issue Nov 25, 2016 · 3 comments
Open

Playbook example confusion? #73

PhroZenOne opened this issue Nov 25, 2016 · 3 comments

Comments

@PhroZenOne
Copy link

The documentation for the installer uses JasonGiedymin.mesos so shouldn't the playbook installer use the same name as the role?

Not a big issue but just a small annoyance when testing this. :)

@lhoss
Copy link
Contributor

lhoss commented Dec 1, 2016

true!
@ernestas-poskus can you update before 0.6.0 release ?

ps: for some time we/you did not (request) update mesos_playbook_version like before:
#56 (comment)
Not sure how useful it is but I'ld either opt:

  • removing it
  • keep it, but then let's keep it up2date

@ernestas-poskus
Copy link
Member

mesos_playbook_version will remove it, anyway we don't use it as compatibility tool.

@ernestas-poskus
Copy link
Member

The documentation for the installer uses JasonGiedymin.mesos so shouldn't the playbook installer use the same name as the role?

We had plans to re-import role under/as AnsibleShipyard/ansible-mesos but I am not sure when this happens.

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

No branches or pull requests

3 participants