Difference between revisions of "Infrastructure Upgrade"

From Apache OpenOffice Wiki
Jump to: navigation, search
(Post Upgrade Tasks)
(update to 4.5.2)
Line 1: Line 1:
We are going to upgrade the development framework the main site runs on from SourceCast (SC 2.6) to CollabNet Enterprise Edition (CEE 3.5.1, 19.4).
+
We are going to upgrade the development framework the main site runs on from CollabNet Enterprise Edition (CEE) 3.5.1 to CEE 4.5.2.
  
 
=== Timeline ===
 
=== Timeline ===
Line 11: Line 11:
 
Please review the full version of the CollabNet Enterprise Edition versions 3.0.0, 3.1.0,
 
Please review the full version of the CollabNet Enterprise Edition versions 3.0.0, 3.1.0,
 
3.5.0, and 3.5.1 release notes prior to your upgrade: http://www.collab.net/rn/.
 
3.5.0, and 3.5.1 release notes prior to your upgrade: http://www.collab.net/rn/.
 
=== Staging Test ===
 
 
There are 2 weeks reserved for a test of CEE 3.5.1 on a staging server with our data set.
 
 
We are responsible to
 
* not change site branding after the branding freeze date.
 
* verify that branding appears as it should on the stage site.
 
* test all custom functionality, as well as any specialized build processes, or any other processes.
 
* investigate our favorite areas in addition to testing our host performs.
 
* ensure as far as localization is concerned that CEE 3.5.1 is the same as 2.6.x or better.
 
 
We will file one ticket per issue against the stage site for any questions
 
