Skip to content
Snippets Groups Projects
  1. Jul 25, 2022
  2. Jul 22, 2022
    • Dmitry Tantsur's avatar
      Remove deprecated stuff from baremetal_node · 2d60a045
      Dmitry Tantsur authored
      Change-Id: Ia9fbc5b136347145d1a7ddc2d874f014c06558ae
      2d60a045
    • Jakob Meng's avatar
      Dropped symbolic links and plugin routing for deprecated module names · b87ae7dc
      Jakob Meng authored
      With Ansible OpenStack collection 2.0.0 we break backward
      compatibility to older releases, mainly due to breaking changes
      coming with openstacksdk >=0.99.0. For example, results will change
      for most Ansible modules in this collection.
      
      We take this opportunity to drop the symbolic links with prefix
      os_ in plugins/modules and the plugin routing in meta/runtime.yml.
      This means users have to call modules of the Ansible OpenStack
      collection using their FQCN (Fully Qualified Collection Name) such
      as openstack.cloud.server. Short module names such as os_server
      will now raise an Ansible error. This also decreases the likelihood
      of incompatible Ansible code going undetected.
      
      Symbolic links were introduced to keep our collection backward
      compatible to user code which was written for old(er) Ansible releases
      which did not have support for collections and where OpenStack modules
      where named with a prefix os_ such as os_server which is nowadays
      known and stored as openstack.cloud.server.
      
      In Ansible aka ansible-base 2.10, a internal routing table
      lib/ansible/config/ansible_builtin_runtime.yml [1] was introduced which
      Ansible uses to resolve deprecated module names missing the FQCN (Fully
      Qualified Collection Name). Additionally, collections can define their
      own plugin routing table in meta/runtime.yml [2] which we did.
      
      In ansible-base 2.10 and ansible-core 2.11 or later, if a user uses a
      short module name and the collections keyword is not used, Ansible
      will first look in the internal routing table, get an FQCN, and then
      looks in the collection for that FQCN. If there is another routing
      entry for that new name in that collection's meta/runtime.yml,
      Ansible will continue with that redirect. If it does not find another
      redirect, Ansible will look for the plugin itself, so it will not
      find a redirect in the collection before looking at its internal
      redirects. Except if the user uses a FQCN, then it looks directly in
      that collection.
      
      Ansible 2.9 and 2.8 do not have any notion of these redirects with a
      plugin routing table, backward compatibility with deprecated os_*
      module names is solely achieved with symbolic links. Ansible releases
      older than 2.11 are EOL [3], so usage of os_* symlinks should reduce
      soon.
      
      [1] https://github.com/ansible/ansible/blob/devel/lib/ansible/config/ansible_builtin_runtime.yml
      [2] https://github.com/openstack/ansible-collections-openstack/blob/master/meta/runtime.yml
      [3] https://docs.ansible.com/ansible/devel/reference_appendices/release_and_maintenance.html
      
      Change-Id: I28cc05c95419b72552899c926721eb87fb6f0868
      b87ae7dc
  3. Jul 21, 2022
  4. Jul 20, 2022
    • Arx Cruz's avatar
      Update port info · 960e5df1
      Arx Cruz authored
      Make it compatible with new openstack sdk 1.0.0
      
      Change-Id: I911eecd31ee69dbde1da02a74e152746c1e3edfa
      960e5df1
  5. Jul 19, 2022
  6. Jul 18, 2022
  7. Jul 15, 2022
    • Jakob Meng's avatar
      Replaced code in routers_info module with openstacksdk function · 1f5a2019
      Jakob Meng authored
      Replaced custom code for interface listing with call to openstacksdk.
      The original idea was to reduce the number of calls to the OpenStack
      API but this kind of optimization is better to be implemented in the
      SDK itself [1]. Reimplementing code like this increases our
      maintenance burden, does not help other SDK users and increases the
      likeliness of bugs. For example, variable allowed_device_owners
      introduced a bug, it is not 'network_router_interface_distributed'
      but 'network:router_interface_distributed'.
      
      [1] https://review.opendev.org/c/openstack/openstacksdk/+/849967
      
      Change-Id: I9c52de03c53ef29d7cecdf26253c0c00a7cf3689
      1f5a2019
  8. Jul 12, 2022
  9. Jul 06, 2022
  10. Jul 05, 2022
  11. Jul 04, 2022
  12. Jun 29, 2022
  13. Jun 28, 2022
    • Rafael Castillo's avatar
      Update image for new sdk · 2419b5ab
      Rafael Castillo authored
      - Use proxy layer where possible
        - Image upload has some tricky logic so that stays in the cloud layer
      - Convert return value to dict
      - Document return values
      - Update visibility logic for glance v2 api
      - Increase test coverage
      - General refactoring to bring more in line with rest of collection
      - Deprecate is_public attribute which has been replaced with
        visibility.
      - Deprecate volume attribute which has been made obsolete with
        openstack.cloud.volume module. Removed examples showing the volume
        attribute since users are encouraged to use openstack.cloud.volume
        module.
      
      Change-Id: I1d8034a3b9a391444ea275b68b06ee3a291c73c3
      2419b5ab
  14. Jun 27, 2022
  15. Jun 26, 2022
  16. Jun 23, 2022
    • Arx Cruz's avatar
      Update project_info module to new sdk · bcca2efe
      Arx Cruz authored
      Make project_info module compatible with the new sdk 1.0.0 and also add
      ansible tests for project_info module
      
      Change-Id: I413200cf6a9b8bada7e5d78087246b888d53fac2
      bcca2efe
  17. Jun 20, 2022
  18. Jun 17, 2022
    • Dmitriy Rabotyagov's avatar
      Make publish_collection more universal · 8f27184f
      Dmitriy Rabotyagov authored
      With this change we replace zuul.projects with zuul.project that will
      imply any project which will run the job. Also we read galaxy.yml as
      vars file to predict packed collection naming for futher upload.
      
      Change-Id: I66e27f3026689ad719384203fe66d65f5bca46ce
      Needed-By: https://review.opendev.org/c/openstack/ansible-config_template/+/846391
      8f27184f
    • Jan Horstmann's avatar
      Return details in baremetal_node_info when iterating over all machines · 9b62cd77
      Jan Horstmann authored
      Without any parameters supplied openstack.cloud.baremetal_node_info is
      supposed to gather and return information about all nodes.
      This is done with a call to cloud.list_machines(), which itself calls
      self.baremetal.nodes().
      Unfortunately this will not return detailed information about each
      machine as the details parameter of self.baremetal.nodes() defaults to
      false.
      This commit rewrites the module to use the baremetal service proxy of
      openstacksdk to get machines with details and converts them using the
      `to_dict()` method.
      
      Story: 2010017
      Task: 45207
      Change-Id: Ib06aea5f59f799d6ed81b30264c8a168301c1a9b
      9b62cd77
  19. Jun 16, 2022
  20. Jun 14, 2022
  21. Jun 08, 2022
    • Arx Cruz's avatar
      Update catalog service for the new sdk · 7c7e61d3
      Arx Cruz authored
      This patch do the following:
      
      * Update catalog_service to use new openstacksdk
      * Add catalog_service role to test catalog_service module
      
      Change-Id: I6778f5e91cb0ead63cede28af0111d7ffbbf3ab1
      7c7e61d3
  22. Jun 02, 2022
  23. Jun 01, 2022
  24. May 31, 2022
Loading