[04:19] hello [04:19] i have a question [04:19] if i way ask in here [04:19] coolmariorocks: you probably want to ask in #ubuntu (this channel is for classes) [04:20] ok thanks pleia2 [05:10] HI [05:11] evolution + exchange 2010 is not showing folder ? please help me ? [05:11] evolution + exchange 2010 is not showing folder ? please help me ? [05:14] do you have any documentation for file server in linux? === Guest5698 is now known as zumbi === daker_ is now known as daker === mike is now known as Guest40475 === _LibertyZero is now known as LibertyZero [12:57] when will start the cloud session === med_out is now known as medberry [13:22] ? [13:22] help [13:27] cloud session starts at 16:00 UTC === paulw is now known as Guest32626 [15:08] #ubuntu-classroom-cha [15:08] #ubuntu-classroom-chat [15:08] Sorry... === Wordpad2 is now known as Amivit [15:27] test [15:59] test === 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 Cloud Days - Current Session: Getting started with Ensemble - Instructors: kim0 === Hugo is now known as Guest19460 [16:00] Logs for this session will be available at http://irclogs.ubuntu.com/2011/07/25/%23ubuntu-classroom.html following the conclusion of the session. [16:00] Hello, Good morning, good evening and good afternoon [16:01] Welcome to Ubuntu Cloud Days! [16:01] This is the second UCD ever [16:01] This event will be run for two days (today and tomorrow) [16:01] You can find more information regarding the event on https://wiki.ubuntu.com/UbuntuCloudDays/ [16:02] It would be great to spread the news and let your friends join in [16:02] This is a great chance to get introduced to new ubuntu related server and cloud technologies [16:02] as well as a chance to connect to developers and active community members [16:02] Alright .. [16:03] Let's get started then [16:03] At any time you can "ask a question" [16:04] this is done by prepending your question with QUESTION: .. example .. "QUESTION: what is xxx?" [16:04] a bot will pick up the question, and the instructor will answer it at a suitable time [16:05] So .. this session is for Ensemble [16:05] Take a moment to check out: https://ensemble.ubuntu.com/ [16:06] Ensemble is a cloud orchestration framework [16:06] Since cloud layers an API over compute resources [16:06] many compute resources such as servers, are more and more being regarded as disposable [16:06] people fire up servers, use them for an hour and destroy them [16:07] this is valid for both public and private clouds [16:07] as such, it would be pretty good to think at a higher level than a "server" [16:07] namely to think at the "service" level [16:07] this is one of the main concepts of Ensemble [16:08] Let's quickly discuss a few key concepts about Ensemble [16:08] 1- Ensemble focuses on the higher level concept of "Services" rather than "servers" [16:08] Examples of a "service" would be [16:08] - MySQL [16:08] - Memcached cluster [16:09] - Munin: as a monitoring service [16:09] - Bacula: as a backup service [16:09] and so on [16:09] 2- The second important concept is that Ensemble completely "encapsulates" those services [16:09] that is, if you have no idea how to get munin running [16:10] if you ask ensemble to deploy it, you would have it running a minute or two [16:10] and you can connect it (read: relate it) to other services [16:10] and it would start graphing performance metrics from all around your infrastructure [16:10] you do not need to know how to control munin, it is encapsulated [16:11] 3- The third important concept, is that with Ensemble services are "composable" [16:11] that is, services have well defined interfaces [16:11] such that you can connect/relate many services together .. to form a large infrastructure [16:11] you can replace infrastructure components with others .. such as replace mysql with pgsql if you so wish [16:11] and if both of them implement the same interface! [16:12] so .. [16:13] Ensemble enables layering a high level API over "services" and allows composing sophisticated infrastructures from that .. easily, consistently and without worrying about any details! [16:13] If you have any questions [16:13] now would be a good time to ask [16:13] remember to prepend any question with "QUESTION:" [16:14] I will now prepare the demo environment, that should clear up things a bit [16:15] For anyone wanting to follow along with the demo [16:15] Please ssh as user guest to the following machine [16:15] ssh guest@ec2-50-19-23-213.compute-1.amazonaws.com [16:15] password: guest [16:16] you will get a read-only view to a shared screen session [16:17] I will start the demo [16:17] I will be pasting commands and output text in this session as well, for archival purposes [16:18] The very first step we do is: [16:18] $ ensemble bootstrap [16:18] 2011-07-25 16:17:22,569 INFO Bootstrapping environment 'sample' (type: ec2)... [16:18] 2011-07-25 16:17:23,637 INFO 'bootstrap' command finished successfully [16:18] What the ensemble bootstrap does, is it starts a "management node" if you will [16:18] that is used to control our cloud deployment [16:19] let's check out the files available in the current directory [16:19] $ ls [16:19] byobu-classroom drupal mysql [16:19] byobu-classroom: setup scripts for the shared screen session you are see'ing .. This is not related to Ensemble [16:19] drupal: Ensemble drupal formula [16:19] mysql: Ensemble mysql formula [16:20] What is a formula you ask ? [16:20] A formula holds instructions for Ensemble on how to install and manage a service [16:21] that is .. the drupal formula, tells Ensemble how to install drupal, how to connect it to the database, how to create DB tables, how to configure a drupal website behind a load balancer ...etc [16:21] It is the experience of devops .. distilled .. into a "formula" that everyone can use [16:21] This is one of the great reasons "why use Ensemble" .. [16:22] Your deployment, not only becomes FAST, repeatable but also, you get the experience of the Ensemble community [16:22] all working for you .. without you even knowing about it (if you so choose) [16:22] alright .. [16:22] Let's deploy MySQL [16:22] jump to the screen session [16:24] The command to deploy a production mysql database is [16:24] $ ensemble deploy --repository=. mysql mydb [16:24] Let's break down this command and understand what it does [16:24] ensemble deploy → Asking Ensemble to deploy a service [16:25] --repository = . → Mentioning to Ensemble that the formulas are available in the current directory [16:25] mysql mydb → Deploy the formula "mysql" as a service called "mydb" [16:25] let's quickly paste the output of the command [16:25] $ ensemble deploy --repository=. mysql mydb [16:25] 2011-07-25 16:22:51,307 INFO Connecting to environment. [16:26] 2011-07-25 16:22:54,857 INFO Formula deployed as service: 'mydb' [16:26] 2011-07-25 16:22:54,859 INFO 'deploy' command finished successfully [16:26] So .. deploy .. finished successfully [16:26] similarly .. let's deploy the "drupal" formula .. as "mywebsite" [16:26] $ ensemble deploy --repository=. drupal mywebsite [16:26] 2011-07-25 16:23:04,117 INFO Connecting to environment. [16:26] 2011-07-25 16:23:05,167 INFO Formula deployed as service: 'mywebsite' [16:26] 2011-07-25 16:23:05,168 INFO 'deploy' command finished successfully [16:26] This should be very familiar [16:27] Let us check the status of our deployment [16:27] We use the "ensemble status" command for that [16:28] Here is the command and its output [16:28] $ ensemble status [16:28] 2011-07-25 16:27:37,395 INFO Connecting to environment. [16:28] machines: [16:28] 0: {dns-name: ec2-50-17-158-183.compute-1.amazonaws.com, instance-id: i-8dc16dec} [16:28] 1: {dns-name: ec2-184-72-129-61.compute-1.amazonaws.com, instance-id: i-35de7254} [16:28] 2: {dns-name: ec2-50-16-71-235.compute-1.amazonaws.com, instance-id: i-15de7274} [16:28] services: [16:28] mydb: [16:28] formula: local:mysql-98 [16:28] relations: {} [16:28] units: [16:28] mydb/0: [16:28] machine: 1 [16:28] relations: {} [16:28] state: started [16:28] mywebsite: [16:28] formula: local:drupal-9 [16:28] relations: {} [16:28] units: [16:28] mywebsite/0: [16:28] machine: 2 [16:28] relations: {} [16:29] state: started [16:29] 2011-07-25 16:27:38,635 INFO 'status' command finished successfully [16:29] Let's try to understand this output [16:29] In the "machines" section [16:29] We have 3 machines deployed [16:29] 0 1 and 2 [16:29] 0 is always the very first "bootstrap" node [16:29] 1 and 2 are the machines running mysql and drupal .. [16:29] Looking at the "services" section [16:29] we understand that we just deployed the service "mydb" .. remember this is the name we chose [16:30] the mydb service is running on machine "1" [16:30] and it is "started" [16:30] that is .. mysql has been installed and it is "ready" to be used [16:30] the same for drupal .. it is running on machine 2 and is started as well [16:30] It is interesting to note [16:30] that "relations: {}" [16:31] is empty [16:31] what this really means is [16:31] that the services deployed "mysql" and "drupal": [16:31] have not been "coupled" yet .. [16:31] i.e. mysql does not have the drupal database created yet ..etc [16:32] the magic of Ensemble and the very cool part .. is when you start connecting infrastrcuture pieces together [16:32] watching how all pieces jump together and a bigger system is created [16:32] let's connect those two components [16:33] The command to connect them (read: relate them) is [16:33] $ ensemble add-relation mydb:db mywebsite [16:33] We are adding a relation between mydb (our instance of mysql) and mywebsite (an instance of drupal) [16:34] It is extremely interesting what is happening at this instant [16:34] once this relation is established [16:34] both services start communicating and collaborating towards creating that bigger infrastructure [16:34] so .. mysql creates a database for drupal [16:35] it "sends over" the dabase details "username, password, DB name...etc" to the machine running drupal [16:35] drupal gets this configuration information [16:35] rewrites its configuration files to use this DB [16:35] creates its tables and configures the DB [16:35] the services have now been coupled! [16:36] Let's check the status [16:36] $ ensemble status [16:36] 2011-07-25 16:36:08,453 INFO Connecting to environment. [16:36] machines: [16:36] 0: {dns-name: ec2-50-17-158-183.compute-1.amazonaws.com, instance-id: i-8dc16dec} [16:36] 1: {dns-name: ec2-184-72-129-61.compute-1.amazonaws.com, instance-id: i-35de7254} [16:36] 2: {dns-name: ec2-50-16-71-235.compute-1.amazonaws.com, instance-id: i-15de7274} [16:36] services: [16:36] mydb: [16:36] formula: local:mysql-98 [16:36] relations: {db: mywebsite} [16:36] units: [16:36] mydb/0: [16:36] machine: 1 [16:36] relations: [16:36] db: {state: up} [16:36] state: started [16:36] mywebsite: [16:37] formula: local:drupal-9 [16:37] relations: {db: mydb} [16:37] units: [16:37] mywebsite/0: [16:37] machine: 2 [16:37] relations: [16:37] db: {state: up} [16:37] state: started [16:37] 2011-07-25 16:36:09,646 INFO 'status' command finished successfully [16:37] Notice how the "relations:" field now relates each component to the other [16:37] of course this could be a much larger system [16:37] i.e. there could be a load balancer front end service, a backup service, a monitoring service ...etc [16:37] But fundamentally .. it's the same [16:38] You deploy components .. connect them together and your good to go! [16:38] So .. our drupal instance is ready .. why not pay it a visit [16:39] Since drupal is running on machine 2 .. from the machines section .. this is the machin we need: ec2-50-16-71-235.compute-1.amazonaws.com [16:39] Go ahead and visit [16:39] http://ec2-50-16-71-235.compute-1.amazonaws.com/ensemble/ [16:39] Indeed drupal is there waiting for us! (woohoo) that was easy [16:39] Note how I might have deployed drupal without really knowing anything about how it needs to be deployed [16:40] and yet .. the deployment is done according to best practices of the Ensemble formula writers community [16:40] Awesome .. let's create a tiny first post [16:41] Alright .. we now have some content [16:41] Just refresh http://ec2-50-16-71-235.compute-1.amazonaws.com/ensemble/ [16:42] Now .. here comes another (OMG this is awesome) moment [16:42] What about your blog (or whatever service) suddenly becomes popular [16:42] you're slashdotted [16:42] You want to scale out [16:42] sure this has to be complex right! [16:43] let's check out how we can get this done [16:43] This is what we need [16:43] $ ensemble add-unit mywebsite [16:43] Yes that's it .. we have scaled out [16:43] let's quickly understand this command [16:44] add-unit : Adds a service unit to "mywebsite" [16:44] remember mywebsite is that name of our instance of the drupal formula [16:44] So [16:44] A new ec2 instance is created [16:44] It is important to note .. that Enesmeble uses plain "vanilla" ubuntu images [16:44] everything is installed and configured on the fly [16:44] the new node is configured as type "mywebsite" [16:45] what is really awesome is [16:45] since this new node, is of type mywebsite .. it already "knows" how to hook up to the surrounding services! [16:45] In this case .. only mysql .. but could be much more sophisticated [16:45] This is the DRY: Don't Repeat Yourself .. concept [16:46] let's again quickly check out status [16:46] $ ensemble status [16:46] 2011-07-25 16:46:17,368 INFO Connecting to environment. [16:46] machines: [16:46] 0: {dns-name: ec2-50-17-158-183.compute-1.amazonaws.com, instance-id: i-8dc16dec} [16:46] 1: {dns-name: ec2-184-72-129-61.compute-1.amazonaws.com, instance-id: i-35de7254} [16:46] 2: {dns-name: ec2-50-16-71-235.compute-1.amazonaws.com, instance-id: i-15de7274} [16:46] 3: {dns-name: ec2-50-16-175-35.compute-1.amazonaws.com, instance-id: i-73a50912} [16:46] services: [16:46] mydb: [16:46] formula: local:mysql-98 [16:46] relations: {db: mywebsite} [16:46] units: [16:46] mydb/0: [16:47] machine: 1 [16:47] relations: [16:47] db: {state: up} [16:47] state: started [16:47] mywebsite: [16:47] formula: local:drupal-9 [16:47] relations: {db: mydb} [16:47] units: [16:47] mywebsite/0: [16:47] machine: 2 [16:47] relations: [16:47] db: {state: up} [16:47] state: started [16:47] mywebsite/1: [16:47] machine: 3 [16:47] relations: [16:47] db: {state: up} [16:47] state: started [16:47] 2011-07-25 16:46:18,907 INFO 'status' command finished successfully [16:47] "mywebsite" now has two service unit instances mywebsite/0 and mywebsite/1 [16:47] the new node is running machine "3" which is ec2-50-16-175-35.compute-1.amazonaws.com [16:49] which means .. visiting http://ec2-50-16-175-35.compute-1.amazonaws.com/ensemble/ .. You should see the second drupal instance [16:49] of course if you'd like to further scale out .. you just keep add'ing more units .. that's all it takes [16:49] The mysql formula supports adding "slave" nodes [16:50] so you can scale your DB via adding more slave nodes [16:50] There are 10 minutes remaining in the current session. [16:50] alright .. time flies when you're having fun [16:50] What is really cool is that formulas can be written in ANY language [16:50] so bash, php, python .. whatever you fancy! [16:51] I will vim open the drupal formula in the screen session [16:51] Let me take any questions quickly [16:51] rwh asked: is there already a formula repo, or is this a service that's planned for the future? [16:51] great question [16:52] right now .. You can see formulas over at https://code.launchpad.net/principia [16:52] however a more integrated version is coming very soon .. [16:52] where you'll be able to search and install formulas just like you do with ppas [16:53] TeTeT asked: how much effort is it to write these relations? Isn't this more complicated than configuring the services themselves, e.g. how many units do I need to have so the initial investment in Ensemble pays off [16:53] Great question as well .. [16:53] It is pretty simple to write those relations [16:54] I just opened the db-relation-changed script for my drupal formula [16:54] as you can see it's a pretty simple bash script [16:54] that gets the database configuration details from ensemble .. then simply uses "sed" to render a template configuration file [16:55] I really like the fact that I do not have to wrestle with learning a new DSL configuration language [16:55] There are 5 minutes remaining in the current session. [16:55] I'll use the remaining minutes to let you know that you can find the Ensemble community at [16:55] #ubuntu-ensemble [16:55] all developers, formula writers and community members hang out there [16:56] our goal is to cover all of free software with Ensemble formulas [16:56] such that you're able to ensemble deploy whatever you fancy .. just like you apt-get install whatever you want today [16:56] Please join in .. and start writing and contributing formulas [16:57] it's very easy .. there is no special language to learn, and the community is extremely helpful [16:57] you can ask me (or others ) any questions in #ubuntu-ensemble (or #ubuntu-cloud) at any time [16:57] I hope this was useful and fun .. see you in a next session [16:58] Next session will be for cloud-init .. an Ubuntu originated cloud technology [16:58] the two sessions afterwards will be for Orchestra and its integration with Ensemble .. both great technologies being developed this cycle [16:58] and the final session will be for Eucalyptus v3 .. I hope you will enjoy the first day of UCD [16:58] Good bye === 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 Cloud Days - Current Session: Introduction to Cloudinit - Instructors: koolhead17 [17:00] Logs for this session will be available at http://irclogs.ubuntu.com/2011/07/25/%23ubuntu-classroom.html following the conclusion of the session. [17:00] hello everyone === medberry is now known as med_out [17:01] cloud-init is the Ubuntu cloud technology that enables a cloud instance to bootstrap itself and customize [17:02] we can do many operations on our instance before it boots up [17:04] its like adding an extra layer with more contents [17:04] lets talk about an example [17:05] you want an instance to have say apache installed automatically every time it boots up [17:05] you can simply use [17:05] packages: [17:05] - apache2 [17:05] and if you are using amazon ec2 web interface you can pass the parameter during launching the instance. [17:06] cloud-init works for openstack as well as eucalyptus [17:06] i will try to show you demo of the same if possible at the end [17:07] lets say you want to boot your instance with a specific timezone everytime the instance boots [17:07] you can simply define that using [17:07] timezone: US/Eastern [17:08] parameter in the file which you will be passing [17:10] now lets move to the example file we have http://bazaar.launchpad.net/~cloud-init-dev/cloud-init/trunk/view/head:/doc/examples/cloud-config.txt [17:11] line 7 apt_update: false [17:11] which means the parameter will be passed and at time instance launches automatic update will not happen [17:12] you can change it to apt_update: true and pass it during booting instance to enable it [17:12] similarly to enable/disable we have "apt_upgrade" [17:13] in the next line we can see it mentions about adding of repository. you can add your custom repository as well. [17:14] doing this will save some bandwidth in data-centre like environment :) [17:14] i will skip some of the examples from there :D [17:16] you can even run commands [17:16] line 205 [17:16] bootcmd: [17:16] - echo 192.168.1.130 us.archive.ubuntu.com > /etc/hosts [17:17] you can run commands like : [17:17] runcmd: - [ ls, -l, / ] [17:18] one of the feature which i find most exciting and am fighting with it is debconf_selections: | [17:19] byobu_by_default: system [17:20] enables byobu to all the uses by default once they login [17:22] the availability of cloud-init technology on all the cloud environment am working (openstack, eucalyptus, ec2) [17:23] you can find more info and detailed instruction at kim0 blog http://foss-boss.blogspot.com/search/label/cloud-init === Hugo is now known as Guest86346 [17:26] cloud-init comes pre installed if you are using ec2 [17:26] in case of openstack you need to install the package at time of preparing your cloud image [17:28] you can use euca tools in case of eucalyptus and openstack [17:29] on ec2 you can use web interface as well as via command line [17:29] so lets recap what all we have discussed so far [17:30] Some of the things cloud-init configures are: [17:30] setting hostname [17:30] generate ssh private keys [17:31] *which i forgot covering earlier :( [17:31] adding ssh keys to user's .ssh/authorized_keys so they can log in [17:31] setting up ephemeral mount points [17:32] to execute a command [17:32] runcmd: [17:32] automatic package update and upgrade [17:33] timezone setup [17:33] package installation [17:33] like apache2 [17:34] you can also see https://help.ubuntu.com/community/CloudInit [17:35] you people can take break now [17:35] the next session is about Orchestra [17:35] and it will be presented by 2 members from the server engineering team [17:36] thanks [17:37] it would have been more interesting with the demo which am unable to do :( [17:40] /msg classbot !q === daker is now known as daker_ [17:41] !y [17:41] Guest32626 asked: is cloud-init available for other linux distros? [17:42] Guest32626: it is available for Amazon's linux. [17:42] which is similar to fedora .. [17:42] it has been adopted by Amazon [17:42] and can easily be ported to other linux'es [17:44] Guest86346 asked: Is that possible to configure route table after retrieving metadata with cloud-init ? [17:45] yes its very much possible with the script :) [17:45] runcmd [17:46] one more important thing [17:46] we all are available at #ubuntu-cloud , our official cloud support channel for ubuntu. join us and hangout with ys [17:47] *us [17:47] and 1 more thing the mega session is coming nest [17:47] *next [17:47] about Orchestra and Ensemble .. Two pillar technologies for Ubuntu server in 11.10 [17:47] :) [17:48] Good bye .. and that's all :) [17:50] There are 10 minutes remaining in the current session. [17:55] There are 5 minutes remaining in the current session. === 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 Cloud Days - Current Session: Orchestra and Ensemble (part1) - Instructors: smoser [18:00] Logs for this session will be available at http://irclogs.ubuntu.com/2011/07/25/%23ubuntu-classroom.html following the conclusion of the session. [18:00] OK, lets get started [18:01] Hi, I'm Scott Moser, an Ubuntu Developer working on the Ubuntu Server Team. [18:01] If you're not familiar with the way classroom works, please see https://wiki.ubuntu.com/Classroom/ClassBot [18:01] hint: join #ubuntu-classroom-chat [18:02] Much of the Server Team's focus this cycle has been on deployment. That deployment really falls into 2 different categories [18:02] * ensemble: deploying and managing services on top of existing Ubuntu installs (or new cloud instances) [18:02] * orchestra: deploying Ubuntu onto "bare metal". [18:03] A few weeks ago, it was decided that we wanted to make Orchestra a "provider" for Ensemble. [18:03] What this means is that we wanted to allow Ensemble to deploy and manage "bare metal" machines the same way that it originally knew how to manage EC2 instances. Andres [RoAkSoAx] will talk more about that in the next session. [18:03] Like anybody else, we don't have enough hardware, and even less hardware with remotely controllable power switches and fast networks. [18:03] In order to get ourselves an environment that we could develop the "orchestra provider" for ensemble I put together "cobbler-devenv". [18:04]