16:02:12 #startmeeting openstack_salt 16:02:13 Meeting started Tue Feb 9 16:02:12 2016 UTC and is due to finish in 60 minutes. The chair is jasondotstar. Information about MeetBot at http://wiki.debian.org/MeetBot. 16:02:14 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 16:02:16 The meeting name has been set to 'openstack_salt' 16:02:23 #topic roll call 16:02:26 o/ 16:02:29 o/ 16:03:00 hi cznewt 16:03:18 hello jasondotstar 16:03:26 #topic Introduction 16:03:48 this is the meeting for the openstack-salt team 16:03:56 If you're interested in contributing to the discussion, please join #openstack-salt 16:04:09 #link http://eavesdrop.openstack.org/#OpenStack_Salt_Team_Meeting 16:04:12 o/ 16:04:22 #link https://wiki.openstack.org/wiki/Meetings/openstack-salt 16:04:27 hello geneneric unix unit 16:04:33 hi genunix 16:04:38 :-) Hello 16:04:46 #topic Review past action items 16:05:11 genunix to research how to openstack packaging works 16:05:18 any status? 16:07:02 jasondotstar: not much. I have read some docs but didn't find much useful things, it's not much unified. 16:07:15 very well, we're carry it over 16:07:23 So current conclusion is - try to contact some openstack package maintainer 16:07:34 and ask about how to get our formulas to Debian 16:07:50 #action genunix to continue openstack packaging research 16:08:06 next: jasondotstar to look at the integration of launchpad with our repos 16:08:23 not much movement here either. I'll need to move this one fwd :-( 16:08:37 yes integration with launchpad bugs is iportant to set 16:08:49 so we can keep track of upcoming development 16:09:04 #action jasondotstar to look at the integration of launchpad with our repos (bug triage, tracking, etc.) *important* 16:09:05 as there are already some areas to tackle [vanilla neutron] 16:09:14 +1 16:09:17 +1 16:09:35 ok next one: 16:09:46 jasondotstar to look into dev environment sponsorship 16:09:54 so we were just talking about this 16:09:57 from my understanding 16:10:08 this request is to have a cloud-based dev environment 16:10:26 for functionally testing the services that our salt formulas will deploy 16:10:27 yes, the heat-based both single / cluster deployments 16:10:42 +1 16:10:45 of openstack control clusters + few computes to test 16:10:53 this is beyond the local dev environment 16:11:01 i posed a question to the -infra team 16:11:07 and they made a couple suggestions 16:11:11 1- use trystack 16:11:32 the only problem with trystack is the resources terminate after 24 hours 16:12:17 We can setup more permament labs at tcpcloud 16:12:21 i don't know if we can rely on an environment like that in sustenance 16:12:32 +1 16:12:38 it's possible to run up to 10 labs at once 16:12:51 the other option is to use an employer based environment 16:13:03 so yes, we may have to rely on tcpcloud 16:13:22 the other thing we need to eventually thing about is gating 16:13:30 there can be more lab environments to test 16:13:34 beyond linting 16:14:20 example: puppet uses the beaker gate, to functionally test the service deployed with puppet by launching a couple VMs (one debian based, one rpm based) 16:14:22 yes I'd like that as well 16:14:24 to ensure the service works 16:14:45 yes exactly system testing is missing in out setup now 16:14:52 to automate this is +2 for me 16:14:55 right 16:15:19 #agreed functional testing like beaker is required to achieve gating beyond linting 16:15:32 I can look at beaker gates and how to get it into salt world 16:16:11 #action cznewt to look at beaker gates and how to fold into the salt workflow 16:16:45 #action cznewt to look at beaker gates and how to fold a similar process into the salt workflow 16:17:02 any other thoughts on this 16:17:03 ? 16:17:17 not to this topis 16:17:19 ok 16:17:21 *topic 16:17:23 another issue is the documentation, it is not 16:17:47 building for some time, but we are working on fixing it 16:18:01 as it moved to the openstack namespace 16:18:30 question off topic: if you abandon change in gerrit, can you revert this? 16:19:05 yes 16:19:07 yes 16:19:23 I have much to learn :) 16:20:19 newt test the aio/ha openstack-salt heat setup 16:20:19 the other issue is to try access to development environemnts from various platforms [ie mac] 16:20:53 'access to dev environments' <- what do you mean? 16:21:05 the heat clients, the vagrant installs 16:21:29 it is working on linux 16:21:53 but we need to test it works on win/mac as well 16:21:57 ah 16:22:06 it should :) 16:22:11 windows I can see us working on - mac i'm not sure 16:22:24 you have mac, right? 16:22:33 are we talking local dev 16:22:47 or a managed cloud enviroment (i.e. lab) 16:22:48 ? 16:22:59 local for vagrant, remote for heat, but you still have your laptop as heat client 16:23:10 oh i c. 16:23:41 i'd prefer we can support both cases, but i'd primarily focus on cloud based deploys 16:23:52 jasondotstar: what do you think? 16:24:23 as the vagrant is limited by local resources 16:24:48 perhaps we can take a look at having mac-based heat clients, but i think it's more important to concentrate on fully standing up the services on linux #1, windows #2 16:25:35 +1 16:26:30 I can test the linux client side, do you have anyone around with M$ win who is willing to test? 16:27:11 not right off 16:27:15 something to think about 16:27:25 well we need some viretual windows then :) 16:27:43 and that's somethin we have in saltstack-training lab :) 16:27:51 #action consider testing deployments to windows-based clients 16:29:27 ok 16:29:33 #action cznewt get the first cloud based labs for openstack-salt testing fully operational 16:29:45 i think we can move on, we can chat more about this in chan. 16:30:00 #topic Today's Agenda 16:30:21 yes, the salt community 16:30:29 Salt community involve, no response: https://groups.google.com/forum/#!topic/salt-users/v3PQDfRgtmk 16:30:47 cznewt: yes, thanks for engaging the salt community on this topic 16:31:30 do we anticipate a response soon? 16:31:59 I have contant to Nitin Madhok who is saltstack merger 16:32:35 we met in Tokio and discussed for a while, I'll let him know of our endeavour and ask him for participation as well 16:33:08 he can probably help us to the right path 16:33:15 cznewt: interesting. i did the same :-) 16:33:21 cznewt: a few weeks ago 16:33:32 but that was before we combined our efforts 16:33:54 cool. we'll see if he can help 16:33:55 well I typed him in December and did not get any reply 16:34:08 cznewt: same here. I've yet to hear back from him 16:34:08 but it is different topics now 16:34:12 right 16:35:23 #action continue to engage the salt community regarding our standardizing dependencies, packaging, versioning, and testing 16:35:54 i've yet to finish my dev environment setup :-( 16:36:00 I'm going to clear my plate today 16:36:03 and work on this. 16:36:25 yes, I'd love that and to assist 16:36:37 #action jasondotstar to complete local dev testing setup 16:36:47 cznewt: +1 16:37:00 whatever issues comes, exept weird ruby/vagrant errors 16:37:16 that were tricky :) 16:37:18 hehehe 16:37:20 yeah 16:37:27 i got a couple weird ones 16:37:44 but I'll keep pushing on it. 16:37:48 ok, any other pressing topics? 16:38:04 if not, i wanted to bring up the question that's being asked right now in -infra 16:38:05 I think we went over all pressing topics for now 16:38:18 cool. 16:38:25 so did you see the qn in -infra 16:38:37 regarding the stackforge/salt projects? 16:40:39 basically the issue is we have the new projects 16:40:49 that are under the openstack/ namespace 16:40:56 and there are existing salt projects 16:41:03 under the stackforge/ namespace 16:41:07 I looked these 16:41:14 i.e, we have stackforge/nova-salt-formula and openstack/salt-formula-nova 16:41:29 cznewt: what did you make if these? I've not looked at them 16:41:35 *of 16:41:40 and they don't look good at all 16:41:48 more like empty shells 16:41:50 ok 16:42:04 so the stackforge/ ones are outated 16:42:04 for example look at this https://github.com/stackforge/neutron-salt-formula/commits/master 16:42:20 right nothing there. 16:42:26 so we need to prune these 16:42:29 and they have 'We are retired' in the README 16:42:40 +1 16:42:41 yes, obsolete stugg 16:42:42 i see that 16:42:44 yes, obsolete stuff 16:42:55 ok so, I can work on pruning these 16:43:16 #action jasondotstar to work on pruning the salt formula projects underneath the stackforge/ namespace 16:43:56 i told them that the ones we're migrating from the tcpcloud github repo(s) are house the updated code. 16:44:05 s/are// 16:45:12 yes, thanks, the more interesting will be merging with official salt formulas, as the metadata approach varies a little 16:47:54 +1 16:48:02 ok any other items 16:48:03 ? 16:48:12 we'll topic switch 16:48:18 #topic Open Discussion 16:50:37 I needed some time to reply to the infra guys 16:50:43 cznewt: yeah 16:51:39 i think we'll end up getting rid of those repos, but we'll see. 16:52:04 ok if nothing else we can give the chan 10 mins back 16:52:10 anything else? 16:52:31 if not, thanks again team. we'll talk in channel. 16:52:38 cznewt: thx 16:52:54 genunix: thx 16:52:58 clarkb: thx 16:53:03 #endmeeting