Open Stack

On 10/09/15 19:39, Gal Sagie wrote:
> Hi James,
> 
> I think that https://review.openstack.org/#/c/216021/ might be what you are
> looking for.
> Please review and see that it fits your requierment.
> Hopefully this gets approved for next release and i can start working on
> it, if you would like to join
> and contribute (or anyone in your team) i would love any help on that.

Thanks for the link; looks like a great feature. I'm not sure it is the
best fit for my use case though.

My user story is: Users can see human-readable security group
descriptions in Horizon because the security group model contains a
description field, but no such field exists for security group rules.
This makes it very confusing for users who have to manage complex
security groups.

I agree that one could encode descriptions as tags, but the problem I
see is that API consumers(Horizon, Users) would have to agree on some
common encoding.  For example... To expose a security group rule
description in Horizon, horizon would have to apply and read tags like
'description:SSH Access for Mallory'.

With a tags-based implementation, if a user wants the description for a
security group rule via the API, they have to get the security group,
then filter the tags according to whatever format horizon chose to
encode the description as.

This is in contrast to getting the description of a security group: Get
the security group and access the description attribute.

I think that resource tags are great, but this seems like a
non-intuitive workaround for a specific data model problem: Security
Groups have descriptions, but Security Group Rules do not.

Am I making sense?

Cheers,
James


> 
> Thanks
> Gal.
> 
> On Thu, Sep 10, 2015 at 8:59 AM, Armando M. <armamig at gmail.com> wrote:
> 
>>
>> On 10 September 2015 at 11:04, James Dempsey <jamesd at catalyst.net.nz>
>> wrote:
>>
>>> Greetings Devs,
>>>
>>> I'm very excited about the new RFE process and thought I'd test it by
>>> requesting a feature that is very often requested by my users[1].
>>>
>>> There are some great docs out there about how to submit an RFE, but I
>>> don't know what should happen after the submission to launchpad. My RFE
>>> bug seems to have been untouched for a month and I'm unsure if I've done
>>> something wrong. So, here are a few questions that I have.
>>>
>>>
>>> 1. Should I be following up on the dev list to ask for someone to look
>>> at my RFE bug?
>>> 2. How long should I expect it to take to have my RFE acknowledged?
>>> 3. As an operator, I'm a bit ignorant as to whether or not there are
>>> times during the release cycle during which there simply won't be
>>> bandwidth to consider RFE bugs.
>>> 4. Should I be doing anything else?
>>>
>>> Would love some guidance.
>>>
>>
>> you did nothing wrong, the team was simply busy going through the existing
>> schedule. Having said that, you could have spared a few more words on the
>> use case and what you mean by annotations.
>>
>> I'll follow up on the RFE for more questions.
>>
>> Cheers,
>> Armando
>>
>>
>>>
>>> Cheers,
>>> James
>>>
>>> [1] https://bugs.launchpad.net/neutron/+bug/1483480
>>>
>>> --
>>> James Dempsey
>>> Senior Cloud Engineer
>>> Catalyst IT Limited
>>> +64 4 803 2264
>>> --