[Blueprint servercloud-q-juju-charm-best-practices] Juju Charm Best practices
Blueprint changed by Antonio Rosales: Work items changed: Work items: [jorge] Pick better example charms, "flagbearer charms".: DONE - [jorge] Choose a single place for presenting flagbearer charms (charm browser?): TODO + [jorge] Choose a single place for presenting flagbearer charms (charm browser?): POSTPONED [jorge] Move rules and charm best practices into juju/docs.: DONE [jorge] Add Maintainer field information to documentation. (thanks clint!): DONE [jorge] Reach out to maintainers to get their maintainer field filled out.: DONE [jorge] Add docs work items to patch pilot!: DONE - [jorge] pull "file bug" or "join the doc team" from other projects: TODO + [jorge] pull "file bug" or "join the doc team" from other projects: POSTPONED [jorge] Clarify documentention on what to expect when your using LXC and EC2. Cost, wait time, what you see, logs, downloading. "You should expect this to download 300 megs, etc." Here's a table of look here troubleshooting your LXC thing: DONE [imbrandon] Reach out to maintainers to get their maintainer filled out.: DONE - [imbrandon] Put Doc instructions in the docs: http://askubuntu.com/q/52063 : TODO + [imbrandon] Put Doc instructions in the docs: http://askubuntu.com/q/52063 : POSTPONED [mark-mims] (and individual maintainers!) clean up existing charms wrt best practices: DONE [clint-fewbar] Comment and add links to docs in 'charm create' templates: POSTPONED [clint-fewbar] juju in Debian! NOW!: DONE [clint-fewbar] determine most likely maintainers based on bzr logs: DONE [clint-fewbar] fix doc repos wrt (trunk, go, docs): DONE [marcoceppi] tag:juju review on AU and SE network: DONE [hazmat] incorporate output of charm proof into charm browser: DONE [hazmat] clear out trunk docs for juju: DONE - [imbrandon] Clarify documentention on what to expect when your using LXC and EC2. Cost, wait time, what you see, logs, downloading. "You should expect this to download 300 megs, etc." Here's a table of look here troubleshooting your LXC thing.: TODO - [hazmat] make juju report on initial lxc image downloads ?: TODO - [clint-fewbar] make juju lxc use lxc networking instead of libvirt networking ?: INPROGRESS + [imbrandon] Clarify documentention on what to expect when your using LXC and EC2. Cost, wait time, what you see, logs, downloading. "You should expect this to download 300 megs, etc." Here's a table of look here troubleshooting your LXC thing.: POSTPONED + [hazmat] make juju report on initial lxc image downloads ?: POSTPONED + [clint-fewbar] make juju lxc use lxc networking instead of libvirt networking ?: POSTPONED -- Juju Charm Best practices https://blueprints.launchpad.net/ubuntu/+spec/servercloud-q-juju-charm-best-practices -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Blueprint servercloud-q-juju-charm-best-practices] Juju Charm Best practices
Blueprint changed by Mark Mims: Work items changed: Work items: [jorge] Pick better example charms, "flagbearer charms".: DONE [jorge] Choose a single place for presenting flagbearer charms (charm browser?): TODO [jorge] Move rules and charm best practices into juju/docs.: DONE [jorge] Add Maintainer field information to documentation. (thanks clint!): DONE [jorge] Reach out to maintainers to get their maintainer field filled out.: DONE [jorge] Add docs work items to patch pilot!: DONE [jorge] pull "file bug" or "join the doc team" from other projects: TODO [jorge] Clarify documentention on what to expect when your using LXC and EC2. Cost, wait time, what you see, logs, downloading. "You should expect this to download 300 megs, etc." Here's a table of look here troubleshooting your LXC thing: DONE [imbrandon] Reach out to maintainers to get their maintainer filled out.: DONE [imbrandon] Put Doc instructions in the docs: http://askubuntu.com/q/52063 : TODO - [mark-mims] (and individual maintainers!) clean up existing charms wrt best practices: TODO + [mark-mims] (and individual maintainers!) clean up existing charms wrt best practices: DONE [clint-fewbar] Comment and add links to docs in 'charm create' templates: POSTPONED [clint-fewbar] juju in Debian! NOW!: DONE [clint-fewbar] determine most likely maintainers based on bzr logs: DONE [clint-fewbar] fix doc repos wrt (trunk, go, docs): DONE [marcoceppi] tag:juju review on AU and SE network: DONE [hazmat] incorporate output of charm proof into charm browser: DONE [hazmat] clear out trunk docs for juju: DONE [imbrandon] Clarify documentention on what to expect when your using LXC and EC2. Cost, wait time, what you see, logs, downloading. "You should expect this to download 300 megs, etc." Here's a table of look here troubleshooting your LXC thing.: TODO [hazmat] make juju report on initial lxc image downloads ?: TODO [clint-fewbar] make juju lxc use lxc networking instead of libvirt networking ?: INPROGRESS -- Juju Charm Best practices https://blueprints.launchpad.net/ubuntu/+spec/servercloud-q-juju-charm-best-practices -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Blueprint servercloud-q-juju-charm-best-practices] Juju Charm Best practices
Blueprint changed by Clint Byrum: Work items changed: Work items: [jorge] Pick better example charms, "flagbearer charms".: DONE [jorge] Choose a single place for presenting flagbearer charms (charm browser?): TODO [jorge] Move rules and charm best practices into juju/docs.: DONE [jorge] Add Maintainer field information to documentation. (thanks clint!): DONE [jorge] Reach out to maintainers to get their maintainer field filled out.: DONE [jorge] Add docs work items to patch pilot!: DONE [jorge] pull "file bug" or "join the doc team" from other projects: TODO [jorge] Clarify documentention on what to expect when your using LXC and EC2. Cost, wait time, what you see, logs, downloading. "You should expect this to download 300 megs, etc." Here's a table of look here troubleshooting your LXC thing: DONE [imbrandon] Reach out to maintainers to get their maintainer filled out.: DONE [imbrandon] Put Doc instructions in the docs: http://askubuntu.com/q/52063 : TODO [mark-mims] (and individual maintainers!) clean up existing charms wrt best practices: TODO [clint-fewbar] Comment and add links to docs in 'charm create' templates: POSTPONED [clint-fewbar] juju in Debian! NOW!: DONE [clint-fewbar] determine most likely maintainers based on bzr logs: DONE [clint-fewbar] fix doc repos wrt (trunk, go, docs): DONE [marcoceppi] tag:juju review on AU and SE network: DONE [hazmat] incorporate output of charm proof into charm browser: DONE [hazmat] clear out trunk docs for juju: DONE [imbrandon] Clarify documentention on what to expect when your using LXC and EC2. Cost, wait time, what you see, logs, downloading. "You should expect this to download 300 megs, etc." Here's a table of look here troubleshooting your LXC thing.: TODO [hazmat] make juju report on initial lxc image downloads ?: TODO - [hazmat] make juju lxc use lxc networking instead of libvirt networking ?: TODO + [clint-fewbar] make juju lxc use lxc networking instead of libvirt networking ?: INPROGRESS -- Juju Charm Best practices https://blueprints.launchpad.net/ubuntu/+spec/servercloud-q-juju-charm-best-practices -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Blueprint servercloud-q-juju-charm-best-practices] Juju Charm Best practices
Blueprint changed by Clint Byrum: Work items changed: Work items: [jorge] Pick better example charms, "flagbearer charms".: DONE [jorge] Choose a single place for presenting flagbearer charms (charm browser?): TODO [jorge] Move rules and charm best practices into juju/docs.: DONE [jorge] Add Maintainer field information to documentation. (thanks clint!): DONE [jorge] Reach out to maintainers to get their maintainer field filled out.: DONE [jorge] Add docs work items to patch pilot!: DONE [jorge] pull "file bug" or "join the doc team" from other projects: TODO [jorge] Clarify documentention on what to expect when your using LXC and EC2. Cost, wait time, what you see, logs, downloading. "You should expect this to download 300 megs, etc." Here's a table of look here troubleshooting your LXC thing: DONE [imbrandon] Reach out to maintainers to get their maintainer filled out.: DONE [imbrandon] Put Doc instructions in the docs: http://askubuntu.com/q/52063 : TODO [mark-mims] (and individual maintainers!) clean up existing charms wrt best practices: TODO - [clint-fewbar] Comment and add links to docs in 'charm create' templates: TODO + [clint-fewbar] Comment and add links to docs in 'charm create' templates: POSTPONED [clint-fewbar] juju in Debian! NOW!: DONE [clint-fewbar] determine most likely maintainers based on bzr logs: DONE [clint-fewbar] fix doc repos wrt (trunk, go, docs): DONE [marcoceppi] tag:juju review on AU and SE network: DONE [hazmat] incorporate output of charm proof into charm browser: DONE [hazmat] clear out trunk docs for juju: DONE [imbrandon] Clarify documentention on what to expect when your using LXC and EC2. Cost, wait time, what you see, logs, downloading. "You should expect this to download 300 megs, etc." Here's a table of look here troubleshooting your LXC thing.: TODO [hazmat] make juju report on initial lxc image downloads ?: TODO [hazmat] make juju lxc use lxc networking instead of libvirt networking ?: TODO -- Juju Charm Best practices https://blueprints.launchpad.net/ubuntu/+spec/servercloud-q-juju-charm-best-practices -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Blueprint servercloud-q-juju-charm-best-practices] Juju Charm Best practices
Blueprint changed by Jorge O. Castro: Work items changed: Work items: - [jorge] Pick better example charms, "flagbearer charms".: TODO + [jorge] Pick better example charms, "flagbearer charms".: DONE [jorge] Choose a single place for presenting flagbearer charms (charm browser?): TODO [jorge] Move rules and charm best practices into juju/docs.: DONE [jorge] Add Maintainer field information to documentation. (thanks clint!): DONE [jorge] Reach out to maintainers to get their maintainer field filled out.: DONE [jorge] Add docs work items to patch pilot!: DONE [jorge] pull "file bug" or "join the doc team" from other projects: TODO [jorge] Clarify documentention on what to expect when your using LXC and EC2. Cost, wait time, what you see, logs, downloading. "You should expect this to download 300 megs, etc." Here's a table of look here troubleshooting your LXC thing: DONE [imbrandon] Reach out to maintainers to get their maintainer filled out.: DONE [imbrandon] Put Doc instructions in the docs: http://askubuntu.com/q/52063 : TODO [mark-mims] (and individual maintainers!) clean up existing charms wrt best practices: TODO [clint-fewbar] Comment and add links to docs in 'charm create' templates: TODO [clint-fewbar] juju in Debian! NOW!: DONE [clint-fewbar] determine most likely maintainers based on bzr logs: DONE [clint-fewbar] fix doc repos wrt (trunk, go, docs): DONE [marcoceppi] tag:juju review on AU and SE network: DONE [hazmat] incorporate output of charm proof into charm browser: DONE [hazmat] clear out trunk docs for juju: DONE [imbrandon] Clarify documentention on what to expect when your using LXC and EC2. Cost, wait time, what you see, logs, downloading. "You should expect this to download 300 megs, etc." Here's a table of look here troubleshooting your LXC thing.: TODO [hazmat] make juju report on initial lxc image downloads ?: TODO [hazmat] make juju lxc use lxc networking instead of libvirt networking ?: TODO -- Juju Charm Best practices https://blueprints.launchpad.net/ubuntu/+spec/servercloud-q-juju-charm-best-practices -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Blueprint servercloud-q-juju-charm-best-practices] Juju Charm Best practices
Blueprint changed by Jorge O. Castro: Work items changed: Work items: [jorge] Pick better example charms, "flagbearer charms".: TODO [jorge] Choose a single place for presenting flagbearer charms (charm browser?): TODO [jorge] Move rules and charm best practices into juju/docs.: DONE [jorge] Add Maintainer field information to documentation. (thanks clint!): DONE - [jorge] Reach out to maintainers to get their maintainer field filled out.: INPROGRESS + [jorge] Reach out to maintainers to get their maintainer field filled out.: DONE [jorge] Add docs work items to patch pilot!: DONE [jorge] pull "file bug" or "join the doc team" from other projects: TODO [jorge] Clarify documentention on what to expect when your using LXC and EC2. Cost, wait time, what you see, logs, downloading. "You should expect this to download 300 megs, etc." Here's a table of look here troubleshooting your LXC thing: DONE [imbrandon] Reach out to maintainers to get their maintainer filled out.: DONE [imbrandon] Put Doc instructions in the docs: http://askubuntu.com/q/52063 : TODO [mark-mims] (and individual maintainers!) clean up existing charms wrt best practices: TODO [clint-fewbar] Comment and add links to docs in 'charm create' templates: TODO [clint-fewbar] juju in Debian! NOW!: DONE [clint-fewbar] determine most likely maintainers based on bzr logs: DONE [clint-fewbar] fix doc repos wrt (trunk, go, docs): DONE [marcoceppi] tag:juju review on AU and SE network: DONE [hazmat] incorporate output of charm proof into charm browser: DONE [hazmat] clear out trunk docs for juju: DONE [imbrandon] Clarify documentention on what to expect when your using LXC and EC2. Cost, wait time, what you see, logs, downloading. "You should expect this to download 300 megs, etc." Here's a table of look here troubleshooting your LXC thing.: TODO [hazmat] make juju report on initial lxc image downloads ?: TODO [hazmat] make juju lxc use lxc networking instead of libvirt networking ?: TODO -- Juju Charm Best practices https://blueprints.launchpad.net/ubuntu/+spec/servercloud-q-juju-charm-best-practices -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Blueprint servercloud-q-juju-charm-best-practices] Juju Charm Best practices
Blueprint changed by Clint Byrum: Work items changed: Work items: [jorge] Pick better example charms, "flagbearer charms".: TODO [jorge] Choose a single place for presenting flagbearer charms (charm browser?): TODO [jorge] Move rules and charm best practices into juju/docs.: DONE [jorge] Add Maintainer field information to documentation. (thanks clint!): DONE [jorge] Reach out to maintainers to get their maintainer field filled out.: INPROGRESS [jorge] Add docs work items to patch pilot!: DONE [jorge] pull "file bug" or "join the doc team" from other projects: TODO [jorge] Clarify documentention on what to expect when your using LXC and EC2. Cost, wait time, what you see, logs, downloading. "You should expect this to download 300 megs, etc." Here's a table of look here troubleshooting your LXC thing: DONE [imbrandon] Reach out to maintainers to get their maintainer filled out.: DONE [imbrandon] Put Doc instructions in the docs: http://askubuntu.com/q/52063 : TODO [mark-mims] (and individual maintainers!) clean up existing charms wrt best practices: TODO [clint-fewbar] Comment and add links to docs in 'charm create' templates: TODO [clint-fewbar] juju in Debian! NOW!: DONE [clint-fewbar] determine most likely maintainers based on bzr logs: DONE [clint-fewbar] fix doc repos wrt (trunk, go, docs): DONE [marcoceppi] tag:juju review on AU and SE network: DONE [hazmat] incorporate output of charm proof into charm browser: DONE [hazmat] clear out trunk docs for juju: DONE [imbrandon] Clarify documentention on what to expect when your using LXC and EC2. Cost, wait time, what you see, logs, downloading. "You should expect this to download 300 megs, etc." Here's a table of look here troubleshooting your LXC thing.: TODO - [imbrandon] Clarify documentention on what to expect when your using LXC and EC2. Cost, wait time, what you see, logs, downloading. "You should expect this to download 300 megs, etc." Here's a table of look here troubleshooting your LXC thing.: TODO [hazmat] make juju report on initial lxc image downloads ?: TODO [hazmat] make juju lxc use lxc networking instead of libvirt networking ?: TODO -- Juju Charm Best practices https://blueprints.launchpad.net/ubuntu/+spec/servercloud-q-juju-charm-best-practices -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Blueprint servercloud-q-juju-charm-best-practices] Juju Charm Best practices
Blueprint changed by Clint Byrum: Work items changed: Work items: [jorge] Pick better example charms, "flagbearer charms".: TODO [jorge] Choose a single place for presenting flagbearer charms (charm browser?): TODO [jorge] Move rules and charm best practices into juju/docs.: DONE [jorge] Add Maintainer field information to documentation. (thanks clint!): DONE [jorge] Reach out to maintainers to get their maintainer field filled out.: INPROGRESS [jorge] Add docs work items to patch pilot!: DONE [jorge] pull "file bug" or "join the doc team" from other projects: TODO [jorge] Clarify documentention on what to expect when your using LXC and EC2. Cost, wait time, what you see, logs, downloading. "You should expect this to download 300 megs, etc." Here's a table of look here troubleshooting your LXC thing: DONE [imbrandon] Reach out to maintainers to get their maintainer filled out.: DONE [imbrandon] Put Doc instructions in the docs: http://askubuntu.com/q/52063 : TODO [mark-mims] (and individual maintainers!) clean up existing charms wrt best practices: TODO [clint-fewbar] Comment and add links to docs in 'charm create' templates: TODO [clint-fewbar] juju in Debian! NOW!: DONE [clint-fewbar] determine most likely maintainers based on bzr logs: DONE [clint-fewbar] fix doc repos wrt (trunk, go, docs): DONE - [marcoceppi] tag:juju review on AU and SE network: TODO + [marcoceppi] tag:juju review on AU and SE network: DONE [hazmat] incorporate output of charm proof into charm browser: DONE [hazmat] clear out trunk docs for juju: DONE [imbrandon] Clarify documentention on what to expect when your using LXC and EC2. Cost, wait time, what you see, logs, downloading. "You should expect this to download 300 megs, etc." Here's a table of look here troubleshooting your LXC thing.: TODO [imbrandon] Clarify documentention on what to expect when your using LXC and EC2. Cost, wait time, what you see, logs, downloading. "You should expect this to download 300 megs, etc." Here's a table of look here troubleshooting your LXC thing.: TODO [hazmat] make juju report on initial lxc image downloads ?: TODO [hazmat] make juju lxc use lxc networking instead of libvirt networking ?: TODO -- Juju Charm Best practices https://blueprints.launchpad.net/ubuntu/+spec/servercloud-q-juju-charm-best-practices -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Blueprint servercloud-q-juju-charm-best-practices] Juju Charm Best practices
Blueprint changed by Clint Byrum: Work items changed: Work items: [jorge] Pick better example charms, "flagbearer charms".: TODO [jorge] Choose a single place for presenting flagbearer charms (charm browser?): TODO [jorge] Move rules and charm best practices into juju/docs.: DONE [jorge] Add Maintainer field information to documentation. (thanks clint!): DONE [jorge] Reach out to maintainers to get their maintainer field filled out.: INPROGRESS [jorge] Add docs work items to patch pilot!: DONE [jorge] pull "file bug" or "join the doc team" from other projects: TODO [jorge] Clarify documentention on what to expect when your using LXC and EC2. Cost, wait time, what you see, logs, downloading. "You should expect this to download 300 megs, etc." Here's a table of look here troubleshooting your LXC thing: DONE - [imbrandon] Reach out to maintainers to get their maintainer filled out.: TODO + [imbrandon] Reach out to maintainers to get their maintainer filled out.: DONE [imbrandon] Put Doc instructions in the docs: http://askubuntu.com/q/52063 : TODO [mark-mims] (and individual maintainers!) clean up existing charms wrt best practices: TODO [clint-fewbar] Comment and add links to docs in 'charm create' templates: TODO [clint-fewbar] juju in Debian! NOW!: DONE [clint-fewbar] determine most likely maintainers based on bzr logs: DONE [clint-fewbar] fix doc repos wrt (trunk, go, docs): DONE [marcoceppi] tag:juju review on AU and SE network: TODO [hazmat] incorporate output of charm proof into charm browser: DONE [hazmat] clear out trunk docs for juju: DONE [imbrandon] Clarify documentention on what to expect when your using LXC and EC2. Cost, wait time, what you see, logs, downloading. "You should expect this to download 300 megs, etc." Here's a table of look here troubleshooting your LXC thing.: TODO [imbrandon] Clarify documentention on what to expect when your using LXC and EC2. Cost, wait time, what you see, logs, downloading. "You should expect this to download 300 megs, etc." Here's a table of look here troubleshooting your LXC thing.: TODO [hazmat] make juju report on initial lxc image downloads ?: TODO [hazmat] make juju lxc use lxc networking instead of libvirt networking ?: TODO -- Juju Charm Best practices https://blueprints.launchpad.net/ubuntu/+spec/servercloud-q-juju-charm-best-practices -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Blueprint servercloud-q-juju-charm-best-practices] Juju Charm Best practices
Blueprint changed by Kapil Thangavelu: Work items changed: Work items: [jorge] Pick better example charms, "flagbearer charms".: TODO [jorge] Choose a single place for presenting flagbearer charms (charm browser?): TODO [jorge] Move rules and charm best practices into juju/docs.: DONE [jorge] Add Maintainer field information to documentation. (thanks clint!): DONE [jorge] Reach out to maintainers to get their maintainer field filled out.: INPROGRESS [jorge] Add docs work items to patch pilot!: DONE [jorge] pull "file bug" or "join the doc team" from other projects: TODO [jorge] Clarify documentention on what to expect when your using LXC and EC2. Cost, wait time, what you see, logs, downloading. "You should expect this to download 300 megs, etc." Here's a table of look here troubleshooting your LXC thing: DONE [imbrandon] Reach out to maintainers to get their maintainer filled out.: TODO [imbrandon] Put Doc instructions in the docs: http://askubuntu.com/q/52063 : TODO [mark-mims] (and individual maintainers!) clean up existing charms wrt best practices: TODO [clint-fewbar] Comment and add links to docs in 'charm create' templates: TODO [clint-fewbar] juju in Debian! NOW!: DONE [clint-fewbar] determine most likely maintainers based on bzr logs: DONE [clint-fewbar] fix doc repos wrt (trunk, go, docs): DONE [marcoceppi] tag:juju review on AU and SE network: TODO - [hazmat] incorporate output of charm proof into charm browser: TODO - [hazmat] clear out trunk docs for juju: TODO + [hazmat] incorporate output of charm proof into charm browser: DONE + [hazmat] clear out trunk docs for juju: DONE [imbrandon] Clarify documentention on what to expect when your using LXC and EC2. Cost, wait time, what you see, logs, downloading. "You should expect this to download 300 megs, etc." Here's a table of look here troubleshooting your LXC thing.: TODO [imbrandon] Clarify documentention on what to expect when your using LXC and EC2. Cost, wait time, what you see, logs, downloading. "You should expect this to download 300 megs, etc." Here's a table of look here troubleshooting your LXC thing.: TODO [hazmat] make juju report on initial lxc image downloads ?: TODO [hazmat] make juju lxc use lxc networking instead of libvirt networking ?: TODO -- Juju Charm Best practices https://blueprints.launchpad.net/ubuntu/+spec/servercloud-q-juju-charm-best-practices -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Blueprint servercloud-q-juju-charm-best-practices] Juju Charm Best practices
Blueprint changed by Clint Byrum: Work items changed: Work items: [jorge] Pick better example charms, "flagbearer charms".: TODO [jorge] Choose a single place for presenting flagbearer charms (charm browser?): TODO [jorge] Move rules and charm best practices into juju/docs.: DONE [jorge] Add Maintainer field information to documentation. (thanks clint!): DONE [jorge] Reach out to maintainers to get their maintainer field filled out.: INPROGRESS [jorge] Add docs work items to patch pilot!: DONE [jorge] pull "file bug" or "join the doc team" from other projects: TODO [jorge] Clarify documentention on what to expect when your using LXC and EC2. Cost, wait time, what you see, logs, downloading. "You should expect this to download 300 megs, etc." Here's a table of look here troubleshooting your LXC thing: DONE [imbrandon] Reach out to maintainers to get their maintainer filled out.: TODO [imbrandon] Put Doc instructions in the docs: http://askubuntu.com/q/52063 : TODO [mark-mims] (and individual maintainers!) clean up existing charms wrt best practices: TODO [clint-fewbar] Comment and add links to docs in 'charm create' templates: TODO - [clint-fewbar] juju in Debian! NOW!: TODO - [clint-fewbar] determine most likely maintainers based on bzr logs: TODO - [clint-fewbar] fix doc repos wrt (trunk, go, docs): TODO + [clint-fewbar] juju in Debian! NOW!: DONE + [clint-fewbar] determine most likely maintainers based on bzr logs: DONE + [clint-fewbar] fix doc repos wrt (trunk, go, docs): DONE [marcoceppi] tag:juju review on AU and SE network: TODO [hazmat] incorporate output of charm proof into charm browser: TODO [hazmat] clear out trunk docs for juju: TODO [imbrandon] Clarify documentention on what to expect when your using LXC and EC2. Cost, wait time, what you see, logs, downloading. "You should expect this to download 300 megs, etc." Here's a table of look here troubleshooting your LXC thing.: TODO [imbrandon] Clarify documentention on what to expect when your using LXC and EC2. Cost, wait time, what you see, logs, downloading. "You should expect this to download 300 megs, etc." Here's a table of look here troubleshooting your LXC thing.: TODO [hazmat] make juju report on initial lxc image downloads ?: TODO [hazmat] make juju lxc use lxc networking instead of libvirt networking ?: TODO -- Juju Charm Best practices https://blueprints.launchpad.net/ubuntu/+spec/servercloud-q-juju-charm-best-practices -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Blueprint servercloud-q-juju-charm-best-practices] Juju Charm Best practices
Blueprint changed by Jorge O. Castro: Work items changed: Work items: [jorge] Pick better example charms, "flagbearer charms".: TODO [jorge] Choose a single place for presenting flagbearer charms (charm browser?): TODO [jorge] Move rules and charm best practices into juju/docs.: DONE [jorge] Add Maintainer field information to documentation. (thanks clint!): DONE [jorge] Reach out to maintainers to get their maintainer field filled out.: INPROGRESS [jorge] Add docs work items to patch pilot!: DONE [jorge] pull "file bug" or "join the doc team" from other projects: TODO - [jorge] Clarify documentention on what to expect when your using LXC and EC2. Cost, wait time, what you see, logs, downloading. "You should expect this to download 300 megs, etc." Here's a table of look here troubleshooting your LXC thing: TODO + [jorge] Clarify documentention on what to expect when your using LXC and EC2. Cost, wait time, what you see, logs, downloading. "You should expect this to download 300 megs, etc." Here's a table of look here troubleshooting your LXC thing: DONE [imbrandon] Reach out to maintainers to get their maintainer filled out.: TODO [imbrandon] Put Doc instructions in the docs: http://askubuntu.com/q/52063 : TODO [mark-mims] (and individual maintainers!) clean up existing charms wrt best practices: TODO [clint-fewbar] Comment and add links to docs in 'charm create' templates: TODO [clint-fewbar] juju in Debian! NOW!: TODO [clint-fewbar] determine most likely maintainers based on bzr logs: TODO [clint-fewbar] fix doc repos wrt (trunk, go, docs): TODO [marcoceppi] tag:juju review on AU and SE network: TODO [hazmat] incorporate output of charm proof into charm browser: TODO [hazmat] clear out trunk docs for juju: TODO [imbrandon] Clarify documentention on what to expect when your using LXC and EC2. Cost, wait time, what you see, logs, downloading. "You should expect this to download 300 megs, etc." Here's a table of look here troubleshooting your LXC thing.: TODO [imbrandon] Clarify documentention on what to expect when your using LXC and EC2. Cost, wait time, what you see, logs, downloading. "You should expect this to download 300 megs, etc." Here's a table of look here troubleshooting your LXC thing.: TODO [hazmat] make juju report on initial lxc image downloads ?: TODO [hazmat] make juju lxc use lxc networking instead of libvirt networking ?: TODO -- Juju Charm Best practices https://blueprints.launchpad.net/ubuntu/+spec/servercloud-q-juju-charm-best-practices -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Blueprint servercloud-q-juju-charm-best-practices] Juju Charm Best practices
Blueprint changed by Jorge O. Castro: Work items changed: Work items: [jorge] Pick better example charms, "flagbearer charms".: TODO [jorge] Choose a single place for presenting flagbearer charms (charm browser?): TODO [jorge] Move rules and charm best practices into juju/docs.: DONE [jorge] Add Maintainer field information to documentation. (thanks clint!): DONE - [jorge] Reach out to maintainers to get their maintainer field filled out.: TODO + [jorge] Reach out to maintainers to get their maintainer field filled out.: INPROGRESS [jorge] Add docs work items to patch pilot!: DONE [jorge] pull "file bug" or "join the doc team" from other projects: TODO [jorge] Clarify documentention on what to expect when your using LXC and EC2. Cost, wait time, what you see, logs, downloading. "You should expect this to download 300 megs, etc." Here's a table of look here troubleshooting your LXC thing: TODO [imbrandon] Reach out to maintainers to get their maintainer filled out.: TODO [imbrandon] Put Doc instructions in the docs: http://askubuntu.com/q/52063 : TODO [mark-mims] (and individual maintainers!) clean up existing charms wrt best practices: TODO [clint-fewbar] Comment and add links to docs in 'charm create' templates: TODO [clint-fewbar] juju in Debian! NOW!: TODO [clint-fewbar] determine most likely maintainers based on bzr logs: TODO [clint-fewbar] fix doc repos wrt (trunk, go, docs): TODO [marcoceppi] tag:juju review on AU and SE network: TODO [hazmat] incorporate output of charm proof into charm browser: TODO [hazmat] clear out trunk docs for juju: TODO [imbrandon] Clarify documentention on what to expect when your using LXC and EC2. Cost, wait time, what you see, logs, downloading. "You should expect this to download 300 megs, etc." Here's a table of look here troubleshooting your LXC thing.: TODO [imbrandon] Clarify documentention on what to expect when your using LXC and EC2. Cost, wait time, what you see, logs, downloading. "You should expect this to download 300 megs, etc." Here's a table of look here troubleshooting your LXC thing.: TODO [hazmat] make juju report on initial lxc image downloads ?: TODO [hazmat] make juju lxc use lxc networking instead of libvirt networking ?: TODO -- Juju Charm Best practices https://blueprints.launchpad.net/ubuntu/+spec/servercloud-q-juju-charm-best-practices -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Blueprint servercloud-q-juju-charm-best-practices] Juju Charm Best practices
Blueprint changed by Jorge O. Castro: Work items changed: Work items: [jorge] Pick better example charms, "flagbearer charms".: TODO [jorge] Choose a single place for presenting flagbearer charms (charm browser?): TODO [jorge] Move rules and charm best practices into juju/docs.: DONE [jorge] Add Maintainer field information to documentation. (thanks clint!): DONE [jorge] Reach out to maintainers to get their maintainer field filled out.: TODO - [jorge] Add docs work items to patch pilot!: TODO + [jorge] Add docs work items to patch pilot!: DONE [jorge] pull "file bug" or "join the doc team" from other projects: TODO [jorge] Clarify documentention on what to expect when your using LXC and EC2. Cost, wait time, what you see, logs, downloading. "You should expect this to download 300 megs, etc." Here's a table of look here troubleshooting your LXC thing: TODO [imbrandon] Reach out to maintainers to get their maintainer filled out.: TODO [imbrandon] Put Doc instructions in the docs: http://askubuntu.com/q/52063 : TODO [mark-mims] (and individual maintainers!) clean up existing charms wrt best practices: TODO [clint-fewbar] Comment and add links to docs in 'charm create' templates: TODO [clint-fewbar] juju in Debian! NOW!: TODO [clint-fewbar] determine most likely maintainers based on bzr logs: TODO [clint-fewbar] fix doc repos wrt (trunk, go, docs): TODO [marcoceppi] tag:juju review on AU and SE network: TODO [hazmat] incorporate output of charm proof into charm browser: TODO [hazmat] clear out trunk docs for juju: TODO [imbrandon] Clarify documentention on what to expect when your using LXC and EC2. Cost, wait time, what you see, logs, downloading. "You should expect this to download 300 megs, etc." Here's a table of look here troubleshooting your LXC thing.: TODO [imbrandon] Clarify documentention on what to expect when your using LXC and EC2. Cost, wait time, what you see, logs, downloading. "You should expect this to download 300 megs, etc." Here's a table of look here troubleshooting your LXC thing.: TODO [hazmat] make juju report on initial lxc image downloads ?: TODO [hazmat] make juju lxc use lxc networking instead of libvirt networking ?: TODO -- Juju Charm Best practices https://blueprints.launchpad.net/ubuntu/+spec/servercloud-q-juju-charm-best-practices -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Blueprint servercloud-q-juju-charm-best-practices] Juju Charm Best practices
Blueprint changed by Antonio Rosales: Definition Status: Drafting => Approved -- Juju Charm Best practices https://blueprints.launchpad.net/ubuntu/+spec/servercloud-q-juju-charm-best-practices -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Blueprint servercloud-q-juju-charm-best-practices] Juju Charm Best practices
Blueprint changed by Antonio Rosales: Whiteboard changed: * charm-tools -- charm proof should do everything it can to statically analyze and guide users * man pages are needed sorely * charm-helpers -- Gather tools which are useful for sharing between many charms * python helpers have been proposed, but blocked up on needing to package some extra python deps * Policy -- Policy is somewhat loose, just listed on https://juju.ubuntu.com/Charms * Should be useful information for writing charms, not just "rules" * Perhaps this should be moved into a versioned RST inside charm-tools? charm best practices: aka. "Charm tools all the things!" time to be opinionated? alternatively point to more example charms? also juju best practices: this is really a charm best-practice for now... flag-bearing charms should include a _good_ readme. (see lp:charms/hadoop for an example) BEST PRACTICES == * run charm proof before submitting * use charm helpers --- - Please integrate the spec @ https://wiki.ubuntu.com/BlueprintSpec [a.rosales]. + User Stories: + * Simon is new to the Charm community and woud like to charm his newest web service. He consults the best practices documentation and reviews example charms, man pages, and downloads charm tools to help him as he charms his web service for inclusion in the Charm Store. + + Assumptions: + * Extra Python deps are available for charm-helpers. + + Test Plans: + * Gather feedback from new Charmers on how the charm tools and best practice documentation helped them in the creation of Charms. Possibly gather this data at Charm schools. + + Release Note: + * Provide information on where to get charm tools and read Charm best practices. -- Juju Charm Best practices https://blueprints.launchpad.net/ubuntu/+spec/servercloud-q-juju-charm-best-practices -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Blueprint servercloud-q-juju-charm-best-practices] Juju Charm Best practices
Blueprint changed by Jorge O. Castro: Work items changed: Work items: [jorge] Pick better example charms, "flagbearer charms".: TODO [jorge] Choose a single place for presenting flagbearer charms (charm browser?): TODO - [jorge] Move rules and charm best practices into juju/docs.: TODO - [jorge] Add Maintainer field information to documentation.: TODO + [jorge] Move rules and charm best practices into juju/docs.: DONE + [jorge] Add Maintainer field information to documentation. (thanks clint!): DONE [jorge] Reach out to maintainers to get their maintainer field filled out.: TODO [jorge] Add docs work items to patch pilot!: TODO [jorge] pull "file bug" or "join the doc team" from other projects: TODO [jorge] Clarify documentention on what to expect when your using LXC and EC2. Cost, wait time, what you see, logs, downloading. "You should expect this to download 300 megs, etc." Here's a table of look here troubleshooting your LXC thing: TODO [imbrandon] Reach out to maintainers to get their maintainer filled out.: TODO [imbrandon] Put Doc instructions in the docs: http://askubuntu.com/q/52063 : TODO - [imbrandon] Clarify documentention on what to expect when your using LXC and EC2. Cost, wait time, what you see, logs, downloading. "You should expect this to download 300 megs, etc." Here's a table of look here troubleshooting your LXC thing.: TODO [mark-mims] (and individual maintainers!) clean up existing charms wrt best practices: TODO [clint-fewbar] Comment and add links to docs in 'charm create' templates: TODO [clint-fewbar] juju in Debian! NOW!: TODO [clint-fewbar] determine most likely maintainers based on bzr logs: TODO [clint-fewbar] fix doc repos wrt (trunk, go, docs): TODO [marcoceppi] tag:juju review on AU and SE network: TODO [hazmat] incorporate output of charm proof into charm browser: TODO [hazmat] clear out trunk docs for juju: TODO [imbrandon] Clarify documentention on what to expect when your using LXC and EC2. Cost, wait time, what you see, logs, downloading. "You should expect this to download 300 megs, etc." Here's a table of look here troubleshooting your LXC thing.: TODO + [imbrandon] Clarify documentention on what to expect when your using LXC and EC2. Cost, wait time, what you see, logs, downloading. "You should expect this to download 300 megs, etc." Here's a table of look here troubleshooting your LXC thing.: TODO [hazmat] make juju report on initial lxc image downloads ?: TODO [hazmat] make juju lxc use lxc networking instead of libvirt networking ?: TODO -- Juju Charm Best practices https://blueprints.launchpad.net/ubuntu/+spec/servercloud-q-juju-charm-best-practices -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Blueprint servercloud-q-juju-charm-best-practices] Juju Charm Best practices
Blueprint changed by Antonio Rosales: Definition Status: Discussion => Drafting -- Juju Charm Best practices https://blueprints.launchpad.net/ubuntu/+spec/servercloud-q-juju-charm-best-practices -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Blueprint servercloud-q-juju-charm-best-practices] Juju Charm Best practices
Blueprint changed by Antonio Rosales: Whiteboard changed: * charm-tools -- charm proof should do everything it can to statically analyze and guide users * man pages are needed sorely * charm-helpers -- Gather tools which are useful for sharing between many charms * python helpers have been proposed, but blocked up on needing to package some extra python deps * Policy -- Policy is somewhat loose, just listed on https://juju.ubuntu.com/Charms * Should be useful information for writing charms, not just "rules" * Perhaps this should be moved into a versioned RST inside charm-tools? charm best practices: aka. "Charm tools all the things!" time to be opinionated? alternatively point to more example charms? also juju best practices: this is really a charm best-practice for now... flag-bearing charms should include a _good_ readme. (see lp:charms/hadoop for an example) BEST PRACTICES == * run charm proof before submitting * use charm helpers + + --- + Please integrate the spec @ https://wiki.ubuntu.com/BlueprintSpec [a.rosales]. -- Juju Charm Best practices https://blueprints.launchpad.net/ubuntu/+spec/servercloud-q-juju-charm-best-practices -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Blueprint servercloud-q-juju-charm-best-practices] Juju Charm Best practices
Blueprint changed by Antonio Rosales: Priority: Undefined => Medium -- Juju Charm Best practices https://blueprints.launchpad.net/ubuntu/+spec/servercloud-q-juju-charm-best-practices -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Blueprint servercloud-q-juju-charm-best-practices] Juju Charm Best practices
Blueprint changed by Antonio Rosales: Approver: Robbie Williamson => Antonio Rosales -- Juju Charm Best practices https://blueprints.launchpad.net/ubuntu/+spec/servercloud-q-juju-charm-best-practices -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Blueprint servercloud-q-juju-charm-best-practices] Juju Charm Best practices
Blueprint changed by Jorge O. Castro: Work items changed: Work items: [jorge] Pick better example charms, "flagbearer charms".: TODO [jorge] Choose a single place for presenting flagbearer charms (charm browser?): TODO + [jorge] Move rules and charm best practices into juju/docs.: TODO + [jorge] Add Maintainer field information to documentation.: TODO + [jorge] Reach out to maintainers to get their maintainer field filled out.: TODO + [jorge] Add docs work items to patch pilot!: TODO + [jorge] pull "file bug" or "join the doc team" from other projects: TODO + [jorge] Clarify documentention on what to expect when your using LXC and EC2. Cost, wait time, what you see, logs, downloading. "You should expect this to download 300 megs, etc." Here's a table of look here troubleshooting your LXC thing: TODO + [imbrandon] Reach out to maintainers to get their maintainer filled out.: TODO + [imbrandon] Put Doc instructions in the docs: http://askubuntu.com/q/52063 : TODO + [imbrandon] Clarify documentention on what to expect when your using LXC and EC2. Cost, wait time, what you see, logs, downloading. "You should expect this to download 300 megs, etc." Here's a table of look here troubleshooting your LXC thing.: TODO [mark-mims] (and individual maintainers!) clean up existing charms wrt best practices: TODO [clint-fewbar] Comment and add links to docs in 'charm create' templates: TODO + [clint-fewbar] juju in Debian! NOW!: TODO + [clint-fewbar] determine most likely maintainers based on bzr logs: TODO + [clint-fewbar] fix doc repos wrt (trunk, go, docs): TODO + [marcoceppi] tag:juju review on AU and SE network: TODO [hazmat] incorporate output of charm proof into charm browser: TODO - [jorge] Move rules and charm best practices into docs.: TODO - [jorge] Add Maintainer field information to documents.: TODO - [clint-fewbar] determine most likely maintainers based on bzr logs: TODO - [jorge] Reach out to maintainers to get their maintainer firled filled out.: TODO - [imbrandon] Reach out to maintainers to get their maintainer filled out.: TODO - [marcoceppi] tag:juju review on AU and SE network: TODO - [clint-fewbar] fix doc repos wrt (trunk, go, docs): TODO - [imbrandon] Put Doc instructions in the docs: http://askubuntu.com/q/52063 : TODO - [jcastro] pull "file bug" or "join the doc team" from other projects: TODO [hazmat] clear out trunk docs for juju: TODO + [imbrandon] Clarify documentention on what to expect when your using LXC and EC2. Cost, wait time, what you see, logs, downloading. "You should expect this to download 300 megs, etc." Here's a table of look here troubleshooting your LXC thing.: TODO [hazmat] make juju report on initial lxc image downloads ?: TODO [hazmat] make juju lxc use lxc networking instead of libvirt networking ?: TODO - [jorge] Clarify documentention on what to expect when your using LXC and EC2. Cost, wait time, what you see, logs, downloading. "You should expect this to download 300 megs, etc." Here's a table of look here troubleshooting your LXC thing.: TODO - [imbrandon] Clarify documentention on what to expect when your using LXC and EC2. Cost, wait time, what you see, logs, downloading. "You should expect this to download 300 megs, etc." Here's a table of look here troubleshooting your LXC thing.: TODO - [clint-fewbar] juju in Debian! NOW!: TODO - [jorge] Add docs work to patch pilot!! (AW YEAA!): TODO -- Juju Charm Best practices https://blueprints.launchpad.net/ubuntu/+spec/servercloud-q-juju-charm-best-practices -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Blueprint servercloud-q-juju-charm-best-practices] Juju Charm Best practices
Blueprint changed by Jorge O. Castro: Whiteboard changed: * charm-tools -- charm proof should do everything it can to statically analyze and guide users * man pages are needed sorely * charm-helpers -- Gather tools which are useful for sharing between many charms * python helpers have been proposed, but blocked up on needing to package some extra python deps * Policy -- Policy is somewhat loose, just listed on https://juju.ubuntu.com/Charms * Should be useful information for writing charms, not just "rules" * Perhaps this should be moved into a versioned RST inside charm-tools? charm best practices: aka. "Charm tools all the things!" - time to be opinionated? + time to be opinionated? alternatively point to more example charms? also juju best practices: - this is really a charm best-practice for now... flag-bearing charms should include a _good_ readme. - (see lp:charms/hadoop for an example) + this is really a charm best-practice for now... flag-bearing charms should include a _good_ readme. + (see lp:charms/hadoop for an example) BEST PRACTICES == * run charm proof before submitting * use charm helpers - - - WORK ITEMS - === - [jorge] Pick better example charms, "flagbearer charms". - [jorge] Choose a single place for presenting flagbearer charms (charm browser?) - [mark-mims] (and individual maintainers!) clean up existing charms wrt best practices - [clint-fewbar] Comment and add links to docs in 'charm create' templates - [hazmat] incorporate output of charm proof into charm browser - [jorge] Move rules and charm best practices into docs. - [jorge] Add Maintainer field information to documents. - [clint-fewbar] determine most likely maintainers based on bzr logs - [jorge] Reach out to maintainers to get their maintainer firled filled out. - [imbrandon] Reach out to maintainers to get their maintainer filled out. - [marcoceppi] tag:juju review on AU and SE network - [clint-fewbar] fix doc repos wrt (trunk, go, docs) - [imbrandon] Put Doc instructions in the docs: http://askubuntu.com/q/52063 - [jcastro] pull "file bug" or "join the doc team" from other projects - [hazmat] clear out trunk docs for juju - [hazmat] make juju report on initial lxc image downloads ? - [hazmat] make juju lxc use lxc networking instead of libvirt networking ? - [jorge] Clarify documentention on what to expect when your using LXC and EC2. Cost, wait time, what you see, logs, downloading. "You should expect this to download 300 megs, etc." Here's a table of look here troubleshooting your LXC thing. - [imbrandon] Clarify documentention on what to expect when your using LXC and EC2. Cost, wait time, what you see, logs, downloading. "You should expect this to download 300 megs, etc." Here's a table of look here troubleshooting your LXC thing. - [clint-fewbar] juju in Debian! NOW! - [jorge] Add docs work to patch pilot!! (AW YEAA!) -- Juju Charm Best practices https://blueprints.launchpad.net/ubuntu/+spec/servercloud-q-juju-charm-best-practices -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Blueprint servercloud-q-juju-charm-best-practices] Juju Charm Best practices
Blueprint changed by Jorge O. Castro: Work items set to: Work items: [jorge] Pick better example charms, "flagbearer charms".: TODO [jorge] Choose a single place for presenting flagbearer charms (charm browser?): TODO [mark-mims] (and individual maintainers!) clean up existing charms wrt best practices: TODO [clint-fewbar] Comment and add links to docs in 'charm create' templates: TODO [hazmat] incorporate output of charm proof into charm browser: TODO [jorge] Move rules and charm best practices into docs.: TODO [jorge] Add Maintainer field information to documents.: TODO [clint-fewbar] determine most likely maintainers based on bzr logs: TODO [jorge] Reach out to maintainers to get their maintainer firled filled out.: TODO [imbrandon] Reach out to maintainers to get their maintainer filled out.: TODO [marcoceppi] tag:juju review on AU and SE network: TODO [clint-fewbar] fix doc repos wrt (trunk, go, docs): TODO [imbrandon] Put Doc instructions in the docs: http://askubuntu.com/q/52063 : TODO [jcastro] pull "file bug" or "join the doc team" from other projects: TODO [hazmat] clear out trunk docs for juju: TODO [hazmat] make juju report on initial lxc image downloads ?: TODO [hazmat] make juju lxc use lxc networking instead of libvirt networking ?: TODO [jorge] Clarify documentention on what to expect when your using LXC and EC2. Cost, wait time, what you see, logs, downloading. "You should expect this to download 300 megs, etc." Here's a table of look here troubleshooting your LXC thing.: TODO [imbrandon] Clarify documentention on what to expect when your using LXC and EC2. Cost, wait time, what you see, logs, downloading. "You should expect this to download 300 megs, etc." Here's a table of look here troubleshooting your LXC thing.: TODO [clint-fewbar] juju in Debian! NOW!: TODO [jorge] Add docs work to patch pilot!! (AW YEAA!): TODO -- Juju Charm Best practices https://blueprints.launchpad.net/ubuntu/+spec/servercloud-q-juju-charm-best-practices -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Blueprint servercloud-q-juju-charm-best-practices] Juju Charm Best practices
Blueprint changed by Jorge O. Castro: Whiteboard changed: * charm-tools -- charm proof should do everything it can to statically analyze and guide users - * man pages are needed sorely + * man pages are needed sorely * charm-helpers -- Gather tools which are useful for sharing between many charms - * python helpers have been proposed, but blocked up on needing to package some extra python deps + * python helpers have been proposed, but blocked up on needing to package some extra python deps * Policy -- Policy is somewhat loose, just listed on https://juju.ubuntu.com/Charms - * Should be useful information for writing charms, not just "rules" - * Perhaps this should be moved into a versioned RST inside charm-tools? + * Should be useful information for writing charms, not just "rules" + * Perhaps this should be moved into a versioned RST inside charm-tools? + + charm best practices: + + aka. "Charm tools all the things!" + + time to be opinionated? + alternatively point to more example charms? + + also juju best practices: + this is really a charm best-practice for now... flag-bearing charms should include a _good_ readme. + (see lp:charms/hadoop for an example) + + BEST PRACTICES + == + + * run charm proof before submitting * + use charm helpers + + + WORK ITEMS + === + [jorge] Pick better example charms, "flagbearer charms". + [jorge] Choose a single place for presenting flagbearer charms (charm browser?) + [mark-mims] (and individual maintainers!) clean up existing charms wrt best practices + [clint-fewbar] Comment and add links to docs in 'charm create' templates + [hazmat] incorporate output of charm proof into charm browser + [jorge] Move rules and charm best practices into docs. + [jorge] Add Maintainer field information to documents. + [clint-fewbar] determine most likely maintainers based on bzr logs + [jorge] Reach out to maintainers to get their maintainer firled filled out. + [imbrandon] Reach out to maintainers to get their maintainer filled out. + [marcoceppi] tag:juju review on AU and SE network + [clint-fewbar] fix doc repos wrt (trunk, go, docs) + [imbrandon] Put Doc instructions in the docs: http://askubuntu.com/q/52063 + [jcastro] pull "file bug" or "join the doc team" from other projects + [hazmat] clear out trunk docs for juju + [hazmat] make juju report on initial lxc image downloads ? + [hazmat] make juju lxc use lxc networking instead of libvirt networking ? + [jorge] Clarify documentention on what to expect when your using LXC and EC2. Cost, wait time, what you see, logs, downloading. "You should expect this to download 300 megs, etc." Here's a table of look here troubleshooting your LXC thing. + [imbrandon] Clarify documentention on what to expect when your using LXC and EC2. Cost, wait time, what you see, logs, downloading. "You should expect this to download 300 megs, etc." Here's a table of look here troubleshooting your LXC thing. + [clint-fewbar] juju in Debian! NOW! + [jorge] Add docs work to patch pilot!! (AW YEAA!) -- Juju Charm Best practices https://blueprints.launchpad.net/ubuntu/+spec/servercloud-q-juju-charm-best-practices -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Blueprint servercloud-q-juju-charm-best-practices] Juju Charm Best practices
Blueprint changed by Clint Byrum: Whiteboard set to: * charm-tools -- charm proof should do everything it can to statically analyze and guide users * man pages are needed sorely * charm-helpers -- Gather tools which are useful for sharing between many charms * python helpers have been proposed, but blocked up on needing to package some extra python deps * Policy -- Policy is somewhat loose, just listed on https://juju.ubuntu.com/Charms * Should be useful information for writing charms, not just "rules" * Perhaps this should be moved into a versioned RST inside charm-tools? -- Juju Charm Best practices https://blueprints.launchpad.net/ubuntu/+spec/servercloud-q-juju-charm-best-practices -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Blueprint servercloud-q-juju-charm-best-practices] Juju Charm Best practices
Blueprint changed by Robbie Williamson: Drafter: (none) => Ubuntu Server Team -- Juju Charm Best practices https://blueprints.launchpad.net/ubuntu/+spec/servercloud-q-juju-charm-best-practices -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs