gistfile1.txt

- notes from 1-23-15

1. on boarding
- we need to have a plan for how to on board new team members
- as people want to join
- -  we need low hanging fruit to get started
     - check issues in github
     - check all warning/errors across all logs on deployemnts, pick a log message, log a ticket, make it go away
     - fix a failing tempest test
- - we need to write more specifications and allow people to engage by designing larger feature sets
    via specification
2. documentation
3. finish reference architecture
- horizontally scalable database (ie: vitess)
    work on a specification document to capture plan
- horizontally scaling contrail (Dan)
    I will implement this and sync with Harish on details
    - also review module, and deployment model
- LBAAS/SNAT (needs to be validated, should have tempest tests)
- clustering consul servers
- clustering haproxy
- ceph crushmap
5. external services
- monitoring? (implement a specification)
- event aggregation (implement specification)
- metrics (implement specification)
4. known tasks
  - implement consul discovery service as a local service (does it go in the external layout?)
5. tempest
- support tempest team, but it is taking way too much of harish's time.
  can someone else support them on this?
6. specifications
- intelligent upgrades
- operations procedures
- monitoring and metric collection
- aggregation
- moving configration from puppet to consul
7. security (I want the security person to own this)
- consul
8. integration testing
- integration tests for multiple layouts
- auto-jenkins upgrade through pipeline
- gating for python-jiocloud
9. consul templating
- haproxy
- matchmaker

I believe we should implement consul template and use it whereever required

1. haproxy config
2. matchmaker.json
   (there may be more )