17:00:46 <thinrichs> #startmeeting CongressTeamMeeting
17:00:47 <openstack> Meeting started Tue Jul  7 17:00:46 2015 UTC and is due to finish in 60 minutes.  The chair is thinrichs. Information about MeetBot at http://wiki.debian.org/MeetBot.
17:00:48 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
17:00:51 <openstack> The meeting name has been set to 'congressteammeeting'
17:01:12 <thinrichs> I know some people are out of town, so if you're here for Congress, could you say hi?
17:01:28 <masahito> hi, I'm here
17:01:34 <thinrichs> masahito: hi!
17:01:37 <veena> Hi, I'm here
17:02:05 <thinrichs> veena: hi!  I don't recognize your handle.  Have you been here before?
17:02:32 <veena> thinrichs: Nope. This is the first time am joining congress meeting
17:02:59 <bryan_att> Hi all
17:03:02 <thinrichs> veena: Welcome!
17:03:09 <thinrichs> bryan_att: hi!
17:03:52 <veena> thinrichs: recently got to know about this project, developed interest, so thought to join. Thank you.
17:05:23 <thinrichs> veena: you're welcome to join any time.  Let us know if things aren't clear.
17:05:50 <thinrichs> veena: would you mind telling us about yourself and what got you interested?
17:09:17 <veena> thinrichs: Sure. Am using and working in Openstack since a year. I have fixed few bugs in horizon, rally and neutron. Recently I started working on NFVO. Policy management is an important thing in NFVO, while working for this I came accross Congress.
17:09:51 <thinrichs> veena: great!  Where do you work?
17:10:12 <veena> thinrichs: Then I saw the summit videos related to congress. This seems very interesting project.
17:10:27 <veena> thinrichs: I work in Juniper Networks.
17:11:38 <thinrichs> veena: Thanks for the background.
17:11:59 <thinrichs> In terms of agenda this week, I have the following.
17:12:07 <veena> thinrichs: Thank you
17:12:13 <thinrichs> 1. midcycle sprint
17:12:22 <thinrichs> 2. UI demo by Yali
17:12:32 <thinrichs> 3. discuss moving meeting time
17:12:43 <thinrichs> 4. Keystone talk
17:12:47 <thinrichs> Anything else?
17:13:25 <masahito> how about summit sessions?
17:13:38 <thinrichs> masahito: that was my #4 (Keystone talk)
17:13:59 <masahito> thinrichs: ok
17:14:15 <thinrichs> bryan_att: need to discuss getting the hands-on-lab up and running?
17:14:41 <bryan_att> I'm still working on it - I can provide an update.
17:14:55 <thinrichs> 5. bryan_att gives update on HOL.
17:15:02 <thinrichs> So let's get started then.
17:15:06 <thinrichs> #topic midcycle sprint
17:15:18 <thinrichs> I put together a wiki page with details of the sprint.
17:15:42 <thinrichs> #link https://wiki.openstack.org/wiki/Sprints/CongressLibertySprint
17:15:55 <thinrichs> It's also linked from the list of Liberty sprints:
17:16:01 <thinrichs> #link https://wiki.openstack.org/wiki/Sprints#Liberty_sprints
17:16:33 <thinrichs> It's all the same info we discussed: Aug 6-7 at the VMware campus in Palo Alto, CA, USA
17:17:16 <thinrichs> The only real new thing is that we can all sign up using eventbrite.
17:17:18 <thinrichs> #link https://www.eventbrite.com/e/congress-liberty-midcycle-sprint-tickets-17654731778
17:17:30 <thinrichs> So if you're attending, please use that form to sign up.
17:17:46 <masahito_> I've done!!
17:17:58 <thinrichs> That way we can get a headcount, and we have a way of sending messages to attendees.
17:18:02 <thinrichs> masahito: thanks!
17:18:40 <veena> thinrichs: Is there any way to attend it online?
17:18:41 <thinrichs> veena: for the midcycle sprint we're focusing on doing some distributed systems work on Congress.
17:19:12 <thinrichs> veena: we'll have an etherpad and will plan on having a phone line open.
17:19:55 <thinrichs> But in reality I imagine it'll be tough since software design always seems to end up on a whiteboard.
17:20:17 <thinrichs> If there are remote people we'll do what we can to engage them.
17:20:22 <veena> thinrichs: Okay. A google hangout would also work if it is possible
17:20:38 <thinrichs> veena: good suggestion
17:21:00 <thinrichs> Any questions about the sprint?
17:21:10 <veena> thinrichs: Thanks for the consideration
17:21:41 <veena> thinrichs: is there any doc related to the distributed systems work that you just mentioned?
17:22:03 <thinrichs> veena: let me look.  One minute.
17:23:05 <thinrichs> There's a brief description on the wiki page.
17:23:35 <thinrichs> There are a couple of blueprints that touch on this, but we should probably create a new blueprint:
17:23:36 <thinrichs> https://blueprints.launchpad.net/congress/+spec/integrate-oslo-messaging
17:23:51 <thinrichs> https://blueprints.launchpad.net/congress/+spec/dse-control-bus
17:24:03 <thinrichs> https://blueprints.launchpad.net/congress/+spec/hierarchical-dse
17:26:04 <thinrichs> Let's move on.
17:26:07 <thinrichs> #topic UI demo
17:26:31 <veena> thinrichs: is anybody working on integrating oslo.messaging?
17:26:46 <thinrichs> Yali has been working on a new GUI for writing policy and as part of the review process is giving a demo.
17:27:26 <thinrichs> veena: That's part of what the sprint is focused on.  Figuring out how to extend our internal message bus to be cross-process, cross-host.
17:27:44 <thinrichs> One option is to integrate oslo.messaging.  But there are others as well.
17:27:54 <veena> thinrichs: okay
17:28:08 <thinrichs> Back to the new GUI.
17:28:19 <thinrichs> If anyone wants to attend the demo, let me know.
17:28:35 <thinrichs> B/c of time zone constraints it'll be either 6a-7a or 5-6p Pacific time.
17:28:59 <bryan_att> I'd like to be there
17:29:02 <thinrichs> We're going to find a day later this week or early next week.
17:29:08 <masahito_> how I see the demo, online?
17:29:30 <thinrichs> masahito_: We haven't worked out details yet, but yes online.
17:29:53 <thinrichs> bryan_att: can you drop me an email with the days/times you're available the rest of this week and early next week?
17:30:04 <bryan_att> OK
17:31:01 <thinrichs> Any other questions about the demo?
17:31:21 <thinrichs> Moving on…
17:31:23 <masahito_> thinrichs: Would you send the time to ML when the time of the demo is decided?
17:31:30 <thinrichs> #topic Summit sessions
17:31:52 <masahito_> If possible I want to watch the demo.
17:32:23 <thinrichs> masahito_: could you email me your day/time availability for the rest of this week and early next week?  Remember options are 6a-7a and 5-6p Pacific.
17:32:42 <thinrichs> I'm thinking about proposing a summit session where build a tool that unifies Keystone and Congress policies.
17:32:44 <masahito_> thinrichs: okay.
17:33:31 <veena> thinrichs: Okay
17:33:32 <thinrichs> The idea would be to pull in policy.json from different services, translate them into the Congress policy language (Datalog), and do some analysis for how a Congress policy relates to the policy.json files.
17:33:52 <thinrichs> Any thoughts or reactions?
17:34:47 <masahito_> thinrichs: just translation? or will Congress do some action?
17:35:13 <masahito_> anyway that's sound fun.
17:35:50 <thinrichs> masahito_: I was just thinking analysis—the idea being to give operators a single pane of glass for Congress/Keystone policy.
17:36:08 <thinrichs> But I suppose we could also try to push policy down to those services.
17:36:37 <thinrichs> That's a good thing to think about at least.  Thanks!
17:37:03 <thinrichs> Any other plans for proposing a session?
17:37:31 <masahito_> I plan to submit my usecase as I mentioned last meeting
17:38:34 <thinrichs> masahito_: I'm happy to give feedback on the description if you want.  Just let me know.
17:38:49 <masahito_> The idea is about VM-HA using reactive enforcement for VM.
17:39:39 <thinrichs> Sounds interesting!
17:41:04 <thinrichs> Due date is July 15.
17:41:06 <masahito_> If possible, I want to speak the session with some Congress folks
17:41:30 <thinrichs> masahito_: we're happy to help.  Just let us know what you want us to do.
17:41:58 <masahito_> thinrichs: Thank you for offering.
17:42:30 <thinrichs> If anyone else has ideas, I'm happy to give feedback via email or #congress.
17:42:34 <thinrichs> Let's move on...
17:42:41 <thinrichs> #topic hands-on-lab update
17:42:55 <thinrichs> bryan_att: want to give us an update on how the HOL is going?
17:43:00 <bryan_att> OK, here's a quick update
17:43:25 <bryan_att> we are still working to get our OPNFV Arno lab off the ground
17:43:48 <bryan_att> step #2 will be adding Congress using the Ansible installer
17:44:19 <bryan_att> I should be ready to start testing end of next week on use cases for Congress
17:45:06 <bryan_att> Thus by the week of the summit I may not have all the pieces together for a HOL at ODL, but stil have the intent to run one if necessary virtually asap
17:45:29 <thinrichs> Great!  Is there anything you need from us?
17:45:44 <bryan_att> We are at the same time looking to have a SFC and GBP demo at the ODL Summit, as part of the OPNFV SFC project - the ODL PTLs are involved
17:46:05 <bryan_att> My goal is to use that to trigger some config violation reports as monitored by Congress
17:46:41 <bryan_att> So bringing those two things together may take more than three weeks - thus the risk that I may not be ready for the HOL goal by the summit
17:46:53 <bryan_att> That's all - just a progress report
17:47:31 <thinrichs> bryan_att: Thanks!  Make sure to reach out if you need our help.
17:47:40 <bryan_att> What I could use (if not provided earlier - I'll check) is guidance on Ansible install for Congress
17:47:49 <bryan_att> I need to check the old IRC logs
17:48:08 <bryan_att> Also whether I need Kilo or will Juno suffice
17:48:19 <thinrichs> I haven't tried the ansible installer personally.
17:48:53 <thinrichs> I remember the phone call though.
17:49:08 <thinrichs> I don't remember any docs coming out of that.
17:49:13 <bryan_att> Any installer will be fine - just might need some help to develop the install script given an existing installed OpenStack base
17:49:35 <thinrichs> I think that installer was designed to work with an existing OpenStack system.
17:49:42 <bryan_att> I will followup with you and team - the installer seemed pretty complete and easy
17:49:49 <thinrichs> Sounds good.
17:49:54 <bryan_att> yes, installing based upon an existing system is the assumption
17:50:17 <bryan_att> that's all - thanks
17:50:35 <thinrichs> Thanks!
17:50:39 <thinrichs> #topic meeting time
17:50:58 <thinrichs> We have a growing number of people who are actively contributing from the Asia time zone.
17:51:45 <thinrichs> It'd be great if they could attend.
17:52:39 <thinrichs> I'm guessing that if we moved the meeting, it would either need to be early (say 6a-8a Pacific) or late (say 5-6p Pacific).
17:53:18 <thinrichs> We don't have enough of the cores around today to figure out if moving the time would work.
17:53:38 <thinrichs> But for the rest of us in the US, does early morning or later evening work?
17:53:52 <masahito_> thinrichs: I realy appreciate your concern.
17:54:05 <bryan_att> 6-7AM PDT is fine for me also late afternoon - I'm in Seattle
17:54:26 <thinrichs> masahito_: do those times work for you generally?
17:54:40 <thinrichs> (I'll try to get the conversion to UTC.  One sec.)
17:54:51 <masahito_> wait a minitus. I need to translate the time to JST
17:56:16 <masahito_> thinrichs: Did you mention the time in summer time?
17:56:19 <thinrichs> 6a Pacific = 1p UTC
17:56:27 <thinrichs> 5p Pacific = midnight UTC
17:56:36 <thinrichs> We're in Pacific Daylight Time right now.
17:56:54 <thinrichs> masahito_: so yes summer time
17:57:47 <masahito_> both works well.
17:58:40 <veena> thinrichs: Any time would be fine. I can make out to attend
17:58:59 <thinrichs> I don't know if those times will work for the other US cores.  We'll need to investigate more.
17:59:31 <thinrichs> We're out of time for today.
17:59:34 <masahito_> In generally, my work time is in 5p-6p Pacific (UTC midnight)
17:59:35 <thinrichs> Thanks all!
18:00:04 <thinrichs> masahito_: good to know.  The 5-6p Pacific timeslot is likely better.
18:00:07 <thinrichs> #endmeeting