[SAC] Mirroring OSGeo Downloads over OSUOSL ftp Service

Committees SAC mailing list
1

OSUOSL runs a high bandwidth, redundant (?), download cluster. They have
offered to host OSGeo Downloads there in order to prevent the current
Downloads machine from saturating it's vlan. It's doing ~ 1TB a day of
traffic.

I'm recommending we take advantage of this. I think the net result is
that download.osgeo.org would point to their service. We would keep
upload.osgeo.org where it is (Geotools webdav should use this, and any
other exotic services). Our users would still upload directly to our
machine via the upload name.

To make this work we need to either open an rsync service for them to
pull, or they can give us a shell account to push. I can't recall what
we currently have in the way of rsync or what would be easier.

Comments, questions, information about how to proceed?

Thanks,
Alex

PS: Once we get this working I'd like to work on expanding the space
allocated to our VM. That will be another ticket/thread.

2

A new ticket has been created and assigned an ID of [support.osuosl.org/27802].

---

From: tech@wildintellect.com <tech@wildintellect.com>

OSUOSL runs a high bandwidth, redundant (?), download cluster. They have
offered to host OSGeo Downloads there in order to prevent the current
Downloads machine from saturating it's vlan. It's doing ~ 1TB a day of
traffic.

I'm recommending we take advantage of this. I think the net result is
that download.osgeo.org would point to their service. We would keep
upload.osgeo.org where it is (Geotools webdav should use this, and any
other exotic services). Our users would still upload directly to our
machine via the upload name.

To make this work we need to either open an rsync service for them to
pull, or they can give us a shell account to push. I can't recall what
we currently have in the way of rsync or what would be easier.

Comments, questions, information about how to proceed?

Thanks,
Alex

PS: Once we get this working I'd like to work on expanding the space
allocated to our VM. That will be another ticket/thread.

3

OSUOSL Team,

Seems this might be easiest if you give us an account so we can push the
files when needed (let us determine the schedule).

Thanks,
Alex

On 10/07/2015 09:52 AM, tech@wildintellect.com via RT wrote:

A new ticket has been created and assigned an ID of [support.osuosl.org/27802].

---

From: tech@wildintellect.com <tech@wildintellect.com>

OSUOSL runs a high bandwidth, redundant (?), download cluster. They have
offered to host OSGeo Downloads there in order to prevent the current
Downloads machine from saturating it's vlan. It's doing ~ 1TB a day of
traffic.

I'm recommending we take advantage of this. I think the net result is
that download.osgeo.org would point to their service. We would keep
upload.osgeo.org where it is (Geotools webdav should use this, and any
other exotic services). Our users would still upload directly to our
machine via the upload name.

To make this work we need to either open an rsync service for them to
pull, or they can give us a shell account to push. I can't recall what
we currently have in the way of rsync or what would be easier.

Comments, questions, information about how to proceed?

Thanks,
Alex

PS: Once we get this working I'd like to work on expanding the space
allocated to our VM. That will be another ticket/thread.

_______________________________________________
Sac mailing list
Sac@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/sac

4

On Mon, Oct 12, 2015 at 08:21:26AM -0700, Alex Mandel wrote:

Seems this might be easiest if you give us an account so we can push the
files when needed (let us determine the schedule).

From my perspective I'd say no individual account is required. Let's

keep the profile as low as possible and instead provide an Rsync-
service to OSL, they just need to provide an IP address they use for
pulling from Rsync.

OSL folks, does this sound reasonable to you ?

  Martin.
--
Unix _IS_ user friendly - it's just selective about who its friends are !
--------------------------------------------------------------------------

5

On 10/15/2015 04:55 AM, Martin Spott via RT wrote:

On Mon, Oct 12, 2015 at 08:21:26AM -0700, Alex Mandel wrote:

Seems this might be easiest if you give us an account so we can push the
files when needed (let us determine the schedule).

From my perspective I'd say no individual account is required. Let's
keep the profile as low as possible and instead provide an Rsync-
service to OSL, they just need to provide an IP address they use for
pulling from Rsync.

OSL folks, does this sound reasonable to you ?

  Martin.

The only issue with that is that we can't control the timing in the
event we need to push files, or re-arrange the source machines.

Maybe we should discuss a little more 1st. It's not a bad thing to know
the IPs they plan to sync with anyways.

Thanks,
Alex

6

On 10/15/2015 08:48 AM, Alex Mandel wrote:

On 10/15/2015 04:55 AM, Martin Spott via RT wrote:

On Mon, Oct 12, 2015 at 08:21:26AM -0700, Alex Mandel wrote:

Seems this might be easiest if you give us an account so we can push the
files when needed (let us determine the schedule).

From my perspective I'd say no individual account is required. Let's
keep the profile as low as possible and instead provide an Rsync-
service to OSL, they just need to provide an IP address they use for
pulling from Rsync.

OSL folks, does this sound reasonable to you ?

  Martin.

