Bug #44749 ndb_config --xml: hostname as valid key and MaxNoOfOpenFiles need fix

Description:
ndb_config --xml needs fix for the following:

MaxNoOfOpenFiles should not have a default (or a default within the min / max boundaries)
HostName - should be a valid key

to be consistent with what you actually can put into config.ini

How to repeat:
run ndb_config --xml --configinfo and note that HostName is missing although a valid key, and MaxNoOfOpenFiles=0 is not valid.

A patch for this bug has been committed. After review, it may
be pushed to the relevant source trees for release in the next
version. You can access the patch from:

  http://lists.mysql.com/commits/73664

Pushed into 5.1.34-ndb-6.3.25 (revid:magnus.blaudd@sun.com-20090518121246-zp3gju1pobzcb0x8) (version source revid:magnus.blaudd@sun.com-20090518121246-zp3gju1pobzcb0x8) (merge vers: 5.1.34-ndb-6.3.25) (pib:6)

Pushed into 5.1.34-ndb-7.0.6 (revid:magnus.blaudd@sun.com-20090518130935-dtpb708as2r6fzn6) (version source revid:magnus.blaudd@sun.com-20090518121313-bajhjq3qrvdpd6f3) (merge vers: 5.1.34-ndb-7.0.6) (pib:6)

Pushed into 5.1.34-ndb-6.3.25 (revid:magnus.blaudd@sun.com-20090519135829-xedif18zi226cs78) (version source revid:magnus.blaudd@sun.com-20090519135829-xedif18zi226cs78) (merge vers: 5.1.34-ndb-6.3.25) (pib:6)

A patch for this bug has been committed. After review, it may
be pushed to the relevant source trees for release in the next
version. You can access the patch from:

  http://lists.mysql.com/commits/74477

Pushed into 5.1.34-ndb-7.0.6 (revid:magnus.blaudd@sun.com-20090519140027-dt0vrn3e8pkpmi9c) (version source revid:magnus.blaudd@sun.com-20090519140027-dt0vrn3e8pkpmi9c) (merge vers: 5.1.34-ndb-7.0.6) (pib:6)

Documented bugfix in the NDB-6.3.25 and 7.0.6 changelogs as follows:'

        The output of ndb_config --xml did not provide information about
        all sections of the configuration file.

Closed.

Corrected changelog entry:

        ndbconfig --xml did not output any entries for the HostName
        parameter. In addition, the default listed for MaxNoOfFiles was
        outside the allowed range of values.

(Accidentally switched with another bug report.)