Re: Odd ec2 behavior - volumes attached to bootstrap node.
On Fri, Mar 21, 2014 at 08:21:11AM +0400, John Meinel wrote: Notice that volume which is attached is a *new* volume. You are right... confused by euca/ec2 cmdline output again! :( Thanks John. -- David Britton david.brit...@canonical.com -- Juju mailing list Juju@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
Re: I WANT YOU, to give me your feedback (Juju docs!)
Markdown +1 IMO On Fri, Mar 21, 2014 at 10:47 AM, Marco Ceppi marco.ce...@canonical.comwrote: Hi everyone, I'm spreading this email out across the juju-core, juju, and juju-gui list to start a discussion about the next format for the docs. Currently, I've worked on a proof of concept to converting the docs to Markdown and it's going really well. Using python-markdown with a few custom plugins to handle the unique user friendly features the docs provide. However, I wanted to get feedback on the choice of formatting. Markdown has quickly become the choice of formatting for new projects, it's used heavily on the StackExchange network as well as Github. It's even a recommendation for the charm README files and charm-tools creates a Markdown template for use. Finally, it bares similarities to RST but tends to be more forgiving and require less syntax to use. To quote the John Gruber, Markdown creator: While Markdown's syntax has been influenced by several existing text-to-HTML filters, the single biggest source of inspiration for Markdown's syntax is the format of plain text email. This low barrier of entry is likely one of the reasons it's grown in popularity over the years. I'm curious of people's opinions, do you support this move to Markdown? Do you have other formats for docs in mind and if so reasons that style instead? After some time I'll consider the responses, for and against, as a poll for which language to move the docs to as I finish my conversion Thanks, Marco Ceppi -- Juju mailing list Juju@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju -- Thanks, Juan L. Negron juan.neg...@canonical.com Mobile: +1 408 634 0292 Cloud Architect Canonical Technical Services Canonical USA GPG : 0A62 BC70 5CBC B4DD F3E6 8A27 A6B1 F3F0 E6B5 F5A3 -- Juju mailing list Juju@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
Re: I WANT YOU, to give me your feedback (Juju docs!)
I support the move to Markdown formatted text. I'd even further support the move to something similar to GitHub Flavored Markdown (http://github.github.com/github-flavored-markdown/), which I prefer since it supports fenced code blocks and syntax highlighting. I feel moving the content to Markdown will lower the barrier for contributors, as opposed to moving to formatting documentation in something like LaTeX (in other words, -1 for LaTeX from me), which is more complex in my opinion. - Joshua On 3/21/2014 19:49, Juan Negron wrote: Markdown +1 IMO On Fri, Mar 21, 2014 at 10:47 AM, Marco Ceppi marco.ce...@canonical.com mailto:marco.ce...@canonical.com wrote: Hi everyone, I'm spreading this email out across the juju-core, juju, and juju-gui list to start a discussion about the next format for the docs. Currently, I've worked on a proof of concept to converting the docs to Markdown and it's going really well. Using python-markdown with a few custom plugins to handle the unique user friendly features the docs provide. However, I wanted to get feedback on the choice of formatting. Markdown has quickly become the choice of formatting for new projects, it's used heavily on the StackExchange network as well as Github. It's even a recommendation for the charm README files and charm-tools creates a Markdown template for use. Finally, it bares similarities to RST but tends to be more forgiving and require less syntax to use. To quote the John Gruber, Markdown creator: While Markdown's syntax has been influenced by several existing text-to-HTML filters, the single biggest source of inspiration for Markdown's syntax is the format of plain text email. This low barrier of entry is likely one of the reasons it's grown in popularity over the years. I'm curious of people's opinions, do you support this move to Markdown? Do you have other formats for docs in mind and if so reasons that style instead? After some time I'll consider the responses, for and against, as a poll for which language to move the docs to as I finish my conversion Thanks, Marco Ceppi -- Juju mailing list Juju@lists.ubuntu.com mailto:Juju@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju -- Thanks, Juan L. Negron juan.neg...@canonical.com mailto:juan.neg...@canonical.com Mobile: +1 408 634 0292 Cloud Architect Canonical Technical Services Canonical USA GPG : 0A62 BC70 5CBC B4DD F3E6 8A27 A6B1 F3F0 E6B5 F5A3 -- Juju mailing list Juju@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
Re: [Juju-gui-peeps] I WANT YOU, to give me your feedback (Juju docs!)
On Fri, Mar 21, 2014 at 1:47 PM, Marco Ceppi marco.ce...@canonical.comwrote: Hi everyone, I'm spreading this email out across the juju-core, juju, and juju-gui list to start a discussion about the next format for the docs. Currently, I've worked on a proof of concept to converting the docs to Markdown and it's going really well. Using python-markdown with a few custom plugins to handle the unique user friendly features the docs provide. However, I wanted to get feedback on the choice of formatting. Markdown has quickly become the choice of formatting for new projects, it's used heavily on the StackExchange network as well as Github. It's even a recommendation for the charm README files and charm-tools creates a Markdown template for use. Finally, it bares similarities to RST but tends to be more forgiving and require less syntax to use. To quote the John Gruber, Markdown creator: While Markdown's syntax has been influenced by several existing text-to-HTML filters, the single biggest source of inspiration for Markdown's syntax is the format of plain text email. This low barrier of entry is likely one of the reasons it's grown in popularity over the years. I'm curious of people's opinions, do you support this move to Markdown? Do you have other formats for docs in mind and if so reasons that style instead? After some time I'll consider the responses, for and against, as a poll for which language to move the docs to as I finish my conversion This is pretty biased towards markdown, generally restructured text has a tradition and success for being used for documentation.. Any plain text format is big win imo from what we have today. http://stackoverflow.com/questions/34276/markdown-versus-restructuredtext So the question becomes, what format would be preferential among developers for writing docs . The candidates so far are as follows 1. Markdown 2. Restructured Text 3. HTML5/CSS preprocessors/custom scripts (Currently in use) -- Juju mailing list Juju@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
Re: I WANT YOU, to give me your feedback (Juju docs!)
On Fri, Mar 21, 2014 at 1:47 PM, Marco Ceppi marco.ce...@canonical.com wrote: I'm spreading this email out across the juju-core, juju, and juju-gui list to start a discussion about the next format for the docs. Currently, I've worked on a proof of concept to converting the docs to Markdown and it's going really well. Using python-markdown with a few custom plugins to handle the unique user friendly features the docs provide. However, I wanted to get feedback on the choice of formatting. Markdown has +1 Caveat that I think we need a post proc to format input examples and output examples and possibly glossary links. Given that 1.18.0 can be out next week. 1.18.0's docs will be written in the current HTML format so that we can deliver them next week too...unless you happen to already have tip and unstable docs already converted to markdown and a post processor ready to go. -- Curtis Hovey Canonical Cloud Development and Operations http://launchpad.net/~sinzui -- Juju mailing list Juju@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
Re: I WANT YOU, to give me your feedback (Juju docs!)
I feel there needs to be a slight (big) addendum to this: 1. There is no specific timetable for this, so people shouldn't be expecting big changes next week or something. 2. It isn't a question of Markdown or stay as it is. If you have strong feelings about RsT or SGML or Mallard or who knows what, I'd like to hear about them too. If there are specific reasons for using a particular format, please mention them. Bear in mind that the primary goal is to give USERS the documentation they want/need. 3. Ideally I would like to move to a position where we could use one source format and set of tools for all docs projects in CDO, but that is a longer term goal. 4. This isn't a democracy. I would be interested to hear what formats people are comfortable with, but if 10 people who have never contributed to the docs before all say DocBook or something, that will have to be slightly balanced by whether we can make an acceptable workflow around that for the people who actually do the majority of the work (i.e. me) and others who make more frequent contributions. The bottom line is, I would like the docs to be easier to contribute to. There are too many features landing that aren't documented and this really needs to change, for everyone's benefit. Nick On Fri, Mar 21, 2014 at 6:45 PM, Curtis Hovey-Canonical cur...@canonical.com wrote: On Fri, Mar 21, 2014 at 1:47 PM, Marco Ceppi marco.ce...@canonical.com wrote: I'm spreading this email out across the juju-core, juju, and juju-gui list to start a discussion about the next format for the docs. Currently, I've worked on a proof of concept to converting the docs to Markdown and it's going really well. Using python-markdown with a few custom plugins to handle the unique user friendly features the docs provide. However, I wanted to get feedback on the choice of formatting. Markdown has +1 Caveat that I think we need a post proc to format input examples and output examples and possibly glossary links. Given that 1.18.0 can be out next week. 1.18.0's docs will be written in the current HTML format so that we can deliver them next week too...unless you happen to already have tip and unstable docs already converted to markdown and a post processor ready to go. -- Curtis Hovey Canonical Cloud Development and Operations http://launchpad.net/~sinzui -- 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: I WANT YOU, to give me your feedback (Juju docs!)
+1 to Markdown. Nice integration with GitHub (edit, preview, etc.), pretty much a de facto standard on there. I'd also like to see us using GitHub Pages for unstable/unreleased versions of Juju. On Sat, Mar 22, 2014 at 1:47 AM, Marco Ceppi marco.ce...@canonical.comwrote: Hi everyone, I'm spreading this email out across the juju-core, juju, and juju-gui list to start a discussion about the next format for the docs. Currently, I've worked on a proof of concept to converting the docs to Markdown and it's going really well. Using python-markdown with a few custom plugins to handle the unique user friendly features the docs provide. However, I wanted to get feedback on the choice of formatting. Markdown has quickly become the choice of formatting for new projects, it's used heavily on the StackExchange network as well as Github. It's even a recommendation for the charm README files and charm-tools creates a Markdown template for use. Finally, it bares similarities to RST but tends to be more forgiving and require less syntax to use. To quote the John Gruber, Markdown creator: While Markdown's syntax has been influenced by several existing text-to-HTML filters, the single biggest source of inspiration for Markdown's syntax is the format of plain text email. This low barrier of entry is likely one of the reasons it's grown in popularity over the years. I'm curious of people's opinions, do you support this move to Markdown? Do you have other formats for docs in mind and if so reasons that style instead? After some time I'll consider the responses, for and against, as a poll for which language to move the docs to as I finish my conversion Thanks, Marco Ceppi -- Juju-dev mailing list juju-...@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju-dev -- Juju mailing list Juju@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
Re: Help with arcitecture Part1
Oh awesome. That is really neat the flexibility. On Mar 21, 2014 10:22 PM, John Meinel j...@arbash-meinel.com wrote: You can always do juju deploy --to 3 to deploy directly to machine 3 on the bare metal. I was just mentioning that you can also do KVM or LXC containers on top of bare metal. John =:- On Fri, Mar 21, 2014 at 8:35 PM, Brian Wawok bwa...@gmail.com wrote: So --to:kvm is as close to bare metal as we can get? What is the performance implications of a single KVM vm on a bare metal (vs if we had done a direct to metal install). Brian On Thu, Mar 20, 2014 at 11:24 PM, John Meinel j...@arbash-meinel.com wrote: I would actually just use MaaS + LXC or KVM virtualization. You should be able to bring up a MaaS environment, and then do: juju deploy NEWSERVICE --to lxc:10 And Juju will create a new LXC container on machine 10 and deploy the NEWSERVICE into it. That gives you all the give me baremetal when I want it, and it gives you container separation as well. (You should also be able to do juju deploy foo --to kvm:12 for times when you have a Charm that needs direct device access.) John =:- -- Juju mailing list Juju@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
Re: I WANT YOU, to give me your feedback (Juju docs!)
+1 Markdown is great. It's basically the only way to write HTML that is actually legible outside of a browser (like in diffs, code reviews, as you're actually writing it, etc). On Fri, Mar 21, 2014 at 1:47 PM, Marco Ceppi marco.ce...@canonical.comwrote: Hi everyone, I'm spreading this email out across the juju-core, juju, and juju-gui list to start a discussion about the next format for the docs. Currently, I've worked on a proof of concept to converting the docs to Markdown and it's going really well. Using python-markdown with a few custom plugins to handle the unique user friendly features the docs provide. However, I wanted to get feedback on the choice of formatting. Markdown has quickly become the choice of formatting for new projects, it's used heavily on the StackExchange network as well as Github. It's even a recommendation for the charm README files and charm-tools creates a Markdown template for use. Finally, it bares similarities to RST but tends to be more forgiving and require less syntax to use. To quote the John Gruber, Markdown creator: While Markdown's syntax has been influenced by several existing text-to-HTML filters, the single biggest source of inspiration for Markdown's syntax is the format of plain text email. This low barrier of entry is likely one of the reasons it's grown in popularity over the years. I'm curious of people's opinions, do you support this move to Markdown? Do you have other formats for docs in mind and if so reasons that style instead? After some time I'll consider the responses, for and against, as a poll for which language to move the docs to as I finish my conversion Thanks, Marco Ceppi -- Juju-dev mailing list Juju-dev@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju-dev -- Juju-dev mailing list Juju-dev@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju-dev
Re: I WANT YOU, to give me your feedback (Juju docs!)
I have contributed to the Juju documentation and the process was harder than the format. Another vote for Markdown from me. If we truly want contributions from the community we should keep the barrier of entry low. It is written somewhere in the docs that people can and should contribute to the Juju documentation. The Juju community already needs to know markdown for the README.md files in the charms, so it makes sense to use the *same* format for the docs. - Matt Bruzek On Fri, Mar 21, 2014 at 12:47 PM, Marco Ceppi marco.ce...@canonical.comwrote: Hi everyone, I'm spreading this email out across the juju-core, juju, and juju-gui list to start a discussion about the next format for the docs. Currently, I've worked on a proof of concept to converting the docs to Markdown and it's going really well. Using python-markdown with a few custom plugins to handle the unique user friendly features the docs provide. However, I wanted to get feedback on the choice of formatting. Markdown has quickly become the choice of formatting for new projects, it's used heavily on the StackExchange network as well as Github. It's even a recommendation for the charm README files and charm-tools creates a Markdown template for use. Finally, it bares similarities to RST but tends to be more forgiving and require less syntax to use. To quote the John Gruber, Markdown creator: While Markdown's syntax has been influenced by several existing text-to-HTML filters, the single biggest source of inspiration for Markdown's syntax is the format of plain text email. This low barrier of entry is likely one of the reasons it's grown in popularity over the years. I'm curious of people's opinions, do you support this move to Markdown? Do you have other formats for docs in mind and if so reasons that style instead? After some time I'll consider the responses, for and against, as a poll for which language to move the docs to as I finish my conversion Thanks, Marco Ceppi -- Juju-dev mailing list Juju-dev@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju-dev -- Juju-dev mailing list Juju-dev@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju-dev
Re: I WANT YOU, to give me your feedback (Juju docs!)
+1 to Markdown. Nice integration with GitHub (edit, preview, etc.), pretty much a de facto standard on there. I'd also like to see us using GitHub Pages for unstable/unreleased versions of Juju. On Sat, Mar 22, 2014 at 1:47 AM, Marco Ceppi marco.ce...@canonical.comwrote: Hi everyone, I'm spreading this email out across the juju-core, juju, and juju-gui list to start a discussion about the next format for the docs. Currently, I've worked on a proof of concept to converting the docs to Markdown and it's going really well. Using python-markdown with a few custom plugins to handle the unique user friendly features the docs provide. However, I wanted to get feedback on the choice of formatting. Markdown has quickly become the choice of formatting for new projects, it's used heavily on the StackExchange network as well as Github. It's even a recommendation for the charm README files and charm-tools creates a Markdown template for use. Finally, it bares similarities to RST but tends to be more forgiving and require less syntax to use. To quote the John Gruber, Markdown creator: While Markdown's syntax has been influenced by several existing text-to-HTML filters, the single biggest source of inspiration for Markdown's syntax is the format of plain text email. This low barrier of entry is likely one of the reasons it's grown in popularity over the years. I'm curious of people's opinions, do you support this move to Markdown? Do you have other formats for docs in mind and if so reasons that style instead? After some time I'll consider the responses, for and against, as a poll for which language to move the docs to as I finish my conversion Thanks, Marco Ceppi -- Juju-dev mailing list Juju-dev@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju-dev -- Juju-dev mailing list Juju-dev@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju-dev
