← Back to team overview

juju-tosca team mailing list archive

Re: tosca node_type to Juju charm translator draft version

 

Thanks for pushing that branch. I've been looking at it and I think the model is good for the overall structure. Perhaps we can make use of it for the other areas as well.

I do still run into the problem with the EOL translation from Windows. It looks like there's some git config that can prevent this issue. Check out the answer with 10 votes here: http://stackoverflow.com/questions/2466959/git-removing-carriage-returns-from-source-controlled-files Maybe we should give those a try and see if it fixes the problem before merging.

Thanks,
Mike


On 08/26/2014 08:30 AM, Zhi Xiang Zhai wrote:
Hi toscateers,
    I committed my codes to "draft" branch at repo
github.com/juju/juju-tosca, the function includes unit hooks mapping,
metadata.yaml translation, config.yaml translation (Didn't implement
relation hooks mapping yet). Since we just have unit hooks and relation
hooks mapping design document, many other elements mapping logic are
implemented based on my assumption. Please feel free to let me know if
there are any error logic in the translator codes. The following are my
changed code, you could run the "python translator/test.py" to test the
function.


Thanks.





Follow ups

References