#9695 Ansible Cleanup: Move systems to linux-system-roles networking
Opened 2 months ago by smooge. Modified 12 days ago

Describe what you would like us to do:

Many older systems are configured using various templates or hand configured when brought up. The 'new' ansible linux-system-roles for networking allow for us to get rid of these templates and use a standard method per OS to get things configured. Task would be to collect the mac addresses for each system and then make a pr request for the system host_vars data

Old method:

---
datacenter: iad2

br0_ip: 10.3.170.11
br0_nm: 255.255.255.0
br0_gw: 10.3.170.254
br0_dev: eth1

dns: 10.3.163.33

New method:

---
# This virthost only has stg instances, so it doesn't freeze
freezes: false
nested: true
dns: 10.3.163.33

has_ipv4: yes
br0_ipv4: 10.3.166.28
br0_ipv4_nm: 24
br0_ipv4_gw: 10.3.166.254

mgmt_mac: 2c:ea:7f:f3:6c:be
mgmt_ipv4: 10.3.160.46
mac1: E4:43:4B:F7:B7:B8
mac2: E4:43:4B:F7:B7:BA
mac3: E4:43:4B:F7:B7:D8
mac4: E4:43:4B:F7:B7:D9

br0_port0_mac: "{{ mac1 }}"

network_connections:
  - name: br0
    state: up
    type: bridge
    autoconnect: yes
    ip:
      address: 
      - "{{ br0_ipv4 }}/{{ br0_ipv4_nm }}"
      gateway4: "{{ br0_ipv4_gw }}"
      dns: 
      - "{{ dns }}"
      dns_search: 
      - stg.iad2.fedoraproject.org
      - iad2.fedoraproject.org
      - fedoraproject.org
      dhcp4: no
      auto6: no
  - name: br0-port0
    state: up
    type: ethernet
    master: br0
    mac: "{{ br0_port0_mac }}"

Data that isn't known is ok to ask for more help on.


When do you need this to be done by? (YYYY/MM/DD)



Metadata Update from @mohanboddu:
- Issue priority set to: Waiting on Assignee (was: Needs Review)
- Issue tagged with: easyfix, low-gain, low-trouble, ops

2 months ago

I can take a look at this, but need some info to get started:
- Do we have a map of these "Many older systems "
- How to access these systems.
- What is the location for the pr request for the system host_vars data

The ansible repository is at https://pagure.io/fedora-infra/ansible and I will create a list of systems and information later today.

Looks like uploading tar balls does not work. I am putting the tar ball at https://smooge.fedorapeople.org/fedora-infra/ansible-ip-info.tgz

If @copperi doesnt have the time for this I can take it and start working on it.

@bodanel I have started, but sure you can work on this as well, there are about 500 machines and I have access to 50.

So far I have done:
pr_submitted proxy05.fedoraproject.org ... ... proxy05.fedoraproject.org moved to linux-system-roles networking
no response ... proxy06.fedoraproject.org
no response ... proxy09.fedoraproject.org
pr_submitted proxy10.iad2.fedoraproject.org ... proxy10.iad2.fedoraproject.org moved to linux-system-roles networking
pr_submitted proxy101.iad2.fedoraproject.org ... proxy101.iad2.fedoraproject.org moved to linux-system-roles networking
pr_submitted proxy11.fedoraproject.org ... proxy11.fedoraproject.org moved to linux-system-roles networking
pr_submitted proxy110.iad2.fedoraproject.org ... proxy110.iad2.fedoraproject.org moved to linux-system-roles networking
pr_submitted proxy12.fedoraproject.org ... proxy12.fedoraproject.org moved to linux-system-roles networking
no response ... proxy13.fedoraproject.org
pr_submitted proxy14.fedoraproject.org ... proxy14.fedoraproject.org moved to linux-system-roles networking
n/a proxy30.fedoraproject.org
n/a proxy31.fedoraproject.org
n/a proxy32.fedoraproject.org
n/a proxy33.fedoraproject.org
n/a proxy34.fedoraproject.org
n/a proxy35.fedoraproject.org
n/a proxy36.fedoraproject.org
n/a proxy37.fedoraproject.org
n/a proxy38.fedoraproject.org
n/a proxy39.fedoraproject.org
n/a proxy40.fedoraproject.org

Yes please do this in multiple small PR requests. We will want to be able to merge them, test them in blocks which small pr's will work better for.

@smooge
When you can please have a look at https://pagure.io/fedora-infra/ansible/pull-request/481 and let me know if it is ok. If yes, I will start modifying blocks of servers.

buildhw-a64-0[1-6].iad2.fedoraproject.org
buildhw-a64-11.iad2.fedoraproject.org
buildhw-a64-19.iad2.fedoraproject.org
buildhw-a64-20.iad2.fedoraproject.org
buildhw-x86-02.iad2.fedoraproject.org
buildhw-x86-03.iad2.fedoraproject.org
buildhw-x86-04.iad2.fedoraproject.org
buildhw-x86-0[6-16].iad2.fedoraproject.org
done. I'll keep updating the tickets as I push my modifications

The following servers are done also

buildvm-a32-0[1-27].iad2.fedoraproject.org
buildvm-a32-0[1-2].stg.iad2.fedoraproject.org
buildvm-a32-3[1-3].iad2.fedoraproject.org

@smooge
Can you please assing the ticket to me at least so I can find it more easy?

Below servers are commited
buildvm-a64-01.iad2.fedoraproject.org
buildvm-a64-01.stg.iad2.fedoraproject.org
buildvm-a64-02.iad2.fedoraproject.org
buildvm-a64-02.stg.iad2.fedoraproject.org

The following servers are done
buildvm-a64-[03-23].iad2.fedoraproject.org

Assigning to @bodanel :) Thanks for working on it.

Metadata Update from @kevin:
- Issue assigned to bodanel

23 days ago

buildvm-ppc64le-[11-40].iad2.fedoraproject.org done.

Metadata Update from @bodanel:
- Assignee reset

12 days ago

Metadata Update from @smooge:
- Issue assigned to bodanel

12 days ago

Login to comment on this ticket.

Metadata
Boards 1
ops Status: Backlog