Hi Justin and Michal,
Thanks for your infos. It works fine when we export https_proxy
environment variable in /etc/init.d/deltacloud-ec2-us-east-1 file.
Our Amazon account is now created in Aeolus.
We want now to create a deployable following the guide at :
http://justinclift.fedorapeople.org/aeolus/configuring_aeolus.html
Unfortunately, downloading the template using the command :
wget
http://www.aeolusproject.org/templates/fedora_14_x86_64.tpl
returns the following error :
--2011-08-10 17:02:25--
http://www.aeolusproject.org/templates/fedora_14_x86_64.tpl
Connexion vers 129.182.77.31:80...connecté.
requête Proxy transmise, en attente de la réponse...404 Not Found
2011-08-10 17:02:26 ERREUR 404: Not Found.
Bad luck!! The url given in the guide does not work. Any idea?
Michel
De : Justin Clift <jclift(a)redhat.com>
A : Michal Fojtik <mfojtik(a)redhat.com>, michel.gauthier(a)bull.net
Cc : aeolus-devel(a)lists.fedorahosted.org
Date : 10/08/2011 15:44
Objet : Re: Proxy Aeolus Conductor 0.3.0
On 10/08/2011, at 10:21 PM, Michal Fojtik wrote:
On Aug 10, 2011, at 12:15 PM, michel.gauthier(a)bull.net wrote:
> We have installed Aeolus 0.3.0 on a fedora14 x86_64 platform.
> We want to create a provider account for ec2 using Conductor web
interface
(our ec2 account already exists on ec2 portal).
> Unfortunately, we receive the following error message :
> NameError - uninitialized constant Deltacloud::BackendError:
> ././lib/deltacloud/drivers/ec2/ec2_driver.rb:654:in
`valid_credentials?'
> ././server.rb:71:in `GET /api/?'
>
> We need a proxy to go to the internet network from our platform and we
think
that this error is due to the fact that the Conductor component has
no knowledge of the proxy.
> How can we configure the Conductor component to take the proxy
value
into account?
First of all the support for HTTP proxy is not yet pushed into
http_connection
gem
we're using for HTTPS communication with Amazon EC2 API.
So in order to get it work, you need to install 'manualy' my fork[1] of
this gem which
has support for 'http_proxy' environment variable. To do that
you need:
$ wget
http://mifo.sk/tmp/http_connection-1.4.1.gem
$ gem uninstall http_connection
$ gem install http_connection-1.4.1.gem --local
After that you need to export the 'https_proxy' variable. The best place
to do that
will be probably the Deltacloud API init.d script
(/etc/init.d/deltacloud-core) where you
need to put:
export https_proxy="YOUR_PROXY_ADDRESS:PORT"
After that, restart deltacloud-core service and you should be able to
access EC2
API through
proxy.
Cool, thanks Michal. :)
Heh, we'll have to add instructions for "configuring proxy support" to the
new Getting Started
Guide in development.
With the Aeolus 0.3.0 case, the script to modify won't be
/etc/init.d/deltacloud-core though.
The 0.3.0 release of Aeolus is still using individual start up scripts for
each provider. So,
Michel will need to add the "export https_proxy=XXXX" bit to the
deltacloud-ec2-* init.d scripts
instead. (then restart them)
As an additional thought, this might be useful:
http://justinclift.fedorapeople.org/aeolus/configuring_aeolus.html
It's a development snapshot of the Getting Started Guide written for
Aeolus 0.3.0, from yesterday.
Pages 5 onwards are outdated, written for the previous release of Aeolus,
so ignore those.
Everything before that though, is up to date.
Does that help?
Regards and best wishes,
Justin Clift
--
Aeolus Community Manager
http://www.aeolusproject.org