<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">It does seem that best practices and
recommended tools/ workflows is something that keeps coming up.
Maybe a charm school dedicated to writing a charm from scratch
would be useful?<br>
<br>
Matt<br>
<br>
On 22/05/13 14:49, <a class="moz-txt-link-abbreviated" href="mailto:franck.dehay@orange.com">franck.dehay@orange.com</a> wrote:<br>
</div>
<blockquote
cite="mid:1961_1369230569_519CCCE9_1961_2258_1_10EBB1E3DA88224D91F0AE3C2909D3D630BC2416DE@PUEXCB1F.nanterre.francetelecom.fr"
type="cite">
<meta http-equiv="Content-Type" content="text/html;
charset=ISO-8859-1">
<meta name="Generator" content="Microsoft Word 14 (filtered
medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";
mso-fareast-language:EN-US;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
{mso-style-priority:99;
mso-style-link:"Texte de bulles Car";
margin:0cm;
margin-bottom:.0001pt;
font-size:8.0pt;
font-family:"Tahoma","sans-serif";
mso-fareast-language:EN-US;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri","sans-serif";
color:windowtext;}
span.TextedebullesCar
{mso-style-name:"Texte de bulles Car";
mso-style-priority:99;
mso-style-link:"Texte de bulles";
font-family:"Tahoma","sans-serif";}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri","sans-serif";
mso-fareast-language:EN-US;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:70.85pt 70.85pt 70.85pt 70.85pt;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
<div class="WordSection1">
<p class="MsoNormal">Hello all,<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span lang="EN-US">Being quite new to juju,
I would like to be able to give fellow programmers some best
practices on how to write charms.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">We are investigating
Chef as well and the move from bash to ruby was seen as a
progress (indempotence with keywords, templating engine…)<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">Browsing through the
charm store, I see lots of diversity, which is normal as
juju requires only executable files as hooks.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">Some implement all in
one python program with symlinks (quite cute I would say),
most do the install with bash…<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">If you guys had some
proposal for best suited method it would be nice.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">I remember having read
in the archives that python would be the recommended
language.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">Is it still the vision?<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">Which templating method
would be recommended (jinja?)<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:10.0pt;font-family:"Arial","sans-serif";color:black;mso-fareast-language:FR"
lang="EN-US">Do you have one recommended charm as starting
point? <o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:10.0pt;font-family:"Arial","sans-serif";color:black;mso-fareast-language:FR"
lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span
style="font-size:10.0pt;font-family:"Arial","sans-serif";color:black;mso-fareast-language:FR"
lang="EN-US">Thanks a lot!<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:10.0pt;font-family:"Arial","sans-serif";color:black;mso-fareast-language:FR"
lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span
style="font-size:10.0pt;font-family:"Arial","sans-serif";color:black;mso-fareast-language:FR"><a
moz-do-not-send="true"
href="mailto:franck.dehay@orange-ftgroup.com"><span
style="color:#FF6600" lang="EN-US">franck.dehay@orange.com</span></a></span><span
style="font-size:10.0pt;font-family:"Arial","sans-serif";color:black;mso-fareast-language:FR"
lang="EN-US"><o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<pre>_________________________________________________________________________________________________________________________
Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
France Telecom - Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.
This message and its attachments may contain confidential or privileged information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this message and its attachments.
As emails may be altered, France Telecom - Orange is not liable for messages that have been modified, changed or falsified.
Thank you.
</pre>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
</blockquote>
<br>
</body>
</html>