| *** VW has joined #craton | 00:11 | |
| *** valw has quit IRC | 00:49 | |
| *** valw has joined #craton | 00:55 | |
| *** VW_ has joined #craton | 01:16 | |
| *** VW has quit IRC | 01:16 | |
| *** VW_ has quit IRC | 01:30 | |
| *** VW has joined #craton | 01:58 | |
| *** VW has quit IRC | 01:59 | |
| *** VW has joined #craton | 02:00 | |
| *** valw has quit IRC | 02:13 | |
| *** valw has joined #craton | 02:14 | |
| *** valw has quit IRC | 02:18 | |
| *** Syed__ has quit IRC | 02:45 | |
| jimbaker | sulo, i merged in one outstanding python-cratonclient change from you; i didn't see a second one | 02:56 |
|---|---|---|
| jimbaker | also filed a few bugs | 02:57 |
| *** valw has joined #craton | 03:02 | |
| *** valw has quit IRC | 03:30 | |
| *** VW has quit IRC | 03:41 | |
| *** VW has joined #craton | 03:51 | |
| *** VW has quit IRC | 03:59 | |
| *** VW has joined #craton | 04:58 | |
| *** mudpuppy has quit IRC | 05:05 | |
| *** mudpuppy has joined #craton | 05:07 | |
| *** VW has quit IRC | 06:01 | |
| *** tojuvone has joined #craton | 07:47 | |
| *** VW has joined #craton | 08:01 | |
| *** VW has quit IRC | 08:06 | |
| sulo | jimbaker: https://review.openstack.org/#/c/425221/ | 12:12 |
| sulo | thats the second one | 12:12 |
| *** VW has joined #craton | 14:11 | |
| sulo | sigmavirus: if you are around can you take a look at https://review.openstack.org/#/c/425221/ | 14:13 |
| sigmavirus | In an IRC meeting, but I'll queue it :) | 14:13 |
| sulo | i need someone other than me to at least +2 it for me | 14:13 |
| sulo | sigmavirus: cool, thanks | 14:13 |
| sigmavirus | oh wait, all negative review? +2+A automagically ;) | 14:13 |
| sulo | heh, its a simple one, needed to rebase something on top of that | 14:18 |
| *** VW has quit IRC | 14:49 | |
| *** VW has joined #craton | 14:50 | |
| sulo | which one is the right way to do: | 14:51 |
| sulo | variables-list --host=1 and varialbles-list --region=1 | 14:52 |
| sulo | to get vars for host and region etc | 14:52 |
| sulo | or | 14:52 |
| sulo | host-vars-list -h=1 | 14:52 |
| sulo | region-vars-list -r=1 | 14:52 |
| sulo | ?? | 14:52 |
| sigmavirus | I don't like variables-list unless you enforce something like --type host | 15:12 |
| sigmavirus | because people will try to combine --host=1 --region=1 | 15:12 |
| sigmavirus | I like `<type>-vars-from` better because it's explicit in the command-name and we won't have a required -- param | 15:12 |
| sigmavirus | s/from/for/ | 15:13 |
| sigmavirus | for is also fewer things to type than list | 15:13 |
| sulo | ok, that sounds good to me | 15:28 |
| sigmavirus | I also worry that list might imply that we won't resolve variables for an object if they're not immediately associated with the object | 15:35 |
| git-harry | Is the client design going to be discussed in a spec? | 15:40 |
| sigmavirus | git-harry: it was designed at the start save for variables | 15:41 |
| sigmavirus | tl;dr, cratonclient is going to be as awful as every python-<service>client | 15:42 |
| git-harry | sigmavirus: so this vars stuff is the last piece? | 15:42 |
| sigmavirus | to design? yeah | 15:44 |
| sigmavirus | I wouldn't be adverse to a spec submitted to python-cratonclient to design the client | 15:44 |
| sigmavirus | but jovon doc'd all of this inc raton already iirc | 15:44 |
| *** Syed__ has joined #craton | 15:53 | |
| sulo | git-harry: no, i am just fixing a missing resource, not designing this thing | 15:56 |
| sulo | i have very little idea about client | 15:56 |
| sulo | also i am not sure how to do the variables part either | 15:56 |
| git-harry | sulo: yeah, I misunderstood - I've not yet used the client. | 15:57 |
| sulo | looks like this thing expects base path and all .. which i am not sure works for /hosts/xxx/variables et | 15:57 |
| sulo | still looking though | 15:57 |
| sigmavirus | sulo: if we had accepted the url-structure spec with nested resources, then the client would be far more flexible already =P | 16:04 |
| sigmavirus | as such, I didn't prioritize it | 16:04 |
| sulo | sigmavirus: how so ? you have the exact same url for variables ? | 16:05 |
| *** jovon has joined #craton | 16:05 | |
| sigmavirus | sulo: variables was created after most of that work was done in the client | 16:05 |
| sigmavirus | but necessitating nested resources as a 1st class citizen would have meant needing immediate changes in the client | 16:05 |
| sigmavirus | variables landed after both the spec iirc | 16:06 |
| sulo | ah gotcha | 16:06 |
| sigmavirus | And I didn't approve/review vars | 16:06 |
| sigmavirus | so I didn't notice whta would become a difficulty | 16:06 |
| jimbaker | when we were loser about the api, the client's crud meant that variables used to work for set by using host.update (which would then just use PUT). i don't see why the client would not just automagically use v1/hosts/$host/variables instead | 16:13 |
| jimbaker | it still retrieves the variables when doing GET against v1/hosts/$host | 16:14 |
| jimbaker | looser | 16:14 |
| jimbaker | :) | 16:14 |
| jimbaker | love that | 16:14 |
| jimbaker | sulo, so that's my recommendation. just support being able to do stuff like craton.hosts.update(item_id=8, variables={'foo': 42, 'bar': [1,2,3,4]} | 16:15 |
| sulo | jimbaker: i dont think that works | 16:18 |
| jimbaker | sulo, also what's the status of the functional testing with respect to python mysql client? i spent a bit of time trying to resolve it myself, but somewhere in the various bits of config to be done, it was not picking up the recommended PyMySQL | 16:18 |
| jimbaker | (pure python reimpl) | 16:18 |
| sulo | pymysql works | 16:18 |
| sulo | i havent updated my patch, but did test it | 16:19 |
| jimbaker | sulo, can you push up that? | 16:19 |
| sulo | i want to add a small bit to deal with users/project in db | 16:19 |
| jimbaker | ok | 16:19 |
| sulo | and i didnt get to that yet today | 16:19 |
| jimbaker | sulo, re not working with update, so validation now strips out variables. it is possible that i didn't check in the past against the underlying store, and my memory is mixed up | 16:20 |
| jimbaker | but with the validation stuff, it of course will not work. i think that's fine. we should use v1/hosts/$host/variables, but i think treating variables specially here makes sense in doing stuff like craton.hosts.update(item_id=8, variables={'foo': 42, 'bar': [1,2,3,4]} | 16:21 |
| sulo | jimbaker: so i dont think this is a issue to solve for in craton core | 16:23 |
| sulo | i think this needs to be handled on client side | 16:23 |
| jimbaker | sulo, right, it's client side. we already have the rest api, and it clearly works | 16:24 |
| sulo | yeah | 16:24 |
| sulo | (dont know if its a problem yet) but looks like its mostly on how the urls are constructed | 16:24 |
| jimbaker | i don't see a problem in the url construction in the client. just not taking advantage of it :) | 16:25 |
| sulo | how do you mean ? | 16:25 |
| jimbaker | a good example of where the rest api usage works is the generate_fake_data.py | 16:26 |
| jimbaker | but there's no specific support right now in cratonclient for variables | 16:27 |
| jimbaker | brb | 16:27 |
| *** VW has quit IRC | 16:43 | |
| jimbaker | #startmeeting craton | 16:59 |
| openstack | Meeting started Thu Jan 26 16:59:59 2017 UTC and is due to finish in 60 minutes. The chair is jimbaker. Information about MeetBot at http://wiki.debian.org/MeetBot. | 16:59 |
| openstack | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 17:00 |
| openstack | The meeting name has been set to 'craton' | 17:00 |
| jimbaker | #chair sigmavirus sulo jimbaker | 17:00 |
| openstack | Current chairs: jimbaker sigmavirus sulo | 17:00 |
| jimbaker | #link https://etherpad.openstack.org/p/craton-meetings | 17:00 |
| jimbaker | #topic Roll Call | 17:00 |
| jimbaker | o/ | 17:00 |
| Syed__ | o/ | 17:00 |
| jovon | o/ | 17:00 |
| jimbaker | i have posted a short agenda in the meeting notes | 17:01 |
| tojuvone | hi | 17:01 |
| jimbaker | tojuvone, thanks for joining! | 17:01 |
| jimbaker | we will wait a couple more minutes for git-harry, sigmavirus, sulo to join us | 17:02 |
| sigmavirus | o/ | 17:02 |
| git-harry | here | 17:03 |
| jimbaker | ok, let's get started | 17:04 |
| jimbaker | #topic upcoming demos | 17:05 |
| Syed__ | when is the demo ? | 17:05 |
| jimbaker | so we have been asked to prepare two demos for next week, on tues jan 31 and thur feb 2 | 17:05 |
| Syed__ | cool | 17:05 |
| sigmavirus | Who is "we"? | 17:05 |
| sigmavirus | =P | 17:05 |
| sigmavirus | o/ antonym in case you want to participate in our meeting/sync | 17:06 |
| jimbaker | sigmavirus, well i have been asked, and by extension, all of us have been asked ;) | 17:06 |
| sigmavirus | jimbaker: even tojuvone ? =P | 17:06 |
| jimbaker | sigmavirus, no i mean to universally quantify all intelligences | 17:06 |
| Syed__ | by whom ? where will it be presented? | 17:06 |
| jimbaker | ;) | 17:06 |
| tojuvone | sigmavirus, :D | 17:07 |
| jimbaker | Syed__, in due time | 17:07 |
| jimbaker | so we (the craton dev team) have been asked by toan and dusty to do a demo next tues during our regular vidyo call | 17:07 |
| jimbaker | this will then be prep for a larger demo one week from today, with time/place to be set. but likely in craton vidyo room, possibly at this time | 17:08 |
| jimbaker | by larger demo, i meant to say, in front of a larger audience | 17:09 |
| sulo | jimbaker: whats the expections from the demo ? | 17:10 |
| jimbaker | so this is sort of crunch time. we need to ensure everything that is necessary for basic inventory is working. we got the basics | 17:10 |
| antonym | o/ | 17:10 |
| *** valw has joined #craton | 17:10 | |
| jimbaker | sulo, basic crud ops, with variables | 17:10 |
| sulo | k | 17:10 |
| jimbaker | antonym, thanks for joining | 17:11 |
| antonym | no prob | 17:11 |
| jimbaker | so for antonym: we should show off the python client, since he's going to need this for his tooling work | 17:12 |
| Syed__ | So later on down the road specially for boston summit, do we have a set of goals infront of us which we are looking to be done by that | 17:12 |
| Syed__ | like having UI for Craton etc. | 17:12 |
| jimbaker | Syed__, sorry, but that's a different topic. let me suggest we discuss later in today's meeting. can you add to the agenda please? | 17:13 |
| Syed__ | sure | 17:13 |
| jimbaker | current topic is demos :) | 17:13 |
| git-harry | jimbaker: do you have a specific list of things that will be done in the demo? | 17:13 |
| antonym | we were kicking around the idea of starting to use the maas agent to populate the database with server info: https://github.com/virgo-agent-toolkit/rackspace-monitoring-agent/pull/950 | 17:13 |
| git-harry | It will make it easier to identify problems | 17:13 |
| jimbaker | git-harry, very good question! thanks | 17:14 |
| jimbaker | so it turns on crud ops, variables, and access via python client and CLI | 17:14 |
| sulo | antonym: i had a chat with maas team about using the agent for audit work few months back | 17:14 |
| sulo | by extending the agent | 17:14 |
| git-harry | jimbaker: so are you going to go through every single one of those options? | 17:15 |
| antonym | yep, i think that would be a really quick way to funnel data in from environments where we don't have a lot of access to scan things | 17:15 |
| jimbaker | git-harry, right now for crud ops we have host deletion failing. which requires me to get some basic changes in i made to alembic setup | 17:15 |
| jimbaker | git-harry, i'm going to go against dusty's doc | 17:15 |
| jimbaker | req doc | 17:15 |
| sulo | antonym: only problem is navigating around rax agent vs its opensource version | 17:15 |
| sulo | at least for us | 17:16 |
| Syed__ | jimbaker: please share that doc | 17:16 |
| antonym | i'd imagine the data we'd need would work in either version? we could probably keep the implementation pretty generic | 17:16 |
| jimbaker | Syed__, you should have access to that doc, but if not i will pm you privately | 17:16 |
| Syed__ | cool | 17:16 |
| jimbaker | sorry tojuvone, we need to get that req doc that rackspace private cloud cleaned up for public distribu | 17:17 |
| sulo | antonym: yeah i think sould | 17:17 |
| tojuvone | jimbaker, np | 17:17 |
| jimbaker | but there's nothing in there that's not in our bugs/blueprints | 17:17 |
| git-harry | jimbaker: I guess I'm suggesting something more explicit, like if you take that doc and write the list of things you want to do to show the state then that can be broken down to verify. | 17:18 |
| jimbaker | just helpful for specific data elements that would be useful for a demo | 17:18 |
| sulo | i was thinking making this an option so 1) we have the generic ssh way of doing audits and gathering data | 17:18 |
| sulo | and 2) using the agent to do the same | 17:18 |
| antonym | yeah, getting into some of these environments can be difficult so having a push from the host would be nice | 17:18 |
| jimbaker | git-harry, they want to be able to see how we could capture hardware and software inventory aspects | 17:19 |
| sulo | given the agent is already doing much of what we want to gather .. it might make sense to focus on that .. given audit though ssh will be acheieved regardless when we work on remediation stuff | 17:19 |
| jimbaker | pretty much the same conversation that antonym and sulo are having, except framing it in a specific usage | 17:19 |
| antonym | sulo: but yeah, i'm plus one on those 2 options | 17:20 |
| jimbaker | so the big missing piece here on crud ops is simple - we need to have updating variables work with the python client; and general variable support in the CLI | 17:21 |
| jimbaker | git-harry, to return to your point, i see the reqs doc as a script for the desired demo. because this is what rackspace support wants from a CMDB - it was explicitly gathered from them | 17:22 |
| jimbaker | since we are in the business of generalization/abstraction, we haven't thought about the specific desired data elements so much. but that's what we will do in the demo itself | 17:23 |
| jimbaker | hope that makes sense! | 17:24 |
| sulo | jimbaker: the cli is also missing networks network-interface and net-devices | 17:24 |
| git-harry | jimbaker: I might just need to take another look at the doc. | 17:24 |
| jimbaker | git-harry, just pm'ed you the link | 17:24 |
| jimbaker | again we will share this publicly asap. i will ask dusty what we need to do to make it public | 17:25 |
| jimbaker | sulo, yeah, we should get that support in. but i don't see that as critical for tues and probably not even thurs demo | 17:26 |
| jimbaker | in my discussion with john wood from FAWS (= fanatical AWS support), this is something you thought would be helpful for their needs | 17:27 |
| jimbaker | i'm not certain if we discussed network modeling support with antonym or not... | 17:27 |
| jimbaker | sulo, so really the important stuff here would presumably be variables to the CLI; and json support so we can show off with jq | 17:28 |
| sulo | ok | 17:30 |
| Syed__ | jimbaker: tried logging but unable to connect, will talk with you on pm once the meeting is over | 17:30 |
| jimbaker | Syed__, np | 17:31 |
| jimbaker | let's briefly switch topics here before we get back in some of these details | 17:33 |
| jimbaker | #topic functional testing | 17:33 |
| sulo | i need to update my patch with pymysql requirement | 17:33 |
| jimbaker | sulo, that would be awesome, since we are almost there on the functional testing changes | 17:34 |
| sulo | but i want to add db clenup for user/project as well .. which i havent done yet | 17:34 |
| sulo | yea, other than that .. my local branch works well | 17:34 |
| jimbaker | can we do that separately? | 17:34 |
| sulo | i have hosts tests that needs to be updated as well | 17:34 |
| sulo | i am still witing on that sqlalchemy change for that | 17:34 |
| sulo | host deletes to be exact | 17:35 |
| jimbaker | ahh, so we are in deadlock in each other :) | 17:35 |
| jimbaker | i've been waiting on you | 17:35 |
| sulo | ? | 17:35 |
| sulo | for what ? | 17:35 |
| jimbaker | so i can have something to test against | 17:35 |
| jimbaker | i like fixes to have corresponding tests | 17:35 |
| jimbaker | sulo, let me give you the alembic diff | 17:36 |
| sulo | i can upload the test if you want to test with it | 17:36 |
| jimbaker | one of these two options works... let's discuss later | 17:37 |
| jimbaker | (immediately after meeting) | 17:37 |
| jimbaker | overall, sounds like we are in good shape with the functional testing updates | 17:38 |
| jimbaker | #topic variable support | 17:38 |
| jimbaker | so we were discussing this before the meeting on #craton | 17:42 |
| jimbaker | the net of it is, the python client when accessing /v1/hosts/$host will get the variables and populate in the host object on the client | 17:43 |
| jimbaker | eg usage like host = craton.hosts.get(item_id=8) will result in host.variables being populated | 17:43 |
| jimbaker | because we do not support PUT with variables against /v1/hosts/$host, this is not symmetric, so the current simple crud model the python client uses will not work. example: craton.hosts.update(item_id=8, variables={'foo': 42, 'bar': [1,2,3,4]}) to replace the variables for this host | 17:44 |
| jimbaker | so some choices here, but the simplest to me would be to keep the symmetry and have the python client use PUT /v1/hosts/$host/variables | 17:47 |
| jimbaker | when using the above update method | 17:47 |
| jimbaker | (the client would hide this distinction) | 17:48 |
| jimbaker | git-harry, sigmavirus, sulo, what say you? | 17:48 |
| sigmavirus | jimbaker: that works for me | 17:49 |
| sulo | did we just decide to do host-vars-for --host=xxx and host-vars-update --host=xxx | 17:49 |
| jimbaker | this doesn't change the CLI aspects we were discussing earlier, which was craton variables-for-RESOURCE or something like that | 17:49 |
| sulo | so that makes cli and python api different | 17:49 |
| sigmavirus | but if we're going to do /v1/hosts/:host_id/variables I'd expect a user to be able to do `host = host.get(id); host.variables.update(...)` | 17:50 |
| sulo | right | 17:50 |
| sigmavirus | sulo: why do people think the cli and python api need to reflect each other? | 17:50 |
| jimbaker | sigmavirus, sulo, i'm good with that | 17:50 |
| sigmavirus | the CLI should be what's most ergonomic | 17:50 |
| jimbaker | sigmavirus, +1 | 17:50 |
| sigmavirus | The Python API should be ergnomic as well | 17:50 |
| sigmavirus | What's ergonomic in bash may not be true in Python and vice-versa | 17:50 |
| sulo | ok, if the vote is thats cool, then i am fine with it | 17:51 |
| jimbaker | and nested objects are a good example | 17:51 |
| jimbaker | yes, we can do jq, but not every usage of say craton host-show should require it :) | 17:52 |
| jimbaker | ok, enough. we have agreed | 17:52 |
| jimbaker | sigmavirus, so yeah, host.variables.update(...) sounds good to me | 17:52 |
| jimbaker | right now if i'm not mistaken host.variables is a simple dict, but making it an object sounds far better | 17:52 |
| jimbaker | given that there's stuff like blame, history, etc, that we want to attach to it | 17:53 |
| jimbaker | in the python client | 17:53 |
| sigmavirus | right | 17:54 |
| thomasem | o/ | 17:55 |
| jimbaker | thomasem, thanks for stopping by | 17:55 |
| thomasem | You bet! | 17:55 |
| sulo | thomasem: o/ | 17:55 |
| jimbaker | thomasem will be joining us to help develop craton! | 17:55 |
| thomasem | That I will. Starting next Tuesday, :) | 17:56 |
| jimbaker | so welcome to the team. and timing sounds excellent! | 17:56 |
| thomasem | Thanks!! | 17:56 |
| sulo | jimbaker: sigmavirus: so whats the net here ? who is done what to get this going for the demo ? | 17:56 |
| sigmavirus | just in time to help us burn craton to the ground for our demo ;) | 17:56 |
| jimbaker | sigmavirus, yep, construct the pyre higher | 17:56 |
| sigmavirus | sulo: I have zero visibility into any of this demo nonsense | 17:56 |
| thomasem | Lol | 17:56 |
| tojuvone | great :) and good stuff the demo and variables for host | 17:57 |
| sigmavirus | No one has included me in craton conversations in over a month | 17:57 |
| sigmavirus | So I just assume I'm succeeding at not being seen | 17:57 |
| sigmavirus | Or in other words "Not it" | 17:57 |
| Syed__ | Same with me sigmavirus | 17:57 |
| Syed__ | i haven't been upto date at all on whats been happening | 17:57 |
| sulo | i dont think other than what we are talking abou there has been much | 17:58 |
| *** david-lyle has quit IRC | 17:59 | |
| sulo | the demo thing is ... i guess something we are expected to do to show progress | 17:59 |
| jimbaker | right, we are just being asked to demo something. the only thing that is not really negotiable are the dates | 18:00 |
| jimbaker | so we have to figure something out, and dusty's req doc seems to be the best starting point | 18:00 |
| jimbaker | sulo, +1 on progress | 18:00 |
| sulo | might also be a good time to record it and send to the community | 18:01 |
| jimbaker | sulo, also +1 | 18:01 |
| sulo | i've been meanign to post vidyo to the ops and dev lists | 18:01 |
| sulo | but just havent made a scrrencast nice enough to do so | 18:01 |
| jimbaker | and sulo is a true master of the impromptu demo | 18:01 |
| jimbaker | so we are in good shape there. just want to make sure that we show all the good dev progress we have made | 18:02 |
| sulo | wait a sec, you expecting me to do this demo ? | 18:02 |
| sulo | :D | 18:02 |
| jimbaker | sulo, ;) | 18:02 |
| jimbaker | so far it has worked well for us. i'm good for the impromptu commentary/comedy bits | 18:04 |
| sigmavirus | jimbaker: you shouldn't have said that until Tuesday | 18:04 |
| jimbaker | sulo, but we can always reverse roles if you want | 18:04 |
| sigmavirus | jimbaker: wait, you do comedy? | 18:04 |
| jimbaker | yep, of the pratfall kind | 18:04 |
| * sigmavirus is teasing | 18:04 | |
| jimbaker | demo goes down into a burning heap | 18:04 |
| sigmavirus | okay, well we're over time | 18:05 |
| jimbaker | anyway, we will figure this out. really i think the key piece is get some key code committed that has been written | 18:05 |
| jimbaker | and finalize variables | 18:06 |
| jimbaker | DONE | 18:06 |
| jimbaker | and we are done | 18:06 |
| jimbaker | #endmeeting | 18:06 |
| openstack | Meeting ended Thu Jan 26 18:06:11 2017 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 18:06 |
| openstack | Minutes: http://eavesdrop.openstack.org/meetings/craton/2017/craton.2017-01-26-16.59.html | 18:06 |
| openstack | Minutes (text): http://eavesdrop.openstack.org/meetings/craton/2017/craton.2017-01-26-16.59.txt | 18:06 |
| openstack | Log: http://eavesdrop.openstack.org/meetings/craton/2017/craton.2017-01-26-16.59.log.html | 18:06 |
| sulo | thomasem: since you are joning from Tuseday, here is something for you ;) https://review.openstack.org/#/c/421337/ | 18:06 |
| sulo | to start looking at | 18:06 |
| thomasem | Great. Thanks!! | 18:06 |
| thomasem | sulo: ^^ | 18:06 |
| tojuvone | For me have my other duties, but now waiting acceptance to be in ops mid-cycle 13th-16th March in Milan | 18:10 |
| *** VW has joined #craton | 18:10 | |
| sulo | tojuvone: you presenting ? | 18:11 |
| tojuvone | sulo, well talked to jimbaker earlier if some of you going. So I could also; just for Craton | 18:12 |
| jimbaker | tojuvone, sounds good. at this time, i don't expect to be going, but maybe sulo can make it. regardless having someone there to discuss craton would be awesome | 18:13 |
| sulo | yeah, i am still undecided. | 18:13 |
| tojuvone | ok | 18:13 |
| tojuvone | For Craton, I'd definately would need somebody to talk about it other than me | 18:15 |
| tojuvone | if going there | 18:15 |
| jimbaker | sulo, it would be awesome if we could have you be there. maybe git-harry as well | 18:17 |
| sigmavirus | hey all, so regarding pagination, do we plan on supporting multiple sort-keys where each key can have its own direction? (per API-WG guidelines)? | 18:18 |
| tojuvone | I thought the 13th-14th would be time to look things within Craton and then see about the meetup on 15th-16th. | 18:19 |
| jimbaker | $121 round trip on british airways for those dates from LHR to MXP... | 18:20 |
| jimbaker | sigmavirus, makes sense. fwiw, i don't see such multiple sort keys as being high priority at this time | 18:21 |
| tojuvone | I am not still 100% sure I get acceptance, but my thing has priority in our side | 18:23 |
| sigmavirus | jimbaker: okay then | 18:23 |
| tojuvone | I get back to "Milan" thingy, when get to know can I go there. | 18:27 |
| jimbaker | tojuvone, awesome, and we need to revisit notifications | 18:31 |
| *** valw has quit IRC | 18:31 | |
| tojuvone | yeah, I am actually taking the notification thing up in Vitrage Pike design session | 18:31 |
| jimbaker | we also briefly discussed the question of maintenance state | 18:31 |
| jimbaker | in tues meeting | 18:31 |
| jimbaker | in terms of further elaboration of the current active property | 18:32 |
| tojuvone | jimbaker, might not be much yet for notification till that (Vitrage), but to discuss they could utilize it when it would come | 18:32 |
| jimbaker | related to this is a transition state when moving devices/resources between clouds | 18:32 |
| jimbaker | which i was asked about separately by another potential user | 18:33 |
| jimbaker | tojuvone, sounds good about the timing with vitrage | 18:33 |
| tojuvone | jimbaker, a bit proactive as nothing yet for the notification here then, but it is good to know plans for that, so can prepare to consume notifications then. | 18:34 |
| jimbaker | tojuvone, right, some form of auditing or notification is a requirement we have been given from rackspace support. i would like for us to design something that can accommodate a range of uses | 18:36 |
| jimbaker | so your input here is highly welcome! | 18:36 |
| *** valw has joined #craton | 18:36 | |
| tojuvone | jimbaker, yes, for me, now, I can just give the use case of that planned host maintenance and what kind of notifications would be needed | 18:38 |
| tojuvone | jimbaker, then another thing is for me to understand how everything can/is done in Craton | 18:38 |
| tojuvone | jimbaker, so can help on making things happen. Demo will be again nice | 18:39 |
| jimbaker | tojuvone, +1 | 18:43 |
| *** valw has quit IRC | 19:01 | |
| *** harlowja has quit IRC | 19:02 | |
| *** VW has quit IRC | 19:04 | |
| *** VW has joined #craton | 19:07 | |
| *** valw has joined #craton | 19:22 | |
| jimbaker | sulo, https://gist.github.com/jimbaker/9a19d4e45ac73aa7db63edb54526e09b | 19:23 |
| jimbaker | so fairly small change, and seems to work well. just want to verify against your testing | 19:23 |
| jimbaker | please note i did choose to change how fk constraints are setup so it models more closely how we do this in models.py - and also make it easy to name the constraint | 19:23 |
| jimbaker | i have a change i have been planning to do for a while to refactor the remaining alembic pk/fk constraint setups to do the same | 19:23 |
| *** david-lyle has joined #craton | 19:45 | |
| sulo | sigmavirus: i have commented on that comment :) https://review.openstack.org/#/c/424179 | 20:07 |
| sigmavirus | sulo: that comment is much more clear =P | 20:08 |
| sulo | jimbaker: git-harry please review ^ i am just nit picking that code but would love to get that in for the demo | 20:08 |
| sigmavirus | sulo: I'm almost at the end of the pagination spec | 20:08 |
| sigmavirus | (adding in links to response bodies) | 20:08 |
| sigmavirus | That might be something to hold off on though because cratonclient doesn't understand it yet | 20:08 |
| sulo | ah true | 20:08 |
| sigmavirus | Although it'd make auto-pagination in cratonclient easier | 20:08 |
| sulo | would be awesome to show tuesday though | 20:08 |
| sigmavirus | Well what you commented on can absolutely go in now | 20:09 |
| sigmavirus | There's' no changes to response body in there | 20:09 |
| sigmavirus | The next patch I submit, on the other hand, not so much =P | 20:09 |
| sulo | ok | 20:09 |
| *** harlowja has joined #craton | 20:09 | |
| *** valw has quit IRC | 20:34 | |
| *** valw has joined #craton | 20:47 | |
| sigmavirus | my kingdom for a batch api | 20:58 |
| mudpuppy | kindom of hearts | 20:59 |
| * sigmavirus never played that | 21:01 | |
| *** valw has quit IRC | 21:09 | |
| sigmavirus | I just pushed up a wip for the hypermedia linking | 21:17 |
| sigmavirus | I haven't thoroughly tested it | 21:17 |
| sigmavirus | But I'd love to write functional tests for it | 21:17 |
| sigmavirus | *nudge nudge* | 21:18 |
| *** valw has joined #craton | 21:49 | |
| jimbaker | sulo, i'm absolutely fine with that code. my only nit pick was about pagination_params vs pagination_args. your nit pick seems valid too, but i'm ready to +2 and revisit | 21:54 |
| *** valw has quit IRC | 21:54 | |
| *** VW has quit IRC | 22:27 | |
| *** VW has joined #craton | 22:27 | |
| *** VW has quit IRC | 22:31 | |
| *** VW has joined #craton | 22:33 | |
| *** david-lyle has quit IRC | 23:51 | |
| *** david-lyle has joined #craton | 23:54 | |
Generated by irclog2html.py 2.14.0 by Marius Gedminas - find it at mg.pov.lt!