DPDK CI discussions
 help / color / Atom feed
From: Jeremy Plsek <jplsek@iol.unh.edu>
To: ci@dpdk.org
Cc: dpdklab@iol.unh.edu
Subject: Re: [dpdk-ci] DPDK Community Lab CI will be down
Date: Tue, 23 Jul 2019 16:14:38 -0400
Message-ID: <CA+xUZB6nLxOw0vdhoNOFQ0aUjeUz0fuuPuChmqk9vwHVvzT69w@mail.gmail.com> (raw)
In-Reply-To: <CA+xUZB5CDJhYSoo7=BgEw-K9fv0bgnXHFjQmM0oZ34aWiMBW7Q@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1155 bytes --]

Hi,

Everything should be back up and running.

For existing VPN configurations, you will need change the "dev" option from
"tap" to "tun".
If the "dev" option is not changed, you'll be able to connect to the VPN
server, but you won't be able to reach anything.
You have any VPN issues, let me know!

Thanks.

On Fri, Jul 19, 2019 at 1:26 PM Jeremy Plsek <jplsek@iol.unh.edu> wrote:

> Hi,
>
> We are almost done with our migration, and there are two final steps that
> need to be done:
> 1. Move all the data to the new system
> 2. Update the VPN configuration.
>
> For 1, the CI will be shut down and may take several hours to complete.
> For 2, the CI will be back and running by this time. We may look into
> fixing this on either Monday or Tuesday.
>
> I'll reply back once the migration and VPN updates are done. In
> particular, the VPN client configuration will need to be updated. I'll send
> instructions on how to update the configuration, but I can also regenerate
> configurations if anyone has issues with this migration.
>
> Thanks.
> --
> Jeremy Plsek
> UNH InterOperability Laboratory
>


-- 
Jeremy Plsek
UNH InterOperability Laboratory

[-- Attachment #2: Type: text/html, Size: 2327 bytes --]

<div dir="ltr"><div>Hi,</div><div><br></div><div>Everything should be back up and running.</div><div><br></div><div>For existing VPN configurations, you will need change the &quot;dev&quot; option from &quot;tap&quot; to &quot;tun&quot;.</div><div>If the &quot;dev&quot; option is not changed, you&#39;ll be able to connect to the VPN server, but you won&#39;t be able to reach anything.<br></div><div>You have any VPN issues, let me know!<br></div><div><br></div><div>Thanks.<br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Fri, Jul 19, 2019 at 1:26 PM Jeremy Plsek &lt;<a href="mailto:jplsek@iol.unh.edu" target="_blank">jplsek@iol.unh.edu</a>&gt; wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div>Hi,</div><div><br></div><div>We are almost done with our migration, and there are two final steps that need to be done:</div><div>1. Move all the data to the new system</div><div>2. Update the VPN configuration.<br></div><div><br></div><div>For 1, the CI will be shut down and may take several hours to complete.</div><div>For 2, the CI will be back and running by this time. We may look into fixing this on either Monday or Tuesday.</div><div><br></div><div>I&#39;ll reply back once the migration and VPN updates are done. In particular, the VPN client configuration will need to be updated. I&#39;ll send instructions on how to update the configuration, but I can also regenerate configurations if anyone has issues with this migration.<br></div><div><br></div><div>Thanks.<br></div>-- <br><div dir="ltr" class="gmail-m_-2900063390797903281gmail-m_7470341425089499929m_-6324454178383636738gmail_signature"><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div></div>Jeremy Plsek<br></div><div>UNH InterOperability Laboratory<br></div></div></div></div></div></div></div></div></div></div></div>
</blockquote></div><br clear="all"><br>-- <br><div dir="ltr" class="gmail-m_-2900063390797903281gmail_signature"><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div></div>Jeremy Plsek<br></div><div>UNH InterOperability Laboratory<br></div></div></div></div></div></div></div></div></div></div>

      reply index

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-19 17:26 Jeremy Plsek
2019-07-23 20:14 ` Jeremy Plsek [this message]

Reply instructions:

You may reply publically 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=CA+xUZB6nLxOw0vdhoNOFQ0aUjeUz0fuuPuChmqk9vwHVvzT69w@mail.gmail.com \
    --to=jplsek@iol.unh.edu \
    --cc=ci@dpdk.org \
    --cc=dpdklab@iol.unh.edu \
    /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

DPDK CI discussions

Archives are clonable:
	git clone --mirror http://inbox.dpdk.org/ci/0 ci/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 ci ci/ http://inbox.dpdk.org/ci \
		ci@dpdk.org
	public-inbox-index ci


Newsgroup available over NNTP:
	nntp://inbox.dpdk.org/inbox.dpdk.ci


AGPL code for this site: git clone https://public-inbox.org/ public-inbox