Continuous Automated Deployment with Apache ACE
2 likes1,526 views
The document discusses continuous automated deployment using Apache ACE, focusing on the transition from monolithic to modular applications and versioning strategies for bundles. It highlights the importance of semantic versioning, baselining, and the CI workflow for managing deployments and artifacts efficiently. Additionally, it includes demos and examples of how to set up and manage artifacts using various tools such as Jenkins and Git.
![!
echo "For each bundle"
each $deployed {
echo "Get metadata from bundle"
identity = $it getIdentity
version = $it getVersion
name = "$identity - $version"
url = $it getUrl
mimetype = $it getMimetype
echo "Bundle exists?"
if { (coll:first
($workspace la "(&(Bundle-SymbolicName=$identity)
(Bundle-Version=$version))")) } {
echo "$name already exists"
} {
echo "Create artifact for bundle"
$workspace ca [
artifactName="$name"
url="$url"
mimetype="$mimetype"
Bundle-SymbolicName="$identity"
Bundle-Version="$version"
]
}
}
!
echo "Commit workspace"
$workspace commit
exit 0
Get metadata
from bundle
Create artifact for
bundle
Bundle
exists?
Commit
workspace
Quit
For each
bundle
no
yes
next bundle
done](https://image.slidesharecdn.com/continuousautomateddeploymentwithapacheace-140410111022-phpapp02/85/Continuous-Automated-Deployment-with-Apache-ACE-24-320.jpg)
Continuous Automated Deployment with Apache ACE
- 2. Who are we Director at Luminis Technologies Member at the Apache Software Foundation @m4rr5 Marcel Offermans Jan Willem Janssen Software Architect at Luminis Technologies committer and PMC member of Apache ACE @j_w_janssen
- 3. Agenda •Traditional Continuous Integration •From EAR to bundles •Versioning and baselining •ACE basics •Build env. setup with ACE •Demo
- 4. Typical CI workflow (D)VCS CI EAR/WAR Target ? Maven,! scp, ftp, nfs, smb, … without OSGi and ACE
- 5. Monolithic to Modular •Single, big, monolithic application •Versioned whenever “something” changes •On every change the whole application has to be redeployed •Many, small modules that can be combined to form applications •Modules versioned independently •Only modules that changed need to be redeployed
- 6. What to version? So we know their contents has changed So we know the interface contract has changed our focus here is on bundle versions, because they tell us what to update Bundles Exported Packages
- 7. Semantic Versioning • Major: Backward incompatible change! • Minor: Backward compatible change! • Micro: Implementation change! • Qualifier: Label, e.g. build number major.minor.micro(.qualifier) 1.0.0.abc tells us what has changed
- 8. Baselining •Compares build with latest release •Checks if version numbers should be bumped •Uses byte code analysis -‐baseline: * -‐removeheaders: Bnd-‐LastModified,Tool,Created-‐By Eclipse with Bndtools
- 9. Baselining •Bnd annotations •@ProviderType A type that is provided by the implementor of the contract. •@ConsumerType A type that is typically implemented by the consumer of the contract.
- 11. Apache ACE •Software distribution framework •Manage installation/upgrade of targets •bundles •configurations •etc
- 13. ACE basics Store&Repository Ar-fact Distribu-onFeature License'Repository Distribu1on Target •group artifacts into features and distributions to make them manageable •IKEA catalogue
- 15. Apache ACE demo
- 16. CI workflow (D)VCS CI Bundles Target Snapshots Releases OBR ACE with OSGi & ACE
- 17. Build env. with ACE Snapshots Releases Bundles from build
- 18. A 1.0.1.SNAPSHOT Workspace B 1.0.1.SNAPSHOT C 1.0.1.SNAPSHOT Snapshot Repository A 1.0.0 B 1.0.0 C 1.0.0 Release Repository A 1.0.1.SNAPSHOT B 1.0.1.SNAPSHOT C 1.0.1.SNAPSHOT Versioning bundles from a build Assume only bundle A changed since the release 1.0.1.SNAPSHOT > 1.0.1 even though they have the same version, not all snapshots are equal even if nothing changed, you still end up with a new snapshot bundle
- 19. A 1.0.1.20131023 Workspace B 1.0.1.20131023 C 1.0.1.20131023 A 1.0.1.20131024 B 1.0.1.20131024 C 1.0.1.20131024 Snapshot Repository A 1.0.0 B 1.0.0 C 1.0.0 Release Repository Versioning bundles from a build Assume only bundle A changed since the release 1.0.1.20131022 > 1.0.1 even though they have a different version, they might still be equal even if nothing changed, you still end up with a new bundle
- 20. Versioning bundles from a build Assume only bundle A changed since the release A 1.0.1 Workspace B 1.0.0 C 1.0.0 A 1.0.0.CDS001 Snapshot Repository B 1.0.0 C 1.0.0 A 1.0.0 B 1.0.0 C 1.0.0 Release Repository 1.0.0.CDS001 < 1.0.1 the bundle gets a new qualifier if it has changed if nothing changed, nothing new is deployed
- 21. What do we need? CI! Script that places bundles in the OBR ACE Server with snapshot and release OBR Target! Management agent configured to the ACE instance
- 22. GoGo shell •“Standard” OSGi shell (RFC-147) •Powerful and extensible •Available from Apache Felix •ACE provides commands to interact with its client API and OBRs
- 23. Script echo “Define repositories” sourceindex = (repo:index ../release) sourcerepo = (repo:repo R5 $sourceindex) targetrepo = (repo:repo OBR "http://localhost:8084/obr/repository.xml") releaserepo = (repo:repo OBR "http://localhost:8083/obr/repository.xml") ! echo "Deploying bundles" deployed = repo:cd $releaserepo $sourcerepo $targetrepo ! echo "Create workspace" workspace = (ace:cw) ! echo "For each bundle" each $deployed { echo "Get metadata from bundle" identity = $it getIdentity version = $it getVersion name = "$identity - $version" url = $it getUrl mimetype = $it getMimetype echo "Bundle exists?" Setup Define repositories Deploy bundles Create workspace Get metadata from bundle Bundle For each bundle yes next bundle done
- 24. ! echo "For each bundle" each $deployed { echo "Get metadata from bundle" identity = $it getIdentity version = $it getVersion name = "$identity - $version" url = $it getUrl mimetype = $it getMimetype echo "Bundle exists?" if { (coll:first ($workspace la "(&(Bundle-SymbolicName=$identity) (Bundle-Version=$version))")) } { echo "$name already exists" } { echo "Create artifact for bundle" $workspace ca [ artifactName="$name" url="$url" mimetype="$mimetype" Bundle-SymbolicName="$identity" Bundle-Version="$version" ] } } ! echo "Commit workspace" $workspace commit exit 0 Get metadata from bundle Create artifact for bundle Bundle exists? Commit workspace Quit For each bundle no yes next bundle done
- 25. Example •Amdatu showcase in local git repo •post-‐commit or post-‐receive hook •Jenkins •post build step to deploy to ACE •ACE •deploys artifacts to targets
- 26. Demo • With the Amdatu Showcase (extended) demo
- 27. Cloud OSGi services! http://www.amdatu.org/ Eclipse OSGi plugin! http://bndtools.org/ ! Provisioning Server! http://ace.apache.org/! That’s us! http://luminis.eu/ Demo code! bitbucket.org/amdatu/showcase/