> -----Original Message-----
> From: Matt Wagner [mailto:[email protected]]
> Sent: Tuesday, December 04, 2012 11:26 AM
> On Mon, Dec 03, 2012 at 04:26:53PM +0000, Gavin Adams wrote:
> > Hi,
> >
> > I'm going though the most recent testing version Aeolus attempting to get
> a connection to our OpenStack cloud platform. I've installed aeolus-all from
> the testing repo, along with the deltacloud packages. I can use irb to connect
> to the launched daemon and successfully get responses back from our
> platform.
>
> Hi Gavin,
>
> Thanks for trying Aeolus! :)
[gadams]
Glad to check it out. I actually heard about while listening to a FLOSS Weekly
podcast, ironically coming from one of our data centers where we were installed
some cloud servers. Destiny. Plus it's better aligned to what I've seen as use
cases so far.
> OpenStack support is actually something we're working on implementing
> now. I had looked into this a few months ago, but it was largely blocked on us
> not being able to build/push/import images to OpenStack.
>
> Recently, Image Factory 2.0 was released, which added OpenStack support.
> We're actively integrating support for this into Conductor (through a new
> component, Tim[1]). I'm secretly hoping this will all be working by the end of
> the month. Once that starts to firm up into something usable, I'd be more
> than happy to work with you to test this in the wild.
[gadams]
Please do let me know when it hits a level where it's operational. I'll
continue to test with vSphere and Redhat so when I get to the point of
integrating OpenStack, I'll be (hopefully) more knowledgeable.
> > However, once configuring aeolus (ec2,mock) and tring to add a new
> provider, I get the same error mentioned back in a July thread:
> >
> > Cannot add the provider.
> > 1 error prohibited this Provider from being saved Url translation
> > missing:
> > en.activerecord.errors.models.provider.attributes.url.invalid_framewor
> > k
>
> As Firefox says when it starts after an unclean exit, "Well, this is
> embarrassing." Conductor hit an error ("translation missing") trying to show
> you the error it encountered. The invalid_framework error, though, comes
> up when it hits an unexpected exception talking to Deltacloud.
[gadams]
I'll --verbose deltacloudd and see if there's anything else that comes up.
>
> > The deltacloudd logs the standard 401 message (this is before credentials
> are created):
> >
> > 127.0.0.1 - - [03/Dec/2012 10:52:52] "GET /api HTTP/1.1" 401 - 0.0073
>
> I'm a little confused by this one, though this isn't an area of the code I
> work
> on, so it's slightly unfamiliar territory for me. The fact that it occurs
> before
> you're able to save the Provider is a little confounding, since I didn't
> think any
> credentials were required at this point.
[gadams]
My research on redmine showed something similar where as long as a 401 was
returned that should be okay (at that point). Again, maybe something more from
the logging will help out.
> While I'm not sure about the specific error you're encountering, there is
> indeed an overall functionality issue here as we work to finish up proper
> OpenStack support. I'm hoping it's something that will be in place relatively
> soon, though -- a few of us are working now on getting Tim and Image
> Factory 2.0 working with Conductor, and then it should (knock on wood!) be
> as simple as knocking out a couple of the bumps in the road I noted in my
> ancient blog post[2] on the matter.
>
> If the present incompleteness isn't too repulsive, I'd be happy to keep you in
> the loop as we work on this. It would certainly be beneficial to be able to
> test
> this on a 'real' OpenStack setup, versus me testing it against a single
> OpenStack box on my LAN.
[gadams]
Please do keep me, or at least this list, posted. Once it gets to a point where
functionality is ready, I'll give it a go. Y'all keep up the great work on this!
Regards,
--- Gavin Adams ([email protected])
