Hi,
Thanks everyone. I will take a look to the containers facilities.
Best regards,
Remy
Le 06/07/2016 20:41, [email protected] a écrit :
Elias,
Is using Docker containers an option for you? You’ll find the user
experience much better (on Ubuntu/Debian for sure) with
OMSA-in-a-container than installing directly on the OS. Please see here:
https://hub.docker.com/r/jdelaros1/openmanage/
If you are new to containers then there will be a small learning
curve. But once you’re up and running, using the OMSA image will be
very easy. This container image is not officially supported, but then
again OMSA on Ubuntu is not supported either so you have nothing to
lose (and lots to gain).
https://docs.docker.com/engine/installation/linux/ubuntulinux/
*Jose De la Rosa*
*Linux Engineering***
*Dell****| **Enterprise Solutions Group***
*From:*linux-poweredge-bounces-Lists *On Behalf Of *Elias Abacioglu
*Sent:* Wednesday, July 6, 2016 8:35 AM
*To:* Remy Dernat <[email protected]
<mailto:[email protected]>>
*Cc:* linux-poweredge-Lists <[email protected]
<mailto:[email protected]>>
*Subject:* Re: [Linux-PowerEdge] OMSA broken package Ubuntu Trusty
I would say apt-get dist-upgrade( is defacto standard. I use aptitude
safe-upgrade(which almost like apt-get dist-upgrade).
There's nothing bad with running dist-upgrade.. the name is confusing,
but it doesn't upgrade trusty to xenial or similar (unless you take
some steps to do so).
apt-get upgrade doesn't upgrade kernel packages for instance.
Anyway, I've been struggling with this myself.
Since Dell doesn't know how to make working deb packages first you
have to purge your all srvadmin packages.
Something like this
chmod +x /opt/dell/srvadmin/{bin,sbin}/*
find /opt/dell/srvadmin/lib64/ -name '*.sh' |xargs chmod +x
sudo aptitude purge -y srvadmin-base srvadmin-deng srvadmin-hapi
srvadmin-omacore srvadmin-idracadm7 srvadmin-omilcore srvadmin-omacs
srvadmin-isvc srvadmin-xmlsup srvadmin-ominst srvadmin-omcommon syscfg
The order of which you remove packages seems to matter since you can
end up in the condition where you've removed the package that got some
script that is needed by some others package prerm or postrm script.
I like to use purge instead of remove since I don't have any custom
settings..
Then start with installing something like this..
apt-get install srvadmin-base
# this is needed because some srvadmin packages doesn't make their
binaries or scripts executable.
# its good practice to run these two commands between all srvadmin
packages you install until dell fixes the deb packages.
chmod +x /opt/dell/srvadmin/{bin,sbin}/*
find /opt/dell/srvadmin/lib64/ -name '*.sh' |xargs chmod +x
apt-get install srvadmin-omcommon
chmod +x /opt/dell/srvadmin/{bin,sbin}/*
find /opt/dell/srvadmin/lib64/ -name '*.sh' |xargs chmod +x
apt-get install syscfg
chmod +x /opt/dell/srvadmin/{bin,sbin}/*
find /opt/dell/srvadmin/lib64/ -name '*.sh' |xargs chmod +x
apt-get install srvadmin-storage-cli
chmod +x /opt/dell/srvadmin/{bin,sbin}/*
find /opt/dell/srvadmin/lib64/ -name '*.sh' |xargs chmod +x
If you got a gen13
apt-get install srvadmin-idracadm8
if you got a gen12
apt-get install srvadmin-idrac7
Restart srvadmin services.
/opt/dell/srvadmin/sbin/srvadmin-services.sh restart
The whole OMSA .deb experience is horrible! They would be better off
compiling everything with statically linked libraries and make a big
tarball of everything..
Good luck!
/Elias
--
Rémy Dernat
Ingénieur d'Etudes
MBB/ISE-M
_______________________________________________
Linux-PowerEdge mailing list
[email protected]
https://lists.us.dell.com/mailman/listinfo/linux-poweredge
