Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Patrick Ohly <patrick.ohly@intel.com>
To: Alexander Kanavin <alexander.kanavin@linux.intel.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 1/3] rpm: add support for remote package feeds via PACKAGE_FEED_URIS variable
Date: Wed, 15 Mar 2017 13:44:21 +0100	[thread overview]
Message-ID: <1489581861.6396.97.camel@intel.com> (raw)
In-Reply-To: <9ca28013-06c6-c668-2e42-1d13a75d4331@linux.intel.com>

On Wed, 2017-03-15 at 13:19 +0200, Alexander Kanavin wrote:
> On 03/15/2017 01:13 PM, Burton, Ross wrote:
> >
> >     +        cls.repo_server.port = 8080
> >
> >
> > What if parallel selftests are running at once?  Can this service be
> > started before the image is created, so the right port can be written
> > into the image?
> 
> I don't know. I only followed what Humberto wrote in the original patch; 
> we need to ask him. I'm also not entirely certain that hardcoding the ip 
> address will always work, and did not get an answer to that.
> 
> Another, more hackish option is to monkey patch the ephemeral port 
> before running dnf into the repo config on the image.

Or perhaps use ssh with port forwarding? Then the host-side port can be
picked randomly, while on the target side it can be fixed.

I was about to suggest qemu slirp networking because that also does port
mapping, but I think ssh port forwarding is better.

-- 
Best Regards, Patrick Ohly

The content of this message is my personal opinion only and although
I am an employee of Intel, the statements I make here in no way
represent Intel's position on the issue, nor am I authorized to speak
on behalf of Intel on this matter.





  reply	other threads:[~2017-03-15 12:44 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-14 17:27 [PATCH 1/3] rpm: add support for remote package feeds via PACKAGE_FEED_URIS variable Alexander Kanavin
2017-03-14 17:27 ` [PATCH 2/3] lib/oe/package_manager: import rpm signing key to rpmdb Alexander Kanavin
2017-03-14 17:27 ` [PATCH 3/3] selftest/signing.py: verify that images can be created from signed packages Alexander Kanavin
2017-03-15 11:13 ` [PATCH 1/3] rpm: add support for remote package feeds via PACKAGE_FEED_URIS variable Burton, Ross
2017-03-15 11:19   ` Alexander Kanavin
2017-03-15 12:44     ` Patrick Ohly [this message]
2017-03-15 15:38     ` Ibarra Lopez, Humberto
2017-03-15 16:08       ` Richard Purdie
2017-03-15 17:10         ` Ibarra Lopez, Humberto

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=1489581861.6396.97.camel@intel.com \
    --to=patrick.ohly@intel.com \
    --cc=alexander.kanavin@linux.intel.com \
    --cc=openembedded-core@lists.openembedded.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