Re: [openstack-dev] [Cyborg] Core Team Update

[Zhipeng Huang]

Big +1, xinran has been tremendously helpful in the development.

On Tue, Oct 9, 2018, 7:55 PM Li Liu  wrote:

> Hi Cyborg Team,
>
> I want to nominate Xinran Wang as a new core reviewer for Cyborg project.
> Xiran has been working hard and kept contributing to the project[1][2].
> Keep Claim and Carry on :)
>
> [1]
> https://review.openstack.org/#/q/owner:xin-ran.wang%2540intel.com+status:open
> [2]
> http://stackalytics.com/?module=cyborg-group=person-day=rocky_id=xinran
> --
> Thank you
>
> Regards
>
> Li
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@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-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [cyborg]zero tolerance policy on padding activities

[Zhipeng Huang]

Hi all,

I want to emphasize the zero tolerance policy in cyborg project regarding
padding activities. If you look at the gerrit record [0] you would probably
got the idea: out of the 15 abandoned patches, only the ones from jiapei
and shaohe were actually meant to do real fixing.

We have #openstack-cyborg irc channel, community mailinglist as well as
individual core member email you could reach out to. We also have setup
wechat group for Chinese developers where the atmosphere is welcoming and
funny gifs flies around all the time. There are more than enough measures
to help you actually get involved with the project.

Do the right thing.

[0]
https://review.openstack.org/#/q/status:abandoned+project:openstack/cyborg+label:Code-Review%253D-2


-- 
Zhipeng (Howard) Huang

Standard Engineer
IT Standard & Patent/IT Product Line
Huawei Technologies Co,. Ltd
Email: huangzhip...@huawei.com
Office: Huawei Industrial Base, Longgang, Shenzhen

(Previous)
Research Assistant
Mobile Ad-Hoc Network Lab, Calit2
University of California, Irvine
Email: zhipe...@uci.edu
Office: Calit2 Building Room 2402

OpenStack, OPNFV, OpenDaylight, OpenCompute Aficionado
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [penstack-dev]Discussion about the future of OpenStack in China

[Zhipeng Huang]

watcher is known by some, but I don't think Masakari is

On Tue, Sep 25, 2018 at 5:47 AM Matt Riedemann  wrote:

> On 9/24/2018 12:12 PM, Jay Pipes wrote:
> > There were a couple points that I did manage to decipher, though. One
> > thing that both articles seemed to say was that OpenStack doesn't meet
> > public (AWS-ish) cloud use cases and OpenStack doesn't compare favorably
> > to VMWare either.
>
> Yeah I picked up on that also - trying to be all things to all people
> means we do less well at any single thing. No surprises there.
>
> >
> > Is there a large contingent of Chinese OpenStack users that expect
> > OpenStack to be a free (as in beer) version of VMware technology?
> >
> > What are the 3 most important features that Chinese OpenStack users
> > would like to see included in OpenStack projects?
>
> Yeah I picked up on a few things as well. The article was talking about
> gaps in upstream services:
>
> a) they did a bunch of work on trove for their dbaas solution, but did
> they contribute any of that work?
>
> b) they mentioned a lack of DRS and HA support, but didn't mention the
> Watcher or Masakari projects - maybe they didn't know they exist?
>
> --
>
> Thanks,
>
> Matt
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>


-- 
Zhipeng (Howard) Huang

Standard Engineer
IT Standard & Patent/IT Product Line
Huawei Technologies Co,. Ltd
Email: huangzhip...@huawei.com
Office: Huawei Industrial Base, Longgang, Shenzhen

(Previous)
Research Assistant
Mobile Ad-Hoc Network Lab, Calit2
University of California, Irvine
Email: zhipe...@uci.edu
Office: Calit2 Building Room 2402

OpenStack, OPNFV, OpenDaylight, OpenCompute Aficionado
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Openstack-sigs] [all][tc] We're combining the lists! (was: Bringing the community together...)

[Zhipeng Huang]

+1 and thanks for the effort to make this happen

On Fri, Sep 21, 2018, 9:22 AM Lance Bragstad  wrote:

>
>
> On Thu, Sep 20, 2018 at 7:19 PM Sean McGinnis 
> wrote:
>
>> On Thu, Sep 20, 2018 at 03:46:43PM -0600, Doug Hellmann wrote:
>> > Excerpts from Jeremy Stanley's message of 2018-09-20 16:32:49 +:
>> > > tl;dr: The openstack, openstack-dev, openstack-sigs and
>> > > openstack-operators mailing lists (to which this is being sent) will
>> > > be replaced by a new openstack-disc...@lists.openstack.org mailing
>> > > list.
>> >
>> > Since last week there was some discussion of including the openstack-tc
>> > mailing list among these lists to eliminate confusion caused by the fact
>> > that the list is not configured to accept messages from all subscribers
>> > (it's meant to be used for us to make sure TC members see meeting
>> > announcements).
>> >
>> > I'm inclined to include it and either use a direct mailing or the
>> > [tc] tag on the new discuss list to reach TC members, but I would
>> > like to hear feedback from TC members and other interested parties
>> > before calling that decision made. Please let me know what you think.
>> >
>> > Doug
>> >
>>
>> This makes sense to me. I would rather have any discussions where
>> everyone is
>> likely to see them than to continue with the current separation.
>>
>
> +1
>
>
>>
>>
>> __
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe:
>> openstack-dev-requ...@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-requ...@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-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Openstack-sigs] Capturing Feedback/Input

[Zhipeng Huang]

big +1, really look forward to the storyboard setup

On Fri, Sep 21, 2018 at 6:31 AM Melvin Hillsman 
wrote:

> Hey everyone,
>
> During the TC meeting at the PTG we discussed the ideal way to capture
> user-centric feedback; particular from our various groups like SIGs, WGs,
> etc.
>
> Options that were mentioned ranged from a wiki page to a standalone
> solution like discourse.
>
> While there is no perfect solution it was determined that Storyboard could
> facilitate this. It would play out where there is a project group
> openstack-uc? and each of the SIGs, WGs, etc would have a project under
> this group; if I am wrong someone else in the room correct me.
>
> The entire point is a first step (maybe final) in centralizing
> user-centric feedback that does not require any extra overhead be it cost,
> time, or otherwise. Just kicking off a discussion so others have a chance
> to chime in before anyone pulls the plug or pushes the button on anything
> and we settle as a community on what makes sense.
>
> --
> Kind regards,
>
> Melvin Hillsman
> mrhills...@gmail.com
> mobile: (832) 264-2646
> ___
> openstack-sigs mailing list
> openstack-s...@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-sigs
>


-- 
Zhipeng (Howard) Huang

Standard Engineer
IT Standard & Patent/IT Product Line
Huawei Technologies Co,. Ltd
Email: huangzhip...@huawei.com
Office: Huawei Industrial Base, Longgang, Shenzhen

(Previous)
Research Assistant
Mobile Ad-Hoc Network Lab, Calit2
University of California, Irvine
Email: zhipe...@uci.edu
Office: Calit2 Building Room 2402

OpenStack, OPNFV, OpenDaylight, OpenCompute Aficionado
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Openstack-sigs] [Openstack-operators] [tc]Global Reachout Proposal

[Zhipeng Huang]

Thanks Anita, will definitely do as you kindly suggested :)

On Thu, Sep 20, 2018, 12:04 PM Anita Kuno  wrote:

> On 2018-09-18 08:40 AM, Jeremy Stanley wrote:
> > On 2018-09-18 11:26:57 +0900 (+0900), Ghanshyam Mann wrote:
> > [...]
> >> I can understand that IRC cannot be used in China which is very
> >> painful and mostly it is used weChat.
> > [...]
> >
> > I have yet to hear anyone provide first-hand confirmation that
> > access to Freenode's IRC servers is explicitly blocked by the
> > mainland Chinese government. There has been a lot of speculation
> > that the usual draconian corporate firewall policies (surprise, the
> > rest of the World gets to struggle with those too, it's not just a
> > problem in China) are blocking a variety of messaging protocols from
> > workplace networks and the people who encounter this can't tell the
> > difference because they're already accustomed to much of their other
> > communications being blocked at the border. I too have heard from
> > someone who's heard from someone that "IRC can't be used in China"
> > but the concrete reasons why continue to be missing from these
> > discussions.
> >
>
> I'll reply to this email arbitrarily in order to comply with Zhipeng
> Huang's wishes that the conversation concerned with understanding the
> actual obstacles to communication takes place on the mailing list. I do
> hope I am posting to the correct thread.
>
> In response to part of your comment on the patch at
> https://review.openstack.org/#/c/602697/ which you posted about 5 hours
> ago you said "@Anita you are absolutely right it is only me stuck my
> head out speaks itself the problem I stated in the patch. Many of the
> community tools that we are comfortable with are not that accessible to
> a broader ecosystem. And please assured that I meant I refer the patch
> to the Chinese community, as Leong also did on the ML, to try to bring
> them over to join the convo." and I would like to reply.
>
> I would like to say that I am honoured by your generosity. Thank you.
> Now, when the Chinese community consumes the patch, as well as the
> conversation in the comments, please encourage folks to ask for
> clarification if any descriptions or phrases don't make sense to them.
> One of the best ways of ensuring clear communication is to start off
> slowly and take the time to ask what the other side means. It can seem
> tedious and a waste of time, but I have found it to be very educational
> and helpful in understanding how the other person perceives the
> situation. It also helps me to understand how I am creating obstacles in
> ways that I talk.
>
> Taking time to clarify helps me to adjust how I am speaking so that my
> meaning is more likely to be understood by the group to which I am
> trying to offer my perspective. I do appreciate that many people are
> trying to avoid embarrassment, but I have never found any way to
> understand people in a culture that is not the one I group up in, other
> than embarrassing myself and working through it. Usually I find the
> group I am wanting to understand is more than willing to rescue me from
> my embarrassment and support me in my learning. In a strange way, the
> embarrassment is kind of helpful in order to create understanding
> between myself and those people I am trying to understand.
>
> Thank you, Anita
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@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-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Openstack-sigs] [tc]Global Reachout Proposal

[Zhipeng Huang]

A quick sidenote for anyone is using riot.im but not super familiar with it
like I did ...

Its global search could not cache all the openstack channels, therefore you
have to manually join them via their own cmd lines as I recently discover
the methods ..
1. add @appservice-irc:matrix.org for friend
2. type in the console : !join chat.freenode.net #openstack-xxx

For registration, it is more wacky but I found it on google anyways:
1. add @appservice-irc:matrix.org for friend
2. type in the console : !storepass chat.freenode.net PASSWORD
3. add NickServ(IRC) for friend
4. type in the console : identify NICK PASSWORD

viola 

On Thu, Sep 20, 2018 at 1:34 AM Melvin Hillsman 
wrote:

> Regarding some web clients that are potentially useful
>
> https://webchat.freenode.net/
>   - Zane mentioned this already and I can say I tried/used it some time
> ago until I opted for CLI/alternatives
> https://riot.im (iOS and Android apps available along with online client)
>   - i find it a bit sluggish at times, others have not, either way it is a
> decent alternative
> https://thelounge.chat/
>   - have not tried it yet but looks promising especially self-hosted option
> https://irccloud.com
>   - what I currently use, I do believe it can be blocked, i am looking
> into riot and thelounge tbh
>
>
> On Wed, Sep 19, 2018 at 12:18 PM Zane Bitter  wrote:
>
>> On 18/09/18 9:10 PM, Jaesuk Ahn wrote:
>> > On Wed, Sep 19, 2018 at 5:30 AM Zane Bitter > > > wrote:
>>
>> Resotring the whole quote here because I accidentally sent the original
>> to the -sigs list only and not the -dev list.
>>
>> >> As others have mentioned, I think this is diving into solutions when
>> we haven't defined the problems. I know you mentioned it briefly in the PTG
>> session, but that context never made it to the review or the mailing list.
>> >>
>> >> So AIUI the issue you're trying to solve here is that the TC members
>> seem distant and inaccessible to Chinese contributors because we're not on
>> the same social networks they are?
>> >>
>> >> Perhaps there are others too?
>> >>
>> >> Obvious questions to ask from there would be:
>> >>
>> >> - Whether this is the most important issue facing contributors from
>> the APAC region
>> >>
>> >> - To what extent the proposed solution is expected to help
>> >
>> >
>> > I do agree with Zane on the above point.
>>
>> For the record, I didn't express an opinion. I'm just pointing out what
>> the questions are.
>>
>> > As one of OpenStack participants from Asia region, I will put my
>> > personal opinion.
>> > IRC and ML has been an unified and standard way of communication in
>> > OpenStack Community, and that has been a good way to encourage "open
>> > communication" on a unified method wherever you are from, or whatever
>> > background you have. If the whole community start recognize some other
>> > tools (say WeChat) as recommended alternative communication method
>> > because there are many people there, ironically, it might be a way to
>> > break "diversity" and "openness" we want to embrace.
>> >
>> > Using whatever social media (or tools) in a specific region due to any
>> > reason is not a problem. Anyone is free to use anything. Only thing we
>> > need to make sure is, if you want to communicate officially with the
>> > whole community, there is a very well defined and unified way to do it.
>> > This is currently IRC and ML. Some of Korean dev has difficulties to
>> use
>> > IRC. However, there is not a perfect tool out there in this world, and
>> > we accept all the reason why the community selected IRC as official tool
>> >
>> > But, that being said, There are some things I am facing with IRC from
>> > here in Korea
>> >
>> > As a person from Asia, I do have some of pain points. Because of time
>> > differences, often, I have to do achieve searching since most of
>> > conversations happened while I am sleeping. IRC is not a good tool to
>> > perform "search backlog". Although there is message archive you can
>> dig,
>> > it is still hard. This is a problem. I do love to see any technical
>> > solution for me to efficiently and easily go through irc backlog, like
>> > most of modern chat tools.
>> >
>> > Secondly, IRC is not a popular one even in dev community here in Korea.
>> > In addition, in order to properly use irc, you need to do extra work,
>> > something like setting up bouncing server. I had to do google search to
>> > figure out how to use it.
>>
>> I think part of the disconnect here is that people have different ideas
>> about what IRC (and chat in general) is for.
>>
>> For me it's a way to conduct synchronous conversations. These tend to go
>> badly on the mailing list (really long threads of 1 sentence per
>> message) or on code review (have to keep refreshing), so it's good that
>> we have another tool to do this. I answer a lot of user questions,
>> clarify comments on patches, and obviously join team meetings in IRC.
>>
>> The key part is 

Re: [openstack-dev] [User-committee] [publiccloud-wg] Meeting tomorrow

[Zhipeng Huang]

cc'ed sig list.

Kind reminder for the meeting about 2 and half hours away, we will do a
review of the denver ptg summary [0] and then go over the forum sessions
which we want to propose [1]

This is an EU/APAC friendly meeting so please do join us if you are in the
region :)

[0]https://etherpad.openstack.org/p/publiccloud-wg-stein-ptg-summary
[1]https://etherpad.openstack.org/p/BER-forum-public-cloud

On Tue, Sep 18, 2018 at 8:05 PM Tobias Rydberg <
tobias.rydb...@citynetwork.eu> wrote:

> Hi everyone,
>
> Don't forget that we have a meeting tomorrow at 0700 UTC at IRC channel
> #openstack-publiccloud.
>
> See you all there!
>
> Cheers,
> Tobias
>
> --
> Tobias Rydberg
> Senior Developer
> Twitter & IRC: tobberydberg
>
> www.citynetwork.eu | www.citycloud.com
>
> INNOVATION THROUGH OPEN IT INFRASTRUCTURE
> ISO 9001, 14001, 27001, 27015 & 27018 CERTIFIED
>
>
> ___
> User-committee mailing list
> user-commit...@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/user-committee
>


-- 
Zhipeng (Howard) Huang

Standard Engineer
IT Standard & Patent/IT Product Line
Huawei Technologies Co,. Ltd
Email: huangzhip...@huawei.com
Office: Huawei Industrial Base, Longgang, Shenzhen

(Previous)
Research Assistant
Mobile Ad-Hoc Network Lab, Calit2
University of California, Irvine
Email: zhipe...@uci.edu
Office: Calit2 Building Room 2402

OpenStack, OPNFV, OpenDaylight, OpenCompute Aficionado
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [election][tc]Question for candidates about global reachout

[Zhipeng Huang]

On Tue, Sep 18, 2018 at 8:06 AM Jeremy Stanley  wrote:

> This seems to completely miss the reasons I personally reject such
> platforms. I don't use proprietary tools or services for interacting
> with our community, I avoid relying on products from companies which
> attempt to track or share my location and activities for their own
> profit or to report them to various government agencies, and I have
> no interest in owning a "smart phone" (which some services such as
> wechat outright require). At least for me, the example rejection you
> proposed above is a miss on all counts...
>
> I am plenty capable of coping with any of the "personalities or
> social characters" I'm likely to encounter on those services (I'm
> quite certain IRC is where you're going to find some of the worst
> and *most* intolerable characters of any discussion medium). I also
> am accustomed to providing a near instant response to urgent
> requests in IRC, and at the same time don't feel particularly
> "pressured" to do so. And I _do_ use some social media: both IRC and
> mailing lists are in fact legitimate examples of social media. I'm
> really not even opposed to using other forms as long as they rely on
> open protocols and both the client _and_ server software are
> available under a free/libre open source license.
> --
> Jeremy Stanley
>

Jeremy, what I'm saying here, and also addressed in comments with the
related resolution patch, is that personality reasons are the ones that we
have to respect and no form of governance change could help solve the
problem. However other than that, we could always find a way to address the
issue for remedies, if we don't have a good answer now maybe we will have
sometime later.

Preference on  social tooling is something that the technical committee is
able to address, with isolation of usage of proprietary tools for certain
scenario and also strict policy on enforcing the open source communication
solutions we have today as the central ones the community will continue to
use. This is not an unsolvable problem given that we have a technical
committee, but personality issues are, no matter what governance instrument
we have.


-- 
Zhipeng (Howard) Huang

Standard Engineer
IT Standard & Patent/IT Product Line
Huawei Technologies Co,. Ltd
Email: huangzhip...@huawei.com
Office: Huawei Industrial Base, Longgang, Shenzhen

(Previous)
Research Assistant
Mobile Ad-Hoc Network Lab, Calit2
University of California, Irvine
Email: zhipe...@uci.edu
Office: Calit2 Building Room 2402

OpenStack, OPNFV, OpenDaylight, OpenCompute Aficionado
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [election][tc]Question for candidates about global reachout

[Zhipeng Huang]

Thanks Anne :)

On another side note, there has not been a (maybe I missed) good "no" vote
message I was looking for.

A good quality "no" message could something like this in my opinion (and
this is just one of many possibilities):

"Thanks for invitation but no I would not like to use social media apps
other than IRC. General social media apps are open to a more variety of
people than in IRC channels and there are personalities or social
characters that I found myself just cannot cope with. Moreover social media
apps demands instant response, or at least has the expectation for one, in
its nature and it would make me feel pressured all the time. So no thank
you I would not use social media in any form, however if you do have good
technical questions from the social apps, please feel free to relay to me
and I'm glad to help when I have the bandwidth"




On Tue, Sep 18, 2018 at 7:06 AM Anne Bertucio  wrote:

> I though I remember someone (annabelleB?) saying there were known issues
> (technical or otherwise) regarding the official channels spun up by the
> Foundation.
>
>
> Two separate issues that perhaps got mashed together :)
>
> Unofficial WeChat channels are limited to ~500 participants and are
> invite-only. That makes a few challenges for a community of our size (much
> more than 500!). Official subscription channels don’t have these
> limitations, but there’s a lengthy process to get one. It’s currently in
> progress (unfortunately I don’t think we have an ETA beyond “in progress”
> at this point—more than one month; less than six months?).
>
>
> Anne Bertucio
> OpenStack Foundation
> a...@openstack.org | irc: annabelleB
>
>
>
>
>
> On Sep 17, 2018, at 2:56 PM, Lance Bragstad  wrote:
>
>
>
> On Mon, Sep 17, 2018 at 1:42 PM Mohammed Naser 
> wrote:
>
>> Hi,
>>
>> On that note, is there any way to get an 'invite' onto those channels?
>>
>> Any information about the foundation side of things about the
>> 'official' channels?
>>
>
> I actually have a question about this as well. During the TC discussion
> last Friday there was representation from the Foundation in the room. I
> though I remember someone (annabelleB?) saying there were known issues
> (technical or otherwise) regarding the official channels spun up by the
> Foundation.
>
> Does anyone know what issues were being referred to here?
>
>
>>
>> Thanks,
>> Mohammed
>> On Mon, Sep 17, 2018 at 3:28 PM Samuel Cassiba  wrote:
>> >
>> > On Mon, Sep 17, 2018 at 6:58 AM Sylvain Bauza 
>> wrote:
>> > >
>> > >
>> > >
>> > > Le lun. 17 sept. 2018 à 15:32, Jeremy Stanley  a
>> écrit :
>> > >>
>> > >> On 2018-09-16 14:14:41 +0200 (+0200), Jean-philippe Evrard wrote:
>> > >> [...]
>> > >> > - What is the problem joining Wechat will solve (keeping in mind
>> the
>> > >> > language barrier)?
>> > >>
>> > >> As I understand it, the suggestion is that mere presence of project
>> > >> leadership in venues where this emerging subset of our community
>> > >> gathers would provide a strong signal that we support them and care
>> > >> about their experience with the software.
>> > >>
>> > >> > - Isn't this problem already solved for other languages with
>> > >> > existing initiatives like local ambassadors and i18n team? Why
>> > >> > aren't these relevant?
>> > >> [...]
>> > >>
>> > >> It seems like there are at least couple of factors at play here:
>> > >> first the significant number of users and contributors within
>> > >> mainland China compared to other regions (analysis suggests there
>> > >> were nearly as many contributors to the Rocky release from China as
>> > >> the USA), but second there may be facets of Chinese culture which
>> > >> make this sort of demonstrative presence a much stronger signal than
>> > >> it would be in other cultures.
>> > >>
>> > >> > - Pardon my ignorance here, what is the problem with email? (I
>> > >> > understand some chat systems might be blocked, I thought emails
>> > >> > would be fine, and the lowest common denominator).
>> > >>
>> > >> Someone in the TC room (forgive me, I don't recall who now, maybe
>> > >> Rico?) asserted that Chinese contributors generally only read the
>> > >> first message in any given thread (perhaps just looking for possible
>> > >> announcements?) and that if they _do_ attempt to read through some
>> > >> of the longer threads they don't participate in them because the
>> > >> discussion is presumed to be over and decisions final by the time
>> > >> they "reach the end" (I guess not realizing that it's perfectly fine
>> > >> to reply to a month-old discussion and try to help alter course on
>> > >> things if you have an actual concern?).
>> > >>
>> > >
>> > > While I understand the technical issues that could be due using IRC
>> in China, I still don't get why opening the gates and saying WeChat being
>> yet another official channel would prevent our community from fragmenting.
>> > >
>> > > Truly the usage of IRC is certainly questionable, but if we have
>> multiple ways to discuss, I just 

Re: [openstack-dev] [election][tc]Question for candidates about global reachout

[Zhipeng Huang]

Would like to see some updates on the foundation's official wechat group up
:)

On the other note, I would like to point out that this email is merely
asking who would be interested. The question about "dividing teams" and
such is addressed in https://review.openstack.org/602697 .


On Tue, Sep 18, 2018 at 5:57 AM Lance Bragstad  wrote:

