Skip to main content

Dell Linux community repository beta - software repository update

There was a message from Michael Brown on the Dell PowerEdge mailing list, that I thought is important enough to repeat here as many people may not know about that list.

Dell has an active OpenManage infra setup for Linux to help monitor and manage their hardware. As we have their 2950s, I'm monitoring that list.

"After several months of work, I am ready to announce a bèta period for the Dell Community Linux repository at http://linux.dell.com/repo/community. When complete, this repository will be the replacement for the current software repository. Please read the details on the repository homepage.

I will be running a two week beta period to ensure that the repository is functioning properly. After two weeks, I will redirect software repo bootstrap so that new installs will use the community repo. And two weeks after that, I will redirect all current software repo users to the community repository.

Early this year I asked the community if people would be willing to submit RPMs to the Dell repository for things that would enhance Dell systems. There was a pretty good response from that query, but the problem was that we were not in a position to accept these contributions. The community repository is the answer for this. With this new repository, we will be able to accept outside contributions and enable community involvement around the sorts of things that enhance Dell systems.

OpenSUSE Build Service:

The new community repository is built using the OpenSUSE Build Service. The Dell repository is using the build service project isv:dell:community. After the beta period for the repository is over, we will be allowing external contributions by using the security features available in the Build Service. Please follow the links on the repository welcome page to see the process for contributing.

Why the name change:

The 'software' repository was the first repository that we set up, over 5 years ago. Little did we know that it would be popular and that we would have the need for other repositories (the firmware and hardware repos, for example), and the name was a bit unfortunate. We feel that the name "Community Repository" will more accurately reflect the content of this specific repository.

What is in the repository:

The goal is to get all of the open source software that Dell distributes into this repository. Things like DKMS, libsmbios, etc, are in this repository. In the future, we expect that community contributions will become a major part of the repository as well. It is our hope that things like Nagios and OpenNMS plugins for Dell systems are contributed.

Other Benefits of the Build Service:

Using the OpenSUSE Build service, we are able to support a very wide variety of distributions, much wider than my previous homegrown build system, and with far less administration as well. We now support Fedora and OpenSUSE, with Ubuntu and Debian support on the way. The Build Service project is enabled for Ubuntu builds, but no packages currently have the proper build service enabling files. This will come in time."

Comments

Popular posts from this blog

Preventing PuTTY timeouts

Just found a great tip to prevent timeouts of PuTTY sessions. I'm fine with timeouts by the host, but in our case the firewall kills sessions after 30 minutes of inactivity... When using PuTTY to ssh to your Linux/Unix servers, be sure to use the feature to send NULL packets to prevent a timeout. I've set it to once every 900 seconds, i.e. 15 minutes... See screenshot on the right.

Removing VGs or LVs from LVM

While are many excellent tutorials about creating and using LVM on Linux, not may show you how you can remove disks from LVM Volume Groups (VG) and reclaim storage or how to remove a Logical Volume (LV) from your LVM set-up. Here is what I did: Use -t to TEST ANY LVM action first! We are going to release 1 TB from LVM. The Volume group was extended with 1 TB storage to serve as a cheap NFS/CIFS file server when setting up our data center. It is now deprecated and replaced by a NAS so it's no longer needed. 1) check LVM; note the four 256 GB LUNs [root@server ~]# pvscan -v Wiping cache of LVM-capable devices Wiping internal VG cache Walking through all physical volumes PV /dev/sdb1 VG vgdata lvm2 [50.00 GB / 0 free] PV /dev/sdc1 VG vgdata lvm2 [256.00 GB / 0 free] PV /dev/sdd1 VG vgdata lvm2 [256.00 GB / 0 free] PV /dev/sde1 VG vgdata lvm2 [256.00 GB / 0 free] PV /dev/sdf1 VG vgdata lvm2 [256.00 GB / 0 free] PV /dev/sdg ...

Dell Linux - OMSA Hardware Monitoring

Just getting started using Dell's OpenManage Server Administrator (OMSA) on our Oracle Linux platform. There are some confusing instructions going around so it's not immediately clear what to do, hence my blogging here. :) There is a site on Dell - Hardware Monitoring , as well as a wiki with instruction on how to setup their OMSA tooling using yum or up2date. [update]My first update for their instructions: be sure your server has Internet access, as most servers will use a proxy or so. use export http_proxy=http://yourproxy.example.com:port to configure it just for the session, and setup up2date to use an HTTP proxy by editing the settings in /etc/sysconfig/rhn/up2date .