On 01/02/2012 04:35 AM, Tomas Sedovic wrote:
On 12/28/2011 06:29 AM, Hugh Brock wrote:
> Hello Balu.
> You will have to import your existing AWS images in order to see them
> in the Aeolus UI. We want to fix this in a future release (i.e. have
> an automatic import feature) but for now the import process is manual.
> Hope this helps,
> Hugh Brock
> On Dec 28, 2011, at 12:17 AM, balan rp<balutvm2008(a)gmail.com> wrote:
>> Hi Team,
>> In my organization, we are using Amazon cloud services.I was
>> evaluating the cloud management systems and installed the Aeolus
>> package for evaluation.
>> I successfully installed the software on Fedora 16 but i had a doubt
>> while setting up the configurations.The documentation clearly explains
>> method to upload an image to AWS and we can see them of Aeolus
>> console.But i couldn't see the instances which are present on my AWS
>> My intention is to view my existing instances in AWS also deploying
>> and managing new one's using Aeolus.
>> Please could you let me know whether its possible?
Regarding instances, the situation is similar.
Right now we don't show instances that we didn't launch. We keep track
of certain metadata that isn't available to us from instances not
launched by us.
I'm not sure what's the plan regarding this feature but I recon it's
something people would like to have.
Yes, this is a slightly tricky issue to implement (if we want to do so).
We can't list all instances, since there's really no notion that
conductor has exclusive use of the account. A given provider account may
be accessed by two different conductor instances, so we'd really want
each conductor to only see instances that it started. It may be that we
would want to provide something similar to the "image import" process --
where we currently allow conductor to use previously-existing images
that it didn't build. The "instance import" feature could allow a
provider account admin to let conductor know about instances in the
account that conductor didn't start. With our current model, this would
also require assigning these instances to a pool in an environment that
uses the provider account, and an owner (presumably the owner would be
the importing admin user). We'd also need to import the image that the
instance is running, so this image would show up as an "imported image"
in the same way as it would if the image was imported directly.
That said, I have no idea whether this feature is on the radar as
something that's been asked for. I know it doesn't exist now, and nobody
has done any work to put it in place.