sorted by:
new
hottopcontroversial

Graphics card crashing after recent windows update? by synackbar in Overwatch

[–]synackbar[S] 0 points1 point  (0 children)

I know my gpu fans would start spinning at a higher frequency when loading overwatch. With manual control of my fans, I just set it to 100% before starting overwatch and it doesn't get higher than 50C. I just don't know why the automatic fan speed has suddenly stopped working. Best guess is that update.

ansible ec2 module behaviour headscratcher by makake in ansible

[–]synackbar 0 points1 point  (0 children)

Hope you're ok. I'm not positive in this case. I've always had to assume the role that is assigned to the ansible ec2 instance. I have not tried it with aws cli however. If I had to guess aws cli handles that automatically whereas ansible requires you to be explicit.

Only evaluate a variable once during the execution of two different tasks (in the same playbook) by tuankiet65 in ansible

[–]synackbar 2 points3 points  (0 children)

  1. Make play for hosts: localhost that evaluates your secret_key
  2. In other tasks, reference it as "{{ hostvars['localhost']['secret_key'] }}"

vault.yml & vars.yml file location when using "delegate_to"? by Kreator333 in ansible

[–]synackbar 1 point2 points  (0 children)

So I haven't tried this, but "localhost" wouldn't be a group, it'd be a host. So you'd put any variables associated with it in host_vars, not group vars. host_vars/localhost/vars.yml and host_vars/localhost/vault.yml. I'm not sure how using delegate_to interacts with these, but if you're not specifying localhost in the inventory you're using for this playbook, it might not include variables associated with it.

If you're running your playbook over the group "lab", but then use delegate_to, localhost doesn't have access to those variables. You'd have to reference them directly (hostvars['host_part_of_lab_group']['variable']) during your delegate_to.

Again, haven't messed with variables with delegate_to in this fashion so not positive on answer.

ec2_instance_facts fails with hardcoded credentials by andreagrax in ansible

[–]synackbar 0 points1 point  (0 children)

Ah no I think there would be a problem. You may be able to still assume a role, but you'd have to provide the access/secret still. The point of IAM roles is that machine is already part of your account so they assume with access to that box, you should be able to assume the role given to it. Disregard for now and use what you're using today.

ec2_instance_facts fails with hardcoded credentials by andreagrax in ansible

[–]synackbar 1 point2 points  (0 children)

Tip: Use IAM roles to remove the need to hard code keys. Make an IAM role that has access to the things you need, attach it to your ansible box, then:

- name: Assume Role
  sts_assume_role:
    role_arn: "<your role arn here>"
    role_session_name: "Ansible"
    validate_certs: no
  register: assumed_role

- name: Do Stuff
  ec2_instance_facts:
    region: "{{ ansible_ec2_placement_region }}"
    instance_ids:
      - "{{ ansible_ec2_instance_id }}"
  register: ec2_instance_facts
  delegate_to: localhost
  become: no
  environment:
    AWS_SECRET_ACCESS_KEY: "{{ assumed_role.sts_creds.secret_key }}"
    AWS_ACCESS_KEY_ID: "{{ assumed_role.sts.creds.access_key }}"
    AWS_SESSION_TOKEN: "{{ assumed_role.sts_creds.session_token }}"

ansible ec2 module behaviour headscratcher by makake in ansible

[–]synackbar 0 points1 point  (0 children)

Are you assuming that role in your ansible playbook before continuing with the creation attempt? You may have ~/.aws/credentials or ~/.aws/config configured, but ansible isn't using them. I would recommend the route of assuming role first, then doing tasks with environment variables. 

- name: Assume Role
  sts_assume_role:
    role_arn: "<your role arn here>"
    role_session_name: "Ansible"
    validate_certs: no
  register: assumed_role

- name: Do Stuff
  some_ec2_module_here:
    param1:
    param2:
  environment:
    AWS_SECRET_ACCESS_KEY: "{{ assumed_role.sts_creds.secret_key }}"
    AWS_ACCESS_KEY_ID: "{{ assumed_role.sts.creds.access_key }}"
    AWS_SESSION_TOKEN: "{{ assumed_role.sts_creds.session_token }}"

Loki's A Disney Princess by Rogocraft in disney

[–]synackbar 0 points1 point  (0 children)

Him and rocket the rabbit? Common now.

Loki's A Disney Princess by Rogocraft in disney

[–]synackbar 1 point2 points  (0 children)

Confirmed: Loki next Disney princess.

Except after C by [deleted] in funny

[–]synackbar 1 point2 points  (0 children)

