14:14:36 <mburns> #startmeeting oVirt Node Weekly Meeting
14:14:36 <ovirtbot> Meeting started Tue Sep  3 14:14:36 2013 UTC.  The chair is mburns. Information about MeetBot at http://wiki.debian.org/MeetBot.
14:14:36 <ovirtbot> Useful Commands: #action #agreed #help #info #idea #link #topic.
14:14:44 * fabiand is here
14:14:45 <mburns> #chair jboggs fabiand rbarry
14:14:45 <ovirtbot> Current chairs: fabiand jboggs mburns rbarry
14:14:49 <mburns> #topic agenda
14:14:55 * jboggs here
14:15:00 <mburns> #info 3.0.x updates
14:15:03 * rbarry here
14:15:05 <mburns> #info 3.1.0 planning
14:15:14 <mburns> #info other topics
14:15:20 <mburns> #topic 3.0.x updates
14:15:32 <mburns> fabiand: rbarry:  where are we with vdsm issues?
14:15:37 <mburns> solved? pending?
14:16:00 <fabiand> mburns, I'm just doing abuild to test something ..
14:16:18 <rbarry> Pretty much same. Root cause analysis.
14:16:19 <fabiand> maybe it's a missing rwtab entry
14:16:47 <mburns> #info issues with vdsm starting after reboot
14:16:53 <mburns> #info still trying to get a root cause
14:17:13 <mburns> rbarry: fabiand:  have you been working with anyone from the vdsm team ( dougsland, maybe)?
14:17:31 <fabiand> mburns, I only really got started today
14:17:38 <fabiand> but dougsland doesn't seem to be around, so no ..
14:17:39 <fabiand> not yet
14:17:45 <fabiand> I wanted to discuss my findings with him..
14:17:50 <fabiand> and analyze the warning I found
14:18:18 <rbarry> dougsland is aware of it, but not actively working with him for the last couple of days, since I'm still trying to figure out exactly where it's breaking
14:18:25 <jboggs> to reproduce just install and register then reboot?
14:18:27 <mburns> fsimonce: is there someone other than dougsland that can help with vdsm not starting after reboot on ovirt-node?
14:19:16 <fabiand> jboggs, yep
14:19:22 <fabiand> jboggs, vdsmd will be in a failed state ..
14:19:27 <rbarry> jboggs: Yep. vdsmd fails to start after the reboot. vdsmd.log has no entries since shutdown. Can be brought up as normal by hand. It's failing somewhere in init
14:20:34 <jhernand> exit
14:20:53 <mburns> fabiand: rbarry:  but manual start/stop works, right?
14:21:07 <fabiand> mburns, yes
14:22:38 <rbarry> mburns: Yes. Which is effectively what's taking so long. Muck with systemd a bit. Build a new image with some slight change. Repeat :/
14:22:57 <mburns> jboggs: isn't there a way to crack the image and run a specific set of commands?
14:23:08 <mburns> so we don't have to rebuild from scratch everytime?
14:23:09 <fabiand> ... edit-node ..
14:23:09 <ovirtbot> fabiand: Error: ".." is not a valid command.
14:23:13 <jboggs> --script
14:23:17 <fabiand> thanks ovirtbot
14:23:24 <mburns> rbarry: there you go, use --script
14:24:20 <rbarry> Ack. That'd make life easier...
14:24:51 <mburns> jboggs: do we still have the option to have it stop with --script if no script is provided
14:25:00 <mburns> and then we can manually go in and do something?
14:25:14 <jboggs> it should be checking...
14:25:29 <MCLinux> sorry guys was out; did I miss the go/no go?
14:25:48 <mburns> MCLinux: yes
14:26:00 <mburns> we have a couple updates coming in today with a ship date of monday
14:26:17 <mburns> but working from the beta repo later today will be the same as stable repo on monday
14:26:57 <jboggs> mburns, no there is no shell can be added back by a possible one liner
14:27:11 <jboggs> or worse case add a sleep in the script file and go edit manually
14:27:31 <mburns> jboggs: cool, can you post that patch?
14:27:38 <mburns> that will make our lives easier, i think
14:27:49 <MCLinux> rock, ok well ty anyways I am assuming there was an email? or if anyone wants to be nice enough to just let me know dates I would appreciate it
14:27:50 <jboggs> yep
14:28:37 <mburns> MCLinux: no email yet (meeting just ended, and another one started)
14:28:43 <mburns> will email after i'm out of meetings
14:28:48 <MCLinux> oh ok, well I will get out of the way
14:28:57 <MCLinux> ty guys
14:29:00 <mburns> MCLinux: ship date will be 09-Sep (pending something critical before then)
14:29:09 <mburns> jboggs: thanks
14:29:10 <MCLinux> k tyvm
14:30:14 <mburns> fabiand: rbarry:  if dougsland doesn't show, then see if you can get someone else from vdsm to help (ping fsimonce or danken)
14:30:41 <rbarry> Ack
14:30:44 <fabiand> yep
14:30:47 <mburns> anything else pending for 3.0.x?
14:30:55 <fabiand> not from my pov ..
14:31:02 <fabiand> I didn't get in as much as I wanted ..
14:31:08 <fabiand> but let us stable be first
14:31:13 <mburns> fabiand: agreed
14:31:15 <fabiand> what a nice grammar ..
14:31:24 <mburns> fabiand: good enough for me to understand
14:31:34 <fabiand> For 3.0.2 I try to do it differently - I already started reviewing pending patches early
14:31:41 <mburns> fabiand: excellent
14:31:44 <fabiand> So they stay in master for longer - and we test them each time we do some tests ..
14:31:50 <fabiand> mburns, thanks;)
14:31:55 * mburns hoping to get time to review early as well
14:32:08 <mburns> #topic node 3.1.0 release planning
14:32:17 <mburns> #link http://www.ovirt.org/Node_3.1_release-management
14:32:22 <fabiand> I actually liked how it wsa done in 3.0.1 ... not many patches in the late phase, only real bug fixes
14:32:56 <mburns> #info proposed features:
14:33:07 <mburns> #info PackageRefactoring
14:33:13 <mburns> fabiand: are you going to own this?
14:33:21 <mburns> oh, no, that's mine
14:33:26 <mburns> nevermind
14:33:33 * mburns was confusing it with something else
14:33:46 <fabiand> okay
14:33:46 <mburns> #info mburns will own package re-factoring
14:33:53 <mburns> #action mburns to work on feature page
14:34:08 <mburns> #info BuildtoolMigration
14:34:12 <mburns> who is going to own this?
14:34:22 <mburns> jboggs: i know you worked on this at one point...
14:34:31 <jboggs> what is it? :)
14:34:39 <fabiand> jboggs, migrate to oz/imgfac
14:34:40 <mburns> move from livecd-tools to oz/livemedia
14:34:43 <jboggs> ahh ok
14:34:50 <jboggs> yeah I'll work on that
14:35:03 <mburns> #info jboggs will own this feature
14:35:09 <mburns> #action jboggs to start on feature page
14:35:13 <mburns> #undo
14:35:13 <ovirtbot> Removing item from minutes: <MeetBot.items.Action object at 0x9abad4c>
14:35:21 <mburns> #action jboggs to start on feature page for build tool migration
14:35:37 <mburns> #info Storage/Installer module rewrite
14:35:41 <mburns> fabiand: this is yours, right?
14:35:49 <fabiand> yep
14:35:52 <fabiand> I can take that one
14:35:59 <jboggs> I can help on that as well, for efi and what not
14:36:00 <mburns> #info fabiand to own this
14:36:15 <mburns> #action fabiand to start on feature page for installer/storage re-write
14:36:22 <mburns> jboggs: sure
14:36:27 <mburns> #info jboggs to help as well
14:36:43 <mburns> #info OpenVSwitchSupport
14:36:47 <mburns> rbarry: this yours?
14:37:14 <rbarry> Yep, that's mine
14:37:20 <mburns> #info rbarry to own
14:37:36 <mburns> #action rbarry to start on feature page for openvswitch support
14:37:48 <mburns> rbarry: might make sense to investigate neutron networking as well
14:38:02 <mburns> (formerly known as quantum)
14:38:27 <mburns> #info PluginLiveInstall
14:38:39 <mburns> jboggs: i think this is yours
14:38:55 <mburns> #info jboggs will own
14:38:56 <fabiand> mburns, jboggs I wonder if we should already start on this ..
14:39:08 <mburns> #action jboggs to start on feature page
14:39:12 <fabiand> well, I can see the need for it .
14:39:12 <mburns> fabiand: ?
14:39:24 <fabiand> I wondered if we shouldn't wait for union mounts for this ..
14:39:45 <fabiand> But there is no ETA (that I know of) for them .. so ... ignore my request :)
14:39:59 <mburns> fabiand: let's at least try to come up with a workable concept
14:40:04 <fabiand> yes
14:40:26 <mburns> if we can come up with something that works only with union mounts, then we'll wait
14:40:37 <mburns> but i think there are ways to do this without union mounts
14:40:38 <fabiand> ack
14:40:44 <fabiand> right
14:40:52 <fabiand> can we do a discussion somewhere?
14:40:55 <mburns> #undo
14:40:55 <ovirtbot> Removing item from minutes: <MeetBot.items.Action object at 0x9abab6c>
14:40:59 <fabiand> ml or on the wiki discussion page?
14:41:06 <mburns> #action jboggs to start on feature page for live plugin install
14:41:19 <mburns> fabiand: yes, let's break it off onto the ML
14:41:31 <mburns> jboggs: can you start that thread?
14:41:35 <jboggs> sure
14:41:45 <mburns> #action jboggs to start thread on live plugin installation
14:41:49 <jboggs> arch-list?
14:42:02 <mburns> jboggs: i think node-devel to start
14:42:11 <mburns> then we can bring it to arch once we have a concept
14:42:29 <mburns> #info PublicAPI
14:42:44 <mburns> fabiand: you've started discussions already, right?
14:42:44 <fabiand> / HighLevel FeaturePublishing
14:42:56 <mburns> #undo
14:42:56 <ovirtbot> Removing item from minutes: <MeetBot.items.Info object at 0x9b7fe8c>
14:42:57 <fabiand> mburns, yes - I also want to - at least - mention it on the ml ..
14:43:10 <mburns> #info PublicAPI/Feature and capability publishing
14:43:15 <mburns> #info owned by fabiand
14:43:36 <mburns> #action fabiand to create feature page for public api and feature publishing
14:43:47 <mburns> #action fabiand to start mailing list discussion as well
14:44:00 <mburns> fabiand: that one may make more sense on arch@ and node-devel
14:44:10 <fabiand> okay
14:44:24 <mburns> #info Kimchi Plugin
14:44:36 <mburns> rbarry: you want this one?
14:44:43 <jboggs> if not im interested
14:44:47 <rbarry> I'm interested
14:45:38 <jboggs> --shell option http://gerrit.ovirt.org/18834
14:45:40 <mburns> not much can be done until the packaging is done in fedora, anyway
14:45:49 <mburns> #info jboggs and rbarry are interested
14:46:21 <mburns> #action rbarry to create feature page for Kimchi plugin
14:46:29 <mburns> jboggs: rbarry:  no issue with you collaborating
14:46:38 <jboggs> ack
14:46:44 <mburns> but now everyone has 2 feature pages to do
14:46:52 <mburns> (except me)
14:47:05 <mburns> but i'll be reviewing and contributing to all of them
14:47:29 <mburns> can we target next week for feature pages being at least started with initial concepts?
14:47:46 <fabiand> yep
14:48:45 <mburns> fabiand: rbarry:  though if you get completely bogged down in the vdsm issue, then we can slip to the week after
14:49:03 * mburns just realized that swap enhancements need to be added here
14:49:08 <mburns> and that belongs to mburns...
14:49:15 <mburns> #info SwapEnhancements
14:49:19 <mburns> #info owned by mburns
14:49:39 <mburns> #action mburns to add feature page to 3.1 release management and update (was proposed for 3.0)
14:50:16 <mburns> #info target feature pages for next week
14:50:58 <mburns> #info mburns to review schedules and come up with release date proposal for next week
14:51:13 <mburns> anything else for 3.1?
14:51:34 <fabiand> Nothing for now from me
14:51:48 <rbarry> Nothing
14:51:55 <jboggs> nothing here either
14:52:07 <mburns> ok, anything non-3.1?
14:52:10 <mburns> #topic Other Topics
14:52:58 <fabiand> I'm fine for now ..
14:53:03 <fabiand> Happy when vdsmd is also working :)
14:53:10 <mburns> ok, thanks all
14:53:13 <mburns> #endmeeting