Loading Profile...
Creating packages that simply do an apt-get on Ubuntu
Some of the packages that I want to install are available on Ubuntu with a simple call to apt-get. I know I can do the "apt-get install" once I log into my running server via ssh. But, is there a standard way of creating an elastic server package that simple installs a bunch of .debs using apt-get? I am thinking of things like python, blas/lapack/atlas, etc. that are a pain to build and Ubuntu already has.
2
people have this question
I have this question, too!
Tell me when someone answers.
The more people who ask this question, the more it gets noticed.
The more people who ask this question, the more it gets noticed.
Create a customer community for your own organization
Plans starting at $19/month
-
Inappropriate?Hi Brian,
Thanks for both questions. Elastic Server fulfills a couple roles: 1) as a "meta packaging" system - letting you pull together disparate packages from different worlds; things from the distros, things from the rubygems world, the maven world, plain old java world, 2) as a way to target the bill of materials you pull together to a specific execution context; vmware, xen, ec2, eucalyptus, etc..
Within the packaging world there are things in the distros that are very operating system library specific (apache2 for example) and things that are unlikely to be OS specific (most rubygems for example). We are working to make the Elastic Server builder and the import process increasingly sensitive and useful with respect to those distinctions.
SO...to answer your question..... :-)
We internally have a tool that lets us, as ES administrators, point to an upstream mirror and import a package. (The reason we import a copy is that even mirrors change over time and we want you to be able to re-build your vm in the future with that specific package.)
Ideally we get everything setup in a way that we can just let you reference upstream packages in a URI type format and away we go. But we aren't quite there yet.
Here is the approach we have been trying to follow in the background. We use our internal admin capabilities to get what we think of as "foundation technologies" in place; apache, tomcat, appserver, mysql, postgres, ruby, java, python, perl, tcl, erlang, common os utilities, etc. in place. And then have people use one of the "Create Package" techniques for yet another package that runs within one of those environments.
So until we make the admin function of "point to upstream mirror" available to all, we are happy to take requests for getting core upstream mirror things visible in ES. For the layer of packages on top of those foundations, I would for now use the "Create Package" type of "run-on-boot-script", choosing the "run on first boot only" option, as the place to stick some of the apt-gets.
Please respond here or email us at support (at) cohesiveft.com with your upstream wish list.
Thanks,
Pat Kerpan
CohesiveFT
-
Inappropriate?Thanks this help. I will let you know about what "core" packages we need when we get to actually moving forward with this.
But, it guess it is easy enough to do the run-on-boot-script approach. -
Inappropriate?Would the following also be a workaround (even if somewhat harder than the above)?
- Use a temporary outboard instance to do apt-gets on top of a base OS image.
- Figure out the directory paths installed by each package.
- Use ElasticServer packages of type "Filesystem Tree Archive" to capture the installed packages from the temporary instance. -
Inappropriate?Debian Lenny: In trying to do "apt-get install" or "aptitude install", I receive warnings from SecureApt complaining about unverified or untrusted packages. Because these warnings also request user confirmation to proceed, the script does not complete when run-on-first-boot only.
I believe the root cause is due to the fact that there is a CFT repo listed in /etc/apt/sources.list, and no trusted key as been added for this repo. Can I either (a) remove the CFT repo, or (b) install a CFT key so that this repo will be trusted?
I’m frustrated
EMPLOYEE
