https://fedoraproject.org/w/api.php?action=feedcontributions&user=Kushal&feedformat=atomFedora Project Wiki - User contributions [en]2024-03-19T12:42:22ZUser contributionsMediaWiki 1.39.4https://fedoraproject.org/w/index.php?title=Fedora_Meetup_Pune_June_2019&diff=545115Fedora Meetup Pune June 20192019-06-05T07:48:55Z<p>Kushal: adding my name</p>
<hr />
<div>{{header|events}}<br />
<br />
= Fedora Events: Fedora Meetup Pune, June 2019 =<br />
<br />
== About ==<br />
<br />
Let's all gather to celebrate the release of Fedora 30 and also to know about the latest features which were added to make the life of a developer easier. In addition we'll also talk about Modularity and Fedora CoreOS so don't miss out this opportunity.<br />
<br />
== Location & Schedule ==<br />
<br />
* '''Date:''' 15th June 2019 <br />
* '''Time:''' 10:00 IST till 13:00 IST<br />
* '''Address:''' <br />
** Red Hat India Pvt. Ltd. Tower X, Level-1, Magarpatta city, Hadapsar, Pune, Maharashtra 411013<br />
<br />
* '''Note:''' Please carry a valid ID proof to enter the building. If security guys ask, tell them you are coming to meet Ompragash or Parag. <br />
Emergency contact number: +91 7028019962<br />
<br />
== Participants ==<br />
<br />
Please add your name here.<br />
<br />
{|<br />
! # !! Name <br />
|-<br />
| 1 || [[User:ompragash | Ompragash Viswanathan ]] (Organizer)<br />
|-<br />
| 2 || [[User:Pnemade | Parag Nemade]] (Organizer)<br />
|-<br />
| 3 || [[User:pravins | Pravin Satpute]] (Organizer)<br />
|-<br />
| 4 || [[User:suprith4989 | Suprith Gangawar]] (Organizer)<br />
|-<br />
| 5 || [[User:Pyadav | Pooja Yadav]] (Organizer)<br />
|-<br />
| 6 || [[User:Kumarpraveen| Praveen Kumar]] (Speaker)<br />
|-<br />
| 7 || [[User:Whereistejas| Tejas Sanap]] (Attendee)<br />
|-<br />
| 8 || [[User:kushal| Kushal Das]] (Attendee)<br />
|}<br />
<br />
== Agenda ==<br />
<br />
* 10:00- 10:30 Fedora 30 Features: A Brief Walk-through <br />
* 10:35- 11:15 What is Modularity in Fedora?<br />
* 11:20- 12:00 Introduction to Fedora CoreOS<br />
* 12:05- 13:00 Fedora 30 Release Celebration<br />
<br />
<br />
[[Category:Marketing]] [[Category:Events]] [[Category:Events 2018]]</div>Kushalhttps://fedoraproject.org/w/index.php?title=Release_Party_F27_Pune&diff=506155Release Party F27 Pune2017-11-21T09:47:42Z<p>Kushal: /* Who Will Attend */ Adding my name</p>
<hr />
<div>{{header|events}}<br />
= Fedora 27 Release Party - Pune, India =<br />
<br />
*What: '''Fedora 27 Release Party'''<br />
*When: '''November 22, 2017'''<br />
*Time: '''1:00 PM - 2:00 PM'''<br />
*Where: '''Red Hat India Pvt.Ltd'''<br />
**Address: '''Lohgad, Level-1, Tower X, Magarpatta Inner Circle, Magarpatta city, Hadapsar, Pune, Maharashtra 411013'''<br />
<br />
== Who Will Attend ==<br />
* [[user:Pravins|Pravin Satpute]] (Organizer)<br />
* [[user:Rtalwatk|Rupali Talwatkar]] (Organizer) <br />
* [[User:Pnemade|Parag Nemade]]<br />
* [[User:Sundeep|Sundeep Anand]]<br />
* [[User:Petersen|Jens Petersen]]<br />
* [[User:Fujiwara|Takao Fujiwara]]<br />
* [[User:Tagoh|Akira TAGOH]]<br />
* [[User:pwu|Peng Wu]]<br />
* [[User:mfabian|Mike FABIAN]]<br />
* [[User:smaitra|Satyabrata Maitra]]<br />
* [[User:rluzynski|Rafał Lużyński]]<br />
* [[User:Ompragash|Ompragash Viswanathan]]<br />
* [[User:Pyadav|Pooja Yadav]]<br />
* [[User:Sandeeps|Sandeep Shedmake]]<br />
* [[User:Bbarve|Bhushan Barve]] <br />
* [[User:Kushal|Kushal Das]] <br />
* ADD_YOUR_NAME_HERE<br />
<br />
== Schedule ==<br />
<br />
{|<br />
|- style="width: 98% ;color: white; background-color: #3074c2; font-weight: bold"<br />
| '''Time''' || Topic || Speaker <br />
|-<br />
| 1:00 PM - 1:10 PM || Cake Cutting and || Everyone<br />
|-<br />
| 1:10 PM - 1:50 PM || Round Table discussion about F27 & F28 || Everyone<br />
|-<br />
| 1:50 PM - 2:00 PM || Closing Remarks and Group Photo || Everyone<br />
|-<br />
<br />
|}<br />
<br />
== Detailed Cost Breakup ==<br />
<br />
* No budget required.<br />
<br />
== Links ==<br />
<br />
<br />
== Reports ==<br />
<br />
<br />
==Pictures==<br />
<br />
<br />
[[Category:Release events]] [[Category:Events]] [[Category:Events 2017]]</div>Kushalhttps://fedoraproject.org/w/index.php?title=User:Kushal&diff=497149User:Kushal2017-07-07T07:51:14Z<p>Kushal: updating the page</p>
<hr />
<div><br />
= Kushal Das =<br />
I am the Fedora Cloud Engineer, and also a Fedora Ambassador and mentor from India. I keep contributing to various teams inside Fedora, like docs, l10n, artwork, packaging, marketing. <br />
I am a CPython Core developer and director at Python Software Foundation.<br />
<br />
__TOC__<br />
<br />
Visit my [http://www.kushaldas.in blog] .<br />
== About Me ==<br />
* I am a Free Software developer and a coordinator of Linux Users Group of Durgapur ([http://www.dgplug.org dgplug] ). I stay in Pune, in India. I try to cover different GNU/Linux events through the country to spread the words of Fedora. My LUG, dgplug is mainly full of Fedora users :) <br />
* I am a fellow at Python Software Foundation.<br />
* I maintain various packages in Fedora, a list can be found at https://admin.fedoraproject.org/pkgdb/users/packages/kushal?acls=owner&acls=commit<br />
* I wrote a book on Python programming language, you can read it at [https://pymbook.readthedocs.io here]<br />
* I organize an online summer training for students which is generally attended by students all across India and from few other countries. 2017 is the 10th year of the training. Details can be found [https://dgplug.org/summertraining17 here]<br />
* I teach Python in various workshops and also online.<br />
<br />
== Badges ==<br />
{{#fedorabadges: kushal }}<br />
<br />
'''Badges Count:''' {{ #fedorabadgescount: kushal }}<br />
<br />
== Talks & Workshops ==<br />
<br />
* "MicroPython and NodeMCU", workshop at FOSSASIA, 2017<br />
* "Micropython workshop for kids", Science Hack Day, India 2016 <br />
* "Testing containers using Tunir", Flock, Poland, 2016<br />
* "Automated testing of CPython patches", [https://lwn.net/Articles/691307/ Language summit], PyCon 2016<br />
* "Tunir, a simple CI", Flock, USA, 2015<br />
* "Document your code", workshop at FOSSASIA 2015<br />
* "Exciting days with Python", at FOSSASSIA 2015<br />
* "Moments from my ongoing journey", keynote at PyCon India 2014<br />
* "Document your code", python-sphinx workshop at PyCon India 2014<br />
* "Document your code", python-sphinx workshop at PyCon India 2013<br />
* "Document your code", python-sphinx workshop at Flock 2013<br />
* "Darkserver: Current and future roadmap" at Flock 2013<br />
* "Darkserver: help to debug userspace" at PyCon US 2013<br />
* "Document your code" at foss.in 2012<br />
* "Introduction to Python" at PyCon India 2012<br />
* "Document your code" at PyCon India 2012<br />
* "Python workshop" at FUDCon KL 2012<br />
* "Darkserver, way to the new world" at FUDCon KL 2012<br />
* "gobject-introspection, a new friend to help" at PyConIndia, 2011<br />
* "Fedora Activity Day" at NIT Durgapur, 2011<br />
* "Python workshop" at NIT Durgapur, 2011<br />
* "System programming using Python" at NIT Durgapur, 2011<br />
* "Python Deadly Combo" at PyConIndia, 2010<br />
* "Python workshop" at GNUnify, 2010<br />
* "Deadly Combo" at FOSS.IN, 2009<br />
* "Python Workshop" at Malda Engineering College, 2009<br />
* "OpenPCD: Free Hardware, Software for RFID" at LinuxTag , Berlin , Germany, 2007<br />
* "OpenPCD: Free Hardware, Software for RFID" at FOSS.NITC meet, Calicut, 2007<br />
* "Python and PyQt4" at SISCR, Pune , 2008<br />
* "KDE Application Development" in Horizon07, Durgapur, 2006<br />
* "Inside of Fedora Extras, a technical journey" in FOSS.IN 2006<br />
* "Its Fedora" in "A day with Fedora", Dr. B. C. Roy Engineering College, Durgapur, 2006<br />
* "An introduction to AJAX & Rico" in Linuxasia 2006<br />
* "dgplug,first trip Round the Sun..problems & answer” in FOSS.IN 2005<br />
<br />
Email: kushal AT fedoraproject DOT org<br />
...<br />
<br />
<br />
[[Category:Ambassadors from India]]</div>Kushalhttps://fedoraproject.org/w/index.php?title=User:Kushal&diff=497148User:Kushal2017-07-07T07:35:00Z<p>Kushal: /* About Me */</p>
<hr />
<div><br />
= Kushal Das =<br />
I am the Fedora Cloud Engineer, and also a Fedora Ambassador and mentor from India. I keep contributing to various teams inside Fedora, like docs, l10n, artwork, packaging, marketing. <br />
I am a CPython Core developer and fellow at Python Software Foundation.<br />
<br />
__TOC__<br />
<br />
Visit my [http://www.kushaldas.in blog] .<br />
== About Me ==<br />
* I am the coordinator of Linux User Group of Durgapur ([http://www.dgplug.org dgplug] ). I stay in Pune, in India. I try to cover different GNU/Linux events through the country to spread the words of Fedora. My LUG, dgplug is mainly full of Fedora users :) <br />
* I am a fellow at Python Software Foundation.<br />
* I maintain various packages in Fedora , a list can be found at https://admin.fedoraproject.org/pkgdb/users/packages/kushal?acls=owner&acls=commit<br />
* I wrote a book on Python programming language, you can read it at [https://pymbook.readthedocs.io here]<br />
* I organize an online summer training for students which is generally attended by students all across India and from few other countries. 2017 is the 19th year of the training. Details can be found [https://dgplug.org/summertraining17 here]<br />
* I teach Python in various workshops and also online.<br />
<br />
== Badges ==<br />
{{#fedorabadges: kushal }}<br />
<br />
'''Badges Count:''' {{ #fedorabadgescount: kushal }}<br />
<br />
== Talks & Workshops ==<br />
<br />
* "Document your code", workshop at FOSSASIA 2015<br />
* "Exciting days with Python", at FOSSASSIA 2015<br />
* "Moments from my ongoing journey", keynote at PyCon India 2014<br />
* "Document your code", python sphinx workshop at PyCon India 2014<br />
* "Document your code", python sphinx workshop at PyCon India 2013<br />
* "Document your code", python sphinx workshop at Flock 2013<br />
* "Darkserver: Current and future roadmap" at Flock 2013<br />
* "Darkserver: help to debug userspace" at PyCon US 2013<br />
* "Document your code" at foss.in 2012<br />
* "Introduction to Python" at PyCon India 2012<br />
* "Document your code" at PyCon India 2012<br />
* "Python workshop" at FUDCon KL 2012<br />
* "Darkserver, way to the new world" at FUDCon KL 2012<br />
* "gobject-introspection, a new friend to help" at PyConIndia, 2011<br />
* "Fedora Activity Day" at NIT Durgapur, 2011<br />
* "Python workshop" at NIT Durgapur, 2011<br />
* "System programming using Python" at NIT Durgapur, 2011<br />
* "Python Deadly Combo" at PyConIndia, 2010<br />
* "Python workshop" at GNUnify, 2010<br />
* "Deadly Combo" at FOSS.IN, 2009<br />
* "Python Workshop" at Malda Engineering College, 2009<br />
* "OpenPCD: Free Hardware, Software for RFID" at LinuxTag , Berlin , Germany, 2007<br />
* "OpenPCD: Free Hardware, Software for RFID" at FOSS.NITC meet, Calicut, 2007<br />
* "Python and PyQt4" at SISCR, Pune , 2008<br />
* "KDE Application Development" in Horizon07, Durgapur, 2006<br />
* "Inside of Fedora Extras, a technical journey" in FOSS.IN 2006<br />
* "Its Fedora" in "A day with Fedora", Dr. B. C. Roy Engineering College, Durgapur, 2006<br />
* "An introduction to AJAX & Rico" in Linuxasia 2006<br />
* "dgplug,first trip Round the Sun..problems & answer” in FOSS.IN 2005<br />
<br />
Email: kushal AT fedoraproject DOT org<br />
...<br />
<br />
<br />
[[Category:Ambassadors from India]]</div>Kushalhttps://fedoraproject.org/w/index.php?title=Ambassadors_Join_choose_a_mentor&diff=485598Ambassadors Join choose a mentor2017-02-07T10:22:37Z<p>Kushal: /* Available */ Removing my name</p>
<hr />
<div>{{header|ambassadors}}<br />
__NOTOC__{{autolang|base=yes}}<br />
{{Link/prev | Ambassadors_Join_request_ambassador_membership | Request Ambassador Membership}}<br />
{{ Admon/note | This is not the [[Ambassadors_Join_start|Ambassadors Join Start Page]], go there first! }}<br />
<br />
'''A Mentor is your partner to get sponsored!'''<br />
<br />
Mentors are experienced ambassadors who can help you quickly become acclimated to the work expected of Ambassadors as well as ensuring that Ambassadors within Fedora do an acceptable job of representing Fedora. <br />
<br />
{{admon/important | <br />
* Please don't expect an immediate reply. Most mentors have full time jobs, families, and many responsibilities within Fedora. Please be patient.<br />
* A mentor will NOT initiate contact with you. You MUST initiate contact with a mentor.<br />
* Also note that a mentor is under no obligation to accept you, you may have to try several mentors, before you find one who has the time and availability to mentor you.<br />
}}<br />
<br />
=== Choosing a mentor ===<br />
Each major region has a list of possible [[#Regional Ambassador Mentors|Regional Ambassador Mentors]]. Please contact the Mentor via email and introduce yourself. Please include the following information:<br />
<br />
* Your main purpose for joining the Fedora Ambassadors. <br />
** '''Note''': The mentor may ask you to expand upon this if it's incomplete, or seems inconsistent with the goals of the Fedora Ambassadors. <br />
* Your Fedora user wiki page. If you have not yet created your user page, please [[Ambassadors_Join_create_user_page|visit this page]]. The mentor will reject your application if you do not have a Fedora user wiki page.<br />
* A bit of information about what you have done so far to promote Fedora amongst your peers/friends.<br />
<br />
This email will help the Mentor to assess your suitability to be an ambassador.<br />
<br />
=== Regional Ambassador Mentors ===<br />
<br />
{{Admon/note | You can obtain help from one of these mentors from your region. Please note that the status indicates whether an ambassador is available or unavailable. Sending an email to a mentor who is '''unavailable''' or '''outside your region''' will result in an unspecified delay!!!}}<br />
<br />
{{admon/important | <br />
"Regional Ambassador Mentors are a group of people - selected, proposed and appointed by people - not by a leveling system - based on trust (and a lot of soft facts). '''Prospective mentors are nominated by existing Mentors and confirmed by FAmSCo - [http://meetbot.fedoraproject.org/fedora-meeting/2010-01-07/fedora-meeting.2010-01-07-18.06.html]'''. If you want to be a mentor for the Ambassador group, be a good ambassador and if asked, volunteer to help, when needed. One great way to prepare is, to be a good mentor for the project as a whole." Mentors follow a [[Ambassador Candidate Ticket Management|defined process]] for helping candidates join the Ambassadors program.}}<br />
<br />
==== North America (NA) ====<br />
<br />
===== Available =====<br />
* [[User:award3535|Andrew Ward]]<br />
* [[User:Markdude|Mark Terranova]]<br />
* [[User:Nb|Nick Bebout]]<br />
<br />
===== Unavailable =====<br />
* [[User:bpowell01|Brian Powell]]<br />
* [[User:Herlo|Clint Savage]]<br />
* [[User:Ke4qqq|David Nalley]]<br />
* [[User:inode0|John Rose]]<br />
* [[User:Quaid|Karsten Wade]]<br />
* [[User:Vwbusguy|Scott Williams]]<br />
<br />
<br />
==== Latin America and Mexico (LATAM) ====<br />
<br />
===== Available =====<br />
*[[User:dbruno|Daniel Bruno]]<br />
*[[User:Nushio|Juan Rodriguez Moreno]]<br />
*[[User:Lbazan|Luis Bazán ]]<br />
*[[User:Tatica|María "tatica" Leandro]]<br />
*[[User:matiasmaceira|Matias Maceira ]]<br />
<br />
===== Unavailable =====<br />
<br />
<br />
==== Europe, Middle-East, Africa (EMEA) ====<br />
<br />
===== Available =====<br />
*[[User:Cmpahar|Christos Bacharakis]]<br />
*[[User:Geroldka|Gerold Kassube]]<br />
*[[User:Giannisk|Giannis Konstantinidis]]<br />
*[[User:Eischmann|Jiří Eischmann]]<br />
*[[User:Affix|Keiran Smith]] (UK and Ireland Only)<br />
*[[User:Palazzot|Marco Palazzotti]] (Italy only)<br />
*[[User:Robyduck|Robert Mayr]]<br />
*[[User:robert|Robert Scheck]]<br />
*[[User:Zoltanh721|Zoltan Hoppar]]<br />
<br />
===== Unavailable =====<br />
*[[User:Biertie|Bert Desmet]]<br />
*[[User:fab|Fabian Affolter]]<br />
*[[User:Shaiton|Kévin Raymond]]<br />
*[[User:MooDoo|Paul Mellors]]<br />
*[[User:Ppapadeas|Pierros Papadeas]]<br />
<br />
<br />
==== Asia-Pacific (APAC) ====<br />
<br />
===== Available =====<br />
*[[User:Kaio|Caius 'kaio' Chance ]]<br />
*[[User:Dramsey|David Ramsey]] (approval as mentor pending)<br />
*[[User:Gbraad|Gerard Braad — 吉拉德 ]]<br />
*[[User:Azneita|HehersonPagcaliwagan]]<br />
*[[User:Tuanta|Truong Anh Tuan]]<br />
<br />
===== Unavailable =====<br />
*[[User:Shakthimaan|Shakthi Kannan]]<br />
*[[User:Susmit|SusmitShannigrahi]]<br />
<br />
<br />
===== APAC [http://en.wikipedia.org/wiki/Oceania Oceania] =====<br />
*[[User:Kaio|Caius 'kaio' Chance ]] (available)<br />
<br />
===== APAC [http://en.wikipedia.org/wiki/Greater_China Greater China / 大中華地區] =====<br />
*[[User:Kaio|Caius 'kaio' Chance ]] (available)<br />
*[[User:Gbraad|Gerard Braad — 吉拉德 ]] (available)<br />
*[[User:Bbbush|Yuan Yijun]] (unavailable)<br />
<br />
<br />
===== APAC India =====<br />
{{admon/note | If you are a student from India, we encourage you to participate in one of the various projects within Fedora before applying to become an Ambassador. We believe that this provides you with the necessary skills and experience to handle the responsibilities expected of a Fedora Ambassador. The various projects can be seen at [http://join.fedoraproject.org join.fedoraproject.org]. Please subscribe to the fedora-india mailing list and join us at #fedora-india on IRC for guidance.}}<br />
<br />
====== Available ======<br />
*[[User:Sankarshan | Sankarshan]]<br />
<br />
====== Unavailable ======<br />
*[[User:Sundaram | Rahul Sundaram]]<br />
*[[User:Shakthimaan| Shakthi Kannan]]<br />
*[[User:Susmit|SusmitShannigrahi]]<br />
<br />
{{Link/next | Ambassadors_Join_subscribe_to_the_ambassadors_mailing_list | Subscribe to the Ambassadors Mailing List}}<br />
<br />
[[Category:Ambassadors]]</div>Kushalhttps://fedoraproject.org/w/index.php?title=Fedora_Meetup_Pune_January_2017&diff=484914Fedora Meetup Pune January 20172017-01-26T06:38:47Z<p>Kushal: /* Fedora Project Attendees */ Updating the list as I will not be attending.</p>
<hr />
<div>{{autolang|base=yes}}<br />
<br />
{{header|events}}<br />
<br />
= Fedora Meetup Pune January 2017 =<br />
<br />
== About ==<br />
<br />
This is a (sort of) monthly meetup in Pune aimed at Fedora contributors and users.<br />
<br />
== Location & Schedule ==<br />
<br />
Date: January 29, 2017 Timing: 2PM onwards<br />
<br />
reserved-bit,<br />
337, Amanora Chambers,<br />
Above Amanora Mall (3rd Floor from the lift at the Exit next to the Ethnicity store)<br />
Hadapsar, Pune - 411028<br />
<br />
Contact number: +91 020 6727 1050<br />
<br />
== Agenda ==<br />
<br />
* Fedora on 96boards, a roundup and potential contribution areas<br />
* Update on glibc documentation<br />
<br />
== Fedora Project Attendees ==<br />
<br />
Please add your name to the end of the list.<br />
<br />
{|<br />
! # !! Name <br />
|-<br />
| 0 || [[User:Siddhesh | Siddhesh]]<br />
|-<br />
| 1 || [[User:Ganeshkadam| Ganesh]]<br />
|-<br />
| 2 || [[User:Dhanesh95| Dhanesh B. Sabane]]<br />
|-<br />
| 3 || [[User:Sayanchowdhury | Sayan Chowdhury]]<br />
|-<br />
|-<br />
| 4 || [[User:Kumarpraveen | Praveen Kumar]]<br />
|-<br />
|}</div>Kushalhttps://fedoraproject.org/w/index.php?title=Fedora_Meetup_Pune_January_2017&diff=484635Fedora Meetup Pune January 20172017-01-23T10:20:02Z<p>Kushal: /* Fedora Project Attendees */ adding my name</p>
<hr />
<div>{{autolang|base=yes}}<br />
<br />
{{header|events}}<br />
<br />
= Fedora Meetup Pune January 2017 =<br />
<br />
== About ==<br />
<br />
This is a (sort of) monthly meetup in Pune aimed at Fedora contributors and users.<br />
<br />
== Location & Schedule ==<br />
<br />
Date: January 29, 2017 Timing: 2PM onwards<br />
<br />
reserved-bit,<br />
337, Amanora Chambers,<br />
Above Amanora Mall (3rd Floor from the lift at the Exit next to the Ethnicity store)<br />
Hadapsar, Pune - 411028<br />
<br />
Contact number: +91 020 6727 1050<br />
<br />
== Agenda ==<br />
<br />
* Fedora on 96boards, a roundup and potential contribution areas<br />
* Update on glibc documentation<br />
<br />
== Fedora Project Attendees ==<br />
<br />
Please add your name to the end of the list.<br />
<br />
{|<br />
! # !! Name <br />
|-<br />
| 42 || [[User:Siddhesh | Siddhesh]]<br />
|-<br />
| 1 || [[User:Kushal| Kushal]]<br />
|-<br />
|}</div>Kushalhttps://fedoraproject.org/w/index.php?title=Changes/Automated_AMI_test_and_release&diff=483619Changes/Automated AMI test and release2017-01-10T13:27:52Z<p>Kushal: ChangeReadyForWrangler</p>
<hr />
<div><!-- Self Contained or System Wide Change Proposal?<br />
Use this guide to determine to which category your proposed change belongs to.<br />
<br />
Self Contained Changes are:<br />
* changes to isolated/leaf package without the impact on other packages/rest of the distribution<br />
* limited scope changes without the impact on other packages/rest of the distribution<br />
* coordinated effort within SIG with limited impact outside SIG functional area, accepted by the SIG<br />
<br />
System Wide Changes are:<br />
* changes that does not fit Self Contained Changes category touching <br />
* changes that require coordination within the distribution (for example mass rebuilds, release engineering or other teams effort etc.)<br />
* changing system defaults<br />
<br />
For Self Contained Changes, sections marked as "REQUIRED FOR SYSTEM WIDE CHANGES" are OPTIONAL but FESCo/Wrangler can request more details (especially in case the change proposal category is <br />
improper or updated to System Wide category). For System Wide Changes all fields on this form are required for FESCo acceptance (when applies). <br />
<br />
We request that you maintain the same order of sections so that all of the change proposal pages are uniform.<br />
--><br />
<br />
<!-- The actual name of your proposed change page should look something like: Changes/Your_Change_Proposal_Name. This keeps all change proposals in the same namespace --><br />
<br />
<!-- The actual name of your proposed change page should look something like: Changes/Your_Change_Proposal_Name. This keeps all change proposals in the same namespace --><br />
= Automated AMI test and release <!-- The name of your change proposal --> =<br />
<br />
== Summary ==<br />
<!-- A sentence or two summarizing what this change is and what it will do. This information is used for the overall changeset summary page for each release. --><br />
We will test the AMI image we build on one single region using the same tests used in Vagrant/local Autocloud testing, and if the tests pass, then only the AMI will be uploaded to all the regions and released.<br />
<br />
== Owner ==<br />
<!-- <br />
For change proposals to qualify as self-contained, owners of all affected packages need to be included here. Alternatively, a SIG can be listed as an owner if it owns all affected packages. <br />
This should link to your home wiki page so we know who you are. <br />
--><br />
* Name: [[User:Kushal| Kushal Das]]<br />
<!-- Include you email address that you can be reached should people want to contact you about helping with your change, status is requested, or technical issues need to be resolved. If the change proposal is owned by a SIG, please also add a primary contact person. --><br />
* Email: <mail@kushaldas.in><br />
* Name: [[User:Sayanchowdhury,| Sayan Chowdhury]]<br />
* Email: <sayan.chowdhury2012@gmail.com,><br />
<br />
* Release notes owner: <!--- To be assigned by docs team [[User:FASAccountName| Release notes owner name]] <email address> --><br />
<!--- UNCOMMENT only for Changes with assigned Shepherd (by FESCo)<br />
* FESCo shepherd: [[User:FASAccountName| Shehperd name]] <email address><br />
--><br />
<!--- UNCOMMENT only if this Change aims specific product, working group (Cloud, Workstation, Server, Base, Env & Stacks)<br />
* Product:<br />
* Responsible WG:<br />
--><br />
<br />
== Current status ==<br />
* Targeted release: [[Releases/26 | Fedora 26 ]] <br />
* Last updated: <!-- this is an automatic macro — you don't need to change this line --> {{REVISIONYEAR}}-{{REVISIONMONTH}}-{{REVISIONDAY2}} <br />
<!-- After the change proposal is accepted by FESCo, tracking bug is created in Bugzilla and linked to this page <br />
Bugzilla states meaning as usual:<br />
NEW -> change proposal is submitted and announced<br />
ASSIGNED -> accepted by FESCo with on going development<br />
MODIFIED -> change is substantially done and testable<br />
ON_QA -> change is code completed and could be tested in the Beta release (optionally by QA)<br />
CLOSED as NEXTRELEASE -> change is completed and verified and will be delivered in next release under development<br />
--><br />
* Tracker bug: <will be assigned by the Wrangler><br />
<br />
== Detailed Description ==<br />
<br />
Currenly fedming tool creates and uploads the AMI images to AWS, in all the regions. It only tests the output /usr/bin/true command to determine if an image is right or not.<br />
<br />
The proposed change will split the process in the two parts. fedimg will first upload the image to only one region and emit a fedmsg message. Autocloud listening to these message will start testing the image using the same tests it uses for Vagrant/Atomic qcow2. Autocloud will upload the test details to ResultsDB. Fedimg will listen to ResultsDB fedmsg messages for the results of the test and if all the tests passes then then fedimg would copy the images to other regions as well.<br />
<br />
== Benefit to Fedora ==<br />
<br />
Fedora AMI images will get the same level of testing like rest of the Atomic/Cloud images. Currently, qcow2 images for OpenStack are tested automatically, and while the same bits go to EC2, we have to validate the EC2 images manually (or trust that everything is close enough, which is not a good assumption). The automation will bring us to the same level of testing for AMIs as the rest of the images already get.<br />
<br />
<br />
<!-- What is the benefit to the platform? If this is a major capability update, what has changed? If this is a new functionality, what capabilities does it bring? Why will Fedora become a better distribution or project because of this proposal?--><br />
<br />
== Scope ==<br />
* Proposal owners: kushal, sayanchowdhury<br />
<!-- What work do the feature owners have to accomplish to complete the feature in time for release? Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?--><br />
<br />
* Other developers: N/A (not a System Wide Change) <!-- REQUIRED FOR SYSTEM WIDE CHANGES --><br />
<!-- What work do other developers have to accomplish to complete the feature in time for release? Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?--><br />
<br />
* Release engineering: N/A (not a System Wide Change) <!-- REQUIRED FOR SYSTEM WIDE CHANGES --><br />
<!-- Does this feature require coordination with release engineering (e.g. changes to installer image generation or update package delivery)? Is a mass rebuid required? If a rel-eng ticket exists, add a link here. <br />
Please work with releng prior to feature submission, and ensure that someone is on board to do any process development work and testing; don't just assume that a bullet point in a change puts someone else on the hook.--><br />
** [[Fedora_Program_Management/ReleaseBlocking/Fedora{{FedoraVersionNumber|next}}|List of deliverables]]: N/A (not a System Wide Change) <!-- REQUIRED FOR SYSTEM WIDE CHANGES --><br />
<!-- Please check the list of Fedora release deliverables and list all the differences the feature brings --><br />
<br />
* Policies and guidelines: N/A (not a System Wide Change) <!-- REQUIRED FOR SYSTEM WIDE CHANGES --><br />
<!-- Do the packaging guidelines or other documents need to be updated for this feature? If so, does it need to happen before or after the implementation is done? If a FPC ticket exists, add a link here. --><br />
<br />
* Trademark approval: N/A (not needed for this Change)<br />
<!-- If your Change may require trademark approval (for example, if it is a new Spin), file a ticket ( https://fedorahosted.org/council/ ) requesting trademark approval from the Fedora Council. This approval will be done via the Council's consensus-based process. --><br />
<br />
== Upgrade/compatibility impact ==<br />
<!-- What happens to systems that have had a previous versions of Fedora installed and are updated to the version containing this change? Will anything require manual configuration or data migration? Will any existing functionality be no longer supported? --><br />
<br />
<!-- REQUIRED FOR SYSTEM WIDE CHANGES --><br />
N/A (not a System Wide Change) <br />
<br />
== How To Test ==<br />
<!-- This does not need to be a full-fledged document. Describe the dimensions of tests that this change implementation is expected to pass when it is done. If it needs to be tested with different hardware or software configurations, indicate them. The more specific you can be, the better the community testing can be. <br />
<br />
Remember that you are writing this how to for interested testers to use to check out your change implementation - documenting what you do for testing is OK, but it's much better to document what *I* can do to test your change.<br />
<br />
A good "how to test" should answer these four questions:<br />
<br />
0. What special hardware / data / etc. is needed (if any)?<br />
1. How do I prepare my system to test this change? What packages<br />
need to be installed, config files edited, etc.?<br />
2. What specific actions do I perform to check that the change is<br />
working like it's supposed to?<br />
3. What are the expected results of those actions?<br />
--><br />
<br />
<!-- REQUIRED FOR SYSTEM WIDE CHANGES --><br />
N/A (not a System Wide Change) <br />
<br />
== User Experience ==<br />
<!-- If this change proposal is noticeable by its target audience, how will their experiences change as a result? Describe what they will see or notice. --><br />
<!-- REQUIRED FOR SYSTEM WIDE CHANGES --><br />
N/A (not a System Wide Change) <br />
<br />
== Dependencies ==<br />
<!-- What other packages (RPMs) depend on this package? Are there changes outside the developers' control on which completion of this change depends? In other words, completion of another change owned by someone else and might cause you to not be able to finish on time or that you would need to coordinate? Other upstream projects like the kernel (if this is not a kernel change)? --><br />
<br />
<!-- REQUIRED FOR SYSTEM WIDE CHANGES --><br />
N/A (not a System Wide Change) <br />
<br />
== Contingency Plan ==<br />
<br />
<!-- If you cannot complete your feature by the final development freeze, what is the backup plan? This might be as simple as "Revert the shipped configuration". Or it might not (e.g. rebuilding a number of dependent packages). If you feature is not completed in time we want to assure others that other parts of Fedora will not be in jeopardy. --><br />
* Contingency mechanism: (What to do? Who will do it?) N/A (not a System Wide Change) <!-- REQUIRED FOR SYSTEM WIDE CHANGES --><br />
<!-- When is the last time the contingency mechanism can be put in place? This will typically be the beta freeze. --><br />
* Contingency deadline: N/A (not a System Wide Change) <!-- REQUIRED FOR SYSTEM WIDE CHANGES --><br />
<!-- Does finishing this feature block the release, or can we ship with the feature in incomplete state? --><br />
* Blocks release? N/A (not a System Wide Change), Yes/No <!-- REQUIRED FOR SYSTEM WIDE CHANGES --><br />
* Blocks product? product <!-- Applicable for Changes that blocks specific product release/Fedora.next --><br />
<br />
== Documentation ==<br />
<!-- Is there upstream documentation on this change, or notes you have written yourself? Link to that material here so other interested developers can get involved. --><br />
<br />
<!-- REQUIRED FOR SYSTEM WIDE CHANGES --><br />
N/A (not a System Wide Change) <br />
<br />
== Release Notes ==<br />
<!-- The Fedora Release Notes inform end-users about what is new in the release. Examples of past release notes are here: http://docs.fedoraproject.org/release-notes/ --><br />
<!-- The release notes also help users know how to deal with platform changes such as ABIs/APIs, configuration or data file formats, or upgrade concerns. If there are any such changes involved in this change, indicate them here. A link to upstream documentation will often satisfy this need. This information forms the basis of the release notes edited by the documentation team and shipped with the release. <br />
<br />
Release Notes are not required for initial draft of the Change Proposal but has to be completed by the Change Freeze. <br />
--><br />
<br />
[[Category:ChangeReadyForWrangler]]<br />
<!-- When your change proposal page is completed and ready for review and announcement --><br />
<!-- remove Category:ChangePageIncomplete and change it to Category:ChangeReadyForWrangler --><br />
<!-- The Wrangler announces the Change to the devel-announce list and changes the category to Category:ChangeAnnounced (no action required) --> <br />
<!-- After review, the Wrangler will move your page to Category:ChangeReadyForFesco... if it still needs more work it will move back to Category:ChangePageIncomplete--><br />
<br />
<!-- Select proper category, default is Self Contained Change --><br />
[[Category:SelfContainedChange]]<br />
<!-- [[Category:SystemWideChange]] --></div>Kushalhttps://fedoraproject.org/w/index.php?title=Changes/Automated_AMI_test_and_release&diff=483618Changes/Automated AMI test and release2017-01-10T13:26:36Z<p>Kushal: /* Scope */ adding proposal owners</p>
<hr />
<div>{{admon/important | Comments and Explanations | The page source contains comments providing guidance to fill out each section. They are invisible when viewing this page. To read it, choose the "view source" link.<br/> '''Copy the source to a ''new page'' before making changes! DO NOT EDIT THIS TEMPLATE FOR YOUR CHANGE PROPOSAL.'''}}<br />
<br />
<!-- Self Contained or System Wide Change Proposal?<br />
Use this guide to determine to which category your proposed change belongs to.<br />
<br />
Self Contained Changes are:<br />
* changes to isolated/leaf package without the impact on other packages/rest of the distribution<br />
* limited scope changes without the impact on other packages/rest of the distribution<br />
* coordinated effort within SIG with limited impact outside SIG functional area, accepted by the SIG<br />
<br />
System Wide Changes are:<br />
* changes that does not fit Self Contained Changes category touching <br />
* changes that require coordination within the distribution (for example mass rebuilds, release engineering or other teams effort etc.)<br />
* changing system defaults<br />
<br />
For Self Contained Changes, sections marked as "REQUIRED FOR SYSTEM WIDE CHANGES" are OPTIONAL but FESCo/Wrangler can request more details (especially in case the change proposal category is <br />
improper or updated to System Wide category). For System Wide Changes all fields on this form are required for FESCo acceptance (when applies). <br />
<br />
We request that you maintain the same order of sections so that all of the change proposal pages are uniform.<br />
--><br />
<br />
<!-- The actual name of your proposed change page should look something like: Changes/Your_Change_Proposal_Name. This keeps all change proposals in the same namespace --><br />
<br />
<!-- The actual name of your proposed change page should look something like: Changes/Your_Change_Proposal_Name. This keeps all change proposals in the same namespace --><br />
= Automated AMI test and release <!-- The name of your change proposal --> =<br />
<br />
== Summary ==<br />
<!-- A sentence or two summarizing what this change is and what it will do. This information is used for the overall changeset summary page for each release. --><br />
We will test the AMI image we build on one single region using the same tests used in Vagrant/local Autocloud testing, and if the tests pass, then only the AMI will be uploaded to all the regions and released.<br />
<br />
== Owner ==<br />
<!-- <br />
For change proposals to qualify as self-contained, owners of all affected packages need to be included here. Alternatively, a SIG can be listed as an owner if it owns all affected packages. <br />
This should link to your home wiki page so we know who you are. <br />
--><br />
* Name: [[User:Kushal| Kushal Das]]<br />
<!-- Include you email address that you can be reached should people want to contact you about helping with your change, status is requested, or technical issues need to be resolved. If the change proposal is owned by a SIG, please also add a primary contact person. --><br />
* Email: <mail@kushaldas.in><br />
* Name: [[User:Sayanchowdhury,| Sayan Chowdhury]]<br />
* Email: <sayan.chowdhury2012@gmail.com,><br />
<br />
* Release notes owner: <!--- To be assigned by docs team [[User:FASAccountName| Release notes owner name]] <email address> --><br />
<!--- UNCOMMENT only for Changes with assigned Shepherd (by FESCo)<br />
* FESCo shepherd: [[User:FASAccountName| Shehperd name]] <email address><br />
--><br />
<!--- UNCOMMENT only if this Change aims specific product, working group (Cloud, Workstation, Server, Base, Env & Stacks)<br />
* Product:<br />
* Responsible WG:<br />
--><br />
<br />
== Current status ==<br />
* Targeted release: [[Releases/26 | Fedora 26 ]] <br />
* Last updated: <!-- this is an automatic macro — you don't need to change this line --> {{REVISIONYEAR}}-{{REVISIONMONTH}}-{{REVISIONDAY2}} <br />
<!-- After the change proposal is accepted by FESCo, tracking bug is created in Bugzilla and linked to this page <br />
Bugzilla states meaning as usual:<br />
NEW -> change proposal is submitted and announced<br />
ASSIGNED -> accepted by FESCo with on going development<br />
MODIFIED -> change is substantially done and testable<br />
ON_QA -> change is code completed and could be tested in the Beta release (optionally by QA)<br />
CLOSED as NEXTRELEASE -> change is completed and verified and will be delivered in next release under development<br />
--><br />
* Tracker bug: <will be assigned by the Wrangler><br />
<br />
== Detailed Description ==<br />
<br />
Currenly fedming tool creates and uploads the AMI images to AWS, in all the regions. It only tests the output /usr/bin/true command to determine if an image is right or not.<br />
<br />
The proposed change will split the process in the two parts. fedimg will first upload the image to only one region and emit a fedmsg message. Autocloud listening to these message will start testing the image using the same tests it uses for Vagrant/Atomic qcow2. Autocloud will upload the test details to ResultsDB. Fedimg will listen to ResultsDB fedmsg messages for the results of the test and if all the tests passes then then fedimg would copy the images to other regions as well.<br />
<br />
== Benefit to Fedora ==<br />
<br />
Fedora AMI images will get the same level of testing like rest of the Atomic/Cloud images. Currently, qcow2 images for OpenStack are tested automatically, and while the same bits go to EC2, we have to validate the EC2 images manually (or trust that everything is close enough, which is not a good assumption). The automation will bring us to the same level of testing for AMIs as the rest of the images already get.<br />
<br />
<br />
<!-- What is the benefit to the platform? If this is a major capability update, what has changed? If this is a new functionality, what capabilities does it bring? Why will Fedora become a better distribution or project because of this proposal?--><br />
<br />
== Scope ==<br />
* Proposal owners: kushal, sayanchowdhury<br />
<!-- What work do the feature owners have to accomplish to complete the feature in time for release? Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?--><br />
<br />
* Other developers: N/A (not a System Wide Change) <!-- REQUIRED FOR SYSTEM WIDE CHANGES --><br />
<!-- What work do other developers have to accomplish to complete the feature in time for release? Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?--><br />
<br />
* Release engineering: N/A (not a System Wide Change) <!-- REQUIRED FOR SYSTEM WIDE CHANGES --><br />
<!-- Does this feature require coordination with release engineering (e.g. changes to installer image generation or update package delivery)? Is a mass rebuid required? If a rel-eng ticket exists, add a link here. <br />
Please work with releng prior to feature submission, and ensure that someone is on board to do any process development work and testing; don't just assume that a bullet point in a change puts someone else on the hook.--><br />
** [[Fedora_Program_Management/ReleaseBlocking/Fedora{{FedoraVersionNumber|next}}|List of deliverables]]: N/A (not a System Wide Change) <!-- REQUIRED FOR SYSTEM WIDE CHANGES --><br />
<!-- Please check the list of Fedora release deliverables and list all the differences the feature brings --><br />
<br />
* Policies and guidelines: N/A (not a System Wide Change) <!-- REQUIRED FOR SYSTEM WIDE CHANGES --><br />
<!-- Do the packaging guidelines or other documents need to be updated for this feature? If so, does it need to happen before or after the implementation is done? If a FPC ticket exists, add a link here. --><br />
<br />
* Trademark approval: N/A (not needed for this Change)<br />
<!-- If your Change may require trademark approval (for example, if it is a new Spin), file a ticket ( https://fedorahosted.org/council/ ) requesting trademark approval from the Fedora Council. This approval will be done via the Council's consensus-based process. --><br />
<br />
== Upgrade/compatibility impact ==<br />
<!-- What happens to systems that have had a previous versions of Fedora installed and are updated to the version containing this change? Will anything require manual configuration or data migration? Will any existing functionality be no longer supported? --><br />
<br />
<!-- REQUIRED FOR SYSTEM WIDE CHANGES --><br />
N/A (not a System Wide Change) <br />
<br />
== How To Test ==<br />
<!-- This does not need to be a full-fledged document. Describe the dimensions of tests that this change implementation is expected to pass when it is done. If it needs to be tested with different hardware or software configurations, indicate them. The more specific you can be, the better the community testing can be. <br />
<br />
Remember that you are writing this how to for interested testers to use to check out your change implementation - documenting what you do for testing is OK, but it's much better to document what *I* can do to test your change.<br />
<br />
A good "how to test" should answer these four questions:<br />
<br />
0. What special hardware / data / etc. is needed (if any)?<br />
1. How do I prepare my system to test this change? What packages<br />
need to be installed, config files edited, etc.?<br />
2. What specific actions do I perform to check that the change is<br />
working like it's supposed to?<br />
3. What are the expected results of those actions?<br />
--><br />
<br />
<!-- REQUIRED FOR SYSTEM WIDE CHANGES --><br />
N/A (not a System Wide Change) <br />
<br />
== User Experience ==<br />
<!-- If this change proposal is noticeable by its target audience, how will their experiences change as a result? Describe what they will see or notice. --><br />
<!-- REQUIRED FOR SYSTEM WIDE CHANGES --><br />
N/A (not a System Wide Change) <br />
<br />
== Dependencies ==<br />
<!-- What other packages (RPMs) depend on this package? Are there changes outside the developers' control on which completion of this change depends? In other words, completion of another change owned by someone else and might cause you to not be able to finish on time or that you would need to coordinate? Other upstream projects like the kernel (if this is not a kernel change)? --><br />
<br />
<!-- REQUIRED FOR SYSTEM WIDE CHANGES --><br />
N/A (not a System Wide Change) <br />
<br />
== Contingency Plan ==<br />
<br />
<!-- If you cannot complete your feature by the final development freeze, what is the backup plan? This might be as simple as "Revert the shipped configuration". Or it might not (e.g. rebuilding a number of dependent packages). If you feature is not completed in time we want to assure others that other parts of Fedora will not be in jeopardy. --><br />
* Contingency mechanism: (What to do? Who will do it?) N/A (not a System Wide Change) <!-- REQUIRED FOR SYSTEM WIDE CHANGES --><br />
<!-- When is the last time the contingency mechanism can be put in place? This will typically be the beta freeze. --><br />
* Contingency deadline: N/A (not a System Wide Change) <!-- REQUIRED FOR SYSTEM WIDE CHANGES --><br />
<!-- Does finishing this feature block the release, or can we ship with the feature in incomplete state? --><br />
* Blocks release? N/A (not a System Wide Change), Yes/No <!-- REQUIRED FOR SYSTEM WIDE CHANGES --><br />
* Blocks product? product <!-- Applicable for Changes that blocks specific product release/Fedora.next --><br />
<br />
== Documentation ==<br />
<!-- Is there upstream documentation on this change, or notes you have written yourself? Link to that material here so other interested developers can get involved. --><br />
<br />
<!-- REQUIRED FOR SYSTEM WIDE CHANGES --><br />
N/A (not a System Wide Change) <br />
<br />
== Release Notes ==<br />
<!-- The Fedora Release Notes inform end-users about what is new in the release. Examples of past release notes are here: http://docs.fedoraproject.org/release-notes/ --><br />
<!-- The release notes also help users know how to deal with platform changes such as ABIs/APIs, configuration or data file formats, or upgrade concerns. If there are any such changes involved in this change, indicate them here. A link to upstream documentation will often satisfy this need. This information forms the basis of the release notes edited by the documentation team and shipped with the release. <br />
<br />
Release Notes are not required for initial draft of the Change Proposal but has to be completed by the Change Freeze. <br />
--><br />
<br />
[[Category:ChangePageIncomplete]]<br />
<!-- When your change proposal page is completed and ready for review and announcement --><br />
<!-- remove Category:ChangePageIncomplete and change it to Category:ChangeReadyForWrangler --><br />
<!-- The Wrangler announces the Change to the devel-announce list and changes the category to Category:ChangeAnnounced (no action required) --> <br />
<!-- After review, the Wrangler will move your page to Category:ChangeReadyForFesco... if it still needs more work it will move back to Category:ChangePageIncomplete--><br />
<br />
<!-- Select proper category, default is Self Contained Change --><br />
[[Category:SelfContainedChange]]<br />
<!-- [[Category:SystemWideChange]] --></div>Kushalhttps://fedoraproject.org/w/index.php?title=Changes/Automated_AMI_test_and_release&diff=483614Changes/Automated AMI test and release2017-01-10T13:09:15Z<p>Kushal: First version</p>
<hr />
<div>{{admon/important | Comments and Explanations | The page source contains comments providing guidance to fill out each section. They are invisible when viewing this page. To read it, choose the "view source" link.<br/> '''Copy the source to a ''new page'' before making changes! DO NOT EDIT THIS TEMPLATE FOR YOUR CHANGE PROPOSAL.'''}}<br />
<br />
<!-- Self Contained or System Wide Change Proposal?<br />
Use this guide to determine to which category your proposed change belongs to.<br />
<br />
Self Contained Changes are:<br />
* changes to isolated/leaf package without the impact on other packages/rest of the distribution<br />
* limited scope changes without the impact on other packages/rest of the distribution<br />
* coordinated effort within SIG with limited impact outside SIG functional area, accepted by the SIG<br />
<br />
System Wide Changes are:<br />
* changes that does not fit Self Contained Changes category touching <br />
* changes that require coordination within the distribution (for example mass rebuilds, release engineering or other teams effort etc.)<br />
* changing system defaults<br />
<br />
For Self Contained Changes, sections marked as "REQUIRED FOR SYSTEM WIDE CHANGES" are OPTIONAL but FESCo/Wrangler can request more details (especially in case the change proposal category is <br />
improper or updated to System Wide category). For System Wide Changes all fields on this form are required for FESCo acceptance (when applies). <br />
<br />
We request that you maintain the same order of sections so that all of the change proposal pages are uniform.<br />
--><br />
<br />
<!-- The actual name of your proposed change page should look something like: Changes/Your_Change_Proposal_Name. This keeps all change proposals in the same namespace --><br />
<br />
<!-- The actual name of your proposed change page should look something like: Changes/Your_Change_Proposal_Name. This keeps all change proposals in the same namespace --><br />
= Automated AMI test and release <!-- The name of your change proposal --> =<br />
<br />
== Summary ==<br />
<!-- A sentence or two summarizing what this change is and what it will do. This information is used for the overall changeset summary page for each release. --><br />
We will test the AMI image we build on one single region using the same tests used in Vagrant/local Autocloud testing, and if the tests pass, then only the AMI will be uploaded to all the regions and released.<br />
<br />
== Owner ==<br />
<!-- <br />
For change proposals to qualify as self-contained, owners of all affected packages need to be included here. Alternatively, a SIG can be listed as an owner if it owns all affected packages. <br />
This should link to your home wiki page so we know who you are. <br />
--><br />
* Name: [[User:Kushal| Kushal Das]]<br />
<!-- Include you email address that you can be reached should people want to contact you about helping with your change, status is requested, or technical issues need to be resolved. If the change proposal is owned by a SIG, please also add a primary contact person. --><br />
* Email: <mail@kushaldas.in><br />
* Name: [[User:Sayanchowdhury,| Sayan Chowdhury]]<br />
* Email: <sayan.chowdhury2012@gmail.com,><br />
<br />
* Release notes owner: <!--- To be assigned by docs team [[User:FASAccountName| Release notes owner name]] <email address> --><br />
<!--- UNCOMMENT only for Changes with assigned Shepherd (by FESCo)<br />
* FESCo shepherd: [[User:FASAccountName| Shehperd name]] <email address><br />
--><br />
<!--- UNCOMMENT only if this Change aims specific product, working group (Cloud, Workstation, Server, Base, Env & Stacks)<br />
* Product:<br />
* Responsible WG:<br />
--><br />
<br />
== Current status ==<br />
* Targeted release: [[Releases/26 | Fedora 26 ]] <br />
* Last updated: <!-- this is an automatic macro — you don't need to change this line --> {{REVISIONYEAR}}-{{REVISIONMONTH}}-{{REVISIONDAY2}} <br />
<!-- After the change proposal is accepted by FESCo, tracking bug is created in Bugzilla and linked to this page <br />
Bugzilla states meaning as usual:<br />
NEW -> change proposal is submitted and announced<br />
ASSIGNED -> accepted by FESCo with on going development<br />
MODIFIED -> change is substantially done and testable<br />
ON_QA -> change is code completed and could be tested in the Beta release (optionally by QA)<br />
CLOSED as NEXTRELEASE -> change is completed and verified and will be delivered in next release under development<br />
--><br />
* Tracker bug: <will be assigned by the Wrangler><br />
<br />
== Detailed Description ==<br />
<br />
Currenly fedming tool creates and uploads the AMI images to AWS, in all the regions. It only tests the output /usr/bin/true command to determine if an image is right or not.<br />
<br />
The proposed change will slip the process in the two parts. fedimg will first upload the image to only one region and emit a fedmsg message. Autocloud listening to these message will start testing the image using the same tests it uses for Vagrant/Atomic qcow2. Autocloud will upload the test details to ResultsDB. Fedimg will listen to ResultsDB fedmsg messages for the results of the test and if all the tests passes then then fedimg would copy the images to other regions as well.<br />
<br />
== Benefit to Fedora ==<br />
<br />
Fedora AMI images will get the same level of testing like rest of the Atomic/Cloud images. Currently, we have to manually test the images for everything. The automation will help us to be in the same level of the rest of the images.<br />
<br />
<br />
<!-- What is the benefit to the platform? If this is a major capability update, what has changed? If this is a new functionality, what capabilities does it bring? Why will Fedora become a better distribution or project because of this proposal?--><br />
<br />
== Scope ==<br />
* Proposal owners:<br />
<!-- What work do the feature owners have to accomplish to complete the feature in time for release? Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?--><br />
<br />
* Other developers: N/A (not a System Wide Change) <!-- REQUIRED FOR SYSTEM WIDE CHANGES --><br />
<!-- What work do other developers have to accomplish to complete the feature in time for release? Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?--><br />
<br />
* Release engineering: N/A (not a System Wide Change) <!-- REQUIRED FOR SYSTEM WIDE CHANGES --><br />
<!-- Does this feature require coordination with release engineering (e.g. changes to installer image generation or update package delivery)? Is a mass rebuid required? If a rel-eng ticket exists, add a link here. <br />
Please work with releng prior to feature submission, and ensure that someone is on board to do any process development work and testing; don't just assume that a bullet point in a change puts someone else on the hook.--><br />
** [[Fedora_Program_Management/ReleaseBlocking/Fedora{{FedoraVersionNumber|next}}|List of deliverables]]: N/A (not a System Wide Change) <!-- REQUIRED FOR SYSTEM WIDE CHANGES --><br />
<!-- Please check the list of Fedora release deliverables and list all the differences the feature brings --><br />
<br />
* Policies and guidelines: N/A (not a System Wide Change) <!-- REQUIRED FOR SYSTEM WIDE CHANGES --><br />
<!-- Do the packaging guidelines or other documents need to be updated for this feature? If so, does it need to happen before or after the implementation is done? If a FPC ticket exists, add a link here. --><br />
<br />
* Trademark approval: N/A (not needed for this Change)<br />
<!-- If your Change may require trademark approval (for example, if it is a new Spin), file a ticket ( https://fedorahosted.org/council/ ) requesting trademark approval from the Fedora Council. This approval will be done via the Council's consensus-based process. --><br />
<br />
== Upgrade/compatibility impact ==<br />
<!-- What happens to systems that have had a previous versions of Fedora installed and are updated to the version containing this change? Will anything require manual configuration or data migration? Will any existing functionality be no longer supported? --><br />
<br />
<!-- REQUIRED FOR SYSTEM WIDE CHANGES --><br />
N/A (not a System Wide Change) <br />
<br />
== How To Test ==<br />
<!-- This does not need to be a full-fledged document. Describe the dimensions of tests that this change implementation is expected to pass when it is done. If it needs to be tested with different hardware or software configurations, indicate them. The more specific you can be, the better the community testing can be. <br />
<br />
Remember that you are writing this how to for interested testers to use to check out your change implementation - documenting what you do for testing is OK, but it's much better to document what *I* can do to test your change.<br />
<br />
A good "how to test" should answer these four questions:<br />
<br />
0. What special hardware / data / etc. is needed (if any)?<br />
1. How do I prepare my system to test this change? What packages<br />
need to be installed, config files edited, etc.?<br />
2. What specific actions do I perform to check that the change is<br />
working like it's supposed to?<br />
3. What are the expected results of those actions?<br />
--><br />
<br />
<!-- REQUIRED FOR SYSTEM WIDE CHANGES --><br />
N/A (not a System Wide Change) <br />
<br />
== User Experience ==<br />
<!-- If this change proposal is noticeable by its target audience, how will their experiences change as a result? Describe what they will see or notice. --><br />
<!-- REQUIRED FOR SYSTEM WIDE CHANGES --><br />
N/A (not a System Wide Change) <br />
<br />
== Dependencies ==<br />
<!-- What other packages (RPMs) depend on this package? Are there changes outside the developers' control on which completion of this change depends? In other words, completion of another change owned by someone else and might cause you to not be able to finish on time or that you would need to coordinate? Other upstream projects like the kernel (if this is not a kernel change)? --><br />
<br />
<!-- REQUIRED FOR SYSTEM WIDE CHANGES --><br />
N/A (not a System Wide Change) <br />
<br />
== Contingency Plan ==<br />
<br />
<!-- If you cannot complete your feature by the final development freeze, what is the backup plan? This might be as simple as "Revert the shipped configuration". Or it might not (e.g. rebuilding a number of dependent packages). If you feature is not completed in time we want to assure others that other parts of Fedora will not be in jeopardy. --><br />
* Contingency mechanism: (What to do? Who will do it?) N/A (not a System Wide Change) <!-- REQUIRED FOR SYSTEM WIDE CHANGES --><br />
<!-- When is the last time the contingency mechanism can be put in place? This will typically be the beta freeze. --><br />
* Contingency deadline: N/A (not a System Wide Change) <!-- REQUIRED FOR SYSTEM WIDE CHANGES --><br />
<!-- Does finishing this feature block the release, or can we ship with the feature in incomplete state? --><br />
* Blocks release? N/A (not a System Wide Change), Yes/No <!-- REQUIRED FOR SYSTEM WIDE CHANGES --><br />
* Blocks product? product <!-- Applicable for Changes that blocks specific product release/Fedora.next --><br />
<br />
== Documentation ==<br />
<!-- Is there upstream documentation on this change, or notes you have written yourself? Link to that material here so other interested developers can get involved. --><br />
<br />
<!-- REQUIRED FOR SYSTEM WIDE CHANGES --><br />
N/A (not a System Wide Change) <br />
<br />
== Release Notes ==<br />
<!-- The Fedora Release Notes inform end-users about what is new in the release. Examples of past release notes are here: http://docs.fedoraproject.org/release-notes/ --><br />
<!-- The release notes also help users know how to deal with platform changes such as ABIs/APIs, configuration or data file formats, or upgrade concerns. If there are any such changes involved in this change, indicate them here. A link to upstream documentation will often satisfy this need. This information forms the basis of the release notes edited by the documentation team and shipped with the release. <br />
<br />
Release Notes are not required for initial draft of the Change Proposal but has to be completed by the Change Freeze. <br />
--><br />
<br />
[[Category:ChangePageIncomplete]]<br />
<!-- When your change proposal page is completed and ready for review and announcement --><br />
<!-- remove Category:ChangePageIncomplete and change it to Category:ChangeReadyForWrangler --><br />
<!-- The Wrangler announces the Change to the devel-announce list and changes the category to Category:ChangeAnnounced (no action required) --> <br />
<!-- After review, the Wrangler will move your page to Category:ChangeReadyForFesco... if it still needs more work it will move back to Category:ChangePageIncomplete--><br />
<br />
<!-- Select proper category, default is Self Contained Change --><br />
[[Category:SelfContainedChange]]<br />
<!-- [[Category:SystemWideChange]] --></div>Kushalhttps://fedoraproject.org/w/index.php?title=Fedora_26_Change_Proposals_Atomic_WG&diff=481220Fedora 26 Change Proposals Atomic WG2016-12-01T06:16:18Z<p>Kushal: /* List of ideas to be proposed as F26 change from the Atomic Working Group */</p>
<hr />
<div>=List of ideas to be proposed as F26 change from the Atomic Working Group=<br />
<br />
Please add any idea you have below. There is an existing thread in the mailing list where you can discuss about your idea. You can also start a new thread for your idea.<br />
<br />
== Idea 1 ==<br />
<br />
Description<br />
<br />
== Idea 2 ==<br />
<br />
Description</div>Kushalhttps://fedoraproject.org/w/index.php?title=Fedora_26_Change_Proposals_Atomic_WG&diff=481218Fedora 26 Change Proposals Atomic WG2016-12-01T06:12:18Z<p>Kushal: Creating for the first time</p>
<hr />
<div>=List of ideas to be proposed as F26 change from the Atomic Working Group=<br />
<br />
Please add any idea you have below. There is an existing thread in the mailing list where you can discuss about your idea. You can also start a new thread for your idea.<br />
<br />
* Idea 1<br />
* Idea 2</div>Kushalhttps://fedoraproject.org/w/index.php?title=Atomic_WG_docs&diff=481213Atomic WG docs2016-12-01T04:13:19Z<p>Kushal: Adding for the first time</p>
<hr />
<div>==Where can I find the docs?==<br />
<br />
They are live [http://fedoracloud.readthedocs.io/en/latest/ here].<br />
<br />
==How can I add a new document?==<br />
<br />
Please create a pull request to our [https://github.com/fedora-cloud/fedoracloud GitHub repository]. We are using Spinx as tool to create these documents.<br />
<br />
==How to get help on the documents, or even writing a new one?==<br />
<br />
Ping us on #fedora-cloud channel in freenode server.</div>Kushalhttps://fedoraproject.org/w/index.php?title=Test_Results:Fedora_25_RC_1.2_Cloud&diff=479471Test Results:Fedora 25 RC 1.2 Cloud2016-11-10T04:49:16Z<p>Kushal: /* x86_64 */ Adding my tests results</p>
<hr />
<div>{{Release_validation_instructions|testtype=Cloud|release=25|milestone=RC|compose=1.2|date=}}<br />
<br />
{{anchor|results}}<br />
== '''Test Matrix''' ==<br />
<br />
<onlyinclude><br />
<br />
{{Template:Cloud Setup}}<br />
<br />
==== '''x86_64''' ====<br />
<br />
{| class="wikitable sortable collapsible" border="1" width=100%<br />
! Milestone !! Test Case !! Local !! EC2 !! Openstack<br />
|-<br />
| Alpha<br />
| [[QA:Testcase_base_startup]]<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|pass|kushal}}<br />
|-<br />
| Alpha<br />
| [[QA:Testcase_base_system_logging]]<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|pass|kushal}}<br />
|-<br />
| Final<br />
| [[QA:Testcase_Services_start]]<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|pass|kushal}}<br />
|-<br />
| Final<br />
| [[QA:Testcase_base_selinux]]<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|pass|kushal}}<br />
|-<br />
| Final<br />
| [[QA:Testcase_base_service_manipulation]]<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|pass|kushal}}<br />
|-<br />
|}<br />
<references/><br />
<br />
==== '''i386''' ====<br />
<br />
{| class="wikitable sortable collapsible" border="1" width=100%<br />
! Milestone !! Test Case !! Local !! EC2 !! Openstack<br />
|-<br />
| Optional<br />
| [[QA:Testcase_base_startup]]<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
|-<br />
| Optional<br />
| [[QA:Testcase_base_system_logging]]<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
|-<br />
| Optional<br />
| [[QA:Testcase_Services_start]]<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
|-<br />
| Optional<br />
| [[QA:Testcase_base_selinux]]<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
|-<br />
| Optional<br />
| [[QA:Testcase_base_service_manipulation]]<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
|-<br />
|}<br />
<references/><br />
<br />
==== '''Atomic''' ====<br />
<br />
{| class="wikitable sortable collapsible" border="1" width=100%<br />
! Milestone !! Test Case !! Local !! EC2 !! Openstack<br />
|-<br />
| Optional<br />
| [[QA:Testcase_base_startup]]<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
|-<br />
| Optional<br />
| [[QA:Testcase_base_system_logging]]<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
|-<br />
| Optional<br />
| [[QA:Testcase_Services_start]]<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
|-<br />
| Optional<br />
| [[QA:Testcase_base_selinux]]<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
|-<br />
| Optional<br />
| [[QA:Testcase_base_service_manipulation]]<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
|-<br />
|}<br />
<references/></onlyinclude><br />
<br />
[[Category:Cloud_validation_testing]]<br />
{{#if:|[[Category:Fedora_25_Nightly_Test_Results|Cloud]]|[[Category:Fedora_25_RC_Test_Results|Cloud]]}}</div>Kushalhttps://fedoraproject.org/w/index.php?title=Test_Day:2016-10-24_Cloud&diff=477877Test Day:2016-10-24 Cloud2016-10-24T16:11:54Z<p>Kushal: /* How to test? */ adding known issue</p>
<hr />
<div>{{Infobox_group<br />
| name = Fedora Test Day<br />
| image = [[File:Echo-testing-48px.png|link=QA/Test Days]]<br />
| caption = [[Fedora Cloud Test day]]<br />
| date = 2016-10-24<br />
| time = all day<br />
| website = [[QA/Test Days]]<br />
| irc = [irc://irc.freenode.net/#fedora-test-day #fedora-test-day] ([http://webchat.freenode.net/?channels=fedora-test-day webirc])<br />
| fedora_mailing_list = test<br />
}}<br />
<br />
{{admon/note | Can't make the date? | If you come to this page before or after the test day is completed, your testing is still valuable, and you can use the information on this page to test, file any bugs you find at [http://bugzilla.redhat.com Bugzilla], and add your results to the results section. If this page is more than a month old when you arrive here, please check the [[QA/Test_Days|current schedule]] and see if a similar but more recent Test Day is planned or has already happened.}}<br />
<br />
== What to test? ==<br />
<br />
Today's installment of Fedora Test Day will focus on '''Cloud, Atomic Host''' images for Fedora 25.<br />
<br />
== Who's available ==<br />
<br />
The following cast of characters will be available testing, workarounds, bug fixes, and general discussion ...<br />
* Development - <br />
* Quality Assurance -<br />
* Community Members - dustymabe, jasonbrooks, kushal<br />
<br />
== Prerequisite for Test Day == <br />
<br />
You will require at least a system with libvirt/kvm installed. Having access to any Openstack or other Cloud IAAS system where you can upload an image will be even better.<br />
<br />
Download the images from below links<br />
<br />
* [https://kojipkgs.fedoraproject.org/compose/branched/Fedora-25-20161023.n.0/compose/CloudImages/x86_64/images/Fedora-Atomic-25-20161023.n.0.x86_64.qcow2 Atomic Host QCOW2]<br />
* [https://kojipkgs.fedoraproject.org/compose/branched/Fedora-25-20161023.n.0/compose/CloudImages/x86_64/images/Fedora-Atomic-Vagrant-25-20161023.n.0.x86_64.vagrant-virtualbox.box Vagrant Virtualbox Atomic]<br />
* [https://kojipkgs.fedoraproject.org/compose/branched/Fedora-25-20161023.n.0/compose/CloudImages/x86_64/images/Fedora-Atomic-Vagrant-25-20161023.n.0.x86_64.vagrant-libvirt.box Vagrant libvirt Atomic]<br />
<br />
* [https://kojipkgs.fedoraproject.org/compose/branched/Fedora-25-20161023.n.0/compose/CloudImages/x86_64/images/Fedora-Cloud-Base-25-20161023.n.0.x86_64.qcow2 Cloud Base QCOW2]<br />
* [https://kojipkgs.fedoraproject.org/compose/branched/Fedora-25-20161023.n.0/compose/CloudImages/x86_64/images/Fedora-Cloud-Base-Vagrant-25-20161023.n.0.x86_64.vagrant-virtualbox.box Vagrant Virtualbox Cloud Base]<br />
<br />
* [https://kojipkgs.fedoraproject.org/compose/branched/Fedora-25-20161023.n.0/compose/CloudImages/x86_64/images/Fedora-Cloud-Base-Vagrant-25-20161023.n.0.x86_64.vagrant-libvirt.box Vagrant libvirt Cloud Base]<br />
<br />
<br />
List of AMIs<br />
<br />
{|<br />
|-<br />
! Image Name<br />
! AMI id<br />
! Destination<br />
! Virt type <br />
! Vol type<br />
|-<br />
| Fedora-Atomic-25-20161023.n.0.x86_64 || EC2 (us-west-2) || ami-2d4bef4d || hvm || gp2 <br />
|- <br />
| Fedora-Atomic-25-20161023.n.0.x86_64 || EC2 (us-west-2) || ami-7d48ec1d || hvm || standard <br />
|- <br />
| Fedora-Atomic-25-20161023.n.0.x86_64 || EC2 (us-west-1) || ami-c4450ea4 || hvm || standard <br />
|- <br />
| Fedora-Atomic-25-20161023.n.0.x86_64 || EC2 (sa-east-1) || ami-1bd64a77 || hvm || standard <br />
|- <br />
| Fedora-Atomic-25-20161023.n.0.x86_64 || EC2 (eu-west-1) || ami-1b327b68 || hvm || standard <br />
|- <br />
| Fedora-Atomic-25-20161023.n.0.x86_64 || EC2 (eu-central-1) || ami-2645bc49 || hvm || standard <br />
|- <br />
| Fedora-Atomic-25-20161023.n.0.x86_64 || EC2 (ap-southeast-2) || ami-100b3673 || hvm || standard <br />
|- <br />
| Fedora-Atomic-25-20161023.n.0.x86_64 || EC2 (ap-southeast-1) || ami-afe948cc || hvm || standard <br />
|- <br />
| Fedora-Atomic-25-20161023.n.0.x86_64 || EC2 (ap-northeast-1) || ami-5abd1c3b || hvm || standard <br />
|- <br />
| Fedora-Atomic-25-20161023.n.0.x86_64 || EC2 (us-west-1) || ami-6a400b0a || hvm || gp2 <br />
|- <br />
| Fedora-Atomic-25-20161023.n.0.x86_64 || EC2 (sa-east-1) || ami-39d64a55 || hvm || gp2 <br />
|- <br />
| Fedora-Atomic-25-20161023.n.0.x86_64 || EC2 (eu-west-1) || ami-52337a21 || hvm || gp2 <br />
|- <br />
| Fedora-Atomic-25-20161023.n.0.x86_64 || EC2 (eu-central-1) || ami-9d44bdf2 || hvm || gp2 <br />
|- <br />
| Fedora-Atomic-25-20161023.n.0.x86_64 || EC2 (ap-southeast-2) || ami-7a0a3719 || hvm || gp2 <br />
|- <br />
| Fedora-Atomic-25-20161023.n.0.x86_64 || EC2 (ap-southeast-1) || ami-71e94812 || hvm || gp2 <br />
|- <br />
| Fedora-Atomic-25-20161023.n.0.x86_64 || EC2 (ap-northeast-1) || ami-8fba1bee || hvm || gp2 <br />
|- <br />
| Fedora-Atomic-25-20161023.n.0.x86_64 || EC2 (us-east-1) || ami-a7461bb0 || hvm || standard <br />
|- <br />
| Fedora-Atomic-25-20161023.n.0.x86_64 || EC2 (us-east-1) || ami-71471a66 || hvm || gp2 <br />
|-<br />
| Fedora-Cloud-Base-25-20161023.n.0.x86_64 || EC2 (us-west-2) || ami-a74befc7 || paravirtual || gp2<br />
|- <br />
| Fedora-Cloud-Base-25-20161023.n.0.x86_64 || EC2 (us-west-2) || ami-a54befc5 || paravirtual || standard <br />
|-<br />
| Fedora-Cloud-Base-25-20161023.n.0.x86_64 || EC2 (us-west-1) || ami-bc470cdc || paravirtual || standard <br />
|-<br />
| Fedora-Cloud-Base-25-20161023.n.0.x86_64 || EC2 (sa-east-1) || ami-e2da468e || paravirtual || standard <br />
|-<br />
| Fedora-Cloud-Base-25-20161023.n.0.x86_64 || EC2 (eu-west-1) || ami-05337a76 || paravirtual || standard <br />
|-<br />
| Fedora-Cloud-Base-25-20161023.n.0.x86_64 || EC2 (eu-central-1) || ami-2b45bc44 || paravirtual || standard <br />
|-<br />
| Fedora-Cloud-Base-25-20161023.n.0.x86_64 || EC2 (ap-southeast-2) || ami-33053850 || paravirtual || standard <br />
|-<br />
| Fedora-Cloud-Base-25-20161023.n.0.x86_64 || EC2 (ap-southeast-1) || ami-9be746f8 || paravirtual || standard <br />
|-<br />
| Fedora-Cloud-Base-25-20161023.n.0.x86_64 || EC2 (us-west-1) || ami-07460d67 || paravirtual || gp2 <br />
|-<br />
| Fedora-Cloud-Base-25-20161023.n.0.x86_64 || EC2 (sa-east-1) || ami-47d4482b || paravirtual || gp2 <br />
|-<br />
| Fedora-Cloud-Base-25-20161023.n.0.x86_64 || EC2 (eu-west-1) || ami-51347d22 || paravirtual || gp2 <br />
|-<br />
| Fedora-Cloud-Base-25-20161023.n.0.x86_64 || EC2 (eu-central-1) || ami-7db84012 || paravirtual || gp2 <br />
|-<br />
| Fedora-Cloud-Base-25-20161023.n.0.x86_64 || EC2 (ap-southeast-2) || ami-dc0a37bf || paravirtual || gp2 <br />
|-<br />
| Fedora-Cloud-Base-25-20161023.n.0.x86_64 || EC2 (ap-southeast-1) || ami-99e746fa || paravirtual || gp2 <br />
|-<br />
| Fedora-Cloud-Base-25-20161023.n.0.x86_64 || EC2 (ap-northeast-1) || ami-ffbf1e9e || paravirtual || gp2 <br />
|-<br />
| Fedora-Cloud-Base-25-20161023.n.0.x86_64 || EC2 (ap-northeast-1) || ami-37802156 || paravirtual || standard <br />
|-<br />
| Fedora-Cloud-Base-25-20161023.n.0.x86_64 || EC2 (us-east-1) || ami-ed401dfa || paravirtual || gp2 <br />
|-<br />
| Fedora-Cloud-Base-25-20161023.n.0.x86_64 || EC2 (us-east-1) || ami-f1461be6 || paravirtual || standard <br />
|-<br />
| Fedora-Cloud-Base-25-20161023.n.0.x86_64 || EC2 (us-west-2) || ami-194feb79 || hvm || standard <br />
|-<br />
| Fedora-Cloud-Base-25-20161023.n.0.x86_64 || EC2 (sa-east-1) || ami-ce069ba2 || hvm || standard <br />
|-<br />
| Fedora-Cloud-Base-25-20161023.n.0.x86_64 || EC2 (us-west-1) || ami-a1470cc1 || hvm || standard <br />
|-<br />
| Fedora-Cloud-Base-25-20161023.n.0.x86_64 || EC2 (eu-west-1) || ami-91337ae2 || hvm || standard <br />
|-<br />
| Fedora-Cloud-Base-25-20161023.n.0.x86_64 || EC2 (eu-central-1) || ami-fb46bf94 || hvm || standard <br />
|-<br />
| Fedora-Cloud-Base-25-20161023.n.0.x86_64 || EC2 (ap-southeast-2) || ami-130b3670 || hvm || standard <br />
|-<br />
| Fedora-Cloud-Base-25-20161023.n.0.x86_64 || EC2 (ap-southeast-1) || ami-a4e849c7 || hvm || standard <br />
|-<br />
| Fedora-Cloud-Base-25-20161023.n.0.x86_64 || EC2 (us-west-2) || ami-114aee71 || hvm || gp2 <br />
|-<br />
| Fedora-Cloud-Base-25-20161023.n.0.x86_64 || EC2 (ap-northeast-1) || ami-3cbe1f5d || hvm || standard <br />
|-<br />
| Fedora-Cloud-Base-25-20161023.n.0.x86_64 || EC2 (sa-east-1) || ami-cd069ba1 || hvm || gp2 <br />
|- <br />
| Fedora-Cloud-Base-25-20161023.n.0.x86_64 || EC2 (us-west-1) || ami-c6450ea6 || hvm || gp2 <br />
|-<br />
| Fedora-Cloud-Base-25-20161023.n.0.x86_64 || EC2 (eu-west-1) || ami-b1327bc2 || hvm || gp2 <br />
|-<br />
| Fedora-Cloud-Base-25-20161023.n.0.x86_64 || EC2 (eu-central-1) || ami-f546bf9a || hvm || gp2 <br />
|-<br />
| Fedora-Cloud-Base-25-20161023.n.0.x86_64 || EC2 (ap-southeast-2) || ami-1a0b3679 || hvm || gp2 <br />
|-<br />
| Fedora-Cloud-Base-25-20161023.n.0.x86_64 || EC2 (ap-southeast-1) || ami-2ce8494f || hvm || gp2 <br />
|-<br />
| Fedora-Cloud-Base-25-20161023.n.0.x86_64 || EC2 (ap-northeast-1) || ami-64812005 || hvm || gp2 <br />
|-<br />
| Fedora-Cloud-Base-25-20161023.n.0.x86_64 || EC2 (us-east-1) || ami-d04a17c7 || hvm || standard <br />
|-<br />
| Fedora-Cloud-Base-25-20161023.n.0.x86_64 || EC2 (us-east-1) || ami-cf4419d8 || hvm || gp2 <br />
|}<br />
<br />
<br />
Here's a chunk which is commonly used for most Test Days. Replace XX with whatever Fedora release is pending:<br />
<br />
* An updated [https://www.happyassassin.net/nightlies.html Fedora 25 nightly Cloud/Atomic Host image]<br />
<br />
== How to test? ==<br />
<br />
* Boot the images on a cloud system, or on Vagrant or using testcloud on a local system.<br />
* Execute the tests.<br />
<br />
Note: For the service manipulation tests we are stopping/disabling '''chronyd''' service on Fedora 25 systems.<br />
<br />
=== Known Issues ===<br />
<br />
For the Atomic qcow2 image we have a known docker storage issue. Use the following cloud-config to start an instance<br />
in a cloud.<br />
<br />
<code><br />
<br />
#cloud-config<br />
bootcmd:<br />
- sed s/After=cloud-final.service/After=cloud-init-local.service/ /usr/lib/systemd/system/docker-storage-setup.service > /etc/systemd/system/docker-storage-setup.service<br />
- systemctl daemon-reload<br />
- systemctl start --no-block docker.service<br />
</code><br />
<br />
=== Run the tests ===<br />
<br />
Visit the [http://testdays.fedorainfracloud.org/events/15 result page] and click on the column title links to see the tests that need to be run: most column titles are links to a specific test case. Follow the instructions there, then enter your results by clicking the ''Enter result'' button for the test.<br />
<br />
=== Exploratory testing ===<br />
<br />
If you run out of test cases, congratulations! But that's not the end! You can still help out by playing around with the tool in whatever ways you can think of: try out all the things you can find, and try writing different Fedora images with it. If you have systems with different Windows versions, try running the tool on all of them. Get creative! Any problems you find please file a bug, or report to the IRC channel.<br />
<br />
== Reporting bugs ==<br />
<br />
<br />
<br />
If you have problems with any of the tests, report a bug to [https://bugzilla.redhat.com Bugzilla]. If you are unsure about exactly how to file the report or what other information to include, just ask on IRC and we will help you.<br />
<br />
IRC Channel name: #fedora-cloud, #fedora-test-day<br />
Server: Freenode<br />
<br />
== Test Results ==<br />
<br />
Please enter your results on the [http://testdays.fedorainfracloud.org/events/15 result page]. The results will be transferred here after the Test Day is finished.<br />
<br />
<br />
<br />
<br />
<br />
[[Category:Fedora 25 Test Days]]</div>Kushalhttps://fedoraproject.org/w/index.php?title=Test_Day:2016-10-24_Cloud&diff=477876Test Day:2016-10-24 Cloud2016-10-24T16:11:06Z<p>Kushal: /* Who's available */</p>
<hr />
<div>{{Infobox_group<br />
| name = Fedora Test Day<br />
| image = [[File:Echo-testing-48px.png|link=QA/Test Days]]<br />
| caption = [[Fedora Cloud Test day]]<br />
| date = 2016-10-24<br />
| time = all day<br />
| website = [[QA/Test Days]]<br />
| irc = [irc://irc.freenode.net/#fedora-test-day #fedora-test-day] ([http://webchat.freenode.net/?channels=fedora-test-day webirc])<br />
| fedora_mailing_list = test<br />
}}<br />
<br />
{{admon/note | Can't make the date? | If you come to this page before or after the test day is completed, your testing is still valuable, and you can use the information on this page to test, file any bugs you find at [http://bugzilla.redhat.com Bugzilla], and add your results to the results section. If this page is more than a month old when you arrive here, please check the [[QA/Test_Days|current schedule]] and see if a similar but more recent Test Day is planned or has already happened.}}<br />
<br />
== What to test? ==<br />
<br />
Today's installment of Fedora Test Day will focus on '''Cloud, Atomic Host''' images for Fedora 25.<br />
<br />
== Who's available ==<br />
<br />
The following cast of characters will be available testing, workarounds, bug fixes, and general discussion ...<br />
* Development - <br />
* Quality Assurance -<br />
* Community Members - dustymabe, jasonbrooks, kushal<br />
<br />
== Prerequisite for Test Day == <br />
<br />
You will require at least a system with libvirt/kvm installed. Having access to any Openstack or other Cloud IAAS system where you can upload an image will be even better.<br />
<br />
Download the images from below links<br />
<br />
* [https://kojipkgs.fedoraproject.org/compose/branched/Fedora-25-20161023.n.0/compose/CloudImages/x86_64/images/Fedora-Atomic-25-20161023.n.0.x86_64.qcow2 Atomic Host QCOW2]<br />
* [https://kojipkgs.fedoraproject.org/compose/branched/Fedora-25-20161023.n.0/compose/CloudImages/x86_64/images/Fedora-Atomic-Vagrant-25-20161023.n.0.x86_64.vagrant-virtualbox.box Vagrant Virtualbox Atomic]<br />
* [https://kojipkgs.fedoraproject.org/compose/branched/Fedora-25-20161023.n.0/compose/CloudImages/x86_64/images/Fedora-Atomic-Vagrant-25-20161023.n.0.x86_64.vagrant-libvirt.box Vagrant libvirt Atomic]<br />
<br />
* [https://kojipkgs.fedoraproject.org/compose/branched/Fedora-25-20161023.n.0/compose/CloudImages/x86_64/images/Fedora-Cloud-Base-25-20161023.n.0.x86_64.qcow2 Cloud Base QCOW2]<br />
* [https://kojipkgs.fedoraproject.org/compose/branched/Fedora-25-20161023.n.0/compose/CloudImages/x86_64/images/Fedora-Cloud-Base-Vagrant-25-20161023.n.0.x86_64.vagrant-virtualbox.box Vagrant Virtualbox Cloud Base]<br />
<br />
* [https://kojipkgs.fedoraproject.org/compose/branched/Fedora-25-20161023.n.0/compose/CloudImages/x86_64/images/Fedora-Cloud-Base-Vagrant-25-20161023.n.0.x86_64.vagrant-libvirt.box Vagrant libvirt Cloud Base]<br />
<br />
<br />
List of AMIs<br />
<br />
{|<br />
|-<br />
! Image Name<br />
! AMI id<br />
! Destination<br />
! Virt type <br />
! Vol type<br />
|-<br />
| Fedora-Atomic-25-20161023.n.0.x86_64 || EC2 (us-west-2) || ami-2d4bef4d || hvm || gp2 <br />
|- <br />
| Fedora-Atomic-25-20161023.n.0.x86_64 || EC2 (us-west-2) || ami-7d48ec1d || hvm || standard <br />
|- <br />
| Fedora-Atomic-25-20161023.n.0.x86_64 || EC2 (us-west-1) || ami-c4450ea4 || hvm || standard <br />
|- <br />
| Fedora-Atomic-25-20161023.n.0.x86_64 || EC2 (sa-east-1) || ami-1bd64a77 || hvm || standard <br />
|- <br />
| Fedora-Atomic-25-20161023.n.0.x86_64 || EC2 (eu-west-1) || ami-1b327b68 || hvm || standard <br />
|- <br />
| Fedora-Atomic-25-20161023.n.0.x86_64 || EC2 (eu-central-1) || ami-2645bc49 || hvm || standard <br />
|- <br />
| Fedora-Atomic-25-20161023.n.0.x86_64 || EC2 (ap-southeast-2) || ami-100b3673 || hvm || standard <br />
|- <br />
| Fedora-Atomic-25-20161023.n.0.x86_64 || EC2 (ap-southeast-1) || ami-afe948cc || hvm || standard <br />
|- <br />
| Fedora-Atomic-25-20161023.n.0.x86_64 || EC2 (ap-northeast-1) || ami-5abd1c3b || hvm || standard <br />
|- <br />
| Fedora-Atomic-25-20161023.n.0.x86_64 || EC2 (us-west-1) || ami-6a400b0a || hvm || gp2 <br />
|- <br />
| Fedora-Atomic-25-20161023.n.0.x86_64 || EC2 (sa-east-1) || ami-39d64a55 || hvm || gp2 <br />
|- <br />
| Fedora-Atomic-25-20161023.n.0.x86_64 || EC2 (eu-west-1) || ami-52337a21 || hvm || gp2 <br />
|- <br />
| Fedora-Atomic-25-20161023.n.0.x86_64 || EC2 (eu-central-1) || ami-9d44bdf2 || hvm || gp2 <br />
|- <br />
| Fedora-Atomic-25-20161023.n.0.x86_64 || EC2 (ap-southeast-2) || ami-7a0a3719 || hvm || gp2 <br />
|- <br />
| Fedora-Atomic-25-20161023.n.0.x86_64 || EC2 (ap-southeast-1) || ami-71e94812 || hvm || gp2 <br />
|- <br />
| Fedora-Atomic-25-20161023.n.0.x86_64 || EC2 (ap-northeast-1) || ami-8fba1bee || hvm || gp2 <br />
|- <br />
| Fedora-Atomic-25-20161023.n.0.x86_64 || EC2 (us-east-1) || ami-a7461bb0 || hvm || standard <br />
|- <br />
| Fedora-Atomic-25-20161023.n.0.x86_64 || EC2 (us-east-1) || ami-71471a66 || hvm || gp2 <br />
|-<br />
| Fedora-Cloud-Base-25-20161023.n.0.x86_64 || EC2 (us-west-2) || ami-a74befc7 || paravirtual || gp2<br />
|- <br />
| Fedora-Cloud-Base-25-20161023.n.0.x86_64 || EC2 (us-west-2) || ami-a54befc5 || paravirtual || standard <br />
|-<br />
| Fedora-Cloud-Base-25-20161023.n.0.x86_64 || EC2 (us-west-1) || ami-bc470cdc || paravirtual || standard <br />
|-<br />
| Fedora-Cloud-Base-25-20161023.n.0.x86_64 || EC2 (sa-east-1) || ami-e2da468e || paravirtual || standard <br />
|-<br />
| Fedora-Cloud-Base-25-20161023.n.0.x86_64 || EC2 (eu-west-1) || ami-05337a76 || paravirtual || standard <br />
|-<br />
| Fedora-Cloud-Base-25-20161023.n.0.x86_64 || EC2 (eu-central-1) || ami-2b45bc44 || paravirtual || standard <br />
|-<br />
| Fedora-Cloud-Base-25-20161023.n.0.x86_64 || EC2 (ap-southeast-2) || ami-33053850 || paravirtual || standard <br />
|-<br />
| Fedora-Cloud-Base-25-20161023.n.0.x86_64 || EC2 (ap-southeast-1) || ami-9be746f8 || paravirtual || standard <br />
|-<br />
| Fedora-Cloud-Base-25-20161023.n.0.x86_64 || EC2 (us-west-1) || ami-07460d67 || paravirtual || gp2 <br />
|-<br />
| Fedora-Cloud-Base-25-20161023.n.0.x86_64 || EC2 (sa-east-1) || ami-47d4482b || paravirtual || gp2 <br />
|-<br />
| Fedora-Cloud-Base-25-20161023.n.0.x86_64 || EC2 (eu-west-1) || ami-51347d22 || paravirtual || gp2 <br />
|-<br />
| Fedora-Cloud-Base-25-20161023.n.0.x86_64 || EC2 (eu-central-1) || ami-7db84012 || paravirtual || gp2 <br />
|-<br />
| Fedora-Cloud-Base-25-20161023.n.0.x86_64 || EC2 (ap-southeast-2) || ami-dc0a37bf || paravirtual || gp2 <br />
|-<br />
| Fedora-Cloud-Base-25-20161023.n.0.x86_64 || EC2 (ap-southeast-1) || ami-99e746fa || paravirtual || gp2 <br />
|-<br />
| Fedora-Cloud-Base-25-20161023.n.0.x86_64 || EC2 (ap-northeast-1) || ami-ffbf1e9e || paravirtual || gp2 <br />
|-<br />
| Fedora-Cloud-Base-25-20161023.n.0.x86_64 || EC2 (ap-northeast-1) || ami-37802156 || paravirtual || standard <br />
|-<br />
| Fedora-Cloud-Base-25-20161023.n.0.x86_64 || EC2 (us-east-1) || ami-ed401dfa || paravirtual || gp2 <br />
|-<br />
| Fedora-Cloud-Base-25-20161023.n.0.x86_64 || EC2 (us-east-1) || ami-f1461be6 || paravirtual || standard <br />
|-<br />
| Fedora-Cloud-Base-25-20161023.n.0.x86_64 || EC2 (us-west-2) || ami-194feb79 || hvm || standard <br />
|-<br />
| Fedora-Cloud-Base-25-20161023.n.0.x86_64 || EC2 (sa-east-1) || ami-ce069ba2 || hvm || standard <br />
|-<br />
| Fedora-Cloud-Base-25-20161023.n.0.x86_64 || EC2 (us-west-1) || ami-a1470cc1 || hvm || standard <br />
|-<br />
| Fedora-Cloud-Base-25-20161023.n.0.x86_64 || EC2 (eu-west-1) || ami-91337ae2 || hvm || standard <br />
|-<br />
| Fedora-Cloud-Base-25-20161023.n.0.x86_64 || EC2 (eu-central-1) || ami-fb46bf94 || hvm || standard <br />
|-<br />
| Fedora-Cloud-Base-25-20161023.n.0.x86_64 || EC2 (ap-southeast-2) || ami-130b3670 || hvm || standard <br />
|-<br />
| Fedora-Cloud-Base-25-20161023.n.0.x86_64 || EC2 (ap-southeast-1) || ami-a4e849c7 || hvm || standard <br />
|-<br />
| Fedora-Cloud-Base-25-20161023.n.0.x86_64 || EC2 (us-west-2) || ami-114aee71 || hvm || gp2 <br />
|-<br />
| Fedora-Cloud-Base-25-20161023.n.0.x86_64 || EC2 (ap-northeast-1) || ami-3cbe1f5d || hvm || standard <br />
|-<br />
| Fedora-Cloud-Base-25-20161023.n.0.x86_64 || EC2 (sa-east-1) || ami-cd069ba1 || hvm || gp2 <br />
|- <br />
| Fedora-Cloud-Base-25-20161023.n.0.x86_64 || EC2 (us-west-1) || ami-c6450ea6 || hvm || gp2 <br />
|-<br />
| Fedora-Cloud-Base-25-20161023.n.0.x86_64 || EC2 (eu-west-1) || ami-b1327bc2 || hvm || gp2 <br />
|-<br />
| Fedora-Cloud-Base-25-20161023.n.0.x86_64 || EC2 (eu-central-1) || ami-f546bf9a || hvm || gp2 <br />
|-<br />
| Fedora-Cloud-Base-25-20161023.n.0.x86_64 || EC2 (ap-southeast-2) || ami-1a0b3679 || hvm || gp2 <br />
|-<br />
| Fedora-Cloud-Base-25-20161023.n.0.x86_64 || EC2 (ap-southeast-1) || ami-2ce8494f || hvm || gp2 <br />
|-<br />
| Fedora-Cloud-Base-25-20161023.n.0.x86_64 || EC2 (ap-northeast-1) || ami-64812005 || hvm || gp2 <br />
|-<br />
| Fedora-Cloud-Base-25-20161023.n.0.x86_64 || EC2 (us-east-1) || ami-d04a17c7 || hvm || standard <br />
|-<br />
| Fedora-Cloud-Base-25-20161023.n.0.x86_64 || EC2 (us-east-1) || ami-cf4419d8 || hvm || gp2 <br />
|}<br />
<br />
<br />
Here's a chunk which is commonly used for most Test Days. Replace XX with whatever Fedora release is pending:<br />
<br />
* An updated [https://www.happyassassin.net/nightlies.html Fedora 25 nightly Cloud/Atomic Host image]<br />
<br />
== How to test? ==<br />
<br />
* Boot the images on a cloud system, or on Vagrant or using testcloud on a local system.<br />
* Execute the tests.<br />
<br />
Note: For the service manipulation tests we are stopping/disabling '''chronyd''' service on Fedora 25 systems.<br />
<br />
=== Run the tests ===<br />
<br />
Visit the [http://testdays.fedorainfracloud.org/events/15 result page] and click on the column title links to see the tests that need to be run: most column titles are links to a specific test case. Follow the instructions there, then enter your results by clicking the ''Enter result'' button for the test.<br />
<br />
=== Exploratory testing ===<br />
<br />
If you run out of test cases, congratulations! But that's not the end! You can still help out by playing around with the tool in whatever ways you can think of: try out all the things you can find, and try writing different Fedora images with it. If you have systems with different Windows versions, try running the tool on all of them. Get creative! Any problems you find please file a bug, or report to the IRC channel.<br />
<br />
== Reporting bugs ==<br />
<br />
<br />
<br />
If you have problems with any of the tests, report a bug to [https://bugzilla.redhat.com Bugzilla]. If you are unsure about exactly how to file the report or what other information to include, just ask on IRC and we will help you.<br />
<br />
IRC Channel name: #fedora-cloud, #fedora-test-day<br />
Server: Freenode<br />
<br />
== Test Results ==<br />
<br />
Please enter your results on the [http://testdays.fedorainfracloud.org/events/15 result page]. The results will be transferred here after the Test Day is finished.<br />
<br />
<br />
<br />
<br />
<br />
[[Category:Fedora 25 Test Days]]</div>Kushalhttps://fedoraproject.org/w/index.php?title=Test_Day:2016-10-24_Cloud&diff=477845Test Day:2016-10-24 Cloud2016-10-24T11:52:57Z<p>Kushal: /* How to test? */</p>
<hr />
<div>{{Infobox_group<br />
| name = Fedora Test Day<br />
| image = [[File:Echo-testing-48px.png|link=QA/Test Days]]<br />
| caption = [[Fedora Cloud Test day]]<br />
| date = 2016-10-24<br />
| time = all day<br />
| website = [[QA/Test Days]]<br />
| irc = [irc://irc.freenode.net/#fedora-test-day #fedora-test-day] ([http://webchat.freenode.net/?channels=fedora-test-day webirc])<br />
| fedora_mailing_list = test<br />
}}<br />
<br />
{{admon/note | Can't make the date? | If you come to this page before or after the test day is completed, your testing is still valuable, and you can use the information on this page to test, file any bugs you find at [http://bugzilla.redhat.com Bugzilla], and add your results to the results section. If this page is more than a month old when you arrive here, please check the [[QA/Test_Days|current schedule]] and see if a similar but more recent Test Day is planned or has already happened.}}<br />
<br />
== What to test? ==<br />
<br />
Today's installment of Fedora Test Day will focus on '''Cloud, Atomic Host''' images for Fedora 25.<br />
<br />
== Who's available ==<br />
<br />
The following cast of characters will be available testing, workarounds, bug fixes, and general discussion ...<br />
* Development - <br />
* Quality Assurance - <br />
<br />
== Prerequisite for Test Day == <br />
<br />
You will require at least a system with libvirt/kvm installed. Having access to any Openstack or other Cloud IAAS system where you can upload an image will be even better.<br />
<br />
Download the images from below links<br />
<br />
* [https://kojipkgs.fedoraproject.org/compose/branched/Fedora-25-20161023.n.0/compose/CloudImages/x86_64/images/Fedora-Atomic-25-20161023.n.0.x86_64.qcow2 Atomic Host QCOW2]<br />
* [https://kojipkgs.fedoraproject.org/compose/branched/Fedora-25-20161023.n.0/compose/CloudImages/x86_64/images/Fedora-Atomic-Vagrant-25-20161023.n.0.x86_64.vagrant-virtualbox.box Vagrant Virtualbox Atomic]<br />
* [https://kojipkgs.fedoraproject.org/compose/branched/Fedora-25-20161023.n.0/compose/CloudImages/x86_64/images/Fedora-Atomic-Vagrant-25-20161023.n.0.x86_64.vagrant-libvirt.box Vagrant libvirt Atomic]<br />
<br />
* [https://kojipkgs.fedoraproject.org/compose/branched/Fedora-25-20161023.n.0/compose/CloudImages/x86_64/images/Fedora-Cloud-Base-25-20161023.n.0.x86_64.qcow2 Cloud Base QCOW2]<br />
* [https://kojipkgs.fedoraproject.org/compose/branched/Fedora-25-20161023.n.0/compose/CloudImages/x86_64/images/Fedora-Cloud-Base-Vagrant-25-20161023.n.0.x86_64.vagrant-virtualbox.box Vagrant Virtualbox Cloud Base]<br />
<br />
* [https://kojipkgs.fedoraproject.org/compose/branched/Fedora-25-20161023.n.0/compose/CloudImages/x86_64/images/Fedora-Cloud-Base-Vagrant-25-20161023.n.0.x86_64.vagrant-libvirt.box Vagrant libvirt Cloud Base]<br />
<br />
<br />
List of AMIs<br />
<br />
{|<br />
|-<br />
! Image Name<br />
! AMI id<br />
! Destination<br />
! Virt type <br />
! Vol type<br />
|-<br />
| Fedora-Cloud-Base-25-20161023.n.0.x86_64 || EC2 (us-west-2) || ami-a74befc7 || paravirtual || gp2<br />
|- <br />
| Fedora-Cloud-Base-25-20161023.n.0.x86_64 || EC2 (us-west-2) || ami-a54befc5 || paravirtual || standard <br />
|-<br />
| Fedora-Cloud-Base-25-20161023.n.0.x86_64 || EC2 (us-west-1) || ami-bc470cdc || paravirtual || standard <br />
|-<br />
| Fedora-Cloud-Base-25-20161023.n.0.x86_64 || EC2 (sa-east-1) || ami-e2da468e || paravirtual || standard <br />
|-<br />
| Fedora-Cloud-Base-25-20161023.n.0.x86_64 || EC2 (eu-west-1) || ami-05337a76 || paravirtual || standard <br />
|-<br />
| Fedora-Cloud-Base-25-20161023.n.0.x86_64 || EC2 (eu-central-1) || ami-2b45bc44 || paravirtual || standard <br />
|-<br />
| Fedora-Cloud-Base-25-20161023.n.0.x86_64 || EC2 (ap-southeast-2) || ami-33053850 || paravirtual || standard <br />
|-<br />
| Fedora-Cloud-Base-25-20161023.n.0.x86_64 || EC2 (ap-southeast-1) || ami-9be746f8 || paravirtual || standard <br />
|-<br />
| Fedora-Cloud-Base-25-20161023.n.0.x86_64 || EC2 (us-west-1) || ami-07460d67 || paravirtual || gp2 <br />
|-<br />
| Fedora-Cloud-Base-25-20161023.n.0.x86_64 || EC2 (sa-east-1) || ami-47d4482b || paravirtual || gp2 <br />
|-<br />
| Fedora-Cloud-Base-25-20161023.n.0.x86_64 || EC2 (eu-west-1) || ami-51347d22 || paravirtual || gp2 <br />
|-<br />
| Fedora-Cloud-Base-25-20161023.n.0.x86_64 || EC2 (eu-central-1) || ami-7db84012 || paravirtual || gp2 <br />
|-<br />
| Fedora-Cloud-Base-25-20161023.n.0.x86_64 || EC2 (ap-southeast-2) || ami-dc0a37bf || paravirtual || gp2 <br />
|-<br />
| Fedora-Cloud-Base-25-20161023.n.0.x86_64 || EC2 (ap-southeast-1) || ami-99e746fa || paravirtual || gp2 <br />
|-<br />
| Fedora-Cloud-Base-25-20161023.n.0.x86_64 || EC2 (ap-northeast-1) || ami-ffbf1e9e || paravirtual || gp2 <br />
|-<br />
| Fedora-Cloud-Base-25-20161023.n.0.x86_64 || EC2 (ap-northeast-1) || ami-37802156 || paravirtual || standard <br />
|-<br />
| Fedora-Cloud-Base-25-20161023.n.0.x86_64 || EC2 (us-east-1) || ami-ed401dfa || paravirtual || gp2 <br />
|-<br />
| Fedora-Cloud-Base-25-20161023.n.0.x86_64 || EC2 (us-east-1) || ami-f1461be6 || paravirtual || standard <br />
|-<br />
| Fedora-Cloud-Base-25-20161023.n.0.x86_64 || EC2 (us-west-2) || ami-194feb79 || hvm || standard <br />
|-<br />
| Fedora-Cloud-Base-25-20161023.n.0.x86_64 || EC2 (sa-east-1) || ami-ce069ba2 || hvm || standard <br />
|-<br />
| Fedora-Cloud-Base-25-20161023.n.0.x86_64 || EC2 (us-west-1) || ami-a1470cc1 || hvm || standard <br />
|-<br />
| Fedora-Cloud-Base-25-20161023.n.0.x86_64 || EC2 (eu-west-1) || ami-91337ae2 || hvm || standard <br />
|-<br />
| Fedora-Cloud-Base-25-20161023.n.0.x86_64 || EC2 (eu-central-1) || ami-fb46bf94 || hvm || standard <br />
|-<br />
| Fedora-Cloud-Base-25-20161023.n.0.x86_64 || EC2 (ap-southeast-2) || ami-130b3670 || hvm || standard <br />
|-<br />
| Fedora-Cloud-Base-25-20161023.n.0.x86_64 || EC2 (ap-southeast-1) || ami-a4e849c7 || hvm || standard <br />
|-<br />
| Fedora-Cloud-Base-25-20161023.n.0.x86_64 || EC2 (us-west-2) || ami-114aee71 || hvm || gp2 <br />
|-<br />
| Fedora-Cloud-Base-25-20161023.n.0.x86_64 || EC2 (ap-northeast-1) || ami-3cbe1f5d || hvm || standard <br />
|-<br />
| Fedora-Cloud-Base-25-20161023.n.0.x86_64 || EC2 (sa-east-1) || ami-cd069ba1 || hvm || gp2 <br />
|- <br />
| Fedora-Cloud-Base-25-20161023.n.0.x86_64 || EC2 (us-west-1) || ami-c6450ea6 || hvm || gp2 <br />
|-<br />
| Fedora-Cloud-Base-25-20161023.n.0.x86_64 || EC2 (eu-west-1) || ami-b1327bc2 || hvm || gp2 <br />
|-<br />
| Fedora-Cloud-Base-25-20161023.n.0.x86_64 || EC2 (eu-central-1) || ami-f546bf9a || hvm || gp2 <br />
|-<br />
| Fedora-Cloud-Base-25-20161023.n.0.x86_64 || EC2 (ap-southeast-2) || ami-1a0b3679 || hvm || gp2 <br />
|-<br />
| Fedora-Cloud-Base-25-20161023.n.0.x86_64 || EC2 (ap-southeast-1) || ami-2ce8494f || hvm || gp2 <br />
|-<br />
| Fedora-Cloud-Base-25-20161023.n.0.x86_64 || EC2 (ap-northeast-1) || ami-64812005 || hvm || gp2 <br />
|-<br />
| Fedora-Cloud-Base-25-20161023.n.0.x86_64 || EC2 (us-east-1) || ami-d04a17c7 || hvm || standard <br />
|-<br />
| Fedora-Cloud-Base-25-20161023.n.0.x86_64 || EC2 (us-east-1) || ami-cf4419d8 || hvm || gp2 <br />
|}<br />
<br />
<br />
Here's a chunk which is commonly used for most Test Days. Replace XX with whatever Fedora release is pending:<br />
<br />
* An updated [https://www.happyassassin.net/nightlies.html Fedora 25 nightly Cloud/Atomic Host image]<br />
<br />
== How to test? ==<br />
<br />
* Boot the images on a cloud system, or on Vagrant or using testcloud on a local system.<br />
* Execute the tests.<br />
<br />
Note: For the service manipulation tests we are stopping/disabling '''chronyd''' service on Fedora 25 systems.<br />
<br />
=== Run the tests ===<br />
<br />
Visit the [http://testdays.fedorainfracloud.org/events/11 result page] and click on the column title links to see the tests that need to be run: most column titles are links to a specific test case. Follow the instructions there, then enter your results by clicking the ''Enter result'' button for the test.<br />
<br />
=== Exploratory testing ===<br />
<br />
If you run out of test cases, congratulations! But that's not the end! You can still help out by playing around with the tool in whatever ways you can think of: try out all the things you can find, and try writing different Fedora images with it. If you have systems with different Windows versions, try running the tool on all of them. Get creative! Any problems you find please file a bug, or report to the IRC channel.<br />
<br />
== Reporting bugs ==<br />
<br />
<br />
<br />
If you have problems with any of the tests, report a bug to [https://bugzilla.redhat.com Bugzilla]. If you are unsure about exactly how to file the report or what other information to include, just ask on IRC and we will help you.<br />
<br />
IRC Channel name: #fedora-cloud, #fedora-test-day<br />
Server: Freenode<br />
<br />
== Test Results ==<br />
<br />
Please enter your results on the [http://testdays.fedorainfracloud.org/events/11 result page]. The results will be transferred here after the Test Day is finished.<br />
<br />
<br />
<br />
<br />
<br />
[[Category:Fedora 25 Test Days]]</div>Kushalhttps://fedoraproject.org/w/index.php?title=Test_Day:2016-10-24_Cloud&diff=477844Test Day:2016-10-24 Cloud2016-10-24T11:40:55Z<p>Kushal: /* Prerequisite for Test Day */ Updating the links to the images to test</p>
<hr />
<div>{{Infobox_group<br />
| name = Fedora Test Day<br />
| image = [[File:Echo-testing-48px.png|link=QA/Test Days]]<br />
| caption = [[Fedora Cloud Test day]]<br />
| date = 2016-10-24<br />
| time = all day<br />
| website = [[QA/Test Days]]<br />
| irc = [irc://irc.freenode.net/#fedora-test-day #fedora-test-day] ([http://webchat.freenode.net/?channels=fedora-test-day webirc])<br />
| fedora_mailing_list = test<br />
}}<br />
<br />
{{admon/note | Can't make the date? | If you come to this page before or after the test day is completed, your testing is still valuable, and you can use the information on this page to test, file any bugs you find at [http://bugzilla.redhat.com Bugzilla], and add your results to the results section. If this page is more than a month old when you arrive here, please check the [[QA/Test_Days|current schedule]] and see if a similar but more recent Test Day is planned or has already happened.}}<br />
<br />
== What to test? ==<br />
<br />
Today's installment of Fedora Test Day will focus on '''Cloud, Atomic Host''' images for Fedora 25.<br />
<br />
== Who's available ==<br />
<br />
The following cast of characters will be available testing, workarounds, bug fixes, and general discussion ...<br />
* Development - <br />
* Quality Assurance - <br />
<br />
== Prerequisite for Test Day == <br />
<br />
You will require at least a system with libvirt/kvm installed. Having access to any Openstack or other Cloud IAAS system where you can upload an image will be even better.<br />
<br />
Download the images from below links<br />
<br />
* [https://kojipkgs.fedoraproject.org/compose/branched/Fedora-25-20161023.n.0/compose/CloudImages/x86_64/images/Fedora-Atomic-25-20161023.n.0.x86_64.qcow2 Atomic Host QCOW2]<br />
* [https://kojipkgs.fedoraproject.org/compose/branched/Fedora-25-20161023.n.0/compose/CloudImages/x86_64/images/Fedora-Atomic-Vagrant-25-20161023.n.0.x86_64.vagrant-virtualbox.box Vagrant Virtualbox Atomic]<br />
* [https://kojipkgs.fedoraproject.org/compose/branched/Fedora-25-20161023.n.0/compose/CloudImages/x86_64/images/Fedora-Atomic-Vagrant-25-20161023.n.0.x86_64.vagrant-libvirt.box Vagrant libvirt Atomic]<br />
<br />
* [https://kojipkgs.fedoraproject.org/compose/branched/Fedora-25-20161023.n.0/compose/CloudImages/x86_64/images/Fedora-Cloud-Base-25-20161023.n.0.x86_64.qcow2 Cloud Base QCOW2]<br />
* [https://kojipkgs.fedoraproject.org/compose/branched/Fedora-25-20161023.n.0/compose/CloudImages/x86_64/images/Fedora-Cloud-Base-Vagrant-25-20161023.n.0.x86_64.vagrant-virtualbox.box Vagrant Virtualbox Cloud Base]<br />
<br />
* [https://kojipkgs.fedoraproject.org/compose/branched/Fedora-25-20161023.n.0/compose/CloudImages/x86_64/images/Fedora-Cloud-Base-Vagrant-25-20161023.n.0.x86_64.vagrant-libvirt.box Vagrant libvirt Cloud Base]<br />
<br />
<br />
List of AMIs<br />
<br />
{|<br />
|-<br />
! Image Name<br />
! AMI id<br />
! Destination<br />
! Virt type <br />
! Vol type<br />
|-<br />
| Fedora-Cloud-Base-25-20161023.n.0.x86_64 || EC2 (us-west-2) || ami-a74befc7 || paravirtual || gp2<br />
|- <br />
| Fedora-Cloud-Base-25-20161023.n.0.x86_64 || EC2 (us-west-2) || ami-a54befc5 || paravirtual || standard <br />
|-<br />
| Fedora-Cloud-Base-25-20161023.n.0.x86_64 || EC2 (us-west-1) || ami-bc470cdc || paravirtual || standard <br />
|-<br />
| Fedora-Cloud-Base-25-20161023.n.0.x86_64 || EC2 (sa-east-1) || ami-e2da468e || paravirtual || standard <br />
|-<br />
| Fedora-Cloud-Base-25-20161023.n.0.x86_64 || EC2 (eu-west-1) || ami-05337a76 || paravirtual || standard <br />
|-<br />
| Fedora-Cloud-Base-25-20161023.n.0.x86_64 || EC2 (eu-central-1) || ami-2b45bc44 || paravirtual || standard <br />
|-<br />
| Fedora-Cloud-Base-25-20161023.n.0.x86_64 || EC2 (ap-southeast-2) || ami-33053850 || paravirtual || standard <br />
|-<br />
| Fedora-Cloud-Base-25-20161023.n.0.x86_64 || EC2 (ap-southeast-1) || ami-9be746f8 || paravirtual || standard <br />
|-<br />
| Fedora-Cloud-Base-25-20161023.n.0.x86_64 || EC2 (us-west-1) || ami-07460d67 || paravirtual || gp2 <br />
|-<br />
| Fedora-Cloud-Base-25-20161023.n.0.x86_64 || EC2 (sa-east-1) || ami-47d4482b || paravirtual || gp2 <br />
|-<br />
| Fedora-Cloud-Base-25-20161023.n.0.x86_64 || EC2 (eu-west-1) || ami-51347d22 || paravirtual || gp2 <br />
|-<br />
| Fedora-Cloud-Base-25-20161023.n.0.x86_64 || EC2 (eu-central-1) || ami-7db84012 || paravirtual || gp2 <br />
|-<br />
| Fedora-Cloud-Base-25-20161023.n.0.x86_64 || EC2 (ap-southeast-2) || ami-dc0a37bf || paravirtual || gp2 <br />
|-<br />
| Fedora-Cloud-Base-25-20161023.n.0.x86_64 || EC2 (ap-southeast-1) || ami-99e746fa || paravirtual || gp2 <br />
|-<br />
| Fedora-Cloud-Base-25-20161023.n.0.x86_64 || EC2 (ap-northeast-1) || ami-ffbf1e9e || paravirtual || gp2 <br />
|-<br />
| Fedora-Cloud-Base-25-20161023.n.0.x86_64 || EC2 (ap-northeast-1) || ami-37802156 || paravirtual || standard <br />
|-<br />
| Fedora-Cloud-Base-25-20161023.n.0.x86_64 || EC2 (us-east-1) || ami-ed401dfa || paravirtual || gp2 <br />
|-<br />
| Fedora-Cloud-Base-25-20161023.n.0.x86_64 || EC2 (us-east-1) || ami-f1461be6 || paravirtual || standard <br />
|-<br />
| Fedora-Cloud-Base-25-20161023.n.0.x86_64 || EC2 (us-west-2) || ami-194feb79 || hvm || standard <br />
|-<br />
| Fedora-Cloud-Base-25-20161023.n.0.x86_64 || EC2 (sa-east-1) || ami-ce069ba2 || hvm || standard <br />
|-<br />
| Fedora-Cloud-Base-25-20161023.n.0.x86_64 || EC2 (us-west-1) || ami-a1470cc1 || hvm || standard <br />
|-<br />
| Fedora-Cloud-Base-25-20161023.n.0.x86_64 || EC2 (eu-west-1) || ami-91337ae2 || hvm || standard <br />
|-<br />
| Fedora-Cloud-Base-25-20161023.n.0.x86_64 || EC2 (eu-central-1) || ami-fb46bf94 || hvm || standard <br />
|-<br />
| Fedora-Cloud-Base-25-20161023.n.0.x86_64 || EC2 (ap-southeast-2) || ami-130b3670 || hvm || standard <br />
|-<br />
| Fedora-Cloud-Base-25-20161023.n.0.x86_64 || EC2 (ap-southeast-1) || ami-a4e849c7 || hvm || standard <br />
|-<br />
| Fedora-Cloud-Base-25-20161023.n.0.x86_64 || EC2 (us-west-2) || ami-114aee71 || hvm || gp2 <br />
|-<br />
| Fedora-Cloud-Base-25-20161023.n.0.x86_64 || EC2 (ap-northeast-1) || ami-3cbe1f5d || hvm || standard <br />
|-<br />
| Fedora-Cloud-Base-25-20161023.n.0.x86_64 || EC2 (sa-east-1) || ami-cd069ba1 || hvm || gp2 <br />
|- <br />
| Fedora-Cloud-Base-25-20161023.n.0.x86_64 || EC2 (us-west-1) || ami-c6450ea6 || hvm || gp2 <br />
|-<br />
| Fedora-Cloud-Base-25-20161023.n.0.x86_64 || EC2 (eu-west-1) || ami-b1327bc2 || hvm || gp2 <br />
|-<br />
| Fedora-Cloud-Base-25-20161023.n.0.x86_64 || EC2 (eu-central-1) || ami-f546bf9a || hvm || gp2 <br />
|-<br />
| Fedora-Cloud-Base-25-20161023.n.0.x86_64 || EC2 (ap-southeast-2) || ami-1a0b3679 || hvm || gp2 <br />
|-<br />
| Fedora-Cloud-Base-25-20161023.n.0.x86_64 || EC2 (ap-southeast-1) || ami-2ce8494f || hvm || gp2 <br />
|-<br />
| Fedora-Cloud-Base-25-20161023.n.0.x86_64 || EC2 (ap-northeast-1) || ami-64812005 || hvm || gp2 <br />
|-<br />
| Fedora-Cloud-Base-25-20161023.n.0.x86_64 || EC2 (us-east-1) || ami-d04a17c7 || hvm || standard <br />
|-<br />
| Fedora-Cloud-Base-25-20161023.n.0.x86_64 || EC2 (us-east-1) || ami-cf4419d8 || hvm || gp2 <br />
|}<br />
<br />
<br />
Here's a chunk which is commonly used for most Test Days. Replace XX with whatever Fedora release is pending:<br />
<br />
* An updated [https://www.happyassassin.net/nightlies.html Fedora 25 nightly Cloud/Atomic Host image]<br />
<br />
== How to test? ==<br />
<br />
* Boot the images on a cloud system, or on Vagrant or using testcloud on a local system.<br />
* Execute the tests.<br />
<br />
Note: For the service manipulation tests we are stopping/disabling **chronyd** service on Fedora 25 systems.<br />
<br />
=== Run the tests ===<br />
<br />
Visit the [http://testdays.fedorainfracloud.org/events/11 result page] and click on the column title links to see the tests that need to be run: most column titles are links to a specific test case. Follow the instructions there, then enter your results by clicking the ''Enter result'' button for the test.<br />
<br />
=== Exploratory testing ===<br />
<br />
If you run out of test cases, congratulations! But that's not the end! You can still help out by playing around with the tool in whatever ways you can think of: try out all the things you can find, and try writing different Fedora images with it. If you have systems with different Windows versions, try running the tool on all of them. Get creative! Any problems you find please file a bug, or report to the IRC channel.<br />
<br />
== Reporting bugs ==<br />
<br />
<br />
<br />
If you have problems with any of the tests, report a bug to [https://bugzilla.redhat.com Bugzilla]. If you are unsure about exactly how to file the report or what other information to include, just ask on IRC and we will help you.<br />
<br />
IRC Channel name: #fedora-cloud, #fedora-test-day<br />
Server: Freenode<br />
<br />
== Test Results ==<br />
<br />
Please enter your results on the [http://testdays.fedorainfracloud.org/events/11 result page]. The results will be transferred here after the Test Day is finished.<br />
<br />
<br />
<br />
<br />
<br />
[[Category:Fedora 25 Test Days]]</div>Kushalhttps://fedoraproject.org/w/index.php?title=Test_Day:2016-10-24_Cloud&diff=477842Test Day:2016-10-24 Cloud2016-10-24T11:29:11Z<p>Kushal: Updating the link of the event based on the mailing list</p>
<hr />
<div>{{Infobox_group<br />
| name = Fedora Test Day<br />
| image = [[File:Echo-testing-48px.png|link=QA/Test Days]]<br />
| caption = [[Fedora Cloud Test day]]<br />
| date = 2016-10-24<br />
| time = all day<br />
| website = [[QA/Test Days]]<br />
| irc = [irc://irc.freenode.net/#fedora-test-day #fedora-test-day] ([http://webchat.freenode.net/?channels=fedora-test-day webirc])<br />
| fedora_mailing_list = test<br />
}}<br />
<br />
{{admon/note | Can't make the date? | If you come to this page before or after the test day is completed, your testing is still valuable, and you can use the information on this page to test, file any bugs you find at [http://bugzilla.redhat.com Bugzilla], and add your results to the results section. If this page is more than a month old when you arrive here, please check the [[QA/Test_Days|current schedule]] and see if a similar but more recent Test Day is planned or has already happened.}}<br />
<br />
== What to test? ==<br />
<br />
Today's installment of Fedora Test Day will focus on '''Cloud, Atomic Host''' images for Fedora 25.<br />
<br />
== Who's available ==<br />
<br />
The following cast of characters will be available testing, workarounds, bug fixes, and general discussion ...<br />
* Development - <br />
* Quality Assurance - <br />
<br />
== Prerequisite for Test Day == <br />
<br />
You will require at least a system with libvirt/kvm installed. Having access to any Openstack or other Cloud IAAS system where you can upload an image will be even better.<br />
<br />
Download the images from below links<br />
<br />
* [linkTK Cloud Image QCOW2]<br />
* [linkTK Atomic Host Image QCOW2]<br />
<br />
* [linkTK Vagrant Virtualbox cloud base]<br />
* [linkTK Vagrant Virtualbox Atomic]<br />
<br />
List of AMIs<br />
<br />
{|<br />
|-<br />
! Image Name<br />
! AMI id<br />
! Destination<br />
! Virt type <br />
! Vol type<br />
|-<br />
| Fedora-Cloud-Base-25-20161023.n.0.x86_64 || EC2 (us-west-2) || ami-a74befc7 || paravirtual || gp2<br />
|- <br />
| Fedora-Cloud-Base-25-20161023.n.0.x86_64 || EC2 (us-west-2) || ami-a54befc5 || paravirtual || standard <br />
|-<br />
| Fedora-Cloud-Base-25-20161023.n.0.x86_64 || EC2 (us-west-1) || ami-bc470cdc || paravirtual || standard <br />
|-<br />
| Fedora-Cloud-Base-25-20161023.n.0.x86_64 || EC2 (sa-east-1) || ami-e2da468e || paravirtual || standard <br />
|-<br />
| Fedora-Cloud-Base-25-20161023.n.0.x86_64 || EC2 (eu-west-1) || ami-05337a76 || paravirtual || standard <br />
|-<br />
| Fedora-Cloud-Base-25-20161023.n.0.x86_64 || EC2 (eu-central-1) || ami-2b45bc44 || paravirtual || standard <br />
|-<br />
| Fedora-Cloud-Base-25-20161023.n.0.x86_64 || EC2 (ap-southeast-2) || ami-33053850 || paravirtual || standard <br />
|-<br />
| Fedora-Cloud-Base-25-20161023.n.0.x86_64 || EC2 (ap-southeast-1) || ami-9be746f8 || paravirtual || standard <br />
|-<br />
| Fedora-Cloud-Base-25-20161023.n.0.x86_64 || EC2 (us-west-1) || ami-07460d67 || paravirtual || gp2 <br />
|-<br />
| Fedora-Cloud-Base-25-20161023.n.0.x86_64 || EC2 (sa-east-1) || ami-47d4482b || paravirtual || gp2 <br />
|-<br />
| Fedora-Cloud-Base-25-20161023.n.0.x86_64 || EC2 (eu-west-1) || ami-51347d22 || paravirtual || gp2 <br />
|-<br />
| Fedora-Cloud-Base-25-20161023.n.0.x86_64 || EC2 (eu-central-1) || ami-7db84012 || paravirtual || gp2 <br />
|-<br />
| Fedora-Cloud-Base-25-20161023.n.0.x86_64 || EC2 (ap-southeast-2) || ami-dc0a37bf || paravirtual || gp2 <br />
|-<br />
| Fedora-Cloud-Base-25-20161023.n.0.x86_64 || EC2 (ap-southeast-1) || ami-99e746fa || paravirtual || gp2 <br />
|-<br />
| Fedora-Cloud-Base-25-20161023.n.0.x86_64 || EC2 (ap-northeast-1) || ami-ffbf1e9e || paravirtual || gp2 <br />
|-<br />
| Fedora-Cloud-Base-25-20161023.n.0.x86_64 || EC2 (ap-northeast-1) || ami-37802156 || paravirtual || standard <br />
|-<br />
| Fedora-Cloud-Base-25-20161023.n.0.x86_64 || EC2 (us-east-1) || ami-ed401dfa || paravirtual || gp2 <br />
|-<br />
| Fedora-Cloud-Base-25-20161023.n.0.x86_64 || EC2 (us-east-1) || ami-f1461be6 || paravirtual || standard <br />
|-<br />
| Fedora-Cloud-Base-25-20161023.n.0.x86_64 || EC2 (us-west-2) || ami-194feb79 || hvm || standard <br />
|-<br />
| Fedora-Cloud-Base-25-20161023.n.0.x86_64 || EC2 (sa-east-1) || ami-ce069ba2 || hvm || standard <br />
|-<br />
| Fedora-Cloud-Base-25-20161023.n.0.x86_64 || EC2 (us-west-1) || ami-a1470cc1 || hvm || standard <br />
|-<br />
| Fedora-Cloud-Base-25-20161023.n.0.x86_64 || EC2 (eu-west-1) || ami-91337ae2 || hvm || standard <br />
|-<br />
| Fedora-Cloud-Base-25-20161023.n.0.x86_64 || EC2 (eu-central-1) || ami-fb46bf94 || hvm || standard <br />
|-<br />
| Fedora-Cloud-Base-25-20161023.n.0.x86_64 || EC2 (ap-southeast-2) || ami-130b3670 || hvm || standard <br />
|-<br />
| Fedora-Cloud-Base-25-20161023.n.0.x86_64 || EC2 (ap-southeast-1) || ami-a4e849c7 || hvm || standard <br />
|-<br />
| Fedora-Cloud-Base-25-20161023.n.0.x86_64 || EC2 (us-west-2) || ami-114aee71 || hvm || gp2 <br />
|-<br />
| Fedora-Cloud-Base-25-20161023.n.0.x86_64 || EC2 (ap-northeast-1) || ami-3cbe1f5d || hvm || standard <br />
|-<br />
| Fedora-Cloud-Base-25-20161023.n.0.x86_64 || EC2 (sa-east-1) || ami-cd069ba1 || hvm || gp2 <br />
|- <br />
| Fedora-Cloud-Base-25-20161023.n.0.x86_64 || EC2 (us-west-1) || ami-c6450ea6 || hvm || gp2 <br />
|-<br />
| Fedora-Cloud-Base-25-20161023.n.0.x86_64 || EC2 (eu-west-1) || ami-b1327bc2 || hvm || gp2 <br />
|-<br />
| Fedora-Cloud-Base-25-20161023.n.0.x86_64 || EC2 (eu-central-1) || ami-f546bf9a || hvm || gp2 <br />
|-<br />
| Fedora-Cloud-Base-25-20161023.n.0.x86_64 || EC2 (ap-southeast-2) || ami-1a0b3679 || hvm || gp2 <br />
|-<br />
| Fedora-Cloud-Base-25-20161023.n.0.x86_64 || EC2 (ap-southeast-1) || ami-2ce8494f || hvm || gp2 <br />
|-<br />
| Fedora-Cloud-Base-25-20161023.n.0.x86_64 || EC2 (ap-northeast-1) || ami-64812005 || hvm || gp2 <br />
|-<br />
| Fedora-Cloud-Base-25-20161023.n.0.x86_64 || EC2 (us-east-1) || ami-d04a17c7 || hvm || standard <br />
|-<br />
| Fedora-Cloud-Base-25-20161023.n.0.x86_64 || EC2 (us-east-1) || ami-cf4419d8 || hvm || gp2 <br />
|}<br />
<br />
<br />
Here's a chunk which is commonly used for most Test Days. Replace XX with whatever Fedora release is pending:<br />
<br />
* An updated [https://www.happyassassin.net/nightlies.html Fedora 25 nightly Cloud/Atomic Host image]<br />
<br />
== How to test? ==<br />
<br />
* Boot the images on a cloud system, or on Vagrant or using testcloud on a local system.<br />
* Execute the tests.<br />
<br />
Note: For the service manipulation tests we are stopping/disabling **chronyd** service on Fedora 25 systems.<br />
<br />
=== Run the tests ===<br />
<br />
Visit the [http://testdays.fedorainfracloud.org/events/11 result page] and click on the column title links to see the tests that need to be run: most column titles are links to a specific test case. Follow the instructions there, then enter your results by clicking the ''Enter result'' button for the test.<br />
<br />
=== Exploratory testing ===<br />
<br />
If you run out of test cases, congratulations! But that's not the end! You can still help out by playing around with the tool in whatever ways you can think of: try out all the things you can find, and try writing different Fedora images with it. If you have systems with different Windows versions, try running the tool on all of them. Get creative! Any problems you find please file a bug, or report to the IRC channel.<br />
<br />
== Reporting bugs ==<br />
<br />
<br />
<br />
If you have problems with any of the tests, report a bug to [https://bugzilla.redhat.com Bugzilla]. If you are unsure about exactly how to file the report or what other information to include, just ask on IRC and we will help you.<br />
<br />
IRC Channel name: #fedora-cloud, #fedora-test-day<br />
Server: Freenode<br />
<br />
== Test Results ==<br />
<br />
Please enter your results on the [http://testdays.fedorainfracloud.org/events/11 result page]. The results will be transferred here after the Test Day is finished.<br />
<br />
<br />
<br />
<br />
<br />
[[Category:Fedora 25 Test Days]]</div>Kushalhttps://fedoraproject.org/w/index.php?title=Test_Day:2016-10-24_Cloud&diff=477841Test Day:2016-10-24 Cloud2016-10-24T11:28:12Z<p>Kushal: /* How to test? */ use chronyd service</p>
<hr />
<div>{{Infobox_group<br />
| name = Fedora Test Day<br />
| image = [[File:Echo-testing-48px.png|link=QA/Test Days]]<br />
| caption = [[Fedora Cloud Test day]]<br />
| date = 2016-10-24<br />
| time = all day<br />
| website = [[QA/Test Days]]<br />
| irc = [irc://irc.freenode.net/#fedora-test-day #fedora-test-day] ([http://webchat.freenode.net/?channels=fedora-test-day webirc])<br />
| fedora_mailing_list = test<br />
}}<br />
<br />
{{admon/note | Can't make the date? | If you come to this page before or after the test day is completed, your testing is still valuable, and you can use the information on this page to test, file any bugs you find at [http://bugzilla.redhat.com Bugzilla], and add your results to the results section. If this page is more than a month old when you arrive here, please check the [[QA/Test_Days|current schedule]] and see if a similar but more recent Test Day is planned or has already happened.}}<br />
<br />
== What to test? ==<br />
<br />
Today's installment of Fedora Test Day will focus on '''Cloud, Atomic Host''' images for Fedora 25.<br />
<br />
== Who's available ==<br />
<br />
The following cast of characters will be available testing, workarounds, bug fixes, and general discussion ...<br />
* Development - <br />
* Quality Assurance - <br />
<br />
== Prerequisite for Test Day == <br />
<br />
You will require at least a system with libvirt/kvm installed. Having access to any Openstack or other Cloud IAAS system where you can upload an image will be even better.<br />
<br />
Download the images from below links<br />
<br />
* [linkTK Cloud Image QCOW2]<br />
* [linkTK Atomic Host Image QCOW2]<br />
<br />
* [linkTK Vagrant Virtualbox cloud base]<br />
* [linkTK Vagrant Virtualbox Atomic]<br />
<br />
List of AMIs<br />
<br />
{|<br />
|-<br />
! Image Name<br />
! AMI id<br />
! Destination<br />
! Virt type <br />
! Vol type<br />
|-<br />
| Fedora-Cloud-Base-25-20161023.n.0.x86_64 || EC2 (us-west-2) || ami-a74befc7 || paravirtual || gp2<br />
|- <br />
| Fedora-Cloud-Base-25-20161023.n.0.x86_64 || EC2 (us-west-2) || ami-a54befc5 || paravirtual || standard <br />
|-<br />
| Fedora-Cloud-Base-25-20161023.n.0.x86_64 || EC2 (us-west-1) || ami-bc470cdc || paravirtual || standard <br />
|-<br />
| Fedora-Cloud-Base-25-20161023.n.0.x86_64 || EC2 (sa-east-1) || ami-e2da468e || paravirtual || standard <br />
|-<br />
| Fedora-Cloud-Base-25-20161023.n.0.x86_64 || EC2 (eu-west-1) || ami-05337a76 || paravirtual || standard <br />
|-<br />
| Fedora-Cloud-Base-25-20161023.n.0.x86_64 || EC2 (eu-central-1) || ami-2b45bc44 || paravirtual || standard <br />
|-<br />
| Fedora-Cloud-Base-25-20161023.n.0.x86_64 || EC2 (ap-southeast-2) || ami-33053850 || paravirtual || standard <br />
|-<br />
| Fedora-Cloud-Base-25-20161023.n.0.x86_64 || EC2 (ap-southeast-1) || ami-9be746f8 || paravirtual || standard <br />
|-<br />
| Fedora-Cloud-Base-25-20161023.n.0.x86_64 || EC2 (us-west-1) || ami-07460d67 || paravirtual || gp2 <br />
|-<br />
| Fedora-Cloud-Base-25-20161023.n.0.x86_64 || EC2 (sa-east-1) || ami-47d4482b || paravirtual || gp2 <br />
|-<br />
| Fedora-Cloud-Base-25-20161023.n.0.x86_64 || EC2 (eu-west-1) || ami-51347d22 || paravirtual || gp2 <br />
|-<br />
| Fedora-Cloud-Base-25-20161023.n.0.x86_64 || EC2 (eu-central-1) || ami-7db84012 || paravirtual || gp2 <br />
|-<br />
| Fedora-Cloud-Base-25-20161023.n.0.x86_64 || EC2 (ap-southeast-2) || ami-dc0a37bf || paravirtual || gp2 <br />
|-<br />
| Fedora-Cloud-Base-25-20161023.n.0.x86_64 || EC2 (ap-southeast-1) || ami-99e746fa || paravirtual || gp2 <br />
|-<br />
| Fedora-Cloud-Base-25-20161023.n.0.x86_64 || EC2 (ap-northeast-1) || ami-ffbf1e9e || paravirtual || gp2 <br />
|-<br />
| Fedora-Cloud-Base-25-20161023.n.0.x86_64 || EC2 (ap-northeast-1) || ami-37802156 || paravirtual || standard <br />
|-<br />
| Fedora-Cloud-Base-25-20161023.n.0.x86_64 || EC2 (us-east-1) || ami-ed401dfa || paravirtual || gp2 <br />
|-<br />
| Fedora-Cloud-Base-25-20161023.n.0.x86_64 || EC2 (us-east-1) || ami-f1461be6 || paravirtual || standard <br />
|-<br />
| Fedora-Cloud-Base-25-20161023.n.0.x86_64 || EC2 (us-west-2) || ami-194feb79 || hvm || standard <br />
|-<br />
| Fedora-Cloud-Base-25-20161023.n.0.x86_64 || EC2 (sa-east-1) || ami-ce069ba2 || hvm || standard <br />
|-<br />
| Fedora-Cloud-Base-25-20161023.n.0.x86_64 || EC2 (us-west-1) || ami-a1470cc1 || hvm || standard <br />
|-<br />
| Fedora-Cloud-Base-25-20161023.n.0.x86_64 || EC2 (eu-west-1) || ami-91337ae2 || hvm || standard <br />
|-<br />
| Fedora-Cloud-Base-25-20161023.n.0.x86_64 || EC2 (eu-central-1) || ami-fb46bf94 || hvm || standard <br />
|-<br />
| Fedora-Cloud-Base-25-20161023.n.0.x86_64 || EC2 (ap-southeast-2) || ami-130b3670 || hvm || standard <br />
|-<br />
| Fedora-Cloud-Base-25-20161023.n.0.x86_64 || EC2 (ap-southeast-1) || ami-a4e849c7 || hvm || standard <br />
|-<br />
| Fedora-Cloud-Base-25-20161023.n.0.x86_64 || EC2 (us-west-2) || ami-114aee71 || hvm || gp2 <br />
|-<br />
| Fedora-Cloud-Base-25-20161023.n.0.x86_64 || EC2 (ap-northeast-1) || ami-3cbe1f5d || hvm || standard <br />
|-<br />
| Fedora-Cloud-Base-25-20161023.n.0.x86_64 || EC2 (sa-east-1) || ami-cd069ba1 || hvm || gp2 <br />
|- <br />
| Fedora-Cloud-Base-25-20161023.n.0.x86_64 || EC2 (us-west-1) || ami-c6450ea6 || hvm || gp2 <br />
|-<br />
| Fedora-Cloud-Base-25-20161023.n.0.x86_64 || EC2 (eu-west-1) || ami-b1327bc2 || hvm || gp2 <br />
|-<br />
| Fedora-Cloud-Base-25-20161023.n.0.x86_64 || EC2 (eu-central-1) || ami-f546bf9a || hvm || gp2 <br />
|-<br />
| Fedora-Cloud-Base-25-20161023.n.0.x86_64 || EC2 (ap-southeast-2) || ami-1a0b3679 || hvm || gp2 <br />
|-<br />
| Fedora-Cloud-Base-25-20161023.n.0.x86_64 || EC2 (ap-southeast-1) || ami-2ce8494f || hvm || gp2 <br />
|-<br />
| Fedora-Cloud-Base-25-20161023.n.0.x86_64 || EC2 (ap-northeast-1) || ami-64812005 || hvm || gp2 <br />
|-<br />
| Fedora-Cloud-Base-25-20161023.n.0.x86_64 || EC2 (us-east-1) || ami-d04a17c7 || hvm || standard <br />
|-<br />
| Fedora-Cloud-Base-25-20161023.n.0.x86_64 || EC2 (us-east-1) || ami-cf4419d8 || hvm || gp2 <br />
|}<br />
<br />
<br />
Here's a chunk which is commonly used for most Test Days. Replace XX with whatever Fedora release is pending:<br />
<br />
* An updated [https://www.happyassassin.net/nightlies.html Fedora 25 nightly Cloud/Atomic Host image]<br />
<br />
== How to test? ==<br />
<br />
* Boot the images on a cloud system, or on Vagrant or using testcloud on a local system.<br />
* Execute the tests.<br />
<br />
Note: For the service manipulation tests we are stopping/disabling **chronyd** service on Fedora 25 systems.<br />
<br />
=== Run the tests ===<br />
<br />
Visit the [http://testdays.fedorainfracloud.org/events/13 result page] and click on the column title links to see the tests that need to be run: most column titles are links to a specific test case. Follow the instructions there, then enter your results by clicking the ''Enter result'' button for the test.<br />
<br />
=== Exploratory testing ===<br />
<br />
If you run out of test cases, congratulations! But that's not the end! You can still help out by playing around with the tool in whatever ways you can think of: try out all the things you can find, and try writing different Fedora images with it. If you have systems with different Windows versions, try running the tool on all of them. Get creative! Any problems you find please file a bug, or report to the IRC channel.<br />
<br />
== Reporting bugs ==<br />
<br />
<br />
<br />
If you have problems with any of the tests, report a bug to [https://bugzilla.redhat.com Bugzilla]. If you are unsure about exactly how to file the report or what other information to include, just ask on IRC and we will help you.<br />
<br />
IRC Channel name: #fedora-cloud, #fedora-test-day<br />
Server: Freenode<br />
<br />
== Test Results ==<br />
<br />
Please enter your results on the [http://testdays.fedorainfracloud.org/events/13 result page]. The results will be transferred here after the Test Day is finished.<br />
<br />
<br />
<br />
<br />
<br />
[[Category:Fedora 25 Test Days]]</div>Kushalhttps://fedoraproject.org/w/index.php?title=Test_Day:2016_10_24_Cloud/App_Metadata&diff=477840Test Day:2016 10 24 Cloud/App Metadata2016-10-24T11:24:34Z<p>Kushal: Adding the real tests.</p>
<hr />
<div>= TestdayApp Metadata =<br />
* F25 Atomic / Cloud test day; https://fedoraproject.org/wiki/Test_Day:2016_10_14_Cloud<br />
<br />
<br />
<br />
== Basic Tests ==<br />
<br />
* Base startup; https://fedoraproject.org/wiki/QA:Testcase_base_startup<br />
* System logging; https://fedoraproject.org/wiki/QA:Testcase_base_system_logging<br />
* Services start; https://fedoraproject.org/wiki/QA:Testcase_Services_start<br />
* SELinux; https://fedoraproject.org/wiki/QA:Testcase_base_selinux<br />
* Service manipulation; https://fedoraproject.org/wiki/QA:Testcase_base_service_manipulation<br />
<br />
== Atomic Tests ==<br />
<br />
* Image boots; http://fedoraproject.org/wiki/User:Roshi/QA/AtomicTests/Atomic_Image_Boots<br />
* Upgrade works; http://fedoraproject.org/wiki/User:Roshi/QA/AtomicTests/Atomic_Upgrade<br />
* Rollback works; http://fedoraproject.org/wiki/User:Roshi/QA/AtomicTests/Atomic_Rollback<br />
<br />
== Docker tests ==<br />
* Docker install; https://fedoraproject.org/wiki/QA:Testcase_Docker_Install<br />
* Docker storage setup; https://fedoraproject.org/wiki/QA:Testcase_Docker_Storage_Setup<br />
* Docker daemon; https://fedoraproject.org/wiki/QA:Testcase_Docker_Daemon<br />
<br />
== More Atomic related tests ==<br />
<br />
* Atomic command; https://fedoraproject.org/wiki/QA:Testcase_Atomic_command<br />
* Atomic read only mounts; https://fedoraproject.org/wiki/QA:Testcase_Atomic_read_only_mounts<br />
* Atomic root mount; https://fedoraproject.org/wiki/QA:Testcase_Atomic_root_mount<br />
* Atomic tmp mount; https://fedoraproject.org/wiki/QA:Testcase_Tmp_Mount<br />
* Atomic tmp writable; https://fedoraproject.org/wiki/QA/Draft/Testcase_tmp_writable<br />
* Atomic journal written; https://fedoraproject.org/wiki/QA:Testcase_Journal_Written<br />
<br />
== Vagrant test ==<br />
* eth0 naming; https://fedoraproject.org/wiki/QA/Draft/Testcase_Vagrant_eth0_naming<br />
<br />
<br />
[[Category:TestdayApp]]</div>Kushalhttps://fedoraproject.org/w/index.php?title=Fedora_Meetup_Pune_August_2016&diff=468512Fedora Meetup Pune August 20162016-08-19T06:47:53Z<p>Kushal: /* Fedora Project Attendees */</p>
<hr />
<div>{{autolang|base=yes}}<br />
<br />
{{header|events}}<br />
<br />
= Fedora Meetup Pune August 2016 =<br />
<br />
== About ==<br />
<br />
This is Fedora Pune, India monthly meetup. We will discuss about Agenda and OpenSource project ideas discussed in last Meetup.<br />
<br />
== Location & Schedule ==<br />
<br />
Date: August 20, 2016 Timing: 2PM onwards<br />
<br />
K 104, Jasminium, Magarpatta City<br />
Pune. (Our regular Meetup location)<br />
<br />
Note: Please carry a valid ID proof to enter the building. If security guys ask, tell them you are coming to meet Sayan Chowdhury or Kushal Das. <br />
Emergency contact number: +91 8605430990<br />
<br />
== Agenda ==<br />
*Update on glibc documentation<br />
<br />
== Fedora Project Attendees ==<br />
<br />
Please add your name to the end of the list.<br />
<br />
{|<br />
! # !! Name <br />
|-<br />
| 1 || [[User:ganeshkadam | Ganesh Kadam]] <br />
|-<br />
| 2 || [[User:trishnag | Trishna Guha]] <br />
|-<br />
| 3 || [[User:Kushal | Kushal Das]] <br />
<br />
<br />
|}</div>Kushalhttps://fedoraproject.org/w/index.php?title=Flock_2016_Talks&diff=467566Flock 2016 Talks2016-08-16T10:41:39Z<p>Kushal: /* Wednesday 3 August 2016 */ adding my details</p>
<hr />
<div>== Tuesday 2 August 2016 ==<br />
<br />
{|<br />
! Talk !! Speaker(s) FAS ID !! Slides/Materials !! Recording !! Transcript<br />
<br />
|-<br />
| State of Fedora 2016 Keynote || [[User:Mattdm|mattdm]] || [https://mattdm.org/fedora/2016flock/StateofFedoraAugust2016-v160731a.pdf Slides] || || <br />
|-<br />
| Introducing Fedora Docker Layered Image Builds|| || [https://maxamillion.fedorapeople.org/Events/Flock2016/Flock2016_IntroducingDockerLayeredImageBuildService.pdf Slides] || || <br />
|-<br />
| Fedora with Amazon EC2 Container Service|| || || || [https://meetbot.fedoraproject.org/fedora-flock-matejko/2016-08-02/flock2016.2016-08-02-08.02.log.html Transcript]<br />
|-<br />
| Fedora Workstation Next Steps|| || || || <br />
|-<br />
| Localization (G11N)|| [[User:Noriko|noriko]] || [https://noriko.fedorapeople.org/flock-Localization-v2.0.pdf Slides] || || [https://meetbot.fedoraproject.org/fedora-flock-chelmonski/2016-08-02/flock2016.2016-08-02-08.02.log.html Transcript]<br />
|-<br />
| A year managing the Italian Fedora Community|| || || || <br />
|-<br />
| Getting new things into Fedora|| || || || [https://meetbot.fedoraproject.org/fedora-flock-monet/2016-08-02/flock2016.2016-08-02-09.06.log.html Transcript]<br />
|-<br />
| Introduction to Container Security|| || || || [https://meetbot.fedoraproject.org/fedora-flock-matejko/2016-08-02/flock2016.2016-08-02-08.59.log.html Transcript]<br />
|-<br />
| Towards an Atomic Workstation|| || || || [https://meetbot.fedoraproject.org/fedora-flock-canaletto/2016-08-02/flock2016.2016-08-02-09.00.log.html Transcript]<br />
|-<br />
| I contributed ! but, what now? || [[User:Aeng|aeng]] || || || [https://meetbot.fedoraproject.org/fedora-flock-openqa/2016-08-02/flock2016.2016-08-02-09.02.log.html Transcript]<br />
|-<br />
| The state of Fedora-Infra|| || || || <br />
|-<br />
| Low Hanging Fruits Hackfest|| || || || <br />
|-<br />
| Hacking Koji for Fun and Profit|| || || || <br />
|-<br />
| Packaging Chromium for Fedora|| || || || [https://meetbot.fedoraproject.org/fedora-flock-canaletto/2016-08-02/flock2016.2016-08-02-11.37.log.html Transcript]<br />
|-<br />
| State of the Fedora Server Union|| || || || <br />
|-<br />
| How to use personal kanban for better organization|| || [https://hguemar.fedorapeople.org/slides/personal-kanban/#1 Slides] || || [https://meetbot.fedoraproject.org/fedora-flock-openqa/2016-08-02/how_to_use_personal_kanban_for_better_organization.2016-08-02-11.42.log.html Transcript]<br />
|-<br />
| Python Packaging in Fedora|| [https://fedoraproject.org/wiki/User:pviktori pviktori] || [https://speakerdeck.com/encukou/python-packaging-in-fedora Slides] || || [https://meetbot.fedoraproject.org/fedora-flock-chelmonski/2016-08-02/flock2016.2016-08-02-11.30.log.html Transcript]<br />
|-<br />
| Containers in Production|| || || || [https://meetbot.fedoraproject.org/fedora-flock-matejko/2016-08-02/flock2016.2016-08-02-12.31.log.html Transcript]<br />
|-<br />
| Copr: What's new?|| msuchy, clime || [http://miroslav.suchy.cz/presentations/flock2016/copr/ Slides] || || [https://meetbot.fedoraproject.org/fedora-flock-monet/2016-08-02/flock2016.2016-08-02-12.30.log.html Transcript]<br />
|-<br />
| OpenPOWER and Open Source, How to Succeed|| || || || <br />
|-<br />
| Zanata - translation platform|| [[User:Aeng|aeng]] || [http://www.slideshare.net/AlexEng1/zanata-flock2016 Slides] || || [https://meetbot.fedoraproject.org/fedora-flock-chelmonski/2016-08-02/zanata.2016-08-02-13.22.log.html Transcript]<br />
|-<br />
| The Kernel Talk|| || || || <br />
|-<br />
| Application Containers and System Services|| || [https://hhorak.fedorapeople.org/2016/160802_application_containers_and_system_services.pdf Slides] || || <br />
|-<br />
| Fedora Magazine and what it teaches us about users || [[User:Pfrields|pfrields]] || || || [https://meetbot.fedoraproject.org/fedora-flock-openqa/2016-08-02/flock2016.2016-08-02-13.31.log.html Transcript]<br />
|-<br />
| Electronic/Robotics with Nodejs|| || || || [https://meetbot.fedoraproject.org/fedora-flock-chelmonski/2016-08-02/electronicrobotics_with_nodejs.2016-08-02-13.28.log.html Transcript]<br />
|-<br />
| Fedora Council Update & Town Hall|| || || || <br />
|-<br />
| Fedora SWAG|| [[User:eischmann|eischmann]] || [https://vps.eischmann.cz/nextcloud/index.php/s/V3tURb9uPhWDLkv slides] || || <br />
|-<br />
| Fedora's MirrorManager - now and the future|| || || || <br />
|-<br />
| Ensuring ABI stability in Fedora|| [[User:sinnykumari|sinnykumari]] , [[User:dodji|dodji]] || [https://sinnykumari.fedorapeople.org/slides/flock2016/abichecking-in-fedora.pdf Slides] || || <br />
|-<br />
| Fedora ARM state of the Union|| || || || [https://meetbot.fedoraproject.org/fedora-flock-picasso/2016-08-02/flock2016.2016-08-02-14.32.log.html Transcript]<br />
|-<br />
| Globalization audit of Fedora Atomic|| || || || <br />
|-<br />
| Thoughts on Fedora and Arts || [[UserLailah:lailah|lailah]] || || || [https://meetbot.fedoraproject.org/fedora-flock-openqa/2016-08-02/flock2016.2016-08-02-14.39.log.html Transcript]<br />
|-<br />
| Scaling containers for profit|| || || || <br />
|-<br />
| Mailman 3 and HyperKitty|| || || || <br />
|-<br />
| University Outreach – New task or new mindset? || [[User:Jflory7|jflory7]], [[User:Jonatoni|jonatoni]] || [https://jflory7.fedorapeople.org/pub/flock/2016/university-outreach/flock-2016-university-outreach-new-task-new-mindset-slides.pdf Slides] || || [https://meetbot.fedoraproject.org/fedora-flock-canaletto/2016-08-02/university_initiatives.2016-08-02-15.32.log.html Transcript]<br />
|-<br />
| Fedora sponsors|| msuchy || [http://miroslav.suchy.cz/presentations/flock2016/sponsors/ Slides] || || <br />
|-<br />
| Software Repository Management with Pulp|| ipanova || [https://drive.google.com/file/d/0B62BpJHFrMmZSzF2bDJpZ2RhcVE/view Slides] || || <br />
<br />
|}<br />
<br />
== Wednesday 3 August 2016 ==<br />
<br />
{|<br />
! Talk !! Speaker(s) FAS ID !! Slides/Materials !! Recording !! Transcript<br />
<br />
|-<br />
| Radosław Krowiak Co-owner, Akademia Programowania|| || || || <br />
|-<br />
| Continuous Integration and the Glorious Future|| || || || <br />
|-<br />
| Desktop security, keeping the keys to the castle|| || || || [https://meetbot.fedoraproject.org/fedora-flock-openqa/2016-08-03/desktop_security.2016-08-03-08.02.log.html Transcript]<br />
|-<br />
| GNOME Software: You'll Never Guess What Happens!|| || || || <br />
|-<br />
| Kirk, McCoy, and Spock build the future of Fedora || [[User:Mattdm|mattdm]] || || || <br />
|-<br />
| Fedora in the Classroom|| || || || [https://meetbot.fedoraproject.org/fedora-flock-monet/2016-08-03/flock2016.2016-08-03-08.01.log.html Transcript]<br />
|-<br />
| How to start a Fedora movement in a new country|| || || || <br />
|-<br />
| Modularity: Why, where we are, and how to get involved|| || || || [https://meetbot.fedoraproject.org/fedora-flock-picasso/2016-08-03/flock2016.2016-08-03-09.08.log.html Transcript]<br />
|-<br />
| Secure Automated Decryption|| || || || [https://meetbot.fedoraproject.org/fedora-flock-openqa/2016-08-03/secure,_automated_decryption.2016-08-03-08.59.log.html Transcript]<br />
|-<br />
| This is how we test Fedora now|| || || || <br />
|-<br />
| What's Fedora's alternative to vi httpd.conf?|| || || || <br />
|-<br />
| Bringing Developers into the Flock|| bex dustymabe|| [http://www.winglemeyer.org/bexelbie-talks-demos/Flock.2016.developers/ Slides] || || [https://meetbot.fedoraproject.org/fedora-flock-monet/2016-08-03/flock2016.2016-08-03-08.58.log.html Transcript]<br />
|-<br />
| Do you ship SELinux policy for your product?|| ||[http://lvrabec-selinux.rhcloud.com/wp-content/uploads/2016/08/slides-deck-6-7-9.html#/ Slides]|| ||<br />
|-<br />
| Factory 2.0 || [[User:Ralph|ralph]] || || || [https://meetbot.fedoraproject.org/fedora-flock-picasso/2016-08-03/flock2016.2016-08-03-11.30.log.html Transcript]<br />
|-<br />
| Fleet Commander: large desktop deployments for F24|| || || || [https://meetbot.fedoraproject.org/fedora-flock-canaletto/2016-08-03/flock2016.2016-08-03-11.25.log.html Transcript]<br />
|-<br />
| Integrating a Modular System: How Cockpit does it|| || || || <br />
|-<br />
| Don't Destroy Your Machine with Development|| || || || [https://meetbot.fedoraproject.org/fedora-flock-chelmonski/2016-08-03/flock2016.2016-08-03-11.30.log.html Transcript]<br />
|-<br />
| Nulecule - Packaging multi container applications|| || [https://docs.google.com/presentation/d/1RebFCxZ5ct3sgKLB4XEEU1fmHc6PcGAVuN5CVrGXtTg/edit?usp=sharing Slides] || || <br />
|-<br />
| docker in production|| || || || <br />
|-<br />
| IoT on Fedora|| || || || [https://meetbot.fedoraproject.org/fedora-flock-openqa/2016-08-03/flock2016.2016-08-03-12.32.log.html Transcript]<br />
|-<br />
| Using Fedora Atomic as workstation|| || || || [https://meetbot.fedoraproject.org/fedora-flock-canaletto/2016-08-03/flock2016.2016-08-03-12.29.log.html Transcript]<br />
|-<br />
| Diversity Panel: Building an inclusive community || [[User:Amsharma|amsharma]], [[User:Marinaz|marinaz]], [[User:Riecatnor|riecatnor]], [[User:Jonatoni|jonatoni]], [[User:Mattdm|mattdm]], [[User:Bee2502|bee2502]] || N/A || || <br />
|-<br />
| Globalization in Free Software Communities|| || || || <br />
|-<br />
| Living on the edge: Using rawhide day to day|| || || || <br />
|-<br />
| Progress on Enterprise Fedora Desktop|| || [http://talks.vda.li/2016/08/Flock/ Slides] || || [https://meetbot.fedoraproject.org/fedora-flock-canaletto/2016-08-03/flock2016.2016-08-03-13.27.log.html Transcript]<br />
|-<br />
| Testing Bleeding Edge Development Kernels|| || [http://www.paul-moore.com/blog/d/2016/08/flock-kernel-testing.html Slides] || || [https://meetbot.fedoraproject.org/fedora-flock-monet/2016-08-03/flock2016.2016-08-03-13.30.log.html Transcript]<br />
|-<br />
| Bugyou: Report bugs automatically from fedmsg|| || || || <br />
|-<br />
| Pagure: Past, Present and Future || [[User:Pingou|pingou]] || || || [https://meetbot.fedoraproject.org/fedora-flock-picasso/2016-08-03/flock2016.2016-08-03-13.33.log.html Transcript]<br />
|-<br />
| Rebases done easily with rebase-helper|| || || || <br />
|-<br />
| OS-level testing with openQA|| || || || <br />
|-<br />
| Diversity - women in open source|| [[User:Amsharma|amsharma]] || [https://speakerdeck.com/ami_117/women-in-opensource Slides] || || [https://meetbot.fedoraproject.org/fedora-flock-openqa/2016-08-03/flock2016.2016-08-03-14.36.log.html Transcript]<br />
|-<br />
| How we took care of spam || [[User:Puiterwijk|puiterwijk]] || || || [https://meetbot.fedoraproject.org/fedora-flock-monet/2016-08-03/flock2016.2016-08-03-14.39.log.html Transcript]<br />
|-<br />
| Realtime IRC chat on Fedora Hubs|| || [https://docs.google.com/presentation/d/1TUXh0vamc-ldUBGFw06tNzaxQLnqmL35f0Wk4q3jsAU/edit?usp=sharing Slides] || || <br />
|-<br />
| State of Raspberry/Pi in Fedora|| || || || [https://meetbot.fedoraproject.org/fedora-flock-chelmonski/2016-08-03/state_of_raspberrypi_in_fedora.2016-08-03-14.28.log.html Transcript]<br />
|-<br />
| Minimizing modules with Insim|| || || || <br />
|-<br />
| Redefing how we deliver Fedora|| || || || [https://meetbot.fedoraproject.org/fedora-flock-monet/2016-08-03/flock2016.2016-08-03-15.32.log.html Transcript]<br />
|-<br />
| Testing containers using Tunir|| [[User:Kushal|kushal]] || [https://kushaldas.in/talks/flock16 Slides] || || <br />
|-<br />
| Continuous security management via OpenSCAP Daemon|| || || || <br />
<br />
|}<br />
<br />
== Thursday 4 August 2016 ==<br />
<br />
{|<br />
! Talk !! Speaker(s) FAS ID !! Slides/Materials !! Recording !! Transcript<br />
<br />
|-<br />
| Lightning Talks || || || || [https://meetbot.fedoraproject.org/fedora-flock-picasso/2016-08-04/flock2016.2016-08-04-07.28.log.html Transcript]<br />
|-<br />
| Building A Fedora Containers Library|| || || || <br />
|-<br />
| Hands on building the Fedora Kernel|| || || || <br />
|-<br />
| Automation Workshop|| || || || <br />
|-<br />
| Hackfest: Fedora Docs Learn and Hack || bex || [http://www.winglemeyer.org/bexelbie-talks-demos/Flock.2016.docs/ Slides] || || <br />
|-<br />
| Meet your FAmSCo! || [[User:Cwickert|cwickert]], [[User:Gnokii|gnokii]], [[User:Giannisk|giannisk]], [[User:Mailga|mailga]] || || || [https://meetbot.fedoraproject.org/fedora-flock-picasso/2016-08-04/meet_your_famsco!_-_gnokii,_giannisk,_mailga,_cwickert.2016-08-04-08.05.log.html Transcript]<br />
|-<br />
| Fedora Badges Workshop|| || || || <br />
|-<br />
| One library to rule them all: unbundling workshop|| || || || <br />
|-<br />
| OpenShift on Fedora|| || || || <br />
|-<br />
| CommOps Workshop || [[User:Jflory7|jflory7]], [[User:Bee2502|bee2502]] || [https://jflory7.fedorapeople.org/pub/flock/2016/commops-workshop/flock-2016-commops-workshop-slides.pdf Slides] || || <br />
|-<br />
| Infrastructure workshop|| || || || <br />
|-<br />
| Building Modules Workshop|| || || || <br />
|-<br />
| G11N meetup|| || || || <br />
|-<br />
| PRD Workshop|| || || || <br />
|-<br />
| Design Clinic|| || || || <br />
|-<br />
| Fedora Loves Python || [[User:Churchyard|churchyard]] || [https://churchyard.fedorapeople.org/flock-2016-fedora-loves-python.pdf Slides] || || <br />
<br />
|}<br />
<br />
== Friday 5 August 2016 ==<br />
{|<br />
! Talk !! Speaker(s) FAS ID !! Slides/Materials !! Recording !! Transcript<br />
<br />
|-<br />
| Ansible best practice working session|| || || || <br />
|-<br />
| Bodhi Hackfest|| || || || <br />
|-<br />
| Fedora Security Lab|| || || || <br />
|-<br />
| Write AppStream metadata for add-ons|| || || || <br />
|-<br />
| Fedora Budget Workshop || [[User:Jzb|jzb]] || || || [https://meetbot.fedoraproject.org/fedora-flock-picasso/2016-08-05/flock2016.2016-08-05-08.14.log.html Transcript]<br />
|-<br />
| Fedora Hubs Meetup/Hackfest|| || || || [https://meetbot.fedoraproject.org/fedora-flock-openqa/2016-08-05/flock2016.2016-08-05-11.33.log.html Transcript]<br />
|-<br />
| 101 - Poster & Infographic Design|| || || || <br />
|-<br />
| Taskotron: Create automated, package-specific test|| || || || <br />
|-<br />
| What we do for Docker image test automation|| || || || <br />
|-<br />
| Server SIG Pow-Wow|| || || || <br />
|-<br />
| Haskell SIG meeting|| || || || <br />
|-<br />
| Wallpaper Hunt|| || || || <br />
<br />
|}<br />
<br />
----<br />
[[Category:Flock]]<br />
[[Category:Flock 2016]]</div>Kushalhttps://fedoraproject.org/w/index.php?title=F24_release_events&diff=467426F24 release events2016-08-14T09:51:14Z<p>Kushal: /* APAC */ adding pune event</p>
<hr />
<div>'''F24 Release Events are organized by Fedora Ambassadors and Contributors to celebrate the new release.'''<br />
<br />
=== Why join one? ===<br />
<br />
If you are a hobbyist, a student, a developer or a indomitable curious (or both), you will find information on the new release, demos, speeches and, at last but not least, friends ready to answer all your questions.<br />
<br />
If you are interested in contributing in Fedora, a Release Event it's the right place to meet contributors and have the possibility to ask them about their experience, and receive help to join our marvelous community! <br />
<br />
If you are still undecided, remember you are invited to take part in a party, with its fun and pleasure sides ;)<br />
<br />
== Upcoming Release Parties - Fedora 24 ==<br />
<br />
{{ Admon/note | When add / edit an event please sort adjust with the Date, make it easier to understand. }}<br />
<br />
=== LATAM ===<br />
<br />
{|style="t1" class="wikimedia sortable"<br />
|-<br />
!Date<br />
!Time<br />
!Location & Region<br />
!Owner<br />
!Event Name & Wikipage<br />
! Abstract<br />
!Event Reports<br />
|-<br />
| June 30th, 2016 || 20:00 || Chihuahua, Mexico|| [[user:Aacosta|Alejandro Acosta]], [[user:Ichavero|Ivan Chavero]] || [https://fedoraproject.org/wiki/Release_Party_F24_Chihuahua_MX Fedora 24 Release Party in Chihuahua, Mexico] || ||<br />
|-<br />
| 2nd July 2016 || 12:00 || Panama, Panama || [[user:potty|Abdel G. Martínez L.]] & [[user:josereyesjdi|Jose Reyes]]|| [https://fedoraproject.org/wiki/Release_Party_F24_Panama Fedora 24 Release Party in Panama, Panama] || ||<br />
* [http://www.abdelmartinez.com/2016/07/fedora-24-release-party-panama-report.html Abdel's Report]<br />
* [https://yoseft7.wordpress.com/2016/07/03/f24-release-party-pa/ Jose Reyes Report]<br />
|-<br />
| 2nd July 2016 || 10:00 || Sao Paulo, Brazil || [[user:Danielamorais|Daniela Morais]] & [[user:Ribeiro|Athos Ribeiro]] || [https://fedoraproject.org/wiki/Release_Party_F24_Sao_Paulo Fedora 24 Release Party in Sao Paulo, Brazil] || || <br />
* [https://rimolive.github.io/aprendendo-cloud-computing/2016/07/fedora-24-release-party by Ricardo Martinelli]<br />
* [http://athosribeiro.com/post/fedora24-rp-sp/ by Athos Ribeiro]<br />
* [http://danielammorais.com/2016/07/04/fedora-24-release-party-in-sao-paulo/ by Daniela Morais] <br />
|-<br />
| 5th July 2016 || 14:00 || Porto Alegre, Brazil || [[user:Mativi|Ana Mativi]] and [[user:itamarjp|Itamar Reis Peixoto]] || [https://fedoraproject.org/wiki/Release_Party_F24_Porto_Alegre Fedora 24 Release Party in Porto Alegre, Brazil] || ||<br />
* [https://anamativi.github.io/fedora/foss/2016/07/12/release-party-fedora-24-porto-alegre.html Mativi's Report]<br />
|-<br />
| 26 July 2016 || 9:30 || Managua, Nicaragua || [[user:espasmo|Fernando Espinoza]] ||[https://fedoraproject.org/wiki/Release_Party_F24_Managua_UCA Fedora 24 Release Party in Managua, Nicaragua] || ||<br />
|- ] || ||<br />
|-<br />
<br />
|}<br />
<br />
=== EMEA ===<br />
<br />
{|style="t1" class="wikimedia sortable"<br />
|-<br />
!Date<br />
!Time<br />
!Location & Region<br />
!Owner<br />
!Event Name & Wikipage<br />
!Abstract<br />
!Event Reports<br />
|-<br />
| 18th June 2016 || 12:00 || Novi Sad, Serbia || [[user:nmilosev|Nemanja Milosevic]] || [https://fedoraproject.org/wiki/Release_Party_F24_Novi_Sad Fedora 24 Release Party in Novi Sad, Serbia] || ||<br />
|-<br />
| 24th June 2016 || 19:00 || Brno, Czech Republic || [[user:frantisekz|Frantisek Zatloukal]] || [https://fedoraproject.org/wiki/Release_Party_F24_Brno Fedora 24 Release Party in Brno, Czech Republic] || ||<br />
|-<br />
| 25th June 2016 || 19:00 || Patras, Greece || [[user:keramidas|Vasilis Keramidas]] || [https://fedoraproject.org/wiki/Release_Party_F24_P-Space Release Party F24 @ P-Space] || ||<br />
|-<br />
| 9th July 2016 || 16:00 || Tirana, Albania || [[user:jonatoni|Jona Azizaj]] & [[user:elioqoshi|Elio Qoshi]] || [https://fedoraproject.org/wiki/Release_Party_F24_Tirana_Albania Fedora 24 Release Party in Tirana, Albania] || ||<br />
|-<br />
| 28th July 2016 || 18:00 || Prague, Czech Republic || [[user:frantisekz|Frantisek Zatloukal]] & [[user:churchyard|Miro Hrončok]] || [https://fedoraproject.org/wiki/Release_Party_F24_Prague Fedora 24 Release Party in Prague, Czech Republic] || || [http://www.etnetera.cz/blog/fedora-24-release-party Czech report]<br />
|-<br />
| 30th July 2016 || 9:00 || Ouagadougou, Burkina Faso || [[user:pandaconstantin|DRABO Constantin]] || [https://fedoraproject.org/wiki/Release_Party_F24_Ouagadougou_Burkina_Faso Fedora 24 Release Party in Ouagadougou, Burkina Faso] || ||<br />
|-<br />
| 3rd September 2016 || 14:00 || Paris, France || [[User:Nobrakal|Alexandre Moine]] & [[User:Eseyman|Emmanuel Seyman]] & [[User:Jibecfed|Jean-Baptiste Holcroft]] || [[Rencontres Fedora 24 à Universciences]] || ||<br />
|-<br />
|}<br />
<br />
=== NA===<br />
<br />
{|style="t1" class="wikimedia sortable"<br />
|-<br />
!Date<br />
!Time<br />
!Location & Region<br />
!Owner<br />
!Event Name & Wikipage<br />
! Abstract<br />
!Event Reports<br />
|-<br />
| 2nd July 2016 || 18:00 || Los Angeles, CA || [[user:lajuggler|Perry Rivera]] || [https://fedoraproject.org/wiki/SFVLUG/2016/Fedora_24_Release_Party SFVLUG Fedora 24 Release Party in Lake Balboa, CA, USA] || ||<br />
|-<br />
|}<br />
<br />
=== APAC ===<br />
<br />
{|style="t1" class="wikimedia sortable"<br />
|-<br />
!Date<br />
!Time<br />
!Location & Region<br />
!Owner<br />
!Event Name & Wikipage<br />
! Abstract<br />
!Event Reports<br />
|- <br />
|30th June 2016||8:00AM -1.00PM||[https://goo.gl/E1jEqt Padukka Sri Lanka]|| [[User:Nuwan600|Nuwan]] || [https://fedoraproject.org/wiki/Sri_Lanka_events/Fedora_24_Sri_Lanka_release_event ReleaseParty F24 Sri Lanka] || || [https://fedoraproject.org/wiki/Sri_Lanka_events/Fedora_24_Sri_Lanka_release_event Event report 01]<br />
|-<br />
|13rd August 2016||2:00-7:00PM||[https://goo.gl/maps/h67iHk8p8dx RUPP Phnom Penh]|| [[User:Leapsok|Leap SOK]] || [https://fedoraproject.org/wiki/Release_Party_F24_Phnom_Penh ReleaseParty F24 Phnom Penh] || ||<br />
|-<br />
|3rd July 2016||11:00AM-4:00PM||[https://goo.gl/maps/wfoMMbjQ9RA2 Bangalore, India]|| [[User:sumantrom|sumantrom]] || [https://fedoraproject.org/wiki/Release_Party_F24_Bangalore_India ReleaseParty F24 Bangalore] || ||<br />
|-<br />
|30th July 2016(TBD)||13:30 - 17:00 UTC+8 ||Beijing, China|| [[User:tonghuix|tonghuix]], [[User:zsun|zsun]]|| [[Release_Party_F24_Beijing]] || || [https://tonghuix.wordpress.com/2016/08/02/fedora-24-release-party-in-beijing/ Event Report]<br />
|-<br />
|9th July 2016||14:00 - 18:30 UTC+5:30 ||Pune, India|| [[User:kushal|kushal]], [[User:Sayanchowdhury| Sayan Chowdhury]]|| [[Release_Party_F24_Pune]] || || [https://kushaldas.in/posts/event-report-fedora-24-release-party-pune.html Event Report]<br />
|-<br />
|}</div>Kushalhttps://fedoraproject.org/w/index.php?title=Flock_2016_Lightning_Talks&diff=466651Flock 2016 Lightning Talks2016-08-02T14:00:08Z<p>Kushal: fixing syntax</p>
<hr />
<div>= Lightning Talks 2016 - 4 August 2016 @ 09:00 Local Time in Krakow, Poland = <br />
<br />
From 9 a.m. to 10 a.m. on Thursday, we will feature lightning talks as the morning plenary session. If you'd like to give a Lightning Talk, please sign up below. Note that slots are first-come, first-serve, and only 5 minutes each. Talks must be related to Fedora in some way, be audience-appropriate (family friendly, please), and '''no slides''' allowed. <br />
<br />
<br />
{|<br />
|- style=" color: #fff; background-color: #3074c2;" tablewidth="98%" <br />
| '''Slot''' || '''Topic''' || '''Speaker''' ||'''Description''' || '''Relevance to Fedora'''<br />
|-<br />
| 0 || Marketing: It's not a Spectator Sport! || [[User:jzb|Joe Brockmeier]] || How you ''yes, you'' can help with Fedora Marketing || [[Marketing]] <br />
|-<br />
| 1 || Provisioning OpenShift on Fedora on AWS || [[User:scollier|Scott Collier]] || What's it take to get OpenShift installed on AWS - distributed? || [[Cloud]]<br />
|-<br />
| 2 || Communicating About Community || [[User:Jflory7|Justin W. Flory]] || Doing something awesome in Fedora? Tell me more… we want to know what you're up to over on the [[Community Blog]]! || [[CommOps]] <br />
|-<br />
| 3 || Loopabull || [[User:Maxamillion|Adam Miller]] || Event loop driven Ansible playbook execution engine. || [[Infrastructure]] and [[ReleaseEngineering]]<br />
|-<br />
| 4 || dgplug summer training || [[User:Kushal|Kushal Das]] || Making new contributors in a distributed way || Community <br />
|-<br />
| 5 || TBD || TBD || TBD || TBD <br />
|-<br />
| 6 || TBD || TBD || TBD || TBD <br />
|-<br />
| 7 || TBD || TBD || TBD || TBD <br />
|-<br />
| 8 || TBD || TBD || TBD || TBD <br />
|-<br />
| 9 || TBD || TBD || TBD || TBD <br />
|-<br />
| 10 || TBD || TBD || TBD || TBD <br />
|-<br />
|}</div>Kushalhttps://fedoraproject.org/w/index.php?title=Flock_2016_Lightning_Talks&diff=466649Flock 2016 Lightning Talks2016-08-02T13:59:42Z<p>Kushal: Adding my dgplug talk</p>
<hr />
<div>= Lightning Talks 2016 - 4 August 2016 @ 09:00 Local Time in Krakow, Poland = <br />
<br />
From 9 a.m. to 10 a.m. on Thursday, we will feature lightning talks as the morning plenary session. If you'd like to give a Lightning Talk, please sign up below. Note that slots are first-come, first-serve, and only 5 minutes each. Talks must be related to Fedora in some way, be audience-appropriate (family friendly, please), and '''no slides''' allowed. <br />
<br />
<br />
{|<br />
|- style=" color: #fff; background-color: #3074c2;" tablewidth="98%" <br />
| '''Slot''' || '''Topic''' || '''Speaker''' ||'''Description''' || '''Relevance to Fedora'''<br />
|-<br />
| 0 || Marketing: It's not a Spectator Sport! || [[User:jzb|Joe Brockmeier]] || How you ''yes, you'' can help with Fedora Marketing || [[Marketing]] <br />
|-<br />
| 1 || Provisioning OpenShift on Fedora on AWS || [[User:scollier|Scott Collier]] || What's it take to get OpenShift installed on AWS - distributed? || [[Cloud]]<br />
|-<br />
| 2 || Communicating About Community || [[User:Jflory7|Justin W. Flory]] || Doing something awesome in Fedora? Tell me more… we want to know what you're up to over on the [[Community Blog]]! || [[CommOps]] <br />
|-<br />
| 3 || Loopabull || [[User:Maxamillion|Adam Miller]] || Event loop driven Ansible playbook execution engine. || [[Infrastructure]] and [[ReleaseEngineering]]<br />
|-<br />
| 4 || dgplug summer training || [[User:Kushal|Kushal Das || Making new contributors in a distributed way || Community <br />
|-<br />
| 5 || TBD || TBD || TBD || TBD <br />
|-<br />
| 6 || TBD || TBD || TBD || TBD <br />
|-<br />
| 7 || TBD || TBD || TBD || TBD <br />
|-<br />
| 8 || TBD || TBD || TBD || TBD <br />
|-<br />
| 9 || TBD || TBD || TBD || TBD <br />
|-<br />
| 10 || TBD || TBD || TBD || TBD <br />
|-<br />
|}</div>Kushalhttps://fedoraproject.org/w/index.php?title=Release_Party_F24_Pune&diff=465532Release Party F24 Pune2016-07-18T03:54:19Z<p>Kushal: /* Event Blogs */ Updated blogs</p>
<hr />
<div>{{autolang|base=yes}}<br />
<br />
{{header|events}}<br />
<br />
= Fedora 24 Release Party in Pune =<br />
<br />
This will be a event to knowing the new Fedora 24 features, learn about how contribute to free open source software and meet other Pune Fedora users. This is part of our monthly Pune Fedora meetup. We will have our regular technical discussions, and hands-on during this event too.<br />
<br />
== Date and Location ==<br />
July 9, 2016 at K-104 Jasminium, Magarpatta City, Pune (Our regular meet up location).<br />
2PM onward.<br />
<br />
== Activities ==<br />
* Presentation about Fedora 24 <br />
* Plan the future meetups in Pune<br />
<br />
== Event Owners ==<br />
<br />
* [[User:Kushal|Kushal Das]]<br />
* [[User:sayanchowdhury |Sayan Chowdhury]]<br />
<br />
== List of attendees ==<br />
<br />
* Your FAS ACCOUNT name/ Real name<br />
* [[user:suraj353|Suraj Narwade]]<br />
* [[user:satya4ever|Satyajit Bulage]]<br />
* [[user:niyaz|Niyaz Ansari]]<br />
* [[user:RahulBajaj|Rahul Bajaj]]<br />
* [[user:ganeshkadam|Ganesh Kadam]]<br />
* [[user:Kumarpraveen|Praveen Kumar]]<br />
* [[User:siddhesh|Siddhesh]]<br />
* [[User:amolkahat|Amol Kahat]]<br />
* [[User:Pnemade| Parag Nemade]]<br />
* [[User:komcy| Kamlesh Chaudhari]]<br />
* [[user:sverma|Sudhir Verma]]<br />
* [[user:amitg14|Amit Ghadge]]<br />
* [[user:neha10|Neha Shinde]]<br />
* [[user:sheshantkumbhar|Sheshant Kumbhar]]<br />
<br />
== Event Budget ==<br />
We will use the 50 USD for food and drinks. (Ticket is yet to be opened)<br />
<br />
== Event Blogs ==<br />
* [https://meganeshkadam.github.io/post/fedorapunemeetup/ Ganesh Kadam]<br />
* [https://kushaldas.in/posts/event-report-fedora-24-release-party-pune.html Kushal Das]</div>Kushalhttps://fedoraproject.org/w/index.php?title=Release_Party_F24_Pune&diff=460292Release Party F24 Pune2016-07-01T12:27:28Z<p>Kushal: /* Fedora 24 Release Party in Pune */</p>
<hr />
<div>{{autolang|base=yes}}<br />
<br />
{{header|events}}<br />
<br />
= Fedora 24 Release Party in Pune =<br />
<br />
This will be a event to knowing the new Fedora 24 features, learn about how contribute to free open source software and meet other Pune Fedora users. This is part of our monthly Pune Fedora meetup. We will have our regular technical discussions, and hands-on during this event too.<br />
<br />
== Date and Location ==<br />
July 9, 2016 at K-104 Jasminium, Magarpatta City, Pune (Our regular meet up location).<br />
2PM onward.<br />
<br />
== Activities ==<br />
* Presentation about Fedora 24 <br />
* Plan the future meetups in Pune<br />
<br />
== Event Owners ==<br />
<br />
* [[User:Kushal|Kushal Das]]<br />
* [[User:sayanchowdhury |Sayan Chowdhury]]<br />
<br />
== List of attendees ==<br />
<br />
* Your FAS ACCOUNT name/ Real name<br />
* [[user:suraj353|Suraj Narwade]]<br />
* [[user:satya4ever|Satyajit Bulage]]<br />
* [[user:niyaz|Niyaz Ansari]]<br />
* [[user:RahulBajaj|Rahul Bajaj]]<br />
* [[user:ganeshkadam|Ganesh Kadam]]<br />
* [[user:Kumarpraveen|Praveen Kumar]]<br />
<br />
== Event Budget ==<br />
We will use the 50 USD for food and drinks. (Ticket is yet to be opened)</div>Kushalhttps://fedoraproject.org/w/index.php?title=Release_Party_F24_Pune&diff=460289Release Party F24 Pune2016-07-01T12:14:14Z<p>Kushal: /* Fedora 24 Release Party in Pune */</p>
<hr />
<div>{{autolang|base=yes}}<br />
<br />
{{header|events}}<br />
<br />
= Fedora 24 Release Party in Pune =<br />
<br />
This will be a event to knowing the new Fedora 24 features, learn about how contribute to free open source software and meet other Pune Fedora users. This is part of our monthly Pune Fedora meetup. We will have our technical discussions, and hands-on during this event too.<br />
<br />
== Date and Location ==<br />
July 9, 2016 at K-104 Jasminium, Magarpatta City, Pune (Our regular meet up location).<br />
2PM onward.<br />
<br />
== Activities ==<br />
* Presentation about Fedora 24 <br />
* Plan the future meetups in Pune<br />
<br />
== Event Owners ==<br />
<br />
* [[User:Kushal|Kushal Das]]<br />
* [[User:sayanchowdhury |Sayan Chowdhury]]<br />
<br />
== List of attendees ==<br />
<br />
* Your FAS ACCOUNT name/ Real name<br />
* [[user:suraj353|Suraj Narwade]]<br />
* [[user:satya4ever|Satyajit Bulage]]<br />
* [[user:niyaz|Niyaz Ansari]]<br />
* [[user:RahulBajaj|Rahul Bajaj]]<br />
* [[user:ganeshkadam|Ganesh Kadam]]<br />
* [[user:Kumarpraveen|Praveen Kumar]]<br />
<br />
== Event Budget ==<br />
We will use the 50 USD for food and drinks. (Ticket is yet to be opened)</div>Kushalhttps://fedoraproject.org/w/index.php?title=Release_Party_F24_Pune&diff=459223Release Party F24 Pune2016-06-29T12:20:04Z<p>Kushal: /* Date and Location */</p>
<hr />
<div>{{autolang|base=yes}}<br />
<br />
{{header|events}}<br />
<br />
= Fedora 24 Release Party in Pune =<br />
<br />
This will be a event to knowing the new Fedora 24 features, learn about how contribute to free open source software and meet other Pune Fedora users <br />
<br />
== Date and Location ==<br />
July 9, 2016 at K-104 Jasminium, Magarpatta City, Pune (Our regular meet up location).<br />
2PM onward.<br />
<br />
== Activities ==<br />
* Presentation about Fedora 24 <br />
* Plan the future meetups in Pune<br />
<br />
== Event Owners ==<br />
<br />
* [[User:Kushal|Kushal Das]]<br />
* [[User:sayanchowdhury |Sayan Chowdhury]]<br />
<br />
== List of attendees ==<br />
<br />
* Your FAS ACCOUNT name/ Real name<br />
* [[user:suraj353|Suraj Narwade]]<br />
* [[user:satya4ever|Satyajit Bulage]]<br />
* [[user:niyaz|Niyaz Ansari]]<br />
<br />
== Event Budget ==<br />
We will use the 50 USD for food and drinks. (Ticket is yet to be opened)</div>Kushalhttps://fedoraproject.org/w/index.php?title=Release_Party_F24_Pune&diff=459006Release Party F24 Pune2016-06-28T11:40:43Z<p>Kushal: Adding the event page for the first time.</p>
<hr />
<div>{{autolang|base=yes}}<br />
<br />
{{header|events}}<br />
<br />
= Fedora 24 Release Party in Pune =<br />
<br />
This will be a event to knowing the new Fedora 24 features, learn about how contribute to free open source software and meet other Pune Fedora users <br />
<br />
== Date and Location ==<br />
July 9, 2016 at K-104 Jasminium, Magarpatta City, Pune (Our regular meet up location). <br />
<br />
<br />
<br />
== Activities ==<br />
* Presentation about Fedora 24 <br />
* Plan the future meetups in Pune<br />
<br />
== Event Owners ==<br />
<br />
* [[User:Kushal|Kushal Das]]<br />
* [[User:sayanchowdhury |Sayan Chowdhury]]<br />
<br />
== List of attendees ==<br />
<br />
* Your FAS ACCOUNT name/ Real name<br />
<br />
== Event Budget ==<br />
We will use the 50 USD for food and drinks. (Ticket is yet to be opened)</div>Kushalhttps://fedoraproject.org/w/index.php?title=Objectives/ProjectFAO&diff=457303Objectives/ProjectFAO2016-06-22T07:09:48Z<p>Kushal: /* More Details */ Fixing formatting</p>
<hr />
<div>{{admon/warning|DRAFT|This page is currently under construction and all information should be considered in draft form.}}<br />
<br />
== DRAFT Objective: Project FAO (Fedora + Atomic + OpenShift) ==<br />
<br />
Also known as: ''Codename Foosion''<br />
<br />
=== Goal ===<br />
<br />
The goal of this is to deliver a Fedora Atomic Host image that comes pre-enabled to run [https://www.openshift.org/ OpenShift Origin] in a multi-node cluster to enable Fedora users to easily deploy and maintain multi-node clustered services in a container-based solution.<br />
<br />
=== More Details ===<br />
<br />
At the [https://fedoraproject.org/wiki/FAD_Cloud_WG_2016 Fedora Cloud WG Activity Day 2016] it was discussed that the industry is moving towards a new paradigm of deploying software in Cloud environments and as such Fedora should be on the Leading Edge of that movement. The proposal was to refocus the primary deliverable of the [[Cloud | Fedora Cloud WG]] to be one based on [https://getfedora.org/en/cloud/download/atomic.html Fedora Atomic Host] and [https://www.openshift.org/ OpenShift Origin]. This will also come as an extension of the [[Changes/Layered_Docker_Image_Build_Service| Fedora Docker Layered Image]] work as we will want to enhance the guidelines for Docker Layered Image Maintainers to include the metadata required for deployment of software into an OpenShift environment (or [http://kubernetes.io/ Kubernetes], as the container orchestration engine OpenShift is built on).<br />
<br />
==== Notes from the [[FAD_Cloud_WG_2016|Fedora Cloud WG FAD 2016]] ====<br />
<br />
* Fedora/OpenShift Strategy<br />
** Several years ago was the Fedora.Next initiative<br />
** Three offerings: Workstation, Server, Cloud<br />
* Currently looking to refresh how we do Fedora Cloud<br />
** Came into meeting aiming for Fedora Atomic Host, but quickly came to consensus that that doesn't go far enough<br />
** Going "more grand"<br />
*** Fedora + OpenShift<br />
*** The aim of Fedora is to be the future of the platform, the goal of the platform is to run services and applications. The direction things are going tomorrow with services and applications is to run them in a container centric scaled out environment and the future of that in the opinion of the Fedora Cloud SIG is OpenShift. We believe Fedora + OpenShift is the future of "The Platform" for Cloud.<br />
** Things Fedora could be doing to be useful or helpful for OpenShift<br />
*** openshift-ansible - potentially a fork that's Fedora focused or maybe a branch<br />
**** Target OpenShift in containers, create an ansible playbook/roles that would deploy OpenShift in containers on Fedora Atomic Host<br />
*** source-to-image docker images based on Fedora content to deliver language runtime stacks<br />
*** Be a place to try out things like full container based deployments<br />
**** Such as installing OpenShift in Fedora Atomic Host by default as system containers, or via layered rpm (don't do in-docker)<br />
*** Add things that OpenShift could use to the layered image build system<br />
*** Fedora working an "Operating System" for the container<br />
**** minimization<br />
**** something like busybox (for the people who care)<br />
**** a rich and diverse userspace<br />
**** bridge between running systemd in a container<br />
***** what I really want to do is just launch a service<br />
*** Making it easier to package things under the Fedora banner<br />
*** Fedora, arguably, is best positioned for enabling continuous delivery<br />
**** although, there's much work to be done<br />
**** <walters> Could just deploy rpmdistro-gitoverlay *today* for Atomic Host content<br />
* Fedora Initiative for OpenShift Origin + Fedora<br />
** First taken as Fedora Incubator Project - First run PoC admiller, jberkus, walters, dmcphers (as a point of contact)<br />
*** Identify containers to build from Fedora rpms to host OpenShift Origin in a container deployment<br />
**** System containers for OpenShift Origin, not docker<br />
*** Deploy on Fedora Atomic Host<br />
**** 1 Master, 2 Nodes<br />
*** Automate with Ansible<br />
**** fork openshift-ansible, rip and replace as needed<br />
** Fedora Council official initiative once "graduated" from the Incubator Project<br />
** Codename: Project FOO (get Dave Grohl, he can be the project drummer so long as he isn't fighting us, or is at least fighting for us)<br />
*** Atomic Fusion (always 20 years away)<br />
*** Talk to Grant Shipley about this<br />
** previous message: https://lists.fedoraproject.org/pipermail/council-discuss/2015-September/013694.html<br />
<br />
=== Deliverables ===<br />
<br />
==== Proof of Concept ====<br />
<br />
We will initially target a proof of concept as discussed at the Fedora Cloud WD FAD.<br />
<br />
* First run PoC<br />
** admiller, jberkus, walters, dmcphers (as a point of contact)<br />
** Identify containers to build from Fedora rpms to host OpenShift Origin in a container deployment<br />
*** System containers for OpenShift Origin, not docker<br />
** Deploy on Fedora Atomic Host<br />
*** 1 Master, 2 Nodes<br />
** Automate with Ansible<br />
*** fork openshift-ansible, rip and replace as needed<br />
<br />
==== Objective Deliverables ====<br />
<br />
* Fedora Atomic Host<br />
** This already exists but we will need to work with upstreams to develop new technologies and make sure they are included in the Host images and the rpm-ostree repositories.<br />
* OpenShift running in an [https://github.com/projectatomic/atomic/issues/298 Atomic System Container]<br />
* [https://www.ansible.com/ Ansible] Playbooks do deploy and manage the system<br />
** Potentially an integration with [http://www.projectatomic.io/blog/2016/05/introducing_commissaire/ Commissaire]<br />
* Fedora Website or landing portal that offers documentation on how to quickly/easily install and run both the FAO environment but also multi-host containerized applications<br />
** Pre-existing examples that are "one-click" deploy is likely<br />
* Testing of the full solution as a sum of it's parts, including installation<br />
** Fedora Cloud WG will own this work, but will coordinate with [[QA|Fedora QA]].<br />
<br />
== Fedora Cloud Working Group ==<br />
<br />
This Objective is being driven through the Fedora Cloud Working Group and the Cloud WG will take ownership of the relevant work within Fedora but will also coordinate and collaborate with the various upstreams involved in order to drive relevant items in a collaborate way, out in the open. Details on specific items will be determined later and we will track work items in a [https://taiga.io/ Taiga] [https://en.wikipedia.org/wiki/Kanban Kanban] board here: http://taiga.fedorainfracloud.org<br />
<br />
== Objective Leads ==<br />
<br />
* [[User:Maxamillion|Adam Miller]]<br />
* [[User:Jberkus|Josh Berkus]]<br />
<br />
== Timeframe ==<br />
<br />
This is targeted for Fedora 26 as an official release item, but would like the freedom to operate under the Fedora Brand and an Incubator project in the mean time.<br />
<br />
== History ==<br />
<br />
FIXME</div>Kushalhttps://fedoraproject.org/w/index.php?title=FAD_Cloud_WG_2016&diff=449915FAD Cloud WG 20162016-06-08T15:46:42Z<p>Kushal: /* Attendees and Travel Details */ going out on 10th</p>
<hr />
<div>This is the main page for [[FAD]] Fedora Cloud Working Group 2016.<br />
<br />
== Purpose ==<br />
<br />
Our purpose is to complete the following '''primary''' goals:<br />
# Retrospective of Fedora 23 release for the Cloud/Atomic products. <br />
# Future of Automated Testing for Fedora Cloud/Atomic<br />
# Concrete Plan for Fedora Atomic Edition for F25.<br />
# Increase the Public Cloud Provider reach.<br />
# OpenShift Origin, and how to integrate in our cloud story (may be for contributors)<br />
# Alignment/Synergies for CentOS and Fedora Atomic hosts<br />
# Improvements in the Vagrant ecosystem<br />
<br />
== Objectives ==<br />
<br />
This FAD supports the following Fedora Objectives:<br />
<br />
* '''Be on the leading edge of free and open source technology''': through Atomic Edition and OSTree for os-level imaging and transactional upgrades<br />
* '''Fedora Editions''': further work on the Atomic Edition.<br />
* '''Fedora Modularization''': work on Cloud and Container support and layered images <br />
* '''Promote rapid adoption of new releases''': through containerization of version-sensitive libraries and stacks<br />
** also deal with Docker upgrade issues<br />
* '''Establish and implement technical standards for packages''': for containers, specifically Nulecule, Super Privileged Containers, and container security standards.<br />
<br />
== Diversity Statement ==<br />
<br />
We are aware that the State of North Carolina has passed recent laws which are not consistent with the Fedora Project's views on equality and diversity, and may make some attendees of the FAD uncomfortable. Both Red Hat and the Fedora Project are committed to providing a discrimination-free experience for attendees. Red Hat, the host of this FAD, will provide facilities appropriately regardless of gender, sexuality, religion or race.<br />
<br />
* [https://fedoraproject.org/wiki/Diversity Fedora Project Diversity Statement]<br />
* [https://twitter.com/JWhitehurst/status/712739076877582336 Statement by Jim Whitehurst]<br />
<br />
Regardless, if North Carolina's laws make you feel uncomfortable or unable to attend the FAD for any reason, or require changes to your travel arrangements, please contact either [mailto:jberkus@redhat.com Josh Berkus] or the Fedora Project diversity advisor, [mailto:tatica@fedoraproject.org Maria Leandro] with your concerns. All such contacts will be confidential.<br />
<br />
== Detailed Work Items & Final Attendees ==<br />
<br />
=== Communications ===<br />
<br />
We will be using the follow etherpad for notes, status and tracking work: https://public.etherpad-mozilla.org/p/FedoraCloud-WG-FAD-2016<br />
<br />
IRC communications will happen in #fedora-meeting-3 on irc.freenode.net<br />
<br />
There will be a bluejeans session here for video conferencing, link can be found in the etherpad above.<br />
<br />
=== Priorities ===<br />
<br />
==== Schedule ====<br />
<br />
The exact times for each item will be determined during the backlog grooming session. Times will be filled in then.<br />
<br />
Lunch is at 12:30ET each day.<br />
<br />
{|<br />
! Deliverable<br />
! Notes<br />
! Start Time<br />
! End Time<br />
|-<br />
!colspan="4"| Tuesday 2016-06-07<br />
|-<br />
| <!-- Deliverable --> Morning festivities and backlog creation<br />
| <!-- Notes --> Say hello, get coffee, go over agenda, prioritize tasks, create a backlog for the day<br />
| <!-- Start Time --> 8:00am<br />
| <!-- End Time --> 9:00am<br />
|-<br />
| <!-- Deliverable --> Documentation Hackathon<br />
| <!-- Notes --><br />
| <!-- Start Time --> 9:00am<br />
| <!-- End Time --> 11:00am<br />
|-<br />
| <!-- Deliverable --> Automated Testing<br />
| <!-- Notes --> Atomic Host and Layered Image Build Testing design<br />
| <!-- Start Time --> 11:00am<br />
| <!-- End Time --> 12:30am<br />
|-<br />
| <!-- Deliverable --> Atomic Edition<br />
| <!-- Notes --> A Fedora 25 change proposal outlining switch to Atomic and how it will affect websites, releng, docs, and so on. <br />
| <!-- Start Time --> 1:30pm<br />
| <!-- End Time --> 3:30pm<br />
|-<br />
| <!-- Deliverable --> Docker + Registry<br />
| <!-- Notes --> Docker and Registry decisions can be co-dependent, combining the time slots<br />
| <!-- Start Time --> 3:30pm<br />
| <!-- End Time --> 5:30pm<br />
|-<br />
!colspan="4"| Wednesday 2016-06-08<br />
|-<br />
| <!-- Deliverable --> Vagrant<br />
| <!-- Notes --> Improvements for Vagrant for F25 time frame <br />
| <!-- Start Time --> 9:00am<br />
| <!-- End Time --> 11:00am<br />
|-<br />
| <!-- Deliverable --> Fedora Cloud Base Image Monthly <br />
| <!-- Notes --> Scope and define what is needed to implement monthly release of the Fedora Cloud Image (base image)<br />
| <!-- Start Time --> 11:00am<br />
| <!-- End Time --> 11:30pm<br />
|-<br />
| <!-- Deliverable --> Public Cloud Provider Outreach<br />
| <!-- Notes --> How can we increase our public cloud footprint? <br />
| <!-- Start Time --> 11:30am<br />
| <!-- End Time --> 12:30pm<br />
|-<br />
| <!-- Deliverable --> Hackathon<br />
| <!-- Notes --> Work on action items that we establish<br />
| <!-- Start Time --> 3:30pm<br />
| <!-- End Time --> 5:00pm<br />
|-<br />
| <!-- Deliverable --> Event Report for CommOps Blog<br />
| <!-- Notes --> Collective write up of work done at the FAD<br />
| <!-- Start Time --> 5:00pm<br />
| <!-- End Time --> 5:30pm<br />
|-<br />
|}<br />
<br />
=== Deliverables ===<br />
<br />
# Automated testing<br />
#* Atomic Host Tests<br />
#* Plan for CI builds/testing for Host/OStree<br />
#* Deliverables: Decide upon the blocking tests for Atomic hosts, and for layered image builds<br />
# Atomic Edition<br />
#* Deliverables<br />
#** A Fedora 25 change proposal outlining switch to Atomic and how it will affect websites, releng, docs, and so on.<br />
#** List of other potential changes for Atomic in F25 timeframe.<br />
#** Update the PRD for Atomic/Container universe. (May not complete at FAD, but identify sections which need work.)<br />
#** Proposal to Council for new deliverable and updated PRD.<br />
# Docker<br />
#* As of version 1.10, it has become necessary for us to support multiple versions of Docker in our repo, as new versions are not backwards-compatible. This requires deciding:<br />
#** Which versions will we offer?<br />
#** What will the packaging look like? Will we follow RHEL's lead with Docker-1.9 and Docker-Next?<br />
#** Does this affect packaging/versions for runc?<br />
#* Deliverables: plan for packaging and supporting different versions of Docker in Fedora.<br />
# Registry<br />
#* Public Atomic Registry for Fedora: It is now possible for us to have a dedicated Fedora container registry. We need to figure out:<br />
#** Feasibily of doing so<br />
#** Build pipeline for images<br />
#** Hosting: OK to have CentOS host this?<br />
#** Requirements for accounts, official images only or open to all project members?<br />
#* Deliverables: either decision not to run a registry, or a workable plan for maintaining and governing one.<br />
# Documentation<br />
#* At least one F24-focused runbook.<br />
# Event report for Community Blog<br />
#* Need to produce one or more reports for the larger group / project to follow along with results of the FAD<br />
# Vagrant<br />
#* Improvements for Vagrant for F25 time frame<br />
#** More Box types (hyperv, vmware, etc)<br />
#** remote providers (DigitalOcean, OpenStack, AWS, etc)<br />
#* Deliverables: decide on items to concentrate on for F25 time frame<br />
# Public Cloud Provider Outreach<br />
#* How can we increase our public cloud footprint?<br />
#** Support in more cloud providers (GCE, Azure, other)<br />
#* Deliverables: Decide on providers to target, Identify blockers in the process.<br />
<br />
=== Attendees and Travel Details ===<br />
{|<br />
! Contributor !! Arrival !! Departure !! Roommate !! Need Travel Funding? || Budget amount for travel || Food Restrictions<br />
|-<br />
| Josh Berkus || Jun 6 || Jun 9 || - || No || || Non-meat (fish OK)<br />
|-<br />
| Matthew Miller || Jun 6 || Jun 9 || - ||No || ||<br />
|-<br />
| Scott Collier || Not sure yet || Also not sure yet || - ||No || ||<br />
|-<br />
| [[User:dustymabe|Dusty Mabe]] || Jun 6 || Jun 8 (late) || - || No || ||<br />
|-<br />
| [[User:jzb|Joe Brockmeier]] || Lives Here || Lives Here || Heck No || No || ||<br />
|-<br />
| [[User:Maxamillion|Adam Miller]] || Jun 6 || Jun 9 || [[User:Kushal|Kushal Das]] || Yes || $1000 ($450 Hotel, $400 Flight<br />$50 To/From Airport, $100 Food) ||<br />
|-<br />
| [[User:Kushal|Kushal Das]] || June 6th || June 10th || - || Yes || $1050 ($450 Hotel, $450 Flight, $50 To/From Airport)<br />(I hope food will be taken care by in total). ||<br />
|-<br />
| [[User:Tflink|Tim Flink]] || June 6th || June 9th || None, need to find one || Yes || || Vegetarian<br />
|-<br />
| [[User:jasonbrooks|Jason Brooks]] || Jun 6 || Jun 9 || - || No || ||<br />
|-<br />
| [[User:jsmith|Jared Smith]] || Jun 6 || Jun 8 (early) || None || No || None ||<br />
|-<br />
| [[User:decause| Remy DeCausemaker]] || Jun 6 || June 10th || - ||No || ||<br />
|-<br />
| Steve 'Ashcrow' Milner || Local || Local || No ||No || None ||<br />
|-<br />
| [[User:Rbarlow|Randy Barlow]] || Local || Local || - || No || - || None<br />
|-<br />
|}<br />
<br />
<br />
{|<br />
! Remote attendees !! TimeZone<br />
|-<br />
| [[User:bex|Brian Exelbierd]] || Europe/Prague UTC+2<br />
|-<br />
| [[User:walters|Colin Walters]] || US/EST UTC-4<br />
|}<br />
<br />
<!-- <br />
<br />
== Planning Prerequisites ==<br />
<br />
See the [[How to organize a FAD]] list; you can keep your to-do list here.<br />
<br />
* Work out budget<br />
* <strike>Decide on Dates and Location</strike><br />
* Arrange Facilities<br />
* List Resources<br />
* Be Somewhat Structured<br />
* Arrange Lodging<br />
* Arrange Refreshments<br />
* Arrange a Social Event<br />
<br />
--><br />
<br />
== Plan ==<br />
# '''Location:''' Red Hat, Raleigh, NC USA<br />
# '''Room''' Red Hat Annex, "Red Rover" room<br />
# '''Date:''' Jun-07 to Jun-08<br />
<br />
== Social ==<br />
<br />
At this point, we are planning a full team dinner for Tuesday night. Wednesday night is TBD.<br />
<br />
== Logistics ==<br />
'''Snacks/Beverages:''' <br />
<br />
'''Breakfast:'''<br />
* Covered at hotel<br />
<br />
'''Lunch:'''<br />
* Days other than Tue/Wed/ to be covered by attendees.<br />
* Tue: Order in, cost covered (est. $125)<br />
* Wed: Order in, cost covered (est. $125)<br />
<br />
'''Dinner:'''<br />
* Days other than Tue/Wed to be covered by attendees<br />
* Tue: Team @ local venue (est. $300)<br />
* Wed: Team @ local venue (est. $300)<br />
<br />
'''Total food: est. $850'''<br />
<br />
== Travel estimates ==<br />
<br />
{|<br />
! Contributor !! Taxi/transport (to/from home) !! Airfare !! Hotel !! Taxi/transport (to/from site) !! Parking !! Add Meals !! Other <br />
|-<br />
| [[User:Tflink|tflink]] || 0 || USD 320 || USD 450 || USD 40 || USD 50 || USD 40 ||<br />
|-<br />
| [[User:Maxamillion|Adam]] || $50 || $400 || $450 || $40 || || $100 ||<br />
|-<br />
| Kushal || $50 || $450 || Shared || $40 || || $50 ||<br />
|-<br />
|}<br />
<br />
<br />
# '''Space:'''<br />
#* $0 if Supplied by Red Hat<br />
# '''Supplies:'''<br />
#* N/A<br />
# '''Food:''' $850 (from above)<br />
<br />
''Total budget: $3380''<br />
<br />
== Hotel and Local Travel ==<br />
<br />
There are two hotels for this venue:<br />
<br />
* [http://www.marriott.com/hotels/travel/rdumc-raleigh-marriott-city-center/ RALEIGH MARRIOTT CITY CENTER]<br />
* [http://www.sheratonraleigh.com/ SHERATON RALEIGH HOTEL]<br />
<br />
Red Hat employees should book these through global travel. Non-RH staff should contact [mailto:jberkus@redhat.com the FAD organizer] about getting access to corporate discounts.<br />
<br />
Both hotels are walking distance to the venue (3 blocks). We do not recommend renting a car in Raleigh, as parking is costly and a car is not needed downtown. Instead, take a rideshare or taxi from the airport to the hotel; coordinate with other attendees so that you can split fares. Rideshare compaines (Lyft, Uber, etc.) are significantly cheaper than a taxi ($20 to $25).<br />
<br />
[[Category:FAD]]</div>Kushalhttps://fedoraproject.org/w/index.php?title=Fedora_24_talking_points&diff=448030Fedora 24 talking points2016-05-27T17:18:39Z<p>Kushal: /* Fedora Workstation */ adding the support for microbit</p>
<hr />
<div>{{admon/caution|DISCUSSION DRAFT|This is a draft only for discussion. This is not a final set of talking points, nor are all of the features listed here complete at the time of this draft. ''Please do a reality check before using these talking points as anything other than a discussion draft!''}}<br />
<br />
These are the [[Talking Points]] for the Fedora 24 release. For information on how these talking points were chosen, see [[Talking Points SOP]]. They are intended to help [[Ambassadors]] quickly present an overview of highlighted features when talking about the release, and to help drive content for the release, etc.<br />
<br />
The talking points are based in part on the [[Releases/24/ChangeSet|Change Set]] for this release.<br />
<br />
== Overall Release Story == <br />
<br />
<br />
== Fedora-Wide Changes and Improvements ==<br />
<br />
* GNOME now has 3.20 <br />
** More inline with upstream <br />
** System upgrades use dnf system-upgrade logic -- reducing the reboot failure and gdm instabilities known to come with some upgrades<br />
** Cantarell fonts improved<br />
** Updates / Improvements for Mouse & Touchpad Users<br />
** Gtk+ theming enhancements (CSS)<br />
** Addition of `Shortcut windows`<br />
* Glibc moves to 2.23<br />
** Updating is more automated and verbose in the 'what was updated' info dialog<br />
** This automation is also removing much of the security and bugfix update runs for glibc as it is pulled in natively like a dnf update would. <br />
** Allows for better tooling with things like pungi and koji.<br />
* Pungi refactor <br />
** Faster builds -- partly due to a full build kick-off<br />
** More frequent builds -- allowing for nightlies (qa / releng) to match more closely the RC (qa / releng / test-days)<br />
** Streamlining and ensuring Fedora build templates seamlessly cross compose for / on RHEL<br />
** Allows for better / more logging of builds (more transparent as well)<br />
** Allowing for install_tree builds for all supported variants / releases resulting in a working result build ( cold or live media)<br />
** Much cleaner / understandable switches ( --ksurl, repo, repo_from, etc )<br />
** Allowing for making koji the compose 'farm' <br />
* Langpacks now have metapackages<br />
** Allows per-language install Greatly reducing payload downloads and allowing much more granular control of installed langpacks<br />
* Node.js has been updated to version 4.4.4<br />
** New and great version of the popular server-side JavaScript engine.<br />
<br />
== Fedora Cloud ==<br />
<br />
Overall message for Fedora 24 release cycle: The Fedora Cloud Working Group is focusing on "cloud native" applications and infrastructure, from top to bottom. We're focusing on Atomic Host for running containerized applications, putting energy into providing a better developer experience around Atomic Host, and enabling developers to use OpenShift Origin on Fedora / Fedora Atomic Host. <br />
<br />
A reminder that Fedora Atomic Host is released on a two-week cadence, barring any show-stopping bugs. While the Atomic Host still roughly tracks Fedora 24 development, we have the ability to push out releases quickly and allow users to get the most recent Docker, Kubernetes, ''etc''. ahead of the normal Fedora release cycle.<br />
<br />
* '''OpenShift Origin for Fedora''': We want to enable a "full stack" experience for folks to run the OpenShift Origin Platform-as-a-Service on Fedora and Fedora Atomic Host. We've packaged Origin so Fedora users can spin it up and get started working with containerized applications in Origin.<br />
<br />
* '''Developer Mode for Fedora Atomic Host''': Using "developer mode" for Fedora Atomic Host obviates the need for a cloud-init data source, and gives a better developer experience overall. When running in '''[https://fedoraproject.org/wiki/Changes/Atomic_Developer_Mode Developer Mode]''', the host will download and start Cockpit and fire up a '''tmux''' session to make it easier to work at the console and obtain necessary inforamation (like the root password, IP address, etc.).<br />
<br />
<br />
<br />
See this ticket: https://fedorahosted.org/cloud/ticket/143<br />
<br />
Tracking features that will make it into the Alpha. From there we'll create the basic points.<br />
<br />
The overall "story" for Fedora Cloud this cycle is continuing work on container technologies for cloud environments. Most of the wood behind the arrow this cycle is going to be for Fedora Atomic Host and running OpenShift Origin on top of Fedora.<br />
<br />
== Fedora Server ==<br />
<br />
* '''New partitioning scheme''': The new partitioning scheme for Fedora Server is designed to be more in line with a server deployment, and further differentiate the server edition from other editions of Fedora.<br />
** Allowing for use of cockpit for to allocate 'free space' and not have to allocate the full VG at install.<br />
<br />
* '''Reducing the footprint of the Server edition''': More packages have been removed from the default Server edition in order to make the footprint of the default installation smaller.<br />
<br />
* '''FreeIPA 4.3''': A new version of FreeIPA (Domain Controller role) is included in Fedora 24. Version 4.3 of FreeIPA includes a number of new features that helps streamline installation of replicas by adding a replica promotion method for new installs. A new topology plugin has also been added that automatically manages new replication segment creation. A very effective replica topology visualization tool is also available in the webUI.<br />
<br />
== Fedora Workstation ==<br />
<br />
* '''Wayland''' - The new display technology to replace the aging X is ready for daily use. Although Wayland hasn't reached 100% feature parity with X, developers have covered most use cases and made it a reliable option. Wayland brings better HiDPI support for multiple monitors, tear-free video playback, significantly improved security due to app isolation on the display server level, and lots of potential for the future.<br />
<br />
* '''Graphical Upgrades''' - Upgrading your OS is now easy with Software. No need to use a CLI tool to upgrade your Fedora to the newest release. You'll be notified once the new release is available, and you can start the upgrade process from the "Updates" section in Software.<br />
<br />
* '''Flatpak support''' - [http://jimmac.github.io/xdg-app-website/ Flatpak] provides a new way to package apps for Linux distributions. Flatpaks run in a sandbox and independently on the underlying system. They're more secure and don't depend on particular versions of libraries in your system. The flatpak tool was available in previous releases of Fedora as xdg-app, but now it's integrated in Software where you can easily manage Flatpaks. GNOME already provides a repository with Flatpaks, and other upstream projects will soon. Want the newest version of your favorite app? With Flatpak, it won't be a problem!<br />
<br />
* '''Reviews in Software''' - The Software tool for managing your apps now supports user reviews. Now it's easier than ever to choose the right app for your need.<br />
<br />
* '''Improvements in Shell''' - The GNOME Shell has also received a couple of handy improvements: Music controls have been added to the calendar drop down, above the calendar list. It uses MPRIS so lots of media players are supported. A hidden setting to show the battery percentage has been added, replacing four existing extensions. For systems that cannot detect whether a headset, headphones or a microphone is getting plugged in, a new dialog in the Shell configures the jack properly. Keyboard keys to disable Wi-Fi or Bluetooth are now supported out of the box.<br />
<br />
* '''QGnomePlatform''' - This new addition to Workstation improves integration of GTK and Qt worlds by synchronizing settings. In Fedora 24, it supports font settings. If you change font settings in GNOME Tweak Tool, the change will be reflected in Qt applications, too. No need to change it in two different places anymore.<br />
<br />
* '''Redesigned Printer Job Dialog & Mouse and Touchpad Settings''' - The dialog to manage printer jobs has been redesigned and is easier to use. The Mouse and Touchpad Settings have also been redone. Among other improvement, you'll only see relevant settings to you, meaning those supported by your device. <br />
<br />
* '''Font Improvements''' - The default font, Cantarell, has received major improvements. Language coverage has been brought up almost to [https://github.com/adobe-type-tools/adobe-latin-charsets Adobe Latin 4] and [https://github.com/adobe-type-tools/adobe-cyrillic-charsets Adobe Cyrillic 2]. For example, Vietnamese is fully supported now. Hinting has also been tweaked so the font is more legible and useful.<br />
<br />
* '''BBC Microbit support''' - Fedora now supports [https://www.microbit.co.uk/ BBC Microbit] devices using the [https://fedoraproject.org/wiki/Changes/Micro_Bit mu IDE]. <br />
<br />
* '''Application Improvements:'''<br />
** '''Shortcuts Windows''' - 18 GNOME apps have received a window that shows an overview of keyboard shortcuts and multitouch gestures available for the application. Just hit Control-F1 or Control-? to open the window.<br />
** '''New Search UI in Files''' - The Files browser (aka Nautilus) has a new interface for search filters. It now uses a popover and is more intuitive.<br />
** '''LibreOffice 5.1''' - A new major release of this popular office suite comes with many improvements across all its apps. As always, the document format compatibility has been significantly improved. LO now supports import of Gnumeric, Microsoft Write (.wri), and Apple Keynote 6 documents. There are many improvements in export and import filters for OOXML, MS Visio, and Corel Draw files. There have also been refinements in the user interface, such as reorganization of the main menu in Writer, Calc, and Impress. All OpenGL transitions in Impress have been ported to OpenGL 2.1+, which removes support for very old graphics processors, but allows better usage of modern ones. Four new transitions have been added which require OpenGL 3.2+ that exploit these new available features. LibreOffice in Fedora 24 has also switched to GTK+ 3 by default which gives it a more native look, and the ability to run natively on Wayland.<br />
** '''Native LO document support in Documents''' - Documents now natively support LibreOffice documents through the LibreOfficeKit widget.<br />
** '''Automatic Initial Snapshots in Boxes''' - Boxes now automatically makes a snapshot of a VM installation, so you can reset your VMs at any time and return to the initial state.<br />
** '''Eclipse Neon''' - A major new release of the Eclipse IDE will ship with Fedora 24. See the upstream "New and Noteworthy" document for the core platform and Java tooling: https://www.eclipse.org/eclipse/news/4.6/<br />
<br />
== Spins ==<br />
<br />
<br />
[[Category:Marketing]] [[Category:Talking points]] [[Category:F24]]</div>Kushalhttps://fedoraproject.org/w/index.php?title=Test_Day:2016_05_10_Cloud&diff=446350Test Day:2016 05 10 Cloud2016-05-12T06:10:50Z<p>Kushal: /* Test Results */ Updated test results</p>
<hr />
<div>{{Infobox_group<br />
| name = Fedora Test Day<br />
| image = [[File:Echo-testing-48px.png|link=QA/Test Days]]<br />
| caption = [[Fedora Cloud Test day]]<br />
| date = 2016-05-10<br />
| time = all day<br />
| website = [[QA/Test Days]]<br />
| irc = [irc://irc.freenode.net/#fedora-test-day #fedora-test-day] ([http://webchat.freenode.net/?channels=fedora-test-day webirc])<br />
| fedora_mailing_list = test<br />
}}<br />
<br />
{{admon/note | Can't make the date? | If you come to this page before or after the test day is completed, your testing is still valuable, and you can use the information on this page to test, file any bugs you find at [http://bugzilla.redhat.com Bugzilla], and add your results to the results section. If this page is more than a month old when you arrive here, please check the [[QA/Test_Days|current schedule]] and see if a similar but more recent Test Day is planned or has already happened.}}<br />
<br />
== What to test? ==<br />
<br />
Today's installment of Fedora Test Day will focus on '''Cloud, Atomic Host''' images for Fedora 24.<br />
<br />
== Who's available ==<br />
<br />
The following cast of characters will be available testing, workarounds, bug fixes, and general discussion ...<br />
* Development - [[User:Kushal|Kushal]] (kushal)<br />
* Quality Assurance - [[User:lbrabec|Lukas Brabec]] (lbrabec), [[User:pschindl|Petr Schindler]] (pschindl)<br />
<br />
== Prerequisite for Test Day == <br />
<br />
You will require at least a system with libvirt/kvm installed. Having access to any Openstack or other Cloud IAAS system where you can upload an image will be even better.<br />
<br />
Download the images from below links<br />
<br />
* [https://kojipkgs.fedoraproject.org/compose/branched/Fedora-24-20160509.n.1/compose/CloudImages/x86_64/images/Fedora-Cloud-Base-24-20160509.n.1.x86_64.qcow2 Cloud Image QCOW2]<br />
* [https://kojipkgs.fedoraproject.org/compose/branched/Fedora-24-20160509.n.1/compose/CloudImages/x86_64/images/Fedora-Atomic-24-20160509.n.1.x86_64.qcow2 Atomic Host Image QCOW2]<br />
<br />
* [https://kojipkgs.fedoraproject.org/compose/branched/Fedora-24-20160509.n.1/compose/CloudImages/x86_64/images/Fedora-Cloud-Base-Vagrant-24-20160509.n.1.x86_64.vagrant-virtualbox.box Vagrant Virtualbox cloud base]<br />
* [https://kojipkgs.fedoraproject.org/compose/branched/Fedora-24-20160506.n.0/compose/CloudImages/x86_64/images/Fedora-Atomic-Vagrant-24-20160506.n.0.x86_64.vagrant-virtualbox.box Vagrant Virtualbox Atomic]<br />
<br />
List of AMIs <br />
<br />
{|<br />
|-<br />
! Image Name<br />
! AMI id<br />
! Destination<br />
! Virt type <br />
! Vol type<br />
|-<br />
| Fedora-Cloud-Base-24-20160509.n.1.x86_64 || ami-639de403 || EC2 (us-west-1) || paravirtual || standard <br />
|-<br />
| Fedora-Cloud-Base-24-20160509.n.1.x86_64 || ami-d6d7fbb5 || EC2 (ap-southeast-2) || hvm || standard <br />
|-<br />
| Fedora-Cloud-Base-24-20160509.n.1.x86_64 || ami-7c31dc11 || EC2 (us-east-1) || hvm || standard<br />
|-<br />
| Fedora-Cloud-Base-24-20160509.n.1.x86_64 || ami-f9d1fd9a || EC2 (ap-southeast-2) || hvm || gp2 <br />
|-<br />
| Fedora-Cloud-Base-24-20160509.n.1.x86_64 || ami-5d9be23d || EC2 (us-west-1) || hvm || standard<br />
|- <br />
| Fedora-Cloud-Base-24-20160509.n.1.x86_64 || ami-2bfa074b || EC2 (us-west-2) || paravirtual || gp2 <br />
|-<br />
| Fedora-Cloud-Base-24-20160509.n.1.x86_64 || ami-36855355 || EC2 (ap-southeast-1) || paravirtual || gp2 <br />
|-<br />
| Fedora-Cloud-Base-24-20160509.n.1.x86_64 || ami-6d36db00 || EC2 (us-east-1) || hvm || gp2 <br />
|-<br />
| Fedora-Cloud-Base-24-20160509.n.1.x86_64 || ami-12c4297d || EC2 (eu-central-1) || paravirtual || gp2 <br />
|-<br />
| Fedora-Cloud-Base-24-20160509.n.1.x86_64 || ami-a307e3c2 || EC2 (ap-northeast-1) || paravirtual || standard <br />
|-<br />
| Fedora-Cloud-Base-24-20160509.n.1.x86_64 || ami-bb9de4db || EC2 (us-west-1) || hvm || gp2 <br />
|-<br />
| Fedora-Cloud-Base-24-20160509.n.1.x86_64 || ami-643db408 || EC2 (sa-east-1) || paravirtual || standard <br />
|-<br />
| Fedora-Cloud-Base-24-20160509.n.1.x86_64 || ami-5e27ae32 || EC2 (sa-east-1) || hvm || standard <br />
|-<br />
| Fedora-Cloud-Base-24-20160509.n.1.x86_64 || ami-7f00e41e || EC2 (ap-northeast-1) || hvm || standard <br />
|-<br />
| Fedora-Cloud-Base-24-20160509.n.1.x86_64 || ami-4fe76d3c || EC2 (eu-west-1) || paravirtual || standard <br />
|-<br />
| Fedora-Cloud-Base-24-20160509.n.1.x86_64 || ami-42835521 || EC2 (ap-southeast-1) || hvm || gp2 <br />
|-<br />
| Fedora-Cloud-Base-24-20160509.n.1.x86_64 || ami-45815726 || EC2 (ap-southeast-1) || hvm || standard <br />
|-<br />
| Fedora-Cloud-Base-24-20160509.n.1.x86_64 || ami-fcd0fc9f || EC2 (ap-southeast-2) || paravirtual || gp2 <br />
|-<br />
| Fedora-Cloud-Base-24-20160509.n.1.x86_64 || ami-a237dacf || EC2 (us-east-1) || paravirtual || standard <br />
|-<br />
| Fedora-Cloud-Base-24-20160509.n.1.x86_64 || ami-3636db5b || EC2 (us-east-1) || paravirtual || gp2 <br />
|-<br />
| Fedora-Cloud-Base-24-20160509.n.1.x86_64 || ami-2398e143 || EC2 (us-west-1) || paravirtual || gp2 <br />
|-<br />
| Fedora-Cloud-Base-24-20160509.n.1.x86_64 || ami-863fdbe7 || EC2 (ap-northeast-1) || paravirtual || gp2 <br />
|-<br />
| Fedora-Cloud-Base-24-20160509.n.1.x86_64 || ami-3b38b157 || EC2 (sa-east-1) || paravirtual || gp2 <br />
|-<br />
| Fedora-Cloud-Base-24-20160509.n.1.x86_64 || ami-18fa706b || EC2 (eu-west-1) || hvm || gp2 <br />
|-<br />
| Fedora-Cloud-Base-24-20160509.n.1.x86_64 || ami-f2c62b9d || EC2 (eu-central-1) || hvm || standard <br />
|-<br />
| Fedora-Cloud-Base-24-20160509.n.1.x86_64 || ami-c9e16bba || EC2 (eu-west-1) || paravirtual || gp2 <br />
|-<br />
| Fedora-Cloud-Base-24-20160509.n.1.x86_64 || ami-5c27ae30 || EC2 (sa-east-1) || hvm || gp2 <br />
|-<br />
| Fedora-Cloud-Base-24-20160509.n.1.x86_64 || ami-f3c72a9c || EC2 (eu-central-1) || hvm || gp2 <br />
|-<br />
| Fedora-Cloud-Base-24-20160509.n.1.x86_64 || ami-8ed2feed || EC2 (ap-southeast-2) || paravirtual || standard <br />
|-<br />
| Fedora-Cloud-Base-24-20160509.n.1.x86_64 || ami-823edae3 || EC2 (ap-northeast-1) || hvm || gp2 <br />
|-<br />
| Fedora-Cloud-Base-24-20160509.n.1.x86_64 || ami-a5f508c5 || EC2 (us-west-2) || paravirtual || standard <br />
|-<br />
| Fedora-Cloud-Base-24-20160509.n.1.x86_64 || ami-fce66c8f || EC2 (eu-west-1) || hvm || standard <br />
|-<br />
| Fedora-Cloud-Base-24-20160509.n.1.x86_64 || ami-2e82544d || EC2 (ap-southeast-1) || paravirtual || standard <br />
|-<br />
| Fedora-Cloud-Base-24-20160509.n.1.x86_64 || ami-9dfa07fd || EC2 (us-west-2) || hvm || gp2 <br />
|-<br />
| Fedora-Cloud-Base-24-20160509.n.1.x86_64 || ami-27c62b48 || EC2 (eu-central-1) || paravirtual || standard <br />
|-<br />
| Fedora-Cloud-Base-24-20160509.n.1.x86_64 || ami-a4fa07c4 || EC2 (us-west-2) || hvm || standard <br />
|}<br />
<br />
<br />
Here's a chunk which is commonly used for most Test Days. Replace XX with whatever Fedora release is pending:<br />
<br />
* An updated [https://www.happyassassin.net/nightlies.html Fedora 24 nightly Cloud/Atomic Host image]<br />
<br />
== How to test? ==<br />
<br />
* Boot the images on a cloud system, or on Vagrant or using testcloud on a local system.<br />
* Execute the tests.<br />
<br />
=== Run the tests ===<br />
<br />
Visit the [http://testdays.fedorainfracloud.org/events/7 result page] and click on the column title links to see the tests that need to be run: most column titles are links to a specific test case. Follow the instructions there, then enter your results by clicking the ''Enter result'' button for the test.<br />
<br />
=== Exploratory testing ===<br />
<br />
If you run out of test cases, congratulations! But that's not the end! You can still help out by playing around with the tool in whatever ways you can think of: try out all the things you can find, and try writing different Fedora images with it. If you have systems with different Windows versions, try running the tool on all of them. Get creative! Any problems you find please file a bug, or report to the IRC channel.<br />
<br />
== Reporting bugs ==<br />
<br />
<br />
<br />
If you have problems with any of the tests, report a bug to [https://bugzilla.redhat.com Bugzilla]. If you are unsure about exactly how to file the report or what other information to include, just ask on IRC and we will help you.<br />
<br />
IRC Channel name: #fedora-cloud, #fedora-test-day<br />
Server: Freenode<br />
<br />
== Test Results ==<br />
<br />
Please enter your results on the [http://testdays.fedorainfracloud.org/events/7 result page]. The results will be transferred here after the Test Day is finished.<br />
<br />
=== Basic Tests ===<br />
{|<br />
! User<br />
! Profile<br />
! [http://fedoraproject.org/wiki/QA:Testcase_base_startup Base startup]<br />
! [http://fedoraproject.org/wiki/QA:Testcase_base_system_logging System logging]<br />
! [http://fedoraproject.org/wiki/QA:Testcase_Services_start Services start]<br />
! [http://fedoraproject.org/wiki/QA:Testcase_base_selinux SELinux]<br />
! [http://fedoraproject.org/wiki/QA:Testcase_base_service_manipulation Service manipulation]<br />
! References<br />
|-<br />
| [[User:ashutoshbhakare|ashutoshbhakare]]<br />
| Openstack<br />
| {{result|pass}}<ref>Cloud Image </ref>{{result|pass}}{{result|pass}}<br />
| <br />
| {{result|fail}}<ref>{{bz|1335149}} Cloud Image failed</ref><br />
| {{result|pass}}<ref>Cloud Base Image</ref><br />
| <br />
| <references/><br />
|-<br />
| [[User:chandankumar|chandankumar]]<br />
| OpenStack<br />
| {{result|pass}}<ref>[1.] Added Image to Glance <br />
[2.] Created Instance using fedora 24 beta image <br />
[3.] Added floating ip to the instance <br />
[4.] Booted fine on OpenStack Instance <br />
[5.] Able to ssh into the fedora beta instance <br />
</ref><br />
| <br />
| <br />
| <br />
| <br />
| <references/><br />
|-<br />
| [[User:chandankumar|chandankumar]]<br />
| OpenStack [ OS1 public ]<br />
| <br />
| <br />
| {{result|pass}}<ref>Fedora Cloud Image</ref><br />
| {{result|pass}}<ref>[4.] Fedora Cloud Image</ref><br />
| {{result|pass}}<ref>[5.] Fedora Cloud Image</ref><br />
| <references/><br />
|-<br />
| [[User:coremodule|coremodule]]<br />
| Base Install<br />
| {{result|pass}}<br />
| <br />
| <br />
| <br />
| <br />
| <references/><br />
|-<br />
| [[User:coremodule|coremodule]]<br />
| testcloud<br />
| {{result|pass}}<ref>[1]Cloud Image</ref><br />
| <br />
| <br />
| <br />
| <br />
| <references/><br />
|-<br />
| [[User:dustymabe|dustymabe]]<br />
| EC2 m3.medium ami-6d36db00<br />
| {{result|pass}}<br />
| {{result|pass}}<br />
| {{result|pass}}<br />
| {{result|pass}}<br />
| {{result|pass}}<br />
| <references/><br />
|-<br />
| [[User:ganeshkadam|ganeshkadam]]<br />
| local kvm/libvirt<br />
| {{result|pass}}<ref>Fedora-Atomic image</ref>{{result|pass}}<ref>Cloud-Base image</ref><br />
| {{result|pass}}<ref>Atomic-image</ref>{{result|pass}}<ref>Cloud-Based image</ref><br />
| {{result|pass}}<ref>Atomic-image</ref>{{result|pass}}<ref>Cloud-Based image<br />
</ref><br />
| {{result|pass}}<ref>Atomic-image</ref>{{result|pass}}<ref>Cloud-Based image</ref><br />
| {{result|pass}}<ref>Atomic-image</ref>{{result|pass}}<ref>Cloud-Based image</ref><br />
| <references/><br />
|-<br />
| [[User:jberkus|jberkus]]<br />
| jberkus<br />
| {{result|pass}}<ref>Atomic Host image running on AWS us-west-2</ref><br />
| {{result|pass}}<ref>Atomic Host image running on AWS us-west-2</ref><br />
| {{result|fail}}<ref>Atomic Host running on AWS us-west-2<br />
<br />
Two services failed to start:<br />
<br />
UNIT LOAD ACTIVE SUB DESCRIPTION<br />
var-lib-nfs-rpc_pipefs.mount loaded failed failed RPC Pipe File System<br />
kube-controller-manager.service loaded failed failed Kubernetes Controller Manager<br />
<br />
While the second is an Atomic test, the first is not.<br />
</ref><br />
| {{result|pass}}<ref>Atomic Host on AWS us-west-2</ref><br />
| {{result|pass}}<ref>Atomic Host on AWS us-west-2</ref><br />
| <references/><br />
|-<br />
| [[User:jsedlak|jsedlak]]<br />
| <br />
| {{result|pass}}<ref>Atomic image</ref><br />
| {{result|pass}}<ref>Atomic image</ref><br />
| {{result|pass}}<ref>Atomic image</ref><br />
| {{result|pass}}<ref>Atomic image</ref><br />
| {{result|pass}}<ref>Atomic image</ref><br />
| <references/><br />
|-<br />
| [[User:kushal|kushal]]<br />
| Openstack (Fedora Infra)<br />
| {{result|pass}}<ref>Cloud base image</ref>{{result|pass}}<ref>Atomic image</ref>{{result|pass}}<br />
| {{result|pass}}<ref>Cloud base image</ref>{{result|pass}}<ref>Atomic image</ref><br />
| {{result|pass}}<ref>Cloud base image</ref>{{result|pass}}<ref>Atomic image</ref><br />
| {{result|pass}}<ref>Cloud base image</ref>{{result|pass}}<ref>Atomic image</ref><br />
| {{result|pass}}<ref>Cloud base image</ref>{{result|pass}}<ref>Atomic image</ref><br />
| <references/><br />
|-<br />
| [[User:lbrabec|lbrabec]]<br />
| testcloud<br />
| {{result|pass}}<ref>cloud and atomic</ref><br />
| {{result|pass}}<ref>cloud and atomic</ref><br />
| {{result|pass}}<ref>cloud and atomic</ref><br />
| {{result|pass}}<ref>cloud and atomic</ref><br />
| {{result|pass}}<ref>cloud and atomic</ref><br />
| <references/><br />
|-<br />
| [[User:satya4ever|satya4ever]]<br />
| Openstack<br />
| {{result|pass}}<ref>Atomic Host Image</ref>{{result|pass}}<ref>Cloud Image QCOW2</ref><br />
| {{result|pass}}<ref>Atomic image</ref>{{result|pass}}<ref>Cloud base image</ref><br />
| {{result|pass}}<ref>Cloud base image</ref>{{result|pass}}<ref>Atomic image</ref><br />
| {{result|pass}}<ref>Atomic image</ref>{{result|pass}}<ref>Cloud base image</ref><br />
| {{result|pass}}<ref>Atomic image</ref>{{result|pass}}<ref>Cloud base image</ref><br />
| <references/><br />
|-<br />
| [[User:sumantrom|sumantrom]]<br />
| testcloud<br />
| {{result|pass}}<ref>Cloud base Image</ref><br />
| {{result|pass}}<ref>Cloud base image</ref><br />
| {{result|pass}}<ref>Cloud base</ref><br />
| {{result|pass}}<ref>Cloud base </ref><br />
| {{result|pass}}<ref>Cloud base</ref><br />
| <references/><br />
|-<br />
| [[User:suraj353|suraj353]]<br />
| Openstack<br />
| {{result|pass}}<ref>2. Atomic image <br />
</ref>{{result|pass}}<ref>Cloud base image</ref><br />
| {{result|pass}}<ref>Cloud base image</ref>{{result|pass}}<ref>Atomic image</ref><br />
| {{result|pass}}<ref>Atomic image</ref>{{result|pass}}<ref>Cloud base image</ref><br />
| {{result|pass}}<ref>Cloud base image</ref>{{result|pass}}<ref>Atomic image</ref><br />
| {{result|pass}}<ref>Atomic image</ref>{{result|pass}}<ref>Cloud base image</ref><br />
| <references/><br />
<br />
|-<br />
|}<br />
<br />
=== Atomic Tests ===<br />
{|<br />
! User<br />
! Profile<br />
! [http://fedoraproject.org/wiki/User:Roshi/QA/AtomicTests/Atomic_Image_Boots Image boots]<br />
! [http://fedoraproject.org/wiki/User:Roshi/QA/AtomicTests/Atomic_Upgrade Upgrade works]<br />
! [http://fedoraproject.org/wiki/User:Roshi/QA/AtomicTests/Atomic_Rollback Rollback works]<br />
! References<br />
|-<br />
| [[User:jberkus|jberkus]]<br />
| jberkus<br />
| {{result|pass}}<ref>Atomic Host on AWS us-west-2</ref><br />
| <br />
| <br />
| <references/><br />
|-<br />
| [[User:jsedlak|jsedlak]]<br />
| <br />
| {{result|pass}}<br />
| {{result|fail}}<ref>{{bz|1330318}} </ref><br />
| <br />
| <references/><br />
|-<br />
| [[User:kushal|kushal]]<br />
| Openstack (Fedora Infra)<br />
| {{result|pass}}<ref>Atomic image</ref><br />
| {{result|fail}}<ref>{{bz|1330318}} Atomic image (known issue)</ref><br />
| <br />
| <references/><br />
|-<br />
| [[User:lbrabec|lbrabec]]<br />
| testcloud<br />
| {{result|pass}}<br />
| {{result|fail}}<ref>{{bz|1330318}} </ref><br />
| <br />
| <references/><br />
|-<br />
| [[User:satya4ever|satya4ever]]<br />
| Openstack<br />
| {{result|pass}}<ref>Atomic image</ref><br />
| {{result|fail}}<ref>{{bz|1330318}} #1330318</ref><br />
| <br />
| <references/><br />
|-<br />
| [[User:suraj353|suraj353]]<br />
| Openstack<br />
| {{result|pass}}<ref>Atomic image</ref><br />
| {{result|fail}}<ref>#1330318</ref><br />
| <br />
| <references/><br />
<br />
|-<br />
|}<br />
<br />
=== Docker tests ===<br />
{|<br />
! User<br />
! Profile<br />
! [http://fedoraproject.org/wiki/QA:Testcase_Docker_Install Docker install]<br />
! [http://fedoraproject.org/wiki/QA:Testcase_Docker_Storage_Setup Docker storage setup]<br />
! [http://fedoraproject.org/wiki/QA:Testcase_Docker_Daemon Docker daemon]<br />
! References<br />
|-<br />
| [[User:ganeshkadam|ganeshkadam]]<br />
| local kvm/libvirt<br />
| {{result|pass}}<ref>Atomic-image</ref><br />
| {{result|pass}}<ref>Atomic-image</ref><br />
| <br />
| <references/><br />
|-<br />
| [[User:kushal|kushal]]<br />
| Openstack (Fedora Infra)<br />
| {{result|pass}}<ref>Cloud base image</ref>{{result|pass}}<ref>Atomic image</ref><br />
| {{result|pass}}<ref>Atomic image</ref>{{result|pass}}<ref>Atomic image</ref><br />
| {{result|pass}}<ref>Cloud base image</ref>{{result|pass}}<ref>Atomic image</ref><br />
| <references/><br />
|-<br />
| [[User:lbrabec|lbrabec]]<br />
| testcloud<br />
| {{result|pass}}<ref>cloud and atomic</ref><br />
| {{result|pass}}<ref>cloud and atomic</ref><br />
| {{result|pass}}<ref>cloud and atomic</ref><br />
| <references/><br />
|-<br />
| [[User:satya4ever|satya4ever]]<br />
| Openstack<br />
| {{result|pass}}<ref>Cloud base image</ref>{{result|pass}}<ref>Atomic image</ref><br />
| {{result|pass}}<ref>Cloud base image</ref>{{result|pass}}<ref>Atomic image</ref><br />
| {{result|pass}}<ref>Cloud base image</ref>{{result|pass}}<ref>Atomic image</ref><br />
| <references/><br />
|-<br />
| [[User:sumantrom|sumantrom]]<br />
| testcloud<br />
| {{result|pass}}<ref>Cloud base Image</ref><br />
| {{result|pass}}<ref>Cloud Base</ref><br />
| {{result|pass}}<ref>Cloud Base Image</ref><br />
| <references/><br />
|-<br />
| [[User:suraj353|suraj353]]<br />
| Openstack<br />
| {{result|pass}}<ref>Cloud base image</ref>{{result|pass}}<ref>Atomic image</ref><br />
| {{result|pass}}<ref>Cloud base image</ref>{{result|pass}}<ref>Atomic image</ref><br />
| {{result|pass}}<ref>Cloud base image</ref>{{result|pass}}<ref>Atomic image</ref><br />
| <references/><br />
<br />
|-<br />
|}<br />
<br />
=== More Atomic related tests ===<br />
{|<br />
! User<br />
! Profile<br />
! [http://fedoraproject.org/wiki/QA:Testcase_Atomic_command Atomic command]<br />
! [http://fedoraproject.org/wiki/QA:Testcase_Atomic_read_only_mounts Atomic read only mounts]<br />
! [http://fedoraproject.org/wiki/QA:Testcase_Atomic_root_mount Atomic root mount]<br />
! [http://fedoraproject.org/wiki/QA:Testcase_Tmp_Mount Atomic tmp mount]<br />
! [http://fedoraproject.org/wiki/QA/Draft/Testcase_tmp_writable Atomic tmp writable]<br />
! [http://fedoraproject.org/wiki/QA:Testcase_Journal_Written Atomic journal written]<br />
! References<br />
|-<br />
| [[User:ganeshkadam|ganeshkadam]]<br />
| local kvm/libvirt<br />
| {{result|pass}}<ref>Atomic-image</ref><br />
| {{result|pass}}<ref>Atomic-image</ref><br />
| <br />
| {{result|pass}}<ref>Atomic-image</ref><br />
| {{result|pass}}<ref>Atomic-image</ref><br />
| {{result|pass}}<ref>Atomic-image</ref><br />
| <references/><br />
|-<br />
| [[User:kushal|kushal]]<br />
| Openstack (Fedora Infra)<br />
| {{result|fail}}<ref>{{bz|1334588}} Atomic image, it is failing with a system error.</ref><br />
| {{result|pass}}<ref>Atomic image</ref><br />
| <br />
| {{result|pass}}<ref>Atomic image</ref><br />
| {{result|pass}}<ref>Atomic image</ref><br />
| {{result|pass}}<ref>Atomic image</ref><br />
| <references/><br />
|-<br />
| [[User:lbrabec|lbrabec]]<br />
| testcloud<br />
| {{result|fail}}<ref>{{bz|1334588}} </ref><br />
| {{result|pass}}<br />
| <br />
| {{result|pass}}<br />
| {{result|pass}}<br />
| {{result|pass}}<br />
| <references/><br />
|-<br />
| [[User:suraj353|suraj353]]<br />
| Openstack<br />
| {{result|fail}}<ref>#1334588,</ref><br />
| {{result|pass}}<ref>Atomic image</ref><br />
| <br />
| {{result|pass}}<ref>Atomic image</ref><br />
| {{result|pass}}<ref>Atomic image</ref><br />
| {{result|pass}}<ref>Atomic image</ref><br />
| <references/><br />
<br />
|-<br />
|}<br />
<br />
=== Vagrant test ===<br />
{|<br />
! User<br />
! Profile<br />
! [http://fedoraproject.org/wiki/QA/Draft/Testcase_Vagrant_eth0_naming eth0 naming]<br />
! References<br />
<br />
|-<br />
|}<br />
<br />
<br />
<br />
[[Category:Fedora 24 Test Days]]<br />
<br />
<!-- remove this category when creating a test day page --><br />
[[Category:QA Templates]]</div>Kushalhttps://fedoraproject.org/w/index.php?title=PyCon_2016&diff=446346PyCon 20162016-05-12T04:54:56Z<p>Kushal: /* Fedora <3's Python */ 💖 sign added</p>
<hr />
<div>= PyCon 2016 =<br />
<br />
PyCon is the largest annual gathering for the community using and developing the open-source Python programming language. PyCon is organized by the Python community for the community. We try to keep registration far cheaper than most comparable technology conferences, to make PyCon accessible to the widest group possible. PyCon is a diverse conference dedicated to providing an enjoyable experience to everyone. Our code of conduct is intended to help everyone maintain the PyCon spirit. We thank all attendees and staff for observing it.<br />
<br />
== Site ==<br />
[https://us.pycon.org/2016/ PyCon 2016]<br />
<br />
== Schedule ==<br />
* '''Tutorial Days''' May 28 & May 29<br />
* '''Conference Days''' May 30 - June 1<br />
* '''Development Sprints''' June 2 - June 5<br />
<br />
== Team ==<br />
<br />
* [[User:kushal | Kushal Das ]]<br />
* [[User:lmacken | Luke Macken ]]<br />
* [[User:decause|decause]]<br />
* [[User:ralph | Ralph Bean ]]<br />
<br />
== Hotel ==<br />
<br />
<br />
<br />
Listed below are the hotels with which PyCon has negotiated discount rates. These conference rates are only available to attendees of the PyCon conference who make reservations through our conference registration site.<br />
<br />
The hotels this year vary in distance from the convention center:<br />
<br />
The [http://hoteleastlund.com/ Hotel Eastlund] is about a 5-minute walk from the venue.<br />
<br />
The [http://www.cpportland.com/ Crowne Plaza], [http://www.marriott.com/hotels/travel/pdxcl-courtyard-portland-downtown-convention-center/ Courtyard Mariott], and [http://www.doubletreeportland.com/ DoubleTree] are another block or two away, within a 10-minute walk of the conference center. <br />
<br />
Everyone that is staying at a conference hotel (booked through the conference website) will get a complimentary week-long ticket for the TriMet public transportation system in Portland. These tickets will be distributed at registration when you pick up your badge.<br />
<br />
== The Sprints ==<br />
<br />
Fedora will be hosting a dedicated Sprint Room at PyCon this year for new and established contributors who want hack on or with Fedora! To get involved (physically or virtually) join #fedora-python on Freenode, and/or send an email to [[user:decause|decause]] and let him know.<br />
<br />
== Fedora 💖 Python ==<br />
<br />
As part of our proposed Python Marketing Objective, The Fedora Design Team has created a series of Python marketing materials for use at this conference, and other Python events going forward.<br />
<br />
Stickers: https://fedorahosted.org/design-team/raw-attachment/ticket/442/hexspec-sticker-python_no-text.pdf<br />
<br />
Brochure (under construction): https://fedorahosted.org/design-team/attachment/ticket/434/python-fedora.pdf<br />
<br />
Tshirts: https://fedorahosted.org/design-team/ticket/431#comment:8<br />
<br />
Poster: https://fedorahosted.org/design-team/raw-attachment/ticket/444/fedora_python_poster-landscape.pdf</div>Kushalhttps://fedoraproject.org/w/index.php?title=Fedora_meetup_Pune_May_2016&diff=446293Fedora meetup Pune May 20162016-05-11T13:58:55Z<p>Kushal: /* Agenda */ Updating the agenda</p>
<hr />
<div>{{header|events}}<br />
<br />
= Fedora Events: Fedora meetup Pune, May 2016 =<br />
<br />
== About ==<br />
<br />
This is the forth edition of our regular Fedora meetup in Pune. We will learn/discuss about various new technologies being used in the project. We will also work<br />
on various parts of projects during the meetups.<br />
<br />
== Location & Schedule ==<br />
<br />
Date: 2016-05-14 18:00 IST onwards<br />
<br />
K 104, Jasminium, Magarpatta City<br />
Pune. <br />
<br />
Note: Please carry a valid ID proof to enter the building. If security guys ask, tell them you are coming to meet Sayan Chowdhury or Kushal Das. <br />
Emergency contact number: +91 8605430990<br />
<br />
== Participants ==<br />
<br />
Please add your name to the end of the list.<br />
<br />
{|<br />
! # !! Name <br />
|-<br />
| 1 || [[User:kushal | Kushal Das]] <br />
|-<br />
| 2 || [[User:kumarpraveen | Praveen Kumar]] <br />
|-<br />
| 3 || [[User:chandankumar | Chandan Kumar]] <br />
|}<br />
<br />
== Agenda ==<br />
<br />
* (Fill in if you want to do something)<br />
* Documentation work for Fedora<br />
* Figuring out newbies pain points and create docs for the same<br />
<br />
== Pictures and Reports ==<br />
<br />
<br />
[[Category:Marketing]] [[Category:Events]] [[Category:Events 2016]]</div>Kushalhttps://fedoraproject.org/w/index.php?title=Test_Day:2016_05_10_Cloud&diff=446131Test Day:2016 05 10 Cloud2016-05-10T09:36:22Z<p>Kushal: /* How to test? */</p>
<hr />
<div>{{Infobox_group<br />
| name = Fedora Test Day<br />
| image = [[File:Echo-testing-48px.png|link=QA/Test Days]]<br />
| caption = [[Fedora Cloud Test day]]<br />
| date = 2016-05-10<br />
| time = all day<br />
| website = [[QA/Test Days]]<br />
| irc = [irc://irc.freenode.net/#fedora-test-day #fedora-test-day] ([http://webchat.freenode.net/?channels=fedora-test-day webirc])<br />
| fedora_mailing_list = test<br />
}}<br />
<br />
{{admon/note | Can't make the date? | If you come to this page before or after the test day is completed, your testing is still valuable, and you can use the information on this page to test, file any bugs you find at [http://bugzilla.redhat.com Bugzilla], and add your results to the results section. If this page is more than a month old when you arrive here, please check the [[QA/Test_Days|current schedule]] and see if a similar but more recent Test Day is planned or has already happened.}}<br />
<br />
== What to test? ==<br />
<br />
Today's instalment of Fedora Test Day will focus on '''Cloud, Atomic Host''' images for Fedora 24.<br />
<br />
== Who's available ==<br />
<br />
The following cast of characters will be available testing, workarounds, bug fixes, and general discussion ...<br />
* Development - [[User:Kushal|Kushal]] (kushal)<br />
* Quality Assurance - [[User:lbrabec|Lukas Brabec]] (lbrabec), [[User:pschindl|Petr Schindler]] (pschindl)<br />
<br />
== Prerequisite for Test Day == <br />
<br />
You will require at least a system with libvirt/kvm installed. Having access to any Openstack or other Cloud IAAS system where you can upload an image will be even better.<br />
<br />
Download the images from below links<br />
<br />
* [https://kojipkgs.fedoraproject.org/compose/branched/Fedora-24-20160509.n.1/compose/CloudImages/x86_64/images/Fedora-Cloud-Base-24-20160509.n.1.x86_64.qcow2 Cloud Image QCOW2]<br />
* [https://kojipkgs.fedoraproject.org/compose/branched/Fedora-24-20160509.n.1/compose/CloudImages/x86_64/images/Fedora-Atomic-24-20160509.n.1.x86_64.qcow2 Atomic Host Image QCOW2]<br />
<br />
* [https://kojipkgs.fedoraproject.org/compose/branched/Fedora-24-20160509.n.1/compose/CloudImages/x86_64/images/Fedora-Cloud-Base-Vagrant-24-20160509.n.1.x86_64.vagrant-virtualbox.box Vagrant Virtualbox cloud base]<br />
* [https://kojipkgs.fedoraproject.org/compose/branched/Fedora-24-20160506.n.0/compose/CloudImages/x86_64/images/Fedora-Atomic-Vagrant-24-20160506.n.0.x86_64.vagrant-virtualbox.box Vagrant Virtualbox Atomic]<br />
<br />
<br />
<br />
Here's a chunk which is commonly used for most Test Days. Replace XX with whatever Fedora release is pending:<br />
<br />
* An updated [https://www.happyassassin.net/nightlies.html Fedora 24 nightly Cloud/Atomic Host image]<br />
<br />
== How to test? ==<br />
<br />
* Boot the images on a cloud system, or on Vagrant or using testcloud on a local system.<br />
* Execute the tests.<br />
<br />
=== Run the tests ===<br />
<br />
Visit the [http://testdays.fedorainfracloud.org/events/7 result page] and click on the column title links to see the tests that need to be run: most column titles are links to a specific test case. Follow the instructions there, then enter your results by clicking the ''Enter result'' button for the test.<br />
<br />
=== Exploratory testing ===<br />
<br />
If you run out of test cases, congratulations! But that's not the end! You can still help out by playing around with the tool in whatever ways you can think of: try out all the things you can find, and try writing different Fedora images with it. If you have systems with different Windows versions, try running the tool on all of them. Get creative! Any problems you find please file a bug, or report to the IRC channel.<br />
<br />
== Reporting bugs ==<br />
<br />
<br />
<br />
If you have problems with any of the tests, report a bug to [https://bugzilla.redhat.com Bugzilla]. If you are unsure about exactly how to file the report or what other information to include, just ask on IRC and we will help you.<br />
<br />
IRC Channel name: #fedora-cloud, #fedora-test-day<br />
Server: Freenode<br />
<br />
== Test Results ==<br />
<br />
Please enter your results on the [http://testdays.fedorainfracloud.org/events/7 result page]. The results will be transferred here after the Test Day is finished.<br />
[[Category:Fedora 24 Test Days]]<br />
<br />
<!-- remove this category when creating a test day page --><br />
[[Category:QA Templates]]</div>Kushalhttps://fedoraproject.org/w/index.php?title=Test_Day:2016_05_10_Cloud&diff=446117Test Day:2016 05 10 Cloud2016-05-10T06:03:09Z<p>Kushal: /* Prerequisite for Test Day */ Updates link</p>
<hr />
<div>{{Infobox_group<br />
| name = Fedora Test Day<br />
| image = [[File:Echo-testing-48px.png|link=QA/Test Days]]<br />
| caption = [[Fedora Cloud Test day]]<br />
| date = 2016-05-10<br />
| time = all day<br />
| website = [[QA/Test Days]]<br />
| irc = [irc://irc.freenode.net/#fedora-test-day #fedora-test-day] ([http://webchat.freenode.net/?channels=fedora-test-day webirc])<br />
| fedora_mailing_list = test<br />
}}<br />
<br />
{{admon/note | Can't make the date? | If you come to this page before or after the test day is completed, your testing is still valuable, and you can use the information on this page to test, file any bugs you find at [http://bugzilla.redhat.com Bugzilla], and add your results to the results section. If this page is more than a month old when you arrive here, please check the [[QA/Test_Days|current schedule]] and see if a similar but more recent Test Day is planned or has already happened.}}<br />
<br />
== What to test? ==<br />
<br />
Today's instalment of Fedora Test Day will focus on '''Cloud, Atomic Host''' images for Fedora 24.<br />
<br />
== Who's available ==<br />
<br />
The following cast of characters will be available testing, workarounds, bug fixes, and general discussion ...<br />
* Development - [[User:Kushal|Kushal]] (kushal)<br />
* Quality Assurance - [[User:lbrabec|Lukas Brabec]] (lbrabec), [[User:pschindl|Petr Schindler]] (pschindl)<br />
<br />
== Prerequisite for Test Day == <br />
<br />
You will require at least a system with libvirt/kvm installed. Having access to any Openstack or other Cloud IAAS system where you can upload an image will be even better.<br />
<br />
Download the images from below links<br />
<br />
* [https://kojipkgs.fedoraproject.org/compose/branched/Fedora-24-20160509.n.1/compose/CloudImages/x86_64/images/Fedora-Cloud-Base-24-20160509.n.1.x86_64.qcow2 Cloud Image QCOW2]<br />
* [https://kojipkgs.fedoraproject.org/compose/branched/Fedora-24-20160509.n.1/compose/CloudImages/x86_64/images/Fedora-Atomic-24-20160509.n.1.x86_64.qcow2 Atomic Host Image QCOW2]<br />
<br />
* [https://kojipkgs.fedoraproject.org/compose/branched/Fedora-24-20160509.n.1/compose/CloudImages/x86_64/images/Fedora-Cloud-Base-Vagrant-24-20160509.n.1.x86_64.vagrant-virtualbox.box Vagrant Virtualbox cloud base]<br />
* [https://kojipkgs.fedoraproject.org/compose/branched/Fedora-24-20160506.n.0/compose/CloudImages/x86_64/images/Fedora-Atomic-Vagrant-24-20160506.n.0.x86_64.vagrant-virtualbox.box Vagrant Virtualbox Atomic]<br />
<br />
<br />
<br />
Here's a chunk which is commonly used for most Test Days. Replace XX with whatever Fedora release is pending:<br />
<br />
* An updated [https://www.happyassassin.net/nightlies.html Fedora 24 nightly Cloud/Atomic Host image]<br />
<br />
== How to test? ==<br />
<br />
=== Run the tests ===<br />
<br />
Visit the [http://testdays.fedorainfracloud.org/events/7 result page] and click on the column title links to see the tests that need to be run: most column titles are links to a specific test case. Follow the instructions there, then enter your results by clicking the ''Enter result'' button for the test.<br />
<br />
=== Exploratory testing ===<br />
<br />
If you run out of test cases, congratulations! But that's not the end! You can still help out by playing around with the tool in whatever ways you can think of: try out all the things you can find, and try writing different Fedora images with it. If you have systems with different Windows versions, try running the tool on all of them. Get creative! Any problems you find please file a bug, or report to the IRC channel.<br />
<br />
== Reporting bugs ==<br />
<br />
<br />
<br />
If you have problems with any of the tests, report a bug to [https://bugzilla.redhat.com Bugzilla]. If you are unsure about exactly how to file the report or what other information to include, just ask on IRC and we will help you.<br />
<br />
IRC Channel name: #fedora-cloud, #fedora-test-day<br />
Server: Freenode<br />
<br />
== Test Results ==<br />
<br />
Please enter your results on the [http://testdays.fedorainfracloud.org/events/7 result page]. The results will be transferred here after the Test Day is finished.<br />
[[Category:Fedora 24 Test Days]]<br />
<br />
<!-- remove this category when creating a test day page --><br />
[[Category:QA Templates]]</div>Kushalhttps://fedoraproject.org/w/index.php?title=Test_Day:2016_05_10_Cloud&diff=446115Test Day:2016 05 10 Cloud2016-05-10T04:43:50Z<p>Kushal: /* Prerequisite for Test Day */ Adding Vagrant virtualbox for download</p>
<hr />
<div>{{Infobox_group<br />
| name = Fedora Test Day<br />
| image = [[File:Echo-testing-48px.png|link=QA/Test Days]]<br />
| caption = [[Fedora Cloud Test day]]<br />
| date = 2016-05-10<br />
| time = all day<br />
| website = [[QA/Test Days]]<br />
| irc = [irc://irc.freenode.net/#fedora-test-day #fedora-test-day] ([http://webchat.freenode.net/?channels=fedora-test-day webirc])<br />
| fedora_mailing_list = test<br />
}}<br />
<br />
{{admon/note | Can't make the date? | If you come to this page before or after the test day is completed, your testing is still valuable, and you can use the information on this page to test, file any bugs you find at [http://bugzilla.redhat.com Bugzilla], and add your results to the results section. If this page is more than a month old when you arrive here, please check the [[QA/Test_Days|current schedule]] and see if a similar but more recent Test Day is planned or has already happened.}}<br />
<br />
== What to test? ==<br />
<br />
Today's instalment of Fedora Test Day will focus on '''Cloud, Atomic Host''' images for Fedora 24.<br />
<br />
== Who's available ==<br />
<br />
The following cast of characters will be available testing, workarounds, bug fixes, and general discussion ...<br />
* Development - [[User:Kushal|Kushal]] (kushal)<br />
* Quality Assurance - [[User:lbrabec|Lukas Brabec]] (lbrabec), [[User:pschindl|Petr Schindler]] (pschindl)<br />
<br />
== Prerequisite for Test Day == <br />
<br />
You will require at least a system with libvirt/kvm installed. Having access to any Openstack or other Cloud IAAS system where you can upload an image will be even better.<br />
<br />
Download the images from below links<br />
<br />
* [https://kojipkgs.fedoraproject.org/compose/branched/Fedora-24-20160509.n.1/compose/Cloud/x86_64/iso/Fedora-Cloud-netinst-x86_64-24-20160509.n.1.iso Cloud Image]<br />
* [https://kojipkgs.fedoraproject.org/compose/branched/Fedora-24-20160509.n.1/compose/CloudImages/x86_64/images/Fedora-Atomic-24-20160509.n.1.x86_64.qcow2 Atomic Host Image]<br />
<br />
* [https://kojipkgs.fedoraproject.org/compose/branched/Fedora-24-20160509.n.1/compose/CloudImages/x86_64/images/Fedora-Cloud-Base-Vagrant-24-20160509.n.1.x86_64.vagrant-virtualbox.box Vagrant Virtualbox cloud base]<br />
* [https://kojipkgs.fedoraproject.org/compose/branched/Fedora-24-20160506.n.0/compose/CloudImages/x86_64/images/Fedora-Atomic-Vagrant-24-20160506.n.0.x86_64.vagrant-virtualbox.box Vagrant Virtualbox Atomic]<br />
<br />
<br />
<br />
Here's a chunk which is commonly used for most Test Days. Replace XX with whatever Fedora release is pending:<br />
<br />
* An updated [https://www.happyassassin.net/nightlies.html Fedora 24 nightly Cloud/Atomic Host image]<br />
<br />
== How to test? ==<br />
<br />
=== Run the tests ===<br />
<br />
Visit the [http://testdays.fedorainfracloud.org/events/7 result page] and click on the column title links to see the tests that need to be run: most column titles are links to a specific test case. Follow the instructions there, then enter your results by clicking the ''Enter result'' button for the test.<br />
<br />
=== Exploratory testing ===<br />
<br />
If you run out of test cases, congratulations! But that's not the end! You can still help out by playing around with the tool in whatever ways you can think of: try out all the things you can find, and try writing different Fedora images with it. If you have systems with different Windows versions, try running the tool on all of them. Get creative! Any problems you find please file a bug, or report to the IRC channel.<br />
<br />
== Reporting bugs ==<br />
<br />
<br />
<br />
If you have problems with any of the tests, report a bug to [https://bugzilla.redhat.com Bugzilla]. If you are unsure about exactly how to file the report or what other information to include, just ask on IRC and we will help you.<br />
<br />
IRC Channel name: #fedora-cloud, #fedora-test-day<br />
Server: Freenode<br />
<br />
== Test Results ==<br />
<br />
Please enter your results on the [http://testdays.fedorainfracloud.org/events/7 result page]. The results will be transferred here after the Test Day is finished.<br />
[[Category:Fedora 24 Test Days]]<br />
<br />
<!-- remove this category when creating a test day page --><br />
[[Category:QA Templates]]</div>Kushalhttps://fedoraproject.org/w/index.php?title=Test_Day:2016_05_10_Cloud_TestdayApp_Metadata&diff=446088Test Day:2016 05 10 Cloud TestdayApp Metadata2016-05-09T17:22:35Z<p>Kushal: /* More Atomic related tests */ Updates the wrong url</p>
<hr />
<div>= TestdayApp Metadata =<br />
* F24 Cloud test day; https://fedoraproject.org/wiki/Test_Day:2016_05_10_Cloud<br />
<br />
== Basic Tests ==<br />
<br />
* Base startup; https://fedoraproject.org/wiki/QA:Testcase_base_startup<br />
* System logging; https://fedoraproject.org/wiki/QA:Testcase_base_system_logging<br />
* Services start; https://fedoraproject.org/wiki/QA:Testcase_Services_start<br />
* SELinux; https://fedoraproject.org/wiki/QA:Testcase_base_selinux<br />
* Service manipulation; https://fedoraproject.org/wiki/QA:Testcase_base_service_manipulation<br />
<br />
== Atomic Tests ==<br />
<br />
* Image boots; http://fedoraproject.org/wiki/User:Roshi/QA/AtomicTests/Atomic_Image_Boots<br />
* Upgrade works; http://fedoraproject.org/wiki/User:Roshi/QA/AtomicTests/Atomic_Upgrade<br />
* Rollback works; http://fedoraproject.org/wiki/User:Roshi/QA/AtomicTests/Atomic_Rollback<br />
<br />
== Docker tests ==<br />
* Docker install; https://fedoraproject.org/wiki/QA:Testcase_Docker_Install<br />
* Docker storage setup; https://fedoraproject.org/wiki/QA:Testcase_Docker_Storage_Setup<br />
* Docker daemon; https://fedoraproject.org/wiki/QA:Testcase_Docker_Daemon<br />
<br />
== More Atomic related tests ==<br />
<br />
* Atomic command; https://fedoraproject.org/wiki/QA:Testcase_Atomic_command<br />
* Atomic read only mounts; https://fedoraproject.org/wiki/QA:Testcase_Atomic_read_only_mounts<br />
* Atomic root mount; https://fedoraproject.org/wiki/QA:Testcase_Atomic_root_mount<br />
* Atomic tmp mount; https://fedoraproject.org/wiki/QA:Testcase_Tmp_Mount<br />
* Atomic tmp writable; https://fedoraproject.org/wiki/QA/Draft/Testcase_tmp_writable<br />
* Atomic journal written; https://fedoraproject.org/wiki/QA:Testcase_Journal_Written<br />
<br />
== Vagrant test ==<br />
* eth0 naming; https://fedoraproject.org/wiki/QA/Draft/Testcase_Vagrant_eth0_naming</div>Kushalhttps://fedoraproject.org/w/index.php?title=Fedora_meetup_Pune_April_2016&diff=445892Fedora meetup Pune April 20162016-05-05T16:16:06Z<p>Kushal: /* Pictures and Reports */</p>
<hr />
<div>{{header|events}}<br />
<br />
= Fedora Events: Fedora meetup Pune, April 2016 =<br />
<br />
== About ==<br />
<br />
This is the third edition of our regular Fedora meetup in Pune. We will learn/discuss about various new technologies being used in the project. We will also work<br />
on various parts of projects during the meetups.<br />
<br />
== Location & Schedule ==<br />
<br />
Date: 2016-04-23 18:00 IST onwards<br />
<br />
K 104, Jasminium, Magarpatta City<br />
Pune. <br />
<br />
Note: Please carry a valid ID proof to enter the building. If security guys ask, tell them you are coming to meet Sayan Chowdhury or Kushal Das. <br />
Emergency contact number: +91 8605430990<br />
<br />
== Participants ==<br />
<br />
Please add your name to the end of the list.<br />
<br />
{|<br />
! # !! Name <br />
|-<br />
| 1 || [[User:kushal | Kushal Das]] <br />
|-<br />
| 2 || [[User:kumarpraveen | Praveen Kumar]] <br />
|-<br />
| 3 || [[User:chandankumar | Chandan Kumar]] <br />
|-<br />
| 4 || [[User:siddhesh | Siddhesh]]<br />
|-<br />
| 5 || [[User:girish946 | Girish joshi]]<br />
|-<br />
| 6 || [[User:ganeshkadam | Ganesh Kadam]]<br />
|-<br />
| 7 || [[User:suraj353 | Suraj Narwade]]<br />
|-<br />
| 8 || [[User:satya4ever | Satyajit Bulage]]<br />
|-<br />
| 9 || [[User:pyadav | Pooja Yadav]]<br />
|-<br />
| 10 || [[User:amolkahat | Amol Kahat]]<br />
|-<br />
| 11 || [[User:rahul_bajaj | Rahul Bajaj]]<br />
|}<br />
<br />
== Agenda ==<br />
<br />
* Writing test for fedora Atomic.<br />
<br />
== Pictures and Reports ==<br />
<br />
* http://yadav-pooja.blogspot.in/2016/04/my-first-fedora-meetup.html<br />
* http://surajnarwade.github.io/april-fedora-meetup-unit-testing-revealed.html<br />
* https://satya4ever.wordpress.com/2016/04/25/fedora-meetup-started-contribution-to-fedora<br />
* https://akahat.wordpress.com/2016/04/24/april-fedora-meetup-2016/#more-114<br />
* https://rahulbajaj05.wordpress.com/2016/04/23/fedora-meetup-writing-unittests-in-python/<br />
* https://https://kushaldas.in/posts/fedora-pune-meetup-april-2016.html<br />
<br />
[[Category:Marketing]] [[Category:Events]] [[Category:Events 2016]]</div>Kushalhttps://fedoraproject.org/w/index.php?title=Fedora_meetup_Pune_April_2016&diff=445882Fedora meetup Pune April 20162016-05-05T14:01:05Z<p>Kushal: /* Pictures and Reports */ moreccccccfhhiekvdcnkflbturkvreckijtceclgbvhfrit</p>
<hr />
<div>{{header|events}}<br />
<br />
= Fedora Events: Fedora meetup Pune, April 2016 =<br />
<br />
== About ==<br />
<br />
This is the third edition of our regular Fedora meetup in Pune. We will learn/discuss about various new technologies being used in the project. We will also work<br />
on various parts of projects during the meetups.<br />
<br />
== Location & Schedule ==<br />
<br />
Date: 2016-04-23 18:00 IST onwards<br />
<br />
K 104, Jasminium, Magarpatta City<br />
Pune. <br />
<br />
Note: Please carry a valid ID proof to enter the building. If security guys ask, tell them you are coming to meet Sayan Chowdhury or Kushal Das. <br />
Emergency contact number: +91 8605430990<br />
<br />
== Participants ==<br />
<br />
Please add your name to the end of the list.<br />
<br />
{|<br />
! # !! Name <br />
|-<br />
| 1 || [[User:kushal | Kushal Das]] <br />
|-<br />
| 2 || [[User:kumarpraveen | Praveen Kumar]] <br />
|-<br />
| 3 || [[User:chandankumar | Chandan Kumar]] <br />
|-<br />
| 4 || [[User:siddhesh | Siddhesh]]<br />
|-<br />
| 5 || [[User:girish946 | Girish joshi]]<br />
|-<br />
| 6 || [[User:ganeshkadam | Ganesh Kadam]]<br />
|-<br />
| 7 || [[User:suraj353 | Suraj Narwade]]<br />
|-<br />
| 8 || [[User:satya4ever | Satyajit Bulage]]<br />
|-<br />
| 9 || [[User:pyadav | Pooja Yadav]]<br />
|-<br />
| 10 || [[User:amolkahat | Amol Kahat]]<br />
|-<br />
| 11 || [[User:rahul_bajaj | Rahul Bajaj]]<br />
|}<br />
<br />
== Agenda ==<br />
<br />
* Writing test for fedora Atomic.<br />
<br />
== Pictures and Reports ==<br />
<br />
* http://yadav-pooja.blogspot.in/2016/04/my-first-fedora-meetup.html<br />
* http://surajnarwade.github.io/april-fedora-meetup-unit-testing-revealed.html<br />
* https://satya4ever.wordpress.com/2016/04/25/fedora-meetup-started-contribution-to-fedora<br />
* https://akahat.wordpress.com/2016/04/24/april-fedora-meetup-2016/#more-114<br />
* https://rahulbajaj05.wordpress.com/2016/04/23/fedora-meetup-writing-unittests-in-python/<br />
<br />
[[Category:Marketing]] [[Category:Events]] [[Category:Events 2016]]</div>Kushalhttps://fedoraproject.org/w/index.php?title=Fedora_meetup_Pune_April_2016&diff=445881Fedora meetup Pune April 20162016-05-05T14:00:03Z<p>Kushal: /* Pictures and Reports */ Cleaning up the links to reports</p>
<hr />
<div>{{header|events}}<br />
<br />
= Fedora Events: Fedora meetup Pune, April 2016 =<br />
<br />
== About ==<br />
<br />
This is the third edition of our regular Fedora meetup in Pune. We will learn/discuss about various new technologies being used in the project. We will also work<br />
on various parts of projects during the meetups.<br />
<br />
== Location & Schedule ==<br />
<br />
Date: 2016-04-23 18:00 IST onwards<br />
<br />
K 104, Jasminium, Magarpatta City<br />
Pune. <br />
<br />
Note: Please carry a valid ID proof to enter the building. If security guys ask, tell them you are coming to meet Sayan Chowdhury or Kushal Das. <br />
Emergency contact number: +91 8605430990<br />
<br />
== Participants ==<br />
<br />
Please add your name to the end of the list.<br />
<br />
{|<br />
! # !! Name <br />
|-<br />
| 1 || [[User:kushal | Kushal Das]] <br />
|-<br />
| 2 || [[User:kumarpraveen | Praveen Kumar]] <br />
|-<br />
| 3 || [[User:chandankumar | Chandan Kumar]] <br />
|-<br />
| 4 || [[User:siddhesh | Siddhesh]]<br />
|-<br />
| 5 || [[User:girish946 | Girish joshi]]<br />
|-<br />
| 6 || [[User:ganeshkadam | Ganesh Kadam]]<br />
|-<br />
| 7 || [[User:suraj353 | Suraj Narwade]]<br />
|-<br />
| 8 || [[User:satya4ever | Satyajit Bulage]]<br />
|-<br />
| 9 || [[User:pyadav | Pooja Yadav]]<br />
|-<br />
| 10 || [[User:amolkahat | Amol Kahat]]<br />
|-<br />
| 11 || [[User:rahul_bajaj | Rahul Bajaj]]<br />
|}<br />
<br />
== Agenda ==<br />
<br />
* Writing test for fedora Atomic.<br />
<br />
== Pictures and Reports ==<br />
<br />
- http://yadav-pooja.blogspot.in/2016/04/my-first-fedora-meetup.html<br />
- http://surajnarwade.github.io/april-fedora-meetup-unit-testing-revealed.html<br />
- https://satya4ever.wordpress.com/2016/04/25/fedora-meetup-started-contribution-to-fedora<br />
- https://akahat.wordpress.com/2016/04/24/april-fedora-meetup-2016/#more-114<br />
- https://rahulbajaj05.wordpress.com/2016/04/23/fedora-meetup-writing-unittests-in-python/<br />
<br />
[[Category:Marketing]] [[Category:Events]] [[Category:Events 2016]]</div>Kushalhttps://fedoraproject.org/w/index.php?title=Test_Day:2016_05_10_Cloud_TestdayApp_Metadata&diff=445876Test Day:2016 05 10 Cloud TestdayApp Metadata2016-05-05T12:14:59Z<p>Kushal: Adding more tests</p>
<hr />
<div>= TestdayApp Metadata =<br />
* F24 Cloud test day; https://fedoraproject.org/wiki/Test_Day:2016_05_10_Cloud<br />
<br />
== Basic Tests ==<br />
<br />
* Base startup; https://fedoraproject.org/wiki/QA:Testcase_base_startup<br />
* System logging; https://fedoraproject.org/wiki/QA:Testcase_base_system_logging<br />
* Services start; https://fedoraproject.org/wiki/QA:Testcase_Services_start<br />
* SELinux; https://fedoraproject.org/wiki/QA:Testcase_base_selinux<br />
* Service manipulation; https://fedoraproject.org/wiki/QA:Testcase_base_service_manipulation<br />
<br />
== Atomic Tests ==<br />
<br />
* Image boots; http://fedoraproject.org/wiki/User:Roshi/QA/AtomicTests/Atomic_Image_Boots<br />
* Upgrade works; http://fedoraproject.org/wiki/User:Roshi/QA/AtomicTests/Atomic_Upgrade<br />
* Rollback works; http://fedoraproject.org/wiki/User:Roshi/QA/AtomicTests/Atomic_Rollback<br />
<br />
== Docker tests ==<br />
* Docker install; https://fedoraproject.org/wiki/QA:Testcase_Docker_Install<br />
* Docker storage setup; https://fedoraproject.org/wiki/QA:Testcase_Docker_Storage_Setup<br />
* Docker daemon; https://fedoraproject.org/wiki/QA:Testcase_Docker_Daemon<br />
<br />
== More Atomic related tests ==<br />
<br />
* Atomic command; https://fedoraproject.org/wiki/QA:Testcase_Atomic_command<br />
* Atomic read only mounts; https://fedoraproject.org/wiki/QA:Testcase_Atomic_read_only_mounts<br />
* Atomic root mount; https://fedoraproject.org/wiki/QA:Testcase_Atomic_read_only_mounts<br />
* Atomic tmp mount; https://fedoraproject.org/wiki/QA:Testcase_Tmp_Mount<br />
* Atomic tmp writable; https://fedoraproject.org/wiki/QA/Draft/Testcase_tmp_writable<br />
* Atomic journal written; https://fedoraproject.org/wiki/QA:Testcase_Journal_Written<br />
<br />
== Vagrant test ==<br />
* eth0 naming; https://fedoraproject.org/wiki/QA/Draft/Testcase_Vagrant_eth0_naming</div>Kushalhttps://fedoraproject.org/w/index.php?title=Test_Day:2016_05_10_Cloud&diff=445874Test Day:2016 05 10 Cloud2016-05-05T11:49:25Z<p>Kushal: Just adding text for empty links</p>
<hr />
<div>{{Infobox_group<br />
| name = Fedora Test Day<br />
| image = [[File:Echo-testing-48px.png|link=QA/Test Days]]<br />
| caption = [[Fedora Cloud Test day]]<br />
| date = 2016-05-10<br />
| time = all day<br />
| website = [[QA/Test Days]]<br />
| irc = [irc://irc.freenode.net/#fedora-test-day #fedora-test-day] ([http://webchat.freenode.net/?channels=fedora-test-day webirc])<br />
| fedora_mailing_list = test<br />
}}<br />
<br />
{{admon/note | Can't make the date? | If you come to this page before or after the test day is completed, your testing is still valuable, and you can use the information on this page to test, file any bugs you find at [http://bugzilla.redhat.com Bugzilla], and add your results to the results section. If this page is more than a month old when you arrive here, please check the [[QA/Test_Days|current schedule]] and see if a similar but more recent Test Day is planned or has already happened.}}<br />
<br />
== What to test? ==<br />
<br />
Today's instalment of Fedora Test Day will focus on '''Cloud, Atmoic''' images for Fedora 24.<br />
<br />
== Who's available ==<br />
<br />
The following cast of characters will be available testing, workarounds, bug fixes, and general discussion ...<br />
* Development - [[User:Kushal|Kushal]] (kushal), [[User:Developer2|Developer2]] (irc_nick2)<br />
* Quality Assurance - [[User:Tester1|Tester1]] (irc_nick3), [[User:Tester2|Tester2]] (irc_nick4)<br />
<br />
== Prerequisite for Test Day == <br />
<br />
You will require at least a system with libvirt/kvm installed. Having access to any Openstack or other Cloud IAAS system where you can upload an image will be even better.<br />
<br />
Download the images from below links<br />
<br />
* Cloud Image link [[Will be updated on the day]]<br />
* Atomic Image link [[Will be updated on the day]]<br />
<br />
Here's a chunk which is commonly used for most Test Days. Replace XX with whatever Fedora release is pending:<br />
<br />
* An updated [https://www.happyassassin.net/nightlies.html Fedora 24 nightly Cloud/Atomic image]<br />
<br />
== How to test? ==<br />
<br />
High level details on how a contributor can get involved. This can include (but not limited to):<br />
<br />
* Areas to target with exploratory testing<br />
* A list of pre-defined test cases to execute<br />
* How to report back results<br />
<br />
<br />
=== Run the tests ===<br />
<br />
Visit the [http://testdays.fedorainfracloud.org/events/7 result page] and click on the column title links to see the tests that need to be run: most column titles are links to a specific test case. Follow the instructions there, then enter your results by clicking the ''Enter result'' button for the test.<br />
<br />
=== Exploratory testing ===<br />
<br />
If you run out of test cases, congratulations! But that's not the end! You can still help out by playing around with the tool in whatever ways you can think of: try out all the things you can find, and try writing different Fedora images with it. If you have systems with different Windows versions, try running the tool on all of them. Get creative! Any problems you find please file a bug, or report to the IRC channel.<br />
<br />
== Reporting bugs ==<br />
<br />
<br />
<br />
If you have problems with any of the tests, report a bug to [https://bugzilla.redhat.com Bugzilla]. If you are unsure about exactly how to file the report or what other information to include, just ask on IRC and we will help you.<br />
<br />
IRC Channel name: #fedora-cloud, #fedora-test-day<br />
Server: Freenode<br />
<br />
== Test Results ==<br />
<br />
Please enter your results on the [http://testdays.fedorainfracloud.org/events/7 result page]. The results will be transferred here after the Test Day is finished.<br />
[[Category:Fedora 24 Test Days]]<br />
<br />
<!-- remove this category when creating a test day page --><br />
[[Category:QA Templates]]</div>Kushalhttps://fedoraproject.org/w/index.php?title=Test_Day:2016_05_10_Cloud_TestdayApp_Metadata&diff=445827Test Day:2016 05 10 Cloud TestdayApp Metadata2016-05-05T09:03:34Z<p>Kushal: /* More Atomic related tests */ Fixing typo</p>
<hr />
<div>= TestdayApp Metadata =<br />
* F24 Cloud test day; https://fedoraproject.org/wiki/Test_Day:2016_05_10_Cloud<br />
<br />
== Basic Tests ==<br />
<br />
* Base startup; https://fedoraproject.org/wiki/QA:Testcase_base_startup<br />
* System logging; https://fedoraproject.org/wiki/QA:Testcase_base_system_logging<br />
* Services start; https://fedoraproject.org/wiki/QA:Testcase_Services_start<br />
* SELinux; https://fedoraproject.org/wiki/QA:Testcase_base_selinux<br />
* Service manipulation; https://fedoraproject.org/wiki/QA:Testcase_base_service_manipulation<br />
<br />
== Atomic Tests ==<br />
<br />
* Image boots; http://fedoraproject.org/wiki/User:Roshi/QA/AtomicTests/Atomic_Image_Boots<br />
* Upgrade works; http://fedoraproject.org/wiki/User:Roshi/QA/AtomicTests/Atomic_Upgrade<br />
* Rollback works; http://fedoraproject.org/wiki/User:Roshi/QA/AtomicTests/Atomic_Rollback<br />
<br />
== Docker tests ==<br />
* Docker install; https://fedoraproject.org/wiki/QA:Testcase_Docker_Install<br />
* Docker storage setup; https://fedoraproject.org/wiki/QA:Testcase_Docker_Storage_Setup<br />
* Docker daemon; https://fedoraproject.org/wiki/QA:Testcase_Docker_Daemon<br />
<br />
== More Atomic related tests ==<br />
<br />
* Atomic command; https://fedoraproject.org/wiki/QA:Testcase_Atomic_command<br />
* Atomic read only mounts; https://fedoraproject.org/wiki/QA:Testcase_Atomic_read_only_mounts<br />
* Atomic root mount;https://fedoraproject.org/wiki/QA:Testcase_Atomic_read_only_mounts</div>Kushalhttps://fedoraproject.org/w/index.php?title=Test_Day:2016_05_10_Cloud_TestdayApp_Metadata&diff=445826Test Day:2016 05 10 Cloud TestdayApp Metadata2016-05-05T09:01:37Z<p>Kushal: More tests, yay!</p>
<hr />
<div>= TestdayApp Metadata =<br />
* F24 Cloud test day; https://fedoraproject.org/wiki/Test_Day:2016_05_10_Cloud<br />
<br />
== Basic Tests ==<br />
<br />
* Base startup; https://fedoraproject.org/wiki/QA:Testcase_base_startup<br />
* System logging; https://fedoraproject.org/wiki/QA:Testcase_base_system_logging<br />
* Services start; https://fedoraproject.org/wiki/QA:Testcase_Services_start<br />
* SELinux; https://fedoraproject.org/wiki/QA:Testcase_base_selinux<br />
* Service manipulation; https://fedoraproject.org/wiki/QA:Testcase_base_service_manipulation<br />
<br />
== Atomic Tests ==<br />
<br />
* Image boots; http://fedoraproject.org/wiki/User:Roshi/QA/AtomicTests/Atomic_Image_Boots<br />
* Upgrade works; http://fedoraproject.org/wiki/User:Roshi/QA/AtomicTests/Atomic_Upgrade<br />
* Rollback works; http://fedoraproject.org/wiki/User:Roshi/QA/AtomicTests/Atomic_Rollback<br />
<br />
== Docker tests ==<br />
* Docker install; https://fedoraproject.org/wiki/QA:Testcase_Docker_Install<br />
* Docker storage setup; https://fedoraproject.org/wiki/QA:Testcase_Docker_Storage_Setup<br />
* Docker daemon; https://fedoraproject.org/wiki/QA:Testcase_Docker_Daemon<br />
<br />
== More Atomic related tests ==<br />
<br />
* Atomic command; https://fedoraproject.org/wiki/QA:Testcase_Atomic_command<br />
* Atomic read only; mounts; https://fedoraproject.org/wiki/QA:Testcase_Atomic_read_only_mounts<br />
* Atomic root mount;https://fedoraproject.org/wiki/QA:Testcase_Atomic_read_only_mounts</div>Kushalhttps://fedoraproject.org/w/index.php?title=QA:Testcase_Docker_Daemon&diff=445824QA:Testcase Docker Daemon2016-05-05T08:54:22Z<p>Kushal: Removing the extra text</p>
<hr />
<div>{{QA/Test_Case<br />
|description=We are going to test that Docker daemon starts successfully.<br />
|setup=Test this on Atomic image.<br />
|actions=<br />
Be as specific as required for the target audience. <br />
# ssh into an Atomic/Cloud instance.<br />
# If it is a cloud base image then install docker<br />
<br />
$ sudo dnf install docker -y<br />
<br />
# Next we will start docker deamon. (No need on an Atomic instance)<br />
<br />
$ systemctl start docker.service<br />
<br />
# Check the status of the docker service<br />
<br />
$ systemctl status docker.service<br />
<br />
|results=<br />
The following must be true to consider this a successful test run.<br />
# Step #1 You will be able to login into Atomic instance.<br />
# Step #2 You will see output like this:<br />
<br />
$ systemctl status docker.service<br />
● docker.service - Docker Application Container Engine<br />
Loaded: loaded (/usr/lib/systemd/system/docker.service; enabled; vendor preset: disabled)<br />
Active: active (running) since Thu 2016-05-05 07:21:25 IST; 6h ago<br />
Docs: http://docs.docker.com<br />
Main PID: 1104 (docker)<br />
CGroup: /system.slice/docker.service<br />
└─1104 /usr/bin/docker daemon --selinux-enabled<br />
<br />
|optional=Optionally provide hints for exploratory testing.<br />
}}</div>Kushalhttps://fedoraproject.org/w/index.php?title=QA:Testcase_Docker_Daemon&diff=445823QA:Testcase Docker Daemon2016-05-05T08:53:38Z<p>Kushal: Updating the steps</p>
<hr />
<div>{{QA/Test_Case<br />
|description=We are going to test that Docker daemon starts successfully.<br />
|setup=Test this on Atomic image.<br />
|actions=<br />
Be as specific as required for the target audience. <br />
# ssh into an Atomic/Cloud instance.<br />
# If it is a cloud base image then install docker<br />
<br />
$ sudo dnf install docker -y<br />
<br />
# Next we will start docker deamon. (No need on an Atomic instance)<br />
<br />
$ systemctl start docker.service<br />
<br />
# Check the status of the docker service<br />
<br />
$ systemctl status docker.service<br />
<br />
|results=<br />
The following must be true to consider this a successful test run. Be brief ... but explicit. <br />
# Step #1 You will be able to login into Atomic instance.<br />
# Step #2 You will see output like this:<br />
<br />
$ systemctl status docker.service<br />
● docker.service - Docker Application Container Engine<br />
Loaded: loaded (/usr/lib/systemd/system/docker.service; enabled; vendor preset: disabled)<br />
Active: active (running) since Thu 2016-05-05 07:21:25 IST; 6h ago<br />
Docs: http://docs.docker.com<br />
Main PID: 1104 (docker)<br />
CGroup: /system.slice/docker.service<br />
└─1104 /usr/bin/docker daemon --selinux-enabled<br />
<br />
|optional=Optionally provide hints for exploratory testing.<br />
}}</div>Kushal