>
>
> On Mon, Sep 17, 2018 at 1:42 PM Mohammed Naser 
> wrote:
>
>> Hi,
>>
>> On that note, is there any way to get an 'invite' onto those channels?
>>
>> Any information about the foundation side of things about the
>> 'official' channels?
>>
>
> I actually have a question about this as well. During the TC discussion
> last Friday there was representation from the Foundation in the room. I
> though I remember someone (annabelleB?) saying there were known issues
> (technical or otherwise) regarding the official channels spun up by the
> Foundation.
>
> Does anyone know what issues were being referred to here?
>
>
>>
>> Thanks,
>> Mohammed
>> On Mon, Sep 17, 2018 at 3:28 PM Samuel Cassiba  wrote:
>> >
>> > On Mon, Sep 17, 2018 at 6:58 AM Sylvain Bauza 
>> wrote:
>> > >
>> > >
>> > >
>> > > Le lun. 17 sept. 2018 à 15:32, Jeremy Stanley  a
>> écrit :
>> > >>
>> > >> On 2018-09-16 14:14:41 +0200 (+0200), Jean-philippe Evrard wrote:
>> > >> [...]
>> > >> > - What is the problem joining Wechat will solve (keeping in mind
>> the
>> > >> > language barrier)?
>> > >>
>> > >> As I understand it, the suggestion is that mere presence of project
>> > >> leadership in venues where this emerging subset of our community
>> > >> gathers would provide a strong signal that we support them and care
>> > >> about their experience with the software.
>> > >>
>> > >> > - Isn't this problem already solved for other languages with
>> > >> > existing initiatives like local ambassadors and i18n team? Why
>> > >> > aren't these relevant?
>> > >> [...]
>> > >>
>> > >> It seems like there are at least couple of factors at play here:
>> > >> first the significant number of users and contributors within
>> > >> mainland China compared to other regions (analysis suggests there
>> > >> were nearly as many contributors to the Rocky release from China as
>> > >> the USA), but second there may be facets of Chinese culture which
>> > >> make this sort of demonstrative presence a much stronger signal than
>> > >> it would be in other cultures.
>> > >>
>> > >> > - Pardon my ignorance here, what is the problem with email? (I
>> > >> > understand some chat systems might be blocked, I thought emails
>> > >> > would be fine, and the lowest common denominator).
>> > >>
>> > >> Someone in the TC room (forgive me, I don't recall who now, maybe
>> > >> Rico?) asserted that Chinese contributors generally only read the
>> > >> first message in any given thread (perhaps just looking for possible
>> > >> announcements?) and that if they _do_ attempt to read through some
>> > >> of the longer threads they don't participate in them because the
>> > >> discussion is presumed to be over and decisions final by the time
>> > >> they "reach the end" (I guess not realizing that it's perfectly fine
>> > >> to reply to a month-old discussion and try to help alter course on
>> > >> things if you have an actual concern?).
>> > >>
>> > >
>> > > While I understand the technical issues that could be due using IRC
>> in China, I still don't get why opening the gates and saying WeChat being
>> yet another official channel would prevent our community from fragmenting.
>> > >
>> > > Truly the usage of IRC is certainly questionable, but if we have
>> multiple ways to discuss, I just doubt we could prevent us to silo
>> ourselves between our personal usages.
>> > > Either we consider the new channels as being only for southbound
>> communication, or we envisage the possibility, as a community, to migrate
>> from IRC to elsewhere (I'm particulary not fan of the latter so I would
>> challenge this but I can understand the reasons)
>> > >
>> > > -Sylvain
>> > >
>> >
>> > Objectively, I don't see a way to endorse something other than IRC
>> > without some form of collective presence on more than just Wechat to
>> > keep the message intact. IRC is the official messaging platform, for
>> > whatever that's worth these days. However, at present, it makes less
>> > and less sense to explicitly eschew other outlets in favor. From a
>> > Chef OpenStack perspective, the common medium is, perhaps not
>> > unsurprising, code review. Everything else evolved over time to be
>> > southbound paths to the code, including most of the conversation
>> > taking place there as opposed to IRC.
>> >
>> > The continuation of this thread only confirms that there is already
>> > fragmentation in the community, and that people on each side of the
>> > void genuinely want to close that gap. At this point, the thing to do
>> > is prevent further fragmentation of the intent. It is, however, far
>> > easier to bikeshed over which platform of choice.
>> >
>> > At present, it 

Re: [openstack-dev] [election][tc]Question for candidates about global reachout

[Zhipeng Huang]

Great to see the momentum going ! :)

Another problem is that many people doesn't follow upstream so they are
oblivious about the new features and cool things had been done in every
cycle, and then all these types of half ass openstack trashing blog post
got shared in wechat moments dissing how openstack 2015 didn't help to
solve their 2018 problems

Glad to have Alex and Matt sign up on the Nova side :)

On Mon, Sep 17, 2018, 4:57 AM Alex Xu  wrote:

> I'm happy to be the translator or forwarder for the nova issue if you guys
> need(although, the nova team isn't happy with me now, also  i see it is not
> to my personal. I guess they won't be make me hard for other work I do.). I
> can see there are a lot of Chinese operators/users complain some issues,
> but they never send their feedback to the mail-list, this may due to the
> language, or people don't know the OpenSource culture in the China.(To be
> host, the OpenStack is first project, let a lot of developers to understand
> what is OpenSource, and how it is works. In the before, since the linux
> kernel is hard, really only few people in the China experience OpenSource).
>
>
>
>
> Matt Riedemann  于2018年9月16日周日 下午11:34写道：
>
>> On 9/15/2018 9:50 PM, Fred Li wrote:
>> > As a non-native English speaker, it is nice-to-have that some TC or BoD
>> > can stay in the local social media, like wechat group in China. But it
>> > is also very difficult for non-native Chinese speakers to stay find
>> > useful information in ton of Chinese chats.
>> > My thoughts (even I am not a TC candidate) on this is,
>> > 1. it is kind of you to stay in the local group.
>> > 2. if we know that you are in, we will say English if we want you to
>> notice.
>> > 3. since there is local OpenStack operation manager, hope he/she can
>> > identify some information and help to translate, or remind them to
>> > translate.
>> >
>> > My one cent.
>>
>> Is there a generic openstack group on wechat? Does one have to be
>> invited to it? Is there a specific openstack/nova group on wechat? I'm
>> on wechat anyway so I don't mind being in those groups if someone wants
>> to reach out.
>>
>> --
>>
>> Thanks,
>>
>> Matt
>>
>> __
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe:
>> openstack-dev-requ...@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-requ...@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-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [tc][uc]Community Wide Long Term Goals

[Zhipeng Huang]

Just a quick update, the execution part of the proposal has been added in
patch-2 , so if you have the similar concern shared in Matt's open letter ,
please help review and comment.

On Fri, Sep 14, 2018, 5:51 PM Zhipeng Huang  wrote:

> Hi,
>
> Based upon the discussion we had at the TC session in the afternoon, I'm
> starting to draft a patch to add long term goal mechanism into governance.
> It is by no means a complete solution at the moment (still have not thought
> through the execution method yet to make sure the outcome), but feel free
> to provide your feedback at https://review.openstack.org/#/c/602799/ .
>
> --
> Zhipeng (Howard) Huang
>
> Standard Engineer
> IT Standard & Patent/IT Product Line
> Huawei Technologies Co,. Ltd
> Email: huangzhip...@huawei.com
> Office: Huawei Industrial Base, Longgang, Shenzhen
>
> (Previous)
> Research Assistant
> Mobile Ad-Hoc Network Lab, Calit2
> University of California, Irvine
> Email: zhipe...@uci.edu
> Office: Calit2 Building Room 2402
>
> OpenStack, OPNFV, OpenDaylight, OpenCompute Aficionado
>
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [election][tc]Question for candidates about global reachout

[Zhipeng Huang]

Ya I think the whole point here (the question per se )is just to gauge if
TC Candidates are willing to engage with regional developer in a way that
is best fitting for that region.

It surly will take other measures to make this entire effort work . On that
I totally agree with you that there should be ambassadors to help
facilitate the discussion, and the end goal is always to go to upstream
instead of the convo ending in local or downstream.


On Sat, Sep 15, 2018, 9:52 AM Matt Riedemann  wrote:

> On 9/14/2018 1:52 PM, Zhipeng Huang wrote:
> > This is a joint question from mnaser and me :)
> >
> > For the candidates who are running for tc seats, please reply to this
> > email to indicate if you are open to use certain social media app in
> > certain region (like Wechat in China, Line in Japan, etc.), in order to
> > reach out to the OpenStack developers in that region and help them to
> > connect to the upstream community as well as answering questions or
> > other activities that will help. (sorry for the long sentence ... )
> >
> > Rico and I already sign up for Wechat communication for sure :)
>
> Having had some experience with WeChat, I can't imagine I'd be very
> useful in a nova channel in WeChat since the majority of people in that
> group wouldn't be speaking English so I wouldn't be of much help, unless
> someone directly asked me a question in English. I realize the double
> standard here with expecting non-native English speakers to show up in
> the #openstack-nova freenode IRC channel to ask questions. It's
> definitely a hard problem when people simply can't speak the same
> language and I don't have a great solution. Probably the best common
> solution we have is having more people across time zones and language
> barriers engaging in more discussion in the mailing list (and Gerrit
> reviews of course). So maybe that means if you're in WeChat and someone
> is blocked or has a bigger question for a specific project team,
> encourage them to send an email to the dev ML - but that requires
> ambassadors to be in WeChat channels to make that suggestion. I think of
> this like working with product teams within your own company. Lots of
> those people aren't active upstream contributors and to avoid being the
> middleman (and thus bottleneck) for all communication between upstream
> and downstream teams, I've encouraged the downstream folk to send an
> email upstream to start a discussion.
>
> --
>
> Thanks,
>
> Matt
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@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-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [tc][uc]Community Wide Long Term Goals

[Zhipeng Huang]

Hi,

Based upon the discussion we had at the TC session in the afternoon, I'm
starting to draft a patch to add long term goal mechanism into governance.
It is by no means a complete solution at the moment (still have not thought
through the execution method yet to make sure the outcome), but feel free
to provide your feedback at https://review.openstack.org/#/c/602799/ .

-- 
Zhipeng (Howard) Huang

Standard Engineer
IT Standard & Patent/IT Product Line
Huawei Technologies Co,. Ltd
Email: huangzhip...@huawei.com
Office: Huawei Industrial Base, Longgang, Shenzhen

(Previous)
Research Assistant
Mobile Ad-Hoc Network Lab, Calit2
University of California, Irvine
Email: zhipe...@uci.edu
Office: Calit2 Building Room 2402

OpenStack, OPNFV, OpenDaylight, OpenCompute Aficionado
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [election][tc]Question for candidates about global reachout

[Zhipeng Huang]

This is a joint question from mnaser and me :)

For the candidates who are running for tc seats, please reply to this email
to indicate if you are open to use certain social media app in certain
region (like Wechat in China, Line in Japan, etc.), in order to reach out
to the OpenStack developers in that region and help them to connect to the
upstream community as well as answering questions or other activities that
will help. (sorry for the long sentence ... )

Rico and I already sign up for Wechat communication for sure :)

-- 
Zhipeng (Howard) Huang

Standard Engineer
IT Standard & Patent/IT Product Line
Huawei Technologies Co,. Ltd
Email: huangzhip...@huawei.com
Office: Huawei Industrial Base, Longgang, Shenzhen

(Previous)
Research Assistant
Mobile Ad-Hoc Network Lab, Calit2
University of California, Irvine
Email: zhipe...@uci.edu
Office: Calit2 Building Room 2402

OpenStack, OPNFV, OpenDaylight, OpenCompute Aficionado
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [tc]Global Reachout Proposal

[Zhipeng Huang]

Hi all,

Follow up the diversity discussion we had in the tc session this morning
[0], I've proposed a resolution on facilitating technical community in
large to engage in global reachout for OpenStack more efficiently.

Your feedbacks are welcomed. Whether this should be a new resolution or not
at the end of the day, this is a conversation worthy to have.

[0] https://review.openstack.org/602697

-- 
Zhipeng (Howard) Huang

Standard Engineer
IT Standard & Patent/IT Product Line
Huawei Technologies Co,. Ltd
Email: huangzhip...@huawei.com
Office: Huawei Industrial Base, Longgang, Shenzhen

(Previous)
Research Assistant
Mobile Ad-Hoc Network Lab, Calit2
University of California, Irvine
Email: zhipe...@uci.edu
Office: Calit2 Building Room 2402

OpenStack, OPNFV, OpenDaylight, OpenCompute Aficionado
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Openstack-sigs] Open letter/request to TC candidates (and existing elected officials)

[Zhipeng Huang]

On Thu, Sep 13, 2018 at 10:15 AM Fox, Kevin M  wrote:

> How about stated this way,
> Its the tc's responsibility to get it done. Either by delegating the
> activity, or by doing it themselves. But either way, it needs to get done.
> Its a ball that has been dropped too much in OpenStacks history. If no one
> is ultimately responsible, balls will keep getting dropped.
>
> Thanks,
> Kevin
>

+1 Kevin
-- 
Zhipeng (Howard) Huang

Standard Engineer
IT Standard & Patent/IT Product Line
Huawei Technologies Co,. Ltd
Email: huangzhip...@huawei.com
Office: Huawei Industrial Base, Longgang, Shenzhen

(Previous)
Research Assistant
Mobile Ad-Hoc Network Lab, Calit2
University of California, Irvine
Email: zhipe...@uci.edu
Office: Calit2 Building Room 2402

OpenStack, OPNFV, OpenDaylight, OpenCompute Aficionado
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Openstack-sigs] Open letter/request to TC candidates (and existing elected officials)

[Zhipeng Huang]

On Wed, Sep 12, 2018 at 3:55 PM Jeremy Stanley  wrote:

> On 2018-09-12 09:47:27 -0600 (-0600), Matt Riedemann wrote:
> [...]
> > So I encourage all elected TC members to work directly with the
> > various SIGs to figure out their top issue and then work on
> > managing those deliverables across the community because the TC is
> > particularly well suited to do so given the elected position.
> [...]
>
> I almost agree with you. I think the OpenStack TC members should be
> actively engaged in recruiting and enabling interested people in the
> community to do those things, but I don't think such work should be
> solely the domain of the TC and would hate to give the impression
> that you must be on the TC to have such an impact.
> --
> Jeremy Stanley
>

Jeremy, this is not to say that one must be on the TC to have such an
impact, it is that TC has the duty more than anyone else to get this
specific cross-project goal done. I would even argue it is not the job
description of TC to enable/recruit, but to just do it.

-- 
Zhipeng (Howard) Huang

Standard Engineer
IT Standard & Patent/IT Product Line
Huawei Technologies Co,. Ltd
Email: huangzhip...@huawei.com
Office: Huawei Industrial Base, Longgang, Shenzhen

(Previous)
Research Assistant
Mobile Ad-Hoc Network Lab, Calit2
University of California, Irvine
Email: zhipe...@uci.edu
Office: Calit2 Building Room 2402

OpenStack, OPNFV, OpenDaylight, OpenCompute Aficionado
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Openstack-sigs] Open letter/request to TC candidates (and existing elected officials)

[Zhipeng Huang]

Well Public Cloud WG has prepared the ammo as you know and to discuss with
TC on Friday :)

A hundred percent with you on this matter.

On Wed, Sep 12, 2018 at 9:47 AM Matt Riedemann  wrote:

> Rather than take a tangent on Kristi's candidacy thread [1], I'll bring
> this up separately.
>
> Kristi said:
>
> "Ultimately, this list isn’t exclusive and I’d love to hear your and
> other people's opinions about what you think the I should focus on."
>
> Well since you asked...
>
> Some feedback I gave to the public cloud work group yesterday was to get
> their RFE/bug list ranked from the operator community (because some of
> the requests are not exclusive to public cloud), and then put pressure
> on the TC to help project manage the delivery of the top issue. I would
> like all of the SIGs to do this. The upgrades SIG should rank and
> socialize their #1 issue that needs attention from the developer
> community - maybe that's better upgrade CI testing for deployment
> projects, maybe it's getting the pre-upgrade checks goal done for Stein.
> The UC should also be doing this; maybe that's the UC saying, "we need
> help on closing feature gaps in openstack client and/or the SDK". I
> don't want SIGs to bombard the developers with *all* of their
> requirements, but I want to get past *talking* about the *same* issues
> *every* time we get together. I want each group to say, "this is our top
> issue and we want developers to focus on it." For example, the extended
> maintenance resolution [2] was purely birthed from frustration about
> talking about LTS and stable branch EOL every time we get together. It's
> also the responsibility of the operator and user communities to weigh in
> on proposed release goals, but the TC should be actively trying to get
> feedback from those communities about proposed goals, because I bet
> operators and users don't care about mox removal [3].
>
> I want to see the TC be more of a cross-project project management
> group, like a group of Ildikos and what she did between nova and cinder
> to get volume multi-attach done, which took persistent supervision to
> herd the cats and get it delivered. Lance is already trying to do this
> with unified limits. Doug is doing this with the python3 goal. I want my
> elected TC members to be pushing tangible technical deliverables forward.
>
> I don't find any value in the TC debating ad nauseam about visions and
> constellations and "what is openstack?". Scope will change over time
> depending on who is contributing to openstack, we should just accept
> this. And we need to realize that if we are failing to deliver value to
> operators and users, they aren't going to use openstack and then "what
> is openstack?" won't matter because no one will care.
>
> So I encourage all elected TC members to work directly with the various
> SIGs to figure out their top issue and then work on managing those
> deliverables across the community because the TC is particularly well
> suited to do so given the elected position. I realize political and
> bureaucratic "how should openstack deal with x?" things will come up,
> but those should not be the priority of the TC. So instead of
> philosophizing about things like, "should all compute agents be in a
> single service with a REST API" for hours and hours, every few months -
> immediately ask, "would doing that get us any closer to achieving top
> technical priority x?" Because if not, or it's so fuzzy in scope that no
> one sees the way forward, document a decision and then drop it.
>
> [1]
>
> http://lists.openstack.org/pipermail/openstack-dev/2018-September/134490.html
> [2]
>
> https://governance.openstack.org/tc/resolutions/20180301-stable-branch-eol.html
> [3] https://governance.openstack.org/tc/goals/rocky/mox_removal.html
>
> --
>
> Thanks,
>
> Matt
>
> ___
> openstack-sigs mailing list
> openstack-s...@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-sigs
>


-- 
Zhipeng (Howard) Huang

Standard Engineer
IT Standard & Patent/IT Product Line
Huawei Technologies Co,. Ltd
Email: huangzhip...@huawei.com
Office: Huawei Industrial Base, Longgang, Shenzhen

(Previous)
Research Assistant
Mobile Ad-Hoc Network Lab, Calit2
University of California, Irvine
Email: zhipe...@uci.edu
Office: Calit2 Building Room 2402

OpenStack, OPNFV, OpenDaylight, OpenCompute Aficionado
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [cyborg]Day 2 Arrangement Reminder

[Zhipeng Huang]

Hi Team,

Today the Cyborg session will concentrate on two items that were not
covered yesterday: neutron-cyborg interaction and general device mgmt.
Since I will be mostly at the Public Cloud WG session, Sundar will help to
lead the discussion, and our Stein PTL Li Liu will host the online ZOOM
conference. You are also welcomed to propose new topics.

Our team photo is schedule 11:30 so let's gather at the lobby front around
11:25 :)

All the information could be found at
https://etherpad.openstack.org/p/cyborg-ptg-stein .

-- 
Zhipeng (Howard) Huang

Standard Engineer
IT Standard & Patent/IT Product Line
Huawei Technologies Co,. Ltd
Email: huangzhip...@huawei.com
Office: Huawei Industrial Base, Longgang, Shenzhen

(Previous)
Research Assistant
Mobile Ad-Hoc Network Lab, Calit2
University of California, Irvine
Email: zhipe...@uci.edu
Office: Calit2 Building Room 2402

OpenStack, OPNFV, OpenDaylight, OpenCompute Aficionado
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [election] [tc] TC candidacy

[Zhipeng Huang]

Well nova-cyborg is surely on the top-priority for OpenStack cross-project
collaboration. The two initiatives I mentioned is more in the field of
cross-community.

I think I didn't elaborate on how the TC role fit in this picture. For TC I
think it is important to be able to help on the cross community
collaboration, one community is intimidating enough, let alone venture into
totally different communities.

With that said, other than the two directions that I will personally
involve myself with, I will also help other cross community
ideas/initiatives to build relationship and get work done. I guess it is
more convincing when you as a TC member have actually skin in the game in
cross-community development.

So yes individual team will probably the best ones to drive such
collaborations, but it would also be nice to have TC lend a hand when there
is need :)

On Fri, Sep 7, 2018 at 10:17 PM Matt Riedemann  wrote:

> On 9/7/2018 8:54 AM, Zhipeng Huang wrote:
> > One is related to the cyborg project where the team is working to build
> > the open heterogenous resource mgmt platform. I would like to extend
> > this mission over to kubernetes, which currently lack of such component
> > and could benefit hugely from our work here in OpenStack. There are also
> > other communities like OPNFV where the edge cloud project, the C-RAN
> > project and Rocket project will be integrating and testing cyborg, as
> > well as ONNX where AI models will meet the resource models we defined in
> > Cyborg for NPUs and GPUs and FPGAs and whatever hardware should be
> chosen.
>
> I'd like to actually see some progress made on cyborg/nova integration
> before we get our hopes up about cyborg/something completely outside of
> openstack integration, but that's my biased view on it from being a nova
> person. See [1] for context from a discussion yesterday. I don't really
> know how the TC drives this more than the cyborg team themselves, but OK.
>
> [1]
>
> http://eavesdrop.openstack.org/meetings/nova/2018/nova.2018-09-06-14.00.log.html#l-120
>
> --
>
> Thanks,
>
> Matt
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>


-- 
Zhipeng (Howard) Huang

Standard Engineer
IT Standard & Patent/IT Product Line
Huawei Technologies Co,. Ltd
Email: huangzhip...@huawei.com
Office: Huawei Industrial Base, Longgang, Shenzhen

(Previous)
Research Assistant
Mobile Ad-Hoc Network Lab, Calit2
University of California, Irvine
Email: zhipe...@uci.edu
Office: Calit2 Building Room 2402

OpenStack, OPNFV, OpenDaylight, OpenCompute Aficionado
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [election] [tc] TC candidacy

[Zhipeng Huang]

Thx Matt,

I think as I described in the candidacy patch, there two specific areas
that I would like to do the cross-community collaboration.

One is related to the cyborg project where the team is working to build the
open heterogenous resource mgmt platform. I would like to extend this
mission over to kubernetes, which currently lack of such component and
could benefit hugely from our work here in OpenStack. There are also other
communities like OPNFV where the edge cloud project, the C-RAN project and
Rocket project will be integrating and testing cyborg, as well as ONNX
where AI models will meet the resource models we defined in Cyborg for NPUs
and GPUs and FPGAs and whatever hardware should be chosen.

The other one is policy which related to the Kubernetes Policy WG I'm
leading and the CNCF Security WG which is under voting from ToC to take
shape. We have great policy in code implementation in Keystone and I'm keen
on investigating on how should that impact Kubernetes or Istio or SPIFEE
when we stack them up.

Of course there are other areas that i'm also working on which bridges
communities, one such example is the cloud ledger idea proposed for public
cloud wg involves collaboration with Ethereum Classic community, and
hopefully Hyperledger and others in the near future. However this is a long
term effort compared to the above mentioned two aspects.

Hope that answers the question :)

On Fri, Sep 7, 2018 at 9:34 PM Matt Riedemann  wrote:

> On 9/5/2018 6:49 PM, Zhipeng Huang wrote:
> > I found that most of my statement for my last ran is still valid today
> > [0][1]. I want to build strong cross-community collaboration, best
> > practices for project level governance and more innovations for
> OpenStack.
>
> As I asked Rico, are there specific cross-community initiatives or
> deliverables you plan on working on, or just having open dialog? Because
> the latter doesn't mean much to me personally. If the former, can you
> point some out?
>
> --
>
> Thanks,
>
> Matt
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>