The only issue with that is that we can't control the timing in the
event we need to push files, or re-arrange the source machines.

Maybe we should discuss a little more 1st. It's not a bad thing to know
the IPs they plan to sync with anyways.

Thanks,
Alex

I thought about this some more, I see issues with either setup.

1. We simply open an rsync process restricted to IP and allow OSUOSL to
pull.

The problem here is we don't have direct control to allow for changing
sources, using multiple sources, throttling the speed, picking the timing.

2. We get an account with a set list of SAC admins keys allowed.

The problem here is we'd need a key to push with from a cron job. Seems
somewhat unsafe to create a passphrase-less key for this.

Solution: Both

Why don't we have osuosl create an account, with a set list of SAC admin
keys. This allows us to login and configure the rsync pull ourselves and
time it with crontab. They might even be able to delegate the http conf
file for our domain to us too.

I recommend the following SAC admin keys, and solicit suggestion for
anyone else that should have configuration access:
Alex M.
Martin S.
Jurgen F.
Frank W.

I'd like to get this figured out by the end of this week.

Thanks,
Alex

7

On Tue, Oct 27, 2015 at 09:16:06AM -0700, Alex M wrote:

I'd like to get this figured out by the end of this week.

Fine with me, go ahead,

  Martin.
--
Unix _IS_ user friendly - it's just selective about who its friends are !
--------------------------------------------------------------------------

8

On 10/27/2015 09:16 AM, Alex M wrote:

On 10/15/2015 08:48 AM, Alex Mandel wrote:

On 10/15/2015 04:55 AM, Martin Spott via RT wrote:

On Mon, Oct 12, 2015 at 08:21:26AM -0700, Alex Mandel wrote:

Seems this might be easiest if you give us an account so we can push the
files when needed (let us determine the schedule).

From my perspective I'd say no individual account is required. Let's
keep the profile as low as possible and instead provide an Rsync-
service to OSL, they just need to provide an IP address they use for
pulling from Rsync.

OSL folks, does this sound reasonable to you ?

  Martin.

The only issue with that is that we can't control the timing in the
event we need to push files, or re-arrange the source machines.

Maybe we should discuss a little more 1st. It's not a bad thing to know
the IPs they plan to sync with anyways.

Thanks,
Alex

I thought about this some more, I see issues with either setup.

1. We simply open an rsync process restricted to IP and allow OSUOSL to
pull.

The problem here is we don't have direct control to allow for changing
sources, using multiple sources, throttling the speed, picking the timing.

2. We get an account with a set list of SAC admins keys allowed.

The problem here is we'd need a key to push with from a cron job. Seems
somewhat unsafe to create a passphrase-less key for this.

Solution: Both

Why don't we have osuosl create an account, with a set list of SAC admin
keys. This allows us to login and configure the rsync pull ourselves and
time it with crontab. They might even be able to delegate the http conf
file for our domain to us too.

I recommend the following SAC admin keys, and solicit suggestion for
anyone else that should have configuration access:
Alex M.
Martin S.
Jurgen F.
Frank W.

I'd like to get this figured out by the end of this week.

Thanks,
Alex

Anyone else need to be added to this list. Since downloads is such an
important service I want to make sure we've got enough backup people to
step in when needed. I suppose most people will continue to just push to
upload.osgeo.org and it will sync magically to the download.osgeo and
all will be good.

I'll send OSUOSL the publickeys later today.

Thanks,
Alex

9

Looks like this project got lost in the weeds, any chance of revisting
and proceeding with setup?

Thanks,
Alex

On 10/15/2015 08:51 AM, Jordan Evans via RT wrote:

On Thu Oct 15 08:49:01 2015, tech@wildintellect.com wrote:

On 10/15/2015 04:55 AM, Martin Spott via RT wrote:

On Mon, Oct 12, 2015 at 08:21:26AM -0700, Alex Mandel wrote:

Seems this might be easiest if you give us an account so we can push the
files when needed (let us determine the schedule).

From my perspective I'd say no individual account is required. Let's
keep the profile as low as possible and instead provide an Rsync-
service to OSL, they just need to provide an IP address they use for
pulling from Rsync.

OSL folks, does this sound reasonable to you ?

Martin.

The only issue with that is that we can't control the timing in the
event we need to push files, or re-arrange the source machines.

Maybe we should discuss a little more 1st. It's not a bad thing to know
the IPs they plan to sync with anyways.

We will do all of the pulling from 140.211.166.134.

--Jordan Evans

10

On Fri Mar 04 12:19:39 2016, tech@wildintellect.com wrote:

Looks like this project got lost in the weeds, any chance of revisting and
proceeding with setup?

I'm going through some old tickets and found this. Are you still interested in
getting this done?

Thanks-

--
Lance Albertson
Director
Oregon State University | Open Source Lab

11

On 10/26/18 10:16, Lance Albertson via RT wrote:

On Fri Mar 04 12:19:39 2016, tech@wildintellect.com wrote:

Looks like this project got lost in the weeds, any chance of revisting and
proceeding with setup?

