1. 07 2月, 2020 1 次提交
  2. 04 12月, 2019 2 次提交
  3. 27 6月, 2019 2 次提交
  4. 21 6月, 2019 1 次提交
  5. 20 6月, 2019 2 次提交
  6. 11 4月, 2019 1 次提交
  7. 31 1月, 2019 2 次提交
  8. 05 11月, 2018 1 次提交
  9. 11 11月, 2016 10 次提交
  10. 01 4月, 2016 1 次提交
  11. 31 3月, 2016 6 次提交
  12. 11 3月, 2016 1 次提交
  13. 06 6月, 2014 1 次提交
  14. 27 1月, 2014 1 次提交
  15. 31 10月, 2013 1 次提交
  16. 08 8月, 2013 1 次提交
    • D
      Add info about access control checks into API reference · 664ab280
      Daniel P. Berrange 提交于
      So that app developers / admins know what access control checks
      are performed for each API, this patch extends the API docs
      generator to include details of the ACLs for each.
      
      The gendispatch.pl script is extended so that it generates
      a simple XML describing ACL rules, eg.
      
        <aclinfo>
          ...
          <api name='virConnectNumOfDomains'>
            <check object='connect' perm='search_domains'/>
            <filter object='domain' perm='getattr'/>
          </api>
          <api name='virDomainAttachDeviceFlags'>
            <check object='domain' perm='write'/>
            <check object='domain' perm='save' flags='!VIR_DOMAIN_AFFECT_CONFIG|VIR_DOMAIN_AFFECT_LIVE'/>
            <check object='domain' perm='save' flags='VIR_DOMAIN_AFFECT_CONFIG'/>
          </api>
          ...
        </aclinfo>
      
      The newapi.xsl template loads the XML files containing the ACL
      rules and generates a short block of HTML for each API describing
      the parameter checks and return value filters (if any).
      Signed-off-by: NDaniel P. Berrange <berrange@redhat.com>
      664ab280
  17. 01 2月, 2013 1 次提交
  18. 18 1月, 2013 1 次提交
  19. 28 10月, 2011 1 次提交
    • D
      Add documentation about migration. · a7847844
      Daniel P. Berrange 提交于
      This adds a page documenting many aspects of migration:
      
       - The types of migration (managed direct, p2p, unmanaged direct)
       - Data transports (native, tunnelled)
       - Migration URIs
       - Config file handling
       - Example scenarios
      
      * libvirt.css: Rules for data tables and diagrams
      * Makefile.am: Include extra png/fig files
      * migration-managed-direct.fig, migration-managed-direct.png,
        migration-managed-direct.png, migration-managed-p2p.png,
        migration-native.fig, migration-native.png,
        migration-tunnel.fig, migration-tunnel.png,
        migration-unmanaged-direct.fig, migration-unmanaged-direct.png:
        Diagrams of migration
      * migration.html.in, sitemap.html.in: New migration doc
      a7847844
  20. 12 8月, 2011 1 次提交
    • P
      Align table cells on top · 447e4c46
      Philipp Hahn 提交于
      When the description of an entry is too long and needs multiple lines,
      all other table cells of the same row are currently vertically aligned
      on center. Without row borders or different background colors for
      alternating rows this is hard to read.
      
      Change the style-sheet to align the table cells of a row on top.
      Signed-off-by: NPhilipp Hahn <hahn@univention.de>
      447e4c46
  21. 18 12月, 2010 1 次提交
    • M
      docs: Add additional indentation to level 3 menu items · 1e55c382
      Matthias Bolte 提交于
      formatnetwork.html has a menu item at level 3. libvirt.css
      doesn't have a explicit rule for level 3 and level 3 and
      level 2 items end up at the same indentation level.
      
      Add an additional 1em indentation to level 3 menu items.
      1e55c382
  22. 05 2月, 2010 1 次提交