Moved from ansible-project:
It looks like we’ve received another contribution for this: https://github.com/ansible/ansible/pull/7593
This has not yet been merged in, but you may want to look at it and see if it meets your needs. If you’ve gotten pretty far in developing your version, you may also want to compare them to see if yours covers any areas that this one does not, and either move that functionality into the one above if/when it is merged or submit a competing version.
As Michael requested, any further discussion on this topic should now be moved to ansible-devel.
Thanks!
Yeah please comment on the above PR if you have any thoughts - if there are no major problems, accepting this and using it as a starting point may be wise.
We have some pending interest from a few other parties so may refrain from merging just for a bit to see if they also have comments, but this should be pretty easy to get in I’d think.
Hi,
I have not added a PR because there are still some open issues (like correct docu, etc) but here are the files I have done so far:
https://github.com/matlockx/ansible/blob/devel/library/cloud/azure
https://github.com/matlockx/ansible/blob/devel/lib/ansible/module_utils/azure.py
https://github.com/matlockx/ansible/blob/devel/plugins/inventory/windows_azure.ini
https://github.com/matlockx/ansible/blob/devel/plugins/inventory/windows_azure.py
Currently I have also a somehow strange error:
Sometimes the scripts complain that they cannot find the module azure (the sdk one which is installed via pip). It’s not really clear to me why that happens. I think it started when I created the inventory plugin. I had a long time this script complaining about the missing module. Out of the sudden it then disappeared but now the module itself complains that.
Anyone an idea?
Thx
Martin
I don’t.
Aside from a very clever gremlin process that is occasionally uninstalling and reinstalling the module 
That is probably not the case!
i think i messed up my system with pip… i cleaned up everything and now it’s working again
by the way, is there any information about merging https://github.com/ansible/ansible/pull/7593 and when it will happen? I got the guys from the azure-sdk to merge a pull request for temporary redirects, so that should also be no issue in the future anymore with the module: https://github.com/Azure/azure-sdk-for-python/pull/157
I’m actually signing up for an Azure account now to test it, so I hope to merge it in today.
After the merge of the last pr I wanted to ask how we continue? I would like to see meta data of hosts in the inventory and the feature to create multiple roles in one deployment. What do you think?
I implemented the roles per deployment already but there is of course some work to do to merge it into the current implementation.
Our shall we wait for the next release and put it then into the branch?
There is also a question open in another thread concerning the data structures. Can I use a shared data model of azure objects which can be used in the module and also in the inventory file and if so where to put it in the directory structure?
Thanks,
Martin
I’m confused what the azure module has to do with roles.
Ah, sorry. VMs are in azure speak 'roles', one VM == one role.
The concept of azure wants you to create multiple VMs in one deployment under one cloud service. All VMs, or roles, can communicate over network with each other without a virtual network and you set up a load balance for them.
So if you want to deploy several instances of the same webapp I think it makes sense to create these 'roles' in one deployment. The azure API has therefore the commands add-role, delete-role, start/stop-role, etc.
Hi,
regarding pull request 7966: https://github.com/ansible/ansible/pull/7966 I just wanted to ask whether there is something to do from my side to help get it merged?
Best
Martin
Should be good… you are in queue, sir!
Note we have a very big queue and are tackling things in priority order, mostly bug reports affecting the most users first, etc.
Sometimes some very very easy things get merged when we see them.
We are going to be ramping up Azure testing very very soon and will have an opportunity to dig in more deeply.