13:01:25 #startmeeting openstack-salt 13:01:26 Meeting started Tue May 31 13:01:25 2016 UTC and is due to finish in 60 minutes. The chair is cznewt. Information about MeetBot at http://wiki.debian.org/MeetBot. 13:01:27 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 13:01:30 The meeting name has been set to 'openstack_salt' 13:01:55 #topic roll call 13:02:07 o/ 13:02:58 o/ 13:03:36 hello genunix :) 13:03:49 welcome from cold toscany 13:04:37 Hello from Czech :-) 13:05:16 well, today it seems the attendance is small, so we'll make it quick 13:05:22 #topic introduction 13:05:34 This meeting is for the openstack-salt team 13:05:45 If you're interested in contributing to the discussion, please join #openstack-salt 13:05:50 Meetings are Weekly on Tuesdays at 1300UTC 13:05:55 #link http://eavesdrop.openstack.org/#OpenStack_Salt_Team_Meeting 13:06:01 #link https://wiki.openstack.org/wiki/Meetings/openstack-salt 13:06:21 #topic Review past action items 13:08:09 last time, the meeting was cancelled, but the issue discussed was alignment our work with salt stack community 13:08:55 if I may quote Thomas Hatch here: I don't think that we should look into merging these with our openstack states, yours are much more thought out and have had more time dedicated to being a unified design, so I would say to not try to merge. Your model looks very nice and is made in a highly reusable way, so I am all on board with saying that we over at Saltstack should look into updating how we push out openst 13:09:21 hello all 13:09:28 hello latecommer :) 13:10:11 I just posted thomas reply to the integration of formula ecosystem of openstack-salt 13:11:15 the resolution is: we will make the formulas compatible with the latest standards 13:11:29 to comply with SPM, it is matter of one file 13:12:08 and then we will propose a standard interoperability guidelines for advanced formula metadata 13:12:29 #action newt: make sure formulas are SPM compliant and registered 13:12:53 #action cznewt make sure formulas are SPM compliant and registered 13:13:37 #topic Today's Agenda 13:14:09 the saltstack based docker image creation 13:14:22 can genunix or jpavlik tell us more? 13:15:27 it's almost done :-) 13:15:43 #link https://github.com/tcpcloud/docker-salt 13:16:22 We've got images, jpavlik is now preparing docker-compose for simple dev setup and marco is working on Kubernetes setup. 13:16:42 yes, we are almost done. This approach can be used for CI as well. 13:17:38 will we keep the dockerfiles in separate repository? 13:17:58 or include it within the formulas? 13:18:50 I would keep it separate 13:19:21 actually dockerfile is still the same, just the service name differs, so I would maybe simply generate it. 13:19:40 docker compose is for docker-salt repository testing 13:19:41 yes, that is the most prefferable way 13:19:50 nothing more 13:20:21 docker-salt repo builds your containers by salt formulas and then you can launch them through one compose.yml 13:20:24 for testing 13:20:46 regardung this: are there any services to add to openstack repos? 13:20:46 target platform is still kubernetes 13:21:32 https://review.openstack.org/#/c/322000/ 13:21:37 every service has this 13:22:04 shall we place the kubernetes and swift repos under the openstack CI? 13:22:20 do we agree that we should? 13:22:26 yes 13:22:29 definatelly 13:22:34 kubernetes formula must out 13:22:37 as well as swift 13:23:11 #action cznewt add kubernetes and switf repos to opesntack-salt project repos 13:23:40 and what about docker-salt? 13:23:41 now the issue of salt documentation under docs.openstack.org 13:23:53 do you think that it can be usefull? 13:23:58 to put under openstak as well? 13:24:27 docker salt ... I'd put the scripts to openstack-salt repo and generate the dockerfiles 13:24:46 what does genunix think? 13:26:30 and there's one more repo that may be added under openstack and it is the metadata model containing repo with all possible deployment combinations 13:27:25 to test reviews for example, test all possible combinations of operating sysstem, openstack versions and networking and virtualization, etc ... 13:28:06 dunno 13:28:10 But I'm not sure, but it can stay on github 13:28:25 don't have an opinion yet :) 13:28:27 genunix: the last message goes to my previous messages 13:28:45 genunix: there are already several scripts 13:28:48 it could go to openstack-salt when finished 13:29:03 yes, I think it will be the best spot 13:29:06 I would wait before we are done 13:29:27 #agreed 13:29:29 from my point of view, it doesn't matter where the scripts lives now when is under heavy development 13:29:48 since stable release we can move it to the final location 13:29:50 yes, I see your point 13:30:01 hello majklk 13:30:10 hi bro 13:30:13 nice to see you 13:31:13 yes, miss you here 13:31:25 the docs.openstack.org, the documentation moving there, does anyone have time to look at it? I've made some progress but I'm stuck 13:31:58 if not, I'll have to push it 13:32:02 push it 13:32:08 it must be there 13:32:18 #action cznewt deploy the documentation to proper place 13:32:40 #action genunix finish the docker deployment scripts 13:33:02 I need to leave now 13:33:05 so thanks guys 13:33:45 bye jakob 13:35:26 we have made progress with deployments by heat and vagrant 13:35:59 it is under heavy finalisation 13:36:02 #link https://review.openstack.org/#/c/321260/ 13:36:41 good 13:37:22 it provides a way to test openstack-salt in any form, we need to get it documented thoroughly and prepare basic set of valid parameter combinations 13:37:56 we need to get it out for the community to test the review options 13:38:35 #action cznewt to document the changes to development deployments 13:39:10 this all from todays agenda 13:39:11 #topic Open Discussion 13:39:32 well we have 20 minutes to go 13:39:51 do you have anything more to discuss? 13:41:58 does anyone has anything else to say? [sounds like killbill quote :)] 13:45:23 well, I'll end the meeting then a little earlier, as I have a pressing issue to attend 13:45:37 thanks all 13:45:46 #endmeeting