On Wed, 20 Dec 2023 19:57:39 +0000 smooney@redhat.com wrote:
it woudl proably be better to take a step back then and come up with a design propsoal and talks to teh qa team about your objectives. i dont think devstack uses spec but tis would be better to define the exact set of goals and agree with the maintianers if its in scope before trying to make large changes.
Honestly I hoped just to sprinkle a few reviews. Rolling a whole spec just to add a couple of new fields for credentials is going to create a whole lot of delay. You know how slow they go in.
You are right, of course, but what a drag. you dont nessiarly need a spec. you just need to socialise the aim with the peopel that have review rights so that
On Wed, 2023-12-20 at 16:47 -0600, Pete Zaitcev wrote: they are aware of the work your doing and why. that will help them recommend how to do it correctly and speed up the review process. part of the reason that reviews linger sometimes is that we dont know why someone has proposed it or even that they have propsed it. so grouping a set of related changes into a gerrit topic and then reaching out on irc to the maintaienr or starting a email thread similar to this but where you lay out the problem description and why you want to chagne it can help land your code much faster. devstack is a developmet tool so while there is no direct need to have authenticated memcache access as it is not for use in production there is no reason not to if its simple to enable across all distos that are supported and can be used to test that functionaltiy in oslo.cache for example. if that your over all goal, ensuring that openstack can correcctly use memcahce with auth enabled then enhancing devstack to support that make sense to me.
-- P