Re: CloudPlatform 4.5 released?
I¹m not sure what bearing Redhat has on this discussion, but you are correct in noting the Citrix did release CloudPlatform 4.5 today ‹ and it is largely based on ACS 4.5 code. Collectively, Citrix engineers continue to contribute the lion¹s share of ACS code and we carefully follow all rules established by the community. That being said, today was the start of our Citrix Summit event. It is the Sales Kick Off and and Partner gathering for Citrix to start 2015. It was a great opportunity to publicize what we¹re doing with CloudPlatform (and thus ACS by extension) and we chose today as our launch date. The reception by our sales personnel and channel partners at the show has been very positive so far. We expect good reaction from customers as well as we believe this is our highest quality release to date. Thanks for your interest. -Steve Steve Wilson VP Product Unit Manager Cloud Software Citrix @virtualsteve On 1/13/15, 3:14 PM, Nux! n...@li.nux.ro wrote: Hi, I am slightly confused. I thought Cloudstack was Citrix' Fedora, not the other way around. Should we care at all what Citrix does? Seems like they launched a 4.5 ignoring the benefit of squishing bugs we may possibly uncover during RC period. Lucian -- Sent from the Delta quadrant using Borg technology! Nux! www.nux.ro
CloudStack Quality Process
Hi Everyone, It was great to get to see a number of you at the recent CCC in Budapest. While I was there, I got to meet face to face with individuals working for several companies that have a real stake in the commercial success of the CloudStack project. After joining Citrix (and becoming involved in CloudStack) about a year ago, I’ve come to believe that we need to do more to mature our quality practices around this codebase. We all like to say #cloudstackworks (and it’s true), but this is a massive codebase that’s used in the most demanding situations. We have large telecommunications companies and enterprises who are betting their businesses on this software. It has to be great! There has been quite a bit of discussion on the mailing list in recent months about how we improve in this area. There is plenty of passion, but we haven’t made enough concrete progress as a community. In my discussions with key contributors as CCC, there was general agreement that the DEV list isn’t a good forum for hashing out these kinds of things. Email is too low-bandwidth and too impersonal. At CCC, I discussed with several people the idea that we commission a small sub team to go hash out a proposal for how we handle the following topics within the ACS community (which can then be brought back to the larger community for ratification): * Continuous integration and test automation * Gating of commits * Overall commit workflow We are looking for volunteers to commit to being part of this team. This would imply a serious commitment. We don’t want hangers on or observers. This will entail real work and late night meetings. We’re looking for people who are serious contributors to the codebase. From Citrix, David Nalley and Animesh Chaturvedi have booth told me they’re willing to commit to this project. They’ve both managed ACS releases and have a really good view into the current process — and I know both are passionate about improving our process. From my CCC discussions, I believe there are individuals from Schuberg Philis, Shape Blue and Cloud Ops who are willing to commit to this process. If you are willing to be part of this team to drive forward our community, please reply here. Thanks, -Steve Steve Wilson VP Product Unit Manager Cloud Software Citrix @virtualsteve
Re: [VOTE] Apache CloudStack 4.3.0 (seventh round)
I think it was suggested multiple times that we push out the 4.4 freeze date because the 4.3 work has been lagging. I think this is just another indicator we need to evaluate our release cadence as a community. That being said, I don¹t think we want to hold 4.3 any further. This must be the best tested RC in the history of software at this point. Unless someone finds a new showstopper (that wasn¹t in the previous 6 builds!) then let¹s get this puppy out! :-) -Steve On 3/12/14, 10:25 AM, Mike Tutkowski mike.tutkow...@solidfire.com wrote: I hate to point this out as I know we've been struggling to get 4.3 out the door, but this week is probably not a great week to count votes for 4.3 as it is the last week before 4.4 Feature Freeze. On Wed, Mar 12, 2014 at 11:09 AM, Wilder Rodrigues wrodrig...@schubergphilis.com wrote: Hi guys and gals, Based on the findings after my first round of tests, I give a +1 to the 4.3 RC Please, find below what I have tested so far: * Environment - Management Server: Debian 7 VM under VirtualBox - DevCloud: XenServer 6.2 - MySQL: running on the DevCloud - System VM: Latest from http://jenkins.buildacloud.org/view/4.3/job/cloudstack-4.3-systemvm/ * Initial start-up - Everything seems to work fine * Zone - DNS1: 8.8.8.8 - DNS2: 8.8.4.4 - Hypervisor: XenServer - Guest CIDR: 10.1.2.0/24 - Local Storage enabled: true * Public Traffic - 10.1.1.1 / 255.255.255.0 / 10.1.1.2 / 10.1.1.100 * POD - 10.1.1.1 / 255.255.255.0 / 10.1.1.101 / 10.1.1.200 * VLAN - 101 - 109 * Host - Host Name: 178.237.34.120 - Username: root - Password: blah * Secondary Storage - Provider: NFS - Name: sec01 - Server: 10.1.1.114 - Path: /opt/storage/secondary ::: ALL GREEN UP TO NOW ::: * Create Instance - Featured: Tiny Linux - Compute Offering: Tiny Offering - Disk Offering: None - Instance name: cs43-01 * NIC Information - IP Address: 10.1.2.186 - Gateway: 10.1.2.1 - Netmask: 255.255.255.0 * Create Network - Name: devcloud-net01 - Type: Isolated - CIDR: 10.1.2.0/24 - Public IP: 10.1.1.4 [Source NAT] - Egress Rules: 0.0.0.0/0 - All - Network Offering: Offering for Isolated networks with Source Nat service enabled * Create ACLs - 10.1.0.0/16 - TCP - 22 - 22 - 10.1.0.0/16 - TCP - 443 - 443 * Create Port Forwarding - 22:22 - 22:22 - instance cs43-01 [10.1.2.186] - 443:443 - 443:443 - instance cs43-01 [10.1.2.186] * SSH into the new instance via the Public IP: [root@devcloud-wil01 ~]# ssh root@10.1.1.4 The authenticity of host '10.1.1.4 (10.1.1.4)' can't be established. RSA key fingerprint is 02:43:6c:24:c5:79:b6:e2:c8:b7:e8:3c:8d:13:37:91. Are you sure you want to continue connecting (yes/no)? yes Warning: Permanently added '10.1.1.4' (RSA) to the list of known hosts. root@10.1.1.4's password: % % % ls ssh-host-dss-key.pub ssh-host-rsa-key.pub % cd / % ls bin bootdev etc homelib lost+found mnt procrootsbinsys tmp usr var % With kind regards, Wilder -Original Message- From: Paul Angus [mailto:paul.an...@shapeblue.com] Sent: Wednesday, March 12, 2014 12:45 PM To: dev@cloudstack.apache.org; Hugo Trippaers Cc: Animesh Chaturvedi Subject: RE: [VOTE] Apache CloudStack 4.3.0 (seventh round) Yes, I can build now. :-) Regards Paul Angus Cloud Architect S: +44 20 3603 0540 | M: +447711418784 | T: CloudyAngus paul.an...@shapeblue.com -Original Message- From: Damoder Reddy [mailto:damoder.re...@citrix.com] Sent: 12 March 2014 10:49 To: dev@cloudstack.apache.org; Hugo Trippaers Cc: Animesh Chaturvedi Subject: RE: [VOTE] Apache CloudStack 4.3.0 (seventh round) HI Paul, After you pull Hugo changes are you able to build now? Thanks Regards Damodar/ -Original Message- From: Paul Angus [mailto:paul.an...@shapeblue.com] Sent: Wednesday, March 12, 2014 2:04 PM To: Hugo Trippaers Cc: Animesh Chaturvedi; dev@cloudstack.apache.org Subject: Re: [VOTE] Apache CloudStack 4.3.0 (seventh round) Yes that's correct. I'm building noredist Regards, Paul Angus S: +44 20 3603 0540tel:+44%2020%203603%200540 | M: +447711418784tel: +447711418784 T: @CloudyAngus paul.an...@shapeblue.commailto:paul.an...@shapeblue.com Original message From: Hugo Trippaers Date:12/03/2014 07:32 (GMT+00:00) To: Paul Angus Cc: Animesh Chaturvedi ,dev@cloudstack.apache.org Subject: Re: [VOTE] Apache CloudStack 4.3.0 (seventh round) Hey Paul, Just to be clear, this problem only occurs during the noredist build right? Mysql HA is one of the noredist features, so it should not be present in the regular build. I'm checking the poms now to see if everything is configured correctly. Cheers, Hugo On 12 mrt. 2014, at 08:14, Paul Angus paul.an...@shapeblue.com wrote: If I manually fix the white spaces I
Re: ANNOUNCE] New Committer: Giles Sirett
Excellent! Congrats! On 12/2/13 8:06 AM, John Burwell jburw...@basho.com wrote: The Project Management Committee (PMC) for Apache CloudStack has asked Giles Sirett to become a committer and we are pleased to announce that they have accepted. Being a committer allows many contributors to contribute more autonomously. For developers, it makes it easier to submit changes and eliminates the need to have contributions reviewed via the patch submission process. Whether contributions are development-related or otherwise, it is a recognition of a contributor's participation in the project and commitment to the project and the Apache Way. Please join me in congratulating Giles! ‹ John Burwell, on behalf of the Apache CloudStack PMC
Re: [DISCUSS] Reporting tool for feeding back zone, pod and cluster information
I built something like this for products at Sun Microsystems. We embedded into nearly everything we built: The Java Runtime Environment Open Office Solaris MySQL Even things like Server LOMs (the list goes on) By default, when each of these products installed/first run, it would try to bring the user into the program. It was always possible to opt out, but we really worked to get people to not opt out. We got shockingly HUGE piles of data (literally from millions of installed product instances). We didn't get any complaints (EVER) in the years we ran this program. It was hugely useful to the product teams. BTW, we didn't even make this data anonymous. You could obviously choose to be anonymous, but if people want to give their names/companies then why not let them? You'd be surprised how many people wouldn't mind. -Steve On 11/26/13 12:49 PM, Chiradeep Vittal chiradeep.vit...@citrix.com wrote: +1. Of course we must ensure proper treatment of this data (anonymization, retention, removal, copyrights) On 11/23/13 11:01 AM, Wido den Hollander w...@widodh.nl wrote: Hi, I discussed this during CCCEU13 with David, Chip and Hugo and I promised I put it on the ml. My idea is to come up with a reporting tool which users can run daily which feeds us back information about how they are using CloudStack: * Hypervisors * Zone sizes * Cluster sizes * Primary Storage sizes and types * Same for Secondary Storage * Number of management servers * Version This would ofcourse be anonimized where we would send one file with JSON data back to our servers where we can proccess it to do statistics. The tool will obviously be open source and participating in this will be opt-in only. We currently don't know what's running out there, so that would be great to know. Some questions remain: * Who is going to maintain the data? * Who has access to the data? * How long do we keep it? * Do we do logging of IPs sending the data to us? I certainly do not want to spy on our users, so that's why it's opt-in and the tool should be part of the main repo, but I think that for us as a project it's very useful to know what our users are doing with CloudStack. Comments? Wido
Re: CloudStack.next
Lots of interesting ideas there. Thanks for sharing! BTW, I really share your interest in making CloudStack and Docker work really well together. On Nov 17, 2013, at 9:57 AM, Rohit Yadav bhais...@apache.org wrote: Hi, On Wed, Nov 13, 2013 at 5:11 AM, Steve Wilson steve.wil...@citrix.comwrote: Hi All, As we ramp towards freeze on 4.3 and start talking about 4.4, I thought it would be fun to queue up a discussion here on the list before Collab next week. What do you envision in the next MAJOR release of CloudStack? Call it 5.0 or whatever you like, but If we're not changing/breaking APIs and since we had adopted semantic versioning, we should not change the major version. what would you like to see there? What would you change? Few things I'm personally looking forward to is to have CloudStack have better abilities and ease for controlling containers (lxc using docker or what have you) and a being able to act as a container coordinator between baremetal/virtual machines. I guess this is not a new request and we know ACS already supports LXC but I would like to use ACS as a tool that works for me to configure, deploy and manage containers using docker. In essence, we can have something like a recipe, a DSL or infra-management-as-code to automate infrastructure at a higher level just like we use Puppet or Chef, we could have something for our infrastructure that just works. What would you enhance? Probably next iteration of cloudmonkey and add tests (in my free time). Are there big bets we should be placing as a community? There is a lot of architectural debt that CloudStack is paying for, maybe we could introduce and implement cloud engine, new api services and the other next gen stuff that we had discussed in that past; I would like to contribute if that happens. The cluster management service and the way agents and ACS mgmt server communicate can be improved, things like Raft could be implemented as our consensus problem is not solved (in case of network/io issue, the agents and ACS mgmt server may have different view of the world, for example). The codebase is monstrous, we can maybe bet of splitting every part as a plugin and maybe move some code to other languages that are interoperable and run on JVM like Scala. One motivation for this is the fact that a lot of infrastructure code in the last one year has been written in Scala which works perfectly with existing Java based ecosystem. Since I've some experience of Scala and ACS's API layer, web services, plugin system, ACS's ORM and build system I can think refactoring and rewriting stuff in Scala would greatly reduce a lot of code while it would be still interoperable with the rest of the components. If you think about ACS from a top level bird's eye view, ACS is a big resource consuming poorly written web app that takes in some request, spits answers for read queries (sync commands) or enqueues in its job queue (async jobs) and stores information what it knows about (from MySQL) and/or cache (in/via DAOs). There are a lot of moving parts and SPOFs. If all these components could be a ran as a separate service which could run on different or same server, they could be cleanly separated and they can become more testable, easier to understand, enhance and develop. Just my views :) Regards. Feel free to post any thoughts here and I'll look forward to talking to many of you in person at Collab next week. You are coming to Collab, right? -Steve Steve Wilson VP, Cloud Engineering Citrix twitter: @virtualsteve
Re: CloudStack.next
Hi Daan, Prasanna, Simon, David and Andrei! Thanks for chiming in. Great way to kick off the discussion. In my thinking, we might want to look at things in three buckets: 1. Things that could go into a maintenance release like a 4.2.x 2. Things that could go into a minor release like a 4.4 3. Things that would require major architecture changes and might wind up in 5.0 or something like it From a Citrix perspective, we're definitely looking at things that fall into all three of these buckets. We've contributed a huge number of fixes to 4.2.1 and a number of features to 4.3. We're also now starting to plan our contributions to 4.4 as well. However, since I joined the community, I've seen very little discussion of what's really next. What are the major things we'd like to see done? I don¹t have a particular timeframe in mind for these things, I'm just looking to spark discussion -- especially as we go to Collab next week. Things that are interesting to me that fit in bucket three. Here are a couple: What level of scale should CloudStack be able to support? I imagine we'll bee CloudStack clouds managing millions of VMs in the next few years. What do we need to do to make that effective? I think people will want to manage micro-clouds -- very small, but flexible clouds for special purpose needs. What would CloudStack need to do to scale down very small and still be cost effective to run? Any thoughts about these, or any other ideas? -Steve On 11/12/13 9:58 PM, Daan Hoogland daan.hoogl...@gmail.com wrote: I don't see any sugestions I don't like (including not breaking api) but, - I like to second Simnons 'HA for VPC routers' extra. It is hurting not having that. - smaller releases is another one. monthly preferably or maybe an db upgrade model that allows for running snapshots and upgrading them regularly. The time to market for new features is now between 4 and 8 months:( - related: master as a stable/always building and passing unit tests On Wed, Nov 13, 2013 at 6:39 AM, Prasanna Santhanam t...@apache.org wrote: On Tue, Nov 12, 2013 at 11:41:17PM +, Steve Wilson wrote: Hi All, As we ramp towards freeze on 4.3 and start talking about 4.4, I thought it would be fun to queue up a discussion here on the list before Collab next week. What do you envision in the next MAJOR release of CloudStack? Call it 5.0 or whatever you like, but what would you like to see there? What would you change? What would you enhance? Are there big bets we should be placing as a community? Feel free to post any thoughts here and I'll look forward to talking to many of you in person at Collab next week. You are coming to Collab, right? simplified upgradeability at all stages of development from version x to version y. -- Prasanna., Powered by BigRock.com
Re: CloudStack.next
Hi Mike, Really interesting stuff and very differentiaing! -Steve On 11/13/13 12:33 PM, Mike Tutkowski mike.tutkow...@solidfire.com wrote: Just as an FYI (to whom it may concern): For me, personally, my primary focus has been (and continues to be) on bringing true storage Quality of Service (QoS) to CloudStack (guaranteed IOPS on a per-CloudStack-volume basis). Prior to 4.2, CloudStack expected an admin to preallocate large amounts of storage (ex. a large volume on a SAN), then introduce this storage to his hypervisor, then create Primary Storage in CloudStack to represent that hypervisor-configured storage. At this point, a user could then create root and data disks that leveraged this storage (i.e. multiple root and data disks running on the same storage volume). That model may be efficient in terms of, say, number of iSCSI connections, but it is not very useful from the point of view of a storage system that is designed to deliver true QoS (eliminating the Noisy Neighbor effect by guaranteeing IOPS on a per-volume basis). In such a storage system, each volume on the SAN has independent QoS settings. In this world, it is ideal to map a single CloudStack volume to a single volume on the SAN. This means being able to create volumes on the SAN dynamically (ex. when a CloudStack volume is attached to a VM for the first time). Much of what Edison Su worked on for 4.2's storage-framework changes enabled me to take a large first step in that I could create a plug-in that could dynamically create volumes on our SAN (SolidFire SAN). However, the concept of preallocated storage is so embedded in CloudStack that I've needed to update core components of CloudStack, as well as CloudStack hypervisor-related code, to deal with dynamically created volumes. In 4.2 I released support for storage QoS with data disks on XenServer and VMware. In 4.3 I am releasing support for storage Qos with data disks on KVM. As we move forward, I plan to support storage QoS with root volumes on these hypervisors, as well (most likely starting with XenServer). It has been a bit tricky to support hypervisor snapshots in this model (where volumes are created dynamically on a SAN and the hypervisor data structures like SRs or datastores are created behind the scenes). This is another area I'm tackling for the 4.3 release (for XenServer and VMware). On Wed, Nov 13, 2013 at 11:50 AM, Steve Wilson steve.wil...@citrix.comwrote: Hi Daan, Prasanna, Simon, David and Andrei! Thanks for chiming in. Great way to kick off the discussion. In my thinking, we might want to look at things in three buckets: 1. Things that could go into a maintenance release like a 4.2.x 2. Things that could go into a minor release like a 4.4 3. Things that would require major architecture changes and might wind up in 5.0 or something like it From a Citrix perspective, we're definitely looking at things that fall into all three of these buckets. We've contributed a huge number of fixes to 4.2.1 and a number of features to 4.3. We're also now starting to plan our contributions to 4.4 as well. However, since I joined the community, I've seen very little discussion of what's really next. What are the major things we'd like to see done? I don¹t have a particular timeframe in mind for these things, I'm just looking to spark discussion -- especially as we go to Collab next week. Things that are interesting to me that fit in bucket three. Here are a couple: What level of scale should CloudStack be able to support? I imagine we'll bee CloudStack clouds managing millions of VMs in the next few years. What do we need to do to make that effective? I think people will want to manage micro-clouds -- very small, but flexible clouds for special purpose needs. What would CloudStack need to do to scale down very small and still be cost effective to run? Any thoughts about these, or any other ideas? -Steve On 11/12/13 9:58 PM, Daan Hoogland daan.hoogl...@gmail.com wrote: I don't see any sugestions I don't like (including not breaking api) but, - I like to second Simnons 'HA for VPC routers' extra. It is hurting not having that. - smaller releases is another one. monthly preferably or maybe an db upgrade model that allows for running snapshots and upgrading them regularly. The time to market for new features is now between 4 and 8 months:( - related: master as a stable/always building and passing unit tests On Wed, Nov 13, 2013 at 6:39 AM, Prasanna Santhanam t...@apache.org wrote: On Tue, Nov 12, 2013 at 11:41:17PM +, Steve Wilson wrote: Hi All, As we ramp towards freeze on 4.3 and start talking about 4.4, I thought it would be fun to queue up a discussion here on the list before Collab next week. What do you envision in the next MAJOR release of CloudStack? Call it 5.0 or whatever you like, but what would you like to see there? What would you change? What would you enhance
CloudStack.next
Hi All, As we ramp towards freeze on 4.3 and start talking about 4.4, I thought it would be fun to queue up a discussion here on the list before Collab next week. What do you envision in the next MAJOR release of CloudStack? Call it 5.0 or whatever you like, but what would you like to see there? What would you change? What would you enhance? Are there big bets we should be placing as a community? Feel free to post any thoughts here and I'll look forward to talking to many of you in person at Collab next week. You are coming to Collab, right? -Steve Steve Wilson VP, Cloud Engineering Citrix twitter: @virtualsteve
Re: Hi
Thanks! On 10/2/13 10:33 PM, Koushik Das koushik@citrix.com wrote: Hi Steve, Welcome to CloudStack. Looking forward to working with you. On 02-Oct-2013, at 6:10 PM, Chip Childers chip.child...@sungard.com wrote: Welcome Steve! On Wed, Oct 2, 2013 at 12:38 AM, Steve Wilson steve.wil...@citrix.comwrote: Hi Everyone, I just wanted to take a second and introduce myself. I recently joined Citrix as the VP of Cloud Engineering, and I'm responsible for the Citrix CloudPlatofrm (powered by Apache CloudStack). I just joined the list and am looking forward to working with everyone in the community. Feel free to drop me a note if you have suggestions for me on how Citrix can best work with the Apache CloudStack community. Thanks, -Steve twitter: @virtualsteve email: steve.wil...@citrix.com
Re: Hi
I'll try to live up to that! Thanks for the welcome! On 10/3/13 1:37 AM, Daan Hoogland daan.hoogl...@gmail.com wrote: H Steve, I wish you luck with managing the Citrix - Community interaction and given the continued huge importance of Citrix to Apache CloudStack I am taking the liberty of calling you our friend. Welcome, Daan On Thu, Oct 3, 2013 at 7:33 AM, Koushik Das koushik@citrix.com wrote: Hi Steve, Welcome to CloudStack. Looking forward to working with you. On 02-Oct-2013, at 6:10 PM, Chip Childers chip.child...@sungard.com wrote: Welcome Steve! On Wed, Oct 2, 2013 at 12:38 AM, Steve Wilson steve.wil...@citrix.com wrote: Hi Everyone, I just wanted to take a second and introduce myself. I recently joined Citrix as the VP of Cloud Engineering, and I'm responsible for the Citrix CloudPlatofrm (powered by Apache CloudStack). I just joined the list and am looking forward to working with everyone in the community. Feel free to drop me a note if you have suggestions for me on how Citrix can best work with the Apache CloudStack community. Thanks, -Steve twitter: @virtualsteve email: steve.wil...@citrix.com
Re: Hi
Thanks! Looking forward to working with you too! On 10/3/13 4:35 AM, Bharat Kumar bharat.ku...@citrix.com wrote: Hi Steve, Welcome to CloudStack. I look forward to working with you in the community. On Oct 3, 2013, at 2:07 PM, Daan Hoogland daan.hoogl...@gmail.com wrote: H Steve, I wish you luck with managing the Citrix - Community interaction and given the continued huge importance of Citrix to Apache CloudStack I am taking the liberty of calling you our friend. Welcome, Daan On Thu, Oct 3, 2013 at 7:33 AM, Koushik Das koushik@citrix.com wrote: Hi Steve, Welcome to CloudStack. Looking forward to working with you. On 02-Oct-2013, at 6:10 PM, Chip Childers chip.child...@sungard.com wrote: Welcome Steve! On Wed, Oct 2, 2013 at 12:38 AM, Steve Wilson steve.wil...@citrix.com wrote: Hi Everyone, I just wanted to take a second and introduce myself. I recently joined Citrix as the VP of Cloud Engineering, and I'm responsible for the Citrix CloudPlatofrm (powered by Apache CloudStack). I just joined the list and am looking forward to working with everyone in the community. Feel free to drop me a note if you have suggestions for me on how Citrix can best work with the Apache CloudStack community. Thanks, -Steve twitter: @virtualsteve email: steve.wil...@citrix.com
Re: Hi
Thanks! On 10/3/13 4:37 AM, Wei ZHOU ustcweiz...@gmail.com wrote: Welcome Steve! 2013/10/2 Steve Wilson steve.wil...@citrix.com Hi Everyone, I just wanted to take a second and introduce myself. I recently joined Citrix as the VP of Cloud Engineering, and I'm responsible for the Citrix CloudPlatofrm (powered by Apache CloudStack). I just joined the list and am looking forward to working with everyone in the community. Feel free to drop me a note if you have suggestions for me on how Citrix can best work with the Apache CloudStack community. Thanks, -Steve twitter: @virtualsteve email: steve.wil...@citrix.com
Hi
Hi Everyone, I just wanted to take a second and introduce myself. I recently joined Citrix as the VP of Cloud Engineering, and I'm responsible for the Citrix CloudPlatofrm (powered by Apache CloudStack). I just joined the list and am looking forward to working with everyone in the community. Feel free to drop me a note if you have suggestions for me on how Citrix can best work with the Apache CloudStack community. Thanks, -Steve twitter: @virtualsteve email: steve.wil...@citrix.com
