Mailing-List: contact dev-help@aurora.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@aurora.apache.org
Date: Wed, 22 Jul 2015 20:18:49 +0000 (UTC)
From: meghdoot bhattacharya <meghdoot_b@yahoo.com.INVALID>
Reply-To: meghdoot bhattacharya <meghdoot_b@yahoo.com>
To: "dev@aurora.apache.org" <dev@aurora.apache.org>
Message-ID: <191515313.705024.1437596329186.JavaMail.yahoo@mail.yahoo.com>
In-Reply-To: 
 <CAAATh-b7Zm9wm9e4eY56kZyP+t-2A-4bSyNxqHOCPN2VOdcCEg@mail.gmail.com>
References: 
 <CAAATh-b7Zm9wm9e4eY56kZyP+t-2A-4bSyNxqHOCPN2VOdcCEg@mail.gmail.com>
Subject: Re: http auth and aurora tutorial
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_Part_705023_1254048136.1437596329180"

------=_Part_705023_1254048136.1437596329180
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Kevin what is the fix for this?Not sure what is causing this but we are not=
icing this as well and the odd thing is some of us has 192.X.X.X registered=
 and but we are finding cases where 127.0.1.1 is there as well.
Thx
      From: Kevin Sweeney <kevints@apache.org>
 To: dev@aurora.apache.org=20
 Sent: Monday, July 6, 2015 6:23 PM
 Subject: Re: http auth and aurora tutorial
  =20
I just reproduced this as well - the issue appears to be that the scheduler
is registering in ZooKeeper with an IP address of 127.0.1.1, but the netrc
file is configured for 192.168.33.7.

vagrant@aurora:~$ PEX_INTERPRETER=3D1 aurora
Python 2.7.6 (default, Jun 22 2015, 17:58:13)
[GCC 4.8.2] on linux2
Type "help", "copyright", "credits" or "license" for more information.
(InteractiveConsole)
>>> from kazoo.client import KazooClient
>>> from twitter.common.zookeeper.serverset import get_serverset_hosts,
ServiceInstance
>>> client =3D KazooClient()
>>> client.start()
>>> hosts =3D get_serverset_hosts('/aurora/scheduler', client)
>>> [ServiceInstance.to_dict(host) for host in hosts]
[{'status': 'ALIVE', 'additionalEndpoints': {u'http': {'host': u'*127.0.1.1=
*',
'port': 8081}}, 'serviceEndpoint': {'host': u'*127.0.1.1*', 'port': 8081}}]


On Mon, Jul 6, 2015 at 10:43 AM, Bill Farner <wfarner@apache.org> wrote:

> 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].=C2=A0 This is certainly confusing when the clusters.json
> plainly suggests that there is no auth happening [3].=C2=A0 This is the r=
esult
> 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/14e7b84f4303968029c3803e9b096908f34=
99d57/docs/tutorial.md#creating-the-job
> [2]
>
> https://github.com/apache/aurora/blob/be75c36f6ce0b2ca6cc7a910b64e2bb9ca4=
0953d/examples/vagrant/provision-dev-cluster.sh#L92-L99
> [3]
>
> https://github.com/apache/aurora/blob/056c35b169874023760edca4fcc222c1ad2=
1d8b1/examples/vagrant/clusters.json#L5
>
> -=3DBill
>
> On Sun, Jul 5, 2015 at 6:01 PM, Mauricio Garavaglia <
> mauriciogaravaglia@gmail.com> wrote:
>
> > Hi,
> > the vagrant setup seems to enable http_authentication_mechanism=3DBASIC=
 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?
> >
>


------=_Part_705023_1254048136.1437596329180--