On Mon, Jul 03, 2023 at 10:30:42PM +0200, Bastian Blank wrote:
> Hi Julien
>
> On Wed, Apr 26, 2023 at 02:10:05PM +0200, Julien Cristau wrote:
> > I haven't been able to get connections to the host working again after
> > the dhcp issues, can we maybe start over, using debian 11, and if
> >
Hi Julien
On Wed, Apr 26, 2023 at 02:10:05PM +0200, Julien Cristau wrote:
> I haven't been able to get connections to the host working again after
> the dhcp issues, can we maybe start over, using debian 11, and if
> possible some form of OOB access?
I finally managed to get to it, sorry about
Hi Bastian,
I haven't been able to get connections to the host working again after
the dhcp issues, can we maybe start over, using debian 11, and if
possible some form of OOB access?
Thanks,
Julien
On Mon, Mar 13, 2023 at 08:58:15 +0100, Bastian Blank wrote:
> On Sat, Mar 11, 2023 at
On Sat, Mar 11, 2023 at 12:43:52PM +0100, Julien Cristau wrote:
> I finally got around to the initial setup. A couple of things so far:
> - the machine is running bookworm; that's going to cause extra work
> initially. I'll give it a try anyway, since it's essentially work
> we'll need to do
On Thu, Feb 16, 2023 at 06:14:53PM +0100, Bastian Blank wrote:
> On Thu, Feb 16, 2023 at 01:23:41PM +0100, Bastian Blank wrote:
> > Okay, 4TB it is. We can always grow if we need to.
>
> Setup complete. IP is 2600:1f13:fb2:f400:6b1e:beae:ebbc:c6a
>
Hi Bastian,
I finally got around to the
On Thu, Feb 16, 2023 at 06:14:53PM +0100, Bastian Blank wrote:
> On Thu, Feb 16, 2023 at 01:23:41PM +0100, Bastian Blank wrote:
> > Okay, 4TB it is. We can always grow if we need to.
> Setup complete. IP is 2600:1f13:fb2:f400:6b1e:beae:ebbc:c6a
Some remarks:
Please always communicate the range
On Thu, Feb 16, 2023 at 01:23:41PM +0100, Bastian Blank wrote:
> Okay, 4TB it is. We can always grow if we need to.
Setup complete. IP is 2600:1f13:fb2:f400:6b1e:beae:ebbc:c6a
Regards,
Bastian
--
Knowledge, sir, should be free to all!
-- Harry Mudd, "I, Mudd", stardate 4513.3
Hi
On Wed, Feb 15, 2023 at 02:47:00PM +0100, Julien Cristau wrote:
> On Wed, Feb 15, 2023 at 02:16:08PM +0100, Bastian Blank wrote:
> > On Mon, Feb 13, 2023 at 10:12:01AM +0100, Bastian Blank wrote:
> > > - One dedicated /56 per region for all DSA stuff
> > > - One instance, m6g.2xlarge, arm64,
Hi Bastian,
Thanks for getting this sorted for us.
On Wed, Feb 15, 2023 at 02:16:08PM +0100, Bastian Blank wrote:
> Hi
>
> On Mon, Feb 13, 2023 at 10:12:01AM +0100, Bastian Blank wrote:
> > - One dedicated /56 per region for all DSA stuff
> > - One instance, m6g.2xlarge, arm64, Debian 12 (also
Hi
On Mon, Feb 13, 2023 at 10:12:01AM +0100, Bastian Blank wrote:
> - One dedicated /56 per region for all DSA stuff
> - One instance, m6g.2xlarge, arm64, Debian 12 (also possible is Debian
> 11)
> - One dedicated data volume with ext4, on instance creation mounted on
> /srv
> - SSH keys
Hi
On Wed, Feb 08, 2023 at 09:26:55PM -0800, Ross Vandegrift wrote:
> Okay, great. We're going to go ahead and work on deploying this.
> Here's what we're going to deploy, please let us know if anything sounds
> wrong:
This is now
On Sat, Feb 11, 2023 at 11:59:16AM +0100, Julien Cristau wrote:
> On Wed, Feb 08, 2023 at 09:26:55PM -0800, Ross Vandegrift wrote:
> > Do you have a list of hosts that should be permitted ssh access?
> Can we (DSA) control the cloud-side firewall? If not then we'll
> probably want it open to the
On Wed, Feb 08, 2023 at 09:26:55PM -0800, Ross Vandegrift wrote:
> Here's what we're going to deploy, please let us know if anything sounds
> wrong:
>
> - 8 cpu arm64, 16G of RAM (in AWS-speak: c6g.2xlarge)
> - two disks:
> - root volume for the OS
> - data volume that can persist the data if
On Thu, Feb 09, 2023 at 08:27:34AM +0100, Bastian Blank wrote:
> On Wed, Feb 08, 2023 at 09:26:55PM -0800, Ross Vandegrift wrote:
> > - 8 cpu arm64, 16G of RAM (in AWS-speak: c6g.2xlarge)
>
> My thought was on m6g.2xlarge. With a more useful amount of ram (32
> GB). While rsync is CPU
On Wed, Feb 08, 2023 at 09:26:55PM -0800, Ross Vandegrift wrote:
> - 8 cpu arm64, 16G of RAM (in AWS-speak: c6g.2xlarge)
My thought was on m6g.2xlarge. With a more useful amount of ram (32
GB). While rsync is CPU intensive, it needs a lot of cache.
Bastian
--
Military secrets are the most
Hi Julien,
On Mon, Jan 23, 2023 at 05:24:51PM +0100, Julien Cristau wrote:
> On Tue, Jan 17, 2023 at 22:22:59 -0800, Ross Vandegrift wrote:
> > It probably makes sense for the cloud team to own the cloud
> > infrastructure, and DSA to own the OS config and ongoing operations. Is
> > this what
Hi Julien
On Thu, Mar 17, 2022 at 12:03:18PM +0100, Julien Cristau wrote:
> Would it be possible to work with the cloud team to stand up appropriate
> accounts and so on on one of the cloud infras Debian has a relationship
> with? I don't have a whole lot of knowledge of this space so will
>
Hi Julien,
Digging up this thread after our last cloud team meeting, hoping to
shake out the next steps. Summarizing things so far:
1. you've provded some technical requirements for the hosts, all of
which sound easily do-able to me.
2. Amazon has given us the go-ahead to use their sponsored
> On Mar 17, 2022, at 12:55 PM, Noah Meyerhans wrote:
>
> (Disclosure: I'm employed by AWS, and generally a fan of it, but am not
> speaking in any official capacity on its behalf. Never the less, you
> may want to consider the possibility that my position is biased.)
>
> On Thu, Mar 17,
Hi Julien
On Thu, Mar 17, 2022 at 10:01:11PM +0100, Julien Cristau wrote:
> Looking at syncproxy2.wna
> (https://munin.debian.org/debian.org/mirror-isc.debian.org/ip_149_20_4_16.html
> and
> https://munin.debian.org/debian.org/mirror-isc.debian.org/ip_2001_4f8_1_c__16.html)
> it looks like we're
Hi Julien
On Thu, Mar 17, 2022 at 10:31:33PM +0100, Julien Cristau wrote:
> > You are just talking about the authenticated rsync and push stuff right
> > now? Because mirror-isc.d.o for example does more.
> I figured we'd start there, yes. Moving static mirrors around seems a lot
> easier.
You
Hi Bastian,
On Thu, Mar 17, 2022 at 09:58:12PM +0100, Bastian Blank wrote:
> Hi Julien
>
> On Thu, Mar 17, 2022 at 12:03:18PM +0100, Julien Cristau wrote:
> > DSA's looking into options to replace some of our archive mirroring
> > infrastructure. For context, so far we've been maintaining a few
Hi Julien
On Thu, Mar 17, 2022 at 12:03:18PM +0100, Julien Cristau wrote:
> DSA's looking into options to replace some of our archive mirroring
> infrastructure. For context, so far we've been maintaining a few machines
> around the globe, called syncproxies, that serve as "hubs" for archive
>
Hi Noah,
On Thu, Mar 17, 2022 at 12:55:59PM -0700, Noah Meyerhans wrote:
> On Thu, Mar 17, 2022 at 12:03:18PM +0100, Julien Cristau wrote:
> > DSA's looking into options to replace some of our archive mirroring
> > infrastructure. For context, so far we've been maintaining a few machines
> >
(Disclosure: I'm employed by AWS, and generally a fan of it, but am not
speaking in any official capacity on its behalf. Never the less, you
may want to consider the possibility that my position is biased.)
On Thu, Mar 17, 2022 at 12:03:18PM +0100, Julien Cristau wrote:
> DSA's looking into
Hi,
DSA's looking into options to replace some of our archive mirroring
infrastructure. For context, so far we've been maintaining a few machines
around the globe, called syncproxies, that serve as "hubs" for archive
mirroring and push downstream mirrors.
As some of that hardware ages we're
26 matches
Mail list logo