I'm going through some old tickets and found this. Are you still interested in
getting this done?

Thanks-

Maybe.

We did just buy a new machine and were planning on moving over to that,
but extra mirrors is never a bad thing.

How would we go about setting it up, I think we're looking at .5-1 TB
worth of space, as we've outgrown our current allocation and want to
leave room for growth.

Thanks,
Alex

12

On 10/26/18 10:16, Lance Albertson via RT wrote:

On Fri Mar 04 12:19:39 2016, tech@wildintellect.com wrote:

Looks like this project got lost in the weeds, any chance of revisting and
proceeding with setup?

I'm going through some old tickets and found this. Are you still interested in
getting this done?

Thanks-

Maybe.

We did just buy a new machine and were planning on moving over to that,
but extra mirrors is never a bad thing.

How would we go about setting it up, I think we're looking at .5-1 TB
worth of space, as we've outgrown our current allocation and want to
leave room for growth.

Thanks,
Alex

13

On Fri Oct 26 12:19:29 2018, tech@wildintellect.com wrote:

Maybe.

We did just buy a new machine and were planning on moving over to that, but
extra mirrors is never a bad thing.

How would we go about setting it up, I think we're looking at .5-1 TB worth of
space, as we've outgrown our current allocation and want to leave room for
growth.

We can do it a variety of ways depending on what works best. We can either sync
from an rsync endpoint at a regular basis, or we could give you a shell account
on the master server where you can initiate the sync and also sync the slaves.

--
Lance Albertson
Director
Oregon State University | Open Source Lab

14

On Mon Oct 29 14:51:21 2018, ramereth wrote:

On Fri Oct 26 12:19:29 2018, tech@wildintellect.com wrote:
> Maybe.
>
> We did just buy a new machine and were planning on moving over to that, but
> extra mirrors is never a bad thing.
>
> How would we go about setting it up, I think we're looking at .5-1 TB worth
> of space, as we've outgrown our current allocation and want to leave room
> for growth.

We can do it a variety of ways depending on what works best. We can either
sync from an rsync endpoint at a regular basis, or we could give you a shell
account on the master server where you can initiate the sync and also sync the
slaves.

Just checking in on this to see if you still want to proceed or not.

--
Lance Albertson
Director
Oregon State University | Open Source Lab

15

On 11/30/18 10:41, Lance Albertson via RT wrote:

On Mon Oct 29 14:51:21 2018, ramereth wrote:

On Fri Oct 26 12:19:29 2018, tech@wildintellect.com wrote:

Maybe.

We did just buy a new machine and were planning on moving over to that, but
extra mirrors is never a bad thing.

How would we go about setting it up, I think we're looking at .5-1 TB worth
of space, as we've outgrown our current allocation and want to leave room
for growth.

We can do it a variety of ways depending on what works best. We can either
sync from an rsync endpoint at a regular basis, or we could give you a shell
account on the master server where you can initiate the sync and also sync the
slaves.

Just checking in on this to see if you still want to proceed or not.

Yes, we just didn't reach a decision about which method we prefer. It's
probably best if we give you an ssh account to our machine, and then you
pull with rsync over ssh a specified directory on maybe a nightly
schedule. At least lets try starting with that. I can see why later we
might want to be able to push, in order to get new releases mirrored sooner.

Thanks,
Alex

16

On 11/30/18 10:41, Lance Albertson via RT wrote:

On Mon Oct 29 14:51:21 2018, ramereth wrote:

On Fri Oct 26 12:19:29 2018, tech@wildintellect.com wrote:

Maybe.

We did just buy a new machine and were planning on moving over to that, but
extra mirrors is never a bad thing.

How would we go about setting it up, I think we're looking at .5-1 TB worth
of space, as we've outgrown our current allocation and want to leave room
for growth.

We can do it a variety of ways depending on what works best. We can either
sync from an rsync endpoint at a regular basis, or we could give you a shell
account on the master server where you can initiate the sync and also sync the
slaves.

Just checking in on this to see if you still want to proceed or not.

Yes, we just didn't reach a decision about which method we prefer. It's
probably best if we give you an ssh account to our machine, and then you
pull with rsync over ssh a specified directory on maybe a nightly
schedule. At least lets try starting with that. I can see why later we
might want to be able to push, in order to get new releases mirrored sooner.

Thanks,
Alex

17

Hi Alex,

We can get periodic mirroring setup for you while you ruminate whether you'd
like push access to our mirrors.

I just need an rsync endpoint/URL and the rsync command you use for syncing.

