From [Wrap-Up Period Activities]:

Overview The focus of the wrap-up period is to document, peer review, integration test, fix bugs and prepare an initial scoping and task list for the next iteration.

Review scope

For this review, I am reviewing the Nimbus context agent - Chef integration. The Contextualization Scenarios page is also helpful in understanding the work, as is System Configuration Management and Frameworks. Invaluable detail on the loadbalancer scenario is here.

Does the summary material clearly explain the work done? Is there enough context to understand the work done?

After a few minutes with Alex to get context and starting points, yes. It's spread across several pages, but the Contextualization Scenarios page in particular explains the concepts and use-cases well.

The pages don't explain what's produced - I assume code, on github, but it's not clear to me.

How does this work relate to your work and your subsystem? What ideas or tools can you apply to your work?

For the data exchange, the ability to write a set of DX recipes would make development and testing easier and more repeatable. DX already requires the following for a full test: controller, proxy, persister, fetcher, notification service, policy service, pub-sub, redis, attribute store and rabbit. Expressing this as a Chef 'cookbook' would let me

• More easily startup/restart/shutdown for local testing, using 'chef-solo'
• Deploy to EC2/Nimbus

For the Buildbot at OOI, we might be able to use Chef to handle the complex code dependencies that are developing. For example, the attribute store depends on txredis & Magnet, but the data exchange has a longer list of dependencies. Chef could handle installing the dependencies, either via http, pypi or whatever, before having buildbot run the unit and integration tests.

As a test case, I'd also like to use this for the attribute store and try deploying it to EC2.

What issues in the content (Word, Jira, code) should be addressed, either now or sometime?

I don't know Ruby, so I can't critique the cookbooks, though they seem compact and logical.

The documentation could use OOI-specific use cases and examples. There's a Magnet cookbook, so perhaps an OOI-type hello world that includes, say,

• Magnet
• Broker runtime configuration for Magnet.ini
  • Host IP
  • vhost
  • username
  • password
• OOI service (attribute store, perhaps?)
  

  If your code isn't on our git server, please link to it.

  Question - in http://github.com/clemesha-ooi/nimbus/blob/master/ctx-agent/ctx/lib/utils.py (and other files), you have this at the end:
  utils.py

  1	# }}} END: Path/system utilities

  What sort of markup is that? ANSWER: Tim Freeman's vim open/close hooks

What interesting insights, suggestions, or thoughts can you offer for the developer to consider?

None at present. I would be interested in a more interactive walkthrough with Alex, though.