| 453 | | To be discussed on Thursday |
| 454 | | * Web landng page : move to Git |
| 455 | | * IRC |
| 456 | | * Twitter |
| 457 | | * Quattor releases |
| 458 | | * Vidyo for standup? |
| 459 | | * Fix link to Quattor home page in WallStreet Tech article about MS usage of Linux/Quattor |
| | 473 | === Quattor Build and Test Process and Tools === |
| | 474 | |
| | 475 | StratusLab experience |
| | 476 | * Build with maven as the driver |
| | 477 | * Easy to wrap non-java builds and to use other build tools like make |
| | 478 | * Tools should have unit tests |
| | 479 | * Nexus as a package repository |
| | 480 | * Works well with maven: packages pushed automatically after build |
| | 481 | * Wth maven, has very clean dependency resolution process: dependencies automatically pulled in with transitive dependency resolution |
| | 482 | * A new snapshot entry created by maven every time it runs and produces something new |
| | 483 | * Package repository at the heart of the build process |
| | 484 | * Continous integration with Hudson/Jenkins |
| | 485 | * Continuous build of the SW, triggered by modifications to the package repository |
| | 486 | * Can also do build on demand |
| | 487 | * Installation of test infrastructures |
| | 488 | * Allows to manage dependencies between test stages but not working well as a workflow manager (ability to take different decisions based on result of a stage) |
| | 489 | * SlipStream for system testing |
| | 490 | * Workflow-like features to manage deployment of virtual machines |
| | 491 | * Growing use for system deployments and testings |
| | 492 | * Web server for release distributions |
| | 493 | * YUM based repositories for published releases |
| | 494 | |
| | 495 | Proposal for Quattor |
| | 496 | * Move `quattor.org` DNS domain to an active institue to allow more flexible updates |
| | 497 | * Need ability to create entries in this domain |
| | 498 | * Discuss with CERN immediate transfer of primary server and possible transfer of ownership: LAL primary, RAL secondary |
| | 499 | * Start wth same toolset as for StratusLab |
| | 500 | * Decide where to put the tools: StratusLab cloud? persistent disk for data? |
| | 501 | * Move Nexus server from LAPP to the same place as other tools? |
| | 502 | * Demonstrate builds for core tools |
| | 503 | * Some already maven-ready |
| | 504 | * PRobably ~10 more to convert to new build tools: cdispd/listend/ncd, aquilon, rpmt-py/spma, ncm-templates, ncm-query |
| | 505 | * Not necessary to convert them to Maven |
| | 506 | * Deployment/test of Quattor "HelloWorld" |
| | 507 | * Simple test configuration based on Aquilon appliance? |
| | 508 | * Perform "release" of core tools |
| | 509 | * Devise same procedure for configuration modules |
| | 510 | * Think about unit test environment: Luis started some work around this... |
| | 511 | |
| | 512 | Actions |
| | 513 | * DNS changes: Michel |
| | 514 | * Jenkins, Nexus deployment: Cal |
| | 515 | * Integration of core tools: Cal + tool maintainers |
| | 516 | * Target date for initial setup: ~1 month |
| | 517 | |
| | 518 | Extend the number of people with Maven knowledge... |
| | 519 | * Not a requirement for the very short term... core tool maintainers are a very limited set of people |
| | 520 | * Trac page reasonnably up to date... |
| | 521 | |
| | 522 | Quattor releases: let's review how we do it when we have the build infrastructure in place |
| | 523 | * With YUM, no need of metarpm |
| | 524 | * The main issue is not bringing dependencies but identify what are the stable versions of all components that work together |
| | 525 | * "HelloWorld" test configuration may help to assess what is ready for releasing |
| | 526 | |
| | 527 | Weekly standup meetings |
| | 528 | * Should run without Michel: Luis and Ronald agrees to backup |
| | 529 | |
| | 530 | Main priorities should focus usability rather than new features |
| | 531 | * Cookbooks to start with Quattor and its core tools |
| | 532 | * Reuse the panc idea |
| | 533 | * Foster Aquilon adoption as a tool hiding the template complexity |
| | 534 | * Possibility for a Quattor dashboard |
| | 535 | * Possibility to reuse/adapt existing tools like Foreman? |
| | 536 | * Quattor as a tool to manage virtualized infrastructure |
| | 537 | * Start by documenting existing use cases and experiences in blog entries, e.g. LAL work within StratusLab to manage images rather than machines |
| | 538 | |
| | 539 | |
| | 540 | === Quattor Public Visibility and Community === |
| | 541 | |
| | 542 | Main page move to GitHub |
| | 543 | * Need to change DNS... see previous actions |
| | 544 | * Cal makes a proposal that can be reviewed |
| | 545 | * Populate with a few entries all the categories of information |
| | 546 | * Put Oloh! widget on the web page |
| | 547 | * Go live! |
| | 548 | |
| | 549 | News broadcasting |
| | 550 | * Send more general/regular news should appear on the main web site |
| | 551 | * Broadcast it to the general mailing list |
| | 552 | * Tweet this news: any plugin to do it automatically? |
| | 553 | |
| | 554 | Reserve Quattor name on Google+, LinkedIn, (Fabebook?) |
| | 555 | * Cal will do it |
| | 556 | |
| | 557 | IRC: try to continue to listen it despite the low activity... |
| | 558 | |
| | 559 | Dissemination materials |
| | 560 | * Build an internal repository for existing dissemination materials that could be reused by others to make presentations |
| | 561 | |
| | 562 | Miscellaneous |
| | 563 | * Fix link to Quattor home page in WallStreet Tech article about MS usage of Linux/Quattor (Nick) |