Here's our pubkey:
ssh-rsa
AAAAB3NzaC1yc2EAAAADAQABAAACAQDNAoeIFo7KBew2/7L9secSHE+BtBHJJmPgFiHy/yvMYaJdRz9J2kDmYg5O8CZUXLt7/fkQT4bdgaqZJT9NvFizEOzL/oXZMxgCmt/YLP6SBLUQ0F3fYVAnURVkMYtM11/AYTFlODiMjMqRgM1UPVLa13nLmI9jVJeI7vibKiRonI1uO/2k49Maboh82f6aM6KQ0Af4vEbLgK5mYXwHX3d7Q0K3DxHtsDgxkSMDvOU4w806hfMFROhoPAHah3SLzguaoxilCw7+ZTMR4Fk6Jbq4IZzq8WeZSeZDqA3e1z3gfbb0skBsAsttCddmrrTvaCIP7hxgEjKM8w/8vKcIspZZiMdWJass3Bu8C9Tm79WuGrzLRL/X2KiluXEmXS12TMiRxqheYN6U5xalw+kx8Fs3Byg/aIZkRkYB62ALv9nxy3qNyLEIIyRSUOVZ01F2cH4Ncqw/EkojQycq3+B1ptyynTfjI770AYoTegDsFL5F6s5EnUhwJJqwieSToGl3QsogLFSmna//+6gq0EfecnqOmcBMjR1GluIA9ICfaLd73plD+jBHA50l4vxBRkmhg6UJytkVNxVxPwKkIvGkbNLjGM55Pu1OFkw2RcXpnIIVVxCYI+3J9qS31TAW3cACw77vL5lQByykkyeVqI4ldPH0QR2b4ZcfEgDxcoV1jW6YnQ==
root@ftp-osl

Let me know if you need any more information from me.

On Fri Nov 30 12:59:36 2018, tech@wildintellect.com wrote:

On 11/30/18 10:41, Lance Albertson via RT wrote:
> On Mon Oct 29 14:51:21 2018, ramereth wrote:
>> On Fri Oct 26 12:19:29 2018, tech@wildintellect.com wrote:
>>> Maybe.
>>>
>>> We did just buy a new machine and were planning on moving over to
that, but
>>> extra mirrors is never a bad thing.
>>>
>>> How would we go about setting it up, I think we're looking at .5-1
TB worth
>>> of space, as we've outgrown our current allocation and want to
leave room
>>> for growth.
>>
>> We can do it a variety of ways depending on what works best. We can
either
>> sync from an rsync endpoint at a regular basis, or we could give
you a shell
>> account on the master server where you can initiate the sync and
also sync the
>> slaves.
>
> Just checking in on this to see if you still want to proceed or not.
>

Yes, we just didn't reach a decision about which method we prefer.
It's
probably best if we give you an ssh account to our machine, and then
you
pull with rsync over ssh a specified directory on maybe a nightly
schedule. At least lets try starting with that. I can see why later we
might want to be able to push, in order to get new releases mirrored
sooner.

Thanks,
Alex

--
Regards,
--------------
Hunter Lannon
Student Sysadmin
Open Source Lab
Oregon State University

18

Ping!
On Fri Dec 07 14:42:51 2018, kindlehl wrote:

Hi Alex,

We can get periodic mirroring setup for you while you ruminate whether
you'd
like push access to our mirrors.

I just need an rsync endpoint/URL and the rsync command you use for
syncing.

Here's our pubkey:
ssh-rsa

AAAAB3NzaC1yc2EAAAADAQABAAACAQDNAoeIFo7KBew2/7L9secSHE+BtBHJJmPgFiHy/yvMYaJdRz9J2kDmYg5O8CZUXLt7/fkQT4bdgaqZJT9NvFizEOzL/oXZMxgCmt/YLP6SBLUQ0F3fYVAnURVkMYtM11/AYTFlODiMjMqRgM1UPVLa13nLmI9jVJeI7vibKiRonI1uO/2k49Maboh82f6aM6KQ0Af4vEbLgK5mYXwHX3d7Q0K3DxHtsDgxkSMDvOU4w806hfMFROhoPAHah3SLzguaoxilCw7+ZTMR4Fk6Jbq4IZzq8WeZSeZDqA3e1z3gfbb0skBsAsttCddmrrTvaCIP7hxgEjKM8w/8vKcIspZZiMdWJass3Bu8C9Tm79WuGrzLRL/X2KiluXEmXS12TMiRxqheYN6U5xalw+kx8Fs3Byg/aIZkRkYB62ALv9nxy3qNyLEIIyRSUOVZ01F2cH4Ncqw/EkojQycq3+B1ptyynTfjI770AYoTegDsFL5F6s5EnUhwJJqwieSToGl3QsogLFSmna//+6gq0EfecnqOmcBMjR1GluIA9ICfaLd73plD+jBHA50l4vxBRkmhg6UJytkVNxVxPwKkIvGkbNLjGM55Pu1OFkw2RcXpnIIVVxCYI+3J9qS31TAW3cACw77vL5lQByykkyeVqI4ldPH0QR2b4ZcfEgDxcoV1jW6YnQ==

root@ftp-osl

Let me know if you need any more information from me.

