Action development documentation out of date

[Honza Pokorny]

The action development workflow documentation in the tripleo-common README file doesn't work for containerized underclouds. It's not immediately clear what the new method is.

[Dougal Matthews (d0ugal)]

I don't have a containerised env to test and verify the exact commands, but this sounds like a good approach.

14:27 <thrash> d0ugal: One way would be to just mount a volume inside the container.
14:27 <thrash> d0ugal: that's the easiest way. I did that on a running containerized undercloud the other day.

[Dougal Matthews (d0ugal)]

14:29 <thrash> d0ugal: For instance, '-v $HOME/tripleo-common/tripleo_common:/usr/lib/python2.7/site-packages/tripleo_common'

[Toure Dunnon (toure)]

I am working on a similar issue with a new feature for stein which takes place on a containerized undercloud. I will take some notes once I iron out all the details for my dev environment, aka not hacked together to get something working.

[Steven Hardy (shardy)]

Some notes at https://etherpad.openstack.org/p/tripleo-rpm-container-image-notes which I created in response to https://bugs.launchpad.net/tripleo/+bug/1788414, which may actually be a duplicate (or perhaps a more general case) of this bug.

I suspect we can write a small helper script which does the following (see etherpad for details):

1. Clone source & cherry-pick any changes
2. Create dockerfile for images we want to rebuild with the source dir above ADD'ed & steps to install from source
3. Build & push the new image via a temporary tag
4. Figure out which images in the various paunch configs are affected (e.g should be updated)
5. Update them and re-run paunch in order for the relevant steps

[Juan Antonio Osorio Robles (juan-osorio-robles)]

Is this still an issue?

[Steven Hardy (shardy)]

Yes this is still an issue ref https://github.com/openstack/tripleo-common#action-development

We need to update that to reflect how you'd test in a containerized environment

IIRC there are options to pass a Dockerfile to the image prepare command, so we could use that, or the approach I described to manually rebuild the image and restart the container.