To Whom It May Concern,
Whilst I was using the application, I came to the realization that some of the links in the footer served no purpose. They went nowhere, and there wasn't even an apparent place that they *should* go.
I entered https://bugzilla.redhat.com/show_bug.cgi?id=787280 and proceeded to remove the links and the associated entries in en.yml.
I thank you for your kind consideration of this matter.
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.
Two things I think would be well-worth pursuing:
a.) Actual OpenStack support. We (ostensibly) support Rackspace today,
so this may be relatively straightforward. (Or those could be famous
last words.) I think this is important for two reasons. The first is
that OpenStack is a popular private-cloud offering, so we should support
it alongside vSphere and RHEV. (It might also help those who keep trying
to compare us *to* OpenStack understand that we occupy different
The second is that OpenStack powers several public clouds, and it would
be fantastic if EC2 wasn't the only public cloud we supported. Obviously
Rackspace's offering is using OpenStack or something extremely close.
But Internap's Open Public Cloud and HP's new HP Cloud are powered by
OpenStack, so OpenStack support would get us compatibility with multiple
public cloud providers.
b.) Smarter matching of where we launch instances. I don't think this
will be something we get right the first time -- it seems like there are
a bunch of criteria that different people will weigh differently. But I
think that's all the more reason to start out with something now and
iterate over it. Our 'priority' concept helps somewhat, but it still
feels pretty constrained. It feels like we've worked to make it easy to
launch an instance in the cloud of your choosing (a noble enough goal, I
admit), as opposed to allowing you to launch an instance and let
Conductor do something intelligent on its own.
What else do you think we should try to focus on?
This patch adds the breadcrumb partial layout to all admin pages. This results in some weird rounded edges immediately below the breadcrumb section, but Angus agrees that those can be worked out after the breadcrumbs are visible.
This is really a speculative fix, as I could not reproduce the described issue. It appears that the most likely explanation is an image which failed to import fully, so I modified the code slightly to clean up better in that case.
I get 3 failing Cucumber tests with or without this patch.