| | 1 | = Quattor Workshop - Strasbourg - 12-14/10/2011 = |
| | 2 | [[TracNav]] |
| | 3 | |
| | 4 | [[TOC(inline)]] |
| | 5 | |
| | 6 | [https://indico.cern.ch/conferenceTimeTable.py?confId=134032#all.detailed Agenda] |
| | 7 | |
| | 8 | |
| | 9 | == Core Tools == |
| | 10 | |
| | 11 | === SINDES2 - V. Lefebure === |
| | 12 | |
| | 13 | Main new features (see presentations at previous workshops) |
| | 14 | * Based on Krb rather than a private CA/certificates. |
| | 15 | * Unique API for human clients and machines |
| | 16 | |
| | 17 | Jan left CERN in July but still doing some follow-up to help with the move to production at CERN |
| | 18 | * 1st production cluster expected at Christmas |
| | 19 | * Migration beginning of next year |
| | 20 | |
| | 21 | Sources will be put in SF Quattor as soon as the code is considered ready for production. |
| | 22 | |
| | 23 | Stijn: still using v1 at UGant. |
| | 24 | * Same for Bruxelles grid site where it is mainly used for certificate delivery... |
| | 25 | |
| | 26 | MS: not interested by PKI, already have a production Krb infrastructure |
| | 27 | * Chose to add Krb encryption support in ncm-ccm and ncm-download |
| | 28 | * Profile encrypted before sending it but stored plain text on the server |
| | 29 | |
| | 30 | RAL: gave up with SINDES |
| | 31 | * Will ncm-download with its new support of Krb as a replacement |
| | 32 | |
| | 33 | |
| | 34 | === Quattor Status at MS - N. Williams === |
| | 35 | |
| | 36 | MS is doing Quattor its own way... not using Quattor directly, Aquilon a layer above Quattor |
| | 37 | * Quattor used underneath |
| | 38 | * 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... |
| | 39 | * archetype implemented as a pan loadpath |
| | 40 | |
| | 41 | Figures |
| | 42 | * 20K real machines managed with Aquilon |
| | 43 | * 20K virtual machines, including VMware ESX servers using Quattor Remote Deployer (QRD) |
| | 44 | * 50 NetApp servers using QRD too |
| | 45 | * Some Windows management : pre-configuration (host name; IP config...) passed to Windows team |
| | 46 | * No plan to go really further: Windows team relies on its own tools |
| | 47 | * Everything managed from the same server |
| | 48 | * Reusing QWG machine type concept but extending it (personnalities) |
| | 49 | * Working on Hadoop configuration |
| | 50 | |
| | 51 | Still wanting to open-source Aquilon and QRD but lack of time to do the code clean up. |
| | 52 | |
| | 53 | Basically forked AII to fix the issues found. |
| | 54 | |
| | 55 | Need to discuss how to streamline feeding MS contribution into the code mainstream. |
| | 56 | |
| | 57 | Start an Aquilon section on Trac wiki... |
| | 58 | |
| | 59 | === Aquilon Appliance Walk-Through - N. Williams === |
| | 60 | |
| | 61 | Goal: enable an easier evaluation of Aquilon |
| | 62 | * Installing Aquilon to evaluate it can be painful |
| | 63 | * Can also be used to do development validation |
| | 64 | * Allow to import an existing Quattor configuration |
| | 65 | * Zero requirement on existinf infrastructure |
| | 66 | |
| | 67 | Based on Ubuntu Turnkey distribution (intended to create appliances) + sqlite |
| | 68 | * Provides interconnection with a datawarehouse using cdb2sql |
| | 69 | * Web-based management interface to help creating/managing machines |
| | 70 | * Written in Pylons |
| | 71 | * ssh connection to appliance where Aquilon command line interface can be used |
| | 72 | |
| | 73 | Several modes implemented using URLs |
| | 74 | * `/reset`: allow to reset Aquilon configuration and reinitialize it |
| | 75 | * 11 steps before installing the 1st machine : add an archetype, personality, os, define network parameters... |
| | 76 | * Machine management |
| | 77 | * 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... |
| | 78 | |
| | 79 | Aquilon privilege management: 6 possible roles |
| | 80 | |
| | 81 | Last version of the appliance not yet on SF... but soon! |
| | 82 | |
| | 83 | |
| | 84 | === Pan Compiler Update - C. Loomis === |
| | 85 | |
| | 86 | v9 is the actively developped version |
| | 87 | * Currently 8.4.7 with deprecated features removed |
| | 88 | * Main change is new options to fix annotation issues with namespaces |
| | 89 | * Documentation reorganized: just one book merging previous documentations |
| | 90 | * Simplified, streamlined code, no new feature (yet?) |
| | 91 | * Migration to clojure: improved support for multithreading |
| | 92 | * Is clojure licence (EPL 1.0, Eclipse) an issue? |
| | 93 | |
| | 94 | Migration v8 to v9: use 8.4.7 with deprecrated feature warnings to identify problems |
| | 95 | * Use relevant option to turn them into fatal errors |
| | 96 | |
| | 97 | v9 release candidate available but not yet in SF (soon) |
| | 98 | * Will be tagged as a release as soon as there is some feedback |
| | 99 | |
| | 100 | == QWG Templates == |
| | 101 | |
| | 102 | === QWG Templates Update - M. Jouvin === |
| | 103 | |
| | 104 | See presentation. |
| | 105 | |
| | 106 | StratusLab templates: not really part of the QWG templates (yet) but feedback from the community is welcome. |
| | 107 | |
| | 108 | === Monitoring Templates - R. Starink === |
| | 109 | |
| | 110 | Work in progress behind the scene... |
| | 111 | |
| | 112 | Documentation available on the wiki. |
| | 113 | |
| | 114 | UGant is using icinga and started with a previous version of Nagios templates: another fork... |
| | 115 | * Need to see if we can avoid the cost of another future merge... |
| | 116 | * icinga as a Nagios fork has a very similar configuration, check if there is the need for a new configuration component |
| | 117 | * Need to identify the use cases that cannot be implemented by current QWG templates |
| | 118 | |
| | 119 | Discuss on quattor-devel |
| | 120 | |
| | 121 | |
| | 122 | == Development Process == |
| | 123 | |
| | 124 | See [/wiki/Meetings/Workshops/20110316#DevelopmentProcessDiscussion Michel's presentation] at last workshop: basically the same questions after almost 1 year of experience with SCRUM. |
| | 125 | |
| | 126 | Scrum / standup meeting |
| | 127 | * Agreemenent this is rather positive |
| | 128 | * Weekly meeting should happen every week, whether Michel is available or not |
| | 129 | * Weekly meeting should be on time: let's move it to 2:15 pm to increase the chance to start immediatly |
| | 130 | * Meetings should remain short for everybody, not only for the late comers...!!! |
| | 131 | * Add EVO connection into the reminder |
| | 132 | * Have more formal planning/review of sprints and advertize sprint outcome on the mailing list |
| | 133 | * Let's try 1 1/2 month sprint |
| | 134 | |
| | 135 | People working on some developments need to let others know through a message to `quattor-devel` list or participation to standup meetings. |
| | 136 | |
| | 137 | Monthly meeting |
| | 138 | * Ask the general mailing list about the interest of the community |
| | 139 | * If yes, propose to have a larger meeting for the sprint review meeting |
| | 140 | * Plan them in advance and add an event in Quattor Indico area (and reference it on the wiki) |
| | 141 | * Send a reminder 2 weeks in advance |
| | 142 | |
| | 143 | Repository branching |
| | 144 | * 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 |
| | 145 | * Not really a problem for QWG where trunk is really for work in progress |
| | 146 | * As discussed at the last workshop, good candidates for migration are CCM-related things (ccm, ncm-cdispd, ncm-ncd, QuattorFS), AII and its plugins |
| | 147 | * Encourage people who are contributing major changes to make a branch, as it has been done for `ncm-network` |
| | 148 | * Use stand-up/review meetings to decide merging into trunk |
| | 149 | |
