Open Stack

Hi Dave,

AS per your recommendations below are the steps that we have followed:

Step #1: create a WG scoping document to define the who, what and how or your working group

·         https://etherpad.openstack.org/p/Fault_Genes-WG

Step #2: once you have 2-5 people in support of a similar WG document then post it to this mailing list for a [user-committee] member to approve.  Once you have approval we can get you a page on the wiki.

·         Done

Step no.3: schedule an inaugural WG meeting at an upcoming summit.

·         Please provide us with a time slot.

Step #4: we have a committed base team to start our working group

Thanks for your support.

Nemat


From: David F Flanders [mailto:flanders at openstack.org]
Sent: Friday, May 06, 2016 2:44 AM
To: Nematollah Bidokhti
Cc: user-committee; Anita Kuno
Subject: Re: [User-committee] [Openstack-operators] New working group: [fault genes]. Recap from Austin from "Taxonomy of Failure" Ops session and plans going forward as a working group

Hi Nemat,

Great to hear of your interest in establishing a working-group via the [user-committee].  You've already achieved one success by getting a user-committee board member (Edgar) to provide his expert guidance.

Here are some of the steps which recent WGs have utilised in achieving community awareness:

Step no.1: create a WG scoping document to define the who, what and how or your working group, for example:

https://etherpad.openstack.org/p/scientific-wg

https://etherpad.openstack.org/p/apphackathon-wg

Step no.2: once you have 2-5 people in support of a similar WG document then post it to this mailing list for a [user-committee] member to approve.  Once you have approval we can get you a page on the wiki.

Step no.3: schedule an inaugural WG meeting at an upcoming summit.  We can help provide you a mentor (waves @Anita) to help provide good practice on how an affective WG meeting should run. Namely, agreeing an agenda and set of tasks which can be taken forward during the six month cycle.  For example have a look at the 4x task-force groups which the Scientific-WG have established to achieve by Barcelona:

https://etherpad.openstack.org/p/scientific-wg-austin-summit-agenda

Step no.4: WGs either live or die by their community engagement, which IMHO is tied to their ability to deliver outputs at each summit, i.e. 'low hanging fruit' is the name of the game ;)

Naturally, all of the above is advice and should be quickly censured by more experienced community members than myself.  However, please don't hesitate to ask questions and suggest improvements.

Good luck and look forward to hearing more from you and your fellow WG sponsors soon.

Kind Regards,

Flanders

On Fri, May 6, 2016 at 3:52 AM, Anita Kuno <anteaya at anteaya.info<mailto:anteaya at anteaya.info>> wrote:
On 05/05/2016 01:29 PM, Edgar Magana wrote:
> Hello Nemat,
>
> This is really awesome. As member of the User Committee (UC) I would like to encourage you and the members of this working group to add the information on this wiki page:
> https://wiki.openstack.org/wiki/Governance/Foundation/UserCommittee
>
> I also would like to make sure that the focus of this WG is not overlapping with any other already in place. In short the UC will start collecting details of all working groups under the UC umbrella to make sure that we have the proper organization and focus. I would love to see you and the rest of the leads on this WG to attend our IRC meetings.
>
> Thanks,
>
> Edgar

He can't. Since we aren't allowing folks who don't already have an
account on the wiki to create or update wikipages due to the spamming
concerns, he is unable. He tried yesterday. You can see the
#openstack-infra backscroll for the discussion.

Thanks Edgar,
Anita.


