Raised a PR for this issue - https://github.com/ansible/ansible/pull/37170
On Monday, 18 April 2016 17:35:48 UTC+5:30, David Shrewsbury wrote: > > I just realized that someone could probably add the logic to compare the > current flavor > and the parameters and, if different, do the delete/create to simulate the > update. I'd be > happy to merge such a change if you wanted to propose it. I could add it > to my list of > changes to do, but it would be low priority. > > > > On Sunday, April 17, 2016 at 7:28:57 PM UTC-4, David Shrewsbury wrote: >> >> Looks to me like horizon just does a delete/create. So it's the same as >> your workaround. >> >> >> https://github.com/openstack/horizon/blob/b0f3ec3ace531c110f328d208cded302d2617f88/openstack_dashboard/dashboards/admin/flavors/workflows.py#L304-L309 >> >> >> >> On Sunday, April 17, 2016 at 6:13:21 PM UTC-4, Thiago Martins wrote: >>> >>> Mmm... Interesting... >>> >>> How it is done via Horizon? Since I can manually update the flavors via >>> Web GUI... >>> >>> Don't you think that Shade / Ansible can somehow, mimic Horizon "flavor >>> update feature"? >>> >>> On Sunday, April 17, 2016 at 6:27:46 PM UTC-3, David Shrewsbury wrote: >>>> >>>> The Nova API does not have any way to update flavors. Because of this, >>>> the Ansible >>>> module does not support updating. >>>> >>>> >>>> >>>> On Sunday, April 17, 2016 at 11:52:30 AM UTC-4, Thiago Martins wrote: >>>>> >>>>> Guys, >>>>> >>>>> I'm trying to update the default OpenStack flavors, by using >>>>> "os_nova_flavor" but, it does not update the flavors settings if it >>>>> already >>>>> exists... >>>>> >>>>> Is there any way to force it to update the flavors? >>>>> >>>>> A workaround is to first, delete the flavors, and then, create it >>>>> again. But this is bad because every time I run Ansible, it will delete >>>>> and >>>>> recreate the flavors over and over again. >>>>> >>>>> My intention is to update the flavors, only if it is different. For >>>>> example: >>>>> >>>>> --- >>>>> - name: nova updating m1.small flavor >>>>> environment: "{{admin_openrc_env}}" >>>>> os_nova_flavor: >>>>> state=present >>>>> name=m1.small >>>>> ram=2048 >>>>> swap=1024 >>>>> vcpus=2 >>>>> disk=20 >>>>> ephemeral=4 >>>>> --- >>>>> >>>>> I was thinking that, if "m1.small" flavor doesn't have those >>>>> settings, it sill be "changed", otherwise, if it already have those >>>>> settings, it will "not be changed / green Ansible ok". >>>>> >>>>> Is there any way to make it behaves like this? >>>>> >>>>> Thanks! >>>>> Thiago >>>>> >>>> -- 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 ansible-project+unsubscr...@googlegroups.com. To post to this group, send email to ansible-project@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-project/2f058ab1-eb93-407f-9e64-329e291bc848%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
