Re: Proposal for weekly Ensemble releases into Oneiric
> Unless anybody has any red flag on this, I'll go ahead and do this every > Tuesday. I'm also going to start linking specific bugs to the Ubuntu > package that need to get fixed in 11.10, and will encourage others to > do so. If there are Critical open bugs in upstream, I will delay the > weekly release until they are closed. Sounds great, thanks Clint. -- Gustavo Niemeyer http://niemeyer.net http://niemeyer.net/plus http://niemeyer.net/twitter http://niemeyer.net/blog -- I never filed a patent. -- 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] Complex deployment testing automation
Hey James, > I think this is worth re-visiting; automating something using ec2/puppet > (and maybe ensemble?) might make this fairly easy todo and would add > more depth to the testing that we already do automatically on ISO's and > ec2 images. Yeah, that sounds like a perfect fit for Ensemble. We've actually been doing exactly that already just with the initial tests. Clint has been developing the principia repository at Launchpad [1] which already contains some bootstrapping formulas. We'd be happy to discuss further how we can make Ensemble help more with that kind of testing. [1] https://launchpad.net/principia -- Gustavo Niemeyer http://niemeyer.net http://niemeyer.net/blog http://niemeyer.net/twitter -- 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: [ubuntu-server] Trying Ubuntu Server in Amazon EC2
> We're now launching instances on http://10.cloud.ubuntu.com without keys > that canonical has access to. > > I do think we're over-reacting a bit here. Agreed. Thanks for removing the key, Scott. Case closed. -- Gustavo Niemeyer http://niemeyer.net http://niemeyer.net/blog http://niemeyer.net/twitter -- 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: [ubuntu-server] Trying Ubuntu Server in Amazon EC2
> I agree pretty strongly with Eric here. This just raises so many red > flags that don't need to be raised, and puts Canonical in a bad light > that will take a long time to undo. Certainly agree regarding raising unnecessary red flags, but feels like there's a bit of overreaction here too. > How is this not a back door in an Ubuntu delivery? This is an experiment we're attempting to allow people to play with a sandbox for less than an hour, with the backend being open sourced and available for anyone to read, and with a FAQ about the raised issue in place even before anyone brought it up. If anything, that's an obvious front door with a welcome sign. >> I don't (yet) regret that decision, but I understand the concern. Again, >> we're not using it at all, and its very easily disabled by the user. If we're not using it at all, feels like a good idea to remove it. -- Gustavo Niemeyer http://niemeyer.net http://niemeyer.net/blog http://niemeyer.net/twitter -- 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: Ubuntu server and cloud IRC consolidation
> All suggested changes have been applied. I've changed topic on > #ubuntu-cloud to remove the redirection to #ubuntu-server > Regards Thanks Ahmed. -- Gustavo Niemeyer http://niemeyer.net http://niemeyer.net/blog http://niemeyer.net/twitter -- 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: Ubuntu server and cloud IRC consolidation
> Strike that, reverse it, I read the original message before I had my coffee. > Oops! > > Did not realize the suggestion was to move ensemble+ec2+virt -> cloud .. > > Sounds great as originally written. Indeed, we're a single community, so it makes sense to be together while the traffic does not justify separating the forums. I'll organize the merger tomorrow. -- Gustavo Niemeyer http://niemeyer.net http://niemeyer.net/blog http://niemeyer.net/twitter -- 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: Ubuntu Server update for Maverick Meerkat
Hi Jos, > with the Maverick cycle kicking off and UDS-M just behind > us, it's time to take a look at what's in store for the next > release of Ubuntu Server. In broad strokes, these will be > the likely topics: Are the LXC conversations a subtopic in one of those items, or should it be included as a new topic? -- Gustavo Niemeyer http://niemeyer.net http://niemeyer.net/blog http://niemeyer.net/identi.ca http://niemeyer.net/twitter -- 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: Ideas for landscape-sysinfo tool
Hello Steven, > Just to add to that, it would be nice to see a 24 hour history, 7 day > history, and 30 day history of load averages, and network usage if > possible. That's precisely the kind of feature that landscape-client and the Landscape server already offer. But long histories might not be good candidates for the login message. The idea is offering a quick hint about how things are generally going, together with any outstanding warnings that are likely worth keeping an eye on. -- Gustavo Niemeyer http://niemeyer.net -- 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: Ideas for landscape-sysinfo tool
Hi Daniel, > is that information going to be dynamically generated each time an > user does login, or it's going to be updated in a file every X > minutes, and the motd message will just happen to be the latest > version available?Personally I have some servers I never login It'll be displayed only during logins, even though it's quite possible that some of the notes do consider historic information at some point. > into, unless I know there is a problem with it, or I know security > updates are available, which make that message a bit pointless to > display at login time only. > > If that "motd" info was available in a file, then I could find a way > to push that into a centralized server where I could see it no matter > when I do an actual login. This is just one more feature we're implementing in Landscape, and in this case it'll benefit even administrators that are not Landscape users. If you want to reuse it in different situations, the software is GPL and it should be trivial to just run it from cron and ask it to mail the information anywhere you want, for instance. > And actually that type of expanded motd message may be more useful on > my desktop computer where I login more often than on a server that > just happily runs in a corner of the server room serving services or > disk space without human intervention for days at end. It'll be easy to run it on desktops too. > These days I'm playing with the getting old Big Brother (www.bb4.org) > to centralize messages from various servers into one web page. Now > looking at some of the info I have been tracking that way from my > servers: connectivity, system load, disk usage (i.e, specific > important disks are nearly full while other disks I can ignore), if > specific processes are still running (by default big brother tracks > cron), and if specific services are online and listening (ftp, http, > ssh). I could see some of these bits of info being useful in that motd > message. > > It is on my to-do list to tied into Dell's OMSA and track down as well > more hardware specific basic info (temperature, state of disks and > raid, are the fans working, etc). Nice ideas! Thank you! -- Gustavo Niemeyer http://niemeyer.net -- 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: Ideas for landscape-sysinfo tool
> I'm one of the developers working on the Landscape project at > Canonical[1]. Recently we've started working on a tool, so far named > landscape-sysinfo, which will be used to display some dynamic > information next to the MOTD message during logins. Andreas pointed out some interesting fact that I missed in my explanation: this tool won't depend on Landscape (even though it may end up benefiting somehow when Landscape is available to provide more information). -- Gustavo Niemeyer http://niemeyer.net -- 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: Ideas for landscape-sysinfo tool
Hey Scott, > There isn't a USN until a fix issued, so it's only apt-get update && > apt-get upgrade to deal with it. I don't particularly need a tool to find The idea is precisely to tell you that apt-get upgrade is advised. In any case, please don't focus too much on the example. The idea is precisely to find out what you do find useful, rather than the opposite. > this out. Open CVEs that I need to mitigate in another way would be much > more interesting. That's an interesting idea. Note taken. -- Gustavo Niemeyer http://niemeyer.net -- ubuntu-server mailing list ubuntu-server@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-server More info: https://wiki.ubuntu.com/ServerTeam
Ideas for landscape-sysinfo tool
Hello everyone, I'm one of the developers working on the Landscape project at Canonical[1]. Recently we've started working on a tool, so far named landscape-sysinfo, which will be used to display some dynamic information next to the MOTD message during logins. The goal of this tool is to provide the administrator a basic overview of how the system is running. To give a basic feeling of what it is about, a rough mockup follows. Please note that we don't even know yet which of these details will be available, and how they will be actually worded. System load: 1.15 Processes: 1500 Memory usage: 65% Temperature: 74 C Swap usage: None Users logged on: 1 (you) => Zombie processes were found alive. => Disk usage on /home is above 90%. => This machine is being affected by USNs 123, 456 and 789. The headers at the top will always be present, while notes at the bottom will report outstanding events. So the question is: what information would you find useful to look at during logins, to get an idea of how things are going in your servers? We obviously can't include too much information because we're limited to a reasonable amount of space, so it'd be very useful if any ideas were accompanied by the motivation, as that would help us to figure together which are the most interesting ones. Thank you very much. [1] http://landscape.canonical.com -- Gustavo Niemeyer http://niemeyer.net -- ubuntu-server mailing list ubuntu-server@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-server More info: https://wiki.ubuntu.com/ServerTeam