-- 
Zhipeng (Howard) Huang

Standard Engineer
IT Standard & Patent/IT Product Line
Huawei Technologies Co,. Ltd
Email: huangzhip...@huawei.com
Office: Huawei Industrial Base, Longgang, Shenzhen

(Previous)
Research Assistant
Mobile Ad-Hoc Network Lab, Calit2
University of California, Irvine
Email: zhipe...@uci.edu
Office: Calit2 Building Room 2402

OpenStack, OPNFV, OpenDaylight, OpenCompute Aficionado
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [publiccloud-wg]PTG session prep

[Zhipeng Huang]

Hi Folks,

For those of you are interested in the openstack public cloud, please take
a look at the etherpad for our agenda[0] , you are more than welcomed to
suggest/add new topics !

[0] https://etherpad.openstack.org/p/publiccloud-wg-stein-ptg

-- 
Zhipeng (Howard) Huang

Standard Engineer
IT Standard & Patent/IT Product Line
Huawei Technologies Co,. Ltd
Email: huangzhip...@huawei.com
Office: Huawei Industrial Base, Longgang, Shenzhen

(Previous)
Research Assistant
Mobile Ad-Hoc Network Lab, Calit2
University of California, Irvine
Email: zhipe...@uci.edu
Office: Calit2 Building Room 2402

OpenStack, OPNFV, OpenDaylight, OpenCompute Aficionado
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [cyborg]Denver PTG arrangements

[Zhipeng Huang]

Hi Team,

As we discussed at yesterday's team meeting, please find our schedule for
PTG at https://etherpad.openstack.org/p/cyborg-ptg-stein , team dinner
information also available :)

-- 
Zhipeng (Howard) Huang

Standard Engineer
IT Standard & Patent/IT Product Line
Huawei Technologies Co,. Ltd
Email: huangzhip...@huawei.com
Office: Huawei Industrial Base, Longgang, Shenzhen

(Previous)
Research Assistant
Mobile Ad-Hoc Network Lab, Calit2
University of California, Irvine
Email: zhipe...@uci.edu
Office: Calit2 Building Room 2402

OpenStack, OPNFV, OpenDaylight, OpenCompute Aficionado
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [election] [tc] TC candidacy

[Zhipeng Huang]

Hi all,

I ran for TC in the last cycle and I guess you can find out more
information on the candidacy patch [0], so I won't copy and paste that long
article here again :)

I found that most of my statement for my last ran is still valid today
[0][1]. I want to build strong cross-community collaboration, best
practices for project level governance and more innovations for OpenStack.

Hopefully second time is a charm and I could bring something fresh and
diverse thinking to the group :)

[0] https://review.openstack.org/#/c/600279/
[1] https://hannibalhuang.github.io/2018/04/16/i-didn't-build-it/
-- 
Zhipeng (Howard) Huang

Standard Engineer
IT Standard & Patent/IT Product Line
Huawei Technologies Co,. Ltd
Email: huangzhip...@huawei.com
Office: Huawei Industrial Base, Longgang, Shenzhen

(Previous)
Research Assistant
Mobile Ad-Hoc Network Lab, Calit2
University of California, Irvine
Email: zhipe...@uci.edu
Office: Calit2 Building Room 2402

OpenStack, OPNFV, OpenDaylight, OpenCompute Aficionado
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [cyborg]Team Weekly Meeting 2018.08.08

[Zhipeng Huang]

Hi Team,

We are rushing towards the end of Rocky cycle and let's use the meeting to
sync up with any important features still on the fly.

starting UTC1400 at #openstack-cyborg, as usual

-- 
Zhipeng (Howard) Huang

Standard Engineer
IT Standard & Patent/IT Product Line
Huawei Technologies Co,. Ltd
Email: huangzhip...@huawei.com
Office: Huawei Industrial Base, Longgang, Shenzhen

(Previous)
Research Assistant
Mobile Ad-Hoc Network Lab, Calit2
University of California, Irvine
Email: zhipe...@uci.edu
Office: Calit2 Building Room 2402

OpenStack, OPNFV, OpenDaylight, OpenCompute Aficionado
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [publiccloud-wg] Asia-EU friendly meeting today

[Zhipeng Huang]

Hi team,

A kind reminder for the UTC 7:00 meeting today, please do remember to
register yourself to irc due to new channel policy.
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [cyborg]Stepping down (but stick around)

[Zhipeng Huang]

Hi Team,

For those of you who has been around since the "Nomad" time, you know how a
terrific journey we have come along together. A pure idea, through
community discussion and development, morphed into a project who is rapidly
growing and gaining industry attentions.

It is my privilege to serve as Cyborg's project's PTL for two cycles and I
hope for all of my inefficiency and sometimes incapability as a tech lead,
I did help the project grew both in development and governance (thank you
for putting up with me btw :) ). We got help from the Nova team, release
team, TC, Scientific SIG and other teams constantly, and we could not be
where we are now without these hand-holdings.

Although we have been suffering considerably high core reviewer fade out
rate, we keep have new strong core reviewers coming in. This is what makes
me proud and happy the most, and also why I'm comfortable with the decision
of non-candidacy in Stein. A great open source project, should do without
any specific leader, and keep grow organically. This is what I have been
hoping for Cyborg to achieve.

Hence I want to nominate Li Liu to be a candidate of PTL for Cyborg project
in Stein cycle. Li Liu has been joining Cyborg development since very early
stage and contributed a lot important work: deployable db design, metadata
standardization, FPGA programming support, etc. As an expert both in FPGA
synthesis as well as software development for OpenStack, I think Li Liu, or
Uncle Li as we nicknamed him, is the best choice we should have for S
release.

I would like to emphasize that this does not mean I have done with Cyborg
project, on the contrary I will be spending more time to build a great
ecosystem for Cyborg project. We have four target areas (AI, NFV, Edge,
HPC) and it will be an even more amazing journey in front of us.

Keep up the good work folks, and let's work even harder.

-- 
Zhipeng (Howard) Huang

Standard Engineer
IT Standard & Patent/IT Product Line
Huawei Technologies Co,. Ltd
Email: huangzhip...@huawei.com
Office: Huawei Industrial Base, Longgang, Shenzhen

(Previous)
Research Assistant
Mobile Ad-Hoc Network Lab, Calit2
University of California, Irvine
Email: zhipe...@uci.edu
Office: Calit2 Building Room 2402

OpenStack, OPNFV, OpenDaylight, OpenCompute Aficionado
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [publiccloud-wg]New Meeting Time Starting This Week

[Zhipeng Huang]

Hi Folks,

As indicated in https://review.openstack.org/#/c/584389/, PCWG is moving
towards a tick-tock meeting arrangements to better accommodate participants
along the globe.

For even weeks starting this Wed, we will have a new meeting time on
UTC0700. For odd weeks we will remain for the UTC1400 time slot.

Look forward to meet you all at #openstack-publiccloud on Wed !

-- 
Zhipeng (Howard) Huang

Standard Engineer
IT Standard & Patent/IT Product Line
Huawei Technologies Co,. Ltd
Email: huangzhip...@huawei.com
Office: Huawei Industrial Base, Longgang, Shenzhen

(Previous)
Research Assistant
Mobile Ad-Hoc Network Lab, Calit2
University of California, Irvine
Email: zhipe...@uci.edu
Office: Calit2 Building Room 2402

OpenStack, OPNFV, OpenDaylight, OpenCompute Aficionado
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [cyborg]Nominate Zhenghao Wang as new core reviewer

[Zhipeng Huang]

Hi Team,

If you have been closely part of the rocky crazy development process, then
you know Zhenghao :) Zhenghao is an open source engineer from Lenovo and
has been very active in Cyborg project in Rocky cycle. He has helped
finished os-acc lib setup, worked with coco to demonstrate the first ever
working Cyborg demo at Vancouver Summit, and lead on the GPU driver
development as well as many other critical patches at the moment.

His stats could be found at [0] and [1].

As part of the tradition, please feedback any of your concern you might
have for this nomination, if there is no objection the nomination will go
into effect next Monday.

[0] http://stackalytics.com/?module=cyborg-group
[1]
https://review.openstack.org/#/q/project:openstack/cyborg+owner:%22wangzhh+%253Cwangzh21%2540lenovo.com%253E%22


-- 
Zhipeng (Howard) Huang

Standard Engineer
IT Standard & Patent/IT Product Line
Huawei Technologies Co,. Ltd
Email: huangzhip...@huawei.com
Office: Huawei Industrial Base, Longgang, Shenzhen

(Previous)
Research Assistant
Mobile Ad-Hoc Network Lab, Calit2
University of California, Irvine
Email: zhipe...@uci.edu
Office: Calit2 Building Room 2402

OpenStack, OPNFV, OpenDaylight, OpenCompute Aficionado
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [cyborg]Weekly Team Meeting 2018.07.11

[Zhipeng Huang]

Hi Team,

Weekly meeting as usual starting UTC1400 at #openstack-cyborg, since
holiday is over, let's focus on getting Rocky features done :)

-- 
Zhipeng (Howard) Huang

Standard Engineer
IT Standard & Patent/IT Product Line
Huawei Technologies Co,. Ltd
Email: huangzhip...@huawei.com
Office: Huawei Industrial Base, Longgang, Shenzhen

(Previous)
Research Assistant
Mobile Ad-Hoc Network Lab, Calit2
University of California, Irvine
Email: zhipe...@uci.edu
Office: Calit2 Building Room 2402

OpenStack, OPNFV, OpenDaylight, OpenCompute Aficionado
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [cyborg]Weekly Team Meeting 2018.07.04

[Zhipeng Huang]

Hi Team,

We will have our weekly meeting as usual at #openstack-cyborg starting
UTC1400. The main focus is to align the development status.

-- 
Zhipeng (Howard) Huang

Standard Engineer
IT Standard & Patent/IT Product Line
Huawei Technologies Co,. Ltd
Email: huangzhip...@huawei.com
Office: Huawei Industrial Base, Longgang, Shenzhen

(Previous)
Research Assistant
Mobile Ad-Hoc Network Lab, Calit2
University of California, Irvine
Email: zhipe...@uci.edu
Office: Calit2 Building Room 2402

OpenStack, OPNFV, OpenDaylight, OpenCompute Aficionado
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [cyborg]Weekly Team Meeting 2018.06.20

[Zhipeng Huang]

Hi Team,

Weekly meeting as usual starting UTC1400 at #openstack-cyborg

Initial agenda:

1. Rocky task assignment confirmation
2. os-acc discussion

-- 
Zhipeng (Howard) Huang

Standard Engineer
IT Standard & Patent/IT Product Line
Huawei Technologies Co,. Ltd
Email: huangzhip...@huawei.com
Office: Huawei Industrial Base, Longgang, Shenzhen

(Previous)
Research Assistant
Mobile Ad-Hoc Network Lab, Calit2
University of California, Irvine
Email: zhipe...@uci.edu
Office: Calit2 Building Room 2402

OpenStack, OPNFV, OpenDaylight, OpenCompute Aficionado
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [cyborg]Team Weekly Meeting 2018.06.13

[Zhipeng Huang]

Hi Team,

Kind reminder for the team meeting today about 30 mins later at
#openstack-cyborg .

-- 
Zhipeng (Howard) Huang

Standard Engineer
IT Standard & Patent/IT Product Line
Huawei Technologies Co,. Ltd
Email: huangzhip...@huawei.com
Office: Huawei Industrial Base, Longgang, Shenzhen

(Previous)
Research Assistant
Mobile Ad-Hoc Network Lab, Calit2
University of California, Irvine
Email: zhipe...@uci.edu
Office: Calit2 Building Room 2402

OpenStack, OPNFV, OpenDaylight, OpenCompute Aficionado
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Release-job-failures][cyborg][release] Pre-release of openstack/cyborg failed

[Zhipeng Huang]

thx guys , patch has been submitted at

https://review.openstack.org/574927

On Wed, Jun 13, 2018 at 8:09 AM Clark Boylan  wrote:

