13:00:15 <fdegir> #startmeeting Cross Community CI
13:00:15 <collabot_> Meeting started Wed May 30 13:00:15 2018 UTC.  The chair is fdegir. Information about MeetBot at http://wiki.debian.org/MeetBot.
13:00:15 <collabot_> Useful Commands: #action #agreed #help #info #idea #link #topic.
13:00:15 <collabot_> The meeting name has been set to 'cross_community_ci'
13:00:20 <fdegir> hello everyone!
13:00:29 <fdegir> #topic Rollcall
13:00:43 <electrocucaracha> #info Victor Morales
13:00:49 <fdegir> lets talk about what's been happening lately
13:01:06 <fdegir> first of all, apologies for missing the meeting last week
13:01:34 <jmorgan1> #info Jack Morgan
13:01:38 <fdegir> good morning electrocucaracha jmorgan1
13:01:47 <jmorgan1> good morning!
13:02:15 <electrocucaracha> fdegir: good morning
13:02:15 <hw_wutianwei_> #info Tianwei Wu
13:02:39 <fdegir> lets start and we ping others when their turn comes
13:02:43 <fdegir> #topic OpenCI Updates
13:03:04 <fdegir> #info OpenDev happened last week and I must say it was pretty successful
13:03:15 <fdegir> I don't know if jmorgan1 agrees to it
13:03:21 <hwoarang> #info Markos Chandras
13:03:36 <fdegir> there were lots of people and lots of things/discussions happening
13:03:45 <fdegir> and one of the topics was OpenCI
13:03:54 <jmorgan1> yes, it was successful - next level of detail discussions
13:03:56 <joekidder> #info Joe Kidder
13:04:15 <fdegir> #info You can see OpenCI slides we presented from the following link
13:04:16 <fdegir> #link https://docs.google.com/presentation/d/1ZdjatVB8nZbUf2GJsYRFbwm6BA3naELJhyajWkVdY-A/edit?usp=sharing
13:04:33 <mbuil> #info Manuel Buil
13:05:08 <fdegir> #info What we have been working on with XCI is recognized by many and XCI has pretty close relation to OpenCI with the ideas we have been talking about and things we have been doing
13:05:22 <fdegir> so I want to thank all of you for contributing to XCI
13:05:50 <fdegir> and we are really changing things
13:05:53 <tinatsou> #info Tina Tsou
13:05:56 <epalper> #info Periyasamy Palanisamy
13:05:56 <fdegir> I'm not exaggerating btw
13:06:36 <fdegir> #info During OpenDev joint conclusion session, many people asked about how they can continue collaborating in CI/CD area and there was no community to do that
13:07:11 <fdegir> #info OpenStack Foundation people pointed to OpenCI so OpenCI could become "the" community to collaborate in CI/CD further, increasing the scope of it - not just Cross Community CI/CD
13:07:23 <fdegir> we will see how successful it will be
13:07:36 <fdegir> and one last point regarding the event driven CI/CD stuff
13:08:08 <fdegir> #info The prototype between OpenDaylight, ONAP, and OPNFV was demostrated during OpenDev which enables Jenkinses to talk to each other using events
13:08:18 <fdegir> #info You can see the prototype jobs from the links below
13:08:29 <fdegir> #link https://jenkins.onap.org/view/openci/
13:08:45 <fdegir> #link https://jenkins.opendaylight.org/releng/view/openci/
13:08:57 <fdegir> #link https://build.opnfv.org/ci/view/OpenCI/
13:09:23 <fdegir> #info We are working on making prototype real and will start adding pieces to ODL and OPNFV Jenkins
13:09:33 <fdegir> any questions about OpenCI, prototype, etc.?
13:09:50 <mbuil> fdegir: how the jenkins systems were communicating? Did you use a specific MQ tool?
13:09:51 <jmorgan1> great job fdegir on demo
13:10:03 <fdegir> thx jmorgan1
13:10:08 <mbuil> yep, great job!
13:10:16 <fdegir> mbuil: as part of the prototype, we used Jenkins JMS Messaging Pluing
13:10:24 <mbuil> fdegir: ok :)
13:10:32 <fdegir> #link https://wiki.jenkins.io/display/JENKINS/JMS+Messaging+Plugin
13:10:33 <electrocucaracha> interesting
13:10:44 <fdegir> so, these jenkinses are not aware of existence of each other
13:11:03 <fdegir> they just broadcast events saying "I built ODL and it is good"
13:11:10 <fdegir> or "I built ONAP and it is good"
13:11:22 <fdegir> whoever is out there is subscribed to message broker, consuming those events
13:11:43 <fdegir> the most important thing about this prototype is to establish a common messaging spec across communities
13:11:56 <mbuil> right
13:12:14 <fdegir> so the things happening on CI/CD systems of various communities can be expressed using same messages
13:12:19 <fdegir> making them to talk each other
13:12:31 <fdegir> in summary, simple pubsub but with a well defined messaging spec
13:12:49 <fdegir> which we will need to work on to define together with all the communities whoa re involed in openci
13:13:04 <fdegir> CNCF is next in line, following OPNFV, ODL, and ONAP
13:13:26 <fdegir> so we can bring kubernetes in automatically with much less trouble
13:13:52 <fdegir> if there is no other question, moving to the next topic
13:14:03 <fdegir> which is
13:14:13 <fdegir> #topic PDF and IDF
13:14:26 <fdegir> mbuil: it is you
13:14:33 <fdegir> and perhaps hwoarang as well
13:15:06 <hwoarang> haven't done much. terribly busy with other things. mostly answering questions for mbuil
13:15:19 <fdegir> ;)
13:15:31 <mbuil> fdegir: The most part of the work is done and I have it working locally
13:15:50 <fdegir> mbuil: so, the vms can be created using pdf and then they can be provisioned?
13:16:04 <mbuil> fdegir: but I need to refactor things because I realized that there are a few ugly stuff which I think could be improved or I will received a lot of -1
13:16:13 <jmorgan1> this is a VM deployment? not baremetal?
13:16:59 <mbuil> fdegir: opnfv VM gets booted separately and provisioned. Then all the bifrost stuff (ironic, etc) runs from the opnfv VM and the rest of VMs get booted and provisioned from the opnfv vm
13:17:13 <mbuil> jmorgan1: still VM deployment. It is the first step for baremetal
13:17:21 <fdegir> mbuil: great - so we totally isolated ourselves from the host!
13:17:23 <jmorgan1> mbuil: ok, thanks
13:17:31 <fdegir> jmorgan1: it is more than just pdf actually
13:17:50 <fdegir> moving ourselves into a vm
13:18:06 <fdegir> realy dynamicity
13:18:11 <jmorgan1> cool
13:18:14 <fdegir> not sure if there is a word dynamicity...
13:18:32 <mbuil> apart from that I have been bugging hwoarang with a lot of stupid questions ;)
13:18:35 <fdegir> mbuil: you will remove WIP once you are ready with the stuff
13:18:43 <fdegir> mbuil: so we are not reviewing and -1ing it yet
13:18:55 <mbuil> fdegir: yes
13:18:57 <fdegir> ok
13:19:01 <fdegir> mbuil: anything else?
13:19:08 <mbuil> and it is not working in CI yet, I want to check what is going on
13:19:32 <mbuil> fdegir: no
13:19:34 <fdegir> that we can fix
13:19:38 <fdegir> thanks mbuil
13:19:46 <fdegir> #topic Baremetal
13:20:11 <fdegir> #info Work with baremetal will start once PDF, IDF work is done with VMs
13:20:19 <fdegir> mbuil: is this ^ a good summary/plan?
13:21:24 <mbuil> fdegir: yes, although my June looks already pretty busy ;)
13:21:56 <fdegir> mbuil: we believe in you
13:22:12 <fdegir> #topic SDF
13:22:21 <fdegir> hwoarang's RFC is up for review
13:22:32 <fdegir> #link https://gerrit.opnfv.org/gerrit/#/c/57679/
13:22:36 <fdegir> hwoarang: anything else to add?
13:22:58 <hwoarang> i will email the opnfv tech discuss ml later this week to seek feedback from installers
13:24:08 <fdegir> thx hwoarang
13:24:22 <fdegir> moving to the scenarios
13:24:24 <fdegir> and the first one is
13:24:26 <fdegir> #topic k8-nosdn-onap
13:24:31 <fdegir> electrocucaracha: jmorgan1: hello
13:25:12 <jmorgan1> im planning to work on it at the end of the week
13:25:19 <jmorgan1> with help from electrocucaracha
13:25:35 <jmorgan1> we need to get playbook from Orange folks as well
13:25:40 <jmorgan1> to work off of
13:26:08 <fdegir> jmorgan1: electrocucaracha: have you seen mail from Morgan?
13:26:17 <fdegir> he brought few topics up
13:26:23 <fdegir> and asked whether if you can make the meeting
13:26:50 <fdegir> moving on
13:26:53 <electrocucaracha> fdegir: that should be better
13:27:09 <fdegir> electrocucaracha: what?
13:27:19 <electrocucaracha> fdegir: having a meeting to discuss it
13:27:24 <fdegir> electrocucaracha: ok
13:27:25 <jmorgan1> fdegir: yeah, will schedule a meeting
13:27:38 <fdegir> jmorgan1: Morgan did that
13:27:49 <fdegir> i think onap should follow the practice set by ODL and provide the role
13:27:53 <fdegir> we shouldn't maintain it
13:28:04 <fdegir> we should just consume it like how we are doing with ODL one
13:28:17 <fdegir> #topic os-nosdn-onap
13:28:31 <fdegir> #info ONAP might drop Heat support and deployment on OpenStack
13:28:48 <fdegir> #info So we decided to park this scenario until we get clarification to what they will do
13:29:05 <fdegir> epalper: anything to add?
13:29:21 <epalper> yes fdegir, i have stopped working on it.
13:29:51 <fdegir> epalper: good because you have a new scenario now :)
13:29:54 <fdegir> #topic k8-odl-coe
13:29:57 <fdegir> epalper: ^
13:30:23 <epalper> yes, the spec is raised at https://gerrit.opnfv.org/gerrit/#/c/58021/
13:30:37 <epalper> now looking at the implementation details
13:30:40 <fdegir> #link https://gerrit.opnfv.org/gerrit/#/c/58021/
13:30:54 <fdegir> everyone, please review
13:31:06 <fdegir> epalper: can you continue bugging Prem so he reviews it as well?
13:31:21 <epalper> ok fdegir, i will do that
13:31:26 <fdegir> thx epalper
13:31:33 <fdegir> any update for any other scenarios?
13:32:08 <fdegir> hw_wutianwei_: do you think we have another k8s scenario we can bring in to?
13:33:08 <hw_wutianwei_> fdegir:  could we  deploy istio ?
13:33:15 <fdegir> hw_wutianwei_: I was just going to ask that :)
13:33:20 <fdegir> opened the webpage even
13:33:24 <fdegir> https://istio.io/docs/setup/kubernetes/
13:33:31 <fdegir> hw_wutianwei_: do you want to work on that?
13:33:43 <hw_wutianwei_> I can try
13:33:49 <fdegir> hw_wutianwei_: that would be great
13:33:57 <fdegir> I think onap will have it for the next release
13:34:14 <fdegir> so we can have some competence with it
13:34:21 <fdegir> electrocucaracha: do you know about this?
13:34:30 <fdegir> electrocucaracha: when they will have it in onap?
13:34:40 <electrocucaracha> yes, it's using service mesh pattern
13:34:59 <fdegir> ok
13:35:10 <fdegir> if anyone wants to help out with it, reach out to hw_wutianwei_ please
13:35:21 <electrocucaracha> I think that make sense to include it in onap, in that way the projects can share functionality and focus in their work
13:35:45 <mbuil> I saw that there was a presentation about openstack + istio during the summit
13:36:19 <fdegir> mbuil: ok - this needs to be added into the backlog as well then
13:36:37 <fdegir> electrocucaracha: hw_wutianwei_: so we can start with something like k8-nosdn-istio or whatever without onap
13:37:05 <electrocucaracha> fdegir: I'm not sure if that needs to consider as an additional scenario
13:37:07 <fdegir> and complicate it later on once we have k8-nosdn-onap scenario and we know what onap is going to do with istio better
13:37:34 <electrocucaracha> fdegir: more likely, it'll be another requirement for the deployment
13:38:12 <fdegir> electrocucaracha: so it makes even more sense to have a standalone scenario so we can switch onap from k8-nosdn-onap to k8-nosdn-istio_onap or whatever by reusing k8-nosdn-istio
13:38:32 <fdegir> but i think we are going into details now so if you are interested, please feel free to work on it together
13:39:01 <electrocucaracha> ok
13:39:09 <fdegir> moving to next topic
13:39:13 <fdegir> #topic OSA Shabump
13:39:21 <hwoarang> i did some investigation here.
13:39:30 * fdegir is listening eagerly
13:39:45 <hwoarang> the log_hosts thing can be fixed but a subsequent SHA bump for OSA to be able to handle the missing group
13:39:46 <hwoarang> or
13:39:53 <hwoarang> you need to add that group to all the scenarios yaml files
13:40:09 <hwoarang> because i know you add it in your review, but then all scenarios override that with their config files
13:40:13 <hwoarang> and they remove that group
13:40:27 <fdegir> but
13:40:28 <hwoarang> *"fixed by a subsequent"
13:40:41 <fdegir> i checked scenario openstack_user_config.yml files
13:40:55 <fdegir> and i thought whatever is not defined in them is brought in from the default one
13:41:32 <fdegir> hwoarang: so, should i just move to a later sha rather than trying to do what you suggest?
13:41:34 <hwoarang> so all scenarios have a openstack_user_config.yml file
13:41:42 <hwoarang> which they copy to /etc/openstack_deploy/
13:41:53 <hwoarang> effectively overwriting our own file
13:42:01 <hwoarang> and in their file log_hosts is commented out
13:42:25 <fdegir> so whatever we have in releng-xci/xci/installer/osa/files/<flavor>/openstack_user_config.yml is useless
13:42:25 <hwoarang> yeah using a more recent SHA for OSA should be better
13:42:32 <fdegir> should we just remove those files then?
13:42:33 <hwoarang> yes they are useless
13:42:35 <hwoarang> yes
13:42:39 <fdegir> ok
13:42:46 <fdegir> i'll attempt what you suggest
13:42:56 <fdegir> and will probably ask questions similar to mbuil's
13:42:58 <hwoarang> there should be a new tag this week i think
13:43:14 <fdegir> thanks for the pointer hwoarang
13:43:18 <fdegir> i'll keep an eye on osa repo
13:43:32 <hwoarang> any sha after May 17th should be ok
13:43:36 <fdegir> but also try some other sha locally and ci as well
13:43:42 <fdegir> will do that
13:44:11 <fdegir> #action fdegir to do what hwoarang suggests
13:44:23 <fdegir> #topic OpenStack Helm in XCI
13:44:38 <fdegir> so, I had a meeting with OpenStack Helm (OSH) team last week
13:44:47 <fdegir> they very much like to see OSH in XCI
13:44:57 <fdegir> which I passed the same requirements as we did for Kolla
13:45:24 <fdegir> if it happens, it might be logical to ask them to work with os-nosdn-nofeature
13:45:30 <fdegir> and os-tf-nofeature together with tf guys
13:45:42 <fdegir> mbuil: can you have a chat with tf guy next week and mention this?
13:46:22 <fdegir> #action mbuil to talk to tf guy and mention the possibility of osh appearing in xci
13:46:29 <fdegir> anyone has any questions about osh?
13:46:29 * electrocucaracha at least XCI arch is more decoupled
13:46:44 <fdegir> thanks to hwoarang
13:46:50 <electrocucaracha> 1
13:46:53 <electrocucaracha> +1
13:46:55 <fdegir> but i feel we will have some trouble when it comes to handling scenarios
13:46:56 <jmorgan1> great job hwoarang
13:47:31 <fdegir> like we need to have something like releng-xci-scenarios/scenarios/<installer>/role/<scenario> or something
13:47:44 <fdegir> assuming 2 or more installers supporting same scenario
13:47:49 <mbuil> fdegir: yes, I will. We will prefer OSH to Kolla because at least it seems like people will join to support OSH or?
13:48:01 <fdegir> mbuil: that is a possibility
13:48:32 <fdegir> mbuil: osh ptl was very eager to bring osh to xci
13:48:32 <mbuil> fdegir: I feel like the TF guys want one of them but not sure if they will maintain the XCI - Kolla/OSH integration
13:48:42 <fdegir> i said if you bring people, it lives
13:48:46 <fdegir> if not, we bury it together
13:48:57 <mbuil> all right
13:49:13 <fdegir> #topic Kubecon/CloudNativeCon NA
13:49:16 <hwoarang> good deal
13:49:20 <fdegir> thanks to whoever added the topic
13:49:23 <jmorgan1> me
13:49:34 <fdegir> #info The early registration ends tomorrow - May 31st
13:49:45 <fdegir> #link https://events.linuxfoundation.org/events/kubecon-cloudnativecon-north-america-2018/attend/register/
13:49:55 <fdegir> apart form it is being good to attend
13:50:04 <fdegir> there might be an openci workshop colocated with it
13:50:18 <fdegir> in case if people want to make a case to travel to kubecon
13:50:28 <fdegir> thx jmorgan1
13:50:37 <fdegir> #topic Kolla Support
13:50:40 <fdegir> any updates?
13:51:11 <electrocucaracha> I didn't see any other response from the mail that you included me
13:51:27 <jmorgan1> last time we spoke i think Orange team (?) was working on including it
13:51:49 <jmorgan1> we don't have xci person working on it, right?
13:52:00 <fdegir> as far as i know, we don't
13:52:09 <fdegir> but
13:52:16 <fdegir> isn't osh using kolla images?
13:52:42 <electrocucaracha> I think that they can use kolla or loci images
13:52:45 <fdegir> so we might benefit from kolla
13:52:55 <fdegir> will check
13:53:02 <electrocucaracha> https://github.com/openstack/loci
13:53:10 <fdegir> ok
13:53:17 <fdegir> electrocucaracha: jmorgan1: so if they support both
13:53:23 <fdegir> would you prefer to see kolla images?
13:54:03 <electrocucaracha> well, I haven't checked the process to create the loci images
13:54:15 <fdegir> ok
13:54:23 <electrocucaracha> In Kolla is possible to have better control over the HASHes
13:54:32 <fdegir> let's ask them when/if they join to a meeting coming weeks
13:54:40 <electrocucaracha> maybe it's something that LOCI didn't have
13:54:43 <fdegir> i'll create an etherpad and share with all of you as well
13:54:49 <fdegir> so we can add some questions
13:55:07 <jmorgan1> ok, lets add action item for etherpad
13:55:44 <fdegir> #link https://etherpad.opnfv.org/p/osh-in-xci
13:55:58 <fdegir> please add whatever you might want to ask
13:56:07 <fdegir> #topic AoB
13:56:16 <fdegir> anyone else wants to bring up a topic?
13:56:46 <fdegir> #action hw_wutianwei_ and electrocucaracha to look at bringing in istio into xci k8s scenario(s)
13:57:02 <fdegir> then we are done
13:57:06 <fdegir> thank you all for joining
13:57:11 <fdegir> talk to you next week!
13:57:14 <fdegir> #endmeeting