15:02:10 <lalatenduM> #startmeeting Atomic Developer Bundle Weekly Meeting
15:02:10 <zodbot> Meeting started Mon Feb 22 15:02:10 2016 UTC.  The chair is lalatenduM. Information about MeetBot at http://wiki.debian.org/MeetBot.
15:02:10 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
15:02:10 <zodbot> The meeting name has been set to 'atomic_developer_bundle_weekly_meeting'
15:02:19 <dharmit> .fas dharmit
15:02:19 <zodbot> dharmit: dharmit 'Dharmit Shah' <shahdharmit@gmail.com> - shahdharmit 'Dharmit Shah' <shahdharmit@gmaill.com>
15:02:23 <nshaikh> .fas nshaikh
15:02:23 <zodbot> nshaikh: nshaikh 'Navid Ahmed Shaikh' <shaikhnavid14@gmail.com>
15:02:23 <lalatenduM> .hellomynameis lalatendu
15:02:25 <zodbot> lalatenduM: lalatendu 'Lalatendu Mohanty' <lmohanty@redhat.com>
15:02:48 <ccaf> .hellomynameis containscafeine
15:02:49 <zodbot> ccaf: containscafeine 'Shubham Minglani' <shubham@linux.com>
15:02:54 <lalatenduM> info meeting agenda at https://titanpad.com/adbmeeting
15:02:56 <tkral> .hellomynameis tkral
15:02:56 <zodbot> tkral: tkral 'Tomas Kral' <tkral@redhat.com>
15:03:01 <lalatenduM> #info meeting agenda at https://titanpad.com/adbmeeting
15:03:22 <budhram> .hellomynameis budhram
15:03:23 <zodbot> budhram: budhram 'Budh Ram Gurung' <bgurung@redhat.com>
15:03:57 <mzee1000> .fas mohammedzee1000
15:03:57 <zodbot> mzee1000: mohammedzee1000 'Mohammed Zeeshan Ahmed' <mohammed.zee1000@gmail.com>
15:04:30 <surajd> .fas surajd
15:04:31 <zodbot> surajd: surajd 'Suraj Deshmukh' <surajssd009005@gmail.com>
15:05:39 <lalatenduM> ok, looks like are good to go ahead
15:05:53 <tuxdna> .fas tuxdna
15:05:53 <zodbot> tuxdna: tuxdna '' <tuxdna@gmail.com>
15:06:07 <lalatenduM> #topic Next ADB release @lalaenduM
15:07:02 <lalatenduM> According to biweekly schedule we should do a release this week. But because we slipped the schedule for last build by1 week
15:07:07 <nshaikh> What all changes we are looking for next ADB release ?
15:07:23 <lalatenduM> I am not sure whether we should do a release this week
15:07:37 <lalatenduM> nshaikh: there will be bug fixes in adb and adb-utils
15:08:03 <nshaikh> okay
15:08:32 <nshaikh> are we also looking at targeting the glibc fix  in next release ?
15:08:58 <nshaikh> lalatenduM, there will be some changes needed in the ADB box as part of fixing the TLS certs generation issue.
15:09:06 <lalatenduM> nshaikh: we escaped that , last release has teh fix , thats kbsingh mentioned
15:09:28 <nshaikh> okay
15:09:52 <nshaikh> regarding TLS certs issue: With <https://github.com/projectatomic/vagrant-service-manager/pull/54> in place for service-manager plugin -
15:09:53 <lalatenduM> nshaikh: yeah TLS certs generation issue is a major one
15:10:20 <lalatenduM> nshaikh: I think bexelbie was planning to send a mail about it to container-tools
15:10:24 <nshaikh> the docker daemon will be re-configured at the time of `vagrant up`
15:10:40 <budhram> lalatenduM, last release means ADB 1.7 release?
15:10:40 <nshaikh> lalatenduM, I had a chat with him and he is on it, should be in the ML latest by tomorrow.
15:10:50 <lalatenduM> budhram: yes
15:11:09 <lalatenduM> nshaikh: ok, then we should do a release thsi week
15:11:42 <lalatenduM> but we have very less time
15:11:43 <nshaikh> lalatenduM, yes - temporarily the plugin can carry the patches to fill in gaps for sought-changes-in-ADB
15:12:07 <lalatenduM> nshaikh: right
15:12:12 <nshaikh> once ADB has required changes for config + hook approach PR , the plugin will need re-spin.
15:12:43 <budhram> lalatenduM, is it written differently in changelog(https://github.com/projectatomic/adb-atomic-developer-bundle/blob/master/CHANGELOG.md#v170-feb-17-2016) ? unable to find that change
15:13:01 <lalatenduM> budhram: you mean the glibc fix?
15:13:50 <budhram> lalatenduM, no disabling docker so that it could be re-configured on vagrant up
15:14:11 <lalatenduM> budhram: oh thats not done yet , it would be in the next release
15:14:31 <lalatenduM> just crossed checked ADB 1.7.0 for glibc
15:14:38 <lalatenduM> and it has glibc-2.17-106.el7_2.4.x86_64 which has teh fix
15:15:04 <lalatenduM> #info ADB 1.7.0  has glibc security fix i.e. version glibc-2.17-106.el7_2.4.x86_64
15:15:25 <lalatenduM> ok moving on to next topic
15:15:35 <nshaikh> ok
15:15:39 <lalatenduM> #topic Next release of vagrant-service-manager
15:16:03 <lalatenduM> nshaikh: I think we have this covered in the previous discussion , right?
15:16:17 <nshaikh> lalatenduM, there are few more points I would like to add.
15:16:36 <budhram> lalatenduM, waiting for your review too
15:16:45 <budhram> as you said u will review it later
15:17:00 <lalatenduM> budhram: yup, will do
15:17:11 <lalatenduM> nshaikh: go ahead
15:17:27 <nshaikh> #info: Next release of the plugin will add a sub-command for displaying the openshift info.
15:17:28 <budhram> also I added my last comment on bexelbie's comment
15:17:47 <nshaikh> #info: Next release is also targeted to add a sub-command for displaying the box version.
15:18:11 <nshaikh> Need to investigate more on copying the kubeconfig from ADB to host machine and setting required info.
15:18:14 <budhram> nshaikh, also need to add way to show warning info if any service is unavailable
15:18:36 <nshaikh> budhram, that's for config + hook PR right ?
15:18:47 <budhram> yes
15:18:53 <nshaikh> budhram, yes then.
15:19:24 <lalatenduM> nshaikh: budhram ok
15:19:33 <nshaikh> To show the kubernetes information via the plugin - the kubernetes configuration inside the box needs tweaks.
15:19:51 <lalatenduM> nshaikh: yes, I saw the patch from you
15:20:10 <nshaikh> Also, what about configuring kubernetes via containers ?
15:20:39 <nshaikh> does anybody have more info on that ?
15:20:41 <lalatenduM> nshaikh: yeah we need to starting planning that
15:20:53 <lalatenduM> nshaikh: Chris pointed me to some docs
15:20:58 <lalatenduM> I need to go through that
15:21:05 <budhram> nshaikh, please give me more context on issue#16(https://github.com/projectatomic/vagrant-service-manager/issues/16). may be we can include it in next release if done
15:21:27 <nshaikh> lalatenduM, so - can we solve adb issue #250 as part of shipping kube via containers ? or we want to discuss more over cabal ?
15:21:31 <budhram> nshaikh, K8s via containers?
15:21:51 <lalatenduM> nshaikh: we need discuss in cabal too
15:22:22 <nshaikh> budhram, re: service-manager issue #16 : For VirtualBox provider, private networking needs to be setup for ADB box - If user has not configured private networking in Vagrantfile, the plugin should report that.
15:22:31 <lalatenduM> nshaikh: but I think that would be after 2.0 GA
15:22:39 <budhram> u mean running k8s inside docker container? like master in one container and minion in others?
15:22:43 <tkral> lalatenduM, I think  that #250 is now more about documenting how to do that right,
15:23:02 <tkral> ^ + some vagrant-service-manager magic ;-)
15:23:21 <nshaikh> budhram, There needs to be a way to figure out, if the provider is virtualbox && private networking is not configured, then error out.
15:23:25 <nshaikh> budhram, does that make it clear ?
15:23:45 <lalatenduM> tkral: I will look in to it  and figure out if we need to fix it or document it
15:24:08 <nshaikh> budhram, that applies for use case where user wants to connect to providers (docker, kube, openshift) from client side tools.
15:24:41 <nshaikh> budhram, the gist is to have a routable IP for the box if VirtualBox provider is used.
15:24:47 <lalatenduM> tkral: if we can fix it bydefault in teh ADB box that would be good experience for th euser
15:24:50 <budhram> yes. so is it only with virtualbox ? not libvirt? sorry don't know much about libvirt
15:25:05 <lalatenduM> nshaikh: budhram we need to mov eon to #oepenfloor
15:25:06 <nshaikh> budhram, correct - for VirtualBox provider.
15:25:11 <nshaikh> okay
15:25:11 <lalatenduM> openfloor*
15:25:16 <budhram> ok nshaikh thnks
15:25:21 <lalatenduM> #topic openfloor
15:25:52 <lalatenduM> tkral: do you have any topic
15:26:02 <lalatenduM> dharmit: ^
15:26:10 <tkral> I have one: https://github.com/projectatomic/adb-atomic-developer-bundle/issues/235
15:26:37 <lalatenduM> +1 to include it as RPM
15:26:45 <dharmit> lalatenduM: Nope, I am still waiting for my CentOS CI account to get created! And looking at other issues on ADB to possibly contribute to.
15:27:35 <dharmit> Not focusing more on latter part as CI for ADB is going to be a major thing to implement IMO.
15:27:42 <lalatenduM> I think when we include any RPM in to ADB box we need make sure all teh maintainers agree to it cc nshaikh bexelbie praveenkumar
15:28:00 <lalatenduM> dharmit: thanks for the update
15:28:08 <nshaikh> tkral, lalatenduM : is running openshift must for functioning openshift2nulecule ?
15:28:51 <nshaikh> dharmit, The account creation at CI is taking a bit longer time!
15:29:04 <dharmit> bit? :-)
15:29:06 <tkral> lalatenduM, ok. Than I would also need big assistance how to properly propagate rpms to adb/cdk. I am clue less how to do that.
15:29:23 <lalatenduM> tkral: BTW thsi repo is already available in ADB http://mirror.centos.org/centos-7/7/atomic/x86_64/adb/
15:29:41 <lalatenduM> tkral: we can always make openshift2nulecule available there
15:29:42 <tkral> nshaikh, you don't need running openshift, You only need oc client binary
15:29:47 <lalatenduM> nshaikh: answer is no
15:30:00 <nshaikh> okay, +1 for including it as RPM.
15:30:28 <nshaikh> If a utility is provider specific, I'll vote for having the utility shipped via same means as we are shipping the provider itself.
15:30:32 <tkral> lalatenduM, ok, there are also some python libraries that are only in epel
15:31:03 <lalatenduM> tkral: sure we can rebuild dependancies too
15:31:40 <lalatenduM> tkral: I think you should maintain the RPM in CentOS SIG
15:31:55 <lalatenduM> I will help you through teh process
15:32:05 <tkral> lalatenduM, ok. Only think now is that i don't know how to do any of that
15:32:12 <tkral> lalatenduM,  thx ;-)
15:32:15 <lalatenduM> tkral: np :)
15:32:38 <lalatenduM> We are reaching of time limit of our meeting
15:32:56 <lalatenduM> if you guys dont have new topics we can close the meeting
15:33:06 <lalatenduM> going 1..
15:33:13 <lalatenduM> 2 ..
15:33:35 <lalatenduM> 3 ..
15:33:40 <lalatenduM> #endmeeting