[00:58] its over for today ? === AlienDev_ is now known as AlienDev [02:51] is there a pc suites for ubuntu? [02:54] anyone in here? [02:54] !classroom [02:54] The Ubuntu Classroom is a project which aims to tutor users about Ubuntu, Kubuntu and Xubuntu through biweekly sessions in #ubuntu-classroom - For more information visit https://wiki.ubuntu.com/Classroom === emma is now known as em === _LibertyZero is now known as LibertyZero === Igorot is now known as Knightlust [07:16] Hello? === daker_ is now known as daker === msnsachin12 is now known as msnsachin [11:43] where is the class [12:56] the class will be here in about 3 hours from now (the first class of the day about QML. chat and ask questions in #ubuntu-classroom-chat === fabio_ is now known as fabio- [15:53] HELLO EVERYBODY! Welcome to Day 4 of Ubuntu Developer Week! [15:53] How are you all doing? [15:53] hey dholbach, hi everyone [15:53] We still have 7 minutes left until we start, but I just wanted to bring up a few organisational bits and pieces first: [15:53] - If you can't make it to a session or missed one, logs to the sessions that already happened are linked from https://wiki.ubuntu.com/UbuntuDeveloperWeek [15:54] - If you want to chat or ask questions, please make sure you also join #ubuntu-classroom-chat [15:54] - If you ask questions, please prefix them with QUESTION: [15:54] ie: QUESTION: What does oSoMoN stand for? [15:54] :) [15:54] - if you are on twitter/identi.ca or facebook, follow @ubuntudev to get the latest development updates :) [15:54] ;) [15:54] that's it from me [15:55] you still have 5 minutes until oSoMoN will kick off today and talk about QML App development goodness! [15:55] Have a great day! [15:55] dholbach, bye [15:55] thanks for the introduction dholbach [15:56] let’s wait for 18:00 sharp and we’ll start === Cyberkilla is now known as CK|Spectating === ChanServ changed the topic of #ubuntu-classroom to: Welcome to the Ubuntu Classroom - https://wiki.ubuntu.com/Classroom || Support in #ubuntu || Upcoming Schedule: http://is.gd/8rtIi || Questions in #ubuntu-classroom-chat || Event: Ubuntu Developer Week - Current Session: From idea to app in no time with QML - Instructors: oSoMoN [16:00] let’s get this rolling… [16:00] Logs for this session will be available at http://irclogs.ubuntu.com/2011/07/14/%23ubuntu-classroom.html following the conclusion of the session. [16:00] let’s get this rolling… [16:01] Hi everyone! [16:01] In this session I’m gonna show you how to write a cool application in QML in no time (in Ubuntu of course!) [16:01] I’ll first start with a super quick introduction to QML and pointers to documentation for complete beginners, and then I’ll move on to writing an actual application step by step. [16:01] If you have contextual questions don’t hesitate to ask, myself and others (I hope) will be happy to answer as best as we can. [16:01] If a question is too general, keep it for the end of the session so as not to disrupt the flow too much, we’ll save some time at the end to answer them, and eventually if we go overflow the allocated time we can take the discussions offline. [16:01] So, on to the topic! [16:01] There’s a very good introduction of what QML is at http://doc.qt.nokia.com/qdeclarativeintroduction.html. [16:01] There’s also very good documentation, it’s one of the strong points of Qt in general. [16:02] There are official tutorials as well as plenty of unofficial ones on the interwebs. [16:02] Basic tutorial: http://doc.qt.nokia.com/qml-tutorial.html [16:02] Advanced tutorial: http://doc.qt.nokia.com/qml-advtutorial.html === Hutley_ is now known as Hutley [16:02] Here is a non exhaustive list of advantages that make it a great language to develop applications for Ubuntu: [16:02] very good documentation [16:02] implicit animations [16:02] property bindings [16:02] states [16:02] extensible in C++ or Python (using PySide) [16:02] supports touch input (e.g. kinetic scrolling for lists) [16:03] First let’s install the packages we’re going to need: `sudo apt-get install qtcreator qt4-qmlviewer libqtwebkit-qmlwebkitplugin` [16:03] My purpose with this session is not to teach you QML from the very beginning, there’s plenty of great documentation out there for that. [16:03] The idea is more to show you how to use it to write a real application for Ubuntu, not the typical and useless Hello World. [16:04] For years I’ve been using liferea, a gnome feed reader, to aggregate and read RSS feeds. It does the job, but it’s been getting incredibly slow, to the point it takes more than a minute to start and display its main window, and that’s not even checking for new feeds. Not acceptable, let’s see if we can write a replacement in QML. [16:04] For the sake of the example it’s going to aggregate all feeds from Planet Ubuntu (http://planet.ubuntu.com/). [16:04] The desired layout is basic: a list of all recents entries in a left pane, and a view of the currently selected entry in a right pane. [16:04] I’ll guide you through the code step by step, you can find it in the following bzr branch: lp:~osomon/+junk/qml-feedreader. [16:05] Each revision in the branch corresponds to a step. For convenience, you can browse the revisions and see the diffs between each revision at http://bazaar.launchpad.net/~osomon/+junk/qml-feedreader/changes. [16:05] Let’s fire up Qt Creator, and click on "Create Project". [16:05] Select "Qt Quick Project" > "Qt Quick UI". [16:05] Let’s call it "feedreader" and create it in e.g. "~/dev/qml". Then click "Next" and then "Finish". [16:05] (if I’m pasting too fast, someone please tell me and I’ll slow down) [16:06] Qt Creator created a skeleton application, which we can already run. [16:06] We will replace this code incrementally to implement the functionality of our feed reader. [16:06] Let’s get started. [16:06] http://bazaar.launchpad.net/~osomon/+junk/qml-feedreader/revision/1 [16:06] We’re starting by adding to the root element an XmlListModel that will be responsible for fetching the data from the RSS feed and exposing this data in the form of properties for each item in the model, using XPath queries to extract the relevant data. [16:07] Then we’re adding a ListView to display the data from the list model. The delegate is the component responsible for displaying one item in the list, it is automatically instantiated and positioned correctly by the list view. [16:07] At this point we can already run this code, and tada! We get a list of the latest entries for the RSS feed. [16:07] As you can see, you can use the mouse wheel and do kinetic scrolling on the list. All of this comes for free with the ListView element. [16:07] It’s rather ugly and not very readable as no layout is applied to the delegates. We are going to remedy this in the next step. [16:08] http://bazaar.launchpad.net/~osomon/+junk/qml-feedreader/revision/2 [16:08] Instead of a simple Text element, we make the delegate a Rectangle containing two rows of text. [16:08] The first line displays the title of the entry, and the second line the publication date. We tweak the font size, add an ellipsis, margins and spacing. [16:09] It is much better already, but we can improve it visually by adding alternating colors to the rows. [16:10] http://bazaar.launchpad.net/~osomon/+junk/qml-feedreader/revision/3 [16:11] The SystemPalette element exposes a palette of colors for the current theme, which allows us to give a consistent look’n’feel to our application. [16:11] As you can see, an interesting feature of QML is that we can assign an anonymous function to the value of a property, for non-trivial computations. This of course preserves property binding, meaning that whenever the value of a property used inside the body of this function changes, the property is updated in a transparent manner. [16:13] http://bazaar.launchpad.net/~osomon/+junk/qml-feedreader/revision/4 [16:13] QML items are not mouse-aware by default, but it is very easy to fix this: we just add an invisible MouseArea that covers the area of the item, and we can now connect to the various signals it emits when it receives mouse events. [16:14] In this case, clicking an item in the list will make it the current item. It will be highlighted with a different color for visual feedback. [16:15] http://bazaar.launchpad.net/~osomon/+junk/qml-feedreader/revision/5 [16:15] We now want to display the contents of the current entry in a pane to the right of the list. [16:16] The contents are stored in the 'description' attribute, so we need to add it to the XmlListModel. [16:17] The contents are HTML, so we are going to display them in a WebView, which is basically a component embedding webkit to render a web page or arbitrary HTML. This requires an extra import. [16:17] As you can see here, property binding is a very powerful feature: unlike in imperative programming, I do not have to set the value of the 'html' property to the contents whenever I change the current entry in the list. All I need to do is bind it, and done! [16:17] http://bazaar.launchpad.net/~osomon/+junk/qml-feedreader/revision/6 [16:18] You may have noticed that the web view cannot be scrolled. This can be annoying if the contents don’t fit in the frame. Putting the WebView inside a Flickable element fixes this. [16:18] The contents can now be scrolled vertically by clicking and dragging them. Note that a limitation of the Flickable element it that unfortunately it currently doesn’t handle mouse wheel events (this could be overcome by writing a custom Flickable element in C++, but is not the point of today’s session). [16:19] http://bazaar.launchpad.net/~osomon/+junk/qml-feedreader/revision/7 [16:20] We now add a one-pixel separator between the list view and the webview. [16:20] Note how QML stacks sibling elements: the last on top of the others. Which is why we add the separator at the end, after the listview and the flickable. [16:21] http://bazaar.launchpad.net/~osomon/+junk/qml-feedreader/revision/8 [16:21] To handle keyboard focus properly, we make the top-level element a focus scope, meaning that when it gets the focus it transfers it to one and only one of its children (in our case, the listview). [16:22] http://bazaar.launchpad.net/~osomon/+junk/qml-feedreader/revision/9 [16:22] We now add a fancy animation on the opacity of the webview whenever we click an entry in the list: the web view fades out, then the index is actually changed, then the webview fades in again. [16:23] This is achieved with a sequential animation; by default animations in QML are run in parallel. [16:24] http://bazaar.launchpad.net/~osomon/+junk/qml-feedreader/revision/10 [16:25] Our webview can be scrolled, that’s nice, but we don’t have any visual indicator of the position within the document. [16:25] Let’s add a simple scrollbar that will act as a visual clue (it won’t be clickable to actually change the position). [16:26] The scrollbar is made up of two rectangles: the first one is a semi-transparent background, and the second one is the handle of the scrollbar. [16:26] The scrollbar defines custom properties for the position and the pageSize, those are bound the usual way, so whenever the position of the contents inside the flickable is updated, the properties of the scrollbar are updated accordingly. [16:27] http://bazaar.launchpad.net/~osomon/+junk/qml-feedreader/revision/11 [16:28] This scrollbar is very nice, how about we extract it to a separate file so as to make it a reusable component? [16:28] QML files representing components in the same directory as the main one are discovered automatically, no need to import anything else. [16:28] We name the file "ScrollBar.qml", and the component can be used under the name 'ScrollBar'. Easy, heh? [16:29] In the external component, we remove all references to the flickable. The properties of the scrollbar will be set wherever it is instantiated. This ensures our component is truly reusable and doesn’t rely on the implicit presence of other components. [16:30] http://bazaar.launchpad.net/~osomon/+junk/qml-feedreader/revision/12 [16:30] Now that we’ve done that, it is trivial to add a scrollbar to the listview as well. Almost too easy :) === a is now known as Guest32986 [16:31] http://bazaar.launchpad.net/~osomon/+junk/qml-feedreader/revision/13 [16:32] For the final touch, let’s add a header to the right pane, displaying two lines: one with the title of the current entry, and the second one with a link to the original blog entry. [16:33] As a bonus, we can very easily make the link clickable by using a MouseArea and invoking the handy helper function "Qt.openUrlExternally(…)". [16:34] That’s it for the code folks! [16:34] We have written a full-fledged real-word application in about half an hour and under 200 lines of code (158 lines if we exclude copyright and license headers and blank lines). [16:35] real-world [16:35] Here is a screenshot of the application running: http://tilloy.net/olivier/qml/qml-feedreader.png, for those who haven’t tested it. [16:35] This is only a quick example of what QML can help you build, it’s by no means a complete overview of how rich the framework is. [16:36] The following page has lots of very interesting pointers to resources and documentation to take in on from here, including extending QML components with C++: http://doc.qt.nokia.com/qtquick.html [16:37] It looks like I went really fast (maybe too fast?), let’s open the floor for questions [16:37] !q [16:38] any questions? should I go back to one of the steps and explain in more details? [16:43] abhinav_singh asked: can you please give some links for including QML components with python [16:44] shadeslayer asked: what is the ideal way of communicating with DBus using QML ? [16:44] shadeslayer: normally you create c++ classes that implement the DBUS interface and then you expose them to QML. to expose them you have two possibilities [16:45] shadeslayer: one is to use QDeclarativeContext::setContextProperty (assuming you're not using qmlviewer) [16:46] shadeslayer: the other is to create a plugin which exposes them, and then use the import directive in QML to import that plugin. after that you can use the classes exported by the plugin in QML. there's some good docs for that, let me find them [16:47] shadeslayer: http://doc.qt.nokia.com/4.7-snapshot/qml-extending.html [16:47] one could also probably write a generic DBus QML component that allows connecting to whatever object/interface on a given bus, but that may be overkill for most use-cases [16:48] shadeslayer: QtCreator has also some templates to create these plugins easil [16:48] y [16:49] if we’re done with questions, I’d like to mention two cools projects that use QML [16:49] the first one is unity-2d [16:50] the UI is almost entirely written in QML, and it makes it super easy and fun to prototype new ideas [16:50] There are 10 minutes remaining in the current session. [16:51] and the second one is an experiment of mine, a limited clone of the Ubuntu Software Center, written in QML and Python [16:51] this one is more like a playground at the moment [16:52] but you can already get the code form S-C’s trunk (lp:software-center) and play with it by running ./software-center-qml [16:52] that’s all I got for you today, we have 10 minutes left, more questions maybe? [16:54] tsimpson asked: have there been any comparisons of the speed of native (C++) apps compared to QML apps? [16:55] tsimpson: I recall reading a blog post about it, let me see if I can find the link for you [16:55] There are 5 minutes remaining in the current session. [16:56] tsimpson: http://labs.qt.nokia.com/2011/05/31/qml-scene-graph-in-master/ has some clues about performance, but apparently not compared with native C++ apps [16:58] tsimpson: look at the numbers at the end of the article [16:59] looks like it’s time to wrap up, thanks everyone for following and the interesting questions === ChanServ changed the topic of #ubuntu-classroom to: Welcome to the Ubuntu Classroom - https://wiki.ubuntu.com/Classroom || Support in #ubuntu || Upcoming Schedule: http://is.gd/8rtIi || Questions in #ubuntu-classroom-chat || Event: Ubuntu Developer Week - Current Session: Deploy your App to the cloud, Writing Ensemble formulas 101 - Instructors: kim0 [17:01] Logs for this session will be available at http://irclogs.ubuntu.com/2011/07/14/%23ubuntu-classroom.html following the conclusion of the session. [17:01] Good morning, good afternoon and good evening everyone [17:02] I'm here to introduce you to Ensemble → https://ensemble.ubuntu.com/ [17:02] Ensemble is a cloud orchestration framework [17:02] I am assuming you know what cloud is, and maybe played around a bit with Amazon ec2 [17:03] if you'd like me to provide a quick intro about that as well .. let me know [17:03] just ping me in #ubuntu-classroom-chat or leave a question [17:03] I will be hosting a demo of Ensemble (yay!) [17:04] You can login to this shared screen session → ssh guest@ec2-107-20-18-151.compute-1.amazonaws.com [17:04] password: guest [17:04] or you may view the web UI → https://ec2-107-20-18-151.compute-1.amazonaws.com/ [17:05] So .. as a developer, why would Ensemble interest you ? [17:05] - Ensemble enables you to quickly deploy your code to the cloud for testing/qa purposes [17:05] - You're able to easily test various different versions of operating systems [17:06] - And most importantly .. If deployment instructions for your application are not too simple, Ensemble provides an easy and consistent way [17:06] for your users to deploy your application [17:06] It's like having that big red "easy" button to hit, to deploy your code [17:07] As a developer, you're also ensured that users have deployed your application in exactly the way you would recommend [17:07] If there is any questions so far .. shoot [17:08] Let me jump over a couple of ensemble concepts quickly [17:08] then we'll do the demo [17:08] this session should be short and sweet [17:08] - Ensemble concepts [17:08] * The first thing to note, is that since Ensemble was written in the cloud age [17:09] it does not really care about "servers" .. [17:09] rather it focuses on "services" [17:09] services being .. [17:09] mysql : a database service [17:09] memcached : a high performance caching service [17:09] munin : a monitoring service [17:09] and so on and so forth [17:09] You application, of course interacts with many of those services [17:10] * The second important concept is that Ensemble completely "encapsulates" those services [17:10] that is, if you have no idea how to get munin running [17:10] if you ask ensemble to deploy it, you would have it running within minutes [17:11] and you can connect it (read: relate it) to other services [17:11] and it would start graphing performance metrics from all around your infrastructure [17:11] you do not need to know how to control munin, it is encapsulated [17:12] * The third important concept, is that with Ensemble services are "composable" [17:12] that is, services have well defined interfaces [17:12] such that you can connect/relate many services together .. to form a large infrastructure [17:12] you can replace infrastructure components with others .. such as replace mysql with pgsql if you so wish [17:13] and if both of them implement the same interface! [17:13] In the future, Ensemblse would even handle backing up and migrating your data! [17:13] Cool! [17:13] Enough talk .. let's jump to demo land [17:14] If there's any questions pre demo .. shoot [17:14] * kim0 waits a minute .. and prepares demo land [17:17] = demo begin = [17:17] Please make sure you're logged into the shared ssh session or web UI [17:17] for instructions, scroll up [17:17] Alright! let's get started [17:18] The very fist step, is as I just did in the shared screen [17:18] ensemble bootstrap [17:18] What this does, is it starts a "management" node for Ensemble [17:18] this is the brains for the deployment [17:18] it is a utility node [17:19] of course ec2 needs some time to create this node .. [17:19] so I need to check it is available and ready before proceeding [17:19] I can do this with [17:19] ensemble status [17:20] The node seems to be bootstrapping [17:21] While the node is bootstrapping [17:21] I would like to introduce "formulas" [17:22] Formulas, are Ensemble's way of codifying the experience of deploying code and orchestrating the full service [17:22] So, if you would like to deploy a mysql service [17:22] You would need a mysql formula [17:22] this is the same for any other service [17:23] and if you as a developer, would like your application to be deployable by Ensemble, you would need to write a formula for it [17:23] the "very cool" part! [17:23] is that formulas are language indepndant [17:23] that is, you do not need to learn yet another programming language [17:24] to write those formulas, formulas can be written in python, bash, php, c++ or whatever! [17:24] Very well .. the bootstrap has of course finish bootstrapping [17:24] I will paste ensemble commands and output here for archiving purposes [17:24] $ ensemble status [17:24] 2011-07-14 17:24:16,265 INFO Connecting to environment. [17:24] machines: [17:24] 0: {dns-name: ec2-50-17-153-3.compute-1.amazonaws.com, instance-id: i-f3c13e92} [17:25] services: {} [17:25] 2011-07-14 17:24:18,137 INFO 'status' command finished successfully [17:25] machine number "0" is our bootstrap node [17:25] let us now quickly deploy a wordpress service and a drupal application [17:25] How hard do you think that is? [17:26] Here it is [17:26] ensemble deploy --repository=. drupal mycms [17:26] This deploys an instance of "drupal" .. calls the instance "mycms" [17:27] $ ensemble deploy --repository=. mysql mydb [17:27] This also deploys mysql, calling it mydb! [17:27] doesn't really get much simpler than that! [17:27] let's check out ensemble status now [17:27] $ ensemble status [17:27] 2011-07-14 17:27:34,085 INFO Connecting to environment. [17:27] machines: [17:27] 0: {dns-name: ec2-50-17-153-3.compute-1.amazonaws.com, instance-id: i-f3c13e92} [17:27] 1: {dns-name: ec2-107-20-30-230.compute-1.amazonaws.com, instance-id: i-0537c864} [17:27] 2: {dns-name: ec2-50-19-190-104.compute-1.amazonaws.com, instance-id: i-e537c884} [17:27] services: [17:28] mycms: [17:28] formula: local:drupal-9 [17:28] relations: {} [17:28] units: [17:28] mycms/0: [17:28] machine: 1 [17:28] relations: {} [17:28] state: null [17:28] mydb: [17:28] formula: local:mysql-97 [17:28] relations: {} [17:28] units: [17:28] mydb/0: [17:28] machine: 2 [17:28] relations: {} [17:28] state: null [17:28] 2011-07-14 17:27:35,995 INFO 'status' command finished successfully [17:28] Let us quickly check out the meaning of this status message [17:28] In the machines section .. we now have 3 machines .. 0 1 and 2 [17:28] In the services section, we have two services deployed [17:28] mycms and mydb [17:29] You can see mycms (drupal) is running on machine 1 (from the machines section, it's url is ec2-107-20-30-230.compute-1.amazonaws.com) [17:29] and mydb (mysql) is running on machine 2 [17:30] Let me know paste an updated status [17:30] $ ensemble status [17:30] 2011-07-14 17:29:44,206 INFO Connecting to environment. [17:30] machines: [17:30] 0: {dns-name: ec2-50-17-153-3.compute-1.amazonaws.com, instance-id: i-f3c13e92} [17:30] 1: {dns-name: ec2-107-20-30-230.compute-1.amazonaws.com, instance-id: i-0537c864} [17:30] 2: {dns-name: ec2-50-19-190-104.compute-1.amazonaws.com, instance-id: i-e537c884} [17:30] services: [17:30] mycms: [17:30] formula: local:drupal-9 [17:30] relations: {} [17:30] units: [17:30] mycms/0: [17:30] machine: 1 [17:30] relations: {} [17:30] state: started [17:30] mydb: [17:30] formula: local:mysql-97 [17:30] relations: {} [17:30] units: [17:30] mydb/0: [17:30] machine: 2 [17:30] relations: {} [17:30] state: started [17:30] 2011-07-14 17:29:46,435 INFO 'status' command finished successfully [17:31] Now you can the state of both services is "started" [17:31] which means they have been successfully installed and started [17:31] Note however that till now, the two services are deployed "separately" [17:31] that is mysql knows nothing about drupal and vice versa [17:31] The big bang (a ha) moment happens when you connect both services together! [17:31] let's do just that [17:32] Here is how I just did it [17:32] $ ensemble add-relation mycms mydb:db [17:32] 2011-07-14 17:32:03,640 INFO Connecting to environment. [17:32] 2011-07-14 17:32:04,759 INFO Added mysql relation to all service units. [17:32] 2011-07-14 17:32:04,760 INFO 'add_relation' command finished successfully [17:32] I am using add-relation to connect the two services together [17:32] Once the connection happens [17:33] mysql recognizes drupal needs a database service [17:33] mysql creates a new database for drupal [17:33] sends over the connection information (ip, username, password) needed to connect to the newly created database! cool! [17:33] drupal receives this information, configures itself to connect to that service [17:34] the end result .. with that single command === zyga is now known as zyga-afk [17:34] and with Ensemble in the background [17:34] you have deployed a multi-tier service [17:35] As we just mentioned the url for the mycms machine is http://ec2-107-20-30-230.compute-1.amazonaws.com/ensemble/ [17:35] and you can indeed hit that url with your browser right now [17:35] and you should get drupal waiting for you .. hurray [17:36] I'd like to quickly show you as well .. the formula for drupal [17:36] i.e. how simple it is to write such a formula [17:36] I chose to write this formula in bash, however as mentioned, you can use any language you fancy! [17:38] The install hook (what runs to install the service) is now shown in the shared screen [17:38] I am however .. pasting it as well for archiving purposes [17:38] #!/bin/bash [17:38] set -eux # -x for verbose logging to ensemble debug-log [17:38] ensemble-log "Installing drush,apache2,php via apt-get" [17:38] apt-get -y install drush apache2 php5-gd libapache2-mod-php5 php5-cgi mysql-client-core-5.1 [17:38] a2enmod php5 [17:38] /etc/init.d/apache2 restart [17:38] ensemble-log "Using drush to download latest Drupal" [17:38] cd /var/www && drush dl drupal --drupal-project-rename=ensemble [17:39] As you can see, it simply uses apt-get to install some packages, enables php, restarts apache [17:39] and then uses "drush" the drupal shell, to download a fresh version of drupal [17:39] it's interesting to see that ensemble does NOT force you to only use ubuntu packages [17:39] you can mix and match like I just did [17:40] as a developer, you can grab any code branch and build it and mix that with package installations, if you so wish [17:40] Very well .. [17:40] remember the magic that happened when we connected the two services together [17:40] the "add-relation" command [17:40] let us see the code that runs from drupal's perspective [17:41] I have just displayed it on the shared screen [17:41] I will paste it in chunks [17:41] #!/bin/bash [17:41] set -eux # -x for verbose logging to ensemble debug-log [17:41] hooksdir=$PWD [17:41] user=`relation-get user` [17:41] password=`relation-get password` [17:41] host=`relation-get host` [17:41] database=`relation-get database` [17:42] these last 4 lines, read various settings from Ensemble provided communication channels [17:42] they read: user, password, host, database [17:42] these settings are provided by the mysql service upon establishing the connection. [17:42] drupal reads them, to configure itself to connect to that DB [17:43] let us see how the connection happens [17:43] ensemble-log "Setting up Drupal for the first time" [17:43] cd /var/www/ensemble && drush site-install -y standard \ [17:43] --db-url=mysql://$user:$password@$host/$database \ [17:43] --site-name=Ensemble --clean-url=0 [17:43] easy enough! [17:43] we just use drush to install drupal passing the need parameters we just consumed [17:43] What is really important to notice here [17:44] is that I might have never touched mysql before [17:44] I do not have to know how it works or how to configure it [17:44] or I cared about, was the Ensemble provided interface .. those 4 parameters in this case [17:45] The actual script is slightly longer, since it checks whether or not this is first time drupal is being set up [17:45] i.e. are we starting the very first drupal node, or just scaling it up [17:45] oh yeah .. because scaling it up is as simple as [17:45] ensemble add-unit mycms [17:45] yep .. that's it [17:46] So I hope this was a useful introduction to Ensemble [17:46] I'll provide a couple of pointers and answer question [17:46] questions* [17:46] You can read more about Ensemble at: https://ensemble.ubuntu.com/ [17:46] Documentation: https://ensemble.ubuntu.com/docs/ [17:46] Mailing list: https://lists.ubuntu.com/mailman/listinfo/ensemble [17:47] IRC Channel: #ubuntu-ensemble @ Freenode [17:47] we are a very welcoming community .. it's a party and everyone is invited :) [17:47] So start hacking on your own formula today! [17:47] You can see a list of existing formulas at: https://code.launchpad.net/principia [17:48] Our goal is to cover all of free software! [17:48] Alright .. taking questions [17:48] alexm asked: can emsemble be used to deploy outside the cloud? [17:48] alexm: Ensemble uses multiple "providers" to handle what to deploy to [17:49] ec2 cloud is currently the one that is ready, a provider for LXC (Linux container) is being worked on heavily [17:49] and myunderstanding is that it will be ready during this 11.10 cycle [17:49] you can also deploy to private clouds such as openstack or eucalyptus .. not sure how well tested that is, but should mostly work [17:50] Also, Ensemble is being currently integrated with Orchestra [17:50] the Ubuntu server hardware deployment tool [17:50] so you will be able to install to your own hardware farm as well [17:50] I hope that answers your question [17:51] There are 10 minutes remaining in the current session. [17:51] chadadavis asked: Does ensemble have upstart's concepts of services vs tasks. Backup seems more like a service, whereas migration more like a task. [17:51] Things are a bit too early in Ensemble development right now .. Currently everything is a service [17:52] however the dev team recognize the need that some operation have special needs [17:52] "machine services" are being debated [17:52] various types of services (or whatever they'd be called) can definitely arise [17:52] ahs3 asked: each service seems to be a separate machine; can i have multiple services on the same machine? [17:53] ahs3: good question .. With the LXC provider that will become possible [17:53] there is also design work currently to colocate chosen services together [17:53] interested code hackers are invited to hack on ensemble core to make this happen faster :) [17:53] #ubuntu-ensemble [17:54] Ensemble itself is written in python using twisted framework afaik [17:54] ahs3 asked: how do i find out what services are available? [17:54] ahs3: As mentioned this is the current list [17:54] https://code.launchpad.net/principia [17:54] this only started a few weeks back [17:54] so it is growing rapidly === janimo` is now known as janimo [17:55] I am more than ready to help anyone write his own first formula [17:55] just grab me (kim0) on #ubuntu-ensemble [17:55] and start hacking on your own formula :) [17:55]