Open Stack

Hi Igor,

The repo directory its is too large to fit in a docker container and
work reliably. It is just a symlink inside the repo storage container
from host:/var/www/nailgun to repo-container:/repo. This /repo folder
is shared out to containers, such as nginx, and then symlinks are
created for each subdir in /var/www/nailgun. If you need more links
without rebuilding your environment, you would need to symbolically
link your new repository from /var/www/nailgun/newlink to
/var/lib/docker/devicemapper/mnt/$(docker nspect -f='{{.ID}}'
__containername__)/rootfs/repo. (replace __containername__ with the
container you're trying to work on).

I hope this helps.

-Matthew

On Sun, Jun 15, 2014 at 2:32 PM, Igor Kalnitsky <ikalnitsky at mirantis.com> wrote:
> Hello fuelers,
>
> I'm working on openstack patching for 5.1 and I've met some problems.
> The problems I've met are in repos/puppets installing process.
>
> The problems are almost same, so I describe it on repos example.
>
> The repos data are located in /var/www/nailgun. This folder is mounted
> as /repo into Nginx container. Nginx container has own /var/www/nailgun
> with various symlinks to /repo's content.
>
> So the problem is that we need to add symlinks to newest repos in Nginx
> container. How this problem should be solved? Should our fuel-upgrade
> script add these symlinks or we'll ship new docker containers which
> already contain these symlinks?
>
>
> Thanks,
> Igor
>
> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>