Return-Path: X-Original-To: apmail-incubator-cloudstack-dev-archive@minotaur.apache.org Delivered-To: apmail-incubator-cloudstack-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 182FBCA17 for ; Fri, 25 Jan 2013 21:22:34 +0000 (UTC) Received: (qmail 41048 invoked by uid 500); 25 Jan 2013 21:22:33 -0000 Delivered-To: apmail-incubator-cloudstack-dev-archive@incubator.apache.org Received: (qmail 40945 invoked by uid 500); 25 Jan 2013 21:22:33 -0000 Mailing-List: contact cloudstack-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: cloudstack-dev@incubator.apache.org Delivered-To: mailing list cloudstack-dev@incubator.apache.org Received: (qmail 40931 invoked by uid 99); 25 Jan 2013 21:22:33 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 25 Jan 2013 21:22:33 +0000 X-ASF-Spam-Status: No, hits=2.5 required=5.0 tests=HTML_MESSAGE,NORMAL_HTTP_TO_IP,RCVD_IN_DNSWL_LOW,SPF_SOFTFAIL X-Spam-Check-By: apache.org Received-SPF: softfail (athena.apache.org: transitioning domain of mike.tutkowski@solidfire.com does not designate 209.85.214.179 as permitted sender) Received: from [209.85.214.179] (HELO mail-ob0-f179.google.com) (209.85.214.179) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 25 Jan 2013 21:22:29 +0000 Received: by mail-ob0-f179.google.com with SMTP id un3so1000880obb.38 for ; Fri, 25 Jan 2013 13:22:08 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:content-type:x-gm-message-state; bh=5boR5ZTICsJbloaYLPjoE7pRK1j5V97Vgeumcv32daA=; b=ptimkqmnPe4DDUegjGKdgD+CLh7BEzFb50eLUtFBYVHnNJFbqsXKMowgNtXSLXuf/e OAxjpM9QGUZpTDu9sG2yokw2hBUYM29M2tPGk7cj5C1eadByHay0c5egRUpACGrOykru KbLYYWpPqKX3OiB3JA/w95phBzr7L7D56bZsy/kmUswQZ65+96eO2L0vbWc4+jm7G8Fg Q5zJymjEVV36i+2yzrazwaBe4g9FsZVgF+knMGUgc63vPhfeoiEw+fpP2sqaVYexHqmd 2YPGau8vTQ3srHrtDf/70fTaN4EFXCFk3+iMmH1Te/PVcACqspl41egInr59t70+Vg1k kX3w== MIME-Version: 1.0 X-Received: by 10.60.26.234 with SMTP id o10mr5725425oeg.116.1359148928092; Fri, 25 Jan 2013 13:22:08 -0800 (PST) Received: by 10.182.49.202 with HTTP; Fri, 25 Jan 2013 13:22:07 -0800 (PST) In-Reply-To: References: <8ECD6DAC-55B6-40B2-ABD8-4F4697F7D4C4@gmail.com> <4D35F9DF-F74C-49A9-9B38-89CF025D29E0@gmail.com> Date: Fri, 25 Jan 2013 14:22:07 -0700 Message-ID: Subject: Re: DevCloud Question From: Mike Tutkowski To: cloudstack-dev@incubator.apache.org Content-Type: multipart/alternative; boundary=e89a8f83a4d90e4a0704d42385a7 X-Gm-Message-State: ALoCoQmbP61X/wTwBYLPuFHmGdN3waM0yEOL9P6+ge/3y0/+2gfhZ+p22UZS0mHptgcZpfUEjSsT X-Virus-Checked: Checked by ClamAV on apache.org --e89a8f83a4d90e4a0704d42385a7 Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable Hi Marcus, I think I set up my iSCSI target correctly, but when I try to add Primary Storage, I get this exception. Any idea why this might be the case? Thanks! ERROR [cloud.api.ApiServer] (1567014364@qtp-858368545-7:) unhandled exception executing api command: createStoragePool com.cloud.utils.exception.CloudRuntimeException: Can not create storage pool through host 1 due to Catch Exception com.cloud.utils.exception.CloudRuntimeException, create StoragePool failed due to com.cloud.utils.exception.CloudRuntimeException: Unable to create Iscsi SR {targetIQN=3Diqn.2013-01.com.solidfire:volume-1, target=3D192.168.1.4} due to Unable to create Iscsi SR {targetIQN=3Diqn.2013-01.com.solidfire:volume-1, target=3D192.168.1.4} due= to The SR could not be connected because the driver was not recognised. on host:9d4c9db8-32f7-25c3-0435-eab4bf3adcea pool: 192.168.1.4/iqn.2013-01.com.solidfire:volume-1/0 at com.cloud.storage.StorageManagerImpl.createStoragePool(StorageManagerImpl.j= ava:1671) at com.cloud.storage.StorageManagerImpl.createPool(StorageManagerImpl.java:145= 0) at com.cloud.storage.StorageManagerImpl.createPool(StorageManagerImpl.java:212= ) at org.apache.cloudstack.api.command.admin.storage.CreateStoragePoolCmd.execut= e(CreateStoragePoolCmd.java:119) at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:168) at com.cloud.api.ApiServer.queueCommand(ApiServer.java:502) at com.cloud.api.ApiServer.handleRequest(ApiServer.java:353) at com.cloud.api.ApiServlet.processRequest(ApiServlet.java:310) at com.cloud.api.ApiServlet.doGet(ApiServlet.java:67) at javax.servlet.http.HttpServlet.service(HttpServlet.java:707) at javax.servlet.http.HttpServlet.service(HttpServlet.java:820) at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:511) at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:401) at org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216) at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:182) at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:766) at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:450) at org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandlerCol= lection.java:230) at org.mortbay.jetty.handler.HandlerCollection.handle(HandlerCollection.java:1= 14) at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152) at org.mortbay.jetty.Server.handle(Server.java:326) at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:542) at org.mortbay.jetty.HttpConnection$RequestHandler.headerComplete(HttpConnecti= on.java:928) at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:549) at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:212) at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:404) at org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:410= ) at org.mortbay.thread.QueuedThreadPool$PoolThread.run(QueuedThreadPool.java:58= 2) On Thu, Jan 24, 2013 at 7:25 PM, Mike Tutkowski < mike.tutkowski@solidfire.com> wrote: > Great description, Marcus - thanks for taking the time to write this out > for me! > > > On Thu, Jan 24, 2013 at 4:37 PM, Marcus Sorensen wro= te: > >> On Thu, Jan 24, 2013 at 4:05 PM, Mike Tutkowski >> wrote: >> > I do have some questions about some of the fields, though: >> > >> > For SolidFire storage, our nodes are on two networks: a management >> network >> > and a storage network. I supposed the Server field is looking for the >> IP >> > address of the node on the storage network? >> >> Yes, it would be the ip of the iscsi target that it can log into. >> Later, when cloudstack is actually configuring/creating LUNs on the >> solidfire device, then it will probably talk to the management >> network. But the functionality right now might be: >> >> 1. Admin creates 2T LUN on solid fire device >> 2. Admin registers that LUN as a primary storage in cloudstack >> 3. Cloudstack creates volumes on that LUN when volumes are asked for >> and the selected disk offering matches that LUN >> >> > >> > For Storage Tags, it says these needs to be equal to or a superset of >> the >> > tags on our Disk Offerings. Does this mean if I, say, have Disk >> Offerings >> > with tags of x, y, and z that only x, y, and/or z are valid entries >> here? >> > I'm not clear on the difference between a Disk Offering and Primary >> > Storage, I guess. >> >> A disk offering is just a profile. So it says something like '5GB on >> SSD'. Then when someone creates a volume, They get to choose from the >> available disk offerings. They don't get to say what size or where, >> they just ask for it based on disk offering. Then the offering is used >> to determine where the storage comes from (based on tags that match >> real primary storages), and how big it is. Now there's also a custom >> disk offering, which they can submit a size for, but the point really >> is that an admin can create a few offerings for someone to choose >> from, maybe they attach a price or something to each offering. It's >> just a way to define what packages are available in your cloud. >> >> More to your question, the tags are just arbitrary strings, but they >> do have to match. So for example, if I create a primary storage and >> want to tag it, I just make up a string. "SSD", or "FAST", or >> "testtag123". I can then create a disk offering with no tag, and it >> could select this primary storage, or I could specify one of these >> tags, which would force cloudstack to use this storage. You can add >> storage tags to service offerings as well, so when someone deploys a >> VM it's default OS disk (root) will go onto a particular primary >> storage. >> >> An example of where I use this is in my devcloud. By default it uses >> local storage for everything, but if I want to test my CLVM code, I >> have to create a disk offering with a tag, I use 'clvm', and then when >> I define my CLVM primary storage I also use that tag. This way when I >> try to create a volume or a VM I force it to use my CLVM storage, so I >> can watch/debug my code. >> >> > >> > Thanks! >> > >> > >> > On Thu, Jan 24, 2013 at 3:53 PM, Mike Tutkowski < >> > mike.tutkowski@solidfire.com> wrote: >> > >> >> I was in the wrong place. :) Found it now. >> >> >> >> >> >> On Thu, Jan 24, 2013 at 3:40 PM, Mike Tutkowski < >> >> mike.tutkowski@solidfire.com> wrote: >> >> >> >>> Hey Marcus, >> >>> >> >>> I'm trying to walk through your suggestions here: >> >>> >> >>> "Then I would add a primary storage of type iscsi, point it at >> >>> your solidfire server, and set a storage tag of 'solidfire'. You >> should >> >>> see >> >>> on the xen host (devcloud) that it creates a new SR and attaches to >> your >> >>> iscsi storage. Then I would create a service offering that uses this >> >>> storage (set a storage tag on it of 'solid fire'), and select this >> service >> >>> offering when deploying a VM." >> >>> >> >>> I brought the GUI up and went to the Service Offerings tab. I >> elected to >> >>> add a Disk Offering. Under Storage Type, I don't see an iSCSI optio= n >> - >> >>> just shared and local. Am I in the wrong place? >> >>> >> >>> Thanks! >> >>> >> >>> >> >>> On Wed, Jan 23, 2013 at 3:20 PM, Mike Tutkowski < >> >>> mike.tutkowski@solidfire.com> wrote: >> >>> >> >>>> Thanks for all the help, guys, in getting me up and running. :) >> >>>> >> >>>> >> >>>> On Wed, Jan 23, 2013 at 3:18 PM, Mike Tutkowski < >> >>>> mike.tutkowski@solidfire.com> wrote: >> >>>> >> >>>>> Looks like I had something messed up in my environment. I believe >> it's >> >>>>> OK now. :) >> >>>>> >> >>>>> >> >>>>> On Wed, Jan 23, 2013 at 3:04 PM, Mike Tutkowski < >> >>>>> mike.tutkowski@solidfire.com> wrote: >> >>>>> >> >>>>>> Let's see...I have Jetty running (as was the case earlier). I >> looked >> >>>>>> in devcloud.cfg and the IP addresses seem fine (192.168.56.1 and >> >>>>>> 192.168.56.10 are probably the most important ones). >> >>>>>> >> >>>>>> Are you thinking the dataCenterDeploy.py script (which references= a >> >>>>>> non-existent tools/marvin/marvin/datacenterCfg file) should >> reference >> >>>>>> tools/devcloud/devcloud.cfg? >> >>>>>> >> >>>>>> >> >>>>>> On Wed, Jan 23, 2013 at 2:58 PM, Sebastien Goasguen < >> runseb@gmail.com>wrote: >> >>>>>> >> >>>>>>> >> >>>>>>> On Jan 23, 2013, at 10:54 PM, Mike Tutkowski < >> >>>>>>> mike.tutkowski@solidfire.com> wrote: >> >>>>>>> >> >>>>>>> > Well...it was worth a shot. Apparently it actually wants ther= e >> to >> >>>>>>> be >> >>>>>>> > useful data in the file, too. :) >> >>>>>>> >> >>>>>>> Your mgt server needs to be running. >> >>>>>>> the maven command just calls marvin to deploy the "datacenter" o= n >> >>>>>>> your mgt server. >> >>>>>>> >> >>>>>>> the cfg file is in tools/devcloud/devcloud.cfg >> >>>>>>> >> >>>>>>> All the data is in there, you should not have to write it from >> >>>>>>> scratch. What may happen is that you have to edit it to change >> the ip of >> >>>>>>> the host.. >> >>>>>>> >> >>>>>>> >> >>>>>>> >> >>>>>>> > >> >>>>>>> > >> >>>>>>> > On Wed, Jan 23, 2013 at 2:47 PM, Mike Tutkowski < >> >>>>>>> > mike.tutkowski@solidfire.com> wrote: >> >>>>>>> > >> >>>>>>> >> Interesting...that didn't work either. :) >> >>>>>>> >> >> >>>>>>> >> I looked in the script and it does reference a datacenterCfg >> file. >> >>>>>>> Maybe >> >>>>>>> >> I can just create a blank one and see what happens. :) >> >>>>>>> >> >> >>>>>>> >> >> >>>>>>> >> On Wed, Jan 23, 2013 at 2:45 PM, Sebastien Goasguen < >> >>>>>>> runseb@gmail.com>wrote: >> >>>>>>> >> >> >>>>>>> >>> >> >>>>>>> >>> On Jan 23, 2013, at 10:42 PM, Sebastien Goasguen < >> >>>>>>> runseb@gmail.com> >> >>>>>>> >>> wrote: >> >>>>>>> >>> >> >>>>>>> >>>> >> >>>>>>> >>>> On Jan 23, 2013, at 10:38 PM, Mike Tutkowski < >> >>>>>>> >>> mike.tutkowski@solidfire.com> wrote: >> >>>>>>> >>>> >> >>>>>>> >>>>> Cool...that problem's solved now. :) However, the script >> >>>>>>> can't find a >> >>>>>>> >>>>> config file now. I don't see this config file anywhere on >> my >> >>>>>>> system. >> >>>>>>> >>>>> >> >>>>>>> >>>>> IOError: config file ./datacenterCfg not found. please >> specify >> >>>>>>> a valid >> >>>>>>> >>>>> config file >> >>>>>>> >>>>> >> >>>>>>> >>>> >> >>>>>>> >>>> try: >> >>>>>>> >>>> mvn -P developer -pl tools/devcloud -Ddeploysvr >> >>>>>>> >>> >> >>>>>>> >>> or: >> >>>>>>> >>> >> >>>>>>> >>> mvn -P developer,deploysvr -pl tools/devcloud -Ddeploysvr >> >>>>>>> >>> >> >>>>>>> >>> I am no maven expert=85:( >> >>>>>>> >>> >> >>>>>>> >>>> >> >>>>>>> >>>> this will use marvin to configure your mgt server >> infrastructure. >> >>>>>>> >>>> >> >>>>>>> >>>> if that does not work try: >> >>>>>>> >>>> >> >>>>>>> >>>> cd tools/devcloud >> >>>>>>> >>>> python ../marvin/marvin/deployDataCenter.py -i devcloud.cfg >> >>>>>>> >>>> >> >>>>>>> >>>> this is straight up out of Rohit's blog: >> >>>>>>> >>>> http://rohityadav.in >> >>>>>>> >>>> >> >>>>>>> >>>> Once you become familiar with this you can edit the >> devcloud.cfg >> >>>>>>> file >> >>>>>>> >>> and modify it to do what you want (storage, hosts, hyperviso= r >> >>>>>>> type, etc=85) >> >>>>>>> >>>> >> >>>>>>> >>>> >> >>>>>>> >>>> >> >>>>>>> >>>>> >> >>>>>>> >>>>> On Wed, Jan 23, 2013 at 2:17 PM, Sebastien Goasguen < >> >>>>>>> runseb@gmail.com >> >>>>>>> >>>> wrote: >> >>>>>>> >>>>> >> >>>>>>> >>>>>> >> >>>>>>> >>>>>> On Jan 23, 2013, at 10:10 PM, Mike Tutkowski < >> >>>>>>> >>> mike.tutkowski@solidfire.com> >> >>>>>>> >>>>>> wrote: >> >>>>>>> >>>>>> >> >>>>>>> >>>>>>> I tried the "backup" approach, as well, but it didn't wo= rk >> >>>>>>> for me. >> >>>>>>> >>> Looks >> >>>>>>> >>>>>>> like I'm missing a Python module? >> >>>>>>> >>>>>>> >> >>>>>>> >>>>>>> mtutkowski-lt:incubator-cloudstack mtutkowski$ cd >> >>>>>>> tools/devcloud >> >>>>>>> >>>>>>> mtutkowski-lt:devcloud mtutkowski$ pwd >> >>>>>>> >>>>>>> >> >>>>>>> >>>>>> >> >>>>>>> >>> >> >>>>>>> >> /Users/mtutkowski/documents/cloudstack/src/incubator-cloudstack/tools/de= vcloud >> >>>>>>> >>>>>>> mtutkowski-lt:devcloud mtutkowski$ python >> >>>>>>> >>>>>>> ../marvin/marvin/deployDataCenter.py >> >>>>>>> >>>>>>> Traceback (most recent call last): >> >>>>>>> >>>>>>> File "../marvin/marvin/deployDataCenter.py", line 21, in >> >>>>>>> >> >>>>>>> >>>>>>> import cloudstackTestClient >> >>>>>>> >>>>>>> File >> >>>>>>> >>>>>>> >> >>>>>>> >>>>>> >> >>>>>>> >>> >> >>>>>>> >> "/Users/mtutkowski/Documents/CloudStack/src/incubator-cloudstack/tools/m= arvin/marvin/cloudstackTestClient.py", >> >>>>>>> >>>>>>> line 20, in >> >>>>>>> >>>>>>> import dbConnection >> >>>>>>> >>>>>>> File >> >>>>>>> >>>>>>> >> >>>>>>> >>>>>> >> >>>>>>> >>> >> >>>>>>> >> "/Users/mtutkowski/Documents/CloudStack/src/incubator-cloudstack/tools/m= arvin/marvin/dbConnection.py", >> >>>>>>> >>>>>>> line 18, in >> >>>>>>> >>>>>>> import mysql >> >>>>>>> >>>>>>> ImportError: No module named mysql >> >>>>>>> >>>>>>> >> >>>>>>> >>>>>>> I did download mysql-connector-python, but I'm not that >> >>>>>>> familiar with >> >>>>>>> >>>>>>> Python and where to put this download so it can be >> leveraged. >> >>>>>>> >>>>>> >> >>>>>>> >>>>>> How did you install it ? >> >>>>>>> >>>>>> >> >>>>>>> >>>>>> you should try something like: >> >>>>>>> >>>>>> >> >>>>>>> >>>>>> sudo easy_install mysql-connector-python 1.0 >> >>>>>>> >>>>>> >> >>>>>>> >>>>>>> >> >>>>>>> >>>>>>> Thanks! >> >>>>>>> >>>>>>> >> >>>>>>> >>>>>>> >> >>>>>>> >>>>>>> On Wed, Jan 23, 2013 at 1:49 PM, Sebastien Goasguen < >> >>>>>>> >>> runseb@gmail.com >> >>>>>>> >>>>>>> wrote: >> >>>>>>> >>>>>>> >> >>>>>>> >>>>>>>> >> >>>>>>> >>>>>>>> On Jan 23, 2013, at 9:16 PM, David Nalley > > >> >>>>>>> wrote: >> >>>>>>> >>>>>>>> >> >>>>>>> >>>>>>>>> On Wed, Jan 23, 2013 at 2:35 PM, Mike Tutkowski >> >>>>>>> >>>>>>>>> wrote: >> >>>>>>> >>>>>>>>>> This really was a great overview of using DevCloud. = I >> >>>>>>> wonder if >> >>>>>>> >>> we >> >>>>>>> >>>>>>>> might >> >>>>>>> >>>>>>>>>> link to it from here: >> >>>>>>> >>>>>>>>>> >> >>>>>>> >>>>>>>>>> >> >>>>>>> https://cwiki.apache.org/confluence/display/CLOUDSTACK/DevCloud >> >>>>>>> >>>>>>>>>> >> >>>>>>> >>>>>>>>> >> >>>>>>> >>>>>>>>> >> >>>>>>> >>>>>>>>> It's a wiki, please edit boldly! >> >>>>>>> >>>>>>>>> >> >>>>>>> >>>>>>>>> --David >> >>>>>>> >>>>>>>> >> >>>>>>> >>>>>>>> Mike, I added the video link to the new docs, but it >> won't >> >>>>>>> hit until >> >>>>>>> >>>>>>>> release... >> >>>>>>> >>>>>>>> >> >>>>>>> >>>>>>>> >> >>>>>>> >>>>>>> >> >>>>>>> >>>>>>> >> >>>>>>> >>>>>>> -- >> >>>>>>> >>>>>>> *Mike Tutkowski* >> >>>>>>> >>>>>>> *Senior CloudStack Developer, SolidFire Inc.* >> >>>>>>> >>>>>>> e: mike.tutkowski@solidfire.com >> >>>>>>> >>>>>>> o: 303.746.7302 >> >>>>>>> >>>>>>> Advancing the way the world uses the >> >>>>>>> >>>>>>> cloud >> >>>>>>> >>>>>>> *=99* >> >>>>>>> >>>>>> >> >>>>>>> >>>>>> >> >>>>>>> >>>>> >> >>>>>>> >>>>> >> >>>>>>> >>>>> -- >> >>>>>>> >>>>> *Mike Tutkowski* >> >>>>>>> >>>>> *Senior CloudStack Developer, SolidFire Inc.* >> >>>>>>> >>>>> e: mike.tutkowski@solidfire.com >> >>>>>>> >>>>> o: 303.746.7302 >> >>>>>>> >>>>> Advancing the way the world uses the >> >>>>>>> >>>>> cloud >> >>>>>>> >>>>> *=99* >> >>>>>>> >>>> >> >>>>>>> >>> >> >>>>>>> >>> >> >>>>>>> >> >> >>>>>>> >> >> >>>>>>> >> -- >> >>>>>>> >> *Mike Tutkowski* >> >>>>>>> >> *Senior CloudStack Developer, SolidFire Inc.* >> >>>>>>> >> e: mike.tutkowski@solidfire.com >> >>>>>>> >> o: 303.746.7302 >> >>>>>>> >> Advancing the way the world uses the cloud< >> >>>>>>> http://solidfire.com/solution/overview/?video=3Dplay> >> >>>>>>> >> *=99* >> >>>>>>> >> >> >>>>>>> > >> >>>>>>> > >> >>>>>>> > >> >>>>>>> > -- >> >>>>>>> > *Mike Tutkowski* >> >>>>>>> > *Senior CloudStack Developer, SolidFire Inc.* >> >>>>>>> > e: mike.tutkowski@solidfire.com >> >>>>>>> > o: 303.746.7302 >> >>>>>>> > Advancing the way the world uses the >> >>>>>>> > cloud >> >>>>>>> > *=99* >> >>>>>>> >> >>>>>>> >> >>>>>> >> >>>>>> >> >>>>>> -- >> >>>>>> *Mike Tutkowski* >> >>>>>> *Senior CloudStack Developer, SolidFire Inc.* >> >>>>>> e: mike.tutkowski@solidfire.com >> >>>>>> o: 303.746.7302 >> >>>>>> Advancing the way the world uses the cloud< >> http://solidfire.com/solution/overview/?video=3Dplay> >> >>>>>> *=99* >> >>>>>> >> >>>>> >> >>>>> >> >>>>> >> >>>>> -- >> >>>>> *Mike Tutkowski* >> >>>>> *Senior CloudStack Developer, SolidFire Inc.* >> >>>>> e: mike.tutkowski@solidfire.com >> >>>>> o: 303.746.7302 >> >>>>> Advancing the way the world uses the cloud< >> http://solidfire.com/solution/overview/?video=3Dplay> >> >>>>> *=99* >> >>>>> >> >>>> >> >>>> >> >>>> >> >>>> -- >> >>>> *Mike Tutkowski* >> >>>> *Senior CloudStack Developer, SolidFire Inc.* >> >>>> e: mike.tutkowski@solidfire.com >> >>>> o: 303.746.7302 >> >>>> Advancing the way the world uses the cloud< >> http://solidfire.com/solution/overview/?video=3Dplay> >> >>>> *=99* >> >>>> >> >>> >> >>> >> >>> >> >>> -- >> >>> *Mike Tutkowski* >> >>> *Senior CloudStack Developer, SolidFire Inc.* >> >>> e: mike.tutkowski@solidfire.com >> >>> o: 303.746.7302 >> >>> Advancing the way the world uses the cloud< >> http://solidfire.com/solution/overview/?video=3Dplay> >> >>> *=99* >> >>> >> >> >> >> >> >> >> >> -- >> >> *Mike Tutkowski* >> >> *Senior CloudStack Developer, SolidFire Inc.* >> >> e: mike.tutkowski@solidfire.com >> >> o: 303.746.7302 >> >> Advancing the way the world uses the cloud< >> http://solidfire.com/solution/overview/?video=3Dplay> >> >> *=99* >> >> >> > >> > >> > >> > -- >> > *Mike Tutkowski* >> > *Senior CloudStack Developer, SolidFire Inc.* >> > e: mike.tutkowski@solidfire.com >> > o: 303.746.7302 >> > Advancing the way the world uses the >> > cloud >> > *=99* >> > > > > -- > *Mike Tutkowski* > *Senior CloudStack Developer, SolidFire Inc.* > e: mike.tutkowski@solidfire.com > o: 303.746.7302 > Advancing the way the world uses the cloud > *=99* > --=20 *Mike Tutkowski* *Senior CloudStack Developer, SolidFire Inc.* e: mike.tutkowski@solidfire.com o: 303.746.7302 Advancing the way the world uses the cloud *=99* --e89a8f83a4d90e4a0704d42385a7--