regarding access or functionality on the stage site. The component is "www" and subcomponent "openoffice.org upgrade".
 
 
[http://qa.openoffice.org/issues/buglist.cgi?Submit+query=Submit+query&component=www&subcomponent=openoffice.org+Upgrade&issue_status=UNCONFIRMED&issue_status=NEW&issue_status=STARTED&issue_status=REOPENED Query for Open Upgrade Issues]
 
 
The stage site is named [http://www.stage.openoffice.org/servlets/StartPage stage.openoffice.org].
 
 
You will be able to access the site with the same
 
username and password you use on our production site.
 
 
==== Preparations ====
 
 
It is a good idea to make a list of features and functionality that we are
 
interested in testing during our test weeks.
 
 
If you plan on testing features which
 
send email, such as mailing lists, CVS or SVN commits which trigger email, etc., please
 
note that all email addresses have been changed. Before testing these features, make sure
 
that you edit your user profile and change your email address back to one at which you
 
can receive email.
 
 
The stage site was created with data taken
 
from our running production site weeks ago. Any content added to your production site after it has been created will not be reflected on our stage site.
 
 
 
==== Branding ====
 
 
* How can we remove project headers?
 
 
Due to the changes in staticization project home pages look different. All project home pages (like http://api.stage.openoffice.org) start with a project header. In SC26 this was only the case for dynamic pages like http://udk.openoffice.org but not for static pages like http://api.openoffice.org).
 
http://api.stage.openoffice.org/index.html does not contain the header. But the project list (http://www.stage.openoffice.org/servlets/ProjectList?type=Projects&mode=TopLevel) points to the short form and more important every user will use the short form.
 
 
: Stefan: I need things to be clear here. Is the desired behaviour then for all new project index pages *NOT* to have the project header?  -louis
 
: BTW, more on header.  The velocity template *can* be changed. But looking at /index.html vs. /, you will see the Help and Project tools boxes also change: dynamic content is inserted in / not in /index.html.  That dynamic content includes:
 
: - discussion forums
 
: - My issues
 
: or, in short, those things depending on a user's permissions.
 
 
: One argument for forcing pages not to bring up this dynamic content could also be a robustness argument: to do so might be taxing to the system.
 
 
: * Update: I can file issues on OOo assigned to support to change the velocity template so that /index.html is rendered not "/", the default and current set up. The change may be visible in stage--or not; more info. is needed.  Because staticization will be operating differently--it's not really staticization any longer they tell me--this change will affect *all* project index.html pages. [[User:LouisSuarez|LouisSuarez]]
 
 
:: The quick answer is that http://de.stage.openoffice.org (without index.html) as well as http://api.stage.openoffice.org should look "right" - no header. We took the loss of dynamic content like "Discussion forums, My issues" and dynamic help content for all (staticized) SC26 home pages. I'm willing to accept this for CEE351 in favour of a clean home page with an easy to type URL.  Let's continue on the list. --[[User:St|stx12]] 20:16, 1 June 2006 (CEST)
 
 
: The project header has been removed by now. This also means that project leads have to keep useful URLs like [http://test.openoffice.org/servlets/ProjectEdit Edit], [http://test.openoffice.org/servlets/WatchProject Watch], [http://test.openoffice.org/servlets/ProjectMembershipRequest Request Role] in mind. --[[User:St|stx12]] 11:16, 12 June 2006 (CEST)
 
 
 
* Project specific navigation bar entries are lost (e.g. http://api.openoffice.org)
 
 
project_tools has been renamed but the point was that it replaced the default set. Christian is looking at that....
 
 
It seems that "navcol" was renamed to "leftcol", producing some of this behaviour
 
 
  the navcol vs leftcol is kind of another problem.. Fixed in the following way:
 
  * projects/pages hiding the left navbar-column need to adjust their css
 
    so that it hides #navcol instead of #leftcol
 
  * I modified the template so that it looks for project_tools.html instead of the new default
 
    of "NavColumn-ProjectToolsList.html" and modified inst.css so that the old project_tools.html
 
    can be used without modifications
 
    The new way would be to use definition lists (<dl>}} with the <dt> and <dd> tags
 
    where the individual links would be <ul>s), but the old way using the <div>s is now
 
    supported again
 
    Projects shouldn't need to modify it (but are encouraged to use the new format in future)
 
  [[User:Cloph|Cloph]]
 
 
* Suppression of Search and Help Box doesn't work (e.g. http://support.openoffice.org)
 
 
* We shouldn't forget to remove the link to release notes from the Help box
 
 
There are numerous things that have changed and been added in the Help box. What would you like to keep? Some things are useful, many not.
 
 
==== CVS ====
 
 
* TBT: problems with the case of file names (MH)
 
* r-commands (especially rdiff) still does not work in the supposed way. The workaround (specifying /shared/data/helm/cvs/repository as repository) works.
 
* cvs co CVSROOT works and the content looks ok
 
* cvs co -c is ok.
 
* keys are installed
 
* cvs commit messages are sent (cvs@test.stage->allcvs@test.stage)
 
 
===== cvsup =====
 
 
* cvsup: Server message: Unknown collection "cvs" has been [http://qa.openoffice.org/issues/show_bug.cgi?id=66241 fixed]
 
 
==== IZ ====
 
 
===== submitted =====
 
 
* [http://www.openoffice.org/issues/show_bug.cgi?id=66026 Issue 66026] when submitting issues, projects are now sorted ignoring case
 
[Will be fixed via changes in the inst-set before the upgrade --AS@CN]
 
 
* [http://qa.openoffice.org/issues/show_bug.cgi?id=44314 Issue 44314] IZ still lies about cc when not logged in [[User:Cloph|Cloph]]
 
 
===== solved =====
 
 
* [http://www.openoffice.org/issues/show_bug.cgi?id=66024 Issue 66024] missing "Add comment" privileges for some accounts
 
 
* FEATUREs have an usuable coloring (WHITE on LIGHT or DARK GREY) in issue lists cp. [http://qa.stage.openoffice.org/issues/buglist.cgi?issue_id=20315%2C20316%2C20317%2C20318 here]
 
  good: IZ doesn't use hardformatting anymore
 
  bad:  IZ uses a class that was previously used.
 
  Anyway, should be fixed now using the default color as defined in tigris.css
 
  if you don't like it, just post your wish :-) [[User:Cloph|Cloph]]
 
 
  Much better, thanks
 
 
===== misc =====
 
 
* Issue view has "BLACK on DARK GREY" coloring for some items, e.g. "depends on" in [http://www.stage.openoffice.org/issues/show_bug.cgi?id=64990 this issue]
 
 
* Lookup Users for issue assignement contains user groups ([http://qa.openoffice.org/issues/show_bug.cgi?id=66253]) and might hit performance ([http://qa.openoffice.org/issues/show_bug.cgi?id=66255]).
 
 
===== the good news =====
 
 
* default target milestone is "not determined" (instead of "---")
 
 
* input validation happens using java script (on client side), not after a round trip to the server
 
 
* can reassign fixed issues! They keep their resolution!
 
 
==== Mail ====
 
 
===== submitted =====
 
 
* [http://www.openoffice.org/issues/show_bug.cgi?id=66257 Issue 66257] Mailing list archives don't work
 
 
* [http://www.openoffice.org/issues/show_bug.cgi?id=66032 Issue 66032] Mailing lists: descriptions do not respect HTML formatting
 
 
 
<b>Bad</b>
 
 
The Web-interface still lacks badly
 
* No threaded view
 
* The "threads" view can still not be limited to some period of time or filtered
 
* The authors view still cannot be filtered
 
* Still there is no way to get the ID in the web-interface from the mail that is delivered, if you recieve a mail it is impossible to construct an URL to the message in the archive based on the data in the headers. You have to search  for the message online. - This is hard since the search doesn't allow a search for message-id. Still the fastes way is to browse the archives by date.
 
* The other was is not possible either. If you got the mail in the online-archive, you cannot send a mail zu ezmlm zu get the thread belonging to that message.
 
* Searching is still very incomfortable
 
** the results are not threaded
 
** the results cannot be ordered by date
 
** the results cannot be ordered by summary
 
** even worse, there is no default odering, the results are random.
 
 
* tried to post messages to dev@qa.stage from registered Sun email account and from gmx account (allowed to pass through) but both emails didn't get into archives (ja). This has been fixed.
 
 
<b>Good</b>
 
 
* The site-search facility now remembers the search modifiers (like +this +that or "this that") and it is actually possible to go to the "next" results page.
 
* Search for the german-lang users' archive is possible
 
[[User:Cloph|Cloph]]
 
 
<b>Tests</b>
 
* sublists work (cvs@test->allcvs@test)
 
* list of type discuss (news@test), bridging to newsgroups, ooposters work
 
 
 
==== Documents & files ====
 
 
* rejecting (disapproval) documents works (ja)
 
 
===== submitted =====
 
 
* [http://www.openoffice.org/issues/show_bug.cgi?id=66031 Issue 66031] Documents & files: descriptions do not respect HTML formatting
 
 
==== Annoucements ====
 
* No problem found so far (ja)
 
==== Webcontent====
 
 
* Staticization (now in place)
 
;: [http://www.mnot.net/cache_docs Caching Tutorial for Web Authors and Webmasters]
 
;: [http://www.w3.org/Protocols/rfc2616/rfc2616-sec13.html HTTP 1.1 RFC: Caching in HTTP]
 
 
==== L10N====
 
====Search ====
 
====User/role/permission/registration (ST)====
 
 
* Report "Count users by role and project" has been dropped
 
 
=====My Start Page=====
 
* Pending actions / Pending roles in project xxx (1) for project owner only and not for domain admin
 
* The total number of outstanding password tickets is no longer available (was on My Page of Domain Admin)
 
 
====Boundary Systems====
 
 
* EIS (BEI) - Login feature using staging CVS server works fine
 
* Feature / Interface mails (BEI) - submitting feature mail to test mailing list has Problems: HTML Mail not accepted, corrupt mail ends up in Archive. CWS Announce mails expected to have similar problems. [http://www.openoffice.org/issues/show_bug.cgi?id=66379 Issue 66379]
 
* iBIS (FMA)
 
TBT: Submission with target milestone<br>
 
TBT: ooo version and target administration (MH)
 
* IZ New Issue Feed (Pavel)
 
An adapted  version is available. The cron job has to be stopped and restart once this new version is in place for the upgraded production site.
 
* mailstats (ST)
 
* broken links (ST)
 
Link checking works fine now that it's HTTP 1.1 aware.
 
 
====Configuration Parameters====
 
* Allow issue deletion? off
 
* Project path separator string: ">" or "&amp;nbsp;&amp;gt;&amp;nbsp;" (&nbsp;&gt;&nbsp;)
 
* Enable content repository templating? on
 
* Add "Project Issue Tracking - Comment" for role "Registered User" [http://qa.openoffice.org/issues/show_bug.cgi?id=66024 issue 66024]
 
* Revoke "Project - Suggest" for "Registered User"
 
* Add "Project - View", resource "All applicable resources" to "Anonymous Guest".
 
* SVN and PT have to be enabled.
 
==== Miscellaneous ====
 
* changed layout
 
 
On some systems (notably: Sunray running Solaris), lot of pages look are pretty unreadable, since they have a too small font. Most problematic are pages like http://qa.stage.openoffice.org/issue_handling/pre_submission.html, compared with http://qa.openoffice.org/issue_handling/pre_submission.html.
 
Note that that's really browser-( or display-)dependent, since I do not have those problems on e.g. a Windows machine.
 
 
Responsible for this problem is the following style from tigris.css:
 
  #bodycol, #bodycol table td, #bodycol table th {
 
    font-size: 95%;
 
    line-height:135%;
 
  }
 
Seems that with some displays, this becomes unusable. Can we remove this font-size item? Effectively, it affects the whole page, so it is useless, anyway.
 
 
* I filed http://www.openoffice.org/issues/show_bug.cgi?id=66478, asking that the fonts on STAGE be made to look like those on production.
 
[[LouisSuarez]]
 
  
 
=== Production Upgrade ===
 
=== Production Upgrade ===
  
The Production Upgrade is planned for Tuesday 2006-06-20 starting 17:00 UTC. THe overall process will take bout 48 hours.
+
The Production Upgrade is planned for Monday 2007-04-30 starting 17:00 UTC. The overall process will take about 48 hours.
  
 
==== Migratiobn ====
 
==== Migratiobn ====
Line 250: Line 21:
  
 
==== Configuration and Testing ====
 
==== Configuration and Testing ====
Wednesday night (UTC) the upgraded site running CEE 3.5.1 will be back using the new IP address 204.16.104.2.
+
Tuesday night (UTC) the upgraded site running CEE 4.5.2 will be back.
 
A [http://www.openoffice.org/servlets/BroadcastMessage Broadcast message] will inform users that the upgrade is not yet finished.
 
A [http://www.openoffice.org/servlets/BroadcastMessage Broadcast message] will inform users that the upgrade is not yet finished.
 
==== Indexing ====
 
As soon as the configuration and testing is finished DNS records will be changed to point to the new site.
 
 
The production site may be sluggish for the first half day during which time various indexes are being rebuilt. This is a list of the plug-ins which need to be re-Indexed, and the end user impact until the Full Index is completed:
 
 
{|
 
! Plug-in !! What will happen till the full Index is not completed?
 
|-
 
| eyebrowse/message || the 'Mailing list archives will not be searchable'.
 
|-
 
| issuezilla/attachment || the 'Attached to' column in the search results page will display a 'null' string.
 
|-
 
| nidaba/document || the path in the search result will show absolute path.
 
|-
 
| wedge/forum || clicking on the forum will take you to the page which lists all the forums instead of the forum page.
 
|}
 
  
  
Line 278: Line 32:
 
* Enable Issue Feed
 
* Enable Issue Feed
  
Furthermore some issues have been postponed and will be handled when the production site has been upgraded to 3.5.1.
+
- cleanup cvs repository
 
+
- apply domain-wide allowed-posters list
[http://qa.openoffice.org/issues/showdependencytree.cgi?id=64392 CEE 3.5.1 Post Upgrade Tasks]
+
- remove password tickets
 
+
* Query: when was it decided that we would be using DomainHome.html.html and not www/www/index.html?  There is a disparity now between the two files, of course, and www.openoffice.org/ pulls up DomainHome.html.html but not www/www/index.html.
+

Revision as of 19:31, 21 April 2007

We are going to upgrade the development framework the main site runs on from CollabNet Enterprise Edition (CEE) 3.5.1 to CEE 4.5.2.

Timeline

  • Branding Freeze on Production Site: 4/14/06
  • Tests Stage Site: 5/30/06 – 6/16/06
  • Date Range for Production Deployment: 6/20/06 – 6/23/06

Release Notes

Please review the full version of the CollabNet Enterprise Edition versions 3.0.0, 3.1.0, 3.5.0, and 3.5.1 release notes prior to your upgrade: http://www.collab.net/rn/.

Production Upgrade

The Production Upgrade is planned for Monday 2007-04-30 starting 17:00 UTC. The overall process will take about 48 hours.

Migratiobn

The site will be unavailable for more than 24 hours. During this time a placeholder page will be installed.

Configuration and Testing

Tuesday night (UTC) the upgraded site running CEE 4.5.2 will be back. A Broadcast message will inform users that the upgrade is not yet finished.


Post Upgrade Tasks

  • Test cvsup
  • Enable cvsupd
  • Run cvsup (crontabs anoncvs, so-cvsup)
  • Enable Issue Feed

- cleanup cvs repository - apply domain-wide allowed-posters list - remove password tickets

Personal tools