Re: [openstack-dev] [DriverLog][nova][neutron][cinder] Call for vendor participation please
Hi, Thanks for the effort. While I am looking the website and the driver database, I have a couple of questions and suggestions. - Is it better to include trunk (= Juno) in releases in each driver if it is a part of the trunk or to wait it until Juno is released? We need some guidelines on this. - Which is better as maintainer email, an individual mail address or CI account contact address? IMO an individual mail address looks better because CI account contact address receives all review comments and mails to the address can be missed or not noticed soon from my experience. It is better to have some guideline on the maintainer email. - How is the status of CI tested determined? I am not sure how it is handled in Wiki informaiton. - (Related to the above) How does DriverLog handle a case where multiple drivers are tested under once CI account? AFAIK some CI acounts run third party testing for multiple drivers. - releases in drivers section is a list of release names now. It means we need to update releases in every release. I wonder we can support [from_release, to_release] style. If to_release is omitted, it means trunk. Thanks, Akihiro (2014/04/29 2:05), Jay Pipes wrote: Hi Stackers, Mirantis has been collaborating with a number of OpenStack contributors and PTLs for the last couple months on something called DriverLog. It is an effort to consolidate and display information about the verification of vendor drivers in OpenStack. Current implementation is here: http://staging.stackalytics.com/driverlog/ Public wiki here: https://wiki.openstack.org/wiki/DriverLog Code is here: https://github.com/stackforge/driverlog There is currently a plan by the foundation to publicly announce this in the coming weeks. At this point Evgeniya Shumakher, in cc, is manually maintaining the records, but we aspire for this to become a community driven process over time with vendors submitting updates as described in the wiki and PTLs and cores of the respective projects participating in update reviews. A REQUEST: If you are vendor that has built an OpenStack driver, please check that it is listed on the dashboard and update the record (following the process in the wiki) to make sure the information is accurately reflected. We want to make sure that the data is accurate prior to announcing it to general public. Also, if anybody has a suggestion on what should be improved / changed etc. == please don’t hesitate to share your ideas! Thanks! Jay and Evgeniya ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [DriverLog][nova][neutron][cinder] Call for vendor participation please
Hi Akihiro, Please see my comments inline. 2014-05-07 10:35 GMT+04:00 Akihiro Motoki mot...@da.jp.nec.com: Hi, Thanks for the effort. While I am looking the website and the driver database, I have a couple of questions and suggestions. - Is it better to include trunk (= Juno) in releases in each driver if it is a part of the trunk or to wait it until Juno is released? We need some guidelines on this. For drivers that have external CI application explicitly converts results for master branch into the latest release (=Juno), but probably this is a bit misleading since release doesn't exist yet. I give Evgenia and Boris a chance to comment on this. - Which is better as maintainer email, an individual mail address or CI account contact address? IMO an individual mail address looks better because CI account contact address receives all review comments and mails to the address can be missed or not noticed soon from my experience. It is better to have some guideline on the maintainer email. I'd prefer individual email too or (as an option) an alias of team that supports driver. - How is the status of CI tested determined? I am not sure how it is handled in Wiki informaiton. Status CI tested means that driver is tested by vendor and test results are attached to gerrit review. Currently DriverLog takes into account votes only, so if CI doesn't vote (even if leaves a comment) then it is treated as CI not present. The code is implemented this way because format of test result comment is not unified and differs from driver to driver. To specify that driver has CI the one needs to provide CI's gerrit id in attribute ci_id, for example like this https://github.com/stackforge/driverlog/blob/master/etc/default_data.json#L343 - (Related to the above) How does DriverLog handle a case where multiple drivers are tested under once CI account? AFAIK some CI acounts run third party testing for multiple drivers. It is not handled correctly and is subject to discuss and re-implement. For example in Neutron Big Switch CI runs tests against 2 drivers, but sets only 1 vote. Seems like solution may be to parse comment from CI. - releases in drivers section is a list of release names now. It means we need to update releases in every release. I wonder we can support [from_release, to_release] style. If to_release is omitted, it means trunk. This is made intentionally, so maintainers verify list of drivers before every release and add new release only if everything works. Thanks, Akihiro Thanks, Ilya (2014/04/29 2:05), Jay Pipes wrote: Hi Stackers, Mirantis has been collaborating with a number of OpenStack contributors and PTLs for the last couple months on something called DriverLog. It is an effort to consolidate and display information about the verification of vendor drivers in OpenStack. Current implementation is here: http://staging.stackalytics.com/driverlog/ Public wiki here: https://wiki.openstack.org/wiki/DriverLog Code is here: https://github.com/stackforge/driverlog There is currently a plan by the foundation to publicly announce this in the coming weeks. At this point Evgeniya Shumakher, in cc, is manually maintaining the records, but we aspire for this to become a community driven process over time with vendors submitting updates as described in the wiki and PTLs and cores of the respective projects participating in update reviews. A REQUEST: If you are vendor that has built an OpenStack driver, please check that it is listed on the dashboard and update the record (following the process in the wiki) to make sure the information is accurately reflected. We want to make sure that the data is accurate prior to announcing it to general public. Also, if anybody has a suggestion on what should be improved / changed etc. == please don’t hesitate to share your ideas! Thanks! Jay and Evgeniya ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [DriverLog][nova][neutron][cinder] Call for vendor participation please
Hi Stackers, Mirantis has been collaborating with a number of OpenStack contributors and PTLs for the last couple months on something called DriverLog. It is an effort to consolidate and display information about the verification of vendor drivers in OpenStack. Current implementation is here: http://staging.stackalytics.com/driverlog/ Public wiki here: https://wiki.openstack.org/wiki/DriverLog Code is here: https://github.com/stackforge/driverlog There is currently a plan by the foundation to publicly announce this in the coming weeks. At this point Evgeniya Shumakher, in cc, is manually maintaining the records, but we aspire for this to become a community driven process over time with vendors submitting updates as described in the wiki and PTLs and cores of the respective projects participating in update reviews. A REQUEST: If you are vendor that has built an OpenStack driver, please check that it is listed on the dashboard and update the record (following the process in the wiki) to make sure the information is accurately reflected. We want to make sure that the data is accurate prior to announcing it to general public. Also, if anybody has a suggestion on what should be improved / changed etc. == please don’t hesitate to share your ideas! Thanks! Jay and Evgeniya ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
