17:00:12 <devkulkarni> #startmeeting Solum Team Meeting
17:00:13 <openstack> Meeting started Tue Feb 16 17:00:12 2016 UTC and is due to finish in 60 minutes.  The chair is devkulkarni. Information about MeetBot at http://wiki.debian.org/MeetBot.
17:00:14 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
17:00:16 <openstack> The meeting name has been set to 'solum_team_meeting'
17:00:18 <devkulkarni> #topic Roll Call
17:00:22 <devkulkarni> Devdatta Kulkarni
17:02:37 <vijendar1> o/
17:02:44 <devkulkarni> hi vijendar1
17:03:03 <devkulkarni> looks like the attendance is thin today
17:03:14 <devkulkarni> I haven't seen ashish in last couple of days on irc
17:03:17 <pt_15_> devkulkarni: Hi!
17:03:23 <devkulkarni> hi pt_15_
17:03:32 <devkulkarni> we have vijendar1 as well with us
17:04:01 <devkulkarni> here is agenda for today: https://wiki.openstack.org/wiki/Meetings/Solum#Agenda_for_2016-02-09_1700_UTC
17:04:11 <devkulkarni> take a minute to go through it
17:04:17 <vijendar1> ok
17:04:18 <pt_15_> hi vijendar1!
17:04:30 <vijendar1> hi pt_15_
17:05:28 <devkulkarni> alright.. lets proceed
17:05:52 <devkulkarni> #topic Announcements
17:06:08 <devkulkarni> I don't have any prepared announcements.. Do any of you have any announcements/
17:06:09 <devkulkarni> ?
17:06:41 <devkulkarni> ok
17:06:48 <devkulkarni> #topic Review Action Items
17:06:54 <devkulkarni> there were none from last meeting
17:07:02 <devkulkarni> #topic Patch review
17:07:15 <devkulkarni> We have three items here
17:07:21 <devkulkarni> 1) Add CORS support
17:07:25 <devkulkarni> https://review.openstack.org/#/c/278568/
17:07:36 <vijendar1> can you give little context on this
17:07:40 <devkulkarni> yes
17:10:00 <devkulkarni> the problem that this patch is addressing is, how to enable browser/javascript to directly make calls to the Solum API when the js and solum api are not running from the same security domain.
17:10:15 <devkulkarni> standard security model of javascript does not allow this
17:10:28 <devkulkarni> the standard model follows 'same-origin policy'
17:10:35 <vijendar1> ok
17:10:50 <devkulkarni> meaning that the js will be able to make calls on the api running on the same domain as where the js is served from
17:11:12 <vijendar1> I am not sure, what is the need to enable this cross domain javascript calls
17:11:15 <devkulkarni> cors, which stands for cross-origin resource sharing is the mechanism which selectively allows this
17:11:29 <devkulkarni> vijendar1: check the commit message on that patch
17:11:43 <devkulkarni> check the first version of the patch
17:12:04 <devkulkarni> there is some discussion between me and the author
17:12:44 <vijendar1> devkulkarni: ok. will take a look.
17:12:51 <vijendar1> devkulkarni: thanks
17:13:35 <devkulkarni> while supporting cors, how to do it in a secure manner is something that needs some care from the operator, for example, the headers that are set should not allow for making calls to any domain (*), etc.
17:13:39 <devkulkarni> *
17:14:09 <devkulkarni> this patch provides the framework to set up cors support if required
17:14:23 <devkulkarni> by default it will be off
17:15:03 <vijendar1> ok
17:16:06 <devkulkarni> I am just adding a comment to the patch
17:17:35 <devkulkarni> alright
17:17:52 <devkulkarni> the next set of reviews are for app scaling feature
17:17:57 <devkulkarni> https://review.openstack.org/#/c/280377/
17:18:01 <devkulkarni> https://review.openstack.org/#/c/280379/
17:18:16 <devkulkarni> please review these
17:19:59 <dimtruck> o/
17:20:36 <vijendar1> dimtruck: hi
17:20:42 <dimtruck> hello! sorry i'm late
17:20:44 <devkulkarni> hi dimtruck
17:20:48 <devkulkarni> dimtruck:  no worries
17:20:53 <devkulkarni> here is the agenda for today's meeting
17:21:01 <devkulkarni> https://wiki.openstack.org/wiki/Meetings/Solum#Agenda_for_2016-02-09_1700_UTC
17:21:16 <devkulkarni> we are currently in 'Patches for review' topi
17:21:18 <dimtruck> yup, reviewd
17:21:19 <dimtruck> yup
17:21:23 <devkulkarni> awesome
17:21:36 <devkulkarni> next item is a tech debt
17:21:43 <devkulkarni> https://review.openstack.org/#/c/238714/
17:21:52 <devkulkarni> pt_15_: do you want to provide some context for this patch?
17:22:20 <pt_15_> devkulkarni: yes, sure!
17:22:42 <devkulkarni> please go ahead
17:23:25 <pt_15_> the patch basically refactors the trigger controller, which  earlier just had one big method
17:24:00 <pt_15_> it breaks up that method into smaller ones, and also add tests for these newly created methods
17:24:21 <devkulkarni> I have reviewed the patch pt_15_
17:24:25 <devkulkarni> it looked good to me
17:24:47 <devkulkarni> looks like vijendar1 also reviewed
17:24:48 <devkulkarni> it
17:25:13 <pt_15_> yes, thanks! :)
17:25:21 <devkulkarni> vijendar1: I see that you have given +1 for workflow.. cool .. but I think you will have to give a +2 vote as well
17:25:26 <devkulkarni> otherwise it won't merge
17:25:42 <vijendar1> devkulkarni: ok
17:25:53 <devkulkarni> alright
17:26:07 <devkulkarni> well nm, it merged
17:26:25 <devkulkarni> next item is
17:26:30 <devkulkarni> Cutting a release
17:26:35 <devkulkarni> #link http://lists.openstack.org/pipermail/openstack-dev/2016-February/086152.html
17:26:43 <devkulkarni> last week we talked about this a bit
17:27:09 <devkulkarni> I re-read that email and realized that we actually have to cut one release in next two weeks
17:27:17 <devkulkarni> basically, before the mitaka-3 deadline
17:27:32 <devkulkarni> after that, till April 1, we can cut as many releases as we want
17:27:57 <devkulkarni> but infra folks are suggesting that we have one release in next two weeks
17:28:27 <devkulkarni> so I am thinking that, we should try to get most of our current outstanding patches merged in next few days
17:28:48 <devkulkarni> and then next week I can propose a patch for the release
17:29:16 <devkulkarni> thought/comments/questions?
17:30:25 <devkulkarni> alright.. lets move to open discussion then
17:30:26 <vijendar1> sure. let's merge as many possible
17:30:35 <devkulkarni> cool, thank vijendar1
17:30:45 <devkulkarni> #topic Open Discussion
17:30:52 <devkulkarni> Austin summit talks submitted by our team
17:30:56 <devkulkarni> https://www.openstack.org/summit/austin-2016/vote-for-speakers/Presentation/7864
17:31:00 <devkulkarni> https://www.openstack.org/summit/austin-2016/vote-for-speakers/Presentation/7842
17:31:04 <devkulkarni> https://www.openstack.org/summit/austin-2016/vote-for-speakers/presentation/8129
17:31:08 <devkulkarni> please vote :)
17:32:14 <vijendar1> devkulkarni: is there any last date to vote?
17:32:31 <devkulkarni> I think it is end of february
17:33:34 <vijendar1> devkulkarni: anyways I just did my voting
17:33:43 <devkulkarni> cool
17:33:53 <devkulkarni> I also voted on several last week itself
17:34:08 <devkulkarni> if you search for 'solum', you will see that there are a few other talks submitted as well
17:34:13 <devkulkarni> I have voted for those too
17:35:07 <devkulkarni> on another note, I spent some time trying to get devstack setup with solum plugin
17:35:17 <devkulkarni> this is for development purposes
17:35:27 <devkulkarni> we have been wanting to do this for a while
17:35:42 <devkulkarni> and last week's meeting kind of brought this into more focus
17:36:29 <devkulkarni> I think I have got success in this.. in my vagrant vm I was able to use the solum's devstack plugin to spin up solum services
17:36:42 <devkulkarni> the trick is to add the enable_plugin line in local.conf
17:37:02 <devkulkarni> I am in the middle of verifying that it again..
17:37:06 <vijendar1> devkulkarni: cool
17:37:11 <devkulkarni> trying it on a brand new cloud server
17:37:17 <vijendar1> devkulkarni: it will be very useful
17:37:31 <devkulkarni> will post instructions as a review once the verification is done
17:37:54 <devkulkarni> while I was trying to get the plugin story figured out,
17:38:10 <devkulkarni> I also wanted to see if we can get a consistent app deployment experience..
17:38:30 <devkulkarni> basically, we want to be able to get a "READY" app consistently
17:39:04 <devkulkarni> I am testing out few things in this regard right now
17:39:44 <devkulkarni> basic issue that we are running into is docker seems to pick ipv6 when assigning ip addresses to the application containers that it spins up
17:39:56 <dimtruck> you can pass a flag
17:40:07 <dimtruck> to force it to use ipv4
17:40:11 <devkulkarni> dimtruck: flag to the docker daemon?
17:40:27 <devkulkarni> dimtruck: what is the flag? where to pass it in?
17:40:38 <devkulkarni> dimtruck: the solution that I am experimenting with is the following
17:41:28 <devkulkarni> I am basically telling neutron to not create ipv6 subnets in the first place.. I found that we can set 'IP_VERSION=4' in local.conf for this
17:41:53 <devkulkarni> the reason I followed this path was based on the explanation given on this link:
17:42:05 <devkulkarni> http://blog.oddbit.com/2015/02/11/installing-novadocker-with-devstack/
17:42:09 <devkulkarni> check the comments section
17:42:23 <devkulkarni> there is a comment by nindate
17:42:42 <devkulkarni> what nindate has described there is exactly what I was seeing
17:42:47 <dimtruck> hmmm
17:42:57 <devkulkarni> the solution that nindate found was to delete the neutron ipv6 subnet
17:43:04 <devkulkarni> I tried that, but it does not work
17:43:17 <devkulkarni> as there are ports associated with that subnet which we cannot delete
17:43:25 <devkulkarni> atleast, I was not able to delete them
17:43:39 <devkulkarni> so then I started thinking, what if we tell neutron to not even create the ipv6 subnet
17:43:55 <devkulkarni> after quite a lot of googling I stumbled upon IP_VERSION variable
17:44:09 <devkulkarni> there is also one more, SERVICE_IP_VERSION
17:44:23 <devkulkarni> don't know which is the correct one.. right now I am setting them both to '4'
17:44:37 <devkulkarni> with this setup, I was able to get an app to READY state consistently
17:44:55 <devkulkarni> but again, the apps may have become READY due to random chance
17:45:05 <vijendar1> devkulkarni: will try in my dev env
17:45:14 <devkulkarni> I have experienced it before.. randomly apps will reach READY
17:45:26 <devkulkarni> so I don't want to yet conclude if we have found a solution
17:45:35 <devkulkarni> vijendar1: yes, that will be very helpful
17:45:56 <devkulkarni> if you have the setup, I would say just add those two variables in your local.conf
17:46:04 <devkulkarni> and then ./unstack and ./stack
17:46:15 <devkulkarni> right now, I am trying that as well
17:46:25 <dimtruck> weiiirrd
17:46:26 <dimtruck> ok
17:46:42 <devkulkarni> will have more clarity about the plugin and ipv4 hopefully today/tomorrow
17:47:56 <devkulkarni> pt_15_: how is your development environment looking these days?
17:48:08 <devkulkarni> pt_15_: and when is the deadline for your application submission?
17:48:30 <pt_15_> devkulkarni: it's still pretty much as i had left it in december
17:48:41 <pt_15_> i havent been able to get round to working on it
17:48:56 <pt_15_> the deadline is 25th march
17:49:34 <devkulkarni> pt_15_: ok.. hopefully with the new plugin stuff it will be bit easier to get the development environment
17:49:49 <devkulkarni> pt_15_: for the deadline, what all things do you need?
17:50:03 <pt_15_> devkulkarni: yeah, hopefully it will be easier :)
17:50:20 <pt_15_> i will need details of the project i intend to work on
17:51:21 <pt_15_> and i was actually hoping that we could maybe discuss these details within this week, before the deadline for the organization to propose projects
17:52:07 <devkulkarni> pt_15_: sure.. the etherpad that we created for last round had details about several projects
17:52:14 <devkulkarni> we can revisit that and see
17:52:33 <pt_15_> ok, that would be great!
17:52:39 <devkulkarni> https://etherpad.openstack.org/p/projects-for-outreachy-program
17:53:12 <devkulkarni> vijendar1, dimtruck: please add your ideas if you have any on the etherpad
17:53:36 <devkulkarni> pt_15_ is planning to apply for Outreachy and Google summer of code internship programs
17:53:37 <dimtruck> will do!
17:53:42 <vijendar1> ok
17:53:43 <dimtruck> awesomeness!!!
17:53:54 <devkulkarni> cool
17:54:26 <devkulkarni> alright.. anything else for us to cover today?
17:55:30 <devkulkarni> ok then..
17:55:39 <devkulkarni> thank pt_15_ vijendar1 dimtruck for joining today
17:55:48 <devkulkarni> I will see you next week
17:56:08 <devkulkarni> in the mean while use the solum irc channel to find me (or others)
17:56:22 <devkulkarni> #endmeeting