| *** Bhujay has joined #openstack-chef | 04:45 | |
| *** Bhujay has quit IRC | 06:07 | |
| *** Bhujay has joined #openstack-chef | 06:18 | |
| jklare | scas i can understand why you are doing that, but i think we should go back to the usual 2 review and then +1 workflow habit | 07:35 |
|---|---|---|
| jklare | scas if we move to everybody self approving his patches, we end up in a completely broken project | 07:36 |
| jklare | scas for me its much more important to have the code reviewed (although it might be a lot slower) than releasing fast | 07:36 |
| jklare | scas regarding the fog-openstack issues in the bare-metal cookbook in master i still do not see the real relation | 07:38 |
| jklare | scas the fog-openstack gem should be installed in the version specified in the cookbook-openstackclient metadata, if this is not done during any of our tests, the test is broken imho | 07:39 |
| jklare | scas if our tests indicate an issue that does not exist during a "normal" deployment, we should fix the tests | 07:40 |
| scas | i'm still awake for a little while. what happens when chef_gem is called in chefdk, it looks for the local gem and only for the local gem, without an action to otherwise update it | 07:41 |
| scas | with rocky being released, my rate of change will slow down | 07:42 |
| jklare | whats the hurry with releasing rocky asap? | 07:42 |
| scas | i'm not rushing to release rocky, but getting the sweeping changes out of the way | 07:43 |
| jklare | and you want to stick with merging by yourself without more core-reviewer reviews? | 07:44 |
| scas | i always want someone to review things. the signals came to me as though i needed to take a drastic approach to handling changes, that i could no longer take comfort in relying on you or calbers to be there. it's a distasteful practice, but one i initiated as a means to keep things going | 07:49 |
| jklare | scas calbers and me and frickler are still working on the project | 07:52 |
| jklare | scas maybe not as active as we were before, but we still use all of the cookbooks in our testing and production environments | 07:53 |
| jklare | scas we are currently integrating them in an gitlab based ci that builds our whole setup with the cookbooks and our wrapper every night | 07:53 |
| jklare | and we still try to patch things if we think patches are needed | 07:54 |
| jklare | if you think more reviews are needed or even urgent, please just ping us | 07:54 |
| jklare | i would really like to go back to the usual review and merging style we had before, since i see no reason to do otherwise | 07:55 |
| scas | kubernetes is the new 'dingo ate my baby', so forgive the misunderstanding. like i said, text is so difficult to convey intent | 07:55 |
| jklare | scas yes, we are working on kubernetes, but that does not mean we are not working, using and focussing on openstack anymore | 07:55 |
| jklare | i will drive to the office now, maybe we can continue the chat later when you got some sleep and i am closing it to the end of my day :) | 07:56 |
| scas | in my experience, when someone says they're working on a new hot thing, that usually means the old gets swiftly tossed to the side. as a USian, it's easier to lose sight of the global scale | 07:58 |
| scas | in UTC-7, that doesn't give much overlap with other regions of the world, as it's the worst time for pretty much everyone | 08:00 |
| jklare | scas we can't really toss openstack or the cookbooks to the side, since we are running a pretty big chunk of our business on these things | 08:19 |
| jklare | scas its just that we are still moving with the same pace as before, so we have currently pike deployed and are working on queens | 08:20 |
| jklare | scas so if the cookbooks try to run for rocky as fast as possible, thats a bit too fast for us to contribute much | 08:20 |
| jklare | scas which still does not mean that we can't review | 08:20 |
| *** mattgo has joined #openstack-chef | 10:55 | |
| *** mattgo has quit IRC | 11:39 | |
| *** mattgo has joined #openstack-chef | 11:55 | |
| *** Bhujay has quit IRC | 14:34 | |
| scas | jklare: definitely appreciate you saying that. most of my friends have jumped ship to aws/kubernetes/something-not-openstack, and when they did, it was all-or-nothing | 14:56 |
| jklare | scas so you got a full 6.5h of sleep :) | 14:57 |
| jklare | was wondering when you would be up again ;) | 14:57 |
| scas | i have to force myself to sleep some nights | 14:58 |
| scas | related, i've been reading https://rbtcollins.wordpress.com/2018/09/06/is-openstacks-mission-broken/ | 15:02 |
| jklare | scas nice article | 15:24 |
| jklare | although i am not sure if theses things are new to anyone, i think the issue here is that the questions and issues are obvious, but nobody knows "realistic" solutions to them | 15:26 |
| scas | i don't think anyone has gotten to the solution point, merely to the point of "blagh this sucks" in a more eloquent way | 15:27 |
| jklare | :) sounds about right | 15:28 |
| jklare | but i think from the testing point of view, kubernetes has the exact same problem | 15:28 |
| jklare | i submitted a patch, and the ci kept failing for about 2 month with completely unrelated issues before we could even start working on the real ones | 15:29 |
| scas | testing is a major problem, which is why i was trying to figure out kitchen before Roger proposed a simpler path to the same goal | 15:29 |
| scas | jklare: speaking of testing, chefdk 3.3 is in the current channel. i'm going to be bumping my builders to see what shakes out | 16:14 |
| *** ChanServ sets mode: -rf | 17:18 | |
| *** mattgo has quit IRC | 17:40 | |
Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!