Thursday, 2015-04-09

*** petertr7 has quit IRC00:11
*** chlong has joined #openstack-chef00:25
*** wojdev has joined #openstack-chef00:25
*** wojdev has quit IRC00:40
*** jerome80 has joined #openstack-chef00:46
*** wojdev has joined #openstack-chef00:52
*** kei_yama has quit IRC00:53
*** kei_yama_ has joined #openstack-chef00:53
*** thumpba has quit IRC01:16
*** thumpba has joined #openstack-chef01:17
*** _joel has left #openstack-chef01:41
*** otter768 has joined #openstack-chef01:49
*** otter768 has quit IRC01:53
*** ncerny has joined #openstack-chef02:03
*** harlowja is now known as harlowja_away02:03
*** stevemar has joined #openstack-chef02:12
*** kei_yama_ has quit IRC02:29
*** kei_yama has joined #openstack-chef02:32
*** ncerny has quit IRC03:02
sc`markvan: with patches/hacks, i was able to hit the nova bug03:24
openstackgerritEthan Lynn proposed stackforge/cookbook-openstack-orchestration: Move amqp options into correct section  https://review.openstack.org/17037703:33
*** ozialien has joined #openstack-chef03:35
*** jerome80 has quit IRC03:45
*** jerome80 has joined #openstack-chef03:46
*** otter768 has joined #openstack-chef03:50
*** otter768 has quit IRC03:54
*** tmichael has quit IRC04:07
*** stevemar has quit IRC04:57
*** tmichael has joined #openstack-chef04:58
*** tmichael has quit IRC04:59
*** ozialien has quit IRC05:06
*** chlong has quit IRC05:09
openstackgerritMerged stackforge/cookbook-openstack-orchestration: Move amqp options into correct section  https://review.openstack.org/17037705:09
*** dmowrer has quit IRC05:23
*** wojdev has quit IRC05:40
*** otter768 has joined #openstack-chef05:50
*** thumpba has quit IRC05:52
*** otter768 has quit IRC05:55
*** jmickle has joined #openstack-chef06:11
*** seizadi has joined #openstack-chef06:29
*** jmickle has quit IRC06:45
*** wojdev has joined #openstack-chef06:55
*** opscode-logger has quit IRC07:00
*** opscode-logger has joined #openstack-chef07:00
*** seizadi has quit IRC07:07
*** otter768 has joined #openstack-chef07:51
*** otter768 has quit IRC07:56
*** pradipta has joined #openstack-chef08:28
openstackgerritLan Qi Song proposed stackforge/cookbook-openstack-compute: Enable config_drive_format parameter for nova  https://review.openstack.org/17197809:13
*** wojdev has quit IRC09:41
*** wojdev has joined #openstack-chef09:43
*** otter768 has joined #openstack-chef09:52
*** otter768 has quit IRC09:57
*** ogny1 has joined #openstack-chef10:18
*** wojdev has quit IRC10:19
*** wojdev has joined #openstack-chef10:41
*** wojdev_ has joined #openstack-chef10:57
*** wojdev has quit IRC10:59
*** wojdev_ is now known as wojdev10:59
*** rtheis has joined #openstack-chef11:10
*** DaveIshmael has quit IRC11:31
*** stevemar has joined #openstack-chef11:43
*** otter768 has joined #openstack-chef11:53
*** pradipta has quit IRC11:57
*** otter768 has quit IRC11:58
*** stevemar has quit IRC12:02
*** kei_yama has quit IRC12:03
*** wojdev has quit IRC12:18
*** wojdev has joined #openstack-chef12:19
*** wojdev has quit IRC12:20
*** jerome80 has quit IRC12:39
*** ozialien has joined #openstack-chef12:43
*** wojdev has joined #openstack-chef12:48
*** wojdev has quit IRC12:48
*** neelashah has joined #openstack-chef13:23
markvancmluciano: j^2  This one should be ready for rabbitmq now https://github.com/jjasghar/rabbitmq/pull/247   would like to see this get in, then I can update ops-messaging to use this new level.13:25
*** stevemar has joined #openstack-chef13:46
*** openstackgerrit has quit IRC13:53
*** openstackgerrit has joined #openstack-chef13:53
*** otter768 has joined #openstack-chef13:54
*** mattray has joined #openstack-chef13:56
*** ChanServ sets mode: +o mattray13:56
*** otter768 has quit IRC13:59
*** wenchma has joined #openstack-chef14:12
markvansc`: thx for verifying what I'm seeing.  I have asked nova core for some help with understanding that bug.  I don't know of a way to workaround that yet.  Having said that j^2 cmluciano I think that image patch can go as it's being tested with this setup.14:16
markvanhttps://review.openstack.org/#/c/171330/14:16
markvanThe other patch I have tested on centos and our internal repo is: https://review.openstack.org/#/c/167321/   This is very straight forward, just a new package requirement for kilo.14:16
sc`speaking of centos and kilo: http://trunk.rdoproject.org/centos70/latest-RDO-trunk-CI/14:18
*** ncerny has joined #openstack-chef14:18
sc`haven't tested, but i think overriding the rdo uri might get kilo packages on c714:20
*** grealish has quit IRC14:20
j^2I'm on the road getting my daughter to school. I should be ready for the meeting a couple late. Unless someone else wants to run it.14:21
markvansc`: humm, I'll have to try that.  did you see anything related to when https://repos.fedorapeople.org/repos/openstack/openstack-kilo/epel-7/ would be updated?14:21
sc`no. they're still focusing on getting delorean in good shape14:21
markvanj^2: that's fine14:22
markvank14:22
sc`i might have kicked the hornets' nest a bit about having distro packages kind of sequestered off14:22
sc`hard to keep up with this stuff with everyone off on their own islands14:23
*** grealish has joined #openstack-chef14:23
*** seizadi has joined #openstack-chef14:26
markvanyeah, but still a good discussion to have for us as we rely on these distro repos14:27
*** seizadi has quit IRC14:27
markvanalmost tempting to forking our own copy of the repo just to allow patches to continue to flow at some rate, but "catch-up" could be very ugly14:28
sc`i really want everyone leveraging openstack infra for packaging, but that's a larger scale issue14:28
sc`http://trunk.rdoproject.org/f21/report.html14:32
sc`actually, wrong link14:33
sc`http://trunk.rdoproject.org/centos70/report.html14:33
markvansc`: scary there are still that many packaging issues for kilo14:36
sc`indeed14:37
sc`they're leery about rolling up into openstack.org, but have said they're not modifying the source, which is a Good Thing14:39
*** mattray has quit IRC14:41
*** seizadi has joined #openstack-chef14:48
*** emagana has joined #openstack-chef14:55
openstackgerritMerged stackforge/cookbook-openstack-telemetry: Enable store_events parameter in notification service  https://review.openstack.org/17125214:56
openstackgerritMa Wen Cheng proposed stackforge/cookbook-openstack-block-storage: Make sure lvm2 package is installed  https://review.openstack.org/16732115:00
*** mattray has joined #openstack-chef15:01
*** ChanServ sets mode: +o mattray15:01
*** nathenharvey has joined #openstack-chef15:03
sc`shall we do this?15:08
sc`ah, looks like i don't know how to trigger the bot yet15:13
cmlucianothink we were waiting on j^2 to get bacj15:14
sc`sounds good. i've got a couple of topics but i'll be somewhat distracted for part of the meeting then15:15
j^2Yeah sorry I'm still in travel mode. Daughter threw a massive tantrum15:16
sc`j^2: no worries15:16
j^2#startmeeting openstac-chef15:16
openstackMeeting started Thu Apr  9 15:16:28 2015 UTC and is due to finish in 60 minutes.  The chair is j^2. Information about MeetBot at http://wiki.debian.org/MeetBot.15:16
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:16
*** openstack changes topic to " (Meeting topic: openstac-chef)"15:16
openstackThe meeting name has been set to 'openstac_chef'15:16
j^2Shit15:16
j^2#endmeeting15:16
*** openstack changes topic to "OpenStack & Chef | chef.io/openstack | wiki.openstack.org/wiki/Chef/GettingStarted | groups.google.com/group/opscode-chef-openstack | github.com/stackforge/openstack-chef-repo | docs.chef.io/openstack.html | botbot.me/irc.freenode.net/openstack-chef/"15:16
openstackMeeting ended Thu Apr  9 15:16:45 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:16
openstackMinutes:        http://eavesdrop.openstack.org/meetings/openstac_chef/2015/openstac_chef.2015-04-09-15.16.html15:16
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/openstac_chef/2015/openstac_chef.2015-04-09-15.16.txt15:16
openstackLog:            http://eavesdrop.openstack.org/meetings/openstac_chef/2015/openstac_chef.2015-04-09-15.16.log.html15:16
j^2#startmeeting openstack-chef15:17
openstackMeeting started Thu Apr  9 15:17:02 2015 UTC and is due to finish in 60 minutes.  The chair is j^2. Information about MeetBot at http://wiki.debian.org/MeetBot.15:17
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:17
*** openstack changes topic to " (Meeting topic: openstack-chef)"15:17
openstackThe meeting name has been set to 'openstack_chef'15:17
j^2There go. Hi all!15:17
sc`o/15:17
wenchmahello15:17
j^2sc`: take it away15:17
sc`#topic rdo kilo packages15:18
sc`started following #rdo's progress on kilo. they have what looks like mostly working packages in their delorean repo15:19
sc`http://trunk.rdoproject.org/centos70/report.html is the link to their CI builds for anyone that wants to follow along15:19
sc`#topic nova-api-metadata fix15:20
sc`still wip on getting openstack-compute to toggle the attribute. been backlogged quite a bit but am catching up with queued patches15:21
sc`that's about all i have15:21
wenchmaseems there is a patch fo fix nova-api-metadata15:24
wenchmahttps://review.openstack.org/#/c/142249/15:24
wenchmasc`: right ?15:24
wenchmaor partial15:25
sc`yeah... i tried that approach myself a while back15:25
sc`right now we're overriding enabled_apis in environments, which is ok as a stopgap15:26
*** tmichael has joined #openstack-chef15:26
sc`but the cookbook should know whether or not to lay down the proper config var depending on if you have the metadata recipe in the run_list15:27
sc`the current state in openstack-chef-repo is to let the metadata recipe handle things itself, but what if someone doesn't want to use the recipe and wants nova-api to manage the metadata service itself?15:30
markvansc`: I think we need to make that decision.  I vote for using the recipe and NOT allowing nova-api to mess with it.  Cleaner for our env's that way.15:31
sc`it does make sense that way15:32
markvanI don't see a need to clutter our support to allow both ways.  recipe works fine and does the job correctly, so use it.  I think we need a patch to put out a warning if enabled_apis contains metadata.15:33
markvanand then remove it from the list to avoid to overlap issue.15:33
*** jmickle has joined #openstack-chef15:35
sc`yep. makes sense15:35
markvank, I can followup with a patch for that, and see what reviewers think of that approach.15:38
sc`there's no real valid reason to keep both around, other than to keep what's out of the box intact15:38
markvan#topic  ubuntu kilo packages15:39
markvanI posted what I think is the latest workaround here: http://paste.openstack.org/show/200736/15:39
markvanThe one patch is needed as a result of the service role work: https://review.openstack.org/#/c/171330/15:40
markvanI have not see movement on the nova libvirt bug yet, but I have asked around a bit15:40
wenchmafor 171330, gave some comments15:41
wenchmaif we make amdin create public glance image, we also need to make sure publicize_image is admin in glance policy file15:43
markvanwenchma: yup, need to update policy to allow for non admin public images now.  It was a security measure15:43
markvanand for admin, that is the default in the glance_policy file15:43
markvansee https://github.com/openstack/glance/blob/master/etc/policy.json#L1015:44
wenchmayes, The ability to upload a public image is now admin-only by default15:44
wenchmahmmm....15:46
wenchmashould be this rightr15:46
markvanand from history, the cookbooks have to date avoided messing with the policy files, so until someone asks, I don't see a need for supporting non-admin public with the lwrp15:46
wenchmamaybe I deployed the node , not use the latest pkgs15:47
markvanThe other way to enable that would be to create another use within the admin role, then they could also create public images.  This is doable today with the identity lwrp.15:47
wenchmalooks gogd15:49
wenchmagood15:49
markvanAnd in general I think this was a good move by the base, separate what a "service" and "admin" can do, to make security controllable15:49
*** jmickle has quit IRC15:51
markvanSo I guess that leads to my main topic.... how to get patches flowing again, and how to de-couple a bit from being stuck in the future?15:51
markvan#topic repo dependencies15:51
markvanIf you look at our patch list, there are a bunch of low haning fruit ones that are straight forward and imo ready to go.    So, what is the best way to move forward?15:52
markvanI have tried the ubuntu/rdo trunks a bit, but usually very messy.15:52
markvanThen I tried using our testing repo with our internal repo (aio_neutron, we don't support nova network), and it works.  But since it's an internal repo, is that enough to justify merging a patch?15:54
markvanthoughts?15:54
*** seizadi has quit IRC15:55
sc`i think as long as the code is from the same line, it should be about the same15:55
*** otter768 has joined #openstack-chef15:55
sc`but as far as merging, i'd personally be comfortable with being able to pull down internet artifacts and being able to prove that the proposed patch works15:55
markvanyup, our internal repo is usually almost bleeding edge, rebased daily, and is fairly clean of forks.15:55
markvanyup, I can't disagee with having public artifacts to verify15:56
sc`if it works against ubuntu/rdo trunk, that's one thing15:56
j^2hey all, i’m actaully at my laptop, i can actaully type15:57
markvanSo, does that mean we could create our own snapshot somwhow, and not live so close to the edge?15:57
j^2i need to catch up with :)15:57
sc`perhaps snapshotting ubuntu/rdo trunk may be enough to suffice15:58
markvanif we find a cut that works for our basic verify needs, would be nice to hang on to that for a short period to allow basic patches to continue to flow.15:59
markvanThere will be patches that require a later level of base openstack, but I think those a fewer in number15:59
*** otter768 has quit IRC16:00
markvanIs there a way we could simply capture/clone a repo into a zip and push that up to a github project, maybe next to the testing suite.  and then tie those to gether with doc for testing with it.16:01
markvanI'n not an expert on repos, but it seems like it can be done locally, just download zip and change url to it?16:02
sc`longer-term, i'd like to get rdo, ubuntu, etc. on an openstack site, but that's a bigger yak to shave16:03
sc`rdo would be amenable to mirroring packages that way16:03
markvansc`: that's encouraging to hear, and a cleaner approach for all16:03
cmlucianocatching up16:07
cmlucianowe’re talking about how to get up-to-date packages it seems16:07
markvanLooking at yum, seems like we could just have a zip of the repo, and then inject a recipe to push that to the node, unzip and update the atttr url to point to file:///...16:07
cmlucianoI suppose that’s the major downfall of having to rely on rdo/ubuntu16:07
markvancmluciano: more then up to date, a cut of "working" packages16:07
cmlucianoAh16:08
sc`i was looking at the backlog and noticed several rhel 7.1 patches outstanding. is this because of fauxhai?16:12
cmlucianoI haven’t been CRing things since I can’t get master to work16:14
*** jeff_laplante has joined #openstack-chef16:14
cmlucianoI know we have a couple of workarounds but I haven’t been able to get any to work without running into other issues16:14
markvansc`: yup, need an update to that fauxhai gem to pull in the 7.1 support,  then a patch to the gem files to pull that in16:14
markvancmluciano: yup, see http://paste.openstack.org/show/200736/ for where I think we stand with ubuntu + master + aio_nova16:15
sc`with markvan's notes, i have a converged node but i hit the nova bug indicated in those notes when booting an image16:16
sc`looks like there's some recent activity on the bug16:17
markvanso, with that in mind, I think the https://review.openstack.org/#/c/171330/1 image patch should go in, as the images are being created properly.  And then we eliminate one patch from the workaround list.16:18
sc`i concur16:18
cmlucianoworkflowed that patch16:19
cmlucianofrom that paste it appears that the other issues involve updated packages and an open bug for nova cpu affinity16:20
markvanbummer, that nova libvirt cpu pinning bug looks like a ubuntu packaging issue, probably not up to date16:20
cmlucianosad_panda16:21
markvancmluciano: yup, the pysaml2 package fix has gone into the ubuntu trunk.16:21
markvanso, it's close, but I don't see a workaround for the nova bug.16:22
markvanAnd that's why I'm suggesting we think about cutting a copy of a working ubuntu/rdo repo to help make progress with some patches16:24
cmlucianowhere would these be hosted?16:24
*** ozialien has quit IRC16:26
markvanI was thinking just locally for now, so take a cut, create a zip, push that to github project.  Then we needed, use new recipe in testing repo to pull that down, unzip in node and point to it with file://16:26
markvanshoiuld be able to grab the zip directly from the github via a new testing suite recipe step16:27
markvannot sure If I'm making sense, maybe I'll have to fully prototype it, seems fairly easy way to do it, and allows anyone to upload to github new zips16:29
sc`i see where you're going with that16:29
markvannot sure if there's an easier way/place to host a working cut16:29
sc`ya. it has to go somewhere16:29
sc`it's just a matter of *where*16:29
markvanI figure either way, you have to download the packages, so having them right on the node is easy place to start.  and yeah for multi, would need push to each node.16:31
markvanor maybe we can find some public cloud drive space out there to use for at least a holding 1 or 2 cuts, not sure how big, but I don't think multi gig's here.16:33
sc`packagecloud maybe?16:33
markvanthat would be easier, then just a attr override to use it16:33
sc`or some to-be-created openstack infra?16:35
*** harlowja_away is now known as harlowja16:35
sc`that's all longer-term stuff, most likely16:35
markvanbummer, looks like packagecloud is very nice, but free acct only allows 25 packages, I think openstack repos are just a bit bigger16:36
sc`for right now, just snapshotting into a tar could work. it's kinda ugly imho16:36
sc`but it'd work16:37
markvanyeah, I think it would allow some progress for us16:37
*** jmickle has joined #openstack-chef16:39
*** seizadi has joined #openstack-chef16:39
*** wenchma has quit IRC16:40
markvanj^2: is there any place within Chef to drop a repo cut? so we could get public http access when using testing suite?16:40
*** PaulCzar has joined #openstack-chef16:41
openstackgerritMerged stackforge/cookbook-openstack-image: Only admin can create public glance images  https://review.openstack.org/17133016:46
*** jeff_laplante has quit IRC17:02
j^2markvan: sorry i’m missing your question? you mean chef-dk?17:05
j^2#endmeeting17:05
*** openstack changes topic to "OpenStack & Chef | chef.io/openstack | wiki.openstack.org/wiki/Chef/GettingStarted | groups.google.com/group/opscode-chef-openstack | github.com/stackforge/openstack-chef-repo | docs.chef.io/openstack.html | botbot.me/irc.freenode.net/openstack-chef/"17:05
openstackMeeting ended Thu Apr  9 17:05:10 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:05
openstackMinutes:        http://eavesdrop.openstack.org/meetings/openstack_chef/2015/openstack_chef.2015-04-09-15.17.html17:05
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/openstack_chef/2015/openstack_chef.2015-04-09-15.17.txt17:05
openstackLog:            http://eavesdrop.openstack.org/meetings/openstack_chef/2015/openstack_chef.2015-04-09-15.17.log.html17:05
*** smccully has joined #openstack-chef17:05
markvanj^2: not chef dk.  Were taking about taking a snapshot of a "working" ubuntu/rdo repo, and putting that somewhere that folks could use as alternative when running the testing suite.  If there was a small public http space that Chef has, it would make this very easy to do.17:07
j^2ohhh17:07
j^2something like an s3 bucket to pull stuff down from?17:07
markvanhumm s3?   basically just a repo mirror, simple http repo access17:08
j^2yeah chef _doesnt_ have a repo mirror that i know of17:13
j^2but we could create one in s3 i’m betting17:13
j^2https://github.com/krobertson/deb-s317:13
j^2or this: http://skife.org/apt/aws/2012/10/12/private-apt-repos-in-s3.html17:13
j^2and i bet i could put this in the chef namespace17:13
markvanhumm, that sounds like a good place.17:13
cmluciano+117:13
sc`that could work17:13
j^2can you drop me a note at jj@chef.io asking exactly what you’d like i’m kinda split brained at the momemnt and would like to get working on the openstack-client cookbook fog POC again at some point17:13
*** openstack has quit IRC17:13
*** openstack has joined #openstack-chef17:15
*** ChanServ sets mode: +o openstack17:15
*** ncerny has quit IRC17:22
*** ozialien has joined #openstack-chef17:26
cmluciano i think we can just point at the proper repo url17:26
*** neelashah has joined #openstack-chef17:27
*** neelashah1 has joined #openstack-chef17:28
markvanfound this: http://www.aptly.info/   seems like easy way to do a mirror, then we just control how often we sync17:29
*** neelashah has quit IRC17:32
*** ncerny has joined #openstack-chef17:33
markvanit has a step to do a simple snapshot of a remote repo, then can publish that snapshot to S3.  Then diff snapshot and re-sync as needed.17:35
*** emagana has quit IRC17:37
*** emagana has joined #openstack-chef17:38
*** emagana has quit IRC17:43
*** ogny1 has quit IRC17:43
markvanI think that aptly and S3 should work, I'll give that a try with current repo to see that I can reproduce the same testing env.17:48
cmlucianocan also look into https://github.com/blueboxgroup/giftwrap17:49
sc`do we have any tripleo stuff yet?17:53
*** otter768 has joined #openstack-chef17:56
*** otter768 has quit IRC18:01
cmlucianosc`:  don’t believe so18:04
cmlucianoI’m trying to remember if their was a blueprint18:04
sc`i didn't see one in a quick scan18:05
sc`unless it's called something unrelated18:06
cmlucianodoubtful, I don’t think it has come up yet18:06
j^2yeah the giftwrap thing was being pushed by carlp18:29
j^2the project never really got anywhere18:29
*** rtheis_ has joined #openstack-chef18:30
*** nathenharvey has quit IRC18:30
*** rtheis has quit IRC18:33
sc`hm18:41
*** ozialien has quit IRC18:42
*** ozialien has joined #openstack-chef18:44
*** carlp has joined #openstack-chef18:45
*** ChanServ sets mode: +o carlp18:45
j^2carlp: sc` was asking about giftwrap :)18:47
carlpHello sc, I don't know if I have a lot of info I can add, but I know the right people to poke. Fire away.18:48
sc`oh, mostly just curious to know what it can do. rdo and ubuntu kilo trunk are a little hot to the touch right now18:52
sc`we were throwing around the idea of snapshotting trunk for both and having them somewhere closer to home18:53
sc`makes it easier to get cookbook patches in without getting blocked like is the case today18:54
carlpwell, we are currently not using giftwrap against trunk. So I don't know if it will be a huge help.18:57
carlpAlso, by default giftwrap makes generic packages - just like RDO. So, if RDO is busted giftwrap will be as well18:58
sc`well, it's not to keep up with trunk, but to stay just a little bit behind the latest and brokenest19:02
*** mattray has quit IRC19:02
sc`does it make any sense? markvan correct me if i'm in left field19:03
*** mattray has joined #openstack-chef19:03
*** ChanServ sets mode: +o mattray19:03
sc`basically, i don't want another situation like we're in with rdo19:05
markvansc`: yup, that's the basic idea, of course it usually would be a snapshot of a "working" repo package set19:05
sc`i'd rather have the last set of usable packages that passed rdo's ci19:05
sc`as opposed to no openstack packages as is currently the case19:05
*** wojdev has joined #openstack-chef19:06
*** wojdev has quit IRC19:06
sc`when the kilo packages broke, there became no option for getting a working set of packages from rdo19:07
sc`even if they're a little stale19:07
sc`currently, you have to go even closer to trunk, to delorean19:07
sc`and there's no guarantee it even works19:07
carlpThis sounds like we need something that builds trunk and tests it. I've been working on plans for that for a while, but no one seemed interested. I may have to dust all that off19:24
sc`i've strongly suggested rdo to shift their efforts to openstack infra to take advantage of zuul19:25
sc`but that's a longer-term thing19:25
sc`and the same would have to be done for every other openstack packager19:26
sc`with rdo, it's easy to know what is and isn't consumable for trunk19:27
sc`if it shows up on fp.o, it's probably good19:27
openstackgerritMark Gloshen proposed stackforge/cookbook-openstack-ops-database: Add additional mysql tunables  https://review.openstack.org/16784319:29
sc`https://repos.fedorapeople.org/repos/openstack/openstack-kilo/epel-7/19:30
sc`all of these have made it out of delorean19:30
sc`but no openstack packages are there yet19:30
sc`before the build broke, you could grab a full snapshot19:30
sc`when the build broke, the packages disappeared19:30
openstackgerritMark Gloshen proposed stackforge/cookbook-openstack-ops-database: Add additional mysql tunables  https://review.openstack.org/16784319:53
*** otter768 has joined #openstack-chef19:57
*** thumpba has joined #openstack-chef19:58
*** thumpba_ has joined #openstack-chef19:59
sc`https://review.openstack.org/#/c/167321/ should probably be wf'd if it's good to go20:00
*** otter768 has quit IRC20:01
*** thumpba has quit IRC20:02
*** ozialien has quit IRC20:03
openstackgerritJJ Asghar proposed stackforge/cookbook-openstack-client: Adding nova creating and deleting for client  https://review.openstack.org/17219220:05
j^2@core ^^^ boom! this is the start of the way to write the LWRPs for the client cookbook!20:06
os-chef-bot@j^2 @markvan @mattray @wenchma @jklare @cmluciano ^^^ boom! this is the start of the way to write the LWRPs for the client cookbook!20:06
sc`woot :)20:07
j^2damn foodcritic and rubocop20:07
cmlucianolololololo20:07
cmlucianosc`: Unfortunately I can’t test it :P20:08
sc`cmluciano: it works with markvan's notes on getting aio_nova to work20:08
cmlucianoI thought we still got caught at the libvirt issue?20:09
sc`libvirt is a problem with the ubuntu package, it seems20:09
sc`but converge works20:09
cmlucianoso it converges but I can20:09
sc`you can't boot a vm20:09
cmlucianoexactly20:09
sc`well, you can, but the vm bails out because nova is busted20:10
sc`so from a pure perspective of "does it work?", the answer is yes20:10
cmlucianoi would rather be able to go through to the end to make sure20:10
sc`fair enough20:10
openstackgerritJJ Asghar proposed stackforge/cookbook-openstack-client: Adding nova creating and deleting for client  https://review.openstack.org/17219220:11
cmlucianowhile it seems like a simple change we keep getting bit by small things that are not fully tested20:11
cmlucianothen we end up with issues down the line20:11
cmlucianocase in point, ironic20:11
sc`dumb question: do changes to the cookbooks kick off tests that suck in the rest of the cookbook set?20:11
cmlucianolike the tests that jenkins runs?20:12
markvansc`: yup, gates run berks vendor each time to pull them in20:12
sc`tempest would be a good smoke test for the cookbooks20:13
sc`a bit heavyweight20:13
cmlucianoya I think j^2 has a commit up for tempest20:13
markvansc`: yup, checkout https://review.openstack.org/#/c/164876/20:13
cmlucianowe’d like to have a separate CI to run the testing stack and report back also20:14
sc`yeah20:14
sc`the changes i've seen in the backlog seem to be going in that direction20:14
sc`which is a Good Thing20:14
markvanj^2: for other cookbooks use of the client cookbook lwrp's it seems very ugly to have to pass in all the auth stuff each time, must be a way we can make that easier.  maybe a helper between Common and Client to provide all that as an option.   Would greatly simplify the existing cookbooks.20:18
markvanclean separation of auth info from task info.20:21
*** ozialien has joined #openstack-chef20:26
j^2markvan: I agree there should be an abstraction for auth but I don't think it should hold up merges. The lwrp working with fog is more important then clean code. No reason you couldn't declare it at the top of the recipe either20:27
j^2I want this out so we can start testing neutron too20:28
j^2Aio_neutron and the like20:28
markvanyup, understand, but we should explore this a bit to see how it might affect this, I don't want to go back and redesign from beginning again.20:30
j^2No reason why you should it's just a simple wrapper around fog20:31
markvanI think the big question here is if client cookbook can depend upon Common cookbook?  If no, then need a better way to pass in auth, if yes, need a way to integrate them20:31
*** jmickle has quit IRC20:31
markvanIt;s the "wrapper around fog" I worried about.  Fog interface is not friendly to our cookbook usage20:32
j^2I don't think it's something we should think about in the beginning. Again is is more driven to the lwrps for fog then anything else. MVP is more important t20:32
j^2Then you don't have to use it20:33
j^2It's not required for anything at the moment20:33
j^2Eventually It can be, but initially it's a MVP20:33
markvanyup, simple wrapper is ok for a poc, but before we try to make use of this in other cookbooks, will need to overcome this auth mess20:34
*** ozialien has quit IRC20:34
j^2And the MVP is a POC of a wrapper around fog so we can create all the LWRPs so we aren't gated by this20:35
*** jmickle has joined #openstack-chef20:35
j^2Agreed, but the auth mess is down the line much farther then we should be looking in practical expectations I believe20:35
markvansure.  When you mentioned the aio_neutron, I'm thinking that will go into the neutron cookbook, and would like to auth integration when that happens.  If it's outside network is a separate aio_neutron recipe, then I'm ok with using a simple poc.20:38
j^2No no you completely miss understood20:39
j^2We don't created networks or routers with neutron as we all know20:39
j^2This client cookbook would run after the chef-provisioning script and create a sane default network router and probably compute nodes for you20:40
markvanyup, no lwrp for doing that in the network cookbook.20:40
j^2And the heavy lifting is all die with fog20:41
j^2Done*20:41
j^2hence the lwrp20:41
markvansure, but it's really not in the client cookbook it self right, that's just where the lwrps will live.  Need other recipes in repo to use them.20:42
*** jmickle has quit IRC20:42
j^2So are you suggesting putting the lwrps in the different projects not client?20:43
j^2Being that client was supposed to be the "operators" and "consumers" entry point I though that simple lwrps was a good starting point20:44
markvanno, lwrp's belong in client.   The code that makes use of them for setting up a multi/aio_neutron need to be closer to that, so I was suggesting jsut dropping in repo for now20:44
sc`just looking at the poc, i'm good with it in its current form just to have something to poke at20:44
markvanDo, you also want to out "working" example recipes within the client cookbook to show it off?   That sounds ok to.20:45
j^2Yeah we can easily improve it, but it's very much a start ya know?20:45
markvansuch that the aio_network would just use that "working" example recipe from client to actually test with it20:46
j^2I mean the delete action requires the id that's just lame. It should be the friendly name ya know20:46
j^2markvan: yep exactly20:46
markvanhumm, pretty sure nova cli can handle either id or name (if unique)20:46
j^2Fog can too20:47
markvanbut not sure what Fog can handle20:47
sc`no need to boil the ocean on this one20:47
j^2It just requires the id for the actual method20:47
markvanah, interesting20:47
j^2sc`: yeah it's not anything we should worry about now20:48
j^2More importantly is all the methods matched to lwrps after this being merged20:48
*** smccully has quit IRC20:49
*** neelashah1 has quit IRC20:52
*** mattray has quit IRC20:57
*** stevemar has quit IRC20:58
*** jmickle has joined #openstack-chef21:03
*** emagana has joined #openstack-chef21:06
*** jmickle has quit IRC21:07
*** jmickle has joined #openstack-chef21:30
*** mancdaz has quit IRC21:35
*** mancdaz has joined #openstack-chef21:38
*** otter768 has joined #openstack-chef21:58
*** otter768 has quit IRC22:03
*** emagana has quit IRC22:03
openstackgerritMark Gloshen proposed stackforge/cookbook-openstack-ops-database: Add additional mysql tunables  https://review.openstack.org/16784322:13
*** emagana has joined #openstack-chef22:33
*** emagana_ has joined #openstack-chef22:35
*** emagana has quit IRC22:38
*** emagana_ has quit IRC22:39
*** emagana has joined #openstack-chef22:45
*** ncerny has quit IRC22:55
*** seizadi has quit IRC22:57
*** emagana has quit IRC22:58
*** DaveIshmael has joined #openstack-chef23:04
*** jmickle has quit IRC23:05
*** thumpba has joined #openstack-chef23:06
*** thumpba_ has quit IRC23:08
*** seizadi has joined #openstack-chef23:29
*** thumpba_ has joined #openstack-chef23:34
*** kei_yama has joined #openstack-chef23:36
*** thumpba has quit IRC23:37
sc`j^2: know any good resources on chef-provisioning? for some reason, chef-zero seems to try to respawn in this run23:43
j^2sc`: hmmm that's odd23:57
sc`very odd, but it's probably the cookbooks i'm using23:58
j^2The main chef-provisioning repo has a good readme on how write a driver that breaks the majority of it down23:58
sc`i'll poke around in there23:59
*** otter768 has joined #openstack-chef23:59

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