[
http://jira.amdatu.org/jira/browse/AMDATU-394?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=11279#comment-11279
]
Bram de Kruijff commented on AMDATU-394:
----------------------------------------
Notes on integration/compatibility:
1) We'll need 0.8.0 + as ACE-156 makes webui compatible with Amdatu Web
(https://issues.apache.org/jira/browse/ACE-156)
2) We can replace ace-configurator with file install by simply mapping factory
cfg from "<pid>/instance.cfg" to "<pid>-<instance>.cfg"
3) ACE needs a preferencesservice (see AMDATU-402]
4) Current release modules deploys Felix main... remove
5) While looking at (pax) scripts consider optional bundles (tui / webconsole)
for production deployment
> Create initial Amdatu AMS with ACE server
> -----------------------------------------
>
> Key: AMDATU-394
> URL: http://jira.amdatu.org/jira/browse/AMDATU-394
> Project: Amdatu
> Issue Type: Task
> Components: Amdatu Provisioning
> Affects Versions: 0.3.0-M0
> Reporter: Marcel Offermans
> Assignee: Bram de Kruijff
> Fix For: 0.3.0-M1
>
>
> Based on the Apache ACE server, create an Amdatu AMS that can be used to
> provision Amdatu AMA targets.
> Proposed approach:
> 1) Create new Amdatu AMS module that creates an assembly like the release
> module does (could become a subproject at a later stage)
> 2) Investigate maven inheritance, overlayt and pax runner scan options to
> avoid redundancy (not highest priority but would be nice)
> 3) Assemble minimal set of ACE artifacts required to provide provisioning
> capabilities and webui
> 4) Look into simple ways to brand the UI a little (low prio as it may be just
> a tmp solution)
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
Amdatu-developers mailing list
[email protected]
http://lists.amdatu.org/mailman/listinfo/amdatu-developers
