- Dale Arntson
- Chris Creswell
- Anne L. Highsmith
- Hongwei Ji
- Ingolf Kuss
- Craig McNally
- Christopher Manly
- Steven Pampell
- Wayne Schneider
- Paul Hoffman (filling in for Walter Stine)
- Michael Winkler
- Tod Olson
|10 min||Introductions||Everyone||today's note keeper : Tod|
|10 min||Review charge (again)||Ingolf|
What should we start with? (Review discussion/action items from Augustl kick off meeting)
Wayne Schneider to ask as liaison between this SIG and the dev group–we want to make sure that we don't duplicate effort or overlook anything.
Deployments and Documentation
In general, existing documentation has been written for developer. Now we need documentation from the sysadmin point as we start planning production-oriented deployments. Current documentation assumes a level of knowledge that not everyone understands. Very good for devs already familiar with all concepts, not so good for sysadmins or people trying to get an instance up and running. Would like to see the concepts all introduced. One thing missing is a conceptual diagram, need a system architecture description from the sysadmin perspective.
We may want a subgroup to look at migration and production deployments.
Can we share CI scripts to get started? See github:
Many on the call are looking at cloud deployments. Calls for a container deployment, maybe we can share Docker files for each back-end module so that we can build Docker containers for each. CI process builds Docker images.
Wayne and Craig have done deployments that are moving toward production-ready. Can we put together an outline for what needs to be in the documentation. Craig can maybe give high-level documention, but would have to stop short of details. Would be useful to jump-start the documetation and a deployment process.
In next month, Index Data will be trying to build a more production-ready depolyment for more public consumption without the constraint of building a commercial hosting service.
|10 min||When should we meet again? How often?||Ingolf|
Will meet at same time each of the next two weeks, Dec. 14 & 21, to establish momentum, then take a holiday break.
Long term will want to change time because it collides with the Product Council