Great - Thanks Islam
As it happens our team is in the process of reviewing the productisation of
these tools.
I updated the installation information for IMG over the past few days.
https://meego.gitorious.org/meego-infrastructure-tools/imger/blobs/skynet/doc/INSTALL
Could you perhaps try again using that information?
IMG does need a little care and attention - it's in the process of being
refactored to better fit to our CI automation and we've not tested it in a
scaled up deployment .. yet.
I hope you don't mind .. I've cc'ed: [email protected]
I think it is the best place to have this discussion:
http://lists.meego.com/listinfo/meego-distribution-tools
David
On 15/07/11 06:24, [email protected] wrote:
Hello,
Great to see some interest in our tools by your OBSLight for MeeGo, as
mentioned in recent emails on the mailing lists, IMHO there is quite a
lot of overlap between the MINT and OBSLight projects.
It seems you have mixed the new and old versions of IMG code and
instructions.
The configuration file you attached works with the new code living in
the skynet branch :
http://meego.gitorious.org/meego-infrastructure-tools/imger/commits/skynet
and to get that working use the instructions in :
http://meego.gitorious.org/meego-infrastructure-tools/imger/blobs/skynet/doc/INSTALL
There is a packaged and somewhat tested version at :
https://build.pub.meego.com/package/show?package=imager&project=Project:MINT:Testing
Also David Greaves recently tried imager our and got it to work, I have
CC'ed him in this email so he can help, and because I am on vacation
abroad :)
On 07/14/2011 06:09 PM, ext Vladimir Hellmann wrote:
Dear Sir or Madame,
My name is Vladimir Gustav Hellmann and I am working in France
in the "OBSLight for MeeGo" project togehter with my colleague Mr. Ronan
Le Martret and*
Mr. Dominique Le Folle (Intel) *
as project leader.
My login on gitorious is "gustav".
I have succesfully downloaded the IMGER sources you've submitted on
https://meego.gitorious.org/meego-infrastructure-tools/imger
Following the instructions on
http://wiki.meego.com/Release_Infrastructure/IMG
I have installed the KVM ( and MIC2 ...) and then created an*
/etc/imger/img.conf **file* which is joined to this mail.
When launching the*img-amqp* via
*/etc/init.d/img-amqp start*
I have got the following error message:
____________________
IOError: Socket closed
____________________
The sections [worker], [amqp] and [build_image] have been
added to the file img.conf as follows:
________________________________________________
[worker]
base_url = http://127.0.0.1
base_dir = /home/hellmann/ks_files
post_creation =
use_kvm = yes
mic_opts =
mic_cache_dir = mycache
img_home =
img_tmp =
reposerver =
templates_dir =
[amqp]
amqp_host = amqp
amqp_user = amqp
amqp_pwd =
amqp_vhost =
[build_image]
daemon =
logfile =
pidfile =
runas_user = hellmann
runas_group = users
____________________________________________________
Could you please give me a hint to resolve the problem?
Should I modify the*img.conf* file or does the problem come from
the*img-web/Django part*?
Does the problem eventually come from *RabbitMQ*?
When launching
*/etc/init.d/img-web start*
I have got a similar error message.
Thank you very much in advance for your answer/hint.
In exchange we may regularly inform you about the advances
of our project "OBSLight fro MeeGo" if you are interested.
With best regards,
Vladimir Gustav Hellmann
Mail:[email protected]<mailto:mail%[email protected]>
--
"Don't worry, you'll be fine; I saw it work in a cartoon once..."
_______________________________________________
MeeGo-distribution-tools mailing list
[email protected]
http://lists.meego.com/listinfo/meego-distribution-tools
