public inbox for overseers@sourceware.org
 help / color / mirror / Atom feed
From: Karsten Wade <kwade@redhat.com>
To: "Frank Ch. Eigler" <fche@elastic.org>
Cc: "Frank Ch. Eigler" <fche@redhat.com>,
	overseers@sourceware.org, Jason Brooks <jbrooks@redhat.com>
Subject: Re: Looking for service/server operators
Date: Tue, 12 Dec 2017 18:43:00 -0000	[thread overview]
Message-ID: <12c53526-b711-0d7b-4488-03b8b983a358@redhat.com> (raw)
In-Reply-To: <20170726164956.GA106052@elastic.org>


[-- Attachment #1.1: Type: text/plain, Size: 1858 bytes --]

Frank:

I've included you on a thread with the other parties involved so we can
get a decision on bare metal vs. VM by this Friday.

That VM would be provided by RDO Cloud on an ongoing basis. Our team
would help create and broker the initial relationship, then get out of
the way once you all and RDO Cloud ops team are properly connected.

Some further comments below:

On 07/26/2017 09:49 AM, Frank Ch. Eigler wrote:
> The next resource we seem to be short of is disk iops.  Would y'll be
> able to help fund something like this pciexpress ssd card:
> https://www.newegg.com/Product/Product.aspx?item=0D9-000G-00071 ?

I would be happy to get that for you from OSAS, we some have budget
specifically for such things.

The questions are:

* Is it safe to do an upgrade with existing hardware?
* Should we wait for the new VM/server before proceeding with an
upgrade? But then why bother?
  - One point is that it may still be a few months before something is
operational to back up or replace the current server, where we can get
that part delivered very soon and installed in the system fairly
quickly, but are you all ready on the operations side for that?

Thanks for working with us and having patience as we try to 'help'. ;-)
Part of what our team is doing is finding all the community
infrastructure that has built up organically over the years and make
sure it has ongoing love and attention from the various groups at Red
Hat who care ... once they know about and have something plugged into
their systems. So plugging into the systems is what OSAS Community Infra
team is busy doing all the time and happy to continue helping here.

Best regards,

- Karsten
-- 
Karsten Wade
Community Infrastructure Team : https://osci.io
Red Hat Open Source and Standards (OSAS) : @redhatopen
@quaid gpg: AD0E0C41


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

      reply	other threads:[~2017-12-12 18:43 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-16 19:15 Karsten Wade
2017-03-16 19:40 ` Frank Ch. Eigler
2017-03-16 19:54   ` Karsten Wade
2017-07-25 20:41   ` Karsten Wade
2017-07-26 15:33     ` Christopher Faylor
2017-07-26 16:50     ` Frank Ch. Eigler
2017-12-12 18:43       ` Karsten Wade [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=12c53526-b711-0d7b-4488-03b8b983a358@redhat.com \
    --to=kwade@redhat.com \
    --cc=fche@elastic.org \
    --cc=fche@redhat.com \
    --cc=jbrooks@redhat.com \
    --cc=overseers@sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).