16:00:14 <xarses> #startmeeting fuel
16:00:14 <xarses> #chair xarses
16:00:14 <xarses> Todays Agenda:
16:00:14 <xarses> #link https://etherpad.openstack.org/p/fuel-weekly-meeting-agenda
16:00:14 <xarses> Who's here?
16:00:15 <openstack> Meeting started Thu Aug 25 16:00:14 2016 UTC and is due to finish in 60 minutes.  The chair is xarses. Information about MeetBot at http://wiki.debian.org/MeetBot.
16:00:16 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
16:00:18 <mwhahaha> hi
16:00:18 <openstack> The meeting name has been set to 'fuel'
16:00:19 <maximov> hi
16:00:20 <openstack> Current chairs: xarses
16:00:27 <mzawadzki> Hello.
16:00:30 <vkramskikh> hi
16:00:40 <zubchick> hi
16:00:41 <mattymo> hi!
16:01:26 <xarses> #topic action items from last meeting
16:01:33 <xarses> romcheg to annouunce fuel2 promotion and old fuel CLI removal on ML
16:02:08 <kozhukalov> romcheg is PTO
16:02:13 <xarses> ok
16:02:18 <xarses> akscram to send ML about moving cluster_upgrade extension
16:02:40 <kozhukalov> seems done
16:02:43 <romcheg> who is on PTO?
16:02:45 <romcheg> :)
16:02:50 <kozhukalov> wow
16:03:04 <romcheg> I've just returned today
16:03:17 <romcheg> There is nothing to deprecate unfortunatelly
16:03:18 <mattymo> It's a miracle
16:03:22 <xarses> any update on your action item?
16:03:40 <xarses> I don't recall anything on the ML about it
16:04:06 <romcheg> while I was away someone from the management decided that we cannot remove the old CLI in 9.1
16:04:23 <romcheg> due to a minor issue in fuel-devops
16:05:11 <romcheg> As soon as the epic is updated I will  be able to make an announcement in the ML
16:05:19 <xarses> ok, thanks
16:05:23 <xarses> gkibardin to follow up on ML about mcollective config issues
16:05:24 <romcheg> dpyzhov asked someone
16:05:34 <romcheg> to update the epic
16:05:34 <xarses> seems done too
16:05:50 <xarses> xarses will update spec regarding release naming and summarize on ML
16:06:08 <xarses> the spec was updated, and I still need to write up releases in the ML
16:06:15 <xarses> actually, the spec is merged now =)
16:06:42 <xarses> onto our regular topics
16:06:45 <kozhukalov> you mean spec "release as a plugin"?
16:06:51 <xarses> yes
16:07:02 <romcheg> xarses: should we create another action item for fuelclient for me?
16:07:08 <xarses> romcheg:
16:07:11 <xarses> sure
16:07:33 <romcheg> thanks!
16:07:36 <kozhukalov> yes, there were some q from you? did ashtokolov answer all your q?
16:07:51 <xarses> #action romcheg update ML with regards to the removal of fuel and the promotion of fuel2
16:08:17 <xarses> kozhukalov: yes, adding the last parameter closed the question for me
16:09:54 <xarses> #topic Add new vote jenkins job to fuel-web for cluster_upgrade extension testing (nzubkov)
16:10:19 <xarses> nzubkov isn't here, can someone else speak to this?
16:10:25 <zubchick> I'm here
16:10:36 <xarses> oh, hi
16:10:38 <xarses> =)
16:10:38 <kozhukalov> -)))) nice nickname
16:11:15 <zubchick> We have separated extension from fuel web repo and want run extension tests for every fuel-web patch set
16:11:33 <zubchick> to keep thing up
16:12:17 <xarses> ok, ya didn't I see a CR for that?
16:12:28 <xarses> (adding the tests)
16:13:10 <zubchick> we have already have job that non voting
16:13:56 <zubchick> here CR that makes it voting https://review.fuel-infra.org/#/c/23796/
16:14:47 <xarses> ok, anything else we need to do here?
16:15:09 <zubchick> No objections? :)
16:15:23 <zubchick> then I’ll ask CI team merge this
16:15:27 <xarses> none from me
16:15:52 <xarses> you have +1 from some of the fuel-web cores, so I think thats good
16:16:08 <kozhukalov> +1
16:16:18 <zubchick> ok,thanks
16:16:35 <xarses> moving on?
16:17:17 <xarses> #topic Recent UI improvements (vkramskikh)
16:17:21 <vkramskikh> Hi! I'd like to announce that Fuel UI team has implemented 2 features in master and stable/mitaka. Deployment history allows to see a list of deployment transactions and details for each transaction, including the running deployment. Custom graph management allows to view, download, upload and run custom graphs for clusters. These 2 features are represented as 2 new tabs on the cluster page in Fuel UI. They are fully functional
16:17:21 <vkramskikh> and can be used, though some bugfixes are still expected. We would appreciate any feedback and bugreports regarding these 2 features.
16:18:16 <xarses> sounds awesome
16:18:39 <kozhukalov> yes, I saw these changes, they are nice
16:19:01 <kozhukalov> especially tasks progress
16:19:47 <xarses> anything else?
16:19:51 <kozhukalov> one q
16:19:54 <vkramskikh> none from my side
16:20:25 <kozhukalov> just wondering is it planning to run graphs unbound from any clusters and releases?
16:20:48 <xarses> oh, the cluster 0 stuff?
16:20:55 <vkramskikh> don't have such plans, but that can be discussed
16:20:57 <kozhukalov> are there any ideas on how to deal with fake clusters if we bind some graphs to fake clusters
16:21:26 <kozhukalov> at least diagnostic snapshot could one of such graphs
16:21:50 <kozhukalov> ok, let's discuss this later
16:21:59 <vkramskikh> shouldn't be any difficulties to implement this on UI side
16:22:01 <xarses> and the task to edit the dhcp ranges in dnsmasq
16:22:01 <kozhukalov> thanks vkramskikh
16:22:16 <maximov> kozhukalov: why we cannot bind diag snapshot to clusters ?
16:22:28 <kozhukalov> we can
16:22:37 <maximov> usually you want to troubleshoot some specific cluster
16:22:39 <maximov> right/?
16:22:43 <kozhukalov> but it should be admin cluster
16:23:18 <xarses> to prevent more than one running at a time
16:23:29 <kozhukalov> right. but sometimes you want to troubleshoot admin node
16:23:36 <xarses> that too
16:24:07 <xarses> ok moving on?
16:24:14 <maximov> so the point is just to prevent parallel execution?
16:24:32 <kozhukalov> not only parallel execution
16:25:03 <kozhukalov> we will definitely need graphs of tasks that do not relate to any cluster
16:25:26 <kozhukalov> like dhcp ranges, that xarses mentioned
16:25:26 <maximov> in case of diag snapshot, why do we need it ?
16:26:02 <kozhukalov> forget about diag snapshot, my q was about how to deal with fake/admin clusters on UI
16:26:25 <kozhukalov> i was wondering if there are any ideas on this
16:26:48 <maximov> I think we need to collect all uses cases.. before.
16:27:15 <kozhukalov> sure
16:27:16 <maximov> we have dhcp ranges update as a possible candidate for global workflow
16:27:36 <kozhukalov> not only this
16:27:48 <kozhukalov> upgrade master node for example
16:28:12 <kozhukalov> rebuild bootstrap image
16:28:16 <kozhukalov> etc
16:28:21 <maximov> ok i see
16:28:38 <kozhukalov> let's move one
16:28:44 <kozhukalov> let's move on
16:28:58 <xarses> #topic Documentation on upgrades https://review.openstack.org/#/c/337122 (REVIEW IS WELCOME) (kozhukalov)
16:29:31 <kozhukalov> I'd just like to ask everyone to help to review this patch
16:30:08 <kozhukalov> feature is ready, spec on review, and documentation part is very important
16:30:17 * xarses adds it to his list
16:30:25 <xarses> I'll try to take a look at it soon
16:30:35 <kozhukalov> users continue asking where to read about upgrades, backups
16:30:48 <kozhukalov> xarses: thanks
16:31:07 <kozhukalov> looks like we don't have any other topic
16:31:44 <kozhukalov> just small announcement: we are under FF now for mitaka branch
16:31:57 <xarses> #topic open discuss
16:32:06 <xarses> anything else to raise or discuss?
16:32:32 <kozhukalov> I continue to work on ISOless bvt jobs for our CI
16:32:49 <kozhukalov> it is on review, but WIP
16:33:15 <kozhukalov> #link https://review.fuel-infra.org/#/c/25285/
16:33:44 <xarses> I started a spec about creating a new release
16:33:49 <xarses> #link https://review.openstack.org/357346
16:34:26 <xarses> ok, if nothing else, I'll close the meeting
16:34:51 <kozhukalov> yet another announcement
16:35:09 <kozhukalov> we are 2 months from Ocata design summit
16:35:26 <kozhukalov> so, please feel free to add your topics here https://etherpad.openstack.org/p/fuel-ocata-summit-planning
16:35:31 <kozhukalov> #link https://etherpad.openstack.org/p/fuel-ocata-summit-planning
16:35:52 <kozhukalov> I requested 2 fishbowls and 4 workrooms sessions
16:36:55 <kozhukalov> I am not sure many people from fuel team will attend this summit
16:37:27 <kozhukalov> but still it is better to plan it in advance
16:37:45 <kozhukalov> nothing more from my side
16:38:01 <kozhukalov> ccp people aren't here
16:38:07 <mzawadzki> we are here
16:38:14 <kozhukalov> ohh nice
16:38:22 <amnk> yep
16:38:32 <kozhukalov> would you like to share something?
16:38:32 <xarses> ok, will close if there is nothing else
16:38:45 <mzawadzki> I can share stuff we're currently working on.
16:38:48 <mzawadzki> for CCP
16:39:49 <mzawadzki> So we'll soon have feature for showing status of deployed applications & ability to redeploy specific service.
16:40:16 <mzawadzki> We also finished implementing command for displaying service dependencies.
16:40:52 <mzawadzki> Another feature that is important for OpenStack developers is abvility to use git repositories as sources for building Docker images for CCP.
16:41:18 <mzawadzki> Including tags & private branches - so one can run OpenStack in Docker with custom changes to e.g. Keystone.
16:41:52 <mzawadzki> There is also WIP on providing Vagrant based dev env for developers & testers.
16:42:18 <mzawadzki> Research in progress on galera clustering with proxysql.
16:42:48 <mzawadzki> We've also recently started publishing CCP Docker images in public repo: http://registry.mcp.fuel-infra.org:5002/?name=.*&tag=.*&format=dictionary
16:43:13 <mzawadzki> + some CI improvements.
16:43:54 <mzawadzki> Major goals for nearest future are updates & CI/CD automation for production.
16:44:07 <mzawadzki> That's it, I don't want to take more time, feel free to ask questions.
16:44:32 <kozhukalov> it would be nice to have a single place like wiki page where users/developers could read about reference architecture, tools, UX, etc.
16:44:47 <kozhukalov> we could link this page from fuel wiki
16:44:59 <amnk> we are working on documentation
16:45:24 <amnk> unfortunately it's not there yet
16:45:33 <kozhukalov> nice, are there any links to CRs to review?
16:46:02 <kozhukalov> like this one for example https://review.openstack.org/#/c/337122
16:46:08 <mzawadzki> No, we've just started discussing how to handle the process of moving our docs to upstream.
16:46:28 <mzawadzki> So far they live only on internal wiki.
16:46:43 <mzawadzki> But we have a user story about it.
16:47:11 <kozhukalov> what is user story? you mean jira?
16:47:35 <mzawadzki> Yeah.
16:47:43 <kozhukalov> let's avoid mentioning vendor specific terminology here
16:47:58 <mzawadzki> OK. IOW we have a plan, just need to work on it.
16:48:06 <kozhukalov> ok, looking forward for documentation CRs
16:48:25 <kozhukalov> thanks very much for this infromation
16:48:28 <mzawadzki> np
16:49:22 <kozhukalov> if there is nothing more, closing then
16:49:42 <kozhukalov> thanks everyone for attending
16:50:11 <kozhukalov> xarses: closing?
16:50:24 <xarses> thanks
16:50:27 <xarses> #endmeeting