On 03/10/11 08:48 AM, [email protected] wrote:
Hi Folks,

Is there a pointer to any background reading material on this feature?

Here's the first paragraph of the design document, it's the closest thing to an overview we have.

Linked images, and zones in particular, must keep certain packages in sync with the global zone in order to be functional. The global zone will constrain packages within the non-global zones and configure special publishers in the non-global zone (NGZ). These publishers (henceforth called system publishers) are special because the non-global zone cannot make certain kinds of modifications to them. Among the forbidden operations for the non-global zone on the system publishers are deleting, disabling, removing or replacing origins provided by the system repository, and any other operations which might prevent the solver from meeting the constraints imposed by the constraint package. The global zone must provide the means for the non-global zone to configure itself with system publishers by providing information like origins. The global zone also has to provide a connection to the system publishers' repositories which is available even in a scratch zone. This connection, broadly, is called the system repository.



If you're interested in a more detailed (slightly out of date) design document, you can find it here:
http://cr.opensolaris.org/~bpytlik/sysrepo/sysrepo_design_doc.txt

Brock

Thanks,

--shri


On 3/8/2011 9:52 PM, Tim Foster wrote:
Hi there,

If anyone's interested in following along with the system publisher work
that Brock and myself are doing, we've got a hg repository at:

ssh://[email protected]/hg/pkg/sysrepo-gate

Thanks Danek for setting that up.

This is a work-in-progress project-gate, and as such has not been
code-reviewed or tested in depth.  It may not work, may damage your
machine and may insult your neighbours (enough disclaimers?)

The sysrepo work in general is captured by the following bugs:
https://defect.opensolaris.org/bz/buglist.cgi?&status_whiteboard=sysrepo

At the time of writing, there's just the basics of the server-side code
in the gate.  Having built the gate, here's how to try it:

% pkg install pkg/sysrepo
% svcadm enable system/pkg/sysrepo

This should give you an apache instance running on port 15000.

That instance is automatically configured to provide services as a http
proxy, proxying local requests to all configured and enabled publishers
on your system (it can proxy http requests across to https://
repositories using the keys and certificates configured on your system)

It also provides direct http access to file:// repositories, so for
example, we can do:

timf@linn[204] pkg publisher pkg5-nightly

            Publisher: pkg5-nightly
Alias: Origin URI: file:///home/timf/projects/ips/sysrepo-proxy-pkg.hg/packages/i386/repo/
              SSL Key: None
             SSL Cert: None
          Client UUID: 00184128-3f08-11e0-a1b1-00e04c00052e
Catalog Updated: March 9, 2011 03:31:12 AM Enabled: Yes

timf@linn[205] pkg image-create -p http://localhost:15000/pkg5-nightly /tmp/b
timf@linn[206] pkg -R /tmp/b info -r sysrepo
          Name: package/sysrepo
       Summary: IPS System Repository
Description: A service used for providing publisher proxies to zones (bad
                description for now, it'll do)
      Category: System/Packaging
         State: Not installed
     Publisher: pkg5-nightly
       Version: 0.5.11
 Build Release: 5.11
        Branch: 0.161
Packaging Date: March  9, 2011 03:30:46 AM           Size: 45.35 kB
FMRI: pkg://pkg5-nightly/package/[email protected],5.11-0.161:20110309T033046Z


For normal http:// access to file:// repositories, you're still better off
using the standard pkg.depotd server - performance is a little slower at
the moment using apache, and it doesn't provide all of the features that
the pkg.depotd does (notably, search is unavailable)

We don't have a notification alias for pushes to the
sysrepo-gate, but let me know if you're interested in getting
notification and I'll see what I can do.

    cheers,
            tim


_______________________________________________
pkg-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
_______________________________________________
pkg-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/pkg-discuss

_______________________________________________
pkg-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/pkg-discuss

Reply via email to