Charm Tools
- Similar to last week, no real big changes, Marco will hit these after he’s done with testing.
- We need to update the review queue charm schools, the website queue fixed the “time to first response”, but the CLI tool is behind. Mims to bust it out.
Ben’s charm-tools feedback. Just some ideas:
- It would be nice for
charm create
to work more likedh_make
- It should ask for the license to use, and populate the copyright file
- It would be nice for it read the DEBFULLNAME and DEBEMAIL and s/DEB/CHARM/ environment settings or even .bzr information to determine authorship
- Category should be asked during the charm create
- It should initialize the branch and accept
--git
or--subversion
- It should ask for standard requires, i.e. allow
--requires-db mysql
or--requires-http varnish
or prompt - It should ask for what it provides, i.e.
--provides http
- It should offer the option of a
--peer
for peer relationships - For the relationship hook, it would be great to have commented examples based on the
--requires-X
Charm Helpers
- MPs coming in, progress looks great.
- Wedgewood handling incoming work, activity happening, Marco will roll up a summary of work for next week.
- Thanks Matthew for driving this!
Testing
Minor work:
- charmtester updates to make it more flexible. This is the one that reports to jenkins on qa.ubuntu.com
- juju test plugin, new features requested by the gui team
- Can now run in an existing bootstrapped environment
- You can now specify a config file in the test directory with options for the tests you want to run. There’s an example yaml template if you run
juju-test -h
if you wanna check it out, will be published EOD 2013-06-19
Major work:
- First release of the testing harness (lp:amulet) ready (ppa being prepped for folks to use). \o/
- Wait command, just like
jitsu watch
- Deployer command, describe an environment setting by running a bunch of manual commands, and then uses Kapil, Adam, Matthew, & Co lp:juju-deployer tool to stand up an environment in a test. “Whoa”.
- We’re using it to test openstack deployments and it’s designed to set up complex environments that are repeatable.
- Wait command, just like
Docs
- Translating old charm author docs to the new format.
- DONE AS OF MONDAY. \o/ \o/ \o/
- Just need to finish up the testing, and validation (just a port over of old docs to the new format, content still needs to be confirmed).
- idea - have the new docs deployed as a sub off the apache2 charm. Have the charm do a cron to update from the bzr branch every 12 hours (need feedback).
- Redirects are ready, for when docs go live
- New doc branch @ lp:~charmers/juju-core/docs
- any docs problems - file a bug!
Charm Updates from the Store
- http://jujucharms.com/recently-changed
- Jorge talking to MariaDB see if someone is interested in adding Maria Support to the MySQL charm, any help here appreciated, if you’re using MariaDB and Ubuntu we could use a hand here!
Misc
- Merge proposal workflow.
Events
- OSCON - In progress, no issues.
FRAMEWORK UPDATES
- Rails - almost ready to begin
- node.js - in progress.
- Django and friends - in progress, no thanks to our messed up merge proposals. :)
Blockers
- Backports of juju-core to 12.04!!
- Dependencies on go compiler, core team aware of it, trying to resolve.
- charm tools and helpers backports blocking on this too.
Goals from last week
- Mims: 0mq and storm
- mims preping for Stanford talk
- Do your docs videos!
Goals for this week
- Mims to sync with Dave on juju-core pre-install hooks.
- Mims: 0mq and storm
- Mims preping for Stanford talk
- Everyone: When you touch a charm, rate it, categorize it, see if you can give it an icon.
- Do your docs videos!
- People who did not do docs/videos this week and need to be embarrassed
- Jorge Castro
- Antonio Rosales
- Mark Mims
- Marco Ceppi
- arosales: get docs to a charm’ed up deployed stage
- utlemming: on vacation
- jorge: video and doc page
- marco: vacation
- mims: Storm and 0mq, talk prep
- nick: 4 videos