Open Stack

Hi Tim,

Monday 9am PST should be ok for me, it is better if u guys could do 4 - 5
pm, but let's settle on 9 am for now, see if Bryan and others would be ok.
Regarding meeting tools, in opnfv we use GoToMeeting a lot, would u guys be
ok with that? Or should we have a Google Hangout?
On Feb 14, 2015 8:04 AM, "Tim Hinrichs" <thinrichs at vmware.com> wrote:

>  Hi Zhipeng,
>
>  Sure we can talk online Mon/Tue.  If you come up with some times the
> Copper team is available, I’ll do the same for a few of the Congress team.
> We’re usually available 9-4p Pacific, and for me Monday looks better than
> Tuesday.
>
>  If we schedule an hour meeting in Santa Rosa for Wed at say 1:30 or 2p,
> I’ll do my best to make it there.  Even if I can’t make it, you’ll always
> have Sean to talk with.
>
>  Tim
>
>
>
>
>  On Feb 12, 2015, at 6:49 PM, Zhipeng Huang <zhipengh512 at gmail.com> wrote:
>
>  THX Tim!
>
>  I think It'd be great if we could have some online discussion ahead of
> F2F LFC summit.We could have the crash course early next week (Monday or
> Tuesday), and then Bryan could discuss with Sean in detail when they met,
> with specific questions.
>
>  Would this be ok for everyone ?
>
> On Fri, Feb 13, 2015 at 7:21 AM, Tim Hinrichs <thinrichs at vmware.com>
> wrote:
>
>> Bryan and Zhipeng,
>>
>>  Sean Roberts (CCed) is planning to be in Santa Rosa.   Sean’s
>> definitely there on Wed.  Less clear about Thu/Fri.
>>
>>  I don’t know if I’ll make the trip yet, but I’m guessing Wed early
>> afternoon if I can.
>>
>>  Tim
>>
>>
>>  On Feb 11, 2015, at 9:04 PM, SULLIVAN, BRYAN L <bs3131 at att.com> wrote:
>>
>>   Hi Tim,
>>
>>
>> It would be great to meet with members of the Congress project if
>> possible at our meetup in Santa Rosa. I plan by then to have a basic
>> understanding of Congress and some test driver apps / use cases to demo at
>> the meetup. The goal is to assess the current state of Congress support for
>> the use cases on the OPNFV wiki: https://wiki.opnfv.org/copper/use_cases
>> <https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.opnfv.org_copper_use-5Fcases&d=AwMFAg&c=Sqcl0Ez6M0X8aeM67LKIiDJAXVeAw-YihVMNtXt-uEs&r=B6BWd4kFfgOzAREgThxkmTZKy7dDXE2-eBAmL0PBK7s&m=79iOYd5evGtBk2y36AKWDlDGaxiAbtt-Aago3I-8XcU&s=d4pb7BHqqZMj3oOoJBwixcr4VsTM0B4JwHe_JHRQ_VU&e=>
>>
>>
>> I would be doing the same with ODL but I’m not as far on getting ready
>> with it. So the opportunity to discuss the use cases under Copper and the
>> other policy-related projects
>>
>> (fault management
>> <https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.opnfv.org_doctor&d=AwMFAg&c=Sqcl0Ez6M0X8aeM67LKIiDJAXVeAw-YihVMNtXt-uEs&r=B6BWd4kFfgOzAREgThxkmTZKy7dDXE2-eBAmL0PBK7s&m=79iOYd5evGtBk2y36AKWDlDGaxiAbtt-Aago3I-8XcU&s=Wq56oTQYc1glpCeJ6wfL60x0AdyAphZeL55R7Kc7TvU&e=>,
>> resource management
>> <https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.opnfv.org_promise&d=AwMFAg&c=Sqcl0Ez6M0X8aeM67LKIiDJAXVeAw-YihVMNtXt-uEs&r=B6BWd4kFfgOzAREgThxkmTZKy7dDXE2-eBAmL0PBK7s&m=79iOYd5evGtBk2y36AKWDlDGaxiAbtt-Aago3I-8XcU&s=69Ak90Xh9biVNpWyCeLW8_7I0CoX0WrcDuFwlHQmM30&e=>,
>> resource scheduler
>> <https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.opnfv.org_requirements-5Fprojects_resource-5Fscheduler&d=AwMFAg&c=Sqcl0Ez6M0X8aeM67LKIiDJAXVeAw-YihVMNtXt-uEs&r=B6BWd4kFfgOzAREgThxkmTZKy7dDXE2-eBAmL0PBK7s&m=79iOYd5evGtBk2y36AKWDlDGaxiAbtt-Aago3I-8XcU&s=haq_oYTeYW7TkZp-eJrCx33KJjCg_tQlWTwiH_4OO9I&e=>)
>> with Congress experts would be great.
>>
>>
>> Once we understand the gaps in what we are trying to build in OPNFV, the
>> goal for our first OPNFV release is to create blueprints for new work in
>> Congress. We might also just find some bugs and get directly involved in
>> Congress to address them, or start a collaborative development project in
>> OPNFV for that. TBD
>>
>>
>> Thanks,
>>
>> Bryan Sullivan | Service Standards | AT&T
>>
>>
>> *From:* Tim Hinrichs [mailto:thinrichs at vmware.com <thinrichs at vmware.com>]
>>
>> *Sent:* Wednesday, February 11, 2015 10:22 AM
>> *To:* OpenStack Development Mailing List (not for usage questions)
>> *Cc:* SULLIVAN, BRYAN L; HU, BIN; Rodriguez, Iben; Howard Huang
>> *Subject:* Re: [openstack-dev] [congress][Policy][Copper]Collaboration
>> between OpenStack Congress and OPNFV Copper
>>
>>
>>
>> Hi Zhipeng,
>>
>>
>>
>> We’d be happy to meet.  Sounds like fun!
>>
>>
>>
>> I don’t know of anyone on the Congress team who is planning to attend the
>> LF collaboration summit.  But we might be able to send a couple of people
>> if it’s the only real chance to have a face-to-face.  Otherwise, there are
>> a bunch of us in and around Palo Alto.  And of course, phone/google
>> hangout/irc are fine options as well.
>>
>>
>>
>> Tim
>>
>>
>>
>>
>>
>>
>>
>> On Feb 11, 2015, at 8:59 AM, Zhipeng Huang <zhipengh512 at gmail.com> wrote:
>>
>>
>>
>> Hi Congress Team,
>>
>>
>>
>> As you might already knew, we had a project in OPNFV covering deployment
>> policy called Copper
>> <https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.opnfv.org_copper&d=AwMFaQ&c=Sqcl0Ez6M0X8aeM67LKIiDJAXVeAw-YihVMNtXt-uEs&r=B6BWd4kFfgOzAREgThxkmTZKy7dDXE2-eBAmL0PBK7s&m=R1ER1wU47Knv6PaOiamDwCm76pwx5uuE47mpn_03mzY&s=S7VfJALm_Pmzb2S-o3NUlcNzLAy9yYceGzcyKX3CA-w&e=>,
>> in which we identify Congress as one of the upstream projects that we need
>> to put our requirement to. Our team has been working on setting up a simple
>> openstack environment with congress integrated that could demo simple use
>> cases for policy deployment.
>>
>>
>>
>> Would it possible for you guys and our team to find a time do an
>> Copper/Congress interlock meeting, during which Congress Team could
>> introduce how to best integrate congress with "vanilla" openstack? Will
>> some of you attend LF Collaboration Summit?
>>
>>
>>
>> Thanks a lot :)
>>
>>
>>
>> --
>>
>> Zhipeng (Howard) Huang
>>
>>
>>
>> Standard Engineer
>>
>> IT Standard & Patent/IT Prooduct Line
>>
>> Huawei Technologies Co,. Ltd
>>
>> Email: huangzhipeng at huawei.com
>>
>> Office: Huawei Industrial Base, Longgang, Shenzhen
>>
>>
>>
>> (Previous)
>>
>> Research Assistant
>>
>> Mobile Ad-Hoc Network Lab, Calit2
>>
>> University of California, Irvine
>>
>> Email: zhipengh at uci.edu
>>
>> Office: Calit2 Building Room 2402
>>
>>
>>
>> OpenStack, OpenDaylight, OpenCompute affcienado
>>
>> __________________________________________________________________________
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe: OpenStack-dev-request at lists.openstack.org
>> ?subject:unsubscribe
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>>
>>
>>
>>
>> __________________________________________________________________________
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe:
>> OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
>> <http://OpenStack-dev-request@lists.openstack.org/?subject:unsubscribe>
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>>
>
>
>  --
>  Zhipeng (Howard) Huang
>
>  Standard Engineer
> IT Standard & Patent/IT Prooduct Line
> Huawei Technologies Co,. Ltd
> Email: huangzhipeng at huawei.com
> Office: Huawei Industrial Base, Longgang, Shenzhen
>
>  (Previous)
> Research Assistant
> Mobile Ad-Hoc Network Lab, Calit2
> University of California, Irvine
> Email: zhipengh at uci.edu
> Office: Calit2 Building Room 2402
>
>  OpenStack, OpenDaylight, OpenCompute affcienado
>
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
>
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20150214/398f4f27/attachment.html>