> On Tue, Jun 12, 2018, at 4:59 PM, Sean McGinnis wrote:
> > On 06/12/2018 06:01 PM, Zhipeng Huang wrote:
> > > Hi Doug,
> > >
> > > Thanks for raising this, we will check it out
> > >
> >
> > Clark was sharped eyed enough to point out that setuptools does not
> > accept regexes for
> > data files. So it would appear this:
> >
> > https://git.openstack.org/cgit/openstack/cyborg/tree/setup.cfg#n31
> >
> > Needs to be changed to explicitly list each file that is needed.
> >
> > Hope that helps.
> >
> > Sean
>
> I thought data_files was a setuptools thing but on further reading it
> appears to be PBR. And reading the PBR docs trailing globs should be
> supported. Reading the code I think PBR expects the entire data_file spec
> on one line so that you end up with 'foo = bar/*' instead of 'foo =\n
> bar/*'. This is likely a bug that should be fixed.
>
> To workaround this you can use 'etc/cyborg/rootwrap.d =
> etc/cyborg/rootwrap.d/*' all on one line in your config.
>
> Clark
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>


-- 
Zhipeng (Howard) Huang

Standard Engineer
IT Standard & Patent/IT Product Line
Huawei Technologies Co,. Ltd
Email: huangzhip...@huawei.com
Office: Huawei Industrial Base, Longgang, Shenzhen

(Previous)
Research Assistant
Mobile Ad-Hoc Network Lab, Calit2
University of California, Irvine
Email: zhipe...@uci.edu
Office: Calit2 Building Room 2402

OpenStack, OPNFV, OpenDaylight, OpenCompute Aficionado
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Release-job-failures][cyborg][release] Pre-release of openstack/cyborg failed

[Zhipeng Huang]

Hi Doug,

Thanks for raising this, we will check it out

On Wed, Jun 13, 2018 at 6:32 AM Doug Hellmann  wrote:

> Excerpts from zuul's message of 2018-06-12 21:57:02 +:
> > Build failed.
> >
> > - release-openstack-python
> http://logs.openstack.org/2c/2ca19224a22541ceccf74c6f760ee40a2c90fed2/pre-release/release-openstack-python/124b5be/
> : FAILURE in 6m 45s
> > - announce-release announce-release : SKIPPED
> > - propose-update-constraints propose-update-constraints : SKIPPED
> >
>
> The cyborg milestone 2 release failed due to a packaging error.
>
>   error: can't copy 'etc/cyborg/rootwrap.d/*': doesn't exist or not a
> regular file
>
>
> http://logs.openstack.org/2c/2ca19224a22541ceccf74c6f760ee40a2c90fed2/pre-release/release-openstack-python/124b5be/job-output.txt.gz#_2018-06-12_21_55_33_679298
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>


-- 
Zhipeng (Howard) Huang

Standard Engineer
IT Standard & Patent/IT Product Line
Huawei Technologies Co,. Ltd
Email: huangzhip...@huawei.com
Office: Huawei Industrial Base, Longgang, Shenzhen

(Previous)
Research Assistant
Mobile Ad-Hoc Network Lab, Calit2
University of California, Irvine
Email: zhipe...@uci.edu
Office: Calit2 Building Room 2402

OpenStack, OPNFV, OpenDaylight, OpenCompute Aficionado
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [cyborg] [nova] Cyborg quotas

[Zhipeng Huang]

Hi Blair,

Sorry for the late reply, could you elaborate more on the proxy driver idea
?

On Mon, May 21, 2018 at 4:05 PM, Blair Bethwaite 
wrote:

> (Please excuse the top-posting)
>
> The other possibility is that the Cyborg managed devices are plumbed in
> via IP in guest network space. Then "attach" isn't so much a Nova problem
> as a Neutron one - probably similar to Manila.
>
> Has the Cyborg team considered a RESTful-API proxy driver, i.e., something
> that wraps a vendor-specific accelerator service and makes it friendly to a
> multi-tenant OpenStack cloud? Quantum co-processors might be a compelling
> example which fit this model.
>
> Cheers,
>
>
> On Sun., 20 May 2018, 23:28 Chris Friesen, 
> wrote:
>
>> On 05/19/2018 05:58 PM, Blair Bethwaite wrote:
>> > G'day Jay,
>> >
>> > On 20 May 2018 at 08:37, Jay Pipes  wrote:
>> >> If it's not the VM or baremetal machine that is using the accelerator,
>> what
>> >> is?
>> >
>> > It will be a VM or BM, but I don't think accelerators should be tied
>> > to the life of a single instance if that isn't technically necessary
>> > (i.e., they are hot-pluggable devices). I can see plenty of scope for
>> > use-cases where Cyborg is managing devices that are accessible to
>> > compute infrastructure via network/fabric (e.g. rCUDA or dedicated
>> > PCIe fabric). And even in the simple pci passthrough case (vfio or
>> > mdev) it isn't hard to imagine use-cases for workloads that only need
>> > an accelerator sometimes.
>>
>> Currently nova only supports attach/detach of volumes and network
>> interfaces.
>> Is Cyborg looking to implement new Compute API operations to support hot
>> attach/detach of various types of accelerators?
>>
>> Chris
>>
>>
>>
>> 
>> __
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe: openstack-dev-requ...@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-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>


-- 
Zhipeng (Howard) Huang

Standard Engineer
IT Standard & Patent/IT Product Line
Huawei Technologies Co,. Ltd
Email: huangzhip...@huawei.com
Office: Huawei Industrial Base, Longgang, Shenzhen

(Previous)
Research Assistant
Mobile Ad-Hoc Network Lab, Calit2
University of California, Irvine
Email: zhipe...@uci.edu
Office: Calit2 Building Room 2402

OpenStack, OPNFV, OpenDaylight, OpenCompute Aficionado
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [cyborg]Weekly Team Meeting 2018.06.06

[Zhipeng Huang]

Hi Team,

let's resume the team meeting, at today's meeting we need to make decisions
on all Rocky critical specs in order to meet MS2 deadline.

-- 
Zhipeng (Howard) Huang

Standard Engineer
IT Standard & Patent/IT Product Line
Huawei Technologies Co,. Ltd
Email: huangzhip...@huawei.com
Office: Huawei Industrial Base, Longgang, Shenzhen

(Previous)
Research Assistant
Mobile Ad-Hoc Network Lab, Calit2
University of California, Irvine
Email: zhipe...@uci.edu
Office: Calit2 Building Room 2402

OpenStack, OPNFV, OpenDaylight, OpenCompute Aficionado
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [tc][all] A culture change (nitpicking)

[Zhipeng Huang]

For me nitpicking during review is really not a good experience, however i
do think we should tolerate at least one round of nitpicking.

On another aspect, the nitpicking review culture also in some way
encourage, and provide legitimacy in some way, to the padding activities.
People are feeling ok about "fixing dictionary" as we joked.



On Fri, Jun 1, 2018 at 4:55 AM, Jeremy Stanley  wrote:

> On 2018-05-31 16:49:13 -0400 (-0400), John Dennis wrote:
> > On 05/30/2018 08:23 PM, Jeremy Stanley wrote:
> > > I think this is orthogonal to the thread. The idea is that we should
> > > avoid nettling contributors over minor imperfections in their
> > > submissions (grammatical, spelling or typographical errors in code
> > > comments and documentation, mild inefficiencies in implementations,
> > > et cetera). Clearly we shouldn't merge broken features, changes
> > > which fail tests/linters, and so on. For me the rule of thumb is,
> > > "will the software be better or worse if this is merged?" It's not
> > > about perfection or imperfection, it's about incremental
> > > improvement. If a proposed change is an improvement, that's enough.
> > > If it's not perfect... well, that's just opportunity for more
> > > improvement later.
> >
> > I appreciate the sentiment concerning accepting any improvement yet on
> the
> > other hand waiting for improvements to the patch to occur later is
> folly, it
> > won't happen.
> >
> > Those of us familiar with working with large bodies of code from multiple
> > authors spanning an extended time period will tell you it's very
> confusing
> > when it's obvious most of the code follows certain conventions but there
> are
> > odd exceptions (often without comments). This inevitably leads to
> investing
> > a lot of time trying to understand why the exception exists because
> "clearly
> > it's there for a reason and I'm just missing the rationale" At that point
> > the reason for the inconsistency is lost.
> >
> > At the end of the day it is more important to keep the code base clean
> and
> > consistent for those that follow than it is to coddle in the near term.
>
> Sure, I suppose it comes down to your definition of "improvement." I
> don't consider a change proposing incomplete or unmaintainable code
> to be an improvement. On the other hand I think it's fine to approve
> changes which are "good enough" even if there's room for
> improvement, so long as they're "good enough" that you're fine with
> them possibly never being improved on due to shifts in priorities.
> I'm certainly not suggesting that it's a good idea to merge
> technical debt with the expectation that someone will find time to
> solve it later (any more than it's okay to merge obvious bugs in
> hopes someone will come along and fix them for you).
> --
> Jeremy Stanley
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>


-- 
Zhipeng (Howard) Huang

Standard Engineer
IT Standard & Patent/IT Product Line
Huawei Technologies Co,. Ltd
Email: huangzhip...@huawei.com
Office: Huawei Industrial Base, Longgang, Shenzhen

(Previous)
Research Assistant
Mobile Ad-Hoc Network Lab, Calit2
University of California, Irvine
Email: zhipe...@uci.edu
Office: Calit2 Building Room 2402

OpenStack, OPNFV, OpenDaylight, OpenCompute Aficionado
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [tc] Organizational diversity tag

[Zhipeng Huang]

I agree with Zane's proposal here, it is a good rule to have 2 core
reviewer from different companies to provide +2 for a patch. However it
should not be very strict given that project in early stage usually have to
rely on devs from one or two companies.

But it should be recommended that project apply for the diversity-tag
should at least expressed that they have adopted this rule.

On Sat, Jun 2, 2018 at 3:19 AM, Zane Bitter  wrote:

> On 01/06/18 12:18, Doug Hellmann wrote:
>
>> Excerpts from Zane Bitter's message of 2018-06-01 10:10:31 -0400:
>>
>>> Crazy idea: what if we dropped the idea of measuring the diversity and
>>> allowed teams to decide when they applied the tag to themselves like we
>>> do for other tags. (No wait! Come back!)
>>>
>>> Some teams enforce a requirement that the 2 core +2s come from reviewers
>>> with different affiliations. We would say that any project that enforces
>>> that rule would get the diversity tag. Then it's actually attached to
>>> something concrete, and teams could decide for themselves when to drop
>>> it (because they would start having difficulty merging stuff otherwise).
>>>
>>> I'm not entirely sold on this, but it's an idea I had that I wanted to
>>> throw out there :)
>>>
>>> cheers,
>>> Zane.
>>>
>>>
>> The point of having the tags is to help consumers of the projects
>> understand their health in some capacity. In this case we were
>> trying to use measures of actual activity within the project to
>> help spot projects that are really only maintained by one company,
>> with the assumption that such projects are less healthy than others
>> being maintained by contributors with more diverse backing.
>>
>
> (Clarification for readers: there are actually 3 levels; getting the
> diverse-affiliations tag has a higher bar than dropping the single-vendor
> tag.)
>
> Does basing the tag definition on whether approvals need to come
>> from people with diverse affiliation provide enough project health
>> information that it would let us use it to replace the current tag?
>>
>
> Yes. Project teams will soon drop this rule if it's the only way to get
> patches in. A single-vendor project by definition cannot adopt this rule
> and continue to... exist as a project, really.
>
> It would tell potential users that if one organisation drops out it there
> is at least somebody left to review patches, and also guarantee that the
> project's direction is not down to the whim of one organisation.
>
> How many teams enforce the rule you describe?
>>
>
> I don't know.
>
> I do know that in Heat we never enforced it - at first because it was a
> single-vendor project, and then later because it was so diverse (and not
> subject to any particular cross-company animosity) that nobody particularly
> saw the need to change, and now that many of those vendors have pulled out
> of OpenStack because it would be an obstacle to getting patches approved
> again.
>
> I was kind of under the impression that all of the projects used this rule
> prior to Heat and Ceilometer being incubated. That may be incorrect. At
> least Nova and the projects that have a lot of vendor drivers (and are thus
> susceptible to suspicions of bias) - i.e. Cinder & Neutron mainly - may
> still follow this rule? I haven't yet found a mention of it in any of the
> contributor guides though, so possibly it was dropped OpenStack-wide and I
> never noticed.
>
> Is that rule a sign of a healthy team dynamic, that we would want
>> to spread to the whole community?
>>
>
> Yeah, this part I am pretty unsure about too. For some projects it
> probably is. For others it may just be an unnecessary obstacle, although I
> don't think it'd actually be *un*healthy for any project, assuming a big
> enough and diverse enough team (which should be a goal for the whole
> community).
>
> For most projects with small core teams it would obviously be a
> showstopper, but the idea would be for them to continue to opt out.
>
> cheers,
> Zane.
>
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>



-- 
Zhipeng (Howard) Huang

Standard Engineer
IT Standard & Patent/IT Product Line
Huawei Technologies Co,. Ltd
Email: huangzhip...@huawei.com
Office: Huawei Industrial Base, Longgang, Shenzhen

(Previous)
Research Assistant
Mobile Ad-Hoc Network Lab, Calit2
University of California, Irvine
Email: zhipe...@uci.edu
Office: Calit2 Building Room 2402

OpenStack, OPNFV, OpenDaylight, OpenCompute Aficionado
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [cyborg]No Meeting This Week

[Zhipeng Huang]

Hi team,

Given that people still recover from the summit and memorial day holiday,
let's cancel the team weekly meeting this week as well.

At the mean time feel free to communicate over irc or email :)

-- 
Zhipeng (Howard) Huang

Standard Engineer
IT Standard & Patent/IT Product Line
Huawei Technologies Co,. Ltd
Email: huangzhip...@huawei.com
Office: Huawei Industrial Base, Longgang, Shenzhen

(Previous)
Research Assistant
Mobile Ad-Hoc Network Lab, Calit2
University of California, Irvine
Email: zhipe...@uci.edu
Office: Calit2 Building Room 2402

OpenStack, OPNFV, OpenDaylight, OpenCompute Aficionado
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [cyborg]no meeting today

[Zhipeng Huang]

Enjoy the water view folks :)

-- 
Zhipeng (Howard) Huang

Standard Engineer
IT Standard & Patent/IT Product Line
Huawei Technologies Co,. Ltd
Email: huangzhip...@huawei.com
Office: Huawei Industrial Base, Longgang, Shenzhen

(Previous)
Research Assistant
Mobile Ad-Hoc Network Lab, Calit2
University of California, Irvine
Email: zhipe...@uci.edu
Office: Calit2 Building Room 2402

OpenStack, OPNFV, OpenDaylight, OpenCompute Aficionado
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [cyborg] [nova] Cyborg quotas

[Zhipeng Huang]

@Chris yes we are actively exploring this option :)

On Mon, May 21, 2018 at 2:27 PM, Chris Friesen 
wrote:

> On 05/19/2018 05:58 PM, Blair Bethwaite wrote:
>
>> G'day Jay,
>>
>> On 20 May 2018 at 08:37, Jay Pipes  wrote:
>>
>>> If it's not the VM or baremetal machine that is using the accelerator,
>>> what
>>> is?
>>>
>>
>> It will be a VM or BM, but I don't think accelerators should be tied
>> to the life of a single instance if that isn't technically necessary
>> (i.e., they are hot-pluggable devices). I can see plenty of scope for
>> use-cases where Cyborg is managing devices that are accessible to
>> compute infrastructure via network/fabric (e.g. rCUDA or dedicated
>> PCIe fabric). And even in the simple pci passthrough case (vfio or
>> mdev) it isn't hard to imagine use-cases for workloads that only need
>> an accelerator sometimes.
>>
>
> Currently nova only supports attach/detach of volumes and network
> interfaces. Is Cyborg looking to implement new Compute API operations to
> support hot attach/detach of various types of accelerators?
>
> Chris
>
>
>
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>



-- 
Zhipeng (Howard) Huang

Standard Engineer
IT Standard & Patent/IT Product Line
Huawei Technologies Co,. Ltd
Email: huangzhip...@huawei.com
Office: Huawei Industrial Base, Longgang, Shenzhen

(Previous)
Research Assistant
Mobile Ad-Hoc Network Lab, Calit2
University of California, Irvine
Email: zhipe...@uci.edu
Office: Calit2 Building Room 2402

OpenStack, OPNFV, OpenDaylight, OpenCompute Aficionado
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [cyborg]Weekly Team Meeting 2018.05.16

[Zhipeng Huang]

Hi team,

As usual we will have our weekly meeting starting UTC1400 at
#openstack-cyborg, initial agenda as follows:

1. summit prep
2. sub team report
3. critical rocky spec review
4. open patches

-- 
Zhipeng (Howard) Huang

Standard Engineer
IT Standard & Patent/IT Product Line
Huawei Technologies Co,. Ltd
Email: huangzhip...@huawei.com
Office: Huawei Industrial Base, Longgang, Shenzhen

(Previous)
Research Assistant
Mobile Ad-Hoc Network Lab, Calit2
University of California, Irvine
Email: zhipe...@uci.edu
Office: Calit2 Building Room 2402

OpenStack, OPNFV, OpenDaylight, OpenCompute Aficionado
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [cyborg]Nominating Sundar as new core reviewer (reminder)

[Zhipeng Huang]

Hi team,

Since the meetbot not function properly after our long running review
party, I would like send out this email for archiving purpose about
Sundar's nomination to our core review team which was discussed Wed last
week.

As already stated during the team meeting last week, Sundar has been a
tremendous help on two critical specs in Rocky and had conducted great
inter-project discussions. He has been very active on team meeting despite
the time difference (7am on west coast). He has also contributed a lot on
the k8s cyborg integration design. It would be great to have Sundar on the
core team to increase our bandwidth.

Plz provide any feedback about this nomination before Wed this week :)

-- 
Zhipeng (Howard) Huang

Standard Engineer
IT Standard & Patent/IT Product Line
Huawei Technologies Co,. Ltd
Email: huangzhip...@huawei.com
Office: Huawei Industrial Base, Longgang, Shenzhen

(Previous)
Research Assistant
Mobile Ad-Hoc Network Lab, Calit2
University of California, Irvine
Email: zhipe...@uci.edu
Office: Calit2 Building Room 2402

OpenStack, OPNFV, OpenDaylight, OpenCompute Aficionado
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [cyborg]spec review day (May 9th)

[Zhipeng Huang]

Hi team,

Let's make use of the team meeting on Wed to kickstart a whole day of
concentration of review of the critical Rocky specs [0] and try to get them
done as much as possible.

We start with the meeting and folks in US and Europe could carry on til the
end of the day when Asian devs could come in again :)

Initial agenda for Wed team meeting:
- Promote Sundar as new core reviewer
- KubeCon feedback
- Bugs and Issues
- Spec Review Day kickstart

[0] https://etherpad.openstack.org/p/cyborg-rocky-spec-day
-- 
Zhipeng (Howard) Huang

Standard Engineer
IT Standard & Patent/IT Product Line
Huawei Technologies Co,. Ltd
Email: huangzhip...@huawei.com
Office: Huawei Industrial Base, Longgang, Shenzhen

(Previous)
Research Assistant
Mobile Ad-Hoc Network Lab, Calit2
University of California, Irvine
Email: zhipe...@uci.edu
Office: Calit2 Building Room 2402

OpenStack, OPNFV, OpenDaylight, OpenCompute Aficionado
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [cyborg]No Team Meeting this Wed

[Zhipeng Huang]

Hi team,

Since I'm traveling to KubeCon this week, let's cancel the weekly meeting
today . You are still more than welcome to raise questions or just chat on
our irc channel :)
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [All] [Elections] Rocky TC Election Results

[Zhipeng Huang]

Congratulations to the newly elected TC members !

On Tue, May 1, 2018 at 2:17 AM, Amy  wrote:

> Congrats to all who were elected!
>
> Amy (spotz)
>
> Sent from my iPhone
>
> On Apr 30, 2018, at 7:02 PM, Kendall Nelson  wrote:
>
> Hello Everyone :)
>
> Please join me in congratulating the 7 newly elected members of the
> Technical Committee (TC)!
>
>
>- Thierry Carrez (ttx)]
>- Chris Dent (cdent)
>- Sean McGinnis (smcginnis)
>- Davanum Srinivas (dims)
>- Zane Bitter (zaneb)
>- Graham Hayes (mugsie)
>- Mohammed Naser (mnaser)
>
>
> Full results: https://civs.cs.cornell.edu/cgi-bin/results.pl?id=E_
> 98430d99fc2ed59d
>
> Election process details and results are also available here:
> https://governance.openstack.org/election/
>
> Thank you to all of the candidates, having a good group of candidates
> helps engage the community in our democratic process.
>
> Thank you to all who voted and who encouraged others to vote. We need to
> ensure your voices are heard!
>
> Thank you for another great round.
>
> -Kendall Nelson (diablo_rojo)
>
> [1] https://review.openstack.org/#/c/565368/
> 
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@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-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>


-- 
Zhipeng (Howard) Huang

Standard Engineer
IT Standard & Patent/IT Product Line
Huawei Technologies Co,. Ltd
Email: huangzhip...@huawei.com
Office: Huawei Industrial Base, Longgang, Shenzhen

(Previous)
Research Assistant
Mobile Ad-Hoc Network Lab, Calit2
University of California, Irvine
Email: zhipe...@uci.edu
Office: Calit2 Building Room 2402

OpenStack, OPNFV, OpenDaylight, OpenCompute Aficionado
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Zun][k8s] AWS Fargate and OpenStack Zun

[Zhipeng Huang]

Thanks Hongbin this is absolutely awesome.

On Sun, Apr 29, 2018 at 7:46 AM, Hongbin Lu  wrote:

> Hi folks,
>
> FYI. I wrote a blog post about a comparison between AWS Fargate and
> OpenStack Zun. It mainly covers the following:
>
> * The basic concepts of OpenStack Zun and AWS Fargate
> * The Kubernetes integration plan
>
> Here is the link: https://www.linkedin.com/pulse/aws-fargate-
> openstack-zun-comparing-serverless-container-hongbin-lu/
>
> Best regards,
> Hongbin
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>


-- 
Zhipeng (Howard) Huang

Standard Engineer
IT Standard & Patent/IT Product Line
Huawei Technologies Co,. Ltd
Email: huangzhip...@huawei.com
Office: Huawei Industrial Base, Longgang, Shenzhen

(Previous)
Research Assistant
Mobile Ad-Hoc Network Lab, Calit2
University of California, Irvine
Email: zhipe...@uci.edu
Office: Calit2 Building Room 2402

OpenStack, OPNFV, OpenDaylight, OpenCompute Aficionado
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [cyborg]Weekly Team Meeting 2018.04.25

[Zhipeng Huang]

Hi Team,

Team meeting starting UTC1400 as usual at #openstack-cyborg, initial agenda
as follows:

1. KubeCon preparation for resource mgmt wg discussion
2. subteam meeting arrangement for more agile meeting time/logistic
3. Rocky critical spec update
4. open patches/bug review

-- 
Zhipeng (Howard) Huang

Standard Engineer
IT Standard & Patent/IT Product Line
Huawei Technologies Co,. Ltd
Email: huangzhip...@huawei.com
Office: Huawei Industrial Base, Longgang, Shenzhen

(Previous)
Research Assistant
Mobile Ad-Hoc Network Lab, Calit2
University of California, Irvine
Email: zhipe...@uci.edu
Office: Calit2 Building Room 2402

OpenStack, OPNFV, OpenDaylight, OpenCompute Aficionado
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [tc] campaign question: How can we make contributing to OpenStack easier?

[Zhipeng Huang]

I think many projects are now beginning to develop the sub-team structure
(e.g Nova, Ironic and Cyborg) and that might be part of the answer here.

Having a sub-team structure and also have volunteer as sub team leads could
also help people that are not good at code review to contribute
significantly and get recognized in another way.

On Tue, Apr 24, 2018 at 7:24 PM, Davanum Srinivas  wrote:

> Thierry,
>
> please see below:
>
> On Tue, Apr 24, 2018 at 6:24 AM, Thierry Carrez 
> wrote:
> > Fox, Kevin M wrote:
> >> OpenStack has created artificial walls between the various Projects. It
> shows up, for example, as holes in usability at a user level or extra
> difficulty for operators juggling around so many projects. Users and for
> the most part, Operators don't really care about project organization, or
> ptls, or cores or such.  OpenStack has made some progress this direction
> with stuff like the unified cli. But OpenStack is not very unified.
> >
> > I've been giving this some thought (in the context of a presentation I
> > was giving on hard lessons learned from 8 years of OpenStack). I think
> > that organizing development around project teams and components was the
> > best way to cope with the growth of OpenStack in 2011-1015 and get to a
> > working set of components. However it's not the best organization to
> > improve on the overall "product experience", or for a maintenance phase.
> >
> > While it can be confusing, I like the two-dimensional approach that
> > Kubernetes followed (code ownership in one dimension, SIGs in the
> > other). The introduction of SIGs in OpenStack, beyond providing a way to
> > build closer feedback loops around specific topics, can help us tackle
> > this "unified experience" problem you raised. The formation of the
> > upgrades SIG, or the self-healing SIG is a sign that times change. Maybe
> > we need to push in that direction even more aggressively and start
> > thinking about de-emphasizing project teams themselves.
>
> Big +1. Another thing to check into is how can we split some of the
> work the PTL does into multiple roles ... that are short term and is
> rotated around. Hoping that will help with the problem where we need
> folks to be totally available full time to do meaningful work in a
> project.
>
> > --
> > Thierry Carrez (ttx)
> >
> > 
> __
> > OpenStack Development Mailing List (not for usage questions)
> > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:
> unsubscribe
> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
>
> --
> Davanum Srinivas :: https://twitter.com/dims
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>



-- 
Zhipeng (Howard) Huang

Standard Engineer
IT Standard & Patent/IT Product Line
Huawei Technologies Co,. Ltd
Email: huangzhip...@huawei.com
Office: Huawei Industrial Base, Longgang, Shenzhen

(Previous)
Research Assistant
Mobile Ad-Hoc Network Lab, Calit2
University of California, Irvine
Email: zhipe...@uci.edu
Office: Calit2 Building Room 2402

OpenStack, OPNFV, OpenDaylight, OpenCompute Aficionado
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [publiccloud-wg]KubeCon EU Public Cloud Meetup ?

[Zhipeng Huang]

Hi,

I'm wondering for people who will attend KubeCon EU is there any interest
for a public cloud meetup ? We could discuss many items listed in the ptg
summary I just sent out via the meetup :)

-- 
Zhipeng (Howard) Huang

Standard Engineer
IT Standard & Patent/IT Product Line
Huawei Technologies Co,. Ltd
Email: huangzhip...@huawei.com
Office: Huawei Industrial Base, Longgang, Shenzhen

(Previous)
Research Assistant
Mobile Ad-Hoc Network Lab, Calit2
University of California, Irvine
Email: zhipe...@uci.edu
Office: Calit2 Building Room 2402

OpenStack, OPNFV, OpenDaylight, OpenCompute Aficionado
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] Public Cloud WG PTG Summary

[Zhipeng Huang]

Hi team,

Sorry for this long overdue summary. During the Dublin PTG as a WG we held
two successful discussion sessions on Mon and Tues, and below are the
conclusions for this year's planning as far as I could recall. Please feel
free to provide further feedback :)


   - Passport Program v2
  - We want to push forward the passport program into the v2 stage this
  year, including QR code promotion, more member clouds (APAC and North
  America) and possibly a blockchain experiment (cloud ledger proposal [0])
  targeting Berlin Summit if the testnet proves to be successful.
  - We will be also looking into the possibility of having OpenLab as a
  special member of Passport Program to help ease some of the
difficulties of
  purely business facing or academic clouds to join the initiative.
   -  Public Cloud Feature List
   - We will look at a more formal draft of the feature list [1] ready for
  Vancouver and gather some additional requirement at Vancouver
summit. It is
  also possible for us to do a white paper based upon the feature list
  content this year, to help user and operators alike better understanding
  what OpenStack public cloud could offer.
   - Public Cloud SDK Certification
  - Chris Hoge, Dims and Melvin have been helping putting up a testing
  plan for public cloud sdk certification based upon the initial
work OpenLab
  team has achieved. Public Cloud WG will provide a interop-like guideline
  based upon the testing mechanism.
   - Public Cloud Meetup
  - We look forward to have more :)

[0]
https://docs.google.com/presentation/d/1RYRq1YdYEoZ5KNKwlDDtnunMdoYRAHPjPslnng3VqcI/edit?usp=sharing


[1]
https://docs.google.com/spreadsheets/d/1Mf8OAyTzZxCKzYHMgBl-QK_2-XSycSkOjqCyMTIedkA/edit?usp=sharing


-- 
Zhipeng (Howard) Huang

Standard Engineer
IT Standard & Patent/IT Product Line
Huawei Technologies Co,. Ltd
Email: huangzhip...@huawei.com
Office: Huawei Industrial Base, Longgang, Shenzhen

(Previous)
Research Assistant
Mobile Ad-Hoc Network Lab, Calit2
University of California, Irvine
Email: zhipe...@uci.edu
Office: Calit2 Building Room 2402

OpenStack, OPNFV, OpenDaylight, OpenCompute Aficionado
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [all] Topics for the Board+TC+UC meeting in Vancouver

[Zhipeng Huang]

big +1 to Graham's suggestion

On Mon, Apr 23, 2018 at 10:36 PM, Graham Hayes  wrote:

> On 18/04/18 11:38, Chris Dent wrote:
> > On Tue, 17 Apr 2018, Thierry Carrez wrote:
> >
> >> So... Is there any specific topic you think we should cover in that
> >> meeting ?
> >
> > The topics:
> >
> > 1. What are we to do, as a community, when external pressures for
> > results are not matched by contribution of resources to produce
> > those results? There are probably several examples of this, but one
> > that I'm particularly familiar with is the drive to be able to
> > satisfy complex hardware topologies demanded by virtual network
> > functions and related NFV use cases. Within nova, and I suspect other
> > projects, there is intense pressure to make progress and intense
> > effort that is removing resources from other areas. But the amount
> > of daily, visible contribution from the interest companies [1] is
> > _sometimes_ limited. There are many factors in this, and obviously
> > "throw more people at it" is not a silver bullet, but there are
> > things to talk about here that need the input from all the segments.
> >
> > 2. We've made progress of late with acknowledging the concepts
> > and importance of casual contribution and "drive-by bug fixing" in
> > our changing environment. But we've not yet made enough progress in
> > changing the way we do work. Corporate foundation members need to be
> > more aware and more accepting that the people they provide to work
> > "mostly upstream" need to be focused on making other people capable
> > of contribution. Not on getting features done. And those of us who
> > do have the privilege of being "mostly upstream" need to adjust our
> > priorities.
> >
> > Somewhere in that screed are, I think, some things worth talking
> > about, but they need to be distilled out.
> >
> > [1] http://superuser.openstack.org/articles/5g-open-source-att/
>
>
> I think as an add on to this, would to ask the board to talk to members
> and see what contributions they have made to the technical side of
> OpenStack.
>
> This should not just be Number of commits / reviews / bugs etc but
> also the motivation for the work, e.g. - Feature for a product, bug fix
> found in a product, cross project work or upstream project maintenance.
>
> I don't necessarily want to shame corporate members of the foundation,
> but I think it is important to understand where our contributor base
> comes from, and what each member brings to the community table.
>
> We should also ask the board to try and formulate a plan for growing
> new cross project leaders (not just TC / PTLs). We need to grow more
> technical contributors in the horizontal teams, which requires more
> than assigning a contributor to the QA / Infra / Olso / Docs teams
> for a year or so - the people should be allowed a certain amount
> of stability in a role, while not necessarily driving business goals.
>
> >
> >
> >
> > 
> __
> > OpenStack Development Mailing List (not for usage questions)
> > Unsubscribe: openstack-dev-requ...@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-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>


-- 
Zhipeng (Howard) Huang

Standard Engineer
IT Standard & Patent/IT Product Line
Huawei Technologies Co,. Ltd
Email: huangzhip...@huawei.com
Office: Huawei Industrial Base, Longgang, Shenzhen

(Previous)
Research Assistant
Mobile Ad-Hoc Network Lab, Calit2
University of California, Irvine
Email: zhipe...@uci.edu
Office: Calit2 Building Room 2402

OpenStack, OPNFV, OpenDaylight, OpenCompute Aficionado
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [tc] campaign question related to new projects

[Zhipeng Huang]

I think it actually relies upon the new team to actively reaching out to
the existing team. The new team cannot be lazy and wait for something
happen for them, they have to keep reaching out and believe me the core
developers from the existing official project will lend a hand in the end :)

For Cyborg, I didn't even rush the application for an official project
status. We've had more than one year just discuss the necessity and
usefulness of the project, because I was not sure as well at the time if we
are overlapping with something Nova or other project is already doing or we
are just dreaming up some use cases.

It turns out by conducting active and long discussions , we've got more
than enough help from the Nova team :) I believe this is the team that is
famous for their busy schedule, but the core developers helped tramendously
because we are the one that is actively reaching out.

SO back to topic, for TC's role, it should be to help the new team to find
a productive way to actively get in contact with any related existing
teams, not to put pressure on the existing projects :)

On Mon, Apr 23, 2018 at 10:39 PM, Doug Hellmann 
wrote:

> Excerpts from Zhipeng Huang's message of 2018-04-21 07:06:30 +0800:
> > As the one who just lead a new project into governance last year, I
> think I
> > could take a first stab at it.
> >
> > For me the current requirements in general works fine, as I emphasized in
> > my recent blog [0], the four opens are extremely important. Open Design
> is
> > one of the most important out the four I guess, because it actually will
> > lead to the diversity question. A team with a single vendor, although it
> > could satisfy all the other three easily, could not have a good open
> design
> > rather well.
> >
> > Another criteria (more related to the mission statement specifically) I
> > would consider important is the ability to demonstrate (1)its scope does
> > not overlap with existing official projects and (2) its ability to
> actively
> > work with related projects. The cross project collaboration does not have
> > to be waited after the project got anointed, rather started when the
> > project is in conception.
>
> In the past we have had challenges with existing teams having time,
> energy, or interest in working with new teams. These issues are
> often, but not always, outside of the control of the new teams.
> What role can, or should, the TC play in mediating these situations?
>
> Doug
>
> >
> > Well I guess that is my two cents :)
> >
> > [0] https://hannibalhuang.github.io/
> >
> >
> >
> > On Sat, Apr 21, 2018 at 5:26 AM, Doug Hellmann 
> > wrote:
> >
> > > [This is meant to be one of (I hope) several conversation-provoking
> > > questions directed at prospective TC members to help the community
> > > understand their positions before considering how to vote in the
> > > ongoing election.]
> > >
> > > We are discussing adding at least one new project this cycle, and
> > > the specific case of Adjutant has brought up questions about the
> > > criteria we use for evaluating new projects when they apply to
> > > become official.  Although the current system does include some
> > > well-defined requirements [1], it was also designed to rely on TC
> > > members to use their judgement in some other areas, to account for
> > > changing circumstances over the life of the project and to reflect
> > > the position that governance is not something we can automate away.
> > >
> > > Without letting the conversation devolve too much into a discussion
> > > of Adjutant's case, please talk a little about how you would evaluate
> > > a project's application in general.  What sorts of things do you
> > > consider when deciding whether a project "aligns with the OpenStack
> > > Mission," for example?
> > >
> > > Doug
> > >
> > > [1] https://governance.openstack.org/tc/reference/new-projects-
> > > requirements.html
> > >
> > > 
> __
> > > OpenStack Development Mailing List (not for usage questions)
> > > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:
> unsubscribe
> > > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> > >
> >
> >
> >
> > --
> > Zhipeng (Howard) Huang
> >
> > Standard Engineer
> > IT Standard & Patent/IT Product Line
> > Huawei Technologies Co,. Ltd
> > Email: huangzhip...@huawei.com
> > Office: Huawei Industrial Base, Longgang, Shenzhen
> >
> > (Previous)
> > Research Assistant
> > Mobile Ad-Hoc Network Lab, Calit2
> > University of California, Irvine
> > Email: zhipe...@uci.edu
> > Office: Calit2 Building Room 2402
> >
> > OpenStack, OPNFV, OpenDaylight, OpenCompute Aficionado
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> 

Re: [openstack-dev] [tc] campaign question: How "active" should the TC be?

[Zhipeng Huang]

I don't have specific ideas now, but it would be great to have TC publish
something like a new direction outlook per cycle or per year, to summarize
that these x,y,z new areas are what the OpenStack Technical Committee
considers worth exploring for new directions and we will sponsor projects
that will do the development in these areas. Of course I think it would be
great for TC member to personally leading projects in these new directions,
but find a way to sponsor or encourage other people leading is also a great
choice :)

Hope this clarifies a bit :)

On Mon, Apr 23, 2018 at 10:35 PM, Doug Hellmann 
wrote:

> Excerpts from Zhipeng Huang's message of 2018-04-23 21:50:15 +0800:
> > In general I would prefer TC take an active role regarding exploring new
> > use cases and technology directions leverage the existing OpenStack
> > infrastructure. I would against TC being too active on project level
> > governance.
>
> This would be a new area for the TC to consider. Can you elaborate a bit
> on what you think we would need to change in order to support that, and
> why the TC is the best place to do it (rather than one of our other
> team-based structures like a project team or SIG)?
>
> >
> > For example we have been discussing about edge computing recently and we
> > don't have any idea on how a lightweight OpenStack should look like:
> maybe
> > no scheduling since edge is more about provisioning ? maybe a Rust
> > implementation of this lightweight version of OpenStack ? There are so
> many
> > interesting new things that yet to be explored and should be championed
> by
> > the TC.
> >
> > However regarding issues like how a project should govern itself, it is
> > better for TC to reactive and let project team driven its own structure.
> I
> > can't think of there is any concrete example on this matter now since TC
> > has been doing rather well on this matter , but I guess this could be a
> > precautious action :)
> >
> > On Mon, Apr 23, 2018 at 9:35 PM, Doug Hellmann 
> > wrote:
> >
> > > Excerpts from Doug Hellmann's message of 2018-04-23 09:27:09 -0400:
> > > > [This is meant to be one of (I hope) several conversation-provoking
> > > > questions directed at prospective TC members to help the community
> > > > understand their positions before considering how to vote in the
> > > > ongoing election.]
> > > >
> > > > We frequently have discussions about whether the TC is active enough,
> > > > in terms of driving new policies, technology choices, and other
> > > > issues that affect the entire community.
> > > >
> > > > Please describe one case where we were either active or reactive
> > > > and how that was shown to be the right choice over time.
> > > >
> > > > Please describe another case where the choice to be active or
> > > > reactive ended up being the wrong choice.
> > > >
> > > > If you think the TC should tend to be more active in driving change
> > > > than it is today, please describe the changes (policy, culture,
> > > > etc.) you think would need to be made to do that effectively (not
> > > > which policies you want us to be more active on, but *how* to
> > > > organize the TC to be more active and have that work within the
> > > > community culture).
> > > >
> > > > If you think the TC should tend to be less active in driving change
> > > > overall, please describe what policies you think the TC should be
> > > > taking an active role in implementing.
> > > >
> > > > Doug
> > >
> > > There was a question from ttx on IRC [1] about my use of the terms
> > > "active" and "reactive" here. I mean active as "going out there and
> > > doing things and anticipating issues" and reactive as "dealing with
> > > things as they come up and aren't resolved in another way".
> > >
> > > Doug
> > >
> > > [1]
> > > http://eavesdrop.openstack.org/irclogs/%23openstack-tc/%
> > > 23openstack-tc.2018-04-23.log.html
> > >
> > > 
> __
> > > OpenStack Development Mailing List (not for usage questions)
> > > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:
> unsubscribe
> > > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> > >
> >
> >
> >
> > --
> > Zhipeng (Howard) Huang
> >
> > Standard Engineer
> > IT Standard & Patent/IT Product Line
> > Huawei Technologies Co,. Ltd
> > Email: huangzhip...@huawei.com
> > Office: Huawei Industrial Base, Longgang, Shenzhen
> >
> > (Previous)
> > Research Assistant
> > Mobile Ad-Hoc Network Lab, Calit2
> > University of California, Irvine
> > Email: zhipe...@uci.edu
> > Office: Calit2 Building Room 2402
> >
> > OpenStack, OPNFV, OpenDaylight, OpenCompute Aficionado
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> 

Re: [openstack-dev] [tc] campaign question: How can we make contributing to OpenStack easier?

[Zhipeng Huang]

Culture wise, being too IRC-centric is definitely not helping, from my own
experience getting new Cyborg developer joining our weekly meeting from
China. Well we could always argue it is part of a open source/hacker
culture and preferable to commercial solutions that have the constant risk
of suddenly being shut down someday. But as OpenStack becomes more
commercialized and widely adopted, we should be aware that more and more
(potential) contributors will come from the groups who are used to
non-strictly open source environment, such as product develop team which
relies on a lot of "closed source" but easy to use softwares.

The change ? Use more video conferences, and more commercial tools that
preferred in certain region. Stop being allergic to non-open source
softwares and bring more capable but not hacker culture inclined
contributors to the community.

I know this is not a super welcomed stance in the open source hacker
culture. But if we want OpenStack to be able to sustain more developers and
not have a mid-life crisis then got fringed, we need to start changing the
hacker mindset.

Another important thing, as I stated in the previous email, is that
OpenStack should keep explore new technology directions and TC should take
the lead position on it. No matter how good we could facilitate the
contributors, a stale community cannot win more contributors. I'm against
hype like any other, but reluctant or lazy on innovation is another thing
and will cost the community to lose more and more existing and potential
contributors.



On Mon, Apr 23, 2018 at 10:06 PM, Doug Hellmann 
wrote:

> [This is meant to be one of (I hope) several conversation-provoking
> questions directed at prospective TC members to help the community
> understand their positions before considering how to vote in the
> ongoing election.]
>
> Over the last year we have seen some contraction in the number of
> companies and individuals contributing to OpenStack. At the same
> time we have started seeing contributions from other companies and
> individuals. To some degree this contraction and shift in contributor
> base is a natural outcome of changes in OpenStack itself along with
> the rest of the technology industry, but as with any change it
> raises questions about how and whether we can ensure a smooth
> transition to a new steady state.
>
> What aspects of our policies or culture make contributing to OpenStack
> more difficult than contributing to other open source projects?
>
> Which of those would you change, and how?
>
> Where else should we be looking for contributors?
>
> Doug
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>



-- 
Zhipeng (Howard) Huang

Standard Engineer
IT Standard & Patent/IT Product Line
Huawei Technologies Co,. Ltd
Email: huangzhip...@huawei.com
Office: Huawei Industrial Base, Longgang, Shenzhen

(Previous)
Research Assistant
Mobile Ad-Hoc Network Lab, Calit2
University of California, Irvine
Email: zhipe...@uci.edu
Office: Calit2 Building Room 2402

OpenStack, OPNFV, OpenDaylight, OpenCompute Aficionado
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [tc] campaign question: How should we handle projects with overlapping feature sets?

[Zhipeng Huang]

I think this depends on the nature of the project.

For deployment tools, as we also have witnessed in OPNFV, it tends to have
multiple solutions. So it is normal to have multiple such projects although
they are solving the same problem generally speaking.

For projects that has a clear definition on a specific set of features of
functionalities which are critical to any cloud infrastructure, then
overlapping should be strictly avoided. I don't think for a team that
proposes a new project that got a significant overlap with existing project
has seriously studies the community or a good intention to collaborate
within the community.

Of course there will be exceptions for implementations in different langs
but generally I would prefer to take a strong stance on strictly avoiding
the overlap. The benefit we would got as a community is that we will have
developers working on projects that is clearly defined both individually
and collaboratively without any confusion.






On Mon, Apr 23, 2018 at 9:50 PM, Doug Hellmann 
wrote:

> [This is meant to be one of (I hope) several conversation-provoking
> questions directed at prospective TC members to help the community
> understand their positions before considering how to vote in the
> ongoing election.]
>
> In the course of evaluating new projects that have asked to join
> as official members of the OpenStack community, we often discuss
> whether the feature set of the project overlaps too much with other
> existing projects. This came up within the last year during Glare's
> application, and more recently as part of the Adjutant application.
>
> Our current policy regarding Open Development is that a project
> should cooperate with existing projects "rather than gratuitously
> competing or reinventing the wheel." [1] The flexibility provided
> by the use of the term "gratuitously" has allowed us to support
> multiple solutions in the deployment and telemetry problem spaces.
> At the same time it has left us with questions about how (and
> whether) the community would be able to replace the implementation
> of any given component with a new set of technologies by "starting
> from scratch".
>
> Where do you draw the line at "gratuitous"?
>
> What benefits and drawbacks do you see in supporting multiple tools
> with similar features?
>
> How would our community be different, in positive and negative ways,
> if we were more strict about avoiding such overlap?
>
> Doug
>
> [1] https://governance.openstack.org/tc/reference/new-projects-
> requirements.html
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>



-- 
Zhipeng (Howard) Huang

Standard Engineer
IT Standard & Patent/IT Product Line
Huawei Technologies Co,. Ltd
Email: huangzhip...@huawei.com
Office: Huawei Industrial Base, Longgang, Shenzhen

(Previous)
Research Assistant
Mobile Ad-Hoc Network Lab, Calit2
University of California, Irvine
Email: zhipe...@uci.edu
Office: Calit2 Building Room 2402

OpenStack, OPNFV, OpenDaylight, OpenCompute Aficionado
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [tc] campaign question: How "active" should the TC be?

[Zhipeng Huang]

In general I would prefer TC take an active role regarding exploring new
use cases and technology directions leverage the existing OpenStack
infrastructure. I would against TC being too active on project level
governance.

For example we have been discussing about edge computing recently and we
don't have any idea on how a lightweight OpenStack should look like: maybe
no scheduling since edge is more about provisioning ? maybe a Rust
implementation of this lightweight version of OpenStack ? There are so many
interesting new things that yet to be explored and should be championed by
the TC.

However regarding issues like how a project should govern itself, it is
better for TC to reactive and let project team driven its own structure. I
can't think of there is any concrete example on this matter now since TC
has been doing rather well on this matter , but I guess this could be a
precautious action :)

On Mon, Apr 23, 2018 at 9:35 PM, Doug Hellmann 
wrote:

> Excerpts from Doug Hellmann's message of 2018-04-23 09:27:09 -0400:
> > [This is meant to be one of (I hope) several conversation-provoking
> > questions directed at prospective TC members to help the community
> > understand their positions before considering how to vote in the
> > ongoing election.]
> >
> > We frequently have discussions about whether the TC is active enough,
> > in terms of driving new policies, technology choices, and other
> > issues that affect the entire community.
> >
> > Please describe one case where we were either active or reactive
> > and how that was shown to be the right choice over time.
> >
> > Please describe another case where the choice to be active or
> > reactive ended up being the wrong choice.
> >
> > If you think the TC should tend to be more active in driving change
> > than it is today, please describe the changes (policy, culture,
> > etc.) you think would need to be made to do that effectively (not
> > which policies you want us to be more active on, but *how* to
> > organize the TC to be more active and have that work within the
> > community culture).
> >
> > If you think the TC should tend to be less active in driving change
> > overall, please describe what policies you think the TC should be
> > taking an active role in implementing.
> >
> > Doug
>
> There was a question from ttx on IRC [1] about my use of the terms
> "active" and "reactive" here. I mean active as "going out there and
> doing things and anticipating issues" and reactive as "dealing with
> things as they come up and aren't resolved in another way".
>
> Doug
>
> [1]
> http://eavesdrop.openstack.org/irclogs/%23openstack-tc/%
> 23openstack-tc.2018-04-23.log.html
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>



-- 
Zhipeng (Howard) Huang

Standard Engineer
IT Standard & Patent/IT Product Line
Huawei Technologies Co,. Ltd
Email: huangzhip...@huawei.com
Office: Huawei Industrial Base, Longgang, Shenzhen

(Previous)
Research Assistant
Mobile Ad-Hoc Network Lab, Calit2
University of California, Irvine
Email: zhipe...@uci.edu
Office: Calit2 Building Room 2402

OpenStack, OPNFV, OpenDaylight, OpenCompute Aficionado
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [kolla][vote]Retire kolla-kubernetes project

[Zhipeng Huang]

+1

On Sun, Apr 22, 2018 at 8:55 AM, Davanum Srinivas  wrote:

> +1
>
> On Sat, Apr 21, 2018 at 5:56 PM, Pete Birley  wrote:
> > +1
> >
> > On Thu, Apr 19, 2018, 1:24 AM Eduardo Gonzalez 
> wrote:
> >>
> >> +1
> >>
> >> 2018-04-19 8:21 GMT+02:00 Christian Berendt
> >> :
> >>>
> >>> +1
> >>>
> >>> > On 18. Apr 2018, at 03:51, Jeffrey Zhang 
> >>> > wrote:
> >>> >
> >>> > Since many of the contributors in the kolla-kubernetes project are
> >>> > moved to other things. And there is no active contributor for
> months.  On
> >>> > the other hand, there is another comparable project, openstack-helm,
> in the
> >>> > community.  For less confusion and disruptive community resource, I
> propose
> >>> > to retire the kolla-kubernetes project.
> >>> >
> >>> > More discussion about this you can check the mail[0] and patch[1]
> >>> >
> >>> > please vote +1 to retire the repo, or -1 not to retire the repo. The
> >>> > vote will be open until everyone has voted, or for 1 week until
> April 25th,
> >>> > 2018.
> >>> >
> >>> > [0]
> >>> > http://lists.openstack.org/pipermail/openstack-dev/2018-
> March/128822.html
> >>> > [1] https://review.openstack.org/552531
> >>> >
> >>> > --
> >>> > Regards,
> >>> > Jeffrey Zhang
> >>> > Blog: http://xcodest.me
> >>> >
> >>> > 
> __
> >>> > OpenStack Development Mailing List (not for usage questions)
> >>> > Unsubscribe:
> >>> > openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> >>> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> >>>
> >>> --
> >>> Christian Berendt
> >>> Chief Executive Officer (CEO)
> >>>
> >>> Mail: bere...@betacloud-solutions.de
> >>> Web: https://www.betacloud-solutions.de
> >>>
> >>> Betacloud Solutions GmbH
> >>> Teckstrasse 62 / 70190 Stuttgart / Deutschland
> >>>
> >>> Geschäftsführer: Christian Berendt
> >>> Unternehmenssitz: Stuttgart
> >>> Amtsgericht: Stuttgart, HRB 756139
> >>>
> >>>
> >>>
> >>> 
> __
> >>> OpenStack Development Mailing List (not for usage questions)
> >>> Unsubscribe:
> >>> openstack-dev-requ...@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-requ...@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-requ...@lists.openstack.org?subject:
> unsubscribe
> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> >
>
>
>
> --
> Davanum Srinivas :: https://twitter.com/dims
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>



-- 
Zhipeng (Howard) Huang

Standard Engineer
IT Standard & Patent/IT Product Line
Huawei Technologies Co,. Ltd
Email: huangzhip...@huawei.com
Office: Huawei Industrial Base, Longgang, Shenzhen

(Previous)
Research Assistant
Mobile Ad-Hoc Network Lab, Calit2
University of California, Irvine
Email: zhipe...@uci.edu
Office: Calit2 Building Room 2402

OpenStack, OPNFV, OpenDaylight, OpenCompute Aficionado
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [tc] campaign question related to new projects

[Zhipeng Huang]

As the one who just lead a new project into governance last year, I think I
could take a first stab at it.

For me the current requirements in general works fine, as I emphasized in
my recent blog [0], the four opens are extremely important. Open Design is
one of the most important out the four I guess, because it actually will
lead to the diversity question. A team with a single vendor, although it
could satisfy all the other three easily, could not have a good open design
rather well.

Another criteria (more related to the mission statement specifically) I
would consider important is the ability to demonstrate (1)its scope does
not overlap with existing official projects and (2) its ability to actively
work with related projects. The cross project collaboration does not have
to be waited after the project got anointed, rather started when the
project is in conception.

Well I guess that is my two cents :)

[0] https://hannibalhuang.github.io/



On Sat, Apr 21, 2018 at 5:26 AM, Doug Hellmann 
wrote:

> [This is meant to be one of (I hope) several conversation-provoking
> questions directed at prospective TC members to help the community
> understand their positions before considering how to vote in the
> ongoing election.]
>
> We are discussing adding at least one new project this cycle, and
> the specific case of Adjutant has brought up questions about the
> criteria we use for evaluating new projects when they apply to
> become official.  Although the current system does include some
> well-defined requirements [1], it was also designed to rely on TC
> members to use their judgement in some other areas, to account for
> changing circumstances over the life of the project and to reflect
> the position that governance is not something we can automate away.
>
> Without letting the conversation devolve too much into a discussion
> of Adjutant's case, please talk a little about how you would evaluate
> a project's application in general.  What sorts of things do you
> consider when deciding whether a project "aligns with the OpenStack
> Mission," for example?
>
> Doug
>
> [1] https://governance.openstack.org/tc/reference/new-projects-
> requirements.html
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>



-- 
Zhipeng (Howard) Huang

Standard Engineer
IT Standard & Patent/IT Product Line
Huawei Technologies Co,. Ltd
Email: huangzhip...@huawei.com
Office: Huawei Industrial Base, Longgang, Shenzhen

(Previous)
Research Assistant
Mobile Ad-Hoc Network Lab, Calit2
University of California, Irvine
Email: zhipe...@uci.edu
Office: Calit2 Building Room 2402

OpenStack, OPNFV, OpenDaylight, OpenCompute Aficionado
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [cyborg][release][Release-job-failures] Pre-release of openstack/cyborg failed

[Zhipeng Huang]

Thanks Doug we will take a look into it

On Sat, Apr 21, 2018 at 12:02 AM, Doug Hellmann 
wrote:

> Excerpts from zuul's message of 2018-04-20 13:59:14 +:
> > Build failed.
> >
> > - release-openstack-python http://logs.openstack.org/fa/
> fabeaffa6efe8b1ef3d828f5b8c2cdc896e4afe9/pre-release/
> release-openstack-python/c624655/ : FAILURE in 6m 07s
> > - announce-release announce-release : SKIPPED
> > - propose-update-constraints propose-update-constraints : SKIPPED
> >
>
> The cyborg milestone release failed to build because the packaging step
> could not find some expected rootwrap files:
>
> http://logs.openstack.org/fa/fabeaffa6efe8b1ef3d828f5b8c2cd
> c896e4afe9/pre-release/release-openstack-python/
> c624655/job-output.txt.gz#_2018-04-20_13_58_20_454319
>
> Doug
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>



-- 
Zhipeng (Howard) Huang

Standard Engineer
IT Standard & Patent/IT Product Line
Huawei Technologies Co,. Ltd
Email: huangzhip...@huawei.com
Office: Huawei Industrial Base, Longgang, Shenzhen

(Previous)
Research Assistant
Mobile Ad-Hoc Network Lab, Calit2
University of California, Irvine
Email: zhipe...@uci.edu
Office: Calit2 Building Room 2402

OpenStack, OPNFV, OpenDaylight, OpenCompute Aficionado
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [cyborg]Weekly Team Meeting 2018.04.18

[Zhipeng Huang]

Hi Team,

Weekly meeting as usual starting UTC1400 at #openstack-cyborg, initial
agenda as follows:

1. MS1 preparation
2. bug report on storyboard
3. Rocky critical spec review
4. open patches discussion

-- 
Zhipeng (Howard) Huang

Standard Engineer
IT Standard & Patent/IT Product Line
Huawei Technologies Co,. Ltd
Email: huangzhip...@huawei.com
Office: Huawei Industrial Base, Longgang, Shenzhen

(Previous)
Research Assistant
Mobile Ad-Hoc Network Lab, Calit2
University of California, Irvine
Email: zhipe...@uci.edu
Office: Calit2 Building Room 2402

OpenStack, OPNFV, OpenDaylight, OpenCompute Aficionado
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [election][tc]TC candidacy

[Zhipeng Huang]

Hi all,

I'm announcing my candidacy for the OpenStack Technical Committee.

I started following OpenStack community since Portland Summit in 2013, and
has been an integral part of it from then on. I'm currently serving as the
PTL for the Cyborg project [0] which provides general management framework
for accelerators. I'm also serving as the co-chair of the Public Cloud WG
[1], active member of the First Contact SIG [2] and had been a contributor
for the Interop WG throughout the year 2017 [3]. Outside of OpenStack, I'm
one of the founding co-leads for the Kubernetes Policy WG [4], the
ecosystem lead for OpenSDS community [5], and also served as the PTL of
OPNFV Parser project from 2014 to 2016 [6]. I've also been involved with
Open Service Broker API and SPDK community where my team members are
working on.

I would like to think my strength are in the areas like cross-community
collaboration, community team building, and non-stop innovation. I believe
these are also the areas that my future work on the Technical Committee
should continue to bring forth.

** Cross Community Collaboration **

For those of you who are familiar with my work, you would know that I've
always been taking a full stack approach for open source community work and
strongly believed the value of collaboration. From the very start building
of the *Cyborg project*, we collaborated with the OPNFV community and also
had a concrete plan on working with communities like Kubernetes, Linaro,
ONNX and so forth. With my work in *OpenSDS*, I've repeatedly emphasize the
importance of the capability of working with OpenStack and Kubernetes but
not drop something and claim it would be better to replace the existing
module which has been built by a lot of community work. During our
discussions in the *Kubernetes Policy WG* on multi-tenancy I've also
introduced what the Keystone team has greatly done and try to build a
synergy there.

Hence if I were to be elected on the technical committee, I would like to
pushing further on the community collaborations within but not limited to
the following areas:
*- Data model alignment regarding accelerator between OpenStack and
Kubernetes via Cyborg project and the Resource Management SIG.*
*- Alignment regarding Policy architecture between OpenStack and Kubernetes
via Kubernetes Policy WG as well as Keystone team.*


** Community Team Building **

With currently busting the hype bubble, I've seen many commentaries on how
OpenStack "is getting outdated" and not "technically cool" any more. Set
aside the absurdity on the technical aspects, I think one of the core
things people will learn in the OpenStack community is the governance, the
way how we work here.

Take *Cyborg* for example, from day one I've been strictly following the
four opens principle and trying to build a good team structure by learning
from great teams like Nova, Cinder, Neutron, etc. The Cyborg project was
started from basically zero and I intentionally avoided any code dumping as
we've seen in many open source projects. We designed the specs from open
discussion, wrote the codes with public reviews and continue on. When few
people believe even this could work, we make it happen. The reward we are
having is awesome, for example on nova-cyborg collaboration, by not
mandating certain design philosophy, we have great Nova developers joining
our project meeting from time to time, providing valuable comments on how
we better design the interaction, and help reviewing the specs. I think for
a new project I dare say we've got the best and logical architecture design
with regarding to nova interaction.

With that said, the community team building will be another important theme
for my future work on TC:
*- Leveraging First Contact SIG, to try to incubate or help more project
that knows how to build their team in a community way instead of a
corporate way.*
*- Continue on the Cyborg team structure building, enable reasonable
sub-team work and encourage more developers to join and contribute.*
*- Enabling more collaboration between projects and WG/SIGs. We have some
good experience on Cyborg working with Scientific SIG as well as Public
Cloud WG working with Nova/Keystone team, and I think we could make further
progress on it*

** Non Stop Innovation **

OpenStack offers the ultimate open source cloud computing infrastructure
and there are just so many exciting new things we could do with it. I've
experimenting the ideas of *how Cyborg could better support AI application,
and also the possibility of utilizing blockchain for the Passport Program
[7]*. I plan to keep bring new things like these forward when given the
opportunity to serve on the  technical committee to make OpenStack's edge
keep cutting as sharp as ever :)

Thank you for your time to read such a long letter and please vote for me
and any other candidate that you see value in. A great community could not
exist without your important voice.

[openstack-dev] [cyborg]Weekly Team Meeting April 11, 2018

[Zhipeng Huang]

Hi Team,

Our weekly meeting starting from UTC1400 at #openstack-cyborg as usual. The
initial agenda is as follows:

1. Confirmation of new core reviewer promotion,
2. Critical Rocky Spec update and discussion
3. open patch discussion

Please feel free to suggest new topics any time :)

-- 
Zhipeng (Howard) Huang

Standard Engineer
IT Standard & Patent/IT Product Line
Huawei Technologies Co,. Ltd
Email: huangzhip...@huawei.com
Office: Huawei Industrial Base, Longgang, Shenzhen

(Previous)
Research Assistant
Mobile Ad-Hoc Network Lab, Calit2
University of California, Irvine
Email: zhipe...@uci.edu
Office: Calit2 Building Room 2402

OpenStack, OPNFV, OpenDaylight, OpenCompute Aficionado
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [cyborg] Promote Li Liu as new core reviewer

[Zhipeng Huang]

Hi Team,

This is an email for my nomination of adding Li Liu to the core reviewer
team. Li Liu has been instrumental in the resource provider data model
implementation for Cyborg during Queens release, as well as metadata
standardization and programming design for Rocky.

His overall stats [0] and current stats [1] for Rocky speaks for itself.
His patches could be found here [2].

Given the amount of work undergoing for Rocky, it would be great to add
such an amazing force :)

[0]
http://stackalytics.com/?module=cyborg-group=person-day=all
[1]
http://stackalytics.com/?module=cyborg-group=person-day=rocky
[2] https://review.openstack.org/#/q/owner:liliueecg%2540gmail.com

-- 
Zhipeng (Howard) Huang

Standard Engineer
IT Standard & Patent/IT Product Line
Huawei Technologies Co,. Ltd
Email: huangzhip...@huawei.com
Office: Huawei Industrial Base, Longgang, Shenzhen

(Previous)
Research Assistant
Mobile Ad-Hoc Network Lab, Calit2
University of California, Irvine
Email: zhipe...@uci.edu
Office: Calit2 Building Room 2402

OpenStack, OPNFV, OpenDaylight, OpenCompute Aficionado
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] Asking for ask.openstack.org

[Zhipeng Huang]

The email alert definitely should be the first one to get fixed :)

On Thu, Apr 5, 2018 at 8:23 AM, Zane Bitter  wrote:

> On 04/04/18 17:26, Jimmy McArthur wrote:
>
>> Hi everyone!
>>
>> We have a very robust and vibrant community at ask.openstack.org <
>> https://ask.openstack.org/>.  There are literally dozens of posts a day.
>> However, many of them don't receive knowledgeable answers.  I'm really
>> worried about this becoming a vacuum where potential community members get
>> frustrated and don't realize how to get more involved with the community.
>>
>> I'm looking for thoughts/ideas/feelings about this tool as well as
>> potential admin volunteers to help us manage the constant influx of
>> technical and not-so-technical questions around OpenStack.
>>
>
> Here's the thing: email alerts. They're broken.
>
> I have had my email alert preferences set to 'only subscribed tags' with a
> daily 'Entire forum (tag filtered)' email for several (like 4) years now. I
> am subscribed to exactly 3 tags.[1]
>
> For the first 3 years, I didn't receive any email alerts at all despite
> repeated fiddling with the settings. At the beginning of 2017 there was a
> software update and I started getting daily emails that are *not* tag
> filtered. (I know it was due to a software update, because the first emails
> started coming from the staging server.) Within a couple of days those
> emails started to go directly to spam, because GMail. I trained it not to
> do that any more for me, but it's unlikely most people did, and in any
> event all I get is a daily email that generally doesn't contain any of the
> questions I am interested in - even on days where there _are_ in fact new
> questions with tags that I am subscribed to.
>
> I've been able to make a reasonably significant contribution to answering
> questions because I've made it a habit to check the site itself regularly
> (and the tag filtering on the home page works really quite well). But
> anyone wanting to use technical means to give them notice about only the
> stuff they're interested in only when needed would be unable to do so. (And
> even if you fixed it at this point it'd all be sucked into spam filters.)
>
> There's other problems too - for example if somebody posts a question with
> not enough information and I post a comment asking for more, I won't get a
> notification when they reply unless they specifically @ me, which most
> people won't. (Sometimes I've discovered the replies only years later.) In
> fact in general the learning curve is way too high for people who just want
> to ask a casual question - for example, I'd say users are considerably more
> likely to respond to a correct answer by posting their own 'answer' that
> says 'It worked!' (or, worse, contains a totally unrelated question) than
> they are to click the 'Accepted answer' button - and there's no point
> trying to educate them because you almost never see the same user twice.
> Those are all broader problems with the design of StackExchange though; the
> alert thing is a feature that's supposedly present but doesn't work as
> advertised.
>
> It's also worth noting that the voting in general is fairly pointless
> because ~nobody has an account registered. So if people find a useful
> question and/or answer on ask.openstack from a search engine, they still
> won't bother to upvote because they'd have to create an account.
> Communities with critical mass like StackOverflow can use voting as a
> quality signal to surface the best content; we don't get enough data for
> that. (For reference, I've answered 237 questions and less than a dozen
> have ever gotten a second upvote - which is likely a good proxy for 'has
> ever been voted on by someone other than the original questioner'.)
>
> So, suggestions:
>
> * Fix the email subscription thing.
> * Ensure all devs have an account - perhaps by creating one for them using
> their IRC nickname & Foundation email? - and encourage people to @ each
> other when they see a question where they don't know the answer but they
> know who would (like you might add people to a Gerrit review). (Although
> realistically most of this will end up in the Spam folder... some might say
> deservedly ;)
> * Encourage teams to figure out a set of tags they want to watch, and
> encourage at least all core reviewers to log in once and set up their tag
> subscriptions so they'll see something useful when they visit the homepage.
> * Ask each team to come up with 1 or 2 volunteers to subscribe to
> (filtered!) email alerts and try to answer or triage incoming questions.
>
> For those of you already contributing there, Thank You!  For those that
>> are interested in becoming a moderator (instant AUC status!) or have some
>> additional ideas around fostering this community, please respond.
>>
>
> I'm not sure what else there is that I can't already do at my current
> karma level, but you're welcome to add me to the list and I'll try to do
> 

[openstack-dev] [cyborg]Weejky Team Meeting 2018.04.04

[Zhipeng Huang]

Hi Team,

As usual team meeting starting UTC1400 at #openstack-cyborg, initial agenda
as follows:

1. Status report from subteam
2. Critical spec patch review

Plz feel free to suggest more topics.

-- 
Zhipeng (Howard) Huang

Standard Engineer
IT Standard & Patent/IT Product Line
Huawei Technologies Co,. Ltd
Email: huangzhip...@huawei.com
Office: Huawei Industrial Base, Longgang, Shenzhen

(Previous)
Research Assistant
Mobile Ad-Hoc Network Lab, Calit2
University of California, Irvine
Email: zhipe...@uci.edu
Office: Calit2 Building Room 2402

OpenStack, OPNFV, OpenDaylight, OpenCompute Aficionado
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [k8s] OpenStack and Containers White Paper

[Zhipeng Huang]

Hi Chris,

If it is possible to add Cyborg under  "Projects that can stand alone in
integrations with Kubernetes and
  other cloud technology" section, I would like to help on that content.

On Tue, Apr 3, 2018 at 5:30 AM, Hongbin Lu  wrote:

> Hi Chris,
>
> I can help with the Zun session.
>
> Best regards,
> Hongbin
>
> On Mon, Apr 2, 2018 at 4:59 PM, Chris Hoge  wrote:
>
>> Hi everyone,
>>
>> In advance of the Vancouver Summit, I'm leading an effort to publish a
>> community produced white-paper on OpenStack and container integrations.
>> This has come out of a need to develop materials, both short and long
>> form, to help explain how OpenStack interacts with container
>> technologies across the entire stack, from infrastructure to
>> application. The rough outline of the white-paper proposes an entire
>> technology stack and discuss deployment and usage strategies at every
>> level. The white-paper will focus on existing technologies, and how they
>> are being used in production today across our community. Beginning at
>> the hardware layer, we have the following outline (which may be inverted
>> for clarity):
>>
>> * OpenStack Ironic for managing bare metal deployments.
>> * Container-based deployment tools for installing and managing OpenStack
>>* Kolla containers and Kolla-Ansible
>>* Loci containers and OpenStack Helm
>> * OpenStack-hosted APIs for managing container application
>>   infrastructure.
>>* Magnum
>>* Zun
>> * Community-driven integration of Kubernetes and OpenStack with K8s
>>   Cloud Provider OpenStack
>> * Projects that can stand alone in integrations with Kubernetes and
>>   other cloud technology
>>* Cinder
>>* Neutron with Kuryr and Calico integrations
>>* Keystone authentication and authorization
>>
>> I'm looking for volunteers to help produce the content for these sections
>> (and any others we may uncover to be useful) for presenting a complete
>> picture of OpenStack and container integrations. If you're involved with
>> one of these projects, or are using any of these tools in
>> production, it would be fantastic to get your input in producing the
>> appropriate section. We especially want real-world deployments to use as
>> small case studies to inform the work.
>>
>> During the process of creating the white-paper, we will be working with a
>> technical writer and the Foundation design team to produce a document that
>> is consistent in voice, has accurate and informative graphics that
>> can be used to illustrate the major points and themes of the white-paper,
>> and that can be used as stand-alone media for conferences and
>> presentations.
>>
>> Over the next week, I'll be reaching out to individuals and inviting them
>> to collaborate. This is also a general invitation to collaborate, and if
>> you'd like to help out with a section please reach out to me here, on the
>> K8s #sig-openstack Slack channel, or at my work e-mail,
>> ch...@openstack.org.
>> Starting next week, we'll work out a schedule for producing and delivering
>> the white-paper by the Vancouver Summit. We are very short on time, so
>> we will have to be focused to quickly produce high-quality content.
>>
>> Thanks in advance to everyone who participates in writing this
>> document. I'm looking forward to working with you in the coming weeks to
>> publish this important resource for clearly describing the multitude of
>> interactions between these complementary technologies.
>>
>> -Chris Hoge
>> K8s-SIG-OpenStack/OpenStack-SIG-K8s Co-Lead
>>
>>
>> 
>> __
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscrib
>> e
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>


-- 
Zhipeng (Howard) Huang

Standard Engineer
IT Standard & Patent/IT Product Line
Huawei Technologies Co,. Ltd
Email: huangzhip...@huawei.com
Office: Huawei Industrial Base, Longgang, Shenzhen

(Previous)
Research Assistant
Mobile Ad-Hoc Network Lab, Calit2
University of California, Irvine
Email: zhipe...@uci.edu
Office: Calit2 Building Room 2402

OpenStack, OPNFV, OpenDaylight, OpenCompute Aficionado
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] All Hail our Newest Release Name - OpenStack Stein

[Zhipeng Huang]

In hindsight, it would be much fun the R release named Ramm :P

On Fri, Mar 30, 2018 at 3:10 AM, Paul Belanger 
wrote:

> Hi everybody!
>
> As the subject reads, the "S" release of OpenStack is officially "Stein".
> As
> been with previous elections this wasn't the first choice, that was
> "Solar".
>
> Solar was judged to have legal risk, so as per our name selection process,
> we
> moved to the next name on the list.
>
> Thanks to everybody who participated, and look forward to making OpenStack
> Stein
> a great release.
>
> Paul
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>



-- 
Zhipeng (Howard) Huang

Standard Engineer
IT Standard & Patent/IT Product Line
Huawei Technologies Co,. Ltd
Email: huangzhip...@huawei.com
Office: Huawei Industrial Base, Longgang, Shenzhen

(Previous)
Research Assistant
Mobile Ad-Hoc Network Lab, Calit2
University of California, Irvine
Email: zhipe...@uci.edu
Office: Calit2 Building Room 2402

OpenStack, OPNFV, OpenDaylight, OpenCompute Aficionado
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [cyborg]Team Weekly Meeting 2018.03.28

[Zhipeng Huang]

Hi Team,

Weekly meeting as usual starting UTC1400 at #openstack-cyborg, initial
agenda as follows:

* Cyborg GPU support discussion
* Clock driver introduction by ZTE team
* Rocky dev discussion:
https://review.openstack.org/#/q/status:open+project:openstack/cyborg

-- 
Zhipeng (Howard) Huang

Standard Engineer
IT Standard & Patent/IT Product Line
Huawei Technologies Co,. Ltd
Email: huangzhip...@huawei.com
Office: Huawei Industrial Base, Longgang, Shenzhen

(Previous)
Research Assistant
Mobile Ad-Hoc Network Lab, Calit2
University of California, Irvine
Email: zhipe...@uci.edu
Office: Calit2 Building Room 2402

OpenStack, OPNFV, OpenDaylight, OpenCompute Aficionado
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Nova] [Cyborg] Separate spec for compute node flows?

[Zhipeng Huang]

Hi Sundar,

Zhuli will work on os-acc spec, and Li Liu will work on the glance and
metadata one, as we assigned during ptg. But you are very welcomed to reach
out to them and work together if you have the bandwidth :)

On Wed, Mar 21, 2018 at 3:00 PM, Nadathur, Sundar  wrote:

> Hi all,
>
> The Cyborg Nova scheduling specification
> 
> addresses the scheduling aspects alone. There needs to be a separate spec
> to address:
> * Cyborg/Nova interactions in the compute node, incl. the newly proposed
> os-acc library.
> * Programming, including fetching bitstreams from Glance.
> * Bitstream metadata.
>
> Shall I send such a spec while the first one is still in review?
> Regards,
> Sundar
>
>
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>


-- 
Zhipeng (Howard) Huang

Standard Engineer
IT Standard & Patent/IT Product Line
Huawei Technologies Co,. Ltd
Email: huangzhip...@huawei.com
Office: Huawei Industrial Base, Longgang, Shenzhen

(Previous)
Research Assistant
Mobile Ad-Hoc Network Lab, Calit2
University of California, Irvine
Email: zhipe...@uci.edu
Office: Calit2 Building Room 2402

OpenStack, OPNFV, OpenDaylight, OpenCompute Aficionado
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [cyborg]Team Weekly Meeting 2018.03.21

[Zhipeng Huang]

Hi Team,

Meeting today starting UTC1400 at #openstack-cyborg, initial agenda as
follows:

1. Sub-team lead progress update
2. rocky spec/patch review:
https://review.openstack.org/#/q/status:open+project:openstack/cyborg



-- 
Zhipeng (Howard) Huang

Standard Engineer
IT Standard & Patent/IT Product Line
Huawei Technologies Co,. Ltd
Email: huangzhip...@huawei.com
Office: Huawei Industrial Base, Longgang, Shenzhen

(Previous)
Research Assistant
Mobile Ad-Hoc Network Lab, Calit2
University of California, Irvine
Email: zhipe...@uci.edu
Office: Calit2 Building Room 2402

OpenStack, OPNFV, OpenDaylight, OpenCompute Aficionado
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Nova] [Cyborg] Tracking multiple functions

[Zhipeng Huang]

Hi Sundar,

I think the two points you raised is valid and please also reflect that in
the spec you are helping drafting :)

On Mon, Mar 19, 2018 at 12:34 AM, Nadathur, Sundar <
sundar.nadat...@intel.com> wrote:

> Sorry for the delayed response. I broadly agree with previous replies.
> For the concerns about the impact of Cyborg weigher on scheduling
> performance , there are some options (apart from filtering candidates as
> much as possible in Placement):
> * Handle hosts in bulk by extending BaseWeigher
> <https://github.com/openstack/nova/blob/master/nova/weights.py#L67> and
> overriding weigh_objects
> <https://github.com/openstack/nova/blob/master/nova/weights.py#L92>(),
> instead of handling one host at a time.
> * If we have to handle one host at a time for whatever reason, since the
> weigher is maintained by Cyborg, it could directly query Cyborg DB rather
> than go through Cyborg REST API. This will be not unlike other weighers.
>
> Given these and other possible optimizations, it may be too soon to worry
> about the performance impact.
>
> I am working on a spec that will capture the flow discussed in the PTG. I
> will try to address these aspects as well.
>
> Thanks & Regards,
> Sundar
>
>
> On 3/8/2018 4:53 AM, Zhipeng Huang wrote:
>
> @jay I'm also against a weigher in nova/placement. This should be an
> optional step depends on vendor implementation, not a default one.
>
> @Alex I think we should explore the idea of preferred trait.
>
> @Mathew: Like Sean said, Cyborg wants to support both reprogrammable FPGA
> and pre-programed ones.
> Therefore it is correct that in your description, the programming
> operation should be a call from Nova to Cyborg, and cyborg will complete
> the operation while nova waits. The only problem is that the weigher step
> should be an optional one.
>
>
> On Wed, Mar 7, 2018 at 9:21 PM, Jay Pipes <jaypi...@gmail.com> wrote:
>
>> On 03/06/2018 09:36 PM, Alex Xu wrote:
>>
>>> 2018-03-07 10:21 GMT+08:00 Alex Xu <sou...@gmail.com >> sou...@gmail.com>>:
>>>
>>>
>>>
>>> 2018-03-06 22:45 GMT+08:00 Mooney, Sean K <sean.k.moo...@intel.com
>>> <mailto:sean.k.moo...@intel.com>>:
>>>
>>> __ __
>>>
>>> __ __
>>>
>>> *From:*Matthew Booth [mailto:mbo...@redhat.com
>>> <mailto:mbo...@redhat.com>]
>>> *Sent:* Saturday, March 3, 2018 4:15 PM
>>> *To:* OpenStack Development Mailing List (not for usage
>>> questions) <openstack-dev@lists.openstack.org
>>> <mailto:openstack-dev@lists.openstack.org>>
>>> *Subject:* Re: [openstack-dev] [Nova] [Cyborg] Tracking multiple
>>> functions
>>>
>>> __ __
>>>
>>> On 2 March 2018 at 14:31, Jay Pipes <jaypi...@gmail.com
>>> <mailto:jaypi...@gmail.com>> wrote:
>>>
>>> On 03/02/2018 02:00 PM, Nadathur, Sundar wrote:
>>>
>>> Hello Nova team,
>>>
>>>   During the Cyborg discussion at Rocky PTG, we
>>> proposed a flow for FPGAs wherein the request spec asks
>>> for a device type as a resource class, and optionally a
>>> function (such as encryption) in the extra specs. This
>>> does not seem to work well for the usage model that I’ll
>>> describe below.
>>>
>>> An FPGA device may implement more than one function. For
>>> example, it may implement both compression and
>>> encryption. Say a cluster has 10 devices of device type
>>> X, and each of them is programmed to offer 2 instances
>>> of function A and 4 instances of function B. More
>>> specifically, the device may implement 6 PCI functions,
>>> with 2 of them tied to function A, and the other 4 tied
>>> to function B. So, we could have 6 separate instances
>>> accessing functions on the same device.
>>>
>>> __ __
>>>
>>> Does this imply that Cyborg can't reprogram the FPGA at all?
>>>
>>> */[Mooney, Sean K] cyborg is intended to support fixed function
>>> acclerators also so it will not always be able to program the
>>> accelerator. In this case where an fpga is preprogramed

