| Version 1 (modified by , 13 years ago) (diff) |
|---|
Quattor Workshop - Strasbourg - 12-14/10/2011
TracNav
Table of Contents
Core Tools
SINDES2 - V. Lefebure
Main new features (see presentations at previous workshops)
- Based on Krb rather than a private CA/certificates.
- Unique API for human clients and machines
Jan left CERN in July but still doing some follow-up to help with the move to production at CERN
- 1st production cluster expected at Christmas
- Migration beginning of next year
Sources will be put in SF Quattor as soon as the code is considered ready for production.
Stijn: still using v1 at UGant.
- Same for Bruxelles grid site where it is mainly used for certificate delivery...
MS: not interested by PKI, already have a production Krb infrastructure
- Chose to add Krb encryption support in ncm-ccm and ncm-download
- Profile encrypted before sending it but stored plain text on the server
RAL: gave up with SINDES
- Will ncm-download with its new support of Krb as a replacement
Quattor Status at MS - N. Williams
MS is doing Quattor its own way... not using Quattor directly, Aquilon a layer above Quattor
- Quattor used underneath
- Aquilon providing many advanced features not found in other config DB implementation: personalities, archetype, template sandboxes for development/testing without interfering with production, multiple panc version support...
- archetype implemented as a pan loadpath
Figures
- 20K real machines managed with Aquilon
- 20K virtual machines, including VMware ESX servers using Quattor Remote Deployer (QRD)
- 50 NetApp servers using QRD too
- Some Windows management : pre-configuration (host name; IP config...) passed to Windows team
- No plan to go really further: Windows team relies on its own tools
- Everything managed from the same server
- Reusing QWG machine type concept but extending it (personnalities)
- Working on Hadoop configuration
Still wanting to open-source Aquilon and QRD but lack of time to do the code clean up.
Basically forked AII to fix the issues found.
Need to discuss how to streamline feeding MS contribution into the code mainstream.
Start an Aquilon section on Trac wiki...
Aquilon Appliance Walk-Through - N. Williams
Goal: enable an easier evaluation of Aquilon
- Installing Aquilon to evaluate it can be painful
- Can also be used to do development validation
- Allow to import an existing Quattor configuration
- Zero requirement on existinf infrastructure
Based on Ubuntu Turnkey distribution (intended to create appliances) + sqlite
- Provides interconnection with a datawarehouse using cdb2sql
- Web-based management interface to help creating/managing machines
- Written in Pylons
- ssh connection to appliance where Aquilon command line interface can be used
Several modes implemented using URLs
/reset: allow to reset Aquilon configuration and reinitialize it- 11 steps before installing the 1st machine : add an archetype, personality, os, define network parameters...
- Machine management
- 3 steps per machine: select machine HW, machine network config (including algorithm to allocate IP address), host associating a machine, an archetype, a personality, an OS version, build status...
Aquilon privilege management: 6 possible roles
Last version of the appliance not yet on SF... but soon!
Pan Compiler Update - C. Loomis
v9 is the actively developped version
- Currently 8.4.7 with deprecated features removed
- Main change is new options to fix annotation issues with namespaces
- Documentation reorganized: just one book merging previous documentations
- Simplified, streamlined code, no new feature (yet?)
- Migration to clojure: improved support for multithreading
- Is clojure licence (EPL 1.0, Eclipse) an issue?
Migration v8 to v9: use 8.4.7 with deprecrated feature warnings to identify problems
- Use relevant option to turn them into fatal errors
v9 release candidate available but not yet in SF (soon)
- Will be tagged as a release as soon as there is some feedback
QWG Templates
QWG Templates Update - M. Jouvin
See presentation.
StratusLab templates: not really part of the QWG templates (yet) but feedback from the community is welcome.
Monitoring Templates - R. Starink
Work in progress behind the scene...
Documentation available on the wiki.
UGant is using icinga and started with a previous version of Nagios templates: another fork...
- Need to see if we can avoid the cost of another future merge...
- icinga as a Nagios fork has a very similar configuration, check if there is the need for a new configuration component
- Need to identify the use cases that cannot be implemented by current QWG templates
Discuss on quattor-devel
Development Process
See Michel's presentation at last workshop: basically the same questions after almost 1 year of experience with SCRUM.
Scrum / standup meeting
- Agreemenent this is rather positive
- Weekly meeting should happen every week, whether Michel is available or not
- Weekly meeting should be on time: let's move it to 2:15 pm to increase the chance to start immediatly
- Meetings should remain short for everybody, not only for the late comers...!!!
- Add EVO connection into the reminder
- Have more formal planning/review of sprints and advertize sprint outcome on the mailing list
- Let's try 1 1/2 month sprint
People working on some developments need to let others know through a message to quattor-devel list or participation to standup meetings.
Monthly meeting
- Ask the general mailing list about the interest of the community
- If yes, propose to have a larger meeting for the sprint review meeting
- Plan them in advance and add an event in Quattor Indico area (and reference it on the wiki)
- Send a reminder 2 weeks in advance
Repository branching
- Difficult to use with SVN + old build tools: need to put some effort to make progress on the migration to new build tools and Git
- Not really a problem for QWG where trunk is really for work in progress
- As discussed at the last workshop, good candidates for migration are CCM-related things (ccm, ncm-cdispd, ncm-ncd, QuattorFS), AII and its plugins
- Encourage people who are contributing major changes to make a branch, as it has been done for
ncm-network- Use stand-up/review meetings to decide merging into trunk
