05:00:27 #startmeeting fedora_coreos_apac_meeting 05:00:27 Meeting started Tue Oct 30 05:00:27 2018 UTC. 05:00:27 This meeting is logged and archived in a public location. 05:00:27 The chair is prakashmishra. Information about MeetBot at http://wiki.debian.org/MeetBot. 05:00:27 Useful Commands: #action #agreed #halp #info #idea #link #topic. 05:00:27 The meeting name has been set to 'fedora_coreos_apac_meeting' 05:00:37 Hello everyone :) 05:00:57 This time I see more attendance than previous meetings :) 05:01:15 siddharthvipul: Hi :) 05:01:21 that was a holiday, can't complain ;) 05:01:24 Hi everyone! 05:01:28 Hi 05:01:36 Hello everyone 05:01:42 #topic roll call 05:01:51 paragan: hi :) 05:01:55 .hello sinnykumari 05:01:56 ksinny: sinnykumari 'Sinny Kumari' 05:02:00 .hello prakashmishra1598 05:02:02 .hello2 05:02:03 prakashmishra: prakashmishra1598 'Prakash Mishra' 05:02:04 .hello siddharthvipul1 05:02:06 bhavin192: bhavin192 'Bhavin Gandhi' 05:02:09 siddharthvipul: siddharthvipul1 'Vipul Siddharth' 05:02:33 #chair siddharthvipul ksinny bhavin192 paragan 05:02:33 Current chairs: bhavin192 ksinny paragan prakashmishra siddharthvipul 05:03:11 Hello everyone, It's been quite a while since we had a meeting... Let's get back to business :P 05:03:22 :) 05:04:25 Since we don't have any action items from previous meetings, Let's pick up an issue from the issue tracker 05:04:29 which topic we are discussing today? 05:05:34 Do you wanna discuss the cloud providers issue? I found that interesting and important and it has much recent activity on the tracker 05:05:55 #topic Cloud agents 05:06:06 #link https://github.com/coreos/fedora-coreos-tracker/issues/12 05:07:32 Also a related issue : https://github.com/coreos/fedora-coreos-tracker/issues/41 05:08:00 How do we ship cloud provider specific bits or do we ship it at all 05:09:47 Hmm, I haven't looked into these issues in detail 05:10:45 but yes in Fedora COreOS we will try to not ship separate cloud-agents wehrever possible as per what issue#12 says 05:11:16 Yes, right. 05:11:48 Yes, In the long term it might help though to have a minimal implementations to make it work with most cloud providers 05:12:27 also, we have some recent opened tickets like #71, #70 etc to make sure we discuss cloud agents for each clouproviders like vmware, digitalocean , aws, gce, etc dicussed 05:12:58 So the tools or implementations required for specific cloud provider will be installed and shipped like other packages. This is what I understood 05:13:19 This is really a nice thing as we won't have to deal with these additional overhead 05:13:23 But I also agree that it must not be something we should focus much on 05:13:36 ksinny: Agreed 05:15:15 Anyone has any other thoughts? 05:15:27 But also, Since I run a few CoreOS machines on AWS, I find it easy when my Kubernetes cluster is running smoothly with the CoreOS image seamlessly working with AWS specific bits 05:15:52 Scaling the cluster up and down isn't much of a problem 05:16:10 bhavin192: yeah, whatever is required will be mostly shipped as part of OS 05:16:26 I don't know how this would appear with later versions of Fedora CoreOS 05:17:16 Everyone, Any thoughts on this? 05:17:58 Nothing more from me a of now :) 05:18:07 s/a of/as of/ 05:18:23 I don't know how this would appear with later versions of Fedora CoreOS 05:19:02 we will know soon as FCOS will be in better shape or maybe solution already exist 05:19:07 Okay, Also an interesting issue is the fate of Configuration management tools with Fedora CoreOS 05:19:09 * ksinny needs to dig in 05:19:31 ksinny: Agreed. Time will tell 05:21:00 prakashmishra: Ticket link for the next topic? 05:21:07 #topic Docker version 05:21:35 #topic Configuration management 05:21:44 #link https://github.com/coreos/fedora-coreos-tracker/issues/53 05:22:00 +1 05:22:18 Since we decided not to ship Python, How does this look for the config management tools 05:23:04 I remember having issues with getting Ansible to work with CoreOS a few months ago 05:23:33 prakashmishra, what kind of issue? 05:23:42 Any thoughts on this? everyone 05:24:00 Since Ansible requires the python interpreter to be on the remote machine 05:24:32 siddharthvipul: Ansible needs python to execute modules on remote machine 05:24:55 got it 05:24:56 I think we may go the container approach as mentioned in some of initial discussion of ticket 05:25:29 Yes, But don't you think that approach will be messy? :) 05:26:04 prakashmishra, how? 05:26:13 As then, I'd have to know exactly what parts of the system will my ansible module modify and mount them onto the container 05:26:49 #link https://github.com/coreos/fedora-coreos-tracker/issues/53#issuecomment-423729437 05:27:10 Above link throws some good light on it 05:28:05 prakashmishra, yeah, right. I was thinking about the mapping of directories need to be kept in mind while doing this. That comment explains that well 05:28:18 I think we are running out of time :)... We can continue discussion on this off the meeting :) 05:28:25 +1 bhavin192 05:28:33 #topic Open floor 05:28:38 agreed, we don't have a simple solution of this as of now 05:28:48 Does anybody have anything to discuss?:) 05:28:58 Agreed. ksinny 05:29:11 * ksinny has nothing new to share 05:29:58 I'm ending the meeting :).. Thanks for joining in, Everyone :) 05:30:07 was thinking we can pick "Major release and update cycle for Fedora CoreOS" to discuss in next meeting 05:30:12 ISSue#22 05:30:23 Thank you ksinny and bhavin192 for your views 05:30:32 Awesome, Let's do that :) 05:30:54 prakashmishra++ 05:30:54 prakashmishra, thanks for you effort and chairing the meeting 05:31:02 #endmeeting