Re: [openstack-dev] [cyborg]Summary of Mar 14 Meeting

[Zhipeng Huang]

Hi Sundar,

Thanks and yes I think these are the gist of our discussion during last
meeting :)

On Sun, Mar 18, 2018 at 12:40 PM, Nadathur, Sundar <
sundar.nadat...@intel.com> wrote:

> Hi Howard and all,
>
> Re. my AR to write a spec, please confirm the following:
> * Since the weigher is part of the overall scheduling flow, I presume the
> spec has to cover the scheduling flow that we hashed out in the PTG. The
> compute node aspects could be a separate spec.
>
> * Since there were many questions about the use cases as well, they would
> also need to be covered in the spec.
>
> * This spec would be complementary to current Cyborg-Nova spec
> <https://github.com/openstack/cyborg/blob/master/doc/specs/queens/approved/cyborg-nova-interaction.rst>
> . (It is in addition to it, does not replace it.)
>
> * The spec is not confined to FPGAs but should cover all devices, just as
> the current Cyborg-Nova spec
> <https://github.com/openstack/cyborg/blob/master/doc/specs/queens/approved/cyborg-nova-interaction.rst>
> .
>
> Thanks,
>
> Sundar
>
> On 3/15/2018 9:00 PM, Zhipeng Huang wrote:
>
> Hi Team,
>
> Here are the meeting summary for our post-ptg kickoff meeting.
>
> []
> 2. Rocky Cycle Task Assignments:
>
> Please refer to the meeting minutes about the action items:
> http://eavesdrop.openstack.org/meetings/openstack_cyborg/2018/
> openstack_cyborg.2018-03-14-14.07.html
> --
> Zhipeng (Howard) Huang
>
> Standard Engineer
> IT Standard & Patent/IT Product Line
> Huawei Technologies Co,. Ltd
> Email: huangzhip...@huawei.com
> Office: Huawei Industrial Base, Longgang, Shenzhen
>
> (Previous)
> Research Assistant
> Mobile Ad-Hoc Network Lab, Calit2
> University of California, Irvine
> Email: zhipe...@uci.edu
> Office: Calit2 Building Room 2402
>
> OpenStack, OPNFV, OpenDaylight, OpenCompute Aficionado
>
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: 
> openstack-dev-requ...@lists.openstack.org?subject:unsubscribehttp://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>


