[Bug 1267242] [NEW] Running lxc-ls as non-root should provide a nicer error message
Public bug reported: You need root to run lxc-ls now, but this happens: jorge@jilldactyl:~$ lxc-ls lxc: Permission denied - opendir on lxcpath Traceback (most recent call last): File /usr/bin/lxc-ls, line 200, in module for container_name in lxc.list_containers(config_path=lxcpath): File /usr/lib/python3/dist-packages/lxc/__init__.py, line 390, in list_containers config_path=config_path) ValueError: failure to list containers I asked Serge: hallyn jcastro: you have to run lxc-ls as root now jcastro: however, it shouldn't give you a backtrace like that, just a nice error msg hallyn so that's bug-worthy ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: lxc 1.0.0~beta1-0ubuntu3 ProcVersionSignature: Ubuntu 3.12.0-7.15-generic 3.12.4 Uname: Linux 3.12.0-7-generic x86_64 ApportVersion: 2.12.7-0ubuntu6 Architecture: amd64 CurrentDesktop: Unity Date: Wed Jan 8 15:56:45 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2013-12-11 (28 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) SourcePackage: lxc UpgradeStatus: Upgraded to trusty on 2014-01-07 (1 days ago) defaults.conf: lxc.network.type = veth lxc.network.link = lxcbr0 lxc.network.flags = up lxcsyslog: ** Affects: lxc (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1267242 Title: Running lxc-ls as non-root should provide a nicer error message To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1267242/+subscriptions -- 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
[Bug 1234627] Re: python dependencies missing: markdown and distribute
*** This bug is a duplicate of bug 1231441 *** https://bugs.launchpad.net/bugs/1231441 ** Changed in: charm-tools (Ubuntu) Assignee: (unassigned) = Marco Ceppi (marcoceppi) ** Changed in: charm-tools (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to charm-tools in Ubuntu. https://bugs.launchpad.net/bugs/1234627 Title: python dependencies missing: markdown and distribute To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/charm-tools/+bug/1234627/+subscriptions -- 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-s-juju-contributor-onramp] Juju Contributor Onramp
Blueprint changed by Jorge O. Castro: Work items changed: Work items for ubuntu-13.05: - [jorge] : Highlight Places where people can contribute (https://trello.com/c/RYkKAfH2/314-contributoronramp-highlight-places-where-people-can-contribute): TODO + [jorge] : Highlight Places where people can contribute (https://trello.com/c/RYkKAfH2/314-contributoronramp-highlight-places-where-people-can-contribute): DONE Work items: - [jorge] : Lower the Barrier to entry (https://trello.com/c/1e4Zjzgu/316-contributoronramp-lower-the-barrier-to-entry): TODO + [jorge] : Lower the Barrier to entry (https://trello.com/c/1e4Zjzgu/316-contributoronramp-lower-the-barrier-to-entry): DONE [jorge] Create Problem Tracker for issues found by users (https://trello.com/c/kmBnddSh/355-contributoronramp-create-problem-tracker-for-issues-found-by-users): DONE -- Juju Contributor Onramp https://blueprints.launchpad.net/ubuntu/+spec/servercloud-s-juju-contributor-onramp -- 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-s-juju-contributor-onramp] Juju Contributor Onramp
Blueprint changed by Jorge O. Castro: Work items changed: - Work items for ubuntu-13.04-month-6: - [jjo] Case Studies from webops (move to 2.0 messaging): TODO - [mthaddon] Case Studies from webops (move to 2.0 messaging): TODO - [timrchavez] Case Studies from PES (move to 2.0 messaging): TODO - Work items for ubuntu-13.05: [jorge] : Highlight Places where people can contribute: TODO Work items: [jorge] : Lower the Barrier to entry: TODO [jorge] Create Problem Tracker for issues found by: TODO -- Juju Contributor Onramp https://blueprints.launchpad.net/ubuntu/+spec/servercloud-s-juju-contributor-onramp -- 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-s-juju-contributor-onramp] Juju Contributor Onramp
Blueprint changed by Jorge O. Castro: Work items changed: Work items for ubuntu-13.05: [jorge] : Highlight Places where people can contribute: TODO Work items: [jorge] : Lower the Barrier to entry: TODO - [jorge] Create Problem Tracker for issues found by: TODO + [jorge] Create Problem Tracker for issues found by: DONE -- Juju Contributor Onramp https://blueprints.launchpad.net/ubuntu/+spec/servercloud-s-juju-contributor-onramp -- 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
[Bug 1190634] [NEW] Remove Juju .7 from Saucy
Public bug reported: `juju` is now superceded by `juju-core` and there's no need to keep the older version around. Please remove `juju-.7` and make `juju` default to the go version. Please nuke it from saucy, just to be sure. ** Affects: juju (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju in Ubuntu. https://bugs.launchpad.net/bugs/1190634 Title: Remove Juju .7 from Saucy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/juju/+bug/1190634/+subscriptions -- 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
[Bug 1183110] Re: Handshake error when first bootstrapping with AWS
** Tags added: cli-ui papercut -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju-core in Ubuntu. https://bugs.launchpad.net/bugs/1183110 Title: Handshake error when first bootstrapping with AWS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1183110/+subscriptions -- 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
[Bug 1182902] Re: juju help does not expose 'version' option
** Tags added: cli-ui papercut -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju-core in Ubuntu. https://bugs.launchpad.net/bugs/1182902 Title: juju help does not expose 'version' option To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1182902/+subscriptions -- 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
[Bug 1182901] Re: juju help does not expose version number
** Tags added: cli-ui papercut -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju-core in Ubuntu. https://bugs.launchpad.net/bugs/1182901 Title: juju help does not expose version number To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1182901/+subscriptions -- 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
[Bug 1182898] [NEW] Please support `juju --version`
Public bug reported: I know we have `juju version` but there's some UNIX law we're breaking if we don't support this common flag. Also please alias -v too. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: juju-core 1.10.0.1-0ubuntu1~ubuntu13.04.1 ProcVersionSignature: Ubuntu 3.8.0-19.30-generic 3.8.8 Uname: Linux 3.8.0-19-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 Date: Wed May 22 09:43:58 2013 Dependencies: InstallationDate: Installed on 2013-03-26 (56 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Alpha amd64 (20130326) MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: juju-core UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: juju-core (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug raring -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju-core in Ubuntu. https://bugs.launchpad.net/bugs/1182898 Title: Please support `juju --version` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1182898/+subscriptions -- 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-s-juju-contributor-onramp] Juju Contributor Onramp
Blueprint changed by Jorge O. Castro: Work items changed: Work items for ubuntu-13.04-month-6: [jjo] Case Studies from webops (move to 2.0 messaging): TODO [mthaddon] Case Studies from webops (move to 2.0 messaging): TODO [timrchavez] Case Studies from PES (move to 2.0 messaging): TODO + Work items for ubuntu-13.05: + [jorge] : Highlight Places where people can contribute: TODO + Work items: - [jorge] : Highlight Places where people can contribute: TODO [jorge] : Lower the Barrier to entry: TODO -- Juju Contributor Onramp https://blueprints.launchpad.net/ubuntu/+spec/servercloud-s-juju-contributor-onramp -- 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-s-juju-docs] Improve Juju Documentation
Blueprint changed by Jorge O. Castro: Work items changed: Work items: [evilnick] Define structural elements of HTML5 doc: DONE [evilnick] Create sample getting Started Guide: DONE [marcoceppi] Prepare rollout strategy for new docs launch: TODO [marcoceppi] Propose policy for inclusion of doc contributions as ~charmers contrib: TODO [jorge] Streamline contributions process in documentation: TODO [evilnick] Create video/webinar strategy: TODO [mark-mims] Testing structure for charm documentation: TODO [marcoceppi] Auto-generate charm interfaces documentation: TODO + [jorge] : Make sure our docs are synced on readthedocs.org: TODO -- Improve Juju Documentation https://blueprints.launchpad.net/ubuntu/+spec/servercloud-s-juju-docs -- 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-s-juju-contributor-onramp] Juju Contributor Onramp
Blueprint changed by Jorge O. Castro: Work items changed: Work items for ubuntu-13.04-month-6: [jorge] Contribute to this charm! link in the charm store.: BLOCKED [jorge] Tell people they can help. There's no mention of how to help on jujucharms.com. That sucks. Not make something and get a prize, make it make something you are going to use and get a prize.: BLOCKED [jorge] charm-tools, we need to talk about it more, make a Best practices for charms should be in write a charm, integrate the mythical best practices page with write a charm.: TODO [mark-mims] Investigate making charm documentation testable: TODO [evilnick] Investigate making charm documentation testable: TODO [jjo] Case Studies from webops (move to 2.0 messaging): TODO [mthaddon] Case Studies from webops (move to 2.0 messaging): TODO [timrchavez] Case Studies from PES (move to 2.0 messaging): TODO [jorge] Update /events page on juju.ubuntu.com to show where we are attending.: DONE [jorge] Investigate long running contests on juju.ubuntu.com: TODO [jorge] Ensure that the juju gui can run on the local provider: BLOCKED Work items: - [jorge] File bugs on charms that don't meet quality guidelines. it would be great if this charm did multimaster!! and so on, so people know that they can fix it. needs-scaleout tag?: BLOCKED - [jorge] Way to go, we have over 100 people who contributed charms and you told no one. Nice work.: TODO - jorge] Pimp my charm contest. or Xprize? Scale out HA x service to blah blah with integrated backups: TODO [jorge] : Rewrite submission process for charms.: TODO [jorge] : Get the gui guys to add mean response time measure.: TODO [jorge] : Schedule reviews for charm reviewers.: TODO [jorge] : Find 3 people and ask them to charm something to record it.: TODO [jorge] : At the end of the cycle, do more user testing.: TODO - [jorge] : Bitesize bugs for charms: TODO [a.rosales] : Quantify questions from charm schools. : TODO [a.rosales] : Sync up with webops (mthaddon wedgwood) wrt. charm feedback.: TODO [jorge] : Make a charm-school tag in lp for juju bugs so core team knows what are high visibility bugs: TODO + [jorge] : Highlight Places where people can contribute: TODO -- Juju Contributor Onramp https://blueprints.launchpad.net/ubuntu/+spec/servercloud-s-juju-contributor-onramp -- 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-s-juju-contributor-onramp] Juju Contributor Onramp
Blueprint changed by Jorge O. Castro: Work items changed: Work items for ubuntu-13.04-month-6: [jorge] Contribute to this charm! link in the charm store.: BLOCKED [jorge] Tell people they can help. There's no mention of how to help on jujucharms.com. That sucks. Not make something and get a prize, make it make something you are going to use and get a prize.: BLOCKED [jorge] charm-tools, we need to talk about it more, make a Best practices for charms should be in write a charm, integrate the mythical best practices page with write a charm.: TODO [mark-mims] Investigate making charm documentation testable: TODO [evilnick] Investigate making charm documentation testable: TODO [jjo] Case Studies from webops (move to 2.0 messaging): TODO [mthaddon] Case Studies from webops (move to 2.0 messaging): TODO [timrchavez] Case Studies from PES (move to 2.0 messaging): TODO [jorge] Update /events page on juju.ubuntu.com to show where we are attending.: DONE [jorge] Investigate long running contests on juju.ubuntu.com: TODO [jorge] Ensure that the juju gui can run on the local provider: BLOCKED Work items: [jorge] : Rewrite submission process for charms.: TODO [jorge] : Get the gui guys to add mean response time measure.: TODO [jorge] : Schedule reviews for charm reviewers.: TODO [jorge] : Find 3 people and ask them to charm something to record it.: TODO [jorge] : At the end of the cycle, do more user testing.: TODO [a.rosales] : Quantify questions from charm schools. : TODO [a.rosales] : Sync up with webops (mthaddon wedgwood) wrt. charm feedback.: TODO [jorge] : Make a charm-school tag in lp for juju bugs so core team knows what are high visibility bugs: TODO [jorge] : Highlight Places where people can contribute: TODO + [jorge] : Lower the Barrier to entry: TODO -- Juju Contributor Onramp https://blueprints.launchpad.net/ubuntu/+spec/servercloud-s-juju-contributor-onramp -- 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-s-juju-contributor-onramp] Juju Contributor Onramp
Blueprint changed by Jorge O. Castro: Work items changed: Work items for ubuntu-13.04-month-6: - [jorge] Contribute to this charm! link in the charm store.: BLOCKED - [jorge] Tell people they can help. There's no mention of how to help on jujucharms.com. That sucks. Not make something and get a prize, make it make something you are going to use and get a prize.: BLOCKED - [jorge] charm-tools, we need to talk about it more, make a Best practices for charms should be in write a charm, integrate the mythical best practices page with write a charm.: TODO [mark-mims] Investigate making charm documentation testable: TODO [evilnick] Investigate making charm documentation testable: TODO [jjo] Case Studies from webops (move to 2.0 messaging): TODO [mthaddon] Case Studies from webops (move to 2.0 messaging): TODO [timrchavez] Case Studies from PES (move to 2.0 messaging): TODO - [jorge] Update /events page on juju.ubuntu.com to show where we are attending.: DONE - [jorge] Investigate long running contests on juju.ubuntu.com: TODO - [jorge] Ensure that the juju gui can run on the local provider: BLOCKED Work items: - [a.rosales] : Quantify questions from charm schools. : TODO - [a.rosales] : Sync up with webops (mthaddon wedgwood) wrt. charm feedback.: TODO - [jorge] : Make a charm-school tag in lp for juju bugs so core team knows what are high visibility bugs: TODO [jorge] : Highlight Places where people can contribute: TODO [jorge] : Lower the Barrier to entry: TODO -- Juju Contributor Onramp https://blueprints.launchpad.net/ubuntu/+spec/servercloud-s-juju-contributor-onramp -- 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-s-juju-docs] Improve Juju Documentation
Blueprint changed by Jorge O. Castro: Work items changed: Work items: [evilnick] Define structural elements of HTML5 doc: DONE [evilnick] Create sample getting Started Guide: DONE [evilnick] Create list of screencasts: TODO [jorge] Develop Webinar/Screen cast education series mapped to Docs. (ie 12 sessions from getting started to Debugging): TODO [marcoceppi] Ensure URL rewrites work from olddocs to newdocs: TODO [mark-mims] Script diffs to CLI: TODO [evilnick] Publish list of videos and assign them to jorge, marco, mims, antonio, and whoever.: TODO [evilnick] Recirculate video template specs: TODO [jorge] Find out who will redub our stuff: TODO [jorge] How to contribute to Juju docs section, make sure it follow's nick's style guide: TODO [marcoceppi] Propose to list to allow contributions to docs to count as ~charmers contribution: TODO [marcoceppi] Investigate adding a chapter todo to the review queue: TODO [jorge] Update AU questions to point to newdocs: TODO [marcoceppi] Update AU questions to point to newdocs: TODO + [mark-mims] Investigate making charm documentation testable: TODO + [evilnick] Investigate making charm documentation testable: TODO -- Improve Juju Documentation https://blueprints.launchpad.net/ubuntu/+spec/servercloud-s-juju-docs -- 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-s-juju-contributor-onramp] Juju Contributor Onramp
Blueprint changed by Jorge O. Castro: Work items changed: Work items for ubuntu-13.04-month-6: - [mark-mims] Investigate making charm documentation testable: TODO - [evilnick] Investigate making charm documentation testable: TODO [jjo] Case Studies from webops (move to 2.0 messaging): TODO [mthaddon] Case Studies from webops (move to 2.0 messaging): TODO [timrchavez] Case Studies from PES (move to 2.0 messaging): TODO Work items: [jorge] : Highlight Places where people can contribute: TODO [jorge] : Lower the Barrier to entry: TODO -- Juju Contributor Onramp https://blueprints.launchpad.net/ubuntu/+spec/servercloud-s-juju-contributor-onramp -- 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-s-juju-contributor-onramp] Juju Contributor Onramp
Blueprint changed by Jorge O. Castro: Work items changed: Work items for ubuntu-13.04-month-6: [jorge] Contribute to this charm! link in the charm store.: BLOCKED [jorge] Tell people they can help. There's no mention of how to help on jujucharms.com. That sucks. Not make something and get a prize, make it make something you are going to use and get a prize.: BLOCKED [jorge] charm-tools, we need to talk about it more, make a Best practices for charms should be in write a charm, integrate the mythical best practices page with write a charm.: TODO [mark-mims] Investigate making charm documentation testable: TODO [evilnick] Investigate making charm documentation testable: TODO [jjo] Case Studies from webops (move to 2.0 messaging): TODO [mthaddon] Case Studies from webops (move to 2.0 messaging): TODO [timrchavez] Case Studies from PES (move to 2.0 messaging): TODO [jorge] Update /events page on juju.ubuntu.com to show where we are attending.: DONE [jorge] Investigate long running contests on juju.ubuntu.com: TODO [jorge] Ensure that the juju gui can run on the local provider: BLOCKED Work items: - [jorge] : Rewrite submission process for charms.: TODO - [jorge] : Get the gui guys to add mean response time measure.: TODO - [jorge] : Schedule reviews for charm reviewers.: TODO - [jorge] : Find 3 people and ask them to charm something to record it.: TODO - [jorge] : At the end of the cycle, do more user testing.: TODO [a.rosales] : Quantify questions from charm schools. : TODO [a.rosales] : Sync up with webops (mthaddon wedgwood) wrt. charm feedback.: TODO [jorge] : Make a charm-school tag in lp for juju bugs so core team knows what are high visibility bugs: TODO [jorge] : Highlight Places where people can contribute: TODO [jorge] : Lower the Barrier to entry: TODO -- Juju Contributor Onramp https://blueprints.launchpad.net/ubuntu/+spec/servercloud-s-juju-contributor-onramp -- 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-s-juju-docs] Improve Juju Documentation
Blueprint changed by Jorge O. Castro: Work items changed: Work items: [evilnick] Define structural elements of HTML5 doc: DONE [evilnick] Create sample getting Started Guide: DONE [evilnick] Create list of screencasts: TODO [jorge] Develop Webinar/Screen cast education series mapped to Docs. (ie 12 sessions from getting started to Debugging): TODO + [marcoceppi] Ensure URL rewrites work from olddocs to newdocs: TODO -- Improve Juju Documentation https://blueprints.launchpad.net/ubuntu/+spec/servercloud-s-juju-docs -- 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-s-juju-docs] Improve Juju Documentation
Blueprint changed by Jorge O. Castro: Work items changed: Work items: [evilnick] Define structural elements of HTML5 doc: DONE [evilnick] Create sample getting Started Guide: DONE [evilnick] Create list of screencasts: TODO [jorge] Develop Webinar/Screen cast education series mapped to Docs. (ie 12 sessions from getting started to Debugging): TODO [marcoceppi] Ensure URL rewrites work from olddocs to newdocs: TODO + [mark-mims] Script diffs to CLI: TODO + [evilnick] Publish list of videos and assign them to jorge, marco, mims, antonio, and whoever.: TODO -- Improve Juju Documentation https://blueprints.launchpad.net/ubuntu/+spec/servercloud-s-juju-docs -- 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-s-juju-docs] Improve Juju Documentation
Blueprint changed by Jorge O. Castro: Work items changed: Work items: [evilnick] Define structural elements of HTML5 doc: DONE [evilnick] Create sample getting Started Guide: DONE [evilnick] Create list of screencasts: TODO [jorge] Develop Webinar/Screen cast education series mapped to Docs. (ie 12 sessions from getting started to Debugging): TODO [marcoceppi] Ensure URL rewrites work from olddocs to newdocs: TODO [mark-mims] Script diffs to CLI: TODO [evilnick] Publish list of videos and assign them to jorge, marco, mims, antonio, and whoever.: TODO + [evilnick] Recirculate video template specs: TODO + [jorge] Find out who will redub our stuff: TODO -- Improve Juju Documentation https://blueprints.launchpad.net/ubuntu/+spec/servercloud-s-juju-docs -- 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-s-juju-docs] Improve Juju Documentation
Blueprint changed by Jorge O. Castro: Work items changed: Work items: [evilnick] Define structural elements of HTML5 doc: DONE [evilnick] Create sample getting Started Guide: DONE [evilnick] Create list of screencasts: TODO [jorge] Develop Webinar/Screen cast education series mapped to Docs. (ie 12 sessions from getting started to Debugging): TODO [marcoceppi] Ensure URL rewrites work from olddocs to newdocs: TODO [mark-mims] Script diffs to CLI: TODO [evilnick] Publish list of videos and assign them to jorge, marco, mims, antonio, and whoever.: TODO [evilnick] Recirculate video template specs: TODO [jorge] Find out who will redub our stuff: TODO + [jorge] How to contribute to Juju docs section: TODO -- Improve Juju Documentation https://blueprints.launchpad.net/ubuntu/+spec/servercloud-s-juju-docs -- 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-s-juju-docs] Improve Juju Documentation
Blueprint changed by Jorge O. Castro: Work items changed: Work items: [evilnick] Define structural elements of HTML5 doc: DONE [evilnick] Create sample getting Started Guide: DONE [evilnick] Create list of screencasts: TODO [jorge] Develop Webinar/Screen cast education series mapped to Docs. (ie 12 sessions from getting started to Debugging): TODO [marcoceppi] Ensure URL rewrites work from olddocs to newdocs: TODO [mark-mims] Script diffs to CLI: TODO [evilnick] Publish list of videos and assign them to jorge, marco, mims, antonio, and whoever.: TODO [evilnick] Recirculate video template specs: TODO [jorge] Find out who will redub our stuff: TODO - [jorge] How to contribute to Juju docs section: TODO + [jorge] How to contribute to Juju docs section, make sure it follow's nick's style guide: TODO -- Improve Juju Documentation https://blueprints.launchpad.net/ubuntu/+spec/servercloud-s-juju-docs -- 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-s-juju-docs] Improve Juju Documentation
Blueprint changed by Jorge O. Castro: Work items changed: Work items: [evilnick] Define structural elements of HTML5 doc: DONE [evilnick] Create sample getting Started Guide: DONE [evilnick] Create list of screencasts: TODO [jorge] Develop Webinar/Screen cast education series mapped to Docs. (ie 12 sessions from getting started to Debugging): TODO [marcoceppi] Ensure URL rewrites work from olddocs to newdocs: TODO [mark-mims] Script diffs to CLI: TODO [evilnick] Publish list of videos and assign them to jorge, marco, mims, antonio, and whoever.: TODO [evilnick] Recirculate video template specs: TODO [jorge] Find out who will redub our stuff: TODO [jorge] How to contribute to Juju docs section, make sure it follow's nick's style guide: TODO + [marcoceppi] Propose to list to allow contributions to docs to count as ~charmers contribution: TODO -- Improve Juju Documentation https://blueprints.launchpad.net/ubuntu/+spec/servercloud-s-juju-docs -- 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-s-juju-docs] Improve Juju Documentation
Blueprint changed by Jorge O. Castro: Work items changed: Work items: [evilnick] Define structural elements of HTML5 doc: DONE [evilnick] Create sample getting Started Guide: DONE [evilnick] Create list of screencasts: TODO [jorge] Develop Webinar/Screen cast education series mapped to Docs. (ie 12 sessions from getting started to Debugging): TODO [marcoceppi] Ensure URL rewrites work from olddocs to newdocs: TODO [mark-mims] Script diffs to CLI: TODO [evilnick] Publish list of videos and assign them to jorge, marco, mims, antonio, and whoever.: TODO [evilnick] Recirculate video template specs: TODO [jorge] Find out who will redub our stuff: TODO [jorge] How to contribute to Juju docs section, make sure it follow's nick's style guide: TODO [marcoceppi] Propose to list to allow contributions to docs to count as ~charmers contribution: TODO + [marcoceppi] Investigate adding a chapter todo to the review queue: TODO + [jorge] Update AU questions to point to newdocs: TODO + [marcoceppi] Update AU questions to point to newdocs: TODO -- Improve Juju Documentation https://blueprints.launchpad.net/ubuntu/+spec/servercloud-s-juju-docs -- 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-s-juju-charmstore-feedback-loops] Add User Feedback loops and Social Networking to Charm Store Charm Pages
Blueprint changed by Jorge O. Castro: Work items changed: Work items: [jorge] write templates for all the services: TODO + [jcsackett] Implement the feature: TODO -- Add User Feedback loops and Social Networking to Charm Store Charm Pages https://blueprints.launchpad.net/ubuntu/+spec/servercloud-s-juju-charmstore-feedback-loops -- 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-s-juju-contributor-onramp] Juju Contributor Onramp
Blueprint changed by Jorge O. Castro: Work items changed: - Work items: + Work items for ubuntu-13.04-month-6: [jorge] Contribute to this charm! link in the charm store.: BLOCKED [jorge] Tell people they can help. There's no mention of how to help on jujucharms.com. That sucks. Not make something and get a prize, make it make something you are going to use and get a prize.: BLOCKED [jorge] charm-tools, we need to talk about it more, make a Best practices for charms should be in write a charm, integrate the mythical best practices page with write a charm.: TODO [mark-mims] Investigate making charm documentation testable: TODO [evilnick] Investigate making charm documentation testable: TODO - [gz] #1069883 Fix bug where defaulting to smallest instance type.: INPROGRESS [jjo] Case Studies from webops: TODO [mthaddon] Case Studies from webops: TODO [timrchavez] Case Studies from PES: TODO [jorge] README Review, prioritized based on charm popularity: TODO [jorge] Announce README fixups on the mailing list with maintainers: TODO [jorge] Codify for ~charmers to encourage people to fix readmes on submission of other fixes: [jorge] Provider discounts for charmers?: INPROGRESS [jorge] Update /events page on juju.ubuntu.com to show where we are attending.: DONE [jorge] Investigate long running contests on juju.ubuntu.com: TODO [niemeyer] Post instructions on how to use other code hosting options, and juju publish usage.: TODO [jorge] Ensure that the juju gui can run on the local provider: TODO [jorge] Investigate Openstack's use of github/launchpad workflow: INPROGRESS [jorge] fix dead link: https://wiki.ubuntu.com/ServerTeam/MAAS/Juju from https://juju.ubuntu.com/get-started/maas/: TODO + + Work items: [jorge] File bugs on charms that don't meet quality guidelines. it would be great if this charm did multimaster!! and so on, so people know that they can fix it. needs-scaleout tag?: BLOCKED [jorge] Way to go, we have over 100 people who contributed charms and you told no one. Nice work.: TODO jorge] Pimp my charm contest. or Xprize? Scale out HA x service to blah blah with integrated backups: TODO -- Juju Contributor Onramp https://blueprints.launchpad.net/ubuntu/+spec/servercloud-s-juju-contributor-onramp -- 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-s-juju-contributor-onramp] Juju Contributor Onramp
Blueprint changed by Jorge O. Castro: Work items changed: Work items for ubuntu-13.04-month-6: [jorge] Contribute to this charm! link in the charm store.: BLOCKED [jorge] Tell people they can help. There's no mention of how to help on jujucharms.com. That sucks. Not make something and get a prize, make it make something you are going to use and get a prize.: BLOCKED [jorge] charm-tools, we need to talk about it more, make a Best practices for charms should be in write a charm, integrate the mythical best practices page with write a charm.: TODO [mark-mims] Investigate making charm documentation testable: TODO [evilnick] Investigate making charm documentation testable: TODO - [jjo] Case Studies from webops: TODO - [mthaddon] Case Studies from webops: TODO - [timrchavez] Case Studies from PES: TODO + [jjo] Case Studies from webops (move to 2.0 messaging): TODO + [mthaddon] Case Studies from webops (move to 2.0 messaging): TODO + [timrchavez] Case Studies from PES (move to 2.0 messaging): TODO [jorge] README Review, prioritized based on charm popularity: TODO [jorge] Announce README fixups on the mailing list with maintainers: TODO [jorge] Codify for ~charmers to encourage people to fix readmes on submission of other fixes: [jorge] Provider discounts for charmers?: INPROGRESS [jorge] Update /events page on juju.ubuntu.com to show where we are attending.: DONE [jorge] Investigate long running contests on juju.ubuntu.com: TODO [niemeyer] Post instructions on how to use other code hosting options, and juju publish usage.: TODO [jorge] Ensure that the juju gui can run on the local provider: TODO [jorge] Investigate Openstack's use of github/launchpad workflow: INPROGRESS [jorge] fix dead link: https://wiki.ubuntu.com/ServerTeam/MAAS/Juju from https://juju.ubuntu.com/get-started/maas/: TODO Work items: [jorge] File bugs on charms that don't meet quality guidelines. it would be great if this charm did multimaster!! and so on, so people know that they can fix it. needs-scaleout tag?: BLOCKED [jorge] Way to go, we have over 100 people who contributed charms and you told no one. Nice work.: TODO jorge] Pimp my charm contest. or Xprize? Scale out HA x service to blah blah with integrated backups: TODO -- Juju Contributor Onramp https://blueprints.launchpad.net/ubuntu/+spec/servercloud-s-juju-contributor-onramp -- 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-s-juju-contributor-onramp] Juju Contributor Onramp
Blueprint changed by Jorge O. Castro: Work items changed: Work items for ubuntu-13.04-month-6: [jorge] Contribute to this charm! link in the charm store.: BLOCKED [jorge] Tell people they can help. There's no mention of how to help on jujucharms.com. That sucks. Not make something and get a prize, make it make something you are going to use and get a prize.: BLOCKED [jorge] charm-tools, we need to talk about it more, make a Best practices for charms should be in write a charm, integrate the mythical best practices page with write a charm.: TODO [mark-mims] Investigate making charm documentation testable: TODO [evilnick] Investigate making charm documentation testable: TODO [jjo] Case Studies from webops (move to 2.0 messaging): TODO [mthaddon] Case Studies from webops (move to 2.0 messaging): TODO [timrchavez] Case Studies from PES (move to 2.0 messaging): TODO - [jorge] README Review, prioritized based on charm popularity: TODO - [jorge] Announce README fixups on the mailing list with maintainers: TODO - [jorge] Codify for ~charmers to encourage people to fix readmes on submission of other fixes: [jorge] Provider discounts for charmers?: INPROGRESS [jorge] Update /events page on juju.ubuntu.com to show where we are attending.: DONE [jorge] Investigate long running contests on juju.ubuntu.com: TODO - [niemeyer] Post instructions on how to use other code hosting options, and juju publish usage.: TODO - [jorge] Ensure that the juju gui can run on the local provider: TODO - [jorge] Investigate Openstack's use of github/launchpad workflow: INPROGRESS - [jorge] fix dead link: https://wiki.ubuntu.com/ServerTeam/MAAS/Juju from https://juju.ubuntu.com/get-started/maas/: TODO + [jorge] Ensure that the juju gui can run on the local provider: BLOCKED Work items: [jorge] File bugs on charms that don't meet quality guidelines. it would be great if this charm did multimaster!! and so on, so people know that they can fix it. needs-scaleout tag?: BLOCKED [jorge] Way to go, we have over 100 people who contributed charms and you told no one. Nice work.: TODO jorge] Pimp my charm contest. or Xprize? Scale out HA x service to blah blah with integrated backups: TODO -- Juju Contributor Onramp https://blueprints.launchpad.net/ubuntu/+spec/servercloud-s-juju-contributor-onramp -- 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-s-juju-contributor-onramp] Juju Contributor Onramp
Blueprint changed by Jorge O. Castro: Work items changed: Work items for ubuntu-13.04-month-6: [jorge] Contribute to this charm! link in the charm store.: BLOCKED [jorge] Tell people they can help. There's no mention of how to help on jujucharms.com. That sucks. Not make something and get a prize, make it make something you are going to use and get a prize.: BLOCKED [jorge] charm-tools, we need to talk about it more, make a Best practices for charms should be in write a charm, integrate the mythical best practices page with write a charm.: TODO [mark-mims] Investigate making charm documentation testable: TODO [evilnick] Investigate making charm documentation testable: TODO [jjo] Case Studies from webops (move to 2.0 messaging): TODO [mthaddon] Case Studies from webops (move to 2.0 messaging): TODO [timrchavez] Case Studies from PES (move to 2.0 messaging): TODO [jorge] Update /events page on juju.ubuntu.com to show where we are attending.: DONE [jorge] Investigate long running contests on juju.ubuntu.com: TODO [jorge] Ensure that the juju gui can run on the local provider: BLOCKED Work items: [jorge] File bugs on charms that don't meet quality guidelines. it would be great if this charm did multimaster!! and so on, so people know that they can fix it. needs-scaleout tag?: BLOCKED [jorge] Way to go, we have over 100 people who contributed charms and you told no one. Nice work.: TODO jorge] Pimp my charm contest. or Xprize? Scale out HA x service to blah blah with integrated backups: TODO + [jorge] : Rewrite submission process for charms.: TODO + [jorge] : Get the gui guys to add mean response time measure.: TODO + [jorge] : Schedule reviews for charm reviewers.: TODO + [jorge] : Find 3 people and ask them to charm something to record it.: TODO + [jorge] : At the end of the cycle, do more user testing.: TODO -- Juju Contributor Onramp https://blueprints.launchpad.net/ubuntu/+spec/servercloud-s-juju-contributor-onramp -- 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-s-juju-contributor-onramp] Juju Contributor Onramp
Blueprint changed by Jorge O. Castro: Work items changed: Work items for ubuntu-13.04-month-6: [jorge] Contribute to this charm! link in the charm store.: BLOCKED [jorge] Tell people they can help. There's no mention of how to help on jujucharms.com. That sucks. Not make something and get a prize, make it make something you are going to use and get a prize.: BLOCKED [jorge] charm-tools, we need to talk about it more, make a Best practices for charms should be in write a charm, integrate the mythical best practices page with write a charm.: TODO [mark-mims] Investigate making charm documentation testable: TODO [evilnick] Investigate making charm documentation testable: TODO [jjo] Case Studies from webops (move to 2.0 messaging): TODO [mthaddon] Case Studies from webops (move to 2.0 messaging): TODO [timrchavez] Case Studies from PES (move to 2.0 messaging): TODO [jorge] Update /events page on juju.ubuntu.com to show where we are attending.: DONE [jorge] Investigate long running contests on juju.ubuntu.com: TODO [jorge] Ensure that the juju gui can run on the local provider: BLOCKED Work items: [jorge] File bugs on charms that don't meet quality guidelines. it would be great if this charm did multimaster!! and so on, so people know that they can fix it. needs-scaleout tag?: BLOCKED [jorge] Way to go, we have over 100 people who contributed charms and you told no one. Nice work.: TODO jorge] Pimp my charm contest. or Xprize? Scale out HA x service to blah blah with integrated backups: TODO [jorge] : Rewrite submission process for charms.: TODO [jorge] : Get the gui guys to add mean response time measure.: TODO [jorge] : Schedule reviews for charm reviewers.: TODO [jorge] : Find 3 people and ask them to charm something to record it.: TODO [jorge] : At the end of the cycle, do more user testing.: TODO + [jorge] : Bitesize bugs for charms: TODO + [a.rosales] : Quantify questions from charm schools. : TODO + [a.rosales] : Sync up with webops wrt. charm feedback.: TODO -- Juju Contributor Onramp https://blueprints.launchpad.net/ubuntu/+spec/servercloud-s-juju-contributor-onramp -- 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-s-juju-contributor-onramp] Juju Contributor Onramp
Blueprint changed by Jorge O. Castro: Work items changed: Work items for ubuntu-13.04-month-6: [jorge] Contribute to this charm! link in the charm store.: BLOCKED [jorge] Tell people they can help. There's no mention of how to help on jujucharms.com. That sucks. Not make something and get a prize, make it make something you are going to use and get a prize.: BLOCKED [jorge] charm-tools, we need to talk about it more, make a Best practices for charms should be in write a charm, integrate the mythical best practices page with write a charm.: TODO [mark-mims] Investigate making charm documentation testable: TODO [evilnick] Investigate making charm documentation testable: TODO [jjo] Case Studies from webops (move to 2.0 messaging): TODO [mthaddon] Case Studies from webops (move to 2.0 messaging): TODO [timrchavez] Case Studies from PES (move to 2.0 messaging): TODO [jorge] Update /events page on juju.ubuntu.com to show where we are attending.: DONE [jorge] Investigate long running contests on juju.ubuntu.com: TODO [jorge] Ensure that the juju gui can run on the local provider: BLOCKED Work items: [jorge] File bugs on charms that don't meet quality guidelines. it would be great if this charm did multimaster!! and so on, so people know that they can fix it. needs-scaleout tag?: BLOCKED [jorge] Way to go, we have over 100 people who contributed charms and you told no one. Nice work.: TODO jorge] Pimp my charm contest. or Xprize? Scale out HA x service to blah blah with integrated backups: TODO [jorge] : Rewrite submission process for charms.: TODO [jorge] : Get the gui guys to add mean response time measure.: TODO [jorge] : Schedule reviews for charm reviewers.: TODO [jorge] : Find 3 people and ask them to charm something to record it.: TODO [jorge] : At the end of the cycle, do more user testing.: TODO [jorge] : Bitesize bugs for charms: TODO [a.rosales] : Quantify questions from charm schools. : TODO [a.rosales] : Sync up with webops (mthaddon wedgwood) wrt. charm feedback.: TODO + [jorge] : Make a charm-school tag in lp for juju bugs so core team knows what are high visibility bugs: TODO -- Juju Contributor Onramp https://blueprints.launchpad.net/ubuntu/+spec/servercloud-s-juju-contributor-onramp -- 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-s-juju-contributor-onramp] Juju Contributor Onramp
Blueprint changed by Jorge O. Castro: Whiteboard changed: UDS 1303 Pad Data: Pad: http://pad.ubuntu.com/uds-1303-servercloud-1303-juju-contributor-onramp Old spec: https://blueprints.launchpad.net/ubuntu/+spec/community-r-juju-contributor-onramp-1 Idea: In regards to using other code hosting: mariusko_: Also maybe compare with how it is done with nodejs: npm help publish (https://npmjs.org/doc/developers.html) - [USER STORIES] + [USER STORIES] + + James is a sysadmin at a company and is interested in getting his charms + into the store for convenience/peer review. + + Kirk is deploying a charm but finds that it's missing a feature or needs + a bugfix and he thinks he knows how to fix it. + + Robert is a developer at a company who works on a database that is + charmed up, he notices that the charm needs improvement to follow his + project's recommended best practice, but isn't sure how to claim + ownership of a charm. + + Lars is used to github and is totally confused on how to get charms he's + interested in. + [ASSUMPTIONS] + + - Mims/Castro want to mirror how OpenStack does reviews and code + contributions as well as their usage of LP Blueprints. + [RISKS] + + - There's only so much simplification that can happen when it comes to submitting code. + - Poor response time leads people to believe that we don't want to help them. + - Workflow ties into the store, so we need to be careful on how we simplify this. + [IN SCOPE] + + - Refining workflow for submission + - Measuring contributor metrics and enforcing a fast response time. + [OUT OF SCOPE] + [USER ACCEPTANCE] + [RELEASE NOTE/BLOG] + + - We've made it easier than ever to contribute to charms with a new + submission workflow. -- Juju Contributor Onramp https://blueprints.launchpad.net/ubuntu/+spec/servercloud-s-juju-contributor-onramp -- 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-s-juju-contributor-onramp] Juju Contributor Onramp
Blueprint changed by Jorge O. Castro: Whiteboard changed: UDS 1303 Pad Data: Pad: http://pad.ubuntu.com/uds-1303-servercloud-1303-juju-contributor-onramp Old spec: https://blueprints.launchpad.net/ubuntu/+spec/community-r-juju-contributor-onramp-1 Idea: In regards to using other code hosting: mariusko_: Also maybe compare with how it is done with nodejs: npm help publish (https://npmjs.org/doc/developers.html) [USER STORIES] James is a sysadmin at a company and is interested in getting his charms - into the store for convenience/peer review. + into the store for convenience/peer review. He's got some internal stuff + that he can keep seperate, but he doesn't want to maintain boring + infrastructure charms on his own. Kirk is deploying a charm but finds that it's missing a feature or needs a bugfix and he thinks he knows how to fix it. Robert is a developer at a company who works on a database that is charmed up, he notices that the charm needs improvement to follow his project's recommended best practice, but isn't sure how to claim ownership of a charm. Lars is used to github and is totally confused on how to get charms he's interested in. [ASSUMPTIONS] - Mims/Castro want to mirror how OpenStack does reviews and code contributions as well as their usage of LP Blueprints. [RISKS] - There's only so much simplification that can happen when it comes to submitting code. - Poor response time leads people to believe that we don't want to help them. - - Workflow ties into the store, so we need to be careful on how we simplify this. + - Workflow ties into the store, so we need to be careful on how we simplify this. [IN SCOPE] - Refining workflow for submission - - Measuring contributor metrics and enforcing a fast response time. + - Measuring contributor metrics and enforcing a fast response time. [OUT OF SCOPE] [USER ACCEPTANCE] [RELEASE NOTE/BLOG] - We've made it easier than ever to contribute to charms with a new submission workflow. -- Juju Contributor Onramp https://blueprints.launchpad.net/ubuntu/+spec/servercloud-s-juju-contributor-onramp -- 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-s-juju-contributor-onramp] Juju Contributor Onramp
Blueprint changed by Jorge O. Castro: Whiteboard changed: UDS 1303 Pad Data: Pad: http://pad.ubuntu.com/uds-1303-servercloud-1303-juju-contributor-onramp Old spec: https://blueprints.launchpad.net/ubuntu/+spec/community-r-juju-contributor-onramp-1 Idea: In regards to using other code hosting: mariusko_: Also maybe compare with how it is done with nodejs: npm help publish (https://npmjs.org/doc/developers.html) [USER STORIES] James is a sysadmin at a company and is interested in getting his charms into the store for convenience/peer review. He's got some internal stuff that he can keep seperate, but he doesn't want to maintain boring infrastructure charms on his own. Kirk is deploying a charm but finds that it's missing a feature or needs a bugfix and he thinks he knows how to fix it. Robert is a developer at a company who works on a database that is charmed up, he notices that the charm needs improvement to follow his project's recommended best practice, but isn't sure how to claim ownership of a charm. Lars is used to github and is totally confused on how to get charms he's interested in. + Cliff submitted a fix to a charm two weeks ago and has no idea how to + get someone to get his fix in. + [ASSUMPTIONS] - Mims/Castro want to mirror how OpenStack does reviews and code contributions as well as their usage of LP Blueprints. [RISKS] - There's only so much simplification that can happen when it comes to submitting code. - Poor response time leads people to believe that we don't want to help them. - Workflow ties into the store, so we need to be careful on how we simplify this. [IN SCOPE] - Refining workflow for submission - Measuring contributor metrics and enforcing a fast response time. [OUT OF SCOPE] [USER ACCEPTANCE] [RELEASE NOTE/BLOG] - We've made it easier than ever to contribute to charms with a new submission workflow. -- Juju Contributor Onramp https://blueprints.launchpad.net/ubuntu/+spec/servercloud-s-juju-contributor-onramp -- 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-1303-juju-contributor-onramp] Juju Contributor Onramp
Blueprint changed by Jorge O. Castro: Work items changed: - Work items: + Work items for ubuntu-13.04-month-6: [jorge] Contribute to this charm! link in the charm store.: BLOCKED [jorge] Tell people they can help. There's no mention of how to help on jujucharms.com. That sucks. Not make something and get a prize, make it make something you are going to use and get a prize.: BLOCKED [jorge] charm-tools, we need to talk about it more, make a Best practices for charms should be in write a charm, integrate the mythical best practices page with write a charm.: TODO [mark-mims] Investigate making charm documentation testable: TODO [evilnick] Investigate making charm documentation testable: TODO [gz] #1069883 Fix bug where defaulting to smallest instance type.: INPROGRESS [jjo] Case Studies from webops: TODO [mthaddon] Case Studies from webops: TODO [timrchavez] Case Studies from PES: TODO [jorge] README Review, prioritized based on charm popularity: TODO [jorge] Announce README fixups on the mailing list with maintainers: TODO [jorge] Codify for ~charmers to encourage people to fix readmes on submission of other fixes: TODO [jorge] File bugs on charms that don't meet quality guidelines. it would be great if this charm did multimaster!! and so on, so people know that they can fix it. needs-scaleout tag?: BLOCKED [jorge] Way to go, we have over 100 people who contributed charms and you told no one. Nice work.: TODO [jorge] Provider discounts for charmers?: INPROGRESS [jorge] Pimp my charm contest. or Xprize? Scale out HA x service to blah blah with integrated backups.: POSTPONED [jorge] Update /events page on juju.ubuntu.com to show where we are attending.: TODO [jorge] Investigate long running contests on juju.ubuntu.com: TODO [niemeyer] Post instructions on how to use other code hosting options, and juju publish usage.: TODO [jorge] Ensure that the juju gui can run on the local provider: TODO [jorge] Investigate Openstack's use of github/launchpad workflow: TODO - [jcastro] fix dead link: https://wiki.ubuntu.com/ServerTeam/MAAS/Juju from https://juju.ubuntu.com/get-started/maas/: TODO + [jorge] fix dead link: https://wiki.ubuntu.com/ServerTeam/MAAS/Juju from https://juju.ubuntu.com/get-started/maas/: TODO -- Juju Contributor Onramp https://blueprints.launchpad.net/ubuntu/+spec/servercloud-1303-juju-contributor-onramp -- 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-1303-juju-docs] Improve Juju Documentation
Blueprint changed by Jorge O. Castro: Work items changed: - Work items: + Work items for ubuntu-13.04-month-6: [evilnick] Define structural elements of HTML5 doc: TODO [evilnick] Create sample getting Started Guide: TODO [evilnick] Create list of screencasts: TODO [jorge] Develop screen casts based on defined list: TODO -- Improve Juju Documentation https://blueprints.launchpad.net/ubuntu/+spec/servercloud-1303-juju-docs -- 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-1303-juju-docs] Improve Juju Documentation
Blueprint changed by Jorge O. Castro: Whiteboard changed: --- UDS 1303 Discussion --- PAD URL: http://pad.ubuntu.com/uds-1303-servercloud-1303-juju-docs -Leave behind RST! -pandoc doesn't support some of the newer HTML5 elements (asides, etc) HTML5 w/ JavaScript it is! -Make sure juju.ubuntu.com landing page tell Juju story well (what is it, why should I use it) -Dynamic Content -Screencasts -Code Examples -Better references in sidbars with improved navigation -Annotate Juju deploy command -Annootate Juju GUI deploy -Annotate anatomoy of a charm --- Ideas --- Good examples: *stripe.com (https://stripe.com/docs) -good journeys -not overwhelming *http://developer.android.com/sdk/index.html -ttp://developer.android.com/tools/workflow/index.html Would like to have good sidebar notes, screen shots, tips, and examples. Would like to have knowledge of what I am at in a journey *Getting Started (Juju deploy) *Charm Development *Charm Deployment *Charm Discovery *Charm Debugging Model magazines *Wired *Linux Format *Content rich Need version control Want Markdown not RST Get rid of anything marked draft Need organization of what we currently have. Evaluate Pandoc instead of Sphinx Discuss GUI and Charm Browser --- Immediate Needs --- Verify the usability of docs (are the instructions correct). Identify a model for the docs (framework) *Not docbook - too complicated and print-biased *Sphinx? Needed since core is now Go? *Something markdown based? *simple HTML5? Milestone *13.04 default for Go *How to use it *Transition -Differences -Py and Go living together --- Organization --- juju users: Getting started User tutorial - rename to “Using Juju” Charms Implicit relations Machine Constraints Exposing a service EC2 provider configuration - all the provider stuff should be in one section Local provider configuration OpenStack provider configuration The Juju Charm Store (for users) Handling common errors charm authors: Writing a charm The Juju Charm Store Charm Testing Hook debugging Charm Store Policy Charm Quality Rating Debugging Evaluate for removal: About juju - remove. Frequently Asked Questions - DELETE THIS, link to autogenerated FAQ at AU. juju modules Implementation details - appendix Drafts - REMOVE. Glossary -appendix Commands to work with relation settings and membership Upgrades - both? Charm Upgrades Operating Systems - appendix stuff Relation references - appendix stuff New relation-ids hook command -? + + # Documentation Framework (Courseware) + + + https://juju.ubuntu.com/docs/charm.html + -Make sure to review the docs point, and have a corrolation betweeen user jouneys and screen casts. + - Put screen cast in docs + -screen casets and docs should reference each other. + + 0 -- New to Juju + 1. [user] Installing and configurating Juju + i. https://juju.ubuntu.com/docs/getting-started.html + 1. Charm Introduction + i. https://juju.ubuntu.com/docs/charm.html + 1. Charm Discovery/ Charm Store + i https://juju.ubuntu.com/docs/charm-store.html + 1. [user] Deploying your first charm (include constraints) + i. https://juju.ubuntu.com/docs/user-tutorial.html + 1. [user] How to use relations + 1. [user] Lifecycle managment: Using the configuration.yaml juju set + i. https://juju.ubuntu.com/docs/service-config.html + 1. [user] Debugging deployment - debug logs and friends + 1. [user] Advanced topics (deploy-to, jitsu and friends) + -need to confirm how plug-in model is in Juju 2.0 + + 1- New Charm Author + Review https://juju.ubuntu.com/docs/write-charm.html + + 1. Submitting your first contribution to a charm + 1. Writing a new charm from scratch. + i. https://juju.ubuntu.com/docs/write-charm.html + a. charm tools + a. meta-data/readme/licensing/examples/description/how to use/why to use from Ops or Dev perspective + a. Hooks + a. relations + i. interface + i. requires + a. testing + 1. Publishing to the Juju Charm Store + 1. How to improve your charm using community quality ratings (https://juju.ubuntu.com/docs/charm-quality.html): + a. Reliability + b. Security + c. Flexible + d. Handle Data + e. Scalability + f. Ease of deployment + g. Responsive to devops needs + h. Upstream-friendly. + 1. Getting your work peer reviewed + 1. Charm Debugging -- Improve Juju Documentation https://blueprints.launchpad.net/ubuntu/+spec/servercloud-1303-juju-docs -- 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-1303-juju-contributor-onramp] Juju Contributor Onramp
Blueprint changed by Jorge O. Castro: Work items changed: Work items for ubuntu-13.04-month-6: [jorge] Contribute to this charm! link in the charm store.: BLOCKED [jorge] Tell people they can help. There's no mention of how to help on jujucharms.com. That sucks. Not make something and get a prize, make it make something you are going to use and get a prize.: BLOCKED [jorge] charm-tools, we need to talk about it more, make a Best practices for charms should be in write a charm, integrate the mythical best practices page with write a charm.: TODO [mark-mims] Investigate making charm documentation testable: TODO [evilnick] Investigate making charm documentation testable: TODO [gz] #1069883 Fix bug where defaulting to smallest instance type.: INPROGRESS [jjo] Case Studies from webops: TODO [mthaddon] Case Studies from webops: TODO [timrchavez] Case Studies from PES: TODO [jorge] README Review, prioritized based on charm popularity: TODO [jorge] Announce README fixups on the mailing list with maintainers: TODO - [jorge] Codify for ~charmers to encourage people to fix readmes on submission of other fixes: TODO - [jorge] File bugs on charms that don't meet quality guidelines. it would be great if this charm did multimaster!! and so on, so people know that they can fix it. needs-scaleout tag?: BLOCKED - [jorge] Way to go, we have over 100 people who contributed charms and you told no one. Nice work.: TODO - [jorge] Provider discounts for charmers?: INPROGRESS - [jorge] Pimp my charm contest. or Xprize? Scale out HA x service to blah blah with integrated backups.: POSTPONED - [jorge] Update /events page on juju.ubuntu.com to show where we are attending.: TODO + [jorge] Codify for ~charmers to encourage people to fix readmes on submission of other fixes: [jorge] Provider discounts for charmers?: INPROGRESS + [jorge] Update /events page on juju.ubuntu.com to show where we are attending.: DONE [jorge] Investigate long running contests on juju.ubuntu.com: TODO [niemeyer] Post instructions on how to use other code hosting options, and juju publish usage.: TODO [jorge] Ensure that the juju gui can run on the local provider: TODO - [jorge] Investigate Openstack's use of github/launchpad workflow: TODO + [jorge] Investigate Openstack's use of github/launchpad workflow: INPROGRESS [jorge] fix dead link: https://wiki.ubuntu.com/ServerTeam/MAAS/Juju from https://juju.ubuntu.com/get-started/maas/: TODO + + Work items: + [jorge] File bugs on charms that don't meet quality guidelines. it would be great if this charm did multimaster!! and so on, so people know that they can fix it. needs-scaleout tag?: BLOCKED + [jorge] Way to go, we have over 100 people who contributed charms and you told no one. Nice work.: TODO + jorge] Pimp my charm contest. or Xprize? Scale out HA x service to blah blah with integrated backups: TODO -- Juju Contributor Onramp https://blueprints.launchpad.net/ubuntu/+spec/servercloud-1303-juju-contributor-onramp -- 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-1303-juju-contributor-onramp] Juju Contributor Onramp
Blueprint changed by Jorge O. Castro: Work items changed: Work items: [jorge] Contribute to this charm! link in the charm store.: BLOCKED [jorge] Tell people they can help. There's no mention of how to help on jujucharms.com. That sucks. Not make something and get a prize, make it make something you are going to use and get a prize.: BLOCKED [jorge] Find out what is up with the juju web page.: DONE [jorge] charm-tools, we need to talk about it more, make a Best practices for charms should be in write a charm, integrate the mythical best practices page with write a charm.: TODO [mark-mims] Investigate making charm documentation testable: TODO [gz] #1069883 Fix bug where defaulting to smallest instance type.: INPROGRESS - [marcoceppi] Investigate stacktacking the different juju on different providers into the documentation so it doesn't live in a vacuum.: DONE [clint-fewbar] Fix documentation for LXC in Getting Started.: DONE [jjo] Case Studies from webops: TODO [mthaddon] Case Studies from webops: TODO [timrchavez] Case Studies from PES: TODO [jorge] Find some sales dude to sucker into testing the documentation.: DONE [jorge] Make a juju docs project in lp so people can report bugs, queue and itemize.: DONE [jorge] Make a task for scrub the docs for ensemble and other dumb things.: DONE [jorge] Fix READMEs: POSTPONED [jorge] Queue and target up Charm needed on launchpad.: DONE [jorge] bitesize bugs.: DONE [jorge] File bugs on charms that don't meet quality guidelines. it would be great if this charm did multimaster!! and so on, so people know that they can fix it. needs-scaleout tag?: POSTPONED [jorge] Way to go, we have over 100 people who contributed charms and you told no one. Nice work.: TODO - [jorge] Reintate tshirt program for contributors.: DONE [jorge] Investigate sending contributors to conferences wrt. charm authors: DONE - [jorge] Provider discounts for charmers?: INPROGRESS + [jorge] Provider discounts for charmers?: INPROGRESS [jorge] Pimp my charm contest. or Xprize? Scale out HA x service to blah blah with integrated backups.: POSTPONED -- Juju Contributor Onramp https://blueprints.launchpad.net/ubuntu/+spec/servercloud-1303-juju-contributor-onramp -- 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-1303-juju-contributor-onramp] Juju Contributor Onramp
Blueprint changed by Jorge O. Castro: Work items changed: Work items: [jorge] Contribute to this charm! link in the charm store.: BLOCKED [jorge] Tell people they can help. There's no mention of how to help on jujucharms.com. That sucks. Not make something and get a prize, make it make something you are going to use and get a prize.: BLOCKED [jorge] Find out what is up with the juju web page.: DONE [jorge] charm-tools, we need to talk about it more, make a Best practices for charms should be in write a charm, integrate the mythical best practices page with write a charm.: TODO [mark-mims] Investigate making charm documentation testable: TODO [gz] #1069883 Fix bug where defaulting to smallest instance type.: INPROGRESS - [clint-fewbar] Fix documentation for LXC in Getting Started.: DONE [jjo] Case Studies from webops: TODO [mthaddon] Case Studies from webops: TODO [timrchavez] Case Studies from PES: TODO - [jorge] Find some sales dude to sucker into testing the documentation.: DONE - [jorge] Make a juju docs project in lp so people can report bugs, queue and itemize.: DONE - [jorge] Make a task for scrub the docs for ensemble and other dumb things.: DONE [jorge] Fix READMEs: POSTPONED - [jorge] Queue and target up Charm needed on launchpad.: DONE [jorge] bitesize bugs.: DONE [jorge] File bugs on charms that don't meet quality guidelines. it would be great if this charm did multimaster!! and so on, so people know that they can fix it. needs-scaleout tag?: POSTPONED [jorge] Way to go, we have over 100 people who contributed charms and you told no one. Nice work.: TODO [jorge] Investigate sending contributors to conferences wrt. charm authors: DONE [jorge] Provider discounts for charmers?: INPROGRESS [jorge] Pimp my charm contest. or Xprize? Scale out HA x service to blah blah with integrated backups.: POSTPONED -- Juju Contributor Onramp https://blueprints.launchpad.net/ubuntu/+spec/servercloud-1303-juju-contributor-onramp -- 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-1303-juju-contributor-onramp] Juju Contributor Onramp
Blueprint changed by Jorge O. Castro: Work items changed: Work items: [jorge] Contribute to this charm! link in the charm store.: BLOCKED [jorge] Tell people they can help. There's no mention of how to help on jujucharms.com. That sucks. Not make something and get a prize, make it make something you are going to use and get a prize.: BLOCKED - [jorge] Find out what is up with the juju web page.: DONE [jorge] charm-tools, we need to talk about it more, make a Best practices for charms should be in write a charm, integrate the mythical best practices page with write a charm.: TODO [mark-mims] Investigate making charm documentation testable: TODO [gz] #1069883 Fix bug where defaulting to smallest instance type.: INPROGRESS [jjo] Case Studies from webops: TODO [mthaddon] Case Studies from webops: TODO [timrchavez] Case Studies from PES: TODO [jorge] Fix READMEs: POSTPONED - [jorge] bitesize bugs.: DONE [jorge] File bugs on charms that don't meet quality guidelines. it would be great if this charm did multimaster!! and so on, so people know that they can fix it. needs-scaleout tag?: POSTPONED [jorge] Way to go, we have over 100 people who contributed charms and you told no one. Nice work.: TODO [jorge] Investigate sending contributors to conferences wrt. charm authors: DONE [jorge] Provider discounts for charmers?: INPROGRESS [jorge] Pimp my charm contest. or Xprize? Scale out HA x service to blah blah with integrated backups.: POSTPONED -- Juju Contributor Onramp https://blueprints.launchpad.net/ubuntu/+spec/servercloud-1303-juju-contributor-onramp -- 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-1303-juju-contributor-onramp] Juju Contributor Onramp
Blueprint changed by Jorge O. Castro: Work items changed: Work items: [jorge] Contribute to this charm! link in the charm store.: BLOCKED [jorge] Tell people they can help. There's no mention of how to help on jujucharms.com. That sucks. Not make something and get a prize, make it make something you are going to use and get a prize.: BLOCKED [jorge] charm-tools, we need to talk about it more, make a Best practices for charms should be in write a charm, integrate the mythical best practices page with write a charm.: TODO [mark-mims] Investigate making charm documentation testable: TODO + [evilnick] Investigate making charm documentation testable: TODO [gz] #1069883 Fix bug where defaulting to smallest instance type.: INPROGRESS [jjo] Case Studies from webops: TODO [mthaddon] Case Studies from webops: TODO [timrchavez] Case Studies from PES: TODO [jorge] Fix READMEs: POSTPONED [jorge] File bugs on charms that don't meet quality guidelines. it would be great if this charm did multimaster!! and so on, so people know that they can fix it. needs-scaleout tag?: POSTPONED [jorge] Way to go, we have over 100 people who contributed charms and you told no one. Nice work.: TODO [jorge] Investigate sending contributors to conferences wrt. charm authors: DONE [jorge] Provider discounts for charmers?: INPROGRESS [jorge] Pimp my charm contest. or Xprize? Scale out HA x service to blah blah with integrated backups.: POSTPONED -- Juju Contributor Onramp https://blueprints.launchpad.net/ubuntu/+spec/servercloud-1303-juju-contributor-onramp -- 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-1303-juju-contributor-onramp] Juju Contributor Onramp
Blueprint changed by Jorge O. Castro: Work items changed: Work items: [jorge] Contribute to this charm! link in the charm store.: BLOCKED [jorge] Tell people they can help. There's no mention of how to help on jujucharms.com. That sucks. Not make something and get a prize, make it make something you are going to use and get a prize.: BLOCKED [jorge] charm-tools, we need to talk about it more, make a Best practices for charms should be in write a charm, integrate the mythical best practices page with write a charm.: TODO [mark-mims] Investigate making charm documentation testable: TODO [evilnick] Investigate making charm documentation testable: TODO [gz] #1069883 Fix bug where defaulting to smallest instance type.: INPROGRESS [jjo] Case Studies from webops: TODO [mthaddon] Case Studies from webops: TODO [timrchavez] Case Studies from PES: TODO [jorge] README Review, prioritized based on charm popularity: TODO + [jorge] Announce README fixups on the mailing list with maintainers: TODO [jorge] File bugs on charms that don't meet quality guidelines. it would be great if this charm did multimaster!! and so on, so people know that they can fix it. needs-scaleout tag?: POSTPONED [jorge] Way to go, we have over 100 people who contributed charms and you told no one. Nice work.: TODO [jorge] Investigate sending contributors to conferences wrt. charm authors: DONE [jorge] Provider discounts for charmers?: INPROGRESS [jorge] Pimp my charm contest. or Xprize? Scale out HA x service to blah blah with integrated backups.: POSTPONED -- Juju Contributor Onramp https://blueprints.launchpad.net/ubuntu/+spec/servercloud-1303-juju-contributor-onramp -- 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-1303-juju-contributor-onramp] Juju Contributor Onramp
Blueprint changed by Jorge O. Castro: Work items changed: Work items: [jorge] Contribute to this charm! link in the charm store.: BLOCKED [jorge] Tell people they can help. There's no mention of how to help on jujucharms.com. That sucks. Not make something and get a prize, make it make something you are going to use and get a prize.: BLOCKED [jorge] charm-tools, we need to talk about it more, make a Best practices for charms should be in write a charm, integrate the mythical best practices page with write a charm.: TODO [mark-mims] Investigate making charm documentation testable: TODO [evilnick] Investigate making charm documentation testable: TODO [gz] #1069883 Fix bug where defaulting to smallest instance type.: INPROGRESS [jjo] Case Studies from webops: TODO [mthaddon] Case Studies from webops: TODO [timrchavez] Case Studies from PES: TODO [jorge] README Review, prioritized based on charm popularity: TODO [jorge] Announce README fixups on the mailing list with maintainers: TODO + [jorge] Codify for ~charmers to encourage people to fix readmes on submission of other fixes: TODO [jorge] File bugs on charms that don't meet quality guidelines. it would be great if this charm did multimaster!! and so on, so people know that they can fix it. needs-scaleout tag?: POSTPONED [jorge] Way to go, we have over 100 people who contributed charms and you told no one. Nice work.: TODO [jorge] Investigate sending contributors to conferences wrt. charm authors: DONE [jorge] Provider discounts for charmers?: INPROGRESS [jorge] Pimp my charm contest. or Xprize? Scale out HA x service to blah blah with integrated backups.: POSTPONED -- Juju Contributor Onramp https://blueprints.launchpad.net/ubuntu/+spec/servercloud-1303-juju-contributor-onramp -- 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-1303-juju-contributor-onramp] Juju Contributor Onramp
Blueprint changed by Jorge O. Castro: Work items changed: Work items: [jorge] Contribute to this charm! link in the charm store.: BLOCKED [jorge] Tell people they can help. There's no mention of how to help on jujucharms.com. That sucks. Not make something and get a prize, make it make something you are going to use and get a prize.: BLOCKED [jorge] charm-tools, we need to talk about it more, make a Best practices for charms should be in write a charm, integrate the mythical best practices page with write a charm.: TODO [mark-mims] Investigate making charm documentation testable: TODO [evilnick] Investigate making charm documentation testable: TODO [gz] #1069883 Fix bug where defaulting to smallest instance type.: INPROGRESS [jjo] Case Studies from webops: TODO [mthaddon] Case Studies from webops: TODO [timrchavez] Case Studies from PES: TODO [jorge] README Review, prioritized based on charm popularity: TODO [jorge] Announce README fixups on the mailing list with maintainers: TODO [jorge] Codify for ~charmers to encourage people to fix readmes on submission of other fixes: TODO - [jorge] File bugs on charms that don't meet quality guidelines. it would be great if this charm did multimaster!! and so on, so people know that they can fix it. needs-scaleout tag?: POSTPONED - [jorge] Way to go, we have over 100 people who contributed charms and you told no one. Nice work.: TODO + [jorge] File bugs on charms that don't meet quality guidelines. it would be great if this charm did multimaster!! and so on, so people know that they can fix it. needs-scaleout tag?: BLOCKED + [jorge] Way to go, we have over 100 people who contributed charms and you told no one. Nice work.: TODO [jorge] Investigate sending contributors to conferences wrt. charm authors: DONE [jorge] Provider discounts for charmers?: INPROGRESS [jorge] Pimp my charm contest. or Xprize? Scale out HA x service to blah blah with integrated backups.: POSTPONED -- Juju Contributor Onramp https://blueprints.launchpad.net/ubuntu/+spec/servercloud-1303-juju-contributor-onramp -- 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-1303-juju-contributor-onramp] Juju Contributor Onramp
Blueprint changed by Jorge O. Castro: Work items changed: Work items: [jorge] Contribute to this charm! link in the charm store.: BLOCKED [jorge] Tell people they can help. There's no mention of how to help on jujucharms.com. That sucks. Not make something and get a prize, make it make something you are going to use and get a prize.: BLOCKED [jorge] charm-tools, we need to talk about it more, make a Best practices for charms should be in write a charm, integrate the mythical best practices page with write a charm.: TODO [mark-mims] Investigate making charm documentation testable: TODO [evilnick] Investigate making charm documentation testable: TODO [gz] #1069883 Fix bug where defaulting to smallest instance type.: INPROGRESS [jjo] Case Studies from webops: TODO [mthaddon] Case Studies from webops: TODO [timrchavez] Case Studies from PES: TODO [jorge] README Review, prioritized based on charm popularity: TODO [jorge] Announce README fixups on the mailing list with maintainers: TODO [jorge] Codify for ~charmers to encourage people to fix readmes on submission of other fixes: TODO [jorge] File bugs on charms that don't meet quality guidelines. it would be great if this charm did multimaster!! and so on, so people know that they can fix it. needs-scaleout tag?: BLOCKED [jorge] Way to go, we have over 100 people who contributed charms and you told no one. Nice work.: TODO - [jorge] Investigate sending contributors to conferences wrt. charm authors: DONE [jorge] Provider discounts for charmers?: INPROGRESS [jorge] Pimp my charm contest. or Xprize? Scale out HA x service to blah blah with integrated backups.: POSTPONED -- Juju Contributor Onramp https://blueprints.launchpad.net/ubuntu/+spec/servercloud-1303-juju-contributor-onramp -- 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-1303-juju-contributor-onramp] Juju Contributor Onramp
Blueprint changed by Jorge O. Castro: Work items changed: Work items: [jorge] Contribute to this charm! link in the charm store.: BLOCKED [jorge] Tell people they can help. There's no mention of how to help on jujucharms.com. That sucks. Not make something and get a prize, make it make something you are going to use and get a prize.: BLOCKED [jorge] charm-tools, we need to talk about it more, make a Best practices for charms should be in write a charm, integrate the mythical best practices page with write a charm.: TODO [mark-mims] Investigate making charm documentation testable: TODO [evilnick] Investigate making charm documentation testable: TODO [gz] #1069883 Fix bug where defaulting to smallest instance type.: INPROGRESS [jjo] Case Studies from webops: TODO [mthaddon] Case Studies from webops: TODO [timrchavez] Case Studies from PES: TODO [jorge] README Review, prioritized based on charm popularity: TODO [jorge] Announce README fixups on the mailing list with maintainers: TODO [jorge] Codify for ~charmers to encourage people to fix readmes on submission of other fixes: TODO [jorge] File bugs on charms that don't meet quality guidelines. it would be great if this charm did multimaster!! and so on, so people know that they can fix it. needs-scaleout tag?: BLOCKED [jorge] Way to go, we have over 100 people who contributed charms and you told no one. Nice work.: TODO [jorge] Provider discounts for charmers?: INPROGRESS [jorge] Pimp my charm contest. or Xprize? Scale out HA x service to blah blah with integrated backups.: POSTPONED + [jorge] Update /events page on juju.ubuntu.com to show where we are attending.: TODO + [jorge] Investigate long running contests on juju.ubuntu.com: TODO -- Juju Contributor Onramp https://blueprints.launchpad.net/ubuntu/+spec/servercloud-1303-juju-contributor-onramp -- 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-1303-juju-contributor-onramp] Juju Contributor Onramp
Blueprint changed by Jorge O. Castro: Work items changed: Work items: [jorge] Contribute to this charm! link in the charm store.: BLOCKED [jorge] Tell people they can help. There's no mention of how to help on jujucharms.com. That sucks. Not make something and get a prize, make it make something you are going to use and get a prize.: BLOCKED [jorge] charm-tools, we need to talk about it more, make a Best practices for charms should be in write a charm, integrate the mythical best practices page with write a charm.: TODO [mark-mims] Investigate making charm documentation testable: TODO [evilnick] Investigate making charm documentation testable: TODO [gz] #1069883 Fix bug where defaulting to smallest instance type.: INPROGRESS [jjo] Case Studies from webops: TODO [mthaddon] Case Studies from webops: TODO [timrchavez] Case Studies from PES: TODO - [jorge] Fix READMEs: POSTPONED + [jorge] README Review, prioritized based on charm popularity: TODO [jorge] File bugs on charms that don't meet quality guidelines. it would be great if this charm did multimaster!! and so on, so people know that they can fix it. needs-scaleout tag?: POSTPONED [jorge] Way to go, we have over 100 people who contributed charms and you told no one. Nice work.: TODO [jorge] Investigate sending contributors to conferences wrt. charm authors: DONE [jorge] Provider discounts for charmers?: INPROGRESS [jorge] Pimp my charm contest. or Xprize? Scale out HA x service to blah blah with integrated backups.: POSTPONED -- Juju Contributor Onramp https://blueprints.launchpad.net/ubuntu/+spec/servercloud-1303-juju-contributor-onramp -- 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-1303-juju-contributor-onramp] Juju Contributor Onramp
Blueprint changed by Jorge O. Castro: Work items changed: Work items: [jorge] Contribute to this charm! link in the charm store.: BLOCKED [jorge] Tell people they can help. There's no mention of how to help on jujucharms.com. That sucks. Not make something and get a prize, make it make something you are going to use and get a prize.: BLOCKED [jorge] charm-tools, we need to talk about it more, make a Best practices for charms should be in write a charm, integrate the mythical best practices page with write a charm.: TODO [mark-mims] Investigate making charm documentation testable: TODO [evilnick] Investigate making charm documentation testable: TODO [gz] #1069883 Fix bug where defaulting to smallest instance type.: INPROGRESS [jjo] Case Studies from webops: TODO [mthaddon] Case Studies from webops: TODO [timrchavez] Case Studies from PES: TODO [jorge] README Review, prioritized based on charm popularity: TODO [jorge] Announce README fixups on the mailing list with maintainers: TODO [jorge] Codify for ~charmers to encourage people to fix readmes on submission of other fixes: TODO [jorge] File bugs on charms that don't meet quality guidelines. it would be great if this charm did multimaster!! and so on, so people know that they can fix it. needs-scaleout tag?: BLOCKED [jorge] Way to go, we have over 100 people who contributed charms and you told no one. Nice work.: TODO [jorge] Provider discounts for charmers?: INPROGRESS [jorge] Pimp my charm contest. or Xprize? Scale out HA x service to blah blah with integrated backups.: POSTPONED [jorge] Update /events page on juju.ubuntu.com to show where we are attending.: TODO [jorge] Investigate long running contests on juju.ubuntu.com: TODO + [niemeyer] Post instructions on how to use other code hosting options, and juju publish usage.: TODO -- Juju Contributor Onramp https://blueprints.launchpad.net/ubuntu/+spec/servercloud-1303-juju-contributor-onramp -- 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-1303-juju-contributor-onramp] Juju Contributor Onramp
Blueprint changed by Jorge O. Castro: Work items changed: Work items: [jorge] Contribute to this charm! link in the charm store.: BLOCKED [jorge] Tell people they can help. There's no mention of how to help on jujucharms.com. That sucks. Not make something and get a prize, make it make something you are going to use and get a prize.: BLOCKED [jorge] charm-tools, we need to talk about it more, make a Best practices for charms should be in write a charm, integrate the mythical best practices page with write a charm.: TODO [mark-mims] Investigate making charm documentation testable: TODO [evilnick] Investigate making charm documentation testable: TODO [gz] #1069883 Fix bug where defaulting to smallest instance type.: INPROGRESS [jjo] Case Studies from webops: TODO [mthaddon] Case Studies from webops: TODO [timrchavez] Case Studies from PES: TODO [jorge] README Review, prioritized based on charm popularity: TODO [jorge] Announce README fixups on the mailing list with maintainers: TODO [jorge] Codify for ~charmers to encourage people to fix readmes on submission of other fixes: TODO [jorge] File bugs on charms that don't meet quality guidelines. it would be great if this charm did multimaster!! and so on, so people know that they can fix it. needs-scaleout tag?: BLOCKED [jorge] Way to go, we have over 100 people who contributed charms and you told no one. Nice work.: TODO [jorge] Provider discounts for charmers?: INPROGRESS [jorge] Pimp my charm contest. or Xprize? Scale out HA x service to blah blah with integrated backups.: POSTPONED [jorge] Update /events page on juju.ubuntu.com to show where we are attending.: TODO [jorge] Investigate long running contests on juju.ubuntu.com: TODO [niemeyer] Post instructions on how to use other code hosting options, and juju publish usage.: TODO + [jorge] Ensure that the juju gui can run on the local provider: TODO -- Juju Contributor Onramp https://blueprints.launchpad.net/ubuntu/+spec/servercloud-1303-juju-contributor-onramp -- 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-r-juju-appserver-support] Juju support for application server technologies (Django, JEE, RoR, etc)
Blueprint changed by Jorge O. Castro: Work items changed: Work items: [jorge] Add App-By-Config and App-By-Subordinate to charm quality: TODO [clint-fewbar] Highlight examples of both approaches: TODO [brunogirin] evaluate/improve django (working with existing maintainer): INPROGRESS [brunogirin] Document deploying django tutorial with juju: TODO [jorge] sync up with dev to evaluate/improve node.js (working with existing maintainer): INPROGRESS [jorge] evaluate/improve rails (working with existing maintainer): DONE [brunogirin] Develop principles for normalizing interfaces in like services: TODO [marcoceppi] Contact and work with PHP app devs (Zend and Symfony): TODO [brunogirin] JBOSS charm: TODO [marcoceppi] Mediawiki: INPROGRESS - [jimbaker] Django: INPROGRESS - [jimbaker] MongoDB challenge: TODO + [brunogirin] Django: INPROGRESS + [a.rosales] MongoDB challenge: DONE [negronjl] MongoDB: INPROGRESS - [jorge] Postgresql: TODO - [robert-ayres] MySQL: TODO - [jorge] Node.js: TODO - [a.rosales] Node.js: TODO + [jorge] Postgresql: INPROGRESS + [robert-ayres] MySQL: INPROGRESS + [jorge] Node.js: INPROGRESS + [a.rosales] Node.js: INPROGRESS [mark-mims] Rails: INPROGRESS - [jorge] Memcached: TODO - [negronjl] Redis: TODO - [jorge] Varnish: TODO - [jorge] Cassandra (Talk to evan): TODO - [mark-mims] Rabbit and Sensu: TODO - [jorge] Logstash: TODO - [jorge] University charming: TODO + [jorge] Memcached: POSTPONED + [negronjl] Redis: POSTPONED + [jorge] Varnish: POSTPONED + [jorge] Cassandra (Talk to evan): DONE + [mark-mims] Rabbit and Sensu: POSTPONED + [jorge] Logstash: DONE + [jorge] University charming: POSTPONED -- Juju support for application server technologies (Django, JEE, RoR, etc) https://blueprints.launchpad.net/ubuntu/+spec/servercloud-r-juju-appserver-support -- 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
[Bug 955576] Re: 'local:' services not started on reboot
I'm putting a production tag on this to put it on our things that prevent Juju being used in production environments; developers can't push to prod if we keep resetting their environments. ** Tags added: production -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju in Ubuntu. https://bugs.launchpad.net/bugs/955576 Title: 'local:' services not started on reboot To manage notifications about this bug go to: https://bugs.launchpad.net/juju/+bug/955576/+subscriptions -- 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-r-juju-appserver-support] Juju support for application server technologies (Django, JEE, RoR, etc)
Blueprint changed by Jorge O. Castro: Work items changed: Work items: [jorge] Add App-By-Config and App-By-Subordinate to charm quality: TODO [clint-fewbar] Highlight examples of both approaches: TODO [brunogirin] evaluate/improve django (working with existing maintainer): TODO [brunogirin] Document deploying django tutorial with juju: TODO - [jorge] sync up with dev to evaluate/improve node.js (working with existing maintainer): TODO + [jorge] sync up with dev to evaluate/improve node.js (working with existing maintainer): INPROGRESS [jorge] evaluate/improve rails (working with existing maintainer): DONE [brunogirin] Develop principles for normalizing interfaces in like services: TODO [marcoceppi] Contact and work with PHP app devs (Zend and Symfony): TODO [brunogirin] JBOSS charm: TODO [marcoceppi] Mediawiki: INPROGRESS [jimbaker] Django: INPROGRESS [jimbaker] MongoDB challenge: TODO [negronjl] MongoDB: INPROGRESS [jorge] Postgresql: TODO [robert-ayres] MySQL: TODO [jorge] Node.js: TODO [a.rosales] Node.js: TODO [mark-mims] Rails: INPROGRESS [jorge] Memcached: TODO [negronjl] Redis: TODO [jorge] Varnish: TODO [jorge] Cassandra (Talk to evan): TODO [mark-mims] Rabbit and Sensu: TODO [jorge] Logstash: TODO [jorge] University charming: TODO -- Juju support for application server technologies (Django, JEE, RoR, etc) https://blueprints.launchpad.net/ubuntu/+spec/servercloud-r-juju-appserver-support -- 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-r-juju-appserver-support] Juju support for application server technologies (Django, JEE, RoR, etc)
Blueprint changed by Jorge O. Castro: Work items changed: Work items: - [jcastro] Add App-By-Config and App-By-Subordinate to charm quality: TODO + [jorge] Add App-By-Config and App-By-Subordinate to charm quality: TODO [clint-fewbar] Highlight examples of both approaches: TODO [brunogirin] evaluate/improve django (working with existing maintainer): TODO [brunogirin] Document deploying django tutorial with juju: TODO - [jcastro] sync up with dev to evaluate/improve node.js (working with existing maintainer): TODO - [jcastro] evaluate/improve rails (working with existing maintainer): TODO + [jorge] sync up with dev to evaluate/improve node.js (working with existing maintainer): TODO + [jorge] evaluate/improve rails (working with existing maintainer): DONE [brunogirin] Develop principles for normalizing interfaces in like services: TODO [marcoceppi] Contact and work with PHP app devs: TODO [brunogirin] JBOSS charm: TODO -- Juju support for application server technologies (Django, JEE, RoR, etc) https://blueprints.launchpad.net/ubuntu/+spec/servercloud-r-juju-appserver-support -- 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-r-juju-appserver-support] Juju support for application server technologies (Django, JEE, RoR, etc)
Blueprint changed by Jorge O. Castro: Work items changed: Work items: [jorge] Add App-By-Config and App-By-Subordinate to charm quality: TODO [clint-fewbar] Highlight examples of both approaches: TODO [brunogirin] evaluate/improve django (working with existing maintainer): TODO [brunogirin] Document deploying django tutorial with juju: TODO [jorge] sync up with dev to evaluate/improve node.js (working with existing maintainer): TODO [jorge] evaluate/improve rails (working with existing maintainer): DONE [brunogirin] Develop principles for normalizing interfaces in like services: TODO - [marcoceppi] Contact and work with PHP app devs: TODO + [marcoceppi] Contact and work with PHP app devs (Zend and Symfony): TODO [brunogirin] JBOSS charm: TODO + [marcoceppi] Mediawiki: INPROGRESS + [jimbaker] Django: INPROGRESS + [negronjl] MongoDB: INPROGRESS + [jorge] Postgresql: TODO + [robert-ayres] MySQL: TODO + [jorge] Node.js: TODO + [a.rosales] Node.js: TODO + [mark-mims] Rails: TODO + [jorge] Memcached: TODO + [negronjl] Redis: TODO + [jorge] Varnish: TODO + [jorge] Cassandra (Talk to evan): TODO + [mark-mims] Rabbit and Sensu: TODO + [jorge] Logstash: TODO -- Juju support for application server technologies (Django, JEE, RoR, etc) https://blueprints.launchpad.net/ubuntu/+spec/servercloud-r-juju-appserver-support -- 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
[Bug 1078444] Re: python-boto should verify SSL certificates and should use the systems certificate repository
** Changed in: python-boto (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to python-boto in Ubuntu. https://bugs.launchpad.net/bugs/1078444 Title: python-boto should verify SSL certificates and should use the systems certificate repository To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-boto/+bug/1078444/+subscriptions -- 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 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.: 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] 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 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-charmstore-maintenance] Juju Charm Store Maintenance
Blueprint changed by Jorge O. Castro: Work items changed: Work items: [clint-fewbar] update charm tools to support maintainer : DONE [clint-fewbar] assign maintainers to existing charms, everyone who committed to the charm pinged to see who will maintain it. : INPROGRESS [clint-fewbar] Document orphan process. : TODO [negronjl] Promulgate should run charm proof: DONE - [jorge] Update documentation to reflect reality: TODO - [jorge] Announce maintainer field requirement on the mailing list: TODO + [jorge] Update documentation to reflect reality (someone else did this): DONE + [jorge] Announce maintainer field requirement on the mailing list (thanks Clint!): DONE -- Juju Charm Store Maintenance https://blueprints.launchpad.net/ubuntu/+spec/servercloud-q-juju-charmstore-maintenance -- 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-unit-tests] Juju Charm Unit Tests
Blueprint changed by Jorge O. Castro: Work items set to: Work items: documentation for unit tests: TODO write examples of unit tests on flag-bearing charms: TODO make 'jitsu run-tests' aware of error codes: TODO [hazmat] charm proof testing: TODO keep everything green: TODO [mark-mims] make charmtester easier to use one-off by anyone: TODO [mark-mims] make charmtester whitelist: TODO extend charm tools to help generate tests: TODO run charmtester against maas environment: TODO -- Juju Charm Unit Tests https://blueprints.launchpad.net/ubuntu/+spec/servercloud-q-juju-charm-unit-tests -- 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-unit-tests] Juju Charm Unit Tests
Blueprint changed by Jorge O. Castro: Whiteboard changed: - charm unit tests recap... we automatically run: - - installation - - graph test + - installation + - graph test we'd like to additionally run - - charm tests + - charm tests read the spec lp:juju in the docs dir... look for something like charmtests.rst http://bazaar.launchpad.net/~clint-fewbar/juju/charm-tests-spec/view/head:/source/charm-tests.rst policy stuff? tests required? just encouraged for now additional testing plugins possible: - - nessus, etc against the running service - - app-armor complain against running service - - lint-type 'charm proof' - - upgrade-charm tests - - testing spread with add-unit - - coverage ??? - - watching relation settings?? + - nessus, etc against the running service + - app-armor complain against running service + - lint-type 'charm proof' + - upgrade-charm tests + - testing spread with add-unit + - coverage ??? + - watching relation settings?? please put all projects in one of: charm-tools juju-jitsu charms juju environments - include all of them, including MAAS support MAAS, other distro needs enable manual kicks from ~charmers (charmbot, but we prob wanna do that through openid over the web) - parameterized jenkins tests, both official and against specific distro needs charmtester is a *charm* in the charm store - test my custom stack of services is readily doable (contributions are welcome as always) jenkins file bugs when charms fail (close them when they pass again?) try for maintainer notification through launchpad how do long-failing tests relate to series freeze??? coverage tools possible? check out next cycle load testing for individual charms? for example, siege all charms with http interface scale testing? weekly large runs? really a _juju_ test and less a _charm_ test - - - ACTIONS: - [] documentation for unit tests - [] write examples of unit tests on flag-bearing charms - [] make 'jitsu run-tests' aware of error codes - [hazmat] charm proof testing - [] keep everything green - [mark-mims] make charmtester easier to use one-off by anyone - [mark-mims] make charmtester whitelist - [] extend charm tools to help generate tests - run charmtester against maas environment - - - #uds-q #servercloud #juju -- Juju Charm Unit Tests https://blueprints.launchpad.net/ubuntu/+spec/servercloud-q-juju-charm-unit-tests -- 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-charmstore-maintenance] Juju Charm Store Maintenance
Blueprint changed by Jorge O. Castro: Work items changed: Work items: + [clint-fewbar] Maintainer idea was almost universally accepted: TODO + [clint-fewbar] update charm tools to support maintainer : TODO + [clint-fewbar] assign maintainers to existing charms, everyone who committed to the charm pinged to see who will maintain it. : TODO + [clint-fewbar] Document orphan process. : TODO [negronjl] Promulgate should run charm proof: TODO - [clint-fewbar] update charm tools to support maintainer : DONE - [clint-fewbar] assign maintainers to existing charms, everyone who committed to the charm pinged to see who will maintain it. : INPROGRESS - [clint-fewbar] Document orphan process. : TODO + [jorge] Update documentation to reflect reality: TODO + [jorge] Announce maintainer field requirement on the mailing list: TODO -- Juju Charm Store Maintenance https://blueprints.launchpad.net/ubuntu/+spec/servercloud-q-juju-charmstore-maintenance -- 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 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 * 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-unit-tests] Juju Charm Unit Tests
Blueprint changed by Jorge O. Castro: Whiteboard set to: charm unit tests recap... we automatically run: - installation - graph test we'd like to additionally run - charm tests read the spec lp:juju in the docs dir... look for something like charmtests.rst http://bazaar.launchpad.net/~clint-fewbar/juju/charm-tests-spec/view/head:/source/charm-tests.rst policy stuff? tests required? just encouraged for now additional testing plugins possible: - nessus, etc against the running service - app-armor complain against running service - lint-type 'charm proof' - upgrade-charm tests - testing spread with add-unit - coverage ??? - watching relation settings?? please put all projects in one of: charm-tools juju-jitsu charms juju environments - include all of them, including MAAS support MAAS, other distro needs enable manual kicks from ~charmers (charmbot, but we prob wanna do that through openid over the web) - parameterized jenkins tests, both official and against specific distro needs charmtester is a *charm* in the charm store - test my custom stack of services is readily doable (contributions are welcome as always) jenkins file bugs when charms fail (close them when they pass again?) try for maintainer notification through launchpad how do long-failing tests relate to series freeze??? coverage tools possible? check out next cycle load testing for individual charms? for example, siege all charms with http interface scale testing? weekly large runs? really a _juju_ test and less a _charm_ test ACTIONS: [] documentation for unit tests [] write examples of unit tests on flag-bearing charms [] make 'jitsu run-tests' aware of error codes [hazmat] charm proof testing [] keep everything green [mark-mims] make charmtester easier to use one-off by anyone [mark-mims] make charmtester whitelist [] extend charm tools to help generate tests run charmtester against maas environment #uds-q #servercloud #juju -- Juju Charm Unit Tests https://blueprints.launchpad.net/ubuntu/+spec/servercloud-q-juju-charm-unit-tests -- 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-charms-release-policy] Clarifying Charm Store policy around Ubuntu Releases
Blueprint changed by Jorge O. Castro: Whiteboard set to: Charm Store Policy - This is a living policy, we will not try to get it perfect, so trying to get it perfect is not useful, we need to be agile and revisit our policies on a regular basis. - Charm Store doesn't freeze - I want stability. I want a single place to collaborate around. backports? charm store submissions? When to open the next release series? Where we've been doing: - Default series is LTS with juju deploy foo Where do we want to go with it: - Default series should be LTS with juju deploy foo - Search should default to the best possible solution first. what do we mean by: - open - able to push to this series - development focus - default series to build against? dev focus with release (at beta?) but insure lts gets as much focus as we can one approach - commit to latest dev focus - try to test on previous release - try to test further back two things to do this: - blacklisting for tests - better automated testing also start forward testing as soon as alpha1 is available perhaps charm browser can show test status for each charm... _per release_ security is an aspect of this when considering preventing, allowing, or automating back-ports maybe don't auto-backport... put on the maintainer's shoulders? what about use tags?... auto-backport only tagged appropriately? (kinda like pockets security, etc etc) Tags for charms to denote default behavior perhaps the only valid tags we can use are ones that can be automatically tested? we digress... we branched too late for precise release next time... ? - q the dev focus on beta1 day? - what to do with backports? hard problem, we don't have solid answers... maybe we just need to make a decision and run with it follow the distro model, but lag by three months adjust on demand Dev focus to stay on LTS (precise) and push promulgated charms forward and test forward WORK ITEMS? -- Clarifying Charm Store policy around Ubuntu Releases https://blueprints.launchpad.net/ubuntu/+spec/servercloud-q-juju-charms-release-policy -- 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-integration] Juju Integration
Blueprint changed by Jorge O. Castro: Whiteboard changed: Juju will not live in isolation https://launchpad.net/juju-jitsu exists to enable these use cases Potential integration points: - Existing Puppet Deployments - - Existing puppet subordinate charm promulgated yesterday + - Existing puppet subordinate charm promulgated yesterday - Existing Puppet Manifests - External Node Classifier - Capistrano / Fabric - - jitsu capfile - emits a capfile - - capistrano subordinate? + - jitsu capfile - emits a capfile + - capistrano subordinate? - Chef - SaltStack - + Solutions - REST API (lp:jrapi) other ways to integrate puppetforge cookbooks on github how do you make a charm out of any of these? - - - Work Items: - [mark-mims] charm to deploy chef-server (maybe w sub like clint's puppet sub) - [mark-mims] charms that call chef solo recipes - jujustrano - [negronjl] go to town on clint's puppet sub ( puppetforge? ) ( add charm create option for puppet recipes ) - define ways that capistrano would need to call Capistrano - [negronjl] jrapi as juju-jitsu subcommand... 'jitsu api' - [hazmat] export/import environment into juju-jitsu - use-cases for integration - how to make charms out of puppetforge modules / github cookbooks - plugin for chef-search to interface with juju (possibly just chef sub) - testing against euca and cloudstack - jenkins plugins for juju (anything other than charm-runner?) - vagrant integration to support local development story on osx - [mike-mcclurg] cloudstack integration - [imbrandon] investigate enstratus integration - - related - best practices for juju at scale -- Juju Integration https://blueprints.launchpad.net/ubuntu/+spec/servercloud-q-juju-integration -- 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-charmstore-maintenance] Juju Charm Store Maintenance
Blueprint changed by Jorge O. Castro: Whiteboard changed: == Everything has been copied to the Blueprint https://blueprints.launchpad.net/ubuntu/+spec/servercloud-q-juju-charmstore-maintenance -Juan ( negronjl ) == Welcome to Ubuntu Developer Summit! Avoiding charm store bitrot... automated testing - Assign maintainers to charms (metadata.yaml) - Failing tests for period of time. - - autofiles bug (puts in the Big List to be unpromulgated) + - autofiles bug (puts in the Big List to be unpromulgated) Policy would be to not promote charm series until it's all green (i.e., no critical bugs) Simplify writing tests: make it easy for users to run their own tests... merge 'charm test' in charm tools - - WORK ITEMS: - - [clint-fewbar] Maintainer idea was almost universally accepted: TODO - [negronjl] Promulgate should run charm proof: TODO - [clint-fewbar] update charm tools to support maintainer - [clint-fewbar] assign maintainers to existing charms, everyone who committed to the charm pinged to see who will maintain it. - [clint-fewbar] Document orphan process. -- Juju Charm Store Maintenance https://blueprints.launchpad.net/ubuntu/+spec/servercloud-q-juju-charmstore-maintenance -- 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
[Bug 828288] [NEW] Cobbler errors while importing mini.isos
Public bug reported: I get this over and over for each iso it tries to import when doing a clean install on an up to date oneiric as of Aug 17, the install never finishes: mount: warning: /tmp/cobbler-ubuntu-import.NfFK3f/mnt seems to be mounted read-only. task started: 2011-08-17_150624_import task started (id=Media import, time=Wed Aug 17 15:06:24 2011) Found a debian/ubuntu compatible signature: .disk/mini-info running: rsync -a '/tmp/cobbler-ubuntu-import.NfFK3f/mnt/' /var/www/cobbler/ks_mirror/oneiric-x86_64/ --exclude-from=/etc/cobbler/rsync.exclude --quiet received on stdout: received on stderr: adding distros creating new distro: oneiric-x86_64 Exception occured: class 'cobbler.cexceptions.CX' Exception value: 'Failed to load module for dhcp/module' Exception Info: File /usr/lib/python2.7/dist-packages/cobbler/remote.py, line 93, in run rc = self._run(self) File /usr/lib/python2.7/dist-packages/cobbler/remote.py, line 227, in runner self.logger File /usr/lib/python2.7/dist-packages/cobbler/api.py, line 756, in import_tree return manager.run(pkgdir,mirror_url,mirror_name,network_root,kickstart_file,rsync_flags,arch,breed,os_version) File /usr/lib/python2.7/dist-packages/cobbler/modules/manage_import_debian_ubuntu.py, line 275, in run os.path.walk(self.path, self.distro_adder, distros_added) File /usr/lib/python2.7/posixpath.py, line 229, in walk func(arg, top, names) File /usr/lib/python2.7/dist-packages/cobbler/modules/manage_import_debian_ubuntu.py, line 420, in distro_adder adtls.append(self.add_entry(dirname,kernel,initrd)) File /usr/lib/python2.7/dist-packages/cobbler/modules/manage_import_debian_ubuntu.py, line 484, in add_entry self.distros.add(distro,save=True) File /usr/lib/python2.7/dist-packages/cobbler/collection.py, line 276, in add self.lite_sync = action_litesync.BootLiteSync(self.config, logger=logger) File /usr/lib/python2.7/dist-packages/cobbler/action_litesync.py, line 57, in __init__ self.sync= config.api.get_sync(verbose,logger=self.logger) File /usr/lib/python2.7/dist-packages/cobbler/api.py, line 706, in get_sync manage_isc File /usr/lib/python2.7/dist-packages/cobbler/api.py, line 825, in get_module_from_file return module_loader.get_module_from_file(section,name,fallback) File /usr/lib/python2.7/dist-packages/cobbler/module_loader.py, line 96, in get_module_from_file raise CX(_(Failed to load module for %s/%s) % (category,field)) !!! TASK FAILED !!! failed to import oneiric-x86_64 profile oneiric-x86_64 not found, inheritance not possible ** Affects: cobbler (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cobbler in Ubuntu. https://bugs.launchpad.net/bugs/828288 Title: Cobbler errors while importing mini.isos To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cobbler/+bug/828288/+subscriptions -- 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
[Bug 828288] Re: Cobbler errors while importing mini.isos
** Attachment added: modules.conf https://bugs.launchpad.net/ubuntu/+source/cobbler/+bug/828288/+attachment/2287479/+files/modules.conf -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cobbler in Ubuntu. https://bugs.launchpad.net/bugs/828288 Title: Cobbler errors while importing mini.isos To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cobbler/+bug/828288/+subscriptions -- 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
[Bug 828288] Re: Cobbler errors while importing mini.isos
** Attachment added: settings https://bugs.launchpad.net/ubuntu/+source/cobbler/+bug/828288/+attachment/2287478/+files/settings -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cobbler in Ubuntu. https://bugs.launchpad.net/bugs/828288 Title: Cobbler errors while importing mini.isos To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cobbler/+bug/828288/+subscriptions -- 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
[Bug 828288] Re: Cobbler errors while importing mini.isos
It appears that cobbler-ubuntu-import is the command causing the problem cobbler-ubuntu-import natty-x86_64 returns the same error message. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cobbler in Ubuntu. https://bugs.launchpad.net/bugs/828288 Title: Cobbler errors while importing mini.isos To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cobbler/+bug/828288/+subscriptions -- 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
[Bug 828288] Re: Cobbler errors while importing mini.isos
** Attachment added: modules.conf https://bugs.launchpad.net/ubuntu/+source/cobbler/+bug/828288/+attachment/2287480/+files/modules.conf -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cobbler in Ubuntu. https://bugs.launchpad.net/bugs/828288 Title: Cobbler errors while importing mini.isos To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cobbler/+bug/828288/+subscriptions -- 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
Re: [Bug 828288] Re: Cobbler errors while importing mini.isos
Yep, that did the trick! -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cobbler in Ubuntu. https://bugs.launchpad.net/bugs/828288 Title: Cobbler errors while importing mini.isos To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cobbler/+bug/828288/+subscriptions -- 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
[Bug 644632] Re: nssldap-update-ignoreusers needs to be configurable to ignore users
** Changed in: libnss-ldap (Ubuntu) Assignee: (unassigned) = Nigel Babu (nigelbabu) -- nssldap-update-ignoreusers needs to be configurable to ignore users https://bugs.launchpad.net/bugs/644632 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to libnss-ldap in ubuntu. -- 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
[Bug 497894] Re: Support Application Indicators
** Changed in: bacula (Ubuntu) Importance: Wishlist = Low -- Support Application Indicators https://bugs.launchpad.net/bugs/497894 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to bacula in ubuntu. -- 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
[Bug 497894] [NEW] Support Application Indicators
Public bug reported: This application should be investigated to be ported to use Application Indicators for Lucid - https://edge.launchpad.net/indicator-application affects ubuntu/bacula tag indicator-application ** Affects: bacula (Ubuntu) Importance: Undecided Status: New ** Tags: indicator-application -- Support Application Indicators https://bugs.launchpad.net/bugs/497894 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to bacula in ubuntu. -- 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
[Bug 175527] Re: umount.cifs doesn't remove entry from /etc/mtab
** Also affects: samba via https://bugzilla.samba.org/show_bug.cgi?id=4370 Importance: Unknown Status: Unknown -- umount.cifs doesn't remove entry from /etc/mtab https://bugs.launchpad.net/bugs/175527 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in ubuntu. -- 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
[Bug 318703] Re: nagios check_smtp expects integer instead of double
** Also affects: nagios-plugins via http://sourceforge.net/support/tracker.php?aid=2555775 Importance: Unknown Status: Unknown -- nagios check_smtp expects integer instead of double https://bugs.launchpad.net/bugs/318703 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nagios-plugins in ubuntu. -- 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
