Wednesday, 2014-12-17

*** egafford has quit IRC00:04
*** Longgeek has joined #openstack-sahara00:54
*** Longgeek has quit IRC00:58
*** witlessb has quit IRC01:06
*** Poornima has joined #openstack-sahara01:51
*** hdd has quit IRC02:56
*** Krast has quit IRC03:13
*** zhidong has quit IRC03:41
*** crobertsrh has joined #openstack-sahara04:25
*** Networkn3rd has joined #openstack-sahara04:26
*** Networkn3rd has quit IRC04:27
*** hdd has joined #openstack-sahara04:34
*** crobertsrh is now known as _crobertsrh04:35
*** hdd_ has joined #openstack-sahara04:42
*** hdd has quit IRC04:43
*** dmitryme has quit IRC04:55
*** dmitryme has joined #openstack-sahara04:56
*** tellesnobrega has quit IRC05:03
*** tellesnobrega has joined #openstack-sahara05:04
*** hdd_ has quit IRC05:19
*** Networkn3rd has joined #openstack-sahara06:00
*** hdd has joined #openstack-sahara06:03
*** hdd has quit IRC06:41
*** Networkn3rd has quit IRC06:49
*** pcaruana has joined #openstack-sahara07:16
*** Poornima has quit IRC08:04
*** Poornima has joined #openstack-sahara08:18
*** Longgeek has joined #openstack-sahara08:33
*** zhidong has joined #openstack-sahara08:47
*** tnovacik has joined #openstack-sahara08:49
openstackgerritMerged stackforge/sahara-ci-config: Add Vanilla 2.6.0 jobs  https://review.openstack.org/14176208:51
*** tnovacik has quit IRC08:59
*** tnovacik has joined #openstack-sahara09:06
*** witlessb has joined #openstack-sahara09:07
*** tnovacik has quit IRC09:13
*** tnovacik has joined #openstack-sahara09:33
*** tnovacik has quit IRC10:03
*** skolekonov has joined #openstack-sahara10:06
openstackgerritDenis Egorenko proposed stackforge/sahara-ci-config: Fix integration_cleanup for Vanilla 2.6  https://review.openstack.org/14241310:19
openstackgerritMerged stackforge/sahara-ci-config: Fix integration_cleanup for Vanilla 2.6  https://review.openstack.org/14241311:09
*** Poornima has quit IRC11:50
openstackgerritAlexander Ignatov proposed openstack/sahara: Add one more sample for pig job examples  https://review.openstack.org/14178213:13
*** stannie has joined #openstack-sahara13:14
openstackgerritDenis Egorenko proposed stackforge/sahara-ci-config: Temporary disable heat engine  https://review.openstack.org/14243913:22
*** hdd has joined #openstack-sahara13:50
*** miqui has joined #openstack-sahara14:07
*** tmckay has joined #openstack-sahara14:10
*** egafford has joined #openstack-sahara14:16
*** _crobertsrh is now known as crobertsrh14:19
*** hdd has quit IRC14:36
*** pcaruana has quit IRC14:51
*** IvanBerezovskiy1 has quit IRC14:58
*** IvanBerezovskiy has joined #openstack-sahara14:59
*** hdd has joined #openstack-sahara15:32
*** tellesnobrega has quit IRC15:38
*** miqui_ has joined #openstack-sahara15:48
*** skolekonov has quit IRC15:58
SergeyLukjanovfolks, we already have a kilo-1 release ;)16:00
*** Poornima has joined #openstack-sahara16:00
*** guo has joined #openstack-sahara16:01
*** Networkn3rd has joined #openstack-sahara16:02
elmikoSergeyLukjanov: yay!16:05
*** guo has quit IRC16:07
crobertsrh:)16:07
*** Poornima has quit IRC17:05
*** hdd has quit IRC17:13
*** IvanBerezovskiy has left #openstack-sahara17:17
openstackgerritChad Roberts proposed openstack/sahara-specs: Spec for template editing  https://review.openstack.org/14044817:38
openstackgerritTrevor McKay proposed openstack/sahara: Add options supporting DataSource identifiers in job_configs  https://review.openstack.org/14224817:53
tmckaySo I have a gate unit test that is failing, but the .testrepository logs don't seem to be available for unit tests, or Sahara logs either.  I am experimenting with trapping the assertionError myself and embedding debug information in a new AssertionError with re-raise, so that I can see messages to myself in console.html17:58
tmckayAnybody else have a good solution for this?17:58
tmckayI have a unit test that breaks in CI but does not break locally17:58
tmckaydon't know how else to make "print()" work, or log(...)17:58
tmckaystdout from test code should be available, imho18:00
tmckaybut if it is, I don't know where ...18:00
*** Networkn3rd has quit IRC18:03
*** Networkn3rd has joined #openstack-sahara18:04
openstackgerritTrevor McKay proposed openstack/sahara: Add options supporting DataSource identifiers in job_configs  https://review.openstack.org/14224818:07
elmikotmckay: did you get any traction?18:18
tmckaywell, waiting for CI to run18:19
tmckaybased on what I did locally, it should tell me what line in the real proxy.py returned True when False was expexted18:19
elmikook, seems really weird18:20
tmckayyeah, it should produce locally18:22
tmckayhmm, might have a theory18:38
elmikok18:40
openstackgerritTrevor McKay proposed openstack/sahara: Add options supporting DataSource identifiers in job_configs  https://review.openstack.org/14224819:00
tmckayelmiko, I left the return value for a mocked routine unspecified, and it gave a mock value back which was compared using " > 0"19:01
tmckayin the debugger, it says "False"19:01
tmckaybut, what is that based on?19:01
tmckayassuming it could just as well be True19:02
tmckaymock > 0 is odd at best19:02
tmckayI'm surprised it wasn't throwing an exception, actually.  Anyway, I fixed that bit up, we'll see what happens19:03
*** Networkn3rd has quit IRC19:04
*** Networkn3rd has joined #openstack-sahara19:04
elmikotmckay: interesting, not sure i understand fully19:04
tmckayelmiko, well, it ended up doing "if count_routine() > 0" in proxy.py, where count_routine had been mocked in the test code.  But the return value was left unset19:05
tmckaypdb says the return value was a mock object :)19:06
tmckayI'm wondering if "mock > 0" is indeterminate, or based on some attribute in the object that can change19:06
tmckayso that I could have different results locally vs CI19:07
tmckayonly smoking gun I could find19:07
elmikohuh, good find19:09
*** hdd has joined #openstack-sahara19:10
*** oikawa has quit IRC19:20
openstackgerritMichael McCune proposed openstack/sahara: Adding database detection to migration tests  https://review.openstack.org/14257820:59
elmikoruhe: i think this will fix the db presence issue ^^21:00
*** Networkn3rd has quit IRC21:02
openstackgerritMerged stackforge/sahara-ci-config: Temporary disable heat engine  https://review.openstack.org/14243921:11
tmckaycrobertsrh, ping21:12
crobertsrhyes?21:12
tmckaylooking at the template editing spec.  I wonder if we can do something simple, like create template.1 automatically if template is edited and referenced21:13
tmckaywe talked about this a little previously21:13
tmckayeverything in the UI is name based, everything in the database is id based21:13
crobertsrhright...the oslo-versioned-objects stuff might be a good fit for that21:14
tmckayif we renamed an existing template with a .X version number, then the new template would show up with the expected name and existing objects in the db would still be linked together by id number21:14
crobertsrhare names unique across tenants?21:15
tmckayit wasn't clear to me that that was what they were for.21:15
tmckaymaybe I should read more closely21:15
crobertsrhIt might not be a perfect fit. Mike mentioned it yesterday and it sounded potentially promising21:15
tmckaysounded more like a versioned API kind of thing, to support compatibility over different versions of objects21:16
crobertsrhOf course, if we just did our own .X magic, that may work too21:16
tmckayit would be simple21:16
crobertsrhTrue...not necessarily the real right fit.  Homegrown .X may be better, and potentially simpler21:16
crobertsrhSo far, the spec is more SPECulation21:17
tmckaywe would just need some numbering scheme, and maybe decide what to do (or disallow) if someone edited a template.X21:17
crobertsrhHmm...somewhere in my head, this won't work....trying to articulate it now...21:18
crobertsrhSo...if I have a cluster template C today that references ngt N, then we edit N.  The original N becomes N.X and C still references that?  That doesn't seem like what the desired behavior is.21:19
crobertsrhI was thinking that C should pick-up the changes to N.  Only existing clusters would retain their link to N.X.21:20
crobertsrhI should probably specify those cases in the spec, whatever behavior we agree on.21:20
elmikocrobertsrh: +121:22
tmckayhmmm.  I could imagine that it would chain.  If nothing is ultimately referenced by a cluster, we would just change N in place.  If N or C was tied to a running cluster, we would have to create C.x and N.x for the existing cluster21:22
tmckayand then C and N would be the right thing21:23
tmckaythe whole trouble is if there is an existing cluster that references C that references N21:23
tmckayhave to revisit how the links are done21:24
tmckayI'm fuzzy at the moment21:24
crobertsrhYeah, my clarity comes and goes21:24
crobertsrhI'm pretty sure we do NOT want to affect running clusters.21:25
tmckayagreed21:25
crobertsrhI'm pretty sure we DO want NGT changes to be picked-up in cluster templates21:25
tmckayI'm trying to come up with a way to snapshot existing info tied to a cluster or clusters21:25
tmckayalso agreed21:25
crobertsrhOk.  I'll try to take a look as well, but you are much better versed there than I am.21:30
tmckaycrobertsrh, in my mind, the fundamental difference between copy and edit is that in the edit case we're doing rename magic so no info that is depended on is destroyed, and the user has objects with the same name but different info when they are done21:30
tmckaycan it be done?  I don't know21:30
crobertsrhHeh21:30
crobertsrhMaybe a new field for "version"21:31
crobertsrhnah, that doesn't work either21:31
elmikowe could do something like git and create a previous-ref field that points to a newly created uuid for the older object info, then the updated object can retain the same uuid.21:33
crobertsrhMaybe the edited version keeps the original ID, we make a copy of the original object (with new ID) and update those refs in the database?21:34
elmikoexactly21:34
crobertsrhgreat minds21:34
elmikoi think the edited version has to keep the original id for compatibility21:34
tmckaythat's what I'm envisioning21:34
crobertsrhI think that's the ticket21:35
tmckayid doesn't matter so much, it's the names that are troublesome I think21:35
crobertsrhOh, right.21:35
elmikotmckay: i would think id matters for things like endpoints21:35
crobertsrhWe may need to .X them21:35
tmckayI think the originals would preseve their ids and just have their names changed21:37
tmckayNew stuff would get new ids21:37
tmckaythat way all the foreign key stuff in the db is preserved21:37
tmckaynames are unique, but not used as foreign keys I believe21:37
tmckaycrobertsrh, earlier question, I think every table has a tenant_id, an id, and a name21:38
elmikotmckay: ok, we're on the same page. i thought you were saying that the ids don't matter in terms of updating.21:38
tmckayso, effectively, names are unique across tenants.  They're all in the same db21:39
tmckayelmiko, well, I was thinking of onscreen presentation.  Users want the names to be what they expect. You're right, though, way less work if existing links remain untouched21:41
elmikotmckay: totally agreed about names. no question. i just think it's important to have the uuids be the same to reduce client side mess with renamed endpoints21:42
crobertsrhSo, duplicate uuids are kosher?21:43
tmckayyou're thinking of URLs where the id is part of the path, and somone has it cached?21:43
elmikocrobertsrh: no21:43
tmckayno, duplicate ids are impossible21:43
elmikotmckay: something along those lines21:43
tmckayyeah, we don't want to break that21:44
tmckayIn my mind it's simple21:44
tmckay1) old object gets new name21:44
tmckay2) new object gets old name and new id21:44
tmckayIf you have to bubble up from ngt to cluters, you repeat the operation a level up21:44
elmikoooh, just had a thought21:45
* crobertsrh is updating the spec on the fly to avoid forgetting any of our wisdom.21:45
tmckaybrb21:45
elmikowhen the original object is updated, and a new "reference" object is created for the previous version the name could be some variation of the original uuid.21:46
crobertsrhname.origuuid?21:47
elmikothat could work, if we only keep one historical copy21:48
crobertsrhwe could need multiples21:48
elmikoso maybe, name.rev.origuuid or something21:49
crobertsrh[original...launch cluster, edit, launch another cluster, edit] would require multiple copies to be kept.21:49
elmikoyea totally21:50
crobertsrhA little ugly since the user will see those uuids show up in the names in the UI21:51
elmikoooh good point21:52
elmikoman... this could get ugly21:52
crobertsrhIs the template itself just stored as a blob?21:53
* crobertsrh could look, but found it easier to ask.21:53
* crobertsrh looked. Nope21:54
elmikoare you saying that maybe the template should be stored in the db or something?21:54
crobertsrhjust thinking about keeping all necessary versions in the same record21:55
crobertsrhOr, probably a separate table.21:55
crobertsrhSort of the "microversion" impl21:56
elmikoyea21:56
elmikomaybe we'll want to have a checkbox to delete the old version when updating to reduce the need for people to manually the delete the old ones?21:57
crobertsrhoriginal table would just contain original name, id...and point to the new table that contains all the microversions21:57
elmikonew table could definitely work magic for this, assuming no one has an issue with another db migration21:58
crobertsrhWe should be able to delete any old one that isn't referenced by a running cluster21:58
elmikook, so old ones might not be a huge issue21:58
crobertsrhI don't think so.  They could accumulate in a long-running high use system, but they don't really take much room to store.21:58
elmikoseemed like keeping track of them might be more the issue21:59
openstackgerritTrevor McKay proposed openstack/sahara: Add options supporting DataSource identifiers in job_configs  https://review.openstack.org/14224822:01
crobertsrhI don't think db migrations should be a limiting factor.22:02
crobertsrhOr....we could just say that can't edit a template that is referenced by a running cluster.22:03
crobertsrhI think things get simple in that case22:03
crobertsrhLet them make their own copies explicitly.22:04
elmikoi don't think migrations should be an issue either, i just know it's a factor to consider.22:04
crobertsrhIt would be congruent with not letting users delete templates that are used by a cluster.22:04
openstackgerritChad Roberts proposed openstack/sahara-specs: Spec for template editing  https://review.openstack.org/14044822:10
crobertsrhIs tomorrow's meeting early or late?22:11
crobertsrhWe should talk about this at the meeting.22:11
crobertsrhOk, I may be talking to myself now.22:12
elmikoearly22:13
crobertsrhThanks22:13
elmikosorry, got like 4 different channels i'm watching lol22:13
crobertsrhI don't think zimbra has a good way to juggle the meetings, does it?22:13
crobertsrhheh :)22:13
openstackgerritTrevor McKay proposed openstack/sahara: Add options supporting DataSource identifiers in job_configs  https://review.openstack.org/14224822:13
crobertsrhMy solution....set both meeting times to show up every week22:13
elmikoi dunno, my thunderbird is not syncing with zimbra cal at all. i'm gonna just make 2 entries in my cal for our meetings22:13
elmikolol, nice solution22:13
crobertsrhBonus is that fewer real meetings will be booked with me since I'm "busy" more22:14
crobertsrhI always feel like I've been pardoned when a phantom meeting request pops-up22:14
crobertsrhI have the same thing for the doc team meetings22:14
*** crobertsrh is now known as _crobertsrh22:15
*** egafford has quit IRC23:35
*** hdd has quit IRC23:58

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