Thursday, 2015-09-17

adam_ggate-functional-dsvm-akandaSUCCESS in 32m 06s00:38
*** elo has quit IRC00:45
davidlenwellsweet!00:46
sarobawesome01:08
*** elo has joined #akanda01:42
*** elo has quit IRC01:43
*** elo has joined #akanda06:28
*** elo has quit IRC07:22
*** elo has joined #akanda07:32
*** elo has quit IRC08:23
ryanpetrellofound an akanda-rug bug from a customer13:08
ryanpetrellohttps://bugs.launchpad.net/akanda/+bug/149684813:08
openstackLaunchpad bug 1496848 in akanda "Router hostnames need validation" [Undecided,New] - Assigned to Ryan Petrello (ryan-petrello)13:08
ryanpetrelloworking on a patch on our end and one for upstream13:08
*** openstackgerrit has quit IRC13:31
*** openstackgerrit has joined #akanda13:31
rodsadam_g you around?14:29
*** elo has joined #akanda15:15
*** elo has quit IRC15:16
*** elo has joined #akanda15:18
*** puranamr has joined #akanda15:25
markmcclainryanpetrello: what kind of problem have you see with the hostname?15:40
markmcclainI'm guessing teh tenant changed theirs?15:40
ryanpetrelloname your router: marks_router15:40
ryanpetrelloyep15:40
markmcclainah... ok15:40
ryanpetrelloI'm going to change the code to just normalize it to ak-<tenant>15:40
ryanpetrelloif that makes sense to you15:40
ryanpetrelloand not actually use the router name15:41
markmcclainyeah.. the uuid makes sense15:41
ryanpetrellowe can rely on that value to be hostname-valid15:41
ryanpetrellok15:41
ryanpetrelloworking on a review for our repo and will open an openstack.org review15:41
markmcclainit's not like the hostname is visible to anyone except admins15:41
markmcclaink15:41
ryanpetrelloright15:42
ryanpetrellowe really only added it for convenience when debugging a router15:42
markmcclainyeah15:42
ryanpetrelloso did the neutron pecan merge not happen?15:44
*** elo has quit IRC15:48
*** puranamr has quit IRC15:51
ryanpetrelloman, the unit tests on master take a *really* long time to run16:12
openstackgerritRyan Petrello proposed stackforge/akanda-rug: Use a standard hostname to prevent setting invalid hostnames.  https://review.openstack.org/22480816:14
*** stanchan has joined #akanda16:33
ryanpetrellomarkmcclain adam_g so the akanda-rug tests for me at HEAD are currently failing :\16:35
ryanpetrelloare you all aware of this?16:36
markmcclainryanpetrello: no.. style, unit or devstack?16:37
ryanpetrellotox -epy2716:37
ryanpetrelloI'm running on OSX, so some are related to that16:37
ryanpetrellobut some don't seem related16:37
ryanpetrelloe.g., a bunch of16:37
ryanpetrello>>  raise AssertionError('Expected call: %s\nNot called' % ("run(['--debug', 'tenant', 'manage', 'TENANT123'])",))16:37
ryanpetrellotesting on Linux to be sure, but some of these don't look platform-related16:37
markmcclainyeah.. there is a linux specific test that really should be function rather than unit16:45
ryanpetrellohrm16:45
ryanpetrelloyea16:45
ryanpetrelloI see it16:45
ryanpetrellorunning it a few times in Linux to make sure it's not some weird race16:45
ryanpetrelloif it doesn't work in OSX, that doesn't bother me16:46
markmcclainok... so checked out a fresh head in a new virtualenv and everything worked16:47
ryanpetrelloit's not like I have a shortage of Linux environments I can work in16:47
ryanpetrelloyea, same16:47
markmcclainhaha16:47
*** elo has joined #akanda17:12
drwahl__hey yall19:31
drwahl__quick question19:31
drwahl__is the version of akanda tracking/pinned to the version of openstack?19:31
drwahl__we're trying to get some versioning numbers/names on our akanda appliance builds19:32
drwahl__and wondering if there will simply be an "akanda-juno" appliance, and an "akanda-kilo" appliance19:32
drwahl__or is the version going to be disassociated with the OpenStack version? i.e. akanda-1.0, akanda-2.019:33
*** drwahl__ is now known as drwahl19:38
markmcclaindrwahl_: so the appliance (and the rug) will track the neutron version numbers19:40
markmcclainso 7.0.0 is liberty19:40
markmcclain2015.1.x is kilo etc19:40
drwahlthx19:42
ryanpetrelloadam_g: re: that ticket19:59
ryanpetrellomy reasoning for ak-<tenant-id>19:59
ryanpetrellothe reason is that we generally use this for logging into a routing and quickly knowing "who the hell is this?"19:59
*** elo has quit IRC20:06
ryanpetrellos/that ticket/https://review.openstack.org/#/c/224808/120:06
*** elo has joined #akanda20:06
adam_gryanpetrello, oh wait im dumb20:06
ryanpetrellohttp://reactiongif.org/wp-content/uploads/GIF/2015/06/I-dunno-man-GIF.gif20:06
adam_gryanpetrello, i read the patch wrong. thats only setting the hostname, i thought you were naming the nova instances themselves ak-$tenant_id20:07
ryanpetrelloright20:07
ryanpetrellojust setting the hostname on the VM20:07
ryanpetrellowe use this when we log in as a gut-check20:07
ryanpetrellojust to make sure we're working on the tenant we think we are20:07
adam_gryanpetrello, makes sense. +220:07
ryanpetrellothe issue is that a customer of ours decided to name their router some crazy name20:07
ryanpetrellocool, hx20:07
ryanpetrello*thx20:07
ryanpetrellowhat should I backport it to?20:08
ryanpetrelloKilo?20:08
*** stanchan has quit IRC20:08
*** stanchan has joined #akanda20:09
adam_gryanpetrello, both kilo and juno i guess20:09
ryanpetrellok, wfm20:09
openstackgerritAdam Gandelman proposed stackforge/akanda-rug: Various fixes to get drivers functional (WIP)  https://review.openstack.org/22388420:10
*** elo has quit IRC20:11
adam_gdavidlenwell, markmcclain okay so i think that hsould be good to start building the LBAAS thing on top of. i moved some more stuff into the drivers, stuff that will probably be functionally different with other appliances20:11
adam_gspecifically the stuff that uses akanda.rug.api.akanda_client now, which ATM is effectively a client library to the akanda router20:11
markmcclainadam_g: makes sense20:12
davidlenwellsweet.. I've been working out a list of notifications lbaas will need to watch for.. will start building the lbaas driver tonight20:12
adam_gcool20:12
adam_gi need to prep for this panel tonight. ill see what i can do to help with LB stuff tomorrow20:13
*** elo has joined #akanda20:31
*** elo has quit IRC21:06
sarobi have landed21:11
sarobdum duh dum21:11
openstackgerritSean Roberts proposed stackforge/akanda: installation documentation update  https://review.openstack.org/22490921:33
openstackgerritSean Roberts proposed stackforge/akanda: installation documentation update [WIP]  https://review.openstack.org/22490921:34
*** elo has joined #akanda21:52
*** elo has quit IRC23:11
adam_gdavidlenwell, markmcclain i think we're gonna need a neutron-lbaas akanda agent driver23:16
adam_gthe event notifications themselves dont give us enough context to work with23:16
adam_gie,23:16
adam_gevent_type: loadbalancer.create.start23:16
adam_gpayload: {u'loadbalancer': {u'vip_subnet_id': u'8c58b558-be54-45de-9873-169fe845bb80', u'admin_state_up': True}}23:16
adam_gis all we get on a create23:16
davidlenwellis that not enough information?23:18
davidlenwellwhats it missing?23:18
*** stanchan has quit IRC23:18
adam_gdavidlenwell, the loadbalancer id, for one23:19
davidlenwellhmm23:19
*** elo has joined #akanda23:19
davidlenwellwouldn't it not have an id until after its created?23:20
adam_gshould be available23:21
adam_gwe could probably do something like this https://git.openstack.org/cgit/openstack/neutron-lbaas/tree/neutron_lbaas/drivers/octavia/driver.py#n15823:21
adam_gexcept send out our own notifications on the neutron side with available context via RPC instead of REST'ing it to akanda23:22

Generated by irclog2html.py 2.14.0 by Marius Gedminas - find it at mg.pov.lt!