Re: wishlist: charm bundle for Read The Docs
+1000 for that! It's a django + celery + postgresql tool. Perhaps it can be contained in a generic-ish django charm? Best regards ZK On Wed, Mar 18, 2015 at 3:06 PM, sheila miguez she...@pobox.com wrote: Has anyone written a charm bundle for Read The Docs? I'd enjoy deploying it to a private environment, but I don't have free time to set it up. http://docs.readthedocs.org/en/latest/rtfd.html (may be krufty?) -- she...@pobox.com -- Juju mailing list Juju@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju -- Juju mailing list Juju@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
Re: wishlist: charm bundle for Read The Docs
I bet it can! I've been wanting to set aside a block of time to get some cleanups and fixes in to the python-django charm and share an example mojo spec for deploying a simple django site. I think Read The Docs* could be an example, but I've been so busy outside of work with other volunteer activities that my good juju intentions are really stalled. It's been weeks since I meant to do this. If someone else already has that would be most excellent. * I work on pyvideo.org and would like use it as an example as well. I haven't been using juju with it because we've been running it on donated rackspace instances. but this won't happen because I don't have free time to volunteer on it. I'm very happy to see that rackspace support is planned for the future. On Wed, Mar 18, 2015 at 9:25 AM, Zygmunt Krynicki zygmunt.kryni...@canonical.com wrote: +1000 for that! It's a django + celery + postgresql tool. Perhaps it can be contained in a generic-ish django charm? Best regards ZK On Wed, Mar 18, 2015 at 3:06 PM, sheila miguez she...@pobox.com wrote: Has anyone written a charm bundle for Read The Docs? I'd enjoy deploying it to a private environment, but I don't have free time to set it up. http://docs.readthedocs.org/en/latest/rtfd.html (may be krufty?) -- she...@pobox.com -- Juju mailing list Juju@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju -- she...@pobox.com -- Juju mailing list Juju@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
wishlist: charm bundle for Read The Docs
Has anyone written a charm bundle for Read The Docs? I'd enjoy deploying it to a private environment, but I don't have free time to set it up. http://docs.readthedocs.org/en/latest/rtfd.html (may be krufty?) -- she...@pobox.com -- Juju mailing list Juju@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
Re: Exporting bundles yaml from juju command (not just juju-gui)
Awesome ! Is there a simple way to create the yaml with the exact versions of the charms deployed ?? On Wed, Mar 18, 2015 at 5:33 PM, Jorge Niedbalski jorge.niedbal...@canonical.com wrote: Hello Bryan, On Wed, Mar 18, 2015 at 1:22 PM, Bryan Quigley bryan.quig...@canonical.com wrote: Hi there, [...] As far as I can tell, juju status (format yaml) get's us a lot of the way there, but can't be used to quickly reproduce a customer environment. Thanks! Bryan I just made a plugin for doing this (https://github.com/niedbalski/juju-deployerizer ), basically it takes the status and converts it into yaml bundle that can be used by deployer. Hope it helps. Regards. -- Jorge Niedbalski R. Software Sustaining Engineer CTS - Engineering Team gpg:0x3DA28544, irc: niedbalski -- Juju mailing list Juju@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju -- Best Regards, Nicolas Thomas http://insights.ubuntu.com/?p=889 EMEA Solution Architect Canonical GPG FPR: D592 4185 F099 9031 6590 6292 492F C740 F03A 7EB9 -- Juju mailing list Juju@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
Openstack Service Networking
Let me preface this by letting you know that I have tested and demoed 2 or 3 handfulls of different methods to deploy, automate, configure and maintain Openstack at a production level. I chose to use Juju for my company's method of Openstack orchestration and have been deep diving how to make this whole thing work for quite some time now. Despite my difficulties along the way(and current) I still feel that configuring, deploying, and maintaining is best done with Juju due to its open, pluggable architecture, and durable framework/environment for managing/adding/creating/destroying cloud based services on almost any and every platform. To that end, after spending some time configuring Openstack's services networking through the the use of juju charm configuration parameters, I can say that I am impressed with the high level of configurability offered at an abstracted level through juju charms. The open, abstracted and highly configurable networking parameters of juju charms I feel can also be harmful to some degree when questions must be answered that one (without immense effort and time) does not readily know the answer to because of the abstractedness or magic of the charm that protects us from the highly undesirable details of openstack configuration(JJ.. I was raised on hand rolled stacks :-). To this I attribute that fact that abstraction has became a limitation. I'm trying to see if there is a way we (the community) can get some kind of possible configuration mappings between openstack service charms and possible network configurations? I am fully aware of what services talk to one another and by what means when I hand roll a stack because I configure each parameter of each service myself.but when planning a deployment -- designing and testing networking infrastructure to be placed in a production environment.lets just say the magic of the charms it wears thin quickI now spend most of my days reading charm code (excellently written and designed might I say), network troubleshooting, openstack service investigations, and trying to create workarounds for things I cannot figure out by the aforementioned methods. -- Instead of leading my company to a production ready juno stack...I have now been configuring/testing Juju deploys all the way to (almost) kilo...which is actually great because now I will have one less production stack upgrade to do... I feel that myself as well as others will derive great benefit in planning, testing, and maintaining openstack deployments using Juju might we be aided by a simple, highly available Juju-Openstack service charms network configuration references, information and limitations -- might depict what the limitations, possibilities, and reference configurations exist for a few popular openstack network configurations offered by the juju charms, i.e. what services talk over what networks when configuration A,B,C or D is used, separating storage traffic when deploying with juju charms configs, network address space segmentation on a flat network, multi-net configs, how many interfaces, what traffic talks where when You get my point (hopefully). I'm not looking for a what, when, where, who, how, why on all of openstack networkingbut possibly just a what, when, where, who, how, why on openstack networking using Juju. This is the use case I am describing that would/could be answered by juju given some direction exists for network config: https://www.dropbox.com/s/11e7kjginiofd0d/Screenshot%202015-03-18%2001.37.42.png?dl=0 (nothing to do with mellanox or fuel...just wanted to emphasize the verify networks functionality) EDIT: This sounds more and more like a feature request for the openstack-installer!! Please do not take this the wrong way, I am very thankful for the outstanding software you all createI only hope this can help make it even better. signature.asc Description: Message signed with OpenPGP using GPGMail -- Juju mailing list Juju@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
Re: Exporting bundles yaml from juju command (not just juju-gui)
Hello Bryan, On Wed, Mar 18, 2015 at 1:22 PM, Bryan Quigley bryan.quig...@canonical.com wrote: Hi there, [...] As far as I can tell, juju status (format yaml) get's us a lot of the way there, but can't be used to quickly reproduce a customer environment. Thanks! Bryan I just made a plugin for doing this (https://github.com/niedbalski/juju-deployerizer ), basically it takes the status and converts it into yaml bundle that can be used by deployer. Hope it helps. Regards. -- Jorge Niedbalski R. Software Sustaining Engineer CTS - Engineering Team gpg:0x3DA28544, irc: niedbalski -- Juju mailing list Juju@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
Re: Exporting bundles yaml from juju command (not just juju-gui)
Hello Nicolas, On Wed, Mar 18, 2015 at 1:42 PM, Nicolas Thomas nicolas.tho...@canonical.com wrote: Awesome ! Is there a simple way to create the yaml with the exact versions of the charms deployed ?? Yes, you can: $ juju deployerizer --include-charm-versions -e local Best, -- Jorge Niedbalski R. Software Sustaining Engineer CTS - Engineering Team gpg:0x3DA28544, irc: niedbalski -- Juju mailing list Juju@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
neutron-api plugin data: config vs relation
Hi Charmers! As part of the Midonet charms, I'm targeting the neutron-api charm for extension so that 'midonet' is a new kind of neutron-plugin to configure in its config.yaml In order to have the plugin write the data it should for the plugin I submitted for review a patch[0] to charm-helpers that sets up the right configuration context for neutron. Then, to tackle the neutron-api side, I was unsure of which road to take, so I took two of them :P Config.yaml based approach[1] === This approach relies on the admin using some config.yaml when deploying midonet-api and neutron-api that defines the same midonet-username, midonet-api-host, etc. It feels a bit clunky but the integration will work and it follows an already present model of plugin configuration pioneered by the nsx plugin. relation based approach[2] === This approach establishes a neutron-api interface relation between neutron-api and midonet-api where midonet-api will set the necessary data to the relation (including its own IP thanks to the implicit juju-info interface). It required the addition of a check and a helper function in the neutron context generation, but it feels much cleaner and that it leverages more of the power of juju. I would really appreciate some feedback on the two approaches before I send one for testing and review. Best regards, Toni [0] https://code.launchpad.net/~celebdor/charm-helpers/midonet/+merge/253367 [1] http://bazaar.launchpad.net/~celebdor/charms/trusty/neutron-api/midonet/revision/85 [2] http://bazaar.launchpad.net/~celebdor/charms/trusty/neutron-api/midonet_alter/revision/85 -- Juju mailing list Juju@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
