ServerTeam

Differences between revisions 6 and 60 (spanning 54 versions)
⇤ ← Revision 6 as of 2005-08-06 16:54:42 →
Size: 4622
Editor: henrik
Comment: merged in UDU spec
← Revision 60 as of 2022-02-10 14:05:02 → ⇥
Size: 6900
Editor: paelzer
Comment:
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
== Ubuntu Linux Server Team == = Ubuntu Server Team =
Line 3: Line 3:
The server team, under the able stewardship of Thom "I Bleed For Servers" May, aims to ensure that Ubuntu installs cleanly on data-center grade servers from all major manufacturers. While linux support for server hardware is now generally excellent, the servers themselves often present unusual challenges for the installer. Team Leader: Thom May. <<Include(ServerTeam/Header)>>
Line 5: Line 5:
~+The [[http://launchpad.net/people/ubuntu-server|Ubuntu Server team]] works to enable and promote the use of Ubuntu Server, the number one cloud OS.+~
Line 6: Line 7:
=== Goals === We specifically focus on three key areas:
Line 8: Line 9:
 * Make Ubuntu first class general purpose server platform, with special emphasis on ease of use for the admin.
 * Diversify even more range of hardware platforms Ubuntu could use as a server system on.
 * Make sure Ubuntu servers scale nicely with workload.
 * Make Ubuntu an attractive server platform for orgs and coprporations.
 * Bring ubuntu to the state which allows it to seemingly assimilate in clustering environments.		  1. Providing a robust and stable infrastructure for scale-out computing deployments.
 2. Supporting the latest scale-out computing workloads and architectures.
 3. Providing the right tools for orchestrating services within a scale-out computing environment.
Line 14: Line 13:
=== Issues ===
 
Ubuntu is a desktop system common perception, how to change?		 == Communication ==
Line 18: Line 15:
 * Education, Documentation: Ubuntu as a router, web/nfd/Samba/print/mail/http/content/telephony server.
 * Tools: make server bleeding edge available to skilled admins, make everybody a skilled admin in the future with easier tools and the right interfaces.
 * Marketing : Talk about how Ubuntu is already integrating nicely in hetrogeneous networks. (i.e. win/novell/linux/sun ...)
 * Special editions : Ubuntu Internet Server, Ubuntu Telephony Platform, Ubuntu LAN Server , Ubuntu DevHub Server ....		 If you want to contact the ServerTeam use the following resources:
Line 23: Line 17:
=== People === === Mailing List ===
Line 25: Line 19:
 * SivanGreen (documentation, planning, testing)
 * JeffBailey
 * Ghe Rivero		 Join our mailing list at https://lists.ubuntu.com/mailman/listinfo/ubuntu-server.
Line 29: Line 21:
== Other Ideas == You can read an archive of messages at https://lists.ubuntu.com/archives/ubuntu-server/.
Line 31: Line 23:
=== Ubuntu DevelopersHub Server Edition === === IRC ===
Line 33: Line 25:
 * Specially tailored Ubuntu Operating System for scattered and localized development groups. (docs,code,design)
 * Out of the box ready with:
         * Groupware Software (phpgroupware, [http://freshmeat.net/projects/worldpilot/ worldpilot] may already include some of the mentioned features)
         * Inner organization IM messaging solution.
         * Bug reporting and tracking solution.
         * Development ready (gcc, chroots, eclipse, wing etc..)
         * Intranet web, application and wiki server.
         * Remote administration ready. (swat, webmin etc..)
See discussion: ["ServerTeam/talk"]		 The server team utilizes IRC to offer support for server-related questions. The team sits on freenode in the #ubuntu-server channel.
Line 43: Line 27:
-------
-------
= UDU Spec =
== Status ==		 The [[https://wiki.ubuntu.com/UbuntuBots|ubottu]] IRC bot makes it easy to share an extensive set of [[http://ubottu.com/factoids.cgi|factoids]] to others in an IRC channel. E.g. typing {{{!ask | noobie}}} will cause ubottu to tell noobie that folks should just go ahead and ask their questions. Ubottu can also conveniently show the channel information on bugs and packages. See [[https://wiki.ubuntu.com/UbuntuBots|ubottu]] for more details.
Line 48: Line 29:
 * Created: [[Date(2005-04-26T07:43:26Z)]] by ThomMay
 * Priority: MediumPriority
 * People: ThomMayLead, AdamConradSecond
 * Contributors: ThomMay
 * Interested: OliverGrawert
 * Status: EditedSpecification, BreezyGoal, DistroSpecification, MattZimmermanQueue[[BR]]
 * Branch:
 * Malone Bug:
 * Packages:
 * Depends:
 * Dependents:
 [[FullSearch(ServerTeam)]]
 * UduSessions: 1, 4, 8, etc 		== Getting Involved ==
Line 62: Line 31:
== Introduction == There are different areas where you can help the Ubuntu Server Team. Here are a few ideas:
Line 64: Line 33:
This specification describes goals for the Server team in breezy and onwards.. === Help on Mailing List & IRC ===
Line 66: Line 35:
== Rationale == You can lend a hand with people's questions and problems on the above mailing list and the IRC channel. Ask and answer questions, provide suggestions, and provide input in our periodic calls for input.
Line 68: Line 37:
Ubuntu has fantastic mindshare as a Desktop distribution, but it's great on the server too. We need to promote and enhance Ubuntu so that professionals are keen to use it. === Test, Test, Test ===
Line 70: Line 39:
== Scope and Use Cases == If you have server-type hardware or can spin up VMs and containers, you can make sure that Ubuntu is supported and works well on it. You can also test software and features worked on by the Ubuntu Server Team.
Line 72: Line 41:
== Implementation Plan == === Improve Documentation ===
Line 74: Line 43:
 * Work with BenjaminMakoHill to improve the website to include more mention of Ubuntu in server areas, as well as solicit the community (and possibly clients) to submit white papers and case studies detailing existing uses of Ubuntu in small and large server environments. You can head to the [[https://help.ubuntu.com/community/|community documentation]] to check that server related pages are up to date or help to get the Ubuntu Server Team wiki pages into shape. You can also [[https://ubuntu.com/server/docs|help with the Ubuntu Server Guide]], the official Server documentation.
Line 76: Line 45:
 * Improve our support for "default" server-related packages, including:
  * Promote `mysql-dfsg4.1` to the default and supported version of MySQL for breezy.
  * If we have time, we will completely punt `libmysqlclient10` and `libmysqlclient12` from the distribution, and standardize on one client library for all MySQL access.
  * Get `php5` into supported and drop `php4` to universe.
  * Promote all `php5` extensions to supported, except for `php5-imap`, which we will not build at all, due to the many issues `libc-client` (which it depends on) has.
  * Server-side Java support is currently non-existent, however this should be covered by the JavaRoadmap.
  * We need better Win32 support, however this was covered in another BoF, see WindowsInteroperability.		 === Verify SRUs ===
Line 84: Line 47:
 * Investigate the best way to install `openssh-server` into the default server install. Probably a d-i posthook. Whenever we fix a bug in past stable releases, we need somebody who is not the developer making the fix to verify that the package fixes and doesn't cause any obvious regressions. It is vital that we have people test these updates before they are sent to all users.
Line 86: Line 49:
=== Data Preservation and Migration === The full process for doing so is here:
Line 88: Line 51:
 * `php4` -> `php5` is a painless migration in 99% of cases, and we can document the very small number of corner cases for users.
 * MySQL 4.0 to 4.1 is also a trivial upgrade.		 [[QATeam/PerformingSRUVerification]]
Line 91: Line 53:
=== Packages Affected === Here is the [[http://people.canonical.com/~chucks/SRUTracker/sru-tracker-bugs.html#verified_bugs|list of server bugs needing verification]].
Line 93: Line 55:
 * `php4`
 * `php4-universe`
 * `php5`
 * `mysql-dfsg`
 * `mysql-dfsg4.1`
 * see the packages covered in the referenced BoFs		 === Triage Bugs ===

The goal of triage is to move bugs that are in a NEW status to a CONFIRMED or INVALID status.

To get started:
 1. Choose a bug from [[https://bugs.launchpad.net/ubuntu/+bugs?field.searchtext=&orderby=-importance&field.status%3Alist=NEW&field.importance%3Alist=UNDECIDED&assignee_option=any&field.assignee=&field.bug_reporter=&field.bug_supervisor=ubuntu-server&field.bug_commenter=&field.subscriber=&field.component-empty-marker=1&field.status_upstream-empty-marker=1&field.omit_dupes.used=&field.omit_dupes=on&field.has_patch.used=&field.has_cve.used=&field.tag=&field.tags_combinator=ANY&field.has_no_package.used=&search=Search|the New,Unconfirmed bug list]] and subscribe to it.
 1. Work with the user to identify the issue using the INCOMPLETE status.
 1. Once the bug is reproducible and the process to reproduce it is clearly documented in the bug thread set the status to CONFIRMED. If it turns out that there isn't any bug set the status to INVALID.
 1. You can unsubscribe from the bug as your role as a bug triager is finished.
 1. Read more bug triaging resources:
    * [[BugSquad/KnowledgeBase]]
You should also subscribe to the [[https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs|ubuntu-server-bugs mailing list]] where all the bugs are sent. You can also view the [[https://bugs.launchpad.net/~ubuntu-server/|list of bugs related to the ServerTeam]] and help triaging them.

=== Improve Packages ===

You can have a look at the [[https://bugs.launchpad.net/~ubuntu-server/+packagebugs|list of packages]] looked after by the Ubuntu Server Team to see if some needs packaging work.

This is a excellent way to gain experience to become a [[MOTU]].

== Ubuntu Server Bug Triage ==

'''Goal:''' To successfully review every bug filed against Ubuntu Server related packages

A review involves analyzing a bug to determine if the bug is valid and if sufficient information was provided. If the bug is both valid and provided with sufficient information, the bug is marked as triaged and will be worked to closure by a member of the server team. Otherwise, the bug will be responded to and marked as 'Incomplete' for more details, 'Invalid' for not a real bug, or 'Won't Fix'. In certain (rare) cases bugs might stay in new/confirmed which reflects we need to look into it again more deeply to triage in a better way.

This is a list of the various queues of interest to the server team. They are a good place to go if you are looking for a good "what to do next" bug.

{{{#!wiki comment
contact davidpbritton if you want these bit.ly vanity links modified
}}}
 * [[http://bit.ly/ubuntu-server-next|Top 20 Bugs ("server-next")]]
 * [[http://bit.ly/ubuntu-server-bitesize|Bite-sized Bugs]]
 * [[http://bit.ly/ubuntu-server-recent|Recently modified Bugs]]
 * [[https://bugs.launchpad.net/~ubuntu-server/+subscribedbugs|Full Backlog]]

For Details about the process have a look at The [[https://github.com/canonical/ubuntu-maintainers-handbook/blob/main/BugTriage.md|Ubuntu Maintainers handbook]].

=== Additional Resources ===

Helpful Guides and Definitions:

 * [[Bugs/Importance|Definitions for bug importance levels]]
 * [[Bugs/Status|Definitions for bug status settings]]
 * [[DebuggingServer|Server specific triage responses]]
 * [[Bugs/Responses|Additional predefined response templates]]

== Ubuntu Server Packaging ==

We are transitioning to a [[UbuntuDevelopment/Merging/GitWorkflow|git-based workflow]] for handling package changes. This also allows us to use Launchpad Merge Proposals and request Reviews before publishing a new package version.

For details about this please have a look at [[https://github.com/canonical/ubuntu-maintainers-handbook/blob/main/MergeProposal.md|Merge Proposals]] and [[https://github.com/canonical/ubuntu-maintainers-handbook/blob/main/PackageMerging.md|Package Merges]] in the Ubuntu maintainers handbook.
Line 101: Line 108:
[[CategoryServerTeam]]<<BR>>

Ubuntu Server Team

The Ubuntu Server team works to enable and promote the use of Ubuntu Server, the number one cloud OS.

We specifically focus on three key areas:

  1. Providing a robust and stable infrastructure for scale-out computing deployments.
  2. Supporting the latest scale-out computing workloads and architectures.
  3. Providing the right tools for orchestrating services within a scale-out computing environment.

Communication

If you want to contact the ServerTeam use the following resources:

Mailing List

Join our mailing list at https://lists.ubuntu.com/mailman/listinfo/ubuntu-server.

You can read an archive of messages at https://lists.ubuntu.com/archives/ubuntu-server/.

IRC

The server team utilizes IRC to offer support for server-related questions. The team sits on freenode in the #ubuntu-server channel.

The ubottu IRC bot makes it easy to share an extensive set of factoids to others in an IRC channel. E.g. typing !ask | noobie will cause ubottu to tell noobie that folks should just go ahead and ask their questions. Ubottu can also conveniently show the channel information on bugs and packages. See ubottu for more details.

Getting Involved

There are different areas where you can help the Ubuntu Server Team. Here are a few ideas:

Help on Mailing List & IRC

You can lend a hand with people's questions and problems on the above mailing list and the IRC channel. Ask and answer questions, provide suggestions, and provide input in our periodic calls for input.

Test, Test, Test

If you have server-type hardware or can spin up VMs and containers, you can make sure that Ubuntu is supported and works well on it. You can also test software and features worked on by the Ubuntu Server Team.

Improve Documentation

You can head to the community documentation to check that server related pages are up to date or help to get the Ubuntu Server Team wiki pages into shape. You can also help with the Ubuntu Server Guide, the official Server documentation.

Verify SRUs

Whenever we fix a bug in past stable releases, we need somebody who is not the developer making the fix to verify that the package fixes and doesn't cause any obvious regressions. It is vital that we have people test these updates before they are sent to all users.

The full process for doing so is here:

QATeam/PerformingSRUVerification

Here is the list of server bugs needing verification.

Triage Bugs

The goal of triage is to move bugs that are in a NEW status to a CONFIRMED or INVALID status.

To get started:

  1. Choose a bug from the New,Unconfirmed bug list and subscribe to it.

  2. Work with the user to identify the issue using the INCOMPLETE status.
  3. Once the bug is reproducible and the process to reproduce it is clearly documented in the bug thread set the status to CONFIRMED. If it turns out that there isn't any bug set the status to INVALID.
  4. You can unsubscribe from the bug as your role as a bug triager is finished.
  5. Read more bug triaging resources:

You should also subscribe to the ubuntu-server-bugs mailing list where all the bugs are sent. You can also view the list of bugs related to the ServerTeam and help triaging them.

Improve Packages

You can have a look at the list of packages looked after by the Ubuntu Server Team to see if some needs packaging work.

This is a excellent way to gain experience to become a MOTU.

Ubuntu Server Bug Triage

Goal: To successfully review every bug filed against Ubuntu Server related packages

A review involves analyzing a bug to determine if the bug is valid and if sufficient information was provided. If the bug is both valid and provided with sufficient information, the bug is marked as triaged and will be worked to closure by a member of the server team. Otherwise, the bug will be responded to and marked as 'Incomplete' for more details, 'Invalid' for not a real bug, or 'Won't Fix'. In certain (rare) cases bugs might stay in new/confirmed which reflects we need to look into it again more deeply to triage in a better way.

This is a list of the various queues of interest to the server team. They are a good place to go if you are looking for a good "what to do next" bug.

For Details about the process have a look at The Ubuntu Maintainers handbook.

Additional Resources

Helpful Guides and Definitions:

Ubuntu Server Packaging

We are transitioning to a git-based workflow for handling package changes. This also allows us to use Launchpad Merge Proposals and request Reviews before publishing a new package version.

For details about this please have a look at Merge Proposals and Package Merges in the Ubuntu maintainers handbook.

CategoryServerTeam
CategoryUbuntuTeams

ServerTeam (last edited 2022-02-10 14:05:02 by paelzer)