-- 
Zhipeng (Howard) Huang

Standard Engineer
IT Standard & Patent/IT Product Line
Huawei Technologies Co,. Ltd
Email: huangzhip...@huawei.com
Office: Huawei Industrial Base, Longgang, Shenzhen

(Previous)
Research Assistant
Mobile Ad-Hoc Network Lab, Calit2
University of California, Irvine
Email: zhipe...@uci.edu
Office: Calit2 Building Room 2402

OpenStack, OPNFV, OpenDaylight, OpenCompute Aficionado
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [cyborg]Summary of Mar 14 Meeting

[Zhipeng Huang]

Hi Team,

Here are the meeting summary for our post-ptg kickoff meeting.

0. Meeting recordings: https://www.youtube.com/watch?v=6AZn0SUC_hw ,
https://www.youtube.com/watch?v=-wE2GkSibDo ,
https://www.youtube.com/watch?v=E40JOm311WI

1. PoC from Shaohe and Dolpher (
https://etherpad.openstack.org/p/cyborg-nova-poc)
(1) Agree with the resource class and trait custom definition
(2) Move the claim/release design to the os-acc lib. Also change the
allocation to assigment in order to avoid confusion with Placement
funcationality.
(3) Should avoid cache image as much as possible, but when necessary it
is recommended that cyborg config a default temp folder for the image
cache. Vendoer implementation could point to that location with subfolders
for their images
(4) Agreed that cyborg-agent will be responsible for pulling the image
and cyborg-conductor for coordination with Placement.
(5) Agreed that the programming operation should be a blocking one (if
it fails then everything fails) since that although the delay of
programming varies generally it should not be a major concern.

2. Rocky Cycle Task Assignments:

Please refer to the meeting minutes about the action items:
http://eavesdrop.openstack.org/meetings/openstack_cyborg/2018/openstack_cyborg.2018-03-14-14.07.html

-- 
Zhipeng (Howard) Huang

Standard Engineer
IT Standard & Patent/IT Product Line
Huawei Technologies Co,. Ltd
Email: huangzhip...@huawei.com
Office: Huawei Industrial Base, Longgang, Shenzhen

(Previous)
Research Assistant
Mobile Ad-Hoc Network Lab, Calit2
University of California, Irvine
Email: zhipe...@uci.edu
Office: Calit2 Building Room 2402

OpenStack, OPNFV, OpenDaylight, OpenCompute Aficionado
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Openstack-sigs] [First Contact][SIG] [PTG] Summary of Discussions

