Tosca-2 Issue: Deploying Bugzilla in the Cloud dianem@activestate.com Frank.Leymann@iaas.uni-stuttgart.de
Sample Web Application: Bugzilla as a Service – a composite “service” that is made up of “nodes“ – “Nodes” • Perl Application • Web Server • Database - MySQl • MTA – MailTransferAgent – Each “node” needs a Operating System – Each “node” could be on a separate instance on a different cloud host
Topology If “Operating System” is a Node attribute, rather than a type of Node Perl Environment Perl Modules Bugzilla Web Server DBMS MTA
Install Process
Configure: Map and Bind “node” relationships Web server, DBMS, Bugzilla as a MTA, Perl App Env Service Each Node needs to be made aware of where the other nodes reside
Installing Bugzilla • Download Bugzilla 4.0.2. – it needs to be downloaded and unpacked explicitly. • Apply patches – for the version.pm issue and PSGI support. • Create an automatic configuration file – containing the database credentials – default admin information. • Run checksetup.pl multiple times to – create the initial configuration files and – set up the database schema. More details: http://www.activestate.com/blog/2011/12/running-bugzilla-cloud
Additional Build Plan Details • Resource Allocation – Memory Allocation – Number of Instances • Other considerations: – Name of Service – Fixed or Auto-Scaling
Resource Allocation • Memory Allocation • Number of Instances • Other considerations: – Name of Application – Fixed or Auto-Scaling assuming this would go into the Service Template and that all of these concepts are contained there
Recommend
More recommend
