I got as far as creating a job following the tutorial [1] and didn't encounter any issues.
The client is configured for basic auth, just in a non-obvious way with a .netrc file [2]. This is certainly confusing when the clusters.json plainly suggests that there is no auth happening [3]. This is the result of our move to push authentication down from the application layer, which is what the client-side clusters.json entry is for. Hopefully this clear things up, and if you're encountering any errors you think might be related please report back! [1] https://github.com/apache/aurora/blob/14e7b84f4303968029c3803e9b096908f3499d57/docs/tutorial.md#creating-the-job [2] https://github.com/apache/aurora/blob/be75c36f6ce0b2ca6cc7a910b64e2bb9ca40953d/examples/vagrant/provision-dev-cluster.sh#L92-L99 [3] https://github.com/apache/aurora/blob/056c35b169874023760edca4fcc222c1ad21d8b1/examples/vagrant/clusters.json#L5 -=Bill On Sun, Jul 5, 2015 at 6:01 PM, Mauricio Garavaglia < [email protected]> wrote: > Hi, > the vagrant setup seems to enable http_authentication_mechanism=BASIC in > /examples/vagrant/upstart/aurora-scheduler.conf but, AFAIK, the aurora CLI > client doesn't support authentication yet. This affects the tutorial since > this is not considered and is not pretty obvious why it doesn't work. Would > it make sense to get rid of the authentication in the upstart script? >
