ServerTeam
Differences between revisions 1 and 60 (spanning 59 versions)
|
Size: 10401
Comment: imported from the old wiki
|
← Revision 60 as of 2022-02-10 14:05:02 ⇥
Size: 6900
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 1: | Line 1: |
| = ServerTeam = | = Ubuntu Server Team = |
| Line 3: | Line 3: |
| == Ubuntu Linux Server Team == | <<Include(ServerTeam/Header)>> |
| Line 5: | Line 5: |
| 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. | ~+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 7: | Line 7: |
| We specifically focus on three key areas: | |
| Line 8: | Line 9: |
| === Goals === | 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 10: | Line 13: |
| * 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. |
== Communication == |
| Line 16: | Line 15: |
| === Issues === Ubuntu is a desktop system common perception, how to change? |
If you want to contact the ServerTeam use the following resources: |
| Line 20: | Line 17: |
| * 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 .... |
=== Mailing List === |
| Line 25: | Line 19: |
| Join our mailing list at https://lists.ubuntu.com/mailman/listinfo/ubuntu-server. | |
| Line 26: | Line 21: |
| === People === | You can read an archive of messages at https://lists.ubuntu.com/archives/ubuntu-server/. |
| Line 28: | Line 23: |
| === IRC === | |
| Line 29: | Line 25: |
| * SivanGreen (documentation, planning, testing) * JeffBailey * Ghe Rivero |
The server team utilizes IRC to offer support for server-related questions. The team sits on freenode in the #ubuntu-server channel. |
| Line 33: | Line 27: |
| From JeffBailey Tue Feb 8 23:25:43 +0000 2005 From: Jeff Bailey Date: Tue, 08 Feb 2005 23:25:43 +0000 Subject: Thoughts I'd like to note down of things that I really want Message-ID: <20050208232543+0000@https://www.ubuntulinux.org> |
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 39: | Line 29: |
| Things I would love to see in the server distro: | == Getting Involved == |
| Line 41: | Line 31: |
| * Some sort of /etc/iptables.d/ where packages could drop pieces discribing what they need opened on the firewall, and have a default deny all firewall installed as part of base. | There are different areas where you can help the Ubuntu Server Team. Here are a few ideas: |
| Line 43: | Line 33: |
| * mailman come with the right pieces to integrate with exim4 and postfix. (And sendmail, but I know I'm the only one who loves sendmail here.. *sigh*) | === Help on Mailing List & IRC === |
| Line 45: | Line 35: |
| * config lint checking at every server 'restart'. apache, bind9, and many others come with a pre-flight check. This should be run as part of a /etc/init.d/FOO restart, to make sure that the server can safely restart, and leave the server alone if the config file is not suitable. | 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 47: | Line 37: |
| * Remove inetd by default. It's too easy to have something silently add itself there. | === Test, Test, Test === |
| Line 49: | Line 39: |
| 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 50: | Line 41: |
| === Improve Documentation === | |
| Line 51: | Line 43: |
| From NiallSheridan Wed Feb 9 13:54:59 +0000 2005 From: Niall Sheridan Date: Wed, 09 Feb 2005 13:54:59 +0000 Subject: groupware Message-ID: <20050209135459+0000@www.ubuntulinux.org> |
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 57: | Line 45: |
| How about a groupware server? Perhaps based on opengroupware, as it is web-based, but client plugins for Outlook and Evolution exist? | === Verify SRUs === |
| Line 59: | Line 47: |
| From MarkRzepa Wed Feb 9 15:09:51 +0000 2005 From: Mark Rzepa Date: Wed, 09 Feb 2005 15:09:51 +0000 Subject: System monitoring and self healing Message-ID: <20050209150951+0000@https://www.ubuntulinux.org> |
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 65: | Line 49: |
| It would be nice to see a server that monitors all it's services (apache, bind etc...) and maintains a "last known good" state, it if detects any problems with one of it's services, it should try and fix the problem by doing things like restart the service or it will automatically rollback any changes that have been made since it's "last know good" state. This could include restoring configuration files or downgrading packages to a previous version. | The full process for doing so is here: |
| Line 67: | Line 51: |
| From JeffBailey Thu Feb 10 20:55:27 +0000 2005 From: Jeff Bailey Date: Thu, 10 Feb 2005 20:55:27 +0000 Subject: Audit logging for Apt Message-ID: <20050210205527+0000@https://www.ubuntulinux.org> |
[[QATeam/PerformingSRUVerification]] |
| Line 73: | Line 53: |
| Apt should syslog what it did (before and after) | Here is the [[http://people.canonical.com/~chucks/SRUTracker/sru-tracker-bugs.html#verified_bugs|list of server bugs needing verification]]. |
| Line 75: | Line 55: |
| From MarkRzepa Fri Feb 11 00:26:41 +0000 2005 From: Mark Rzepa Date: Fri, 11 Feb 2005 00:26:41 +0000 Subject: RE: Audit logging for Apt Message-ID: <20050211002641+0000@https://www.ubuntulinux.org> |
=== Triage Bugs === |
| Line 81: | Line 57: |
| Generating meaningful reports based on the logged data would be an asset. e.g. Monthly Package Update Report 6 packaged updated 4 due to security fixes 1 due to bug fix 1 due to new version release |
The goal of triage is to move bugs that are in a NEW status to a CONFIRMED or INVALID status. |
| Line 88: | Line 59: |
| From GheRivero Thu Mar 3 21:58:35 +0000 2005 From: Ghe Rivero Date: Thu, 03 Mar 2005 21:58:35 +0000 Subject: Central Managment Message-ID: <20050303215835+0000@https://www.ubuntulinux.org> |
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. |
| Line 94: | Line 68: |
| There should be a central control panel to see the state of the differents servers (Uptime, disk space, pending updates, services running), mainly in a Web interface to be available everywhere. The comunication between servers and the central can be done using XMLRPC over ssh. (Some thing like the RedHat Network but much better) | === Improve Packages === |
| Line 96: | Line 70: |
| From GheRivero Thu Mar 3 22:29:09 +0000 2005 From: Ghe Rivero Date: Thu, 03 Mar 2005 22:29:09 +0000 Subject: SELinux Message-ID: <20050303222909+0000@https://www.ubuntulinux.org> |
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. |
| Line 102: | Line 72: |
| Default kernels and policy for the most used servers (web, mail) should be provided and active bu default | This is a excellent way to gain experience to become a [[MOTU]]. |
| Line 104: | Line 74: |
| From AndrewMitchell Fri Mar 4 11:32:20 +0000 2005 From: Andrew Mitchell Date: Fri, 04 Mar 2005 11:32:20 +0000 Subject: SELinux tools Message-ID: <20050304113220+0000@https://www.ubuntulinux.org> |
== Ubuntu Server Bug Triage == |
| Line 110: | Line 76: |
| Kernels are enabled with the needed options (except networking hooks, it seems), and a policy is in selinux-policy-default that needs fixed up before hoary. A policy just for common daemons would be like Fedora's targetted policy. | '''Goal:''' To successfully review every bug filed against Ubuntu Server related packages |
| Line 112: | Line 78: |
| From GheRivero Sun Mar 6 23:43:12 +0000 2005 From: Ghe Rivero Date: Sun, 06 Mar 2005 23:43:12 +0000 Subject: Central Managment Message-ID: <20050306234312+0000@https://www.ubuntulinux.org> |
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. |
| Line 118: | Line 80: |
| Something is been doing at the moment. http://savannah.nongnu.org/projects/ulnc/. It uses XMLRPC over ssh and python to access the servers, get info of them, manage package system. More improvement and a GUI is necesary. | 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. |
| Line 120: | Line 82: |
| From MatthewGibbons Mon Apr 11 01:23:21 +0100 2005 From: Matthew Gibbons Date: Mon, 11 Apr 2005 01:23:21 +0100 Subject: apt-get install ubuntu-sbs Message-ID: <20050411012321+0100@https://www.ubuntulinux.org> |
{{{#!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]] |
| Line 126: | Line 90: |
| I currently maintain a number of Microsoft Windows Small Business Servers, and to be honest, they are more of less a joy to administer. Out of the box you get integrated DHCP/DNS, shared files, shared printing, Exchange (with POP3 connector), MSSQL, firewall, intranet, and backup. I would like to see the same approach taken with ubuntu-sbs (this being a meta-package with dependencies to include all the necessary services). I have done some work along these lines already, but lack direction on Exchange replacement (Hula?). | For Details about the process have a look at The [[https://github.com/canonical/ubuntu-maintainers-handbook/blob/main/BugTriage.md|Ubuntu Maintainers handbook]]. |
| Line 128: | Line 92: |
| From AndrewTimberlake-Newell Fri Apr 15 17:51:50 +0100 2005 From: Andrew Timberlake-Newell Date: Fri, 15 Apr 2005 17:51:50 +0100 Subject: Paying attention to Mom and Pop Message-ID: <20050415175150+0100@https://www.ubuntulinux.org> |
=== Additional Resources === |
| Line 134: | Line 94: |
| Mine is just a bit similar to Matthew's. I'm currently planning a system for a small business with a globe-trotting sales force and needs for a server to synchronize and backup files via VPN...maybe with some later use as email/database. They're a touch phobic of non-MS systems, and I've been searching high and low for a distro targeted for migration from SBS...one which at least clearly bills itself as doing the job and lists all the noteworthy features. Maybe even a highlighted set of instructions for migration from SBS to distro X. | Helpful Guides and Definitions: |
| Line 136: | Line 96: |
| From JimCheetham Mon Apr 18 00:40:29 +0100 2005 From: Jim Cheetham Date: Mon, 18 Apr 2005 00:40:29 +0100 Subject: UbuntuDownUnder? Message-ID: <20050418004029+0100@https://www.ubuntulinux.org> |
* [[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]] |
| Line 142: | Line 101: |
| Anyone (besides me :-) planning on attending the upcoming UbuntuDownUnder? I'd like to meet a few people interested in server issues ... | == Ubuntu Server Packaging == |
| Line 144: | Line 103: |
| From shermann Mon Apr 18 23:15:27 +0100 2005 From: shermann Date: Mon, 18 Apr 2005 23:15:27 +0100 Subject: Ubuntu running as Server Message-ID: <20050418231527+0100@www.ubuntulinux.org> |
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. |
| Line 150: | Line 105: |
| I replaced now my gentoo 2005.0 with ubuntu hoary 5.04 there r a couple of pitfalls and the debootstrap installation installs a nice workstation system after `base-config new` call <- has to be changed. After all, a nice work...StephanHermann |
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 153: | Line 107: |
| From JoelWagler Tue May 3 05:20:26 +0100 2005 From: Joel Wagler Date: Tue, 03 May 2005 05:20:26 +0100 Subject: small buisness server. Message-ID: <20050503052026+0100@https://www.ubuntulinux.org> I'd like to see the sbs server Like Matthew Gibsons. I'd like to see samba/ldap/groupware/backup/fileserver/print server/etc all properly setup and integrated in a server. I think Open Groupware might be a good choice as a groupware server. A groupware server ideally should * Not depend on Java (open source issues) * Integrate well with evolution, outlook, thunderbird, and other opensource clients * Have a web interface. * Be an "exchange" replacement. * Integrate well with other products. Use open standards, choice of DB's, mail servers ideally. In general you should be able to put an ubuntu server in and easily replace a microsoft server. Windows clients/ and Ubuntu clients should be well supported (Bonus would be Mac OS as well) From JoelWagler Fri May 13 08:51:20 +0100 2005 From: Joel Wagler Date: Fri, 13 May 2005 08:51:20 +0100 Subject: SME server Message-ID: <20050513085120+0100@https://www.ubuntulinux.org> Hello, all I think a good idea of what an ubuntu server edition would be SME server (http://www.contribs.org). It's a linux, rpm based :( distro that integrates a lot of server stuff into a common interface. It has things like ldap, samba, ftp, ssh, vpn, dns, email, website, fileserver (quotas), backup, etc and all configurations can be accessed from a nice web interface. X windows is not even installed. From PieterduPreez Sat May 28 17:18:54 +0100 2005 From: Pieter du Preez Date: Sat, 28 May 2005 17:18:54 +0100 Subject: SME Server Message-ID: <20050528171854+0100@https://www.ubuntulinux.org> I cannot agree more. I am a Linux newbie and I have a home server, Apapche, LDAP, Samba, Mail, Proxy etc etc and it is on-line and available 100%. I run about 10 websites on it, have multiple users etc. SME server is a good approach for general users and given the uncertainty and lack of progress in the development of newer versions may just be ready for a "takeover" by Canonical |
---- [[CategoryServerTeam]]<<BR>> CategoryUbuntuTeams |
Ubuntu Server Team
#ubuntu-server on Libera Chat IRC |
||||||||
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:
- Providing a robust and stable infrastructure for scale-out computing deployments.
- Supporting the latest scale-out computing workloads and architectures.
- 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:
Choose a bug from the New,Unconfirmed bug list and subscribe to it.
- Work with the user to identify the issue using the INCOMPLETE status.
- 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.
- You can unsubscribe from the bug as your role as a bug triager is finished.
- 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.
ServerTeam (last edited 2022-02-10 14:05:02 by paelzer)