Re: Moving staging to new ip space

2017-05-19 Thread Kevin Fenzi
On 05/19/2017 03:22 AM, Faber wrote:
> i think there is an issue with my patch; i'm following the original idea
> to have stage ip similar to prod ip
> 
> for example: noc01.stg.phx2.fedoraproject.org -> 10.5.126.2
> noc01-a.stg.phx2.fedoraproject.org -> 10.5.128.41 [ matches noc01 on
> 10.5.126.41]

Note that we want them to have the same exact names as they do now. This
is because we have our staging env set in /etc/resolv.conf to search for
hosts in stg.phx2.fedoraproject.org first... so in staging a 'noc01'
would get the ip for 'noc01.stg.phx2.fedoraproject.org' but in
production would get 'noc01.phx2.fedoraproject.org' We do this so we can
keep a lot of the config the same and it just works.
> 
> btw with dhcp IPs going from 10.5.128.10 to 10.5.128.20 there will be
> duplicates
> 
> @smooge is it ok to use your stg.phx2.fedoraproject.org file but with
> the 128 ip space instead of 126?
> 
> so we have ips moved from 10.5.126 -> 10.5.128 numbers, but not 1:1

While it might be handy to make them 1:1 on IP's, I don't think it's a
requirement... so sure.

> it seems all IPs there are unique, except for fas-all  and  fas01  both
> with 10.5.126.86

Yep. That fas-all in stg is just a pointer to the one fas server (since
we only have one there). In production it points to all 3 of the servers
we have in place.

kevin




signature.asc
Description: OpenPGP digital signature
___
infrastructure mailing list -- infrastructure@lists.fedoraproject.org
To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org


Re: Moving staging to new ip space

2017-05-19 Thread Stephen John Smoogen
Hi Faber.

Thanks for keeping this up. It should be ok to use the file even if we
do not implement this until after the freeze is over.

On 19 May 2017 at 05:22, Faber  wrote:
> i think there is an issue with my patch; i'm following the original idea to
> have stage ip similar to prod ip
>
> for example: noc01.stg.phx2.fedoraproject.org -> 10.5.126.2
> noc01-a.stg.phx2.fedoraproject.org -> 10.5.128.41 [ matches noc01 on
> 10.5.126.41]
>
> btw with dhcp IPs going from 10.5.128.10 to 10.5.128.20 there will be
> duplicates
>
> @smooge is it ok to use your stg.phx2.fedoraproject.org file but with the
> 128 ip space instead of 126?
>
> so we have ips moved from 10.5.126 -> 10.5.128 numbers, but not 1:1
>
> it seems all IPs there are unique, except for fas-all  and  fas01  both with
> 10.5.126.86
>
>
>
>
>
>
> ___
> infrastructure mailing list -- infrastructure@lists.fedoraproject.org
> To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org
>



-- 
Stephen J Smoogen.
___
infrastructure mailing list -- infrastructure@lists.fedoraproject.org
To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org


Re: Moving staging to new ip space

2017-05-19 Thread Faber
i think there is an issue with my patch; i'm following the original idea
to have stage ip similar to prod ip

for example: noc01.stg.phx2.fedoraproject.org -> 10.5.126.2
noc01-a.stg.phx2.fedoraproject.org -> 10.5.128.41 [ matches noc01 on
10.5.126.41]

btw with dhcp IPs going from 10.5.128.10 to 10.5.128.20 there will be
duplicates

@smooge is it ok to use your stg.phx2.fedoraproject.org file but with
the 128 ip space instead of 126?

so we have ips moved from 10.5.126 -> 10.5.128 numbers, but not 1:1

it seems all IPs there are unique, except for fas-all  and  fas01  both
with 10.5.126.86



 



signature.asc
Description: OpenPGP digital signature
___
infrastructure mailing list -- infrastructure@lists.fedoraproject.org
To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org


Re: Moving staging to new ip space

2017-05-17 Thread Faber
I'm attaching a patch for stg.phx2.fedoraproject.org file

if looks fine for you i'll start to edit the 128.5.10.in-addr.arpa file



From edbb3f2ae499fa5961e1d157f2d3c1adc956b0db Mon Sep 17 00:00:00 2001
From: giardia 
Date: Wed, 16 May 2017 19:51:07 +0200
Subject: [PATCH] New IP space for staging

---
 master/stg.phx2.fedoraproject.org | 262 --
 1 file changed, 135 insertions(+), 127 deletions(-)

diff --git a/master/stg.phx2.fedoraproject.org b/master/stg.phx2.fedoraproject.org
index 736b5a6..e950b4d 100644
--- a/master/stg.phx2.fedoraproject.org
+++ b/master/stg.phx2.fedoraproject.org
@@ -4,7 +4,7 @@ $TTL 3600
 ; Make SURE to update the serial # when changes are made. Format is
 ; MMDDNN (NN is just a counter to handle multiple changes in one
 ; day). 
-2017051008 ; Serial
+2017051600 ; Serial
 3600   ; Refresh
 600; Retry
 100; Expire
@@ -12,140 +12,140 @@ $TTL 3600
 @   IN  NS  ns03.phx2.fedoraproject.org.
 @   IN  NS  ns04.phx2.fedoraproject.org.
 