On Fri Nov 30 12:59:36 2018, tech@wildintellect.com wrote:
> On 11/30/18 10:41, Lance Albertson via RT wrote:
> > On Mon Oct 29 14:51:21 2018, ramereth wrote:
> >> On Fri Oct 26 12:19:29 2018, tech@wildintellect.com wrote:
> >>> Maybe.
> >>>
> >>> We did just buy a new machine and were planning on moving over
to
> that, but
> >>> extra mirrors is never a bad thing.
> >>>
> >>> How would we go about setting it up, I think we're looking at
.5-1
> TB worth
> >>> of space, as we've outgrown our current allocation and want to
> leave room
> >>> for growth.
> >>
> >> We can do it a variety of ways depending on what works best. We
can
> either
> >> sync from an rsync endpoint at a regular basis, or we could give
> you a shell
> >> account on the master server where you can initiate the sync and
> also sync the
> >> slaves.
> >
> > Just checking in on this to see if you still want to proceed or
not.
> >
>
> Yes, we just didn't reach a decision about which method we prefer.
> It's
> probably best if we give you an ssh account to our machine, and then
> you
> pull with rsync over ssh a specified directory on maybe a nightly
> schedule. At least lets try starting with that. I can see why later
we
> might want to be able to push, in order to get new releases mirrored
> sooner.
>
> Thanks,
> Alex
>

--
Regards,
--------------
Hunter Lannon
Student Sysadmin
Open Source Lab
Oregon State University

--
Regards,
--------------
Hunter Lannon
Student Sysadmin
Open Source Lab
Oregon State University

19

Ha, we were just talking about this at our meeting. Will try to get it
setup soon.

Thanks,
Alex

On 1/3/19 13:18, Hunter Lannon via RT wrote:

Ping!
On Fri Dec 07 14:42:51 2018, kindlehl wrote:

Hi Alex,

We can get periodic mirroring setup for you while you ruminate whether
you'd
like push access to our mirrors.

I just need an rsync endpoint/URL and the rsync command you use for
syncing.

Here's our pubkey:
ssh-rsa

AAAAB3NzaC1yc2EAAAADAQABAAACAQDNAoeIFo7KBew2/7L9secSHE+BtBHJJmPgFiHy/yvMYaJdRz9J2kDssh-rsa

AAAAB3NzaC1yc2EAAAADAQABAAACAQDNAoeIFo7KBew2/7L9secSHE+BtBHJJmPgFiHy/yvMYaJdRz9J2kDmYg5O8CZUXLt7/fkQT4bdgaqZJT9NvFizEOzL/oXZMxgCmt/YLP6SBLUQ0F3fYVAnURVkMYtM11/AYTFlODiMjMqRgM1UPVLa13nLmI9jVJeI7vibKiRonI1uO/2k49Maboh82f6aM6KQ0Af4vEbLgK5mYXwHX3d7Q0K3DxHtsDgxkSMDvOU4w806hfMFROhoPAHah3SLzguaoxilCw7+ZTMR4Fk6Jbq4IZzq8WeZSeZDqA3e1z3gfbb0skBsAsttCddmrrTvaCIP7hxgEjKM8w/8vKcIspZZiMdWJass3Bu8C9Tm79WuGrzLRL/X2KiluXEmXS12TMiRxqheYN6U5xalw+kx8Fs3Byg/aIZkRkYB62ALv9nxy3qNyLEIIyRSUOVZ01F2cH4Ncqw/EkojQycq3+B1ptyynTfjI770AYoTegDsFL5F6s5EnUhwJJqwieSToGl3QsogLFSmna//+6gq0EfecnqOmcBMjR1GluIA9ICfaLd73plD+jBHA50l4vxBRkmhg6UJytkVNxVxPwKkIvGkbNLjGM55Pu1OFkw2RcXpnIIVVxCYI+3J9qS31TAW3cACw77vL5lQByykkyeVqI4ldPH0QR2b4ZcfEgDxcoV1jW6YnQ==
root@ftp-oslmYg5O8CZUXLt7/fkQT4bdgaqZJT9NvFizEOzL/oXZMxgCmt/YLP6SBLUQ0F3fYVAnURVkMYtM11/AYTFlODiMjMqRgM1UPVLa13nLmI9jVJeI7vibKiRonI1uO/2k49Maboh82f6aM6KQ0Af4vEbLgK5mYXwHX3d7Q0K3DxHtsDgxkSMDvOU4w806hfMFROhoPAHah3SLzguaoxilCw7+ZTMR4Fk6Jbq4IZzq8WeZSeZDqA3e1z3gfbb0skBsAsttCddmrrTvaCIP7hxgEjKM8w/8vKcIspZZiMdWJass3Bu8C9Tm79WuGrzLRL/X2KiluXEmXS12TMiRxqheYN6U5xalw+kx8Fs3Byg/aIZkRkYB62ALv9nxy3qNyLEIIyRSUOVZ01F2cH4Ncqw/EkojQycq3+B1ptyynTfjI770AYoTegDsFL5F6s5EnUhwJJqwieSToGl3QsogLFSmna//+6gq0EfecnqOmcBMjR1GluIA9ICfaLd73plD+jBHA50l4vxBRkmhg6UJytkVNxVxPwKkIvGkbNLjGM55Pu1OFkw2RcXpnIIVVxCYI+3J9qS31TAW3cACw77vL5lQByykkyeVqI4ldPH0QR2b4ZcfEgDxcoV1jW6YnQ==

