2E - Chef Cookbook Consolidation & » History » Version 2
Jessica Mack, 06/22/2015 04:53 AM
1 | 1 | Jessica Mack | h1. 2E - Chef Cookbook Consolidation & ceph-deploy Improvements |
---|---|---|---|
2 | |||
3 | 2 | Jessica Mack | h3. Live Pad |
4 | |||
5 | The live pad can be found here: "[pad]":http://pad.ceph.com/p/chef-ceph-deploy |
||
6 | |||
7 | h3. Summit Snapshot |
||
8 | 1 | Jessica Mack | |
9 | Welcome to the Ceph Etherpad! |
||
10 | |||
11 | Chef: ( http://github.com/ceph/ceph-cookbooks ) |
||
12 | |||
13 | Past few months: refactored recipes, included Newdream input |
||
14 | Soliciting input for recipe features or anything else! |
||
15 | |||
16 | Current features: |
||
17 | 2 | Jessica Mack | |
18 | p(. Deploy mon/osd |
||
19 | 1 | Jessica Mack | Supports latest Bobtail and Cuttlefish only |
20 | 2 | Jessica Mack | |
21 | 1 | Jessica Mack | Possible extensions: |
22 | 2 | Jessica Mack | |
23 | p(. Does anyone need other release support? |
||
24 | 1 | Jessica Mack | Limiting power of deployment keys (monitor key opens everything) |
25 | Error management/recovery |
||
26 | 2 | Jessica Mack | |
27 | 1 | Jessica Mack | Other issues: |
28 | 2 | Jessica Mack | |
29 | p(. Consolidate best practices from many Chef cookbook authors |
||
30 | 1 | Jessica Mack | Compatibility with ceph-deploy approach would be nice, at least from ceph-deploy -> Chef |
31 | |||
32 | 2 | Jessica Mack | * -> Documentation on migration path. |
33 | 1 | Jessica Mack | |
34 | 2 | Jessica Mack | Look at https://github.com/wonko/ceph-cookbook to see if we can take some features. |
35 | 1 | Jessica Mack | |
36 | |||
37 | |||
38 | |||
39 | Questions: |
||
40 | 2 | Jessica Mack | |
41 | p(. Q: How will the Chef scripts be synced with the Barclamp Chef recipes? |
||
42 | 1 | Jessica Mack | A: Dell/SuSE are working on it most; ideally they would simply include upstream recipes |
43 | |||
44 | |||
45 | 2 | Jessica Mack | * Q: LWRP for creating pools? clients? manage keys? |
46 | * A: the intent is to deploy, but not administer, so focused on setup for now |
||
47 | |||
48 | * Lightweigth resource Resources and Providers - kind of abstraction for objects/resources in chef - http://docs.opscode.com/lwrp.html |
||
49 | * Presentation on LWRP from chefconf (thanks kbader): |
||
50 | * https://docs.google.com/presentation/d/1gQj_QNbzIecZQtbb4oVNMZKlPqiO1q6d08g5l8BqWOI/edit#slide=id.p |
||
51 | 1 | Jessica Mack | |
52 | 2 | Jessica Mack | p(. Q: when someone want to put effort in the cookbooks, what sections would you want to be tackled first? (cleanup, more distributions, hardening the runs, ...) |
53 | 1 | Jessica Mack | A: first priority is better testing on Centos/Redhat/SuSE/Fedora; error handling also needs help |
54 | |||
55 | 2 | Jessica Mack | p(. Q: are there any tests in the cookbooks? |
56 | 1 | Jessica Mack | A: no, and we'd like to have some |
57 | What kind? Ideally we'd use something like test-kitchen with a handful of minitest handlers |
||
58 | Not sure what the convention is for test frameworks for Chef, but "as nonsurprising as possible" always seems right to me |
||
59 | |||
60 | 2 | Jessica Mack | p(. Q: previously there was some goal of running a setup adding additional disks (osds) through some labels on the disks - and then auto-add them to the cluster - is this still the way to go? |
61 | 1 | Jessica Mack | A: yes, ceph-create-keys/ceph-disk (in the ceph repo itself, http://github.com/ceph/ceph ) and the upstart/sysvinit scripts support auto-configuring disks today, and ceph-deploy will mark disks for that sort of delayed activation |
62 | A2: We have some newer chef cookbooks that dreamhost worked with inktank on and they use the ceph-disk-prepare, ceph-disk-activate tooling, we'll open that up and share it |
||
63 | |||
64 | ceph-deploy: |
||
65 | |||
66 | 2 | Jessica Mack | * Syncing efforts between ceph-deploy and Chef is a requirement; publicizing changes/conventions for other environments (Juju, Salt, Puppet) will probably be done in the mailing list |
67 | * can it have it own mailing list please |
||
68 | 1 | Jessica Mack |