Thursday, 2017-02-23

*** VW has joined #craton00:00
*** VW has quit IRC00:00
*** VW has joined #craton00:00
*** VW has quit IRC00:02
*** VW has joined #craton00:03
*** valw has joined #craton00:20
*** Syed__ has quit IRC01:05
*** valw has quit IRC01:21
*** VW has quit IRC01:48
openstackgerritThomas Maddox proposed openstack/python-cratonclient master: Adds basic Cloud resource CRUD to CLI  https://review.openstack.org/43709802:37
*** VW has joined #craton02:47
*** VW has quit IRC03:10
*** VW has joined #craton03:23
*** wirehead_ has quit IRC03:55
*** wirehead_ has joined #craton03:58
*** wirehead_ has quit IRC03:59
*** wirehead_ has joined #craton04:00
*** valw has joined #craton04:02
*** VW has quit IRC04:10
*** valw has quit IRC04:10
*** valw has joined #craton04:16
*** valw has quit IRC04:18
*** VW has joined #craton04:42
*** pwnall1337 is now known as zz_pwnall133705:16
*** VW has quit IRC06:30
*** VW has joined #craton09:10
suloo/09:17
*** VW has quit IRC09:18
openstackgerritMerged openstack/craton master: Updated from global requirements  https://review.openstack.org/43717811:49
openstackgerritMerged openstack/python-cratonclient master: Updated from global requirements  https://review.openstack.org/43208512:01
openstackgerritMerged openstack/python-cratonclient master: Add parent_id to host fields  https://review.openstack.org/43356312:01
-openstackstatus- NOTICE: Mirror update failures are causing some Ubuntu-based jobs to fail on invalid qemu package dependencies; the problem mirror is in the process of updating now, so this condition should clear shortly.12:59
*** ChanServ changes topic to "Mirror update failures are causing some Ubuntu-based jobs to fail on invalid qemu package dependencies; the problem mirror is in the process of updating now, so this condition should clear shortly."12:59
*** valw has joined #craton13:31
*** ChanServ changes topic to "Summit talk: https://www.youtube.com/watch?v=Q-sf12SDR3M || Logs: http://eavesdrop.openstack.org/irclogs/%23craton/latest.log.html || Mon 1500 UTC in #openstack-meeting-4 || Client/ecosystem Tues 1700 UTC || Core Thur 1700 UTC || Resources: https://etherpad.openstack.org/p/Fleet_Management"13:36
-openstackstatus- NOTICE: The mirror update process has completed and resulting issue confirmed solved; any changes whose jobs failed on invalid qemu package dependencies can now be safely rechecked to obtain new results.13:36
*** david-lyle has joined #craton13:37
*** valw has quit IRC13:50
*** valw has joined #craton13:51
*** david-lyle has quit IRC13:55
*** valw has quit IRC14:09
thomasemo/14:18
sigmavirus\o14:35
openstackgerritThomas Maddox proposed openstack/craton master: Add Cloud resource before Region  https://review.openstack.org/43170514:37
sigmavirusthomasem: I'm beginning to wonder if there isn't a better way to apply base.http_codes to everything14:40
sigmavirus*everything that needs it14:40
faridhi all14:41
thomasemsigmavirus: Is there a hook into whatever calls the HTTP verbs?15:03
thomasemhttps://flask-restful-cn.readthedocs.io/en/0.3.5/extending.html#custom-error-handlers15:06
thomasemSomething worth looking into.15:06
thomasemLooks to serve the same purpose.15:08
thomasem"yet you want to handle all Flask-RESTful errors with the correct content type and error syntax as your 200-level requests."15:08
sigmavirushi farid!15:11
sigmavirusthomasem: yeah there are pre/post filters15:11
sigmavirusI feel like https://flask-restful-cn.readthedocs.io/en/0.3.5/extending.html#resource-method-decorators would be better though15:12
* sigmavirus shrugs15:12
thomasemThat's fair, sigmavirus.15:18
thomasemIf nothing else, it'd probably work better with our already existing decorator (thusly not having to write something else).15:18
thomasemI was about to send you my Spencer Reid "Well, actually..." meme, but I can't find it. :(15:19
thomasemThat's okay. I'll make another.15:19
*** VW has joined #craton15:22
*** VW has quit IRC15:23
*** VW has joined #craton15:23
sigmaviruslol15:24
*** valw has joined #craton15:29
thomasemRelates to this bug: https://bugs.launchpad.net/craton/+bug/166501515:32
openstackLaunchpad bug 1665015 in craton "All text errors reported by the Craton REST API should be JSON encoded" [High,New]15:32
thomasemAnd, interestingly, we already use method_decorators for several other decorators?15:32
thomasemAnyway, bigger fish, atm. Will look into it a bit later.15:34
*** Syed__ has joined #craton15:37
openstackgerritThomas Maddox proposed openstack/python-cratonclient master: Adds basic Cloud resource CRUD to CLI  https://review.openstack.org/43709815:45
thomasemFor listing hosts, do we want to make region AND cloud required, or just cloud?15:49
thomasemThe CLI currently requires region to be specified.15:50
thomasemWant to better understand the goal there.15:50
sigmavirusthomasem: that's an artifact of old timeys15:52
sigmaviruswe don't actually need to require region_id any longer15:52
sigmavirusIt's a bug15:52
sigmavirusOne that Jim has filed and is on my burner15:53
sigmavirusI'm trying to make our integration shell tests better right now first because they drive me up the wall15:54
thomasemAhhhh, okay. That makes more sense. Thank you!15:58
thomasemSo, I'll just make cloud_id optional.15:58
thomasemsigmavirus: thanks15:58
sigmavirusthomasem: happy to help15:59
openstackgerritThomas Maddox proposed openstack/python-cratonclient master: Adds basic Cloud resource CRUD to CLI  https://review.openstack.org/43709816:03
jimbakersounds good about a better replacement for base.http_codes, to remove even more duplicated code16:15
suloso only devices have links ?16:18
sulosigmavirus: ^16:18
sigmavirussulo: huh?16:20
jimbakershould be true of any resource collecton16:22
jimbakersulo, or are you referring to up links?16:23
sulojimbaker: whats an up link ?16:23
jimbakerit's a link for the parent16:23
sulosigmavirus: sorry what i meant was in schemas i see links property defined only for somethings16:24
sulojimbaker: oh!? its called up instead of parent ?16:24
*** jovon has joined #craton16:24
sulosigmavirus: was trying to see why that was .. jumped on the question too soon16:24
jimbakersulo, there was some discussion on this specific name16:25
* sigmavirus still hasn't found anything that says "up" is more canonical than "parent" but *shrug*16:25
sigmavirusbesides, just because everyone else is naming things poorly, doesn't mean we should16:25
sulooh i must have missed that discussion16:25
fariddoes it make sense to create a ticket in python-cratonclient to allow loading an openstack inventory into Craton ?16:26
sigmavirussulo: it was a very very brief discussion16:26
jimbakerhttp://www.iana.org/assignments/link-relations/link-relations.xhtml16:26
sigmavirusjimbaker: IANA does tend to win out16:26
jimbakersince there was a reasonable convention already, we decided to follow it16:26
suloso its up down instead parent child ?16:26
sigmavirussulo: seems that way16:26
sigmavirusthere is no down though16:27
jimbakersulo, well, there's the problem that that doc doesn't define `down`16:27
sigmavirusfarid: would make sense16:27
faridallright16:27
sulook, thats seem even more odd then ?16:27
sigmavirusjimbaker: so that's not a document. It's a registry that points to other documents16:27
sigmavirusEach of those names are defined in RFCs or W3C documents16:27
jimbakersigmavirus, ack. but materialized as a doc :)16:28
sigmavirusit's a glorified spreadsheet =P16:28
sulosigmavirus: i thought those properties could be extended ?16:28
sigmavirussulo: you can't just add to an IANA registry16:28
sigmavirusBut yes, the registries are meant to be expandable16:28
jimbakerbrb16:28
sigmavirushttps://tools.ietf.org/html/rfc5988#section-4.216:29
sigmavirusWe can define our own so long as we provide a clear definition of semantics16:29
sulooh well16:33
suloso if we are using up for parent, what are we using for child ?16:35
* sulo goes to read the spec again16:35
faridzz_pwnall1337: I created this one for the environment import stuff https://bugs.launchpad.net/python-cratonclient/+bug/166737616:40
openstackLaunchpad bug 1667376 in Craton's Python Client "Allow loading an Openstack inventory into Craton" [Undecided,New] - Assigned to Tim Pownall (pownalltim)16:40
sigmavirussulo: don't think we actually came to a conclusion with children links16:43
sulosigmavirus: rgr16:44
openstackgerritThomas Maddox proposed openstack/craton master: Add Cloud resource before Region  https://review.openstack.org/43170516:44
*** zz_pwnall1337 is now known as pwnall133716:49
sigmavirusjimbaker: you're making me want to assign you a work item to write extensive documentation about this for craton's docs17:00
sigmavirus*developer docs17:00
jimbakerlet's kick off our meeting17:05
jimbaker#startmeeting craton17:05
openstackMeeting started Thu Feb 23 17:05:13 2017 UTC and is due to finish in 60 minutes.  The chair is jimbaker. Information about MeetBot at http://wiki.debian.org/MeetBot.17:05
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.17:05
jimbaker#chair sigmavirus sulo jimbaker thomasem17:05
openstackThe meeting name has been set to 'craton'17:05
jimbaker#link https://etherpad.openstack.org/p/craton-meetings17:05
openstackCurrent chairs: jimbaker sigmavirus sulo thomasem17:05
jimbaker#topic Roll Call17:05
thomasemo/17:05
sigmaviruso/17:05
jimbakero/17:05
git-harryhi17:05
sigmavirusSyed__: farid jovon ping17:06
suloo/17:06
jovono/17:06
Syed__o/17:06
farido/17:06
jimbakerthomasem, i assume you will chair today's meeting...17:07
thomasem#topic Action Items from Monday's meeting17:07
thomasemyep17:07
thomasem#link http://eavesdrop.openstack.org/meetings/craton/2017/craton.2017-02-20-15.00.html17:08
thomasemACTION: thomasem to write BP regarding deployment as a starting point for iterating on a suggested deployment model17:08
thomasemCarrying forward. Busy with higher priority items atm.17:08
thomasem#action thomasem to write BP regarding deployment as a starting point for iterating on a suggested deployment model17:08
jimbaker+117:08
thomasemACTION: jimbaker to map Dusty's requirements to work or existing features of Craton, especially with respect to short-term deliverable (~2 weeks remaining)17:08
jimbakerso this has been in the back of my mind. i think we have been working implicitly against this17:09
jimbakerin terms of bugs, but more fomalization needed17:09
jimbakercarry forward, please17:09
jimbaker(done17:09
thomasem#action jimbaker to map Dusty's requirements to work or existing features of Craton, especially with respect to short-term deliverable (~2 weeks remaining)17:09
thomasemACTION: thomasem to review Dusty stories and add notes on concerns or questions17:09
thomasemSeems we're going against Björn's use cases more than anything. I asked a few clarification questions, but overall, no discrepancies found from what we're working on overall.17:10
sigmavirusthomasem: Bjoern ;)17:11
thomasemWill be interested to see what comes out of jimbaker's action item regarding that.17:11
thomasemoe = ö does it not? :P17:11
jimbakeragreed that bjoern (= björn presumably)17:11
jimbakerhas the more detailed stories for the time being17:11
* sigmavirus just knows that's how Bjoern tends to spell his name17:11
thomasemCool. I will refrain from being fancy, then.17:11
thomasemdone on that action item from me.17:12
thomasemACTION: sigmavirus to finish up testing on cli17:12
sigmavirusThat's in progress17:12
sigmavirusAlso as part of that, I'm throwing together a minimal pluggable formatter system so we can simply our shell integration tests17:12
sigmavirus(That way the tests can use the json formatter for most things and verify the output that way, while also using the pretty-table formatters but not relying on those for the bulk of our tests)17:13
thomasemGotcha17:13
sigmavirus#action sigmavirus finish up client/cli testing17:13
sigmavirus(Carried that forward for you)17:13
thomasemAww thanks17:13
* sigmavirus is a helper17:13
jimbakersigmavirus, awesome, that's great stuff17:13
sigmavirusor something17:13
thomasemOkay, cool. That concludes action items.17:13
thomasem#topic Stand Up17:13
thomasem#info each team member briefly describes what they are working on this week, and describes blockers (if there are any)17:14
thomasem#topic Stand Up :: thomasem17:14
thomasemWorking on clouds some more, turned into quite a bit of nuances that need to be shored up. Found some issues with cloud_id filtering, so in the process of correcting those and will add tests.17:14
thomasemAlso working on the CLI changes to support the cloud endpoint and support the cloud_id which will be sprinkled throughout the child resources, as is the going pattern for our relational representation in the API at the moment.17:15
thomasemFiled some bugs around that specifically to see if we can't clean that up in future iterations of the data model and API.17:15
thomasem#link https://bugs.launchpad.net/craton/+bug/166669917:15
openstackLaunchpad bug 1666699 in craton "able to create unexpected relationships via API" [Undecided,New]17:15
thomasem#link https://bugs.launchpad.net/craton/+bug/166669517:16
openstackLaunchpad bug 1666695 in craton "project ID not honored in requests" [Undecided,New]17:16
thomasemOther than that, putting my eyes to code reviews as they come in.17:16
thomasemHopefully at the tail of this cloud work and then I'll pick up the next critical thing!17:16
thomasemdone17:16
thomasem#topic Stand Up :: sigmavirus17:17
sigmavirusWorking on cratonclient tests. Looking at thomasem's cloud review occasionally. Working on a slapdash client formatter system. /fin17:18
thomasem#topic Stand Up :: jimbaker17:18
jimbakerfinalize testing for https://review.openstack.org/#/c/427032/; write alembic script for https://bugs.launchpad.net/craton/+bug/1665066; i might tackle https://bugs.launchpad.net/craton/+bug/1661226, given this should be an important way to look up devices17:19
openstackLaunchpad bug 1665066 in craton "Alembic script must use named constraints to support future upgrades" [Critical,New] - Assigned to Jim Baker (jimbaker)17:19
jimbakerwe need to focus on specific imports from openstack and making sure that pwnall1337 is successful (thomasem is point, but this is our most important responsibility, getting this to work as expected for next week!)17:19
openstackLaunchpad bug 1661226 in craton "Filter by variables lacks resolved variables" [Critical,Confirmed]17:19
jimbakermore reviews, especially the cloud support that thomasem has worked on17:19
jimbakerdone17:19
thomasem#topic Stand Up :: git-harry17:19
git-harryfinishing off /v1/devices today17:20
git-harrydone17:20
thomasem#topic Stand Up :: sulo17:20
sulomostly catching up17:21
sulogot a couple of bugs to fix17:21
sulomostly on cross tenant search17:21
jimbaker+117:21
suloand on cleaning up schema for creates17:21
suloother than that just usual stuff reviews etc17:22
sulodone17:22
thomasem#topic Stand Up :: jovon17:22
jimbakersulo, are we describing json schemas?17:22
thomasem#undo17:22
openstackRemoving item from minutes: #topic Stand Up :: jovon17:22
suloyes17:22
sigmaviruslet's hold off on questions until after standup17:22
jimbakerok, cool17:22
thomasem#topic Stand Up :: jovon17:22
jovonexperimenting with RAML and ramlfication to develop an easy-to-use implementation strategy with existing craton docs or a minimal manual translation17:23
jovondone17:23
thomasem#topic Stand Up :: Syed__17:23
Syed__As per tuesday meeting, i have been looking into cratonclient, more specifically looking into https://bugs.launchpad.net/python-cratonclient/+bug/1659238 and hoping to get this done https://review.openstack.org/#/c/425463/ .17:23
openstackLaunchpad bug 1659238 in Craton's Python Client "client is missing user related commands" [Undecided,In progress] - Assigned to Syed Ahsan Shamim Zaidi (ahsanmohsin04)17:23
Syed__done17:23
thomasem#topic Stand Up :: farid17:23
faridgot a couple client tickets in and plan on working today with tim on any aio/inventory load questions, tickets are https://bugs.launchpad.net/python-cratonclient/+bug/1667109 and https://bugs.launchpad.net/python-cratonclient/+bug/166737617:25
openstackLaunchpad bug 1667109 in Craton's Python Client "Allow environment export from client" [Undecided,New]17:25
fariddone17:25
openstackLaunchpad bug 1667376 in Craton's Python Client "Allow loading an Openstack inventory into Craton" [Undecided,New] - Assigned to Tim Pownall (pownalltim)17:25
thomasem#topic Open Discussion17:25
thomasemNothing on the etherpad in the way of topics, so.17:25
thomasemThink we're all just heads down getting it done.17:26
jimbakersulo, any more discussion on cross-project queries?17:26
sulojimbaker: not really, i veryfiy everyting and we can discuss if anything comes up17:27
jimbakerthomasem, looks like we can just assume heads down, and maybe a quick meeting otday17:27
jimbakersulo, +117:27
thomasemExcellent. I did have a quick question that came out of working with pwnall1337 yesterday.17:28
thomasemWhat's the story with UUIDs sans hyphens?17:28
thomasemfor, like, project_id17:28
jimbakeri'm sorry, what's the context here?17:28
jimbakerin the database?17:28
thomasemYeah, and in the headers17:28
thomasemIs that just an OpenStack thing, or something else?17:29
jimbakerso we should be able to support UUID with and without hyphens17:29
jimbakerat entry point17:29
thomasemAhhh, it truncates the UUID when you generate one when storing in the DB to the size of a UUID sans hyphens.17:29
thomasemWhich caused us to chase our tails a bit when using UUID() in MySQL17:30
jimbakerand on exit from the api, it would be far better if they are formatted17:30
thomasemI think they come back with hyphens just fine.17:30
thomasemBut, they're forcibly stored according to the length of an improper uuid in the DB.17:30
jimbakerso: there's a basic assumption that we are using the uuid type that sqlachemy ext provides us17:30
thomasemSo, if that's not intended, I can file a bug.17:30
jimbakerin the db itself, they are stored as a string without hyphens iirc17:31
jimbakerand that's fine17:31
thomasemRight, why is that?17:31
jimbakerwe don't expect people directly using the db :)17:31
thomasemTo bootstrap one must. :)17:31
jimbakerand if they are, they have to play by our rules17:31
thomasemOkay, but I'm questioning why that rule exists?17:31
thomasemWhat's the purpose? Why not use proper UUIDs there?17:31
jimbakerthere are a few ways to stored uuids in the db. we chose the compact string representation17:32
jimbakervs the more compact bytes representation17:32
jimbakerthis is managed by the model code17:32
jimbakerit would be a simple thing to change if we want to do so17:32
thomasemSo, it's a performance concern?17:32
jimbakerhardly not17:33
thomasemI don't doubt it's simple to change. I'm really only wondering what the original reasoning was for making that choice.17:33
jimbakerbut it should be a canonical repr17:33
jimbakerso with, or without, we want it the same way17:34
thomasemSo why not store it the same way and then you never have to worry about expanding/contracting?17:34
jimbakerfwiw, when we had all IDs as UUIDs, there may have been more of a perf concern17:34
thomasemHaha, yeah. I can see that.17:34
jimbakeri think it's just the default for the UUIDType here...17:34
jimbakerhttps://github.com/openstack/craton/blob/master/craton/db/sqlalchemy/models.py#L23317:34
thomasemOhhhh okay17:34
jimbakeri'm pretty sure we can make it something else if we want17:35
sigmavirusthomasem: jimbaker I'm not sure that's true. I just like being explicit in certain things I do17:35
jimbakertbh, we haven't looked at this for a while17:35
thomasemSure. That's all I was wondering. If it's just what SQLAlchemy does, that's different. I was under the impression that it was a deliberate choice.17:35
jimbakerwell it is a deliberate choice to use this library: https://github.com/openstack/craton/blob/master/craton/db/sqlalchemy/models.py#L23317:35
jimbakerand keep things in types, vs strings, once it entered SA17:36
jimbakerbut i don't think this usage is controversial17:36
sigmavirusrelated https://github.com/kvesteri/sqlalchemy-utils/issues/26117:36
sigmavirusAh, it does default to binary: https://github.com/kvesteri/sqlalchemy-utils/blob/master/sqlalchemy_utils/types/uuid.py#L3117:36
jimbakerit's more of a question, could we opt for a different db repr17:36
sigmavirusI suspect I stole that from another openstack project then17:36
jimbakersigmavirus, yeah, it was binary at some point17:37
jimbakerand that was much more objectionable, since it was opaque in mysql17:37
jimbakeri believe it may adapt itself from the fact that we chose to do the storage as a string in the alembic script17:37
thomasemGotcha17:38
sigmavirusthese things are all fuzzy to me17:38
sigmaviruswe didn't do specs back then17:38
sigmavirusAlso, project UUIDs seems silly now that we won't be doing a horizon plugin17:38
* sigmavirus shrugs17:38
jimbakersigmavirus, yeah, only the code speaks for itself17:38
thomasemLol, it's cool. I didn't mean to spark a bunch about it. I was mostly curious. We can work with it as-is. Something to consider changing later on, if we care.17:39
jimbakerwell, yeah, lets just keep it the way it is. at least project uuid is unique, in case we ever need to consolidate from multiple projects17:39
thomasemAlright. That was all I had!17:40
jimbakerthat's actually a more interesting question, but fortunately mysql multisource replication can readily handle17:40
jimbakerand whatever alt we build17:40
jimbakerthomasem, ok, adjourn for now?17:40
thomasemYeppers17:41
thomasem#endmeeting17:41
openstackMeeting ended Thu Feb 23 17:41:06 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:41
openstackMinutes:        http://eavesdrop.openstack.org/meetings/craton/2017/craton.2017-02-23-17.05.html17:41
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/craton/2017/craton.2017-02-23-17.05.txt17:41
openstackLog:            http://eavesdrop.openstack.org/meetings/craton/2017/craton.2017-02-23-17.05.log.html17:41
jimbakerthanks everyone!17:41
thomasemCheers!17:41
thomasemI need food17:41
jovon+1 to that17:41
jovon:)17:41
toanjimbaker: would it be possible to demo tomorrow, what we have so far, as far as what requirements can be checked off?17:52
toanfarid: ^ ^17:52
jimbakertoan, makes sense17:54
jimbakersulo, up for this?17:54
sulomaybe monday ? .. i think there are way too many things in flight right now17:55
toanjimbaker: ok. it should be just for the team and dusty... no one else so that there would be no distracting question17:55
suloi think monday we can have the cloud stuff and all the otehr stuff ready17:56
toansulo: ^ ^17:56
toanwith data, i hope17:56
sulotoan: fake data will still be there ;), tim is still wokring on getting aio data in .. dunno if that will be done by monday17:57
toansulo: would like have real data... so, i'll ping tim17:58
jimbakeri believe we can get real data in that time frame17:58
sulotoan: roger17:58
toanmonday would be good for demo, as cloudnull and antonym are joining back to this workstream17:58
toanto help finish off the last week of the timebox17:58
jimbakerit's supportable with the REST API, and it's available with this patch (which only requires testing to get merged in) https://review.openstack.org/#/c/427032/17:59
sulojimbaker: yeah was going to ping re that patch17:59
jimbakeri would like to finalize the multi cloud in a project support17:59
sulothat needs to go in for much of my network patches to go in17:59
jimbakersulo, agreed, it's pretty essential18:00
jimbakeri believe i have figured out how the mock testing works for resources and managers; although it seems to me that we could do more of it for the resources that depend on it, not just depend on what's tested with crud18:01
suloi am testing the cloud patch from thomasem18:01
sulo:+118:02
jimbakerbut we can revisit18:02
jimbakeralso hopefully we can get tox -e integration implemented for the clients sooner than later. but definitely not before march 318:02
jimbakeralthough i suppose it would be a straightforward reuse of what's already in tox -e functional18:03
*** david-lyle has joined #craton18:11
*** david-lyle has quit IRC18:16
*** david-lyle has joined #craton18:19
faridtoan: seems like it's all good? :)18:23
toanfarid: yes!18:31
sigmavirusjimbaker: you mean you want to have the client actually run tests against a live craton serve?18:33
* sigmavirus would call those acceptance/functional tests18:33
*** david-lyle has quit IRC18:33
*** harlowja has joined #craton18:33
*** david-lyle has joined #craton18:42
jimbakersigmavirus, i'm good with any name that delivers that type of testing18:46
sigmavirusjimbaker: because I was going to add integration tests that took advantage of betamax for speed and functional tests that talk to the real sever18:46
sigmavirus*server18:46
sigmavirus(openstack is increasingly using betamax but they also have stable-er APIs)18:47
jimbakersigmavirus, :)18:51
jimbakeryeah, that approach works for me18:51
thomasemUhhhh... anyone else having LP issues? I'm trying to create a bug and it keeps timing out. :(19:18
jimbakerthomasem, i'm seeing the same timeout error19:19
thomasemOkay, good. It's not just me.19:20
Syed__rev19:27
*** david-lyle has quit IRC19:35
thomasemWould anyone have any beef with me extracting all of these create_* methods to the base test class for Craton functional tests?19:38
thomasemExercising the cloud_id filter across the API is going to be a bunch of duplicated code in there otherwise.19:39
thomasemAnd it's already a bunch of duplicated code.19:39
sigmavirusthomasem: go for it19:39
thomasemCould dry it out even more, but this is a start.19:39
thomasemCool, will do.19:39
openstackgerritgit-harry proposed openstack/craton master: Add GET /v1/devices  https://review.openstack.org/43758519:48
sigmavirusthomasem: don't use up all your towels19:51
thomasemLol, oh the rush of jokes that come to mind.19:51
thomasemMust. Resist.19:52
thomasemMmm, botched refactorings breaking all the things.19:53
*** david-lyle has joined #craton20:05
openstackgerritsulochan-acharya proposed openstack/craton master: Ensures no extra property is allowed on creates  https://review.openstack.org/43760620:24
openstackgerritsulochan-acharya proposed openstack/craton master: Ensures no extra property is allowed on creates  https://review.openstack.org/43760620:39
*** pwnall1337 is now known as zz_pwnall133720:41
openstackgerritIan Cordasco proposed openstack/python-cratonclient master: Reorganize shell based integration tests  https://review.openstack.org/43765820:57
openstackgerritIan Cordasco proposed openstack/python-cratonclient master: Add --format to the client shell  https://review.openstack.org/43765920:57
sigmavirusLater y'all20:58
*** david-lyle has quit IRC20:59
thomasemCheers, sigmavirus!21:01
faridlater sigmavirus21:03
jimbakerlots of great changes proposed, some of which are conflicting21:26
thomasemWe need to refactor these functional tests to be more isolated from each other.21:37
thomasemThe fact that data from one test impacts another is a bad sign.21:38
thomasemEither via cleanups or unique names21:38
sulothomasem: what ? that shouldnt be everythig on db side gets nuked prior to each test21:38
sulowhat are you seeing ?21:39
thomasemconflicts when I try to run self.create_cloud() twice.21:39
thomasemwithout specifying a different name.21:39
suloon the same test ?21:39
thomasemIn another test21:39
suloyeah thats bad .. it shouldnt be like that21:40
thomasemHmmm... wait, nevermind. You're right. It's because self.create_cloud runs in setUp, too.21:40
thomasemsulo: yeah, nevermind. I think you're correct.21:40
thomasemred herring21:40
sulothomasem: cool21:41
suloyeah but in general i think that is taken care of21:41
suloevery table is turncated prior to each test21:41
thomasemOkay, good.21:41
thomasemalright, let's see if this fixes it.21:43
thomasemGetting wires crossed, lol.21:43
thomasemAlmost done with this refactoring + cell_id filter tests21:43
thomasems/cell_id/cloud_id/21:44
jimbakercool21:46
thomasemGot two extremes this week - one-liners and thousand liners. :P21:47
openstackgerritThomas Maddox proposed openstack/craton master: Add Cloud resource before Region  https://review.openstack.org/43170521:51
openstackgerritThomas Maddox proposed openstack/craton master: Add Cloud resource before Region  https://review.openstack.org/43170521:53
jimbakersomehow i missed this one detail when git-harry proposed the spec (https://github.com/openstack/craton/blob/master/doc/source/specs/approved/list-devices.rst#rest-api-impact), which he has faithfully implemented21:53
jimbakerthat devices has two children (currently), hosts and network-devices21:53
thomasemAnd what's the implication of your not having caught it?21:54
jimbakeri suppose we can do it this way, but for some reason i thought we would have hosts and network-devices all at the same top level21:54
jimbakeras links21:54
openstackgerritThomas Maddox proposed openstack/python-cratonclient master: Adds basic Cloud resource CRUD to CLI  https://review.openstack.org/43709821:54
jimbakerthomasem, well, i would prefer to have read it a bit more closely... the implication is, does this match sigmavirus' expectation or not?21:55
thomasemOh, where instead of {"devices": {"hosts": [...], "network-devices": [...]}} you were thinking {"hosts": [...], "network-devices": [...]}?21:56
thomasemjimbaker: ^^21:57
jimbakeryes. i haven't looked at the impl details, but i cannot imagine it would be difficult to change the output. just a question of whether from a "follow the nose" perspective, the first is as easy as the second21:57
thomasemGotcha21:57
*** david-lyle has joined #craton21:57
jimbakerthomasem, in general i prefer flatter structures. so this seems to be unnecessarily nested21:58
thomasemYeah21:58
jimbakeranyway, it's a quick correction, but we can wait until git-harry and sigmavirus are back online tomorrow21:59
jimbaker(assuming correction is needed... at the very least, clarification!)21:59
thomasemIndeed!22:00
faridcan y'all do a chat tomorrow at the same time as today? think it might be helpful to touch base before the weekend22:05
thomasemfarid: I can.22:07
thomasemActually, let me double-check before committing.22:07
thomasemfarid: yes, I can22:07
thomasemWhew gerrit's sluggish this afternoon.22:10
faridthanks thomasem22:11
thomasemSure thing!22:12
jimbakerfarid, sounds good22:18
farido/22:18
*** VW has quit IRC22:23
*** VW_ has joined #craton22:23
thomasemAlright. Been fun, folks! Time for me to get some grub. Have a lovely evening and catch ya in the morning!22:29
faridhave a good one thomasem , laters !22:35
*** david-lyle_ has joined #craton22:37
*** david-lyle has quit IRC22:37
*** david-lyle_ has quit IRC22:52
faridgonna take off as well, laters all!23:20
*** david-lyle has joined #craton23:37
*** david-lyle has quit IRC23:57

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