root@ftp-osl

Let me know if you need any more information from me.

On Fri Nov 30 12:59:36 2018, tech@wildintellect.com wrote:

On 11/30/18 10:41, Lance Albertson via RT wrote:

On Mon Oct 29 14:51:21 2018, ramereth wrote:

On Fri Oct 26 12:19:29 2018, tech@wildintellect.com wrote:

Maybe.

We did just buy a new machine and were planning on moving over

to

that, but

extra mirrors is never a bad thing.

How would we go about setting it up, I think we're looking at

.5-1

TB worth

of space, as we've outgrown our current allocation and want to

leave room

for growth.

ssh-rsa

AAAAB3NzaC1yc2EAAAADAQABAAACAQDNAoeIFo7KBew2/7L9secSHE+BtBHJJmPgFiHy/yvMYaJdRz9J2kDmYg5O8CZUXLt7/fkQT4bdgaqZJT9NvFizEOzL/oXZMxgCmt/YLP6SBLUQ0F3fYVAnURVkMYtM11/AYTFlODiMjMqRgM1UPVLa13nLmI9jVJeI7vibKiRonI1uO/2k49Maboh82f6aM6KQ0Af4vEbLgK5mYXwHX3d7Q0K3DxHtsDgxkSMDvOU4w806hfMFROhoPAHah3SLzguaoxilCw7+ZTMR4Fk6Jbq4IZzq8WeZSeZDqA3e1z3gfbb0skBsAsttCddmrrTvaCIP7hxgEjKM8w/8vKcIspZZiMdWJass3Bu8C9Tm79WuGrzLRL/X2KiluXEmXS12TMiRxqheYN6U5xalw+kx8Fs3Byg/aIZkRkYB62ALv9nxy3qNyLEIIyRSUOVZ01F2cH4Ncqw/EkojQycq3+B1ptyynTfjI770AYoTegDsFL5F6s5EnUhwJJqwieSToGl3QsogLFSmna//+6gq0EfecnqOmcBMjR1GluIA9ICfaLd73plD+jBHA50l4vxBRkmhg6UJytkVNxVxPwKkIvGkbNLjGM55Pu1OFkw2RcXpnIIVVxCYI+3J9qS31TAW3cACw77vL5lQByykkyeVqI4ldPH0QR2b4ZcfEgDxcoV1jW6YnQ==
root@ftp-osl

We can do it a variety of ways depending on what works best. We

can

either

sync from an rsync endpoint at a regular basis, or we could give

you a shell

account on the master server where you can initiate the sync and

also sync the

slaves.

Just checking in on this to see if you still want to proceed or

not.

Yes, we just didn't reach a decision about which method we prefer.ssh-rsa

AAAAB3NzaC1yc2EAAAADAQABAAACAQDNAoeIFo7KBew2/7L9secSHE+BtBHJJmPgFiHy/yvMYaJdRz9J2kDmYg5O8CZUXLt7/fkQT4bdgaqZJT9NvFizEOzL/oXZMxgCmt/YLP6SBLUQ0F3fYVAnURVkMYtM11/AYTFlODiMjMqRgM1UPVLa13nLmI9jVJeI7vibKiRonI1uO/2k49Maboh82f6aM6KQ0Af4vEbLgK5mYXwHX3d7Q0K3DxHtsDgxkSMDvOU4w806hfMFROhoPAHah3SLzguaoxilCw7+ZTMR4Fk6Jbq4IZzq8WeZSeZDqA3e1z3gfbb0skBsAsttCddmrrTvaCIP7hxgEjKM8w/8vKcIspZZiMdWJass3Bu8C9Tm79WuGrzLRL/X2KiluXEmXS12TMiRxqheYN6U5xalw+kx8Fs3Byg/aIZkRkYB62ALv9nxy3qNyLEIIyRSUOVZ01F2cH4Ncqw/EkojQycq3+B1ptyynTfjI770AYoTegDsFL5F6s5EnUhwJJqwieSToGl3QsogLFSmna//+6gq0EfecnqOmcBMjR1GluIA9ICfaLd73plD+jBHA50l4vxBRkmhg6UJytkVNxVxPwKkIvGkbNLjGM55Pu1OFkw2RcXpnIIVVxCYI+3J9qS31TAW3cACw77vL5lQByykkyeVqI4ldPH0QR2b4ZcfEgDxcoV1jW6YnQ==
root@ftp-osl

It's
probably best if we give you an ssh account to our machine, and then
you
pull with rsync over ssh a specified directory on maybe a nightly
schedule. At least lets try starting with that. I can see why later

we

