[Piuparts-devel] pull: feature/restrict-master-access (was: Re: RFC: preview/restrict-master-access)
Holger Levsen
holger at layer-acht.org
Wed Mar 13 02:10:03 UTC 2013
Hi,
On Sonntag, 10. März 2013, Andreas Beckmann wrote:
> Andreas Beckmann (10):
> p-m: rename to piuparts-master-backend.py
> p-m: add new wrapper script piuparts-master
> p-s/p-m: pass section via stdin instead of command line
> p-s/p-m: move chdir and stderr logging to master wrapper
> p-s: simplify ssh command
> p-s: stop using master-directory
> p-s: stop using (master's) log-file
> p.conf: use simple master-command
> p-s.deb: restrict slave's ssh key to only allow running
> piuparts-master
> p-s: support empty master command
>
> On 2013-03-09 20:12, Holger Levsen wrote:
> > On Samstag, 9. März 2013, Andreas Beckmann wrote:
> >> it needs more testing (including setting up an instance from the .deb
> >> packages)
> >> but I'd really like to see this in 0.50
> >
> > then no. I really want to upload 0.50 now.
>
> with some minor fixes this has been running in my instance for a few
> hours (and previous versions over the last week) and it also worked
> nicely in a .deb installation in virtualbox, so I happily declare this
> feature as ready :-)
sorry, but this rather seems like a well tested candidate for 0.51 to me.
> and now I've actually run out of features that are ready for 0.50 :-)
> some documentation updates may still come
My plan is too upload piuparts by sunday or at least monday.
> and that's one more reason to change the master interface *now* and not
> later after people started deploying more instances, because I don't
> want to add maintainer script code that modifies known_hosts beyond
> initial creation
I don't expect many people setting up master+slave instances now, and I also
don't mind releasing 0.51 in 2 weeks if thats useful then.
cheers,
Holger
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.alioth.debian.org/pipermail/piuparts-devel/attachments/20130312/48188fa4/attachment.html>
More information about the Piuparts-devel
mailing list