Rundeck                     Introduction and use cases                        Vincent Behar <vincent@behar.name>          ...
Rundeck?jeudi 10 mars 2011
What?    • Job            automation    • Job            schedulingjeudi 10 mars 2011
How?    • Connect           to nodes and execute a script/command         • SSH       (private key)    • WebUI           (...
The configuration    • One             instance can handle multiple projects    • Per            project:         • one    ...
A node resource sample        <node name="asuka" type="Node"         description="xen dom0" tags="xen"         hostname="a...
A job sample[..]     <name>www.rtl.fr</name>     <group>lab/webapps/deploy</group>     <context>      <project>rtlnet</pro...
Model providers    • Rundeck           can use remote URL to get         • the       list of nodes (resource model provide...
Access control    • Users          are authenticated via JAAS (LDAP, flat file, etc.)    • Access          control can be de...
Limitations of 1.1    • Only            one private key (w/o passphrase) for all nodes    • No             official remote ...
Real case                       @RTLjeudi 10 mars 2011
Background    • Technologies: Java, Tomcat, SQL    • CI       with Jenkins    • Artifacts      managed by Nexus    •A     ...
0-click deployjeudi 10 mars 2011
Success story    • One            click deployment    • Automated             and reproductible deployment    • The       ...
RunDeck
RunDeck
RunDeck
RunDeck
Upcoming SlideShare
Loading in...5
×

RunDeck

7,441

Published on

This slide is a short description of RunDeck, an automation tool. The slide also demonstrate a use case to deploy Java WebApplications.

Published in: Technology
0 Comments
15 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total Views
7,441
On Slideshare
0
From Embeds
0
Number of Embeds
2
Actions
Shares
0
Downloads
123
Comments
0
Likes
15
Embeds 0
No embeds

No notes for slide

RunDeck

  1. 1. Rundeck Introduction and use cases Vincent Behar <vincent@behar.name> Bruno Bonfils <asyd@asyd.net>jeudi 10 mars 2011
  2. 2. Rundeck?jeudi 10 mars 2011
  3. 3. What? • Job automation • Job schedulingjeudi 10 mars 2011
  4. 4. How? • Connect to nodes and execute a script/command • SSH (private key) • WebUI (Grails) • CLIjeudi 10 mars 2011
  5. 5. The configuration • One instance can handle multiple projects • Per project: • one XML file describe all available nodes • osArch, osFamily, tags • one XML per jobjeudi 10 mars 2011
  6. 6. A node resource sample <node name="asuka" type="Node" description="xen dom0" tags="xen" hostname="asuka.asyd.net" osArch="amd64" osFamily="unix" osName="Linux" osVersion="2.6.32-5-xen-amd64" username="asyd"/>jeudi 10 mars 2011
  7. 7. A job sample[..] <name>www.rtl.fr</name> <group>lab/webapps/deploy</group> <context> <project>rtlnet</project> <options> <option name=version value=LATEST enforcedvalues=true required=true valuesUrl=http://..../ /> </options> </context> <sequence threadcount=1 keepgoing=false strategy=node-first> <command> <exec>cp /repository/${option.version} $CATALINA_HOME/webapps</exec> </command> </sequence> node-first: execute toute les commandes sur un node <nodefilters> avant de passer au node suivant <include> <tags>lab</tags> </include> step-first: execute la premiere sur chaque node </nodefilters> avant d’executer la commande suivante <dispatch> <threadcount>2</threadcount> <keepgoing>true</keepgoing> </dispatch> [..]jeudi 10 mars 2011
  8. 8. Model providers • Rundeck can use remote URL to get • the list of nodes (resource model provider) (XML) • already available: Amazon EC2, Puppet, Chef • the list of available options for a specific job (option model provider) (JSON) • Jenkins, Nexusjeudi 10 mars 2011
  9. 9. Access control • Users are authenticated via JAAS (LDAP, flat file, etc.) • Access control can be defined via policies • Rules by project, group, jobjeudi 10 mars 2011
  10. 10. Limitations of 1.1 • Only one private key (w/o passphrase) for all nodes • No official remote API (REST in 1.2) • Basic notifications by email (will extended in 1.3)jeudi 10 mars 2011
  11. 11. Real case @RTLjeudi 10 mars 2011
  12. 12. Background • Technologies: Java, Tomcat, SQL • CI with Jenkins • Artifacts managed by Nexus •A test environnment •A production environmentjeudi 10 mars 2011
  13. 13. 0-click deployjeudi 10 mars 2011
  14. 14. Success story • One click deployment • Automated and reproductible deployment • The test environment is always the HEAD • The production deployment process is exactly the same as the test • More small deployments in production (less risky) • Easy rollback in productionjeudi 10 mars 2011
  1. A particular slide catching your eye?

    Clipping is a handy way to collect important slides you want to go back to later.

×