*** ruhe2 has joined #openstack-sahara | 01:13 | |
*** ruhe has quit IRC | 01:13 | |
*** NikitaKonovalov has quit IRC | 01:13 | |
*** ruhe2 is now known as ruhe | 01:13 | |
*** NikitaKonovalov has joined #openstack-sahara | 01:31 | |
openstackgerrit | ChangBo Guo(gcb) proposed a change to openstack/sahara: Clean up sqlachemy session usage https://review.openstack.org/84041 | 01:48 |
---|---|---|
*** IlyaE has quit IRC | 02:30 | |
openstackgerrit | ChangBo Guo(gcb) proposed a change to openstack/sahara: Clean up sqlachemy session usage https://review.openstack.org/84041 | 03:33 |
*** IlyaE has joined #openstack-sahara | 04:27 | |
*** NikitaKonovalov2 has joined #openstack-sahara | 04:38 | |
*** alazarev has joined #openstack-sahara | 04:39 | |
*** NikitaKonovalov has quit IRC | 04:39 | |
*** NikitaKonovalov2 is now known as NikitaKonovalov | 04:39 | |
*** alazarev has quit IRC | 04:50 | |
*** akuznetsov has joined #openstack-sahara | 04:55 | |
*** Ch00k has joined #openstack-sahara | 05:23 | |
*** alazarev has joined #openstack-sahara | 05:28 | |
openstackgerrit | Jenkins proposed a change to openstack/sahara: Imported Translations from Transifex https://review.openstack.org/82719 | 06:06 |
*** IlyaE has quit IRC | 06:16 | |
*** alazarev has quit IRC | 06:24 | |
*** dmitryme has joined #openstack-sahara | 06:25 | |
*** IlyaE has joined #openstack-sahara | 06:36 | |
*** IlyaE has quit IRC | 06:52 | |
*** Ch00k has quit IRC | 07:10 | |
*** Ch00k has joined #openstack-sahara | 07:12 | |
*** Ch00k has quit IRC | 07:25 | |
*** akuznetsov has quit IRC | 07:59 | |
*** akuznetsov has joined #openstack-sahara | 07:59 | |
*** witlessb has joined #openstack-sahara | 08:00 | |
*** witlessb has quit IRC | 08:01 | |
*** witlessb has joined #openstack-sahara | 08:01 | |
*** Ch00k has joined #openstack-sahara | 08:03 | |
*** akuznetsov has quit IRC | 08:06 | |
*** akuznetsov has joined #openstack-sahara | 08:32 | |
*** skolekonov has joined #openstack-sahara | 08:35 | |
openstackgerrit | ChangBo Guo(gcb) proposed a change to openstack/sahara: Clean up sqlachemy session usage https://review.openstack.org/84041 | 08:40 |
*** dmitryme has quit IRC | 08:58 | |
*** dmitryme has joined #openstack-sahara | 09:11 | |
*** tosky has joined #openstack-sahara | 09:54 | |
*** themistymay has joined #openstack-sahara | 10:37 | |
themistymay | Good morning/evening! | 10:44 |
themistymay | SergeyLukjanov, ping | 10:45 |
*** skostiuchenko has quit IRC | 10:54 | |
*** themistymay_2 has joined #openstack-sahara | 11:05 | |
*** themistymay_2 has left #openstack-sahara | 11:05 | |
*** themistymay has quit IRC | 11:06 | |
*** themistymay has joined #openstack-sahara | 11:06 | |
SergeyLukjanov | themistymay, morning ;) | 11:23 |
*** ErikB has joined #openstack-sahara | 11:37 | |
*** ErikB has quit IRC | 12:02 | |
SergeyLukjanov | dmitryme volunteered to update installation guide | 12:12 |
dmitryme | SergeyLukjanov: yep, I am doing it right now | 12:13 |
*** tellesnobrega has joined #openstack-sahara | 12:21 | |
SergeyLukjanov | mattf, jspeidel, re removing auto-creation of db | 12:24 |
SergeyLukjanov | + dmitryme ^^ | 12:24 |
SergeyLukjanov | so, the issue is that we support db migrations and we should disable db auto-creation from metadata (w/o migrations) | 12:24 |
openstackgerrit | Sergey Reshetnyak proposed a change to openstack/sahara: Fix default repo links and tarball links for IDH https://review.openstack.org/84118 | 12:25 |
SergeyLukjanov | because "create db from meta" != "create db using from migrations in 100% cases" | 12:25 |
SergeyLukjanov | dmitryme explained this issue well in https://bugs.launchpad.net/sahara/+bug/1300190 | 12:26 |
dmitryme | I actually didn't put a point about difference in table creation into the bug, I think it is not needed | 12:27 |
dmitryme | we simply don't need two ways to create DB | 12:27 |
SergeyLukjanov | current approach was already approved months ago in https://review.openstack.org/#/c/68631/2/savanna/main.py | 12:29 |
SergeyLukjanov | dmitryme, ++ | 12:29 |
SergeyLukjanov | so, it's a bug of the applying migrations support | 12:29 |
SergeyLukjanov | mattf, jspeidel, ^^ | 12:30 |
openstackgerrit | Sergey Reshetnyak proposed a change to openstack/sahara: [IDH] Integration tests for IDH 3.0.2 https://review.openstack.org/79719 | 12:31 |
openstackgerrit | Sergey Lukjanov proposed a change to openstack/sahara: Fix db management: don't autocreate db on start https://review.openstack.org/82750 | 12:33 |
*** crobertsrh has joined #openstack-sahara | 12:37 | |
*** akuznetsov has quit IRC | 12:52 | |
*** sballe has joined #openstack-sahara | 12:57 | |
mattf | SergeyLukjanov, dmitryme, i know users and docs will have to be changed if you proceed. i'd like to know what the downside is of leaving the code as is and waiting until after feature freeze to fix/clean it up. | 13:00 |
dmitryme | mattf: we actually already did this a couple month ago, see https://review.openstack.org/#/c/68631/2/savanna/main.py | 13:03 |
*** akuznetsov has joined #openstack-sahara | 13:03 | |
dmitryme | the problem is that we did creation from metadata in one more place | 13:03 |
dmitryme | which is fixed by Sergey's current patch set | 13:03 |
dmitryme | BTW the need to manually create DB is already covered in docs | 13:04 |
dmitryme | see http://docs.openstack.org/developer/sahara/userdoc/installation.guide.html | 13:04 |
dmitryme | here we ask user to call sahara-db-manage during the installation | 13:04 |
mattf | dmitryme, only for the venv case | 13:05 |
dmitryme | aha, you mean we forgot to make the change to the RDO part, right? | 13:06 |
mattf | my position is we're in feature freeze and should not be making semantic changes unless they solve a blocking bug, one that prevents users from using sahara. | 13:06 |
mattf | i agree this is something that should be resolved. i simply question the urgency of it. | 13:07 |
*** ErikB1 has joined #openstack-sahara | 13:07 | |
mattf | dmitryme, the rdo bits definitely need to change. do the fuel? | 13:07 |
* mattf lowers multitasking level, tries to use proper english | 13:09 | |
aignatov | mattf: as I currently see installation procedures via Fuel in our docs, the procedures will be the same :) | 13:10 |
*** elmiko has joined #openstack-sahara | 13:11 | |
dmitryme | mattf: we need to remove db creation from metadata anyway: once DB is created from metadata, it could not be migrated with alembic. I.e. such users will be stuck with Icehouse release | 13:11 |
elmiko | so, who's ready for some documentation! :D | 13:12 |
dmitryme | elmiko: I already work on installation | 13:12 |
crobertsrh | I am going to look at the dashboard docs right now. | 13:13 |
dmitryme | guys: don't forget to mention on which part of the docs you work in https://blueprints.launchpad.net/sahara/+spec/update-docs-icehouse | 13:14 |
elmiko | dmitryme, crobertsrh, awesome! i'll update the blueprint if it hasn't been already | 13:14 |
dmitryme | otherwise we will end up fixing the same things | 13:14 |
dmitryme | and a word of warning: after you edit the work items, refresh the page and make sure your changes are there. The thing is if two people simultaneously update the items, the last one wins :-) | 13:16 |
mattf | dmitryme, not being able to upgrade is the kind of information i'm looking for that could justify the urgency | 13:17 |
elmiko | dmitryme: thanks | 13:17 |
dmitryme | mattf: right, I think that matters | 13:17 |
aignatov | elmiko: I will change heat related stuff | 13:18 |
aignatov | in the docs | 13:18 |
dmitryme | BTW I am going to write a new page, which describes which configuration parameters user should change in a simple case (both for Sahara and Sahara Dashboard) | 13:20 |
elmiko | aignatov: ack | 13:20 |
dmitryme | from my experience I see that we have rather big amount of parameters and their meaning is not obvious | 13:20 |
elmiko | dmitryme: sounds good, i'll add new work items for the config parameters and the heat related stuff | 13:22 |
*** tosky has quit IRC | 13:32 | |
aignatov | folks, do we plan to add new pages or only updates of existing ones? | 13:40 |
*** tosky has joined #openstack-sahara | 13:40 | |
elmiko | it sounds like dmitryme is going to add a new page | 13:41 |
*** mattf is now known as _mattf | 13:43 | |
dmitryme | elmiko: I do | 13:47 |
dmitryme | aignatov: see several lines above ^^ | 13:47 |
aignatov | dmitryme: lol, I have to visit oculist | 13:48 |
*** sreshetnyak has quit IRC | 14:02 | |
*** tmckay has joined #openstack-sahara | 14:07 | |
tmckay | elmiko, forgot to open pidgin and join the fun :) What's on tap for doc day? | 14:08 |
tmckay | elmiko, where to begin? | 14:08 |
elmiko | https://blueprints.launchpad.net/sahara/+spec/update-docs-icehouse , pick something that looks fun :) | 14:08 |
tmckay | okey doke | 14:09 |
elmiko | tmckay: just be sure to update the blueprint or give me a heads up and i'll update it | 14:11 |
tmckay | elmiko, rename Savanna to Sahara -- what is that? A note about the rename, or looking for Savanna instances still in the docs? | 14:12 |
elmiko | i was wondering that too, i think we need to ask SergeyLukjanov. there are only a few url references to savanna left, and the python-django-savanna package. | 14:12 |
elmiko | SergeyLukjanov: ping | 14:13 |
tmckay | Okay, I can work on REST api docs I suppose, and make sure everything there is still accurate. URLs, data passed in/out, etc | 14:14 |
elmiko | sounds good! | 14:14 |
ErikB1 | Is there way to indicate which items that you sign up for in https://blueprints.launchpad.net/sahara/+spec/update-docs-icehouse | 14:16 |
ErikB1 | I will take the HDP items | 14:16 |
elmiko | ErikB1: if you can't edit the blueprint just give me a note and i'll put your name there | 14:16 |
dmitryme | ErikB1: you can do that by editing Work Items | 14:16 |
ErikB1 | ok | 14:16 |
dmitryme | ErikB1, tmckay: note after you edit the work items, refresh the page and make sure your changes are there. The thing is if two people simultaneously update the items, only the changes of the last one apply | 14:17 |
ErikB1 | dmitryme, thanks. I won. | 14:18 |
dmitryme | :-) | 14:18 |
ErikB1 | Also, I would like to pull out capabilities of various plugins and stick into a separate table vs. sprinkling info through out docs. | 14:19 |
elmiko | ErikB1: sounds good, are you going to create a new page? | 14:19 |
*** alazarev has joined #openstack-sahara | 14:20 | |
ErikB1 | elmiko, I was going to stick it at the bottom of the features page. | 14:20 |
elmiko | ok, cool | 14:20 |
dmitryme | ErikB1: sounds good to me as well | 14:20 |
openstackgerrit | Alexander Ignatov proposed a change to openstack/sahara: Heat docs update https://review.openstack.org/84143 | 14:22 |
aignatov | elmiko: I've have started docs update bp :) | 14:22 |
elmiko | :) | 14:22 |
aignatov | ^^ | 14:22 |
ErikB1 | I see, manual 2PC | 14:22 |
elmiko | i'm going to take a look at the "Setting Up a Development Environment" page | 14:23 |
ErikB1 | Does anyone know why the Horizon/Grizzly stable branch is no longer? | 14:23 |
tmckay | aignatov, hi. Are you getting emails from OpenStack about summit? I got one today ... it says if we have a demo, we should notify our speaker manager immediately (not sure why) | 14:26 |
aignatov | tmckay: who is exact sender of this mail? | 14:27 |
* tmckay pms | 14:28 | |
dmitryme | ErikB1: I think that is because there is no development at all on this version | 14:28 |
dmitryme | ErikB1: you will find Grizzly and older versions in tags | 14:29 |
ErikB1 | dmitryme, tags? | 14:29 |
*** sballe has quit IRC | 14:29 | |
dmitryme | are you looking at Horizon through github web UI? | 14:29 |
ErikB1 | dmitryme, yes. I a see now that it's not just Horizon but also all other components | 14:30 |
dmitryme | ErikB1: when you click on branch, there are two tabs in the pop-up: "Branches" and "Tags" | 14:31 |
tmckay | elmiko and friends, so if we are testing code against docs, the current tip of master is what we want to use, yes? | 14:31 |
tmckay | aignatov, ^^ | 14:31 |
elmiko | tmckay: i guess so? | 14:31 |
dmitryme | tmckay: that is my thinking as well | 14:31 |
tmckay | elmiko, ;-) Heavy is the head that wears the crown | 14:31 |
elmiko | lol | 14:32 |
tmckay | dmitryme, thanks | 14:32 |
ErikB1 | dmitryme, I see it now. Thanks. | 14:32 |
*** themistymay has quit IRC | 14:37 | |
*** IlyaE has joined #openstack-sahara | 14:59 | |
*** alazarev has quit IRC | 15:00 | |
*** dmitryme has quit IRC | 15:03 | |
elmiko | if i want to create a review for this blueprint, do i use the partial-implements and a new change-id? | 15:19 |
crobertsrh | tmckay: Is it true that JobExecution no longer returns the job configs? | 15:23 |
tmckay | crobertsrh, yes. | 15:24 |
crobertsrh | doh! | 15:24 |
tmckay | There could be credentials in there | 15:24 |
crobertsrh | was that intentional? | 15:24 |
tmckay | crobertsrh, do you need them? | 15:24 |
crobertsrh | The "relaunch" functionality requires that info | 15:24 |
tmckay | oh no | 15:24 |
crobertsrh | I just went to relaunch a job and noticed :( | 15:25 |
crobertsrh | I'm guessing it's unlikely that the config info will return since it seems to be a security concern? | 15:26 |
tmckay | crobertsrh, hmmm. The trouble is we need more sophisticated screening to get rid of credential values. It's possible. dmitryme and I talked about a custom filter function | 15:26 |
tmckay | aignatov, SergeyLukjanov, filtering job_configs broke relaunch ^^ oops | 15:27 |
tosky | quick question not related with documentation: I restarted my system (devstack-based) and I rejoined the stack. | 15:27 |
tosky | There was an active cluster, after the restart (of the system and of openstack) the VM instances are in the "shutdown" state, but the cluster is still marked "active" | 15:28 |
crobertsrh | It also kinda cripples the Job Execution details page....it would show any job config before (now currently not "broken", but that part is empty) | 15:28 |
tosky | wouldn't be better to mark it as "inactive" with a button for restarting the instances (*) in such a cases? | 15:29 |
IvanBerezovskiy | mattf, could you please take a look on https://review.openstack.org/#/c/83062/ ? | 15:29 |
tosky | (*) maybe a bit complicated, as the instances states could be not the same | 15:29 |
tmckay | crobertsrh, definitely unintended consequences, apologies. I think we have to do something better. Fixing a "bug" and removing functionality seems like a bad idea to me | 15:31 |
*** Ch00k has quit IRC | 15:31 | |
tmckay | maybe the custom filter function is the way to go in this case | 15:31 |
crobertsrh | What would the "custom filter" solution look like? | 15:32 |
tmckay | here is the review for the change, btw https://review.openstack.org/#/c/82883/ | 15:32 |
crobertsrh | doh, looks like I picked the wrong CR to not review | 15:33 |
tmckay | crobertsrh, instead of just using the blanket "_filter_fields" param, the code that applies the filter_field when generating the wrapped dict would check the class for a custom filter method and run that | 15:33 |
tmckay | crobertsrh, JobExecution would effectively descend through it's own fields. In the case of job_configs we'd have to do something like check for the strings "username" and "password" | 15:34 |
crobertsrh | I suspect that the relaunch would still be broken if any data were left out though. If a job required a username/password and we can't supply that on relaunch, we're still probably toast. | 15:35 |
tmckay | crobertsrh, the only credentials we have at the moment really are swift credentias, but being smart about how to find credentials in general could be tricky. We could produce a "blacklist" of key names, I suppose | 15:35 |
crobertsrh | Unless maybe the filtered code could give us a hint that something is missing....we could probably prompt the user for it at relaunch-time in that case | 15:35 |
tmckay | crobertsrh, the usr/passw comes from the data sources, generally | 15:36 |
crobertsrh | right | 15:36 |
tmckay | and it's filled on when the workflow xml is generated. So I think it might still work ... | 15:36 |
crobertsrh | We're probably ok if it's just data source | 15:36 |
crobertsrh | those get re-chosen at re-launch time and don't require the user to know the credentials | 15:37 |
tmckay | "args" on a Java action is harder -- that could be anything, and we have no way to know whether or not to screen those | 15:37 |
crobertsrh | Yeah, args is where we'd fall on our face | 15:37 |
tmckay | we might need a "hide args" button | 15:37 |
tmckay | which voluntarily says you have to respecify on relaunch | 15:38 |
tmckay | crobertsrh, we went for the easy fix for the bug since we were in feature freeze. But, it's not right. | 15:38 |
elmiko | i'm looking at the docs for setting up a dev environment, and it mentions using devstack. currently devstack does not run sahara by default, i'm thinking about adding a note here about enabling it in local.conf, is that appropriate or should i redirect to the devstack docs? | 15:39 |
tmckay | crobertsrh, if you want to test without it you can remove job configs in filter_fields for JobExecution. Maybe I can come up with a custom filter solution with low impact | 15:39 |
crobertsrh | "need to respecify args" might be fine. If the dashboard can know that args (or whatever) was filtered out, we can prompt for whatever to be entered again. Not totally ideal, but might be reasonable. | 15:39 |
*** dmitryme has joined #openstack-sahara | 15:40 | |
tmckay | dmitryme, ^^ the job_configs filter broke relaunch from the UI | 15:40 |
crobertsrh | I might do that so I can mention it in the docs | 15:40 |
tmckay | dmitryme, unintended side effect. Maybe we need your custom filter idea after all | 15:40 |
dmitryme | tmckay: I'd rather do release without fix and make fix with custom filter after that | 15:41 |
crobertsrh | ideally (imho), when something gets filtered out, there would be some note/value indicating that X was filtered out in the response. | 15:41 |
tmckay | dmitryme, I agree, that might be better. I think we need some core member votes here. | 15:42 |
dmitryme | crobertsrh: hmm, nice idea | 15:42 |
tmckay | crobertsrh, yeah, like "key: <hidden>" or something | 15:42 |
crobertsrh | Yeah, that would make the raw json more honest. | 15:43 |
crobertsrh | "oh, we know the value....we just won't tell YOU" | 15:43 |
dmitryme | crobertsrh: I think we will have two kind of fields we don't want to show: | 15:44 |
tmckay | crobertsrh, do you want to post a high priority bug referencing https://review.openstack.org/#/c/82883/2 and say that I busted relaunch? That should garner some attention | 15:44 |
dmitryme | 1. provided by user - these should be masked | 15:44 |
crobertsrh | I can do that | 15:44 |
dmitryme | 2. internal fields which do not make sense for users, like cluster 'extra' field | 15:44 |
dmitryme | the fields of the second type still should be just dropped | 15:44 |
tmckay | in the case of credentials in job executions, they are #2 I think, since they were copied from data sources | 15:47 |
crobertsrh | https://bugs.launchpad.net/sahara/+bug/1300291 | 15:48 |
tmckay | the trouble is, we need a map somewhere that identifies which fields are which types | 15:48 |
aignatov | SergeyLukjanov and folks, we don't to confirm docs update patches with sahara-ci voting, right? | 15:52 |
elmiko | aignatov: does the sahara-ci do any doc generation to make sure we haven't broken it? | 15:54 |
tmckay | crobertsrh, dmitryme, the other way to take care of this particular issue is to move swift credentials out of job_configs and store them somewhere else. But, that's a big change too (including a database change). If the swift credentials were in other fields they could be excluded | 15:54 |
aignatov | elmiko: nope, it did docs building in the past | 15:54 |
tmckay | and also _mattf wants to address storage of credentials in the db at all | 15:54 |
aignatov | but now it is cancelled | 15:54 |
elmiko | aignatov: yea, then it probably doesn't matter if we have sahara-ci voting or not | 15:55 |
aignatov | elmiko: right, anyway, OpenStack Jenkins does docs generation, we should rely on it :) | 15:55 |
*** dmitryme has quit IRC | 15:56 | |
elmiko | aignatov: definitely | 15:57 |
elmiko | aignatov: if i create a review against this blueprint, do i need to use the partial-implements keyword in the commit comment? | 16:01 |
aignatov | I think yes, it will add review link to the bp whiteboard | 16:02 |
elmiko | ok, i just want to make sure i'm not going to squash another review | 16:03 |
aignatov | otherwise you'll see -1 from someone asking you to use this statement in the commit message :\ | 16:03 |
*** IlyaE has quit IRC | 16:09 | |
*** elmiko is now known as _elmiko | 16:13 | |
*** alazarev has joined #openstack-sahara | 16:16 | |
tmckay | aignatov, have you seen https://bugs.launchpad.net/sahara/+bug/1300291? I think we should decide relatively quickly what to do -- revert, or make something smarter :) | 16:22 |
aignatov | how much efforts would require smart filtering? | 16:25 |
tmckay | aignatov, haven't tried yet, but dimitryme I think pointed to the right solution. I think maybe a day to develop and test, make sure nothing else breaks? | 16:26 |
tmckay | aignatov, for now, I think it would have to be by key name -- we would have to look for things we know, like fs.swift.service.sahara.... etc | 16:27 |
tmckay | aignatov, basically invoke a custom method where _filter_fields is applied | 16:27 |
openstackgerrit | Chad Roberts proposed a change to openstack/sahara: Updating dashboard user guide doc for icehouse https://review.openstack.org/84169 | 16:28 |
openstackgerrit | Chad Roberts proposed a change to openstack/sahara: Updating dashboard user guide doc for icehouse https://review.openstack.org/84169 | 16:30 |
*** IlyaE has joined #openstack-sahara | 16:30 | |
openstackgerrit | Chad Roberts proposed a change to openstack/sahara: Updating dashboard user guide doc for icehouse https://review.openstack.org/84169 | 16:31 |
*** dmitryme has joined #openstack-sahara | 16:32 | |
aignatov | tmckay, reverting that fix leads to security considerations.... So I think we need do not revert this | 16:32 |
tmckay | aignatov, okay. I'll see if I can make something better that will not break crobertsrh. After doc day. | 16:33 |
aignatov | tmckay: great | 16:33 |
tmckay | aignatov, our concern the first time was limiting impact :) I guess we missed, lol | 16:35 |
*** _elmiko is now known as elmiko | 16:35 | |
aignatov | heh | 16:45 |
*** alazarev has quit IRC | 16:45 | |
*** dmitryme has quit IRC | 16:46 | |
elmiko | there are still a few open tasks for the doc effort, https://blueprints.launchpad.net/sahara/+spec/update-docs-icehouse | 16:58 |
elmiko | just a friendly reminder :) | 16:58 |
openstackgerrit | A change was merged to openstack/sahara: Add EDP integration tests for vanilla 2 plugin https://review.openstack.org/82733 | 16:58 |
*** dmitryme has joined #openstack-sahara | 16:59 | |
*** Ch00k has joined #openstack-sahara | 17:06 | |
tmckay | aignatov, this might be a tiny bug. Looking through the REST api, if I ask for the vanilla plug version 1.2.1, when the reply is sent back it says "versions: [2.3.0, 1.2.1]" Is that on purpose? I notice that configs, node_processes, and image_tags are selected by version but the "version" field is not modified in the response. | 17:11 |
tmckay | aignatov, also, the response can be really, really big :) I think the json in the REST doc is shortened. Maybe I should add a note that says "by the way, this can be really really big" | 17:12 |
elmiko | is there documentation for the version of reStructured Text we are using? | 17:25 |
*** dmitryme has quit IRC | 17:27 | |
elmiko | i'm curious, would it be worth it to add a section to the development environment doc about setting up a Sahara install outside of DevStack? | 17:45 |
*** IlyaE has quit IRC | 18:07 | |
crobertsrh | elmiko: I think the extra section is a fine idea | 18:10 |
elmiko | i'll see if i can put something together that makes sense | 18:12 |
*** IlyaE has joined #openstack-sahara | 18:12 | |
elmiko | the only thing that i think is difficult about setting up sahara outside devstack is that getting the dashboard integration can be tricky, but i guess if you are just testing sahara then you don't really need dashboard. | 18:15 |
*** IlyaE has quit IRC | 18:17 | |
*** tmckay has quit IRC | 18:27 | |
*** IlyaE has joined #openstack-sahara | 18:27 | |
*** tmckay has joined #openstack-sahara | 18:30 | |
elmiko | what is the syntax for partial-implements, is it "Partial-Implements", "Partial-implements", "Partial-implement", or something else? | 18:31 |
elmiko | ah,nvm. got it out of crobertsrh commit :) | 18:32 |
crobertsrh | It always seems awkward to me | 18:33 |
*** tosky has quit IRC | 18:34 | |
openstackgerrit | Michael McCune proposed a change to openstack/sahara: Updating the setup development environment docs for icehouse https://review.openstack.org/84206 | 18:36 |
openstackgerrit | Michael McCune proposed a change to openstack/sahara: Updating the setup development environment docs for icehouse https://review.openstack.org/84206 | 18:48 |
crobertsrh | on the docs blueprint, what is the "Rename Savanna to Sahara" item? | 18:57 |
elmiko | still not sure about that, it's a SergeyLukjanov question. the only references i see to savanna are in links. | 18:57 |
elmiko | and the python-django-savanna package | 18:57 |
elmiko | iirc, he was out today though | 18:59 |
SergeyLukjanov | crobertsrh, it's just a reminder that we should check it | 18:59 |
elmiko | maybe not :) | 18:59 |
SergeyLukjanov | elmiko, ^^ | 18:59 |
crobertsrh | He is never really out :) | 18:59 |
elmiko | perma-lurk | 18:59 |
* SergeyLukjanov feeling bad today and many meetings, so, a big lag | 19:00 | |
crobertsrh | I think his collar gets a small shock each time an IRC message goes unanswered. | 19:00 |
SergeyLukjanov | heh ;) | 19:00 |
SergeyLukjanov | just unpleasant bip from client | 19:01 |
SergeyLukjanov | beep* | 19:01 |
*** Ch00k has quit IRC | 19:07 | |
crobertsrh | tmckay: Looks like better exceptions in horizon is also on the mind of others... https://review.openstack.org/#/c/76479/ | 19:16 |
tmckay | crobertsrh, hurray for better errors | 19:18 |
tmckay | Doctor: "You're sick. Really, really, sick. Have a nice day" | 19:18 |
tmckay | "Maybe come back tomorrow and you'll be better" | 19:19 |
tmckay | brb | 19:19 |
elmiko | lol | 19:23 |
*** sballe has joined #openstack-sahara | 19:34 | |
*** Jpeerindex has joined #openstack-sahara | 19:40 | |
*** Jpeerindex has quit IRC | 19:40 | |
openstackgerrit | Michael McCune proposed a change to openstack/sahara: Updating the setup development environment docs for icehouse https://review.openstack.org/84206 | 19:51 |
openstackgerrit | Sergey Reshetnyak proposed a change to openstack/sahara: Fix check avtive nodemanagers for vanilla 2 plugin https://review.openstack.org/84228 | 19:51 |
openstackgerrit | Michael McCune proposed a change to openstack/sahara: Updating the setup development environment docs for icehouse https://review.openstack.org/84206 | 19:53 |
openstackgerrit | Michael McCune proposed a change to openstack/sahara: Updating the setup development environment docs for icehouse https://review.openstack.org/84206 | 19:54 |
elmiko | damn whitespace... | 19:54 |
*** akuznetsov has quit IRC | 20:13 | |
openstackgerrit | Michael McCune proposed a change to openstack/sahara: Updating the setup development environment docs for icehouse https://review.openstack.org/84206 | 20:13 |
elmiko | we still have a few open items at https://blueprints.launchpad.net/sahara/+spec/update-docs-icehouse , looking for any takers :) | 20:15 |
crobertsrh | I'd be happy to help someone with them (review, etc), but I'm afraid that I'm probably not much of a guide for the remaining topics. | 20:18 |
tmckay | crobertsrh, just playing with job-executions to confirm the docs. The swift credentials are visible from a running job anyway, even without job_configs | 20:22 |
tmckay | dmitryme, aignatov, ^^, last comment. It's a bigger fish to fry than we thought. | 20:22 |
tmckay | sign | 20:22 |
tmckay | sigh, that is | 20:23 |
tmckay | Criminals | 20:23 |
crobertsrh | where are you seeing them? | 20:23 |
tmckay | I pasted an example. A running job shows Oozie job record content. the config section is displayed | 20:23 |
tmckay | the swift credentials are passed via config to the running job | 20:24 |
*** sballe has quit IRC | 20:24 | |
crobertsrh | I never saw the paste (still don't see it). That does sounds like a larger fish fry is in order though. | 20:24 |
tmckay | hmm, paste should be there | 20:25 |
crobertsrh | oh...duh... | 20:25 |
tmckay | https://bugs.launchpad.net/sahara/+bug/1300291/comments/2 | 20:25 |
crobertsrh | pasted in the bug :) | 20:25 |
tmckay | sorry, ambiguous | 20:25 |
crobertsrh | I was looking back on IRC...I see it now | 20:25 |
tmckay | so now we start getting into descending into various levels and obscuring stuff. Recursive scrub. But, what about the Oozie console itself? Anyone who can get to that can see the same thing. | 20:26 |
tmckay | Unless there is a way to password protect the Console | 20:26 |
crobertsrh | Yes. | 20:26 |
crobertsrh | Yes, I agree....not "yes, you can protect oozie console"...I have no idea there | 20:27 |
tmckay | When we looked at this the first time, I must have only hit a pending job without the extra content, so I missed it. Pretty much a fail all around. | 20:27 |
crobertsrh | You can probably disable it | 20:27 |
*** dmitryme has joined #openstack-sahara | 20:28 | |
tmckay | I suppose we can scrub the "info" field | 20:29 |
tmckay | status is probably necessary, a few other things. conf probably is not | 20:30 |
tmckay | have to look and see what sahara and python-saharaclient look at (and maybe you can look at what the UI touches crobertsrh) | 20:30 |
openstackgerrit | Andreas Jaeger proposed a change to openstack/sahara: Check that all po/pot files are valid https://review.openstack.org/84236 | 20:32 |
tmckay | elmiko, we okay with doc day bleeding over to Tuesday? | 20:57 |
openstackgerrit | Trevor McKay proposed a change to openstack/sahara: Update REST api docs https://review.openstack.org/84249 | 20:57 |
elmiko | tmckay: i think we'll have to be, there are some docs that need attention from people with more experience | 20:57 |
tmckay | :) | 20:57 |
tmckay | okay | 20:57 |
elmiko | we've got several underway, and a few that are done pending review | 20:58 |
tmckay | elmiko, I think the REST stuff is generally done. Might need another tweak depending on what we do for filtering | 20:58 |
elmiko | ok | 20:59 |
tmckay | doh, I have typo in my changes | 21:01 |
crobertsrh | doh, I missed the type-o and +1'ed it anyway | 21:02 |
openstackgerrit | Trevor McKay proposed a change to openstack/sahara: Update REST api docs https://review.openstack.org/84249 | 21:02 |
openstackgerrit | Trevor McKay proposed a change to openstack/sahara: Update REST api docs https://review.openstack.org/84249 | 21:03 |
tmckay | heh | 21:04 |
*** crobertsrh is now known as _crobertsrh | 21:05 | |
openstackgerrit | Trevor McKay proposed a change to openstack/sahara: Update REST api docs https://review.openstack.org/84249 | 21:06 |
tmckay | doh, and messed up the commit message | 21:06 |
tmckay | I think I got it now | 21:06 |
tmckay | elmiko, I signed up for migrations. I've added a couple, I think I can take a stab at it | 21:10 |
tmckay | but I'll need reviewers | 21:10 |
elmiko | cool, thanks | 21:10 |
tmckay | I'll poke at it tomorrow | 21:10 |
*** tmckay has quit IRC | 21:14 | |
*** ErikB1 has quit IRC | 21:24 | |
*** ErikB1 has joined #openstack-sahara | 21:35 | |
*** ErikB1 has quit IRC | 21:38 | |
*** witlessb has quit IRC | 21:38 | |
*** elmiko has quit IRC | 22:53 | |
*** dmitryme has quit IRC | 23:13 | |
*** ErikB1 has joined #openstack-sahara | 23:44 |
Generated by irclog2html.py 2.14.0 by Marius Gedminas - find it at mg.pov.lt!