-dhcp00		IN  A	10.5.128.10
-dhcp01		IN  A	10.5.128.11
-dhcp02		IN  A	10.5.128.12
-dhcp03		IN  A	10.5.128.13
-dhcp04		IN  A	10.5.128.14
-dhcp05		IN  A	10.5.128.15
-dhcp06		IN  A	10.5.128.16
-dhcp07		IN  A	10.5.128.17
-dhcp08		IN  A	10.5.128.18
-dhcp09		IN  A	10.5.128.19
-dhcp10		IN  A	10.5.128.20
+dhcp00  IN  A   10.5.128.10
+dhcp01  IN  A   10.5.128.11
+dhcp02  IN  A   10.5.128.12
+dhcp03  IN  A   10.5.128.13
+dhcp04  IN  A   10.5.128.14
+dhcp05  IN  A   10.5.128.15
+dhcp06  IN  A   10.5.128.16
+dhcp07  IN  A   10.5.128.17
+dhcp08  IN  A   10.5.128.18
+dhcp09  IN  A   10.5.128.19
+dhcp10  IN  A   10.5.128.20
 
-ask01   IN  A   10.5.126.80
-autocloud-backend01 IN  A   10.5.126.125
-autocloud-backend02 IN  A   10.5.126.126
-autocloud-web01 IN  A   10.5.126.3
-autocloud-web02 IN  A   10.5.126.89
-autosign01  IN  A	10.5.126.139
-badges-backend01IN  A   10.5.126.68
-badges-web01IN  A   10.5.126.69
-basset01IN	A	10.5.126.138
-blockerbugs01   IN  A   10.5.126.65
-bodhi-backend01 IN  A   10.5.126.90
+ask01   IN  A   10.5.128.79
+autocloud-backend01 IN  A   10.5.128.125
+autocloud-backend02 IN  A   10.5.128.126
+autocloud-web01 IN  A   10.5.128.117
+autocloud-web02 IN  A   10.5.128.118
+autosign01	IN	A	10.5.128.22
+badges-backend01IN  A   10.5.128.100
+badges-web01IN  A   10.5.128.101
+basset01	IN	A	10.5.128.194
+blockerbugs01   IN  A   10.5.128.53
+bodhi-backend01 IN  A   10.5.128.90
 bodhi-backend01-nfs IN  A   10.5.127.65
-bodhi01 IN  A   10.5.126.166
-bodhi02 IN  A   10.5.126.169
-bugyou01IN  A   10.5.126.130
-bugzilla2fedmsg01   IN  A   10.5.126.84
-buildvm-01  IN  A   10.5.126.14
-buildvm-02  IN  A   10.5.126.223
-buildvm-03  IN  A   10.5.126.224
-buildvm-04  IN  A   10.5.126.225
-buildvm-05  IN  A   10.5.126.226
-busgateway01IN  A   10.5.126.62
-composerIN  A   10.5.126.6
-darkserver-backend01 IN A   10.5.126.124
-darkserver-web01IN  A   10.5.126.92
-darkserver-web02IN  A   10.5.126.120
-datagrepper01   IN  A   10.5.126.67
-datagrepper02   IN  A   10.5.126.74
-db03IN  A   10.5.126.113
-db-fas01	IN	A   10.5.126.78
-db-koji IN  A   10.5.126.190
-db-koji01   IN  A   10.5.126.188
-db-koji02   IN  A   10.5.126.189
-db01IN  A   10.5.126.204
-db02IN  A   10.5.126.85
-docker-candidate-registry01 IN	A   10.5.126.218
-docker-registry01   IN  A   10.5.126.217
-docker-registry02   IN  A   10.5.126.237
-elections01	IN  A	10.5.126.105
-elections02	IN	A	10.5.126.106
-faf01   IN  A   10.5.126.199
-fas-all IN  A   10.5.126.86
-fas01   IN  A   10.5.126.86
-fas3-01 IN  A   10.5.126.28
-fedimg01IN  A   10.5.126.9
-fedocal01   IN  A   10.5.126.66
-gallery01   IN  A   10.5.126.70
-github2fedmsg01 IN  A   10.5.

Re: Moving staging to new ip space

2017-05-16 Thread Fabrizio Pasqualin
Hi, sorry, been busy, so i'm taking a look just now to the new files in 
dns/master/

in stg.phx2.fedoraproject.org file, i can see a list of the staging hosts with 
IP address still in the 126 space, should i assign the new 128 ip space?

after that i can populate the 128.5.10.in-addr.arpa file too

i can provide a patch since i cannot push them as an apprentice 
___
infrastructure mailing list -- infrastructure@lists.fedoraproject.org
To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org


Re: Moving staging to new ip space

2017-05-10 Thread Stephen John Smoogen
On 9 May 2017 at 16:39, Faber  wrote:
> Hi, as an apprentice i started to look at this easy fix issue
> https://pagure.io/fedora-infrastructure/issue/5931
>
> It needs different steps and the admins to work through ansible...maybe it's
> a good candidate for something to work on the Apprentice Workday on May 24?
>

Hi Faber

I have created a set of files in DNS from the data you had:

master/128.5.10.in-addr.arpa
master/stg.phx2.fedoraproject.org

The 128 file will be where reverse DNS of names will go.
The stg.phx2.fedoraproject.org will be where the hostnames will go.

It still needs some cleanup and after we are done with those we can
start the transfers which would work great as a Apprentice Workday.

Thanks for the initial ideas and I look forward to some feedback.

> By now i just attached a stg.phx2.fedoraproject.org file with new stage IPs
> added, as described by smooge.
>
> Of course as the time pass, some changes are made in dns/master (right now
> pdc-backend03 + pdc-backend03.stg has been added)
>
> so i will have to update it when is needed, let me know when you want it.
>
> giardia
>
>
>
> ___
> infrastructure mailing list -- infrastructure@lists.fedoraproject.org
> To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org
>



-- 
Stephen J Smoogen.
___
infrastructure mailing list -- infrastructure@lists.fedoraproject.org
To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org