13:55:56 <Guest48551> #startmeeting weekly fuel@opnfv sync
13:55:56 <collabot> Meeting started Thu Aug 20 13:55:56 2015 UTC.  The chair is Guest48551. Information about MeetBot at http://wiki.debian.org/MeetBot.
13:55:56 <collabot> Useful Commands: #action #agreed #help #info #idea #link #topic.
13:55:56 <collabot> The meeting name has been set to 'weekly_fuel_opnfv_sync'
13:56:31 <Guest48551> #info Jonas Bjurel
13:56:55 <mskalski> #info Michal Skalski
13:58:13 <lmcdasm> #info Daniel Smith
14:00:45 <Guest48551> Ping Stefan Berg
14:01:25 <Guest48551> im on irc with my phone bear with me
14:02:01 <mskalski> HI, it looks like another project want to use our installer (point 5): http://ircbot.wl.linuxfoundation.org/meetings/opnfv-ovsnfv/2015/opnfv-ovsnfv.2015-08-17-13.02.html
14:02:02 <Guest48551> lets start with odl
14:02:31 <Guest48551> Cool
14:03:49 <Guest48551> chris wants to have a deploy option to select helium or lithium, mskalski?
14:05:26 <mskalski> I don't know but it will be hard to implement because we build packages of odl during plugin compilation so then is time when we choose what version to use
14:07:02 <Guest48551> Could we just have two plugins and select the one to use at deploy?
14:07:20 <lmcdasm> and build both at compilation time?
14:08:12 <Guest48551> Yes
14:08:13 <mskalski> we can not install the same plugin twice with different versions of odl
14:08:23 <stefan_berg> #Info Stefan Berg
14:09:04 * stefan_berg is sorry he's a little late
14:09:09 <mskalski> probably it is possible to build packages for both version of odl in one plugin
14:09:14 <mskalski> as Daniel suggest
14:09:19 * lmcdasm thinks if we can do this as a post deploy puppet switch of the whole karaf container (ODL) if on the front end is hard and then
14:09:41 <Guest48551> Dont you install plugins at deploy? Either you install lith or heli
14:09:45 <lmcdasm> look at having a different name space created later so that ODL is not one plugin but ODL_H is one, ODL_L is another ?
14:10:19 <lmcdasm> i think it would be easier to let the current plugin build, and do "both" builds - so you have the RPM
14:10:39 <lmcdasm> and then do a bit of post-deploy.sh to switch version if need be (puppet file or yaml of "version = L || H"
14:10:47 <lmcdasm> and then the "setup inside the infra" can work
14:10:54 <lmcdasm> and we just swap the karaf out
14:11:00 <lmcdasm> with the "other rpm" that was built
14:11:02 <mskalski> of course you have two version of plugin and before deployment decide which to install
14:11:13 <mskalski> you can have*
14:11:22 <lmcdasm> that would be the idea i was getting at michal
14:11:34 <lmcdasm> so you have two version of the plugin and the 'select plugin verseion'
14:11:40 <lmcdasm> that would allow us to grow it as ODL grows it
14:11:47 <lmcdasm> (versioning wise)
14:11:54 <Guest48551> Mskalski: Then we are set
14:11:56 <mskalski> yes but not from fuel web uil
14:12:02 <lmcdasm> no
14:12:15 <lmcdasm> we can do somehting simlar to the pre-deploy.sh "for now"
14:12:19 <lmcdasm> and then see how it behaves and learn
14:12:40 <lmcdasm> and then discuss later if its an option that Mirantis might wanna add as a GUI element
14:12:44 <lmcdasm> (maybe :) )
14:13:03 <stefan_berg> But "GUI element" could come in the plugin, no?
14:13:14 <mskalski> yes it can
14:13:26 <stefan_berg> I would really love to get rid of pre-deploy.sh straight away.
14:13:57 <Guest48551> Of course every one wants lith but. Rules say sr should not change major ver
14:14:02 <lmcdasm> im fine with doing away with the script.. i was merely saying for version swapping the ODL if we dont / cant have a "checkbox" for different ODL version
14:14:06 <lmcdasm> then we could script around it
14:14:10 <stefan_berg> I'm probably way out on a limb here, but couldn't there be one plugin per version, each which its own "GUI enabler" (and a logical safeguard not to enable both)?
14:15:05 <lmcdasm> one plugin per version  == each plugin has a version (or two) no?
14:15:17 <Guest48551> Lets not complicate install one or the other is ok
14:15:21 <lmcdasm> i think we are saying the same thing.. its about building or deploying FUEL
14:15:22 <mskalski> stefan_berg: yes you can build plugins with different version of ODL but you will need to change the metada file
14:15:29 <lmcdasm> at deployment you can pick the plugin version
14:15:34 <lmcdasm> and the plugin version will have the ODL version in it.
14:15:41 <mskalski> stefan_berg: to install them on the same time
14:15:41 <lmcdasm> but you cant have "both" as an option in the FUEL UI
14:15:45 <lmcdasm> as i understandi t
14:16:00 * stefan_berg is not up to speed and does not know ODL so take everything he says with two grains of salt :)
14:16:57 <mskalski> you can build one plugin and call it fuel-opendaylight-helium
14:17:14 <mskalski> and another fuel-opendaylight-lithium
14:17:23 <mskalski> and install them in the same time
14:17:37 <mskalski> then activate one of them from we ui
14:18:05 <mskalski> you can change the name of the plugin inside metadata.yml file
14:18:34 <lmcdasm> +1
14:18:37 <lmcdasm> nice
14:18:51 <Guest48551> Mskalsi: that is ok
14:19:59 <mskalski> but there will be no mechanism which prevent user from activate both plugin on the same time, so end user will need to know what he is doing
14:20:46 <Guest48551> Mskalski lets do it like that
14:20:47 <stefan_berg> IMHO still better than pre-deploy.sh...
14:21:01 <stefan_berg> So +1 on that one.
14:22:17 <Guest48551> Next stefan on rebase status
14:22:35 * lmcdasm agreed with SBerg
14:23:20 <stefan_berg> Well, have just started with that so not much to report yet. Will not be too hard.
14:23:48 <stefan_berg> Have (hopefully gone now) some issues with auto deploy (my prototype), seemed timing related mostly.
14:24:08 <stefan_berg> Once *that* is working I'll summarize changes to Szillard.
14:24:46 <stefan_berg> And working in master branch, right? :)
14:24:58 <Guest48551> stefan_berg: great
14:25:18 <Guest48551> stefan_berg: yes master
14:25:57 * stefan_berg will ask Santa for the ability to branch freely in the repo
14:26:37 <stefan_berg> Ok, so, done.
14:26:39 * lmcdasm thinks since we have our own repo now.. that your wish should be grantable
14:26:55 * lmcdasm and doesnt think Jonas resembles Santa at all
14:27:35 <stefan_berg> Uhm... So we're not working in genesis now? As I said, not up to speed...
14:29:47 <stefan_berg> (what I mean: Have we broken out the genesis/fuel into the fuel repo yet? Will clone the latter and find the answer...)
14:29:59 <lmcdasm> its a work in progress
14:30:11 <lmcdasm> i know that jonas has done some readmes and a test file (or maybe it was LIcense)
14:30:23 <lmcdasm> im not sure of when we plan to do a clone/cutover and leave Genesis -
14:30:53 <stefan_berg> estefbe@elxgjtqrs22:~/git/fuel$ find * -type f
14:30:53 <stefan_berg> INFO
14:30:53 <stefan_berg> LICENSE
14:30:55 <stefan_berg> :)
14:32:15 * lmcdasm (thinks if we are the ones to leave Genesis - we get to keep Phil C.
14:32:19 <stefan_berg> So this begs the question: Should we expedite the breakout "now" for B-release work?
14:32:37 <lmcdasm> tis a good question
14:32:37 <stefan_berg> Less stuff to move later as we go along...
14:32:54 <lmcdasm> i mean - we could do a clone and then try test building / workig from it
14:32:56 <stefan_berg> But I think we should discuss that when Jonas has a larger keyboard.
14:33:10 <lmcdasm> (haha - good idea)..
14:33:52 * lmcdasm notes - we need to move the genesis/common root levels as well as the FUEL stuff - since our makefiles were altered during release.
14:34:20 * lmcdasm wonders if there is a plan in BGS / Genesis to continue for common ground between installers or if was tossed out
14:34:25 <stefan_berg> So this is a small task in itself, which needs to be coordinated in time.
14:34:40 <lmcdasm> doing one doesnt impact master does it
14:34:55 <lmcdasm> except to let the people collectively know the "date/time" to stop pushing over commits, etc
14:35:13 <lmcdasm> and that makes and verifies from jenkins neeed to be repointed
14:35:49 <Guest48551> Lets work in genesis for now and discuss this next week
14:35:49 <lmcdasm> probably should plan out a "maintenance day / window" or something to have the CI impacts looked at (or maybe we dont touch it and keep as is?).
14:35:56 <stefan_berg> Yes, precisely my point, so the commit in fuel should be merged simultaneously with a commit in genesis that removes Fuel content from the master (legacy still there).
14:36:09 <stefan_berg> Yep, let's discuss later.
14:36:10 <lmcdasm> +1 to both of you ..
14:36:18 <lmcdasm> i think its a bit bigger discussion on "method"
14:38:02 <Guest48551> Anything more to discuss today?
14:38:33 <mskalski> I will be on vacation in next two weeks ;)
14:38:51 <mskalski> but if you need me just write a mail I will try respond
14:39:16 <lmcdasm> have a good (and well deserved) vacation Michal!
14:39:25 <mskalski> thx :)
14:39:38 <Guest48551> Have a good one!
14:39:49 <stefan_berg> May sun by upon you! :)
14:39:59 <mskalski> hehe thank you :)
14:40:52 <Guest48551> #endmeeting