17:00:11 #startmeeting Solum Team Meeting 17:00:11 Meeting started Tue Apr 5 17:00:11 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:12 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 17:00:15 The meeting name has been set to 'solum_team_meeting' 17:00:20 #topic Roll Call 17:00:24 Devdatta Kulkarni 17:01:23 Hi, I will watch :-> 17:01:28 hi Ablu 17:01:48 lets wait for few minutes to allow team members to join in 17:01:55 james li 17:01:59 hi james_li 17:02:04 hi devkulkarni 17:02:19 I know that vijendar may not be joining us today 17:02:44 james_li, Ablu: here is the agenda for today's meeting: https://wiki.openstack.org/wiki/Meetings/Solum#Agenda_for_2016-04-05_1700_UTC 17:02:58 james_li: we have Ablu as well for the meeting today 17:03:10 Ablu: do you want to quickly introduce yourself? 17:03:14 Hi Ablu 17:03:40 Ablu: james_li is one of the core contributors of solum 17:04:39 Hm. I am a student who is writing a bachelor thesis about an openstack topic, It is about deploying directly from source repositories 17:04:53 Ablu: cool. 17:05:01 hi vijendar 17:05:11 devkulkarni: hi 17:05:20 we have james_li and Ablu with us today 17:05:23 so I found solum and plan to observe it too see wether it fits the needs (or wether I can reuse parts :)) 17:05:55 Ablu: whats the app you tries to deploy? 17:06:02 Ablu: we would be happy to help you with anything specific related to solum 17:06:35 james_li: it is not about a specific app, more about a general way to deploy applications in various languages from source 17:07:20 Ablu: sounds something with which solum will be able to help 17:07:20 Ablu: yeah. will be cool if you can find some interesting apps to try :) 17:07:53 thanks Ablu for the introduction 17:07:59 lets get started 17:08:15 #topic Announcements 17:08:21 1) TC voting is open; please vote 17:08:26 http://lists.openstack.org/pipermail/openstack-dev/2016-April/091103.html 17:08:51 TC elections are happening right now 17:09:03 you might have received a link to vote 17:09:15 please take a moment to vote 17:09:46 it is important that we participate in this, as the tc is the one who decides the long term strategic vision of openstack as whole 17:10:06 I think the voting remains open till April 7th 17:10:36 second announcement is regarding Austin summit sessions 17:10:43 2) Austin summit tracks 17:10:51 Solum Fishbowl session: April 28, Thursday, 4:10 - 4:50 17:10:57 Solum Work room: April 28, Thursday, 5:00 - 5:40 17:11:07 I have started an etherpad 17:11:11 https://etherpad.openstack.org/p/solum-austin-summit-planning 17:11:34 please add items that you want us to discuss during the work session and the fishbowl session 17:12:48 any other announcements that any of the team members want to make? 17:13:42 alright.. lets move to next topic 17:13:53 #topic Review Action Items 17:13:59 (devkulkarni) (done) Follow up with openstack-infra team to find out root cause for the devstack gate failure 17:14:08 (devkulkarni) (todo) Follow up with the devstack team 17:14:16 our devstack gate is currently failing 17:14:25 last week I updated the team on the issue 17:14:33 let me summarize that 17:15:06 basically, what is happening is, devstack scripts are trying to upload a non-existent log file (n-dhcp.log) 17:15:20 I reached out to the openstack-infra team about this 17:15:38 they confirmed that this is an issue in devstack setup 17:15:47 so we need to follow up with the devstack team 17:15:59 I did not get a chance to do that last week 17:16:10 I might try reaching out to them sometime this week 17:16:24 in the mean time, I have pushed a patch to workaround the issue and unblock the gate 17:16:40 vijendar, james_li: could you please take a look at this patch and approve it? 17:16:46 yeah 17:16:53 https://review.openstack.org/#/c/298342/ 17:17:23 the patch creates a temporary n-dhcp.log in post-gate-hook 17:17:58 once I get some clarity about the root cause from the devstack team, I will remove this 17:18:10 right now, this will unblock the gate 17:18:19 devkulkarni: I just did +2 17:18:26 vijendar: cool, thanks !! 17:18:51 let me progress the meeting to the next topic, which have started any ways 17:18:58 #topic Patches for Review 17:19:16 1) I have updated our docs: https://review.openstack.org/#/c/301244/ 17:19:38 btw, I have added this: https://wiki.openstack.org/wiki/Solum/solum-development-setup 17:20:16 if any of you get a chance to verify the steps listed ^^ (either Vagrant or Devstack or both) that would be awesome 17:20:41 if you have improvements for the steps to make things smoother, that will be even more awesome 17:20:57 I want to get to a smooth setup before the austin summit 17:21:10 imo, we are almost there.. 17:21:37 there are few remaining things that we need to do manually right now (which are outlined in the solum-development-setup wiki page) 17:21:58 if we can automate those as well, that will be really helpful for on-boarding new contributors 17:22:12 on that note, how has been your experience with Solum so far, Ablu? 17:22:55 well, it was a hard ride without too much experience with devstack and vagrant, but I know have a working snapshot I can rely on in the future :) 17:23:13 But yeah, merging the manual steps into the vagrant setup would make stuff a lot more error prone 17:23:24 *a lot less 17:23:27 ha ha 17:23:36 lot less error prone 17:23:37 agree 17:23:53 Ablu: thanks for the patience 17:24:06 Ablu: I am really glad that you have a working setup 17:25:02 Ablu: if you have any improvements, please feel free to suggest those via patches, pull requests, or just some code outline 17:25:33 alright.. let me proceed to the next patch for review and talk about that 17:26:17 2) https://review.openstack.org/#/c/296644/ —> this one updates the releasenotes to include mitaka release information 17:27:01 3) https://review.openstack.org/#/c/296643/ —> and this one does more mitaka release related stuff 17:27:17 both these patches are currently blocked on the devstack gate getting cleared up 17:27:58 this patch https://review.openstack.org/#/c/298342/ is the workaround that I was talking about earlier regarding clearing up of the devstack gate 17:28:22 james_li: if you can review https://review.openstack.org/#/c/298342/ that will help unblock the gate 17:28:32 looking 17:28:37 james_li: thanks 17:29:28 apart from these, there are no outstanding patches to review 17:29:39 our review queue is pretty light right now 17:29:48 https://review.openstack.org/#/q/project:openstack/solum+status:open,n,z 17:29:53 https://review.openstack.org/#/q/project:openstack/python-solumclient+status:open,n,z 17:30:27 https://review.openstack.org/#/q/project:openstack/solum-dashboard+status:open,n,z 17:30:56 are there any patches that any of you are working on that needs review? 17:31:24 if not, let me move to the next topic 17:31:30 #topic Bug Review 17:31:59 there have been no new bugs filed on: https://bugs.launchpad.net/solum/ 17:32:18 Ablu: if you run into any issues, you can use ^^ to file a bug 17:32:31 we also have https://bugs.launchpad.net/python-solumclient/ 17:32:39 where you can file python-solumclient bugs 17:33:44 are there any bugs that any of you have ran into recently? 17:35:49 alright.. if you have ran into any issues/bugs, please use above mentioned links to file the bugs 17:36:07 #topic Open Discussion 17:36:15 1) Updates from upstream 17:36:27 1) Cross-project sessions 17:36:27 https://etherpad.openstack.org/p/newton-cross-project-sessions 17:36:58 the tuesday during the summit week has been reserved for cross-project meetings and discussions 17:37:18 above etherpad has list of all the cross project sessions that have been proposed 17:37:27 folks have voted on different sessions 17:37:41 the final agenda will have only selected sessions 17:38:18 most of these sessions would be interesting imo 17:38:37 if you are attending summit, I would encourage you to attend these sessions 17:38:48 2) Tempest tests for designate 17:38:53 http://lists.openstack.org/pipermail/openstack-dev/2016-April/091295.html 17:39:18 this thread is discussing how the designate team is splitting out their functional tests in a separate repository 17:39:48 in solum, we have been looking at using tempest plugin for writing our functional tests 17:39:57 dimtruck has submitted a patch for it: 17:40:10 https://review.openstack.org/#/c/264899/ 17:40:59 one of the things that the tempest team advocates about writing/creating tempest plugin, is to split out the tests in a separate repo (which is what the designate team is proposing) 17:41:22 I don't know yet whether it is a good option for us 17:41:36 there are pros/cons of both approaches 17:42:10 just something that we should keep in mind 17:42:40 if you have any thoughts about the tempest plugin code for solum, please add your comments to dimtruck's patch 17:43:04 3) Regarding resource reservations 17:43:08 http://lists.openstack.org/pipermail/openstack-dev/2016-April/091390.html 17:43:22 Another interesting thread this week was resource reservations in openstack 17:44:06 apparently there is a cross project effort to figure out the current state of resource reservation across different openstack projects 17:44:17 cinder team has chimed in on that thread 17:44:47 in solum, the issue of reservation for infrastructure has not come up directly 17:44:55 but we do put limits on the number of apps that can be created 17:45:07 there are also limits on the number of instances to which we can scale an app 17:45:59 if you are interested in that topic (resource reservation), I would encourage you to keep yourself looped in on that thread 17:46:18 4) Default flavors are getting removed from Nova 17:46:57 http://lists.openstack.org/pipermail/openstack-dev/2016-April/091434.html 17:48:10 looks like nova is getting rid of default flavors 17:48:25 I don't know if it will directly affect us in solum 17:48:34 but something that I thought you should know 17:49:22 any other topic for open discussion today? 17:53:20 none from me 17:53:31 thanks james_li 17:53:38 alright then 17:53:50 thanks james_li vijendar Ablu for joining the meeting today 17:53:54 see you next week 17:53:57 #endmeeting