Thanks Michael,

I actually found a bug  (region wasn't being supplied to nova client 
"Client()") in the code and submitted a pull request to the nova_compute 
driver. My very simplistic example that now works with my fix, using HP 
Cloud, is the following:

# Creates a new VM and attaches to a network and passes metadata to the instance
- name: launch a nova instance
  hosts: localhost
  tasks:
  - name: launch an instance
    nova_compute:
      state: present
      login_username: myuser
      login_password: xxxx
      login_tenant_name: myuser-project1
      name: vm1
      auth_url: https://region-b.geo-1.identity.hpcloudsvc.com:35357/v2.0/
      region_name: region-b.geo-1
      image_id: 9302692b-b787-4b52-a3a6-daebb79cb498
      key_name: test
      wait_for: 200
      flavor_id: 101
      security_groups: default
      


On Sunday, March 30, 2014 12:33:52 PM UTC-4, Michael DeHaan wrote:
>
> Can we see this in the full playbook context?
>
>
>
>
> On Sat, Mar 29, 2014 at 12:57 PM, Patrick Galbraith 
> <[email protected]<javascript:>
> > wrote:
>
>> Hi all!
>>
>> I am trying to use the nova_compute plugin and keep on getting:
>>
>> ERROR: nova_compute is not a legal parameter in an Ansible Playbook
>>
>> ansible-doc, if I run it, shows that the module is there as well as 
>> looking in /usr/share/ansible/cloud/ (nova_compute is there). This is 
>> ansible 1.5.3.
>>
>> I'm using the example found in the actual documentation:
>>
>> - nova_compute:
>>        state: present
>>        login_username: xxx
>>        login_password: xxx
>>        login_tenant_name: xxx-project1
>>        name: vm1
>>        auth_url: 
>> https://region-b.geo-1.identity.hpcloudsvc.com:35357/v2.0/tokens
>>        region_name: region-b.geo-1
>>        image_id: 9302692b-b787-4b52-a3a6-daebb79cb498
>>        key_name: test
>>        wait_for: 200
>>        flavor_id: 101
>>        security_groups: default
>>        nics:
>>          - net-id: 7da74520-9d5e-427b-a508-213c84e69616
>>
>> So, what else does one need here? I simply want to get familiar with 
>> using this to launch instances and then manage them. Is there any 
>> simplified document that demonstrates this?
>>
>> Regards and thank you!
>>
>> Patrick
>>
>> -- 
>> 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] <javascript:>.
>> To post to this group, send email to [email protected]<javascript:>
>> .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/ansible-project/7f313a6e-4382-4c9d-8724-7d5fc0df4e86%40googlegroups.com<https://groups.google.com/d/msgid/ansible-project/7f313a6e-4382-4c9d-8724-7d5fc0df4e86%40googlegroups.com?utm_medium=email&utm_source=footer>
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>

-- 
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/70154a01-cd9f-4591-bd01-92ff1ff599b0%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to