re sending to it?
>
>
>
>
> On Thu, Jul 17, 2014 at 12:56 AM, TextEditor > wrote:
>
>> In the Openstack Nova_compute module, I cannot give the availability zone
>> for an instance I want to create. Only the region, but my IAAS provider
>> only has Availability Z
In the Openstack Nova_compute module, I cannot give the availability zone
for an instance I want to create. Only the region, but my IAAS provider
only has Availability Zones.
Does anyone know if, and how that would be possible?
--
You received this message because you are subscribed to the Go
Op woensdag 8 januari 2014 14:48:56 UTC+1 schreef Michael DeHaan:
>
> Excellent,
>
> Both vcenter and vsphere together would be ideal.
>
It also works on standalone ESXi hosts as far as I can see. (Just tried
it).
>
> We're seeing increased interest in folks of having VMware inventory
> la
I've made a simple python script which uses VMWare vCenter to create a
Dynamic Inventory. It is very simple, does not support grouping by
datacenter or resource groups (yet, pull requests accepted).
https://raymii.org/s/software/Ansible__Dynamic_Inventory_From_VMware_vCenter.html
I'd like some
OK. Yet again, thanks for the help.
Op vrijdag 27 december 2013 19:52:03 UTC+1 schreef Michael DeHaan:
>
> Doesn't matter as it is for playbooks.
>
> -- Michael
>
> On Dec 27, 2013, at 1:35 PM, TextEditor >
> wrote:
>
> Seems logical. Can you maybe explain
OK. Yet again, thanks for the help.
Op vrijdag 27 december 2013 19:52:03 UTC+1 schreef Michael DeHaan:
>
> Doesn't matter as it is for playbooks.
>
> -- Michael
>
> On Dec 27, 2013, at 1:35 PM, TextEditor >
> wrote:
>
> Seems logical. Can you maybe explain
I realized in
> order to get it to check all the roles too, you need to use the
> --list-tasks argument too:
>
> ansible-playbook --syntax-check --list-tasks site.yml
>
> --
> Matt Martz
> ma...@sivel.net
>
> On December 27, 2013 at 8:05:50 AM, TextEditor
> (rel
efinition
> not playbooks.
>
> -- Michael
>
> On Dec 27, 2013, at 2:16 AM, TextEditor >
> wrote:
>
> It is run on the YAML files because when run on just the playbook which
> includes the roles it does not check the includes roles.
>
> And, as also can be seen
Even when a broken playbook or a broken yaml file is includes as role it
validates as correct with 1.4.
Op vrijdag 27 december 2013 08:16:26 UTC+1 schreef TextEditor:
>
> It is run on the YAML files because when run on just the playbook which
> includes the roles it does not check the
ed, it could not be reproduced.
>
> -- Michael
>
> On Dec 26, 2013, at 6:50 PM, TextEditor >
> wrote:
>
> Since my bug report is ignored and closed I'm asking for support here.
> Since the upgrade to Ansible 1.4 the --syntax-check feature broke when used
>
--
> Matt Martz
> ma...@sivel.net
>
> On December 26, 2013 at 5:50:45 PM, TextEditor
> (rel...@gmail.com)
> wrote:
>
> Since my bug report is ignored and closed I'm asking for support here.
> Since the upgrade to Ansible 1.4 the --syntax-check feature b
Since my bug report is ignored and closed I'm asking for support here.
Since the upgrade to Ansible 1.4 the --syntax-check feature broke when used
with role files.
This is the ticket: https://github.com/ansible/ansible/issues/5412
--syntax-check fails on 1.4.with ERROR: MODULE is not a legal p
/etc/fstab)."
>
> So no manual editing of fstab.
>
>
>
> On Mon, Dec 9, 2013 at 9:36 AM, Michael DeHaan
>
> > wrote:
>
>> Yes, you can see the remount logic here:
>>
>> https://github.com/ansible/ansible/blob/devel/library/system/mount#L2
How would I remount the root partition with the "noatime" option and
afterwards make it permanent, without knowing the layout of the filesystems
on the machine (so no template for /etc/fstab)?
If the "mounted" state is given to the mount module, will it remount the
partition if it is already mo
14 matches
Mail list logo
