User Tools
juju-charms
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
juju-charms [2014/05/07 17:45] avladu Virtual machine req for Exchange |
juju-charms [2015/02/03 17:44] (current) gsamfira |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | ====== Writting Juju Charms for Windows ====== | + | ====== Writing Juju Charms for Windows ====== |
| - | :!: This page needs more work :!: | + | ======= Rules ======= |
| - | The rules of writting charms are the same in Windows as they are in linux. As a reference, the Havana Hyper-V charm can be used. The charm can be found at: | + | - Charms are self contained. Under no circumstances should they have any missing pieces or require the user to manually include anything for them to work |
| + | - Master branch of any charm is holy ground. If a piece of code gets in, it is expected to work without any issues. | ||
| + | - All new features must be added as new branches. | ||
| + | - Under no circumstances are branches to be merged into master unless they have been thoroughly tested and scrutinized. | ||
| + | - Merges are only to be done after one or more peers have had a chance to review and aprove the code. Untill then, the code WILL remain in its feature branch | ||
| + | - Any deviation from the above is only possible by devine intervention, or if your name is Chuck Norris. | ||
| - | https://github.com/gabriel-samfira/juju-hacks/tree/master/charms/win2012hvr2/nova-hyperv | + | |
| - | | + | ===== Charm Structure ===== |
| + | |||
| + | |||
| + | The rules of writing charms are the same in Windows as they are in linux. As a reference, the Nova Hyper-V charm can be used. The charm can be found at: | ||
| + | |||
| + | https://github.com/cloudbase/nova-hyperv-charm | ||
| By default, Juju adds $env:CHARM_DIR\hooks\Modules and $env:CHARM_DIR\Modules in $env:PSModulePath. So you can simply write a module, bundle it with your charm, and simply do an Import-Module in your hooks. We should strive to create a common suite of helper modules for all juju charms on windows! | By default, Juju adds $env:CHARM_DIR\hooks\Modules and $env:CHARM_DIR\Modules in $env:PSModulePath. So you can simply write a module, bundle it with your charm, and simply do an Import-Module in your hooks. We should strive to create a common suite of helper modules for all juju charms on windows! | ||
| Line 31: | Line 41: | ||
| CPU - more than 4 cores | CPU - more than 4 cores | ||
| RAM - more than 6GB | RAM - more than 6GB | ||
| + | HDD - more than 40GB | ||
| + | Beware!: | ||
| + | You can install only one Exchange per Active Directory Domain | ||
| + | The machine will reboot 4 times | ||
| + | The installation will take approximately 1 hour | ||
| 4. Windows Active Directory MsSQL | 4. Windows Active Directory MsSQL | ||
| 5. Windows Active Directory SharePoint | 5. Windows Active Directory SharePoint | ||
| + | |||
| + | 6. Windows IIS Drupal | ||
| + | |||
| + | Relations: | ||
| + | MySQL | ||
| + | Memcached | ||
| + | Windows Active Directory Controller | ||
| + | Windows Active Directory MsSQL | ||
| + | File dependencies: | ||
| + | Every file dependency is downloaded from the internet using official download links and it is checked for integrity using SHA1 checksum. | ||
| + | Minimum virtual machine requirements: | ||
| + | CPU - 2 cores | ||
| + | RAM - 2GB | ||
| + | HDD - 30GB | ||
| + | NOTE: If any download link becomes unavailable, it must be updated together its SHA1 hash. Use only official download links ! | ||
juju-charms.1399473958.txt.gz · Last modified: 2014/05/07 17:45 by avladu
Page Tools
Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Share Alike 4.0 International
