Thanks to visit codestin.com
Credit goes to github.com

Skip to content
This repository was archived by the owner on Feb 24, 2020. It is now read-only.

Conversation

@borqosky
Copy link
Contributor

@borqosky borqosky commented Mar 8, 2016

Setting ptp template network and IP address in systemd unit during
test. Updated also docs with example.

@borqosky borqosky changed the title functional tests: Add new test with systemd-proxyd [WIP]functional tests: Add new test with systemd-proxyd Mar 8, 2016

`rkt` also supports [socket-proxyd service][systemd-socket-proxyd]. So, like in
socket activation systemd will listen on a port on behalf of a container, and start the container when receiving a connection. It could be useful to provide socket activation for enviroment that natively doesn't support it. One of the
example is the `KVM` flavour in `stage1`.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

flavor

@borqosky borqosky force-pushed the borkos/systemd_proxyd_test branch 2 times, most recently from bd5b40c to a97d768 Compare March 11, 2016 09:24
@borqosky borqosky changed the title [WIP]functional tests: Add new test with systemd-proxyd functional tests: Add new test with systemd-proxyd Mar 11, 2016
@borqosky borqosky force-pushed the borkos/systemd_proxyd_test branch from a97d768 to a48874b Compare March 23, 2016 13:10
@borqosky
Copy link
Contributor Author

review request...

@jellonek
Copy link
Contributor

LFTM


`rkt` also supports [socket-proxyd service][systemd-socket-proxyd]. So, like in
socket activation systemd will listen on a port on behalf of a container, and start the container when receiving a connection. It could be useful to provide socket activation for enviroment that natively doesn't support it. One of the
example is the `KVM` flavor in `stage1`.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

s/enviroment/environment/

@borqosky borqosky force-pushed the borkos/systemd_proxyd_test branch from a48874b to d9448f3 Compare March 30, 2016 13:27
}
defer os.Remove(socketTarget)

// path to systemd-socket-proxyd on Ubuntu (different path on Fedora).
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It seems to be available as well on Fedora.

$ rpm -qf /lib/systemd/systemd-socket-proxyd
systemd-222-14.fc23.x86_64

@alban
Copy link
Member

alban commented Mar 30, 2016

I didn't know systemd-socket-proxyd. It looks cool :)

@joshix , can you review the changes in Documentation/using-rkt-with-systemd.md? Thanks:)

@alban alban added this to the v1.4.0 milestone Mar 30, 2016
@borqosky borqosky force-pushed the borkos/systemd_proxyd_test branch 2 times, most recently from 3e2ea82 to 2fae589 Compare March 31, 2016 08:19
@borqosky
Copy link
Contributor Author

borqosky commented Apr 5, 2016

@joshix review request.


### Bidirectionally proxy local sockets to another (possibly remote) socket.

`rkt` also supports [socket-proxyd service][systemd-socket-proxyd]. So, like in
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

rkt also supports the [socket-proxyd service][systemd-socket-proxyd]. Much like socker activation, with socket-proxyd systemd provides a listener on a given port on behalf of a container, and starts the container when a connection is received. Socket-proxy listening can be useful in environments that lack native support for socket activation. The LKVM stage1 flavor is an example of such an environment.

@borqosky borqosky force-pushed the borkos/systemd_proxyd_test branch from 2fae589 to 46f6cbe Compare April 7, 2016 10:40
@borqosky
Copy link
Contributor Author

borqosky commented Apr 8, 2016

@joshix review request.


### Bidirectionally proxy local sockets to another (possibly remote) socket.

`rkt` also supports the [socket-proxyd service][systemd-socket-proxyd]. Much like socker activation, with socket-proxyd systemd provides a listener on a given port on behalf of a container, and starts the container when a connection is received. Socket-proxy listening can be useful in environments that lack native support for socket activation. The LKVM` `stage1 flavor is an example of such an environment.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

s/socker/socket/

remove the backticks after "LKVM" and before "stage1"

@joshix
Copy link
Contributor

joshix commented Apr 8, 2016

@woodbor I have the two little nits noted inline. After those are fixed, the docs part LGTM. Thanks!

@borqosky borqosky force-pushed the borkos/systemd_proxyd_test branch from 46f6cbe to f009ada Compare April 11, 2016 06:45
@borqosky
Copy link
Contributor Author

done

@@ -0,0 +1,201 @@
// Copyright 2015 The rkt Authors
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

2016

@alban
Copy link
Member

alban commented Apr 11, 2016

I also have two little nits noted inline. After that, LGTM.

Setting ptp template network and IP address in systemd unit during
test. Updated also docs with example.
@borqosky borqosky force-pushed the borkos/systemd_proxyd_test branch from f009ada to 3d610d8 Compare April 12, 2016 06:39
@borqosky
Copy link
Contributor Author

done

@alban
Copy link
Member

alban commented Apr 12, 2016

Thanks.
The TestFetch failure is not related to the patch.

@alban alban merged commit 7aa709d into rkt:master Apr 12, 2016
@borqosky borqosky deleted the borkos/systemd_proxyd_test branch April 12, 2016 09:04
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants