https://www.opencompute.org/w/api.php?action=feedcontributions&user=DanHyland&feedformat=atomOpenCompute - User contributions [en]2024-03-29T06:02:18ZUser contributionsMediaWiki 1.39.2https://www.opencompute.org/w/index.php?title=C%26I_Wiki_Portal&diff=184C&I Wiki Portal2014-02-07T17:12:11Z<p>DanHyland: </p>
<hr />
<div>==WELCOME==<br />
<br />
:Welcome to the OCP '''Conformance & Interoperability''' Project.<br />
<br />
:This Project is open to the public and we want to welcome all those who would like to be involved.<br />
<br />
==Get Involved==<br />
<br />
===Events=== <br />
<br />
:This project meets annually at the OCP Summit events. More information on these events and other OCP can be found on the OCP events page at:<br />
<br />
http://www.opencompute.org/community/events/<br />
<br />
===Meetings===<br />
<br />
:This project meets every first and third Monday via a conference call. This call is open to the public. <br />
:The agenda as well as information on how to join the call can be found at: TBD<br />
<br />
:List of meeting notes/minuets can be found here:[[C%26I_Meeting_Notes|Meeting Notes]]<br />
<br />
<br />
<br />
===Communication===<br />
<br />
:Mailing List - opencompute-ci@lists.opencompute.org <br />
to subscribe - http://lists.opencompute.org/mailman/listinfo/opencompute-ci<br />
:IRC Channel - #ocp-ci on irc.freenode.ne<br />
:Website - http://www.opencompute.org/projects/compliance-and-interoperability/<br />
<br />
<br />
:[[C&I Project Tracks & Contact List]]<br />
<br />
<br />
<br />
<br />
----<br />
:C&I Project Chair:<br />
::[mailto:yf.juan@itri.org.tw YF Juan], ITRI</div>DanHylandhttps://www.opencompute.org/w/index.php?title=C%26I_Meeting_Notes&diff=174C&I Meeting Notes2014-02-03T22:29:39Z<p>DanHyland: </p>
<hr />
<div>=Meeting Notes=<br />
<br />
==1/27/14-1/28/14 OCP Summit V @ San Jose Convention Center==<br />
<br />
===Day 1 -- "Ready" vs. "Certified"===<br />
<br />
'''OCP Ready'''<br />
*Ready is executed via self tes*ting from respective hardware vendors<br />
*Should be considered a software only toolkit<br />
*Not a comprehensive certification<br />
*Should be included as a subset of OCP Certified<br />
*Purpose is to lower the barrier of entry of OCP Hardware<br />
*Goal is conform to OCP Hardware Management Spec (Insert link)<br />
*'''[Question]''' - Should recertification take place as OCP Ready iterates? (example: 1.0->1.1)<br />
<br />
<br />
'''OCP Certified'''<br />
*Certification is executed by certification Labs (ITRI/UTSA)<br />
<br />
<br />
'''What is the scope of the certification?'''<br />
*'''[Question]''' - Are we certifying a motherboard/Model/Sku/Bios Rev/Firmware Rev?<br />
*Configuration should be "Max configuration"<br />
*'''[Question]''' - How do we handle different components?<br />
**HDD Amount vs. HDD Configuration vs. Memory Population vs. Memory Amount<br />
**We should look to put ownership on vendor to create respective Hardware Compatibility Lists (HCL) or Approved Vendor Lists (AVL) for sub components<br />
*'''[Question]''' - How do we handle configuration proliferation?<br />
<br />
<br />
'''What are we trying to solve?<br />
*Needs to be clearly defined<br />
<br />
<br />
'''OCP Labs'''<br />
*Cost of certifying (yet to be determined by OCP Foundation) is a revenue source for OCP<br />
*Official determination of certified is done by OCP, not respective Labs<br />
*'''[Question]''' - During certification, if a test fails, how do we notify vendor?<br />
*'''[Question]''' - How do we handle bios/firmware upgrades with respect to previously certified systems?<br />
**Possibly not charge for recertification?<br />
<br />
<br />
'''Action Items:'''<br />
*Work out structure for maintaining and publishing for both Ready and Certified Packages<br />
*Provide documentation for Disposable OS (DOS) for USB Deployment<br />
**Joel Wineland<br />
*Identify what "Max Configuration" means, in terms of hardware to test?<br />
**Example: Populate all HDD bays, Memory slots, Mezz slots<br />
<br />
<br />
===Day 2 -- "Use the email list more!!!"===<br />
<br />
<br />
'''Wiki'''<br />
*Pull Ready/Certified to top of the page (Main Page)<br />
*Move minimum documentation and need that within certified<br />
<br />
<br />
'''FAQ'''<br />
*'''[Question]''' - What does the customer need to know?<br />
*'''[Question]''' - What is minimum criteria?<br />
*Should look to focus more so on community driven support<br />
**Possibly look to establish a '''community based forum''' for OCP users to collbaorate/discuss deployments and reference diagrams.<br />
<br />
<br />
'''Software Framework and Tools'''<br />
*We should look to move these into Ready/Certified respectively and maintain as apart of the respective release cycles<br />
<br />
<br />
'''C&I Branding and Marketing'''<br />
*Hugh is now in charge<br />
*Needs to be defined<br />
*Internally we should look to evangelize/market C&I within the OCP Foundation in order to gain recognition and support<br />
<br />
<br />
'''Training'''<br />
*Remove<br />
<br />
<br />
'''Project communications'''<br />
*Remove, responsibility is taken on by OCP Foundation<br />
<br />
<br />
'''Pre-certification "Tested Configuration" repository'''<br />
*"Doesn't belong but don't forget"<br />
<br />
<br />
'''Ecosystem Optimization'''<br />
*'''[Question]''' - Thao, is this ok?</div>DanHylandhttps://www.opencompute.org/w/index.php?title=C%26I_Meeting_Notes&diff=173C&I Meeting Notes2014-02-03T22:27:24Z<p>DanHyland: Created page with "=Meeting Notes= ==1/27/14-1/28/14 OCP Summit V @ San Jose Convention Center== ===Day 1 -- "Ready" vs. "Certified"=== '''OCP Ready''' *Ready is executed via self tes*ting fr..."</p>
<hr />
<div>=Meeting Notes=<br />
<br />
==1/27/14-1/28/14 OCP Summit V @ San Jose Convention Center==<br />
<br />
===Day 1 -- "Ready" vs. "Certified"===<br />
<br />
'''OCP Ready'''<br />
*Ready is executed via self tes*ting from respective hardware vendors<br />
*Should be considered a software only toolkit<br />
*Not a comprehensive certification<br />
*Should be included as a subset of OCP Certified<br />
*Purpose is to lower the barrier of entry of OCP Hardware<br />
*Goal is conform to OCP Hardware Management Spec (Insert link)<br />
*'''[Question]''' - Should recertification take place as OCP Ready iterates? (example: 1.0->1.1)<br />
<br />
<br />
'''OCP Certified'''<br />
*Certification is executed by certification Labs (ITRI/UTSA)<br />
<br />
<br />
'''What is the scope of the certification'''<br />
*'''[Question]''' - Are we certifying a motherboard/Model/Sku/Bios Rev/Firmware Rev?<br />
*Configuration should be "Max configuration"<br />
*'''[Question]''' - How do we handle different components?<br />
**HDD Amount vs. HDD Configuration vs. Memory Population vs. Memory Amount<br />
**We should look to put ownership on vendor to create respective Hardware Compatibility Lists (HCL) or Approved Vendor Lists (AVL) for sub components<br />
*'''[Question]''' - How do we handle configuration proliferation?<br />
<br />
<br />
'''What are we trying to solve?<br />
*Needs to be clearly defined<br />
<br />
<br />
'''OCP Labs'''<br />
*Cost of certifying (yet to be determined by OCP Foundation) is a revenue source for OCP<br />
*Official determination of certified is done by OCP, not respective Labs<br />
*'''[Question]''' - During certification, if a test fails, how do we notify vendor?<br />
*'''[Question]''' - How do we handle bios/firmware upgrades with respect to previously certified systems?<br />
**Possibly not charge for recertification?<br />
<br />
<br />
'''Action Items:'''<br />
*Work out structure for maintaining and publishing for both Ready and Certified Packages<br />
*Provide documentation for Disposable OS (DOS) for USB Deployment<br />
**Joel Wineland<br />
*Identify what "Max Configuration" means, in terms of hardware to test?<br />
**Example: Populate all HDD bays, Memory slots, Mezz slots<br />
<br />
<br />
===Day 2 -- "Use the email list more!!!"===<br />
<br />
<br />
'''Wiki'''<br />
*Pull Ready/Certified to top of the page (Main Page)<br />
*Move minimum documentation and need that within certified<br />
<br />
<br />
'''FAQ'''<br />
*'''[Question]''' - What does the customer need to know?<br />
*'''[Question]''' - What is minimum criteria?<br />
*Should look to focus more so on community driven support<br />
**Possibly look to establish a '''community based forum''' for OCP users to collbaorate/discuss deployments and reference diagrams.<br />
<br />
<br />
'''Software Framework and Tools'''<br />
*We should look to move these into Ready/Certified respectively and maintain as apart of the respective release cycles<br />
<br />
<br />
'''C&I Branding and Marketing'''<br />
*Hugh is now in charge<br />
*Needs to be defined<br />
*Internally we should look to evangelize/market C&I within the OCP Foundation in order to gain recognition and support<br />
<br />
<br />
'''Training'''<br />
*Remove<br />
<br />
<br />
'''Project communications'''<br />
*Remove, responsibility is taken on by OCP Foundation<br />
<br />
<br />
'''Pre-certification "Tested Configuration" repository'''<br />
*"Doesn't belong but don't forget"<br />
<br />
<br />
'''Ecosystem Optimization'''<br />
*'''[Question]''' - Thao, is this ok?</div>DanHyland