22:36:10 <trevor_intel> #startmeeting OPNFV Test and Performance
22:36:10 <collabot> Meeting started Wed May 20 22:36:10 2015 UTC.  The chair is trevor_intel. Information about MeetBot at http://wiki.debian.org/MeetBot.
22:36:10 <collabot> Useful Commands: #action #agreed #help #info #idea #link #topic.
22:36:10 <collabot> The meeting name has been set to 'opnfv_test_and_performance'
22:36:23 <trevor_intel> #topic Pharos planning and brainstorming
22:36:33 <trevor_intel> #info Trevor Cooper
22:36:51 <fdegir> #info Fatih Degirmenci
22:37:51 <trevor_intel> #info others attending at OS Summit - Sean (EMC), Uli Hui, Wenjing, Fu Qiao
22:38:22 <ulik> #info Uli
22:39:21 <trevor_intel> #info Pharos defines the pre-install state of the environment?
22:42:19 <bryan_att> #info Bryan Sullivan
22:42:59 <trevor_intel> #info     Deployment tools - discover      what is there and deploy accordingly
22:43:27 <trevor_intel> #info define requirements vs what is      flexible
22:43:37 <trevor_intel> #nfo must define end state not implementation
22:44:36 <trevor_intel> #info must define end state not implementation
22:47:36 <trevor_intel> #info MAAS is an option for hardware management
22:53:39 <trevor_intel> #info is it feasible to define profiles?
22:54:09 <trevor_intel> #info what do installers need for config?
22:55:12 <trevor_intel> #info Paros ask for info from installer projects
22:56:13 <trevor_intel> #info Pharos merge form 3 installers -> proposal -> installers review
22:59:29 <trevor_intel> #info To define plumbing, consistent state, naming conventions for infrastructure
23:06:28 <bryan_att> fyi I will be submitting a review patch to the pharos release doc to address formatting issues
23:10:27 <trevor_intel> #info Pharos provides 1) GUIDELINES AND TEMPLATES (ideally a file/format that each installer reads) 2) Checklist (Pharos comliance) 3) Acceptance tests?
23:10:49 <trevor_intel> TThansk Bryan
23:10:56 <trevor_intel> thanks
23:12:37 <bryan_att> PHAROS-16
23:14:41 <trevor_intel> #info accessibility ... Uli proposes use cases 1) private developers 2) virtual deployment 3) test-lab a) small b) medium c) large
23:15:13 <trevor_intel> bryan_att: I will review
23:15:33 <bryan_att> thanks, trying to get engaged
23:15:54 <trevor_intel> me too :)
23:22:54 <trevor_intel> #info immediate goals 1) specifying hw environment 2) uniform way to access 3) tracking (dashboard) for monitoring
23:33:08 <trevor_intel> #action Next steps ... Trevor to get 1) feedback/input on 1) infrastructure templates from lab owners 2) state configuration templates from installers
23:33:19 <trevor_intel> #endmeeting