17:01:59 #startmeeting Fedora Atomic Working Group 17:01:59 Meeting started Wed Nov 9 17:01:59 2016 UTC. The chair is kushal. Information about MeetBot at http://wiki.debian.org/MeetBot. 17:01:59 Useful Commands: #action #agreed #halp #info #idea #link #topic. 17:01:59 The meeting name has been set to 'fedora_atomic_working_group' 17:02:02 .fas jasonbrooks 17:02:03 jbrooks: jasonbrooks 'Jason Brooks' 17:02:11 #topic Roll call 17:02:17 .fas sayanchowdhury 17:02:18 sayan: sayanchowdhury 'Sayan Chowdhury' 17:02:30 .hellomynameis kushal 17:02:34 kushal: kushal 'Kushal Das' 17:02:40 .fas walters 17:02:41 walters: jvwsaw 'James Walters' - jwalters 'Jake Walters' - jwalters1 '' - nawalters 'Nathan Walters' - walters228 'clinton walters' - whodaimen 'Brian Michael Walters' - goldwingers 'David Walters' - jjjwalters '' - walters 'Colin (1 more message) 17:02:48 .hellomynameis walters 17:02:49 walters: walters 'Colin Walters' 17:02:53 .hello sayanchowdhury 17:02:54 sayan: sayanchowdhury 'Sayan Chowdhury' 17:04:40 .hello dustymabe 17:04:41 dustymabe: dustymabe 'Dusty Mabe' 17:04:50 .hello maxamillion 17:04:51 maxamillion: maxamillion 'Adam Miller' 17:05:00 .hello trishnag 17:05:01 trishnag: trishnag 'Trishna Guha' 17:05:39 do we have an agenda for today? 17:05:55 #chair walters trishnag maxamillion dustymabe sayan jbrooks 17:05:55 Current chairs: dustymabe jbrooks kushal maxamillion sayan trishnag walters 17:06:18 Good news is all F25 images are passing. 17:06:24 sweet 17:06:32 walters, if people are are okay we can move to open floor. 17:06:46 walters: we usually go through "meeting" ticket items, but we should start doing a formal agenda like the server wg does 17:07:49 One major point, website change for F25 17:08:30 #topic https://pagure.io/atomic-wg/issue/158 website change for atomic 17:09:58 kushal: is this for f25? 17:10:00 or f26? 17:10:09 There are changes for F25 17:10:12 * kushal is trying to find link 17:10:56 dustymabe, https://stg.getfedora.org/en/cloud/ 17:10:59 https://stg.getfedora.org/en/cloud/ 17:11:06 Everyone please have a look 17:11:48 kushal: that stg site looks good 17:11:57 some weirdness around "atomic CLI" part 17:12:00 do you notice that? 17:12:23 dustymabe, Yup, was thinking about that background X 17:12:26 the background? 17:12:27 X-Men? 17:12:48 the dark text on purple is a little tough to read 17:13:31 Yup. 17:13:43 how do we get this feedback to the right person? 17:13:57 Robyduck is the person in charge iirc. 17:14:10 dustymabe, jbrooks Meanwhile feel free to comment in the ticket. 17:14:13 with the details. 17:14:20 kushal: 10-4 17:14:35 dustymabe, what is that? 17:14:50 kushal: haha - it means ok - i hear you 17:14:50 sorry if I am missing most obvious things :( 17:15:10 Moving to open floor then? 17:15:20 I have few proposals etc. 17:15:45 I say go for it 17:16:11 #topic Open Floor 17:16:44 In the last test day we found no surprises. Autocloud is kind of working hard on the images. 17:16:49 just a note that we're still trying to debug https://bugzilla.redhat.com/show_bug.cgi?id=1392698 17:17:08 But we are still testing the .qcow2 locally, I would love to move that image testing on our Fedora Infra Cloud. 17:17:31 So, only the vagrant images will be tested locally, qcow2s in the real cloud environment. 17:18:10 2. Is about the real tests, till now we are mostly reactive to bugs, we convert those into tests. 17:18:48 .hello bowlofeggs 17:18:50 bowlofeggs: bowlofeggs 'Randy Barlow' 17:18:58 walters: I was going to ask you about that - would be nice to get an executive summary 17:19:02 After F25 release, we can have an online write new test cases (at least file the issues with the ideas) day? We should have enough volunteers to add in those new tests. 17:19:09 #chair bowlofeggs 17:19:09 Current chairs: bowlofeggs dustymabe jbrooks kushal maxamillion sayan trishnag walters 17:19:23 kushal: so what is the problem with testing the qcow locally 17:19:39 I think we should do that, as well as test in openstack ec2 etc.. 17:20:02 dustymabe, Okay, so you are suggesting just add Openstack testing along with local tests? 17:20:10 * are you 17:21:22 sure - that is what I'm suggesting 17:21:35 Okay, we can do that too :) 17:21:43 it already works for local, so might as well keep doing that 17:21:48 Okay. 17:21:50 +1 17:22:26 Next target point is documentation, can we please get our focus back to our users in that area? 17:22:47 In the cloud FAD we had long discussion on that, but not much work was done other than trishnag's writings. 17:22:58 We really need to work more on that area for our users. 17:23:03 bowlofeggs: did make some docs 17:23:09 +1 17:23:17 i did! 17:23:19 dustymabe, Oh yes, about vagrant 17:23:19 it was fun too 17:23:25 One important doc matter -- for f25 atomic, kubernetes is no longer in the image, so we'll need to adjust docs for container-based kube 17:23:33 those same docs are also on the wiki 17:23:51 bowlofeggs: making docs and fun rarely go together ... skeptical face is skeptical 17:23:55 And I think this is a new development, but as of the last rhel atomic, the basic docs are cc licensed 17:24:04 I don't think they were before? 17:24:11 jbrooks: did we make a blog post letting people know about that change? 17:24:14 maxamillion: hahah well i actually kind of like doing that from time to time 17:24:23 dustymabe, I don't think so. 17:24:23 dustymabe, I don't think so 17:24:24 bowlofeggs: fair enough 17:24:25 jbrooks: what are the implications of that 17:24:53 Well, there are a few ways to run kube in containers 17:25:02 jbrooks: no the cc license 17:25:08 Oh, we can resue 17:25:10 reuse 17:25:21 ok, good to know 17:25:26 I think they were behind the paywall before 17:25:43 We don't have fedora-based kube containers 17:25:51 There's an old PR about that 17:26:10 And our kube packages are crazy old 17:26:16 Oh, means we are in kind of broken state :( 17:27:00 I will open up an issue, we have to find out the current state, what all needs to done etc. 17:27:01 I can sum up the situation in a msg to the list 17:27:10 I've been doing some work on possibilities 17:27:17 jbrooks, Can you please open up an issue? 17:27:23 kushal, yes 17:27:41 #action jbrooks to file issue on kube situation w/ f25 atomic 17:27:43 jbrooks, Thanks. 17:28:02 Anything else? 17:28:38 jbrooks: so you're saying the kube in f25 won't work? 17:29:27 dustymabe, It will work, but it's 1.2, and current is 1.4 17:29:30 and 1.5 is in beta 17:29:48 There are up to date kube pkgs in koji for f26 17:30:12 jbrooks: so we just need to karma? 17:30:16 oh wait, f25 17:30:23 f25 != f26 17:30:24 I rebuilt them for f25 and el7: https://copr.fedorainfracloud.org/coprs/jasonbrooks/kubernetes/ 17:30:34 yeah, nothing beyond 1.2 in bodhi 17:30:53 jbrooks: is this because of openshift pinning again? 17:31:00 Just today, Jan switched the pkg back to being based on straight upstream kube, raather than on origin 17:31:05 So that's a nice advance 17:31:19 jbrooks: which means we should be able to move freely again? 17:31:30 Yes 17:31:31 jbrooks, what is stopping us to have it in F25? 17:31:43 I don't know 17:31:51 Here's another option: https://copr.fedorainfracloud.org/coprs/jasonbrooks/kube-release/ 17:32:05 jbrooks: thanks, let's send an email to Jan and copy our list and find out if we can get the latest into f25 17:32:07 for running kube w/ kubeadm, which is slick 17:32:23 I've been in touch w/ him today, I'll ask 17:32:43 jbrooks: wouldn't be bad to have the convo on the list so others can follow 17:32:52 we need to start doing a better job of communicating there 17:32:54 i think 17:32:55 I'll link to the issue on the list 17:33:15 This legit upstream pkg deal is a new development -- I didn't expect it 17:36:05 Okay 17:36:21 I sent Jan a msg 17:36:53 ok one other item for today: 17:36:55 https://lists.fedoraproject.org/archives/list/cloud@lists.fedoraproject.org/thread/2VY5QFBU5KXXBEGCNIYQDSZXEHDILPEG/ 17:36:59 if no other things on plate, we can end the meeting. 17:37:05 please test nightlies as the RC process goes through 17:37:19 we need to make sure we don't forget about atomic host 17:38:10 +1 17:38:26 yup 17:40:00 We will be keeping our eyes open for any new issue. 17:40:14 Ending the meeting then? 17:40:16 5 17:40:19 4.5? 17:40:29 3 17:40:31 2 17:40:35 1 17:40:38 0.7 17:40:40 0.1 17:40:45 #endmeeting