17:01:40 #startmeeting fedora_cloud_wg 17:01:40 Meeting started Wed Aug 17 17:01:40 2016 UTC. The chair is sayan. Information about MeetBot at http://wiki.debian.org/MeetBot. 17:01:40 Useful Commands: #action #agreed #halp #info #idea #link #topic. 17:01:40 The meeting name has been set to 'fedora_cloud_wg' 17:01:48 #topic Roll Call 17:01:52 .hellomynameis kushal 17:01:53 kushal: kushal 'Kushal Das' 17:01:53 * gholms waves 17:02:04 .hellomynameis sayanchowdhury 17:02:05 sayan: sayanchowdhury 'Sayan Chowdhury' 17:02:09 .hello jberkus 17:02:10 jberkus: jberkus 'Josh Berkus' 17:02:11 .hello trishnag 17:02:11 .hello jasonbrooks 17:02:12 trishnag: trishnag 'Trishna Guha' 17:02:15 jbrooks: jasonbrooks 'Jason Brooks' 17:02:38 .hello mmicene 17:02:39 nzwulfin: mmicene 'Matt Micene' 17:03:15 I have few things to say in start. 17:04:00 .hello scollier 17:04:01 scollier: scollier 'Scott Collier' 17:04:11 #chair trishnag kushal nzwulfin scollier jberkus gholms 17:04:11 Current chairs: gholms jberkus kushal nzwulfin sayan scollier trishnag 17:04:18 sayan, can I go ahead? 17:04:29 kushal: sure 17:04:56 So during Flock there was some discussion about PRD(s) from different WG(s). 17:05:03 .hello maxamillion 17:05:04 maxamillion: maxamillion 'Adam Miller' 17:05:06 sorry 17:05:24 #chair maxamillion 17:05:24 Current chairs: gholms jberkus kushal maxamillion nzwulfin sayan scollier trishnag 17:05:34 .hellomynameis jzb 17:05:35 jzb: jzb 'Joe Brockmeier' 17:05:50 #chair jzb 17:05:50 Current chairs: gholms jberkus jzb kushal maxamillion nzwulfin sayan scollier trishnag 17:06:03 One of the suggestion from mattdm was about creating a new Fedora Atomic WG. Keeping the Cloud SIG/wg as it is, and making sure we focus more focus on Atomic/openshift side (as discussed in the last cloud FAD). 17:06:11 .hello bowlofeggs 17:06:12 bowlofeggs: bowlofeggs 'Randy Barlow' 17:06:30 I don't think we have enough people or spare cycles for that, but I'm not against it 17:06:42 #chair bowlofeggs 17:06:42 Current chairs: bowlofeggs gholms jberkus jzb kushal maxamillion nzwulfin sayan scollier trishnag 17:06:53 however, if we do that I'll likely exit the Cloud WG and focus only on Atomic WG purely because I wouldn't have the cycles for both 17:07:04 .hello vvaldez 17:07:05 vvaldez: vvaldez 'Vinny Valdez' 17:07:06 maxamillion, understood. 17:07:32 We will have to create new PRD, and making sure we have the actual user stories for the atomic workgroup. 17:07:34 #chair vvaldez 17:07:34 Current chairs: bowlofeggs gholms jberkus jzb kushal maxamillion nzwulfin sayan scollier trishnag vvaldez 17:07:57 I'd probably shit to atomic wg as well 17:08:00 heh 17:08:00 One problem I personally see, that we are not using Atomic in our daily life, and that means we don't see all the problems our users can see. 17:08:02 shift 17:08:08 jbrooks, hahaha :) 17:08:14 jbrooks: :) 17:08:27 kushal: I'm using it daily 17:08:38 Would starting a new group solve that problem? 17:08:48 kushal: and after LinuxCon, I plan to switch to atomic workstation for my laptop 17:09:08 kushal: I have been for the last few days and likely will in the future 17:09:10 gholms, nope, but I am trying to identify people who are interested/users of the atomic side. 17:09:14 That's interesting, would an atomic wg work on atomic workstation, too? 17:09:19 kushal, i thought the intent was to deprecate the CLoud SIG and focus on atomic? 17:09:25 kushal: I thought the idea was that the remainder of Cloud WG would get folded into Server, though? 17:09:26 jbrooks, I think nope. 17:09:27 jberkus: you building your own trees or are there images somewhere being built? 17:09:49 maxamillion: right now, since I'm only using server and tools, I'm using the mainstream tree 17:09:57 scollier, Deprecating Cloud SIG may send out wrong message that we don' 17:10:02 scollier, Deprecating Cloud SIG may send out wrong message that we don't care about Cloud. 17:10:05 once I move to workstation, I'll be sharing a tree with gscrivano, probably 17:10:07 Which is not true at all. 17:10:17 It was just a shift of emphasis. 17:10:20 kushal: my point at the PRD session is: Cloud *is* Server 17:10:34 would be nice to have Matt here 17:10:34 how many new installs of linux today are on bare metal? 17:10:38 jberkus: I'll take that conversation offline but I'm interested in what you're going to do there 17:10:39 scollier, true that. 17:10:46 IMO, worrying about hte name is ... not really that useful 17:10:49 the 17:11:06 maxamillion: Peter and Guiseppe already have a tree for laptops. 17:11:11 of all the stuff we could spend time on whether it's called cloud or atomic seems not so important. 17:11:37 jzb, partially true, we just should not give out any wrong message. 17:11:42 jberkus: I'd likely build my own tree just because I don't really use anything standard, I normally start from a minimal install and kick off my ansible playbook 17:11:55 jzb, because we have images to run on actual clouds. 17:12:13 and we are not killing the base image (may not be the focus, but it is there). 17:12:18 lemme rephrase 17:12:31 given the amount of person-power we have and the amount of time we have to actually work on things 17:12:45 is it a good use of time to worry about branding vs. the other things we could be doing? 17:13:07 is one hour chasing this question down worth one hour that could be spent doing something else? 17:13:11 jzb, I am with you in this point, getting things done are more important. 17:13:43 jzb: I think some of it is seperation of duties/concerns/focus ... I assume the proposed Atomic WG wouldn't focus on, nor care about, the Cloud Base deliverable(s) 17:13:52 jzb: I was more interested in the substance at the PRD; the idea that eventually the server WG would take over the standard AMI images. 17:14:12 jzb, maxamillion also cloud sig will make sure that Fedora is there on AWS, and any such place in future. 17:14:22 jberkus, question is when? 17:14:42 kushal: you'll notice we didn't get an answer on that ;-) 17:14:56 jberkus, Yes, I am also trying to find answers. 17:15:05 anyway, I'm saying that at the PRD session, people were not suggesting creating a fourth WG 17:15:06 That is why I put up this idea here. 17:15:09 #chair walters 17:15:09 Current chairs: bowlofeggs gholms jberkus jzb kushal maxamillion nzwulfin sayan scollier trishnag vvaldez walters 17:15:09 hey, sorry i haven't been to one of these in a while, have it on my calendar again. 17:15:17 which I would have been opposed to, due to lack of manpower 17:15:19 * gholms is curious what makes that a foregone conclusion 17:16:00 jberkus, then as a WG we can decide that just change the name, and update the PRD as required. 17:16:14 Updating the PRD is more important than the name part. 17:16:26 walters: welcome :) 17:16:54 I need to step out for a bit. sorry. jberkus, i did send you a link to the OSE on AWS code, will follow up later. 17:17:22 https://fedoraproject.org/wiki/Cloud/Cloud_PRD 17:17:27 That's the current PRD? 17:17:33 jbrooks, yes. 17:17:38 jbrooks: we didn't finish updating it at Flock 17:18:02 jberkus, that is part of the problem, we had it hanging :( 17:18:13 Is there a draft from flock? 17:18:39 kushal: here's another question of substance: who's going to handle Atomic Workstation? Us, or Workstation WG? 17:19:09 jbrooks, For cloud, none. 17:19:15 jberkus, As I know, workstation 17:19:28 But I can count it as open question. 17:19:58 kushal: we'll need more active collaboration, then, since things like container base images will overlap both. not that that's a bad thing 17:20:06 One thing that stands out to me is how much time we spend on rel eng stuff vs on getting this prd stuff done 17:20:15 (and I'll have to start hangign out in Workstation) 17:20:17 I think better that we up all these questions in one place, and start the discussion over list, and try to find the answers. Without clear goals, it does not make sense. 17:20:26 jberkus, Yes. 17:21:04 I think we know about the deliverables we want to exist, it's not always clear who should deliver them 17:21:31 FWIW i am working on (and currently use on my laptop) https://pagure.io/fork/walters/workstation-ostree-config/branch/f24-continuous 17:21:32 An atomic wg could focus on tooling around atomic things, and work w/ other groups that have specific deliverables 17:21:53 #link https://pagure.io/fork/walters/workstation-ostree-config/branch/f24-continuous 17:21:58 the package layering makes it practical 17:22:01 Ah, that'd be more along the lines of the core and modularity groups. That would make sense. 17:22:08 server and workstation both seem to want to get into the atomic game, in some ways, which is good 17:22:31 walters: +1 - that's cool 17:23:09 jbrooks: "how much time we spend on rel eng stuff" ..... I'm not sure I follow 17:23:42 maxamillion, most of each week seems to be reviewing tickets 17:23:59 jbrooks: yup, and an alarming number of them are blocked on me :/ 17:24:45 * dustymabe lurks 17:25:36 where could someone new like myself contribute? 17:25:41 jbrooks: exactly, on the deliverables 17:25:50 vvaldez: not sure, what do you want to do? 17:26:00 the number of people who show up to this meeting and are involved in the Cloud WG who actually have enough cycles to get real work done is alarmingly low (myself included a large part of the time) 17:26:09 vvaldez: welcome! 17:26:14 glad to have you here 17:26:51 jberkus: I want to help ;) is there a taiga board with tasks or anything? I'm good with ansible if that is needed anywhere, anything else I can hopefully figure out 17:27:05 kushal: do you plan to take this over to the mailing list? we are almost at 50% 17:27:44 sayan, I think that is the better idea. 17:28:05 #action kushal to start off the atomic workgroup discussion on mailing list 17:28:13 sayan, continue please 17:28:26 dustymabe: thanks! 17:28:42 #topic Action items from last meeting 17:28:57 * rtnpro will add test workflow (and test cases) for testing fedora-motd on F24 atomic image 17:28:59 * kushal to write to infra for permission to update Autocloud tests while in freeze 17:29:22 rtnpro: ^^ 17:29:29 vvaldez: oh! we could definitely use help with openshift-ansible and FAH 17:29:37 since rtnpro is not here I will re-action the item 17:29:46 dustymabe, I could not work on it last week 17:29:54 dustymabe, I commit to do it this week 17:30:01 rtnpro: welcome :) 17:30:09 dustymabe, so, let's add it as an action item this week 17:30:12 #action rtnpro will add test workflow (and test cases) for testing fedora-motd on F24 atomic image 17:30:25 #chair rtnpro 17:30:25 Current chairs: bowlofeggs gholms jberkus jzb kushal maxamillion nzwulfin rtnpro sayan scollier trishnag vvaldez walters 17:30:31 I could not do that, got pulled down in something else last week. 17:30:42 Will make sure to do that this Friday. 17:31:38 #action kushal to write to infra for permission to update Autocloud tests while in freeze 17:32:04 #topic Fedora-Dockerfiles examples for Kubernetes https://fedorahosted.org/cloud/ticket/125 17:32:43 jberkus: ^^ 17:33:39 sayan: no updates due to conference schedule 17:33:48 hmmm, but I should comment on the ticket 17:33:59 jberkus: yes, that would be better 17:34:05 moving to next ticket 17:34:26 #topic vagrant boxes fixups https://fedorahosted.org/cloud/ticket/136 17:35:01 since imcleod is not around, moving to next ticket 17:35:50 #topic Don't overwrite download location for 2 week atomic images https://fedorahosted.org/cloud/ticket/147 17:36:27 jbrooks: update on this ticket ^ 17:37:21 sayan, No, it's caught between some releng rewrite of the future and dusty not wanting to link to images from the testing dir structure 17:37:23 I'm going to try and get that done by next meeting at least for the release script, but I'll have to lean on someone else for fedimg/AWS 17:37:31 ah, cool 17:37:39 maxamillion: I can help with that 17:38:06 the rewrite is going to take some time because we're blocked on an auto-signing implementation and I'm just not going to wait on that, we'll get a band-aid fix in for now and handle it more cleanly later 17:38:31 sweet 17:39:27 #topic design, deploy and document Fedora OpenShift Playground (FOSP) https://fedorahosted.org/cloud/ticket/153 17:39:39 vvaldez: I don't have a good writeup of the work which needs to be done, though. Should we use github issues? Or something else? 17:40:03 jberkus: scollier ^^ 17:40:40 jberkus: that works 17:40:51 scollier: should we follow up on FOSP offmeeting? 17:41:08 jberkus: oh! scollier stepped out of the meeting 17:42:11 moving on to next one 17:42:26 #topic make Fedora Atomic download page clearer https://fedorahosted.org/cloud/ticket/154 17:43:36 jberkus: update on this ticket? 17:44:14 sayan: conference delays. will get to this after LInuxcon 17:44:18 updating 17:44:33 jberkus: sure 17:44:51 #topic Decide on post-GA update cadence for various deliverables https://fedorahosted.org/cloud/ticket/155 17:45:33 maxamillion and I followed up on this some w/ releng 17:45:51 There was a complaint of too little specificity 17:46:07 maxamillion, did that, uh, improve any? 17:47:02 jbrooks: not that I know of 17:48:11 maxamillion, If there's an example of the sort of spec we need, I can work on getting it filled out 17:48:23 talk to ppl, send it to the list, etc 17:49:07 sayan, I'll follow up more before next mtg 17:49:31 jbrooks: yeah, I hope to be able to follow up on this some soon ... I've got some work closing out so I'll have a small amount of lag time before my next big project where I hope to clean up a lot of these 17:49:59 jbrooks: ok, moving to the next ticket. 17:50:16 #topic Need complete Kickstart docs for Atomic Host https://fedorahosted.org/cloud/ticket/156 17:51:03 jberkus: any update on this? 17:52:32 sayan: updating 17:52:53 moving to the next one 17:53:10 #topic Ship fedora-motd in F24 atomic image https://fedorahosted.org/cloud/ticket/160 17:54:41 skipping as he already told he did not get to work on fedora-motd 17:54:59 #topic Decide a process about failed tests for Autocloud https://fedorahosted.org/cloud/ticket/167 17:55:05 No update from, will work on thse next week. 17:55:18 * from me 17:55:36 #topic Put OpenShift Origin in Container with Fedora Base https://fedorahosted.org/cloud/ticket/168 17:55:53 skipping this one as scollier isn't around 17:56:07 #topic Open Floor 17:56:23 trishnag, has started writing/updating docs 17:56:36 ryan is helping us with a Fedora theme 17:56:52 You can find it in this link 17:56:53 http://fedoracloud.readthedocs.io/en/latest/ 17:56:58 kushal: yes 17:57:06 ! 17:57:08 .fas x3mboy 17:57:09 x3mboy: x3mboy 'Eduard Lucena' 17:57:11 Cloud-init recently did a long-awaited release, so I will test that on F24 and push it to F25 if it seems to work. (F25 doesn't boot.) 17:57:36 #action gholms to test updated cloud-init on f24 for f25 17:57:39 gholms, if you have any ideas for docs need to be written, feel free to ping me and trishna :) 17:57:53 Thanks! 17:58:13 the docs looks good, needs some minor css fixes 17:58:24 ryanlerch++ 17:58:24 sayan: Karma for ryanlerch changed to 11 (for the f24 release cycle): https://badges.fedoraproject.org/tags/cookie/any 17:58:51 ryanlerch++ 17:58:51 maxamillion: Karma for ryanlerch changed to 12 (for the f24 release cycle): https://badges.fedoraproject.org/tags/cookie/any 17:59:00 that's awesome, I'd love to be able to use that theme for the releng docs 17:59:07 alright, what's next? we're almost at the hour 17:59:25 i've been told there's a b-day in the channel ... 17:59:26 going ahead and closing the meeting 17:59:34 Heh 17:59:39 Hi team, i'm writting on the behalf of the Marketing Team 17:59:40 but no need to do that in meeting :) 17:59:53 We are collecting the talking points for F25 18:00:03 x3mboy: Hi :) 18:00:08 And we really would like to have some about spins 18:00:12 sayan, o/ 18:00:39 If you look in F24 https://fedoraproject.org/wiki/Fedora_24_talking_points we didn't have nothing on spins 18:00:55 x3mboy: the best place to take this discussion to #fedora-cloud 18:01:01 Ok 18:01:07 sayan, thanks 18:01:19 #endmeeting