Both sides previous revisionPrevious revisionNext revision | Previous revision |
conference:2015:proposals [2015/03/03 22:08] – klussier | conference:2015:proposals [2022/02/10 13:34] (current) – external edit 127.0.0.1 |
---|
| ====== 2015 Proposals ====== |
| |
The 2015 Evergreen International Conference is May 13-16, 2015 in Hood River, Oregon. The deadline for submitting proposals is Friday, Feburary 27, 2015. | The 2015 Evergreen International Conference is May 13-16, 2015 in Hood River, Oregon. The deadline for submitting proposals is Friday, Feburary 27, 2015. |
| |
**Presenter(s):** Benjamin Shum (bshum@biblio.org), Evergreen Systems Manager, Bibliomation and Jason Stephenson (jstephenson@mvlc.org), Assistant Director for Technology Services, Merrimack Valley Library Consortium (MVLC) | **Presenter(s):** Benjamin Shum (bshum@biblio.org), Evergreen Systems Manager, Bibliomation and Jason Stephenson (jstephenson@mvlc.org), Assistant Director for Technology Services, Merrimack Valley Library Consortium (MVLC) |
| |
==== An Introduction to Automated Evergreen Configuration with Ansible: ==== | ==== An Introduction to Automated Evergreen Configuration with Ansible ==== |
| |
**Description:** Building a large Evergreen installation can involve installing various components on many servers. How do you do this consistently without making mistakes? Scripts are one way, but how do you make further changes to the system without keeping a large library of scripts that have to be run in just the right order? A configuration management system can automate everything from virtual machine provisioning to updating your opac templates, while being idempotent means that changes can be made at any time and the system will always end up in the expected state. This talk will focus on using the Ansible management system but most of the concepts apply to other popular systems such as Puppet, Chef, and Salt. | **Description:** Building a large Evergreen installation can involve installing various components on many servers. How do you do this consistently without making mistakes? Scripts are one way, but how do you make further changes to the system without keeping a large library of scripts that have to be run in just the right order? A configuration management system can automate everything from virtual machine provisioning to updating your opac templates, while being idempotent means that changes can be made at any time and the system will always end up in the expected state. This talk will focus on using the Ansible management system but most of the concepts apply to other popular systems such as Puppet, Chef, and Salt. |
==== Catalog: What a mess! ==== | ==== Catalog: What a mess! ==== |
| |
**Description:** Do you suffer from large print syndrome? Do you experience 856 pains from the subfield z? Do you wake up and find that your DVD icons have decided to be phonograph? Have you noticed that search results look redundant? Then this is for you! I am sure we all struggle to keep items attached to the right things. This is a programmatic approach to solve the problem. We will speak in detail about how we solved this issue and created software to distill the information. We will show code and queries so bring your code parser and query planner TI-85. | **Description:** Do you suffer from large print syndrome? Do you experience 856 pains from the subfield z? Do you wake up and find that your DVD icons have decided to be phonograph? Have you noticed that search results look redundant? Then this is for you! I am sure we all struggle to keep items attached to the right things. This is a programmatic approach to solve the problem. We will speak in detail about how we solved this issue and created software to distill the information. We would like to share the employed algorithms that we used to turn perl and SQL into a catalog cleanup aid. We will show code and queries so bring your code parser and query planner TI-85. |
| |
**Technical Expertise:** Moderate to High | **Technical Expertise:** Moderate to High |