[Zhipeng Huang]

Hi folks,

Sorry was not be able to make it to the First Contact SIG discussions in
Dublin. The only suggestion I have is to have as many project as possible
to have a dedicated FC SIG wiki page for localize onboarding support.

For example like what we do in Cyborg:
https://wiki.openstack.org/wiki/Cyborg/FirstContact I've captured all the
discussions of the China Dev Group via a Chinese streaming site and also
put the wiki link in the wechat group description, so that new developer
know where to go to for a localize support.

For communciation tools, per irc  I agree converge to #openstack-dev is
better than maintaining some independent channels. But also from my
experience video conf in native lang is more effective.

On Thu, Mar 15, 2018 at 8:28 AM, Kendall Nelson 
wrote:

> We talked about this more during the meeting last night. Most people were
> pretty neutral on the topic.
>
> I personally feel like #openstack-dev is the ideal place to direct people
> once they get set up on irc and are interested in contributing, but maybe
> that is because my perception of the chats in #openstack isn't correct.
> Looking at the definition in the IRC channel list[1] and the channel
> topic[2] I feel like it more for support questions on running openstack? I
> dunno. I honestly didn't spend time in the channel really until I joined
> last night so maybe my perception just needs an update. I am all ears for
> your reasoning behind #openstack instead of #openstack-dev though too.
> Please enlighten me :)
>
> -Kendall (diablo_rojo)
>
> [1] https://wiki.openstack.org/wiki/IRC
> [2] Openstack Support Channel, Development in #openstack-dev | Wiki:
> http://wiki.openstack.org/ | Docs: http://docs.openstack.org/ | Answers:
> https://ask.openstack.org | Logs: http://eavesdrop.openstack.org/irclogs/
> | Paste: http://paste.openstack.org/
>
>
> On Tue, Mar 13, 2018 at 3:30 PM Amy Marrich  wrote:
>
>> Just one comment on this section before I forget again:
>> #IRC Channels#
>> We want to get rid of #openstack-101 and begin using #openstack-dev
>> instead. The 101 channel isn't watched closely enough anymore and it makes
>> more sense to move onboarding activities (like in OpenStack Upstream
>> Institute) to a channel where there are people that can answer questions
>> rather than asking those to move to a new channel. For those concerned
>> about noise, OUI is run the weekend before the summit when most people are
>> traveling to the Summit anyway.
>>
>> I would recommend sending folks to #openstack vs #openstack-dev by
>> default.
>>
>> Amy (spotz)
>>
>> On Mon, Mar 5, 2018 at 2:00 PM, Kendall Nelson 
>> wrote:
>>
>>> Hello Everyone :)
>>>
>>> It was wonderful to see and talk with so many of you last week! For
>>> those that couldn't attend our whole day of chats or those that couldn't
>>> attend at all, I thought I would put forth a summary of our discussions
>>> which were mostly noted in the etherpad[1]
>>>
>>> #Contributor Guide#
>>>
>>> - Walkthrough: We walked through every section of what exists and came
>>> up with a variety of improvements on what is there. Most of these items
>>> have been added to our StoryBoard project[2]. This came up again Tuesday in
>>> docs sessions and I have added those items to StoryBoard as well.
>>>
>>> - Google Analytics: It was discussed we should do something about
>>> getting the contributor portal[3] to appear higher in Google searches about
>>> onboarding. Not sure what all this entails. NEEDS AN OWNER IF ANYONE WANTS
>>> TO VOLUNTEER.
>>>
>>> #Mission Statement#
>>>
>>> We updated our mission statement[4]! It now states:
>>>
>>> To provide a place for new contributors to come for information and
>>> advice. This group will also analyze and document successful contribution
>>> models while seeking out and providing information to new members of the
>>> community.
>>>
>>> #Weekly Meeting#
>>>
>>> We discussed beginning a weekly meeting- optimized for APAC/Europe and
>>> settled on 800 UTC in #openstack-meeting on Wednesdays. Proposed here[5].
>>> For now I added a section to our wiki for agenda organization[6]. The two
>>> main items we want to cover on a weekly basis are new contributor patches
>>> in gerrit and if anything has come up on ask.openstack.org about
>>> contributors so those will be standing agenda items.
>>>
>>> #Forum Session#
>>>
>>> We discussed proposing some forum sessions in order to get more
>>> involvement from operators. Currently, our activities focus on development
>>> activities and we would like to diversify. When this SIG was first proposed
>>> we wanted to have two chairs- one to represent developers and one to
>>> represent operators. We will propose a session or two when the call for
>>> forum proposals go out (should be today).
>>>
>>> #IRC Channels#
>>> We want to get rid of #openstack-101 and begin using #openstack-dev
>>> instead. The 101 channel isn't watched closely enough anymore 

Re: [openstack-dev] [cyborg]Weekly Team Meeting 2018.03.14 Agenda (No Time Change For US)

[Zhipeng Huang]

Update:

1. ZOOM link:
- Part 1:  https://zoom.us/j/511883630 (starting UTC1400 )
- Part 2:  https://zoom.us/j/741227793

2. Agenda:
- PoC demo from Shaohe
- Rocky Work Assignment: (nova-cyborg interaction, programmability,
multi-tenancy/quota, more drivers, metadata, GPU, documentation, testing)




On Wed, Mar 14, 2018 at 10:14 AM, Zhipeng Huang <zhipengh...@gmail.com>
wrote:

> Yes that would be one of the issue we need to discuss after the PoC demo :)
>
> On Wed, Mar 14, 2018 at 10:11 AM, Nadathur, Sundar <
> sundar.nadat...@intel.com> wrote:
>
>> Hi Howard,
>>
>> Can we discuss the possibility of using a filter/weigher that invokes
>> Cyborg API, as we discussed during the Cyborg/Nova discussion in the PTG?
>>
>>
>>
>> This is line 56 in https://etherpad.openstack.org
>> /p/cyborg-ptg-rocky-nova-cyborg-interaction .
>>
>>
>>
>> Regards,
>>
>> Sundar
>>
>>
>>
>> *From:* Zhipeng Huang [mailto:zhipengh...@gmail.com]
>> *Sent:* Monday, March 12, 2018 1:28 AM
>> *To:* OpenStack Development Mailing List (not for usage questions) <
>> openstack-dev@lists.openstack.org>
>> *Cc:* Konstantinos Samaras-Tsakiris > @cern.ch>; Dutch Althoff <dalth...@xilinx.com>
>> *Subject:* [openstack-dev] [cyborg]Weekly Team Meeting 2018.03.14 Agenda
>> (No Time Change For US)
>>
>>
>>
>> Hi Team,
>>
>>
>>
>> We will resume the team meeting this week. The meeting starting time is
>> still ET 10:00am/PT 7:00am, whereas in China it is moved one hour early to
>> 10:00pm. For Europe please refer to UTC1400 as the baseline.
>>
>>
>>
>> This week we will have a special 2 hour meeting. In the first one hour we
>> will have Shaohe demo the PoC Intel dev team had conducted, and in the
>> second half we will confirm the task and milestones for Rocky based upon
>> the PTG discussion (summary sent out last Friday).
>>
>>
>>
>> ZOOM link will be provided before the meeting :)
>>
>>
>>
>> If there are any other topics anyone would like to propose, feel free to
>> reply to this email thread.
>>
>>
>>
>> --
>>
>> Zhipeng (Howard) Huang
>>
>>
>>
>> Standard Engineer
>>
>> IT Standard & Patent/IT Product Line
>>
>> Huawei Technologies Co,. Ltd
>>
>> Email: huangzhip...@huawei.com
>>
>> Office: Huawei Industrial Base, Longgang, Shenzhen
>>
>>
>>
>> (Previous)
>>
>> Research Assistant
>>
>> Mobile Ad-Hoc Network Lab, Calit2
>>
>> University of California, Irvine
>>
>> Email: zhipe...@uci.edu
>>
>> Office: Calit2 Building Room 2402
>>
>>
>>
>> OpenStack, OPNFV, OpenDaylight, OpenCompute Aficionado
>>
>> 
>> __
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscrib
>> e
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>>
>
>
> --
> Zhipeng (Howard) Huang
>
> Standard Engineer
> IT Standard & Patent/IT Product Line
> Huawei Technologies Co,. Ltd
> Email: huangzhip...@huawei.com
> Office: Huawei Industrial Base, Longgang, Shenzhen
>
> (Previous)
> Research Assistant
> Mobile Ad-Hoc Network Lab, Calit2
> University of California, Irvine
> Email: zhipe...@uci.edu
> Office: Calit2 Building Room 2402
>
> OpenStack, OPNFV, OpenDaylight, OpenCompute Aficionado
>



-- 
Zhipeng (Howard) Huang

Standard Engineer
IT Standard & Patent/IT Product Line
Huawei Technologies Co,. Ltd
Email: huangzhip...@huawei.com
Office: Huawei Industrial Base, Longgang, Shenzhen

(Previous)
Research Assistant
Mobile Ad-Hoc Network Lab, Calit2
University of California, Irvine
Email: zhipe...@uci.edu
Office: Calit2 Building Room 2402

OpenStack, OPNFV, OpenDaylight, OpenCompute Aficionado
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [cyborg]Weekly Team Meeting 2018.03.14 Agenda (No Time Change For US)

[Zhipeng Huang]

Yes that would be one of the issue we need to discuss after the PoC demo :)

On Wed, Mar 14, 2018 at 10:11 AM, Nadathur, Sundar <
sundar.nadat...@intel.com> wrote:

> Hi Howard,
>
> Can we discuss the possibility of using a filter/weigher that invokes
> Cyborg API, as we discussed during the Cyborg/Nova discussion in the PTG?
>
>
>
> This is line 56 in https://etherpad.openstack.org/p/cyborg-ptg-rocky-nova-
> cyborg-interaction .
>
>
>
> Regards,
>
> Sundar
>
>
>
> *From:* Zhipeng Huang [mailto:zhipengh...@gmail.com]
> *Sent:* Monday, March 12, 2018 1:28 AM
> *To:* OpenStack Development Mailing List (not for usage questions) <
> openstack-dev@lists.openstack.org>
> *Cc:* Konstantinos Samaras-Tsakiris <konstantinos.samaras-tsaki...@cern.ch>;
> Dutch Althoff <dalth...@xilinx.com>
> *Subject:* [openstack-dev] [cyborg]Weekly Team Meeting 2018.03.14 Agenda
> (No Time Change For US)
>
>
>
> Hi Team,
>
>
>
> We will resume the team meeting this week. The meeting starting time is
> still ET 10:00am/PT 7:00am, whereas in China it is moved one hour early to
> 10:00pm. For Europe please refer to UTC1400 as the baseline.
>
>
>
> This week we will have a special 2 hour meeting. In the first one hour we
> will have Shaohe demo the PoC Intel dev team had conducted, and in the
> second half we will confirm the task and milestones for Rocky based upon
> the PTG discussion (summary sent out last Friday).
>
>
>
> ZOOM link will be provided before the meeting :)
>
>
>
> If there are any other topics anyone would like to propose, feel free to
> reply to this email thread.
>
>
>
> --
>
> Zhipeng (Howard) Huang
>
>
>
> Standard Engineer
>
> IT Standard & Patent/IT Product Line
>
> Huawei Technologies Co,. Ltd
>
> Email: huangzhip...@huawei.com
>
> Office: Huawei Industrial Base, Longgang, Shenzhen
>
>
>
> (Previous)
>
> Research Assistant
>
> Mobile Ad-Hoc Network Lab, Calit2
>
> University of California, Irvine
>
> Email: zhipe...@uci.edu
>
> Office: Calit2 Building Room 2402
>
>
>
> OpenStack, OPNFV, OpenDaylight, OpenCompute Aficionado
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>


-- 
Zhipeng (Howard) Huang

Standard Engineer
IT Standard & Patent/IT Product Line
Huawei Technologies Co,. Ltd
Email: huangzhip...@huawei.com
Office: Huawei Industrial Base, Longgang, Shenzhen

(Previous)
Research Assistant
Mobile Ad-Hoc Network Lab, Calit2
University of California, Irvine
Email: zhipe...@uci.edu
Office: Calit2 Building Room 2402

OpenStack, OPNFV, OpenDaylight, OpenCompute Aficionado
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [cyborg]Weekly Team Meeting 2018.03.14 Agenda (No Time Change For US)

[Zhipeng Huang]

Hi Team,

We will resume the team meeting this week. The meeting starting time is
still ET 10:00am/PT 7:00am, whereas in China it is moved one hour early to
10:00pm. For Europe please refer to UTC1400 as the baseline.

This week we will have a special 2 hour meeting. In the first one hour we
will have Shaohe demo the PoC Intel dev team had conducted, and in the
second half we will confirm the task and milestones for Rocky based upon
the PTG discussion (summary sent out last Friday).

ZOOM link will be provided before the meeting :)

If there are any other topics anyone would like to propose, feel free to
reply to this email thread.

-- 
Zhipeng (Howard) Huang

Standard Engineer
IT Standard & Patent/IT Product Line
Huawei Technologies Co,. Ltd
Email: huangzhip...@huawei.com
Office: Huawei Industrial Base, Longgang, Shenzhen

(Previous)
Research Assistant
Mobile Ad-Hoc Network Lab, Calit2
University of California, Irvine
Email: zhipe...@uci.edu
Office: Calit2 Building Room 2402

OpenStack, OPNFV, OpenDaylight, OpenCompute Aficionado
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [cyborg]Dublin Rocky PTG Summary

[Zhipeng Huang]

 Hi Team,

Thanks to our topic leads' efforts, below is the aggregated summary from
our dublin ptg session discussion. Please check it out and feel free to
feedback any concerns you might have.

Queens Cycle Review
Etherpad:https://etherpad.openstack.org/p/cyborg-queens-retrospective
1. Adopt MS based release method starting in Rocky to avoid chaos
2. Establish subteams alongside core team that could cover various
important aspects

   - doc team: lead - Li Liu, yumeng


   - release team: lead - howard, zhuli


   - driver team: lead - Shaohe, Dutch

3. Intel might consider setup one for its FPGA card for Cyborg 3rd Party CI
support
4. Promote Shaohe as the new core reviewer

Quota and Multi-tenancy Support
Etherpad: https://etherpad.openstack.org/p/cyborg-ptg-rocky-quota
Slide:
https://docs.google.com/presentation/d/1DUKWW2vgqUI3Udl4UDvxgJ53Ve5LmyaBpX4u--rVrCc/edit?usp=sharing

1. Provide project and user level quota support
2. Treat all resources as the reserved resource type
3. Add quota engine and quota driver for the quota support
4. Tables: quotas, quota_usage, reservation
5. Transactions operation: reserve, commit, rollback

   - Concerns on rollback


   - Implement a two-stage resevation and rollback


   - reserve - commit - rollback (if failed)

6. Experiment with oslo.limit for quota/nested quota support from Keystone
(maybe slated for MS3)

Programability Support
Slide:
Li Liu:
https://docs.google.com/presentation/d/1rzecmKhvjAJcfWHPZb8wPkoW6HDGcEHggxV9rUdYINs/edit?usp=sharing

Sundar:
https://docs.google.com/presentation/d/1Bc6v_Uis_txxj1awpRuLg5KQsC2xrsqnHb54UttaBQo/edit?usp=sharing

1. Security: 2 dimensions: At-rest/In-use,Authentication and/or
encryption.Specific cryptoalgorithms, key lengths and key storage be left
to cloud operators and/orvendors. (could consider interaction with Barbican
which could be used for keymgmt)

   - At-rest (storage): CanGlance handle any authentication/encryption
   algorithm that an implementationwants?


   - In-use: Transfer fromthe repository to compute mode should be
   protected. This means the compute nodeor the FPGA itself is doing the
   decryption. Should the actual auth/decrypt beleft to the vendor driver?

2. Licensing/policies: A cloud operator maywant to set policies on image
usage and enforce licenses. I suggest this beleft to the implementation as
well.
3. Repository: Glance is presumably thedefault. However, some operators
have gone the proprietary way ut may want touse a standardized way in the
future. Do we want to enable a migration path forthese folks to come to
OpenStack?
4. Overall flow:
ComputeNode <-->[IP Policy Engine] <--> IP.Repository
Cyborg can define a standard API forComputeNode<-->IPPolicyEngine, and
PolicyEngine <--> Repository.
5. A strawman for the API:

   - Request: Acceleratortype, Region type


   - Response: Imageproviding the accelerator type matching the region type

6. What if there is more than one image: Amechanism is needed to pick the
most suitable images based on users' request.Or just return warnings when
there are multiple hits.
7. There is broad consensus (and no objections) to allow for the
possibility of an 'IP Policy Engine' between the compute node and IP
repository (Glance), with well-defined APIs from Cyborg. This is expected
to enable the use cases above.
8. add bitstream_uuid to the kv pair list. This refers to the uuid id
generated during sythesis time.

More Driver Support
1. Dutch will help lead on the Xilinx driver development in Queens cycle
2. Yumeng will confirm with her team about the clock driver motivation
3. Howard will contact NVIDIA team for their driver support

Finishing Up Nova Cyborg Interaction
Etherpad:
https://etherpad.openstack.org/p/cyborg-ptg-rocky-nova-cyborg-interaction
1. tentatively agreed flow:

   - Cyborg responsble for tracking available FPGA types/hardware and FPGA
   images/functions


   - The flavor will define the FPGA type/hardware, while the
   image/function will be defined on the glance image. The latter can be
   restricted to prevent users providing their own images. It should be
   possible to state the required function/image in the flavor extra specs.


   - It is recommended to add traits for image/function capability for each
   device/region. This may result in a profusion of traits, but that helps
   Placement do more filtering up front. Having more traits scales better than
   having Placement return a large list of hosts which subsequent
   filters/weighers need to handle.


   - Placement used to provide the FPGA type/hardware. This will filter out
   hosts that don't have the required hardware


   - (Optional)Weighers used to attempt to favour hosts whose FPGAs already
   have the required image/function.


   - Once a host has been chosen, the FPGA programming will take place
   synchronously as part of the instance creation (like VIF, storage
   creation). os-acc will define the common interface for how nova can do this
   wiring

2. 

Re: [openstack-dev] [cyborg]No Meeting This Week

[Zhipeng Huang]

Hi Ed,

it should be categoried under openstack-cyborg :) Our weekly meeting is Wed
UTC1500 on #openstack-cyborg channel. Meeting minutes could be found:
https://wiki.openstack.org/wiki/Cyborg/MeetingLogs

On Fri, Mar 9, 2018 at 4:36 AM, Ed Leafe <e...@leafe.com> wrote:

> On Mar 5, 2018, at 9:51 PM, Zhipeng Huang <zhipengh...@gmail.com> wrote:
>
> > As most of us are rekubrating from PTG and snowenpstack last week, let's
> cancel the team meeting this week. At the mean time I have solicitate the
> meeting summary from topic leads, and will send out a summary of the
> summaries later :)
>
> When is your meeting? I don’t see it listed on
> http://eavesdrop.openstack.org.
>
>
> -- Ed Leafe
>
>
>
>
>
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>



-- 
Zhipeng (Howard) Huang

Standard Engineer
IT Standard & Patent/IT Product Line
Huawei Technologies Co,. Ltd
Email: huangzhip...@huawei.com
Office: Huawei Industrial Base, Longgang, Shenzhen

(Previous)
Research Assistant
Mobile Ad-Hoc Network Lab, Calit2
University of California, Irvine
Email: zhipe...@uci.edu
Office: Calit2 Building Room 2402

OpenStack, OPNFV, OpenDaylight, OpenCompute Aficionado
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Nova] [Cyborg] Tracking multiple functions

[Zhipeng Huang]

@jay I'm also against a weigher in nova/placement. This should be an
optional step depends on vendor implementation, not a default one.

@Alex I think we should explore the idea of preferred trait.

@Mathew: Like Sean said, Cyborg wants to support both reprogrammable FPGA
and pre-programed ones.
Therefore it is correct that in your description, the programming operation
should be a call from Nova to Cyborg, and cyborg will complete the
operation while nova waits. The only problem is that the weigher step
should be an optional one.


On Wed, Mar 7, 2018 at 9:21 PM, Jay Pipes  wrote:

