Skip to main content
Jump to: navigation, search

Difference between revisions of "Equinox p2 M1"

Line 1: Line 1:
Milestone 1, as the name implies, is our first step towards a [[Equinox Provisioning | new provisioning system for Eclipse]].  We have hit most of the major items on the [[Equinox Provisioning Plan#M1.2C August 2nd | M1 plan ]]except for roll-back support.  The meta-goal of M1 was to ''self-provision''.  That is, use the new provisioning support to install and manage the Eclipse environment that we ourselves use to write the provisioning system.
+
Milestone 1, as the name implies, is our first step towards a [[Equinox Provisioning | new provisioning system for Eclipse]].  We have hit most of the major items on the [[Equinox Provisioning Plan#M1.2C August 2nd | M1 plan ]] except for roll-back support.  Most importantly however is that the meta-goal of ''self-provisioning'' is at hand.  That is, the new provisioning support allows people to install and manage the Eclipse environment they use to develop the provisioning system itself!  AKA "[http://en.wikipedia.org/wiki/Eat_one's_own_dog_food eating your own dog food]".
  
'''More information here'''
+
So, what should you expect from Milestone 1. 
* set expectations
+
* First, don't get your hopes up too high.  Most of what we have accomplished is buried well under the covers.  We have be laying a new foundation for a flexible and extensible provisioning platform. 
* what scenarios, what can you do with M1, what can you NOT do?
+
* With M1 you are able to install and uninstall individual bundles as well as groups of bundles and whole Eclipse product installs (e.g., we supply a packaging of the Eclipse SDK).
* context for the UI (admin UI, not representative of the intended end user workflows, ...)
+
* You can start from scratch and install a complete Eclipse SDK and then add to it or remove from it using the agent. Note that since the supplied SDK is just a packaging of 3.3, it does not include the new provisioning support.  Of course, you can use the provisioning agent to add provisioning support to
* where to enter bugs/make comments/...
+
the SDK :-)  
 +
* The Admin UI is just that, a UI intended for administrators, not end-users. The end-user UI will start to take shape during M2.
  
For more information see:
+
== New and Noteworthy ==
 +
 
 +
In a sense it is all new... In any event, here are a few highlights of the new infrastructure:
 +
* There is a little RCP application you can use to create and manage your [[Equinox Provisioning Concepts | profiles]].  The same capabilities are also exposed through a text console.
 +
* The [[Equinox Provisioning Concepts | agent]] allows you to manage the profile you are running as well as other profiles.
 +
* The new support is a complete replacement for Update Manager.  Notice that in the fully functional Admin UI application there are no Update Manager bundles.  Sigh: turns out there is one but that was a mistake.  It is not needed/used (see [https://bugs.eclipse.org/bugs/show_bug.cgi?id=198766 Bug 198766)
 +
* There are simple, lightweight APIs for manipulating and managing [[Equinox Provisioning Concepts | profiles]].
 +
 
 +
== Getting started ==
 +
Sound interesting?  For those who want to learn more, try it or get involved, we've put together a series of guides that will help you along the path.  These documents will continue to fill out and evolve with the provisioning support.
 +
 
 +
== Getting Started and User Guides ==
 
* [[Equinox Provisioning Getting Started#Getting Started with M1 | Getting started with M1]]
 
* [[Equinox Provisioning Getting Started#Getting Started with M1 | Getting started with M1]]
* [[Equinox Provisioning RCP Agent Users Guide]]
+
* [[Equinox Provisioning Admin UI Users Guide]]
 +
* [[Equinox Provisioning Console Users Guide]]
 +
* [[Equinox Provisioning Getting Started for Developers]]
 
* [[Equinox Provisioning Bugs n Blunders]]
 
* [[Equinox Provisioning Bugs n Blunders]]
 +
 +
Speaking of bugs and blunders, it is very early days for the provisioning support and the road will be bumpy in spots.  Your ideas, insights, bug reports and contributions are what will make this effort a success.  Please direct comments to the [mailto:equinox-dev@eclipse.org equinox-dev@eclipse.org] mailing list and bug reports to the [https://bugs.eclipse.org/bugs/enter_bug.cgi?assigned_to=equinox.incubator-inbox%40eclipse.org&blocked=&bug_file_loc=http%3A%2F%2F&bug_severity=normal&bug_status=NEW&comment=&component=Incubator&contenttypeentry=&contenttypemethod=autodetect&contenttypeselection=text%2Fplain&data=&dependson=&description=&flag_type-1=X&flag_type-2=X&flag_type-4=X&flag_type-6=X&form_name=enter_bug&keywords=&maketemplate=Remember%20values%20as%20bookmarkable%20template&op_sys=Windows%20XP&priority=P3&product=Equinox&qa_contact=&rep_platform=PC&short_desc=%5Bprov%5D%20&version=unspecified Eclipse/Equinox/Incubator bugzilla bucket] (use [prov] in the summary line).

Revision as of 23:09, 2 August 2007

Milestone 1, as the name implies, is our first step towards a new provisioning system for Eclipse. We have hit most of the major items on the M1 plan except for roll-back support. Most importantly however is that the meta-goal of self-provisioning is at hand. That is, the new provisioning support allows people to install and manage the Eclipse environment they use to develop the provisioning system itself! AKA "eating your own dog food".

So, what should you expect from Milestone 1.

  • First, don't get your hopes up too high. Most of what we have accomplished is buried well under the covers. We have be laying a new foundation for a flexible and extensible provisioning platform.
  • With M1 you are able to install and uninstall individual bundles as well as groups of bundles and whole Eclipse product installs (e.g., we supply a packaging of the Eclipse SDK).
  • You can start from scratch and install a complete Eclipse SDK and then add to it or remove from it using the agent. Note that since the supplied SDK is just a packaging of 3.3, it does not include the new provisioning support. Of course, you can use the provisioning agent to add provisioning support to

the SDK :-)

  • The Admin UI is just that, a UI intended for administrators, not end-users. The end-user UI will start to take shape during M2.

New and Noteworthy

In a sense it is all new... In any event, here are a few highlights of the new infrastructure:

  • There is a little RCP application you can use to create and manage your profiles. The same capabilities are also exposed through a text console.
  • The agent allows you to manage the profile you are running as well as other profiles.
  • The new support is a complete replacement for Update Manager. Notice that in the fully functional Admin UI application there are no Update Manager bundles. Sigh: turns out there is one but that was a mistake. It is not needed/used (see [https://bugs.eclipse.org/bugs/show_bug.cgi?id=198766 Bug 198766)
  • There are simple, lightweight APIs for manipulating and managing profiles.

Getting started

Sound interesting? For those who want to learn more, try it or get involved, we've put together a series of guides that will help you along the path. These documents will continue to fill out and evolve with the provisioning support.

Getting Started and User Guides

Speaking of bugs and blunders, it is very early days for the provisioning support and the road will be bumpy in spots. Your ideas, insights, bug reports and contributions are what will make this effort a success. Please direct comments to the equinox-dev@eclipse.org mailing list and bug reports to the Eclipse/Equinox/Incubator bugzilla bucket (use [prov] in the summary line).

Back to the top