Hello,

    I have an ansible playbook that is responsible for creating all of the 
projects we have defined in our projects.yml file. 

This playbook currently:
- creates all of our projects
- adds our admin_group to the projects

I am trying to use os_network to create a default private network and 
subnet under each project, however the network is always created under my 
admin project space.

I originally had this code:
--snip--
- name: Creating Project Networks
  os_network:
    name: "{{ item.1.network.name }}"
    state: "{{ item.0.state }}"
    shared: False
    external: False
  with_subelements:
  - "{{ projects }}"
  - networks
--snip--

My credentials are currently set to the default admin account and are 
loaded via the OS_ environment variables by sourcing an openrc file. When I 
execute the above code all the networks and subnets are created under the 
admin tenant.

I tried using the following with a hardcoded project_name:
--snip--
- name: Creating Project Networks
  os_network:
    auth:
      username: admin
      password: my_special_password
      auth_url: http://<my_ip>:5000/v3
      project_name: testproject1
    auth_type: password
    name: "{{ item.1.network.name }}"
    state: "{{ item.0.state }}"
    shared: False
    external: False
  with_subelements:
  - "{{ projects }}"
  - networks
--snip--

However the networks are still created under the admin tenant, is it safe 
to assume that previous os_* modules have cached an auth token? Is there a 
better way to interact with multiple projects when using the os_* modules?


Thanks
Michael

-- 
You received this message because you are subscribed to the Google Groups 
"Ansible Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-project/115acfb4-d143-465a-a640-6b4b56720867%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to