I've never used Azure but this looks like what you want:
https://azure.microsoft.com/en-us/blog/custom-data-and-cloud-init-on-windows-azure/
On 18 April 2017 at 03:42, Madhava Rao wrote:
> Could you please point to some links on how it can done through Azure?
>
> Thanks,
>
> On Thursday, April
Looks like you have a corrupted file or are running on a different CPU type
(eg 386 vs Arm).
On Mon, Apr 17, 2017, 17:40 Anfield wrote:
> Getting the following errors - can anyone help?
>
> Traceback (most recent call last):
> File "/usr/bin/ansible-playbook", line 41, in
> from multiproc
Getting the following errors - can anyone help?
Traceback (most recent call last):
File "/usr/bin/ansible-playbook", line 41, in
from multiprocessing import Lock
File "/usr/lib64/python2.7/multiprocessing/__init__.py", line 65, in
from multiprocessing.util import SUBDEBUG, SUBWARNIN
I'm currently using the ec2_metric_alarm module to create a CloudWatch
alarm. Due to AWS API throttling, the task generally fails during its first
try and must be retried with the "retries" parameter. My code looks
something like this:
- name: create alarm
ec2_metric_alarm:
state: present
This has been reported at https://github.com/ansible/ansible/issues/22572
On Mon, Apr 17, 2017 at 3:48 PM, Don Jackson wrote:
>
> AFAICT, after Ansible 2.3.0.0 was released, when I run 'ansible-galaxy
> install -r roles.yaml' if any filename within the role begins with the name
> of the role, th
AFAICT, after Ansible 2.3.0.0 was released, when I run 'ansible-galaxy
install -r roles.yaml' if any filename within the role begins with the name
of the role, then that filename will be changed to remove the name of the
role.
For example, in role foo, of there is a file templates/foo.conf.j2,
Ansible 2.3 is in EPEL testing.
However, to use `wait_for` you should also use `delegate_to` and delegate
the execution of the task to the bastion, so that `wait_for` is running
from the bastion.
On Mon, Apr 17, 2017 at 2:50 PM, Michael Artz wrote:
> I'm attempting to reboot a Linux host and wa
I'm attempting to reboot a Linux host and wait for it to become available
again. I've followed the ideas in both the docs
(https://docs.ansible.com/ansible/wait_for_module.html) and
https://github.com/ansible/ansible/issues/14413 and it "works", however my
situation is slightly different, as I
I am attempting to create a new server and upload a json file as userdata.
ansible-playbook indicates success but the instance doesn't seem to see the
userdata. However, it does work when I do this via nova boot or a heat
stack.
ansible 2.2.1.0
OpenStack Mitaka (AIO)
The task looks like this
When we create an EC2 instance, we then run playbooks on the EC2 instance
to harden it and configure it the way we need to.
Right now, I have a Python script with Boto3 retrieving tag information. I
then pass the variables into an Ad-Hoc play, but I'm looking for an
automated solution to this
Hey,
You can use ec2_tag module, Go thru the link below for detailed explanation
-
http://docs.ansible.com/ansible/ec2_tag_module.html
On Thursday, March 23, 2017 at 2:23:03 AM UTC+5:30, balubhai555 wrote:
>
> *Hello Team, *
>
> *I got a requirement to create 'n' number of AWS ec2 instances an
Hello Everyone,
i'm trying to setup one of my mac machine using ansible playbook and i want
to install cordova as part of dependencies. i have wrote a playbook and
even tried to call some roles which are available in ansible-galaxy. but
for all of them i'm getting the below error. please let me
Try after deleteing */.ssh/Known_Hosts file.*
On Thursday, April 13, 2017 at 10:15:35 PM UTC+5:30, Li Zheng wrote:
>
> I am following ec2 module for Ansible example on link
> http://docs.ansible.com/ansible/ec2_module.html
>
>
> instance is created correctly. However, during *Configure instance
Hi Daniel,
Would you please share how did you upgrade? I am also getting similar error.
"TASK [GET-MODEL]
***
fatal: [192.168.56.103]: FAILED! => {"changed": false, "failed": true,
"module_stderr":
"/usr/lib/python2.7/dist-packages/
nvm, found a bug report on this issue here:
https://github.com/ansible/ansible/issues/20980
I'll update that ticket with my feedback.
On Monday, April 17, 2017 at 12:54:22 PM UTC-4, Jason Gilfoil wrote:
>
> Did you find a solution to this? I'm having the same issue on the same
> version, ansi
Did you find a solution to this? I'm having the same issue on the same
version, ansible 2.2.1.0.
https://pastebin.com/a2gPLwWm
On Monday, February 6, 2017 at 9:41:41 AM UTC-5, Peter Heitman wrote:
>
> I am running ansible on CentOS 6.8. This morning I ran yum update and got
> updated to a new
Hi
from ansible 1.9 till 2.2.2.0 on centos 7 privilege escalation works
really fine. I could access a server with a non privileged user and a
ssh key authentication and use as last step the privilege escalation
with su.
But with 2.3 I found this doesn't work any more.
The ssh connection to the se
Cool, will do!
On Saturday, April 8, 2017 at 12:06:16 AM UTC+2, Matt Davis wrote:
>
> I'm definitely open to shipping the dynamic DSC executor module as a big
> first step (and maybe the only one?), so if you want to polish it up and PR
> it for 2.4, please do! Agreed WRT the name change to remo
18 matches
Mail list logo
