Re: [openstack-dev] [Ironic] Driver documentation in Ironic

> > 2) Driver docs may not be backported to stable branches. This is a > stable maintenance policy, not an Ironic policy. This problem is > somewhat unique to Ironic as most major projects have deployer docs in > the Ops guide repo, rather than in the code repo. I'm going to chat with > some

[openstack-dev] [Ironic] Driver documentation in Ironic

As mentioned in the weekly IRC, 3rd-party vendor drivers are ranked lower priority and therefore their code tend to merge at the late cycle of a release. Therefore, it leads little time for driver author to submit document and for upstream to review and approve the document. So, as the result,

Re: [openstack-dev] [Ironic] Driver documentation in Ironic

On Wed, Oct 21, 2015 at 03:30:05PM -0700, Wan-yen Hsu wrote: > As mentioned in the weekly IRC, 3rd-party vendor drivers are ranked lower > priority and therefore their code tend to merge at the late cycle of a > release. Therefore, it leads little time for driver author to submit > document and

Re: [openstack-dev] [Ironic] Driver documentation in Ironic

Hi Ramesh, On 15 October 2015 at 11:53, Ramakrishnan G wrote: > > > So what all are the problems ? > 1) Ability to update the driver documentation not-related to Ironic easily > without waiting. > 2) To save some core reviewers time who might not be familiar with

Re: [openstack-dev] [Ironic] Driver documentation in Ironic

Hi Wan-yen, On 19 October 2015 at 01:46, Wan-yen Hsu wrote: > > > I fully agreed with Ramesh. There is a need for driver owners to be able > to quickly update their driver’s document. Particularly, vendor's drivers > have strong > What do you mean by 'quickly'? Quicker

Re: [openstack-dev] [Ironic] Driver documentation in Ironic

On 10/19/2015 01:46 AM, Wan-yen Hsu wrote: I fully agreed with Ramesh. There is a need for driver owners to be able to quickly update their driver’s document. Particularly, vendor's drivers have strong dependencies on their platform’s firmware. For instance, a new release of firmware may

Re: [openstack-dev] [Ironic] Driver documentation in Ironic

On Thu, Oct 15, 2015 at 09:23:18PM +0530, Ramakrishnan G wrote: > Hi All, > > This mail is related to driver-specific documentation in Ironic. > > First a bit of context. I work on iLO drivers in Ironic. Our team would > like to document both Ironic driver related stuff (which is related to >

[openstack-dev] [Ironic] Driver documentation in Ironic

I fully agreed with Ramesh. There is a need for driver owners to be able to quickly update their driver’s document. Particularly, vendor's drivers have strong dependencies on their platform’s firmware. For instance, a new release of firmware may have impact on vendor’s driver and may require a

[openstack-dev] [Ironic] Driver documentation in Ironic

Hi All, This mail is related to driver-specific documentation in Ironic. First a bit of context. I work on iLO drivers in Ironic. Our team would like to document both Ironic driver related stuff (which is related to Ironic) and hardware related stuff like tested platforms, firmware information,