14:01:02 #startmeeting OpenStack 3rd Party CI 14:01:02 Meeting started Wed Aug 31 14:01:02 2016 UTC. The chair is fdegir. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:01:02 Useful Commands: #action #agreed #help #info #idea #link #topic. 14:01:02 The meeting name has been set to 'openstack_3rd_party_ci' 14:01:18 #chair jmorgan1 Julien-zte hwoarang 14:01:18 Current chairs: Julien-zte fdegir hwoarang jmorgan1 14:01:27 #topic Roll Call 14:01:32 #info Julien 14:01:36 #info Chris Price 14:01:42 #chair ChrisPriceAB 14:01:42 Current chairs: ChrisPriceAB Julien-zte fdegir hwoarang jmorgan1 14:01:47 noooooo 14:01:49 :) 14:01:50 #info Markos 14:01:50 :) 14:01:56 #info Jack Morgan 14:01:56 I'm new in this so... 14:02:13 Yolanda is off this week so we can start 14:02:18 here is the agenda 14:02:19 #topic Agenda 14:02:19 ok 14:02:24 #info Welcome 14:02:28 #info Background Info 14:02:32 #info Progress: bifrost 14:02:38 #info Progress: puppet-infracloud 14:02:41 #info Infra/HW Needs 14:02:45 #info AOB 14:02:50 #link http://docs.openstack.org/developer/bifrost/readme.html 14:03:03 if anyone wants to add anything to the agenda, please feel free to do so 14:03:05 #link https://wiki.opnfv.org/display/INF/OpenStack+3rd+Party+CI 14:03:12 Julien-zte: thx 14:03:15 #topic Welcome 14:03:29 #info I want to welcome everyone and thanks for joining this effort! 14:03:46 and I'm really happy to see we have made a direct impact 14:03:49 :) 14:04:04 there have been some contributions to upstream already 14:04:13 thanks fgedir, great job has been done 14:04:14 which I'll paste the link when the topic comes there 14:04:29 this is really encouriging 14:04:42 so, thx again and ChrisPriceAB expects more! 14:04:50 #topic Background Info 14:05:04 #info There might be questions regarding why we are working on this 14:05:25 #info We tried to give a summary regarding this activity on Wiki so please feel free to read, comment, update 14:05:35 #link https://wiki.opnfv.org/display/INF/OpenStack+3rd+Party+CI 14:05:56 #info The primary tools we are looking into are bifrost and puppet-infracloud 14:06:00 #link https://github.com/openstack/bifrost 14:06:04 #link http://git.openstack.org/cgit/openstack-infra/puppet-infracloud 14:06:31 and we can move to real stuff now... 14:06:41 #topic Progress: bifrost 14:07:01 #info We have been evaluating/trying out bifrost and fixing what we think could be fixed/improved 14:07:25 #info Yolanda and Markos have been pretty active with locating and fixing nasty bugs 14:07:34 the rabbitmq stuff for example 14:07:54 #info the objective of this activity is to make sure we can use bifrost to deploy an OPNFV scenario on a "pharos" lab 14:08:22 #info using openstack native CI tools 14:08:34 and from master! 14:08:46 ack 14:08:51 who likes months old sw 14:09:17 yes, from the master branch 14:09:32 good point 14:09:43 #info We can now provision 3 VMs using bifrost 14:09:57 #info Ubuntu as OS and the 3 VMs serve as jumphost, controller, and compute 14:10:06 I have not finished this yet :( 14:10:08 #info Work to introduce Centos and SuSe support is ongoing 14:10:22 hwoarang: would you like to add anything regarding SuSe support 14:10:26 which SuSE versions? 14:10:31 hwoarang: or any other item? 14:10:57 fdegir: it's still work in progress. we are missing the ipxe package which i need to work on. but it's pretty close after that 14:11:05 many a newest LTS version 14:11:13 jmorgan1: openSUSE Tumbleweed at first. then Leap. then SLES 14:11:23 many: maybe 14:11:26 #info Introducing SuSe support is work in progress. we are missing the ipxe package which i need to work on. but it's pretty close after that 14:11:38 #info openSUSE Tumbleweed at first. then Leap. then SLES 14:11:39 hwoarang: ok 14:12:23 #info The work we've done with bifrost is put on OPNFV Jenkins and we are provisioning VMs over and over automatically 14:12:29 #link https://build.opnfv.org/ci/job/infra-provision-virtual-daily-master/lastBuild/consoleFull 14:12:39 my question about bifrost is time cost to run once. 14:12:47 if anyone wants to try stuff, you can take a look at the script from releng repo 14:12:53 do we have some time estimation? 14:13:21 Julien-zte: you mean how much time it takes to provision? 14:13:25 yes 14:13:38 Julien-zte: https://build.opnfv.org/ci/job/infra-provision-virtual-daily-master/buildTimeTrend 14:13:47 but the about 45 minutes 14:13:51 but please note that 14:13:59 the time you see is everything from scratch 14:14:09 installation of complete toolchain (ansible and whatnot) 14:14:13 building diskimages 14:14:17 and so on 14:14:36 and when we do this for real, we will probably skip these and cut the time 14:14:37 good for in a hour 14:14:58 I expect 30 minutes or less for provisioning VMs 14:15:08 baremetal will probably differ 14:15:50 #info This is the script that is run by Jenkins 14:15:52 #link https://gerrit.opnfv.org/gerrit/gitweb?p=releng.git;a=blob;f=jjb/infra/infra-provision.sh 14:16:29 thanks fdegir, will check for this 14:16:31 anyone has any questions or comments regarding bifrost? 14:16:38 or wants to add anything? 14:17:06 I take this as no 14:17:17 for now, just some time issues 14:17:19 some tiny issues 14:17:32 Julien-zte: you now where we live :) 14:17:36 know^ 14:17:53 the other thing I want to highlight is our contributions to OpenStack 14:18:02 people generally talk about features to openstack 14:18:12 but I believe contributions to infra is important 14:18:31 so I will monitor and collect the contributions and link them here 14:18:46 #info bifrost contributions since 2016-06-01 14:18:47 agree, openstack infra has been evoluting, no stop 14:18:47 #link http://bit.ly/2c4tgC7 14:19:17 moving on to puppet-infracloud 14:19:31 #topic Progress: puppet-infracloud 14:19:40 the story is similar for puppet-infracloud as well 14:19:44 #info We have been evaluating/trying out bifrost and fixing what we think could be fixed 14:19:48 #undo 14:19:48 Removing item from minutes: 14:19:56 #info We have been evaluating/trying out puppet-infracloud and fixing what we think could be fixed 14:20:23 #info The main pain with the puppet-infracloud is that the scripts they have for trying stuff have many hardcoded values in them 14:20:44 #info Yolanda spent quite some time to get rid of them to make it work for OPNFV 14:21:20 #info Based on her work, we can now install OpenStack on 2 node setup from stable/mitaka on Ubuntu 14:21:43 this is all manual (via script) right? 14:21:50 it's great 14:22:07 jmorgan1: the provisining using bifrost part is via script/totally automated 14:22:16 jmorgan1: but OpenStack installation lacks the full automation 14:22:45 jmorgan1: I can perhaps info this in 14:22:54 ok, thanks 14:23:09 #info Putting bifrost and puppet-infracloud together: How to provision VMs and install openstack 14:23:37 #info Provision VMs using bifrost (via script: https://gerrit.opnfv.org/gerrit/gitweb?p=releng.git;a=blob;f=jjb/infra/infra-provision.sh) 14:23:54 #info Once the 3 VMs are provisioned, login to controller and do puppet apply 14:24:02 #info And then to compute and do puppet apply 14:24:05 is this what openstack upstream does? 14:24:17 hwoarang: yes 14:24:20 ok 14:24:27 hwoarang: or at least how they explain it in their examples 14:24:40 hwoarang: they probably have more automation but we haven't come that far yet 14:25:03 right 14:25:11 they call this like "ansible driving puppet driving ansible" 14:25:14 or vice versa 14:25:25 it's certainly not pretty :) 14:25:42 I see you make things pretty pretty 14:25:45 so :) 14:26:00 #info Once puppet apply is done on controller and compute 14:26:10 #info The installation can be verified from jumphost 14:26:30 #info The puppet-infracloud process for OPNFV has been documented on Gerrit Releng 14:27:08 #link https://gerrit.opnfv.org/gerrit/gitweb?p=releng.git;a=blob;f=prototypes/puppet-infracloud/README.md 14:27:22 there is a problem there which I intend to send a patch for 14:27:29 but if anyone does not want to wait 14:28:07 #info Fix puppet apply --manifests/site.pp --modulepath=/etc/puppet/modules:/opt/releng/prototypes/puppet-infracloud/modules 14:28:14 #info puppet apply manifests/site.pp --modulepath=/etc/puppet/modules:/opt/releng/prototypes/puppet-infracloud/modules 14:28:39 so we have this part also almost working but automation is missing 14:28:55 need to do some ansible stuff to automate puppet apply and then smoke test 14:29:12 anyone has anything to add? 14:29:19 or have you reached to this point? 14:29:26 i haven't 14:29:41 just something strange for ansible + puppet :) 14:30:03 :) 14:30:30 shall we considering container openstack deployment? 14:30:38 one thing to add, if you create servers on this deployment using cirros, you might experience issues 14:30:47 Julien-zte: maybe in 2018 :) 14:31:06 fdegir: what kind of issues? 14:31:11 Julien-zte: jokes aside, if we stay aligned with the upstream 14:31:21 Julien-zte: and if they do stuff with kolla or whatever 14:31:27 Julien-zte: we should be able to consume that as well 14:31:32 (they=openstack infra) 14:31:45 hwoarang: you can't ping or ssh to those cirros vms 14:31:59 hwoarang: according to Yolanda, xenial works fine 14:32:00 if Kolla team can contribute it will be better 14:32:10 after adjusting security groups 14:32:19 i see 14:32:32 I tried but failed, probably wrong settings with security groups 14:32:42 Julien-zte: +1 14:33:09 in the list you provided, some of issues we found have been resolved! good work! 14:33:22 #info I did the same thing with puppet-infracloud and here is the link to contributions since 2016-06-01 14:33:30 #link http://bit.ly/2bRJWQ5 14:33:51 #info Some might not be for OPNFV so it is up to you to read them 14:34:04 we perhaps need to agree on how to track our contributions to OpenStack Infra as well 14:34:19 ChrisPriceAB: any hints? 14:34:58 one thing to do ouwld be to gat the commit with "opnfv" or something 14:35:11 fdegir: should we get invloved with OpenStack Infra? 14:35:24 jmorgan1: we're already involved in 14:35:33 maybe "releng" or something you specifically want to use. we can then track directly back to this initiative. 14:35:36 too much project in openstack infra 14:35:50 jmorgan1: Yolanda is core in puppet-infracloud I think 14:35:57 and some more perhaps 14:36:29 ChrisPriceAB: we can check with Yolanda to see how would they react if we put opnfv into our commit messages 14:36:35 or how else we can track them 14:36:59 so, this is all good and we have some progress definitely 14:37:07 but we want to go to baremetal obviously 14:37:07 I suggest something for releng specifically. then you can map it back directly. But yeah ask Yolanda how best to do it 14:37:11 fdegir, can the search string support in" commit message" 14:37:26 ChrisPriceAB: will do, thx 14:37:49 #info We started with VMs since it is easier to work with them - at least for me personally 14:37:53 in the cli, I can not implement this requirement. if supported, we can add opnfv community in the commit message 14:37:59 #info But we will soon go to baremetal 14:38:14 #info As noted above, we currently deploy stable/mitaka on Ubuntu 14:38:36 #info Once the Centos support is introduced and we can deploy from latest, work to deploy on baremetal will start 14:38:46 in a week or two 14:39:11 and the aim is to have this up and running on OPNFV Jenkins/Pharos by OpenStack Summit 14:39:53 afterwards, the tricky parts will come in; HA support and OPNFV Networking 14:40:22 But once you get that far you can enable the community to do that part 14:40:39 ChrisPriceAB: yep 14:40:48 I think OpenStack Infra is following what we are doing 14:40:57 they mentioned this during their Infra Meeting last week 14:41:06 and they were happy to have customers :) 14:41:14 how can we help out? 14:41:34 test the code in releng.git? 14:41:43 other? 14:41:48 jmorgan1: https://wiki.opnfv.org/display/INF/OpenStack+3rd+Party+CI#OpenStack3rdPartyCI-HighLevelPlan 14:41:56 that's a very high level plan 14:42:10 and we are on step 1.2 14:42:22 and had like 10+ fixes in upstream just for these small steps 14:42:34 my suggestion would be to start playing with bifrost and puppet-infracloud 14:42:48 maybe more in the later 14:42:49 and get things work - either yourself or using the scripts we have in releng repo 14:42:59 i have more hardware resources, i'll start taking a look 14:43:06 once everyone is comfortable with these tools 14:43:15 we can have better planning and work distribution 14:43:33 but until that happens, it is kind of get something work some way 14:43:41 +1 14:43:47 who will be at openstack summit? 14:43:58 I plan to go 14:44:02 me as well 14:44:03 i may be 14:44:07 me 14:44:11 Yolanda will be there too 14:44:13 and Aric 14:44:21 i'm tbd at the moment 14:44:30 and we want to sit down with the OpenStack Infra guys 14:44:38 and it is important to have real stuff to talk about 14:44:42 rather than wiki pages or slides 14:44:43 right 14:44:48 I'll buy you a cervesa if you show up jack 14:45:04 I'll forget about the etherpad if you show up jack 14:45:10 lol 14:45:28 last topic of the day 14:45:34 #topic Infra/HW Needs for OpenStack 3rd Party CI 14:46:00 #info Our aim is not to fork anything but certain things can't be upstreamed either 14:46:10 #info So we decided to keep them in OPNFV releng repo 14:46:33 #info And have a basic flow regarding how to combine upstream with releng: cp -R 14:46:42 #link https://gerrit.opnfv.org/gerrit/gitweb?p=releng.git;a=tree;f=prototypes 14:46:56 #info As you see, we have 2 folders there; bifrost and puppet-infracloud 14:47:17 hope remaining in releng is the use case, and most of them will be upstreamed 14:47:19 #info Each of these directories follow same directory structure as upstream so we can add new files or overwrite existing files as needed 14:47:36 #info does that process allow OPNFV projects to add things easily? Can SDNVPN for instance add ODL with a specific config? 14:47:54 #info is that a TBD item, or do they create a structue in their repo? 14:47:55 ChrisPriceAB: this is pretty basic at the moment 14:48:10 #info TBD item 14:48:15 ok cool 14:48:32 #info The current structure just allows us to move on with not much hassles 14:48:43 :D sounds wise 14:48:46 #info But needs to be improved definitely when things become serious 14:48:54 with some help from git gurus in community 14:49:13 #info We also have some hardware to use for development work 14:49:34 #info We currently have 4 machines in Intel POD4 to use for development purposes using VMs 14:49:55 #info hwoarang submitted a jira ticket to Pharos/Jack to get access to Intel POD4 and he will get pod4-node2 14:50:07 I have blades in ZTE for development 14:50:08 #info Yolanda uses pod4-jumphost and me pod4-node1 14:50:17 Julien-zte: ping us when you need machine 14:50:28 OK 14:50:29 well, i'd like to join releng project offically then 14:50:43 #info We also will hopefully get a full POD for development on baremetal 14:51:03 #info LF POD4 or POD5 - to be discussed during Infra WG meeting after this one 14:51:06 i'll have more hardware resources in Intel lab after lab move (post colorado 1.0 release) 14:51:12 jmorgan1: you are already part of releng 14:51:40 jmorgan1: if you contribute, you can perhaps become a committer one day 14:51:48 starting with etherpad perhaps :P 14:51:48 fdegir: ok, got it 14:51:49 :) 14:52:05 #topic AoB 14:52:14 anyone wants to say anything? 14:52:16 ask anything? 14:52:20 plans for etherpad training? 14:52:21 complain about stuff? 14:52:35 I think we have some material on wiki 14:52:39 I will ask for help when some issue can not be resolved 14:52:40 for etherpad usage 14:52:59 what training do you need for etherpad? 14:53:00 Can I complain about the infra WG meeting here? 14:53:04 create page, edit ;) 14:53:06 I'm working on ipxe 14:53:16 ChrisPriceAB: off topic ;) 14:53:17 ChrisPriceAB: nope 14:53:36 ChrisPriceAB: I'm the complainer 14:53:53 anyway, this looks like a lot of fun and i'm excited to work on it 14:54:03 thanks for driving it fdegir 14:54:06 #info Finally, I want to thank everyone again to see this happening! 14:54:07 I need training for everything. 14:54:32 thank you fdegir 14:54:34 thanks fdegir 14:54:37 thanks for the day and talk to you all in 5 minutes 14:54:39 ChrisPriceAB, agree 14:54:41 #endmeeting