Re: Call for Charm School topics
Hey Simon! For example, imagine you have an Ansible charm which inside are some php settings applied like php memory limit, and then you relate a subordinated charm to it, that creates a new php.ini with custom configurations that the project needs. If the playbook of the subordinated charm makes a move that doesn't count with files or configurations generated by the other playbook in the main service charm, probably will result in a conflict, and errors will be shown. I was thinking in how to avoid this, leaving less customized configurations in the main charm. But!, it's difficult to know where's the limit. Cheers!, Sebas. Em 08/09/2014 12:03, Simon Davy bloodearn...@gmail.com escreveu: Hi Sebastian On 5 September 2014 18:54, Sebastian sebas5...@gmail.com wrote: - Subordinated charms, when and how to use it. Conflicts with Ansible Charms. Can you give more details on Conflicts with Ansible Charms? We use the ansible support in charm-helpers a lot, for both principle charms and subordinates, and have had no problems mixing those with non-ansible charms, so I'd be keen to hear your issues. Thanks -- Simon -- Juju mailing list Juju@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
Re: Call for Charm School topics
On 9 September 2014 18:45, Sebastian sebas5...@gmail.com wrote: Hey Simon! For example, imagine you have an Ansible charm which inside are some php settings applied like php memory limit, and then you relate a subordinated charm to it, that creates a new php.ini with custom configurations that the project needs. If the playbook of the subordinated charm makes a move that doesn't count with files or configurations generated by the other playbook in the main service charm, probably will result in a conflict, and errors will be shown. This seems to me more like a problem of conflicting on a single file, which is a problem for any subordinate, not specifically an ansible one. As I'm sure you know, it is generally better to use a directory of config files that are included from the main config file, so different things can own different files, and not conflict. Many tools support this OOTB. However, if you can't have includes in a the main php.ini file, then ansible can actually help you with this somewhat, all though in limited fashion. Check out the lineinfile module: http://docs.ansible.com/lineinfile_module.html I was thinking in how to avoid this, leaving less customized configurations in the main charm. But!, it's difficult to know where's the limit. Yeah, so getting the right responsibilities between subordinates/principles can be quite nuanced. A good example IMO is the gunicorn subordinate for running python applications. All configuration is done via the relation to the subordinate, and the subordinate owns the gunicorn config completely (going so far as to disable the debian sysv init packaging as it's quite limited). So the responsibilities are clearly divided. That may not be possible in your scenario, of course[1]. But it's easy for a principle charm to touch a file it really shouldn't be doing. We had some gunicorn using principle charms that invoked /etc/init.d/gunicorn restart directly, which was a real pain when we wanted to change how gunicorn was run. One further idea: pass your extra config to the subordinate (or vice versa) as a string in the relation data, and have the subordinate include that config in the generated php.ini. Not the cleanest solution, but it could work. Or even better, expose all the knobs you want to configure in the relation data, and allow them to be set by the principle (with sane defaults). This is what the gunicorn subordinate does, fyi. HTH [1] I know very little about modern[2] php deployment [2] I can probably help with PHP 3, though ;P -- Simon -- Juju mailing list Juju@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
Call for Charm School topics
Hello everyone, Now that conference season is winding down we can start to spin up on Charm workshops. Antonio and I sat down and bashed out some ideas for charm school topics. I've added that list below and also penciled in an instructor. Getting Started (again!)- jorge/marco Getting started with Charm Testing - jorge/chuck/seb Relationships/Interfaces - How to pass information inbetween charms - marco/bcsaller Debugging Hooks - jorge/marco/chuck Writing Charms for Restrictive Networks - jorge/mbruzek Automated Charm Testing infrastructure - jorge/tim Deploying ElasticSearch Clusters with Juju - jorge Deploying Nagios Workloads with Juju - jorge/mbruzer (Maybe someone from Nagios can copresent?) Leveraging nginx in your charms - jorge/? How to use the DNS Charms - jorge/chuck Swapping JDKs in your charm - jorge/mbruzek Charm Helper Updates and Breakdown - jorge/ceppi Charm Tool Updates - jorge/ceppi Backup and Restore in Juju - jorge/? Using Juju with Digital Ocean - jorge/kapilt Charms for different architectures - jorge/mbruzek/chuck We also need a set of big dataish workload ones, any ideas for those would be great. Did I miss anything? Any specific topics people would like to see? Any other volunteers as instructors? I'd like to do charm testing and relationships/interfaces first, as we've had people ask for those specifically. -- Jorge Castro Canonical Ltd. http://juju.ubuntu.com/ - Automate your Cloud Infrastructure -- Juju mailing list Juju@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
Re: Call for Charm School topics
Great! I'm interested in: - Charm testing. - Relationships / interfaces. - DNS charm. - Juju Updates in general. - Backup and restore. - Charms for different archs. Some topics that I always wanna talk about it with you Juju experts: - What would be the better way to scale a charm?, NFS, GlusterFS, Load balancers, etc... - Subordinated charms, when and how to use it. Conflicts with Ansible Charms. - Update bundle, how this can be done today? (bundle versions). - Linux Containers, how this new paradigm fit with Juju? Docker+Openstack and CoreOS. - How Juju deals with networking. - and many others... but the main ones are the above. I'll be participating :D Cheers!, Sebas. 2014-09-05 12:13 GMT-03:00 Jorge O. Castro jo...@ubuntu.com: Hello everyone, Now that conference season is winding down we can start to spin up on Charm workshops. Antonio and I sat down and bashed out some ideas for charm school topics. I've added that list below and also penciled in an instructor. Getting Started (again!)- jorge/marco Getting started with Charm Testing - jorge/chuck/seb Relationships/Interfaces - How to pass information inbetween charms - marco/bcsaller Debugging Hooks - jorge/marco/chuck Writing Charms for Restrictive Networks - jorge/mbruzek Automated Charm Testing infrastructure - jorge/tim Deploying ElasticSearch Clusters with Juju - jorge Deploying Nagios Workloads with Juju - jorge/mbruzer (Maybe someone from Nagios can copresent?) Leveraging nginx in your charms - jorge/? How to use the DNS Charms - jorge/chuck Swapping JDKs in your charm - jorge/mbruzek Charm Helper Updates and Breakdown - jorge/ceppi Charm Tool Updates - jorge/ceppi Backup and Restore in Juju - jorge/? Using Juju with Digital Ocean - jorge/kapilt Charms for different architectures - jorge/mbruzek/chuck We also need a set of big dataish workload ones, any ideas for those would be great. Did I miss anything? Any specific topics people would like to see? Any other volunteers as instructors? I'd like to do charm testing and relationships/interfaces first, as we've had people ask for those specifically. -- Jorge Castro Canonical Ltd. http://juju.ubuntu.com/ - Automate your Cloud Infrastructure -- Juju mailing list Juju@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju -- Juju mailing list Juju@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