> On 03/06/2018 09:36 PM, Alex Xu wrote:
>
>> 2018-03-07 10:21 GMT+08:00 Alex Xu  sou...@gmail.com>>:
>>
>>
>>
>> 2018-03-06 22:45 GMT+08:00 Mooney, Sean K > >:
>>
>> __ __
>>
>> __ __
>>
>> *From:*Matthew Booth [mailto:mbo...@redhat.com
>> ]
>> *Sent:* Saturday, March 3, 2018 4:15 PM
>> *To:* OpenStack Development Mailing List (not for usage
>> questions) > >
>> *Subject:* Re: [openstack-dev] [Nova] [Cyborg] Tracking multiple
>> functions
>>
>> __ __
>>
>> On 2 March 2018 at 14:31, Jay Pipes > > wrote:
>>
>> On 03/02/2018 02:00 PM, Nadathur, Sundar wrote:
>>
>> Hello Nova team,
>>
>>   During the Cyborg discussion at Rocky PTG, we
>> proposed a flow for FPGAs wherein the request spec asks
>> for a device type as a resource class, and optionally a
>> function (such as encryption) in the extra specs. This
>> does not seem to work well for the usage model that I’ll
>> describe below.
>>
>> An FPGA device may implement more than one function. For
>> example, it may implement both compression and
>> encryption. Say a cluster has 10 devices of device type
>> X, and each of them is programmed to offer 2 instances
>> of function A and 4 instances of function B. More
>> specifically, the device may implement 6 PCI functions,
>> with 2 of them tied to function A, and the other 4 tied
>> to function B. So, we could have 6 separate instances
>> accessing functions on the same device.
>>
>> __ __
>>
>> Does this imply that Cyborg can't reprogram the FPGA at all?
>>
>> */[Mooney, Sean K] cyborg is intended to support fixed function
>> acclerators also so it will not always be able to program the
>> accelerator. In this case where an fpga is preprogramed with a
>> multi function bitstream that is statically provisioned cyborge
>> will not be able to reprogram the slot if any of the fuctions
>> from that slot are already allocated to an instance. In this
>> case it will have to treat it like a fixed function device and
>> simply allocate a unused  vf  of the corret type if available.
>> /*
>>
>>
>> 
>>
>>
>> In the current flow, the device type X is modeled as a
>> resource class, so Placement will count how many of them
>> are in use. A flavor for ‘RC device-type-X + function A’
>> will consume one instance of the RC device-type-X.  But
>> this is not right because this precludes other functions
>> on the same device instance from getting used.
>>
>> One way to solve this is to declare functions A and B as
>> resource classes themselves and have the flavor request
>> the function RC. Placement will then correctly count the
>> function instances. However, there is still a problem:
>> if the requested function A is not available, Placement
>> will return an empty list of RPs, but we need some way
>> to reprogram some device to create an instance of
>> function A.
>>
>>
>> Clearly, nova is not going to be reprogramming devices with
>> an instance of a particular function.
>>
>> Cyborg might need to have a separate agent that listens to
>> the nova notifications queue and upon seeing an event that
>> indicates a failed build due to lack of resources, then
>> Cyborg can try and reprogram a device and then try
>> rebuilding the original request.
>>
>> __ __
>>
>> It was my understanding from that discussion that we intend to
>> insert Cyborg into the spawn workflow for 

Re: [openstack-dev] [cyborg][glance][nova]cyborg FPGA management flow disscusion.

[Zhipeng Huang]

Thanks Shaohe,

Let's schedule a video conf session next week.

On Thu, Mar 8, 2018 at 11:41 AM, Feng, Shaohe <shaohe.f...@intel.com> wrote:

> Hi All:
>
> The POC is here:
> *https://github.com/shaohef/cyborg* <https://github.com/shaohef/cyborg>
>
> BR
> Shaohe Feng
>
> _
> *From:* Feng, Shaohe
> *Sent:* 2018年2月12日 15:06
> *To:* openstack-dev@lists.openstack.org; openstack-operators@lists.
> openstack.org
> *Cc:* Du, Dolpher <dolpher...@intel.com>; Zhipeng Huang <
> zhipengh...@gmail.com>; Ding, Jian-feng <jian-feng.d...@intel.com>; Sun,
> Yih Leong <yih.leong@intel.com>; Nadathur, Sundar <
> sundar.nadat...@intel.com>; Dutch <dalth...@xilinx.com>; Rushil Chugh <
> rushil.ch...@gmail.com>; Nguyen Hung Phuong <phuon...@vn.fujitsu.com>;
> Justin Kilpatrick <jkilp...@redhat.com>; Ranganathan, Shobha <
> shobha.ranganat...@intel.com>; zhuli <zhul...@huawei.com>;
> bao.yum...@zte.com.cn; xiaodong...@tencent.com; kong.w...@zte.com.cn;
> li.xia...@zte.com.cn; Feng, Shaohe <shaohe.f...@intel.com>
> *Subject:* [openstack-dev][cyborg][glance][nova]cyborg FPGA management
> flow disscusion.
>
>
> Now I am working on an FPGA management POC with Dolpher.
> We have finished some code, and have discussion with Li Liu and some
> cyborg developer guys.
>
> Here are some discussions:
>
> image management
> 1. User should upload the FPGA image to glance and set the tags as follow:
> There are two suggestions to upload an FPGA image.
> A. use raw glance api like:
>$ openstack image create --file mypath/FPGA.img  fpga.img
>$ openstack image set --tag FPGA --property vendor=intel --property
> type=crypto 58b813db-1fb7-43ec-b85c-3b771c685d22
>The image must have "FPGA" tag and accelerator type(such as
> type=crypto).
> B. cyborg support a new api to upload a image.
>This API will wrap glance api and include the above steps, also make
> image record in it's local DB.
>
> 2. Cyborg agent/conductor get the FPGA image info from glance.
> There are also two suggestions to get the FPGA image info.
> A. use raw glance api.
> Cyborg will get the images by FPGA tag and timestamp periodically and
> store them in it's local cache.
> It will use the images tags and properties to form placement taits and
> resource_class name.
> B. store the imformations when call cybort's new upload API.
>
> 3. Image download.
> call glance image download API to local file. and make a corresponding md5
> files for checksum.
>
> GAP in image management：
> missing related glance image client in cyborg.
>
> resource report management for scheduler.
> 1.  Cyborg agent/conductor need synthesize all useful information from
> FPGA driver and image information.
> The traits will be like:
> CUSTOM_FPGA, CUSTOM_ACCELERATOR_CRYPTO,
> The resource_class will be like:
> CUSTOM_FPGA_INTEL_PF, CUSTOM_FPGA_INTEL_VF
> {"inventories":
> "CUSTOM_FPGA_INTEL_PF": {
> "allocation_ratio": 1.0,
> "max_unit": 4,
> "min_unit": 1,
> "reserved": 0,
> "step_size": 1,
> "total": 4
> }
> }
>
>
> Accelerator claim and release:
> 1. Cybort will support the releated API for accelerator claim and release.
> It can pass the follow parameters:
>   nodename: Which host that accelerator located on, it is required.
>   type: This accelerator type, cyborg can get image uuid by it. it is
> optional.
>   image uuid: the uuid of FPGA bitstream image, . it is optional.
>   traits: the traits info that cyborg reports to placement.
>   resource_class: the resource_class name that reports to placement.
> And return the address for the accelerator. At present, it is the
> PCIE_ADDRESS.
> 2. When claim an accelerator, type and image is None, cybort will not
> program the fpga for user.
>
> FPGA accelerator program API:
> We still need to support an independent program API for some specific
> scenarios.
> Such as as a FPGA developer, I will change my verilog logical frequently
> and need to do verification on my guest.
> I upload my new bitstream image to glance, and call cyborg to program my
> FPGA accelerator.
>
> End user operations follow:
> 1. upload an bitstream image to glance if necessary and set its tags(at
> least FPGA is requied) and property.
>sucn as: --tag FPGA --property vendor=intel --property type=crypto
> 2. list the FPGA related traits and resource_class names by placement API.
>such as get "CUSTOM_FPGA_INTEL_PF" resource_class names and
> "CUSTOM_HW_INT

Re: [openstack-dev] [keystone] [oslo] new unified limit library

[Zhipeng Huang]

This is certainly a feature will make Public Cloud providers very happy :)

On Thu, Mar 8, 2018 at 12:33 AM, Tim Bell  wrote:

> Sorry, I remember more detail now... it was using the 'owner' of the VM as
> part of the policy rather than quota.
>
> Is there a per-user/per-group quota in Nova?
>
> Tim
>
> -Original Message-
> From: Tim Bell 
> Reply-To: "OpenStack Development Mailing List (not for usage questions)" <
> openstack-dev@lists.openstack.org>
> Date: Wednesday, 7 March 2018 at 17:29
> To: "OpenStack Development Mailing List (not for usage questions)" <
> openstack-dev@lists.openstack.org>
> Subject: Re: [openstack-dev] [keystone] [oslo] new unified limit library
>
>
> There was discussion that Nova would deprecate the user quota feature
> since it really didn't fit well with the 'projects own resources' approach
> and was little used. At one point, some of the functionality stopped
> working and was repaired. The use case we had identified goes away if you
> have 2 level deep nested quotas (and we have now worked around it).
>
> Tim
> -Original Message-
> From: Lance Bragstad 
> Reply-To: "OpenStack Development Mailing List (not for usage
> questions)" 
> Date: Wednesday, 7 March 2018 at 16:51
> To: "openstack-dev@lists.openstack.org"  openstack.org>
> Subject: Re: [openstack-dev] [keystone] [oslo] new unified limit
> library
>
>
>
> On 03/07/2018 09:31 AM, Chris Friesen wrote:
> > On 03/07/2018 08:58 AM, Lance Bragstad wrote:
> >> Hi all,
> >>
> ]
> >
> > 1) Nova currently supports quotas for a user/group tuple that
> can be
> > stricter than the overall quotas for that group.  As far as I
> know no
> > other project supports this.
> ...
> I think the initial implementation of a unified limit pattern is
> targeting limits and quotas for things associated to projects. In
> the
> future, we can probably expand on the limit information in
> keystone to
> include user-specific limits, which would be great if nova wants
> to move
> away from handling that kind of stuff.
> >
> > Chris
> >
> > 
> __
> >
> > OpenStack Development Mailing List (not for usage questions)
> > Unsubscribe:
> > openstack-dev-requ...@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-requ...@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-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>



-- 
Zhipeng (Howard) Huang

Standard Engineer
IT Standard & Patent/IT Product Line
Huawei Technologies Co,. Ltd
Email: huangzhip...@huawei.com
Office: Huawei Industrial Base, Longgang, Shenzhen

(Previous)
Research Assistant
Mobile Ad-Hoc Network Lab, Calit2
University of California, Irvine
Email: zhipe...@uci.edu
Office: Calit2 Building Room 2402

OpenStack, OPNFV, OpenDaylight, OpenCompute Aficionado
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [cyborg]No Meeting This Week

[Zhipeng Huang]

Hi Team,

As most of us are rekubrating from PTG and snowenpstack last week, let's
cancel the team meeting this week. At the mean time I have solicitate the
meeting summary from topic leads, and will send out a summary of the
summaries later :)

-- 
Zhipeng (Howard) Huang

Standard Engineer
IT Standard & Patent/IT Product Line
Huawei Technologies Co,. Ltd
Email: huangzhip...@huawei.com
Office: Huawei Industrial Base, Longgang, Shenzhen

(Previous)
Research Assistant
Mobile Ad-Hoc Network Lab, Calit2
University of California, Irvine
Email: zhipe...@uci.edu
Office: Calit2 Building Room 2402

OpenStack, OPNFV, OpenDaylight, OpenCompute Aficionado
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [ironic] Polling for new meeting time?

[Zhipeng Huang]

understood :)

On Mon, Mar 5, 2018 at 11:30 PM, Julia Kreger <juliaashleykre...@gmail.com>
wrote:

>
> On Mon, Mar 5, 2018 at 1:48 AM Dmitry Tantsur <dtant...@redhat.com> wrote:
>
>> On 03/04/2018 09:46 PM, Zhipeng Huang wrote:
>> > Thx Julia,
>> >
>> > Another option is instead of changing meeting time, you could establish
>> a
>> > tick-tock meeting, for example odd weeks for US-Euro friendly times and
>> even
>> > weeks for US-Asia friendly times.
>>
>> We tried that roughly two years ago, and it did not work because very few
>> people
>> showed up on the APAC time. I think the goal of this poll is to figure
>> out how
>> many people would show up now.
>
>
> Exactly, the overlap is critical to understand. My preference is to try
> and keep one meeting time. If there are no good times, then we might want
> to consider something like office hours, but we will need to adapt planning
> and coordination. I’m not sure I’ve had enough coffee yet to think about
> that further. :)
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>


-- 
Zhipeng (Howard) Huang

Standard Engineer
IT Standard & Patent/IT Product Line
Huawei Technologies Co,. Ltd
Email: huangzhip...@huawei.com
Office: Huawei Industrial Base, Longgang, Shenzhen

(Previous)
Research Assistant
Mobile Ad-Hoc Network Lab, Calit2
University of California, Irvine
Email: zhipe...@uci.edu
Office: Calit2 Building Room 2402

OpenStack, OPNFV, OpenDaylight, OpenCompute Aficionado
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [ironic] Polling for new meeting time?

[Zhipeng Huang]

Thx Julia,

Another option is instead of changing meeting time, you could establish a
tick-tock meeting, for example odd weeks for US-Euro friendly times and
even weeks for US-Asia friendly times.

On Mar 4, 2018 7:01 PM, "Julia Kreger"  wrote:

> Greetings everyone!
>
> As our community composition has shifted to be more global, the
> question has arisen if we should consider shifting the meeting to be
> more friendly to some of our contributors in the APAC time zones.
> Alternatively this may involve changing our processes to better plan
> and communicate, but the first step is to understand our overlaps and
> what might work well for everyone.
>
> I have created a doodle poll, from which I would like understand what
> times would ideally work, and from there we can determine if there is
> a better time to meet.
>
> The poll can be found at: https://doodle.com/poll/6kuwixpkkhbwsibk
>
> Please don't feel the need to select times that would be burdensome to
> yourself. This is only to gather information as to the time of day
> that would be ideal for everyone. All times are set as UTC on the
> poll.
>
> Once we have collected some data, we should expect to discuss during
> our meeting on the 12th.
>
> Thanks everyone!
>
> -Julia
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@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-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [cyborg]Team Dinner 6:30pm at Croke Park Hotel

[Zhipeng Huang]

Hi Team,

I reserved a table for 8 at Sideline Bar in the Croke Park Hotel for team
dinner . Look forward to meat you guys there :P
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [nova][ptg] reminder: cyborg nova-interaction discussion at 2pm this afternoon

[Zhipeng Huang]

THX Melanie ! :)

On Tue, Feb 27, 2018 at 10:34 AM, melanie witt  wrote:

> Howdy everyone,
>
> This is just a reminder that we have some time scheduled to chat with the
> Cyborg team at 2pm this afternoon at the Cyborg room (Suite 665).
>
> From our PTG etherpad agenda[1] :
>
> "Cyborg (previously known as Nomad) is an OpenStack project that aims to
> provide a general purpose management framework for acceleration resources
> (i.e. various types of accelerators such as Crypto cards,GPU, FPGA,
> NVMe/NOF SSDs, ODP, DPDK/SPDK and so on).
> https://wiki.openstack.org/wiki/Cyborg”
>
> If you are interested, please join us!
>
> -melanie
>
> [1] https://etherpad.openstack.org/p/nova-ptg-rocky at L572
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>



-- 
Zhipeng (Howard) Huang

Standard Engineer
IT Standard & Patent/IT Product Line
Huawei Technologies Co,. Ltd
Email: huangzhip...@huawei.com
Office: Huawei Industrial Base, Longgang, Shenzhen

(Previous)
Research Assistant
Mobile Ad-Hoc Network Lab, Calit2
University of California, Irvine
Email: zhipe...@uci.edu
Office: Calit2 Building Room 2402

OpenStack, OPNFV, OpenDaylight, OpenCompute Aficionado
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [cyborg]reminder for team photo

[Zhipeng Huang]

Just a kind reminder for team photo, our slot is 1:40, plz gather around
the reg desk on time :)

-- 
Zhipeng (Howard) Huang

Standard Engineer
IT Standard & Patent/IT Product Line
Huawei Technologies Co,. Ltd
Email: huangzhip...@huawei.com
Office: Huawei Industrial Base, Longgang, Shenzhen

(Previous)
Research Assistant
Mobile Ad-Hoc Network Lab, Calit2
University of California, Irvine
Email: zhipe...@uci.edu
Office: Calit2 Building Room 2402

OpenStack, OPNFV, OpenDaylight, OpenCompute Aficionado
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [cyborg]Dublin PTG schedule update

[Zhipeng Huang]

Hi Team,

There haven been several updates that I recorded on the etherpad:
https://etherpad.openstack.org/p/cyborg-ptg-rocky

[1] Team Photo time has been changed
[2] I've setup the sub-etherpad for each topic. Topic owner please fill in
these etherpads with the content that you want to discuss
[3] Plz confirm your availability for team dinner on Tuesday night
[4] Room is Suite 665


-- 
Zhipeng (Howard) Huang

Standard Engineer
IT Standard & Patent/IT Product Line
Huawei Technologies Co,. Ltd
Email: huangzhip...@huawei.com
Office: Huawei Industrial Base, Longgang, Shenzhen

(Previous)
Research Assistant
Mobile Ad-Hoc Network Lab, Calit2
University of California, Irvine
Email: zhipe...@uci.edu
Office: Calit2 Building Room 2402

OpenStack, OPNFV, OpenDaylight, OpenCompute Aficionado
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [acceleration]Cancelation of Cyborg Team meeting on Feb 14th and 21th

[Zhipeng Huang]

Hi Team,

Due to Chinese new year and the approaching PTG, let's cancel this week and
next week's team meeting. But as usual we will lurk around the IRC channel
still, so if you got anything, feel free to shoot on #openstack-cyborg

-- 
Zhipeng (Howard) Huang

Standard Engineer
IT Standard & Patent/IT Product Line
Huawei Technologies Co,. Ltd
Email: huangzhip...@huawei.com
Office: Huawei Industrial Base, Longgang, Shenzhen

(Previous)
Research Assistant
Mobile Ad-Hoc Network Lab, Calit2
University of California, Irvine
Email: zhipe...@uci.edu
Office: Calit2 Building Room 2402

OpenStack, OPNFV, OpenDaylight, OpenCompute Aficionado
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [nova][cyborg]Dublin PTG Cyborg Nova Interaction Discussion

[Zhipeng Huang]

@melanie yes Cyborg has its meeting room I think :) Room details should be
fixed this week or early next week I suppose.

So it will be 2:00pm on Tuesday, first thing of buisness after lunch :)

On Wed, Feb 14, 2018 at 7:20 AM, melanie witt <melwi...@gmail.com> wrote:

> > On Feb 12, 2018, at 16:06, Zhipeng Huang <zhipengh...@gmail.com> wrote:
> >
> > Let's settle on Tuesday afternoon session then, thanks a lot :)
>
> Do we have a proposed time and place for the session already? I checked
> the cyborg etherpad [1] and it looks like we’re thinking 2:00pm on Tuesday.
> Do we need to reserve a room for the discussion or do you already have a
> room we can join?
>
> Thanks,
> -melanie
>
> [1] https://etherpad.openstack.org/p/cyborg-ptg-rocky
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>



-- 
Zhipeng (Howard) Huang

Standard Engineer
IT Standard & Patent/IT Product Line
Huawei Technologies Co,. Ltd
Email: huangzhip...@huawei.com
Office: Huawei Industrial Base, Longgang, Shenzhen

(Previous)
Research Assistant
Mobile Ad-Hoc Network Lab, Calit2
University of California, Irvine
Email: zhipe...@uci.edu
Office: Calit2 Building Room 2402

OpenStack, OPNFV, OpenDaylight, OpenCompute Aficionado
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [cyborg]Cyborg PTG Schedule

[Zhipeng Huang]

Hi Team,

After some discussion, we have tentatively setup our project specific
schedule for Dublin PTG meeting.

*Meetings:*

In general, Cyborg project gathering will happen on Monday and Tuesday [0].

Due to several meeting conflicts, we divide our gathering meeting into two
parts for each day:

(1) Office Hour: 9:00am - 12:00pm. Cyborg core member will be around our
meeting room to answer questions, devstack setup, and so forth.
(2) Discussion Session: 2:00pm - 6:00pm. Rocky Cycle dev discussion. We
will have ZOOM conference for each topic and thus each topic got 40 mins.

*Team Photo:*

Team photo is Tuesday 11:50 - 12:00 [1]

*Team Interview:*

Team Interview is Tuesday 13:00 [2]

*Team Dinner:*

We will have team dinner on Tuesday night, venue info to be updated later :)

For specific topic arrangement , plze refer to [3]

[0] https://www.openstack.org/ptg/#tab_schedule
[1]
https://docs.google.com/spreadsheets/d/1J2MRdVQzSyakz9HgTHfwYPe49PaoTypX66eNURsopQY/edit?usp=sharing
[2]
https://docs.google.com/spreadsheets/d/1MK7rCgYXCQZP1AgQ0RUiuc-cEXIzW5RuRzz5BWhV4nQ/edit#gid=0
[3] https://etherpad.openstack.org/p/cyborg-ptg-rocky

-- 
Zhipeng (Howard) Huang

Standard Engineer
IT Standard & Patent/IT Product Line
Huawei Technologies Co,. Ltd
Email: huangzhip...@huawei.com
Office: Huawei Industrial Base, Longgang, Shenzhen

(Previous)
Research Assistant
Mobile Ad-Hoc Network Lab, Calit2
University of California, Irvine
Email: zhipe...@uci.edu
Office: Calit2 Building Room 2402

OpenStack, OPNFV, OpenDaylight, OpenCompute Aficionado
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [nova][cyborg]Dublin PTG Cyborg Nova Interaction Discussion

[Zhipeng Huang]

Let's settle on Tuesday afternoon session then, thanks a lot :)

On Tue, Feb 13, 2018 at 1:43 AM, Ed Leafe  wrote:

> On Feb 12, 2018, at 9:57 AM, Chris Dent  wrote:
> >
> > Tuesday would be best for me as Monday is api-sig day.
>
> Same, for the same reason.
>
>
> -- Ed Leafe
>
>
>
>
>
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>



-- 
Zhipeng (Howard) Huang

Standard Engineer
IT Standard & Patent/IT Product Line
Huawei Technologies Co,. Ltd
Email: huangzhip...@huawei.com
Office: Huawei Industrial Base, Longgang, Shenzhen

(Previous)
Research Assistant
Mobile Ad-Hoc Network Lab, Calit2
University of California, Irvine
Email: zhipe...@uci.edu
Office: Calit2 Building Room 2402

OpenStack, OPNFV, OpenDaylight, OpenCompute Aficionado
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [nova][cyborg]Dublin PTG Cyborg Nova Interaction Discussion

[Zhipeng Huang]

Hi Nova team,

Cyborg will have ptg sessions on Mon and Tue from 2:00pm to 6:00pm, and we
would love to invite any of you guys who is interested in nova-cyborg
interaction to join the discussion. The discussion will mainly focus on:

(1) Cyborg team recap on the resource provider features that are
implemented in Queens.
(2) Joint discussion on what will be the impact on Nova side and future
collaboration areas.

The session is planned for 40 mins long.

If you are interested plz feedback which date best suit for your
arrangement so that we could arrange the topic accordingly :)

Thank you very much.



-- 
Zhipeng (Howard) Huang

Standard Engineer
IT Standard & Patent/IT Product Line
Huawei Technologies Co,. Ltd
Email: huangzhip...@huawei.com
Office: Huawei Industrial Base, Longgang, Shenzhen

(Previous)
Research Assistant
Mobile Ad-Hoc Network Lab, Calit2
University of California, Irvine
Email: zhipe...@uci.edu
Office: Calit2 Building Room 2402

OpenStack, OPNFV, OpenDaylight, OpenCompute Aficionado
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [All][Elections] End of PTL Nominations

[Zhipeng Huang]

Hi Kendall,

There is a small typo for cyborg PTL name, rushil helped e submit the
patch, but the name of the PTL should be Zhipeng Huang :) if you could
correct that on the governance page that would be less confusing :)

On Feb 8, 2018 8:06 AM, "Kendall Nelson" <kennelso...@gmail.com> wrote:

Hello Everyone!

The PTL Nomination period is now over. The official candidate list is
available on the election website[0].

There are 0 projects without candidates, so the TC will not have to appoint
any PTL's.

There are 3 projects that will have elections: Kolla, QA, & Mistral. The
details for those will be posted shortly after we setup the CIVS system.

Thank you,
- Kendall Nelson (diablo_rojo)

[0] http://governance.openstack.org/election/#Rocky-ptl-candidates


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@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-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [acceleration]Cyborg Team Weekly Meeting 2018.02.07

[Zhipeng Huang]

Hi Team,

Weekly meeting happen starting UTC1500 at #openstack-cyborg , we will wrap
up all the remaining patches and discuss PTG schedule.

-- 
Zhipeng (Howard) Huang

Standard Engineer
IT Standard & Patent/IT Product Line
Huawei Technologies Co,. Ltd
Email: huangzhip...@huawei.com
Office: Huawei Industrial Base, Longgang, Shenzhen

(Previous)
Research Assistant
Mobile Ad-Hoc Network Lab, Calit2
University of California, Irvine
Email: zhipe...@uci.edu
Office: Calit2 Building Room 2402

OpenStack, OPNFV, OpenDaylight, OpenCompute Aficionado
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev