=== Varka_ is now known as Varka === tonyy is now known as tonyyarusso === tonyy is now known as tonyyarusso === asac_ is now known as asac === j_ack_ is now known as j_ack === SWAT__ is now known as SWAT === greeneggsnospam is now known as jsgotangco === \sh_away is now known as \sh === dholbach_ is now known as dholbach === \sh is now known as \sh_away === Hobbsee_ is now known as Hobbsee === doko_ is now known as doko === _czessi is now known as Czessi [15:04] is this working? im not sure somebody say something.... [15:04] yes it is [15:05] ok thanks [15:26] @schedule montreal [15:26] Schedule for America/Montreal: 12 Dec 18:00: Kubuntu Developers | 13 Dec 09:00: Desktop Team Development | 18 Dec 10:00: Server Team meeting | 20 Dec 09:00: Desktop Team Development [15:42] @schedule halifax [15:42] Schedule for America/Halifax: 12 Dec 19:00: Kubuntu Developers | 13 Dec 10:00: Desktop Team Development | 18 Dec 11:00: Server Team meeting | 20 Dec 10:00: Desktop Team Development [15:43] server team meeting here in 15 minutes.... [15:52] can i sit in? [15:52] im not part of it [15:52] michalski: open to all [15:53] ok thanks [15:54] https://wiki.ubuntu.com/ServerTeam/Meeting [15:59] Hey everyone [16:00] #startmeeting [16:00] Meeting started at 16:00. The chair is dendrobates. [16:00] Commands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE] [16:00] hello [16:00] https://wiki.ubuntu.com/ServerTeam/Meeting [16:00] Hi, guys. [16:00] hi [16:00] hi === duluu is now known as doluu [16:02] [TOPIC] Review ACTION points from previous meeting. [16:02] New Topic: Review ACTION points from previous meeting. [16:03] action 1: mathiaz will update the Developer section of the Roadmap with the specs for hardy [16:03] mathiaz is on holiday. [16:04] I haven't checked to see if this was done. Does anyone know offhand? [16:04] Sorry, no. [16:04] I just checked as well. [16:05] action 2: nijaba will check the minimun requirement for an installation of ubuntu-server [16:06] that was done and the installation and introduction sections of the serverguide are updated. [16:06] Cool. What was the result? [16:06] cool [16:06] 128M memory and a 1G hd space... on x86, amd64, and Sparc [16:06] * nijaba is late... sorry [16:06] action 3: sommer will add an item about writing a wiki page to install a minimal GUI on the server [16:07] there's an item on the road map, but I don't think the actual article has been started yet. [16:07] do you really need 1GB of HD space? [16:07] dendrobates: I wouldn't install with less... need space for log files and such [16:08] ok. [16:08] dendrobates: it all depends on what you want to do... [16:08] I guess technically ~600M would work [16:08] but you probably won't be happy for long [16:08] syslog remotely.... [16:08] I would have guessed half of that. [16:09] I supose it doesn't hurt to go 1GB. === \sh_away is now known as \sh [16:09] Minimal requirements are not about being happy. They're about minimal requirements. [16:09] unless we're trying to attract the largest segment - smaller and smaller servers [16:09] ala jeos (which is different, but some similar motivations) [16:10] soren: it depends how it is presented. I have seen recommended miniumum system requirements. [16:10] If the installation requires 300MB to actually be installable, those are the minimal requirements. If people want to have space for data, they should add that to the 300 MB. [16:10] there are so many different kinds of servers [16:10] What are we trying to accomplish with this information? [16:11] dendrobates: Give a reasonable sense, to newcomer, of what a server install might require [16:11] dendrobates: I think that's silly. We're trying to establish minimal requirements, not "minimal requirements leaving space for 600 MB of data". [16:11] not tell people how little space we can tweak it to fit in with [16:11] so we could talk about firewall servers, web servers, mail servers etc [16:12] nealmcb: agreed [16:12] I suggest linking to the existing text and letting people propose updates [16:12] The only number that objectively makes sense is the size of a standard install. We have no way of knowing how much data a user will want to have on his server. [16:13] cant we have minimum and suggested size? [16:13] soren: agreed [16:13] However if var fills up on the second reboot, that is not a usable system. [16:13] Will everyone be happy if we don't say "The minimal requiremenst are X MB", but instead "A default installation of UBuntu Server only takes up X MB"? [16:13] soren: does it really matter whether we say 600M or 1G? Even flash rives are bigger than this nowdays! [16:13] maybe we should include info on that [16:13] That's as unambiguous as it gets. [16:13] or recommendations [16:14] soren: ok for your rewording [16:14] soren: +1 on soren phrasing [16:15] works for me, currenlty the specs are listed in a table [16:15] I guess change "Hard Drive Space" to "Hard Drive Space Used"? [16:15] If that's what the data actually is, then yes. [16:15] If it's recommended sizes, I call bogus on them. [16:15] nowdays every administrator nows that they must have something bigger than recommended [16:16] perhaps with a "*This does not include any extra packages, logs, or data that accumulate" [16:16] If the install takes 500 MB and we say "1GB is required", we're somehow implying that a usual amount of data to have on a system is 500 MB. That's nonsense. [16:16] what if we made several tables saying how much we recommend and how much you need on the different types of installs [16:16] ftp, http ect [16:17] I'll do a base install of x86 version with all tasks and will send the space used to sommer, is that ok? [16:17] maybe minimal requirement is 300MB, and recommended one is 1g is better? [16:17] . o O (how many angels fit on the head of a pin) [16:17] nijaba: works for me. [16:17] here's a link to where the current specs are: https://help.ubuntu.com/7.10/server/C/preparing-to-install.html [16:19] What about ram.. I suggested increasing the minimum to 256M... [16:19] nijaba: Why? [16:19] nijaba: I disagree. [16:19] nijaba: ya, I listed that incorrectly... the updated docs have 256M [16:19] another hassle is the installer pulling in updates - https://bugs.edge.launchpad.net/ubuntu/+source/ubiquity/+bug/112516 [16:19] Launchpad bug 112516 in ubiquity "ubuquity using over 2 GB during apt upgrade due to unused packages" [Undecided,New] [16:20] so it is unpredictable [16:20] nealmcb: does that apply to a new install? [16:20] I think that it is important that we can run in 128 [16:20] soren: because I don't want people to think that anyone would have something that would swap all the time... [16:20] sommer: yes [16:20] gotcha [16:21] we need to be realistic though, the oldest computers that work today have about 2gbs of space can we put that as a minimum just to be safe [16:21] here is excerpt from Windows XP requirements "128 megabytes (MB) of RAM or higher recommended (64 MB minimum supported; may limit performance and some features)" [16:21] We are talking about *minimal* _*requirements*_. If I want it to be better, *I* add extra RAM. If it says that the minimal is 256, I'll be sure to add 512 instead. [16:21] michalski: fully agree with you... I don't see what we are targeting with 128M [16:21] doluu: very good idea too [16:22] with virtualisation, admins are slicing systems to the bare minimum at times for single purpose vms [16:22] What is the point of making the written requirements higher than the *actual* requirements? [16:22] soren: safety [16:23] From what? [16:23] fwiw I think 128M is an important target too [16:23] soren: you dont want your server going down because you dont have room to put an update [16:23] +1 on 128 [16:23] michalski: No. So? [16:23] what about the tasksel options. did these numbers take into account selecting them all? [16:23] dendrobates: no [16:23] soren: from people telling us that their servers are so slow... [16:24] soren: be generous to your system and add a couple of mbs [16:24] I think we need to clarify that different servers have wildly different requirements, so people know they can do cool things on small platforms, and need more for users who, uh, accumulate mail :-) [16:24] michalski: Bloating the minimal requirements will not magically add RAM to your system. [16:25] I think exaggerating the minimal requirements is an insult to our users. [16:25] however, I think we need to consider the tasksel tasks, or at least specify that we do not in the doc. [16:25] right [16:25] dendrobates: Agreed. [16:25] Soren's point here is that it may not be the server team's job to tell you what it should be at, the admin can put whatever they want in the machine, it *is* the server teams job to tell you what at a minimum the system will work at. [16:25] it all comes down to the applications. if you want a full on LAMP server or mail server for tens of thousands of users, then 128M and 300M hard drive won't cut it [16:25] dendrobates: agreed [16:25] dendrobates: The numbers we put there should specify what they are actually representing. [16:25] guys what do you think about this page http://www.centos.org/docs/5/html/5.1/Installation_Guide/ch-ent-table.html? [16:25] but that doesn't mean you can't install ubuntu server onto that system [16:25] soren: sorry if I misrepresented your point [16:25] * nealmcb wonders about a tasksel for "router with IDS" that would be really tight [16:26] mralphabet: No, that sums it fairly well :) [16:27] soren: good, I agree with that point . .. it is MY job as an admin to determine what is acceptable minimum performance for my installation. [16:28] but we need to add recommendations too, for newbies [16:28] michalski: That's fine. [16:28] as somebody mentioned above, when dealing with single function servers, the minimum is what I can plan for [16:28] ...but they should be marked as such. [16:28] Requirements != recommendations [16:28] soren:agreed [16:28] soren: agreed [16:28] I think if we included a minimum, and also a realistic reccomendation for a lamp server that would be useful. [16:29] I agree [16:29] Sounds reasonable [16:29] +1 [16:29] +1 [16:29] so do we document the minimum as with tasksel options or without? [16:29] so minimum ram: 128M [16:29] without I think. [16:29] (as long as the minimum is 128M ;) [16:29] I would say without [16:29] I would say without [16:29] minimum disk: will send for all tasks and without any, ok ? [16:30] nijaba: works for me [16:30] nijaba: great [16:30] I think lamp stack is good enough, we don't need to cover all cases. [16:30] I will just cover min and max [16:30] As long as we are upfront and honest about the numbers, we should be fine. [16:31] I think df is honest, AFAIK ;) [16:31] so we will have minimum numbers, and recommended numbers, right? [16:31] nijaba: well, remember stuff gets deleted as my bug points out - so it does need some padding [16:32] i.e. there is a higher "high water mark" on the df during the install [16:32] nealmcb: you were pointing to ubiquity, not d-i... [16:32] good point [16:32] doluu: I think we'll have min numbers and tasksel numbers [16:32] no problem [16:32] does d-i not get updates during install? [16:32] [ACTION] nijaba will revise the minimum requirements to include tasksel tasks [16:32] nealmcb: could do with autogrow partition in wmware [16:32] ACTION received: nijaba will revise the minimum requirements to include tasksel tasks [16:33] cool! [16:33] maybe it would be nice to have table with names of tasks and required minimum numbers? [16:34] doluu: yes [16:34] and we could add it to minimum reqs, have approximate min req for a installation [16:34] great [16:34] we are halfway done. Do we want to keep on this topic? [16:34] I don't necessarily disagree with that, but I think if you through a bunch of numbers at people it may be confusing [16:34] If we have more to discuss fine, if not, we need to move on. [16:35] I think we can move on. [16:35] move on [16:35] Yes, please. [16:35] yes [16:35] move on [16:35] move on [16:35] :) [16:35] dont put too many numbers but dont let them have a big surprise later on [16:35] Since the roadmap needs to be updated, we won't spen time going over it here. === \sh is now known as \sh_away [16:36] factoids are in good shape now - I'll update that section [16:36] [TOPIC] The Debian import freeze is Thursday. [16:36] New Topic: The Debian import freeze is Thursday. [16:37] if i have a suggestion for the server edition how do i put it on the agenda? [16:37] soren: are there any merges that we need to make sure are done. [16:37] dendrobates: I think the last one we reaslistically have to worry about is multipath-tools, which I'm already all over. [16:38] michalski: you can update the agenda: https://wiki.ubuntu.com/ServerTeam/Meeting [16:38] michalski: add it to the wiki https://wiki.ubuntu.com/ServerTeam/Meeting [16:38] ok thanks [16:38] soren: good. [16:39] [TOPIC] ruby-on-rails (What is the status of this? [16:39] New Topic: ruby-on-rails (What is the status of this? [16:39] Is anyone working on this here? [16:40] I volenteered to help, but I'm not sure what the status is. [16:40] I know Rails released 2.0 last week. [16:40] :) [16:41] I forget who was working on it.. mathiaz and ivoks, possibly. [16:41] I'll look back and contact the people working on it. [16:42] [TOPIC] Agree on next meeting date and time. [16:42] New Topic: Agree on next meeting date and time. [16:42] Next Tuesday at the same time ok? [16:42] same bat time, same bat channel? [16:42] it's no related to anything we were talking here [16:43] did i add that right? https://wiki.ubuntu.com/ServerTeam/Meeting#preview [16:43] same time and place works for me... just fyi [16:43] michalski: " Suggest install option for GUI(Gnome,KDE,ect) on server edition." [16:43] today Kir from OpenVZ said in email that the team is working hard OpenVZ available in next LTS [16:43] michalski: If is't about adding gnome and kde tasks, then yes. [16:43] i'll try to make it next week but im in school so i might not be able to [16:44] nealmcb: yes [16:44] it will be based on 2.6.24 [16:44] michalski: our approach is to do guis via the web, not x11 - see ebox etc [16:44] michalski: What's the use case? [16:44] doluu: yes, I will probaly not be in main, but I hope it will be available in some way. [16:44] soren: newbie wants server but doesnt want to use command line utilities [16:45] even if we added something realy basic for a gui it'd still be good [16:45] doluu: yes [16:45] michalski: Then he doesn't want server. [16:45] michalski: Simple. [16:45] michalski: install desktop edition, then install apache or whatever on top of it [16:46] well, there are kernel issues also [16:46] michalski: there is nothing that stops a user from using apt to install a desktop on the server. [16:46] michalski: we just don't support it. [16:46] but that would only matter for high-performance servers [16:46] michalski: heh, everybody answering for you [16:46] mralphabets: is there a help guide for that? [16:46] mralphabets: i know it sucks :P [16:46] michalski: apache and whatever else should be included in the "add remove programs" [16:47] michalski: there's a task to create one: https://wiki.ubuntu.com/ServerTeam/Roadmap#head-89567453e89879dec5253fb3ba56d27c6d27fc3f [16:47] there is also nothing that stops a user from installing server apps on their desktop box [16:47] michalski: but again - the direction for simple admin of a server in most of these cases is ebox - [16:47] ok thanks [16:47] michalski: the desktop install pulls from the exact same repositories [16:47] sommer: minimal install, no tasks: 500M (466812928B) based on the vmdk size after install [16:47] I experiencing some problem with latest version of php5 [16:48] nijaba: stop doing work - we're talking!! :-) [16:48] nijaba: sweet, I'll revise the docs. Just to double check we're going with 128M ram and 500M hd? [16:48] nijaba: That's a really good way to determinate it actually. [16:48] already file bug to LP, and maybe Kees is working on it [16:48] sommer: df shows 420M used [16:48] nijaba: ..as that takes temporary storage into account. [16:48] sommer: yes [16:49] cool I'll get it updated. [16:49] sommer: wait for the "all tasks" results [16:49] nijaba: yep, will do [16:51] dendrobates: i want to join tons of different groups,but their meetings are during school hours, what do i do? [16:51] ...without missing school :P [16:51] michalski: Cut class. [16:51] Oh. [16:51] :) [16:51] lol [16:51] another item I had was that we're adding a lot of new conent to the docs and if anyone is willing to help review that would be awesome. [16:51] michalski: you can participate in lots of stuff really well via email [16:52] ubuntu members? [16:52] I can send you the xml files if you don't want to check out the whole repo. [16:52] sommer: I'm always up for it :) [16:52] nijaba, sommer: thanks [16:52] michalski: http://mcburnett.org/neal/talks/contribute_to_ubuntu.html [16:53] nijaba: very cool, thanks [16:53] nealmcb: haha cool i am 14 :P [16:53] michalski: we've already got one 14-year-old ubuntu member :-) [16:54] the problem with young guys, is that they tend to grow older every year ;) [16:54] nealmcb: realy wow [16:54] o0 [16:54] lol yeah [16:57] ok, if there is nothing else, were done. [16:57] #endmeeting [16:57] Meeting finished at 16:57. [16:57] Woo! [16:57] thanks all [16:58] cheers [16:58] mathias would be proud [16:58] thanks all [17:00] michalski: chat with peanutb on e.g. #ubuntu-us [17:00] nealmcb: ok === _neversfelde is now known as neversfelde === rpereira_ is now known as rpereira === pochu_ is now known as pochu [22:13] @now [22:13] Current time in Etc/UTC: December 11 2007, 22:13:09 - Next meeting: Kubuntu Developers in 1 day === ausimag1 is now known as ausimage