>
> From: Nematollah Bidokhti <Nematollah.Bidokhti at huawei.com<mailto:Nematollah.Bidokhti at huawei.com><mailto:Nematollah.Bidokhti at huawei.com<mailto:Nematollah.Bidokhti at huawei.com>>>
> Date: Wednesday, May 4, 2016 at 6:22 PM
> To: "openstack-operators at lists.openstack.org<mailto:openstack-operators at lists.openstack.org><mailto:openstack-operators at lists.openstack.org<mailto:openstack-operators at lists.openstack.org>>" <openstack-operators at lists.openstack.org<mailto:openstack-operators at lists.openstack.org><mailto:openstack-operators at lists.openstack.org<mailto:openstack-operators at lists.openstack.org>>>, "user-committee at lists.openstack.org<mailto:user-committee at lists.openstack.org><mailto:user-committee at lists.openstack.org<mailto:user-committee at lists.openstack.org>>" <user-committee at lists.openstack.org<mailto:user-committee at lists.openstack.org><mailto:user-committee at lists.openstack.org<mailto:user-committee at lists.openstack.org>>>
> Cc: Rochelle Grober <rochelle.grober at huawei.com<mailto:rochelle.grober at huawei.com><mailto:rochelle.grober at huawei.com<mailto:rochelle.grober at huawei.com>>>
> Subject: [Openstack-operators] New working group: [fault genes]. Recap from Austin from "Taxonomy of Failure" Ops session and plans going forward as a working group
>
> Hi,
>
> This email is a recap from our OpenStack summit meeting “Taxonomy of Failure” in Austin. The purpose of this email is to provide a summary of the meeting and future plans.
>
> We had between 55-60 people participating in our session and received a number of comments and suggestions. Basically all comments were positive and felt we are going in a right direction.
>
> The goal is to look at OpenStack resiliency in holistic fashion by identifying all possible failure modes (either experienced to date or based on design implementation), classifying them, defining the ideal mitigation strategy, how should they be reported and how they can be re-created with the OpenStack version in mind. The results of this effort will be used throughout OpenStack lifecycle (design, development, test, deployment).
>
> After our meeting I met with a lot of companies in the market place and received lots of encouragement to complete the effort that we have started. There were 20 companies that I met with and all expressed their interest to support this activity. As a result, we have decided to start a working group “Fault Genes” to focus on all OpenStack failure modes.
>
> The plan is to start with email communications and filling out our Google Sheet template (https://docs.google.com/spreadsheets/d/1sekKLp7C8lsTh-niPHNa2QLk5kzEC_2w_UsG6ifC-Pw/edit#gid=2142834673<https://urldefense.proofpoint.com/v2/url?u=https-3A__docs.google.com_spreadsheets_d_1sekKLp7C8lsTh-2DniPHNa2QLk5kzEC-5F2w-5FUsG6ifC-2DPw_edit-23gid-3D2142834673&d=CwMFAg&c=DS6PUFBBr_KiLo7Sjt3ljp5jaW5k2i9ijVXllEdOozc&r=G0XRJfDQsuBvqa_wpWyDAUlSpeMV4W1qfWqBfctlWwQ&m=ozuLPy_mXjSViieCMUGctjhZTJxMATkcjenldm1Z9rI&s=tbdwWpux_CHqkMU2gCYuwd6asW35O9wTW8y0IncOpSs&e=>) that we have set up, start out with a weekly meeting, adjusting as the group sees fit and in 3 months have a check point on what we have accomplished. Then, we should have a picture of what we have accomplished, where this will go and have information to present at OpenStack in Barcelona. Below is the link to the etherpad:
>
> https://etherpad.openstack.org/p/AUS-ops-Taxonomy-of-Failures<https://urldefense.proofpoint.com/v2/url?u=https-3A__etherpad.openstack.org_p_AUS-2Dops-2DTaxonomy-2Dof-2DFailures&d=CwMFAg&c=DS6PUFBBr_KiLo7Sjt3ljp5jaW5k2i9ijVXllEdOozc&r=G0XRJfDQsuBvqa_wpWyDAUlSpeMV4W1qfWqBfctlWwQ&m=ozuLPy_mXjSViieCMUGctjhZTJxMATkcjenldm1Z9rI&s=FtDLAUlP9p8xwSr4ij-7PT5n_MmD2tf-OnGnC0hdf6k&e=>
>
> For those who were in the meeting or discussed this at the summit, and  you understand spreadsheet, please take time and fill in the spreadsheet with the failure modes that you have experienced so far and related attributes for each failure mode.
>
> I’ll schedule a meeting to get those who weren’t at the summit informed of the process and how to use the spreadsheet.
>
> Suggestions of meeting times, or further discussion here is appreciated and appropriate.
>
> My availability for meetings is:  1600-2359 UTC
>
> Please use this link http://doodle.com/poll/8ymwuqva7itv84p8<https://urldefense.proofpoint.com/v2/url?u=http-3A__doodle.com_poll_8ymwuqva7itv84p8&d=CwMFAg&c=DS6PUFBBr_KiLo7Sjt3ljp5jaW5k2i9ijVXllEdOozc&r=G0XRJfDQsuBvqa_wpWyDAUlSpeMV4W1qfWqBfctlWwQ&m=ozuLPy_mXjSViieCMUGctjhZTJxMATkcjenldm1Z9rI&s=-LICHxWghb_85hHgEfOYvqEqr-1qismatlQwg5zXvBM&e=> to provide your suggested time.
>
> Thanks,<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.timeanddate.com_worldclock_timezone_utc&d=CwMFAg&c=DS6PUFBBr_KiLo7Sjt3ljp5jaW5k2i9ijVXllEdOozc&r=G0XRJfDQsuBvqa_wpWyDAUlSpeMV4W1qfWqBfctlWwQ&m=ozuLPy_mXjSViieCMUGctjhZTJxMATkcjenldm1Z9rI&s=HjKT2VU1ZOfcmYw8gT6s6qmhWUw_DaiPAaVldJiK7A0&e=>
>
> Nemat Bidokhti<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.timeanddate.com_worldclock_timezone_utc&d=CwMFAg&c=DS6PUFBBr_KiLo7Sjt3ljp5jaW5k2i9ijVXllEdOozc&r=G0XRJfDQsuBvqa_wpWyDAUlSpeMV4W1qfWqBfctlWwQ&m=ozuLPy_mXjSViieCMUGctjhZTJxMATkcjenldm1Z9rI&s=HjKT2VU1ZOfcmYw8gT6s6qmhWUw_DaiPAaVldJiK7A0&e=>
> Chief Reliability Architect
> IT Product Line, Computing Lab<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.timeanddate.com_worldclock_timezone_utc&d=CwMFAg&c=DS6PUFBBr_KiLo7Sjt3ljp5jaW5k2i9ijVXllEdOozc&r=G0XRJfDQsuBvqa_wpWyDAUlSpeMV4W1qfWqBfctlWwQ&m=ozuLPy_mXjSViieCMUGctjhZTJxMATkcjenldm1Z9rI&s=HjKT2VU1ZOfcmYw8gT6s6qmhWUw_DaiPAaVldJiK7A0&e=>
> Futurewei Technologies, Inc.<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.timeanddate.com_worldclock_timezone_utc&d=CwMFAg&c=DS6PUFBBr_KiLo7Sjt3ljp5jaW5k2i9ijVXllEdOozc&r=G0XRJfDQsuBvqa_wpWyDAUlSpeMV4W1qfWqBfctlWwQ&m=ozuLPy_mXjSViieCMUGctjhZTJxMATkcjenldm1Z9rI&s=HjKT2VU1ZOfcmYw8gT6s6qmhWUw_DaiPAaVldJiK7A0&e=>
> HUAWEI R&D USA<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.timeanddate.com_worldclock_timezone_utc&d=CwMFAg&c=DS6PUFBBr_KiLo7Sjt3ljp5jaW5k2i9ijVXllEdOozc&r=G0XRJfDQsuBvqa_wpWyDAUlSpeMV4W1qfWqBfctlWwQ&m=ozuLPy_mXjSViieCMUGctjhZTJxMATkcjenldm1Z9rI&s=HjKT2VU1ZOfcmYw8gT6s6qmhWUw_DaiPAaVldJiK7A0&e=>
> Tel:         +1-408-330-4714<tel:%2B1-408-330-4714><https://urldefense.proofpoint.com/v2/url?u=http-3A__www.timeanddate.com_worldclock_timezone_utc&d=CwMFAg&c=DS6PUFBBr_KiLo7Sjt3ljp5jaW5k2i9ijVXllEdOozc&r=G0XRJfDQsuBvqa_wpWyDAUlSpeMV4W1qfWqBfctlWwQ&m=ozuLPy_mXjSViieCMUGctjhZTJxMATkcjenldm1Z9rI&s=HjKT2VU1ZOfcmYw8gT6s6qmhWUw_DaiPAaVldJiK7A0&e=>
> Cell:       +1-408-528-4909<tel:%2B1-408-528-4909><https://urldefense.proofpoint.com/v2/url?u=http-3A__www.timeanddate.com_worldclock_timezone_utc&d=CwMFAg&c=DS6PUFBBr_KiLo7Sjt3ljp5jaW5k2i9ijVXllEdOozc&r=G0XRJfDQsuBvqa_wpWyDAUlSpeMV4W1qfWqBfctlWwQ&m=ozuLPy_mXjSViieCMUGctjhZTJxMATkcjenldm1Z9rI&s=HjKT2VU1ZOfcmYw8gT6s6qmhWUw_DaiPAaVldJiK7A0&e=>
> Fax:        +1-408-330-5088<tel:%2B1-408-330-5088><https://urldefense.proofpoint.com/v2/url?u=http-3A__www.timeanddate.com_worldclock_timezone_utc&d=CwMFAg&c=DS6PUFBBr_KiLo7Sjt3ljp5jaW5k2i9ijVXllEdOozc&r=G0XRJfDQsuBvqa_wpWyDAUlSpeMV4W1qfWqBfctlWwQ&m=ozuLPy_mXjSViieCMUGctjhZTJxMATkcjenldm1Z9rI&s=HjKT2VU1ZOfcmYw8gT6s6qmhWUw_DaiPAaVldJiK7A0&e=>
> E-mail: nematollah.bidokhti at huawei.com<mailto:nematollah.bidokhti at huawei.com><https://urldefense.proofpoint.com/v2/url?u=http-3A__www.timeanddate.com_worldclock_timezone_utc&d=CwMFAg&c=DS6PUFBBr_KiLo7Sjt3ljp5jaW5k2i9ijVXllEdOozc&r=G0XRJfDQsuBvqa_wpWyDAUlSpeMV4W1qfWqBfctlWwQ&m=ozuLPy_mXjSViieCMUGctjhZTJxMATkcjenldm1Z9rI&s=HjKT2VU1ZOfcmYw8gT6s6qmhWUw_DaiPAaVldJiK7A0&e=>
> 2330 Central Expressway <mailto:nematollah.bidokhti at huawei.com<mailto:nematollah.bidokhti at huawei.com>>
> Santa Clara, CA 95050<mailto:nematollah.bidokhti at huawei.com<mailto:nematollah.bidokhti at huawei.com>>
> http://www.huawei.com<mailto:nematollah.bidokhti@huawei.com<mailto:nematollah.bidokhti@huawei.com>>
>
>
>
> _______________________________________________
> User-committee mailing list
> User-committee at lists.openstack.org<mailto:User-committee at lists.openstack.org>
> http://lists.openstack.org/cgi-bin/mailman/listinfo/user-committee
>


_______________________________________________
User-committee mailing list
User-committee at lists.openstack.org<mailto:User-committee at lists.openstack.org>
http://lists.openstack.org/cgi-bin/mailman/listinfo/user-committee

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/user-committee/attachments/20160516/a3f674ee/attachment-0001.html>