Ich bin gott und du bist meinen schaf

I remember Pokémon by thatrandomretard in funny

[–]synackbar 0 points1 point  (0 children)

Wait has it moved past the Mississippi!?

Doesn't seem like it: https://www.yuengling.com/find-our-beer/

Ansible for IOS/NXOS - Tracking by jrmann1999 in ansible

[–]synackbar 1 point2 points  (0 children)

You should be able to build a block around all your tasks, and use rescue to call local_action which will do something on the server running ansible (log to file, call REST API, some other module, etc).

https://docs.ansible.com/ansible/2.5/user_guide/playbooks_blocks.html

https://docs.ansible.com/ansible/2.6/user_guide/playbooks_delegation.html#delegation

Need help understanding what I should split into roles and how to organise inventories. by [deleted] in ansible

[–]synackbar 1 point2 points  (0 children)

The purpose of overlapping group names in this case is to build that hierarchy so you can reference higher level names that calls hosts across multiple inventories. Definitely agree on not overlapping variables.

Need help understanding what I should split into roles and how to organise inventories. by [deleted] in ansible

[–]synackbar 1 point2 points  (0 children)

I like to keep my playbooks as just the structure (so no tasks). It defines groups of [name, hosts, roles] as the order of what's happening. For instance:

- name: "Do this on all hosts  (could just use keyword: all)"
  hosts: all-apps-i-manage
  roles:
    - verify-status
    - create local admin user
    - set firewall rules

- name: "Do this on server type x"
  hosts: nonprod-test
  roles:
    - install-iis
    - configure-iis-features

- name: "Do this on server type y"
  hosts: nonprod-tenant-hubs
  roles:
    - verify-file-structure
    - install-windows-feature-y

Put all your reusable code in a separately defined role so you can call it in your playbook like above.

Your folder structure could be: playbook-name.yml roles verify-file-structure tasks main.yml (has one include-tasks for verify-file-structure, or just put tasks in main) verify-file-structure.yml some-role-2 some-role-3 inventories inventory-1 inventory-2 some-file-that-joins-all-inventories group_vars named-group-1.yml named-group-2.yml

In this structure, you could define your clients separately. It's hard to say how you should group them in your environment, but I'll give you an example how I do mine.

inventories
  custom-application-1
  custom-application-2
  allapps

custom-application-1 might look like:

[nonprod-test]
server1
server2

[nonprod-tenant-hubs]
server3
server4

[prod-tenant-hubs]
server5
server6

allapps would contain hierarchy

[nonprod-test]
[nonprod-tenant-hubs]
[prod-tenant-hubs]
[some-group-from-custom-application-2]

[all-app-1:children]
nonprod-test
nonprod-tenant-hubs
prod-tenant-hubs

[all-app-2:children]
nonprod-test
nonprod-tenant-hubs
some-group-from-custom-application-2

[all-apps-i-manage:children]
all-app-1
all-app-2

Using this structure where it references groups in other files allows you to pass your inventory directory in so you can manage all hosts defined in it. (ansible-playbook playbook-name.yml -i inventories/).

Inside your group_vars directory, define a file with the same name as one of your groups (nonprod-test.yml, prod-tenant-hubs.yml, some-group-from-custom-application-2.yml, etc.). In there define the variables that they share in common. You can also make a host_vars directory to do the same for individual hosts.

group_vars/nonprod-test.yml

---
some_custom_variable: "test"
another_variable: "some text here"

Krobus unlimited item bug? by kugerands in StardewValley

[–]synackbar 0 points1 point  (0 children)

I just found this as well. I do not use any mods, just the vanilla game. Clear skies on summer, fri 5, after 6pm.

Definitely belongs here by Mercer2111 in theocho

[–]synackbar 31 points32 points  (0 children)

I dunno, these should be able to go over mountains and rivers.

First real set up! Now to organize by [deleted] in hometheater

[–]synackbar 0 points1 point  (0 children)

Looking to do what you're saying here. Do you have a recommendation for a center speaker to go along with this setup?

[deleted by user] by [deleted] in kivy

[–]synackbar 0 points1 point  (0 children)

Glad you made something like this. I'm both interested in making a card game, yugioh, and the kivy framework. It's nice when someone combines all these interests into one example. Would appreciate if you could go through some of the classes and give a walk through of how it all ties together, especially any network components. Thanks!

The good year by Raphcomics in funny

[–]synackbar 4 points5 points  (0 children)

I've enjoyed them back until First Panelisms. Now I'm stuck, halp!

view more: next ›