[Bug 1546776] Re: [FFe] charm-tools 2.0
theblues is licensed LGPLv3 just had upstream sort this: https://github.com/juju/theblues/blob/develop/LICENSE -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to charm-tools in Ubuntu. https://bugs.launchpad.net/bugs/1546776 Title: [FFe] charm-tools 2.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/charm-tools/+bug/1546776/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1547115] [NEW] [FFe] charm 1.0
Public bug reported: A new charm command is being created to accompany charm-tools 2.0 and Juju 2.0 - this new command will install /usr/bin/charm (previously managed by charm-tools 1.0.0 so this command will break charm-tools 1.0.0 and suggest charm-tools 2.0 (where charm-tools 2.0 will depend on this charm command. Since this is a new package not yet in the archive, and it's dependent on changes in the Juju 2.0 FFe we request a Freeze Exception for this package as we wait for Juju and charm-tools to be uploaded as well. This tool adds: * Ability to publish charms to the charm store without needing a dvcs * A charmstore compatible search and query lookup * Managing a users assets in the Juju charm store ** Affects: ubuntu Importance: Undecided Status: New ** Package changed: charm-tools (Ubuntu) => ubuntu -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to charm-tools in Ubuntu. https://bugs.launchpad.net/bugs/1547115 Title: [FFe] charm 1.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1547115/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1546776] [NEW] [FFe] charm-tools 2.0
Public bug reported: With the release of Juju 2.0 a new charm-tools is planned to be released with this. charm-tools 2.0 is a huge jump in features from the 1.0.0 in the archive. It also becomes a suite of plugins to the new charm command being developed in Juju 2.0 - In general it brings about bug fixes and a new set of commands: * Ability to build charm using layers * Enhanced charm proof * Support for creating Windows charms * Removal of antiquated and broken commands Because charm-tools relies on the new `charm` command being added, which is dependent on Juju 2.0 (which has a FFe) this needs to be held until the new Juju 2.0 and Charm command is released. https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1545913 ** Affects: charm-tools (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to charm-tools in Ubuntu. https://bugs.launchpad.net/bugs/1546776 Title: [FFe] charm-tools 2.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/charm-tools/+bug/1546776/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 802117] Re: juju ssh/scp commands cause spurious key errors
** Changed in: amulet Milestone: 1.10.0 = 1.11.0 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju in Ubuntu. https://bugs.launchpad.net/bugs/802117 Title: juju ssh/scp commands cause spurious key errors To manage notifications about this bug go to: https://bugs.launchpad.net/amulet/+bug/802117/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 802117] Re: juju ssh/scp commands cause spurious key errors
** Changed in: amulet Milestone: None = 1.10.0 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju in Ubuntu. https://bugs.launchpad.net/bugs/802117 Title: juju ssh/scp commands cause spurious key errors To manage notifications about this bug go to: https://bugs.launchpad.net/amulet/+bug/802117/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 802117] Re: juju ssh/scp commands cause spurious key errors
** Changed in: amulet Status: New = Triaged ** Changed in: amulet Importance: Undecided = High -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju in Ubuntu. https://bugs.launchpad.net/bugs/802117 Title: juju ssh/scp commands cause spurious key errors To manage notifications about this bug go to: https://bugs.launchpad.net/amulet/+bug/802117/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 802117] Re: juju ssh/scp commands cause spurious key errors
** Tags added: charmers -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju in Ubuntu. https://bugs.launchpad.net/bugs/802117 Title: juju ssh/scp commands cause spurious key errors To manage notifications about this bug go to: https://bugs.launchpad.net/amulet/+bug/802117/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1380076] Re: Can't suspend on Surface Pro 3
What couple of lines of bash would fix this with regards to pm-utils? -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to pm-utils in Ubuntu. https://bugs.launchpad.net/bugs/1380076 Title: Can't suspend on Surface Pro 3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1380076/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1182905] Re: charm-tools installs juju-0.7
** Changed in: charm-tools (Ubuntu Precise) Status: Triaged = Fix Committed ** Changed in: charm-tools (Ubuntu Precise) Assignee: (unassigned) = Marco Ceppi (marcoceppi) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to charm-tools in Ubuntu. https://bugs.launchpad.net/bugs/1182905 Title: charm-tools installs juju-0.7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/charm-tools/+bug/1182905/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1182905] Re: charm-tools installs juju-0.7
** Description changed: This is what happened to me: - * Configured environments.yaml for AWS. - * I bootstrapped Juju, deployed wordpress and mysql and related them. I exposed wordpress and hit it in the browser. It worked. Woo! - * While doing this I decided to install charm-tools - * Now when I use Juju it errors requiring me to configure additional parts of environments.yaml + * Configured environments.yaml for AWS. + * I bootstrapped Juju, deployed wordpress and mysql and related them. I exposed wordpress and hit it in the browser. It worked. Woo! + * While doing this I decided to install charm-tools + * Now when I use Juju it errors requiring me to configure additional parts of environments.yaml Now, at first it only required me to configure a default-series for each provider, which is a no-brainer, but then it asked for maas-oauth config. This completely stopped me in my tracks. I don't care about the other providers as I have already got my AWS provider configured and up and running, and it put Juju in a position where it stopped working for me due to the missing configuration. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: charm-tools 0.3+151-0ubuntu1 ProcVersionSignature: Ubuntu 3.9.0-2.6-generic 3.9.2 Uname: Linux 3.9.0-2-generic i686 ApportVersion: 2.10.1-0ubuntu1 Architecture: i386 Date: Wed May 22 06:49:59 2013 InstallationDate: Installed on 2013-05-05 (17 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Alpha i386 (20130504) MarkForUpload: True PackageArchitecture: all SourcePackage: charm-tools UpgradeStatus: No upgrade log present (probably fresh install) + + [Impact] + + * Users who install juju-core, then install charm-tools will have their installations broken in precise + * This fix decouples juju from charm-tools as a Recommended package to a Suggested package. This also makes juju-core package a satisfactory Suggestion in addition to juju + + [Test Case] + + * On precise, install juju-core and juju-local using the preferred installation method, from cloud-tools pocket archive. + * Run `juju init` to create environments.yaml + * Switch to local environment, `juju switch local` + * Verify version of juju installed, `juju version` + * Bootstrap with `sudo juju bootstrap` + * Deploy a charm, `juju deploy ubuntu` + * Install charm-tools package from precise archives + * Run `juju version`, command should fail. + * Run `juju --version`, command should succeed with a verion 1.0.0 + * Attempt to connect to environment with `juju status`, should fail + + [Regression Potential] + + * This simply changes the the control file to lower priority of + Recommended packages. + + [Other Info] + + * This has been patched and updated in Saucy and Trusty as of version 1.0.0 of charm-tools. However, 1.0.0 breaks backwards compatibility with 0.3 packaging wise. charm-helper-sh and charm-helper-python are no longer supported and subsequently dropped from 1.0.0 version of charm-tools and it's packaging. Otherwise I likely would have requested a backport of 1.0.0 to precise. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to charm-tools in Ubuntu. https://bugs.launchpad.net/bugs/1182905 Title: charm-tools installs juju-0.7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/charm-tools/+bug/1182905/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1234627] Re: python dependencies missing: markdown and distribute
*** This bug is a duplicate of bug 1231441 *** https://bugs.launchpad.net/bugs/1231441 ** This bug has been marked a duplicate of bug 1231441 python-markdown missing in the deb packacge's dependencies -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to charm-tools in Ubuntu. https://bugs.launchpad.net/bugs/1234627 Title: python dependencies missing: markdown and distribute To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/charm-tools/+bug/1234627/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1231441] Re: python-markdown missing in the deb packacge's dependencies
** Changed in: charm-tools Status: In Progress = Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to charm-tools in Ubuntu. https://bugs.launchpad.net/bugs/1231441 Title: python-markdown missing in the deb packacge's dependencies To manage notifications about this bug go to: https://bugs.launchpad.net/charm-tools/+bug/1231441/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1098634] Re: incorrect bzr invocation on certain charm gets
** Changed in: charm-tools Status: Triaged = Fix Committed ** Changed in: charm-tools Assignee: (unassigned) = Marco Ceppi (marcoceppi) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju in Ubuntu. https://bugs.launchpad.net/bugs/1098634 Title: incorrect bzr invocation on certain charm gets To manage notifications about this bug go to: https://bugs.launchpad.net/charm-tools/+bug/1098634/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1098634] Re: incorrect bzr invocation on certain charm gets
** Changed in: charm-tools Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju in Ubuntu. https://bugs.launchpad.net/bugs/1098634 Title: incorrect bzr invocation on certain charm gets To manage notifications about this bug go to: https://bugs.launchpad.net/charm-tools/+bug/1098634/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 955070] Re: charm getall stderr output
Marking this as won't fix, since it's not longer valid with the current code of charm-tools ** Changed in: charm-tools Status: New = Won't Fix -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to charm-tools in Ubuntu. https://bugs.launchpad.net/bugs/955070 Title: charm getall stderr output To manage notifications about this bug go to: https://bugs.launchpad.net/charm-tools/+bug/955070/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1098634] Re: incorrect bzr invocation on certain charm gets
** Changed in: juju (Ubuntu) Status: Confirmed = Invalid ** Changed in: charm-tools Status: New = Triaged ** Changed in: charm-tools Importance: Undecided = High ** Changed in: charm-tools Milestone: None = 1.0 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju in Ubuntu. https://bugs.launchpad.net/bugs/1098634 Title: incorrect bzr invocation on certain charm gets To manage notifications about this bug go to: https://bugs.launchpad.net/charm-tools/+bug/1098634/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Blueprint servercloud-s-juju-charmhelper2] Charm Development Tooling
Blueprint changed by Marco Ceppi: 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 + Develop repos/organization structure of code base (modularize code): DONE + Define distribution methods: DONE [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 + [marcoceppi] sync up with james and adam when structuring lp:charm-helpers: DONE + [wedgwood] With help from marcoceppi, bac, adam_g, and james_page get core libraries ready: DONE + [marcoceppi] charm-tools: Do not auto-fill charm description from package in charm create.: DONE + Shell out language specific commands: DONE -- 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-charm-testing] Juju Charm Testing
Blueprint changed by Marco Ceppi: Work items changed: Work items: [marcoceppi] Integration Testing includes framework that charm authors can write tests against (embedded in the charm) (amulet): INPROGRESS [marcoceppi] Jenkins testing on new merge proposal, on success it is a candidate for review: POSTPONED [marcoceppi] Develop Juju test plugin (ie juju test): DONE [marcoceppi] Modify charm tools to capture a stub integration test: INPROGRESS - Include charm-helper library for all charmers: TODO + Include charm-helper library for all charmers: DONE -- 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-charm-testing] Juju Charm Testing
Blueprint changed by Marco Ceppi: Work items changed: Work items: [marcoceppi] Integration Testing includes framework that charm authors can write tests against (embedded in the charm) (amulet): INPROGRESS - [marcoceppi] Jenkins testing on new merge proposal, on success it is a candidate for review: TODO + [marcoceppi] Jenkins testing on new merge proposal, on success it is a candidate for review: POSTPONED [marcoceppi] Develop Juju test plugin (ie juju test): DONE [marcoceppi] Modify charm tools to capture a stub integration test: INPROGRESS 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-juju-contributor-onramp] Juju Contributor Onramp
Blueprint changed by Marco Ceppi: 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 + + vUDS 1308 Notes: http://pad.ubuntu.com/uds-1308-servercloud-s-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) [USER STORIES] James is a sysadmin at a company and is interested in getting his charms into the store for convenience/peer review. He's got some internal stuff that he can keep seperate, but he doesn't want to maintain boring infrastructure charms on his own. Kirk is deploying a charm but finds that it's missing a feature or needs a bugfix and he thinks he knows how to fix it. Robert is a developer at a company who works on a database that is charmed up, he notices that the charm needs improvement to follow his project's recommended best practice, but isn't sure how to claim ownership of a charm. Lars is used to github and is totally confused on how to get charms he's interested in. Cliff submitted a fix to a charm two weeks ago and has no idea how to get someone to get his fix in. [ASSUMPTIONS] - Mims/Castro want to mirror how OpenStack does reviews and code contributions as well as their usage of LP Blueprints. [RISKS] - There's only so much simplification that can happen when it comes to submitting code. - Poor response time leads people to believe that we don't want to help them. - Workflow ties into the store, so we need to be careful on how we simplify this. [IN SCOPE] - Refining workflow for submission - Measuring contributor metrics and enforcing a fast response time. [OUT OF SCOPE] [USER ACCEPTANCE] [RELEASE NOTE/BLOG] - We've made it easier than ever to contribute to charms with a new submission workflow. [notes from cloudsprint 2013-05] Low hanging fruit Docs! Big issue to getting new contributors Instructional videos will be a big help to resolving “How do I get going” for new people “Contribute to this charm” on jujucharms.com Better charm tools to help contributors (charm-helpers, charm-tools, charmsupport) NO LOCAL PROVIDER FOR JUJU-CORE Inhibitor for WebOps, charmers, community, and basically everyone -- 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-charm-testing] Juju Charm Testing
Blueprint changed by Marco Ceppi: Work items changed: 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 + [marcoceppi] Integration Testing includes framework that charm authors can write tests against (embedded in the charm) (amulet): INPROGRESS + [marcoceppi] Jenkins testing on new merge proposal, on success it is a candidate for review: TODO + [marcoceppi] Develop Juju test plugin (ie juju test): DONE + [marcoceppi] Modify charm tools to capture a stub integration test: INPROGRESS 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-juju-docs] Improve Juju Documentation
Blueprint changed by Marco Ceppi: 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] Prepare rollout strategy for new docs launch: DONE [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
[Bug 1182905] Re: charm-tools requires extra environments.yaml config
** Changed in: charm-tools (Ubuntu) Status: Confirmed = Fix Committed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to charm-tools in Ubuntu. https://bugs.launchpad.net/bugs/1182905 Title: charm-tools requires extra environments.yaml config To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/charm-tools/+bug/1182905/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1182905] Re: charm-tools installs juju-0.7
This is due to the package Recommending juju instead of either juju or juju-core. I have an updated recipe and hope to have this fixed in the PPA soon. ** Summary changed: - charm-tools requires extra environments.yaml config + charm-tools installs juju-0.7 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to charm-tools in Ubuntu. https://bugs.launchpad.net/bugs/1182905 Title: charm-tools installs juju-0.7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/charm-tools/+bug/1182905/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1182905] Re: charm-tools installs juju-0.7
This only affects users who have juju-core installed and not juju-0.7, those with either juju-0.7 or juju-0.7 and juju-core are unaffected. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to charm-tools in Ubuntu. https://bugs.launchpad.net/bugs/1182905 Title: charm-tools installs juju-0.7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/charm-tools/+bug/1182905/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Blueprint servercloud-s-juju-charm-testing] Juju Charm Testing
Blueprint changed by Marco Ceppi: 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 + Saul is patching a charm and wants to insure his changes work with the current tests - Laura is a charm maintainer and wants to add tests to in sure her charm + Laura is a charm maintainer and wants to add tests to insure 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 -- Juju Charm Testing https://blueprints.launchpad.net
[Blueprint servercloud-s-juju-charmhelper2] Charm Development Tooling
Blueprint changed by Marco Ceppi: Work items changed: Work items: - [marcoceppi] Consolidate existing forks/helper code bases: TODO + [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 -- 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 Marco Ceppi: 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 + [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 -- 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-charmhelper2] Charm Development Tooling
Blueprint changed by Marco Ceppi: Work items set to: Work items: [marcoceppi] Consolidate existing forks/helper code bases: TODO 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 -- 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
[Bug 1178384] Re: Charm needs Maintainership
** Also affects: memcached (Juju Charms Collection) Importance: Undecided Status: New ** Changed in: memcached (Juju Charms Collection) Status: New = In Progress ** Also affects: memcached (Ubuntu) Importance: Undecided Status: New ** No longer affects: memcached (Ubuntu) ** Also affects: rsyslog (Juju Charms Collection) Importance: Undecided Status: New ** Also affects: rsyslog-forwarder (Juju Charms Collection) Importance: Undecided Status: New ** Also affects: nagios (Juju Charms Collection) Importance: Undecided Status: New ** Also affects: nrpe (Juju Charms Collection) Importance: Undecided Status: New ** Changed in: nagios (Juju Charms Collection) Status: New = In Progress ** Changed in: nrpe (Juju Charms Collection) Status: New = In Progress ** Changed in: rsyslog (Juju Charms Collection) Status: New = In Progress ** Changed in: rsyslog-forwarder (Juju Charms Collection) Status: New = In Progress ** Changed in: memcached (Juju Charms Collection) Assignee: (unassigned) = Marco Ceppi (marcoceppi) ** Changed in: nagios (Juju Charms Collection) Assignee: (unassigned) = Marco Ceppi (marcoceppi) ** Changed in: nrpe (Juju Charms Collection) Assignee: (unassigned) = Marco Ceppi (marcoceppi) ** Changed in: rsyslog (Juju Charms Collection) Assignee: (unassigned) = Marco Ceppi (marcoceppi) ** Changed in: rsyslog-forwarder (Juju Charms Collection) Assignee: (unassigned) = Marco Ceppi (marcoceppi) ** No longer affects: rsyslog (Juju Charms Collection) ** No longer affects: rsyslog-forwarder (Juju Charms Collection) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to memcached in Ubuntu. https://bugs.launchpad.net/bugs/1178384 Title: Charm needs Maintainership To manage notifications about this bug go to: https://bugs.launchpad.net/charms/+source/memcached/+bug/1178384/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Blueprint servercloud-s-juju-charmhelper2] Charm Helper 2 - Declarative Charming
Blueprint changed by Marco Ceppi:
Whiteboard changed:
- [USER STORIES]
+ [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]
--- 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 Marco Ceppi: 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] === 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
[Bug 767352] Re: Virtual Users rules with @ in the username
There's a valid work around? What is it? Because the only valid work around I've found is use ProFTPD -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to vsftpd in Ubuntu. https://bugs.launchpad.net/bugs/767352 Title: Virtual Users rules with @ in the username To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vsftpd/+bug/767352/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 767352] [NEW] Virtual Users rules with @ in the username
Public bug reported: Binary package hint: vsftpd When using virtual users and custom pam authentication vsftpd won't load user_config_dir rules if that username has an @ symbol - which many shared hosts use to distinguish FTP users for a certain account or username. Authentication occurs correctly - just not the rules for that user. Ubuntu 10.04 LTS Server vsftpd: version 2.2.2 ** Affects: vsftpd (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to vsftpd in Ubuntu. https://bugs.launchpad.net/bugs/767352 Title: Virtual Users rules with @ in the username -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 767352] Re: Virtual Users rules with @ in the username
** Description changed: Binary package hint: vsftpd When using virtual users and custom pam authentication vsftpd won't load user_config_dir rules if that username has an @ symbol - which many shared hosts use to distinguish FTP users for a certain account or username. Authentication occurs correctly - just not the rules for that user. Ubuntu 10.04 LTS Server vsftpd: version 2.2.2 + + Details on how I have come to the conclusion this is a bug can be found + here: http://serverfault.com/q/261774/24044 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to vsftpd in Ubuntu. https://bugs.launchpad.net/bugs/767352 Title: Virtual Users rules with @ in the username -- 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
