Software Depot Service

CPTE 433John Beckett

What?

• A centralized source for software in your organization.

• Managed by the SA group.• Provides supported versions of

software for all users.• Methods vary so widely that the

function can be hard to recognize.– But it needs to be there!

If You Get It Right

• The service will function so smoothly that people will hardly know it exists.

• App updates should come from it seamlessly.

Is This a UNIX/LINUX Thing?

• Absolutely not:• Downloadable open-source software

such as FireFox• Downloadable proprietary software

such as Acrobat/Word/PowerPoint readers

• Other freeware that has been found useful

• Download vendor updates once, to save bandwidth and achieve control

Implementations

• Network share• “Push” system (distribution server

model)• Intranet/Extranet

Justification

• This is going to cost work, money, and organization. So we need to know why!

• If we don’t do it they will do it around us– Picking up the pieces will cost us more

• Save bandwidth for our Internet connection

• Save support work– Same argument as images– Scalability – get more without spending

more

Policies• Need a clear charter• Focus on players – who is going to do

what, and what happens if they don’t– Or if they leave the organization

• Standard “wrappers”: .deb, ZEN, Windows installer

• What if something isn’t right?– Argument to place software depot under

help desk

Depot Software

• FTP server• Web site

– Content management system?• UNIX has several depot systems• Windows has a depot system

More About Policies

• Life-cycle of components– How they get in, and why– How they are distributed, and to whom– How they are removed, and why

• Scope– Cluster, department, enterprise, virtual

enterprise • …which may include customers and even

our customers’ customers (Acrobat Reader)

LINUX Mirror

• Automatically keeps that package updated– Debian: Has three distributed versions

according to your preference of latest-thing versus stability

• Saves bandwidth• But…You don’t have control

– You are depending on distro to manage quality

ISO Format• Disk images suitable for “burning” to

CD or DVD.• Traditionally used to distribute images

of install disks. But…• Mac OS X can “mount” them directly.• Windows: Daemon Tools

(http://www.daemon-tools.cc/eng/products/dtLite) does the same thing. – Works to mount a video DVD image.– Useful for corporate info video distribution– Built into Windows 8

Partitioning Your Depot

Who Uses It• Standard – suitable for

every machine• Preinstalled – on every

machine• Experimental – clear

policy on responsibility. Troubles with experimental software may degrade service priority

• Admin – only for SAs

What Form• Disk images (see ISO)• Documents• Installers

Local Replication

• Multi-building campus• Multi-location company

– Issue is bandwidth limitation versus disk storage capacity

• Consider using a synchronization tool so you have an equivalent depot at each location.

• Tada! – No need to back up replication sites.– Remember, cost of disk drives is normally a

small fraction of the cost of disk storage. This is an exception to that rule.

Note on Bandwidth Bloat• It’s easy to think, “We have a fat pipe going

that direction”• Sort of like “We can just put it on the credit

card”• Eventually the pipe will fill up, and expanding

it will be expensive• As a loan company once began their ads:

“Never borrow money needlessly”• You might treat it like technical debt: A way to

save time/money now, which you’ll have to deal with when the pipe fills up.– Or it’ll be forgiven if you get a bigger pipe anyhow

Commercial Software

• Address licensing issue• Does the same person manage

licensing that manages your depot or distributions system?

• Is that really a site license?– Or is it a quantity discount?

Second-Class Citizens

• Reduced service priority• Candidates for first-class citizens

– If there is a conflict, consider the possibility that this software needs to be elevated to first-class status

Today’s World

• This is probably part of your client management system

• Updates should be first installed on your image master computer

• Questions remaining:– Do you enable fast-track updating for

patches from vendors?– Do you give control to third-party

vendors?

Conclusion

• A software depot probably exists.– You just haven’t organized it.– The Internet is one.

• It is possible to over-organize a software depot.– Higher costs than you expected.– Rogue depots crop up.

• Develop a clear, simple-as-possible plan.– As in: Simple for the users

• Be aware that the plan is based on people.…and your people will change!

• Bandwidth bloat can come from technical debt