Re: [equinox-dev] [prov] ECF discovery of artifact and metadata repos
Jeff McAffer wrote: There currently is no support for known repositories. At least not that I know of. :-) I created enhancement request https://bugs.eclipse.org/bugs/show_bug.cgi?id=218534 for this. ___ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev
Re: [equinox-dev] [prov] ECF discovery of artifact and metadata repos
Scott Lewis wrote: but it would be desirable to have a UI with less detail, that only shows meta-data and artifact repos rather than all services...and doesn't show all the details of the service properties as the ECF discovery view does. Hi, do we really need a separate UI or could we achieve the same by adding pre-configured viewer filters to the UI? Btw CQ2038 doesn't show the properties in the tree but in the generic properties view instead. Though it requires EMF. Cheers Markus ___ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev
Re: [equinox-dev] [prov] ECF discovery of artifact and metadata repos
Unless it has changed since I messed with it, that FileServerApplication was some hacky attempt at putting an HTTP server on front of some repos. It may be an ok starting point but i'd not put too much weight on it. Perhaps we should just have one thing that exposes a set of repos through HTTP and is optionally discoverable? Does that make sense? As for hte UI, p2 users, admin or otherwise, likely have no interest in discovery. They just want to nkow what repos are available to be added to their system. So, for example, when someone goes to add a repo, they might have an option of choosing from known repos. That way the list of available repos can be supplied through discovery, static list, dynamic downloaed list, hard coded, ... Jeff Scott Lewis wrote: Hi Markus, Markus Alexander Kuppe wrote: Scott Lewis wrote: but it would be desirable to have a UI with less detail, that only shows meta-data and artifact repos rather than all services...and doesn't show all the details of the service properties as the ECF discovery view does. Hi, do we really need a separate UI or could we achieve the same by adding pre-configured viewer filters to the UI? I agree with you...having a pre-configured viewer filter would be the way to go for the ECF service discovery view. We can just add this ourselves (ECF team). But for the provisioning admin ui, I think any UI integration needs the opinion of whoever is responsible for the Admin UI...i.e. I'm not sure the Admin UI really needs/wants a separate view to discover meta-data and artifact repos...although OTOH, if it did use the ECF discovery view (s) it would make it very simple/easy/quick to add. Scott ___ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev ___ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev
Re: [equinox-dev] [prov] ECF discovery of artifact and metadata repos
Hi Jeff, Jeff McAffer wrote: Unless it has changed since I messed with it, that FileServerApplication was some hacky attempt at putting an HTTP server on front of some repos. It may be an ok starting point but i'd not put too much weight on it. Perhaps we should just have one thing that exposes a set of repos through HTTP and is optionally discoverable? Does that make sense? Sure. Sounds fine. Adding optional discoverability will be easy. As for hte UI, p2 users, admin or otherwise, likely have no interest in discovery. They just want to nkow what repos are available to be added to their system. So, for example, when someone goes to add a repo, they might have an option of choosing from known repos. That way the list of available repos can be supplied through discovery, static list, dynamic downloaed list, hard coded, ... I agree. The ECF service discovery view will not make an appearance...rather the discovered artifact and meta-data repos will just appear in a 'known repos' UI. So I suppose the 'known repos' UI has to added...I guess as another button (and associated shell/dialog) in the add repo dialog? Unless it's already there and I haven't seen it. Scott ___ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev
Re: [equinox-dev] [prov] ECF discovery of artifact and metadata repos
There currently is no support for known repositories. At least not that I know of. :-) At various times we talked about priming the repo list etc in installed configurations but that would likely have been with loaded repos. Is discovery expensive? For example, if someone clicked an Add... button would it make sense to do the discovery then or is this something you essentially do in the background periodically or allow the user to drive a look for repositories button? As you know the schedule for 1.0 is very tight so Susan and others will have to comment on the feasibility of getting this in. Having said that, we can always have another route that is less well integrated and comes from the incubator at the beginning and then gets integrated over time. Jeff Scott Lewis wrote: Hi Jeff, Jeff McAffer wrote: Unless it has changed since I messed with it, that FileServerApplication was some hacky attempt at putting an HTTP server on front of some repos. It may be an ok starting point but i'd not put too much weight on it. Perhaps we should just have one thing that exposes a set of repos through HTTP and is optionally discoverable? Does that make sense? Sure. Sounds fine. Adding optional discoverability will be easy. As for hte UI, p2 users, admin or otherwise, likely have no interest in discovery. They just want to nkow what repos are available to be added to their system. So, for example, when someone goes to add a repo, they might have an option of choosing from known repos. That way the list of available repos can be supplied through discovery, static list, dynamic downloaed list, hard coded, ... I agree. The ECF service discovery view will not make an appearance...rather the discovered artifact and meta-data repos will just appear in a 'known repos' UI. So I suppose the 'known repos' UI has to added...I guess as another button (and associated shell/dialog) in the add repo dialog? Unless it's already there and I haven't seen it. Scott ___ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev ___ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev
Re: [equinox-dev] [prov] ECF discovery of artifact and metadata repos
Hi Jeff, Jeff McAffer wrote: There currently is no support for known repositories. At least not that I know of. :-) At various times we talked about priming the repo list etc in installed configurations but that would likely have been with loaded repos. Is discovery expensive? For example, if someone clicked an Add... button would it make sense to do the discovery then or is this something you essentially do in the background periodically or allow the user to drive a look for repositories button? The discovery providers do background discovery. They expose access to discovered services via an IDiscoveryService (OSGi service defined by ECF discovery API). So a client can just get the IDiscoveryService(s) via service registry and use it ask for any discovered services of the appropriate type. As you know the schedule for 1.0 is very tight so Susan and others will have to comment on the feasibility of getting this in. Having said that, we can always have another route that is less well integrated and comes from the incubator at the beginning and then gets integrated over time. ok. Scott Jeff Scott Lewis wrote: Hi Jeff, Jeff McAffer wrote: Unless it has changed since I messed with it, that FileServerApplication was some hacky attempt at putting an HTTP server on front of some repos. It may be an ok starting point but i'd not put too much weight on it. Perhaps we should just have one thing that exposes a set of repos through HTTP and is optionally discoverable? Does that make sense? Sure. Sounds fine. Adding optional discoverability will be easy. As for hte UI, p2 users, admin or otherwise, likely have no interest in discovery. They just want to nkow what repos are available to be added to their system. So, for example, when someone goes to add a repo, they might have an option of choosing from known repos. That way the list of available repos can be supplied through discovery, static list, dynamic downloaed list, hard coded, ... I agree. The ECF service discovery view will not make an appearance...rather the discovered artifact and meta-data repos will just appear in a 'known repos' UI. So I suppose the 'known repos' UI has to added...I guess as another button (and associated shell/dialog) in the add repo dialog? Unless it's already there and I haven't seen it. Scott ___ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev ___ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev ___ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev
Re: [equinox-dev] [prov] ECF discovery of artifact and metadata repos
Initially, I'm thinking of setting up a discoverable http server to expose p2 meta-data and artifact repos. I noticed that there is an Equinox application: FileServerApplication (in org.eclipse.equinox.p2.tools plugin). Would it be OK to add discovery to this app (via patches)? Or should I create a new separate DiscoverableFileServerApplication? Also, would there be any interest in adding a discovery client to the ProvAdminUI? We have a general service discovery view in ECF http://wiki.eclipse.org/Update_Site_Discovery http://wiki.eclipse.org/Discovery_of_Remote_Services but it would be desirable to have a UI with less detail, that only shows meta-data and artifact repos rather than all services...and doesn't show all the details of the service properties as the ECF discovery view does. Scott John Arthorne wrote: Hi Scott, repository locations are simply represented as a URL. Since both metadata and artifact repositories are pluggable via extension point, any valid URL could potentially represent a repository. Currently the one way to find out if a give URL actually represents a repository is by calling loadRepository(URL, ...) on either IMetadataRepositoryManager or IArtifactRepositoryManager. Hope that helps get you started... John *Scott Lewis [EMAIL PROTECTED]* Sent by: [EMAIL PROTECTED] 02/05/2008 12:08 PM Please respond to Equinox development mailing list equinox-dev@eclipse.org To Equinox development mailing list equinox-dev@eclipse.org cc Subject [equinox-dev] [prov] ECF discovery of artifact and metadata repos In prep for EclipseCon, the ECF team would like to create a demo that discovers p2 artifact and metadata repos. ECF has a discovery API [1], now implemented with both zeroconf/bonjour and SLP providers [2]. We've recently done an example that discovers update sites on lan [3]. So, my main question is: for discovering artifact and metadata repos, what is the necessary meta-meta-data? (data about location/access to repos). Is it simply an URL, or is there more to it? Pointers into p2 code desired...as I need to do that anyway. Thanks, Scott [1] http://wiki.eclipse.org/ECF_API_Docs#Discovery_API [2] http://www.lemmster.de/blog/index.php/2008/02/03/168/ [3] http://wiki.eclipse.org/Update_Site_Discovery ___ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev ___ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev ___ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev
Re: [equinox-dev] [prov] ECF discovery of artifact and metadata repos
Hi Scott, repository locations are simply represented as a URL. Since both metadata and artifact repositories are pluggable via extension point, any valid URL could potentially represent a repository. Currently the one way to find out if a give URL actually represents a repository is by calling loadRepository(URL, ...) on either IMetadataRepositoryManager or IArtifactRepositoryManager. Hope that helps get you started... John Scott Lewis [EMAIL PROTECTED] Sent by: [EMAIL PROTECTED] 02/05/2008 12:08 PM Please respond to Equinox development mailing list equinox-dev@eclipse.org To Equinox development mailing list equinox-dev@eclipse.org cc Subject [equinox-dev] [prov] ECF discovery of artifact and metadata repos In prep for EclipseCon, the ECF team would like to create a demo that discovers p2 artifact and metadata repos. ECF has a discovery API [1], now implemented with both zeroconf/bonjour and SLP providers [2]. We've recently done an example that discovers update sites on lan [3]. So, my main question is: for discovering artifact and metadata repos, what is the necessary meta-meta-data? (data about location/access to repos). Is it simply an URL, or is there more to it? Pointers into p2 code desired...as I need to do that anyway. Thanks, Scott [1] http://wiki.eclipse.org/ECF_API_Docs#Discovery_API [2] http://www.lemmster.de/blog/index.php/2008/02/03/168/ [3] http://wiki.eclipse.org/Update_Site_Discovery ___ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev ___ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev
