ArchitectureRepository

This page is intended for developers of AmbariKave. For users, return to Home.

This page introduces the repository layout (repos.kave.io).

Repository

So we've got a lot to do here. We have a couple of responsibilities and levels of architecture we go to look at.

• How are we going to install files from our own projects?
• How are we going to get files from different installers?
• Are we allowed to?
• Should we use rpm's, plain files or a mixture?
• How do we manage versions of the Kave and of the pieces of software we depend on?

Initial proposal

/OS/MAIN_COMPONENT/MAIN_COMPONENT_VERSION/PACKAGE-VERSION.tar.gz

Which will look something like this:

• centos6/
  • KaveToolbox/
    • 1.0/
      • eclipse-java-luna-SR1a-linux-gtk-x86_64.tar.gz
  • AmbariKave/
    • 1.0-Beta/
      • gitlab-7.6.2_omnibus.5.3.0.ci.1-1.el6.x86_64.rpm
      • jboss-as-7.1.1.Final.zip
• centos7/
  • KaveToolbox/
    • 1.0/
      • eclipse-java-luna-SR1a-linux-gtk-x86_64.tar.gz
  • AmbariKave/
    • 1.0-Beta/
      • gitlab-7.6.2_omnibus.5.3.0.ci.1-1.el6.x86_64.rpm
      • jboss-as-7.1.1.Final.zip
• noarch/
  • KaveToolbox/
    • 1.0/
      • kavetoolbox-1.0.tar.gz

Reading files from there

repos.kave.io , use wget

Getting Access to place files there

1. Create a public-private ssh key pair
2. Place the public key into the repos user's authorized_keys on the server
3. Use scp or winscp to dump the file into /opt/repos/web/... (softlink repo in the home directory)
4. ssh into the machine and use the ./setwww_permissions.py repo (to fix the permissions of the files you just sent)