[Blueprint servercloud-r-juju-charm-testing] Juju Charm Testing
Blueprint changed by Antonio Rosales: Whiteboard changed: Discussion: *Bug submission on charm failure. *Define a process around how charm maintainers respond to test failures and subsequent bugs. Can a user run a manual test and submit the test back to the bug report to update testing status to green. *Enable Autocharm tester to be more resilient against provider failures, and Jenkins usage. simulate provider failure, and be able to recover: $ juju ssh MACHINE sudo shutdown now * Define WIs to execute auto charm testing on Go. * Continuous Integration (also will help with gating on charm commits) * Juju Testing Blogging * Juju testing communication to Juju lists. Reference Links: *Charm Test Spec [html] https://juju.ubuntu.com/docs/charm-tests.html - * Charm Test Speck [source] http://bazaar.launchpad.net/~juju/juju/docs/view/head:/source/charm-tests.rst + * Charm Test Spec [source] http://bazaar.launchpad.net/~juju/juju/docs/view/head:/source/charm-tests.rst * CharmTester Charm http://jujucharms.com/~mark-mims/oneiric/charmtester * Jenkins Charm Testing: https://jenkins.qa.ubuntu.com/view/Charms/ --- User Stories --- --- Risks --- --- Test Plans --- --- Release Note --- --- Blog Post --- (Needs spec and WI definition) -[a.rosales; 12-DEC-2012] -- Juju Charm Testing https://blueprints.launchpad.net/ubuntu/+spec/servercloud-r-juju-charm-testing -- 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 Antonio Rosales: 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 (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: 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 + [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 Antonio Rosales: 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 (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: 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 Antonio Rosales: Whiteboard changed: User Stories: As a sysop, I want to deploy a web application container on a cloud node. As a developer, I want to create a Juju charm to deploy my web application on any compatible container. Example of compatible container: Django app = Django container; JEE .war = servlet container (e.g. Apache Tomcat) or JEE app server (e.g. JBoss); JEE .ear or .jar = JEE app server (e.g. JBoss) As a sysop, I want to deploy a web application onto a compatible container node. As a sysop, I want to define a named data source in a web app node and add a relationship to a database node for that data source. Risks: Properly gathering best practices from developer communities, and integrating that knowledge into the framework charm itself. Test Plans: - CharmTesting should be leveraged here to exercise a framework charm with traditional workloads, and to specifically repeatedly exercise the individual functions of the framework charm. + CharmTesting should be leveraged here to exercise a framework charm with traditional workloads, and to specifically repeatedly exercise the individual functions of the framework charm. Framework charm development will need a base set of application charms to test the functionality of the framework itself. There could also be an “exerciser” framework charm that specifically and exhaustively tests each function of the framework (where a ‘normal’ application charm may not exercise all the functions or do it repeatedly). - Release Note: + Release Note: Release not may not be applicable here, but we should blog about framework charms so folks now they are available to use. - --- Discussion at UDS --- Why is this important - Application servers come before Apps - Private/Enterprise apps are more numerous than public apps - Deployment needs to be easier/simpler because testing suffers when deployment is difficult --- jitsu import/export for above ? - Connect named resources to app without app specifically knowing about it - Scalability as needed PaaSish Ubuntu Juju mailing list: -https://lists.ubuntu.com/archives/juju/2012-October/001910.html Improving framework/infrastructure service charms on Juju mailing list: -https://lists.ubuntu.com/archives/juju/2012-September/001884.html - List of possible technologies to take into account: - mediawiki - Django - MongoDB - Postgres - MySQL - node.js - rails/rack-esque - memcacheD - varnish - redis - rabbit - Pyramid - Sensu - Logstash - rsyslog - WordPress - Possible implementation options (may not be mutually exclusive): # App-by-Subordinate juju deploy django juju deploy myapp # subordinate juju add-relation django myapp juju deploy mysql app-db-1 juju add-relation app-db-1 django # relation handled by django via ORM layer juju deploy mongodb juju add-relation myapp mongodb # relation handled by the app itself -- # App-by-Config juju deploy django --set app-src=git:// -- # App-by-Fork bzr branch lp:charms/django myapp -- 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-charm-testing] Juju Charm Testing
Blueprint changed by Antonio Rosales: Whiteboard changed: Discussion: *Bug submission on charm failure. *Define a process around how charm maintainers respond to test failures and subsequent bugs. Can a user run a manual test and submit the test back to the bug report to update testing status to green. *Enable Autocharm tester to be more resilient against provider failures, and Jenkins usage. simulate provider failure, and be able to recover: $ juju ssh MACHINE sudo shutdown now * Define WIs to execute auto charm testing on Go. * Continuous Integration (also will help with gating on charm commits) * Juju Testing Blogging * Juju testing communication to Juju lists. + * Work on integrating/fixing Charm runner (graph testing/ dependency/env set up testing). Reference Links: *Charm Test Spec [html] https://juju.ubuntu.com/docs/charm-tests.html * Charm Test Spec [source] http://bazaar.launchpad.net/~juju/juju/docs/view/head:/source/charm-tests.rst * CharmTester Charm http://jujucharms.com/~mark-mims/oneiric/charmtester * Jenkins Charm Testing: https://jenkins.qa.ubuntu.com/view/Charms/ --- User Stories --- --- Risks --- --- Test Plans --- --- Release Note --- --- Blog Post --- (Needs spec and WI definition) -[a.rosales; 12-DEC-2012] -- Juju Charm Testing https://blueprints.launchpad.net/ubuntu/+spec/servercloud-r-juju-charm-testing -- 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-charm-testing] Juju Charm Testing
Blueprint changed by Antonio Rosales: Whiteboard changed: Discussion: *Bug submission on charm failure. *Define a process around how charm maintainers respond to test failures and subsequent bugs. Can a user run a manual test and submit the test back to the bug report to update testing status to green. *Enable Autocharm tester to be more resilient against provider failures, and Jenkins usage. simulate provider failure, and be able to recover: $ juju ssh MACHINE sudo shutdown now * Define WIs to execute auto charm testing on Go. * Continuous Integration (also will help with gating on charm commits) * Juju Testing Blogging * Juju testing communication to Juju lists. - * Work on integrating/fixing Charm runner (graph testing/ dependency/env set up testing). + * Work on integrating/fixing Charm runner (graph testing/ dependency/env set up testing). + + Add a Jenkins workflow to run a charm or a set of charms in the following LXC environments: + raring container on raring host + raring container on precise host + precise container on raring host + precise container on precise host Reference Links: *Charm Test Spec [html] https://juju.ubuntu.com/docs/charm-tests.html * Charm Test Spec [source] http://bazaar.launchpad.net/~juju/juju/docs/view/head:/source/charm-tests.rst * CharmTester Charm http://jujucharms.com/~mark-mims/oneiric/charmtester * Jenkins Charm Testing: https://jenkins.qa.ubuntu.com/view/Charms/ --- User Stories --- --- Risks --- --- Test Plans --- --- Release Note --- --- Blog Post --- (Needs spec and WI definition) -[a.rosales; 12-DEC-2012] -- Juju Charm Testing https://blueprints.launchpad.net/ubuntu/+spec/servercloud-r-juju-charm-testing -- 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-charm-testing] Juju Charm Testing
Blueprint changed by Antonio Rosales: Whiteboard changed: Discussion: *Bug submission on charm failure. *Define a process around how charm maintainers respond to test failures and subsequent bugs. Can a user run a manual test and submit the test back to the bug report to update testing status to green. *Enable Autocharm tester to be more resilient against provider failures, and Jenkins usage. simulate provider failure, and be able to recover: $ juju ssh MACHINE sudo shutdown now * Define WIs to execute auto charm testing on Go. * Continuous Integration (also will help with gating on charm commits) * Juju Testing Blogging * Juju testing communication to Juju lists. * Work on integrating/fixing Charm runner (graph testing/ dependency/env set up testing). Add a Jenkins workflow to run a charm or a set of charms in the following LXC environments: - raring container on raring host - raring container on precise host - precise container on raring host - precise container on precise host + -raring container on raring host + -raring container on precise host + -precise container on raring host + -precise container on precise host Reference Links: *Charm Test Spec [html] https://juju.ubuntu.com/docs/charm-tests.html * Charm Test Spec [source] http://bazaar.launchpad.net/~juju/juju/docs/view/head:/source/charm-tests.rst * CharmTester Charm http://jujucharms.com/~mark-mims/oneiric/charmtester * Jenkins Charm Testing: https://jenkins.qa.ubuntu.com/view/Charms/ --- User Stories --- --- Risks --- --- Test Plans --- --- Release Note --- --- Blog Post --- (Needs spec and WI definition) -[a.rosales; 12-DEC-2012] -- Juju Charm Testing https://blueprints.launchpad.net/ubuntu/+spec/servercloud-r-juju-charm-testing -- 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-charm-testing] Juju Charm Testing
Blueprint changed by Antonio Rosales: Assignee: Jim Baker = Antonio Rosales -- Juju Charm Testing https://blueprints.launchpad.net/ubuntu/+spec/servercloud-r-juju-charm-testing -- 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-charm-testing] Juju Charm Testing
Blueprint changed by Antonio Rosales: Whiteboard changed: Discussion: *Bug submission on charm failure. *Define a process around how charm maintainers respond to test failures and subsequent bugs. Can a user run a manual test and submit the test back to the bug report to update testing status to green. *Enable Autocharm tester to be more resilient against provider failures, and Jenkins usage. simulate provider failure, and be able to recover: $ juju ssh MACHINE sudo shutdown now * Define WIs to execute auto charm testing on Go. * Continuous Integration (also will help with gating on charm commits) * Juju Testing Blogging * Juju testing communication to Juju lists. * Work on integrating/fixing Charm runner (graph testing/ dependency/env set up testing). Add a Jenkins workflow to run a charm or a set of charms in the following LXC environments: - -raring container on raring host - -raring container on precise host + -raring container on raring host + -raring container on precise host -precise container on raring host - -precise container on precise host + -precise container on precise host Reference Links: *Charm Test Spec [html] https://juju.ubuntu.com/docs/charm-tests.html * Charm Test Spec [source] http://bazaar.launchpad.net/~juju/juju/docs/view/head:/source/charm-tests.rst * CharmTester Charm http://jujucharms.com/~mark-mims/oneiric/charmtester + * Charm Runner: https://launchpad.net/charmrunner * Jenkins Charm Testing: https://jenkins.qa.ubuntu.com/view/Charms/ --- User Stories --- --- Risks --- --- Test Plans --- --- Release Note --- --- Blog Post --- (Needs spec and WI definition) -[a.rosales; 12-DEC-2012] -- Juju Charm Testing https://blueprints.launchpad.net/ubuntu/+spec/servercloud-r-juju-charm-testing -- 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 Antonio Rosales: Drafter: (none) = Ubuntu Server Team -- 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 Antonio Rosales: 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 + [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 -- 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 Antonio Rosales: Whiteboard set to: UDS 1303 Pad Data: Old spec: https://blueprints.launchpad.net/ubuntu/+spec/community-r-juju-contributor-onramp-1 New spec: https://blueprints.launchpad.net/ubuntu/+spec/servercloud-1303-juju-contributor-onramp 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) -- 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 Antonio Rosales: Whiteboard set to: --- 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 -? -- 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-r-juju-charm-testing] Juju Charm Testing
Blueprint changed by Antonio Rosales: Whiteboard changed: Discussion: *Bug submission on charm failure. *Define a process around how charm maintainers respond to test failures and subsequent bugs. Can a user run a manual test and submit the test back to the bug report to update testing status to green. *Enable Autocharm tester to be more resilient against provider failures, and Jenkins usage. simulate provider failure, and be able to recover: $ juju ssh MACHINE sudo shutdown now * Define WIs to execute auto charm testing on Go. * Continuous Integration (also will help with gating on charm commits) * Juju Testing Blogging * Juju testing communication to Juju lists. * Work on integrating/fixing Charm runner (graph testing/ dependency/env set up testing). Add a Jenkins workflow to run a charm or a set of charms in the following LXC environments: -raring container on raring host -raring container on precise host -precise container on raring host -precise container on precise host Reference Links: *Charm Test Spec [html] https://juju.ubuntu.com/docs/charm-tests.html * Charm Test Spec [source] http://bazaar.launchpad.net/~juju/juju/docs/view/head:/source/charm-tests.rst * CharmTester Charm http://jujucharms.com/~mark-mims/oneiric/charmtester - * Charm Runner: https://launchpad.net/charmrunner + * Charm Runner: https://launchpad.net/charmrunner * Jenkins Charm Testing: https://jenkins.qa.ubuntu.com/view/Charms/ --- User Stories --- --- Risks --- --- Test Plans --- --- Release Note --- --- Blog Post --- (Needs spec and WI definition) -[a.rosales; 12-DEC-2012] + + === UDS 1303 Notes === + Pad: http://pad.ubuntu.com/uds-1303-servercloud-r-juju-charm-testing + + Question: + Is there a way in meta-data to explicitly state provider support. + -Example: Ceph: Does cloud provider have block support + -More broadly stated does the cloud provider have the capabilities the charm needs + + Idea: + -In charm testing status be able to show that a charm failure can be a result of the provider not providing the needed capabilities, ie the Ceph charm fails on a provider because it does not support object store. + -Make interface usage more verbose in the charm description. + -Need a rule/spec on how a interface should be implemented + -Need to investigate possible enforment of interfaces + -**Have the testing framework iterate through the operational deployment requirments. + + Interfaces doc link broken: + -Example: http://jujucharms.com/interfaces/ceph-client Interface doc link broken: + https://juju.ubuntu.com/Interfaces/ceph-client -- broken + + Meta-language testing (http://paste.ubuntu.com/5588570/): + + Lanugage suggestions: + http://lettuce.it/ + http://cukes.info/ -- Juju Charm Testing https://blueprints.launchpad.net/ubuntu/+spec/servercloud-r-juju-charm-testing -- 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 Antonio Rosales: 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 - New spec: https://blueprints.launchpad.net/ubuntu/+spec/servercloud-1303-juju-contributor-onramp 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) -- 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-webscale] WebScale Packaging and Main Promotions
Blueprint changed by Antonio Rosales: Whiteboard changed: --- User Stories --- Frank wants to deploy nginx instead of apache to support a specific requirement he has which cannot but fulfilled bu apache; he's able to use a fully supported solution when using Ubuntu. Toby is a nodejs developer; Ubuntu has the latest and greatest packaged and easily installable. Ante has been deploying varnish for some time; Ubuntu now fully supports varnish so he can stop cutting his own security updates. --- Risks --- Upstream appetite Volatility/release frequency of upstream projects (nodejs specifically). --- Test Plans --- TBC --- Release Note --- [NGINX|nodejs|MongoDB|Varnish] is now in Ubuntu main and will recieved Security Updates from the Ubuntu Security Team. --- Blog Post --- Maybe - --- UDS Discussion --- + --- UDS R+1303 Discussion --- + 1303 Pad: http://pad.ubuntu.com/uds-1303-webscale-packaging-review - Etherpad from UDS session: + Etherpad from UDS session (which one? R): Webscale Packaging Improvements and main promotions * Nginx - Has become de-facto scalable web server, and grown up as an OSS project now - - Bug tracker? Now addressed - - Supporting tooling might need some work to get feature parity with Apache: - - nginxensite/nginxenmod etc - - http://nginx.org/en/security_advisories.html - - Better backend support sounds compelling + - Bug tracker? Now addressed + - Supporting tooling might need some work to get feature parity with Apache: + - nginxensite/nginxenmod etc + - http://nginx.org/en/security_advisories.html + - Better backend support sounds compelling * Node.js - Gaining popularity fast, and *SHOULD* be a build-dep of OpenStack Horizon - - Also a direct dependency of the new Juju GUI - - Azure tooling - - Openstack Horizon Build Dependency - - RBD's should drive seeding... +- Also a direct dependency of the new Juju GUI +- Azure tooling +- Openstack Horizon Build Dependency +- RBD's should drive seeding...(What's an RBD?) good question +-Package moves too fast to maintain or upload an appropriate version in Ubuntu Main/Supported archive. +-probably better to have node.js in a PPA + -https://launchpad.net/~chris-lea/+archive/node.js +-Other deps are gotten from npm +-reliance on specific node.js versions sounds like the messy world of java dependencies +-A version of nodejs in backports would be better I think than PPA, or supply different versions for the user to decide. + -If the PPA was official this may have some of the same effect as backports + -ARM support would be a plus, and have that incluced in the PPA. + + * MongoDB (also headed for main as part of juju) + - Dependency for Go Juju + - Required support for TLS - needs looking at + - The license of OpenSSL apparently prevents arbitrary shipping + - There's _apparently_ an exception that allows Ubuntu to ship it + - If that's the case, we should really ship that support. It's a good service we'd be doing to people. + - http://people.gnome.org/~markmc/openssl-and-the-gpl.html + - ceilometer support required this + - Cons: large codebase + - Pros: good upstream development process. + - James Page poked mongodb enough last night to get 2.2.3 into raring, sans SSL support + - 2.4 is headed for inclusion + JamesPage requested a OpenSSL license exception from upstream to resolve this cleanly - * MongoDB (also headed for main as part of juju) - - Dependency for Go Juju - - Required support for TLS - needs looking at - - ceilometer support required this - Cons: large codebase - Pros: good upstream development process. + *Nginx + -Ben notes some improvments in reverse proxy over squid + -Ben to volunteer to package Nginx + -code: svn://svn.nginx.org/nginx + + * Varnish (if time) + - Popular heavily used caching. + - More configurable--language based. + -in universe + -Upstream position on Ubuntu packages: https://www.varnish-cache.org/installation/ubuntu + -Does this infer that upstream only supports the latest, and if so how often does that change. + -How does upstream handle their packaging version/updates, bug fixes, how often does it change, and what is supported +http://packages.debian.org/squeeze/varnish +-Consensus was to communicate with upstream on the Ubuntu MIR needs. - * Varnish (if time) - Popular heavily used caching. - More configurable--language based. + *Jboss + -Not trivial to support (for initial packaging, regular maintenance and security) + -Needs some further investigation around a MIR reqest + - only a reduced subset of JBoss is currently in Debian/Ubuntu +- http://wiki.debian.org/JBossPackaging + - receives regular security updates (from RedHat, who
[Blueprint servercloud-r-webscale] WebScale Packaging and Main Promotions
Blueprint changed by Antonio Rosales: Work items changed: Work items: - Identify specific advantages of nginx over apache: TODO - Review security track record of nginx: TODO - Speak with nginx upstream re main inclusion appetite: TODO - Prepare MIR for nginx: BLOCKED + [utlemming] Identify specific advantages of nginx over apache: TODO + [utlemming] Review security track record of nginx: TODO + [utlemming] Speak with nginx upstream re main inclusion appetite: TODO + [utlemming] Prepare MIR for nginx: BLOCKED Evaluate nodejs core in supported seed: TODO Confirm npm not suitable for inclusion: TODO Prepare MIR for nodejs: BLOCKED Evalute mongodb for supported seed: INPROGRESS Confirm mongodb upstream appetite: TODO Review SSL support enablement in MongoDB: INPROGRESS Hook up with go juju team with dependency on mongodb: DONE Prepare MIR for mongodb: BLOCKED [ivoks] Determine if there is value in including varnish in main: TODO [ivoks] Prepare MIR for varnish: BLOCKED -- WebScale Packaging and Main Promotions https://blueprints.launchpad.net/ubuntu/+spec/servercloud-r-webscale -- 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 Antonio Rosales: 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 - + *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 + *Getting Started (Juju deploy) + *Charm Development + *Charm Deployment + *Charm Discovery + *Charm Debugging Model magazines - *Wired - *Linux Format - *Content rich - + *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? + *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 + *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. + 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 + 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 -? -- 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 Antonio Rosales: Work items set to: Work items: [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 Antonio Rosales: 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 + -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 -? - - TO DOs: - Define structural elements of HTML5 doc (evilnick) - Create sample getting Started Guide (evilnick) - Create list of screencasts (jorge, evilnick) -- 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-r-mysql] MySQL Roundtable
Blueprint changed by Antonio Rosales: Work items changed: Work items: [clint-fewbar] Package percona cluster server for Debian and Ubuntu: TODO [clint-fewbar] Resolve delta between ubuntu and debian: TODO [nryeng] Investigate packaging mysql cluster for Debian/Ubuntu: TODO - [clint-fewbar] Talk with nryeng about juju charm improvements: TODO + [a.rosales] Talk with nryeng about juju charm improvements: TODO -- MySQL Roundtable https://blueprints.launchpad.net/ubuntu/+spec/servercloud-r-mysql -- 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-charm-testing] Juju Charm Testing
Blueprint changed by Antonio Rosales: Assignee: Antonio Rosales = Marco Ceppi -- Juju Charm Testing https://blueprints.launchpad.net/ubuntu/+spec/servercloud-r-juju-charm-testing -- 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 Antonio Rosales: 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 + Reference Guide + Full table of all charm attributes + Full table of all juju commands + example: http://developer.android.com/reference/packages.html + 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 - creating relations - removing relations + creating relations + removing relations 1. [user] Service configuration/Lifecycle managment: Using the configuration.yaml juju set i. https://juju.ubuntu.com/docs/service-config.html 1.[user] Scaling services 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
[Blueprint servercloud-1303-juju-docs] Improve Juju Documentation
Blueprint changed by Antonio Rosales: 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” +Local provider configuration +OpenStack provider configuration +EC2 provider configuration - all the provider stuff should be in one section +All provider configs here +Deploying a Charm +Exposing A charm +Implicit Relations +Machine Constraints + * User tutorial - rename to “Using Juju” (should be embeddedd per topic) 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 Reference Guide - Full table of all charm attributes - Full table of all juju commands - example: http://developer.android.com/reference/packages.html + Full table of all charm attributes + Full table of all juju commands + example: http://developer.android.com/reference/packages.html 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 creating relations removing relations 1. [user] Service configuration/Lifecycle managment: Using the configuration.yaml juju set i. https://juju.ubuntu.com/docs/service-config.html 1.[user] Scaling services 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
[Blueprint servercloud-1303-juju-docs] Improve Juju Documentation
Blueprint changed by Antonio Rosales: 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 -Local provider configuration -OpenStack provider configuration -EC2 provider configuration - all the provider stuff should be in one section -All provider configs here -Deploying a Charm -Exposing A charm -Implicit Relations -Machine Constraints - * User tutorial - rename to “Using Juju” (should be embeddedd per topic) +Providers: + Local provider configuration + OpenStack provider configuration + EC2 provider configuration +Rackspace +New Providers + Deploying a Charm + Exposing A charm + Implicit Relations + Machine Constraints + * User tutorial - rename to “Using Juju” (should be embeddedd per topic) Charms 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 Reference Guide Full table of all charm attributes Full table of all juju commands example: http://developer.android.com/reference/packages.html + Glossary -appendix + Operating Systems - appendix stuff + Relation references - appendix stuff 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 -? + -move- + About juju - *move to juju.ubuntu.com. + -delete- + Frequently Asked Questions - DELETE THIS, link to autogenerated FAQ at AU. + juju modules - remove Juju core specific + Drafts - REMOVE. + -content should be covered- + Implementation details - (should be in reference guide for charm attributes) + Commands to work with relation settings and membership (be sure to cover in charm author) + Upgrades - both (be sure how to implement charm upgrade hooks are covered in charm author) + Charm Upgrades (be sure to be covered in Charm Users: deployment) + New relation-ids hook command -(should be covered in charm author) # 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 creating relations removing relations 1. [user] Service configuration/Lifecycle managment: Using the configuration.yaml
[Blueprint servercloud-1303-juju-docs] Improve Juju Documentation
Blueprint changed by Antonio Rosales: 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 -Providers: Local provider configuration OpenStack provider configuration EC2 provider configuration -Rackspace -New Providers + Rackspace + New Providers Deploying a Charm Exposing A charm Implicit Relations Machine Constraints * User tutorial - rename to “Using Juju” (should be embeddedd per topic) Charms 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 Reference Guide Full table of all charm attributes Full table of all juju commands example: http://developer.android.com/reference/packages.html - Glossary -appendix - Operating Systems - appendix stuff - Relation references - appendix stuff + Glossary -appendix + Operating Systems - appendix stuff + Relation references - appendix stuff Evaluate for removal: -move- - About juju - *move to juju.ubuntu.com. + About juju - *move to juju.ubuntu.com. -delete- - Frequently Asked Questions - DELETE THIS, link to autogenerated FAQ at AU. - juju modules - remove Juju core specific - Drafts - REMOVE. + Frequently Asked Questions - DELETE THIS, link to autogenerated FAQ at AU. + juju modules - remove Juju core specific + Drafts - REMOVE. -content should be covered- - Implementation details - (should be in reference guide for charm attributes) - Commands to work with relation settings and membership (be sure to cover in charm author) - Upgrades - both (be sure how to implement charm upgrade hooks are covered in charm author) - Charm Upgrades (be sure to be covered in Charm Users: deployment) - New relation-ids hook command -(should be covered in charm author) + Implementation details - (should be in reference guide for charm attributes) + Commands to work with relation settings and membership (be sure to cover in charm author) + Upgrades - both (be sure how to implement charm upgrade hooks are covered in charm author) + Charm Upgrades (be sure to be covered in Charm Users: deployment) + New relation-ids hook command -(should be covered in charm author) # 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 creating relations removing relations 1. [user] Service configuration/Lifecycle managment: Using
[Blueprint servercloud-r-juju-appserver-support] Juju support for application server technologies (Django, JEE, RoR, etc)
Blueprint changed by Antonio Rosales: Whiteboard changed: User Stories: As a sysop, I want to deploy a web application container on a cloud node. As a developer, I want to create a Juju charm to deploy my web application on any compatible container. Example of compatible container: Django app = Django container; JEE .war = servlet container (e.g. Apache Tomcat) or JEE app server (e.g. JBoss); JEE .ear or .jar = JEE app server (e.g. JBoss) As a sysop, I want to deploy a web application onto a compatible container node. As a sysop, I want to define a named data source in a web app node and add a relationship to a database node for that data source. Risks: Properly gathering best practices from developer communities, and integrating that knowledge into the framework charm itself. Test Plans: CharmTesting should be leveraged here to exercise a framework charm with traditional workloads, and to specifically repeatedly exercise the individual functions of the framework charm. Framework charm development will need a base set of application charms to test the functionality of the framework itself. There could also be an “exerciser” framework charm that specifically and exhaustively tests each function of the framework (where a ‘normal’ application charm may not exercise all the functions or do it repeatedly). Release Note: Release not may not be applicable here, but we should blog about framework charms so folks now they are available to use. --- Discussion at UDS --- Why is this important - Application servers come before Apps - Private/Enterprise apps are more numerous than public apps - Deployment needs to be easier/simpler because testing suffers when deployment is difficult --- jitsu import/export for above ? - Connect named resources to app without app specifically knowing about it - Scalability as needed PaaSish Ubuntu Juju mailing list: -https://lists.ubuntu.com/archives/juju/2012-October/001910.html Improving framework/infrastructure service charms on Juju mailing list: -https://lists.ubuntu.com/archives/juju/2012-September/001884.html Possible implementation options (may not be mutually exclusive): # App-by-Subordinate juju deploy django juju deploy myapp # subordinate juju add-relation django myapp juju deploy mysql app-db-1 juju add-relation app-db-1 django # relation handled by django via ORM layer juju deploy mongodb juju add-relation myapp mongodb # relation handled by the app itself -- # App-by-Config juju deploy django --set app-src=git:// -- # App-by-Fork bzr branch lp:charms/django myapp + + [2013-04-21: arosales: current work being tracked in + https://blueprints.launchpad.net/ubuntu/+spec/servercloud-1305-juju- + framework-charms Thus, postponing all non-done work items.] -- 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 Antonio Rosales: 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] Add App-By-Config and App-By-Subordinate to charm quality: POSTPONED + [clint-fewbar] Highlight examples of both approaches: POSTPONED + [brunogirin] evaluate/improve django (working with existing maintainer): POSTPONED + [brunogirin] Document deploying django tutorial with juju: POSTPONED + [jorge] sync up with dev to evaluate/improve node.js (working with existing maintainer): POSTPONED [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 - [brunogirin] Django: INPROGRESS + [brunogirin] Develop principles for normalizing interfaces in like services: POSTPONED + [marcoceppi] Contact and work with PHP app devs (Zend and Symfony): POSTPONED + [brunogirin] JBOSS charm: POSTPONED + [marcoceppi] Mediawiki: POSTPONED + [brunogirin] Django: POSTPONED [a.rosales] MongoDB challenge: DONE [negronjl] MongoDB: DONE - [jorge] Postgresql: INPROGRESS - [robert-ayres] MySQL: INPROGRESS - [jorge] Node.js: INPROGRESS - [a.rosales] Node.js: INPROGRESS - [mark-mims] Rails: INPROGRESS + [jorge] Postgresql: POSTPONED + [robert-ayres] MySQL: POSTPONED + [jorge] Node.js: POSTPONED + [a.rosales] Node.js: POSTPONED + [mark-mims] Rails: POSTPONED [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
[Blueprint servercloud-q-juju-charm-unit-tests] Juju Charm Unit Tests
Blueprint changed by Antonio Rosales: Work items changed: Work items: documentation for unit tests: INPROGRESS write examples of unit tests on flag-bearing charms (example charm): DONE - [jimbaker] make 'jitsu run-tests' aware of error codes (Jitsu watch): INPROGRESS + [jimbaker] make 'jitsu run-tests' aware of error codes (Jitsu watch): POSTPONED [jimbaker] improve charmtester logging information: DONE [hazmat] charm proof testing: DONE keep everything green (ongoing task): DONE [mark-mims] make charmtester easier to use one-off by anyone: DONE [mark-mims] make charmtester whitelist: DONE extend charm tools to help generate tests: POSTPONED 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-r-juju-gui] Juju GUI
Blueprint changed by Antonio Rosales: Work items changed: Work items: [a.rosales] Public mailing list (weekly retrospectives, dev notes): DONE - [a.rosales] Nicer staging site url: TODO + [gary] Nicer staging site url: DONE -- Juju GUI https://blueprints.launchpad.net/ubuntu/+spec/servercloud-r-juju-gui -- 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 Antonio Rosales: Name: servercloud-1305-juju-charmstore-feedback-loops = servercloud-s-juju-charmstore-feedback-loops -- 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-charmstore-feedback-loops] Add User Feedback loops and Social Networking to Charm Store Charm Pages
Blueprint changed by Antonio Rosales: Whiteboard changed: + [USER STORIES] Benefits to charm developers - sarnold would like to know roughly how many people have deployed his charms (quantitative feedback) - would like to know roughly how many have upgraded the charm recently - can be a measure of user satisfaction/interest with a charm + + [ASSUMPTIONS] + [RISKS] + [IN SCOPE] + [OUT OF SCOPE] + [USER ACCEPTANCE] -- 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-docs] Improve Juju Documentation
Blueprint changed by Antonio Rosales: Name: servercloud-1303-juju-docs = servercloud-s-juju-docs -- 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 Antonio Rosales: Priority: Undefined = High -- 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-r-juju-charm-testing] Juju Charm Testing
Blueprint changed by Antonio Rosales: Whiteboard changed: Discussion: *Bug submission on charm failure. *Define a process around how charm maintainers respond to test failures and subsequent bugs. Can a user run a manual test and submit the test back to the bug report to update testing status to green. *Enable Autocharm tester to be more resilient against provider failures, and Jenkins usage. simulate provider failure, and be able to recover: $ juju ssh MACHINE sudo shutdown now * Define WIs to execute auto charm testing on Go. * Continuous Integration (also will help with gating on charm commits) * Juju Testing Blogging * Juju testing communication to Juju lists. * Work on integrating/fixing Charm runner (graph testing/ dependency/env set up testing). Add a Jenkins workflow to run a charm or a set of charms in the following LXC environments: -raring container on raring host -raring container on precise host -precise container on raring host -precise container on precise host Reference Links: *Charm Test Spec [html] https://juju.ubuntu.com/docs/charm-tests.html * Charm Test Spec [source] http://bazaar.launchpad.net/~juju/juju/docs/view/head:/source/charm-tests.rst * CharmTester Charm http://jujucharms.com/~mark-mims/oneiric/charmtester * Charm Runner: https://launchpad.net/charmrunner * Jenkins Charm Testing: https://jenkins.qa.ubuntu.com/view/Charms/ - --- User Stories --- - - --- Risks --- - - --- Test Plans --- - - --- Release Note --- - - --- Blog Post --- + [USER STORIES] + [ASSUMPTIONS] + [RISKS] + [IN SCOPE] + [OUT OF SCOPE] + [USER ACCEPTANCE] (Needs spec and WI definition) -[a.rosales; 12-DEC-2012] === UDS 1303 Notes === Pad: http://pad.ubuntu.com/uds-1303-servercloud-r-juju-charm-testing Question: Is there a way in meta-data to explicitly state provider support. - -Example: Ceph: Does cloud provider have block support - -More broadly stated does the cloud provider have the capabilities the charm needs - + -Example: Ceph: Does cloud provider have block support + -More broadly stated does the cloud provider have the capabilities the charm needs + Idea: - -In charm testing status be able to show that a charm failure can be a result of the provider not providing the needed capabilities, ie the Ceph charm fails on a provider because it does not support object store. - -Make interface usage more verbose in the charm description. - -Need a rule/spec on how a interface should be implemented - -Need to investigate possible enforment of interfaces - -**Have the testing framework iterate through the operational deployment requirments. - + -In charm testing status be able to show that a charm failure can be a result of the provider not providing the needed capabilities, ie the Ceph charm fails on a provider because it does not support object store. + -Make interface usage more verbose in the charm description. + -Need a rule/spec on how a interface should be implemented + -Need to investigate possible enforment of interfaces + -**Have the testing framework iterate through the operational deployment requirments. + Interfaces doc link broken: - -Example: http://jujucharms.com/interfaces/ceph-client Interface doc link broken: - https://juju.ubuntu.com/Interfaces/ceph-client -- broken + -Example: http://jujucharms.com/interfaces/ceph-client Interface doc link broken: + https://juju.ubuntu.com/Interfaces/ceph-client -- broken Meta-language testing (http://paste.ubuntu.com/5588570/): Lanugage suggestions: http://lettuce.it/ http://cukes.info/ -- Juju Charm Testing https://blueprints.launchpad.net/ubuntu/+spec/servercloud-r-juju-charm-testing -- 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 Antonio Rosales: 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 Local provider configuration OpenStack provider configuration EC2 provider configuration Rackspace New Providers Deploying a Charm Exposing A charm Implicit Relations Machine Constraints * User tutorial - rename to “Using Juju” (should be embeddedd per topic) Charms 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 Reference Guide Full table of all charm attributes Full table of all juju commands example: http://developer.android.com/reference/packages.html Glossary -appendix Operating Systems - appendix stuff Relation references - appendix stuff Evaluate for removal: -move- About juju - *move to juju.ubuntu.com. -delete- Frequently Asked Questions - DELETE THIS, link to autogenerated FAQ at AU. juju modules - remove Juju core specific Drafts - REMOVE. -content should be covered- Implementation details - (should be in reference guide for charm attributes) Commands to work with relation settings and membership (be sure to cover in charm author) Upgrades - both (be sure how to implement charm upgrade hooks are covered in charm author) Charm Upgrades (be sure to be covered in Charm Users: deployment) New relation-ids hook command -(should be covered in charm author) # 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 creating relations removing relations 1. [user] Service configuration/Lifecycle managment: Using the configuration.yaml juju set i. https://juju.ubuntu.com/docs/service-config.html 1.[user] Scaling services 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
[Blueprint servercloud-r-juju-charm-testing] Juju Charm Testing
Blueprint changed by Antonio Rosales: Whiteboard changed: Discussion: *Bug submission on charm failure. *Define a process around how charm maintainers respond to test failures and subsequent bugs. Can a user run a manual test and submit the test back to the bug report to update testing status to green. *Enable Autocharm tester to be more resilient against provider failures, and Jenkins usage. simulate provider failure, and be able to recover: $ juju ssh MACHINE sudo shutdown now * Define WIs to execute auto charm testing on Go. * Continuous Integration (also will help with gating on charm commits) * Juju Testing Blogging * Juju testing communication to Juju lists. * Work on integrating/fixing Charm runner (graph testing/ dependency/env set up testing). Add a Jenkins workflow to run a charm or a set of charms in the following LXC environments: -raring container on raring host -raring container on precise host -precise container on raring host -precise container on precise host Reference Links: *Charm Test Spec [html] https://juju.ubuntu.com/docs/charm-tests.html * Charm Test Spec [source] http://bazaar.launchpad.net/~juju/juju/docs/view/head:/source/charm-tests.rst * CharmTester Charm http://jujucharms.com/~mark-mims/oneiric/charmtester * Charm Runner: https://launchpad.net/charmrunner * Jenkins Charm Testing: https://jenkins.qa.ubuntu.com/view/Charms/ - [USER STORIES] + [USER STORIES] [ASSUMPTIONS] [RISKS] [IN SCOPE] [OUT OF SCOPE] [USER ACCEPTANCE] + [RELEASE NOTE/BLOG] (Needs spec and WI definition) -[a.rosales; 12-DEC-2012] === UDS 1303 Notes === Pad: http://pad.ubuntu.com/uds-1303-servercloud-r-juju-charm-testing Question: Is there a way in meta-data to explicitly state provider support. -Example: Ceph: Does cloud provider have block support -More broadly stated does the cloud provider have the capabilities the charm needs Idea: -In charm testing status be able to show that a charm failure can be a result of the provider not providing the needed capabilities, ie the Ceph charm fails on a provider because it does not support object store. -Make interface usage more verbose in the charm description. -Need a rule/spec on how a interface should be implemented -Need to investigate possible enforment of interfaces -**Have the testing framework iterate through the operational deployment requirments. Interfaces doc link broken: -Example: http://jujucharms.com/interfaces/ceph-client Interface doc link broken: https://juju.ubuntu.com/Interfaces/ceph-client -- broken Meta-language testing (http://paste.ubuntu.com/5588570/): Lanugage suggestions: http://lettuce.it/ http://cukes.info/ -- Juju Charm Testing https://blueprints.launchpad.net/ubuntu/+spec/servercloud-r-juju-charm-testing -- 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 Antonio Rosales: 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 Local provider configuration OpenStack provider configuration EC2 provider configuration Rackspace New Providers Deploying a Charm Exposing A charm Implicit Relations Machine Constraints * User tutorial - rename to “Using Juju” (should be embeddedd per topic) Charms 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 Reference Guide Full table of all charm attributes Full table of all juju commands example: http://developer.android.com/reference/packages.html Glossary -appendix Operating Systems - appendix stuff Relation references - appendix stuff Evaluate for removal: -move- About juju - *move to juju.ubuntu.com. -delete- Frequently Asked Questions - DELETE THIS, link to autogenerated FAQ at AU. juju modules - remove Juju core specific Drafts - REMOVE. -content should be covered- Implementation details - (should be in reference guide for charm attributes) Commands to work with relation settings and membership (be sure to cover in charm author) Upgrades - both (be sure how to implement charm upgrade hooks are covered in charm author) Charm Upgrades (be sure to be covered in Charm Users: deployment) New relation-ids hook command -(should be covered in charm author) # 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 creating relations removing relations 1. [user] Service configuration/Lifecycle managment: Using the configuration.yaml juju set i. https://juju.ubuntu.com/docs/service-config.html 1.[user] Scaling services 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
[Blueprint servercloud-s-juju-charmstore-feedback-loops] Add User Feedback loops and Social Networking to Charm Store Charm Pages
Blueprint changed by Antonio Rosales: Whiteboard changed: - [USER STORIES] + [USER STORIES] Benefits to charm developers - sarnold would like to know roughly how many people have deployed his charms (quantitative feedback) - would like to know roughly how many have upgraded the charm recently - can be a measure of user satisfaction/interest with a charm [ASSUMPTIONS] [RISKS] [IN SCOPE] [OUT OF SCOPE] [USER ACCEPTANCE] + [RELEASE NOTE/BLOG] -- 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 Antonio Rosales: Name: servercloud-1303-juju-contributor-onramp = servercloud-s-juju-contributor-onramp -- 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 Antonio Rosales: 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] + [ASSUMPTIONS] + [RISKS] + [IN SCOPE] + [OUT OF SCOPE] + [USER ACCEPTANCE] + [RELEASE NOTE/BLOG] -- 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 Antonio Rosales: Priority: Undefined = Medium -- 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-charmhelper2] Charm Helper 2 - Declarative Charming
Blueprint changed by Antonio Rosales:
Whiteboard changed:
- --- User Stories ---
-
- --- Risks ---
-
- --- Test Plans ---
-
- --- Release Note ---
-
- --- Blog Post ---
-
- (Needs spec and WI definition) -[a.rosales; 12-DEC-2012]
+ [USER STORIES]
+ [ASSUMPTIONS]
+ [RISKS]
+ [IN SCOPE]
+ [OUT OF SCOPE]
+ [USER ACCEPTANCE]
+ [RELEASE NOTE/BLOG]
--- UDS Discussion ---
We've learned a lot since the creation of charm helper. Debian packagers
took 7 iterations before boiling all of debhelper's goodness into a
declarative system. We can learn from them, and get there in our second
iteration.
Discussion:
Charm-helper is not easily discoverable, poorly documented, and not as
awesome as it could be.
dannf likes to write makefiles
sources list
config settings with meaning
want common things to go in a declarative charm
get rid of copied lib files/folder
Maintain charm-helper seperately from juju, calling it at the top of the hook
vs included in juju trunk
What happens during upgrade-charm or if a pakcage gets removed?
Juju can't help with leader election across units of a service, but
charm-helper could)
Work:
- describe how to handle lifecycle changes for packages in
charm-helper/packages (also thinkof: upgrade-charm)
- install packages
- debconf preseeding too
- templating and/or building config files with dotd/concat partials
(erb_template _and_ cheetah_template helpers)?
- remote_files
- deploy from {distro,ppa,upstream?} ?
- Manage config files (dynamic, static, etc)
- Sanitize relation settings (potential risk of SQL Ejection, highjacking,
terror)
- Plugin based for easy extension of charm-helper
- leader election (perhaps somewhere other than charmhelper)
- private files (SSL certs) ... no clue...
- Collaborate on files that no charm owns
--
Charm Helper 2 - Declarative Charming
https://blueprints.launchpad.net/ubuntu/+spec/servercloud-s-juju-charmhelper2
--
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-charm-testing] Juju Charm Testing
Blueprint changed by Antonio Rosales: Name: servercloud-r-juju-charm-testing = servercloud-s-juju-charm-testing -- Juju Charm Testing https://blueprints.launchpad.net/ubuntu/+spec/servercloud-s-juju-charm-testing -- 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-charmhelper2] Charm Helper 2 - Declarative Charming
Blueprint changed by Antonio Rosales: Assignee: Mark Mims = Marco Ceppi -- Charm Helper 2 - Declarative Charming https://blueprints.launchpad.net/ubuntu/+spec/servercloud-r-juju-charmhelper2 -- 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-charmhelper2] Charm Helper 2 - Declarative Charming
Blueprint changed by Antonio Rosales: Name: servercloud-r-juju-charmhelper2 = servercloud-s-juju-charmhelper2 -- Charm Helper 2 - Declarative Charming https://blueprints.launchpad.net/ubuntu/+spec/servercloud-s-juju-charmhelper2 -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Blueprint servercloud-q-juju-charm-best-practices] Juju Charm Best practices
Blueprint changed by Antonio Rosales: Work items changed: Work items: [jorge] Pick better example charms, flagbearer charms.: DONE - [jorge] Choose a single place for presenting flagbearer charms (charm browser?): TODO + [jorge] Choose a single place for presenting flagbearer charms (charm browser?): POSTPONED [jorge] Move rules and charm best practices into juju/docs.: DONE [jorge] Add Maintainer field information to documentation. (thanks clint!): DONE [jorge] Reach out to maintainers to get their maintainer field filled out.: DONE [jorge] Add docs work items to patch pilot!: DONE - [jorge] pull file bug or join the doc team from other projects: TODO + [jorge] pull file bug or join the doc team from other projects: POSTPONED [jorge] Clarify documentention on what to expect when your using LXC and EC2. Cost, wait time, what you see, logs, downloading. You should expect this to download 300 megs, etc. Here's a table of look here troubleshooting your LXC thing: DONE [imbrandon] Reach out to maintainers to get their maintainer filled out.: DONE - [imbrandon] Put Doc instructions in the docs: http://askubuntu.com/q/52063 : TODO + [imbrandon] Put Doc instructions in the docs: http://askubuntu.com/q/52063 : POSTPONED [mark-mims] (and individual maintainers!) clean up existing charms wrt best practices: DONE [clint-fewbar] Comment and add links to docs in 'charm create' templates: POSTPONED [clint-fewbar] juju in Debian! NOW!: DONE [clint-fewbar] determine most likely maintainers based on bzr logs: DONE [clint-fewbar] fix doc repos wrt (trunk, go, docs): DONE [marcoceppi] tag:juju review on AU and SE network: DONE [hazmat] incorporate output of charm proof into charm browser: DONE [hazmat] clear out trunk docs for juju: DONE - [imbrandon] Clarify documentention on what to expect when your using LXC and EC2. Cost, wait time, what you see, logs, downloading. You should expect this to download 300 megs, etc. Here's a table of look here troubleshooting your LXC thing.: TODO - [hazmat] make juju report on initial lxc image downloads ?: TODO - [clint-fewbar] make juju lxc use lxc networking instead of libvirt networking ?: INPROGRESS + [imbrandon] Clarify documentention on what to expect when your using LXC and EC2. Cost, wait time, what you see, logs, downloading. You should expect this to download 300 megs, etc. Here's a table of look here troubleshooting your LXC thing.: POSTPONED + [hazmat] make juju report on initial lxc image downloads ?: POSTPONED + [clint-fewbar] make juju lxc use lxc networking instead of libvirt networking ?: POSTPONED -- Juju Charm Best practices https://blueprints.launchpad.net/ubuntu/+spec/servercloud-q-juju-charm-best-practices -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Blueprint servercloud-s-openstack-havana] Openstack Next steps for S
Blueprint changed by Antonio Rosales: Whiteboard set to: [USER STORIES] [ASSUMPTIONS] [RISKS] [IN SCOPE] [OUT OF SCOPE] [USER ACCEPTANCE] [RELEASE NOTE/BLOG] -- Openstack Next steps for S https://blueprints.launchpad.net/ubuntu/+spec/servercloud-s-openstack-havana -- 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-openstack-havana] Openstack Next steps for S
Blueprint changed by Antonio Rosales: Assignee: (none) = Chuck Short -- Openstack Next steps for S https://blueprints.launchpad.net/ubuntu/+spec/servercloud-s-openstack-havana -- 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-openstack-havana] Openstack Next steps for S
Blueprint changed by Antonio Rosales: Approver: (none) = Dave Walker -- Openstack Next steps for S https://blueprints.launchpad.net/ubuntu/+spec/servercloud-s-openstack-havana -- 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-openstack-havana] Openstack Next steps for S
Blueprint changed by Antonio Rosales: Drafter: (none) = Ubuntu Server Team -- Openstack Next steps for S https://blueprints.launchpad.net/ubuntu/+spec/servercloud-s-openstack-havana -- 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-charm-testing] Juju Charm Testing
Blueprint changed by Antonio Rosales: Whiteboard changed: Discussion: *Bug submission on charm failure. *Define a process around how charm maintainers respond to test failures and subsequent bugs. Can a user run a manual test and submit the test back to the bug report to update testing status to green. *Enable Autocharm tester to be more resilient against provider failures, and Jenkins usage. simulate provider failure, and be able to recover: $ juju ssh MACHINE sudo shutdown now * Define WIs to execute auto charm testing on Go. * Continuous Integration (also will help with gating on charm commits) * Juju Testing Blogging * Juju testing communication to Juju lists. * Work on integrating/fixing Charm runner (graph testing/ dependency/env set up testing). Add a Jenkins workflow to run a charm or a set of charms in the following LXC environments: -raring container on raring host -raring container on precise host -precise container on raring host -precise container on precise host Reference Links: *Charm Test Spec [html] https://juju.ubuntu.com/docs/charm-tests.html * Charm Test Spec [source] http://bazaar.launchpad.net/~juju/juju/docs/view/head:/source/charm-tests.rst * CharmTester Charm http://jujucharms.com/~mark-mims/oneiric/charmtester * Charm Runner: https://launchpad.net/charmrunner * Jenkins Charm Testing: https://jenkins.qa.ubuntu.com/view/Charms/ [USER STORIES] [ASSUMPTIONS] [RISKS] [IN SCOPE] [OUT OF SCOPE] [USER ACCEPTANCE] [RELEASE NOTE/BLOG] (Needs spec and WI definition) -[a.rosales; 12-DEC-2012] === UDS 1303 Notes === Pad: http://pad.ubuntu.com/uds-1303-servercloud-r-juju-charm-testing Question: Is there a way in meta-data to explicitly state provider support. -Example: Ceph: Does cloud provider have block support -More broadly stated does the cloud provider have the capabilities the charm needs Idea: -In charm testing status be able to show that a charm failure can be a result of the provider not providing the needed capabilities, ie the Ceph charm fails on a provider because it does not support object store. -Make interface usage more verbose in the charm description. -Need a rule/spec on how a interface should be implemented -Need to investigate possible enforment of interfaces -**Have the testing framework iterate through the operational deployment requirments. Interfaces doc link broken: -Example: http://jujucharms.com/interfaces/ceph-client Interface doc link broken: https://juju.ubuntu.com/Interfaces/ceph-client -- broken Meta-language testing (http://paste.ubuntu.com/5588570/): Lanugage suggestions: http://lettuce.it/ http://cukes.info/ + + Charm-Runner integration: + - https://launchpad.net/juju-deployer + + Wrap Go/Py juju client status: + - https://launchpad.net/python-jujuclient -- Juju Charm Testing https://blueprints.launchpad.net/ubuntu/+spec/servercloud-s-juju-charm-testing -- 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-openstack-qa] Openstack qa
Blueprint changed by Antonio Rosales: Whiteboard set to: [USER STORIES] [ASSUMPTIONS] [RISKS] [IN SCOPE] [OUT OF SCOPE] [USER ACCEPTANCE] [RELEASE NOTE/BLOG] -- Openstack qa https://blueprints.launchpad.net/ubuntu/+spec/servercloud-s-openstack-qa -- 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-openstack-pkg] Openstack packaging for S
Blueprint changed by Antonio Rosales: Whiteboard set to: [USER STORIES] [ASSUMPTIONS] [RISKS] [IN SCOPE] [OUT OF SCOPE] [USER ACCEPTANCE] [RELEASE NOTE/BLOG] -- Openstack packaging for S https://blueprints.launchpad.net/ubuntu/+spec/servercloud-s-openstack-pkg -- 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-database-alternatives] Investigate alternatives to mysql
Blueprint changed by Antonio Rosales: Whiteboard set to: [USER STORIES] [ASSUMPTIONS] [RISKS] [IN SCOPE] [OUT OF SCOPE] [USER ACCEPTANCE] [RELEASE NOTE/BLOG] -- Investigate alternatives to mysql https://blueprints.launchpad.net/ubuntu/+spec/servercloud-s-database-alternatives -- 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-cloud-archive] Ubuntu Cloud Archive Status Check
Blueprint changed by Antonio Rosales: Whiteboard set to: [USER STORIES] [ASSUMPTIONS] [RISKS] [IN SCOPE] [OUT OF SCOPE] [USER ACCEPTANCE] [RELEASE NOTE/BLOG] -- Ubuntu Cloud Archive Status Check https://blueprints.launchpad.net/ubuntu/+spec/servercloud-s-cloud-archive -- 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-openstack-charms-ha-v2] HA Openstack Charms V2
Blueprint changed by Antonio Rosales: Drafter: (none) = Ubuntu Server Team -- HA Openstack Charms V2 https://blueprints.launchpad.net/ubuntu/+spec/servercloud-s-openstack-charms-ha-v2 -- 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-openstack-charms-ha-v2] HA Openstack Charms V2
Blueprint changed by Antonio Rosales: Whiteboard set to: [USER STORIES] [ASSUMPTIONS] [RISKS] [IN SCOPE] [OUT OF SCOPE] [USER ACCEPTANCE] [RELEASE NOTE/BLOG] -- HA Openstack Charms V2 https://blueprints.launchpad.net/ubuntu/+spec/servercloud-s-openstack-charms-ha-v2 -- 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-enterprise-testing] Enterprise Grade Level Testing
Blueprint changed by Antonio Rosales: Drafter: (none) = Ubuntu Server Team -- Enterprise Grade Level Testing https://blueprints.launchpad.net/ubuntu/+spec/servercloud-s-enterprise-testing -- 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-openstack-hypervisor] Openstack Hypervisors
Blueprint changed by Antonio Rosales: Whiteboard set to: [USER STORIES] [ASSUMPTIONS] [RISKS] [IN SCOPE] [OUT OF SCOPE] [USER ACCEPTANCE] [RELEASE NOTE/BLOG] -- Openstack Hypervisors https://blueprints.launchpad.net/ubuntu/+spec/servercloud-s-openstack-hypervisor -- 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-mariadb-support] Investigate Adding MariaDB Support to Ubuntu Server
Blueprint changed by Antonio Rosales: Whiteboard changed: - [USER STORIES] + [USER STORIES] [ASSUMPTIONS] - [RISKS] + [ + RISKS] + Currently proposed in Debian, however not complete: + http://lists.alioth.debian.org/pipermail/pkg-mysql-maint/2013-March/005598.html + [IN SCOPE] [OUT OF SCOPE] [USER ACCEPTANCE] [RELEASE NOTE/BLOG] -- Investigate Adding MariaDB Support to Ubuntu Server https://blueprints.launchpad.net/ubuntu/+spec/servercloud-s-mariadb-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-s-mariadb-support] Investigate Adding MariaDB Support to Ubuntu Server
Blueprint changed by Antonio Rosales: Whiteboard changed: [USER STORIES] [ASSUMPTIONS] - [ - RISKS] + + [RISKS] Currently proposed in Debian, however not complete: - http://lists.alioth.debian.org/pipermail/pkg-mysql-maint/2013-March/005598.html + http://lists.alioth.debian.org/pipermail/pkg-mysql-maint/2013-March/005598.html [IN SCOPE] [OUT OF SCOPE] [USER ACCEPTANCE] [RELEASE NOTE/BLOG] -- Investigate Adding MariaDB Support to Ubuntu Server https://blueprints.launchpad.net/ubuntu/+spec/servercloud-s-mariadb-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 s-cloud-ubuntu-server-cisco-cloud] Cisco Cloud Secret Sauce Charms
Blueprint changed by Antonio Rosales: Assignee: (none) = Kapil Thangavelu -- Cisco Cloud Secret Sauce Charms https://blueprints.launchpad.net/cdo-dev/+spec/s-cloud-ubuntu-server-cisco-cloud -- 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-mariadb-support] Investigate Adding MariaDB Support to Ubuntu Server
Blueprint changed by Antonio Rosales: Whiteboard changed: [USER STORIES] [ASSUMPTIONS] [RISKS] Currently proposed in Debian, however not complete: http://lists.alioth.debian.org/pipermail/pkg-mysql-maint/2013-March/005598.html [IN SCOPE] [OUT OF SCOPE] [USER ACCEPTANCE] [RELEASE NOTE/BLOG] + + [NOTES] + Initial comparision (needs review/updating): + https://wiki.ubuntu.com/ServerTeam/KnowledgeBase/FeatureComparison/MySQL -- Investigate Adding MariaDB Support to Ubuntu Server https://blueprints.launchpad.net/ubuntu/+spec/servercloud-s-mariadb-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-s-juju-charm-testing] Juju Charm Testing
Blueprint changed by Antonio Rosales: Whiteboard changed: Discussion: *Bug submission on charm failure. *Define a process around how charm maintainers respond to test failures and subsequent bugs. Can a user run a manual test and submit the test back to the bug report to update testing status to green. *Enable Autocharm tester to be more resilient against provider failures, and Jenkins usage. simulate provider failure, and be able to recover: $ juju ssh MACHINE sudo shutdown now * Define WIs to execute auto charm testing on Go. * Continuous Integration (also will help with gating on charm commits) * Juju Testing Blogging * Juju testing communication to Juju lists. * Work on integrating/fixing Charm runner (graph testing/ dependency/env set up testing). Add a Jenkins workflow to run a charm or a set of charms in the following LXC environments: -raring container on raring host -raring container on precise host -precise container on raring host -precise container on precise host + + Two modes of testing: + -Unit (does the charm start, and report ready) + -Workload (test the charms relations, and pushing data) Reference Links: *Charm Test Spec [html] https://juju.ubuntu.com/docs/charm-tests.html * Charm Test Spec [source] http://bazaar.launchpad.net/~juju/juju/docs/view/head:/source/charm-tests.rst * CharmTester Charm http://jujucharms.com/~mark-mims/oneiric/charmtester * Charm Runner: https://launchpad.net/charmrunner * Jenkins Charm Testing: https://jenkins.qa.ubuntu.com/view/Charms/ [USER STORIES] [ASSUMPTIONS] [RISKS] [IN SCOPE] [OUT OF SCOPE] [USER ACCEPTANCE] [RELEASE NOTE/BLOG] (Needs spec and WI definition) -[a.rosales; 12-DEC-2012] === UDS 1303 Notes === Pad: http://pad.ubuntu.com/uds-1303-servercloud-r-juju-charm-testing Question: Is there a way in meta-data to explicitly state provider support. -Example: Ceph: Does cloud provider have block support -More broadly stated does the cloud provider have the capabilities the charm needs Idea: -In charm testing status be able to show that a charm failure can be a result of the provider not providing the needed capabilities, ie the Ceph charm fails on a provider because it does not support object store. -Make interface usage more verbose in the charm description. -Need a rule/spec on how a interface should be implemented -Need to investigate possible enforment of interfaces -**Have the testing framework iterate through the operational deployment requirments. Interfaces doc link broken: -Example: http://jujucharms.com/interfaces/ceph-client Interface doc link broken: https://juju.ubuntu.com/Interfaces/ceph-client -- broken Meta-language testing (http://paste.ubuntu.com/5588570/): Lanugage suggestions: http://lettuce.it/ http://cukes.info/ Charm-Runner integration: - - https://launchpad.net/juju-deployer + - https://launchpad.net/juju-deployer Wrap Go/Py juju client status: - - https://launchpad.net/python-jujuclient + - https://launchpad.net/python-jujuclient -- Juju Charm Testing https://blueprints.launchpad.net/ubuntu/+spec/servercloud-s-juju-charm-testing -- 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 Antonio Rosales: Work items changed: - Work items for ubuntu-13.04-month-6: + 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.: DONE + [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 Antonio Rosales: 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 + [a.rosales] : Sync up with webops (mthaddon wedgwood) 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-docs] Improve Juju Documentation
Blueprint changed by Antonio Rosales: Work items changed: Work items for ubuntu-13.04-month-6: [evilnick] Define structural elements of HTML5 doc: DONE [evilnick] Create sample getting Started Guide: DONE [evilnick] Create list of screencasts: TODO - [jorge] Develop screen casts based on defined list: TODO + [jorge] Develop Webinar/Screen cast education series mapped to Docs. (ie 12 sessions from getting started to Debugging): 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 Antonio Rosales: Work items changed: - Work items for ubuntu-13.04-month-6: + 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 -- 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-charm-testing] Juju Charm Testing
Blueprint changed by Antonio Rosales: Work items set to: Work items: Integration Testing includes framework that charm authors can write tests against (embedded in the charm): TODO Jenkins testing on new merge proposal, on success it is a candidate for review: TODO Develop Juju test plugin (ie juju test): TODO Modify charm tools to capture a stub integration test: TODO Include charm-helper library for all charmers: TODO -- Juju Charm Testing https://blueprints.launchpad.net/ubuntu/+spec/servercloud-s-juju-charm-testing -- 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-cloud-init] Cloud Init Development for Saucy
Blueprint changed by Antonio Rosales: Whiteboard set to: [USER STORIES] [ASSUMPTIONS] [RISKS] [IN SCOPE] [OUT OF SCOPE] [USER ACCEPTANCE] [RELEASE NOTE/BLOG] [Notes] -- Cloud Init Development for Saucy https://blueprints.launchpad.net/ubuntu/+spec/servercloud-s-cloud-init -- 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 Antonio Rosales: 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 Local provider configuration OpenStack provider configuration EC2 provider configuration Rackspace New Providers Deploying a Charm Exposing A charm Implicit Relations Machine Constraints * User tutorial - rename to “Using Juju” (should be embeddedd per topic) Charms 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 Reference Guide Full table of all charm attributes Full table of all juju commands example: http://developer.android.com/reference/packages.html Glossary -appendix Operating Systems - appendix stuff Relation references - appendix stuff Evaluate for removal: -move- About juju - *move to juju.ubuntu.com. -delete- Frequently Asked Questions - DELETE THIS, link to autogenerated FAQ at AU. juju modules - remove Juju core specific Drafts - REMOVE. -content should be covered- Implementation details - (should be in reference guide for charm attributes) Commands to work with relation settings and membership (be sure to cover in charm author) Upgrades - both (be sure how to implement charm upgrade hooks are covered in charm author) Charm Upgrades (be sure to be covered in Charm Users: deployment) New relation-ids hook command -(should be covered in charm author) # 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 creating relations removing relations 1. [user] Service configuration/Lifecycle managment: Using the configuration.yaml juju set i. https://juju.ubuntu.com/docs/service-config.html 1.[user] Scaling services 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
[Blueprint servercloud-s-juju-docs] Improve Juju Documentation
Blueprint changed by Antonio Rosales: 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 + [marcoceppi] Auto-generate charm interfaces documentation: 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-mariadb-support] Investigate Adding MariaDB Support to Ubuntu Server
Blueprint changed by Antonio Rosales: Whiteboard changed: [USER STORIES] [ASSUMPTIONS] [RISKS] Currently proposed in Debian, however not complete: http://lists.alioth.debian.org/pipermail/pkg-mysql-maint/2013-March/005598.html [IN SCOPE] [OUT OF SCOPE] [USER ACCEPTANCE] [RELEASE NOTE/BLOG] [NOTES] Initial comparision (needs review/updating): https://wiki.ubuntu.com/ServerTeam/KnowledgeBase/FeatureComparison/MySQL https://bugs.launchpad.net/ubuntu/+bug/519478 Note: This Blueprints was obsoleted in reference to BP: - https://blueprints.launchpad.net/ubuntu/+spec/servercloud-s-mariadb- - support + https://blueprints.launchpad.net/ubuntu/+spec/servercloud-s-database- + alternatives -- Investigate Adding MariaDB Support to Ubuntu Server https://blueprints.launchpad.net/ubuntu/+spec/servercloud-s-mariadb-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-s-database-alternatives] Investigate alternatives to mysql
Blueprint changed by Antonio Rosales: Whiteboard changed: - [USER STORIES] + [USER STORIES] [ASSUMPTIONS] [RISKS] + For Maria DB: + Currently proposed in Debian, however not complete: + http://lists.alioth.debian.org/pipermail/pkg-mysql-maint/2013-March/005598.html + [IN SCOPE] [OUT OF SCOPE] [USER ACCEPTANCE] [RELEASE NOTE/BLOG] + [NOTES] + Initial comparision (needs review/updating): + https://wiki.ubuntu.com/ServerTeam/KnowledgeBase/FeatureComparison/MySQL + + https://bugs.launchpad.net/ubuntu/+bug/519478 -- Investigate alternatives to mysql https://blueprints.launchpad.net/ubuntu/+spec/servercloud-s-database-alternatives -- 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-cloud-images-lts-enablement] 12.04.x images with LTS Enablement Kernel
Blueprint changed by Antonio Rosales: Whiteboard changed: [USER STORIES] Bob likes Ceph. The ceph modules in 3.2 do not work as well as later kernel images. Alice likes btrfs. The btrfs kernel module in 3.2 do not have the latest features. She wants to stay on 12.04. [ASSUMPTIONS] [RISKS] - Kernel upgrade story at the end of the LTS kernel is nil. Users have to manually upgrade. [IN SCOPE] - Produce new cloud-images with LTS Enablement kernel [OUT OF SCOPE] [USER ACCEPTANCE] [RELEASE NOTE/BLOG] Ubuntu Cloud Images for 12.04.x are now being produced with the LTS-Enablement Kernel, in addition to the 3.2 seriies that orginially shipped with 12.04 LTS. The LTS-Enablement kernel allows those who need to run a newer kernel versions. - [CONCERNS] - [smoser] Adding yet another image [SUGGESTIONS] - [smoser] Enable rebundling images - [utemming] Enable cloud-init short-hand to do this automatically + + [NOTES] + 1305 vUDS Pad: http://pad.ubuntu.com/uds-1305-servercloud-s-cloud-images-lts-enablement -- 12.04.x images with LTS Enablement Kernel https://blueprints.launchpad.net/ubuntu/+spec/servercloud-s-cloud-images-lts-enablement -- 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-cloud-vagrant] Cloud-Init for Vagrant
Blueprint changed by Antonio Rosales: Whiteboard changed: - [USER STORIES] + [USER STORIES] [ASSUMPTIONS] [RISKS] [IN SCOPE] [OUT OF SCOPE] [USER ACCEPTANCE] [RELEASE NOTE/BLOG] - [Notes] + [NOTES] + vUDS 1305 Pad notes: http://pad.ubuntu.com/uds-1305-servercloud-s-cloud-vagrant -- Cloud-Init for Vagrant https://blueprints.launchpad.net/ubuntu/+spec/servercloud-s-cloud-vagrant -- 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-cloud-vagrant] Cloud-Init for Vagrant
Blueprint changed by Antonio Rosales: Work items set to: Work items: get dkms modules into Ubuntu: TODO cloud-init tooling: TODO get security input on getting dkms modules ack'ed: TODO vagrant provider for cloud-init : TODO -- Cloud-Init for Vagrant https://blueprints.launchpad.net/ubuntu/+spec/servercloud-s-cloud-vagrant -- 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-cloud-init] Cloud Init Cloud Image Development for Saucy
Blueprint changed by Antonio Rosales: Work items set to: Work items: [utlemming] cloud-init plugin development: TODO [utlemming] customize my image tool: TODO [smoser] investigate pre-cloud init phase: TODO [smoser] investigate vendore hook : TODO -- Cloud Init Cloud Image Development for Saucy https://blueprints.launchpad.net/ubuntu/+spec/servercloud-s-cloud-init -- 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-cloud-init] Cloud Init Cloud Image Development for Saucy
Blueprint changed by Antonio Rosales: Whiteboard changed: - [USER STORIES] + [USER STORIES] [ASSUMPTIONS] [RISKS] [IN SCOPE] [OUT OF SCOPE] [USER ACCEPTANCE] [RELEASE NOTE/BLOG] - [Notes] + + [NOTES] + vUDS Notes at: http://pad.ubuntu.com/uds-1305-servercloud-s-cloud-init -- Cloud Init Cloud Image Development for Saucy https://blueprints.launchpad.net/ubuntu/+spec/servercloud-s-cloud-init -- 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-cloud-init] Cloud Init Cloud Image Development for Saucy
Blueprint changed by Antonio Rosales: Assignee: Ubuntu Server Team = Ben Howard -- Cloud Init Cloud Image Development for Saucy https://blueprints.launchpad.net/ubuntu/+spec/servercloud-s-cloud-init -- 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-charmhelper2] Charm Development Tooling
Blueprint changed by Antonio Rosales: Work items changed: Work items: [marcoceppi] Consolidate existing forks/helper code bases: DONE Develop repos/organization structure of code base (modularize code): TODO Define distribution methods: TODO [marcoceppi] Update charm tools to promote best practices wrt stubbing/libraries WITH TESTS: TODO + [marcoceppi] sync up with james and adam when structuring lp:charm-helpers: TODO + [wedgwood] With help from marcoceppi, bac, adam_g, and james_page get core libraries ready: TODO -- Charm Development Tooling https://blueprints.launchpad.net/ubuntu/+spec/servercloud-s-juju-charmhelper2 -- 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-charmhelper2] Charm Development Tooling
Blueprint changed by Antonio Rosales:
Whiteboard changed:
[USER STORIES]
Rodrigo is a new charm writer and needs tools to solve problems other
authors have already solved in their charms.
Dora is a seasoned charmer that has common functions she wants to
publish and share with other authors
Ricardo has written charms before and wants to know what shared
functions are available for charms
Lucy is rewriting several hooks to another language and needs to know
what helpers exist in that language
Bruce wants to review what parameters a helper function accepts and what
the expected output is
[ASSUMPTIONS]
[RISKS]
- It'll be difficult for some functions to create a comperable cross-
language function
[IN SCOPE]
[OUT OF SCOPE]
[USER ACCEPTANCE]
[RELEASE NOTE/BLOG]
+ [NOTES]
+ vUDS 1304 Notes:
http://pad.ubuntu.com/uds-1305-servercloud-s-juju-charmhelper2
+
--- UDS Discussion ---
We've learned a lot since the creation of charm helper. Debian packagers
took 7 iterations before boiling all of debhelper's goodness into a
declarative system. We can learn from them, and get there in our second
iteration.
Discussion:
Charm-helper is not easily discoverable, poorly documented, and not as
awesome as it could be.
dannf likes to write makefiles
sources list
config settings with meaning
want common things to go in a declarative charm
get rid of copied lib files/folder
Maintain charm-helper seperately from juju, calling it at the top of the hook
vs included in juju trunk
What happens during upgrade-charm or if a pakcage gets removed?
Juju can't help with leader election across units of a service, but
charm-helper could)
Work:
- describe how to handle lifecycle changes for packages in
charm-helper/packages (also thinkof: upgrade-charm)
- install packages
- debconf preseeding too
- templating and/or building config files with dotd/concat partials
(erb_template _and_ cheetah_template helpers)?
- remote_files
- deploy from {distro,ppa,upstream?} ?
- Manage config files (dynamic, static, etc)
- Sanitize relation settings (potential risk of SQL Ejection, highjacking,
terror)
- Plugin based for easy extension of charm-helper
- leader election (perhaps somewhere other than charmhelper)
- private files (SSL certs) ... no clue...
- Collaborate on files that no charm owns
---
[notes from cloudsprint 2013-05]
- Wedgewood has “Charm Support” which is used in IS and online services charms
- - Python based library
- - Covers debian packaging
- -
- - Command line interface
- - Bash support via argparse
- - Has hook env for handling various hook specific items (nrpe, relation
data, etc)
- - Exec.d allows you to pre-seed stuff in to charm prior to deployment to
perform “pre-install” tasks
- - Handles items as exec.d/charm-pre-install in various hooks by invoking
the matching command
- - “Rudimentary” persistent storage support
- - Charm helpers doesn’t do what they wanted it to. Charm-helpers wasn’t a
known until after using charm support.
+ - Python based library
+ - Covers debian packaging
+ -
+ - Command line interface
+ - Bash support via argparse
+ - Has hook env for handling various hook specific items (nrpe, relation
data, etc)
+ - Exec.d allows you to pre-seed stuff in to charm prior to deployment to
perform “pre-install” tasks
+ - Handles items as exec.d/charm-pre-install in various hooks by invoking
the matching command
+ - “Rudimentary” persistent storage support
+ - Charm helpers doesn’t do what they wanted it to. Charm-helpers wasn’t a
known until after using charm support.
- OpenStack has “openstack-charm-helpers” which is used by the OpenStack
charms for deployment
- - Configuration/relation abstracting for easier python support
- - “Storage” management like charm-support
- - Conditional restart of services, mapping dicts to services to manage
restart of services
- - Caching of juju environment data, to speed up hook execution
- - Local file syncs between peers
- - Bi-directional file xfer between peers
- - Didn’t use it because: Primitive, moving too fast, and didn’t achieve
anything they needed at the time.
-- Current work: lp:~openstack-charmers/openstack-charm-helpers/ha-helpers
+ - Configuration/relation abstracting for easier python support
+ - “Storage” management like charm-support
+ - Conditional restart of services, mapping dicts to services to manage
restart of services
+ - Caching of juju environment data, to speed up hook execution
+ - Local file syncs between peers
+ - Bi-directional file xfer between peers
+ - Didn’t use it because: Primitive, moving too fast, and didn’t achieve
anything they needed at the time.
+ - Current work: lp:~openstack-charmers/openstack-charm-helpers/ha-helpers
Gary’s Ideas:
- - Python helpers of charm-helpers
- - Three levels
[Blueprint servercloud-s-juju-charmhelper2] Charm Development Tooling
Blueprint changed by Antonio Rosales: Work items changed: Work items: [marcoceppi] Consolidate existing forks/helper code bases: DONE Develop repos/organization structure of code base (modularize code): TODO Define distribution methods: TODO [marcoceppi] Update charm tools to promote best practices wrt stubbing/libraries WITH TESTS: TODO [marcoceppi] sync up with james and adam when structuring lp:charm-helpers: TODO [wedgwood] With help from marcoceppi, bac, adam_g, and james_page get core libraries ready: TODO + [marcoceppi] charm-tools: Do not auto-fill charm description from package in charm create.: TODO -- Charm Development Tooling https://blueprints.launchpad.net/ubuntu/+spec/servercloud-s-juju-charmhelper2 -- 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 Antonio Rosales: 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 Local provider configuration OpenStack provider configuration EC2 provider configuration Rackspace New Providers Deploying a Charm Exposing A charm Implicit Relations Machine Constraints * User tutorial - rename to “Using Juju” (should be embeddedd per topic) Charms 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 Reference Guide Full table of all charm attributes Full table of all juju commands example: http://developer.android.com/reference/packages.html Glossary -appendix Operating Systems - appendix stuff Relation references - appendix stuff Evaluate for removal: -move- About juju - *move to juju.ubuntu.com. -delete- Frequently Asked Questions - DELETE THIS, link to autogenerated FAQ at AU. juju modules - remove Juju core specific Drafts - REMOVE. -content should be covered- Implementation details - (should be in reference guide for charm attributes) Commands to work with relation settings and membership (be sure to cover in charm author) Upgrades - both (be sure how to implement charm upgrade hooks are covered in charm author) Charm Upgrades (be sure to be covered in Charm Users: deployment) New relation-ids hook command -(should be covered in charm author) # 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 creating relations removing relations 1. [user] Service configuration/Lifecycle managment: Using the configuration.yaml juju set i. https://juju.ubuntu.com/docs/service-config.html 1.[user] Scaling services 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
[Blueprint servercloud-s-juju-docs] Improve Juju Documentation
Blueprint changed by Antonio Rosales: 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 + [jorge] Migrate/Move documentation embedded in juju.ubuntu.com into juju.ubuntu.com/docs (getting started, and community).: TODO + [a.rosales] Get a beta site going for Juju docs.: TODO + [a.rosales] Get a permanent staging site for the docs: TODO + [jorge] Get UX testing on the docs: 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 Antonio Rosales: Assignee: (none) = Curtis Hovey -- 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-charmstore-feedback-loops] Add User Feedback loops and Social Networking to Charm Store Charm Pages
Blueprint changed by Antonio Rosales: Work items changed: Work items: [jorge] write templates for all the services: TODO [jcsackett] Implement the feature: TODO + [sinzui] Get clearification from design on displaying the number of +1, Likes, Tweets: TODO + [sinzui] Investigate adding a leave feedback fom for each charm that goes to the maintainer of the charm: 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-charmstore-feedback-loops] Add User Feedback loops and Social Networking to Charm Store Charm Pages
Blueprint changed by Antonio Rosales: Whiteboard changed: [USER STORIES] Benefits to charm developers - sarnold would like to know roughly how many people have deployed his charms (quantitative feedback) - would like to know roughly how many have upgraded the charm recently - can be a measure of user satisfaction/interest with a charm [ASSUMPTIONS] [RISKS] [IN SCOPE] [OUT OF SCOPE] [USER ACCEPTANCE] [RELEASE NOTE/BLOG] + + [NOTES] + vUDS 1305 notes: http://pad.ubuntu.com/uds-1305-servercloud-s-juju-charmstore-feedback-loops -- 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-charm-testing] Juju Charm Testing
Blueprint changed by Antonio Rosales: Whiteboard changed: Discussion: *Bug submission on charm failure. *Define a process around how charm maintainers respond to test failures and subsequent bugs. Can a user run a manual test and submit the test back to the bug report to update testing status to green. *Enable Autocharm tester to be more resilient against provider failures, and Jenkins usage. simulate provider failure, and be able to recover: $ juju ssh MACHINE sudo shutdown now * Define WIs to execute auto charm testing on Go. * Continuous Integration (also will help with gating on charm commits) * Juju Testing Blogging * Juju testing communication to Juju lists. * Work on integrating/fixing Charm runner (graph testing/ dependency/env set up testing). Add a Jenkins workflow to run a charm or a set of charms in the following LXC environments: -raring container on raring host -raring container on precise host -precise container on raring host -precise container on precise host Two modes of testing: -Unit (does the charm start, and report ready) -Workload (test the charms relations, and pushing data) Reference Links: *Charm Test Spec [html] https://juju.ubuntu.com/docs/charm-tests.html * Charm Test Spec [source] http://bazaar.launchpad.net/~juju/juju/docs/view/head:/source/charm-tests.rst * CharmTester Charm http://jujucharms.com/~mark-mims/oneiric/charmtester * Charm Runner: https://launchpad.net/charmrunner * Jenkins Charm Testing: https://jenkins.qa.ubuntu.com/view/Charms/ [USER STORIES] William is a juju user who wishes to know a charms current stability Saul is patching a charm and wants to in sure his changes are work with current tests Laura is a charm maintainer and wants to add tests to in sure her charm is stable Kara is a charm maintainer and needs to know when her charm is broken Lee is a charmer who, while reviewing charm submissions, needs to know if these changes break backwards compatibility with currently deployed services Gaius is a charm maintainer from an upstream project and needs an easy way to learn how to write tests for his charm [ASSUMPTIONS] - Charm tester/charm tester control will work with gojuju for at least graph testing [RISKS] - Relying soley on graph testing may result in inaccurate test results due to lack of embedded tests - Making tests too complicated may result in low adoption rate of embedded testing [IN SCOPE] [OUT OF SCOPE] [USER ACCEPTANCE] [RELEASE NOTE/BLOG] - (Needs spec and WI definition) -[a.rosales; 12-DEC-2012] + [Notes] + + UDS 1305 notes: http://pad.ubuntu.com/ep/pad/view/uds-1305-servercloud-s + -juju-charm-testing/latest === UDS 1303 Notes === Pad: http://pad.ubuntu.com/uds-1303-servercloud-r-juju-charm-testing Question: Is there a way in meta-data to explicitly state provider support. -Example: Ceph: Does cloud provider have block support -More broadly stated does the cloud provider have the capabilities the charm needs Idea: -In charm testing status be able to show that a charm failure can be a result of the provider not providing the needed capabilities, ie the Ceph charm fails on a provider because it does not support object store. -Make interface usage more verbose in the charm description. -Need a rule/spec on how a interface should be implemented -Need to investigate possible enforment of interfaces -**Have the testing framework iterate through the operational deployment requirments. Interfaces doc link broken: -Example: http://jujucharms.com/interfaces/ceph-client Interface doc link broken: https://juju.ubuntu.com/Interfaces/ceph-client -- broken Meta-language testing (http://paste.ubuntu.com/5588570/): Lanugage suggestions: http://lettuce.it/ http://cukes.info/ Charm-Runner integration: - https://launchpad.net/juju-deployer Wrap Go/Py juju client status: - https://launchpad.net/python-jujuclient - --- [notes from cloudsprint 2013-05] Topics to cover Current Testing Current todos Experiences from IS Ideas Review charm policy to include: Test must pass tests Charm must have tests We want embedded tests! All tests live in the charm Functional Tests /test (in charm) Integration /test.d (in charm) How to make it low entry for charmers to add tests charm create tests (charm-tools make a stub _simple_ test) leverage libraries, and possibly a deployment (dare I say declarative) testing lang. Sidnei mocks all the juju calls (U1 testing) have a library that stubs this for you. pull this into charm-helper library leverage Go-watch leverage charm testing with charm upgrade Story Points: (added to Blueprint work item) Integration Testing includes framework that charm authors can write tests against
[Blueprint servercloud-s-juju-charm-testing] Juju Charm Testing
Blueprint changed by Antonio Rosales: Whiteboard changed: Discussion: *Bug submission on charm failure. *Define a process around how charm maintainers respond to test failures and subsequent bugs. Can a user run a manual test and submit the test back to the bug report to update testing status to green. *Enable Autocharm tester to be more resilient against provider failures, and Jenkins usage. simulate provider failure, and be able to recover: $ juju ssh MACHINE sudo shutdown now * Define WIs to execute auto charm testing on Go. * Continuous Integration (also will help with gating on charm commits) * Juju Testing Blogging * Juju testing communication to Juju lists. * Work on integrating/fixing Charm runner (graph testing/ dependency/env set up testing). Add a Jenkins workflow to run a charm or a set of charms in the following LXC environments: -raring container on raring host -raring container on precise host -precise container on raring host -precise container on precise host Two modes of testing: -Unit (does the charm start, and report ready) -Workload (test the charms relations, and pushing data) Reference Links: *Charm Test Spec [html] https://juju.ubuntu.com/docs/charm-tests.html * Charm Test Spec [source] http://bazaar.launchpad.net/~juju/juju/docs/view/head:/source/charm-tests.rst * CharmTester Charm http://jujucharms.com/~mark-mims/oneiric/charmtester * Charm Runner: https://launchpad.net/charmrunner * Jenkins Charm Testing: https://jenkins.qa.ubuntu.com/view/Charms/ [USER STORIES] William is a juju user who wishes to know a charms current stability Saul is patching a charm and wants to in sure his changes are work with current tests Laura is a charm maintainer and wants to add tests to in sure her charm is stable Kara is a charm maintainer and needs to know when her charm is broken Lee is a charmer who, while reviewing charm submissions, needs to know if these changes break backwards compatibility with currently deployed services Gaius is a charm maintainer from an upstream project and needs an easy way to learn how to write tests for his charm [ASSUMPTIONS] - Charm tester/charm tester control will work with gojuju for at least graph testing [RISKS] - Relying soley on graph testing may result in inaccurate test results due to lack of embedded tests - Making tests too complicated may result in low adoption rate of embedded testing [IN SCOPE] [OUT OF SCOPE] [USER ACCEPTANCE] [RELEASE NOTE/BLOG] - [Notes] + [NOTES] UDS 1305 notes: http://pad.ubuntu.com/ep/pad/view/uds-1305-servercloud-s -juju-charm-testing/latest === UDS 1303 Notes === Pad: http://pad.ubuntu.com/uds-1303-servercloud-r-juju-charm-testing Question: Is there a way in meta-data to explicitly state provider support. -Example: Ceph: Does cloud provider have block support -More broadly stated does the cloud provider have the capabilities the charm needs Idea: -In charm testing status be able to show that a charm failure can be a result of the provider not providing the needed capabilities, ie the Ceph charm fails on a provider because it does not support object store. -Make interface usage more verbose in the charm description. -Need a rule/spec on how a interface should be implemented -Need to investigate possible enforment of interfaces -**Have the testing framework iterate through the operational deployment requirments. Interfaces doc link broken: -Example: http://jujucharms.com/interfaces/ceph-client Interface doc link broken: https://juju.ubuntu.com/Interfaces/ceph-client -- broken Meta-language testing (http://paste.ubuntu.com/5588570/): Lanugage suggestions: http://lettuce.it/ http://cukes.info/ Charm-Runner integration: - https://launchpad.net/juju-deployer Wrap Go/Py juju client status: - https://launchpad.net/python-jujuclient --- [notes from cloudsprint 2013-05] Topics to cover Current Testing Current todos Experiences from IS Ideas Review charm policy to include: Test must pass tests Charm must have tests We want embedded tests! All tests live in the charm Functional Tests /test (in charm) Integration /test.d (in charm) How to make it low entry for charmers to add tests charm create tests (charm-tools make a stub _simple_ test) leverage libraries, and possibly a deployment (dare I say declarative) testing lang. Sidnei mocks all the juju calls (U1 testing) have a library that stubs this for you. pull this into charm-helper library leverage Go-watch leverage charm testing with charm upgrade -- Juju Charm Testing https://blueprints.launchpad.net/ubuntu/+spec/servercloud-s-juju-charm-testing -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings
[Blueprint servercloud-s-juju-charm-testing] Juju Charm Testing
Blueprint changed by Antonio Rosales: Whiteboard changed: Discussion: *Bug submission on charm failure. *Define a process around how charm maintainers respond to test failures and subsequent bugs. Can a user run a manual test and submit the test back to the bug report to update testing status to green. *Enable Autocharm tester to be more resilient against provider failures, and Jenkins usage. simulate provider failure, and be able to recover: $ juju ssh MACHINE sudo shutdown now * Define WIs to execute auto charm testing on Go. * Continuous Integration (also will help with gating on charm commits) * Juju Testing Blogging * Juju testing communication to Juju lists. * Work on integrating/fixing Charm runner (graph testing/ dependency/env set up testing). Add a Jenkins workflow to run a charm or a set of charms in the following LXC environments: -raring container on raring host -raring container on precise host -precise container on raring host -precise container on precise host Two modes of testing: -Unit (does the charm start, and report ready) -Workload (test the charms relations, and pushing data) Reference Links: *Charm Test Spec [html] https://juju.ubuntu.com/docs/charm-tests.html * Charm Test Spec [source] http://bazaar.launchpad.net/~juju/juju/docs/view/head:/source/charm-tests.rst * CharmTester Charm http://jujucharms.com/~mark-mims/oneiric/charmtester * Charm Runner: https://launchpad.net/charmrunner * Jenkins Charm Testing: https://jenkins.qa.ubuntu.com/view/Charms/ [USER STORIES] William is a juju user who wishes to know a charms current stability Saul is patching a charm and wants to in sure his changes are work with current tests Laura is a charm maintainer and wants to add tests to in sure her charm is stable Kara is a charm maintainer and needs to know when her charm is broken Lee is a charmer who, while reviewing charm submissions, needs to know if these changes break backwards compatibility with currently deployed services Gaius is a charm maintainer from an upstream project and needs an easy way to learn how to write tests for his charm [ASSUMPTIONS] - Charm tester/charm tester control will work with gojuju for at least graph testing [RISKS] - Relying soley on graph testing may result in inaccurate test results due to lack of embedded tests - Making tests too complicated may result in low adoption rate of embedded testing [IN SCOPE] [OUT OF SCOPE] [USER ACCEPTANCE] [RELEASE NOTE/BLOG] [Notes] UDS 1305 notes: http://pad.ubuntu.com/ep/pad/view/uds-1305-servercloud-s -juju-charm-testing/latest === UDS 1303 Notes === Pad: http://pad.ubuntu.com/uds-1303-servercloud-r-juju-charm-testing Question: Is there a way in meta-data to explicitly state provider support. -Example: Ceph: Does cloud provider have block support -More broadly stated does the cloud provider have the capabilities the charm needs Idea: -In charm testing status be able to show that a charm failure can be a result of the provider not providing the needed capabilities, ie the Ceph charm fails on a provider because it does not support object store. -Make interface usage more verbose in the charm description. -Need a rule/spec on how a interface should be implemented -Need to investigate possible enforment of interfaces -**Have the testing framework iterate through the operational deployment requirments. Interfaces doc link broken: -Example: http://jujucharms.com/interfaces/ceph-client Interface doc link broken: https://juju.ubuntu.com/Interfaces/ceph-client -- broken Meta-language testing (http://paste.ubuntu.com/5588570/): Lanugage suggestions: http://lettuce.it/ http://cukes.info/ Charm-Runner integration: - https://launchpad.net/juju-deployer Wrap Go/Py juju client status: - https://launchpad.net/python-jujuclient --- [notes from cloudsprint 2013-05] Topics to cover Current Testing Current todos Experiences from IS Ideas Review charm policy to include: Test must pass tests Charm must have tests We want embedded tests! All tests live in the charm Functional Tests /test (in charm) Integration /test.d (in charm) How to make it low entry for charmers to add tests charm create tests (charm-tools make a stub _simple_ test) leverage libraries, and possibly a deployment (dare I say declarative) testing lang. Sidnei mocks all the juju calls (U1 testing) have a library that stubs this for you. pull this into charm-helper library leverage Go-watch leverage charm testing with charm upgrade - - Story Points: (added to Blueprint work item) - Integration Testing includes framework that charm authors can write tests against (embedded in the charm). - Jenkins testing on new merge proposal
[Blueprint servercloud-s-juju-contributor-onramp] Juju Contributor Onramp
Blueprint changed by Antonio Rosales: 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-charmhelper2] Charm Development Tooling
Blueprint changed by Antonio Rosales: Work items changed: Work items: [marcoceppi] Consolidate existing forks/helper code bases: DONE Develop repos/organization structure of code base (modularize code): TODO Define distribution methods: TODO [marcoceppi] Update charm tools to promote best practices wrt stubbing/libraries WITH TESTS: TODO [marcoceppi] sync up with james and adam when structuring lp:charm-helpers: TODO [wedgwood] With help from marcoceppi, bac, adam_g, and james_page get core libraries ready: TODO [marcoceppi] charm-tools: Do not auto-fill charm description from package in charm create.: TODO + Shell out language specific commands: TODO -- Charm Development Tooling https://blueprints.launchpad.net/ubuntu/+spec/servercloud-s-juju-charmhelper2 -- 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 Antonio Rosales: Assignee: (none) = Jorge O. Castro -- 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 topic-saucy-servercloud-overview] Overview of Ubuntu Server Saucy Blueprints
Blueprint changed by Antonio Rosales: Definition Status: New = Approved -- Overview of Ubuntu Server Saucy Blueprints https://blueprints.launchpad.net/ubuntu/+spec/topic-saucy-servercloud-overview -- 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 topic-saucy-servercloud-overview] Overview of Ubuntu Server Saucy Blueprints
Blueprint changed by Antonio Rosales: Priority: Undefined = Low -- Overview of Ubuntu Server Saucy Blueprints https://blueprints.launchpad.net/ubuntu/+spec/topic-saucy-servercloud-overview -- 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 Antonio Rosales: Approver: Antonio Rosales = Gary Poster -- Add User Feedback loops and Social Networking to Charm Store Charm Pages https://blueprints.launchpad.net/juju-gui/+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-charmstore-feedback-loops] Add User Feedback loops and Social Networking to Charm Store Charm Pages
Blueprint changed by Antonio Rosales: Assignee: Jorge O. Castro = Cloud Engineering Orange Squad -- Add User Feedback loops and Social Networking to Charm Store Charm Pages https://blueprints.launchpad.net/juju-gui/+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 topic-s-servercloud-overview] Overview of Ubuntu Server Saucy Blueprints
Blueprint changed by Antonio Rosales: Name: topic-saucy-servercloud-overview = topic-s-servercloud-overview -- Overview of Ubuntu Server Saucy Blueprints https://blueprints.launchpad.net/ubuntu/+spec/topic-s-servercloud-overview -- 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
