[08:16] hi all [09:00] vciaglia: hey htere [09:01] vciaglia: I think you've pinged me earlier when I wasn't there [09:01] hi kim0, it was just to say "nice to meet you" ;) [09:02] hehe same here [09:02] i'm already hacking with ensemble [09:02] woohoo \o/ [09:02] need any help of some sort [09:03] vciaglia: are you working on some formula already? [09:04] kim0, no, i'm first discovering the tons of features of AWS [09:04] yeah that makes sense [09:05] Alright, I'm here to help .. if you have any questions, just ask away .. Have fun [09:05] really really interesting things ;) [09:07] kim0, ""EC2 error when attempting to delete security group ensemble-sample-0: Error Message: There are active instances using security group 'ensemble-sample-0'" ideas? [09:07] vciaglia: it seems u have instances running [09:07] use ensemble shutdown [09:08] let's see... [09:09] kim0, maybe a stupid question but ... in the environments.yaml [09:10] the field control-bucket and admin-secret are casual? [09:10] i think it is something related to S3, right? [09:11] vciaglia: my understanding is that those are randomly generated unique keys for your account [09:11] I think they're used to create the s3 buckets yeah, but I never cared to look at that part [09:12] oh ok! [09:13] kim0, 2011-08-12 11:12:51,367 INFO 'bootstrap' command finished successfully [09:13] ;) [09:13] nice :) [09:14] let's see "ensemble status" [09:15] woho, machines: [09:15] 0: {dns-name: ec2-184-73-31-67.compute-1.amazonaws.com, instance-id: i-1984c278} [09:15] services: {} [09:15] 2011-08-12 11:15:14,663 INFO 'status' command finished successfully [09:16] kim0, another question for you [09:16] shoot [09:16] here i see that the istance-id is: i-1984c278 but in AWS EC2 web panel it is i-dc6955aa: wtf? [09:18] could you refresh the aws panel [09:18] sometimes it gets out of sync [09:18] ah, ok! [09:21] now i'm deploying service units [09:23] i'm reading that i need of the .ensemble/example directory, where can i get the service units/repository? [09:29] kim0, ? [09:29] ah sorry wasn't looking [09:29] there's two things [09:30] a built in examples repo inside ensemble .. this is at [09:30] vciaglia: /usr/share/doc/ensemble/examples [09:30] kim0, great, thanks [09:31] the 'real' one .. is called principia → [09:31] https://ensemble.ubuntu.com/Formulas?action=show&redirect=Principia [09:31] vciaglia: basically .. you can 'bzr branch xxx' any of those formulas → https://code.launchpad.net/principia [09:32] vciaglia: if u haven't seen this article yet .. you should check it out http://cloud.ubuntu.com/2011/06/so-what-is-ensemble-anyway/ [09:32] kim0, nice [09:33] kim0, no, i'll read it [09:42] kim0, once "ensamble shutdown" i still see in STATUS: Running my istance. Why? Just a sync issue? [09:42] vciaglia: did you answer 'y' to ensemble ? [09:42] kim0, yes [09:43] vciaglia: then yeah .. click the little refresh button in AWS [09:43] you'll see em terminating [09:43] :~$ ensemble shutdown [09:43] Warning, this will destroy all machines and services in the [09:43] environment. Continue [y/N]y [09:43] 2011-08-12 11:43:04,983 INFO Shutting down environment 'sample' (type: ec2)... [09:43] 2011-08-12 11:43:06,275 INFO 'shutdown' command finished successfully [09:43] cool .. refresh aws then [09:44] kim0, still running [09:45] that never really happened to me [09:45] I guess in 5 mins if they're still up .. you could right click and terminate them from aws [09:46] wops, maybe this is the problem: Termination Protection: Enabled [09:47] ah hehe :) [09:49] kim0, well, the first thing we can do togheter is to add "Do not enable the Termination Protection for your Istance" in the official howto ;) [09:49] haha [09:53] kim0, umh ... now the status is "Terminated" but how to restart? The fields "Start" and "Stop" in the "Instance Actions menu" are inactive now [09:55] terminated means 'machine destroyed' .. it is gone [09:55] you start a new one [09:56] kim0, great! [13:21] kim0, ping! [13:22] vciaglia: pong :) [13:23] kim0, i tried to create another istance and bootstrap ensemble but still the same problem: the istance id/dns name showed in Ensemble doesn't match with the AWS Managemente Console. Is it a bug? [13:24] Ensemble: [13:24] machines: [13:24] 0: {dns-name: ec2-174-129-58-219.compute-1.amazonaws.com, instance-id: i-d34504b2} [13:24] AWS Web: [13:24] ec2-46-137-15-64.eu-west-1.compute.amazonaws.com [13:25] and id: i-6e300c18 [13:26] wops, kim0 ... problem found! [13:26] vciaglia: did you configure ensemble to use eu-west [13:26] by default it uses us-east I think [13:27] you're right! You've found the problem too! ;) [13:28] kim0, how to configure eu-west? [13:30] vciaglia: is that the region that the lightnin hit :) [13:31] eheh [13:31] i found the solution: add "region" to the environments.yaml [13:31] right? [13:31] Yes [13:31] you're fast :) [13:31] vciaglia: https://ensemble.ubuntu.com/docs/provider-configuration-ec2.html [13:32] thanks! [13:36] kim0, i see the light [13:36] 0: {dns-name: ec2-46-137-8-151.eu-west-1.compute.amazonaws.com, instance-id: i-54281422} [13:36] the right one! ;) [13:37] \o/ [13:41] wow, now it works. Finally deployed wordpress! [13:45] Yeeha :) [13:45] vciaglia: did you ensemble expose wordpress ? [13:45] this is recent functioanlity, so not sure if you've seen it in docs [13:48] kim0, pointing via browser to the wordpress istance i cannot access to the blog ... maybe a security rule problem? [13:49] kim0, i'm reading this doc: https://ensemble.ubuntu.com/docs/user-tutorial.html [13:49] vciaglia: yeah that's what I meant [13:49] vciaglia: ensemble expose wordpress [13:50] this should open up the firewall so you can access it [13:50] kim0, ok! [13:52] vciaglia: let me know when it works [13:58] kim0, ensemble assumes that Apache is already installed? [14:04] kim0, now it works: http://ec2-46-137-63-5.eu-west-1.compute.amazonaws.com [14:04] ;) [14:05] kim0, you just need to open up the 80/HTTP port on 0.0.0.0/0 to get access [14:07] vciaglia: what do you mean "open" [14:07] vciaglia: did you edit AWS security groups manually ? [14:07] kim0, yes [14:08] vciaglia: ensemble expose should do this for you [14:08] vciaglia: can u paste its output [14:09] kim0, no i didn't use the "esemble expose" command [14:09] see I told you to :) [14:12] kim0, oh excuse me :) [14:13] vciaglia: so now that you get everything running .. start preparing to write your very first own formula .. what do you think :) [14:21] kim0, yes i'm ready! ;) [14:21] kim0, in the next days i'll try to write my first formulas [14:22] kim0, now i have to go. Thank you for your time. Really excited to start working on Ensemble. [14:22] vciaglia: awesome .. ping me once you're ready to hack again .. enjoy [14:24] kim0, sure! Talk to you very soon [14:24] same here [14:58] Daviey: last day, how goes the battle? === otubo is now known as otubo[AFK] [16:06] <_mup_> Bug #825307 was filed: zookeeper connection needs to detect errors differently < https://launchpad.net/bugs/825307 > [16:17] FYI, for those that missed the email, principia is being renamed to 'formulas' [16:21] <_mup_> Bug #825326 was filed: Need wrapper around lxc interaction < https://launchpad.net/bugs/825326 > [16:40] SpamapS: yeah! === otubo[AFK] is now known as otubo [17:51] lynxman: ping, whats the status of the openstack deployment you guys were working on? [18:12] SpamapS: We just did a demo of an Ensemble deployment with Openstack, didn't have enough time on the sprint to do one in real life servers I'm afraid [18:14] lynxman: ahh, ok.. bummer. [18:15] s [18:19] lynxman: so you were driving openstack w/ ensemble? [18:19] lynxman: as in, using openstack to deploy formulas? [18:21] <_mup_> Bug #825398 was filed: Store Ensemble version number in topology node and verify ops < https://launchpad.net/bugs/825398 > [18:22] SpamapS: not me, adam_g was the one driving that [18:22] SpamapS: I'm with swift upstartify and LXC integration [20:02] SpamapS: hey [20:03] SpamapS: just got into boston. i can push the swift-storage and swift-proxy, and nova-compute and glance. but need to figure out a way to get the nova-cloud-controller pushed into principia [20:17] adam_g: I found them actually [20:17] adam_g: actually, swift-storage needs a way in as well [20:17] adam_g: they can stay in +junk for now.. they're about to fix that bug so you can push directly. [20:18] SpamapS: oh, sweet :) [20:19] <_mup_> ensemble/verify-version r311 committed by jim.baker@canonical.com [20:19] <_mup_> Initial commit [20:19] SpamapS: are you putting swift on hardware or ec2? [20:20] adam_g: no but I want to mess with it to run a parallel S3 on canonistack [20:20] in either case, i just pushed some changes that you'll probably need [20:21] make sure the swift-storage's block-device config matches something usable and free on the instance. [20:23] ok [20:23] adam_g: do you know if any of the machines are available for use? [20:24] SpamapS: no clue. didn't know about canonistack till yestreday [20:26] adam_g: no I mean the machines we had allocated for HW provisioning [20:30] SpamapS: oh, they are free from me, dont know about anyone else [20:45] <_mup_> ensemble/verify-version r312 committed by jim.baker@canonical.com [20:45] <_mup_> Test IncompatibleVersion exception === otubo is now known as otubo[AFK] [21:11] <_mup_> ensemble/verify-version r313 committed by jim.baker@canonical.com [21:11] <_mup_> Doc string and missing new file [21:50] <_mup_> ensemble/machine-agent-uses-formula-url r312 committed by kapil.thangavelu@canonical.com [21:50] <_mup_> formula downloads via http [22:25] SpamapS: It went well for us... far to tired to brief [22:34] Daviey: ;) I bet [22:34] Daviey: didn't realize you guys were done yesterday [22:35] Daviey: been trying to play with canonistack, but the S3 service is basically hosed [22:35] SpamapS: better we know now eh? :) [22:36] Daviey: I think its because its using nova-objectstore and not swift [22:36] SpamapS: I would be suprised if it plainly doesn't work [22:37] if it is using objectstore i mean [22:37] Yeah it gets wedged at 100% CPU often [22:37] I guess they're planning on deploying swift later [22:37] sounds like maybe that needs to be moved up [22:38] ah.. i see [22:38] Daviey: when you have time, can you send out a summary of the status of the machines on the nickel network? [22:38] I'm just overjoyed it's public facing.. i never thought that would happen! :) [22:39] Me too. :) [22:40] SpamapS: Yeah, the old dhcpd from prior deployment was being shared by other teams.. [22:40] *oops* [22:40] but yes, can you jote me a quick email asking for that.. it will drop off my memory otherwise. [22:41] my face hurts [22:41] -> bed [22:41] toodles === otubo[AFK] is now known as otubo