Michal Pryc wrote:
Shawn Walker wrote:
Greetings,
With the putback for the following issues in revision 1504:
9969 client support for multiple origins desired
...the client now supports multiple origins for publisher repositories.
Shawn,
I have started work to support multiple origins per publisher for the
IPS GUI and I would like to clarify few things.
On the following wireframe you can see that publisher can be
removed/added or the search priority can be changed, which works pretty
well with the underlying API:
http://xdesign.sfbay.sun.com/projects/solaris/subprojects/package_mngt/UI_specs/ui_spec_phase4/html-mockup/42_publishers_dialog_1.htm
...
Clicking on the Modify publisher will open new dialog:
http://xdesign.sfbay.sun.com/projects/solaris/subprojects/package_mngt/UI_specs/ui_spec_phase4/html-mockup/43_modify_publisher1.htm
Based on the current API probably we will need to redesign a little bit
this dialog:
- change the repository to origin strings
- user to be able to add origin from this dialog
- user to be able to remove origin from this dialog
- remove modify button for the repository
- add ssl fields for the publisher and also mirrors for the publisher in
this dialog
- remove Active column.
Yes, that seems right. Although I'd still leave something somewhere
that says "Repository Information" and then have a section for "origins"
and a section for "mirrors".
You only need one set of SSL Cert/Key fields for the publisher as a
whole for now, see below.
Clicking on the Modify Repository (origin) is designed to gave us the
following dialog:
http://xdesign.sfbay.sun.com/projects/solaris/subprojects/package_mngt/UI_specs/ui_spec_phase4/html-mockup/44_modify_repository1.htm
And again based on the current API probably the whole dialog should be
gone and some parts should be in the previous dialog such as mirrors/SSL
data.
...
My understanding was that each origin will contain information about
it's mirrors and SSL cert/keys, but from the current implementation I
can see that those informations are for the publisher rather then for
the origin. Am I wrong? Or maybe the work on your side is ongoing and it
will be like that but currently it's not.
There continues to be debate about whether the user can adequately deal
with the configuration complexity of having SSL and other transport
configuration on a per-mirror or per-origin basis.
Because of that, and other higher priority work, nothing has been done
yet for this, so the information essentially remains at the publisher
level. I'd recommend doing what the cli does in this area for now.
Cheers,
--
Shawn Walker
_______________________________________________
pkg-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
