Brainstorming tasks for next sprint
Matt Wagner
matt.wagner at redhat.com
Wed Feb 22 15:55:28 UTC 2012
On Mon, Feb 13, 2012 at 04:06:24PM -0500, Matt Wagner wrote:
> Hi all,
>
> As we start to wrap up bug-fixing, I was hoping to get a conversation
> going about what we need to tackle in upcoming sprints.
A few more, if we're up for a bit more adventure:
- Work with Red Hat's product team to see if we can get Cloud Forms and
Conductor upstream to have a common set of names. We NACKed upstream
the names they are using in Cloud Forms Cloud Engine, but this leaves
us in a weird state of having the two versions of the same code base
calling things by two different names. As someone with a foot in both
camps, this is incredibly confusing.
- Make our interface to iwhd's API less-sucky, for lack of a more
technical term. The image list page takes 5+ seconds[1], because it's
still running thousands of API calls to get the information. I'm not
sure of the right course of action here, but I'm pretty sure status
quo is not it. Maybe we could work with them to get the API to fit
our needs better. Maybe we could talk directly to Mongo. Maybe we
could think about caching information locally, or just becoming the
canonical store for images.
- Give some serious thought to usability of our app. It started out
well-organized, but I think we've managed to make a mess of it. I work
on Conductor every day and even I sometimes have to poke around to
find where things live. This is deliberately kind of open-ended, but
I don't think I'm the only one who finds it much more confusing than
it needs to be.
-- Matt
[1] It grows considerably depending on the number of images that are
stored, but I have about 30 images now.
More information about the aeolus-devel
mailing list