might want to be able to push, in order to get new releases mirrored
sooner.

Thanks,
Alex

--
Regards,
--------------
Hunter Lannon
Student Sysadmin
Open Source Lab
Oregon State University

--
Regards,
--------------
Hunter Lannon
Student Sysadmin
Open Source Lab
Oregon State University

20

Ping!
On Thu Jan 03 13:21:24 2019, tech@wildintellect.com wrote:

Ha, we were just talking about this at our meeting. Will try to get it
setup soon.

Thanks,
Alex

On 1/3/19 13:18, Hunter Lannon via RT wrote:
> Ping!
> On Fri Dec 07 14:42:51 2018, kindlehl wrote:
>> Hi Alex,
>>
>> We can get periodic mirroring setup for you while you ruminate
whether
>> you'd
>> like push access to our mirrors.
>>
>> I just need an rsync endpoint/URL and the rsync command you use for
>> syncing.
>>
>> Here's our pubkey:
>> ssh-rsa
>>
>

AAAAB3NzaC1yc2EAAAADAQABAAACAQDNAoeIFo7KBew2/7L9secSHE+BtBHJJmPgFiHy/yvMYaJdRz9J2kDssh-

rsa

AAAAB3NzaC1yc2EAAAADAQABAAACAQDNAoeIFo7KBew2/7L9secSHE+BtBHJJmPgFiHy/yvMYaJdRz9J2kDmYg5O8CZUXLt7/fkQT4bdgaqZJT9NvFizEOzL/oXZMxgCmt/YLP6SBLUQ0F3fYVAnURVkMYtM11/AYTFlODiMjMqRgM1UPVLa13nLmI9jVJeI7vibKiRonI1uO/2k49Maboh82f6aM6KQ0Af4vEbLgK5mYXwHX3d7Q0K3DxHtsDgxkSMDvOU4w806hfMFROhoPAHah3SLzguaoxilCw7+ZTMR4Fk6Jbq4IZzq8WeZSeZDqA3e1z3gfbb0skBsAsttCddmrrTvaCIP7hxgEjKM8w/8vKcIspZZiMdWJass3Bu8C9Tm79WuGrzLRL/X2KiluXEmXS12TMiRxqheYN6U5xalw+kx8Fs3Byg/aIZkRkYB62ALv9nxy3qNyLEIIyRSUOVZ01F2cH4Ncqw/EkojQycq3+B1ptyynTfjI770AYoTegDsFL5F6s5EnUhwJJqwieSToGl3QsogLFSmna//+6gq0EfecnqOmcBMjR1GluIA9ICfaLd73plD+jBHA50l4vxBRkmhg6UJytkVNxVxPwKkIvGkbNLjGM55Pu1OFkw2RcXpnIIVVxCYI+3J9qS31TAW3cACw77vL5lQByykkyeVqI4ldPH0QR2b4ZcfEgDxcoV1jW6YnQ==

root@ftp-

oslmYg5O8CZUXLt7/fkQT4bdgaqZJT9NvFizEOzL/oXZMxgCmt/YLP6SBLUQ0F3fYVAnURVkMYtM11/AYTFlODiMjMqRgM1UPVLa13nLmI9jVJeI7vibKiRonI1uO/2k49Maboh82f6aM6KQ0Af4vEbLgK5mYXwHX3d7Q0K3DxHtsDgxkSMDvOU4w806hfMFROhoPAHah3SLzguaoxilCw7+ZTMR4Fk6Jbq4IZzq8WeZSeZDqA3e1z3gfbb0skBsAsttCddmrrTvaCIP7hxgEjKM8w/8vKcIspZZiMdWJass3Bu8C9Tm79WuGrzLRL/X2KiluXEmXS12TMiRxqheYN6U5xalw+kx8Fs3Byg/aIZkRkYB62ALv9nxy3qNyLEIIyRSUOVZ01F2cH4Ncqw/EkojQycq3+B1ptyynTfjI770AYoTegDsFL5F6s5EnUhwJJqwieSToGl3QsogLFSmna//+6gq0EfecnqOmcBMjR1GluIA9ICfaLd73plD+jBHA50l4vxBRkmhg6UJytkVNxVxPwKkIvGkbNLjGM55Pu1OFkw2RcXpnIIVVxCYI+3J9qS31TAW3cACw77vL5lQByykkyeVqI4ldPH0QR2b4ZcfEgDxcoV1jW6YnQ==

>> root@ftp-osl
>>
>> Let me know if you need any more information from me.
>>
>> On Fri Nov 30 12:59:36 2018, tech@wildintellect.com wrote:
>>> On 11/30/18 10:41, Lance Albertson via RT wrote:
>>>> On Mon Oct 29 14:51:21 2018, ramereth wrote:
>>>>> On Fri Oct 26 12:19:29 2018, tech@wildintellect.com wrote:
>>>>>> Maybe.
>>>>>>
>>>>>> We did just buy a new machine and were planning on moving over
>> to
>>> that, but
>>>>>> extra mirrors is never a bad thing.
>>>>>>
>>>>>> How would we go about setting it up, I think we're looking at
>> .5-1
>>> TB worth
>>>>>> of space, as we've outgrown our current allocation and want to
>>> leave room
>>>>>> for growth.
>>>>>ssh-rsa

