Daan, I see where you are coming from in your use case scenario. I just think that winning minds over to Open Source platforms could be more difficult if when asked "How often is there a new version?" we need to break the news that a new one is out every week. It won't sound like a solid, mature enough platform. It will sound like it's continuously being patched and therefore buggy.
I go back to my earlier point regards to testing. I think four month cycles, a complete freeze clearly advertised beforehand and a testing schedule published would set us in better step. Add to this a roadmap spanning 24 months I think we would be able to not worry about missing deadlines as much. As an idea, how about RC's needing vetting by the feature writers and associated testers before becoming a 'CTP'(of sorts). Essentially adding a Q/A step. I am looking to become much more involved with testing 4.4 onwards BTW. Regards Alex Hitchins D: +44 1892 523 587 | S: +44 2036 030 540 | M: +44 7788 423 969 alex.hitch...@shapeblue.com -----Original Message----- From: Daan Hoogland [mailto:daan.hoogl...@gmail.com] Sent: 13 March 2014 08:58 To: dev Subject: Re: [VOTE] Apache CloudStack 4.3.0 (seventh round) If we have n features, there may be conflict in n! ways. Some of thos are relatively simple conflicts as these involve only two new features. Others are potentiatlly very complex as these concern more then just two features interacting with each other. The worrying thing about this is that it is a oversimplification of a formula of the number of way in which things may go wrong in a release. The bottom line is that having more features in is not an argument to postpone feature freeze if the release date shifting because of bugs found in a release is keeping us from releasing. We should not be able to get more features in the next release. We should be held back to release a somewhat simpler release next time. So next time we can verify our release better and/or quicker. Strangely enough, I don't agree with Alex, but I do agree with what Lucian takes from his argument. And a weekly release may be a bit of an overstatement. Only a bit though. At Schuberg Philis we want our project/employee cloud to be updated that often, so we can spot problems early and those don't make it to the production cloud. A new proposal: let's have rc's on a weekly basis and releases on a n month basis;) Now ask me about n again, Mike. On Thu, Mar 13, 2014 at 12:57 AM, Mike Tutkowski <mike.tutkow...@solidfire.com> wrote: > Hey Daan, > > I'm trying to understand this paragraph: > > "with n releases there are n*(n-1) potential conficts of the simlest > kind and n*(n-1)(n-2) potential conflicts of a slightly mor complex > kind... The higher n ... do the math. The more we postpone a feature > freeze the higher n will get. And that is only talking of features. > not about the simpler fixes that are added." > > I'm not following what it means. Can you define what n is? What do you > mean by a conflict of the simplest kind? Of a slightly more complex kind? > > Thanks! I'm just curious what you were referring to here. > > Talk to you later! > Mike > > > On Wed, Mar 12, 2014 at 3:10 PM, Daan Hoogland <daan.hoogl...@gmail.com>wrote: > >> Steve, >> >> As I have suggested before, we shoud not lengthen releas periods but >> shorten them. I highly object to the idea of enlarging the window and >> the release. It will pnly make relasing more difficult. >> >> with n releases there are n*(n-1) potential conficts of the simlest >> kind and n*(n-1)(n-2) potential conflicts of a slightly mor complex >> kind... The higher n ... do the math. The more we postpone a feature >> freeze the higher n will get. And that is only talking of features. >> not about the simpler fixes that are added. >> >> postponing when we have difficulty releasing quality makes no sense. >> >> kind regards, >> Daan Hoogland >> >> On Wed, Mar 12, 2014 at 9:46 PM, Steve Wilson >> <steve.wil...@citrix.com> >> wrote: >> > 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-system >> >>> vm/ >> >>> >> >>> * 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 boot dev etc home lib >> >>> lost+found mnt proc root sbin sys >> >>>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 0540<tel:+44%2020%203603%200540> | M: >> >>> +447711418784 >> <tel: >> >>> +447711418784> >> >>> T: @CloudyAngus >> >>> paul.an...@shapeblue.com<mailto: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 can get past MySQL HA >> >>> > Strategy, >> >>>but >> >>> then I hit: >> >>> > >> >>> > [INFO] >> >>> > >> --------------------------------------------------------------------- >> - >> >>> > -- [INFO] Building Apache CloudStack Client UI 4.3.0 [INFO] >> >>> > >> --------------------------------------------------------------------- >> - >> >>> > -- >> >>> > Downloading: >> >>> > >> http://repo.maven.apache.org/maven2/org/apache/cloudstack/cloud-plugi >> n >> >>> > -database-mysqlha/4.3.0/cloud-plugin-database-mysqlha-4.3.0.pom >> >>> > [WARNING] The POM for >> >>> > org.apache.cloudstack:cloud-plugin-database-mysqlha:jar:4.3.0 >> >>> > is missing, no dependency information available >> >>> > Downloading: >> >>> > >> http://repo.maven.apache.org/maven2/org/apache/cloudstack/cloud-plugi >> n >> >>> > -database-mysqlha/4.3.0/cloud-plugin-database-mysqlha-4.3.0.jar >> >>> > [ERROR] Failed to execute goal on project cloud-client-ui: >> >>> > Could not resolve dependencies for project >> >>> > org.apache.cloudstack:cloud-client-ui:war:4.3.0: Could not find >> >>> > artifact >> org.apache.cloudstack:cloud-plugin-database-mysqlha:jar:4.3.0 >> >>> > in central (http://repo.maven.apache.org/maven2) -> [Help 1] >> >>> > >> >>> > MySQL HA Strategy seems to need a bit of work. >> >>> > >> >>> > >> >>> > Regards, >> >>> > >> >>> > Paul Angus >> >>> > Cloud Architect >> >>> > S: +44 20 3603 0540 | M: +447711418784 | T: @CloudyAngus >> >>> > paul.an...@shapeblue.com >> >>> > >> >>> > -----Original Message----- >> >>> > From: Animesh Chaturvedi [mailto:animesh.chaturv...@citrix.com] >> >>> > Sent: 11 March 2014 19:31 >> >>> > To: dev@cloudstack.apache.org >> >>> > Cc: Hugo Trippaers; Hugo Trippaers >> >>> > (htrippa...@schubergphilis.com); Paul Angus >> >>> > Subject: RE: [VOTE] Apache CloudStack 4.3.0 (seventh round) >> >>> > >> >>> > >> >>> > >> >>> >> -----Original Message----- >> >>> >> From: Paul Angus [mailto:paul.an...@shapeblue.com] >> >>> >> Sent: Tuesday, March 11, 2014 10:35 AM >> >>> >> To: dev@cloudstack.apache.org >> >>> >> Subject: RE: [VOTE] Apache CloudStack 4.3.0 (seventh round) >> >>> >> >> >>> >> Trying to build 4.3, the process bombs out for me at MySQL HA >> >>>Strategy. >> >>> >> And strangely it seems to be trying to build MySQL from Master >> >>> >> (4.4.0- SNAPSHOT)? >> >>> > [Animesh] Ok this came in from Hugo's commit that I >> >>> > cherry-picked >> >>> > >> https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=commitdiff >> ; >> >>> > h=472a387d2d828e21aff93a750ed3e178837a1879 >> >>> > >> >>> > from file plugins/database/mysql-ha/pom.xml This is a version >> >>> > issue >> >>> which can be fixed but should not affect functioning. Lets hear >> >>>from Hugo on this. >> >>> > >> >>> > >> >>> > The other errors are formatting issues caught by checkstyle >> >>> > plugin >> >>>that >> >>> can be ignored. The Jenkins build is successful. >> >>> > >> >>> >> >> >>> >> Ideas anyone? >> >>> >> >> >>> >> >> >>> >> [INFO] Apache CloudStack Plugin - MySQL HA Strategy ...... >> >>> >> FAILURE [1.110s] [ERROR] Failed to execute goal >> >>> >> org.apache.maven.plugins:maven-checkstyle- >> >>> >> plugin:2.11:check (cloudstack-checkstyle) on project >> >>> >> cloud-plugin-database- >> >>> >> mysqlha: Failed during checkstyle execution: There are 6 >> >>> >> checkstyle errors. -> [Help 1] >> >>> >> >> >>> >> [INFO] >> >>> >> >> --------------------------------------------------------------------- >> >>> >> - >> >>> >> -- [INFO] Building Apache CloudStack Plugin - MySQL HA >> >>> >> Strategy >> >>> >> 4.4.0- SNAPSHOT [INFO] >> >>> >> >> --------------------------------------------------------------------- >> >>> >> - >> >>> >> -- >> >>> >> [INFO] >> >>> >> [INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ >> >>> >> cloud-plugin- database-mysqlha --- [INFO] Deleting >> >>> >> /usr/local/4.3/cloudstack/dist/rpmbuild/BUILD/cloudstack- >> >>> >> 4.3.0/plugins/database/mysql-ha/target (includes = [**/*], >> >>> >> excludes >> = >> >>> >> []) [INFO] Deleting >> >>> >> /usr/local/4.3/cloudstack/dist/rpmbuild/BUILD/cloudstack- >> >>> >> 4.3.0/plugins/database/mysql-ha (includes = [target, dist], >> >>> >> excludes = >> >>> >> []) [INFO] [INFO] --- maven-checkstyle-plugin:2.11:check >> >>> >> (cloudstack-checkstyle) @ cloud-plugin-database-mysqlha --- >> >>> >> [INFO] >> >>> Starting audit... >> >>> >> /usr/local/4.3/cloudstack/dist/rpmbuild/BUILD/cloudstack- >> >>> >> 4.3.0/plugins/database/mysql- >> >>> >> ha/src/com/cloud/utils/db/StaticStrategy.java:54: Line has >> >>> >> trailing >> >>> spaces. >> >>> >> /usr/local/4.3/cloudstack/dist/rpmbuild/BUILD/cloudstack- >> >>> >> 4.3.0/plugins/database/mysql- >> >>> >> ha/src/com/cloud/utils/db/StaticStrategy.java:58: Line has >> >>> >> trailing >> >>> spaces. >> >>> >> /usr/local/4.3/cloudstack/dist/rpmbuild/BUILD/cloudstack- >> >>> >> 4.3.0/plugins/database/mysql- >> >>> >> ha/src/com/cloud/utils/db/StaticStrategy.java:60: Line has >> >>> >> trailing >> >>> spaces. >> >>> >> /usr/local/4.3/cloudstack/dist/rpmbuild/BUILD/cloudstack- >> >>> >> 4.3.0/plugins/database/mysql- >> >>> >> ha/src/com/cloud/utils/db/StaticStrategy.java:110: Line has >> >>> >> trailing >> >>> spaces. >> >>> >> /usr/local/4.3/cloudstack/dist/rpmbuild/BUILD/cloudstack- >> >>> >> 4.3.0/plugins/database/mysql- >> >>> >> ha/src/com/cloud/utils/db/StaticStrategy.java:120: Line has >> >>> >> trailing >> >>> spaces. >> >>> >> /usr/local/4.3/cloudstack/dist/rpmbuild/BUILD/cloudstack- >> >>> >> 4.3.0/plugins/database/mysql- >> >>> >> ha/src/com/cloud/utils/db/StaticStrategy.java:127: Line has >> >>> >> trailing >> >>> spaces. >> >>> >> Audit done. >> >>> >> >> >>> >> Regards, >> >>> >> >> >>> >> Paul Angus >> >>> >> Cloud Architect >> >>> >> S: +44 20 3603 0540 | M: +447711418784 | T: @CloudyAngus >> >>> >> paul.an...@shapeblue.com >> >>> >> >> >>> >> -----Original Message----- >> >>> >> From: Animesh Chaturvedi >> >>> >> [mailto:animesh.chaturv...@citrix.com] >> >>> >> Sent: 11 March 2014 03:00 >> >>> >> To: dev@cloudstack.apache.org >> >>> >> Subject: [VOTE] Apache CloudStack 4.3.0 (seventh round) >> >>> >> >> >>> >> >> >>> >> >> >>> >> Hi All, >> >>> >> >> >>> >> >> >>> >> >> >>> >> I've created a 4.3.0 release, with the following artifacts up >> >>> >> for a >> >>> >> >> >>> >> vote: >> >>> >> >> >>> >> >> >>> >> >> >>> >> >> >>> >> >> >>> >> Git Branch and Commit SH: >> >>> >> >> >>> >> https://git-wip- >> >>> >> >> us.apache.org/repos/asf?p=cloudstack.git;a=shortlog;h=refs/heads/4.3 >> >>> >> Commit: ec4db7bbff60f0be96e39f51c0f17b12e0de440c >> >>> >> >> >>> >> >> >>> >> >> >>> >> List of changes: >> >>> >> >> >>> >> New Features in 4.3: >> >>> >> https://issues.apache.org/jira/issues/?filter=12325248 >> >>> >> >> >>> >> Improvement in 4.3: >> >>> >> https://issues.apache.org/jira/issues/?filter=12325249 >> >>> >> >> >>> >> Issues fixed in 4.3 >> >>> >> https://issues.apache.org/jira/issues/?filter=12326161 >> >>> >> >> >>> >> Known Issues in 4.3: >> >>> >> https://issues.apache.org/jira/issues/?filter=12326162 >> >>> >> >> >>> >> >> >>> >> >> >>> >> >> >>> >> >> >>> >> >> >>> >> >> >>> >> Source release (checksums and signatures are available at the >> >>> >> same >> >>> >> >> >>> >> location): >> >>> >> >> >>> >> https://dist.apache.org/repos/dist/dev/cloudstack/4.3.0/ >> >>> >> >> >>> >> >> >>> >> >> >>> >> PGP release keys (signed using 94BE0D7C): >> >>> >> >> >>> >> https://dist.apache.org/repos/dist/release/cloudstack/KEYS >> >>> >> >> >>> >> >> >>> >> >> >>> >> Testing instructions are here: >> >>> >> >> >>> >> >> https://cwiki.apache.org/confluence/display/CLOUDSTACK/Release+test+p >> >>> >> r >> >>> >> o >> >>> >> cedure >> >>> >> >> >>> >> >> >>> >> >> >>> >> Vote will be open for 36 hours (Thursday evening PST 8:00 PM) >> >>> >> >> >>> >> >> >>> >> >> >>> >> For sanity in tallying the vote, can PMC members please be >> >>> >> sure to indicate "(binding)" with their vote? >> >>> >> >> >>> >> >> >>> >> >> >>> >> [ ] +1 approve >> >>> >> >> >>> >> [ ] +0 no opinion >> >>> >> >> >>> >> [ ] -1 disapprove (and reason why) >> >>> >> >> >>> >> >> >>> >> Need Enterprise Grade Support for Apache CloudStack? >> >>> >> Our CloudStack Infrastructure >> >>> >> Support<http://shapeblue.com/cloudstack- >> >>> >> infrastructure-support/> offers the best 24/7 SLA for >> >>> >> CloudStack Environments. >> >>> >> >> >>> >> Apache CloudStack Bootcamp training courses >> >>> >> >> >>> >> **NEW!** CloudStack 4.2.1 >> >>> >> training<http://shapeblue.com/cloudstack- >> >>> >> training/> >> >>> >> 18th-19th February 2014, Brazil. >> >>> >> Classroom<http://shapeblue.com/cloudstack-training/> >> >>> >> 17th-23rd March 2014, Region A. Instructor led, On- >> >>> >> line<http://shapeblue.com/cloudstack-training/> >> >>> >> 24th-28th March 2014, Region B. Instructor led, On- >> >>> >> line<http://shapeblue.com/cloudstack-training/> >> >>> >> 16th-20th June 2014, Region A. Instructor led, On- >> >>> >> line<http://shapeblue.com/cloudstack-training/> >> >>> >> 23rd-27th June 2014, Region B. Instructor led, On- >> >>> >> line<http://shapeblue.com/cloudstack-training/> >> >>> >> >> >>> >> This email and any attachments to it may be confidential and >> >>> >> are intended solely for the use of the individual to whom it >> >>> >> is >> >>>addressed. >> >>> >> Any views or opinions expressed are solely those of the author >> >>> >> and >> do >> >>> >> not necessarily represent those of Shape Blue Ltd or related >> >>> >> companies. If you are not the intended recipient of this >> >>> >> email, you must neither take any action based upon its >> >>> >> contents, nor copy or show it to anyone. Please contact the >> >>> >> sender if you believe you have received this email in error. >> >>> >> Shape Blue Ltd is a company incorporated in England & Wales. >> >>> >> ShapeBlue Services India LLP is a company incorporated in >> >>> >> India and is operated under license from Shape Blue Ltd. Shape >> >>> >> Blue Brasil Consultoria Ltda is a company incorporated in >> >>> >> Brasil and is operated under license from Shape Blue >> >>> Ltd. ShapeBlue is a registered trademark. >> >>> > This email and any attachments to it may be confidential and >> >>> > are >> >>> intended solely for the use of the individual to whom it is addressed. >> >>>Any >> >>> views or opinions expressed are solely those of the author and do >> >>>not necessarily represent those of Shape Blue Ltd or related >> >>>companies. If you are not the intended recipient of this email, >> >>>you must neither take any action based upon its contents, nor >> >>>copy or show it to anyone. Please contact the sender if you >> >>>believe you have received this email in >> error. >> >>> Shape Blue Ltd is a company incorporated in England & Wales. >> >>>ShapeBlue Services India LLP is a company incorporated in India >> >>>and is operated under license from Shape Blue Ltd. Shape Blue >> >>>Brasil Consultoria Ltda is a company incorporated in Brasil and >> >>>is operated under license from Shape Blue Ltd. ShapeBlue is a >> >>>registered trademark. >> >>> >> >>> This email and any attachments to it may be confidential and are >> >>>intended solely for the use of the individual to whom it is >> >>>addressed. Any views or opinions expressed are solely those of >> >>>the author and do not >> necessarily >> >>> represent those of Shape Blue Ltd or related companies. If you >> >>>are not the intended recipient of this email, you must neither >> >>>take any action >> based >> >>> upon its contents, nor copy or show it to anyone. Please contact >> >>>the sender if you believe you have received this email in error. >> >>>Shape Blue Ltd is a company incorporated in England & Wales. >> >>>ShapeBlue Services India LLP is a company incorporated in India >> >>>and is operated under license from Shape Blue Ltd. Shape Blue >> >>>Brasil Consultoria Ltda is a company incorporated in Brasil and >> >>>is operated under license from Shape Blue Ltd. ShapeBlue is a >> >>>registered trademark. >> >>> This email and any attachments to it may be confidential and are >> >>>intended solely for the use of the individual to whom it is >> >>>addressed. Any views or opinions expressed are solely those of >> >>>the author and do not >> necessarily >> >>> represent those of Shape Blue Ltd or related companies. If you >> >>>are not the intended recipient of this email, you must neither >> >>>take any action >> based >> >>> upon its contents, nor copy or show it to anyone. Please contact >> >>>the sender if you believe you have received this email in error. >> >>>Shape Blue Ltd is a company incorporated in England & Wales. >> >>>ShapeBlue Services India LLP is a company incorporated in India >> >>>and is operated under license from Shape Blue Ltd. Shape Blue >> >>>Brasil Consultoria Ltda is a company incorporated in Brasil and >> >>>is operated under license from Shape Blue Ltd. ShapeBlue is a >> >>>registered trademark. >> >>> >> >> >> >> >> >> >> >>-- >> >>*Mike Tutkowski* >> >>*Senior CloudStack Developer, SolidFire Inc.* >> >>e: mike.tutkow...@solidfire.com >> >>o: 303.746.7302 >> >>Advancing the way the world uses the >> >>cloud<http://solidfire.com/solution/overview/?video=play> >> >>*(tm)* >> > >> >> >> >> -- >> Daan >> > > > > -- > *Mike Tutkowski* > *Senior CloudStack Developer, SolidFire Inc.* > e: mike.tutkow...@solidfire.com > o: 303.746.7302 > Advancing the way the world uses the > cloud<http://solidfire.com/solution/overview/?video=play> > *(tm)* -- Daan This email and any attachments to it may be confidential and are intended solely for the use of the individual to whom it is addressed. Any views or opinions expressed are solely those of the author and do not necessarily represent those of Shape Blue Ltd or related companies. If you are not the intended recipient of this email, you must neither take any action based upon its contents, nor copy or show it to anyone. Please contact the sender if you believe you have received this email in error. Shape Blue Ltd is a company incorporated in England & Wales. ShapeBlue Services India LLP is a company incorporated in India and is operated under license from Shape Blue Ltd. Shape Blue Brasil Consultoria Ltda is a company incorporated in Brasil and is operated under license from Shape Blue Ltd. ShapeBlue is a registered trademark.
