14:12:12 <[1]JonasB> #startmeeting Weekly fuel sync
14:12:12 <collabot> Meeting started Thu Sep 10 14:12:12 2015 UTC.  The chair is [1]JonasB. Information about MeetBot at http://wiki.debian.org/MeetBot.
14:12:12 <collabot> Useful Commands: #action #agreed #help #info #idea #link #topic.
14:12:12 <collabot> The meeting name has been set to 'weekly_fuel_sync'
14:12:15 <[1]JonasB> #info Jonas Bjurel
14:12:19 <s_berg> #info Stefan Berg
14:12:40 <[1]JonasB> Lets start with SR1
14:12:46 <[1]JonasB> #topic SR1
14:12:52 <bryan_att> trozet: only after verification that we can install them
14:12:55 <szilard> #info Szilard Cserey
14:12:58 <[1]JonasB> What is left to do?
14:13:27 <mskalski> #info debugging problem with starting OpenDaylight controller inside juno/lithium plugin - which we want to use in SR1
14:13:27 <bryan_att> trozet: then that's easy but also in Fuel?
14:13:28 <szilard> I have to test the ODL plugin that Michal provided
14:13:34 <s_berg> #info Fuel 6.1 rebase in build system is done but needs testing - https://gerrit.opnfv.org/gerrit/#/c/1462/
14:13:43 <mskalski> #info When odl start it hang on some moment, ovsdb feature is not initiated. Strange is that it happen on Montreal lab but can't reproduce this on my local labs.
14:13:55 * bryan_att (sorry - I'll postpone the conversation)
14:13:56 <trozet> bryan_att: lets talk in private chat as they are having their meeting
14:14:00 <szilard> #info I have to test the ODL plugin that Michal provided, if problems still happenning then find another workaround
14:14:02 <mskalski> #info I send today Szilard version of the plugin which will restart ODL near to the moment when we observe hang. Maybe this ugly workaround will work.
14:14:57 <[1]JonasB> Good, lets hope
14:15:27 <bryan_att> [1]JonasB: when you get to a point in your meeting, i need to know what OS and ODL features were installed by Fuel in Arno, and where in the git tree are the files I will need to modify for R2 new features so I can provide requirements to Genesis
14:15:40 <[1]JonasB> #info We would preferably want to be able to deploy without Internet access.
14:16:28 <[1]JonasB> bryan_att: When we come to B-release, OK?
14:16:40 <bryan_att> ok
14:16:42 <ruijing> Agree with JonasB that we can deploy without internet access
14:17:11 <[1]JonasB> #info Michal is looking into how to carry the repos on the fuel iso or in a plugin.
14:17:26 <[1]JonasB> mskalski: Did I get it right?
14:18:12 <mskalski> [1]JonasB: yes, but not like this approach ;), would rather use local mirros
14:18:50 <[1]JonasB> mskalski. You mean to have local mirrors on the build machine or similar?
14:19:25 <mskalski> [1]JonasB: yes somewhere in env where we deploy fuel and not have access to internet
14:20:14 <s_berg> I see your point mskalski, and for instance in OPNFV lab this could easily be the jumphost for instance.
14:21:04 <s_berg> But somehow I think that many deployments will be done in isolated labs where firewalls and other restrictions will be in place, and having a "one stop shop" in the form of one ISO would simplify a lot.
14:21:33 <s_berg> (or one ISO and one - huge - plugin) :)
14:22:03 <[1]JonasB> mskalski: I dont think we will be in control of the env we deploy on, and I would want us to aske users to set-up a local mirror them selves
14:22:19 <mskalski> s_berg: yes I understand  I will investigate how we distribute this packages
14:22:27 <mskalski> *can
14:22:49 <s_berg> Or another wild and crazy idea - an automagical additional ISO that will install a web server and necessary repos onto a machine ones booted...?
14:23:02 <s_berg> *once
14:23:23 <[1]JonasB> s_berg: That could work
14:23:35 <s_berg> The neat thing about that is that we could dockerize that on for instance a jumphost, less messy and more repeatable.
14:23:39 <mskalski> [1]JonasB: yes we don't but this is how it is supported in fuel, other solution will be our custom approaches
14:24:10 <[1]JonasB> mskalsk: I understand
14:25:57 <[1]JonasB> Should we try to go for s_berg's proposal, an install script that sets up a local mirror in a container working for both Ubunto and Centos?
14:26:53 <s_berg> Shouldn't be too much work really, basically setting up Apache and then running the already provided mirror cloning tool that's on the ISO...
14:27:17 <mskalski> but if this script will be run inside env where we can't reach external repo how we download packages?
14:27:19 <s_berg> So would the deliverable be a pre-built docker container just to import?
14:28:03 <[1]JonasB> mskalski: Packages would need to be provided with the script I guess
14:28:04 <s_berg> mskalski: No, we must build and provide the container.
14:28:46 <mskalski> s_berg: ok, this would be a part of ISO?
14:28:48 <s_berg> mskalski: I agree, otherwise we're in a catch 22. So one additional artifact that is built cyclically (to have the repos up-to-date) which packages Apache + repo content.
14:29:26 <s_berg> I'd vote for having it in a separate ISO images, striving for the Fuel ISO to be as close to pristine as possible (with the possibility of some hooks and other necessities).
14:30:51 <[1]JonasB> mskalski, s_berg: Could you two look into this off-line?
14:31:13 <s_berg> Sure. The actual work should be quite small I'd guess.
14:31:57 <[1]JonasB> #info Stefan Berg and Michal Skalski will work on a solution for a local packet mirror
14:32:33 <[1]JonasB> Szilard, what do you have in the backlog for SR1?
14:32:56 <szilard> cleanup script
14:33:03 <szilard> virtual environment
14:33:08 <szilard> documentation
14:33:36 <[1]JonasB> szilard: Sounds doable for Sep 28 -right?
14:33:37 <ruijing> what tool to track backlog?
14:33:46 <szilard> jira
14:33:50 <[1]JonasB> ruijing: Jira
14:33:59 <[1]JonasB> jira.opnfv.org
14:33:59 <szilard> rebasing
14:34:15 <szilard> basically it's all done, now we have to make ODL start correctly
14:34:40 <[1]JonasB> szilard: Coll - well doner.
14:35:04 <[1]JonasB> #info deploy tool-chain is on track for SR1
14:35:28 <szilard> I will try to test on LF POD2
14:36:03 <szilard> will have to find the right time slot
14:36:18 <[1]JonasB> s_berg: build rebasing?
14:36:18 <szilard> so that I don't clash with Foreman deployment
14:37:25 <s_berg> I won't feel comfortable merging until I know that it's been through h*ll, or at least some constructive CI testing :) so I'd urge people to throw some test cases against an ISO built with https://gerrit.opnfv.org/gerrit/#/c/1462/1
14:38:15 <Jonas2> s_berg: I will start cyclic tests of that patch-set.
14:38:48 * s_berg is confused by the number of Jonases
14:38:55 <szilard> :)
14:38:56 <Jonas2> #info Build-rebas patch committed, we will run some more tests before merging it.
14:39:01 <s_berg> That's great.
14:39:33 <Jonas2> Anything more I forgot for SR1?
14:39:57 <s_berg> The necessity of doing NTP and DNS plugins? I haven't looked into this yet.
14:40:22 <Jonas2> michal: How does dns and ntp look like in 6.1?
14:40:31 <s_berg> Working on the assumption that we're good with the 6.1 base functionality until CI proves me wrong.
14:40:40 <mskalski> s_berg: but in 6.1 you can configure DNS servers and NTP fo slave
14:41:24 <Jonas2> mskalski: Where is the ntp/dns server - on the controllers?
14:41:52 <mskalski> Jonas2: I mean addresses of dns/ntp servers which will be used
14:41:59 * bryan_att let me know when you get to B release (ping)
14:42:22 <Jonas2> bryan_att: Yes
14:42:53 <s_berg> Yes, definately DNS and NTP changes in there. In that case I think we're good.
14:43:04 <Jonas2> Good
14:43:25 <Jonas2> Can we move to B-release?
14:43:30 <szilard> yes
14:43:36 <s_berg> One question first.
14:44:34 <s_berg> szilard, mskalski: We've agreed to only create manual templates for the deployer for SR1 now? Will that slow anyone down (except me...) like CI for instance?
14:45:14 <s_berg> (assuming that the "copy-my-environment-onto-a-dha.yaml" type of functionality has been used by many?
14:45:15 <szilard> manual template ?
14:45:49 <s_berg> Well, basically tweaking dea.yaml manually for automatic deployment when tweaks are needed?
14:46:39 <szilard> aha, I see, well I have added a few templates
14:46:57 <szilard> for virtual, and for hardware (Montreal, LF)
14:47:18 <s_berg> Ah, OK, that's great - that should keep us floating. :)
14:47:20 <Jonas2> s_berg: I guess we have no other option?
14:47:35 <szilard> located under deploy/templates
14:47:52 <s_berg> Jonas2: Not really, but maybe we should look into this again when we move to 7.0 (?) for R2.
14:48:15 <s_berg> Jonas2: Would love to see if we can get it working again. But with example templates not a big issue.
14:48:22 <Jonas2> #info: auto_reaping will not be supported in SR1, we should try to suppport this for the B-release
14:48:32 <Jonas2> #info We seem to be in ok shape for SR1
14:48:45 <Jonas2> #topic B-release
14:49:07 <[1]JonasB> #topic B-release
14:49:23 <Jonas2> ping bryan_att
14:49:42 * bryan_att thanks
14:49:49 <Jonas2> #info we're now starting to get integration requsets in
14:50:16 <Jonas2> #info requests from SFC exist, and there will be more
14:50:20 <bryan_att> I need to know how to install Fuel on a 3-node non-HA baremetal environment so I can update the install scripts for Congress
14:51:22 <Jonas2> Have you tried using the install documentation from Arno?
14:51:45 <szilard> you need to install only Fuel ?
14:52:50 <bryan_att> I need Kilo+Lithium
14:53:23 <mskalski> bryan_att: Kilo will be in 7.0, in 6.1 have juno
14:53:38 <bryan_att> The install docs don't help a lot.  I need to know exactly where I need to update the scripts and that's not documented anywhere afaict
14:54:05 <mskalski> bryan_att: but 7.0 will be release in next 2/3 weeks
14:54:22 <bryan_att> but the basic question is whether I can install on 3 baremetal boxes with one NIC and a L3 switch; lmcdasm said this was possible
14:54:28 <bryan_att> what is "7.0"
14:54:40 <Jonas2> So why dont use Fuel 7.0 prestine and the documentation that comes with it?
14:54:44 <mskalski> bryan_att: Fuel 7.0
14:55:26 <bryan_att> the question is how do I install another openstack feature etc
14:55:45 <Jonas2> bryan_att: Build a fuel plugin
14:56:07 <Jonas2> mskalski: Can you point to plug-in documentation?
14:56:26 <mskalski> https://wiki.openstack.org/wiki/Fuel/Plugins
14:56:37 <Jonas2> mskalski: Thx
14:56:51 <Jonas2> bryan_att: That should do it for you!
14:57:08 <bryan_att> I also need to know what openstack etc features are installed in Arno so I can make requirements for the B release
14:57:15 <s_berg> bryan_att: Personally I think the best approach is to start straight away building a Debian package and run the trial-and-error approach over that until it does what you expect. Then move into packacking it up in a Fuel package. mskalski may not agree with me here though. :)
14:57:18 <bryan_att> where is this documented? (not in the release notes)
14:58:13 <s_berg> bryan_att: You would probably be better off taking a sneak peak at Fuel 7.0 and what's in there, as that is the base for your delta.
14:58:15 <Jonas2> #link https://wiki.openstack.org/wiki/Fuel/Plugins
14:58:17 <bryan_att> (meaning the set of features installed by Fuel for Arno)
14:58:41 <Jonas2> bryan_att: If you need Kilo, dont use Arno
14:58:54 <bryan_att> so if I intend to add a new feature, I need to modify something under the openstack repo?
14:59:18 <bryan_att> I need t know what's in Arno so I can say what are the Fuel requirements (genesis really) for R2
14:59:26 <Jonas2> bryan_att: No you will write a fuel plugin
15:00:02 <Jonas2> 'bryan_att: Just state your dependencies in the request.
15:00:08 <bryan_att> OK, I will check into that plugin doc
15:00:30 <bryan_att> I didn't want to reference things that are already supported but ok
15:00:41 <Jonas2> ruijing: You have started an ODL 2.4 plugin, right?
15:01:24 <bryan_att> so on the other question, maybe offline - what do I need to know/do if anything to install Fuel on a 3-node baremetal non-HA set of nodes?
15:01:42 <bryan_att> who should I followup with on that?
15:02:42 <Jonas2> bryan_att: It should be covered in the install documentation. If not, ping some of us.
15:03:06 <Jonas2> *any of us
15:03:19 <Jonas2> So were over time.
15:03:32 <Jonas2> Anything more we need to cover today?
15:03:43 <Jonas2> 3
15:03:49 <s_berg> bryan_att: http://artifacts.opnfv.org/genesis/fuel/docs/installation-instructions.html
15:03:54 <Jonas2> 2
15:04:01 <Jonas2> 1
15:04:01 <ruijing> OVS 2.4
15:04:17 <Jonas2> Ok goahead ruijing.
15:04:48 <mskalski> bye guys
15:04:52 <ruijing> bye
15:04:58 <Jonas2> Bye
15:05:02 <Jonas2> #endmeeting
15:05:10 <[1]JonasB> #endmeeting