https://wiki.openstack.org/w/api.php?action=feedcontributions&user=Mbonell&feedformat=atomOpenStack - User contributions [en]2024-03-28T08:43:44ZUser contributionsMediaWiki 1.28.2https://wiki.openstack.org/w/index.php?title=CloudAppHack-WG&diff=128144CloudAppHack-WG2016-07-15T21:40:04Z<p>Mbonell: /* Current Hackathons */</p>
<hr />
<div>== Cloud Application Hackathon Working Group ==<br />
CloudAppHack-WG<br />
<br />
=== Overview ===<br />
The Cloud Application Hackathon working group actively supports community members who wants to organize and run a cloud application hackathon for their community. The working group (WG) will share it’s collective knowledge, exchange of best practices, documentation, and provide mentorship. This WG is a place for hackathon organisers to come and receive planning advice which is practical and helps the organiser achieve event success by leveraging the capabilities of the global OpenStack community.<br />
<br />
=== Goals ===<br />
* Grow a vibrant and inclusive community of cloud application developers who actively use OpenStack as their cloud application infrastructure platform<br />
* Act as an additional point of contact for guidance in developing a successful, safe, inclusive and rewarding hackathon<br />
* Assist in the organization of OpenStack App Hackathon events in your respective communities and to consolidate global activities<br />
* Facilitate activities correspondent to the App Hackathon wherever we can without impeding the interested group’s schedules or progress<br />
* Build personal relationships between AppDev and DevOps communities (tribes) for the purpose of better understanding how resources are exposed (via API/SDK) and how they are consumed<br />
* Establish AppDev champions who regularly participate and are aware for the wide ranging cloud app techniques and events which produce cloud applications<br />
<br />
=== Goals out of Scope ===<br />
* Develop Applications, Tools and Services atop OpenStack<br />
<br />
=== Community Contributions ===<br />
* Encourage the development of a broad OpenStack community and ecosystem of partners in support of DevApp Hackathons <br />
* Facilitate training activities in OpenStack<br />
* Transmit the interested community objectives and ideas to the OpenStack foundation in an easy, fast and organized manner to speed-up the event’s organization<br />
* Provide guidance on the community’s requirements and actively provide contacts who can solve problems stopping progress<br />
* Expectations Management for communities looking forward to run a hackathon<br />
* Provide an up-to-date list of DevApp Hackathon events to the user-committee and maintain an available list of past, present and future hackathons<br />
* Maintain ongoing communication with the user-committee to provide a forum for wider discussion on how the Application Develop Community is growing <br />
* Develop a task timeline for each hackathon and follow up with the interested community group<br />
* Overview the compliance of minimum membership requirements<br />
* Help finding additional stakeholders, sponsors and community collaborators to co-host the event<br />
* Recruit community members who want to be part of an open team that meets and works towards<br />
<br />
=== Organization ===<br />
<br />
[https://drive.google.com/file/d/0B_6QD8ZT8P4gSHROWVp2YUl0YTQ/view?usp=sharing Organigram]<br />
<br />
=== Meetings ===<br />
<br />
==== Every second Tuesday of every month through Google Hangouts ====<br />
<br />
* May 10, 2016<br />
* June 14, 2016<br />
* July 12, 2016<br />
* August 09, 2016<br />
* September 13, 2016<br />
* October 11, 2016<br />
* November 08, 2016<br />
* December 13, 2016<br />
<br />
=== Current Hackathons ===<br />
# [http://hackathon.openstackgdl.org/ Guadalajara Hackathon]<br />
# Prague Hackathon<br />
<br />
== Lead Hacker Checklists for Cloud Application Hackathon Event ==<br />
<br />
The 'lead hacker' is responsible for the overall success of the event. You should be a well organised person, able to kindly delegate tasks and humbly ask for help. You will have run events before with an understanding for basic community principles: especially inclusion, kindness and 'a steady hand' when things get stressful.<br />
<br />
Your objectives as the "Lead Hacker":<br />
<br />
* Assemble a team of event organisers who are passionate for building up your local community.<br />
* Organise weekly/fortnightly meetings to bring the event organising team together to communicate.<br />
* Answer questions daily, being on-call wherever you are needed. Promote, promote, promote.<br />
* Be the cheerleader, help people, do everything you can to make the event a positive organised experience for everyone.<br />
<br />
=== Checklists for the 'Lead Hacker' ===<br />
The below checklists are intended to provide the minimum viable set of tasks which will need to be completed for the hackathon. Naturally, you will add on additional tasks to make your event even better and we would highly encourage you to create your own checklists and share them back with the community.<br />
<br />
Are you ready to help make the world a better place where apps can work on any open cloud?<br />
<br />
=== Pre Event Checklist ===<br />
<br />
To do four months prior to the hackathon taking place:<br />
<br />
# Contact the OpenStack [https://wiki.openstack.org/wiki/Governance/Foundation/UserCommittee#Working_Groups_and_Teams Cloud Application Hackathon Working Group] to find an Ambassador who can support you throughout the event. A liaison from the OpenStack Foundation will be assigned to support you.<br />
# Recruit the x10 event organisers who will help you achieve a successful hackathon event, show them this repository with a list of checklists for the roles they will need to undertake as part of the event organising team.<br />
# Lock down a venue, i.e. lock down the date and tell a new person every day about the Hackathon. Hint: use any contacts you have at Universities as the Uni will often sponsor the event by donating the space.<br />
# Come up with the main theme (aka "tag line') of your event, how can you get all the "idea people" to come to this event and participate. Your event logo will represent this tag line. Your logo will be used on everything. Hint: what is happening at the time of your planned event, any news headlines likely - be timely!<br />
# Organise a simple one page website with basic instructions on how to get involved. Ask your friendly OpenStack liaison to help provide examples of past events. Don't forget: pictures, video and more pictures.<br />
# Draw up a floorplan to share with everyone showing spaces marked out for: opening ceremony stage, team spaces, food/drink areas, judging areas (if not the stages), and closing ceremony.<br />
# Run regular weekly/fortnightly conference calls to make sure your organising team is on track - have fun, encourage smiles as this event is about having fun with ideas!<br />
# Your hackathon begins with the informal training events which happen once month building up to the event, make sure the cloud and trainers are ready. <-- this is where teams will form.<br />
<br />
To do one month before the hackathon happens:<br />
<br />
# Make sure you have all 10 of your event organising team and that they are on course to deliver <br />
<br />
=== Event Checklist ===<br />
<br />
Tasks to achieve during the event:<br />
<br />
# 1st do-->confirm<br />
# 2nd read-->do<br />
# 3rd<br />
# 4th<br />
# 5th<br />
# 6th<br />
# Announce when the next CloudApphack is likely to happen.<br />
# Thank yous to your amazing event organisers, mentors, sponsors and participants <-- cannot begin to express how important this is!<br />
<br />
=== Post Event Checklist ===<br />
<br />
Tasks to achieve after the event:<br />
<br />
# 1st do-->confirm<br />
# 2nd read-->do<br />
# 3rd<br />
# 4th<br />
# 5th<br />
# 6th<br />
# 7th<br />
# Confirm date of next hackathon<br />
<br />
=== Additional Resources, Examples and Precedents ===<br />
<br />
* Example from Taipei<br />
* Example from Guadalajara's Hackathon [https://docs.google.com/document/d/1KO3LdLmw3LePttW4mY0EhMKVoq1IhyF64f7DwVNkkpo/pub Frequently Asked Questions guide]<br />
* Interesting resource worth reading.<br />
* Some precedents of how other open communities do this.<br />
* A helpful person worth contacting and having a chat.<br />
* Why use checklists? Humans are not great at remembering stuff, this is how mistakes happen, people forget things when they are in stressful situations (like events), checklists are great for focusing the mind and result in significant productivity gains. Read more about this in a book called, 'The Checklist Manifesto'.<br />
<br />
== Contact Information ==<br />
<br />
=== Co-Presidents - Newton Release ===<br />
<br />
==== Michael Jenkins ====<br />
Skype: michael.jenkins886<br />
md.jenkins@icloud.com<br />
LinkedIn: https://tw.linkedin.com/in/mjenkins3<br />
<br />
==== Gonzalo De La Torre ====<br />
US: (210) 837-0335<br />
Skype: gonzalo-de-la-torre<br />
Google Hangouts: latioz@gmail.com<br />
LinkedIn: https://www.linkedin.com/in/gonzaloutsa</div>Mbonellhttps://wiki.openstack.org/w/index.php?title=Application_Ecosystem_Working_Group&diff=124128Application Ecosystem Working Group2016-04-19T05:26:32Z<p>Mbonell: /* How to Contribute */</p>
<hr />
<div>'''Status''': Active<br />
<br />
'''Organizers''': <br />
*[mailto:john.callaghan@hpe.com John Callaghan] <br />
*[mailto:patricia.montenegro@intel.com Patricia Montenegro]<br />
<br />
==Purpose==<br />
<br />
To create an ecosystem where a diverse array of applications built for OpenStack can thrive.<br />
<br />
Objectives:<br />
* Grow the number of active OpenStack applications globally, for both private and public cloud use<br />
* Make it simpler to create applications for OpenStack by:<br />
** Improving introductory material<br />
** Ensuring appropriate tools and technical information is available, correct and easy to find<br />
* Further facilitating the association of those creating applications for OpenStack clouds with the OpenStack technical community by:<br />
** Improving developer.openstack.org, a portal for application creators<br />
** Analyzing and improving the 6-monthly conference, particularly the "Cloud App Development" track, and other more feedback-style sessions<br />
** Educating OpenStack's active technical community on the issues faced by those who are targeting OpenStack clouds<br />
<br />
==Mail List==<br />
Email: We use the [http://lists.openstack.org/cgi-bin/mailman/listinfo/user-committee user-committee mailing list] and prefix the subject line with [app].<br /><br />
<br />
==Team Meetings==<br />
The team meets weekly, on <big>'''Mondays at 3:00PM (Pacific) / 10:00PM (UTC)'''</big> '''NEW'''<br />
<br />
Call-in Info: '''(888) 875-9370 or 916-356-2663, Bridge: 2, Passcode: 1467696'''<br /> <br />
Australia - Melbourne - Toll free (+61)1300 365 946<br /><br />
<br />
Current Etherpad: https://etherpad.openstack.org/p/2016_Apr_18_App_Ecosystem_Workgroup<br /> <br />
<br />
Previous Etherpad links can be found here: https://etherpad.openstack.org/p/AppEcoSystemWG_Archives<br />
<br />
==Deliverables==<br />
<br />
1. Application Ecosystem Feedback<br />
<br />
Anyone in the application ecosystem needs a way to give feedback to the OpenStack community at large. This can be a daunting task for those outside of the community. The members of this working group need to gather and channel this feedback into one place where the people building OpenStack itself can consume it. We should be accepting of feedback in all its forms: conversations, email, IRC, blog posts, etc. The point is to act as a conduit and provide a way to get that feedback to the community.<br />
<br />
<br />
2. Communicate Actionable Items<br />
<br />
This working group has a large and diverse group of stakeholders. It's our responsibility to engage these stakeholders, keep them up to date, and communicate actionable items to them. Specifically the [[Application_Ecosystem_Working_Group#Liaisons|Liaisons]] are responsible for ensuring this happens.<br />
<br />
<br />
3. Content<br />
<br />
The content necessary to grow an application ecosystem comes in many forms. Some examples are:<br />
<br />
* Content for events (eg hackathons)<br />
* White papers<br />
* Code examples<br />
* Application examples<br />
* Application architectures<br />
** e.g. [http://support.rightscale.com/12-Guides/Designers_Guide/Cloud_Solution_Architectures/Cloud_Computing_System_Architecture_Diagrams Cloud Computing System Architecture Diagrams] but with OpenStack services<br />
* Presentations<br />
* Anything else you can think of<br />
<br />
<br />
Where a particular piece of content lives will likely depend on the nature of the content.<br />
<br />
==How to Contribute==<br />
<br />
Contributions come in the form of the deliverables above. <br />
<br />
1. To contribute feedback:<br />
<br />
<br />
2. To communicate actionable items:<br />
<br />
The [[Application_Ecosystem_Working_Group#Liaisons|Liaisons]] will know best how to communicate with their respective stakeholders.<br />
<br />
<br />
3. To contribute content:<br />
<br />
# Email your idea for content to the User Committee mailing list<br />
# Discuss the content and where it should live<br />
# Execute on that idea<br />
<br />
<br />
4. Participate in the discussions at the weekly meeting (see [[Meetings]]).<br />
<br />
==Scope==<br />
<br />
There is the related [[API_Working_Group]] (API WG). The Application Ecosystem Working Group (AE WG) is complementary to the API WG. The AE WG is focused on anyone creating or running an application on OpenStack whereas the API WG is focused on guidelines for the APIs. The place where these groups meet in the middle is the API, which forms the contract between the two. Members of the AE WG are encouraged to be members of the API WG and vice versa.<br />
<br />
<br />
== Liaisons ==<br />
<br />
* [[Win_the_Enterprise|Win the Enterprise]]<br />
** Carol Barrett<br />
* [[API_Working_Group|API Working Group]]<br />
** Everett Toews<br />
** Lance Bragstad<br />
* [[Governance/Foundation/UserCommittee|User Committee]]<br />
** Jonathan Proulx<br />
* [[Governance/TechnicalCommittee|Technical Committee]]<br />
** Anne Gentle<br />
** Rags Srinivas<br />
* [[Governance/DefCoreCommittee|DefCore]]<br />
** Jonathan Bryce<br />
* [[CrossProjectLiaisons|Cross-Project Liaisons]]<br />
** TODO<br />
<br />
==How to Join==<br />
<br />
Join the [http://lists.openstack.org/cgi-bin/mailman/listinfo/user-committee user-committee mailing list], watch for emails that are prefixed by [app], and join the discussion. Start contributing to the deliverables.<br />
<br />
<br />
==Members==<br />
<br />
Please add yourself to this list if you are committed to growing the Application Ecosystem for OpenStack. <br />
<br />
* [mailto:tom@openstack.org Tom Fifield]<br />
* [mailto:evan@hp.com Evan Scheessele]<br />
* [mailto:Shilla.Saebi@gmail.com Shilla Saebi]<br />
* [mailto:victor.r.howard@gmail.com Victor Howard]<br />
* [mailto:carol.l.barrett̊intel.com Carol Barrett]<br />
* [mailto:ksa@slac.stanford.edu Karl Amrhein]<br />
* [mailto:bmorel@internap.com Bruno Morel]<br />
* [mailto:dff.openstack@gmail.com David F. Flanders] @DFFlanders<br />
* [mailto:patricia.montenegro@intel.com Patricia Montenegro]<br />
* [mailto:stefano@removethis-openstack.org Stefano Maffulli]<br />
* [mailto:john.callaghan@hpe.com John Callaghan]<br />
* [mailto:john.e.simpson@intel.com John Simpson - Intel Corporation]<br />
* [mailto:doc@aedo.net Christopher Aedo - IBM]<br />
*[mailto:jason.t.clark@hpe.com Jay Clark - Hewlett-Packard Enterprise]<br />
*[mailto:arunsrinivasan@ebay.com Arun Srinivasan - Ebay]<br />
*[mailto:victor.h.diaz@intel.com Victor Diaz - Intel]<br />
*[mailto:marcela.bonell.manjarrez@intel.com Marcela Bonell - Intel]<br />
<br /><br />
<br /><br />
[[Category:Working_Groups]]<br />
[[Category:UserCommittee]]</div>Mbonellhttps://wiki.openstack.org/w/index.php?title=Application_Ecosystem_Working_Group&diff=124126Application Ecosystem Working Group2016-04-19T05:11:25Z<p>Mbonell: /* Purpose */</p>
<hr />
<div>'''Status''': Active<br />
<br />
'''Organizers''': <br />
*[mailto:john.callaghan@hpe.com John Callaghan] <br />
*[mailto:patricia.montenegro@intel.com Patricia Montenegro]<br />
<br />
==Purpose==<br />
<br />
To create an ecosystem where a diverse array of applications built for OpenStack can thrive.<br />
<br />
Objectives:<br />
* Grow the number of active OpenStack applications globally, for both private and public cloud use<br />
* Make it simpler to create applications for OpenStack by:<br />
** Improving introductory material<br />
** Ensuring appropriate tools and technical information is available, correct and easy to find<br />
* Further facilitating the association of those creating applications for OpenStack clouds with the OpenStack technical community by:<br />
** Improving developer.openstack.org, a portal for application creators<br />
** Analyzing and improving the 6-monthly conference, particularly the "Cloud App Development" track, and other more feedback-style sessions<br />
** Educating OpenStack's active technical community on the issues faced by those who are targeting OpenStack clouds<br />
<br />
==Mail List==<br />
Email: We use the [http://lists.openstack.org/cgi-bin/mailman/listinfo/user-committee user-committee mailing list] and prefix the subject line with [app].<br /><br />
<br />
==Team Meetings==<br />
The team meets weekly, on <big>'''Mondays at 3:00PM (Pacific) / 10:00PM (UTC)'''</big> '''NEW'''<br />
<br />
Call-in Info: '''(888) 875-9370 or 916-356-2663, Bridge: 2, Passcode: 1467696'''<br /> <br />
Australia - Melbourne - Toll free (+61)1300 365 946<br /><br />
<br />
Current Etherpad: https://etherpad.openstack.org/p/2016_Apr_18_App_Ecosystem_Workgroup<br /> <br />
<br />
Previous Etherpad links can be found here: https://etherpad.openstack.org/p/AppEcoSystemWG_Archives<br />
<br />
==Deliverables==<br />
<br />
1. Application Ecosystem Feedback<br />
<br />
Anyone in the application ecosystem needs a way to give feedback to the OpenStack community at large. This can be a daunting task for those outside of the community. The members of this working group need to gather and channel this feedback into one place where the people building OpenStack itself can consume it. We should be accepting of feedback in all its forms: conversations, email, IRC, blog posts, etc. The point is to act as a conduit and provide a way to get that feedback to the community.<br />
<br />
<br />
2. Communicate Actionable Items<br />
<br />
This working group has a large and diverse group of stakeholders. It's our responsibility to engage these stakeholders, keep them up to date, and communicate actionable items to them. Specifically the [[Application_Ecosystem_Working_Group#Liaisons|Liaisons]] are responsible for ensuring this happens.<br />
<br />
<br />
3. Content<br />
<br />
The content necessary to grow an application ecosystem comes in many forms. Some examples are:<br />
<br />
* Content for events (eg hackathons)<br />
* White papers<br />
* Code examples<br />
* Application examples<br />
* Application architectures<br />
** e.g. [http://support.rightscale.com/12-Guides/Designers_Guide/Cloud_Solution_Architectures/Cloud_Computing_System_Architecture_Diagrams Cloud Computing System Architecture Diagrams] but with OpenStack services<br />
* Presentations<br />
* Anything else you can think of<br />
<br />
<br />
Where a particular piece of content lives will likely depend on the nature of the content.<br />
<br />
==How to Contribute==<br />
<br />
Contributions come in the form of the deliverables above. <br />
<br />
1. To contribute feedback:<br />
<br />
<br />
2. To communicate actionable items:<br />
<br />
The [[Application_Ecosystem_Working_Group#Liaisons|Liaisons]] will know best how to communicate with their respective stakeholders.<br />
<br />
<br />
3. To contribute content:<br />
<br />
# Email your idea for content to the User Committee mailing list<br />
# Discuss the content and where it should live<br />
# Execute on that idea<br />
<br />
<br />
4. Participate in the discussions at the weekly TODO (see [[Meetings]]).<br />
<br />
==Scope==<br />
<br />
There is the related [[API_Working_Group]] (API WG). The Application Ecosystem Working Group (AE WG) is complementary to the API WG. The AE WG is focused on anyone creating or running an application on OpenStack whereas the API WG is focused on guidelines for the APIs. The place where these groups meet in the middle is the API, which forms the contract between the two. Members of the AE WG are encouraged to be members of the API WG and vice versa.<br />
<br />
<br />
== Liaisons ==<br />
<br />
* [[Win_the_Enterprise|Win the Enterprise]]<br />
** Carol Barrett<br />
* [[API_Working_Group|API Working Group]]<br />
** Everett Toews<br />
** Lance Bragstad<br />
* [[Governance/Foundation/UserCommittee|User Committee]]<br />
** Jonathan Proulx<br />
* [[Governance/TechnicalCommittee|Technical Committee]]<br />
** Anne Gentle<br />
** Rags Srinivas<br />
* [[Governance/DefCoreCommittee|DefCore]]<br />
** Jonathan Bryce<br />
* [[CrossProjectLiaisons|Cross-Project Liaisons]]<br />
** TODO<br />
<br />
==How to Join==<br />
<br />
Join the [http://lists.openstack.org/cgi-bin/mailman/listinfo/user-committee user-committee mailing list], watch for emails that are prefixed by [app], and join the discussion. Start contributing to the deliverables.<br />
<br />
<br />
==Members==<br />
<br />
Please add yourself to this list if you are committed to growing the Application Ecosystem for OpenStack. <br />
<br />
* [mailto:tom@openstack.org Tom Fifield]<br />
* [mailto:evan@hp.com Evan Scheessele]<br />
* [mailto:Shilla.Saebi@gmail.com Shilla Saebi]<br />
* [mailto:victor.r.howard@gmail.com Victor Howard]<br />
* [mailto:carol.l.barrett̊intel.com Carol Barrett]<br />
* [mailto:ksa@slac.stanford.edu Karl Amrhein]<br />
* [mailto:bmorel@internap.com Bruno Morel]<br />
* [mailto:dff.openstack@gmail.com David F. Flanders] @DFFlanders<br />
* [mailto:patricia.montenegro@intel.com Patricia Montenegro]<br />
* [mailto:stefano@removethis-openstack.org Stefano Maffulli]<br />
* [mailto:john.callaghan@hpe.com John Callaghan]<br />
* [mailto:john.e.simpson@intel.com John Simpson - Intel Corporation]<br />
* [mailto:doc@aedo.net Christopher Aedo - IBM]<br />
*[mailto:jason.t.clark@hpe.com Jay Clark - Hewlett-Packard Enterprise]<br />
*[mailto:arunsrinivasan@ebay.com Arun Srinivasan - Ebay]<br />
*[mailto:victor.h.diaz@intel.com Victor Diaz - Intel]<br />
*[mailto:marcela.bonell.manjarrez@intel.com Marcela Bonell - Intel]<br />
<br /><br />
<br /><br />
[[Category:Working_Groups]]<br />
[[Category:UserCommittee]]</div>Mbonellhttps://wiki.openstack.org/w/index.php?title=Women_of_OpenStack&diff=121889Women of OpenStack2016-03-09T06:34:45Z<p>Mbonell: /* Women of OpenStack Directory */</p>
<hr />
<div>Welcome to the Women of OpenStack wiki page!<br />
<br />
=== Join the discussion! ===<br />
* Subscribe to the [http://lists.openstack.org/cgi-bin/mailman/listinfo/women-of-openstack Mailing List] <br />
* Join the [http://www.linkedin.com/groups/Women-OpenStack-WOS-4681909 LinkedIn group]<br />
* If you're an IRC user, join '''#openstack-women'''.<br /><br />
<br /><br />
<br />
=== Work Group Meeting information ===<br />
<br />
The Women of OpenStack meet every 2 weeks (odd weeks) at 2000 UTC.<br /><br />
<br />
Note: We will not meet on March 7th due to travel and conflicting commitments for many team members. <br />
Our next team meeting will be on March 21.<br />
<br />
{| class="wikitable"<br />
|-<br />
| Next Meeting || Monday, March 21, 2016 2000 UTC Dial In: Access: (888) 875-9370, Bridge: 3; PassCode: 9518007#<br />
|-<br />
| Current Meeting Etherpad || https://etherpad.openstack.org/p/WOS_2_22_16<br />
|-<br />
| Meeting Leader and Agenda Tracker - Pls signup to lead an upcoming meeting! || https://etherpad.openstack.org/p/WOS_Agenda_Tracker<br />
|-<br />
| Archive Meeting Notes || https://etherpad.openstack.org/p/WOS_Meeting_Archives<br />
|-<br />
|}<br />
<br />
=== WOO Initiatives === <br />
<br />
==== Identified Challenges & Suggested Solutions ====<br />
'''Sign up to volunteer [https://docs.google.com/spreadsheets/d/1nu_0EperGdXIQifmjHiNVuB2RJb-5bVJkB9oRT-ExVw/edit?usp=sharing here]!'''<br />
<br />
(takeaways from the May 2015 Vancouver Summit)<br />
{| class="wikitable"<br />
|-<br />
! Group !! Challenge !! Suggested Next Steps <br />
|-<br />
| 1 || Need more women PTLs and need to support women who want to grow as technical contributors || Find ways to support women to be recognized as technical leaders. Example: travel funding for women to attend OpenStack summits <br />
|-<br />
| 2 || Not enough women in the OpenStack community || Attract women to the OpenStack community and support them to remain active in the community. Example: mentorship of women to achieve technical leadership roles <br />
|-<br />
| 3 || Women need support and practice to more confidently communicate in meetings or in larger groups || Webinar on how to participate more effectively in meetings. Example: role play meeting scenarios, help women gain confidence and practice to ask questions during a Tokyo summit talk <br />
|-<br />
| 4 || Need to support higher inclusion of women in the OpenStack community || Workshop to develop leadership soft skills, encourage inclusion, recognize regional gaps in communication, celebrate the successes of women in the OpenStack community <br />
|-<br />
| 5 || Need women leaders to be more visible in the OpenStack main tent sessions || Have a woman keynote speaker, more women participate in panel discussions. Support women with speaker training and creating a pipeline of speaking opportunities for them. <br />
|-<br />
| 6 || Need a supportive and interactive environment for women to come together and support one another with the OpenStack community || Create a private IRC channel for the Women of OpenStack, opportunities to seek and find mentors more naturally based on technology and areas of interest <br />
|-<br />
| 7 || Need a platform to encourage informal mentoring and networking || Reward and recognize mentorship as a key skill that is important as other technical skills<br />
|}<br />
<br />
<br />
=== Past & Current WOO Networking Events ===<br />
<br />
* [http://www.openstack.org/blog/2013/04/women-of-openstack-at-the-portland-summit/ Portland Summit] April, 2013: Networking Breakfast<br />
** [https://www.youtube.com/watch?v=XrHZAQBcfkw Video]<br />
* [http://www.openstack.org/blog/2013/11/women-of-openstack-why/ Hong Kong Summit] November 2013: Boat Outing<br />
* [https://openstacksummitmay2014atlanta.sched.org/event/4740112c1b9074905aee620a97e7a006#.VcylJROqqko Atlanta Summit], May 2014: Happy Hour<br />
* [http://www.openstack.org/blog/2015/01/women-of-openstack-working-session-update/ Paris Summit] November 2014: Networking evening event and breakfast working session<br />
** [https://www.youtube.com/watch?v=lhB1dqpH_ro Video]<br />
* [http://superuser.openstack.org/articles/how-to-get-more-women-involved-in-tech-communication-leadership-and-mentors Vancouver Summit] May 2015: Networking events and breakfast working sessions<br />
** Check out the videos [https://www.youtube.com/watch?v=UWeFKMN7vN0 here] and [https://www.youtube.com/watch?v=8uwoL8E14zw here] and [https://www.youtube.com/watch?v=GsNCLZVWKk8 here]<br />
* Austin Summit Planning meeting notes:<br />
** [https://etherpad.openstack.org/p/WOS_Austin_Planning_12_01_15 Meeting Notes Etherpad 12_01_15]<br />
** [https://etherpad.openstack.org/p/WOS_Austin_Planning_01_20_16 Meeting Notes Etherpad 01_20_16]<br />
** [https://etherpad.openstack.org/p/WOS_Austin_Planning_02_17_16 Meeting Notes Etherpad 02_17_16]<br />
** [https://etherpad.openstack.org/p/WOS_Austin_Planning_03_02_16 Meeting Notes Etherpad 03_02_16]<br />
<br />
=== Past Speaking Sessions ===<br />
<br />
Portland Summit (April 2013):<br />
* [https://www.youtube.com/watch?v=64ChnG4rva0 What Everyone Ought to Know About OpenStack Internships]<br />
<br />
<br />
Paris Summit (November 2014):<br />
* [https://www.youtube.com/watch?v=xxkdnqRj3q0 Team Gender Diversity - Working with the Other 50%]<br />
<br />
<br />
Vancouver Summit (May 2015):<br />
* [https://www.youtube.com/watch?v=Jll-FeDTmcE Standing Tall in the Room]<br />
<br />
<br />
Tokyo Summit (October 2015)<br />
* [http://superuser.openstack.org/articles/women-of-openstack-open-doors-at-the-tokyo-summit-and-in-the-community Women of OpenStack Events at the Tokyo Summit]<br />
* [http://superuser.openstack.org/articles/tackling-diversity-in-the-openstack-community Tackling Diversity in the OpenStack Community]<br />
<br />
=== WOO Coverage ===<br />
<br />
*Outreachy (OpenStack Outreach Program)<br />
** [https://wiki.openstack.org/wiki/Outreachy Wiki page]<br />
** [http://www.openstack.org/blog/2012/11/openstack-outreach-program-for-women-accepting-candidates/ Blog Post] <br />
<br />
* [http://superuser.openstack.org/articles/how-to-craft-a-successful-openstack-summit-proposal Women of OpenStack Webinar]: "How to craft a successful OpenStack Summit Proposal. <br />
<br />
* [http://superuser.openstack.org/articles/why-your-first-openstack-commit-will-always-be-the-hardest Why your first OpenStack commit will always be the hardest]<br />
<br />
* Open Mic Series<br />
** [http://superuser.openstack.org/articles/passion-community-support-success-with-openstack Shilla Saebi]<br />
** [http://www.openstack.org/blog/2014/08/open-mic-spotlight-rossella-sblendido/ Rossella Sblendido]<br />
** [http://www.openstack.org/blog/2014/01/open-mic-spotlight-tatiana-mazur/ Tatiana Mazur] <br />
** [http://www.openstack.org/blog/2013/07/open-mic-spotlight-melanie-witt/ Melanie Witt]<br />
** [http://www.openstack.org/blog/2013/07/open-mic-spotlight-victoria-martinez-de-la-cruz/ Victoria Martínez de la Cruz]<br />
** [http://superuser.openstack.org/articles/blazing-the-trail-for-openstack-in-south-korea Nalee Jang]<br />
<br />
<br />
<br />
==== Read more about other Projects and Events by Women of OpenStack ====<br />
* [http://www.openstack.org/blog/category/women-of-openstack/ OpenStack Blog]<br />
* [http://opensource.com/business/14/2/women-of-openstack-conference-group OpenSource.com]: "The Women of OpenStack talk outreach, education, and mentoring" by Anne Gentle<br />
* [http://superuser.openstack.org/articles/new-to-openstack-why-it-pays-to-jump-right-in OpenStack Superuser]: "New to OpenStack? Why it pays to jump right in" with Megan Rosetti <br />
<br />
<br />
=== Other Women and Diversity Groups ===<br />
<br />
*[http://superuser.openstack.org/articles/how-the-ada-initiative-is-encouraging-diversity-in-the-open-source-community The ADA Initiative]<br />
*[http://www.openstack.org/blog/2013/10/openstack-at-the-grace-hopper-conference/ The Grace Hopper Conference]<br />
<br />
<br />
=== Women of OpenStack Directory ===<br />
Feel free to add yourself to the list. For your Contact info, use whatever you're most comfortable with—Facebook or LinkedIn, Launchpad profile page, IRC handle, etc. <br />
<br />
{| class="wikitable"<br />
|-<br />
! Name !! Contact !! Role !! Area(s) of Interest<br />
|-<br />
| Poonam Yadav || IRC: pyadav <br /> [https://uk.linkedin.com/in/pyadav] || Technical || OpenStack Core projects<br />
|-<br />
|-<br />
| Jane Example Stacker || IRC: JaneS <br /> [https://www.linkedin.com/ LinkedIn] <br /> [http://facebook.com Facebook] || Developer || Nova, Neutron<br />
|-<br />
|Malini Bhandaru || IRC: malini1 <br /> [http://www.linkedin.com/pub/malini-bhandaru/0/578/43a/ LinkedIn] <br /> malini dot k dot bhandaru at intel dot com || Architect & Manager - Intel Open Source Technology Center || Security, Advanced Network Services, Glance, Keystone <br />
|-<br />
| Lana Brindley || IRC: loquacities <br /> || Docs PTL, Docs Core & Rackspace Private Cloud Docs || All projects<br />
|-<br />
| Anne Gentle || IRC: annegentle <br /> || Technical Committee, API WG, Docs || All projects<br />
|-<br />
| Karin Levenstein || IRC: KLevenstein || Docs Writer (Information Developer)<br /> Rackspace Private Cloud docs || OpenStack Core projects<br />
|-<br />
| Alexandra Settle || IRC: asettle <br /> || Docs Writer (Information Developer) || OpenStack Core projects<br />
|-<br />
<br />
| Sayali Lunkad || IRC: sayalilunkad <br /> || training-guides core || training-guides, horizon<br />
|-<br />
| Irena Berezovsky || IRC: irenab <br /> || Architect || neutron, nova, SDN, NFV<br />
|-<br />
| Rossella Sblendido || IRC: rossella_s <br /> || Software Engineer || Neutron<br />
|-<br />
| Shilla Saebi || IRC: ShillaSaebi <br /> [https://twitter.com/shillasaebi/ Twitter] <br /> [https://www.linkedin.com/profile/view?id=118642445&trk=nav_responsive_tab_profile/ Linkedin] <br /> || Docs Core/OpenStack Ops Engineer at Comcast || All projects<br />
|-<br />
| Megan Rossetti || IRC: MeganR <br /> [https://twitter.com/megrossetti/ Twitter] <br /> [https://www.linkedin.com/profile/view?id=18509902&trk=nav_responsive_tab_profile/ Linkedin] <br /> || PM , training-guides, Win the Enterprise || All projects<br />
|<br />
|-<br />
| Samta Rangare || IRC: sam <br /> srangare at mvista dot com <br /> || Software Engineer || Neutron, Nova, Ceilometer, Congress<br />
|-<br />
| Victoria Martínez de la Cruz || IRC: vkmc<br/> [https://www.linkedin.com/in/vmartinezdelacruz LinkedIn]<br/>[https://twitter.com/vkmc Twitter] || Software Developer || All projects<br />
|-<br />
| Sandhya Dasu || IRC: sadasu <br /> [https://www.linkedin.com/in/SandhyaDasu LinkedIn] <br /> sadasu at cisco dot com|| Developer || Neutron, NFV<br />
|-<br />
| Emily Hugenbruch || IRC: ekhugen <br /> [https://www.linkedin.com/pub/emily-hugenbruch/a/670/98/ LinkedIn] <br /> [https://twitter.com/ekhugen Twitter]|| Software Engineer || Nova, Tempest<br />
|-<br />
| Catherine Richardson || catherine.richardson@rackspace.com || Information Developer<br /> Rackspace DevDocs || Rackspace API documentation<br />
|-<br />
| Anne McCormick || IRC: annemccormick <br /> [https://www.linkedin.com/pub/anne-winiewicz-mccormick/1/896/8a7 LinkedIn] <br /> || Software Engineer || Neutron<br />
|-<br />
| Kathy Cacciatore || kathyc@openstack.org || Consulting Marketing Manager, OpenStack Foundation || Enterprise Marketing<br />
|-<br />
| Priti Desai || priti_desai@symantec.com || OpenStack Evangelista || OpenStack Doc, Keystone, OSSG<br />
|-<br />
|-<br />
| Beth Cohen || bfcohen@luthcomputer.com <br /> [http://www.linkedin.com/in/bfcohen LinkedIn Profile] <br /> [https://twitter.com/bfcohen Twitter] <br />|| Cloud Technologist || OpenStack Doc, Cloud Architectures<br />
|-<br />
| Aysy Anne Duarte || IRC: aysyd <br /> [https://br.linkedin.com/in/aysyanne/ LinkedIn] <br /> [https://twitter.com/aysyanne Twitter] || Software Engineer || QA <br />
|-<br />
| Nisha Agarwal || IRC: Nisha || Software Engineer || ironic, nova<br />
|-<br />
| Summer Long || IRCː slong || Software Engineer || security<br />
|-<br />
| Tamara Johnston || IRC: TamaraJ <br /> [https://twitter.com/TJohnstonCloud Twitter] <br /> [https://www.linkedin.com/in/tamjohnston LinkedIn] || Senior Manager, Cloud Services || OpenStack Doc<br />
|-<br />
| Val Wanjura || IRCː arcee2 || Technical Operations Manager || All Projects<br />
|-<br />
| Amy Marrich || IRC: spotz || Linux Systems Engineer || OSA, Heat, Barbican, Community<br />
|-<br />
| Carol Barrett || IRC: barret1 || Data Center Software Planner || Community<br />
|-<br />
| Shaifali Agrawal || IRC: exploreshaifali <br /> [https://www.linkedin.com/profile/view?id=257818581 LinkedIn] <br /> [http://twitter.com/exploreshaifali Twitter] || Individual Contributor, Software Developer || Zaqar, Horizon, Magnum, Kola, Trove,TripleO<br />
|-<br />
| Darla Ahlert || IRC: alraddarla <br /> [https://www.linkedin.com/in/darlaahlert LinkedIn] <br /> || Software Engineer|| All Projects<br />
|-<br />
| Margaret Chiosi || IRC: mchiosi <br /> [https://www.linkedin.com/in/mtchiosi LinkedIn] <br /> || Network Architect|| All Projects<br />
|-<br />
| Holly Bazemore || IRC: cloudhollyb <br /> [https://twitter.com/hfbazemore Twitter] <br /> [https://www.linkedin.com/profile/view?id=AAIAAAByreYBKVGzzWH0s_qH0qQ-as81debWPsc&trk=nav_responsive_tab_profile/ Linkedin] <br /> || Director of Elastic Cloud Strategy and Deployments at Comcast || All projects<br />
|-<br />
| K Rain Leander || IRC: leanderthal <br /> [https://twitter.com/rainsdance Twitter] <br /> [https://www.linkedin.com/in/rainsdance Linkedin] <br /> || Software Engineer || TripleO<br />
|-<br />
|-<br />
| Aimee Ukasick || IRC: aimeeU<br /> aimee.ukasick@att.com<br />[https://www.linkedin.com/in/aimee-ukasick-3a441129 LinkedIn]<br /> || Developer on the AT&T OpenStack Community Team|| All Projects<br />
|-<br />
|-<br />
| Marcela Bonell || IRC: mbonell<br /> [https://www.linkedin.com/in/mbonell LinkedIn]<br /> || Cloud Software Engineer || Developer's Experience (First App, SDK's, Heat, Murano, API, Documentation)<br />
|-</div>Mbonellhttps://wiki.openstack.org/w/index.php?title=Application_Ecosystem_Working_Group&diff=105482Application Ecosystem Working Group2016-02-23T01:08:30Z<p>Mbonell: /* Members */</p>
<hr />
<div>'''Status''': Active<br />
<br />
'''Organizers''': <br />
*[mailto:john.callaghan@hpe.com John Callaghan] <br />
*[mailto:patricia.montenegro@intel.com Patricia Montenegro]<br />
<br />
==Purpose==<br />
<br />
To create an ecosystem where a diverse array of applications built for OpenStack can thrive.<br />
<br />
Objectives:<br />
* Grow the number of active OpenStack applications globally, for both private and public cloud use<br />
* Make it simpler to create applications for OpenStack by:<br />
** Improving introductory material<br />
** Ensuring appropriate tools and technical information is available, correct and easy to find<br />
* Further facilitating the association of those creating applications for OpenStack clouds with the OpenStack technical community by:<br />
** Improving developer.openstack.org, a portal for application creators<br />
** Analyzing and improving the 6-monthly conference, particularly the "Targeting OpenStack" track, and other more feedback-style sessions<br />
** Educating OpenStack's active technical community on the issues faced by those who are targeting OpenStack clouds<br />
<br />
<br />
==Mail List==<br />
Email: We use the [http://lists.openstack.org/cgi-bin/mailman/listinfo/user-committee user-committee mailing list] and prefix the subject line with [app].<br /><br />
<br />
==Team Meetings==<br />
The team meets weekly, on Tuesdays at 0:00 UTC (Mondays at 4:00PM Pacific) '''NEW'''<br />
<br />
Call-in Info for '''February 22''': (888) 875-9370 or 916-356-2663, '''Bridge: 2, Passcode: 9018731''' <br /> <br />
Australia - Melbourne - Toll free (+61)1300 365 946<br /><br />
<br />
Current Etherpad: https://etherpad.openstack.org/p/2016_Feb_22_App_Ecosystem_Workgroup<br /><br />
<br />
Previous Etherpad links can be found here: https://etherpad.openstack.org/p/AppEcoSystemWG_Archives<br />
<br />
==Deliverables==<br />
<br />
1. Application Ecosystem Feedback<br />
<br />
Anyone in the application ecosystem needs a way to give feedback to the OpenStack community at large. This can be a daunting task for those outside of the community. The members of this working group need to gather and channel this feedback into one place where the people building OpenStack itself can consume it. We should be accepting of feedback in all its forms: conversations, email, IRC, blog posts, etc. The point is to act as a conduit and provide a way to get that feedback to the community.<br />
<br />
<br />
2. Communicate Actionable Items<br />
<br />
This working group has a large and diverse group of stakeholders. It's our responsibility to engage these stakeholders, keep them up to date, and communicate actionable items to them. Specifically the [[Application_Ecosystem_Working_Group#Liaisons|Liaisons]] are responsible for ensuring this happens.<br />
<br />
<br />
3. Content<br />
<br />
The content necessary to grow an application ecosystem comes in many forms. Some examples are:<br />
<br />
* Content for events (eg hackathons)<br />
* White papers<br />
* Code examples<br />
* Application examples<br />
* Application architectures<br />
** e.g. [http://support.rightscale.com/12-Guides/Designers_Guide/Cloud_Solution_Architectures/Cloud_Computing_System_Architecture_Diagrams Cloud Computing System Architecture Diagrams] but with OpenStack services<br />
* Presentations<br />
* Anything else you can think of<br />
<br />
<br />
Where a particular piece of content lives will likely depend on the nature of the content.<br />
<br />
==How to Contribute==<br />
<br />
Contributions come in the form of the deliverables above. <br />
<br />
1. To contribute feedback:<br />
<br />
<br />
2. To communicate actionable items:<br />
<br />
The [[Application_Ecosystem_Working_Group#Liaisons|Liaisons]] will know best how to communicate with their respective stakeholders.<br />
<br />
<br />
3. To contribute content:<br />
<br />
# Email your idea for content to the User Committee mailing list<br />
# Discuss the content and where it should live<br />
# Execute on that idea<br />
<br />
<br />
4. Participate in the discussions at the weekly TODO (see [[Meetings]]).<br />
<br />
==Scope==<br />
<br />
There is the related [[API_Working_Group]] (API WG). The Application Ecosystem Working Group (AE WG) is complementary to the API WG. The AE WG is focused on anyone creating or running an application on OpenStack whereas the API WG is focused on guidelines for the APIs. The place where these groups meet in the middle is the API, which forms the contract between the two. Members of the AE WG are encouraged to be members of the API WG and vice versa.<br />
<br />
<br />
== Liaisons ==<br />
<br />
* [[Win_the_Enterprise|Win the Enterprise]]<br />
** Carol Barrett<br />
* [[API_Working_Group|API Working Group]]<br />
** Everett Toews<br />
** Lance Bragstad<br />
* [[Governance/Foundation/UserCommittee|User Committee]]<br />
** Jonathan Proulx<br />
* [[Governance/TechnicalCommittee|Technical Committee]]<br />
** Anne Gentle<br />
** Rags Srinivas<br />
* [[Governance/DefCoreCommittee|DefCore]]<br />
** Jonathan Bryce<br />
* [[CrossProjectLiaisons|Cross-Project Liaisons]]<br />
** TODO<br />
<br />
==How to Join==<br />
<br />
Join the [http://lists.openstack.org/cgi-bin/mailman/listinfo/user-committee user-committee mailing list], watch for emails that are prefixed by [app], and join the discussion. Start contributing to the deliverables.<br />
<br />
<br />
==Members==<br />
<br />
Please add yourself to this list if you are committed to growing the Application Ecosystem for OpenStack. <br />
<br />
* [mailto:tom@openstack.org Tom Fifield]<br />
* [mailto:evan@hp.com Evan Scheessele]<br />
* [mailto:Shilla.Saebi@gmail.com Shilla Saebi]<br />
* [mailto:victor.r.howard@gmail.com Victor Howard]<br />
* [mailto:carol.l.barrett̊intel.com Carol Barrett]<br />
* [mailto:ksa@slac.stanford.edu Karl Amrhein]<br />
* [mailto:bmorel@internap.com Bruno Morel]<br />
* [mailto:dff.openstack@gmail.com David F. Flanders] @DFFlanders<br />
* [mailto:patricia.montenegro@intel.com Patricia Montenegro]<br />
* [mailto:stefano@removethis-openstack.org Stefano Maffulli]<br />
* [mailto:john.callaghan@hpe.com John Callaghan]<br />
* [mailto:john.e.simpson@intel.com John Simpson - Intel Corporation]<br />
* [mailto:doc@aedo.net Christopher Aedo - IBM]<br />
*[mailto:jason.t.clark@hpe.com Jay Clark - Hewlett-Packard Enterprise]<br />
*[mailto:arunsrinivasan@ebay.com Arun Srinivasan - Ebay]<br />
*[mailto:victor.h.diaz@intel.com Victor Diaz - Intel]<br />
*[mailto:marcela.bonell.manjarrez@intel.com Marcela Bonell - Intel]<br />
<br /><br />
<br /><br />
[[Category:Working_Groups]]<br />
[[Category:UserCommittee]]</div>Mbonellhttps://wiki.openstack.org/w/index.php?title=Meetings/Rally&diff=91967Meetings/Rally2015-10-07T22:20:48Z<p>Mbonell: /* Agenda */</p>
<hr />
<div>= Weekly Rally meeting =<br />
The [https://launchpad.net/Rally Rally] project team holds a weekly (starting from Oct 29th 2013) team meeting in <code><nowiki>#openstack-meeting</nowiki></code>:<br />
<br />
* Weekly on Mondays at [http://www.worldclock.com/world_clock.html 1400 UTC]<br />
<br />
= Weekly Rally release meeting = <br />
<br />
At this meeting, we do not discuss common topics but release-specific stuff only, including the list of critical patches that have to be merged in the next release; Held in IRC, in the <code><nowiki>#openstack-rally</nowiki></code> channel (irc.freenode.net). <br />
<br />
* Held on Mondays at [http://www.worldclock.com/world_clock.html 1300 UTC]<br />
<br />
= Next meeting = <br />
<br />
NOTE: Include your IRC nickname with your agenda items so that you can be called upon in the meeting and arrive at the meeting promptly if placing items in agenda. Please have any supporting links ready. You might want to put this on your calendar if you are adding items. <br />
<br />
<br />
== Agenda template==<br />
<br />
* [irc_nickname] Topic name. In additional some general question to the community<br />
- Link to the patch, additional links or information.<br />
<br />
== Agenda ==<br />
<br />
'''October 12st, 2015 14:00 UTC'''<br />
* [mbonell] Blueprint discussion. New command to install Tempest's plugins in rally verify.<br />
- https://blueprints.launchpad.net/rally/+spec/install-tempest-plugins<br />
<br />
= Previous meetings =<br />
<br />
'''October 5st, 2015 14:00 UTC'''<br />
* [boris-42] Bug reports housekeeping (Agreed: We will reduce size of patch queue and amount of bugs in project. Bug manager will be ilyakhudoshin. Try keep like less then 30 open bugs)<br />
<br />
'''September 28st, 2015 14:00 UTC'''<br />
* [redixin] rally-ci updates. (Info: Now it supports cloud images. Also it support btrfs (previously was only zfs). Added lots of small changes like timeouts and triggering jobs by ref-updated. Current rally-ci configuration may be found here: https://github.com/redixin/rci-config/blob/master/config.yaml Status of rally-ci may be seen here https://blueprints.launchpad.net/rally-ci)<br />
* [boris-42] Rally 0.1.0 updates (Info: we did it! Here are release notes https://rally.readthedocs.org/en/latest/release_notes/latest.html)<br />
* [boris-42] About Rally 0.1.1 (Info: Should cut new Release 0.1.1 mostly because of serious bug in Rally reports)<br />
* [boris-42] Critical bugs in reports (Info: patch https://review.openstack.org/#/c/228403/)<br />
* [ylobankov] Creating Tempest resources (Info: started work on this https://review.openstack.org/#/c/226652/)<br />
* [rvasilets] A small refactor of Rally install script:<br />
- https://review.openstack.org/#/c/190931/4<br />
<br />
'''September 21st, 2015 14:00 UTC'''<br />
* [amaretskiy] New Rally release model (Info: now we have flexible ability to publish major and minor releases)<br />
* [amaretskiy] Discuss Rally Tags (See [openstack-dev] [openstack-operators][tc][tags])<br />
* [andreykurilin] Status for implementation of 'rally task abort' command<br />
- https://review.openstack.org/#/c/161636/<br />
* [stpierre] The users context acts differently for the v3 and v2 APIs; in the former case, it auto-adds the user to a "member" role, while it doesn't in v2. (Bug: https://bugs.launchpad.net/rally/+bug/1492177)<br />
<br />
'''September 14th, 2015 14:00 UTC'''<br />
* [kun] argument for using atomic actions or not<br />
In the patch https://review.openstack.org/#/c/220200/, the output http://paste.openstack.org/show/451164/ of task seems bad, but:<br />
- if not using atomic actions, the output keeps meaningless from real business<br />
- if using atomic actions, the record time represent a combine of multiple calls, how do operators know what bad happened inside it?<br />
* [rvasilets] How to use Rally API in our functional tests?<br />
- https://review.openstack.org/#/c/198772/ As I understand from this log http://logs.openstack.org/72/198772/8/check/gate-rally-dsvm-cli/f2114f2/console.html.gz#_2015-08-07_15_13_59_652 rally db is empty because "no such table: deployments". Is any idea how to use it right in func tests?<br />
* [boris-42] Rally Tags for Big Tent<br />
<br />
'''September 7th, 2015 14:00 UTC'''<br />
* [yfried] "Compose scenario" vs "new input task format:<br />
We have 2 specs that want to enhance the execution of existing tasks. Can we please define if/how they relate<br />
to each other?<br />
- https://github.com/openstack/rally/blob/master/doc/specs/in-progress/new_rally_input_task_format.rst<br />
- https://review.openstack.org/#/c/215762/<br />
* [boris-42] Rally Info & Plugin reference <br />
* [boris-42] What is important for Rally 0.1.0 release<br />
<br />
'''August 31th, 2015 14:00 UTC'''<br />
<br />
* [amaretskiy] Status for patches related to HTML reports and new charts classes<br />
- https://review.openstack.org/#/c/214695/<br />
- https://review.openstack.org/#/c/146814/<br />
- https://review.openstack.org/#/c/169828/<br />
- https://review.openstack.org/#/c/215598/<br />
* [ikhudoshyn] Object-oriented design of task configuration<br />
- https://review.openstack.org/#/c/211160/<br />
* [boris-42] Rally Plugin reference<br />
<br />
'''August 24th, 2015 14:00 UTC'''<br />
* [andreykurilin] The critical number of outdated patches on review.<br />
- There are a lot of patches on review without any updates at last 2-4 weeks. What we should do with them? Maintain or Abandon(best-practice from OpenStack community)?<br />
* [boris-42] Updates about switching to Plugin base.<br />
<br />
'''August 17th, 2015'''<br />
* [kun_huang] [short news] chinese openstack hackathon (There is a meetup in this week, openstack hackathon (china))<br />
* [rvasilets] 'rally task abort' now is green! Welcome to review. https://review.openstack.org/#/c/161636/<br />
* [boris-42] Switching Scenario to plugin base https://review.openstack.org/#/c/212831/ After this patch we will be able to do few next things:<br />
- common deprecation mechanism for all types of plugins<br />
- common (scenario like) validation mechanism for all types of plugins<br />
- common types mechanism and replace a bunch of bad code from rally engine/framework<br />
* [boris-42] Where is 0.1.0 release? (Agreed: need to switch to plugin base scenarios and implement task aborts. Probably in two weeks)<br />
<br />
'''August 10th, 2015'''<br />
* [amaretskiy ]New classes for HTML report charts. https://review.openstack.org/#/c/159458 (Agreed: They are already done, need review for it)<br />
* [kun] ]Vm workload https://docs.google.com/document/d/1FQicnj6aIdbfYts9ofYdz0dUEf9zyssWqDjQR40h268/edit (Agreed: the next step is to create servers_ext context)<br />
* [kun] What's the state of Solaris support?<br />
* [ikhudoshyn] Refactor BenchmarkEngine https://review.openstack.org/#/c/209046/ (Agreed: take a look at this)<br />
<br />
'''August 3th, 2015'''<br />
* Swift context for Sahara in Rally https://review.openstack.org/#/c/177732/ (Agreed: boris-42 will take a look at them)<br />
* Ability to specify directory with murano package files https://review.openstack.org/#/c/195677/ (Agreed: boris-42 believe that rvasilets should just ping other cores to review it)<br />
* Add 'description' element to scenario config https://review.openstack.org/181307 (Agreed: this information should be somewhere used not just added. yingjun will add this to the task reports)<br />
<br />
'''July 27th, 2015'''<br />
* Make Rally framework independent from OpenStack https://review.openstack.org/#/c/203911/<br />
* Create_and_list_<singular> (e.g., create_and_list_image) or create_and_list_<plural> (e.g., create_and_list_users)? (Agreed: we should use plural everywhere and make hacking rule for this)<br />
* Verify performance with Rally: compare performance of scenarios after 2 runs (Agreed: We will finish this task someday)<br />
* Replace depraceted oslo.db code https://review.openstack.org/#/c/205530/ (Agreed: Looks reasonable)<br />
<br />
'''July 20th, 2015'''<br />
* [boris-42] Meeting agenda and how to make people work on it not at the very last moment (Agreed: meeting manager sends out reminder on Thursday)<br />
* [boris-42] Splitting Rally framework and OpenStack (updates) (Boris: Need "patch that will make our context responsible for mapping resources for each scenario iteration. e.g. I will move this code https://github.com/openstack/rally/blob/master/rally/task/runner.py#L47-L58 to ContextManager. I am going to publish this patch today later")<br />
* [boris-42] Support of benchmarking multi API versions of projects with same plugins (Boris: "We will have special context for openstack_api_versions where you can specify info what python clients to create and there will be validator for all scenarios (which versions they support) and a bit magic in osclients and openstack.scenario to make this work.")<br />
* [amaretskiy] Status for patches related to new streaming Reports generation: (Need code review)<br />
- [https://review.openstack.org/#/c/201611/ more streaming algorithms]<br />
- [https://review.openstack.org/#/c/159458/ new classes for Reports generation]<br />
- [https://review.openstack.org/#/c/146814/ use new classes and chunks for reports]<br />
- [https://review.openstack.org/#/c/169828/ add LoadProfile chart to reports]<br />
* Ironic benchmarks '''led by rvasilets''': (Need code review)<br />
- https://review.openstack.org/#/c/186064/ need code review<br />
<br />
'''July 13th, 2015:'''<br />
* Supporting Solaris (Agreed: We will support Solaris and we will start from CI for it)<br />
* Should we support py26? (Need: Talk without dhellmann about cuping release versions in requriments)<br />
* Stucked specs. https://review.openstack.org/#/c/182245/ (Agreed Split "Refactoring Rally cleanup": 1) consistent resource naming; 2) the actual cleanup.)<br />
* Stucked patches (pain) https://review.openstack.org/#/q/project:openstack/rally+branch:master+topic:bp/vm-workloads-framework,n,z (Agree: Cores take a look at it)<br />
* Who is in charge for moderating 2 next meetings? (Agree: stpierre is going to be in charge for next two meethings)<br />
* Murano benchmarks https://review.openstack.org/#/c/195677/ (Need: code review)<br />
* Cinder benchmarks (Cinder is going to make rally job voting after https://review.openstack.org/#/c/194180/ )<br />
* Ironic benchmarks https://review.openstack.org/#/c/186064/ (Agree: Ask somebody from Ironic core team for review)<br />
<br />
'''July 6th 2015:'''<br />
* Rally Meeting Agenda (Agreed: rotate each 2 weeks meeting manager; write summaries by hand using meetbot stuff https://wiki.debian.org/MeetBot)<br />
* Ironic benchmarks https://review.openstack.org/#/c/186064/. Issues with recursion wile Ironic task execute http://logs.openstack.org/64/186064/14/experimental/gate-rally-dsvm-ironic-rally/9b0a8d7/console.html.gz#_2015-06-30_14_39_09_363 (Agreed: try to understand why Ironic benchmarks doesn't work and why CLI of ironic works; boris-42 will review Ironic patch https://review.openstack.org/#/c/186064/)<br />
* Use DDT framework in tests. Sample of DDT way to test https://github.com/openstack/rally/blob/master/tests/unit/plugins/openstack/scenarios/manila/test_utils.py#L117-L133 (Agreed: using ddt for newly added tests, low priority to rewite)<br />
* Optimize Rally imports https://review.openstack.org/#/c/196493/ (Agreed: That patch should be merged =))<br />
* Some review work update https://etherpad.openstack.org/p/rally_review_work. (Action: do the changes with rally dashboard to fit kun_huang requirments. Agreed: review the oldest patches firstly)<br />
<br />
'''June 29th 2015:'''<br />
* Fixtures upgrades that is block Rally gates<br />
* Optimize Rally imports to reduce start time<br />
* Open discussion<br />
Logs form the meeting above here http://eavesdrop.openstack.org/meetings/rally/2015/rally.2015-06-29-14.01.log.html<br />
<br />
'''June 22th 2015:'''<br />
* Broken cinder attach volume update (https://review.openstack.org/193828)<br />
* Rally task abort (finished)<br />
* Rally CI updates(format of config file, web ui, etc.)<br />
* Rally monasca job<br />
* Open discussion<br />
Logs form the meeting above http://eavesdrop.openstack.org/meetings/rally/2015/rally.2015-06-22-14.11.log.html<br />
<br />
'''June 15th 2015:'''<br />
* Rally gates are/were blocked (ways to became more isolated from such mistakes)<br />
* Delays in next release<br />
* Open discussion<br />
Logs form the meeting above http://eavesdrop.openstack.org/meetings/rally/2015/rally.2015-06-15-14.11.log.html<br />
<br />
'''June 8th 2015:'''<br />
* Plugin base (finished)<br />
* Rally core structure changes<br />
* Rally as a Lib & Rally as a Service (spec https://review.openstack.org/#/c/182245/)<br />
* Rally Infra updates (https://review.openstack.org/#/c/185031/)<br />
* Open discussion<br />
Logs form the meeting above http://eavesdrop.openstack.org/meetings/rally/2015/rally.2015-06-08-14.09.log.html<br />
<br />
'''May 25th 2015:'''<br />
* New HTML reports classes (https://review.openstack.org/#/c/159458/, https://review.openstack.org/#/c/146814/, https://review.openstack.org/#/c/169828/)<br />
* New script for gate jobs (https://review.openstack.org/#/c/175549/)<br />
* Fuel benchmarks (https://review.openstack.org/#/c/178731/)<br />
* Specs in the review<br />
* Open discussion<br />
Logs form the meeting above http://eavesdrop.openstack.org/meetings/rally/2015/rally.2015-05-25-14.01.log.html<br />
<br />
'''May 18th 2015:'''<br />
* [Spec] Enhance Rally API (https://review.openstack.org/182245)<br />
* Fuel benchmarks (https://review.openstack.org/#/c/178731/, https://review.openstack.org/#/c/181270/, https://review.openstack.org/#/c/182873/)<br />
* Splitting plugins in Rally (https://review.openstack.org/#/q/project:openstack/rally+branch:master+topic:bp/split-plugins,n,z)<br />
* Where to find answers (http://rally.readthedocs.org/en/latest/project_info.html)<br />
* Open discussion<br />
Logs form the meeting above http://eavesdrop.openstack.org/meetings/rally/2015/rally.2015-05-18-14.04.log.html<br />
<br />
'''April 28th 2015:'''<br />
* Rally QA week<br />
* Upcoming Rally 0.0.4 release: progress on critical patches<br />
* Spec on refactoring scenario utils: review and discussion (https://review.openstack.org/#/c/172831/)<br />
* Spec on in-tree functional tests: review and discussion (https://review.openstack.org/#/c/166487/)<br />
* Open discussion<br />
Logs form the meeting above http://eavesdrop.openstack.org/meetings/rally/2015/rally.2015-04-28-17.00.log.html<br />
<br />
= Meeting logs =<br />
* [http://eavesdrop.openstack.org/meetings/rally/2015/ Meeting logs for 2015]<br />
* [http://eavesdrop.openstack.org/meetings/rally/2014/ Meeting logs for 2014]<br />
* [http://eavesdrop.openstack.org/meetings/rally/2013/ Meeting logs for 2013]<br />
<br />
= Have any questions? =<br />
<br />
Ping boris-42 at <code><nowiki>#openstack-rally</nowiki></code></div>Mbonell