AAAAB3NzaC1yc2EAAAADAQABAAACAQDNAoeIFo7KBew2/7L9secSHE+BtBHJJmPgFiHy/yvMYaJdRz9J2kDmYg5O8CZUXLt7/fkQT4bdgaqZJT9NvFizEOzL/oXZMxgCmt/YLP6SBLUQ0F3fYVAnURVkMYtM11/AYTFlODiMjMqRgM1UPVLa13nLmI9jVJeI7vibKiRonI1uO/2k49Maboh82f6aM6KQ0Af4vEbLgK5mYXwHX3d7Q0K3DxHtsDgxkSMDvOU4w806hfMFROhoPAHah3SLzguaoxilCw7+ZTMR4Fk6Jbq4IZzq8WeZSeZDqA3e1z3gfbb0skBsAsttCddmrrTvaCIP7hxgEjKM8w/8vKcIspZZiMdWJass3Bu8C9Tm79WuGrzLRL/X2KiluXEmXS12TMiRxqheYN6U5xalw+kx8Fs3Byg/aIZkRkYB62ALv9nxy3qNyLEIIyRSUOVZ01F2cH4Ncqw/EkojQycq3+B1ptyynTfjI770AYoTegDsFL5F6s5EnUhwJJqwieSToGl3QsogLFSmna//+6gq0EfecnqOmcBMjR1GluIA9ICfaLd73plD+jBHA50l4vxBRkmhg6UJytkVNxVxPwKkIvGkbNLjGM55Pu1OFkw2RcXpnIIVVxCYI+3J9qS31TAW3cACw77vL5lQByykkyeVqI4ldPH0QR2b4ZcfEgDxcoV1jW6YnQ==

root@ftp-osl
>>>>> We can do it a variety of ways depending on what works best. We
>> can
>>> either
>>>>> sync from an rsync endpoint at a regular basis, or we could give
>>> you a shell
>>>>> account on the master server where you can initiate the sync and
>>> also sync the
>>>>> slaves.
>>>>
>>>> Just checking in on this to see if you still want to proceed or
>> not.
>>>>
>>>
>>> Yes, we just didn't reach a decision about which method we
prefer.ssh-rsa

AAAAB3NzaC1yc2EAAAADAQABAAACAQDNAoeIFo7KBew2/7L9secSHE+BtBHJJmPgFiHy/yvMYaJdRz9J2kDmYg5O8CZUXLt7/fkQT4bdgaqZJT9NvFizEOzL/oXZMxgCmt/YLP6SBLUQ0F3fYVAnURVkMYtM11/AYTFlODiMjMqRgM1UPVLa13nLmI9jVJeI7vibKiRonI1uO/2k49Maboh82f6aM6KQ0Af4vEbLgK5mYXwHX3d7Q0K3DxHtsDgxkSMDvOU4w806hfMFROhoPAHah3SLzguaoxilCw7+ZTMR4Fk6Jbq4IZzq8WeZSeZDqA3e1z3gfbb0skBsAsttCddmrrTvaCIP7hxgEjKM8w/8vKcIspZZiMdWJass3Bu8C9Tm79WuGrzLRL/X2KiluXEmXS12TMiRxqheYN6U5xalw+kx8Fs3Byg/aIZkRkYB62ALv9nxy3qNyLEIIyRSUOVZ01F2cH4Ncqw/EkojQycq3+B1ptyynTfjI770AYoTegDsFL5F6s5EnUhwJJqwieSToGl3QsogLFSmna//+6gq0EfecnqOmcBMjR1GluIA9ICfaLd73plD+jBHA50l4vxBRkmhg6UJytkVNxVxPwKkIvGkbNLjGM55Pu1OFkw2RcXpnIIVVxCYI+3J9qS31TAW3cACw77vL5lQByykkyeVqI4ldPH0QR2b4ZcfEgDxcoV1jW6YnQ==

root@ftp-osl
>>> It's
>>> probably best if we give you an ssh account to our machine, and
then
>>> you
>>> pull with rsync over ssh a specified directory on maybe a nightly
>>> schedule. At least lets try starting with that. I can see why
later
>> we
>>> might want to be able to push, in order to get new releases
mirrored
>>> sooner.
>>>
>>> Thanks,
>>> Alex
>>>
>>
>>
>> --
>> Regards,
>> --------------
>> Hunter Lannon
>> Student Sysadmin
>> Open Source Lab
>> Oregon State University
>
>
> --
> Regards,
> --------------
> Hunter Lannon
> Student Sysadmin
> Open Source Lab
> Oregon State University
>

--
Regards,
--------------
Hunter Lannon
Student Sysadmin
Open Source Lab
Oregon State University