-
Notifications
You must be signed in to change notification settings - Fork 3
Description
In following the directions for modifying the Python roll, I encounter the following error message in step 2 after successfully completing step 1.
[python]$ sudo make download
Makefile:75 Rolls.mk: No such file or directory
make: *** No rule to make target 'Rolls.mk'. Stop.
What is the proper build tree topology (where should base
be relative to python
) and what environment variables should I have set? I am attempting these steps on a functioning Rocks 6.2 frontend as sudo.
The directions I have for modifying the Python roll are as follows:
-
Make and update the rocks-devel rpm Process (on your frontend) (5 minutes)
git clone https://github.com/rocksclusters/base.git
cd base
git checkout ROCKS_6_2_UPDATES
cd src/devel
make rpm
cd ../..
make createlocalrepo
yum update -c yum.conf rocks-devel -
Verify that you can remake the python roll (15 minutes)
git clone https://github.com/rocksclusters/python.git
cd python
make download
make roll
make createlocalrepo
yum -c yum.conf check-update
(you should see only the a usersguide update (this is because the rocks version number went from 6.2 -> 6.2.1 in the rocks-devel rpm)
- Update python3.
cd src/python-3
download the tar.gz file of the version you really want.
edit version.mk to reflect the updated version. (make sure there is no trailing space on the VERSION = line)
(optionally) edit Makefile to reflect the any configure changes you would want to make when building
make rpm <-- creates the updated opt-python-3 rpm
When your rpm builds without error, you complete remake the roll or simply "reroll" it.
cd ../.. (top level of the python roll directory)
make reroll
You can then create a localrepo (As above) and check for the update. Assuming all of that works, you should add the roll to your cluster
rocks add roll python*iso clean=y
cd /export/rocks/install
rocks create distro
yum clean all
yum update
Once you've added the roll to your distribution, you can reinstall nodes OR ask them to update.
rocks run host compute "yum clean all; yum -y update"