13.04 Blueprints
Hi, As per Robie's previous email request. I've filed some blueprints for upcoming UDS. https://blueprints.launchpad.net/ubuntu/+spec/servercloud-r-openstack-sru https://blueprints.launchpad.net/ubuntu/+spec/servercloud-r-openstack-packaging https://blueprints.launchpad.net/ubuntu/+spec/servercloud-r-openstack-qa https://blueprints.launchpad.net/ubuntu/+spec/servercloud-r-openstack-grizzly\ Regards chuck -- ubuntu-server mailing list ubuntu-server@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-server More info: https://wiki.ubuntu.com/ServerTeam
Re: Preparing for the next release
You did miss something:
https://github.com/zulcss/cobbler-oneiric
Regards
chuck
On Mon, 07 Nov 2011 12:40:36 -0500
Clint Byrum wrote:
>
> We probably need to start upstreaming our patches a lot more
> aggressively:
>
> 05_cobbler_fix_reposync_permissions.patch
> 12_fix_dhcp_restart.patch
> 21_cobbler_use_netboot.patch
> 33_authn_configfile.patch
> 34_fix_apache_wont_start.patch
> 39_cw_remove_vhost.patch
> 40_ubuntu_bind9_management.patch
> 41_update_tree_path_with_arch.patch
> 42_fix_repomirror_create_sync.patch
> 43_fix_reposync_env_variable.patch
> 44_cobbler_manpage_syntax_fix.patch
> 45_add_gpxe_support.patch
> 46_valid_hostname_for_dns.patch
> 47_ubuntu_add_oneiric_codename.patch
> 48_ubuntu_mini_iso_autodetect.patch
> 49_ubuntu_add_arm_arch_support.patch
> 50_fix_cobbler_timezone.patch
> 51_koan_grub2_instead_of_grubby.patch
> 52_ubuntu_default_config.patch
> 53_sample_preseed_kopts_postinst.patch
> 54_koan_fix_tree_when_ksmeta.patch
> 55_ubuntu_branding.patch
> 56_ubuntu_arm_generate_pxe_files.patch
> 57_ubuntu_dnsmasq_domain.patch
>
> Note the forwarded message which shows only a few tiny patches in
> 2.2.2.
>
> I missed the UDS session, but is this on somebody's TODO list for
> alpha1/alpha2 ?
>
> --- Begin forwarded message from James Cammarata ---
> From: James Cammarata
> To: cobbler development list ,
> cobbler mailing list Date: Sun, 06
> Nov 2011 18:57:08 -0500 Subject: Preparing for the next release
>
> Gearing up for 2.2.2, so I've gone through the master and release22
> branches making sure everything has been applied. As of now, I believe
> there are only 4 patches that have not been applied to release22:
>
> commit 5d1f682946cb5bf323ea97062dabf8071c9698a1
> Merge: 1b4f9ec... 7f24553...
> Author: James Cammarata
> Date: Fri Nov 4 03:36:07 2011 -0500
>
> Merge of authn_pam/https feature branch
>
> commit 4bee30b4086a8d845bea5d39d6f2cba1f4a396aa
> Author: James Cammarata
> Date: Fri Oct 28 01:11:02 2011 -0500
>
> Enabling CSRF protection for the web interface
>
> commit 18eb1c06779b37d89dfb2962a08236dd1bab24a6
> Author: James Cammarata
> Date: Fri Nov 4 02:33:38 2011 -0500
>
> Additional CSRF work. All URLs that modify state are now required
> to be POSTs only.
>
> commit 1b4f9ecf051422eb8512794701900f6199651442
> Author: James Cammarata
> Date: Fri Nov 4 03:23:09 2011 -0500
>
> Convert all yaml loads to safe_loads for security/safety reasons.
> https://bugs.launchpad.net/ubuntu/+source/cobbler/+bug/858883
>
>
> If you notice I forgot to apply something you sent in, or if I forgot
> to apply it both to master AND release22, let me know and I'll cherry
> pick it over.
>
> I'd like to get all of these in for the next release, so if anyone has
> some spare cycles I'd love for some extra testing. If you typically
> install RPMs, you can easily build them by cloning the git tree and
> using the command "make rpms", which should generate RPMs with the
> version of 2.3.1-1. Please don't test these on production servers, the
> YAML load change above shouldn't cause any issues but just in case I'd
> hate for someone to corrupt production data.
>
> If you do end up testing the authn_pam/https patch, please be aware
> that a pretty major change was made to the cobbler_web.conf file for
> Apache. Make sure there's no rpmnew/rpmsave version of this, and that
> the contents look like the following:
>
> # This configuration file enables the cobbler web
> # interface (django version)
>
> # Force everything to go to https
> RewriteEngine on
> RewriteCond %{HTTPS} off
> RewriteCond %{REQUEST_URI} ^/cobbler_web
> RewriteRule (.*) https://%{HTTP_HOST}%{REQUEST_URI}
>
> WSGIScriptAlias /cobbler_web /usr/share/cobbler/web/cobbler.wsgi
>
> Here is a list of the patches applied since 2.2.1:
>
> *FEAT: Add fedora16, rawhide, opensuse 11.2, 11.3, 11.4 and 12.1
> to codes.py This should also fix ticket #611
> *FEAT: Added a %post section for the cobbler-web package, which
> replaces the SECRET_KEY field in the Django settings.py with a random
> string
> *BUGFIX: Use VALID_OS_VERSIONS from codes.py in the redhat
> importer.
> *BUGFIX: Fixes to import_tree() to actually copy files to a safe
> place when --available-as is specified.
> Also some cleanup to the debian/ubuntu import module for when
> --available-as is specified.
> *BUGFIX: Modification to import processes so that rsync:// works
> as a path. These changes should also correct the incorrect linking
> issue where the link created in webdir/links/ pointed at a directory
> in ks_mirror without the arch
> Also removed the .old import modules for debian/ubuntu, which
> were replaced with the unified manage_import_debian_ubuntu.py
> *BUGFIX: add the /var/www/cobbler/pub directory to setup.py.
> Calling buildiso from cobbler-web now works as expected.
> *BUGFIX: patch koan (xencreate) to correct the same issue that was
> broken for vmware regarding qemu_net_type
>
Re: Roadmap: Xen revisited
Hi Justin, I am the developer assigned to the specification, alot of the work has already been done. We have the dom0 enabled in the kernel and have the package synced from Debian. Right now we need more testing and opening the bug reports. If you want to contact me off list that would be great as well. chuck On Tue, 5 Jul 2011 16:22:03 -0700 Justin Ryan wrote: > Howdy! > > I came across the Oneiric server roadmap today and saw some sensible > items regarding Xen support which align with work I've been meaning > to do for some time, as well as the quoted recent short thread. > > I'd like to volunteer to help with this work, I did a lot of work > with Xen on Ubuntu over the past couple of years, mostly 3.4 and 4.0 > beta on karmic, and am now revisiting with a goal of converting a > number of kvm hosts to Xen, which I believe will yield better > performance. > > I'm very familiar with dom0 pvops support and would happily work with > the kernel team, as well as refreshing the debian xen packages to > 4.1, which has some really great functionality. > > -- snip -- > > On 03/30/2011 08:27 AM, Chuck Short wrote: > >* Hi,*>**>* In the past Xen support in Ubuntu as a host has been > >difficult for a*>* variety of reasons most notably no upstream > >kernel support. Now that*>* dom0 should be coming into the vanilla > >kernel soon. I think its time to*>* revisit supporting Xen as a > >hypervisor as well.*>**>* Regards*>* chuck*>**Hi there, > > Linus just accepted almost all the xen bits in 2.6.39+, this will > allow Linux to run in Xen as Domain-0 and DomainU fully > paravirtulized, more info: > http://blogs.oracle.com/wim/entry/linux_mainline_contains_all_the? > http://www.kernel.org/diff/diffview.cgi?file=/pub/linux/kernel/v2.6/snapshots/patch-2.6.39-git20.bz2 > > Best regards. > > -- snip -- > > -- > http://about.me/justizin -- ubuntu-server mailing list ubuntu-server@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-server More info: https://wiki.ubuntu.com/ServerTeam
Re: [RFC] The future of iscsitarget
On Thu, 19 May 2011 16:43:51 +0200 Stefan Bader wrote: > We currently carry iscsitarget as one of our ubuntu specific modules. > Due to the compile breaking for Oneiric, I was looking into this. I > found that, at least starting with Maverick, there is a source > package iscsitarget which also produces a dkms module. The code of > both is nearly identical, but have already diverged due to fixups > done to the kernel side while the dkms version just stayed at the > last upstream version. > > First question would be whether we really need iscsitarget at all as > there is an in kernel scsi target framework[1]. The answer may be > yes, because people (still) use it. > > But then it is not very efficient to provide the kernel module in the > kernel itself and a dkms package. I would tend to say it should be > removed from the kernel tree and only be provided by dkms as then all > the code from the iscsitarget project is in one package, the module > should not be important during installation as it only allows to use > the host as a target and when fixing the dkms build in the > iscsitarget package, the changes maybe flow back via debian to the > original project (though it looked a bit like there has been no > activity/changes since end of last year). > > What would be other peoples thoughts on this? > > -Stefan > > [1] http://lwn.net/Articles/424004/ Hi Stefan, I think we should drop iscsitarget since I believe tgt has been promoted to main in place of iscsitarget. Regards chuck -- ubuntu-server mailing list ubuntu-server@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-server More info: https://wiki.ubuntu.com/ServerTeam
Re: SRU tracker list gone
On Thu, 12 May 2011 21:31:13 +0300 Imre Gergely wrote: > > http://people.canonical.com/~chucks/SRUTracker/sru-tracker-bugs.html > > 404. > > What happened to it? Is there another similar list somewhere? > Its been taken down ti fix a bug, it should be back shortly. Regards chuck -- ubuntu-server mailing list ubuntu-server@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-server More info: https://wiki.ubuntu.com/ServerTeam
Re: Backups
On Thu, 21 Apr 2011 12:47:53 +0200 Nicolas Barcet wrote: > On 04/19/2011 04:33 PM, Michael Terry wrote: > > Hello! I'm doing a bit of research for my proposal for Ubuntu > > Desktop to install the GNOME-based Déjà Dup backup tool by > > default. (btw, please cc: me) > > > > I get the sense that command line backup methods are thick on the > > ground. Is there a backup tool that the Ubuntu Server project > > recommends? > > > > Is the program duplicity [1] (upon which Déjà Dup is based) well > > regarded in the server community? I'm curious if there is any > > mindshare overlap at all. > > > > [1] http://duplicity.nongnu.org/ > > If I am not mistaking, Bacula is the only backup tool available in > main at the moment, hence this could be considered the recommended > backup tool at the moment. > > Nick > Actually there is a both backuppc and bacula in main. But we recommend bacula to our users. chuck -- ubuntu-server mailing list ubuntu-server@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-server More info: https://wiki.ubuntu.com/ServerTeam
Re: [Oneiric-Topic] Revisit Xen support
On Mon, 04 Apr 2011 02:40:25 -0700 Clint Byrum wrote: > Excerpts from Soren Hansen's message of Mon Apr 04 01:40:39 -0700 > 2011: > > 2011/4/3 Clint Byrum : > > > Excerpts from Clint Byrum's message of Fri Apr 01 16:51:04 -0700 > > > 2011: > > >> Other than people already having familiarity with Xen, what is a > > >> compelling reason to support it in favor of, or in addition to, > > >> KVM? > > > Not one person has stood up and said that KVM blows Xen away, or > > > is even "better". > > > > Um, no... because you didn't ask. > > > > Fair enough. > > Maybe we should ask though. Adding Xen back in means less resources > for KVM, so the KVM users' opinions matter quite a bit. > I totally disagree with this. Adding Xen back would take little effort to do so. Regards chuck -- ubuntu-server mailing list ubuntu-server@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-server More info: https://wiki.ubuntu.com/ServerTeam
Re: [Oneiric-Topic] Revisit Xen support
On Sat, 02 Apr 2011 08:03:11 -0700 Clint Byrum wrote: > Excerpts from Michael Zoet's message of Sat Apr 02 01:20:36 -0700 > 2011: > > > > -BEGIN PGP SIGNED MESSAGE- > > Hash: SHA1 > > > > Am 02.04.2011 02:05, schrieb Raphaël Pinson: > > > On Sat, Apr 2, 2011 at 1:51 AM, Clint Byrum > > > wrote: > > >> Excerpts from Chuck Short's message of Wed Mar 30 07:27:50 -0700 > > >> 2011: > > >> > > >> Just playing devil's advocate here. > > >> > > >> Other than people already having familiarity with Xen, what is a > > >> compelling reason to support it in favor of, or in addition to, > > >> KVM? > > > > > > > > > Familiarity is a good reason I think, but also industry > > > standards, and hardware considerations. I think a lot of big > > > companies expect major distributions such as Ubuntu to provide a > > > proper support for such a standard as Xen. I know it came as a > > > disappointment for us that using Lucid as a (production) Xen dom0 > > > was nearly impossible. Also, afair, KVM requires hardware > > > support. Most recent machines provide it, but it's not rare to > > > find servers that are too old to use it, and then you'd rather > > > use Xen for servers than VMWare... > > > > > > > I agree with that! Really big companies choose the things they know. > > And if they have to switch the distro they do it. > > > > Noted. It sounds like Xen has a lot of inertia. > > > Another advantage for Xen: it is more mature and easier to setup (at > > least for me because I have only one configuration file I can change > > with vim). Much more documentation around that works. You have much > > more network options. And you can easily assign a hardware NIC to a > > VM with Xen. With KVM this does not work on every hardware... (Now > > I have 2 15.000,- ? servers where I can not do the things with KVM > > I could easily do with Xen. This was a pitty experience...) > > > > I feel like a broken record, but could you provide us with some facts > to back up these claims? Bug reports, manual pages, etc. > > > I feel like there is a lot of anecdotal evidence, but we shouldn't > make our decisions just because somebody says KVM can't do this or > Xen can do that. > http://iopscience.iop.org/1742-6596/.../1742-6596_219_4_042005.pdf Again Im not saying we should drop KVM in favor of XEN. if it something our users want then. We should at least have a better solution in Ubuntu than what we have now. chuck -- ubuntu-server mailing list ubuntu-server@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-server More info: https://wiki.ubuntu.com/ServerTeam
Re: [Oneiric-Topic] SRU Process
On Wed, 30 Mar 2011 11:25:44 -0400 Etienne Goyer wrote: > On 11-03-30 11:05 AM, Scott Kitterman wrote: > > On Wednesday, March 30, 2011 10:40:36 AM Chuck Short wrote: > >> Hi, > >> > >> I do not have the statistics in front of me, but I believe most of > >> users are using LTS releases of Ubuntu. The policy of cherrypicking > >> fixes from the development releases does not scale in my opinon. We > >> should offer PPAs for users who want to use a new version of for > >> example Apache. Or go through the list of packages we support and > >> see if we can get it to qualify as a micro release update. > > > > We can also do a lot of this through backports. We are very close > > to having the backports only install packages that users explicitly > > request from backports (just waiting on an LP change that's in > > progress), so it will be much safer to use going forward. > > The mechanism itself is really only half the question. I am more > interested in the level of commitment we are willing to make in > keeping certain key software "fresh" in LTS. Whether we deliver > these in backports, PPA or some other mechanism is really just an > implementation detail, IMHO. > > Right when I brought this up, I was more interested in the burden of tracking down the fixes in upstream code, backporing the fix, and asking for user testing. If you look at: http://people.canonical.com/~chucks/SRUTracker/sru-tracker-bugs.html We have a lot of requests for SRU bug fixes which takes time to fix. Depending on the workload that what have, we do what we can. >From the systems administrator perspective if they want to use newer versions of apache, mysql, etc then great they can use backports/ppa. If they want to be a more cautious then they can still use the *-updates pocket. Its really all about choice in this case. chuck -- ubuntu-server mailing list ubuntu-server@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-server More info: https://wiki.ubuntu.com/ServerTeam
Re: [Oneiric-Topic] Puppet Integration
On Wed, 30 Mar 2011 10:59:17 -1000 Paul Graydon wrote: > On 03/30/2011 04:53 AM, Chuck Short wrote: > > Hi, > > > > Ubuntu server should be offering better Puppet integration. This > > includes the following: > > > > * Making it really easy to deploy a puppet master server. > > * Possible d-i integration > > * Pre-canned puppet "reciepes" > > > > > > Regards > > chuck > > > To play a little bit of devils advocate, what is wrong with the > current method? > Puppet installs over apt-get and takes editing a quick > /etc/default/puppet file to say YES to enable it (rather than risk > conflicts) > > Paul > > > Nothing is wrong with the current method per se. My view is that it just provides the basics to the users. With Ubuntu orchestra as said before we are trying to offer more than what we currently offer, which is the basics. Regards chuck -- ubuntu-server mailing list ubuntu-server@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-server More info: https://wiki.ubuntu.com/ServerTeam
Re: [Oneiric-Topic] Package Updates
On Thu, 31 Mar 2011 08:55:44 -0400 Ralph Janke wrote: > On 03/30/2011 07:19 PM, Clint Byrum wrote: > > On Wed, Mar 30, 2011 at 10:16:14AM -0400, Ralph Janke wrote: > >> Isn't it time to use mariadb instead of mysql? > >> > > Could you provide some rationalization of MariaDB vs. the main MySQL > > releases? > > > > There are a bunch of forks we could consider with varying degrees of > > compatibility with MYSQL. > > > > Percona (working on packaging) > > MariaDB (available from their own repos) > > Drizzle (in universe) > > > > Compatible or not, none of these are really MySQL. > > > > I'd really like to have a good reason before moving to any of these > > as our preferred MySQL service. I don't think MySQL is like > > Hudson.. Oracle seems to be taking good care of it and (for the > > time being) nothing has changed in their approach to community > > contribution (which has never been fantastic anyway). > > > There are lots of reasons to go to mariadb! > > 1) They explicitly promise that they are always 100% backwards > compatible to the > related mysql version, hence nothing is lost in comparison with mysql > > 2) Mysql only tracks queries with 1s execution time granularity. > Mariadb tracks by > default ms granularity. This is very important for performance > analysis of in > particular websites. > > 3) MariaDb offers additional features (and storage engines) by > default that in mysql > require proprietary licences to obtain similar. > > Every case that I know of, mariadb could be just plugged into the > system for mysql without > any issues. > > That are only the reasons that come immediately into me head, there > are many more when you > look at the comparisons. > > > HI, Sure Mariadb is great but I'm looking with my distro glasses on and I see this: chuck@kyle:~$ apt-cache rdepends libmysqlclient16 | wc -l 166 The 166 is the number of packages that depend on libmysqlclient for functionality that they need. This includes both main and universe. So unless we have a clear plan of transitioning from mysql to mariadb and help from upstream both in Debian and the mariab developers then one can argue about the technical merits of one database over another until the cows come home. chuck -- ubuntu-server mailing list ubuntu-server@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-server More info: https://wiki.ubuntu.com/ServerTeam
Re: [Oneiric-Topic] Nagios
On Wed, 30 Mar 2011 15:58:40 -0400 Greg Wallace wrote: > OpenNMS www.*opennms*.org and Zenoss www.*zenoss*.com are two other > options that I think are also worthy of consideration. > > On Wed, Mar 30, 2011 at 2:25 PM, Clint Byrum wrote: > > > On Wed, 2011-03-30 at 10:59 -0400, Chuck Short wrote: > > > Hi, > > > > > > I think we should re-evaluate if nagios is the monitoring > > > solution we want to support and if it easy make really really > > > easy to deploy. > > > > > > > Seems to me that we should consider dropping nagios from main and > > promoting icinga as its replacement: > > > > https://www.icinga.org/faq/why-a-fork/ > > > > > > > > -- > > ubuntu-server mailing list > > ubuntu-server@lists.ubuntu.com > > https://lists.ubuntu.com/mailman/listinfo/ubuntu-server > > More info: https://wiki.ubuntu.com/ServerTeam > > > > > I was thinking the same thing. chuck -- ubuntu-server mailing list ubuntu-server@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-server More info: https://wiki.ubuntu.com/ServerTeam
Re: [Oneiric-Topic] SRU Process
On Wed, 30 Mar 2011 11:38:14 -0400 Marc Deslauriers wrote: > On Wed, 2011-03-30 at 11:00 -0400, Etienne Goyer wrote: > > On 11-03-30 10:40 AM, Chuck Short wrote: > > > I do not have the statistics in front of me, but I believe most of > > > users are using LTS releases of Ubuntu. The policy of > > > cherrypicking fixes from the development releases does not scale > > > in my opinon. We should offer PPAs for users who want to use a > > > new version of for example Apache. Or go through the list of > > > packages we support and see if we can get it to qualify as a > > > micro release update. > > > > Agreed. Some mechanism to "modularize" the distribution is in > > order. From an end-user perspective, it does no make any sense that > > you need to upgrade the OS to run a new version of Apache. I > > understand why we are doing this from the distribution perspective, > > and I know a lot of people are very attached to the way things are > > being done now, but it really baffles people coming to Ubuntu from > > other platforms at time. > > On the other hand, it doesn't make sense to break everyone's servers > every month when we update the apache or php version and the config > files/features/ABI change and their applications stop working. This is > the type of thing that enterprises dread...and is why IE6 took so long > to die... > > Most people in enterprise scenarios that I've seen who use stuff like > Apache on other platforms tend to install the latest version once, and > stick with that version for the life of the server once it goes into > production...foregoing any security updates. In fact, the constant > update of Apache to remain secure on Windows is one of the reasons > I've seen listed in security audits that recommend either migrating > to IIS, which remains at the same version throughout the life of the > OS, but gets constant security updates, or switching to Linux to > benefit from stable release security updates. > > Apache may be a bad example here for the type of application that > should get updated instead of fixed, as it is not something that is > stand-alone enough and updating it would have a great impact on > Ubuntu use in enterprise environments. > > Besides backports, there is also a process to obtain micro-release > exceptions. Unfortunately, upstream projects who don't change > ABI/config files/features with new versions are the exception and the > massive QA effort to test upgrading them in stable releases would be > orders of magnitude bigger than backporting a patch to fix a specific > issue with a specific test case. > > Marc. > > > Hi Marc, I agree with the points that you brought up and software such as Mysql and Apache are probably not a good idea for such a process because of their history. However I just wanted to put into people's minds that users do want to this. Like your experience in the past I would just install a server and leave it alone. But there is times where I wish the distro developers would have version X rather than version Y. As developers we have to make sure that we are making the best choice of backporting the packages that users want. chuck -- ubuntu-server mailing list ubuntu-server@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-server More info: https://wiki.ubuntu.com/ServerTeam
[Oneiric-Topic] Improvements to cobbler
Hi, I would like to see more puppet intergration with cobbler. That is all. Regards chuck -- ubuntu-server mailing list ubuntu-server@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-server More info: https://wiki.ubuntu.com/ServerTeam
[Oneiric-Topic] Openstack next steps
Hi, I would like to see us further Openstack into Ubuntu. This would include the following for distro: * Package the web interface * Continue packaging nova, glance, and swift snapshots. * Better deployment of openstack on deployment. * Maybe a live CD-ROM. This would I like to see from upstream: * ebsroot * Exposing statistics for instances. chuck -- ubuntu-server mailing list ubuntu-server@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-server More info: https://wiki.ubuntu.com/ServerTeam
[Oneiric-Topic] ipv6 health check
Hi, I would like to make sure that we are okay for IPV6. This includes making sure that various daemons are ready for IPV6 and if they work properly on Ubuntu Server with IPV6 enabled. Regards chuck -- ubuntu-server mailing list ubuntu-server@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-server More info: https://wiki.ubuntu.com/ServerTeam
[Oneiric-Topic] Nagios
Hi, I think we should re-evaluate if nagios is the monitoring solution we want to support and if it easy make really really easy to deploy. chuck -- ubuntu-server mailing list ubuntu-server@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-server More info: https://wiki.ubuntu.com/ServerTeam
[Oneiric-Topic] Puppet Integration
Hi, Ubuntu server should be offering better Puppet integration. This includes the following: * Making it really easy to deploy a puppet master server. * Possible d-i integration * Pre-canned puppet "reciepes" Regards chuck -- ubuntu-server mailing list ubuntu-server@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-server More info: https://wiki.ubuntu.com/ServerTeam
[Oneiric-Topic] SRU Process
Hi, I do not have the statistics in front of me, but I believe most of users are using LTS releases of Ubuntu. The policy of cherrypicking fixes from the development releases does not scale in my opinon. We should offer PPAs for users who want to use a new version of for example Apache. Or go through the list of packages we support and see if we can get it to qualify as a micro release update. Regards chuck -- ubuntu-server mailing list ubuntu-server@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-server More info: https://wiki.ubuntu.com/ServerTeam
[Oneiric-Topic] Revisit Xen support
Hi, In the past Xen support in Ubuntu as a host has been difficult for a variety of reasons most notably no upstream kernel support. Now that dom0 should be coming into the vanilla kernel soon. I think its time to revisit supporting Xen as a hypervisor as well. Regards chuck -- ubuntu-server mailing list ubuntu-server@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-server More info: https://wiki.ubuntu.com/ServerTeam
[Oneiric-Topic] Seed Review
Hi, I would like to propose that we do another server seed review for Oneiric. I think it would be a good idea to see we are offering the best that we can. Regards chuck -- ubuntu-server mailing list ubuntu-server@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-server More info: https://wiki.ubuntu.com/ServerTeam
[Oneiric-Topic] Package Updates
Hi, For Oneiric I would like the following packages updated: dovecot 1.2.x -> 2.x mysql 5.1 -> 5.5 The reasoning for this update in the long run it will be easier to maintain for a LTS and more users want to use both mysql 5.5 and dovecot2. Regards chuck -- ubuntu-server mailing list ubuntu-server@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-server More info: https://wiki.ubuntu.com/ServerTeam
Re: Feedback on the Ubuntu kernel for server and cloud
On Tue, 29 Mar 2011 06:11:14 -0700 John Johansen wrote: > The kernel team is looking for feedback on the state of the kernel for > server and cloud flavors of Ubuntu. Any and all feed back is welcome. > > What are we doing right? > What are we doing wrong? > What configs should we change? > What new features should we included? > > And most importantly what are the use cases for any desired changes, > so that we can evaluate changes in context. > > This information will be used to help improve the Ubuntu kernels > and to help ensure that we have the best server and cloud flavors > available. > > Thanks in advance > > John > > Hi John, Could we possibly turn on dom0 for natty + 1 as well. We would have to update the Xen userland tools as well. Regards chuck -- ubuntu-server mailing list ubuntu-server@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-server More info: https://wiki.ubuntu.com/ServerTeam
Server Team Meeting Minutes
Sorry this was late -- chuck = === Actions from previous meeting === No action was required from the previous meeting. === Natty Development === Last week alpha3 was released. Blueprints work items should be marked as postponed if they were completed. Everyone should have been doing ISO testing last week as well. [ACTION] Everybody should be doing ISO testing. === Ubuntu Server Team Events === No new events, but UDS is coming up pretty quickly. === Weekly Updates and Questions from the QA Team (hggdh) === Hggdh mentioned that he would need help in Alpha 3 testing and some baremetal installs would help. === Weekly Updates and Questions fromt the kernel team (smb) === Smb mentioned there was some EC2 testing fallout, some xfs regresssions, and nome nasty Lucid behavior in net name space (Bug #720095, Bug #725089, Bug #692848) === Weekly Updates from the Server Community team (kim0) === Ubuntu cloud days is coming soon (https://wiki.ubuntu.com/UbuntuCloudDays) which is basically similar to UDW but focus on the cloud. === Open Discussion === I mentioned that we want to add lxc containers support to the UEC images and there was no points raised. This would make things like openstack testing much easier. === Next Meeting date and Time === Tuesday March 8, 2011 16:00 UTC -- ubuntu-server mailing list ubuntu-server@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-server More info: https://wiki.ubuntu.com/ServerTeam
Re: PHP5-FPM is missing in Natty
On Mon, 21 Feb 2011 09:23:26 -0500 Arnaud Soyez wrote: > Hey all, > > Saturday I noticed that PHP5-FPM was missing from Natty. I reported > the issue on launchpad and then I talked with a MOTU to see if we > could prioritize it in order to have it fixed before featurefreeze. > He told me to contact the server team about this issue: > > https://bugs.launchpad.net/ubuntu/+source/php5/+bug/722007 > > Here is the bug description: > > php5-fpm is currently unavailable in Natty. > > This might be due to a change done in package php5 version 5.3.3-2 > (see https://launchpad.net/ubuntu/natty/+source/php5/5.3.3-7ubuntu1) > where building FPM has been disabled. The package had probably been > merged into Ubuntu during debianImport. It seems that the latest > version of php5 (3.5.3-1 see > http://packages.debian.org/changelogs/pool/main/p/php5/current/changelog) > from debian has reintroduced the build of PHP-FPM. > > > Thanks! > Arnaud Hi, It should be back this week. chuck -- ubuntu-server mailing list ubuntu-server@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-server More info: https://wiki.ubuntu.com/ServerTeam
Looking for Feedback: Update mysql from 5.1 to 5.5
Hi, During the Ubuntu Server Team meeting I brought up the agenda item of upgrading mysql 5.1 in main to mysql 5.5. There are several reasons to do this: * Its faster compared to mysql 5.1 (although I dont have any benchmarks) * There are more bug fixes for mysql 5.5. * Amazon is using it on the cloud images. * Packages are nearly ready to be uploaded. * Easier to maintain going forward. Thoughts? chuck -- ubuntu-server mailing list ubuntu-server@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-server More info: https://wiki.ubuntu.com/ServerTeam
Re: SSH and the Ubuntu Server
On 11/18/2010 03:08 PM, Mathias Gug wrote: > Excerpts from Robbie Williamson's message of Thu Nov 18 13:34:58 -0500 2010: >> On Thu, 2010-11-18 at 16:22 +, Colin Watson wrote: >>> On Thu, Nov 18, 2010 at 10:08:47AM -0600, Robbie Williamson wrote: On Thu, 2010-11-18 at 16:04 +, Colin Watson wrote: > On Thu, Nov 18, 2010 at 10:49:38AM -0500, Marc Deslauriers wrote: >> I think this screen is a good idea if in fact tasksel is moved to after >> the first boot. > We used to have a two-stage installer and it was a nightmare to maintain > for several reasons. Since we moved to a single-stage installer several > years back, we've burned all the necessary code with fire and enjoyed > it. Please don't make me go back to that. What if the Server team maintained the 2nd stage? Then we'd be making life easier for you, right? ;) >>> Er. :-) >>> >>> (In seriousness, any good-quality second stage would require some level >>> of cooperation from the first stage. We tried that and it was awful.) >> So I see the 1st stage as just installing the minimal server, then we >> boot to a login prompt...user logs in and can either do his/her business >> as desired or launch the 2nd stage (which they are told about in a 1st >> boot motd-type message). >> > I'd add that the 2nd stage would just be tasksel. > > I don't know what the 2-stage installer was like back in the old days. > The proposal discussed at UDS was: > > * to have the installer create a minimal-lean install (ie 1st > stage - same thing as of today). It creates a basic working system > which upon reboot can be configured for its final role (either by a > sysadmin via a console or ssh login [1] or a configuration management > system such as puppet, chef, cfengine, shell script, etc...). > > * Remove the tasksel step in the installer and add a note in the > motd pointing to tasksel so that a sysadmin can finish the > configuration of the system after reboot (as outlined in [1] above). > > This would provide a similar user experience to the one provided by > the Ubuntu cloud images on EC2 and UEC. Once an instance is started > the following text is displayed upon login into it via ssh: > > - > At the moment, only the core of the system is installed. To tune the > system to your needs, you can choose to install one or more > predefined collections of software by running the following > command: > > sudo tasksel --section server > - > > A similar message would be displayed when a user logs into the > newly-installed system (either via console or ssh). > Hi, If that what you were thinking of a "second stage installer". Then I think you might want something in between, functionailty wise, d-i and a yast type program. But simpler. chuck -- ubuntu-server mailing list ubuntu-server@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-server More info: https://wiki.ubuntu.com/ServerTeam
Ubuntu Server Team meeting minutes
== Agenda == Items we will be discussing: * Review ACTION points from previous meeting * SpamapS to submit rubygems change proposal as Important bug in Debian and CC ubuntu-devel * zul to nudge forward upstart script review process * jjohansen to review bug 493156 * zul to review papercut status of bug 582963 * Maverick development (jib) * Weekly Updates & Questions for the QA Team (hggdh) * Weekly Updates & Questions for the Kernel Team (jjohansen) * pv-ops kernel status update * Weekly Updates & Questions for the Documentation Team (sommer) * Weekly Updates & Questions for the Ubuntu Community Team (kim0) * Papercuts status (ttx) * Open Discussion * Announce next meeting date and time * Tuesday 2010-08-31 at 1800 UTC - #ubuntu-meeting == Minutes == ACTION points from previous meetings * SpamapS to submit rubygems change proposal as Important bug in Debian and CC ubuntu-devel * More work is needed and will be resubmiited * zul to nudge forward upstart script review process * Done * jjohansen to review bug 493156 * Not Done * zul to review papercut status of bug 582963 * Not Done Maverick Development * ttx mentioned that we are bit behind with maverick development, but with a nice trends line. * Beta Freeze was last thursday only RC fixes will be accepted. * ttx mentioed that he has burnup charts available that makes it a bit easier to read. ACTION: ttx to make burnup charts available to people who them Weekly Updates & Questions for the QA Team * Still testing eucalyptus. * QA is going through regression-potential bugs and will ping the team when they are ready. Weekly Updates & Questions for the Kernel Team === * jjohansen was working on fix for the xen kernels because a security fix broke them. * jjohansen mentioned that there was a fix for the phantom High load average on EC2. * bug 606373 is currnently being worked on. === Weekly Updates & Questions for the Documentation Team * Skipped sommer was not available Weekly Updates & Questions for the Ubuntu Community Team * Cloud forum is available on ubuntu forums now. * Working on a new resource and news aggregator for new developers. Papercuts status * We had until Thursday to fix the last six. so you had to unassign yourself to give someone else a chance to fix the bug. -- ubuntu-server mailing list ubuntu-server@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-server More info: https://wiki.ubuntu.com/ServerTeam
Ubuntu Server SRU Nomination Process
Hi, At UDS in Brussels the server team revisited the Ubuntu Server SRU process (Stable Release Updates) for released versions of Ubuntu Server. Currently the process is the following: 1. Bug is fixed in development release. 2. During the weekly IRC meeting the bug is discussed and nominated. 3. Someone fixes the bug in the stable release following the SRU process. 4. Bug fix is released in -updates. This allows users who attend the server meeting to nominated their favorite bugs to be back ported to the stable releases. In order to get more people involved with the SRU process we are moving the nominations to the mailing list. The new process is the following: 1. Bug is fixed in development release. 2. A weekly email is sent to the Ubuntu Server mailing list on the Monday. 3. Users will have until Friday to nominate bugs that have been fixed in the development list, by giving a +1 to the bug number and the reason for it. 4. The nominations will be reviewed and be nominated accordingly based on investigation. If you have any questions or comments please let me know. Regards chuck -- ubuntu-server mailing list ubuntu-server@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-server More info: https://wiki.ubuntu.com/ServerTeam
Server Team Meeting Minutes
Sorry for being late. Agenda Items we will be discussing: * Review ACTION points from previous meeting * ACTION: all to run ISO testing coverage on alpha1 * ACTION: smoser to ensure cloud images make it to the alpha1 iso tracker - Carry over * ACTION: smoser to coordinate with jjohansen and ttx to provide a more detailed work item overview for server-maverick-cloud-kernel-upgrades - Carry over * ACTION: sommer to present list of sections that need input from server team * Maverick development (jib) * Alpha2 subcycle status (ttx) * UEC related specs (jib) * Weekly Updates & Questions for the QA Team (hggdh) * Weekly Updates & Questions for the Kernel Team (jjohansen) * atop kernel patch * Bug:587893: linux-image-2.6.34-5-virtual is oversized, results in oversized server ISO * Weekly Updates & Questions for the Documentation Team (sommer) * Papercuts Alpha2 subcycle status (ttx) * Weekly SRU review: [[https://wiki.ubuntu.com/ServerTeam/KnowledgeBase#SRU%20weekly% 20review]] (mathiaz) * Open Discussion * Announce next meeting date and time * Tuesday 2010-06-15 at 1800 UTC - #ubuntu-meeting Minutes ## Use title4 (ie ) for each section of the minutes ## Only topics discussed during the meetings should be put in the minutes. ## Status reporting is done via another channel. Action Points from Previous Meetings * Action: Alpha 1 testing - Alpha1 testing went well, nothing appear to blow up, only had 50% coverage for Alpha1 need more for Alpha2 [ACTION] ttx to coordinate testing for Alpha 2 * Action: smoser to ensure cloud images make it for Alpha. This was done and tested. Now that slangasek doesnt do release management anymore someone else needs to be trained. [ACTION] smoser to train someone on the release team on the cloud image release. * Action: smoser to coordinate with jjohansen and ttx to provide a more detailed work item overview for server-maverick-cloud-kernel-upgrades. Action has been carried over * Action: sommer to present a list of sections that need input from the server team. No action was taken. Action has been carried over. Maverick Development The burn down chart is looking a little twisted due to the appearance of the UEC blueprints and more. All high specs should be 25% completion and that is not the case. It is worrying that at least 3 of the high specs have 0/1 items done and no status update. As a reminder please update your status and work items by EOB Monday. With regards to UEC specs a split has been made for the work between alpha2/3 and onwards and we'd like to make sure this reflects reality [ACTION] all to keep their specs uptodate with workitems (4-16 hours each) and update their status monday EOB Weekly Updates & Questions for the QA Team (hggdh) Carlos remarked that: 1. UEC test rig is ready to test the new SRUs 2. I cannot put Maverick in right now due to bug #588861 3. I am indeed a bit behind, but should catch up fast After that a whole discussion about SRU processes and sponsorship processes took place revolving around mongodb. Weekly Updates & Questions for the Kernel Team (jjohansen) Jjohansen will look at atop patches and how important they are. Ttx mentioned that 587893 was fixed and that a maverick backport kernel was available. Jjohansen said he would review the patchset, we are concerned with possibe performance degradation and breakage. Papercuts Alpha2 subcycle status (ttx) There was 14 targets nominated and 4 were fixed. Stable Release Updates No bugs were nominated for SRU backports. Open Discussion None Next Meeting The next meeting will be at Tuesday 2010-06-15 at 1800 UTC - #ubuntu-meeting. Agree on next meeting date and time Next meeting will be on Tuesday, June 15th at 15:00 UTC in #ubuntu-meeting. -- ubuntu-server mailing list ubuntu-server@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-server More info: https://wiki.ubuntu.com/ServerTeam
Re: iSCSI target software
On Fri, 2010-04-30 at 12:13 -0400, Etienne Goyer wrote: > Hello all, > > It seems like we have two options if we want to run an iSCSI target (a > "server") in lucid: > > - iscsitarget: widely used, but seems unmaintained. > > - tgt: the project seems more active, it's been recommended to me by > people who had to use both, but the Ubuntu package lack an init script / > upstart job to start tgtd. > > > Both are in universe. > > I am wondering what people think of these two options, and if it would > be appropriate to write a MIR to get one of those in main. > > > -- > Etienne Goyer > Technical Account Manager - Canonical Ltd > Ubuntu Certified Instructor -LPIC-3 > > ~= Ubuntu: Linux for Human Beings =~ > Hi, I would prefer tgt if its better supported IMHO. I would bring it up in the server seed session at UDS. chuck -- ubuntu-server mailing list ubuntu-server@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-server More info: https://wiki.ubuntu.com/ServerTeam
Meeting Minutes from Ubuntu Server Team
== Agenda == * Review ACTION points from previous meeting * Lucid release status (ttx) o RC milestone, ISO testing o Remaining RC bugs o Remaining work items in specs * Weekly Updates & Questions for the QA Team (hggdh) * Weekly Updates & Questions for the Kernel Team (jjohansen) * Weekly SRU review: https://wiki.ubuntu.com/ServerTeam/KnowledgeBase#SRU%20weekly%20review (mathiaz) * Maverick call for blueprints (ttx) * Open Discussion * Announce next meeting date and time == Minutes == Review ACTION points from previous meetings * mathiaz to fix the "server fixed bugs" broken script: NOT DONE * ttx to follow up with ivoks/RoaKSoax on cluster stack state : DONE * mathiaz to propose removal of dovecot-postfix on MLs: DONE Lucid Release status Release Candidate is in the oven, Wednesday focus should be on ISO testing and don't expect an ISO/images re-spin. Please test the heck out of them and don't forget to register your results. On the remaining RC bugs side, ttx has assigned most of them to the [[http://wiki.ubuntu.com/ServerTeam/ReleaseStatus|team]]. After the RC has been released this is the team's main focus. Finally, there are some remaining work item in [[ http://people.canonical.com/~pitti/workitems/canonical-server-ubuntu-10.04.html|specs.]] Most of the are about UEC testing/validation, so we should be ok. Weekly Updates & Questions for the QA team (hggdh) hggdh has been doing a heck of a job in testing UEC and shaking out some hard issues, resulting in a stream of issues in UEC stress testing and cloud images booting. The more we poke the more bugs are exposed. A bunch ideas were discussed on how to improve the testing which will be fleshed out at UDS. Weekly Updates & Questions for the Kernel Team (jjohansen) smoser said no issues found in ec2 testing related to the kernel. jjohansen remarked that a little debug info was shaken out and a couple of more bugs were showing up. smoser asked if jjohansen has proposed a blueprint to get some time to trial paravirt-ops kernels for ec2, which hasnt been done yet. jjohnansen said he hasnt had a chance to look at a kernel oops which appeared in some UEC guests. SRU No new SRU bugs were nominated. mathiaz did mention that the SRU process will be changed, and raised the issue of a dedicated resource for lucid SRU for the point release. [ACTION] ttx to confirm with jib lucid SRU resource allocation Maverick Call for blueprints ttx raised the call for Maverick blueprints. If you want to suggest a UDS session topic, feel free to file an Ubuntu blueprint. The named is server-maverick-* and the approver must be set to Jos Boumans At this point only one blueprint has been proposed. A page has been setup to capture braindumps and spec which is found [[https://wiki.ubuntu.com/ServerTeam/MaverickIdeaPool|here]]. Announce next meeting date and time Next meeting will be on Wednesday, April 28th at 14:00 UTC in #ubuntu-meeting. -- ubuntu-server mailing list ubuntu-server@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-server More info: https://wiki.ubuntu.com/ServerTeam
Meeting Minutes from Ubuntu Server Team meeting
Action points from previous meetings = Mathiaz to discuss with cjwatson about ubuntu-server upload team, not done yet. Beta1 Status review = BetaFreeze is thursday. Only beta targeted bugs will be accepted which doesnt stop you from working on lower priority bugs and waiting for them to be queued. This affects several specs such as the eucalyptus-merging-and-packaging, since we might want to target several bugs to fix. Things for papercuts, bugzapping, puppet-testsuite: fixes of lesser importance should be queued for post beta1freeze. The following bugs are targeted for Beta1: * 499389 * 526480 * 519513 Weekly Updates & Questions from QA Team = Hggdh still mentioned that the Mysql 5.0 testsuite is still failing to build. However, since Mysql 5.0 is going to be removed it should probably be removed from the automated testsuite build process. It was also noticed that Atlas was being built as well. It was questioned why it is being built in the PPA as well. Hggdh will also look at how the UEC test rig is run as well. [ACTION] hggdh to remove mysql5.0 and question atlas in the build regression test rig Weekly Updates & Questions from Kernel Team Bug #527208 is still outstanding and will not make it for the beta since the kernel is closed on monday. For bug #531823 we hope to have a work around for Lucid. JJohansen mentioned that we had a late rebasing for the EC2 kernel so keep your eyes open for bugs. The vlan-modules udeb should be available in beta1 as well. Euca2ools/Boto 1.9 test coverage = We run our euca2ools with boto 1.9 while upstream tests with boto 1.8 and we always tend to run the same set of commands. In order to get confidence that lesser used commands are working, ttx prepared a testcase page coverage at https://wiki.ubuntu.com/Boto19TestCoverage. When you use the euca2ools commands succesfully please update the page. For the more complex commands, the idea is test the optional parameters as well, which will take more time. If you find something broken please open a bug and let smoser know. Server Papercuts Status for beta-1 : https://launchpad.net/server-papercuts/+milestone/lucid-beta-1 Ttx remarked that 4 bugs out of 14 still open. Please feel free to fix what you can especially before BetaFreeze. However there was no nominations this week. [ACTION] ttx to blog about the beta-1 campaign so far, to trigger new candidates Bugzapping status Kirkland mentioned the qemu-kvm bugs were cut in half. Ttx said that the bug zapping was going on wednesday and bug fixing was going on thursday. These are the bugzapping days coming up in the future: * Eucalyptus (week after next) * Mysql (Week of Apr 1) Server documentation Ttx wanted to get an update from asommer about the Ubuntu Server Guide documentation however asommer was not available. Ttx noted there was a couple of sections out of date and was wondering if help was needed to update it. [ACTION] ttx to bring up status of server doc in an email thread Weekly SRU Review = Bug #530945 was the only one to bring for an SRU. Open Discussion * zul mentioned that PHP 5.3.1 transition was mostly done. * smoser wanted people to test EBS root volume for EC2. Agree on next meeting date and time Next meeting will be on Tuesday, March 17th at 15:00 UTC in #ubuntu-meeting. -- ubuntu-server mailing list ubuntu-server@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-server More info: https://wiki.ubuntu.com/ServerTeam
PHP 5.3 for Lucid
Hi Recenty the Debian PHP 5.3 packages entered unstable, which means that the next release of Debian will have PHP 5.3 for their next release. This means that Ubuntu would be the last modern distrobution that I know would still being 5.2 What this means to Ubuntu is the following: If we stay with PHP 5.2: * The status quo remains but we diverge from Debian, which means we are maintaining or own version. * If PHP applications synchronize from Debian we still have to make them work with PHP 5. * More stability If we move to PHP 5.3: * The debian maintainers are relaying on the individual package maintainers to do the transition, which means some applications (such as drupal, joomla, etc) can break * We synchronize with Debian more easily. * Easier PHP maintenance for the Ubuntu Server Team. Note: its not possible to install php 5.2 and 5.3 side by side. Quite frankly Im still sitting on the fence with this and want to solicit people's opinions on the subject. Regards chuck -- ubuntu-server mailing list ubuntu-server@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-server More info: https://wiki.ubuntu.com/ServerTeam
Ubuntu Server Community Team Meeting
Review Action Points from Previous Meeting The actions were assigned at the previous meeting: Action: smoser to publish karmic cloud image refresh (done) Action: Everyone: update status for your specs before the meeting starts (few left to do) Action: ttx, zul to blog about papercuts, make sure UWN gets the word (done) Action: ttx to send email about criteria and nomination to ubuntu-devel, ubuntu-server Action: smoser to raise thread about the no-ramdisk / -virtual config tradeoff (done) Action: zul, kirkland to unassign themselves from "maybe working on one day" bugs (done) Alpha3 subcycle planning Work Items for Alpha 3 Everything that's marked 'medium' or high is fairly sure to make it into 'alpha3'. 'Low' priority specs are targets of opprotunities and we'll do our best to get as many of those done as possible. Please note there's not been much change on this week but we pretty much expect it to be stable now. No questions were raised in the discussion Spec Review A general status review was performed for specifications that were considered to be a "high" priority that are < 30%. The specifciations that were reviewed were: * server-lucid-apport-hooks * server-canonical-application-support * server-lucid-seeds * server-lucid-uec-testing * server-lucid-ec2-config jib raised the point that if you have anything you need f2f time with the team or others on the platform team, make sure your code's in a shape to get cracking staight away on monday. Server Papercuts Now that project has been announced, we have 4 external papercut members, and 18 nominations so far. The next step is to discuss measurable objectives on how we should approach the papercuts. After much discussion, Thierry proposed that we review the papercuts proposals in the next meeting. It should be quick +1 round. ACTION: ttx to announce papercuts nominations Apport Hooks zul provided an update on the current status and the next steps. zul mentioned that the php5 apport hook is complete, and the eucalyptus apport hook has been updated. However, there has not been any community contributions yet. ACTION: zul to do another call to action for the apport hooks involvement PHP 5.3 for Luicd zul brought up in the meeting that Debian is moving to php version 5.3.1 for Debian Stable. It is currently in experimental and in the process to moving to Debian Unstable. zul mentioned that his preference is to stay with 5.2 since PHP applications that we care about (such as media wiki and drupal 5 still dont support PHP 5.3). Daivey asked if I have thought about what to with the "short tag" depreciation and mentioned that upstream is shipping with it by default. After much discussion about security, what it breaks, and to have it in backports the idea was to send an email to ubuntu-devel to get a wider variety of opinnons. ACTION: zul to raise php5.3 update on -server and -devel mailinglist, outline which apps are currently not working with 5.3 Weekly Updates & Questions for the QA Team Soren had perfrormed a UDW class on server automation which was great! Soren also mentioned that the PPA builds have been moved to a team PPA, so more people are being notified of build failures. He is also working on getting more of the qa-regression-testing run on a daily basis. As well as automated ISO testing will be moved to the DC No other questions were raised for Soren. Weekly Updates & Questions for the Kernel Team A summary of launchpad bug 494565 was done by jjohansen. Jjohansen mentioned that the kernel team has changed the suggest configs to builtin (virto, virtnet, and 1 scsi). It booted in limited testing. Test images are available or you could have wait for the next kernel upload, (which is expected to be on friday). There is some concern that configs change will change the behavior so we need wider testing. It was noted that these changes were reasonably risk free but there is still some concern. Assigned and to-be-assigned bugs List at http://qa.ubuntu.com/reports/team-assigned/canonical-server-assigned-bug-tasks.html were cleaned up by kirkland and zul. However there are new bugs there that has to be confirmed and triaged. Weekly SRU review List at http://qa.ubuntu.com/reports/ubuntu-server-team/fixedbugs.ubuntu-server.latest.html The following bugs were nominated: #462172, #480152, #502878, #500457, #504897 Open Discussion Nothing was raised in the open discussion. Agree on next meeting date and time Next meeting will be on Tuesday, Feb 11 at 15:00 UTC in #ubuntu-meeting. -- ubuntu-server mailing list ubuntu-server@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-server More info: https://wiki.ubuntu.com/ServerTeam
Server Team 20091216 meeting minutes
Hi, Here are the minutes of the meeting. They can also be found online with the irc logs here: https://wiki.ubuntu.com/MeetingLogs/Server/20091216. Revew ACTION points from the previous meeting * jib to review/approve server-lucid-more-mail-integration, done * smoser to push cloud dailies to ISO tracker asap, done * smoser to open bug for kernel team follow-up on ramdiskless kernels, done * zul, kirkland, mathiaz to sign up for sponsoring time on [[https://wiki.ubuntu.com/UbuntuDevelopment/CodeReviews|CodeReviews]], zul done, kirkland and mathiaz not done. Check blueprint status and progress for the week * server-lucid-canonical-application-support * 74% done * blocked on MIR team * server-lucid-eucalyptus-karmic-retrospective * 64% done on-track * blocker is the ML implementation * server-lucid-eucalyptus-merging-and-packaging * 61% done, looking good * blocker is getting eucalyptus working * server-lcuid-cloud-krd * 56% done * server-lucid-euca2tools * 50% done, on track * server-lucid-seeds * 47% done, on track * mathiaz working on the list of packages to promote/demote * zul is looking after the MIR * server-lucid-euca-remote-autoregister * 21% done, behind the curve on the burndown chart * in progress - hope to be able to commit some of the scripts this week * server-lucid-uec-testing * 12% done, on-track * hardware status is deffered * server-lucid-landscape-refresh * 0% done, not started yet * pending code drop and accounts setup. * not-started: * server-lucid-ec2-config * server-lucid-ec2-boothooks Assigned and to be assigned bugs Some team members are still assigned to more bugs than they should be actively working on, so this might need more review. Kirkland brought up that he needs some help from the foundations/security to help with ecryptfs in ubuntu stuff. ACTION: jib to talk to robbiew about ecryptfs in ubuntu ScottK also mentioned that courier is in real need of attention to the number of users that we have using it. Weekly Updates and Questions for the QA team Soren was not available so this item was skipped. Weekly updates and Questions for the Kernel team Jjohansen mentioned that he started poking at the kernel configs for lucid. Weekly SRU review [[https://bugs.launchpad.net/ubuntu/+source/samba/+bug/128612|128612]] was reviewed for an SRU update ACTION: zul to look at it. Conference attendance 2010 We're prepping an overview of what conferences people are attending to go anywhere please let jiboumans and randa know. Open Discussions Daviey asked for more contributions for the ubuntu-server-tips. -- ubuntu-server mailing list ubuntu-server@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-server More info: https://wiki.ubuntu.com/ServerTeam
Re: iptables init scripts
Hi Jim, Have you tried ufw I heard its pretty good. Regards chuck Jim Tarvid wrote: > any recommended iptables init scripts that will play well with > network-manager? > > -- ubuntu-server mailing list ubuntu-server@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-server More info: https://wiki.ubuntu.com/ServerTeam
Re: Moving w3m out of standard
If this does happen then the qa testing guidelines will have to be updated. chuck Dustin Kirkland wrote: > On Mon, Jun 16, 2008 at 1:08 PM, James Dinkel <[EMAIL PROTECTED]> wrote: > >> I would read the documentation on another system then, assuming the >> system referred to is a production server and not a test server. Even >> it there is a viable need for an interactive web browser, I think the >> use case would be so rare and added to the fact that people will have >> differing preferences on which text browser is best, that including >> any one in the default seed is a bad idea. >> > > This sounds reasonable to me. As mentioned above, I think it can be > handled in the Ubuntu Server Guide document with a list of viable text > browser alternatives and a pointer to the apt-get command. > > > :-Dustin > > -- ubuntu-server mailing list ubuntu-server@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-server More info: https://wiki.ubuntu.com/ServerTeam
Re: samba 3.0.28a in hardy?
Hi, This is being worked on and feature freeze exception has been filed. Thanks Regards chuck Rönnblom Janåke /Teknous wrote: > Hi, > > I noticed that samba-3.0.28a was released a few days ago. Will it be > included in hardy? Seems that the failure to join Windows 2008 domains > would automatically make it a candidate for inclusion... > > Major bug fixes included in Samba 3.0.28a are: > > o Failure to join Windows 2008 domains > o Windows Vista (including SP1 RC) interop issues > > = > Janåke Rönnblom > IT avdelningen, Teknous, Skellefteå Kommun > Assistentgatan 23 > 931 77 Skelleftea (Sweden) > - > Phone : +46-910-58 54 24 > Mobile : 070-397 07 43 > Fax: +46-910-58 54 99 > URL: http://www.skelleftea.se > - > "Those who do not understand Unix are condemned to reinvent it, > poorly." -- Henry Spencer > > -- ubuntu-server mailing list ubuntu-server@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-server More info: https://wiki.ubuntu.com/ServerTeam
Ebox Testing - Update
Hello, For those who are testing ebox, I have added the newest version to my ppa. apt-get install ebox=0.11.99-0ubuntu1~ppa1 This is the final pre-release before ebox-0.12. Again can you please send me any feed back. Thanks chuck -- ubuntu-server mailing list ubuntu-server@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-server More info: https://wiki.ubuntu.com/ServerTeam
Call for eBox testing.
Hello, I have added ebox 0.11 to my ppa. To install it please add the following to your /etc/apt/sources.list: deb http://ppa.launchpad.net/zulcss/ubuntu hardy main deb-src http://ppa.launchpad.net/zulcss/ubuntu hardy main Next run the command sudo apt-get update and finally sudo apt-get install ebox=0.11.0ubuntu1~ppa1 Let me know of any issues. Thanks chuck -- ubuntu-server mailing list ubuntu-server@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-server More info: https://wiki.ubuntu.com/ServerTeam
Re: update on eBox status
Hi Javier, I will take a look at this soon. Thanks chuck On Feb 11, 2008 9:30 AM, Javier Uruen Val <[EMAIL PROTECTED]> wrote: > Hi there, > > Just a few lines to let you know the status on the eBox platform front. > > I've been working to make eBox comply with the Debian packaging policy. > > I'm going to try summarise the changes we have made to achieve so. > > From the packaging point of view we have stripped out a lot of code from the > maintainer scripts. Now they are way simpler. > > I have done a lot of changes in the framework to deal with this: > > - eBox modules are not enabled by default. The only thing which is enabled by > default is the web interface. The other modules have to be enabled explicitly > by the user. > > - When a module is enabled, the user is prompted with a modal window where > she/he is told the actions and file modifications that eBox needs to perform > to enable the module. In case the user accepts to go ahead, we perform the > actions and file modifications. For every file we have to modify we store a > MD5 digest. > > - When saving changes, that is when the user configuration is translated into > modifications of configuration files, we compute a MD5 digest for every > single file which is going to modify, in case we detect that a file has been > modified manually we prompt the user to confirm if he wants to overwrite the > file or keep it. > > If you want to see how that works now I have recorded a screencast [1] > > These are the modules which have been already modified with the above changes: > > - ebox-services > - ebox-objects > - ebox-network > - ebox-firewall > - ebox-usersandgroups (LDAP) > - ebox-samba (Samba + PDC) > - ebox-printers (Samba + CUPS) > > You can find the above modules here [0]. > > During today I will probably have the following modules ready: > > - ebox-squid (Squid + Dansguardian) > - ebox-dhcp > - ebox-dns > - ebox-ca > - ebox-openvpn > - ebox-trafficshaping > > I do not think we can have the following modules ready: > > - ebox-mail > - ebox-mailfilter > - ebox-jabber > - ebox-soap > > > So just a few days before the FF, do you guys think that we have time to > upload the new packages? > > Thanks, > > Javi > > > [0] http://people.warp.es/~javi/hardy-ebox/ > [1] http://people.warp.es/~javi/ebox-hardy.ogg > > -- > ubuntu-server mailing list > ubuntu-server@lists.ubuntu.com > https://lists.ubuntu.com/mailman/listinfo/ubuntu-server > More info: https://wiki.ubuntu.com/ServerTeam > -- ubuntu-server mailing list ubuntu-server@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-server More info: https://wiki.ubuntu.com/ServerTeam
Main Inclusion Report for Bacula
Hello, For the server package review specification (https://wiki.ubuntu.com/ServerPackageReview) we evaluated the Bacula backup solution. However,Bacula was rejected due to a feature in Bacula which exposed clear text passwords through the command line. This will not be resolved upstream in Debian. If people have an alternative that they would like to suggest please do so. Regards Chuck -- ubuntu-server mailing list ubuntu-server@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-server More info: https://wiki.ubuntu.com/ServerTeam
Re: New meeting time proposal - Wednesday 21:00 UTC
Thats fine with me On Jan 11, 2008 12:28 PM, Ante Karamatić <[EMAIL PROTECTED]> wrote: > On Fri, 11 Jan 2008 10:37:15 -0500 > Mathias Gug <[EMAIL PROTECTED]> wrote: > > > Every Wednesday at 21:00 UTC. > > > > What do you think about it ? > > Much better than last one, which was during working hours. This is 10PM > for me and it is reasonable. I might even attend every time now :) > > > -- > ubuntu-server mailing list > ubuntu-server@lists.ubuntu.com > https://lists.ubuntu.com/mailman/listinfo/ubuntu-server > More info: https://wiki.ubuntu.com/ServerTeam > -- ubuntu-server mailing list ubuntu-server@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-server More info: https://wiki.ubuntu.com/ServerTeam
Re: Xen In Hardy
On 10/25/07, Liberio Cunha Neto <[EMAIL PROTECTED]> wrote: > some comments inline > > > On 10/25/07, Chuck Short <[EMAIL PROTECTED]> wrote: > > Hello, > > > > In order to get Xen working really well for servers in the hardy > > release. I wish to solicit opinions, in an effort to improve the spec > > that I'm in the middle of writing: > > > > 1. Kernel side > > > > Since 2.6.23 will have xen paravirt-ops (domU) we should use that > > right? However, it does not have the full features that users will > > want. No HVM console and no Windows XP guests. Its just basic basic > > domU support. So thats not really an option in my opinion. In gutsy, > > we decided to switch to opensuse dom0 kernel, however this caused more > > problems than what it was worth. So Im using fedora as a base this > > time. I have already started to port their kernel from 2.6.22->2.6.2x. > > paravirt-ops is only supported for domUs (so doesn't work for the host > kernel) and only X86 (no X86_64 available yet), what you are > suggesting here ? Im suggesting not to use paravirt-ops > > > > > 2. Xen hypervisor side > > > > Recently, Xen-3.1.1 was released that contains various fixes for the > > Xen-3.1. However the next version of (Xen-3.2) will be release in > > November. This will (hopefully) include things like cpufreq support. > > (This will also have to be ported from 2.6.18 to 2.6.24). In my > > opinnon, we should be using Xen-3.2 for hardy. I would also like the > > resync debian's patches with our own. So the tools will be in a better > > shape. > > cpufreq is way out of shape , if you check the unstable tree and > complains about it you will know, right now people using unstable is > having all kinds of clock issues because this. > > > > > 3. Windows support > > > > Users would like to use Xen to use windows with it (god only knows why ;) > > why they can't run windows right now ?, the main problem right now is > windows drivers opensource or free available , they don't exists , but > if you don't mind that load dom0 with networking and HD controllers > (via qemu) I don't see any problems , other than need to create all by > hand , no nice tool > > > > > 4. Xen-tools > > > > I would like to expand our simple base of tools that we use now > > (xen-tools, xenman). I would like to use things like virt-man > > (especially for the desktop, however its redhat only no debian images) > > however I might not have time for that. > > virt-manager have good things and bad ones , one that I really don't > like is the way virt-manager store the domU configuration , instead of > the default /etc/xen/domain.conf they use internaly stuff to manage > this so example , if you have a windows or any HVM host and wants to > enable qemu monitor (so you can change de CD image with the HVM > running) instead of just adding monitor = 1 , to your config you will > need to hack virt-manager to do it (this is only one example I have a > lot more if you want) > > > > > > > > Comments and help during the hardy release cycle is greatly appreciated. > > > > Thanks > > chuck > > > > -- > > ubuntu-server mailing list > > ubuntu-server@lists.ubuntu.com > > https://lists.ubuntu.com/mailman/listinfo/ubuntu-server > > More info: https://wiki.ubuntu.com/ServerTeam > > > -- ubuntu-server mailing list ubuntu-server@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-server More info: https://wiki.ubuntu.com/ServerTeam
Xen In Hardy
Hello, In order to get Xen working really well for servers in the hardy release. I wish to solicit opinions, in an effort to improve the spec that I'm in the middle of writing: 1. Kernel side Since 2.6.23 will have xen paravirt-ops (domU) we should use that right? However, it does not have the full features that users will want. No HVM console and no Windows XP guests. Its just basic basic domU support. So thats not really an option in my opinion. In gutsy, we decided to switch to opensuse dom0 kernel, however this caused more problems than what it was worth. So Im using fedora as a base this time. I have already started to port their kernel from 2.6.22->2.6.2x. 2. Xen hypervisor side Recently, Xen-3.1.1 was released that contains various fixes for the Xen-3.1. However the next version of (Xen-3.2) will be release in November. This will (hopefully) include things like cpufreq support. (This will also have to be ported from 2.6.18 to 2.6.24). In my opinnon, we should be using Xen-3.2 for hardy. I would also like the resync debian's patches with our own. So the tools will be in a better shape. 3. Windows support Users would like to use Xen to use windows with it (god only knows why ;) 4. Xen-tools I would like to expand our simple base of tools that we use now (xen-tools, xenman). I would like to use things like virt-man (especially for the desktop, however its redhat only no debian images) however I might not have time for that. Comments and help during the hardy release cycle is greatly appreciated. Thanks chuck -- ubuntu-server mailing list ubuntu-server@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-server More info: https://wiki.ubuntu.com/ServerTeam
