1 / 6

Conclusion

Conclusion. First “non-developers” Quattor tutorial Feedback: Quattor functionality, RFE, bug/features

johnna
Download Presentation

Conclusion

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Conclusion • First “non-developers” Quattor tutorial • Feedback: Quattor functionality, RFE, bug/features • CDB (cdbop: ‘open’ by default, ‘get’ to allow overwritting local files, ‘diff’ with user templates, ‘commit’ to say what is being updated, ACL’s for templates [developed, to be released with Quattor 1.1] etc) • SWRep (eg. allow to use latest versions with SPMA/SWRep, unified auth with CDB, simplify SW templates …) • Components (eg. Use nlist not list in cron, bug in accounts manpage, …) • APT install in installation guide • Feedback: for next tutorial • Less theory (PAN). PAN is a very powerful language, but only 10% of the functionality (and complexity) is needed as a regular site admin. • Possibility of running a dedicated PAN power user course • More focus on standard templates – some exercises • How to setup a site • Exercises with standard templates • More exercises in general (first day) • More feedback: • we will prepare and send you a questionnaire. • Mailing lists: Please subscribe to project-quattor@cern.ch.

  2. Next steps (I) • Wish list for Quattor • Documentation, in particular guidelines • Guidelines for writing components RFC -> circulate draft • Guidelines for schema (“pan user conventions”) RFC -> circulate draft. Add template naming conventions. • Standard templates – simplify the profile template (see Cal’s slides!) • Functionality (core and components) • Eg. 32bit compatibility packages for x86_64 platforms for SPMA/rpmt • Credential distribution (general problem) • ? • Schema for versioning and distributing Quattor/components/templates eg. for LCG-2 • Ideas, others • ? • Again, feedback is very important.

  3. Next steps (II) • How can you contribute? • The quattor dvp team manpower is not infinite. If you want to see changes, your contribution will be crucial to push forward! • Testing and bug reports • System components – enhancing, writing new ones • Core modules • Quattor @ LCG-2 -> LCG/Quattor Working Group – subscribe to QWG mailing list. • Quattor @ EGEE • Open discussion – Questions and Answers!

  4. Many thanks!We hope quattor will help you!

  5. http://quattor.org

  6. Welcome Back! • Please sit at the same place as yesterday! • We will continue working in pairs, connecting to the same nodes as yesterday. • If you don’t remember your node name, check the handouts. • If you don’t have the handouts anylonger… come and talk to us.

More Related