Install from source rather than centos+rdo
Install from source
Blueprint information
- Status:
- Complete
- Approver:
- Steven Dake
- Priority:
- High
- Drafter:
- Steven Dake
- Direction:
- Approved
- Assignee:
- Alicja Kwasniewska
- Definition:
- Approved
- Series goal:
- Accepted for liberty
- Implementation:
- Implemented
- Milestone target:
- liberty-2
- Started by
- Steven Dake
- Completed by
- Paul Bourke
Related branches
Related bugs
Sprints
Whiteboard
https:/
=======
pbourke:
As part of this bp we should likely also update requirements.txt from global to reduce chance of incompatibilities in the master tree:
SamYaple pbourke: where did we lang on pulling in upstream requirements for the projects? 13:46
SamYaple land* 13:46
pbourke umm 13:47
pbourke remind me of that discussion? 13:47
SamYaple https:/
SamYaple we can use that to update teh requirements.txt 13:47
SamYaple the reason being those only get more restrictive rather than less, so it is safe and we catch a few issues earlier 13:48
*** athomas has joined #kolla 13:48
SamYaple downstream projects always update based on that repo, but it takes a few days 13:48
pbourke so you mean you would like to grab the global-requirements from there before building each component? 13:50
SamYaple uh not quite 13:50
SamYaple hold on 13:50
SamYaple https:/
SamYaple cd /opt/kolla/
SamYaple that will update all the items in the requirements.txt file for keystone 13:52
SamYaple (not add new ones, just update existing since issue were encountered upstream) 13:52
pbourke ok. is that standard practice for consumers when installing components from source? 13:53
pbourke (openstack components) 13:53
SamYaple how many from source installs do you think people do :) 13:53
SamYaple i dont think there is a standard practice here 13:53
* pbourke shrugs 13:54
SamYaple but in any case it is a safe operation, it will only catch issues that didn't exist when the branch/tag was created due to new package versions
=======
pbourke:
I had started this as part of https:/
Wrt to the decisions outstanding mentioned above, some were discussed on IRC (logs, http://
1. What source format should we support i.e. tarball/egg/git repo/wheel/etc.
2. Should these be downloaded as part of the Dockerfile or using an external process and ADD'ed in.
Sam has quite a bit of experience in the various approaches and has a good argument for using tarballs, which are fetched *outside* of the image build process. However they are fetched can be flexible, the end result should be a tarball that is provided to the Dockerfile build process.
A key use case this provides is to apply a patch or ref change to a git repo, and build a tarball from that which can be plugged into the image build without having to change the Dockerfile. Another benefit includes not requiring external internet access for this part of the image build.
There are examples in the yaodu repo of this kind of thing that we should review and apply here (https:/
Gerrit topic: https:/
Addressed by: https:/
Keystone installation from source
Addressed by: https:/
Add source base container link for centos
Addressed by: https:/
Move declaration of TMPDIR to top of build-docker-image
Addressed by: https:/
Glance installation from source
Addressed by: https:/
Update centos-source-base from symlink to a real layer
Addressed by: https:/
Add new script to fetch tarballs for source installation
Addressed by: https:/
Glance installation from source
Addressed by: https:/
Add build from source for Heat
Addressed by: https:/
Add build from source for Magnum
Addressed by: https:/
Add build from source for Ceilometer
Addressed by: https:/
Add build from source for Barbican
Addressed by: https:/
Add build from source for Zaqar
Addressed by: https:/
Add build from source for Horizon
Addressed by: https:/
Add build from source for Nova
Addressed by: https:/
Add build from source for Neutron
Addressed by: https:/
Add build from source for Designate
Addressed by: https:/
Adding cinder source image
Addressed by: https:/
Add build from source for gnocchi
Addressed by: https:/
Add fedora base image for build from source
Addressed by: https:/
Add Ubuntu base image for build from source
Addressed by: https:/
Fedora - Install from source for Keystone
Addressed by: https:/
Fedora - Install from source for Cinder
Addressed by: https:/
Fedora - Install from source for Glance
Addressed by: https:/
Fedora - Install from source for Heat
Addressed by: https:/
Fedora - Install from source for Neutron
Addressed by: https:/
Fedora - Install from source for Magnum
Addressed by: https:/
Fedora - Install from source for Ceilometer
Addressed by: https:/
Fedora - Install from source for Nova
Addressed by: https:/
Fedora - Install from source for Horizon
Addressed by: https:/
Add build from source for Swift
Addressed by: https:/
Fedora - Install from source for Swift
Addressed by: https:/
Fedora - Install from source for Gnocchi
Addressed by: https:/
Fedora - Install from source for Designate
Addressed by: https:/
Add horizon source for oraclelinux
Addressed by: https:/
Remove tox -egenconfig since its not needed for cinder